@wildo-ai/framework-knowledge 1.1.3 → 1.1.5
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/esm/framework-knowledge.definitions.d.ts +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +349 -17
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts +19 -0
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js +47 -1
- package/dist/esm/framework-knowledge.loader.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
- 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 +125 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +177 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +213 -7
- 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 +326 -8
- 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 +5 -3
- 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 +21 -14
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +57 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +63 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +132 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +179 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +67 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +76 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +5 -4
- 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 +10 -5
- 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 +67 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +82 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +25 -9
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +124 -7
- 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 +67 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +83 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +69 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +71 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -1
- 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 +71 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +88 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +97 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +156 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +115 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +152 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +188 -8
- 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 +167 -9
- 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 +171 -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 +146 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts +248 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js +248 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +157 -4
- 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 +172 -4
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +5 -4
- 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 +8 -7
- 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 +3 -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 +22 -3
- 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 +5 -3
- 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 +21 -12
- 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 +192 -27
- 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 +172 -33
- 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 +2 -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 +6 -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 +182 -5
- 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 +191 -5
- 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 +2 -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 +3 -2
- 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 +154 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +214 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +44 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +51 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -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 +2 -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 +2 -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 +6 -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 +2 -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 +2 -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 +2 -2
- 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 +7 -3
- 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 +32 -4
- 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 +27 -3
- 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 +2 -2
- 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 +4 -2
- 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 +199 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +227 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +5 -3
- 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 +18 -4
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +155 -4
- 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 +187 -4
- 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 +6 -5
- 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 +18 -17
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.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 -0
- package/dist/knowledge/manifest.json +9 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +75 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
- package/dist/knowledge/playbooks/bottom_up.build/method.md +79 -0
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +65 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +1122 -76
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +49 -13
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +671 -47
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +10 -16
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +31 -35
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -16
- package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +95 -0
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +62 -0
- package/dist/knowledge/playbooks/bottom_up.conception/method.md +80 -0
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +90 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +107 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +70 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +8 -8
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +14 -13
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +165 -0
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +74 -0
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +219 -140
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +55 -22
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +138 -0
- package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +70 -0
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +87 -0
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +69 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +236 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +63 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +116 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +79 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +71 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +70 -0
- package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +83 -0
- package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +68 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +873 -15
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +19 -12
- package/dist/knowledge/playbooks/refinement.document-facts/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.document-facts/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +186 -21
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +12 -16
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +343 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +54 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +28 -11
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -17
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +8 -15
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +25 -49
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +14 -17
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +101 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +209 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +68 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +42 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +39 -12
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +18 -66
- package/dist/knowledge/playbooks/top_down.compliance-research/method.md +78 -0
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +43 -0
- package/dist/knowledge/playbooks/top_down.definition/method.md +103 -0
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +75 -0
- package/dist/knowledge/playbooks/top_down.expert-personas/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +48 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/method.md +51 -165
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +25 -44
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +43 -0
- package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +45 -0
- package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +247 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +71 -0
- 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/method.md +36 -69
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +12 -9
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +11 -7
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +12 -16
- package/dist/knowledge/playbooks/top_down.risk-register/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.risk-register/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +46 -0
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +59 -0
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +12 -5
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +15 -17
- package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +23 -14
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +12 -17
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +13 -17
- package/dist/knowledge/references/acp.execution-profile.md +266 -0
- package/dist/knowledge/references/acp.host-configuration-inheritance.md +29 -0
- package/dist/knowledge/references/acp.permission-ceiling.md +105 -0
- package/dist/knowledge/references/acp.permission-escalation.md +37 -0
- package/dist/knowledge/references/application-documentation-chapters.config.md +152 -0
- package/dist/knowledge/references/application-documentation-plan.config.md +136 -0
- package/dist/knowledge/references/application-maturity.config.md +319 -0
- package/dist/knowledge/references/assertions.authored-metadata.config.md +1 -1
- package/dist/knowledge/references/assertions.specification.config.md +1 -1
- package/dist/knowledge/references/brand.asset.config.md +8 -16
- package/dist/knowledge/references/brand.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/brand.logo-direction.config.md +9 -7
- package/dist/knowledge/references/brand.snapshot.config.md +16 -2
- package/dist/knowledge/references/brand.snapshot.validation.md +0 -7
- package/dist/knowledge/references/build-plan.task-graph.config.md +581 -7
- package/dist/knowledge/references/business-model.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/business-model.pricing-plan.config.md +1 -1
- package/dist/knowledge/references/business-model.snapshot.validation.md +15 -0
- package/dist/knowledge/references/capability-composition.config.md +155 -0
- package/dist/knowledge/references/cli.market.utils.md +1 -0
- package/dist/knowledge/references/companion.technical-doc.service.md +453 -98
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +21 -0
- package/dist/knowledge/references/engine.client-bundle.external-connectors-public.discipline.md +20 -1
- package/dist/knowledge/references/engine.saas-technical-doc.config.md +8 -4
- package/dist/knowledge/references/engine.saas-website.config.md +22 -10
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +8 -12
- package/dist/knowledge/references/example.config.app-shell.full.md +42 -7
- package/dist/knowledge/references/example.config.backend.required-floors.md +4 -0
- package/dist/knowledge/references/example.config.design-system.full.md +3 -0
- package/dist/knowledge/references/example.engine.product-definitions.feature-and-profiles.md +19 -7
- package/dist/knowledge/references/example.features.connected-feature.declaration.md +66 -0
- package/dist/knowledge/references/example.features.connected-feature.surface.md +42 -0
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +4 -3
- package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +6 -10
- package/dist/knowledge/references/example.guidance.bound-survey-flow.md +82 -0
- package/dist/knowledge/references/example.infra.environment-config.local.md +88 -11
- package/dist/knowledge/references/example.milestones.module-definitions.md +73 -0
- package/dist/knowledge/references/example.minion.contained-tick.md +79 -0
- package/dist/knowledge/references/example.module.companion-exports.full.md +38 -3
- package/dist/knowledge/references/example.provider.backend-module-shape.md +31 -13
- package/dist/knowledge/references/example.provider.frontend-app.module.md +103 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +20 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +7 -3
- package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +30 -0
- package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +11 -0
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +3 -0
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +94 -10
- package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +79 -0
- package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +18 -0
- package/dist/knowledge/references/example.worker.node-route.md +94 -0
- package/dist/knowledge/references/experience-plan.config.md +311 -0
- package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +132 -9
- package/dist/knowledge/references/external-connectors.backend.provider-package-convention.md +36 -0
- package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +269 -0
- package/dist/knowledge/references/integration-plan.config.md +185 -0
- package/dist/knowledge/references/market.alternative.config.md +1 -1
- package/dist/knowledge/references/market.authored-metadata.config.md +12 -9
- package/dist/knowledge/references/market.channel.config.md +3 -3
- package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
- package/dist/knowledge/references/market.gain.config.md +1 -1
- package/dist/knowledge/references/market.icp.config.md +2 -2
- package/dist/knowledge/references/market.job.config.md +1 -1
- package/dist/knowledge/references/market.message-template.config.md +2 -2
- package/dist/knowledge/references/market.objection.config.md +1 -1
- package/dist/knowledge/references/market.pain.config.md +1 -1
- package/dist/knowledge/references/market.persona.config.md +2 -2
- package/dist/knowledge/references/market.proof.config.md +1 -1
- package/dist/knowledge/references/market.snapshot.validation.md +15 -0
- package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
- package/dist/knowledge/references/market.trigger.config.md +1 -1
- package/dist/knowledge/references/minions.tick-contract.md +83 -0
- package/dist/knowledge/references/placement-plan.config.md +369 -0
- package/dist/knowledge/references/platform.config.application-database.md +5 -2
- package/dist/knowledge/references/platform.config.backing-services.md +0 -21
- package/dist/knowledge/references/platform.config.environment.deployment.md +206 -14
- package/dist/knowledge/references/platform.config.infra-provider-resolution.md +170 -0
- package/dist/knowledge/references/platform.config.infrastructure-host.md +87 -0
- package/dist/knowledge/references/platform.config.saas.md +261 -9
- package/dist/knowledge/references/presets.models.labelling.sections.md +14 -0
- package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
- package/dist/knowledge/references/requirements.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/requirements.snapshot.validation.md +15 -0
- package/dist/knowledge/references/roadmap.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/roadmap.snapshot.validation.md +15 -7
- package/dist/knowledge/references/saas.backend.a2a.token-budget.md +71 -0
- package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +1 -2
- package/dist/knowledge/references/saas.backend.auth.federated-identity-provider-private-networks.md +62 -0
- package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +86 -0
- package/dist/knowledge/references/saas.backend.billing.catalog-sync-result.md +37 -0
- package/dist/knowledge/references/saas.backend.billing.resolution-failure-reasons.md +24 -5
- package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +187 -0
- package/dist/knowledge/references/saas.backend.domain-module.md +25 -1
- package/dist/knowledge/references/saas.backend.error-builder.user-guidance.md +82 -0
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +6 -0
- package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +22 -4
- package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +17 -4
- package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +84 -0
- package/dist/knowledge/references/saas.backend.health-readiness-contributor.md +73 -0
- package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +200 -0
- package/dist/knowledge/references/saas.backend.providers.operation-executor.md +51 -0
- package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +71 -0
- package/dist/knowledge/references/saas.backend.queue.worker-topology.md +39 -0
- package/dist/knowledge/references/saas.backend.system-access-service.md +51 -42
- package/dist/knowledge/references/saas.composition.scenario-apply.md +51 -0
- package/dist/knowledge/references/saas.config.content-security-policy.md +97 -0
- package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +91 -21
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +4 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +38 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +27 -27
- package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +65 -16
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +41 -11
- package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +44 -8
- package/dist/knowledge/references/saas.frontend.billing-context.md +108 -0
- package/dist/knowledge/references/saas.frontend.brand-identity.md +38 -0
- package/dist/knowledge/references/saas.frontend.celebration-overlay-contract.md +41 -0
- package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +64 -0
- package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
- package/dist/knowledge/references/saas.frontend.errors.user-facing-error-message.md +47 -0
- package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.per-action-retry-loop.md +7 -1
- package/dist/knowledge/references/saas.frontend.execution-view.definition.md +3 -3
- package/dist/knowledge/references/saas.frontend.flows-actors-view.md +7 -4
- package/dist/knowledge/references/saas.frontend.form-fields.file-provider-constraints.md +30 -48
- package/dist/knowledge/references/saas.frontend.full-custom-view.definition.md +24 -0
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
- package/dist/knowledge/references/saas.frontend.onboarding-view.md +84 -0
- package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +65 -0
- package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
- package/dist/knowledge/references/saas.frontend.resource-header-title.md +28 -4
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +127 -1
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +327 -11
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +198 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +220 -0
- package/dist/knowledge/references/saas.market.generation-agent.md +26 -9
- package/dist/knowledge/references/saas.models.analytics.value-moments.md +132 -0
- package/dist/knowledge/references/saas.models.audit.trail-config.md +155 -0
- package/dist/knowledge/references/saas.models.auth.methods.md +513 -0
- package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +82 -0
- package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +77 -0
- package/dist/knowledge/references/saas.models.config.organization-types.md +192 -0
- package/dist/knowledge/references/saas.models.config.registration.md +188 -0
- package/dist/knowledge/references/saas.models.config.tenant-teardown.md +81 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +173 -3
- package/dist/knowledge/references/saas.models.email.template-type.md +40 -0
- package/dist/knowledge/references/saas.models.engine-capabilities.md +85 -7
- package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +61 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +43 -4
- package/dist/knowledge/references/saas.models.features.definition-builders.md +162 -0
- package/dist/knowledge/references/saas.models.file-upload-grant.md +222 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +54 -5
- package/dist/knowledge/references/saas.models.governed-document-acceptance-mode.md +116 -0
- package/dist/knowledge/references/saas.models.guidance-flow.md +160 -0
- package/dist/knowledge/references/saas.models.http-api-binding.md +76 -110
- package/dist/knowledge/references/saas.models.milestone-celebration.md +69 -0
- package/dist/knowledge/references/saas.models.milestone-definition.md +209 -0
- package/dist/knowledge/references/saas.models.navigation.layout.md +2 -2
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +150 -0
- package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +70 -0
- package/dist/knowledge/references/saas.models.notifications.targets.md +138 -0
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +256 -0
- package/dist/knowledge/references/saas.models.onboarding-elements.md +375 -0
- package/dist/knowledge/references/saas.models.onboarding-trigger.md +52 -0
- package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +50 -0
- package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +129 -0
- package/dist/knowledge/references/saas.models.privacy.client-instance-id-scope.md +49 -0
- package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +106 -0
- package/dist/knowledge/references/saas.models.progression-tracker-variant.md +76 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +8 -5
- package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +72 -0
- package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +50 -0
- package/dist/knowledge/references/saas.models.providers.capability-surface.md +58 -0
- package/dist/knowledge/references/saas.models.providers.compliance-choice.md +111 -0
- package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +156 -0
- package/dist/knowledge/references/saas.models.rate-limit-configuration.md +11 -1
- package/dist/knowledge/references/saas.models.relationship-handling-settings.md +23 -1
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -4
- package/dist/knowledge/references/saas.models.resource-config.forwarded-label.md +5 -4
- package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +69 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +15 -2
- package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +66 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-base.md +24 -1
- package/dist/knowledge/references/saas.models.resource-config.operation-cron-job.md +59 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +55 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +5 -4
- package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +158 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-step-up.md +77 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-for-key.md +6 -1
- package/dist/knowledge/references/saas.models.resource-config.queue-policy.md +49 -0
- package/dist/knowledge/references/saas.models.resource-config.required-features.md +84 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +10 -0
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +14 -0
- package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +111 -4
- package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +39 -0
- package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +48 -0
- package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +38 -0
- package/dist/knowledge/references/saas.models.resource-primary-scope.md +11 -2
- package/dist/knowledge/references/saas.models.scope-membership.md +3 -4
- package/dist/knowledge/references/saas.models.shared-saas-module.md +25 -0
- package/dist/knowledge/references/saas.models.systems-of-record.md +635 -0
- package/dist/knowledge/references/saas.public-runtime.contract.md +198 -1
- package/dist/knowledge/references/saas.rag.retrieval-result.md +19 -8
- package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
- package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +15 -36
- package/dist/knowledge/references/saas.specifications.application-document-publication.contract.md +9 -5
- package/dist/knowledge/references/saas.specifications.application-document-publication.generation.md +63 -0
- package/dist/knowledge/references/saas.specifications.application-document-release-set.contract.md +74 -0
- package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +123 -0
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +88 -7
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +774 -53
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +211 -14
- package/dist/knowledge/references/saas.specifications.composite-view-specification.md +10 -0
- package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +364 -0
- package/dist/knowledge/references/saas.specifications.playbook-approval-and-failure-policies.md +96 -0
- package/dist/knowledge/references/saas.specifications.processor-register.md +333 -0
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +8 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
- package/dist/knowledge/references/saas.website.astro.bridge.md +64 -2
- package/dist/knowledge/references/saas.website.astro.head-renderer.md +32 -12
- package/dist/knowledge/references/saas.website.astro.label-loader.md +3 -0
- package/dist/knowledge/references/saas.website.astro.robots-renderer.md +14 -1
- package/dist/knowledge/references/saas.website.blog.bridge.md +21 -1
- package/dist/knowledge/references/saas.website.consent.banner.md +218 -0
- package/dist/knowledge/references/saas.website.consent.context.md +162 -0
- package/dist/knowledge/references/saas.website.consent.gate.md +38 -0
- package/dist/knowledge/references/saas.website.page-layout.component.md +67 -1
- package/dist/knowledge/references/saas.website.page.context.md +4 -3
- package/dist/knowledge/references/saas.website.runtime.context.md +43 -7
- package/dist/knowledge/references/saas.website.section.context.md +3 -2
- package/dist/knowledge/references/saas.website.sections.category-enum.md +19 -20
- package/dist/knowledge/references/vision.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/website-plan.config.md +205 -0
- package/dist/knowledge/references/workers.node.worker-init-contract.md +57 -0
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +43 -2
- package/dist/knowledge/references/zod.decorators.data-categories.md +197 -0
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +51 -4
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +54 -1
- package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +35 -0
- package/dist/knowledge/references/zod.decorators.field-spec-params.md +32 -5
- package/dist/knowledge/references/zod.decorators.file-nature-constraints.md +86 -0
- package/dist/knowledge/references/zod.decorators.file-readiness-metadata.md +67 -0
- package/dist/knowledge/references/zod.decorators.file-schema.md +90 -14
- package/dist/knowledge/references/zod.decorators.file-vocabularies.md +84 -0
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +140 -4
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
- package/dist/knowledge/references/zod.decorators.rag-source.md +6 -2
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +24 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +35 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +46 -12
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +31 -12
- package/dist/knowledge/references/zod.factories.address.md +118 -0
- package/dist/knowledge/references/zod.factories.code.md +2 -0
- package/dist/knowledge/references/zod.factories.duration.md +2 -0
- package/dist/knowledge/references/zod.factories.money.md +2 -0
- package/dist/knowledge/references/zod.factories.phone.md +14 -1
- package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
- package/dist/knowledge/registries/framework-topics.json +1215 -11
- package/dist/knowledge/registries/playbooks.json +454 -50
- package/dist/knowledge/registries/source-tags.json +3153 -1043
- package/dist/knowledge/rules/database-migration-obligation.md +110 -0
- package/dist/knowledge/rules/live-context-door.md +108 -0
- package/dist/knowledge/rules/resource-schema-awareness.md +75 -0
- package/dist/knowledge/skills/INDEX.md +46 -11
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +80 -37
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +167 -0
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +6 -3
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -3
- package/dist/knowledge/skills/application-database-migrations/references/framework-application-database-api.md +5 -2
- package/dist/knowledge/skills/application-database-migrations/references/migration-refusals.md +32 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +94 -3
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +50 -0
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +26 -19
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +25 -1
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-readiness-contributor-api.md +135 -0
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +75 -12
- package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +137 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-error-user-guidance-api.md +112 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +72 -1
- package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +207 -0
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +31 -1
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-asset-api.md +8 -16
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +25 -9
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +135 -5
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +80 -17
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +369 -111
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +32 -10
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +103 -58
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-publication-contract.md +19 -13
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +142 -26
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +722 -23
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +348 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +123 -0
- package/dist/knowledge/skills/config-app-shell/SKILL.md +74 -11
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +85 -19
- package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +70 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +43 -3
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
- package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
- package/dist/knowledge/skills/config-design-system/references/surface-policy-authoring.md +19 -10
- package/dist/knowledge/skills/config-navigation/SKILL.md +85 -2
- package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +2 -2
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +172 -0
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +146 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +141 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +86 -9
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +199 -0
- package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +179 -0
- package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +493 -0
- package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +153 -0
- package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +242 -0
- package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +161 -0
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +93 -12
- package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +785 -0
- package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +172 -0
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +261 -9
- package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +9 -0
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +58 -3
- package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +151 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-auth-methods-api.md +579 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +8 -2
- package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +96 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +316 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-registration-config-api.md +221 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +121 -0
- package/dist/knowledge/skills/config-saas-backend/references/managed-startup-configuration.md +46 -0
- package/dist/knowledge/skills/configure-billing/SKILL.md +27 -22
- package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +27 -15
- package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +41 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +36 -17
- package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +30 -28
- package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +169 -0
- package/dist/knowledge/skills/configure-billing/references/framework-billing-resolution-failure-api.md +44 -11
- package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +187 -0
- package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +76 -0
- package/dist/knowledge/skills/configure-coding-agent/SKILL.md +280 -0
- package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +168 -0
- package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +504 -0
- package/dist/knowledge/skills/email-add-template/SKILL.md +41 -69
- package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +15 -7
- package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +120 -0
- package/dist/knowledge/skills/engine-component-registration/SKILL.md +19 -12
- package/dist/knowledge/skills/engine-product-definitions/SKILL.md +54 -31
- package/dist/knowledge/skills/engine-product-definitions/references/connected-feature-workflow.md +130 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-engine-product-definitions-api.md +25 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-feature-builders-api.md +215 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +78 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +33 -24
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +121 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -8
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +5 -4
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +46 -9
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +34 -7
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +151 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +6 -10
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +54 -5
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +75 -21
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +258 -0
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +480 -0
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +3983 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +211 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +165 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-elements-api.md +381 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-trigger-api.md +57 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-view-api.md +89 -0
- package/dist/knowledge/skills/i18n-label-generation/SKILL.md +13 -1
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +14 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +14 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +3 -1
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +14 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +237 -37
- package/dist/knowledge/skills/infra-environment-config/references/framework-application-database-api.md +5 -2
- package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +174 -21
- package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +206 -14
- package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +95 -0
- package/dist/knowledge/skills/journey-approve/SKILL.md +28 -8
- package/dist/knowledge/skills/journey-approve/references/specification-family-map.md +88 -0
- package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +37 -2
- package/dist/knowledge/skills/journey-next/SKILL.md +41 -1
- package/dist/knowledge/skills/journey-report/SKILL.md +16 -3
- package/dist/knowledge/skills/journey-run/SKILL.md +92 -7
- package/dist/knowledge/skills/journey-run/references/expert-personas-and-deliberations.md +46 -0
- package/dist/knowledge/skills/journey-run/references/framework-playbook-approval-policy.md +108 -0
- package/dist/knowledge/skills/journey-status/SKILL.md +14 -4
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +153 -46
- package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +119 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/initialization-recovery-recipe.md +7 -4
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +253 -33
- package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +1 -1
- package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
- package/dist/knowledge/skills/market-alternatives/SKILL.md +1 -1
- package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +12 -9
- package/dist/knowledge/skills/market-channels/SKILL.md +3 -3
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +226 -14
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +226 -14
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +56 -9
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +32 -9
- package/dist/knowledge/skills/market-icp/SKILL.md +2 -2
- package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +3 -3
- package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -2
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +17 -2
- package/dist/knowledge/skills/market-persona/SKILL.md +2 -2
- package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +2 -2
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -0
- package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +15 -0
- package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +1 -1
- package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +1 -1
- package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +198 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-celebration-overlay-contract.md +51 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-celebration-api.md +79 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-definition-api.md +220 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-progression-tracker-api.md +86 -0
- package/dist/knowledge/skills/minion-authoring/SKILL.md +140 -0
- package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +84 -0
- package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +91 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +38 -3
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +211 -14
- package/dist/knowledge/skills/module-registration/SKILL.md +50 -33
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +50 -1
- package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +142 -0
- package/dist/knowledge/skills/module-registration/references/registry-files.md +14 -5
- package/dist/knowledge/skills/module-relationships/SKILL.md +62 -0
- package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +26 -5
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +279 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +80 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +55 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-convention-api.md +48 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +33 -6
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-file-provider-constraints-api.md +99 -47
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +241 -9
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +196 -0
- package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +50 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +80 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +71 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +58 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +275 -0
- package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +64 -11
- package/dist/knowledge/skills/rate-limit-authoring/references/fixed-window-and-environment-multiplier.md +27 -0
- package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +19 -6
- package/dist/knowledge/skills/resource-add-field/SKILL.md +12 -5
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +373 -23
- package/dist/knowledge/skills/resource-add-module/SKILL.md +116 -265
- package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +133 -0
- package/dist/knowledge/skills/resource-add-module/references/framework-new-module-wiring-api.md +25 -0
- package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +12 -12
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +26 -3
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +122 -4
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +25 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +93 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +136 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +85 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +133 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +141 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-step-up-api.md +126 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +859 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +122 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +124 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +97 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +457 -15
- package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +197 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +162 -46
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +452 -0
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +5 -0
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +327 -11
- package/dist/knowledge/skills/resource-custom-view/references/framework-user-facing-error-message-api.md +50 -0
- package/dist/knowledge/skills/resource-external-data/SKILL.md +228 -15
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +54 -7
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +87 -113
- package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +13 -8
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +69 -26
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +246 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +7 -6
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +5 -3
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +43 -48
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +96 -14
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +47 -15
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +6 -2
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +32 -2
- package/dist/knowledge/skills/resource-schema-authoring/examples/basic-resource-schema.example.md +2 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +17 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +75 -4
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +182 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +245 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +35 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +46 -12
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +480 -15
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +67 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +74 -14
- package/dist/knowledge/skills/resource-schema-authoring/references/polymorphic-per-scope-resources.md +28 -5
- package/dist/knowledge/skills/resource-schema-authoring/references/schema-variants-and-discriminators.md +25 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +34 -0
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +236 -18
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +54 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +35 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +327 -11
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +140 -4
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +155 -5
- package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +165 -0
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +9 -1
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +4 -0
- package/dist/knowledge/skills/seeding-operations/SKILL.md +33 -29
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +13 -5
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-cron-scheduler.md +67 -74
- package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +97 -24
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +205 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +205 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +229 -0
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +38 -3
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +211 -14
- package/dist/knowledge/skills/spec-component-update/SKILL.md +30 -11
- package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +10 -0
- package/dist/knowledge/skills/spec-feature-update/SKILL.md +47 -9
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +3 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +32 -5
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +30 -0
- package/dist/knowledge/skills/views-add-composite-view/SKILL.md +1 -0
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +13 -2
- package/dist/knowledge/skills/views-add-custom-view/references/framework-view-scope-and-full-custom-api.md +24 -0
- package/dist/knowledge/skills/views-app-level/SKILL.md +1 -0
- package/dist/knowledge/skills/views-app-level/references/framework-view-scope-and-full-custom-api.md +24 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +64 -0
- package/dist/knowledge/skills/views-execution-authoring/SKILL.md +3 -0
- package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +3 -3
- package/dist/knowledge/skills/views-execution-authoring/references/framework-user-facing-error-message-api.md +50 -0
- package/dist/knowledge/skills/website-anonymous-session/SKILL.md +43 -7
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +21 -1
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +21 -0
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +41 -1
- package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +735 -211
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +54 -7
- package/dist/knowledge/skills/website-layout-overrides/SKILL.md +67 -1
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -0
- package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +19 -5
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +94 -7
- package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +126 -0
- package/dist/knowledge/skills/website-section-contact/SKILL.md +96 -146
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-cta/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-faq/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-hero/SKILL.md +37 -26
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +14 -1
- package/dist/knowledge/skills/worker-authoring/SKILL.md +164 -0
- package/dist/knowledge/skills/worker-authoring/examples/worker-route.example.md +98 -0
- package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +65 -0
- package/dist/knowledge/topic-index.json +5335 -1010
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/knowledge/references/example.provider.contribution.backend-billing.md +0 -12
- package/dist/knowledge/skills/configure-billing/references/example-provider-contribution-and-backend-config.md +0 -48
- /package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/structured-artifact-action.json +0 -0
|
@@ -1,40 +1,739 @@
|
|
|
1
1
|
# What happens to a candidate after you draft it
|
|
2
2
|
|
|
3
|
-
Read this to understand where your work stops
|
|
3
|
+
Read this to understand where your work stops, and what comes after it. The stages after a draft are
|
|
4
|
+
SEPARATE, and collapsing any two of them is how a draft comes to read as a published legal statement.
|
|
4
5
|
|
|
5
|
-
##
|
|
6
|
+
## Five stages, and you do only the first
|
|
6
7
|
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
8
|
+
| stage | what it is | where it lives | who does it |
|
|
9
|
+
|---|---|---|---|
|
|
10
|
+
| 1. accepted source | your candidate, committed | `./specifications/src/compliance-document-candidates/` | you draft it; a human commit accepts it |
|
|
11
|
+
| 2. recorded release | one candidate bound to one declared variant, an effective date and the release policy, with its text captured | decisions in `./specifications/src/document-releases/compositions.ts`, records in `recorded-releases.generated.ts` | a human decides; `wildo config document-releases` composes and records |
|
|
12
|
+
| 3. approval | a recorded decision on that release | the release's `approvalDecisions` | a human — never the drafter |
|
|
13
|
+
| 4. runtime projection | the browser-safe slice the running application reads | `./backend-api/src/governed-document-releases.generated.ts` | `wildo config document-releases` |
|
|
14
|
+
| 5. public serving | a page a person reads | `compliance.publicDocuments`, written into the same generated module | `wildo config document-releases` writes it; the public pages read it |
|
|
15
|
+
|
|
16
|
+
A stage existing does not mean the next one has happened. A committed candidate has no release; a
|
|
17
|
+
release may have no approval; an approved release is not thereby served to anyone.
|
|
18
|
+
|
|
19
|
+
## 1. A candidate is accepted by being COMMITTED
|
|
20
|
+
|
|
21
|
+
You produce a file. A human reads it, edits it if they disagree, and commits it. That commit accepts
|
|
22
|
+
the SOURCE — it says "this is the draft we hold". It is not an approval of the document for release;
|
|
23
|
+
that is stage 3, and it is recorded on the release, not on your draft.
|
|
10
24
|
|
|
11
25
|
Independence and segregation of duties, where an operator's programme requires them, are enforced by
|
|
12
26
|
the forge: branch protection, required reviewers, a signed history. Never by anything you write into
|
|
13
27
|
the document, and never by a field claiming a review happened.
|
|
14
28
|
|
|
15
|
-
##
|
|
29
|
+
## 2. A release is COMPOSED, and nothing composes it for you
|
|
30
|
+
|
|
31
|
+
`composeGovernedDocumentRelease` (from `@wildo-ai/saas-specifications/assurance`) turns a candidate
|
|
32
|
+
into a release. Most of what a release carries — the document's class, who it addresses, which
|
|
33
|
+
channels may carry it, which interactions a person may perform with it — is DERIVED from the accepted
|
|
34
|
+
document definition, so it is never restated by hand. What a human decides is narrow: which draft,
|
|
35
|
+
which declared locale × jurisdiction variant, when it takes effect, and which release-policy lane
|
|
36
|
+
governs it.
|
|
37
|
+
|
|
38
|
+
The composer returns `{ release, issues, advisories }`, and the two lists mean different things:
|
|
39
|
+
|
|
40
|
+
- an **issue** means the release would be FALSE — the candidate drafts a different document, the
|
|
41
|
+
variant is not one the application declared, the candidate's locale contradicts the variant, the
|
|
42
|
+
policy governs another requirement. No release is produced;
|
|
43
|
+
- an **advisory** means the release is TRUE and the workflow is unfinished — `NOT_APPROVED`, or
|
|
44
|
+
`POLICY_IS_DRAFT_ONLY`. The release IS produced, and it carries the advisory with it.
|
|
45
|
+
|
|
46
|
+
No host, companion or playbook composes a release automatically. A human declares the DECISION in
|
|
47
|
+
`./specifications/src/document-releases/compositions.ts` (exported as `documentReleaseCompositions`),
|
|
48
|
+
and `wildo config document-releases` composes each decision not yet recorded and appends the
|
|
49
|
+
finished release — text included — to `recorded-releases.generated.ts`, which the release set is built
|
|
50
|
+
from. A recorded release is never recomposed: editing your draft afterwards changes no release, and
|
|
51
|
+
publishing new text is a new decision with the next `releaseVersion`.
|
|
52
|
+
|
|
53
|
+
An application with no decisions holds no releases, which is a valid state and the usual one early on
|
|
54
|
+
— it is not something to fix from inside a drafting task.
|
|
55
|
+
|
|
56
|
+
## 3. Approval is a RECORDED decision, and it is not yours to make
|
|
57
|
+
|
|
58
|
+
A release carries `approvalState` (`APPROVED` or `UNAPPROVED`) and `approvalDecisions`. A release
|
|
59
|
+
composed with no decisions is `UNAPPROVED`, and it exists anyway: an artifact that says "nobody has
|
|
60
|
+
approved this yet" is honest, while refusing to hold one until someone signs would put a compliance
|
|
61
|
+
workflow in front of the application's own build.
|
|
62
|
+
|
|
63
|
+
So an approval record DOES exist — on the release. What never exists is a decision nobody took. Do not
|
|
64
|
+
add an approval decision to reach `APPROVED`, do not describe an unapproved release as approved, and
|
|
65
|
+
do not treat `UNAPPROVED` as a blocker to report. It is a state, carried where every reader can see it.
|
|
66
|
+
|
|
67
|
+
## 4. The running application reads a PROJECTION of the releases
|
|
68
|
+
|
|
69
|
+
The specifications package is not a runtime dependency of the application, so a composed release does
|
|
70
|
+
not reach the running backend by itself. `wildo config document-releases` reads the release set and
|
|
71
|
+
writes `./backend-api/src/governed-document-releases.generated.ts`, which
|
|
72
|
+
`./backend-api/src/saas-config.backend.ts` imports into `compliance.governedDocumentReleases`.
|
|
73
|
+
|
|
74
|
+
The projection keeps only what the consent surface and the interaction record read. It deliberately
|
|
75
|
+
drops `governanceScope` and `approvalDecisions`, because this value reaches an unauthenticated
|
|
76
|
+
browser. Commit the generated file beside the release change that produced it:
|
|
77
|
+
`wildo config document-releases --check`, and `wildo config validate --domain document-releases` in the
|
|
78
|
+
application's validation workflow, fail when it is stale. The validate domain also fails when the module
|
|
79
|
+
is current but `saas-config.backend.ts` does not carry it. An application that adopts governed
|
|
80
|
+
documents later has no release wiring until it adds those two assignments, and without them its public
|
|
81
|
+
pages would stay empty behind a green check.
|
|
82
|
+
|
|
83
|
+
What the projection drives today:
|
|
84
|
+
|
|
85
|
+
- registration renders an acceptance control when a release permitting `CONTRACT_ACCEPTED` is in
|
|
86
|
+
force. WHICH control is the application's own choice — see the next section;
|
|
87
|
+
- the backend records a `GOVERNED_DOCUMENT_INTERACTION_RECORDED` audit event naming the exact release
|
|
88
|
+
and version the person accepted. An unapproved release is RECORDED with a `RELEASE_NOT_APPROVED`
|
|
89
|
+
advisory, never silently refused — what the person saw is a fact, whatever its approval state.
|
|
90
|
+
|
|
91
|
+
### How registration ASKS is declared, and the default is the strongest shape
|
|
92
|
+
|
|
93
|
+
`compliance.governedDocumentAcceptanceMode` picks one of three shapes. You set it in
|
|
94
|
+
`./backend-api/src/saas-config.backend.ts`, in the same `compliance` block that carries
|
|
95
|
+
`governedDocumentReleases` and `publicDocuments` — NOT in `wildo.saas.config.ts`, which has no
|
|
96
|
+
compliance block and would accept the line without ever reading it. They
|
|
97
|
+
are the ones online contract formation actually distinguishes, and they differ in how strong a notice
|
|
98
|
+
the operator wants to give — a liability posture, so it is the operator's to declare and not
|
|
99
|
+
something a mechanism should guess:
|
|
100
|
+
|
|
101
|
+
| mode | what the registrant sees | what is withheld |
|
|
102
|
+
|---|---|---|
|
|
103
|
+
| `IMPLIED_BY_REGISTERING` | a notice above the submit control — "by creating an account, you agree to…" | nothing; submitting IS the act of assent |
|
|
104
|
+
| `EXPLICIT_CHECKBOX` | an unticked box | the submit control, until it is ticked |
|
|
105
|
+
| `EXPLICIT_AFTER_READING` | the document itself, in a pane per served document, plus the box | the BOX, until every pane has been scrolled to its end |
|
|
106
|
+
|
|
107
|
+
Four things to know before choosing one:
|
|
108
|
+
|
|
109
|
+
- **`EXPLICIT_CHECKBOX` is the default**, and an application that declares nothing gets it. That is
|
|
110
|
+
deliberate: a default is what every application receives, so any other choice would move applications
|
|
111
|
+
to a weaker acceptance posture on an upgrade without anyone deciding to.
|
|
112
|
+
- **Every mode records the same thing.** The accepted release ids travel with the registration in all
|
|
113
|
+
three, including the implied one — a notice telling somebody they agreed, beside a request that
|
|
114
|
+
records nothing, is worse than not asking at all.
|
|
115
|
+
- **No box is ever pre-ticked**, in any mode. A pre-ticked box is not an affirmative act, so it removes
|
|
116
|
+
the one property the explicit modes exist to provide.
|
|
117
|
+
- **`EXPLICIT_AFTER_READING` needs the documents SERVED.** The pane reads `compliance.publicDocuments`
|
|
118
|
+
(stage 5 below), so a release whose document the application does not publish has nothing to show.
|
|
119
|
+
With nothing to show the mode degrades to `EXPLICIT_CHECKBOX` rather than withholding the box
|
|
120
|
+
forever: the affirmative act survives and only the claim that the text was presented is dropped,
|
|
121
|
+
which is honest, because no text was presented. If you want the reading gate, publish the document.
|
|
122
|
+
|
|
123
|
+
The gate asserts that the text was PLACED IN FRONT of the person and that the act came after — never
|
|
124
|
+
that they read it, which no mechanism can establish.
|
|
125
|
+
|
|
126
|
+
The vocabulary itself, with each member's enforceability position on the member:
|
|
127
|
+
|
|
128
|
+
## Import Origins
|
|
129
|
+
|
|
130
|
+
- `@wildo-ai/saas-models`
|
|
131
|
+
|
|
132
|
+
## Source Excerpts
|
|
133
|
+
|
|
134
|
+
### Origin Package: `@wildo-ai/saas-models`
|
|
135
|
+
|
|
136
|
+
```typescript
|
|
137
|
+
/**
|
|
138
|
+
* HOW an application asks a registrant to accept the documents it requires accepting — the three
|
|
139
|
+
* shapes courts actually distinguish, declared once per application (#1258).
|
|
140
|
+
*
|
|
141
|
+
* Declared on `compliance.governedDocumentAcceptanceMode` in the application's own
|
|
142
|
+
* `backend-api/src/saas-config.backend.ts`, beside `governedDocumentReleases` and `publicDocuments`.
|
|
143
|
+
*
|
|
144
|
+
* It is a RENDERING posture, not a server-side gate. The backend records whichever accepted release
|
|
145
|
+
* ids a registration carries and does not know which mode produced them, so a client that does not
|
|
146
|
+
* use the form is bound by none of the three. That is the honest scope: what the mode decides is how
|
|
147
|
+
* strong a notice a person is given and what the form withholds until they act — the things a
|
|
148
|
+
* registration screen can actually control.
|
|
149
|
+
*
|
|
150
|
+
* ## Why this is a declared CHOICE rather than one shipped behaviour
|
|
151
|
+
*
|
|
152
|
+
* Registration shipped with exactly one shape — an unticked box gating the submit button — and no
|
|
153
|
+
* way to ask for another. That is the strongest of the three and it is the right DEFAULT, but it is
|
|
154
|
+
* not the right answer for every application: a product whose terms are a one-paragraph acceptable-use
|
|
155
|
+
* statement and a product whose terms carry an arbitration clause are not asking the same thing of the
|
|
156
|
+
* same person, and the framework should let each say which it is asking.
|
|
157
|
+
*
|
|
158
|
+
* ## The enforceability ladder, which is what the members are ordered by
|
|
159
|
+
*
|
|
160
|
+
* Enforceability turns on whether the person had REASONABLE NOTICE of the terms and took an action
|
|
161
|
+
* MANIFESTING ASSENT to them. Clickwrap — an affirmative act aimed at the terms themselves — is the
|
|
162
|
+
* shape courts uphold most consistently; sign-in-wrap, where the act is the registration and the
|
|
163
|
+
* notice sits beside it, is upheld when the notice is conspicuous and fails when it is buried;
|
|
164
|
+
* browsewrap, where nothing but a footer link exists, is the shape that routinely fails. This
|
|
165
|
+
* vocabulary offers the first two and does NOT offer the third, because an application that asks for
|
|
166
|
+
* nothing is already representable by declaring no release that permits `CONTRACT_ACCEPTED`.
|
|
167
|
+
*
|
|
168
|
+
* (Drawn from the settled shape of US and EU practice on online contract formation, not from a single
|
|
169
|
+
* cited authority. Not legal advice — an operator's counsel decides which their terms warrant.)
|
|
170
|
+
*
|
|
171
|
+
* ## Every member DOES something, deliberately
|
|
172
|
+
*
|
|
173
|
+
* Each one changes what the registration form renders and what it refuses. A member that only named a
|
|
174
|
+
* posture without changing behaviour is the defect removed from this lane one commit earlier, when a
|
|
175
|
+
* stored privacy-level field was deleted for meaning nothing at any call site.
|
|
176
|
+
*/
|
|
177
|
+
export enum GovernedDocumentAcceptanceMode {
|
|
178
|
+
/**
|
|
179
|
+
* SIGN-IN-WRAP — "by registering you agree to our terms and privacy policy", beside the button.
|
|
180
|
+
*
|
|
181
|
+
* No checkbox and no separate act: submitting the registration IS the act of assent, so the
|
|
182
|
+
* accepted release ids still travel with it and the interaction is still recorded. What changes is
|
|
183
|
+
* that nothing is withheld — the button is available from the first keystroke.
|
|
184
|
+
*
|
|
185
|
+
* The notice is rendered immediately above the submit control rather than in a footer, because
|
|
186
|
+
* conspicuousness is the whole of what distinguishes this from the browsewrap shape that fails.
|
|
187
|
+
*/
|
|
188
|
+
IMPLIED_BY_REGISTERING = "IMPLIED_BY_REGISTERING",
|
|
189
|
+
/**
|
|
190
|
+
* CLICKWRAP — an unticked box the person ticks, with the submit control unavailable until they do.
|
|
191
|
+
*
|
|
192
|
+
* The DEFAULT, and the framework default may not silently weaken: an application that declared
|
|
193
|
+
* nothing shipped this behaviour before the vocabulary existed, and must keep shipping it.
|
|
194
|
+
*
|
|
195
|
+
* The box is never pre-ticked. A pre-ticked box is not an affirmative act, so it undermines the one
|
|
196
|
+
* property this mode exists to provide — the same reason the consent gate's own optional purposes
|
|
197
|
+
* start unticked.
|
|
198
|
+
*/
|
|
199
|
+
EXPLICIT_CHECKBOX = "EXPLICIT_CHECKBOX",
|
|
200
|
+
/**
|
|
201
|
+
* CLICKWRAP WITH A READING GATE — the document is shown, and the box cannot be ticked until the
|
|
202
|
+
* reader has scrolled to the end of it.
|
|
203
|
+
*
|
|
204
|
+
* The strongest available notice: the terms are not merely linked, they are placed in front of the
|
|
205
|
+
* person and the affirmative act is unavailable until they have passed over all of them.
|
|
206
|
+
*
|
|
207
|
+
* Two things it deliberately does NOT claim. It does not claim the person READ the document — no
|
|
208
|
+
* mechanism can — only that the text was presented in full and the act came after. And it does not
|
|
209
|
+
* replace the public document page: the pane shows the same content that page serves, and links to
|
|
210
|
+
* it, because the page is where the document is rendered with its own typography.
|
|
211
|
+
*/
|
|
212
|
+
EXPLICIT_AFTER_READING = "EXPLICIT_AFTER_READING",
|
|
213
|
+
}
|
|
214
|
+
|
|
215
|
+
/**
|
|
216
|
+
* Does this mode require a SEPARATE affirmative act before the registration may be submitted?
|
|
217
|
+
*
|
|
218
|
+
* Two readers, one answer: the form disables its submit control on it, and the same form decides on
|
|
219
|
+
* it whether the accepted release ids travel with the request. Those had to agree — a submit the
|
|
220
|
+
* person could press without the ids being sent records nothing while reporting success — so the
|
|
221
|
+
* predicate is named once here rather than spelled twice at the two call sites.
|
|
222
|
+
*
|
|
223
|
+
* Written as "anything but implied" deliberately: a fourth mode added tomorrow is treated as needing
|
|
224
|
+
* the act until somebody says otherwise, which is the direction that fails safe. The inverse spelling
|
|
225
|
+
* ({@link GovernedDocumentAcceptanceMode.EXPLICIT_CHECKBOX} or `EXPLICIT_AFTER_READING`) would let a
|
|
226
|
+
* new member fall through to "registering is enough" silently.
|
|
227
|
+
*/
|
|
228
|
+
export const governedDocumentAcceptanceRequiresExplicitAct = (mode: GovernedDocumentAcceptanceMode): boolean =>
|
|
229
|
+
mode !== GovernedDocumentAcceptanceMode.IMPLIED_BY_REGISTERING;
|
|
230
|
+
|
|
231
|
+
/**
|
|
232
|
+
* Must the document be placed in front of the reader, and the affirmative act withheld until they
|
|
233
|
+
* have passed over all of it?
|
|
234
|
+
*
|
|
235
|
+
* Named rather than compared inline for the same reason as its sibling, and spelled the other way
|
|
236
|
+
* round for the same fail-safe reason read in the other direction: a new mode does NOT acquire a
|
|
237
|
+
* reading gate nobody asked for.
|
|
238
|
+
*/
|
|
239
|
+
export const governedDocumentAcceptanceRequiresReading = (mode: GovernedDocumentAcceptanceMode): boolean =>
|
|
240
|
+
mode === GovernedDocumentAcceptanceMode.EXPLICIT_AFTER_READING;
|
|
241
|
+
```
|
|
242
|
+
|
|
243
|
+
One thing the modes do NOT do: bind a client that is not the form. The backend records whichever
|
|
244
|
+
accepted release ids a registration carries and does not know which mode produced them, so the mode
|
|
245
|
+
decides how strong a notice a person is given and what the form withholds — not what the API accepts.
|
|
246
|
+
|
|
247
|
+
## 5. Public serving is a READ over the same generated module
|
|
248
|
+
|
|
249
|
+
The public privacy-notice and service-terms pages read `compliance.publicDocuments`, which
|
|
250
|
+
`wildo config document-releases` also writes, and select what to show with
|
|
251
|
+
`resolveInForcePublicDocument` (from `@wildo-ai/saas-models`):
|
|
252
|
+
|
|
253
|
+
- a **release** in force, published to the public web, with the text it carries — release version and
|
|
254
|
+
effective date shown;
|
|
255
|
+
- otherwise, for a public document the application has drafted and **never released**, its latest
|
|
256
|
+
draft — shown with a notice that it is a draft, which may change and has not taken effect. A
|
|
257
|
+
document that has a release, even one not yet in force, never falls back to its draft.
|
|
16
258
|
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
259
|
+
Either way, a clause your draft marks as not established is shown with a "not yet established" note
|
|
260
|
+
and your `needs` text. That is why `needs` must be written for the reader: it is published. `closedBy`,
|
|
261
|
+
fact refs and claim guards are not.
|
|
20
262
|
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
263
|
+
The gate point is one member of your application's configuration, `compliance.governedDocumentApprovalGate`
|
|
264
|
+
(`GovernedDocumentApprovalGate` from `@wildo-ai/saas-models`). It is `UNARMED` by default while the
|
|
265
|
+
application is being built, and must be `ARMED` once the application faces real users. Armed, nothing
|
|
266
|
+
unapproved reaches a person on any surface: the `/privacy` and `/terms` pages withhold unapproved
|
|
267
|
+
releases and drafts, and registration and the first-session acceptance gate stop asking anyone to
|
|
268
|
+
accept an unapproved release. It is one switch on purpose, so the page cannot be armed while sign-up
|
|
269
|
+
keeps asking for the same terms.
|
|
270
|
+
|
|
271
|
+
Being shown on a page does not make a document approved, released or effective. Do not describe it as
|
|
272
|
+
any of those because it appears at a URL.
|
|
273
|
+
|
|
274
|
+
## The machine that used to be described here
|
|
275
|
+
|
|
276
|
+
A previous version of this page described an immutable release sequence with deployment bundles,
|
|
277
|
+
CLI-written sync receipts, backend boot revalidation, content and delivery digests, and signed
|
|
278
|
+
deployment observations bound to a rotated key window. That machine was removed on 2026-08-28. It had
|
|
279
|
+
never once run, and every read path was built on the seal.
|
|
27
280
|
|
|
28
281
|
Why it went, in one sentence: a digest chain cannot merge, so two branches that publish different
|
|
29
|
-
content produce a merged tree whose digests belong to neither, while git and the forge already
|
|
30
|
-
|
|
282
|
+
content produce a merged tree whose digests belong to neither, while git and the forge already provide
|
|
283
|
+
what the machine was protecting — per commit, mergeably, to a reviewer reading a diff.
|
|
284
|
+
|
|
285
|
+
A later version of this page then said there was no release model and no approval record at all. That
|
|
286
|
+
was wrong once releases existed, and it is why the five stages above are spelled out separately.
|
|
31
287
|
|
|
32
288
|
## What this means for your draft
|
|
33
289
|
|
|
34
|
-
- **Do not describe your draft as approved, released, published or effective.** None of those
|
|
35
|
-
|
|
290
|
+
- **Do not describe your draft as approved, released, published or effective.** None of those is a
|
|
291
|
+
property of a draft, and a document asserting them is wrong the moment it lands.
|
|
292
|
+
- **Do not author a release, an approval decision or an effective date inside the candidate.** Each
|
|
293
|
+
belongs to a later stage and a different author.
|
|
36
294
|
- **Do not add fields carrying a digest, a proof, a receipt or an attestation.** They do not exist in
|
|
37
|
-
the contract
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
295
|
+
the contract, and re-inventing one inside document content is the same mistake one layer up.
|
|
296
|
+
- **Do state effective dates as unestablished** in the document text until the operator sets them on
|
|
297
|
+
a release. An effective date is a decision, not a property of the draft.
|
|
298
|
+
|
|
299
|
+
## Source contracts
|
|
300
|
+
|
|
301
|
+
The release composer and the in-force read:
|
|
302
|
+
|
|
303
|
+
## Import Origins
|
|
304
|
+
|
|
305
|
+
- `@wildo-ai/saas-specifications`
|
|
306
|
+
|
|
307
|
+
## Source Excerpts
|
|
308
|
+
|
|
309
|
+
### Origin Package: `@wildo-ai/saas-specifications`
|
|
310
|
+
|
|
311
|
+
```typescript
|
|
312
|
+
*
|
|
313
|
+
* Turning an APPROVED DRAFT into a RELEASE — the step whose absence meant a
|
|
314
|
+
* drafted governed document could never become a published one (issue #245).
|
|
315
|
+
*
|
|
316
|
+
* The lane could draft: an application holds a real
|
|
317
|
+
* `ComplianceDocumentCandidate` with its sections, clauses and prose. What it
|
|
318
|
+
* had no way to do was say *this draft, in this language, for these
|
|
319
|
+
* jurisdictions, is approved and takes effect on this date* — measured
|
|
320
|
+
* 2026-09-02 and re-measured 2026-09-11, `GovernedDocumentReleaseSchema`
|
|
321
|
+
* appeared in exactly two files, its own definition and its unit test, and
|
|
322
|
+
* nothing anywhere constructed one.
|
|
323
|
+
*
|
|
324
|
+
* **This is a composition, not a custody protocol, and the distinction is the
|
|
325
|
+
* whole design.** `0924c256` removed the previous publication lane — "a sealed
|
|
326
|
+
* machine that had never run" — and said what should replace it: *"A governed
|
|
327
|
+
* document is a file; publishing one is a commit. When an application has a
|
|
328
|
+
* document to serve, serving is rebuilt from files — a read, not a custody
|
|
329
|
+
* protocol."* So there is no bundle here, no digest, no content-addressed
|
|
330
|
+
* store and no byte-exact retrieval transport. A release is a record an
|
|
331
|
+
* application COMMITS, and {@link resolveEffectiveDocumentRelease} is the read.
|
|
332
|
+
*
|
|
333
|
+
* **Most of a release is DERIVED rather than authored**, which is the other
|
|
334
|
+
* half of the design. The accepted `AssuranceDocumentDefinition` already
|
|
335
|
+
* decides the document's class, who it addresses, which channels may carry it
|
|
336
|
+
* and which interactions it permits — so asking an author to restate them
|
|
337
|
+
* would invite five ways to disagree with the catalog, and the disagreement
|
|
338
|
+
* would be invisible. What is genuinely a human decision is the narrow part:
|
|
339
|
+
* which draft, which variant, which approval, and when it takes effect.
|
|
340
|
+
*/
|
|
341
|
+
export enum GovernedDocumentReleaseCompositionIssueKind {
|
|
342
|
+
/** The candidate drafts a different document from the one being released. */
|
|
343
|
+
CANDIDATE_DOCUMENT_MISMATCH = "CANDIDATE_DOCUMENT_MISMATCH",
|
|
344
|
+
/** The requested variant is not one the application declared it publishes in. */
|
|
345
|
+
VARIANT_NOT_PUBLISHED = "VARIANT_NOT_PUBLISHED",
|
|
346
|
+
/** The candidate states a locale or jurisdictions that contradict the variant being released. */
|
|
347
|
+
CANDIDATE_VARIANT_CONTRADICTION = "CANDIDATE_VARIANT_CONTRADICTION",
|
|
348
|
+
/** The governance subject is not one the document's definition governs. */
|
|
349
|
+
GOVERNANCE_SUBJECT_NOT_PERMITTED = "GOVERNANCE_SUBJECT_NOT_PERMITTED",
|
|
350
|
+
/** A release that replaces another must supersede the SAME document. */
|
|
351
|
+
REPLACES_DIFFERENT_DOCUMENT = "REPLACES_DIFFERENT_DOCUMENT",
|
|
352
|
+
/** The release policy consulted governs a different document from the one being released. */
|
|
353
|
+
RELEASE_POLICY_FOR_OTHER_REQUIREMENT = "RELEASE_POLICY_FOR_OTHER_REQUIREMENT",
|
|
354
|
+
/** The composed record does not satisfy `GovernedDocumentReleaseSchema`. */
|
|
355
|
+
RELEASE_RECORD_INVALID = "RELEASE_RECORD_INVALID",
|
|
356
|
+
}
|
|
357
|
+
|
|
358
|
+
export interface GovernedDocumentReleaseCompositionIssue {
|
|
359
|
+
readonly kind: GovernedDocumentReleaseCompositionIssueKind;
|
|
360
|
+
readonly message: string;
|
|
361
|
+
}
|
|
362
|
+
|
|
363
|
+
/**
|
|
364
|
+
* What is TRUE about a composed release that a human must eventually act on — never a reason to
|
|
365
|
+
* refuse composing it.
|
|
366
|
+
*
|
|
367
|
+
* The split from {@link GovernedDocumentReleaseCompositionIssueKind} is the design, not a severity
|
|
368
|
+
* scale. An ISSUE means the record would be FALSE: it names a document the candidate does not draft,
|
|
369
|
+
* or publishes an `en-GB` draft as `fr-FR`. An ADVISORY means the record is TRUE and the workflow is
|
|
370
|
+
* not finished — nobody has approved it yet, or the application's own policy keeps this document in
|
|
371
|
+
* the draft-only lane.
|
|
372
|
+
*
|
|
373
|
+
* Wildo is agent-first, so the second kind may never stop the mechanism. A compliance workflow
|
|
374
|
+
* standing in front of application creation is exactly the shape this framework refuses: the system
|
|
375
|
+
* must WORK first, and
|
|
376
|
+
* restrictions arrive later as judge-style guards rather than ceremony wired into the mechanism.
|
|
377
|
+
*/
|
|
378
|
+
export enum GovernedDocumentReleaseAdvisoryKind {
|
|
379
|
+
/** Composed without an approval decision. The release says so in `approvalState`. */
|
|
380
|
+
NOT_APPROVED = "NOT_APPROVED",
|
|
381
|
+
/**
|
|
382
|
+
* The application's accepted policy keeps this document in the DRAFT_ONLY lane.
|
|
383
|
+
*
|
|
384
|
+
* It refused composition until 2026-09-11, and that was the error this whole split corrects: a
|
|
385
|
+
* lane an application chose for its OWN document became a wall in front of its own build. The
|
|
386
|
+
* release is composed, marked UNAPPROVED, and the lane is reported — so the decision to serve it
|
|
387
|
+
* is taken where serving happens, which is Gate 3's to arm.
|
|
388
|
+
*/
|
|
389
|
+
POLICY_IS_DRAFT_ONLY = "POLICY_IS_DRAFT_ONLY",
|
|
390
|
+
}
|
|
391
|
+
|
|
392
|
+
export interface GovernedDocumentReleaseAdvisory {
|
|
393
|
+
readonly kind: GovernedDocumentReleaseAdvisoryKind;
|
|
394
|
+
readonly message: string;
|
|
395
|
+
}
|
|
396
|
+
|
|
397
|
+
/** What a human actually decides. Everything else on the record is derived from the accepted definition. */
|
|
398
|
+
export interface GovernedDocumentReleaseComposition {
|
|
399
|
+
/** The framework-accepted definition. Supplies class, audiences, channels and permitted interactions. */
|
|
400
|
+
readonly definition: AssuranceDocumentDefinition;
|
|
401
|
+
/** The approved draft whose content this release publishes. */
|
|
402
|
+
readonly candidate: ComplianceDocumentCandidate;
|
|
403
|
+
/** The exact locale x jurisdiction combination being published. */
|
|
404
|
+
readonly variant: AssuranceDocumentPublicationVariant;
|
|
405
|
+
/** Every variant the application declared it publishes in; the variant above must be one of them. */
|
|
406
|
+
readonly publishedVariants: readonly AssuranceDocumentPublicationVariant[];
|
|
407
|
+
/**
|
|
408
|
+
* The application's accepted release-policy selection for THIS document's requirement.
|
|
409
|
+
*
|
|
410
|
+
* REQUIRED, because releasing is the act that policy exists to govern. `DRAFT_ONLY` means the
|
|
411
|
+
* document "may be generated and retained, but cannot be released or published" — a sentence with
|
|
412
|
+
* no effect unless something refuses, and the only place that can refuse is here. An optional
|
|
413
|
+
* input would have made the strictest lane the easiest one to skip: omit the field, get a release.
|
|
414
|
+
*
|
|
415
|
+
* The other two lanes do not branch here. Whether an operator attestation or a qualified review
|
|
416
|
+
* actually happened is recorded in `approvalDecisions`, and the selection's own schema already
|
|
417
|
+
* requires an attested lane to carry its explicit limitations.
|
|
418
|
+
*/
|
|
419
|
+
readonly releasePolicy: ApplicationDocumentReleasePolicySelectionV1;
|
|
420
|
+
/** The requirement the policy must govern — the join is by requirement, never by document ref. */
|
|
421
|
+
readonly requirement: { readonly requirementRef: string; readonly requirementVersion: number };
|
|
422
|
+
readonly identity: GovernedDocumentReleaseIdentity;
|
|
423
|
+
readonly governanceScope: GovernedDocumentRelease["governanceScope"];
|
|
424
|
+
/**
|
|
425
|
+
* The approvals retained for this release, if any yet.
|
|
426
|
+
*
|
|
427
|
+
* EMPTY is a first-class answer, not a missing input: it composes an UNAPPROVED release and an
|
|
428
|
+
* advisory saying so. Requiring one here would mean an application could only hold a release by
|
|
429
|
+
* forging an approval identity, which is worse than having none.
|
|
430
|
+
*/
|
|
431
|
+
readonly approvalDecisions: readonly GovernedDocumentApprovalDecisionIdentity[];
|
|
432
|
+
readonly issuedAt: string;
|
|
433
|
+
readonly effectiveAt: string;
|
|
434
|
+
readonly expiresAt?: string;
|
|
435
|
+
/**
|
|
436
|
+
* Superseding another release, stated ONCE as the materiality decision.
|
|
437
|
+
*
|
|
438
|
+
* The release record carries both `replacesRelease` and `materialityDecision`, and its schema
|
|
439
|
+
* requires them to be present together AND to name the same previous release. So the caller gives
|
|
440
|
+
* the decision and `replacesRelease` is DERIVED from `previousRelease` — two fields that must
|
|
441
|
+
* agree are not two decisions, and asking for both would only create a way to disagree.
|
|
442
|
+
*
|
|
443
|
+
* The decision itself is the governance question a replacement owes: did the change matter enough
|
|
444
|
+
* that the audience must meet the document again? `requiredInteractionKinds` is where that lands.
|
|
445
|
+
*/
|
|
446
|
+
readonly supersedes?: GovernedDocumentMaterialityDecisionIdentity;
|
|
447
|
+
}
|
|
448
|
+
const sorted = (values: readonly string[]): string[] => [...values].sort();
|
|
449
|
+
const sameSet = (left: readonly string[], right: readonly string[]): boolean =>
|
|
450
|
+
left.length === right.length && sorted(left).every((value, index) => value === sorted(right)[index]);
|
|
451
|
+
|
|
452
|
+
/**
|
|
453
|
+
* Compose one release, or report why the parts do not agree.
|
|
454
|
+
*
|
|
455
|
+
* Returns issues rather than throwing, following the `_core` validator convention: a caller
|
|
456
|
+
* assembling several releases wants all the disagreements at once, not the first one.
|
|
457
|
+
*/
|
|
458
|
+
export function composeGovernedDocumentRelease(
|
|
459
|
+
composition: GovernedDocumentReleaseComposition,
|
|
460
|
+
): {
|
|
461
|
+
readonly release: GovernedDocumentRelease | undefined;
|
|
462
|
+
readonly issues: readonly GovernedDocumentReleaseCompositionIssue[];
|
|
463
|
+
readonly advisories: readonly GovernedDocumentReleaseAdvisory[];
|
|
464
|
+
} {
|
|
465
|
+
const issues: GovernedDocumentReleaseCompositionIssue[] = [];
|
|
466
|
+
const advisories: GovernedDocumentReleaseAdvisory[] = [];
|
|
467
|
+
const { candidate, variant, identity, definition } = composition;
|
|
468
|
+
|
|
469
|
+
if (candidate.documentRef !== identity.document.documentRef) {
|
|
470
|
+
issues.push({
|
|
471
|
+
kind: GovernedDocumentReleaseCompositionIssueKind.CANDIDATE_DOCUMENT_MISMATCH,
|
|
472
|
+
message: `candidate drafts "${candidate.documentRef}" but the release identifies "${identity.document.documentRef}"`,
|
|
473
|
+
});
|
|
474
|
+
}
|
|
475
|
+
|
|
476
|
+
if (composition.releasePolicy.requirementRef !== composition.requirement.requirementRef
|
|
477
|
+
|| composition.releasePolicy.requirementVersion !== composition.requirement.requirementVersion) {
|
|
478
|
+
issues.push({
|
|
479
|
+
kind: GovernedDocumentReleaseCompositionIssueKind.RELEASE_POLICY_FOR_OTHER_REQUIREMENT,
|
|
480
|
+
message: `release policy governs "${composition.releasePolicy.requirementRef}@${composition.releasePolicy.requirementVersion}" `
|
|
481
|
+
+ `but this release is for "${composition.requirement.requirementRef}@${composition.requirement.requirementVersion}"`,
|
|
482
|
+
});
|
|
483
|
+
}
|
|
484
|
+
if (composition.releasePolicy.lane === ApplicationDocumentReleasePolicyLane.DRAFT_ONLY) {
|
|
485
|
+
advisories.push({
|
|
486
|
+
kind: GovernedDocumentReleaseAdvisoryKind.POLICY_IS_DRAFT_ONLY,
|
|
487
|
+
message: `the accepted release policy puts "${composition.requirement.requirementRef}" in the DRAFT_ONLY lane: compose and retain it, but nothing may serve it as published`,
|
|
488
|
+
});
|
|
489
|
+
}
|
|
490
|
+
|
|
491
|
+
const variantKey = assuranceDocumentPublicationVariantKey(variant);
|
|
492
|
+
if (!composition.publishedVariants.some((published) => assuranceDocumentPublicationVariantKey(published) === variantKey)) {
|
|
493
|
+
issues.push({
|
|
494
|
+
kind: GovernedDocumentReleaseCompositionIssueKind.VARIANT_NOT_PUBLISHED,
|
|
495
|
+
message: `variant "${variantKey}" is not among the variants the application declared it publishes in`,
|
|
496
|
+
});
|
|
497
|
+
}
|
|
498
|
+
|
|
499
|
+
/*
|
|
500
|
+
* A candidate MAY leave locale and jurisdictions open — that is deliberate upstream, so a draft can
|
|
501
|
+
* exist before the routing decision. What it may not do is state them and DISAGREE: releasing an
|
|
502
|
+
* `en-GB` draft as the `fr-FR` variant would publish text under a claim it does not make.
|
|
503
|
+
*/
|
|
504
|
+
if (candidate.locale !== undefined && candidate.locale !== variant.locale) {
|
|
505
|
+
issues.push({
|
|
506
|
+
kind: GovernedDocumentReleaseCompositionIssueKind.CANDIDATE_VARIANT_CONTRADICTION,
|
|
507
|
+
message: `candidate states locale "${candidate.locale}" but the release publishes "${variant.locale}"`,
|
|
508
|
+
});
|
|
509
|
+
}
|
|
510
|
+
if (candidate.jurisdictionRefs !== undefined && !sameSet(candidate.jurisdictionRefs, variant.jurisdictionRefs)) {
|
|
511
|
+
issues.push({
|
|
512
|
+
kind: GovernedDocumentReleaseCompositionIssueKind.CANDIDATE_VARIANT_CONTRADICTION,
|
|
513
|
+
message: `candidate states jurisdictions [${sorted(candidate.jurisdictionRefs).join(", ")}] but the release publishes [${sorted(variant.jurisdictionRefs).join(", ")}]`,
|
|
514
|
+
});
|
|
515
|
+
}
|
|
516
|
+
|
|
517
|
+
if (!definition.governanceSubjectKinds.includes(composition.governanceScope.subjectKind as GovernedDocumentGovernanceSubjectKind)) {
|
|
518
|
+
issues.push({
|
|
519
|
+
kind: GovernedDocumentReleaseCompositionIssueKind.GOVERNANCE_SUBJECT_NOT_PERMITTED,
|
|
520
|
+
message: `definition "${definition.identity.definitionRef}" governs [${definition.governanceSubjectKinds.join(", ")}], not "${composition.governanceScope.subjectKind}"`,
|
|
521
|
+
});
|
|
522
|
+
}
|
|
523
|
+
|
|
524
|
+
const replacesRelease: GovernedDocumentReleaseIdentity | undefined = composition.supersedes?.previousRelease;
|
|
525
|
+
if (replacesRelease !== undefined && replacesRelease.document.documentRef !== identity.document.documentRef) {
|
|
526
|
+
issues.push({
|
|
527
|
+
kind: GovernedDocumentReleaseCompositionIssueKind.REPLACES_DIFFERENT_DOCUMENT,
|
|
528
|
+
message: `a release may only supersede the same document: replacing "${replacesRelease.document.documentRef}" with "${identity.document.documentRef}"`,
|
|
529
|
+
});
|
|
530
|
+
}
|
|
531
|
+
|
|
532
|
+
const approvalState = composition.approvalDecisions.length > 0
|
|
533
|
+
? GovernedDocumentReleaseApprovalState.APPROVED
|
|
534
|
+
: GovernedDocumentReleaseApprovalState.UNAPPROVED;
|
|
535
|
+
if (approvalState === GovernedDocumentReleaseApprovalState.UNAPPROVED) {
|
|
536
|
+
advisories.push({
|
|
537
|
+
kind: GovernedDocumentReleaseAdvisoryKind.NOT_APPROVED,
|
|
538
|
+
message: `no approval decision is retained for "${identity.document.documentRef}"; the release is composed and marked UNAPPROVED`,
|
|
539
|
+
});
|
|
540
|
+
}
|
|
541
|
+
|
|
542
|
+
// ONLY incoherence stops here. Everything above that is workflow travels with the release.
|
|
543
|
+
if (issues.length > 0) return { release: undefined, issues, advisories };
|
|
544
|
+
|
|
545
|
+
const parsed = GovernedDocumentReleaseSchema.safeParse({
|
|
546
|
+
schemaVersion: 1,
|
|
547
|
+
identity,
|
|
548
|
+
definition: definition.identity,
|
|
549
|
+
governanceScope: composition.governanceScope,
|
|
550
|
+
// DERIVED, every one of them — see this module's header.
|
|
551
|
+
documentClass: definition.documentClass,
|
|
552
|
+
audienceKinds: [...definition.audienceKinds],
|
|
553
|
+
publicationChannelKinds: [...definition.publicationChannelKinds],
|
|
554
|
+
allowedInteractionKinds: [...definition.allowedInteractionKinds],
|
|
555
|
+
locale: variant.locale,
|
|
556
|
+
jurisdictionRefs: [...variant.jurisdictionRefs],
|
|
557
|
+
/*
|
|
558
|
+
* The text this release publishes, CAPTURED here (#968). Every later read of the release — the
|
|
559
|
+
* one in force, the one it superseded, the one scheduled next — shows the text it was composed
|
|
560
|
+
* with, not whatever the draft says by then. That only holds if the composed record is what gets
|
|
561
|
+
* committed; recomposing from the live draft on every import re-captures today's text.
|
|
562
|
+
*/
|
|
563
|
+
content: draftPublicContent(candidate, variant),
|
|
564
|
+
// The shape of `content` above — not a caller's choice, so not an input.
|
|
565
|
+
contentMediaType: GOVERNED_DOCUMENT_PUBLIC_CONTENT_MEDIA_TYPE,
|
|
566
|
+
issuedAt: composition.issuedAt,
|
|
567
|
+
effectiveAt: composition.effectiveAt,
|
|
568
|
+
...(composition.expiresAt === undefined ? {} : { expiresAt: composition.expiresAt }),
|
|
569
|
+
approvalDecisions: [...composition.approvalDecisions],
|
|
570
|
+
approvalState,
|
|
571
|
+
// Both, or neither — and both from ONE input, so the schema's pairing rule cannot be violated here.
|
|
572
|
+
...(composition.supersedes === undefined ? {} : { replacesRelease, materialityDecision: composition.supersedes }),
|
|
573
|
+
});
|
|
574
|
+
if (!parsed.success) {
|
|
575
|
+
return {
|
|
576
|
+
release: undefined,
|
|
577
|
+
issues: [{
|
|
578
|
+
kind: GovernedDocumentReleaseCompositionIssueKind.RELEASE_RECORD_INVALID,
|
|
579
|
+
message: parsed.error.issues.map((issue) => `${issue.path.join(".") || "<root>"}: ${issue.message}`).join("; "),
|
|
580
|
+
}],
|
|
581
|
+
advisories,
|
|
582
|
+
};
|
|
583
|
+
}
|
|
584
|
+
return { release: parsed.data, issues: [], advisories };
|
|
585
|
+
}
|
|
586
|
+
|
|
587
|
+
/** What a reader knows: which document, in which language, for which jurisdictions, at which instant. */
|
|
588
|
+
export interface GovernedDocumentReleaseQuery {
|
|
589
|
+
readonly documentRef: string;
|
|
590
|
+
readonly locale: string;
|
|
591
|
+
readonly jurisdictionRefs: readonly string[];
|
|
592
|
+
/** ISO-8601. The instant the answer is wanted FOR — usually now, but a past instant is what an audit asks. */
|
|
593
|
+
readonly at: string;
|
|
594
|
+
/**
|
|
595
|
+
* ⚠️ THE GATE POINT, and it is OFF by default. Deliberately.
|
|
596
|
+
*
|
|
597
|
+
* Serving an UNAPPROVED release to a real reader is a legally-binding statement leaving the
|
|
598
|
+
* system, which `one-source-of-truth.md` D5 names as a critical gate point — and says such points
|
|
599
|
+
* stay MARKED in every mechanism, notifying and proceeding under the current autonomy posture,
|
|
600
|
+
* with ARMING them part of Gate 3's membership test ("an application may face a real user").
|
|
601
|
+
*
|
|
602
|
+
* So this defaults to `false`: an application under construction reads its own documents, and a
|
|
603
|
+
* compliance workflow may not stand in front of the mechanism that builds it. Every returned
|
|
604
|
+
* release carries `approvalState`, so a caller always knows what it has.
|
|
605
|
+
*
|
|
606
|
+
* A surface that genuinely faces a real user passes `true`. When Gate 3 is armed, what changes is
|
|
607
|
+
* that passing it stops being the caller's choice — not that this parameter appears.
|
|
608
|
+
*/
|
|
609
|
+
readonly requireApproved?: boolean;
|
|
610
|
+
}
|
|
611
|
+
|
|
612
|
+
/**
|
|
613
|
+
* THE READ — which release is in force for one document, variant and instant.
|
|
614
|
+
*
|
|
615
|
+
* This is the half `0924c256` asked for when it deleted the custody machine: serving rebuilt as a
|
|
616
|
+
* read over committed files. It takes the releases an application has committed and answers from
|
|
617
|
+
* them alone; there is no store to consult and nothing to retrieve.
|
|
618
|
+
*
|
|
619
|
+
* What decides:
|
|
620
|
+
*
|
|
621
|
+
* - the variant must match EXACTLY. Locale and jurisdictions are one inseparable pair, and nothing
|
|
622
|
+
* here recombines them — an `en-GB` release for `jurisdiction:gb` is not an answer for
|
|
623
|
+
* `jurisdiction:eu`, even though both are `en-GB`;
|
|
624
|
+
* - `effectiveAt` must not be in the future and `expiresAt`, when present, must not have passed.
|
|
625
|
+
* A release that has been ISSUED is not yet in force; the difference is the whole point of
|
|
626
|
+
* carrying both dates;
|
|
627
|
+
* - of those in force, the one that took effect LAST wins, and `releaseVersion` breaks a tie. Two
|
|
628
|
+
* releases sharing an instant is an authoring fault rather than a question, and answering
|
|
629
|
+
* deterministically is better than answering arbitrarily.
|
|
630
|
+
*
|
|
631
|
+
* It does NOT filter by approval unless asked to — see `requireApproved`, which is the marked gate
|
|
632
|
+
* point and is off by default. An application being built must be able to read what it has.
|
|
633
|
+
*
|
|
634
|
+
* Returns `undefined` when nothing is in force, and a caller must treat that as "this application
|
|
635
|
+
* publishes no such document here yet" rather than as an error — for most of an application's life
|
|
636
|
+
* that is the true answer, and it is the state every consumer meets first.
|
|
637
|
+
*/
|
|
638
|
+
export function resolveEffectiveDocumentRelease(
|
|
639
|
+
releases: readonly GovernedDocumentRelease[],
|
|
640
|
+
query: GovernedDocumentReleaseQuery,
|
|
641
|
+
): GovernedDocumentRelease | undefined {
|
|
642
|
+
const at = Date.parse(query.at);
|
|
643
|
+
if (Number.isNaN(at)) return undefined;
|
|
644
|
+
const inForce = releases.filter((release) =>
|
|
645
|
+
(query.requireApproved !== true || release.approvalState === GovernedDocumentReleaseApprovalState.APPROVED)
|
|
646
|
+
&& release.identity.document.documentRef === query.documentRef
|
|
647
|
+
&& release.locale === query.locale
|
|
648
|
+
&& sameSet(release.jurisdictionRefs, query.jurisdictionRefs)
|
|
649
|
+
/*
|
|
650
|
+
* The interval question is ONE implementation, in `saas-models`, shared with the record side
|
|
651
|
+
* (`composeGovernedDocumentInteraction`). It was written out here and again there, and two
|
|
652
|
+
* copies of a half-open interval is precisely where a `<=`/`<` slip lives — which would mean a
|
|
653
|
+
* surface offering a release that the recorder then refuses as out of force, or worse, the
|
|
654
|
+
* reverse.
|
|
655
|
+
*/
|
|
656
|
+
&& governedDocumentReleaseIsInForce(release, query.at));
|
|
657
|
+
if (inForce.length === 0) return undefined;
|
|
658
|
+
return inForce.reduce((winner, candidate) => {
|
|
659
|
+
const byEffective = Date.parse(candidate.effectiveAt) - Date.parse(winner.effectiveAt);
|
|
660
|
+
if (byEffective !== 0) return byEffective > 0 ? candidate : winner;
|
|
661
|
+
return candidate.identity.releaseVersion > winner.identity.releaseVersion ? candidate : winner;
|
|
662
|
+
});
|
|
663
|
+
}
|
|
664
|
+
```
|
|
665
|
+
|
|
666
|
+
The release set an application commits:
|
|
667
|
+
|
|
668
|
+
## Import Origins
|
|
669
|
+
|
|
670
|
+
- `@wildo-ai/saas-specifications`
|
|
671
|
+
|
|
672
|
+
## Source Excerpts
|
|
673
|
+
|
|
674
|
+
### Origin Package: `@wildo-ai/saas-specifications`
|
|
675
|
+
|
|
676
|
+
```typescript
|
|
677
|
+
*
|
|
678
|
+
* The releases an application has COMMITTED — its answer to "which drafted
|
|
679
|
+
* content takes effect, when, and what does it supersede".
|
|
680
|
+
*
|
|
681
|
+
* A release is a file, and committing it is what makes it real: there is no
|
|
682
|
+
* store, no bundle and no custody protocol, per the demolition that removed the
|
|
683
|
+
* previous publication lane. This family is simply the home those files live in,
|
|
684
|
+
* so a reader can resolve one without discovering where an application chose to
|
|
685
|
+
* put them.
|
|
686
|
+
*
|
|
687
|
+
* **An UNAPPROVED release belongs here exactly as much as an approved one.**
|
|
688
|
+
* Approval is a workflow act that happens at the end, and an application holds
|
|
689
|
+
* its releases from the moment they are composed — for most of its life, before
|
|
690
|
+
* anyone has approved anything. Each record states its own
|
|
691
|
+
* `approvalState`, so nothing here has to be inferred and nothing can mistake a
|
|
692
|
+
* draft for a published document.
|
|
693
|
+
*
|
|
694
|
+
* Deliberately separate from the two families beside it, and the separation is
|
|
695
|
+
* what stops one decision silently widening another:
|
|
696
|
+
*
|
|
697
|
+
* | family | decides |
|
|
698
|
+
* |---|---|
|
|
699
|
+
* | the assurance program | WHICH documents are required, and who may approve them |
|
|
700
|
+
* | document-publication | which locale x jurisdiction combinations exist to publish in |
|
|
701
|
+
* | the release POLICY | which approval lane each requirement must go through |
|
|
702
|
+
* | **this family** | which releases the application has actually composed |
|
|
703
|
+
*/
|
|
704
|
+
export const ApplicationDocumentReleaseSetSchema = z
|
|
705
|
+
.strictObject({
|
|
706
|
+
schemaVersion: z.literal(1),
|
|
707
|
+
/**
|
|
708
|
+
* EMPTY is legal and is the honest answer for most applications.
|
|
709
|
+
*
|
|
710
|
+
* Not `.min(1)`: an application that has drafted nothing yet still has this family, and a
|
|
711
|
+
* minimum here would make "we have composed no releases" unrepresentable — the same mistake
|
|
712
|
+
* `approvalDecisions: .min(1)` made one layer down, where it meant an unapproved release could
|
|
713
|
+
* not exist at all.
|
|
714
|
+
*/
|
|
715
|
+
releases: z.array(GovernedDocumentReleaseSchema),
|
|
716
|
+
})
|
|
717
|
+
.superRefine((set, context) => {
|
|
718
|
+
/*
|
|
719
|
+
* One release identity, one record. The identity already carries document, releaseId and
|
|
720
|
+
* releaseVersion, so a duplicate is not a version — it is two records claiming to be the same
|
|
721
|
+
* release, and every read that resolves "which is in force" would then depend on array order.
|
|
722
|
+
*/
|
|
723
|
+
const seen = new Map<string, number>();
|
|
724
|
+
set.releases.forEach((release, index) => {
|
|
725
|
+
const key = governedDocumentReleaseIdentityKey(release.identity);
|
|
726
|
+
const first = seen.get(key);
|
|
727
|
+
if (first !== undefined) {
|
|
728
|
+
context.addIssue({
|
|
729
|
+
code: "custom",
|
|
730
|
+
message: `duplicate release identity "${key}" (already declared at index ${first})`,
|
|
731
|
+
path: ["releases", index, "identity"],
|
|
732
|
+
});
|
|
733
|
+
return;
|
|
734
|
+
}
|
|
735
|
+
seen.set(key, index);
|
|
736
|
+
});
|
|
737
|
+
});
|
|
738
|
+
export type ApplicationDocumentReleaseSet = z.infer<typeof ApplicationDocumentReleaseSetSchema>;
|
|
739
|
+
```
|