@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
|
@@ -607,7 +607,13 @@ export const RepresentativeAssignmentSchema = z.object({
|
|
|
607
607
|
.excludeFromUpdate()
|
|
608
608
|
.isAuditEvidence(),
|
|
609
609
|
|
|
610
|
-
|
|
610
|
+
/**
|
|
611
|
+
* The representing organization's administrator who assigned the person (#3010: a decider, sealed by ASSIGN as an
|
|
612
|
+
* authorization the granting organization relies on). Their own access export carries the act (the resource's
|
|
613
|
+
* `assignedByUserId` person column); the representative's copy withholds it, with `assignedByName`, as another
|
|
614
|
+
* person's data (#3562).
|
|
615
|
+
*/
|
|
616
|
+
assignedByUserId: z.string().min(1).optional().excludeFromCreate().excludeFromUpdate().isAuditEvidence().isDecider(),
|
|
611
617
|
/**
|
|
612
618
|
* Who assigned, NAMED (#1852): an administrator of the representing organization, which reads this row. Resolved at read
|
|
613
619
|
* time (`forwardedUserName`), never stored. `endedByUserId` below has no name on purpose: an assignment ends with its
|
|
@@ -637,15 +643,19 @@ export const RepresentativeAssignmentSchema = z.object({
|
|
|
637
643
|
*
|
|
638
644
|
* BACKEND-ONLY, and that is the whole design: the representing organization reads this row, and is never told who in
|
|
639
645
|
* the granting organization decided (the decision's resolved row, in the GRANTING organization's trail, names them).
|
|
640
|
-
* So it is never in a response, a listing,
|
|
646
|
+
* So it is never in a response, a listing, another person's subject-export bundle or an email, and it is deliberately NOT
|
|
641
647
|
* `.isAuditEvidence()`: that would put its value on the settle's `RESOURCE_OPERATION_PERFORMED` row, which sits in the
|
|
642
648
|
* representing organization's trail.
|
|
643
649
|
*
|
|
644
650
|
* It exists for one reader: the ending repair (`repairUnrecordedRepresentativeApprovalEndings`), which records and tells
|
|
645
651
|
* an answer whose commit landed with its reply lost, so its ending row names the person who answered rather than nobody.
|
|
646
652
|
* Kept as evidence on erasure, like the other actor ids here (the resource is RETAIN_ONLY).
|
|
653
|
+
*
|
|
654
|
+
* `disclosedToSubject` (#2958): the decider's OWN access export carries the decision they took, through the resource's
|
|
655
|
+
* `approvalDecidedByUserId` person column. The representative, who reads this row through their `userId` edge, never
|
|
656
|
+
* does: the resource withholds the field from every edge as another person's data (`subjectExportOthersDataFields`).
|
|
647
657
|
*/
|
|
648
|
-
approvalDecidedByUserId: z.string().min(1).optional().isBackendOnly().excludeFromCreate().excludeFromUpdate().isDecider(),
|
|
658
|
+
approvalDecidedByUserId: z.string().min(1).optional().isBackendOnly({ disclosedToSubject: true }).excludeFromCreate().excludeFromUpdate().isDecider(),
|
|
649
659
|
/** Why a DENIED assignment admitted nobody — a fact the representing side may know, never who in the granting organization decided. */
|
|
650
660
|
approvalDenialReason: z.enum(RepresentativeApprovalDenialReason)
|
|
651
661
|
.systemEnum('RepresentativeApprovalDenialReason')
|
|
@@ -678,7 +688,19 @@ export const RepresentativeAssignmentSchema = z.object({
|
|
|
678
688
|
approvalDecisionWarningFiredAt: z.date().nullish().isBackendOnly().excludeFromCreate().excludeFromUpdate(),
|
|
679
689
|
approvalDecisionMissedFiredAt: z.date().nullish().isBackendOnly().excludeFromCreate().excludeFromUpdate(),
|
|
680
690
|
approvalNextDueAt: z.date().nullish().isDBIndexed().isBackendOnly().excludeFromCreate().excludeFromUpdate(),
|
|
691
|
+
/**
|
|
692
|
+
* #2923: the step-up the granting organization's administrator must carry to answer the approval, from the granting
|
|
693
|
+
* type's `representativeApprovalStepUp` when the assignment was made; absent when it requires none. Stored like the
|
|
694
|
+
* clocks, so a declaration changed or removed while the approval waits never changes what answering it requires.
|
|
695
|
+
*/
|
|
696
|
+
approvalStepUpRequirement: HumanDecision_StepUpRequirementSchema.optional().isBackendOnly().excludeFromCreate().excludeFromUpdate(),
|
|
697
|
+
/** #2923: the channels that may answer the approval, from `representativeApprovalAnswerChannels` at assign, stored the same way. */
|
|
698
|
+
approvalAnswerChannels: HumanDecision_AnswerChannelsSchema.optional().isBackendOnly().excludeFromCreate().excludeFromUpdate(),
|
|
681
699
|
|
|
700
|
+
/**
|
|
701
|
+
* Who ended the assignment. Their own access export carries the act (the `endedByUserId` person column); the
|
|
702
|
+
* representative's copy withholds it as another person's data (#3562).
|
|
703
|
+
*/
|
|
682
704
|
endedByUserId: z.string().min(1).optional().excludeFromCreate().excludeFromUpdate().isAuditEvidence().isDecider(),
|
|
683
705
|
/** When the assignment ended — the retention clock's start point. */
|
|
684
706
|
endedAt: z.date().optional().isDBIndexed().excludeFromCreate().excludeFromUpdate().isAuditEvidence(),
|
|
@@ -1136,9 +1158,13 @@ export const RelationshipInvitationSchema = z.object({
|
|
|
1136
1158
|
* and the representing organization, whose tenant the row lives in, must not learn of it. Both responses and the
|
|
1137
1159
|
* representing organization's audit trail would show it, and so would an ordering: a caller's sort on a backend-only
|
|
1138
1160
|
* field is dropped (`admitDisclosableSortKeys`).
|
|
1161
|
+
*
|
|
1162
|
+
* `disclosedToSubject` (#2958): the decision is the invitee's own, so THEIR access export carries it, through the
|
|
1163
|
+
* resource's `declinedByUserId` person column. No other path reads these two fields: the inviter's and the revoker's
|
|
1164
|
+
* columns are allow-lists that name neither, and the resource is on no person's export graph.
|
|
1139
1165
|
*/
|
|
1140
|
-
declinedAt: z.date().optional().isBackendOnly().excludeFromCreate().excludeFromUpdate(),
|
|
1141
|
-
declinedByUserId: z.string().min(1).optional().isBackendOnly().excludeFromCreate().excludeFromUpdate().isDecider(),
|
|
1166
|
+
declinedAt: z.date().optional().isBackendOnly({ disclosedToSubject: true }).excludeFromCreate().excludeFromUpdate(),
|
|
1167
|
+
declinedByUserId: z.string().min(1).optional().isBackendOnly({ disclosedToSubject: true }).excludeFromCreate().excludeFromUpdate().isDecider(),
|
|
1142
1168
|
|
|
1143
1169
|
createdAt: z.date().optional(),
|
|
1144
1170
|
updatedAt: z.date().optional(),
|
|
@@ -135,7 +135,7 @@ export const SessionSatisfiedFactorSchema = z.strictObject({
|
|
|
135
135
|
/** The organization the factor counts for — a granting organization, never "everyone". */
|
|
136
136
|
organizationId: z.string().min(1),
|
|
137
137
|
factor: z.enum(AuthMethod),
|
|
138
|
-
satisfiedAt: z.
|
|
138
|
+
satisfiedAt: z.date(),
|
|
139
139
|
source: z.enum(FactorSatisfactionSource),
|
|
140
140
|
/** For {@link FactorSatisfactionSource.REPRESENTING_IDP_TRUSTED}: the representing organization whose identity provider reported it. */
|
|
141
141
|
identityProviderOrganizationId: z.string().min(1).optional(),
|
|
@@ -152,7 +152,7 @@ export const SessionFederatedAmrEvidenceSchema = z.strictObject({
|
|
|
152
152
|
identityProviderOrganizationId: z.string().min(1),
|
|
153
153
|
/** The RFC 8176 values the provider's verified ID token carried, as it carried them. */
|
|
154
154
|
amr: z.array(z.string().min(1).max(64)).max(32),
|
|
155
|
-
authenticatedAt: z.
|
|
155
|
+
authenticatedAt: z.date(),
|
|
156
156
|
});
|
|
157
157
|
export type SessionFederatedAmrEvidence = z.infer<typeof SessionFederatedAmrEvidenceSchema>;
|
|
158
158
|
|
|
@@ -103,6 +103,20 @@ export const GrantingOrganizationTypeOptionsSchema = z.object({
|
|
|
103
103
|
securityCriticalCapabilityMaxDays: z.number().int().min(1).max(SECURITY_CRITICAL_CAPABILITY_DEFAULT_MAX_DAYS).optional(),
|
|
104
104
|
/** When a pending approval of a representative lapses, and who is reminded before it does. Absent: the engine's human-decision defaults. */
|
|
105
105
|
representativeApprovalDeadlines: ReviewDeadlinesDeclarationSchema.optional(),
|
|
106
|
+
/**
|
|
107
|
+
* Whether this type's administrators answer an approval of a representative only with a fresh step-up bound to it
|
|
108
|
+
* (#2923): `{ requiresStepUpAuthentication: true }`, and optionally `stepUp: { maximumAgeSeconds, minimumAssurance }`
|
|
109
|
+
* (`reproven` < `possession` < `phishing_resistant`). The administrator re-proves a factor and answers from the decision
|
|
110
|
+
* inbox; a chat answer carries no proof and is refused. The factor and when it was proven are recorded on the decision
|
|
111
|
+
* and its approval seal. Absent: no step-up. Startup refuses a `stepUp` without the flag.
|
|
112
|
+
*/
|
|
113
|
+
representativeApprovalStepUp: HumanDecision_StepUpDeclarationSchema.optional(),
|
|
114
|
+
/**
|
|
115
|
+
* The channels that may answer each approval of a representative (#2923): `web_session`, `chat`, `api_client`.
|
|
116
|
+
* Stored on the assignment when it is made. Absent: every channel the other requirements allow; `chat` is refused beside a
|
|
117
|
+
* `representativeApprovalStepUp`, which a chat answer cannot carry.
|
|
118
|
+
*/
|
|
119
|
+
representativeApprovalAnswerChannels: HumanDecision_AnswerChannelsSchema.optional(),
|
|
106
120
|
});
|
|
107
121
|
export type GrantingOrganizationTypeOptions = z.infer<typeof GrantingOrganizationTypeOptionsSchema>;
|
|
108
122
|
|
|
@@ -516,6 +530,26 @@ export const OrganizationTypeDefinitionSchema = z.object({
|
|
|
516
530
|
* statement is how a declaration comes to disagree with itself.
|
|
517
531
|
*/
|
|
518
532
|
ownsApplication: z.literal(true).optional(),
|
|
533
|
+
|
|
534
|
+
/**
|
|
535
|
+
* The keys this organization type was declared under before, and why it was renamed (#3044).
|
|
536
|
+
*
|
|
537
|
+
* An organization's `type` is fixed when it is created, so renaming the key alone would leave every existing
|
|
538
|
+
* organization (the owner organization the platform seeded for the first administrator among them) typed with a type
|
|
539
|
+
* the application no longer declares, and its members unable to sign in. With the former key declared here, the
|
|
540
|
+
* backend re-types every organization stored under it at its next start, before anything reads one, and records each as
|
|
541
|
+
* `organization_type_assigned` (basis `declared_rename`) at CRITICAL with the justification. Organizations already
|
|
542
|
+
* re-typed match nothing, so the entry may stay for every environment that has not started since.
|
|
543
|
+
*
|
|
544
|
+
* ```ts
|
|
545
|
+
* group: { ownsApplication: true, userTypes: ['employee'], renamedFrom: [{ key: 'workspace', justification: '…' }] },
|
|
546
|
+
* ```
|
|
547
|
+
*
|
|
548
|
+
* Rename every reference with it (`userTypes.*.requiresOrgMembership.orgTypes`, the relationship kinds' organization
|
|
549
|
+
* types). The type's members' user types are renamed by the user type's own `renamedFrom`. See
|
|
550
|
+
* `declared-type-renames.shared.schemas.ts`.
|
|
551
|
+
*/
|
|
552
|
+
renamedFrom: DeclaredTypeRenamesSchema.optional(),
|
|
519
553
|
});
|
|
520
554
|
export type OrganizationTypeDefinition = z.infer<typeof OrganizationTypeDefinitionSchema>;
|
|
521
555
|
```
|
|
@@ -143,6 +143,7 @@ export const RELATIONSHIP_COMMON_RECORDS_FORBIDDEN_RESOURCES: readonly string[]
|
|
|
143
143
|
CoreResourceType.ORGANIZATION_SSO_CONNECTIONS,
|
|
144
144
|
CoreResourceType.ORGANIZATION_SSO_CONFIG,
|
|
145
145
|
CoreResourceType.ORGANIZATION_EMAIL_DOMAINS,
|
|
146
|
+
CoreResourceType.ORGANIZATION_CUSTOM_DOMAINS,
|
|
146
147
|
CoreResourceType.ORGANIZATION_SIEM_EXPORT_CONFIG,
|
|
147
148
|
CoreResourceType.PLATFORM_ACCESS_GRANTS,
|
|
148
149
|
CoreResourceType.ORGANIZATION_RELATIONSHIPS,
|
|
@@ -61,8 +61,12 @@ export const RepresentativeActivityRowSchema = z.object({
|
|
|
61
61
|
outcome: z.enum(AuditEventOutcome).systemEnum('AuditEventOutcome').describe('Whether the act succeeded, by the same rule the SIEM export states it with.'),
|
|
62
62
|
createdAt: z.string().describe('When the row was written, as an ISO 8601 date-time.'),
|
|
63
63
|
grantingOrganizationId: z.string().describe('The organization the act happened in, whose trail holds the row.'),
|
|
64
|
+
grantingOrganizationName: z.string().optional()
|
|
65
|
+
.describe('That organization\'s name, as this organization\'s record of the engagement holds it. Absent where that record holds none; show the id then.'),
|
|
64
66
|
actingViaRelationshipId: z.string().describe('The relationship the act went through.'),
|
|
65
67
|
userId: z.string().optional().describe('The person who acted, when a person did.'),
|
|
68
|
+
userName: z.string().optional()
|
|
69
|
+
.describe('That person\'s name, from their profile, when they are a member of this organization. Absent otherwise (a granting organization\'s person, an erased person, a person with no name); show the id then.'),
|
|
66
70
|
actorKind: z.enum(AuditActorKind).systemEnum('AuditActorKind').optional(),
|
|
67
71
|
agentRef: z.string().optional().describe('The agent that acted, when one did.'),
|
|
68
72
|
resourceType: z.string().optional().describe('The resource the act reached, when the event names one.'),
|
|
@@ -62,6 +62,37 @@ export const ResourceOperationApprovalRequirementSchema = z.object({
|
|
|
62
62
|
assignee: z.string().min(1).optional(),
|
|
63
63
|
escalateTo: z.string().min(1).optional(),
|
|
64
64
|
deadlines: ReviewDeadlinesDeclarationSchema.optional(),
|
|
65
|
+
/**
|
|
66
|
+
* The approver must step up FOR THIS DECISION when they answer it (#2923): re-authenticate (password, an enrolled
|
|
67
|
+
* second factor or a passkey with user verification) with a proof bound to the request and to the presentation they
|
|
68
|
+
* were shown, minted by `POST /auth/reauth` naming both, single-use and short-lived, and carried in `X-Reauth-Token` on
|
|
69
|
+
* the answer. A proof for another decision, a changed presentation, a used or an expired one is refused, and a chat
|
|
70
|
+
* card cannot carry one, so a chat answer is refused too. The name is the operation flag's, reused: it asks the same
|
|
71
|
+
* of the approver that the flag asks of a person running the operation.
|
|
72
|
+
*/
|
|
73
|
+
requiresStepUpAuthentication: z.boolean().optional(),
|
|
74
|
+
/**
|
|
75
|
+
* What the step-up must ALSO be, when `requiresStepUpAuthentication` is `true` (#2923); startup refuses it otherwise.
|
|
76
|
+
*
|
|
77
|
+
* - `maximumAgeSeconds` — the factor was proven at most this many seconds before the answer (at most 300, the
|
|
78
|
+
* proof's own lifetime): "re-authenticate just before you approve", not "at some point in the last five minutes".
|
|
79
|
+
* - `minimumAssurance` — the weakest factor that may answer, weakest first: `reproven` (any step-up factor, a
|
|
80
|
+
* password included), `possession` (an enrolled TOTP or a passkey: a physical authenticator, never a password
|
|
81
|
+
* alone), `phishing_resistant` (a passkey only), as NIST SP 800-63B-4 classifies the authenticators. The approvers'
|
|
82
|
+
* user types must allow that factor as a step-up method (`stepUpAuth.methods`), or nobody can answer.
|
|
83
|
+
*
|
|
84
|
+
* A proof that is too old or too weak is refused like any unusable proof (`decision_step_up_required`); the person
|
|
85
|
+
* steps up again with one that meets it. The factor and the instant it was proven are recorded on the decision and on
|
|
86
|
+
* its approval seal (`decider.stepUpMethod`, `decider.stepUpAt`), so a verifier sees which factor answered and when.
|
|
87
|
+
*/
|
|
88
|
+
stepUp: HumanDecision_StepUpRequirementSchema.optional(),
|
|
89
|
+
/**
|
|
90
|
+
* The channels that may answer the approval (#2923): `web_session` (the application), `chat` (a chat card),
|
|
91
|
+
* `api_client` (a client the approver delegated to; never admitted for an approval, which is decided in person).
|
|
92
|
+
* Absent: every channel the other requirements allow. `chat` is refused beside a step-up, which a chat answer cannot
|
|
93
|
+
* carry; a chat card for an approval it may not answer links to the approval in the application.
|
|
94
|
+
*/
|
|
95
|
+
answerChannels: HumanDecision_AnswerChannelsSchema.optional(),
|
|
65
96
|
});
|
|
66
97
|
export type ResourceOperationApprovalRequirement = z.infer<typeof ResourceOperationApprovalRequirementSchema>;
|
|
67
98
|
```
|
|
@@ -142,17 +142,19 @@ erasure calls. An entry that lists nothing is used for nothing.
|
|
|
142
142
|
**A content-safety classifier in the `companion` scope screens what your
|
|
143
143
|
coding agents read.** While the companion builds the application, a coding
|
|
144
144
|
agent's brief can carry text written outside the repository: market and
|
|
145
|
-
regulatory material a research step gathered from the web. Scope
|
|
146
|
-
|
|
147
|
-
|
|
145
|
+
regulatory material a research step gathered from the web. Scope a classifier
|
|
146
|
+
that SCREENS (`azure-content-safety`; `openai-moderation` moderates output
|
|
147
|
+
only and cannot serve here) under `providers.scopes.companion` with
|
|
148
148
|
`engineCapabilities: [EngineCapability.AI_CONTENT_SAFETY]`, enable
|
|
149
149
|
`AI_CONTENT_SAFETY` in `engineCapabilities`, and set its key with
|
|
150
150
|
`wildo secrets set`. The companion then screens each such element before
|
|
151
151
|
it enters a brief, and withholds from that brief one the classifier flags.
|
|
152
|
-
|
|
153
|
-
|
|
154
|
-
|
|
155
|
-
|
|
152
|
+
`wildo context elements` screens the same elements before it answers, so a
|
|
153
|
+
flagged one is withheld there too, and a research step's evidence is screened
|
|
154
|
+
before the playbook steps beside it read it. The element itself stays in your
|
|
155
|
+
specifications, with its `researchedBy` provenance. Without a classifier the
|
|
156
|
+
element still reaches the brief and the door, marked as unscreened, and the
|
|
157
|
+
build continues.
|
|
156
158
|
|
|
157
159
|
A CATALOGUE-tier provider (the common case for a packaged integration,
|
|
158
160
|
and the tier of most registry modules) claims no engine capability at
|
|
@@ -180,7 +182,11 @@ that can run a coding agent must declare `complianceProfile`.
|
|
|
180
182
|
the vendor offers and the regions it processes in — possibilities, not the
|
|
181
183
|
operator's choice. Its schema refuses a `VENDOR_HOSTED` profile with no
|
|
182
184
|
region, but nothing parses a package's profile at startup, so validate it
|
|
183
|
-
in the package's own tests.
|
|
185
|
+
in the package's own tests. Say how each region is REACHED
|
|
186
|
+
(`processingRegionReach`): by its own endpoint, which the application's
|
|
187
|
+
choice then selects for every arm, or by where the operator's account
|
|
188
|
+
lives. Composition refuses an endpoint region that leaves an arm on its
|
|
189
|
+
default host — see `references/framework-provider-processing-region-api.md`. What a compliance document says about the
|
|
184
190
|
provider comes from the operator's `providerComplianceChoices`: a
|
|
185
191
|
configured provider with no choice declared is reported as not
|
|
186
192
|
established — see `compliance-document-authoring`.
|
|
@@ -275,6 +281,49 @@ machine, in any form, stops the backend at startup and refuses every request,
|
|
|
275
281
|
so a stand-in's address can never carry a real key off to a local process.
|
|
276
282
|
Set the vendor's own host in every other environment.
|
|
277
283
|
|
|
284
|
+
An arm names such a slot with `baseUrlHostEnvVarName`, in place of its fixed
|
|
285
|
+
`baseUrl`. The REST, document-extraction, content-safety, LLM, image and
|
|
286
|
+
embeddings arms all take it, and each must name exactly one endpoint source
|
|
287
|
+
(the REST arm has a third, `baseUrlEnvVarName`, for a whole URL), or the
|
|
288
|
+
engine refuses the arm. On the LLM, image and embeddings arms the engine also
|
|
289
|
+
hands the result to your `sdkFactory`: it is called as
|
|
290
|
+
`sdkFactory(apiKey, { baseUrl })`, with `baseUrl` already resolved
|
|
291
|
+
(`https://<host>`, or the local double's address). Pass it to your SDK client
|
|
292
|
+
(an Azure OpenAI client's `baseURL`, say); never read the host from the
|
|
293
|
+
environment yourself, because a module reads only the secrets the engine gives
|
|
294
|
+
it. A vendor with one fixed host keeps its `baseUrl` and may ignore the second
|
|
295
|
+
argument.
|
|
296
|
+
|
|
297
|
+
An LLM, embeddings or image arm whose vendor authenticates with a SERVICE ACCOUNT
|
|
298
|
+
rather than an API key (Google Vertex AI) declares two more fields:
|
|
299
|
+
|
|
300
|
+
- `serviceAccountToken: { keyFormat, tokenUrl, tokenHosts, scope, algorithm }`
|
|
301
|
+
— `apiKey.secretRef` then holds the account's key file
|
|
302
|
+
(`ProviderServiceAccountKeyFormat.GOOGLE_SERVICE_ACCOUNT_JSON`), the engine
|
|
303
|
+
exchanges it at `tokenUrl` (a JWT-bearer grant signed with the key, sent to no
|
|
304
|
+
host outside `tokenHosts`, never to a `token_uri` the key file names), caches
|
|
305
|
+
the token until a minute before it expires, and calls your `sdkFactory` with
|
|
306
|
+
the TOKEN as its first argument. Send it as `Authorization: Bearer <token>`;
|
|
307
|
+
your module never sees the key.
|
|
308
|
+
- `deploymentParameterEnvVarNames: { project: 'X_PROJECT', location: 'X_LOCATION' }`
|
|
309
|
+
— values the request path names, each read by the engine from a slot your
|
|
310
|
+
secrets contract declares, admitted only as an identifier (letters, digits,
|
|
311
|
+
`.`, `_`, `-`), and handed to `sdkFactory` as `context.deploymentParameters`.
|
|
312
|
+
|
|
313
|
+
An LLM or embeddings arm whose vendor authenticates by SIGNING each request
|
|
314
|
+
with IAM credentials (Amazon Bedrock with AWS SigV4) declares `requestSigning`
|
|
315
|
+
INSTEAD of `apiKey`, exactly one of the two:
|
|
316
|
+
|
|
317
|
+
- `requestSigning: { scheme: ProviderRestSigningScheme.AWS_SIGV4, keyIdSecretRef, secretKeySecretRef, sessionTokenSecretRef? }`
|
|
318
|
+
— each a slot your secrets contract declares (the session token only for
|
|
319
|
+
temporary credentials, `required: false`). The engine reads them and calls
|
|
320
|
+
your `sdkFactory` with an empty first argument and the credentials in
|
|
321
|
+
`context.requestSigningCredentials` (`keyId`, `secretKey`, `sessionToken?`,
|
|
322
|
+
`region?`). Pass every value to your SDK client explicitly, so it reads none
|
|
323
|
+
of the process's `AWS_*` variables, and sign for the Region of the host you
|
|
324
|
+
call. A service account cannot sit beside it, and a module declaring both,
|
|
325
|
+
neither, or an undeclared slot is refused at startup.
|
|
326
|
+
|
|
278
327
|
This covers the API calls only. When the same slot also fills an OAuth2
|
|
279
328
|
endpoint host (Workday's `WORKDAY_API_HOST` names its token endpoint too),
|
|
280
329
|
the connect flow refuses a loopback host in every environment, because that
|
|
@@ -339,6 +388,40 @@ refuses it when the range is missing or excludes the installed base.
|
|
|
339
388
|
Read `references/framework-provider-augmentation-api.md` for the full
|
|
340
389
|
contract and every refusal.
|
|
341
390
|
|
|
391
|
+
### A GraphQL vendor: the operation sends a document the provider owns
|
|
392
|
+
|
|
393
|
+
GitHub v4, Linear, Shopify Admin and monday.com expose ONE endpoint and tell operations apart by a query document.
|
|
394
|
+
Never make the document an input (that hands the caller the vendor's whole schema). Declare `graphql: { document,
|
|
395
|
+
operationName }` on the operation: `method: POST`, `pathTemplate` the GraphQL endpoint (`/graphql`), no
|
|
396
|
+
`requestBody`, and no parameter fed by the input (a `constantValue` header such as a pinned API version is fine). The
|
|
397
|
+
input IS the variables, so `inputSchema` declares exactly the variables the document declares, and `inputOptions` work
|
|
398
|
+
on them. The document holds exactly one operation of that name: a `query` classified READ or a `mutation` classified
|
|
399
|
+
WRITE (a `subscription` is refused). `resultPath` and `outputSchema` read the answer's `data`. Add `errorCodePath`
|
|
400
|
+
(inside each error, such as `extensions.code`) only when the vendor documents a code there. When the vendor documents
|
|
401
|
+
a code meaning the CREDENTIAL itself was refused (a dead or expired token, inside a 200 or a 4xx error list), list it in
|
|
402
|
+
`credentialRefusedErrorCodes` beside `errorCodePath`: the stored credential is then recorded as rejected, as a REST
|
|
403
|
+
vendor's `applicationOutcome.credentialRefusedErrorCodes` does. Never list a code for a resource the token may not reach
|
|
404
|
+
or a missing scope: that credential still works. A vendor that refuses a bad token with an HTTP 401 (GitHub) lists none:
|
|
405
|
+
the engine reads a 401 itself. A 401 to a credential that IS the stored value (an API key in a header or the query, a
|
|
406
|
+
pasted token) records it as rejected; a 401 to an OAuth2 access token records nothing, because renewal decides (a grant
|
|
407
|
+
the vendor refuses to renew is retired there); a 403 never moves the credential.
|
|
408
|
+
A vendor that refuses a WRITE in its payload rather than in `errors` (Shopify's `userErrors`, Linear's `success`) is
|
|
409
|
+
declared on the mutation as `graphql.payloadRefusal`: `{ kind: ProviderGraphqlPayloadRefusalKind.USER_ERRORS, path:
|
|
410
|
+
'productCreate.userErrors', messagePath: 'message', fieldPath: 'field' }` or `{ kind:
|
|
411
|
+
ProviderGraphqlPayloadRefusalKind.SUCCESS_FLAG, path: 'issueCreate.success' }`, paths from `data`. A non-empty list or a
|
|
412
|
+
`false` flag then FAILS the call with the vendor's messages instead of returning a refused write as a result; only a
|
|
413
|
+
mutation may declare it.
|
|
414
|
+
The catalogue load, the
|
|
415
|
+
augmentation merge and `wildo registry publish` refuse a document that disagrees with its declaration. The OpenAPI
|
|
416
|
+
conformance check skips a GraphQL operation; instead, a module declaring one must pin the vendor's published schema in
|
|
417
|
+
`wildo.module.json` under `provider.graphqlSchema`: `url`, a URL that does not move (for GitHub, its docs
|
|
418
|
+
repository's `src/graphql/data/fpt/schema.docs.graphql` at a commit), and `revision`, `sha256:<hex>` of that
|
|
419
|
+
document's bytes (`shasum -a 256`). The document is SDL or an introspection result as JSON. Publish validates every
|
|
420
|
+
GraphQL document against it and refuses a field, an argument or a variable type the vendor's schema does not have,
|
|
421
|
+
naming the operation; it also refuses a module with GraphQL operations and no pin, a pin with no GraphQL operation,
|
|
422
|
+
and a document whose bytes no longer match `revision`. The contract is in the `provider-operation-calls` skill's
|
|
423
|
+
`references/framework-rest-operation-contract-api.md`.
|
|
424
|
+
|
|
342
425
|
### What a provider module tells you about vendors and engine refs
|
|
343
426
|
|
|
344
427
|
Two things in a provider module are easy to misread:
|
|
@@ -380,6 +463,143 @@ refused for a missing scope then offers a re-authorization that asks for that
|
|
|
380
463
|
scope only, and the stored grant keeps what was granted before. Read
|
|
381
464
|
`references/framework-provider-incremental-consent-api.md`.
|
|
382
465
|
|
|
466
|
+
### A connected-account provider: declare how the client authenticates to the token endpoint
|
|
467
|
+
|
|
468
|
+
The code exchange, every refresh and the revocation all send the application's client id and
|
|
469
|
+
secret to the vendor. By default they go in a form-encoded body (`client_secret_post`). Read the
|
|
470
|
+
vendor's token-endpoint documentation (or its discovery document's
|
|
471
|
+
`token_endpoint_auth_methods_supported`) and, when it shows an `Authorization: Basic` header,
|
|
472
|
+
declare it on the `oauth2` block:
|
|
473
|
+
|
|
474
|
+
- `tokenEndpointAuthMethod: ProviderOAuth2ClientAuthenticationMethod.CLIENT_SECRET_BASIC` — the
|
|
475
|
+
framework sends `Basic base64(id:secret)` (each half form-urlencoded first, as RFC 6749 asks) and
|
|
476
|
+
puts neither value in the body. It applies to the exchange, the refresh and the revocation alike.
|
|
477
|
+
- `tokenRequestBodyEncoding: ProviderOAuth2RequestBodyEncoding.JSON` — for a vendor whose token
|
|
478
|
+
endpoint takes a JSON body (Notion). Absent means a form body.
|
|
479
|
+
- `revocationRequestBodyEncoding: ProviderOAuth2RequestBodyEncoding.JSON` — the same choice for the
|
|
480
|
+
revocation request, declared separately because a vendor can differ there (Intuit: form token
|
|
481
|
+
request, JSON revocation).
|
|
482
|
+
|
|
483
|
+
Both enums come from `@wildo-ai/external-connectors-models`; their definitions are in
|
|
484
|
+
`references/framework-provider-incremental-consent-api.md` beside the other `oauth2` vocabularies.
|
|
485
|
+
Declaring nothing keeps the default bytes, so declare only what the vendor documents; a wrong guess
|
|
486
|
+
surfaces as the vendor refusing the connect with `invalid_client`.
|
|
487
|
+
|
|
488
|
+
Two more `oauth2` declarations, each only when the vendor documents it:
|
|
489
|
+
|
|
490
|
+
- `codeExchangeParameters` — fixed extra parameters of the AUTHORIZATION-CODE exchange, never the
|
|
491
|
+
refresh: Shopify's `{ expiring: '1' }`, which asks for an expiring token with a refresh token. A name
|
|
492
|
+
the framework writes itself (`grant_type`, `code`, `redirect_uri`, `code_verifier`, the client's
|
|
493
|
+
credentials, `refresh_token`, `scope`) is refused at startup.
|
|
494
|
+
- `refreshRefusals` — the refresh refusals the vendor documents as a dead refresh token, beside
|
|
495
|
+
`invalid_grant`: `[{ error: 'invalid_request', errorDescription: 'This request requires an active
|
|
496
|
+
refresh_token' }]` for Shopify. A refresh refused that way retires the connection instead of being
|
|
497
|
+
retried. Give `errorDescription` whenever the code is a generic one, so a malformed request is not
|
|
498
|
+
read as a dead grant; `invalid_client` is refused (it names the application's registration).
|
|
499
|
+
|
|
500
|
+
### The application's own account of a connected-account provider: a client-credentials grant
|
|
501
|
+
|
|
502
|
+
A pasted access token in the `apiKey` slot is right for a vendor whose keys last (an API token).
|
|
503
|
+
It is wrong when the vendor's tokens expire within hours: the application's own connection stops
|
|
504
|
+
working the same day. When the vendor offers a server-to-server grant, declare `clientCredentials`
|
|
505
|
+
on the REST contract BESIDE `oauth2`. The framework then mints the APPLICATION's token from it,
|
|
506
|
+
caches it until a minute before it expires and mints anew, while people and organizations keep
|
|
507
|
+
connecting through the exchange. Admit the `APPLICATION × SERVICE` connection, and keep
|
|
508
|
+
`apiKey.secretRef` on the exchanged token's slot (startup refuses the client secret's slot there).
|
|
509
|
+
|
|
510
|
+
- `tokenUrl` / `tokenHosts` — the https token endpoint and the hosts it may be on; the client
|
|
511
|
+
secret is sent nowhere else. When the token endpoint is on the deployment's OWN vendor instance
|
|
512
|
+
(Okta's org, `https://<org>/oauth2/v1/token`), write `tokenUrl: '{deploymentOrigin}/oauth2/v1/token'`
|
|
513
|
+
(`PROVIDER_CLIENT_CREDENTIALS_DEPLOYMENT_ORIGIN_PLACEHOLDER`) and `tokenHosts: []`: the framework fills it
|
|
514
|
+
with the origin of the base URL your contract's `baseUrlHostEnvVarName` (or `baseUrlEnvVarName`) names,
|
|
515
|
+
the same host your operations go to. Admitted for the application's own connection only.
|
|
516
|
+
- `clientIdSecretRef` / `clientSecretSecretRef` — the slots of the vendor's SERVER app, which is
|
|
517
|
+
usually a separate app from the OAuth one (Box's Server Authentication app, Zoom's
|
|
518
|
+
Server-to-Server OAuth app). Declare them in the secrets contract with
|
|
519
|
+
`scope: ExternalProvider_SecretScope.REGISTRATION`.
|
|
520
|
+
- `scope` — only when the vendor takes one; omitted, none is sent.
|
|
521
|
+
- `grantType` — `ProviderClientCredentialsGrantType.ACCOUNT_CREDENTIALS` for Zoom; omitted,
|
|
522
|
+
`client_credentials`.
|
|
523
|
+
- `tokenEndpointAuthMethod` — `CLIENT_SECRET_BASIC` when the vendor documents the Basic header;
|
|
524
|
+
omitted, the id and secret go in the body.
|
|
525
|
+
- `privateKeyJwt` — INSTEAD of `clientSecretSecretRef`, when the vendor authenticates the client
|
|
526
|
+
with a key (`private_key_jwt`: Okta service apps, certificate credentials): `privateKeySecretRef`
|
|
527
|
+
(an unencrypted PEM, PKCS#8 or RSA PKCS#1 / EC; literal `\n` is read as a newline), `algorithm`
|
|
528
|
+
(`ProviderClientAssertionSigningAlgorithm.ES256` or `RS256`, matching the key), optional
|
|
529
|
+
`keyIdSecretRef` (sent as `kid`) and `assertionLifetimeSeconds` (default 300, at most 3600). The
|
|
530
|
+
framework signs a fresh assertion per token request (`iss` = `sub` = the client id, `aud` = the
|
|
531
|
+
token URL, a new `jti`) and sends no secret.
|
|
532
|
+
- `tokenRequestParameters` — further parameters the vendor requires, each a fixed `value` or a slot
|
|
533
|
+
(`secretRef`): Box's `box_subject_type: { value: 'enterprise' }` and
|
|
534
|
+
`box_subject_id: { secretRef: 'BOX_ENTERPRISE_ID' }`, Zoom's `account_id`. The grant's own
|
|
535
|
+
parameters (`grant_type`, `client_id`, `client_secret`, `scope`) are refused here.
|
|
536
|
+
|
|
537
|
+
Alone (no `oauth2`), `clientCredentials` serves every connection, an organization typing its own
|
|
538
|
+
client id and secret (a Teams bot), and `apiKey.secretRef` IS the client secret's slot. The
|
|
539
|
+
contract's definitions (`ProviderRestClientCredentials` and its vocabularies) are in the
|
|
540
|
+
`provider-operation-calls` skill's `references/framework-rest-operation-contract-api.md`.
|
|
541
|
+
|
|
542
|
+
### The application's own account of a vendor whose host is per customer
|
|
543
|
+
|
|
544
|
+
A base URL such as `https://{subdomain}.zendesk.com` is filled from the answer a person gave when
|
|
545
|
+
connecting, admitted against `baseUrlHostAllowances`. The application's own account has no
|
|
546
|
+
connection and answers nothing, so every call it makes (a subject erasure's included) is refused.
|
|
547
|
+
Declare what it answers instead, read from the deployment:
|
|
548
|
+
|
|
549
|
+
```ts
|
|
550
|
+
applicationConnectionAnswers: { subdomain: 'ZENDESK_SUBDOMAIN' },
|
|
551
|
+
```
|
|
552
|
+
|
|
553
|
+
The key is the answer's name: a placeholder of the base URL, or the `answer` a
|
|
554
|
+
`DERIVED_FROM_CONNECTION_ANSWER` allowance follows (Intercom's `appHost`, whose API host follows the
|
|
555
|
+
region). The value is the env var of a secrets-contract slot declared with
|
|
556
|
+
`scope: ExternalProvider_SecretScope.REGISTRATION` and `holdsDeploymentHost: true`; anything else
|
|
557
|
+
is refused without being read. The deployment's answer goes through the SAME allowance a person's
|
|
558
|
+
does, so it reaches no host a person could not connect to. Unset, the call is refused naming the
|
|
559
|
+
variable (or takes a derived allowance's `whenUnanswered` host). Admit the
|
|
560
|
+
`APPLICATION × SERVICE` connection.
|
|
561
|
+
|
|
562
|
+
### A connected account addressed by a fact its vendor reports
|
|
563
|
+
|
|
564
|
+
Some vendors address every path to the account the person connected: QuickBooks' `/v3/company/{realmId}/…`.
|
|
565
|
+
Never make that an operation input. Declare the fact under `oauth2.reportedAccountFacts` with a
|
|
566
|
+
`pathSegmentPattern` (the shape the whole value must have, anchored for you), and name it on the PATH
|
|
567
|
+
parameter with `connectionFact` (the second line, in `operations.ts`); the operation's `inputSchema` must not
|
|
568
|
+
declare it:
|
|
569
|
+
|
|
570
|
+
```ts
|
|
571
|
+
reportedAccountFacts: {
|
|
572
|
+
realmId: { responsePath: 'realmId', source: ProviderOAuth2ReportedFactSource.AUTHORIZATION_REDIRECT_QUERY, pathSegmentPattern: '\\d+' },
|
|
573
|
+
},
|
|
574
|
+
{ name: 'realmId', in: ProviderRestParameterLocation.PATH, required: true, connectionFact: 'realmId' },
|
|
575
|
+
```
|
|
576
|
+
|
|
577
|
+
`source` says where the vendor puts it: the token answer (the default), its ID token's claims, or the query of the
|
|
578
|
+
authorization redirect (Intuit's `realmId`). The connect is refused when the fact is missing or outside the pattern,
|
|
579
|
+
every call re-admits the stored value, and a caller value under that name is refused. A redirect value crosses the
|
|
580
|
+
person's browser, so it is admitted only as a path value of a vendor that checks it against the token; it may never be
|
|
581
|
+
an `origin`, fill a host, or route deliveries. A token-answer fact may instead fill a base URL host placeholder with
|
|
582
|
+
`fillsBaseUrlHost: true`, admitted against the `baseUrlHostAllowances` entry of the same name, as a typed host is.
|
|
583
|
+
Undeclared, a reported fact fills nothing.
|
|
584
|
+
|
|
585
|
+
When the vendor names the account only at its USERINFO endpoint (DocuSign's `accounts[].account_id` and
|
|
586
|
+
`base_uri`), declare `oauth2.userInfoUrl` and read the facts with `source: ProviderOAuth2ReportedFactSource.USERINFO_RESPONSE`.
|
|
587
|
+
The engine calls it once, with the token the person just granted, when they connect; never at a refresh. It may carry
|
|
588
|
+
only the host placeholders the token endpoint carries. A `responsePath` step may pick ONE array element by a stated
|
|
589
|
+
condition, so two facts come from the same element:
|
|
590
|
+
|
|
591
|
+
```ts
|
|
592
|
+
userInfoUrl: 'https://{accountServerHost}/oauth/userinfo',
|
|
593
|
+
reportedAccountFacts: {
|
|
594
|
+
accountId: { responsePath: 'accounts[is_default=true].account_id', source: ProviderOAuth2ReportedFactSource.USERINFO_RESPONSE, pathSegmentPattern: '[0-9A-Fa-f-]{36}' },
|
|
595
|
+
baseUri: { responsePath: 'accounts[is_default=true].base_uri', source: ProviderOAuth2ReportedFactSource.USERINFO_RESPONSE, fillsBaseUrlHost: true },
|
|
596
|
+
},
|
|
597
|
+
```
|
|
598
|
+
|
|
599
|
+
An answer where zero or several elements meet the condition refuses the connect
|
|
600
|
+
(`REPORTED_FACT_SELECTION_NOT_SINGLE`); a `fillsBaseUrlHost` fact missing from the answer refuses it too, since every
|
|
601
|
+
call goes there.
|
|
602
|
+
|
|
383
603
|
### A connected-account provider: the revocation endpoint is used on every teardown
|
|
384
604
|
|
|
385
605
|
A provider whose REST contract carries `oauth2` lets people and tenants connect their own accounts.
|
|
@@ -393,13 +613,15 @@ erasure also reports it in the erasure receipt's external effects.
|
|
|
393
613
|
|
|
394
614
|
What that means for the provider author:
|
|
395
615
|
|
|
396
|
-
- Declare the URL only if the endpoint is really RFC 7009-shaped (
|
|
397
|
-
success). A Web-API revocation method (Slack's `auth.revoke`) or a
|
|
398
|
-
leave the field absent and every teardown honestly records `not_declared`.
|
|
616
|
+
- Declare the URL only if the endpoint is really RFC 7009-shaped (a `token` parameter, 200 on
|
|
617
|
+
success). A Web-API revocation method (Slack's `auth.revoke`) or a `DELETE` (GitHub's) is not;
|
|
618
|
+
leave the field absent and every teardown honestly records `not_declared`. A vendor that takes
|
|
619
|
+
`token` as a JSON body (Intuit, Notion) still qualifies: declare
|
|
620
|
+
`revocationRequestBodyEncoding: ProviderOAuth2RequestBodyEncoding.JSON` beside the URL.
|
|
399
621
|
- The call uses the application's own client registration (`clientIdSecretRef` /
|
|
400
|
-
`clientSecretSecretRef`)
|
|
401
|
-
|
|
402
|
-
hosts connected accounts.
|
|
622
|
+
`clientSecretSecretRef`), authenticated exactly as at the token endpoint (the client-authentication section above). If those
|
|
623
|
+
secrets are unset, the outcome is `not_configured`, and on an erasure the person's grant stays
|
|
624
|
+
live at the vendor — so set them in every environment that hosts connected accounts.
|
|
403
625
|
- Nothing ever retries a revocation: the token exists only in the destroyed row. The recorded
|
|
404
626
|
outcome is the whole record.
|
|
405
627
|
|
|
@@ -434,7 +656,7 @@ Read `references/framework-provider-file-storage-adapter-api.md`.
|
|
|
434
656
|
|
|
435
657
|
### Receiving your vendor's requests: an endpoint the engine verifies
|
|
436
658
|
|
|
437
|
-
Name an engine scheme (`SVIX_V1`, `SLACK_V0`, `BOT_FRAMEWORK_JWT`) on a `WEBHOOK_ORIGINATOR` endpoint and the engine
|
|
659
|
+
Name an engine scheme (`SVIX_V1`, `SLACK_V0`, `BOT_FRAMEWORK_JWT`, `ED25519`, `BASIC_CREDENTIAL`, `MAILGUN_FORWARD_JSON`) on a `WEBHOOK_ORIGINATOR` endpoint and the engine
|
|
438
660
|
verifies every request; the endpoint adds pure `identifyEvent` / `answerHandshake` / `acknowledge` functions and its
|
|
439
661
|
`contentTypes`, and an inbound handler serves it. Read `references/framework-provider-inbound-endpoint-api.md`.
|
|
440
662
|
|
|
@@ -451,6 +673,25 @@ those references, the effect is not registered and erasure reports your vendor N
|
|
|
451
673
|
when the operator declared the vendor's own deletion window instead), with a boot warning saying why. It runs for
|
|
452
674
|
`eraseSubjectAsSystem` only. Read `references/framework-provider-subject-erasure-effect-api.md`.
|
|
453
675
|
|
|
676
|
+
### Checking a setting only your vendor can judge: a configuration check
|
|
677
|
+
|
|
678
|
+
When a setting can be well-formed and still wrong (an account id that must be the one the API key belongs to, a
|
|
679
|
+
workspace that must be the one the bot token is installed in), ship `configurationCheck` on the backend module: an
|
|
680
|
+
async function of your declared secrets (`readSecret`) and your own READ operations on the application's connection
|
|
681
|
+
(`execute`), answering one sentence per problem. The backend runs it once at boot in the background and logs each
|
|
682
|
+
sentence as a WARN; `wildo local doctor` runs it against the local environment and prints a WARN line. It never stops
|
|
683
|
+
anything: a check that throws or overruns is reported as "could not be run". Read
|
|
684
|
+
`references/framework-provider-configuration-check-api.md`.
|
|
685
|
+
|
|
686
|
+
### Reporting what your provider can say about its own state: a compliance-state collector
|
|
687
|
+
|
|
688
|
+
When your provider holds state an auditor would ask about (which account the application uses at your vendor, whether
|
|
689
|
+
it is the vendor's built-in administrator, how your client trusts the server), ship `complianceStateCollectorFactory` on
|
|
690
|
+
the backend module. It receives your resolved secrets and where each came from (platform-minted or operator-authored),
|
|
691
|
+
and returns facts: vocabulary members and booleans, never a value and never a verdict. The application's assurance
|
|
692
|
+
cycle reads every declared provider through one evidence door and records the snapshot; a provider declared but not
|
|
693
|
+
configured is recorded as absent, never guessed. Read `references/framework-provider-compliance-state-collector-api.md`.
|
|
694
|
+
|
|
454
695
|
### What the engine records for each call your capability provider makes
|
|
455
696
|
|
|
456
697
|
An email, SMS, billing or storage provider is called by the engine's own egress, never by
|
|
@@ -543,7 +784,12 @@ providers: defineSaaSProviders({
|
|
|
543
784
|
- `references/framework-provider-subject-erasure-effect-api.md` — reaching
|
|
544
785
|
your vendor when a person is erased: the effect contract, what the
|
|
545
786
|
application declares, how the outcome is decided (source-backed)
|
|
787
|
+
- `references/framework-provider-configuration-check-api.md` — checking a setting only your vendor can judge: the
|
|
788
|
+
`configurationCheck` contract, where it runs (backend boot, `wildo local doctor`) and why it never refuses (source-backed)
|
|
789
|
+
- `references/framework-provider-compliance-state-collector-api.md` — reporting what your provider can say about its own state:
|
|
790
|
+
the `complianceStateCollectorFactory` contract, the facts vocabulary, and why a value can never reach the evidence (source-backed)
|
|
546
791
|
- `references/framework-provider-inbound-endpoint-api.md` — receiving your vendor's requests: engine-verified schemes, handshake, event naming, synchronous answer (source-backed)
|
|
792
|
+
- `references/framework-provider-processing-region-api.md` — declaring how each processing region is reached (its own endpoint, or the operator's account), what an application's region choice then does to every arm, and when it is refused (source-backed)
|
|
547
793
|
|
|
548
794
|
## Verification
|
|
549
795
|
|
|
@@ -558,6 +804,9 @@ providers: defineSaaSProviders({
|
|
|
558
804
|
- [ ] The process starts and its provider count includes the new ref.
|
|
559
805
|
- [ ] An augmentation is named under `providers.augmentations.<baseRef>`
|
|
560
806
|
and appears in the host's artifact under `providerRuntimeAugmentations`.
|
|
807
|
+
- [ ] A setting that can be well-formed and wrong is checked by the module's
|
|
808
|
+
`configurationCheck`, and `wildo local doctor` shows its
|
|
809
|
+
`provider configuration (<ref>)` line.
|
|
561
810
|
|
|
562
811
|
### Grep invariants
|
|
563
812
|
|
|
@@ -584,6 +833,10 @@ rg -n "acme" backend-api/src/provider-contributions.ts
|
|
|
584
833
|
# an erasure stance that reaches the vendor has the effect that does it, and the application said where the ids are
|
|
585
834
|
rg -n "EXTERNAL_ERASURE_OPERATION|subjectErasureEffect" providers/acme/backend/src
|
|
586
835
|
rg -n "subjectReferences" wildo.saas.config.ts
|
|
836
|
+
|
|
837
|
+
# a setting only the vendor can judge is checked by the module, and doctor runs it
|
|
838
|
+
rg -n "configurationCheck" providers/acme/backend/src
|
|
839
|
+
wildo local doctor
|
|
587
840
|
```
|
|
588
841
|
|
|
589
842
|
The last one should find NOTHING for a package provider. A package is
|
|
@@ -603,6 +856,7 @@ disagree with the package.
|
|
|
603
856
|
| "The engine already has this vendor, so I will publish our own provider with the same ref." | Composition refuses two owners of one ref. Ship an augmentation of the engine's ref and have the application opt it in under `providers.augmentations`; it adds operations and leaves the vendor's identity, credential and connection with its owner. |
|
|
604
857
|
| "The augmentation is installed, so its operations are available." | Nothing applies until `providers.augmentations.<baseRef>` names the package and `wildo config sync` records it; the artifact grep below shows whether it did. |
|
|
605
858
|
| "I declared `EXTERNAL_ERASURE_OPERATION`, so an erasure reaches the vendor." | Only with a `subjectErasureEffect` on the module AND the application's `subjectReferences`. Without the effect the stance promises a door nobody built; without the references the engine has nothing to erase by. Either way every erasure reads NOT_REGISTERED, unless the operator declared the vendor's own deletion window as the answer instead. |
|
|
859
|
+
| "I will document the setting and ask the application to call my validation function at boot." | Nothing calls a function an application was asked to call. Declare it as `configurationCheck`: the backend runs it at boot and `wildo local doctor` runs it, both as a WARN, with no application code. |
|
|
606
860
|
| "I will override the provider's `runtimeContract.baseUrl` in `providerConfigurations` to reach my local double." | The configuration is refused: the module owns where its key goes. Set the host slot to `127.0.0.1:<port>` in a development environment instead; staging and production refuse it. |
|
|
607
861
|
| "Our provider also handles email, so I will give it the email arm." | Composition refuses a non-MAIN provider that declares an engine slot's runtime arm while claiming no capability for it. Declare the capability that names the slot — that is what makes it a deliberate substitution rather than an accident. |
|
|
608
862
|
|
|
@@ -630,6 +884,9 @@ disagree with the package.
|
|
|
630
884
|
- A module declaring `EXTERNAL_ERASURE_OPERATION` with no `subjectErasureEffect` —
|
|
631
885
|
catch with the erasure grep above; startup refuses the reverse (an effect on
|
|
632
886
|
any other stance).
|
|
887
|
+
- A provider skill telling the application to log a validation function
|
|
888
|
+
"once at boot": that is a `configurationCheck` the module should declare —
|
|
889
|
+
catch with the `configurationCheck` grep above.
|
|
633
890
|
- A `runtimeContract` or `endpoints` key under `providerConfigurations` —
|
|
634
891
|
catch with the re-point grep above; every configuration door refuses it.
|
|
635
892
|
- A host slot set to `127.0.0.1:<port>` in a staging or production
|
|
@@ -7,13 +7,12 @@ is yours to install in the runtime that enables it.
|
|
|
7
7
|
|
|
8
8
|
In a registry provider module (`providers/<ref>/`), the facet declares the SDK as `"*"` and the module's
|
|
9
9
|
`wildo.module.json` records its exact version once, in `dependsOn.npm.dependencies`: the version the module was
|
|
10
|
-
proven with. Installing the module writes that version into your application's `pnpm.
|
|
10
|
+
proven with. Installing the module writes that version into your application's overrides in `pnpm-workspace.yaml` (an update moves it,
|
|
11
11
|
a remove takes out what the install wrote). An SDK whose install script must run (a native addon) is also listed in
|
|
12
|
-
`dependsOn.npm.onlyBuiltDependencies`, and the install adds it to your root `
|
|
12
|
+
`dependsOn.npm.onlyBuiltDependencies`, and the install adds it to `onlyBuiltDependencies` in your root `pnpm-workspace.yaml`
|
|
13
13
|
and runs `pnpm rebuild -r <name>` after its install, which is what runs the script of a package already installed. If you
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
a `neverBuiltDependencies` list) and warns you: add the name where your list lives, then run
|
|
14
|
+
run every script but a `neverBuiltDependencies` list, the install writes nothing (pnpm refuses to install with both an
|
|
15
|
+
allow-list and a `neverBuiltDependencies` list) and warns you: take the name out of that list, then run
|
|
17
16
|
`pnpm rebuild -r <name>`, or run `pnpm approve-builds`, which does both. Publishing refuses a module whose record, facets
|
|
18
17
|
and `requiredPackages` disagree.
|
|
19
18
|
|