@wildo-ai/framework-knowledge 1.1.4 → 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 +227 -6
- 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/framework-knowledge.schemas.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.js.map +1 -1
- package/dist/esm/index.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +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.build-scale/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +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.d.ts.map +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
|
@@ -71,6 +71,50 @@ export type OrganizationUnitNarrowingDeclaration = {
|
|
|
71
71
|
### Origin Package: `@wildo-ai/saas-models`
|
|
72
72
|
|
|
73
73
|
```typescript
|
|
74
|
+
*
|
|
75
|
+
* Resources that may NEVER be unit-narrowable — the authorization plane.
|
|
76
|
+
*
|
|
77
|
+
* ## The loop this closes
|
|
78
|
+
*
|
|
79
|
+
* A resource that ISSUES authority must not be governed by the authority it issues. Were
|
|
80
|
+
* `ORGANIZATION_UNIT_MEMBERS` narrowable:
|
|
81
|
+
*
|
|
82
|
+
* 1. a principal who is organization-wide `ORG_MEMBER` but `ORG_ADMIN` of ONE unit
|
|
83
|
+
* 2. satisfies the `ORG_ADMIN` gate on the grant surface via that unit grant,
|
|
84
|
+
* 3. grants themselves `ORG_ADMIN` in every other unit,
|
|
85
|
+
* 4. and the union of all units is organization-wide admin — assembled from a single unit grant.
|
|
86
|
+
*
|
|
87
|
+
* Step 3 is blocked today only because the role ceiling derives from organization-wide grants. That
|
|
88
|
+
* is one refactor away from being undone (see the `D-C4 LOCK` regression test), so the containment
|
|
89
|
+
* is also structural: a unit grant can never reach these resources at all.
|
|
90
|
+
*
|
|
91
|
+
* Every major suite enforces the same separation — SAP puts user↔role assignment behind dedicated
|
|
92
|
+
* authorization objects, Azure puts role assignment outside the data plane behind
|
|
93
|
+
* `Microsoft.Authorization/roleAssignments/write`, and Dynamics forbids assigning a role you do not
|
|
94
|
+
* hold.
|
|
95
|
+
*
|
|
96
|
+
* `ORGANIZATION_MEMBERS` is listed for the same reason one level up: it carries the organization-wide
|
|
97
|
+
* `roles` array that produces `initiatorRoles`. The roles-bearing machine credentials are listed
|
|
98
|
+
* because the roles written at CREATE become the authority of every token minted from them.
|
|
99
|
+
*
|
|
100
|
+
* ## `ORGANIZATIONS` is listed for a SECOND, distinct reason — scope inversion
|
|
101
|
+
*
|
|
102
|
+
* The rule above is "a resource that ISSUES authority may not be governed by the authority it
|
|
103
|
+
* issues". `ORGANIZATIONS` is barred by its sibling: **a resource that DEFINES a scope may not be
|
|
104
|
+
* governed by a narrowing INSIDE that scope.** A unit is owned BY an organization, so letting the
|
|
105
|
+
* owned thing gate access to its owner inverts the containment.
|
|
106
|
+
*
|
|
107
|
+
* That is not abstract. The tenant lifecycle verbs live on this resource, and
|
|
108
|
+
* `request_deletion` / `suspend` are `ORG_ADMIN`-gated. Were `ORGANIZATIONS` narrowable, a principal
|
|
109
|
+
* who is organization-wide `ORG_MEMBER` but `ORG_ADMIN` of ONE unit would satisfy that gate through
|
|
110
|
+
* the unit grant — and one division's administrator could mark the ENTIRE tenant for deletion, or
|
|
111
|
+
* halt it. The blast radius is the whole organization, reached from a grant that was supposed to
|
|
112
|
+
* confine them to a subtree of it.
|
|
113
|
+
*
|
|
114
|
+
* It is also meaningless independently of the hazard: an organization is not located inside one of
|
|
115
|
+
* its own units, so there is no honest `unitFieldName` to declare. Listing it turns a declaration
|
|
116
|
+
* that could never be correct into a boot failure instead of a silent authorization hole.
|
|
117
|
+
*/
|
|
74
118
|
export const ORGANIZATION_UNIT_NARROWING_FORBIDDEN_RESOURCES: readonly CoreResourceType[] = [
|
|
75
119
|
CoreResourceType.ORGANIZATION_UNIT_MEMBERS,
|
|
76
120
|
CoreResourceType.ORGANIZATION_MEMBERS,
|
|
@@ -80,5 +124,11 @@ export const ORGANIZATION_UNIT_NARROWING_FORBIDDEN_RESOURCES: readonly CoreResou
|
|
|
80
124
|
CoreResourceType.ORGANIZATIONS,
|
|
81
125
|
CoreResourceType.ORG_API_KEYS,
|
|
82
126
|
CoreResourceType.OAUTH_CLIENTS_ORGANIZATION,
|
|
127
|
+
// A credential authenticates the WHOLE TENANT toward a third party — there is one Slack workspace
|
|
128
|
+
// behind it, not one per division. Narrowing it to a unit would let a unit-scoped administrator
|
|
129
|
+
// rotate or delete the credential every other unit spends, which is the same issues-authority
|
|
130
|
+
// hazard the sibling entries above record: the grant confines them to a subtree, the object they
|
|
131
|
+
// reach does not live in one.
|
|
132
|
+
CoreResourceType.ORG_PROVIDER_CREDENTIALS,
|
|
83
133
|
];
|
|
84
134
|
```
|
|
@@ -53,7 +53,7 @@ one typed module record.
|
|
|
53
53
|
| Module backend root | `backend-api/src/modules/<slug>/index.ts` (exports `default <slug>BackendModule`) |
|
|
54
54
|
| Module resources slot | `backend-api/src/modules/<slug>/resources/index.ts` (`scanDefaultExports` for `.operation`) |
|
|
55
55
|
| Module flows-actors slot | `backend-api/src/modules/<slug>/addons/flows-actors/index.ts` |
|
|
56
|
-
| Module DI container | `backend-api/src/modules/<slug>/addons/container.ts` (
|
|
56
|
+
| Module DI container | `backend-api/src/modules/<slug>/addons/container.ts` (NOT scaffolded — create it when a module owns injectable services; merged from `backend-api/src/index.ts`) |
|
|
57
57
|
| Module services aggregator | `backend-api/src/modules/<slug>/addons/services/index.ts` |
|
|
58
58
|
| Module controllers aggregator | `backend-api/src/modules/<slug>/addons/controllers/index.ts` |
|
|
59
59
|
| Module email template definitions | `backend-api/src/modules/<slug>/emails/index.ts` |
|
|
@@ -115,11 +115,21 @@ record can compose without a TypeScript error.
|
|
|
115
115
|
|
|
116
116
|
### Step 4: Set up the Inversify container
|
|
117
117
|
|
|
118
|
-
|
|
119
|
-
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
|
|
118
|
+
A generated application does NOT scaffold a module container: the
|
|
119
|
+
backend entry, `backend-api/src/index.ts`, builds one process container
|
|
120
|
+
with `setupSaasBackendInjection()` and resolves the start service from it
|
|
121
|
+
straight away. When a module owns services that need injection, create
|
|
122
|
+
`addons/container.ts` yourself — a `ModuleBackendContainer` whose
|
|
123
|
+
`bindServices()` binds INTO the container it is given, plus a
|
|
124
|
+
`setupModuleBackendInjection(container)` export — and call it from the
|
|
125
|
+
backend entry.
|
|
126
|
+
|
|
127
|
+
**Call it before the first `container.get(...StartApplicationService)`.**
|
|
128
|
+
The start service is constructed with the HTTP server and the health
|
|
129
|
+
controller, and they read their injected collaborators once, at that
|
|
130
|
+
moment. A binding merged afterwards is never consulted, and nothing
|
|
131
|
+
reports it — a readiness contributor bound late simply never appears
|
|
132
|
+
(see `references/framework-readiness-contributor-api.md`).
|
|
123
133
|
|
|
124
134
|
### Step 5: Compose the `BackendOwnedModule` record
|
|
125
135
|
|
|
@@ -186,20 +196,16 @@ const backendModule: BackendDomainModule = {
|
|
|
186
196
|
// Singleton config rows auto-seeded on resource lifecycle:
|
|
187
197
|
// - M2M outbound webhook config (per ORG / per APP) — app-specific dev-listener
|
|
188
198
|
// payload, so it stays app-owned (`./seeds/webhook-configs.seeds.ts`).
|
|
189
|
-
//
|
|
190
|
-
//
|
|
191
|
-
//
|
|
192
|
-
//
|
|
193
|
-
//
|
|
194
|
-
//
|
|
195
|
-
//
|
|
196
|
-
//
|
|
197
|
-
// hook ever runs (see `applicationMetadataSeedDefinitions`).
|
|
199
|
+
//
|
|
200
|
+
// The engine's OWN defaults are no longer listed here, and their absence is the point.
|
|
201
|
+
// Enterprise-config disabled defaults (SSO / SCIM / SIEM, both scopes) and APPLICATION_METADATA
|
|
202
|
+
// used to be spread in below under a "framework-provides / app-registers" pattern. The framework
|
|
203
|
+
// now registers them itself (`ENGINE_OWNED_DATA_SEEDS`), because an opt-in is something an
|
|
204
|
+
// application can forget: Wonder CRM never wired any of them, so every SSO / SCIM / SIEM settings
|
|
205
|
+
// panel there answered a 404 that renders as "Couldn't load details". Re-adding them here would
|
|
206
|
+
// now fail the boot on a duplicate `seedKey`, deliberately.
|
|
198
207
|
seeds: [
|
|
199
208
|
...webhookConfigSeeds,
|
|
200
|
-
...enterpriseAuthConfigOrgSeedDefinitions,
|
|
201
|
-
...enterpriseAuthConfigApplicationSeedDefinitions,
|
|
202
|
-
...applicationMetadataSeedDefinitions,
|
|
203
209
|
],
|
|
204
210
|
};
|
|
205
211
|
|
|
@@ -249,7 +255,7 @@ What earns its place:
|
|
|
249
255
|
|
|
250
256
|
What is **not** in this block (and shouldn't be):
|
|
251
257
|
|
|
252
|
-
- No inline service bindings —
|
|
258
|
+
- No inline service bindings — when a module owns injectable services they live in its `addons/container.ts`, merged before the start service is resolved
|
|
253
259
|
- No inline templates — those live in `./emails` barrel
|
|
254
260
|
- No `customLabels` slot on domain modules — it's engine-only
|
|
255
261
|
(single owner via `scanCustomLabelsDirectory`)
|
|
@@ -262,6 +268,7 @@ What is **not** in this block (and shouldn't be):
|
|
|
262
268
|
|
|
263
269
|
- `references/backend-di-routing.md` — container and route patterns
|
|
264
270
|
- `references/framework-backend-bootstrap-api.md` — `BackendDomainModule` + initialization assembly input
|
|
271
|
+
- `references/framework-readiness-contributor-api.md` — what `/health` and `/health/ready` already check, and how a process that cannot serve without another dependency adds it to its readiness answer (and why the binding's ORDER decides whether it counts)
|
|
265
272
|
- `module-registration/SKILL.md` — shared/frontend module registration parity
|
|
266
273
|
- `backend-custom-operation/SKILL.md` — authoring `*.operation.ts` files (the resources slot consumer)
|
|
267
274
|
|
package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md
CHANGED
|
@@ -74,7 +74,7 @@ export interface BackendDomainModule extends SharedDomainModule {
|
|
|
74
74
|
* Aggregated by {@link mergeBackendDomainModules} into a single
|
|
75
75
|
* `Record<string, DataSeedScopeResolver>` and threaded through
|
|
76
76
|
* `ApplicationInitializationConfig.dataSeedScopeResolvers`. The
|
|
77
|
-
* data-seeding bootstrap (`
|
|
77
|
+
* data-seeding bootstrap (`wireDataSeedingDeclarations`) hands
|
|
78
78
|
* the merged map to
|
|
79
79
|
* {@link DataSeedScopeResolverRegistryBackendService.registerResolvers}
|
|
80
80
|
* once per boot.
|
|
@@ -87,6 +87,30 @@ export interface BackendDomainModule extends SharedDomainModule {
|
|
|
87
87
|
dataSeedScopeResolvers?: Record<string, DataSeedScopeResolver>;
|
|
88
88
|
}
|
|
89
89
|
|
|
90
|
+
/**
|
|
91
|
+
* Merge every module's backend contributions into one.
|
|
92
|
+
*
|
|
93
|
+
* ⚠️ **The fields do NOT all treat a cross-module duplicate the same way, and the difference is
|
|
94
|
+
* silent.** Three of them reject a duplicate at merge time with a `CONFIGURATION` error naming both
|
|
95
|
+
* contributors — `dataSeedScopeResolvers`, `pdfTemplateBindings` and `chartDefinitions`. Two of them
|
|
96
|
+
* do not:
|
|
97
|
+
*
|
|
98
|
+
* | field | duplicate across two modules |
|
|
99
|
+
* |---|---|
|
|
100
|
+
* | `resourceConfigurations` | **last module wins, silently** |
|
|
101
|
+
* | `resourceFieldIdentifiers` | **last module wins, silently** |
|
|
102
|
+
* | `dataSeedScopeResolvers` · `pdfTemplateBindings` · `chartDefinitions` | rejected, naming both modules |
|
|
103
|
+
* | `resourceRelationships` · `operations` · `controllers` · `seeds` | concatenated — both are kept |
|
|
104
|
+
*
|
|
105
|
+
* Do not generalise the rejection to the whole object. Two modules declaring the same resource
|
|
106
|
+
* identifier produce no error and no warning: whichever is later in the registry array replaces the
|
|
107
|
+
* earlier one entirely, and the application boots. That shadowing is what lets an application layer
|
|
108
|
+
* its own module over the engine's, so it cannot be made an error — which is exactly why an
|
|
109
|
+
* ACCIDENTAL collision is invisible.
|
|
110
|
+
*
|
|
111
|
+
* If a resource behaves as though its configuration were somebody else's, check for a second module
|
|
112
|
+
* declaring the same identifier before looking anywhere else.
|
|
113
|
+
*/
|
|
90
114
|
export function mergeBackendDomainModules(
|
|
91
115
|
...modules: BackendDomainModule[]
|
|
92
116
|
): BackendDomainModule {
|
package/dist/knowledge/skills/backend-addon-wiring/references/framework-readiness-contributor-api.md
ADDED
|
@@ -0,0 +1,135 @@
|
|
|
1
|
+
# Framework Readiness Contributor API
|
|
2
|
+
|
|
3
|
+
What a backend process's readiness probe already checks, and the one door by which your process adds
|
|
4
|
+
a dependency the framework cannot know about.
|
|
5
|
+
|
|
6
|
+
Read this when:
|
|
7
|
+
|
|
8
|
+
- your backend cannot serve a single request without something outside the framework's own readiness
|
|
9
|
+
set — a cache you deliberately give no fallback, a licence server, a search index, a provider
|
|
10
|
+
endpoint every request calls;
|
|
11
|
+
- a deployment keeps routing traffic to a process that then fails every request;
|
|
12
|
+
- a `503` from `/health/ready` names a component and you need to know where that name comes from.
|
|
13
|
+
|
|
14
|
+
## What every backend process already answers
|
|
15
|
+
|
|
16
|
+
The framework mounts both probes on every backend process. Do not declare your own.
|
|
17
|
+
|
|
18
|
+
| probe | answers | checks |
|
|
19
|
+
|---|---|---|
|
|
20
|
+
| `GET /health` | liveness — `200` while the process is answering | nothing else, on purpose: a dependency blip must not restart every replica at once. It does not detect a process that is running but stuck |
|
|
21
|
+
| `GET /health/ready` | readiness — `200` or `503` | the application configuration is initialised; file storage, only when it is configured (unconfigured storage reports healthy); the document database, only when this process uses one; and **at most one dependency you contribute** |
|
|
22
|
+
|
|
23
|
+
The readiness body carries a `components` map and a `failing` list — the names of what is not healthy —
|
|
24
|
+
and never the error text. The reason a component failed goes to the backend's WARN log, because the
|
|
25
|
+
probe is normally unauthenticated and error text routinely carries hostnames and credential paths.
|
|
26
|
+
|
|
27
|
+
A cache is not in the fixed set because startup allows an in-memory fallback. If YOUR process cannot
|
|
28
|
+
run on that fallback, the cache is exactly the dependency to contribute.
|
|
29
|
+
|
|
30
|
+
## Adding your dependency
|
|
31
|
+
|
|
32
|
+
Implement the interface below and bind it in the backend entry, `backend-api/src/index.ts`, **before
|
|
33
|
+
the first time the start service is resolved**:
|
|
34
|
+
|
|
35
|
+
<!-- TIER C WAIVER: the lesson is the ORDER of three existing lines in the generated entry file, which no anchored example can show without the entry file itself; the contract is source-backed below. -->
|
|
36
|
+
```ts
|
|
37
|
+
const container = setupSaasBackendInjection();
|
|
38
|
+
container.bind(SAAS_SERVICE_TYPES.HealthReadinessContributorService).to(SearchIndexReadiness).inSingletonScope();
|
|
39
|
+
const startApplicationService = container.get<StartApplicationBackendService>(SAAS_SERVICE_TYPES.StartApplicationService);
|
|
40
|
+
```
|
|
41
|
+
|
|
42
|
+
**The order is the whole trap.** The readiness check is constructed together with the start service,
|
|
43
|
+
and it reads the contributor once, then. A binding added after that `get` is never consulted — and
|
|
44
|
+
nothing reports it: your component simply never appears in `components`, and the process reads ready
|
|
45
|
+
while the dependency is down. If your application merges module bindings through a helper, that
|
|
46
|
+
helper must also run before this line.
|
|
47
|
+
|
|
48
|
+
**One contributor per process.** The injection point takes a single binding; two bindings on the same
|
|
49
|
+
identifier make the start service fail to resolve. A process with two such dependencies contributes
|
|
50
|
+
one component that reports on both, named for the one an operator would look at first.
|
|
51
|
+
|
|
52
|
+
`SAAS_SERVICE_TYPES`, `StartApplicationBackendService` and the interface are all exported from
|
|
53
|
+
`@wildo-ai/saas-backend-lib`.
|
|
54
|
+
|
|
55
|
+
## The contract
|
|
56
|
+
|
|
57
|
+
## Import Origins
|
|
58
|
+
|
|
59
|
+
- `@wildo-ai/saas-backend-lib`
|
|
60
|
+
|
|
61
|
+
## Source Excerpts
|
|
62
|
+
|
|
63
|
+
### Origin Package: `@wildo-ai/saas-backend-lib`
|
|
64
|
+
|
|
65
|
+
```typescript
|
|
66
|
+
/**
|
|
67
|
+
* The health of ONE readiness dependency, as a process's own contributor reports it.
|
|
68
|
+
*
|
|
69
|
+
* `connecting` is deliberately distinct from `unhealthy`: it maps to a `degraded` overall status,
|
|
70
|
+
* which is still a READY outcome. A dependency that is coming up must not evict the process from
|
|
71
|
+
* its load balancer.
|
|
72
|
+
*/
|
|
73
|
+
export interface ReadinessDependencyHealth {
|
|
74
|
+
status: 'healthy' | 'unhealthy' | 'connecting';
|
|
75
|
+
latency?: number;
|
|
76
|
+
/**
|
|
77
|
+
* Why it is unhealthy, for the OPERATOR — this reaches the WARN log stream and nothing else.
|
|
78
|
+
* `/health/ready` is typically unauthenticated, so error text (which routinely carries hostnames,
|
|
79
|
+
* ports and credential paths) is deliberately never put on the response.
|
|
80
|
+
*/
|
|
81
|
+
error?: string;
|
|
82
|
+
details?: Record<string, unknown>;
|
|
83
|
+
}
|
|
84
|
+
|
|
85
|
+
/**
|
|
86
|
+
* A process's own readiness dependency, contributed to `/health/ready`.
|
|
87
|
+
*
|
|
88
|
+
* ## The seam, and how a process opens it
|
|
89
|
+
*
|
|
90
|
+
* `HealthControllerBackendService` checks four components: MongoDB (only when this runtime has
|
|
91
|
+
* one), the application configuration, the configured file storage, and — through this interface —
|
|
92
|
+
* ONE dependency the engine cannot know about. Redis is the canonical example of why the seam
|
|
93
|
+
* exists rather than a fifth hard-coded check: backend and companion startup both allow an
|
|
94
|
+
* in-memory fallback, so Redis must not be a universal gate; a process that genuinely CANNOT serve
|
|
95
|
+
* without it says so here instead.
|
|
96
|
+
*
|
|
97
|
+
* A process opens the seam from its own container, which already extends the engine's:
|
|
98
|
+
*
|
|
99
|
+
* ```ts
|
|
100
|
+
* c.bind(SAAS_SERVICE_TYPES.HealthReadinessContributorService)
|
|
101
|
+
* .to(MyProcessReadinessContributor)
|
|
102
|
+
* .inSingletonScope();
|
|
103
|
+
* ```
|
|
104
|
+
*
|
|
105
|
+
* The injection point is `@optional()`, so a process that binds nothing keeps the previous
|
|
106
|
+
* behaviour exactly: the component reports healthy and never appears in `failing`.
|
|
107
|
+
*
|
|
108
|
+
* ## `getComponentName` is a PUBLISHED name, not a log label
|
|
109
|
+
*
|
|
110
|
+
* It keys this component in the readiness response's `components` map and is the string
|
|
111
|
+
* that appears in `failing`. So it is what an operator reads on a 503, and what an e2e lane asserts
|
|
112
|
+
* on. Name the DEPENDENCY (`redis`, `searchIndex`, `licenceServer`), not the check.
|
|
113
|
+
*
|
|
114
|
+
* ## `checkReadiness` is called on EVERY probe
|
|
115
|
+
*
|
|
116
|
+
* Roughly every two seconds, per process. It is bounded at 5 s by the controller — a check that
|
|
117
|
+
* never settles is reported as unhealthy rather than hanging the probe — but it must be cheap:
|
|
118
|
+
* a ping, a cached connection state, a pool statistic. Never a query that does work.
|
|
119
|
+
*
|
|
120
|
+
* Throwing is a supported outcome and is reported as unhealthy with the thrown message; the
|
|
121
|
+
* contributor does not need its own try/catch.
|
|
122
|
+
*/
|
|
123
|
+
export interface HealthReadinessContributorBackendService {
|
|
124
|
+
getComponentName(): string;
|
|
125
|
+
checkReadiness(): Promise<ReadinessDependencyHealth>;
|
|
126
|
+
}
|
|
127
|
+
```
|
|
128
|
+
|
|
129
|
+
## Verification
|
|
130
|
+
|
|
131
|
+
- With the dependency up, `/health/ready` answers `200` and `components` contains your component name.
|
|
132
|
+
- Stop the dependency: within one probe interval `/health/ready` answers `503` and `failing` names your
|
|
133
|
+
component. If it still answers `200`, the binding was added after the start service was resolved.
|
|
134
|
+
- Your `checkReadiness` does no work — a ping or a cached connection state — because it runs on every
|
|
135
|
+
probe, every few seconds, per process.
|
|
@@ -31,14 +31,15 @@ A custom operation file is the spot where:
|
|
|
31
31
|
|
|
32
32
|
1. **Custom validation** beyond Zod runs (cross-field constraints,
|
|
33
33
|
tenant-aware rules, async validation against external systems)
|
|
34
|
-
2. **Side effects**
|
|
35
|
-
|
|
34
|
+
2. **Side effects** are coordinated with the operation; work that must survive
|
|
35
|
+
commit belongs in the durable post-commit mechanism, not an ordinary postfix
|
|
36
36
|
3. **Pipeline composition** layers custom logic on top of the
|
|
37
37
|
framework's generic CRUD path through lifecycle hooks
|
|
38
|
-
4. **Cross-resource orchestration**
|
|
38
|
+
4. **Cross-resource orchestration** can opt into an explicit transactional
|
|
39
|
+
boundary with declared participants and propagated service options
|
|
39
40
|
|
|
40
|
-
The framework's generic CRUD remains the default
|
|
41
|
-
|
|
41
|
+
The framework's generic CRUD remains the default. Hooks can augment it;
|
|
42
|
+
REPLACE and `overrideAll` have distinct ownership rules described in Step 5.
|
|
42
43
|
|
|
43
44
|
## App Paths
|
|
44
45
|
|
|
@@ -141,14 +142,63 @@ produce an equivalent committed winner, author
|
|
|
141
142
|
single bounded full-boundary retry, and `UNHANDLED` preserves the original
|
|
142
143
|
conflict. An absent result never implicitly means “retry.”
|
|
143
144
|
|
|
145
|
+
If the operation must call an external system whose outcome feeds the core
|
|
146
|
+
write — a payment provider changing a subscription, for example — never make
|
|
147
|
+
that call from `prefixCoreOperations` inside `transactionalCore`: the database
|
|
148
|
+
driver may retry the callback, and the external effect would repeat. Declare
|
|
149
|
+
`beforeTransactionalCore` instead. It runs once, after preflight and OUTSIDE any
|
|
150
|
+
transaction, and answers either `CONTINUE` with a `coreInputPatch` (merged into
|
|
151
|
+
the core input every retried attempt sees) and a `continuation` (read by the
|
|
152
|
+
core phases as `utils.beforeTransactionalCore.continuation`), or
|
|
153
|
+
`ALREADY_COMPLETED`, which skips core persistence, managed post-commit effects
|
|
154
|
+
and token consumption, applies the synchronous terminal result transforms, and
|
|
155
|
+
answers the target's stored state. The rules it enforces:
|
|
156
|
+
|
|
157
|
+
- it requires `transactionalCore: true`, exactly one registration may declare
|
|
158
|
+
it, and it is refused inside a caller-owned transaction;
|
|
159
|
+
- the operation input must be an object (not a bulk array), and the phase is
|
|
160
|
+
refused on a bulk operation (`isBulkOperation`, CREATE_MANY, UPDATE_MANY,
|
|
161
|
+
DELETE_MANY) — there is no single continuation or stored state for one.
|
|
162
|
+
Both are checked before the handler runs, so a refused call leaves no
|
|
163
|
+
external effect behind;
|
|
164
|
+
- the patch's keys are treated as server-owned, like `authoritativeFields`:
|
|
165
|
+
the value after PREFIX persists, even for a field the request DTO seals;
|
|
166
|
+
- a refusal that does not depend on the handler's answer — a missing target,
|
|
167
|
+
a client change to a read-only field — happens before the handler runs;
|
|
168
|
+
- `ALREADY_COMPLETED` needs a single explicit target (never a CREATE or a
|
|
169
|
+
filter target) and is refused when a consumable token is presented; a
|
|
170
|
+
replay writes no second audit row, because the original occurrence did.
|
|
171
|
+
|
|
172
|
+
The same reference file carries its result types.
|
|
173
|
+
|
|
174
|
+
Leave `postCommitEffectOwnership` unset (it defaults to `FRAMEWORK`). The
|
|
175
|
+
`IMPLEMENTATION_OUTBOX` value you may see in the reference is reserved for
|
|
176
|
+
engine-owned writers whose effects an engine relay delivers: under it the
|
|
177
|
+
framework stops writing the operation's audit row and sending its
|
|
178
|
+
notifications, and there is no application-facing delivery surface, so an
|
|
179
|
+
application that declared it would lose both silently.
|
|
180
|
+
|
|
181
|
+
Post-operation hooks you register receive a fifth argument,
|
|
182
|
+
`{ postCommitEffectOwnership }`. Ignore it unless your hook does work that an
|
|
183
|
+
engine outbox delivers.
|
|
184
|
+
|
|
144
185
|
### Step 5: Implement only the handlers you need
|
|
145
186
|
|
|
146
187
|
Each handler is optional. Common patterns:
|
|
147
188
|
|
|
189
|
+
- **`beforeTransactionalCore`** — the one place for an external effect whose
|
|
190
|
+
outcome feeds the core write (single-owner; requires `transactionalCore`;
|
|
191
|
+
see Step 4). Make the effect itself idempotent — a request that replays after
|
|
192
|
+
a lost response must find its earlier outcome and answer `ALREADY_COMPLETED`.
|
|
148
193
|
- **`prefixCoreOperations`** — input validation / mutation before
|
|
149
194
|
CRUD runs (must return the (possibly mutated) input)
|
|
150
|
-
- **`replaceCoreOperations`** —
|
|
151
|
-
core operation
|
|
195
|
+
- **`replaceCoreOperations`** — supply the authoritative result (single-owner
|
|
196
|
+
mode). With a CREATE core operation, core persistence is skipped. It is also
|
|
197
|
+
skipped for UPDATE / UPDATE_MANY / DELETE / DELETE_MANY when no target was
|
|
198
|
+
resolved. With a resolved target, those mutations still run core persistence
|
|
199
|
+
before REPLACE; replacing their result does not suppress the write. Other
|
|
200
|
+
core operations run before REPLACE as usual. Use `overrideAll` when the
|
|
201
|
+
implementation must own the entire pipeline instead.
|
|
152
202
|
- **`postfixCoreOperations`** — transform the core/REPLACE result; it
|
|
153
203
|
remains inside `transactionalCore` when that mode is enabled
|
|
154
204
|
- **`afterUserNotifications`** / **`atTheEnd`** — synchronous,
|
|
@@ -241,11 +291,12 @@ What earns its place:
|
|
|
241
291
|
executionContext, operationPath, utils) => {...} }` — single
|
|
242
292
|
hook. The five handler parameters are positional and typed:
|
|
243
293
|
`id` (resource id, may be unset on CREATE prefix),
|
|
244
|
-
`input` (
|
|
294
|
+
`input` (the current core/REPLACE result, typed from the response DTO), `executionContext`
|
|
245
295
|
(auth + tenant), `operationPath` (echoed for convenience),
|
|
246
296
|
`utils` (logger, repository services). The handler **must
|
|
247
|
-
return the
|
|
248
|
-
continue the pipeline.
|
|
297
|
+
return the result** (unchanged or transformed) for the framework to
|
|
298
|
+
continue the pipeline. Here the parameter is named `input`, but it is not
|
|
299
|
+
the CREATE request; this logging hook returns the created result unchanged.
|
|
249
300
|
- `utils.logger.debug('TodosCreatePostfix.postfixCoreOperations executed')`
|
|
250
301
|
— typed logger with named source. Never `console.log`; the
|
|
251
302
|
framework logger is structured and routed.
|
|
@@ -262,8 +313,17 @@ What is **not** in this block (and shouldn't be):
|
|
|
262
313
|
- No raw `console.log` — use `utils.logger`
|
|
263
314
|
- No untyped `(input: any) => ...` handler signatures — the
|
|
264
315
|
generic flow is what makes the handlers safe
|
|
265
|
-
- No
|
|
266
|
-
|
|
316
|
+
- No `transactionalCore` declaration — this logging hook uses the default
|
|
317
|
+
non-transactional mode. Its presence does not create an atomic boundary
|
|
318
|
+
around core persistence and the postfix. A postfix failure alone therefore
|
|
319
|
+
does not guarantee rollback of the core write.
|
|
320
|
+
|
|
321
|
+
To make core persistence and participating hooks one framework-owned atomic
|
|
322
|
+
boundary, opt into `transactionalCore` as described in Step 4. If the operation
|
|
323
|
+
instead joins a caller-owned transaction, the caller controls commit and
|
|
324
|
+
rollback; nested resource calls must preserve `utils.serviceOptions`. Neither
|
|
325
|
+
case is established merely by declaring a postfix, and this example declares
|
|
326
|
+
neither transaction ownership nor a caller transaction.
|
|
267
327
|
|
|
268
328
|
## Rejecting from a hook: throw a WildoError, never `new Error`
|
|
269
329
|
|
|
@@ -293,6 +353,8 @@ map and the message/context rules.
|
|
|
293
353
|
|
|
294
354
|
## References
|
|
295
355
|
|
|
356
|
+
- `references/framework-assurance-control-markers.md` — how to mark an operation that implements a control, and the three things about the marker that are enforced rather than conventional
|
|
357
|
+
- `references/framework-error-user-guidance-api.md` — throwing an error the user can ACT on, and why the `...GuidanceKey` variant is the one to reach for
|
|
296
358
|
- `references/operation-file-conventions.md` — operation file conventions
|
|
297
359
|
- `references/framework-operation-base-and-path-api.md` — source-backed operation identity / path types from `saas-models`
|
|
298
360
|
- `references/framework-transactional-core-api.md` — source-backed atomic core and named participant contract
|
|
@@ -349,6 +411,7 @@ keep the operation aligned with the resource config as it evolves.
|
|
|
349
411
|
| "A conflict resolver can return `undefined` to ask for a retry" | No. Return `RETRY_TRANSACTION` explicitly. Use `UNHANDLED` to preserve the original conflict and `RECONCILED` only with an already-committed equivalent result. |
|
|
350
412
|
| "Catch errors as `Error`" | Use `isWildoBackendError(error)`; raw `Error` catches mask typed backend errors and break observability. |
|
|
351
413
|
| "`throw new Error('bad input')` is simpler" | It bypasses the error system — the framework guesses the status from the message text, the user gets a generic 500, and there is no i18n. Throw `utils.errorBuilder.buildError(ErrorType.X, ec, { customMessageReference })`. |
|
|
414
|
+
| "I'll just mount a route directly — declaring an operation is ceremony" | The generated API reference is a projection of the operations the application DECLARES. An endpoint mounted outside the resource system is outside that projection, so it never appears in the public or administration OpenAPI document and never reaches the documentation portal — and nothing warns you, because a document cannot miss what it was never told about. Declaring the operation is what makes it documented. |
|
|
352
415
|
| "Put the message in `context.message` so the user sees it" | For most ErrorTypes `context` is stripped before the response, so that string is never shown and never localized. The user message is the `customMessageReference`; `context` is for structured, log-only diagnostic values. |
|
|
353
416
|
|
|
354
417
|
## Red Flags
|
|
@@ -0,0 +1,137 @@
|
|
|
1
|
+
# Marking an operation that implements a control
|
|
2
|
+
|
|
3
|
+
Wildo applications are assurance-ready by construction, which means a security-, privacy- or
|
|
4
|
+
access-relevant operation carries a greppable marker naming the objective it discharges.
|
|
5
|
+
|
|
6
|
+
Read this when:
|
|
7
|
+
|
|
8
|
+
- you are writing an operation that authenticates, authorizes, erases, exports, consents, audits, or
|
|
9
|
+
changes a permission or a configuration;
|
|
10
|
+
- you have identified a control the application should have and are not closing it now;
|
|
11
|
+
- a check refuses your marker.
|
|
12
|
+
|
|
13
|
+
The objective ids are the framework's, not yours — the installed authority basis under
|
|
14
|
+
`.claude/skills/../assurance-authority-bases/` lists them, and a marker naming an id the framework's
|
|
15
|
+
catalog does not define fails the check.
|
|
16
|
+
|
|
17
|
+
## Import Origins
|
|
18
|
+
|
|
19
|
+
- `@wildo-ai/saas-specifications`
|
|
20
|
+
|
|
21
|
+
## Source Excerpts
|
|
22
|
+
|
|
23
|
+
### Origin Package: `@wildo-ai/saas-specifications`
|
|
24
|
+
|
|
25
|
+
```typescript
|
|
26
|
+
/**
|
|
27
|
+
* The Wildo-owned assurance objective catalog: every outcome the codebase claims to control, stated once, in Wildo's own words.
|
|
28
|
+
*
|
|
29
|
+
* ## Writing a marker in YOUR application
|
|
30
|
+
*
|
|
31
|
+
* When you implement — or should implement — a control, annotate the site with a greppable marker
|
|
32
|
+
* naming one of these objectives. The block below is an ILLUSTRATION, quoted from an application's
|
|
33
|
+
* erasure-cancellation operation — it is not a marked site in this file, and a sweep deriving an
|
|
34
|
+
* objective's intent from the markers citing it must not read it as one:
|
|
35
|
+
*
|
|
36
|
+
* ```ts
|
|
37
|
+
* // assurance-control: WILDO.PRIVACY.SUBJECT_ERASURE — the subject-controlled withdrawal of a
|
|
38
|
+
* // pending Art. 17 erasure, gated so only a pending request can be withdrawn.
|
|
39
|
+
* ```
|
|
40
|
+
*
|
|
41
|
+
* Use `TODO(assurance-control)` in the same shape for a control gap you have identified and not
|
|
42
|
+
* closed. One site may carry several markers when it discharges several objectives.
|
|
43
|
+
*
|
|
44
|
+
* Three things about it are enforced rather than conventional, and `pnpm
|
|
45
|
+
* check:assurance-control-boundary` reads your application's source as well as the framework's:
|
|
46
|
+
*
|
|
47
|
+
* - **the id must exist in this catalog.** You cannot invent an objective for your own domain; a
|
|
48
|
+
* marker naming an id this file does not define FAILS the check;
|
|
49
|
+
* - **no external framework name, standard, regulation or certification identifier may appear in a
|
|
50
|
+
* marker.** Those belong only at rights-classified mapping and report boundaries, and never in
|
|
51
|
+
* code that selects behaviour. Naming one in a marker is a hard failure, not a baseline row;
|
|
52
|
+
* - **the prose is a comment, so nothing can falsify it.** When the intents in this file were read
|
|
53
|
+
* back against the marked sites, thirty-one of forty-nine were changed and roughly half of those
|
|
54
|
+
* were wrong rather than merely loose. Write the sentence about what the code DOES, and re-read it
|
|
55
|
+
* when you change the code.
|
|
56
|
+
*
|
|
57
|
+
* This is deliberately source-neutral. External standards, regulations and mappings may reference these objectives at rights-classified report boundaries, but they never
|
|
58
|
+
* define the production objective identity or select application behavior.
|
|
59
|
+
*
|
|
60
|
+
* ## Why every marked objective must appear here
|
|
61
|
+
*
|
|
62
|
+
* An `assurance-control:` marker in engine or platform source names an objective by id. Until 2026-08-31 the catalog held two of them while the code cited fifty, so
|
|
63
|
+
* forty-seven objectives existed only as strings inside comments — with no title, no intent, no lifecycle status and no governance scope. An objective in that state
|
|
64
|
+
* cannot appear in a governed document, cannot be assessed, and cannot be bound to a capability, which is why nothing downstream of the catalog had ever produced a
|
|
65
|
+
* result. The catalog and the markers are now held together mechanically by `pnpm check:assurance-control-boundary`, which fails when a marker names an id this file
|
|
66
|
+
* does not define. Add the objective here in the same change that adds the marker.
|
|
67
|
+
*
|
|
68
|
+
* ## The three governance scopes, and their honest status
|
|
69
|
+
*
|
|
70
|
+
* - `governance-scope:application` — the system being built and operated. Every objective is in this scope; it is the default and never absent.
|
|
71
|
+
* - `governance-scope:organization-policy` — what a customer organization decides for itself inside the application: who holds which role, whether single sign-on is
|
|
72
|
+
* enforced, what consent was given, how long its data is kept.
|
|
73
|
+
* - `governance-scope:platform-operator` — the platform operator's own reach and obligations, distinct from any one tenant's. Carried only by objectives whose control
|
|
74
|
+
* is exercised above the tenant: cross-tenant administration, the higher-tier repair of a stranded scope, operator-gated economic writes, and the provider secret
|
|
75
|
+
* contract.
|
|
76
|
+
*
|
|
77
|
+
* `capabilityExpectationRefs` is EMPTY on every objective, and that is an answer rather than an omission.
|
|
78
|
+
*
|
|
79
|
+
* It held one invented `capability-expectation:<slug>` per objective until 2026-09-01. Nothing read them — the field has no consumer beyond its own uniqueness
|
|
80
|
+
* refinement — and 44 of the 49 were a mechanical restatement of the objective's own name, which carries no information a reader could not derive. None named a
|
|
81
|
+
* capability that exists: the real vocabulary is `capability:audit-events` and `capability:subject-data-export`, and it lives in the authority basis.
|
|
82
|
+
*
|
|
83
|
+
* The basis is where the objective-to-capability relationship belongs, because it is the thing entitled to say what satisfies an objective, and it is what actually
|
|
84
|
+
* gets read: `parseAssuranceProgramGeneration` stamps an obligation's capability selections from `ASSURANCE_CAPABILITY_AUTHORITIES` and refuses an objective the basis
|
|
85
|
+
* has no expectation for. Two places naming the same relationship is what `CLAUDE.md` forbids; this is the one with no reader.
|
|
86
|
+
*
|
|
87
|
+
* Leave it empty unless something reads it: a record is written only if something or someone actually
|
|
88
|
+
* reads it.
|
|
89
|
+
*
|
|
90
|
+
* `governanceScopeRefs` now RESOLVE. Every entry must be a member of `AssuranceGovernanceScopeKind`, and the objective schema refuses one that is not (#452) — the
|
|
91
|
+
* meaning that used to live in this comment alone lives on the enum's members, which is where a reader meets it. Note they name a KIND: an `AssuranceGovernanceScope`
|
|
92
|
+
* INSTANCE carries boundaries, jurisdictions and one accountable party, all of which are facts about a deployed application, so an application instantiates it and
|
|
93
|
+
* names it from its programme by identity. The framework owns the vocabulary and deliberately instantiates no scope.
|
|
94
|
+
*
|
|
95
|
+
* `capabilityExpectationRefs` is still a forward reference — it becomes resolvable when the compliance-program family acquires a producer; until then, treat a ref
|
|
96
|
+
* there as a claim about meaning rather than a link that can be followed.
|
|
97
|
+
*
|
|
98
|
+
* ## What an `intent` IS, and what it is NOT
|
|
99
|
+
*
|
|
100
|
+
* An intent states the OBJECTIVE — the outcome Wildo holds itself to. It is NOT a claim that the control is implemented, operating, or effective anywhere.
|
|
101
|
+
* Implementation, verification, evidence and assessment status live in an application's assurance PROGRAM (`AssuranceImplementationStatus`,
|
|
102
|
+
* `AssuranceVerificationStatus`, `AssuranceOperatingEvidenceStatus`), never here. Read an intent as "this is what must hold", not "this holds today".
|
|
103
|
+
*
|
|
104
|
+
* That distinction is load-bearing, because these sentences are what a governed document quotes. Quoting an intent as an accomplished fact is exactly the
|
|
105
|
+
* `OPERATING_EFFECTIVENESS_WITHOUT_EVIDENCE` claim the governance claim guards refuse.
|
|
106
|
+
*
|
|
107
|
+
* Two objectives are cited by markers that are OPEN GAPS at some of their sites — `WILDO.IDENTITY.SESSION_ASSURANCE` (privileged access under another
|
|
108
|
+
* identity) and `WILDO.IDENTITY.LIFECYCLE` (consolidating two identities). Both carry `TODO(assurance-control)` in `users.shared.resources-config.schemas.ts`
|
|
109
|
+
* for capabilities that do not exist. Their intents state the objective those capabilities would have to satisfy; they do not describe shipped behaviour.
|
|
110
|
+
*
|
|
111
|
+
* ## How these intents were derived, and how far that has been checked
|
|
112
|
+
*
|
|
113
|
+
* Each intent was written from the PROSE of the `assurance-control:` markers citing that objective — 305 of them — and not from what the objective's name
|
|
114
|
+
* suggests. That is the strength and the limit: a marker's prose is a comment, and a comment can be wrong or stale in ways nothing mechanical detects.
|
|
115
|
+
*
|
|
116
|
+
* **Verification status.** Every intent has been read against the code at a marked site. **31 of the 49 were changed.**
|
|
117
|
+
*
|
|
118
|
+
* `WILDO.ACCESS.PRIVILEGED_REVIEW` was the one exception when that pass ran, because it then carried no code marker at all and this method could not reach it. It
|
|
119
|
+
* carries two now, in `privileged-access-review.backend.utils.ts` and in the application-startup report that calls it, so its intent is reachable by the same
|
|
120
|
+
* method as every other. Read those two blocks before touching it: they are explicit that the framework enumerates the privileged population and does NOT schedule
|
|
121
|
+
* the review, decide it, or retain its outcome.
|
|
122
|
+
*
|
|
123
|
+
* Roughly half of those were WRONG, not merely loose. Two had inverted their subject: the audit evidence-integrity intent described privileged actions on the TRAIL
|
|
124
|
+
* when the markers are about privileged actions on RESOURCES, and the authorization-decision intent said refusals must not disclose what was refused when the stated
|
|
125
|
+
* risk is that recording them must not become an AVAILABILITY risk. One asserted "hidden from every read path" where an audited see-through door exists. One claimed a
|
|
126
|
+
* key-rotation schedule that does not exist. And one — `WILDO.PRIVACY.SUBJECT_DATA_EXPORT`, which predates this catalog pass — still called exports
|
|
127
|
+
* "content-addressed", digest-era language whose mechanism was demolished on 2026-08-23 and which now returns zero hits in the export surface.
|
|
128
|
+
*
|
|
129
|
+
* The other half were UNDERSTATED: the intent was true but named a weaker guarantee than the code gives. Tenant isolation evaluates its predicate INSIDE the search
|
|
130
|
+
* traversal rather than over its results; third-party routing is opt-in by construction with no egress at all by default; an audit actor may never be disguised as an
|
|
131
|
+
* ordinary automated one. An intent that undersells a real control is a defect too — it is what a governed document will quote.
|
|
132
|
+
*
|
|
133
|
+
* Both directions came from the same habit: writing from a marker's FIRST LINE. A truncated comment reads like a complete sentence, and completing it invents the rest.
|
|
134
|
+
* Read the whole block, and the declaration under it — and re-derive marker line numbers before reading by them, since one marker moved 38 lines mid-pass and a
|
|
135
|
+
* read landed on adjacent documentation. When you change what a marked site does, change the intent with it; issue #194 (closed) carries the full defect table.
|
|
136
|
+
*/
|
|
137
|
+
```
|