@wildo-ai/framework-knowledge 1.1.11 → 1.1.13
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/claude-marketplace/.claude-plugin/marketplace.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +4 -0
- package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +25 -3
- package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +40 -12
- package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +3 -3
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +12 -0
- package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +19 -2
- package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +33 -9
- package/dist/esm/framework-knowledge.definitions.d.ts +2 -3
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +180 -32
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js.map +1 -1
- package/dist/esm/framework-knowledge.research-provenance.d.ts +6 -4
- package/dist/esm/framework-knowledge.research-provenance.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.research-provenance.js.map +1 -1
- package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.js.map +1 -1
- package/dist/esm/index.d.ts.map +1 -1
- package/dist/esm/index.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -3
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +4 -12
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +12 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +7 -4
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +76 -14
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +0 -4
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +3 -15
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +35 -14
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +16 -8
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +19 -8
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +30 -3
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +87 -16
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +2 -2
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +5 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +3 -2
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +45 -10
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +61 -21
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +4 -3
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +8 -5
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +3 -5
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +3 -3
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +8 -6
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +5 -0
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +8 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +4 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +11 -3
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +6 -4
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +3 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +4 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +10 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +36 -13
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +8 -2
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +7 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +4 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +34 -6
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +5 -2
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +4 -3
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +2 -2
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +22 -10
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +39 -29
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +8 -3
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -7
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +2 -2
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +13 -5
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +3 -7
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +12 -14
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +3 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +2 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +3 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +2 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts +4 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.js +14 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +3 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +4 -2
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +34 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +35 -17
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/esm/source-anchor-grammar.d.ts.map +1 -1
- package/dist/esm/source-anchor-grammar.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
- package/dist/knowledge/manifest.json +7 -7
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +6 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +4 -4
- package/dist/knowledge/playbooks/bottom_up.build/method.md +12 -2
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +5 -3
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +439 -27
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +15 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +203 -7
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -5
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +2 -2
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +2 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +104 -2
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +59 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +18 -6
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +121 -24
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +55 -8
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +15 -8
- package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +2 -1
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +19 -2
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +4 -3
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +34 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +9 -2
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +1 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +27 -12
- package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +11 -5
- package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +4 -4
- package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +7 -2
- package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +1 -0
- package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +6 -6
- package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +3 -4
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +56 -5
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +3 -2
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +6 -4
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +5 -1
- package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +8 -1
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -3
- package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +11 -4
- package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +3 -2
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +16 -6
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +3 -2
- package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +5 -1
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/method.md +43 -11
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +24 -8
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +6 -2
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +49 -14
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +3 -3
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +6 -2
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +20 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +4 -3
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +69 -65
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +11 -7
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.definition/method.md +3 -1
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +11 -3
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +4 -2
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +4 -3
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +3 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +3 -2
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +14 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +11 -7
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +7 -0
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +5 -1
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +6 -1
- package/dist/knowledge/playbooks/top_down.service-method/method.md +19 -1
- package/dist/knowledge/playbooks/top_down.service-method/playbook.json +16 -4
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +5 -2
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +9 -3
- package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +17 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +59 -15
- package/dist/knowledge/references/application-documentation-chapters.config.md +45 -10
- package/dist/knowledge/references/application-documentation-plan.config.md +2 -2
- package/dist/knowledge/references/application-maturity.config.md +70 -1
- package/dist/knowledge/references/backend.inbound-channels.attachment-adoption.md +4 -2
- package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +52 -11
- package/dist/knowledge/references/backend.inbound-handlers.definition.md +38 -1
- package/dist/knowledge/references/brand.name-screening.config.md +30 -3
- package/dist/knowledge/references/build-plan.task-graph.config.md +200 -4
- package/dist/knowledge/references/business-model.pricing-plan.config.md +12 -9
- package/dist/knowledge/references/business-model.snapshot.config.md +29 -2
- package/dist/knowledge/references/business-model.snapshot.validation.md +11 -8
- package/dist/knowledge/references/companion.introspection.behaviors.market.md +3 -0
- package/dist/knowledge/references/companion.market.generation-service.md +46 -5
- package/dist/knowledge/references/companion.market.prompt-renderer.md +1 -1
- package/dist/knowledge/references/companion.technical-doc.service.md +195 -63
- package/dist/knowledge/references/domain-plan.record-partition.md +105 -0
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +3 -1
- package/dist/knowledge/references/engine.saas-technical-doc.config.md +69 -15
- package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +10 -0
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +6 -0
- package/dist/knowledge/references/example.backend.custom-operation.declared-refusal-code.md +41 -0
- package/dist/knowledge/references/example.backend.custom-operation.external-effect-reservation.md +107 -0
- package/dist/knowledge/references/example.blueprint.definition.internal-tool.md +4 -2
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +8 -5
- package/dist/knowledge/references/example.infra.environment-config.local.md +13 -66
- package/dist/knowledge/references/example.module.companion-exports.full.md +1 -0
- package/dist/knowledge/references/example.module.relationships.actor-edge-back-to-scope-owner.md +35 -35
- package/dist/knowledge/references/example.navigation.one-entry-per-concept.md +47 -0
- package/dist/knowledge/references/example.organization-identity.system-of-record-partitions.md +18 -0
- package/dist/knowledge/references/example.provider.backend-module-shape.md +28 -4
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +0 -4
- package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +21 -0
- package/dist/knowledge/references/example.resource.custom-view.backend-refusal.md +75 -0
- package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +8 -7
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +37 -2
- package/dist/knowledge/references/example.resource.ui-behavior.record-template.md +0 -1
- package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +1 -1
- package/dist/knowledge/references/example.resource.ui-behavior.workflow-record-page.md +212 -0
- package/dist/knowledge/references/example.subject-export.portability-archive.md +42 -0
- package/dist/knowledge/references/example.views.app-level.workflow-home.md +238 -0
- package/dist/knowledge/references/example.website.demo.complete-items.md +3 -3
- package/dist/knowledge/references/example.website.pricing.audit-payloads.md +38 -0
- package/dist/knowledge/references/example.website.pricing.catalog-load.md +77 -0
- package/dist/knowledge/references/example.website.pricing.offers.md +43 -0
- package/dist/knowledge/references/example.website.pricing.plans-section.md +20 -0
- package/dist/knowledge/references/example.website.pricing.plans.md +88 -0
- package/dist/knowledge/references/example.website.section.stats.md +1 -1
- package/dist/knowledge/references/experience-plan.config.md +111 -1
- package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +2 -0
- package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +8 -1
- package/dist/knowledge/references/external-connectors.models.hook-signature-algorithms.md +104 -0
- package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +11 -6
- package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +165 -0
- package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +1035 -19
- package/dist/knowledge/references/external-connectors.private.provider-compliance-state-collector.md +36 -0
- package/dist/knowledge/references/external-connectors.private.provider-configuration-check.md +69 -0
- package/dist/knowledge/references/integration-plan.config.md +7 -7
- package/dist/knowledge/references/placement-plan.config.md +19 -0
- package/dist/knowledge/references/platform.config.backing-services.md +9 -11
- package/dist/knowledge/references/platform.config.environment.deployment.md +133 -8
- package/dist/knowledge/references/platform.config.infra-provider-resolution.md +3 -3
- package/dist/knowledge/references/platform.config.infrastructure-host.md +1 -1
- package/dist/knowledge/references/platform.config.platform-key-management.md +89 -10
- package/dist/knowledge/references/platform.config.saas.md +20 -18
- package/dist/knowledge/references/presets.3d.frame-style-resolution.md +65 -0
- package/dist/knowledge/references/presets.layouts-2d.authoring.md +1 -1
- package/dist/knowledge/references/presets.models.field-form-control-variant.md +32 -0
- package/dist/knowledge/references/presets.models.labelling.sections.md +39 -0
- package/dist/knowledge/references/presets.models.surface-policy.defaults.md +3 -3
- package/dist/knowledge/references/presets.models.surface-variant.md +5 -4
- package/dist/knowledge/references/presets.themes.compose-theme.md +2 -1
- package/dist/knowledge/references/requirements.engine-substance.md +38 -0
- package/dist/knowledge/references/requirements.functional-requirement.config.md +11 -0
- package/dist/knowledge/references/requirements.non-functional-requirement.config.md +15 -4
- package/dist/knowledge/references/requirements.snapshot.config.md +2 -3
- package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +49 -2
- package/dist/knowledge/references/saas.backend.a2a.token-budget.md +11 -4
- package/dist/knowledge/references/saas.backend.actor-execution-continuation.md +21 -0
- package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +5 -1
- package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +1 -1
- package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +13 -1
- package/dist/knowledge/references/saas.backend.custom-operation.authoritative-fields.md +4 -1
- package/dist/knowledge/references/saas.backend.custom-operation.core-write-precondition.md +38 -0
- package/dist/knowledge/references/saas.backend.custom-operation.external-effect-reservation.md +109 -0
- package/dist/knowledge/references/saas.backend.custom-operation.hook-transaction-posture.md +43 -0
- package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +1 -1
- package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +62 -13
- package/dist/knowledge/references/saas.backend.domain-module.md +30 -1
- package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +26 -3
- package/dist/knowledge/references/saas.backend.flows-actors.chat-reply-handler.md +13 -1
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +435 -2
- package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +5 -3
- package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +1 -1
- package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +9 -4
- package/dist/knowledge/references/saas.backend.flows.start-flow-method.md +2 -1
- package/dist/knowledge/references/saas.backend.privacy.subject-export-archive.md +26 -0
- package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +21 -19
- package/dist/knowledge/references/saas.backend.system-access-service.md +159 -4
- package/dist/knowledge/references/saas.config.content-security-policy.md +26 -9
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +1 -1
- package/dist/knowledge/references/saas.data-seeding.modes.md +4 -1
- package/dist/knowledge/references/saas.data-seeding.row-reference.md +2 -4
- package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +6 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +2 -0
- package/dist/knowledge/references/saas.frontend.chart-dashboard-view.md +43 -0
- package/dist/knowledge/references/saas.frontend.chart-dashboard.md +133 -0
- package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +8 -4
- package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +76 -9
- package/dist/knowledge/references/saas.frontend.command-menu.search-resource.md +3 -3
- package/dist/knowledge/references/saas.frontend.errors.backend-refusal.md +96 -0
- package/dist/knowledge/references/saas.frontend.execution-view.definition.md +40 -0
- package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +4 -0
- package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +3 -5
- package/dist/knowledge/references/saas.frontend.record-page-parts.md +117 -0
- package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +46 -16
- package/dist/knowledge/references/saas.frontend.related-resource-sections.md +6 -0
- package/dist/knowledge/references/saas.frontend.resource-header-title.md +1 -1
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +43 -9
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +259 -15
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -2
- package/dist/knowledge/references/saas.frontend.section-stages.md +63 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +42 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +6 -9
- package/dist/knowledge/references/saas.frontend.viewer-may-perform-operation.md +52 -0
- package/dist/knowledge/references/saas.models.agent-suspension.md +8 -8
- package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +21 -0
- package/dist/knowledge/references/saas.models.auth.relationship-grantor-authentication.md +2 -2
- package/dist/knowledge/references/saas.models.chart-dashboard-tile-sizes.md +40 -0
- package/dist/knowledge/references/saas.models.config.declared-type-renames.md +246 -0
- package/dist/knowledge/references/saas.models.config.organization-types.md +20 -0
- package/dist/knowledge/references/saas.models.conversation-threads.md +39 -3
- package/dist/knowledge/references/saas.models.crypto-keys.floors.md +10 -0
- package/dist/knowledge/references/saas.models.crypto-keys.local-provider.md +2 -0
- package/dist/knowledge/references/saas.models.crypto-keys.purpose-descriptor.md +39 -0
- package/dist/knowledge/references/saas.models.crypto-keys.purposes.md +7 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -78
- package/dist/knowledge/references/saas.models.engine-capabilities.md +11 -2
- package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +3 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +15 -8
- package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report.md +13 -9
- package/dist/knowledge/references/saas.models.flows-actors.agent-configuration.md +29 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-content-guardrails-environment.md +52 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-operation-record.md +7 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-decision-decider.md +8 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-input-form.md +47 -12
- package/dist/knowledge/references/saas.models.flows-actors.operation-approval-requirement.md +31 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +3 -3
- package/dist/knowledge/references/saas.models.flows.runnable-model.md +21 -2
- package/dist/knowledge/references/saas.models.guidance-flow.md +1 -1
- package/dist/knowledge/references/saas.models.http-api-binding.md +19 -8
- package/dist/knowledge/references/saas.models.human-decision-review-marker.md +1 -1
- package/dist/knowledge/references/saas.models.inbound-channels.md +71 -2
- package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +1 -1
- package/dist/knowledge/references/saas.models.notifications.targets.md +3 -1
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +201 -15
- package/dist/knowledge/references/saas.models.organization-assigned-rows-declaration.md +2 -1
- package/dist/knowledge/references/saas.models.organization-dashboard-layout.md +61 -0
- package/dist/knowledge/references/saas.models.organization-own-rows-declaration.md +5 -2
- package/dist/knowledge/references/saas.models.organizations.identity-declaration.md +201 -0
- package/dist/knowledge/references/saas.models.organizations.organization-relationships.md +25 -3
- package/dist/knowledge/references/saas.models.organizations.relationship-invitations.md +6 -2
- package/dist/knowledge/references/saas.models.organizations.relationship-kinds.md +14 -0
- package/dist/knowledge/references/saas.models.organizations.relationship-record-separation.md +1 -0
- package/dist/knowledge/references/saas.models.privacy.data-residency.md +676 -0
- package/dist/knowledge/references/saas.models.privacy.legal-holds.md +46 -2
- package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +6 -0
- package/dist/knowledge/references/saas.models.privacy.retention-binding.md +84 -1
- package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +10 -0
- package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +5 -3
- package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +2 -0
- package/dist/knowledge/references/saas.models.privacy.subject-export.md +134 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +5 -0
- package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +12 -6
- package/dist/knowledge/references/saas.models.providers.compliance-choice.md +15 -0
- package/dist/knowledge/references/saas.models.providers.processing-region-reach.md +132 -0
- package/dist/knowledge/references/saas.models.providers.processing-region-selection.md +139 -0
- package/dist/knowledge/references/saas.models.representative-activity.md +4 -0
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +107 -42
- package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +35 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +4 -2
- package/dist/knowledge/references/saas.models.resource-config.operation-condition-parameters.md +56 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +16 -6
- package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +38 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +14 -16
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +2 -2
- package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +21 -0
- package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +32 -15
- package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +5 -4
- package/dist/knowledge/references/saas.models.roles.definition.md +12 -1
- package/dist/knowledge/references/saas.models.roles.organization-defaults.md +6 -0
- package/dist/knowledge/references/saas.models.schema-family-builder.md +17 -2
- package/dist/knowledge/references/saas.models.system-of-record-actions.md +65 -1
- package/dist/knowledge/references/saas.models.system-of-record-capabilities.md +3 -1
- package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +16 -0
- package/dist/knowledge/references/saas.models.systems-of-record.md +75 -14
- package/dist/knowledge/references/saas.public-runtime.contract.md +41 -23
- package/dist/knowledge/references/saas.rag.retrieval-refusals.md +3 -2
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +12 -4
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +21 -2
- package/dist/knowledge/references/saas.specifications.engine-resource-sub-domain.md +105 -0
- package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +6 -2
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +20 -3
- package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +100 -71
- package/dist/knowledge/references/saas.specifications.translation-glossary.md +80 -0
- package/dist/knowledge/references/saas.website.astro.label-loader.md +44 -10
- package/dist/knowledge/references/saas.website.astro.runtime-helper.md +3 -2
- package/dist/knowledge/references/saas.website.blog.collection-config.md +36 -32
- package/dist/knowledge/references/saas.website.blog.cover-resolver.md +1 -1
- package/dist/knowledge/references/saas.website.blog.frontmatter.md +2 -2
- package/dist/knowledge/references/saas.website.blog.post-renderer.md +2 -2
- package/dist/knowledge/references/saas.website.blog.react-mdx-integration.md +26 -19
- package/dist/knowledge/references/saas.website.blog.react-mdx-query.md +1 -1
- package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +3 -1
- package/dist/knowledge/references/saas.website.config.site-context-loader.md +6 -3
- package/dist/knowledge/references/saas.website.label-keys.format.md +3 -2
- package/dist/knowledge/references/saas.website.label-pack.validator.md +3 -1
- package/dist/knowledge/references/service-method.config.md +35 -2
- package/dist/knowledge/references/vision.constraint.config.md +4 -2
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +60 -0
- package/dist/knowledge/references/zod.decorators.data-categories.md +46 -46
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +24 -0
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +11 -0
- package/dist/knowledge/references/zod.decorators.file-schema.md +4 -3
- package/dist/knowledge/references/zod.decorators.rag-source.md +20 -20
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +2 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +30 -24
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +63 -0
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +63 -0
- package/dist/knowledge/references/zod.factories.bigdecimal.md +4 -4
- package/dist/knowledge/references/zod.factories.code.md +4 -4
- package/dist/knowledge/references/zod.factories.duration.md +4 -4
- package/dist/knowledge/references/zod.factories.money.md +4 -4
- package/dist/knowledge/references/zod.factories.phone.md +4 -4
- package/dist/knowledge/references/zod.factories.year-month.md +79 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +455 -2
- package/dist/knowledge/registries/playbooks.json +51 -39
- package/dist/knowledge/registries/source-tags.json +2505 -1627
- package/dist/knowledge/rules/database-migration-obligation.md +6 -7
- package/dist/knowledge/rules/live-context-door.md +1 -1
- package/dist/knowledge/skills/INDEX.md +3 -1
- package/dist/knowledge/skills/agent-work-review/references/framework-actor-execution-continuation-api.md +24 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +1 -1
- package/dist/knowledge/skills/agent-work-review/references/framework-human-input-form-api.md +47 -12
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +30 -19
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +48 -13
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +2 -2
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -11
- package/dist/knowledge/skills/application-database-migrations/references/postgresql-supported-surfaces.md +64 -0
- package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +13 -11
- package/dist/knowledge/skills/application-roles-authoring/SKILL.md +28 -3
- package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +18 -1
- package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +22 -1
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +46 -2
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-assigned-rows-declaration-api.md +5 -3
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-organization-identity-declaration-api.md +247 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-own-rows-declaration-api.md +12 -5
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +6 -0
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +31 -2
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +51 -14
- package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +4 -1
- package/dist/knowledge/skills/backend-custom-operation/references/declared-refusal-codes.md +95 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +2 -2
- package/dist/knowledge/skills/backend-custom-operation/references/framework-core-write-precondition-api.md +73 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-error-handling-api.md +5 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-external-effect-reservation-api.md +276 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-hook-transaction-posture-api.md +90 -0
- package/dist/knowledge/skills/blueprint-authoring/SKILL.md +4 -2
- package/dist/knowledge/skills/brand-name-screening/SKILL.md +13 -2
- package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +30 -3
- package/dist/knowledge/skills/chat-agent-conversations/SKILL.md +3 -0
- package/dist/knowledge/skills/chat-agent-conversations/references/framework-chat-conversations-api.md +13 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +45 -4
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +17 -7
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +859 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +6 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +2 -0
- package/dist/knowledge/skills/config-app-shell/SKILL.md +5 -1
- package/dist/knowledge/skills/config-app-shell/references/framework-command-menu-omnibox-api.md +3 -3
- package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +4 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +1 -1
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +8 -7
- package/dist/knowledge/skills/config-design-system/references/framework-theme-composition-api.md +44 -1
- package/dist/knowledge/skills/config-navigation/SKILL.md +2 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +5 -0
- package/dist/knowledge/skills/config-navigation/references/one-entry-per-concept.md +101 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +2 -2
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +40 -3
- package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +20 -1
- package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +75 -11
- package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +21 -19
- package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +26 -9
- package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +240 -9
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +16 -2
- package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +116 -16
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +20 -18
- package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +1 -1
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +11 -1
- package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +5 -1
- package/dist/knowledge/skills/config-saas-backend/references/framework-declared-type-renames-api.md +261 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +20 -0
- package/dist/knowledge/skills/config-saas-backend/references/renaming-organization-and-user-types.md +69 -0
- package/dist/knowledge/skills/configure-billing/SKILL.md +6 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +28 -4
- package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +2 -0
- package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +4 -1
- package/dist/knowledge/skills/electronic-signature-deliverables/SKILL.md +131 -0
- package/dist/knowledge/skills/electronic-signature-deliverables/references/what-makes-a-request-signed.md +78 -0
- package/dist/knowledge/skills/email-add-template/SKILL.md +1 -1
- package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +11 -8
- package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +3 -2
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +31 -9
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +11 -4
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +26 -3
- package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +13 -3
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +27 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +34 -11
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +8 -5
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-behavior-reports-api.md +13 -9
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +188 -10
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-operation-record-api.md +7 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-suspension-api.md +11 -9
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +21 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +3 -3
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-realtime-catalog.md +7 -1
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +447 -8
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +30 -1
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-model-spend-limits-api.md +36 -15
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +8 -0
- package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +13 -3
- package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-flow-model-api.md +21 -2
- package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +2 -1
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +13 -3
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +33 -1
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +5 -3
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +1 -1
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +6 -5
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +50 -14
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +1 -1
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +31 -2
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-translation-glossary-api.md +87 -0
- package/dist/knowledge/skills/inbound-channels/SKILL.md +31 -9
- package/dist/knowledge/skills/inbound-channels/references/email-channel.md +16 -4
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +169 -23
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +38 -1
- package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +43 -4
- package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +15 -3
- package/dist/knowledge/skills/inbound-channels/references/sms-channel.md +93 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +149 -77
- package/dist/knowledge/skills/infra-environment-config/references/framework-agent-content-guardrails-environment-api.md +67 -0
- package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +12 -14
- package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +133 -8
- package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +1 -1
- package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +89 -10
- package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-authoring-api.md +1 -1
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-focal-plane-settings-api.md +16 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +72 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +2 -2
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +12 -9
- package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +3 -3
- package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +2 -2
- package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +18 -10
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +7 -7
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +24 -2
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +33 -2
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +47 -6
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +61 -8
- package/dist/knowledge/skills/model-cost-attribution/SKILL.md +3 -1
- package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +1 -1
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +107 -42
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +21 -2
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +30 -1
- package/dist/knowledge/skills/module-relationships/SKILL.md +92 -91
- package/dist/knowledge/skills/organization-relationships/references/framework-organization-relationships-api.md +31 -5
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-grantor-authentication-api.md +2 -2
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-kinds-api.md +34 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-record-separation-api.md +1 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-representative-activity-api.md +4 -0
- package/dist/knowledge/skills/professional-qualifications/references/framework-operation-approval-requirement-api.md +31 -0
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +272 -15
- package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +4 -5
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-compliance-state-collector-api.md +96 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-configuration-check-api.md +130 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +8 -1
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-inbound-endpoint-api.md +124 -3
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +165 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +6 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-processing-region-api.md +340 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +11 -6
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +2 -0
- package/dist/knowledge/skills/provider-frontend-module/SKILL.md +5 -2
- package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +1 -1
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +17 -3
- package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +1035 -19
- package/dist/knowledge/skills/resource-add-field/SKILL.md +7 -0
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +322 -15
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +9 -5
- package/dist/knowledge/skills/resource-add-resource/references/framework-engine-api-reference-categories-api.md +119 -0
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +107 -42
- package/dist/knowledge/skills/resource-chat-commands/SKILL.md +2 -1
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +71 -5
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +2 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-approval-api.md +48 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +34 -7
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-bulk-api.md +15 -11
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +66 -27
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +140 -58
- package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +28 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +34 -10
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +5 -4
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +158 -138
- package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +52 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +205 -19
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +253 -25
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +126 -1
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +259 -15
- package/dist/knowledge/skills/resource-custom-view/references/framework-backend-refusal-api.md +110 -0
- package/dist/knowledge/skills/resource-external-data/SKILL.md +46 -12
- package/dist/knowledge/skills/resource-external-data/references/bidirectional-pipelines.md +1 -1
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +15 -8
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +19 -8
- package/dist/knowledge/skills/resource-external-data/references/framework-system-of-record-capabilities-api.md +3 -1
- package/dist/knowledge/skills/resource-external-data/references/local-test-doubles.md +121 -0
- package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +1 -1
- package/dist/knowledge/skills/resource-external-data/references/partition-from-the-domain-plan.md +230 -0
- package/dist/knowledge/skills/resource-external-data/references/presenting-a-copy-and-a-read-through.md +73 -0
- package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +26 -5
- package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +76 -6
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +8 -0
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +12 -9
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +11 -2
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +29 -2
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +20 -20
- package/dist/knowledge/skills/resource-retention-binding/SKILL.md +18 -2
- package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +46 -2
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +84 -1
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +10 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +5 -3
- package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +21 -0
- package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +14 -2
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +1 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +4 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +78 -17
- package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +2 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +26 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +46 -46
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +17 -2
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +36 -24
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +63 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +104 -23
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +123 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +72 -0
- package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +42 -2
- package/dist/knowledge/skills/resource-status-lifecycle/references/framework-operation-condition-parameters-api.md +67 -0
- package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +16 -12
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +66 -3
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +89 -10
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +11 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +263 -17
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-record-page-parts-api.md +155 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +83 -16
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +44 -10
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-section-stages-api.md +102 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/record-page-anatomy.md +9 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +33 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/visual-quality-rubric.md +19 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/workflow-record-page.md +264 -0
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +24 -4
- package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +12 -0
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +7 -6
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +6 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +42 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +6 -9
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +21 -2
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +26 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +121 -75
- package/dist/knowledge/skills/spec-resource-update/references/workflow-record-page-specification.md +237 -0
- package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +100 -71
- package/dist/knowledge/skills/subject-data-export/SKILL.md +176 -0
- package/dist/knowledge/skills/subject-data-export/references/file-content-exclusions.md +15 -0
- package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-api.md +142 -0
- package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-archive-api.md +33 -0
- package/dist/knowledge/skills/views-app-level/SKILL.md +3 -1
- package/dist/knowledge/skills/views-app-level/references/workflow-home.md +373 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +36 -5
- package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +9 -5
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +4 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-chart-dashboard-api.md +371 -0
- package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +40 -0
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +8 -6
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +70 -59
- package/dist/knowledge/skills/website-building-blocks/SKILL.md +1 -1
- package/dist/knowledge/skills/website-building-blocks/references/framework-website-demo-examples.md +3 -3
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +4 -2
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +3 -1
- package/dist/knowledge/skills/website-label-pack/SKILL.md +20 -5
- package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +6 -3
- package/dist/knowledge/skills/website-section-comparison/SKILL.md +2 -2
- package/dist/knowledge/skills/website-section-contact/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-cta/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-faq/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-hero/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-how-it-works/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-integrations/SKILL.md +3 -3
- package/dist/knowledge/skills/website-section-latest-posts/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +142 -98
- package/dist/knowledge/skills/website-section-pricing/examples/pricing-offers.example.md +178 -66
- package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +3 -1
- package/dist/knowledge/skills/website-section-problem/SKILL.md +3 -3
- package/dist/knowledge/skills/website-section-product-showcase/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-roadmap/SKILL.md +4 -4
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-solution-paths/SKILL.md +2 -2
- package/dist/knowledge/skills/website-section-stats/SKILL.md +3 -3
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +3 -2
- package/dist/knowledge/skills/worker-authoring/SKILL.md +4 -2
- package/dist/knowledge/topic-index.json +2422 -723
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/package.json +6 -6
- package/dist/tsconfig.tsbuildinfo +0 -1
|
@@ -4,7 +4,8 @@ This file exposes `idempotencyKey` — the per-operation-variant declaration tha
|
|
|
4
4
|
`Idempotency-Key` request header, so a caller's retry receives the first request's outcome instead of running the
|
|
5
5
|
effect a second time.
|
|
6
6
|
|
|
7
|
-
Read it when an operation
|
|
7
|
+
Read it when a caller may retry an operation after losing its answer — a create above all, where the retry is a second
|
|
8
|
+
row — and whenever an operation does something your database cannot roll back: charging or changing a subscription at a
|
|
8
9
|
payment provider, sending a message, writing to a third-party system.
|
|
9
10
|
|
|
10
11
|
## Why a retry is the danger
|
|
@@ -36,19 +37,23 @@ whose effect must not run twice is not a read — borrow a mutation verb in `res
|
|
|
36
37
|
exactly like a browser does, so it is bound exactly like one. Engine code calling the operation internally, a provider
|
|
37
38
|
webhook, a queued worker and a nested sub-call are exempt: none of them has a client retry to deduplicate.
|
|
38
39
|
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
40
|
+
The tool planes have no headers, so they carry the key as an `idempotencyKey` ARGUMENT, which the framework takes out
|
|
41
|
+
of the arguments and treats exactly as the header. A model calls a write tool again when a call fails, so these are the
|
|
42
|
+
planes where a retry is most likely:
|
|
43
|
+
|
|
44
|
+
- **MCP tools.** The tool of a variant that declares `idempotencyKey` advertises an `idempotencyKey` argument (required
|
|
45
|
+
for `REQUIRED`, optional for `ACCEPTED`) and tells the model to send a new value for each change and the same value
|
|
46
|
+
when it retries one. A `REQUIRED` operation can therefore be `mcp.exposed`. The application refuses to start when such
|
|
47
|
+
a tool's request DTO, or its resource's id field, already has a field named `idempotencyKey`, which would be taken as
|
|
48
|
+
the key: rename the field, or keep the operation off MCP.
|
|
49
|
+
- **The built-in resource write tool** (`resourceWriteTool`) takes the same argument. Declare it in the tool's
|
|
50
|
+
`inputSchema`, `idempotencyKey: z.string().describe(IDEMPOTENCY_KEY_TOOL_ARGUMENT_DESCRIPTION)`, optional for an
|
|
51
|
+
`ACCEPTED` operation, so the model is told to send one. A call to a `REQUIRED` operation without it is refused before
|
|
52
|
+
anything runs, naming the argument.
|
|
53
|
+
- **An agent function tool you author** passes a key as `options: { idempotencyKey }` to
|
|
54
|
+
`dispatchResourceOperationAsTool`. Take it from the model as the same `idempotencyKey` argument: a key the tool mints
|
|
55
|
+
inside one execution deduplicates only the retries the tool makes itself, never the model calling the tool again
|
|
56
|
+
after a failure, which is a new execution and therefore a new request.
|
|
52
57
|
|
|
53
58
|
## What the framework does, and what it leaves to you
|
|
54
59
|
|
|
@@ -67,13 +72,39 @@ The framework does the transport half:
|
|
|
67
72
|
- refuses a key sent to a variant whose runtime mode is not `INLINE`: queued and background execution cannot carry it to
|
|
68
73
|
your implementation, so accepting it would promise a protection nothing delivers.
|
|
69
74
|
|
|
70
|
-
|
|
75
|
+
It also REMEMBERS the outcome. The first request sent with a key is recorded per (caller, resource, key) before it runs,
|
|
76
|
+
and what became of it after it committed; the record is kept for 24 hours (`IDEMPOTENT_REQUEST_OUTCOME_RETENTION_HOURS`)
|
|
77
|
+
and an hourly sweep deletes it after that. A repeat is answered from the record:
|
|
78
|
+
|
|
79
|
+
| the first request | a repeat of the same request is answered |
|
|
80
|
+
|---|---|
|
|
81
|
+
| succeeded | with the first response, replayed: nothing runs again, no hook, no write, no notification |
|
|
82
|
+
| is still running | 409 `idempotency_key_in_progress`: retry the same request later |
|
|
83
|
+
| was refused before anything landed (validation, permission, not found, a rule) | by running it: the key binds nothing yet, so a corrected request runs too |
|
|
84
|
+
| failed in a way that may have landed (an unclassified error, an unknown commit, a crash) | 409 `idempotency_key_outcome_unknown`: read before acting. It never runs again under the key |
|
|
85
|
+
| succeeded, and its response carried a value shown once (an `.isEphemeral()` secret) | 409 `idempotency_key_outcome_not_replayable`, naming the row in `idempotentRequestResourceId` |
|
|
86
|
+
|
|
87
|
+
The same key with a DIFFERENT request — another operation of the resource, another variant, target or payload — is
|
|
88
|
+
refused 422 with `ErrorCustomMessageReference.IDEMPOTENCY_KEY_REUSED` (a 422 strips error context on the wire, so the
|
|
89
|
+
reference is the signal a client can branch on). Two callers sending the same key are two requests. The 409 codes are
|
|
90
|
+
`IdempotentRequestRefusalCode`.
|
|
91
|
+
|
|
92
|
+
What is kept is the response the caller received, through the operation's response DTO: backend-only fields are not in
|
|
93
|
+
it and write-only secrets are masked. A response carrying a one-time secret is never stored, which is why its repeat is
|
|
94
|
+
refused rather than replayed: the secret exists only in the one response that discloses it.
|
|
95
|
+
|
|
96
|
+
A read-through resource (`httpApiBinding`) is the exception: its writes are remembered by the system-of-record admission
|
|
97
|
+
ledger, which replays by reading the row back and never keeps a copy of it.
|
|
98
|
+
|
|
99
|
+
What is left to you is the effect OUTSIDE your database. A local write is covered; a provider call is not, because a
|
|
100
|
+
crash can land between the provider applying it and the framework recording the outcome. Pass the key, or a key derived
|
|
101
|
+
from it, to the provider so the provider deduplicates the call, or keep your own record of the effect. When your
|
|
102
|
+
implementation replaces the core write (`OVERRIDE_ALL`, `REPLACE_CORE_OPERARTIONS`) or runs an effect before it
|
|
103
|
+
(`BEFORE_TRANSACTIONAL_CORE`), an attempt whose outcome is unknown is NOT refused: the repeat runs again and reaches your
|
|
104
|
+
implementation, which answers it from its own record. So such an implementation must own that answer:
|
|
71
105
|
|
|
72
106
|
- remember that a key was used, durably, in the same transaction as the effect's local write;
|
|
73
|
-
- on a repeat of the same request, answer the recorded outcome without running the effect again
|
|
74
|
-
- on the same key with a DIFFERENT request, refuse with 422 using `ErrorCustomMessageReference.IDEMPOTENCY_KEY_REUSED`
|
|
75
|
-
(a 422 strips error context on the wire, so the reference is the signal a client can branch on);
|
|
76
|
-
- while the first request is still running, refuse the repeat with 409 rather than running it concurrently.
|
|
107
|
+
- on a repeat of the same request, answer the recorded outcome without running the effect again.
|
|
77
108
|
|
|
78
109
|
One concurrency trap is worth naming, because it passes every sequential test. If you check "has this key's request
|
|
79
110
|
already started?" against one read of your state and then record the new request against a LATER read, two concurrent
|
|
@@ -82,8 +113,6 @@ effect again. Record the request only against the exact state you checked (a com
|
|
|
82
113
|
fails, repeat the check once from a fresh read — the first request's recorded outcome or in-flight marker is then there
|
|
83
114
|
to answer it.
|
|
84
115
|
|
|
85
|
-
Declaring the variant without doing that half ships a header nothing deduplicates.
|
|
86
|
-
|
|
87
116
|
## Operation Idempotency Key
|
|
88
117
|
|
|
89
118
|
## Import Origins
|
|
@@ -99,9 +128,10 @@ Declaring the variant without doing that half ships a header nothing deduplicate
|
|
|
99
128
|
* Whether this variant takes the `Idempotency-Key` request header, so a caller's retry receives the first request's
|
|
100
129
|
* outcome instead of running the effect again.
|
|
101
130
|
*
|
|
102
|
-
* Declare it on a mutation
|
|
103
|
-
*
|
|
104
|
-
*
|
|
131
|
+
* Declare it on a mutation a caller may retry after losing the answer — a CREATE above all, where a retry is a second
|
|
132
|
+
* row — and on every mutation whose effect happens OUTSIDE your database (a payment provider, an email, a third-party
|
|
133
|
+
* write), where the duplicate cannot be rolled back. `If-Match` protects an update from a stale read; it does nothing
|
|
134
|
+
* for a create sent twice.
|
|
105
135
|
*
|
|
106
136
|
* - `ACCEPTED`: the header is honored when sent, and a request without it runs unkeyed. Right for an effect that
|
|
107
137
|
* converges when repeated (cancelling something twice leaves it cancelled).
|
|
@@ -124,9 +154,18 @@ Declaring the variant without doing that half ships a header nothing deduplicate
|
|
|
124
154
|
* nothing, so the key would protect no retry and `REQUIRED` would only refuse harmless repeats. A custom operation whose
|
|
125
155
|
* effect must not run twice is not a read: borrow a mutation verb in `resourceOperationLike` and declare the key there.
|
|
126
156
|
*
|
|
127
|
-
*
|
|
128
|
-
*
|
|
129
|
-
*
|
|
157
|
+
* It also REMEMBERS the outcome (#747): the first response to a keyed request is kept for a day per (caller, resource,
|
|
158
|
+
* key), and a repeat of the same request is answered from it without running again. A repeat while the first is still
|
|
159
|
+
* running is refused 409 (`idempotency_key_in_progress`); the same key with a different request (another operation,
|
|
160
|
+
* target or payload) is refused 422 (`ErrorCustomMessageReference.IDEMPOTENCY_KEY_REUSED`). A first request refused
|
|
161
|
+
* before anything landed (validation, permission, a rule) leaves the key free, so the corrected retry runs; one whose
|
|
162
|
+
* outcome is unknown (an unclassified failure, a lost commit, a crash) is never run again under the key (409 `idempotency_key_outcome_unknown`:
|
|
163
|
+
* read before acting). A response carrying a one-time secret (`.isEphemeral()`) is never stored, so its repeat is refused
|
|
164
|
+
* 409 (`idempotency_key_outcome_not_replayable`) naming the row instead. `IdempotentRequestRefusalCode` lists the codes.
|
|
165
|
+
*
|
|
166
|
+
* Your implementation still receives the key, because an effect outside your database needs its own bracket: pass the
|
|
167
|
+
* key (or a key derived from it) to the provider, so the provider deduplicates the call itself. A read-through
|
|
168
|
+
* resource's writes are remembered by its system-of-record admission ledger instead, which never stores the row.
|
|
130
169
|
*
|
|
131
170
|
* @example a provider-backed mutation that must not run twice
|
|
132
171
|
* variants: [{
|
|
@@ -16,7 +16,7 @@ together: the resource factory refuses either one alone.
|
|
|
16
16
|
| **about no person, but naming one** — a pipeline stage or a quote with a `createdByUserId`, a job pointing at a homeowner | `RETAIN_ONLY` | `NO_PRINCIPAL` | **`ALLOWED`** (or `FORBIDDEN` to keep it out on purpose): the link puts it on that person's export graph, and an undeclared resource there makes the subject-access export refuse when it is requested | nothing of its own |
|
|
17
17
|
| **about no person, but keeping the name of the party it describes** — a billing record naming the customer account billed, a record of a relationship naming the other organization | `RETAIN_ONLY` | `NO_PRINCIPAL` | as the row above | the copied name: `.dataCategories(PersonalDataCategory.IDENTITY, { personalOnlyWhen: PersonalDataCondition.DESCRIBED_PARTY_IS_A_NATURAL_PERSON, aboutAnotherParty: true })`. It is a person's data only where that party is a sole trader, and it is about that OTHER party, so `RETAIN_ONLY` still holds; the notice states it under that condition. Leave `aboutAnotherParty` off a record's OWN party's name (a customer account's own name): that is the record's subject, and `RETAIN_ONLY` refuses it |
|
|
18
18
|
| **a person with no account** — a CRM contact, a lead, a homeowner on a quote | `RETAIN_AND_IMPERSONALIZE` | `NO_PRINCIPAL` | `ALLOWED` | every personal field: `.dataCategories(...)` and `.impersonalizeWith(...)` |
|
|
19
|
-
| **a person who signs in** — the row IS the user, or names the user it belongs to | `RETAIN_AND_IMPERSONALIZE` | `
|
|
19
|
+
| **a person who signs in** — the row IS the user, or names the user it belongs to | `RETAIN_AND_IMPERSONALIZE` | `LINKED_PRINCIPAL` with `sessionPrincipalField`, the foreign key to `users`, when only erasing that person scrubs this row; `NO_PRINCIPAL` for a row merely about them. `SELF_PRINCIPAL` is the engine's own `users` row and is refused anywhere else | `ALLOWED` | as above; erasing the row also ends that user's sessions |
|
|
20
20
|
| **a business record carrying free text about people** — notes, descriptions, comments | `RETAIN_AND_IMPERSONALIZE` (the text is personal data of its own, so not `RETAIN_ONLY`) | whichever of the rows above fits the record itself | `ALLOWED` when the record names a person, as above | the text field, optional: `.dataCategories(PersonalDataCategory.USER_CONTENT)` and `.impersonalizeWith(RedactionType.REMOVE)` |
|
|
21
21
|
|
|
22
22
|
`REMOVE` clears the field, so it is accepted only on an optional field; a required one takes
|
|
@@ -242,26 +242,28 @@ export enum ResourceSystemAccessMode {
|
|
|
242
242
|
/**
|
|
243
243
|
* Declares that THIS resource is the application's subject-erasure request lane, and how to read it.
|
|
244
244
|
*
|
|
245
|
-
* ##
|
|
245
|
+
* ## Who declares it, and why it is still a declaration
|
|
246
246
|
*
|
|
247
|
-
*
|
|
248
|
-
*
|
|
249
|
-
*
|
|
250
|
-
*
|
|
251
|
-
*
|
|
252
|
-
* that is one application's modelling choice"*.
|
|
247
|
+
* Since #2296 the lane is the ENGINE's: the core resource `dataSubjectRequests`, which every application
|
|
248
|
+
* has, carries this declaration, and the evidence door refuses an application where a second resource
|
|
249
|
+
* declares one. An application does not declare its own. (Before #2296 the lane was an application's to
|
|
250
|
+
* build, which is why this declaration exists at all: Your Application' `accountErasureRequests` was the
|
|
251
|
+
* first declarer and was harvested into the engine.)
|
|
253
252
|
*
|
|
254
|
-
*
|
|
255
|
-
*
|
|
256
|
-
*
|
|
257
|
-
* to
|
|
253
|
+
* It stays a DECLARATION rather than the door reading the engine's fields by name, because the door
|
|
254
|
+
* and the collector read the lane through it and never through the engine's vocabulary: they count the
|
|
255
|
+
* field and value the declaration names (`evidence-requirement:subject-erasure-execution-record` asks
|
|
256
|
+
* them to), so their reading follows the resource and cannot drift from it. Before this existed, three
|
|
257
|
+
* clauses of that demand had a durable row holding every fact they wanted and no way to find it
|
|
258
|
+
* (#1209): not a missing control, a control nobody could point at.
|
|
258
259
|
*
|
|
259
260
|
* ## It binds FIELDS, never values the framework invents
|
|
260
261
|
*
|
|
261
|
-
* Every member below names something the
|
|
262
|
-
* declaration carries — {@link ResourceSubjectErasureLane.raisedBy}`.subjectValue` — is
|
|
263
|
-
*
|
|
264
|
-
*
|
|
262
|
+
* Every member below names something the declaring resource already has. The one value the
|
|
263
|
+
* declaration carries — {@link ResourceSubjectErasureLane.raisedBy}`.subjectValue` — is that
|
|
264
|
+
* resource's OWN enum member (`DataSubjectRequestChannel.SELF` on the engine's lane), quoted back so a
|
|
265
|
+
* reader can tell the two populations apart. The declaration supplies no vocabulary of its own and must
|
|
266
|
+
* never grow one.
|
|
265
267
|
*
|
|
266
268
|
* ## What is deliberately NOT declared
|
|
267
269
|
*
|
|
@@ -332,6 +334,21 @@ export type ResourceSubjectErasureLane = {
|
|
|
332
334
|
},
|
|
333
335
|
/** The scheduled operation that executes due requests. Its `cronExpression` IS the declared schedule. */
|
|
334
336
|
executionOperationIdentifier: string,
|
|
337
|
+
/**
|
|
338
|
+
* How a row says it is an ERASURE request at all, when the declaring resource also records requests for other rights
|
|
339
|
+
* (#2296: the engine's `dataSubjectRequests` carries access and portability requests beside erasure). The same shape
|
|
340
|
+
* as {@link withdrawnMarker}, and for the same reason: the vocabulary is the resource's.
|
|
341
|
+
*
|
|
342
|
+
* A collector counts only the rows carrying it. Without it, an export request — answered at intake, with a
|
|
343
|
+
* `completedAt` and no erasure — would be counted as an erasure executed, which is the false evidence this lane
|
|
344
|
+
* exists to prevent. Omitting it is a positive claim that every row of the resource is an erasure request.
|
|
345
|
+
*/
|
|
346
|
+
erasureMarker?: {
|
|
347
|
+
/** The field carrying it. Must be a persisted field of this resource. */
|
|
348
|
+
fieldName: string,
|
|
349
|
+
/** The value of that field meaning the row is an erasure request. */
|
|
350
|
+
erasureValue: string,
|
|
351
|
+
},
|
|
335
352
|
};
|
|
336
353
|
|
|
337
354
|
export type ResourceSystemAccessPolicy = {
|
|
@@ -537,6 +554,15 @@ export interface ResourceRetentionPolicy {
|
|
|
537
554
|
* reach RETAINED rows only, and the write refuses any field this list does not name. A field named here may not be
|
|
538
555
|
* personal data (no `.dataCategories()`, no `.impersonalizeWith()`), may not be `.excludeFromUpdate()`, and may not
|
|
539
556
|
* be the primary key or a retention marker: the build refuses each of those.
|
|
557
|
+
*
|
|
558
|
+
* ## Closing a retained record (#1841)
|
|
559
|
+
*
|
|
560
|
+
* A resource bound `RetentionStartPoint.CLOSURE_EVENT` may name its closure field here, the one `.excludeFromUpdate()`
|
|
561
|
+
* field allowed (on a closure clock that decorator means server-owned, not immutable). A record still OPEN when its
|
|
562
|
+
* subject is erased can then be closed: its own close operation, finding the row RETAINED, calls
|
|
563
|
+
* `SystemAccessBackendService.closeRetainedRecordAsSystem`, which writes the closure date only where it is still null.
|
|
564
|
+
* The retention-class sweep then deletes the row at closure + period. This is what lets a statutory record declare a
|
|
565
|
+
* period counted from the end of a contract or a matter; without it the build refuses that combination.
|
|
540
566
|
*/
|
|
541
567
|
retainedRowCompletion?: ResourceRetainedRowCompletion;
|
|
542
568
|
}
|
|
@@ -563,6 +589,18 @@ export interface ResourceStatutoryRetention {
|
|
|
563
589
|
* claim nobody can check.
|
|
564
590
|
*/
|
|
565
591
|
rationale: string;
|
|
592
|
+
/**
|
|
593
|
+
* WHY these rows stay in use after their owner goes, for a resource whose teardown edges do not restrict them.
|
|
594
|
+
*
|
|
595
|
+
* The default, and the right answer for almost every statutory record, is restriction: every owning edge authors
|
|
596
|
+
* `IMPERSONALIZE_AND_RETAIN`, and startup refuses anything else. A few records cannot be frozen, because work still
|
|
597
|
+
* arrives for them after the owner has gone: a billing provider's webhooks and reconciliation reach an invoice long
|
|
598
|
+
* after its customer left. Declaring this keeps the edges as they are and states why, in words a reader can dispute.
|
|
599
|
+
* Required non-empty when present. It changes nothing about the period, which still ends the rows. Because such rows
|
|
600
|
+
* are never restricted, their handlers close them through ordinary writes, so a `CLOSURE_EVENT` binding is accepted
|
|
601
|
+
* with it (#1841).
|
|
602
|
+
*/
|
|
603
|
+
staysInUseBecause?: string;
|
|
566
604
|
}
|
|
567
605
|
|
|
568
606
|
/**
|
|
@@ -627,30 +665,15 @@ export type ResourceConfiguration_BuilderParameters<
|
|
|
627
665
|
* If not specified, uses `appConfig.database.defaultAdapter` — which is the normal case and
|
|
628
666
|
* should stay the normal case.
|
|
629
667
|
*
|
|
630
|
-
* **
|
|
631
|
-
*
|
|
632
|
-
*
|
|
633
|
-
*
|
|
634
|
-
*
|
|
635
|
-
*
|
|
668
|
+
* **An application uses exactly ONE transactional store** (#3328, decided 2026-11-06), so a
|
|
669
|
+
* `mongodb` or `postgresql` value that DISAGREES with the application default is refused at
|
|
670
|
+
* registration, with no declaration that admits it. Declaring an adapter that AGREES with the
|
|
671
|
+
* default is always fine and needs nothing. The non-default values a resource may declare are
|
|
672
|
+
* the ones that hold no transaction: `http-api` (read through from another system) and
|
|
673
|
+
* `introspection` (computed from the application itself).
|
|
636
674
|
*/
|
|
637
675
|
persistenceAdapter?: PersistenceAdapterType,
|
|
638
676
|
|
|
639
|
-
/**
|
|
640
|
-
* This resource's declared relationship to cross-adapter atomic write boundaries.
|
|
641
|
-
*
|
|
642
|
-
* Required — and only meaningful — when {@link
|
|
643
|
-
* ResourceConfiguration_BuilderParameters.persistenceAdapter} disagrees with
|
|
644
|
-
* `appConfig.database.defaultAdapter`. Without it, the resources registry refuses the
|
|
645
|
-
* application at startup; with it, the registry admits the resource and LOGS the admitted
|
|
646
|
-
* set, so a mixed configuration is always named and never ambient.
|
|
647
|
-
*
|
|
648
|
-
* Read {@link ResourcePersistenceAdapterIsolation} before declaring one: the member is an
|
|
649
|
-
* assertion about the resource's design that the persistence unit of work will still enforce
|
|
650
|
-
* at every real boundary.
|
|
651
|
-
*/
|
|
652
|
-
persistenceAdapterIsolation?: ResourcePersistenceAdapterIsolationType,
|
|
653
|
-
|
|
654
677
|
/**
|
|
655
678
|
* REQUIRED companion declaration when `persistenceAdapter` is `HTTP_API`; forbidden otherwise.
|
|
656
679
|
*
|
|
@@ -726,9 +749,9 @@ export type ResourceConfiguration_BuilderParameters<
|
|
|
726
749
|
|
|
727
750
|
/**
|
|
728
751
|
* Declares this resource as the application's SUBJECT-ERASURE REQUEST LANE and binds the fields an
|
|
729
|
-
* evidence collector reads. Omitted ⇒ this resource is not that lane,
|
|
730
|
-
*
|
|
731
|
-
*
|
|
752
|
+
* evidence collector reads. Omitted ⇒ this resource is not that lane, the default for every resource
|
|
753
|
+
* but one: since #2296 the engine's `dataSubjectRequests` declares it in every application, and the
|
|
754
|
+
* evidence door refuses an application where a second resource does. See {@link ResourceSubjectErasureLane}.
|
|
732
755
|
*/
|
|
733
756
|
subjectErasureLane?: ResourceSubjectErasureLane,
|
|
734
757
|
coreOperations: TCoreOperationEnum[],
|
|
@@ -842,14 +865,22 @@ export type ResourceConfiguration_BuilderParameters<
|
|
|
842
865
|
* scrub); this is how long a row lives at all. The two compose: a row an erasure retained is still
|
|
843
866
|
* deleted when its class period ends.
|
|
844
867
|
*
|
|
845
|
-
* Optional
|
|
846
|
-
*
|
|
847
|
-
*
|
|
868
|
+
* Optional, with no default class: an unbound row has no clock. That is normal when something else ends the
|
|
869
|
+
* row, and `deriveResourceRowLifetimes` says what does for every resource. A resource that binds a class may not
|
|
870
|
+
* also declare a `.ttl()` field — one row, one retention authority.
|
|
848
871
|
*
|
|
849
872
|
* {@link RetentionStartPoint.SCOPE_DELETED} injects a server-owned `retentionStartedAt` field.
|
|
850
873
|
*/
|
|
851
874
|
retentionBinding?: ResourceRetentionBinding,
|
|
852
875
|
|
|
876
|
+
/**
|
|
877
|
+
* What ends this resource's rows, for the case its configuration cannot show: a dedicated cleanup, the audit
|
|
878
|
+
* archive, the files cleanup, or operator configuration. Everything else is derived, so declare this only when
|
|
879
|
+
* `deriveResourceRowLifetimes` would otherwise answer `UNDECIDED` and a real mechanism exists. It may not sit beside
|
|
880
|
+
* a {@link retentionBinding}: one row, one retention authority.
|
|
881
|
+
*/
|
|
882
|
+
rowLifetime?: ResourceRowLifetimeDeclaration,
|
|
883
|
+
|
|
853
884
|
/**
|
|
854
885
|
* Resource-level DEFAULT provenance for GDPR Art. 20 (portability) scoping; per-field overrides
|
|
855
886
|
* are `.portabilityProvenance()`. Optional — Art. 15 (access) never consults provenance, so an
|
|
@@ -866,6 +897,40 @@ export type ResourceConfiguration_BuilderParameters<
|
|
|
866
897
|
*/
|
|
867
898
|
subjectExportOthersDataFields?: readonly string[],
|
|
868
899
|
|
|
900
|
+
/**
|
|
901
|
+
* The same withholding, for rows reached through ONE edge (#2958 follow-up): keyed by the foreign-key field of a
|
|
902
|
+
* relationship edge to this resource, the fields a subject export withholds and lists as other people's data when it
|
|
903
|
+
* reaches a row THROUGH THAT EDGE, for both rights, on top of {@link subjectExportOthersDataFields}.
|
|
904
|
+
*
|
|
905
|
+
* For a resource two people reach by two edges with different standing. A data-subject request is the SUBJECT's
|
|
906
|
+
* (`userId`, whole) and names the operator who recorded it (`requestedByUserId`): the operator's own act (that they
|
|
907
|
+
* recorded a request, of which kind, when) is personal data concerning them (Art. 15(1)), the subject's identity and
|
|
908
|
+
* the request's content are another person's (Art. 15(4)). A resource-wide declaration cannot say that, since it
|
|
909
|
+
* would withhold the subject's own request from the subject.
|
|
910
|
+
*
|
|
911
|
+
* Not read by the retained-row scrub (`resolveRetainedRowScrubSurface`), unlike the resource-wide list: these fields
|
|
912
|
+
* are the row's OWN subject's data, removed by that subject's erasure, not a third person's.
|
|
913
|
+
*
|
|
914
|
+
* Each key and each listed name must be a top-level field of the main schema; the factory refuses one that is not.
|
|
915
|
+
*/
|
|
916
|
+
subjectExportOthersDataFieldsByForeignKey?: Readonly<Record<string, readonly string[]>>,
|
|
917
|
+
|
|
918
|
+
/**
|
|
919
|
+
* #2958: columns of this resource that hold a USER's id on no edge of that user's export graph, and that their ACCESS
|
|
920
|
+
* export reads (Art. 15 only): who acted on the row (`ACTED`: proposed, granted, verified, ended, triaged, kept as
|
|
921
|
+
* accountability evidence and never severed) or who owns it (`OWNS`: a user-private file). Keyed by the column; each
|
|
922
|
+
* declares its relation and the fields of a row found through it that are about that person (`shownFields`, an
|
|
923
|
+
* allow-list: every other field is withheld and listed as other people's data). A person-naming column a SEVERER
|
|
924
|
+
* reaches is declared beside the severer instead (`SubjectReferenceSeverer.subjectReferenceColumns`).
|
|
925
|
+
*
|
|
926
|
+
* Not an edge, on purpose: `exportSubject` is per resource, so an `invitedByUserId` edge on `organizationMembers` would
|
|
927
|
+
* put every member the person invited, whole, into their export.
|
|
928
|
+
*
|
|
929
|
+
* Each key and each shown name must be a top-level field of the main schema (a variant's included); the factory refuses
|
|
930
|
+
* one that is not. The resource must declare `systemAccessPolicy.exportSubject`.
|
|
931
|
+
*/
|
|
932
|
+
subjectExportPersonColumns?: SubjectExportPersonColumns,
|
|
933
|
+
|
|
869
934
|
/**
|
|
870
935
|
* Declares every row of this resource a CASE: the unit of work an application sells an outcome for (a
|
|
871
936
|
* matter, a file, a claim, a ticket). Model calls made while working on a row are attributed to it, so the
|
|
@@ -955,26 +1020,28 @@ export enum ResourceSystemAccessMode {
|
|
|
955
1020
|
/**
|
|
956
1021
|
* Declares that THIS resource is the application's subject-erasure request lane, and how to read it.
|
|
957
1022
|
*
|
|
958
|
-
* ##
|
|
1023
|
+
* ## Who declares it, and why it is still a declaration
|
|
959
1024
|
*
|
|
960
|
-
*
|
|
961
|
-
*
|
|
962
|
-
*
|
|
963
|
-
*
|
|
964
|
-
*
|
|
965
|
-
* that is one application's modelling choice"*.
|
|
1025
|
+
* Since #2296 the lane is the ENGINE's: the core resource `dataSubjectRequests`, which every application
|
|
1026
|
+
* has, carries this declaration, and the evidence door refuses an application where a second resource
|
|
1027
|
+
* declares one. An application does not declare its own. (Before #2296 the lane was an application's to
|
|
1028
|
+
* build, which is why this declaration exists at all: Your Application' `accountErasureRequests` was the
|
|
1029
|
+
* first declarer and was harvested into the engine.)
|
|
966
1030
|
*
|
|
967
|
-
*
|
|
968
|
-
*
|
|
969
|
-
*
|
|
970
|
-
* to
|
|
1031
|
+
* It stays a DECLARATION rather than the door reading the engine's fields by name, because the door
|
|
1032
|
+
* and the collector read the lane through it and never through the engine's vocabulary: they count the
|
|
1033
|
+
* field and value the declaration names (`evidence-requirement:subject-erasure-execution-record` asks
|
|
1034
|
+
* them to), so their reading follows the resource and cannot drift from it. Before this existed, three
|
|
1035
|
+
* clauses of that demand had a durable row holding every fact they wanted and no way to find it
|
|
1036
|
+
* (#1209): not a missing control, a control nobody could point at.
|
|
971
1037
|
*
|
|
972
1038
|
* ## It binds FIELDS, never values the framework invents
|
|
973
1039
|
*
|
|
974
|
-
* Every member below names something the
|
|
975
|
-
* declaration carries — {@link ResourceSubjectErasureLane.raisedBy}`.subjectValue` — is
|
|
976
|
-
*
|
|
977
|
-
*
|
|
1040
|
+
* Every member below names something the declaring resource already has. The one value the
|
|
1041
|
+
* declaration carries — {@link ResourceSubjectErasureLane.raisedBy}`.subjectValue` — is that
|
|
1042
|
+
* resource's OWN enum member (`DataSubjectRequestChannel.SELF` on the engine's lane), quoted back so a
|
|
1043
|
+
* reader can tell the two populations apart. The declaration supplies no vocabulary of its own and must
|
|
1044
|
+
* never grow one.
|
|
978
1045
|
*
|
|
979
1046
|
* ## What is deliberately NOT declared
|
|
980
1047
|
*
|
|
@@ -1045,6 +1112,21 @@ export type ResourceSubjectErasureLane = {
|
|
|
1045
1112
|
},
|
|
1046
1113
|
/** The scheduled operation that executes due requests. Its `cronExpression` IS the declared schedule. */
|
|
1047
1114
|
executionOperationIdentifier: string,
|
|
1115
|
+
/**
|
|
1116
|
+
* How a row says it is an ERASURE request at all, when the declaring resource also records requests for other rights
|
|
1117
|
+
* (#2296: the engine's `dataSubjectRequests` carries access and portability requests beside erasure). The same shape
|
|
1118
|
+
* as {@link withdrawnMarker}, and for the same reason: the vocabulary is the resource's.
|
|
1119
|
+
*
|
|
1120
|
+
* A collector counts only the rows carrying it. Without it, an export request — answered at intake, with a
|
|
1121
|
+
* `completedAt` and no erasure — would be counted as an erasure executed, which is the false evidence this lane
|
|
1122
|
+
* exists to prevent. Omitting it is a positive claim that every row of the resource is an erasure request.
|
|
1123
|
+
*/
|
|
1124
|
+
erasureMarker?: {
|
|
1125
|
+
/** The field carrying it. Must be a persisted field of this resource. */
|
|
1126
|
+
fieldName: string,
|
|
1127
|
+
/** The value of that field meaning the row is an erasure request. */
|
|
1128
|
+
erasureValue: string,
|
|
1129
|
+
},
|
|
1048
1130
|
};
|
|
1049
1131
|
|
|
1050
1132
|
export type ResourceSystemAccessPolicy = {
|
|
@@ -38,8 +38,13 @@ stayed green.
|
|
|
38
38
|
|
|
39
39
|
Ask the question the backend will ask, without starting it: run `wildo config check-resources` at the
|
|
40
40
|
application root. It builds every resource configuration and the resources registry from the compiled
|
|
41
|
-
backend, offline, and prints the factory's refusal and the resource it names.
|
|
42
|
-
|
|
41
|
+
backend, offline, and prints the factory's refusal and the resource it names. It then runs the startup
|
|
42
|
+
validation checks that read the registry alone, the same ones the backend runs after the registry builds,
|
|
43
|
+
among them the statutory-retention teardown rule: a resource kept on a statutory ground whose parent edge
|
|
44
|
+
does not declare `onParentDelete: { enabled: true, mode: IMMEDIATE, strategy: IMPERSONALIZE_AND_RETAIN }`
|
|
45
|
+
fails with `[LIFECYCLE] The '<parent> → <child>' teardown edge …`. Exit 1 is a refused configuration;
|
|
46
|
+
exit 2 means it could not ask (rebuild, then ask again). Checks that read implementations, providers or
|
|
47
|
+
the application configuration still run only when the backend starts.
|
|
43
48
|
|
|
44
49
|
## The factory's other start-time refusals a worker trips
|
|
45
50
|
|
|
@@ -97,6 +102,27 @@ type OrganizationEscalationPolicies_CoreOperations =
|
|
|
97
102
|
*/
|
|
98
103
|
dataSubjectPolicy: { kind: ResourceDataSubjectKind.NO_PRINCIPAL },
|
|
99
104
|
|
|
105
|
+
/**
|
|
106
|
+
* On a person's Art. 15 export graph: a policy names the person it escalates to (`targetUserId`) and whoever created it
|
|
107
|
+
* (`createdByUserId`), and both foreign keys put it there. Being named as an escalation target, or as a policy's author,
|
|
108
|
+
* is information about that person, so the rows are disclosed, as the module's other member-naming resources are. Until
|
|
109
|
+
* this was declared, the fail-closed export refused every access request of a person this resource can name (the
|
|
110
|
+
* account-erasure-journey lane's download answered 500, #3743).
|
|
111
|
+
*/
|
|
112
|
+
systemAccessPolicy: { exportSubject: ResourceSystemAccessMode.ALLOWED },
|
|
113
|
+
/**
|
|
114
|
+
* Withheld from every copy: the organization's endpoint, not the person's data, and a webhook URL often carries the
|
|
115
|
+
* credential that authorizes posting to it.
|
|
116
|
+
*/
|
|
117
|
+
subjectExportOthersDataFields: ['webhookUrl'],
|
|
118
|
+
/**
|
|
119
|
+
* Each person's copy withholds the OTHER person the row names: the target's copy does not say who configured the
|
|
120
|
+
* policy, and the author's copy does not say whom it escalates to. An actor's identity is that actor's data.
|
|
121
|
+
*
|
|
122
|
+
* spec-cite: GDPR Art. 15(4) (https://gdpr-info.eu/art-15-gdpr/), as `organizationRepresentativeAssignments` cites it
|
|
123
|
+
*/
|
|
124
|
+
subjectExportOthersDataFieldsByForeignKey: { targetUserId: ['createdByUserId'], createdByUserId: ['targetUserId'] },
|
|
125
|
+
|
|
100
126
|
coreOperations: [
|
|
101
127
|
CoreResourceOperation.READ,
|
|
102
128
|
CoreResourceOperation.LIST,
|
package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md
CHANGED
|
@@ -18,23 +18,35 @@ writes the caller never asked for.
|
|
|
18
18
|
|
|
19
19
|
## What it answers, and what it does not
|
|
20
20
|
|
|
21
|
-
It answers **how high**,
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
the caller may act in.
|
|
21
|
+
It answers **how high**, and counts only the roles the caller holds IN the organization the write acts
|
|
22
|
+
inside, organization-wide (a role held on one unit grants nothing across the tenant), plus their
|
|
23
|
+
application roles. An `ORG_ADMIN` of one tenant is not an `ORG_ADMIN` of another.
|
|
25
24
|
|
|
26
25
|
The comparison is hierarchy-aware: a role expands through its `inheritFrom` chain, so an `ORG_ADMIN`
|
|
27
26
|
whose membership row holds only the literal `ORG_ADMIN` can still grant the roles that role confers.
|
|
28
27
|
A role string unknown in the passed scope expands to the empty set — fail-closed by construction.
|
|
29
28
|
|
|
30
|
-
|
|
29
|
+
It also admits your application's own roles that are OFF the caller's chain when everything they confer
|
|
30
|
+
is within a role the caller holds: their `inheritFrom` chain is on the caller's, and every operation
|
|
31
|
+
naming them admits the caller too, at the same row reach. So an owner or administrator can grant a
|
|
32
|
+
supervisor role that inherits `ORG_MANAGER` and is named beside `ORG_ADMIN`, and a manager cannot. A
|
|
33
|
+
custom role named alone on an operation the caller cannot call exceeds the caller and is refused. The
|
|
34
|
+
same holds wherever else a role name confers authority: an approval route (`requiresApproval.eligibleRole`,
|
|
35
|
+
a function tool's `humanApproval.eligibleRole`, an actor's or a flow's question route), a reference
|
|
36
|
+
constraint's `requiredRoles`, a system-of-record action's `roles` and a provider browser operation's
|
|
37
|
+
`allowedRoles`. A custom role named as the ONLY role a decision route admits can be given by the platform
|
|
38
|
+
super-administrator alone, since no administrator answers that route. Where the application keeps agent
|
|
39
|
+
correction content, a tenant may name any role as its reader, so a custom organization role is grantable
|
|
40
|
+
only by a role at or above `ORG_ADMIN` there. The engine's own roles are never admitted this way:
|
|
41
|
+
`ORG_OWNER` stays above `ORG_ADMIN` whatever the operations say.
|
|
42
|
+
|
|
43
|
+
## What it deliberately skips, and what it does not
|
|
31
44
|
|
|
32
45
|
- **Internally initiated writes.** A seed, a provisioning step or a system-authored write carries no
|
|
33
46
|
human ceiling and assigns whatever it is told.
|
|
34
|
-
- **
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
carries are fixed when it is minted.
|
|
47
|
+
- **Nothing else, for machine credentials.** They are checked at mint, on an update that names roles,
|
|
48
|
+
and on every reissue or expiry extension, where the credential's STORED roles face the caller's
|
|
49
|
+
ceiling: handing out a working secret, or extending one, administers that authority.
|
|
38
50
|
|
|
39
51
|
## Role Ceiling
|
|
40
52
|
|
|
@@ -69,7 +81,10 @@ A role string unknown in the passed scope expands to the empty set — fail-clos
|
|
|
69
81
|
*
|
|
70
82
|
* SEMANTICS. Every requested role must lie within the caller's EFFECTIVE authority — the union of the
|
|
71
83
|
* `inheritFrom` hierarchies of the roles the caller actually holds, each expanded within the scope of
|
|
72
|
-
* the membership that granted it
|
|
84
|
+
* the membership that granted it, plus every application-declared role whose whole authority is within a held
|
|
85
|
+
* role's (a custom role off the core chain, such as a supervisor inheriting `ORG_MANAGER`, which an `ORG_OWNER`
|
|
86
|
+
* may grant when every operation, approval or decision route and action naming the supervisor also admits the owner,
|
|
87
|
+
* measured against the live registries by `AuthorizationsBackendService.getRolesWithinAuthority`). Hierarchy-awareness is not a convenience: with the default table
|
|
73
88
|
* (`ORG_OWNER → ORG_ADMIN → ORG_MANAGER → ORG_MEMBER → ORG_GUEST`) an `ORG_ADMIN`'s membership row
|
|
74
89
|
* holds the literal string `ORG_ADMIN` and nothing else, so a raw set-membership test would reject
|
|
75
90
|
* that admin granting the DEFAULT `ORG_MEMBER` role and break the entire invite flow — while still
|
|
@@ -94,6 +109,13 @@ A role string unknown in the passed scope expands to the empty set — fail-clos
|
|
|
94
109
|
* `createAsSystem`) is the framework itself, not a user principal (it synthesises a super-admin
|
|
95
110
|
* system EC), and carries no human ceiling — it is trusted to assign any role.
|
|
96
111
|
*
|
|
112
|
+
* ONE RULE, SHARED WITH THE FORMS (#3248). The ceiling itself is `resolveRoleGrantCeiling` in
|
|
113
|
+
* `@wildo-ai/saas-models`, which this gate calls with the live role tables and a role-offering form calls with the same
|
|
114
|
+
* tables and the backend's own role entries, so the form and this gate make the same ceiling decision (a form that knew
|
|
115
|
+
* less offered `ORG_OWNER` to an `ORG_ADMIN`, and picking it answered 403). The form decides from the role entries it
|
|
116
|
+
* loaded with the session, so a role changed since can still be refused here, and the write's other checks (a role the
|
|
117
|
+
* organization's type does not offer) still apply: the gate stays the control.
|
|
118
|
+
*
|
|
97
119
|
* SCOPE OF THE COMPARISON. Only the roles the caller holds IN the organization the write acts inside
|
|
98
120
|
* (`executionContext.organizationId`) are counted, plus their APPLICATION roles. Until 2026-09-25 the
|
|
99
121
|
* roles were unioned across every membership, on the stated premise that the authorization layer had
|
|
@@ -106,6 +128,8 @@ A role string unknown in the passed scope expands to the empty set — fail-clos
|
|
|
106
128
|
* `roles` field is caller-settable, passing the roles AS AUTHORED BY THE CALLER — not the
|
|
107
129
|
* post-resolution set. Framework-injected defaults (e.g. an organization type's `defaultMemberRole`)
|
|
108
130
|
* are policy-derived, not a caller request, and must not be measured against the caller's ceiling.
|
|
131
|
+
* Declare the field `.isRoleGrant()` in the same change: a form then offers only the roles the person filling it may
|
|
132
|
+
* grant (plus any the record already holds), decided by this same rule, instead of offering roles this gate refuses.
|
|
109
133
|
*
|
|
110
134
|
* THE REFUSAL IS RECORDED — as a `RESOURCE_OPERATION_DENIED` audit event with
|
|
111
135
|
* `denialReason: role_ceiling_exceeded`, carrying the roles that were refused. A privilege-escalation
|
|
@@ -112,16 +112,17 @@ export enum ResourceOperationFrontendSurface {
|
|
|
112
112
|
}
|
|
113
113
|
|
|
114
114
|
/**
|
|
115
|
-
* Display mode for resource operation action bars —
|
|
116
|
-
*
|
|
115
|
+
* Display mode for resource operation action bars — which surface the actions are drawn on, and so how many stay in
|
|
116
|
+
* view. Every direct action shows its words by default (`DEFAULT_ACTION_LABEL_DISPLAY_MODE`, #3066); the rest wait in
|
|
117
|
+
* the `…` menu, which shows words too.
|
|
117
118
|
*
|
|
118
119
|
* Note: "summary" here is about *UI density*, not API data shape (see DataMode.SUMMARY)
|
|
119
120
|
* or FK rendering (see ForeignKeyDisplayMode.SUMMARY).
|
|
120
121
|
*/
|
|
121
122
|
export enum ResourceOperationDisplayMode {
|
|
122
|
-
/** In a list/table row —
|
|
123
|
+
/** In a list/table row — one direct action beside the record's name (none on a phone), the rest in `…`. The row itself opens the record, so it offers no "View Details". */
|
|
123
124
|
SUMMARY = 'summary',
|
|
124
|
-
/** In a full read/detail view —
|
|
125
|
+
/** In a full read/detail view (the record header) — three direct actions (one on a phone), the rest in `…`. */
|
|
125
126
|
DETAIL = 'detail',
|
|
126
127
|
}
|
|
127
128
|
```
|