@wildo-ai/framework-knowledge 1.1.3 → 1.1.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +349 -17
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts +19 -0
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js +47 -1
- package/dist/esm/framework-knowledge.loader.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +125 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +177 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +213 -7
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +326 -8
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +5 -3
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +21 -14
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +57 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +63 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +132 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +179 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +67 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +76 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +5 -4
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +10 -5
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +67 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +82 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +25 -9
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +124 -7
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +67 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +83 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +69 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +71 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +71 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +88 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +97 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +156 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +115 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +152 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +188 -8
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +167 -9
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +171 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +146 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts +248 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js +248 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +157 -4
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +172 -4
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +5 -4
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +8 -7
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +3 -2
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +22 -3
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +5 -3
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +21 -12
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +192 -27
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +172 -33
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +6 -2
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +182 -5
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +191 -5
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +3 -2
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +154 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +214 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +44 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +51 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +2 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +6 -2
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +2 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +7 -3
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +32 -4
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +27 -3
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +4 -2
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +199 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +227 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +5 -3
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +18 -4
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +155 -4
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +187 -4
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +6 -5
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +18 -17
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
- package/dist/knowledge/manifest.json +9 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +75 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
- package/dist/knowledge/playbooks/bottom_up.build/method.md +79 -0
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +65 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +1122 -76
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +49 -13
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +671 -47
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +10 -16
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +31 -35
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -16
- package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +95 -0
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +62 -0
- package/dist/knowledge/playbooks/bottom_up.conception/method.md +80 -0
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +90 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +107 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +70 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +8 -8
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +14 -13
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +165 -0
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +74 -0
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +219 -140
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +55 -22
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +138 -0
- package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +70 -0
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +87 -0
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +69 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +236 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +63 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +116 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +79 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +71 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +70 -0
- package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +83 -0
- package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +68 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +873 -15
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +19 -12
- package/dist/knowledge/playbooks/refinement.document-facts/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.document-facts/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +186 -21
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +12 -16
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +343 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +54 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +28 -11
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -17
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +8 -15
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +25 -49
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +14 -17
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +101 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +209 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +68 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +42 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +39 -12
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +18 -66
- package/dist/knowledge/playbooks/top_down.compliance-research/method.md +78 -0
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +43 -0
- package/dist/knowledge/playbooks/top_down.definition/method.md +103 -0
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +75 -0
- package/dist/knowledge/playbooks/top_down.expert-personas/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +48 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/method.md +51 -165
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +25 -44
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +43 -0
- package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +45 -0
- package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +247 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +71 -0
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/method.md +36 -69
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +12 -9
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +11 -7
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +12 -16
- package/dist/knowledge/playbooks/top_down.risk-register/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.risk-register/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +46 -0
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +59 -0
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +12 -5
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +15 -17
- package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +23 -14
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +12 -17
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +13 -17
- package/dist/knowledge/references/acp.execution-profile.md +266 -0
- package/dist/knowledge/references/acp.host-configuration-inheritance.md +29 -0
- package/dist/knowledge/references/acp.permission-ceiling.md +105 -0
- package/dist/knowledge/references/acp.permission-escalation.md +37 -0
- package/dist/knowledge/references/application-documentation-chapters.config.md +152 -0
- package/dist/knowledge/references/application-documentation-plan.config.md +136 -0
- package/dist/knowledge/references/application-maturity.config.md +319 -0
- package/dist/knowledge/references/assertions.authored-metadata.config.md +1 -1
- package/dist/knowledge/references/assertions.specification.config.md +1 -1
- package/dist/knowledge/references/brand.asset.config.md +8 -16
- package/dist/knowledge/references/brand.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/brand.logo-direction.config.md +9 -7
- package/dist/knowledge/references/brand.snapshot.config.md +16 -2
- package/dist/knowledge/references/brand.snapshot.validation.md +0 -7
- package/dist/knowledge/references/build-plan.task-graph.config.md +581 -7
- package/dist/knowledge/references/business-model.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/business-model.pricing-plan.config.md +1 -1
- package/dist/knowledge/references/business-model.snapshot.validation.md +15 -0
- package/dist/knowledge/references/capability-composition.config.md +155 -0
- package/dist/knowledge/references/cli.market.utils.md +1 -0
- package/dist/knowledge/references/companion.technical-doc.service.md +453 -98
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +21 -0
- package/dist/knowledge/references/engine.client-bundle.external-connectors-public.discipline.md +20 -1
- package/dist/knowledge/references/engine.saas-technical-doc.config.md +8 -4
- package/dist/knowledge/references/engine.saas-website.config.md +22 -10
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +8 -12
- package/dist/knowledge/references/example.config.app-shell.full.md +42 -7
- package/dist/knowledge/references/example.config.backend.required-floors.md +4 -0
- package/dist/knowledge/references/example.config.design-system.full.md +3 -0
- package/dist/knowledge/references/example.engine.product-definitions.feature-and-profiles.md +19 -7
- package/dist/knowledge/references/example.features.connected-feature.declaration.md +66 -0
- package/dist/knowledge/references/example.features.connected-feature.surface.md +42 -0
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +4 -3
- package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +6 -10
- package/dist/knowledge/references/example.guidance.bound-survey-flow.md +82 -0
- package/dist/knowledge/references/example.infra.environment-config.local.md +88 -11
- package/dist/knowledge/references/example.milestones.module-definitions.md +73 -0
- package/dist/knowledge/references/example.minion.contained-tick.md +79 -0
- package/dist/knowledge/references/example.module.companion-exports.full.md +38 -3
- package/dist/knowledge/references/example.provider.backend-module-shape.md +31 -13
- package/dist/knowledge/references/example.provider.frontend-app.module.md +103 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +20 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +7 -3
- package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +30 -0
- package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +11 -0
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +3 -0
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +94 -10
- package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +79 -0
- package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +18 -0
- package/dist/knowledge/references/example.worker.node-route.md +94 -0
- package/dist/knowledge/references/experience-plan.config.md +311 -0
- package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +132 -9
- package/dist/knowledge/references/external-connectors.backend.provider-package-convention.md +36 -0
- package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +269 -0
- package/dist/knowledge/references/integration-plan.config.md +185 -0
- package/dist/knowledge/references/market.alternative.config.md +1 -1
- package/dist/knowledge/references/market.authored-metadata.config.md +12 -9
- package/dist/knowledge/references/market.channel.config.md +3 -3
- package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
- package/dist/knowledge/references/market.gain.config.md +1 -1
- package/dist/knowledge/references/market.icp.config.md +2 -2
- package/dist/knowledge/references/market.job.config.md +1 -1
- package/dist/knowledge/references/market.message-template.config.md +2 -2
- package/dist/knowledge/references/market.objection.config.md +1 -1
- package/dist/knowledge/references/market.pain.config.md +1 -1
- package/dist/knowledge/references/market.persona.config.md +2 -2
- package/dist/knowledge/references/market.proof.config.md +1 -1
- package/dist/knowledge/references/market.snapshot.validation.md +15 -0
- package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
- package/dist/knowledge/references/market.trigger.config.md +1 -1
- package/dist/knowledge/references/minions.tick-contract.md +83 -0
- package/dist/knowledge/references/placement-plan.config.md +369 -0
- package/dist/knowledge/references/platform.config.application-database.md +5 -2
- package/dist/knowledge/references/platform.config.backing-services.md +0 -21
- package/dist/knowledge/references/platform.config.environment.deployment.md +206 -14
- package/dist/knowledge/references/platform.config.infra-provider-resolution.md +170 -0
- package/dist/knowledge/references/platform.config.infrastructure-host.md +87 -0
- package/dist/knowledge/references/platform.config.saas.md +261 -9
- package/dist/knowledge/references/presets.models.labelling.sections.md +14 -0
- package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
- package/dist/knowledge/references/requirements.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/requirements.snapshot.validation.md +15 -0
- package/dist/knowledge/references/roadmap.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/roadmap.snapshot.validation.md +15 -7
- package/dist/knowledge/references/saas.backend.a2a.token-budget.md +71 -0
- package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +1 -2
- package/dist/knowledge/references/saas.backend.auth.federated-identity-provider-private-networks.md +62 -0
- package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +86 -0
- package/dist/knowledge/references/saas.backend.billing.catalog-sync-result.md +37 -0
- package/dist/knowledge/references/saas.backend.billing.resolution-failure-reasons.md +24 -5
- package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +187 -0
- package/dist/knowledge/references/saas.backend.domain-module.md +25 -1
- package/dist/knowledge/references/saas.backend.error-builder.user-guidance.md +82 -0
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +6 -0
- package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +22 -4
- package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +17 -4
- package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +84 -0
- package/dist/knowledge/references/saas.backend.health-readiness-contributor.md +73 -0
- package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +200 -0
- package/dist/knowledge/references/saas.backend.providers.operation-executor.md +51 -0
- package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +71 -0
- package/dist/knowledge/references/saas.backend.queue.worker-topology.md +39 -0
- package/dist/knowledge/references/saas.backend.system-access-service.md +51 -42
- package/dist/knowledge/references/saas.composition.scenario-apply.md +51 -0
- package/dist/knowledge/references/saas.config.content-security-policy.md +97 -0
- package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +91 -21
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +4 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +38 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +27 -27
- package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +65 -16
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +41 -11
- package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +44 -8
- package/dist/knowledge/references/saas.frontend.billing-context.md +108 -0
- package/dist/knowledge/references/saas.frontend.brand-identity.md +38 -0
- package/dist/knowledge/references/saas.frontend.celebration-overlay-contract.md +41 -0
- package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +64 -0
- package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
- package/dist/knowledge/references/saas.frontend.errors.user-facing-error-message.md +47 -0
- package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.per-action-retry-loop.md +7 -1
- package/dist/knowledge/references/saas.frontend.execution-view.definition.md +3 -3
- package/dist/knowledge/references/saas.frontend.flows-actors-view.md +7 -4
- package/dist/knowledge/references/saas.frontend.form-fields.file-provider-constraints.md +30 -48
- package/dist/knowledge/references/saas.frontend.full-custom-view.definition.md +24 -0
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
- package/dist/knowledge/references/saas.frontend.onboarding-view.md +84 -0
- package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +65 -0
- package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
- package/dist/knowledge/references/saas.frontend.resource-header-title.md +28 -4
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +127 -1
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +327 -11
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +198 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +220 -0
- package/dist/knowledge/references/saas.market.generation-agent.md +26 -9
- package/dist/knowledge/references/saas.models.analytics.value-moments.md +132 -0
- package/dist/knowledge/references/saas.models.audit.trail-config.md +155 -0
- package/dist/knowledge/references/saas.models.auth.methods.md +513 -0
- package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +82 -0
- package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +77 -0
- package/dist/knowledge/references/saas.models.config.organization-types.md +192 -0
- package/dist/knowledge/references/saas.models.config.registration.md +188 -0
- package/dist/knowledge/references/saas.models.config.tenant-teardown.md +81 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +173 -3
- package/dist/knowledge/references/saas.models.email.template-type.md +40 -0
- package/dist/knowledge/references/saas.models.engine-capabilities.md +85 -7
- package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +61 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +43 -4
- package/dist/knowledge/references/saas.models.features.definition-builders.md +162 -0
- package/dist/knowledge/references/saas.models.file-upload-grant.md +222 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +54 -5
- package/dist/knowledge/references/saas.models.governed-document-acceptance-mode.md +116 -0
- package/dist/knowledge/references/saas.models.guidance-flow.md +160 -0
- package/dist/knowledge/references/saas.models.http-api-binding.md +76 -110
- package/dist/knowledge/references/saas.models.milestone-celebration.md +69 -0
- package/dist/knowledge/references/saas.models.milestone-definition.md +209 -0
- package/dist/knowledge/references/saas.models.navigation.layout.md +2 -2
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +150 -0
- package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +70 -0
- package/dist/knowledge/references/saas.models.notifications.targets.md +138 -0
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +256 -0
- package/dist/knowledge/references/saas.models.onboarding-elements.md +375 -0
- package/dist/knowledge/references/saas.models.onboarding-trigger.md +52 -0
- package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +50 -0
- package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +129 -0
- package/dist/knowledge/references/saas.models.privacy.client-instance-id-scope.md +49 -0
- package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +106 -0
- package/dist/knowledge/references/saas.models.progression-tracker-variant.md +76 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +8 -5
- package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +72 -0
- package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +50 -0
- package/dist/knowledge/references/saas.models.providers.capability-surface.md +58 -0
- package/dist/knowledge/references/saas.models.providers.compliance-choice.md +111 -0
- package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +156 -0
- package/dist/knowledge/references/saas.models.rate-limit-configuration.md +11 -1
- package/dist/knowledge/references/saas.models.relationship-handling-settings.md +23 -1
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -4
- package/dist/knowledge/references/saas.models.resource-config.forwarded-label.md +5 -4
- package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +69 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +15 -2
- package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +66 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-base.md +24 -1
- package/dist/knowledge/references/saas.models.resource-config.operation-cron-job.md +59 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +55 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +5 -4
- package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +158 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-step-up.md +77 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-for-key.md +6 -1
- package/dist/knowledge/references/saas.models.resource-config.queue-policy.md +49 -0
- package/dist/knowledge/references/saas.models.resource-config.required-features.md +84 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +10 -0
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +14 -0
- package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +111 -4
- package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +39 -0
- package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +48 -0
- package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +38 -0
- package/dist/knowledge/references/saas.models.resource-primary-scope.md +11 -2
- package/dist/knowledge/references/saas.models.scope-membership.md +3 -4
- package/dist/knowledge/references/saas.models.shared-saas-module.md +25 -0
- package/dist/knowledge/references/saas.models.systems-of-record.md +635 -0
- package/dist/knowledge/references/saas.public-runtime.contract.md +198 -1
- package/dist/knowledge/references/saas.rag.retrieval-result.md +19 -8
- package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
- package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +15 -36
- package/dist/knowledge/references/saas.specifications.application-document-publication.contract.md +9 -5
- package/dist/knowledge/references/saas.specifications.application-document-publication.generation.md +63 -0
- package/dist/knowledge/references/saas.specifications.application-document-release-set.contract.md +74 -0
- package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +123 -0
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +88 -7
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +774 -53
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +211 -14
- package/dist/knowledge/references/saas.specifications.composite-view-specification.md +10 -0
- package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +364 -0
- package/dist/knowledge/references/saas.specifications.playbook-approval-and-failure-policies.md +96 -0
- package/dist/knowledge/references/saas.specifications.processor-register.md +333 -0
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +8 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
- package/dist/knowledge/references/saas.website.astro.bridge.md +64 -2
- package/dist/knowledge/references/saas.website.astro.head-renderer.md +32 -12
- package/dist/knowledge/references/saas.website.astro.label-loader.md +3 -0
- package/dist/knowledge/references/saas.website.astro.robots-renderer.md +14 -1
- package/dist/knowledge/references/saas.website.blog.bridge.md +21 -1
- package/dist/knowledge/references/saas.website.consent.banner.md +218 -0
- package/dist/knowledge/references/saas.website.consent.context.md +162 -0
- package/dist/knowledge/references/saas.website.consent.gate.md +38 -0
- package/dist/knowledge/references/saas.website.page-layout.component.md +67 -1
- package/dist/knowledge/references/saas.website.page.context.md +4 -3
- package/dist/knowledge/references/saas.website.runtime.context.md +43 -7
- package/dist/knowledge/references/saas.website.section.context.md +3 -2
- package/dist/knowledge/references/saas.website.sections.category-enum.md +19 -20
- package/dist/knowledge/references/vision.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/website-plan.config.md +205 -0
- package/dist/knowledge/references/workers.node.worker-init-contract.md +57 -0
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +43 -2
- package/dist/knowledge/references/zod.decorators.data-categories.md +197 -0
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +51 -4
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +54 -1
- package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +35 -0
- package/dist/knowledge/references/zod.decorators.field-spec-params.md +32 -5
- package/dist/knowledge/references/zod.decorators.file-nature-constraints.md +86 -0
- package/dist/knowledge/references/zod.decorators.file-readiness-metadata.md +67 -0
- package/dist/knowledge/references/zod.decorators.file-schema.md +90 -14
- package/dist/knowledge/references/zod.decorators.file-vocabularies.md +84 -0
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +140 -4
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
- package/dist/knowledge/references/zod.decorators.rag-source.md +6 -2
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +24 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +35 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +46 -12
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +31 -12
- package/dist/knowledge/references/zod.factories.address.md +118 -0
- package/dist/knowledge/references/zod.factories.code.md +2 -0
- package/dist/knowledge/references/zod.factories.duration.md +2 -0
- package/dist/knowledge/references/zod.factories.money.md +2 -0
- package/dist/knowledge/references/zod.factories.phone.md +14 -1
- package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
- package/dist/knowledge/registries/framework-topics.json +1215 -11
- package/dist/knowledge/registries/playbooks.json +454 -50
- package/dist/knowledge/registries/source-tags.json +3153 -1043
- package/dist/knowledge/rules/database-migration-obligation.md +110 -0
- package/dist/knowledge/rules/live-context-door.md +108 -0
- package/dist/knowledge/rules/resource-schema-awareness.md +75 -0
- package/dist/knowledge/skills/INDEX.md +46 -11
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +80 -37
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +167 -0
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +6 -3
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -3
- package/dist/knowledge/skills/application-database-migrations/references/framework-application-database-api.md +5 -2
- package/dist/knowledge/skills/application-database-migrations/references/migration-refusals.md +32 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +94 -3
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +50 -0
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +26 -19
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +25 -1
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-readiness-contributor-api.md +135 -0
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +75 -12
- package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +137 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-error-user-guidance-api.md +112 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +72 -1
- package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +207 -0
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +31 -1
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-asset-api.md +8 -16
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +25 -9
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +135 -5
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +80 -17
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +369 -111
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +32 -10
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +103 -58
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-publication-contract.md +19 -13
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +142 -26
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +722 -23
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +348 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +123 -0
- package/dist/knowledge/skills/config-app-shell/SKILL.md +74 -11
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +85 -19
- package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +70 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +43 -3
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
- package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
- package/dist/knowledge/skills/config-design-system/references/surface-policy-authoring.md +19 -10
- package/dist/knowledge/skills/config-navigation/SKILL.md +85 -2
- package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +2 -2
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +172 -0
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +146 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +141 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +86 -9
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +199 -0
- package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +179 -0
- package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +493 -0
- package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +153 -0
- package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +242 -0
- package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +161 -0
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +93 -12
- package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +785 -0
- package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +172 -0
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +261 -9
- package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +9 -0
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +58 -3
- package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +151 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-auth-methods-api.md +579 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +8 -2
- package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +96 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +316 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-registration-config-api.md +221 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +121 -0
- package/dist/knowledge/skills/config-saas-backend/references/managed-startup-configuration.md +46 -0
- package/dist/knowledge/skills/configure-billing/SKILL.md +27 -22
- package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +27 -15
- package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +41 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +36 -17
- package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +30 -28
- package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +169 -0
- package/dist/knowledge/skills/configure-billing/references/framework-billing-resolution-failure-api.md +44 -11
- package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +187 -0
- package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +76 -0
- package/dist/knowledge/skills/configure-coding-agent/SKILL.md +280 -0
- package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +168 -0
- package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +504 -0
- package/dist/knowledge/skills/email-add-template/SKILL.md +41 -69
- package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +15 -7
- package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +120 -0
- package/dist/knowledge/skills/engine-component-registration/SKILL.md +19 -12
- package/dist/knowledge/skills/engine-product-definitions/SKILL.md +54 -31
- package/dist/knowledge/skills/engine-product-definitions/references/connected-feature-workflow.md +130 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-engine-product-definitions-api.md +25 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-feature-builders-api.md +215 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +78 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +33 -24
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +121 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -8
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +5 -4
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +46 -9
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +34 -7
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +151 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +6 -10
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +54 -5
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +75 -21
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +258 -0
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +480 -0
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +3983 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +211 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +165 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-elements-api.md +381 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-trigger-api.md +57 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-view-api.md +89 -0
- package/dist/knowledge/skills/i18n-label-generation/SKILL.md +13 -1
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +14 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +14 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +3 -1
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +14 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +237 -37
- package/dist/knowledge/skills/infra-environment-config/references/framework-application-database-api.md +5 -2
- package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +174 -21
- package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +206 -14
- package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +95 -0
- package/dist/knowledge/skills/journey-approve/SKILL.md +28 -8
- package/dist/knowledge/skills/journey-approve/references/specification-family-map.md +88 -0
- package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +37 -2
- package/dist/knowledge/skills/journey-next/SKILL.md +41 -1
- package/dist/knowledge/skills/journey-report/SKILL.md +16 -3
- package/dist/knowledge/skills/journey-run/SKILL.md +92 -7
- package/dist/knowledge/skills/journey-run/references/expert-personas-and-deliberations.md +46 -0
- package/dist/knowledge/skills/journey-run/references/framework-playbook-approval-policy.md +108 -0
- package/dist/knowledge/skills/journey-status/SKILL.md +14 -4
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +153 -46
- package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +119 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/initialization-recovery-recipe.md +7 -4
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +253 -33
- package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +1 -1
- package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
- package/dist/knowledge/skills/market-alternatives/SKILL.md +1 -1
- package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +12 -9
- package/dist/knowledge/skills/market-channels/SKILL.md +3 -3
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +226 -14
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +226 -14
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +56 -9
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +32 -9
- package/dist/knowledge/skills/market-icp/SKILL.md +2 -2
- package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +3 -3
- package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -2
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +17 -2
- package/dist/knowledge/skills/market-persona/SKILL.md +2 -2
- package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +2 -2
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -0
- package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +15 -0
- package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +1 -1
- package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +1 -1
- package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +198 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-celebration-overlay-contract.md +51 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-celebration-api.md +79 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-definition-api.md +220 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-progression-tracker-api.md +86 -0
- package/dist/knowledge/skills/minion-authoring/SKILL.md +140 -0
- package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +84 -0
- package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +91 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +38 -3
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +211 -14
- package/dist/knowledge/skills/module-registration/SKILL.md +50 -33
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +50 -1
- package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +142 -0
- package/dist/knowledge/skills/module-registration/references/registry-files.md +14 -5
- package/dist/knowledge/skills/module-relationships/SKILL.md +62 -0
- package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +26 -5
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +279 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +80 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +55 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-convention-api.md +48 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +33 -6
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-file-provider-constraints-api.md +99 -47
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +241 -9
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +196 -0
- package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +50 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +80 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +71 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +58 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +275 -0
- package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +64 -11
- package/dist/knowledge/skills/rate-limit-authoring/references/fixed-window-and-environment-multiplier.md +27 -0
- package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +19 -6
- package/dist/knowledge/skills/resource-add-field/SKILL.md +12 -5
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +373 -23
- package/dist/knowledge/skills/resource-add-module/SKILL.md +116 -265
- package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +133 -0
- package/dist/knowledge/skills/resource-add-module/references/framework-new-module-wiring-api.md +25 -0
- package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +12 -12
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +26 -3
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +122 -4
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +25 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +93 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +136 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +85 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +133 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +141 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-step-up-api.md +126 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +859 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +122 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +124 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +97 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +457 -15
- package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +197 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +162 -46
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +452 -0
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +5 -0
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +327 -11
- package/dist/knowledge/skills/resource-custom-view/references/framework-user-facing-error-message-api.md +50 -0
- package/dist/knowledge/skills/resource-external-data/SKILL.md +228 -15
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +54 -7
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +87 -113
- package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +13 -8
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +69 -26
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +246 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +7 -6
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +5 -3
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +43 -48
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +96 -14
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +47 -15
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +6 -2
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +32 -2
- package/dist/knowledge/skills/resource-schema-authoring/examples/basic-resource-schema.example.md +2 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +17 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +75 -4
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +182 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +245 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +35 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +46 -12
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +480 -15
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +67 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +74 -14
- package/dist/knowledge/skills/resource-schema-authoring/references/polymorphic-per-scope-resources.md +28 -5
- package/dist/knowledge/skills/resource-schema-authoring/references/schema-variants-and-discriminators.md +25 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +34 -0
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +236 -18
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +54 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +35 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +327 -11
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +140 -4
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +155 -5
- package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +165 -0
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +9 -1
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +4 -0
- package/dist/knowledge/skills/seeding-operations/SKILL.md +33 -29
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +13 -5
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-cron-scheduler.md +67 -74
- package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +97 -24
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +205 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +205 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +229 -0
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +38 -3
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +211 -14
- package/dist/knowledge/skills/spec-component-update/SKILL.md +30 -11
- package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +10 -0
- package/dist/knowledge/skills/spec-feature-update/SKILL.md +47 -9
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +3 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +32 -5
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +30 -0
- package/dist/knowledge/skills/views-add-composite-view/SKILL.md +1 -0
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +13 -2
- package/dist/knowledge/skills/views-add-custom-view/references/framework-view-scope-and-full-custom-api.md +24 -0
- package/dist/knowledge/skills/views-app-level/SKILL.md +1 -0
- package/dist/knowledge/skills/views-app-level/references/framework-view-scope-and-full-custom-api.md +24 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +64 -0
- package/dist/knowledge/skills/views-execution-authoring/SKILL.md +3 -0
- package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +3 -3
- package/dist/knowledge/skills/views-execution-authoring/references/framework-user-facing-error-message-api.md +50 -0
- package/dist/knowledge/skills/website-anonymous-session/SKILL.md +43 -7
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +21 -1
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +21 -0
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +41 -1
- package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +735 -211
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +54 -7
- package/dist/knowledge/skills/website-layout-overrides/SKILL.md +67 -1
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -0
- package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +19 -5
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +94 -7
- package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +126 -0
- package/dist/knowledge/skills/website-section-contact/SKILL.md +96 -146
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-cta/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-faq/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-hero/SKILL.md +37 -26
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +14 -1
- package/dist/knowledge/skills/worker-authoring/SKILL.md +164 -0
- package/dist/knowledge/skills/worker-authoring/examples/worker-route.example.md +98 -0
- package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +65 -0
- package/dist/knowledge/topic-index.json +5335 -1010
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/knowledge/references/example.provider.contribution.backend-billing.md +0 -12
- package/dist/knowledge/skills/configure-billing/references/example-provider-contribution-and-backend-config.md +0 -48
- /package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/structured-artifact-action.json +0 -0
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
# Top-Down
|
|
1
|
+
# Top-Down Coherence Assessment
|
|
2
2
|
|
|
3
3
|
### Target Application Framing
|
|
4
4
|
|
|
@@ -14,83 +14,50 @@ Read and apply these patterns from the application-developer point of view:
|
|
|
14
14
|
|
|
15
15
|
## Purpose
|
|
16
16
|
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
17
|
+
Assess whether the current top-down definitions agree well enough to guide the next
|
|
18
|
+
work. This playbook writes no application specification and accepts nothing. It can
|
|
19
|
+
be rerun after the working definitions change.
|
|
20
20
|
|
|
21
|
-
|
|
22
|
-
application-feature, requirements, vision, or roadmap state may invalidate
|
|
23
|
-
earlier evidence and make the decision point eligible again.
|
|
21
|
+
## Readiness and inputs
|
|
24
22
|
|
|
25
|
-
|
|
23
|
+
Use `journey-status` to inspect the loaded specification values. `vision-brief`,
|
|
24
|
+
`market-snapshot`, `requirements` and `roadmap` must each pass their declared
|
|
25
|
+
family-validity precondition. A cross-family assessment cannot replace that validation.
|
|
26
26
|
|
|
27
|
-
|
|
27
|
+
The evaluator reads those families plus `feature-drafts` and `business-model` when
|
|
28
|
+
present. These optional inputs add implementation and commercial context; their
|
|
29
|
+
absence does not introduce another readiness gate. The runtime loads the exported
|
|
30
|
+
working-tree values. There is no evidence-sealing step or accepted-head projection.
|
|
28
31
|
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
valid. This floor is non-bypassable.
|
|
33
|
-
2. The compiled Evaluation Protocol interprets cross-family coherence from an
|
|
34
|
-
exact sealed evidence set. It cannot make an invalid family valid or replace
|
|
35
|
-
missing evidence with an assumption.
|
|
36
|
-
|
|
37
|
-
The canonical criterion instructions, evidence identities, verdict guidance,
|
|
38
|
-
prompt-assembly strategy, and aggregation precedence live in
|
|
39
|
-
`playbook.definition.ts`. This method explains how to operate the treatment; it
|
|
40
|
-
does not duplicate that executable meaning.
|
|
41
|
-
|
|
42
|
-
## Evidence preparation
|
|
43
|
-
|
|
44
|
-
Use `journey-status` to identify the current accepted heads for:
|
|
45
|
-
|
|
46
|
-
- `vision-brief`
|
|
47
|
-
- `market-snapshot`
|
|
48
|
-
- `requirements`
|
|
49
|
-
- `roadmap`
|
|
50
|
-
- `feature-drafts`
|
|
51
|
-
|
|
52
|
-
Project only the accepted, current-horizon data required by the five protocol
|
|
53
|
-
criteria. Seal the projected artifacts and their provenance before evaluation.
|
|
54
|
-
If the evidence projection cannot account for a mandatory requirement, request
|
|
55
|
-
evidence; do not invoke the evaluator on an incomplete set.
|
|
56
|
-
|
|
57
|
-
Business model is not an input to this treatment version and must not be loaded
|
|
58
|
-
into its knowledge projection. A later treatment version may add a distinct
|
|
59
|
-
business-model criterion when the structured family contracts can support it
|
|
60
|
-
without prose-only inference.
|
|
32
|
+
The computed coherence report (the declared `coherence_report` context section of your brief) supplies the
|
|
33
|
+
supported dangling-reference and coverage checks. Interpret their consequences;
|
|
34
|
+
do not invent checks or recompute the arithmetic in prose.
|
|
61
35
|
|
|
62
36
|
## Evaluation
|
|
63
37
|
|
|
64
|
-
The
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
Aggregation uses the protocol’s declared worst-verdict precedence:
|
|
69
|
-
|
|
70
|
-
`GAP` → `INDETERMINATE` → `CONCERN` → `PASS`
|
|
71
|
-
|
|
72
|
-
`INDETERMINATE` means that the available evidence is missing, conflicting, or
|
|
73
|
-
too uncertain to decide. A transport, model, timeout, or output-validation
|
|
74
|
-
failure is an evaluator failure and blocks the treatment; it is never rewritten
|
|
75
|
-
as semantic uncertainty.
|
|
38
|
+
The compiled evaluation treatment supplies the criteria and their guidance. For each
|
|
39
|
+
criterion, relate the verdict to the available evidence and explain what should change.
|
|
40
|
+
Use `INDETERMINATE` when evidence does not support a semantic conclusion.
|
|
76
41
|
|
|
77
|
-
|
|
42
|
+
The current judge aggregates by worst severity:
|
|
43
|
+
`GAP` → `INDETERMINATE` → `CONCERN` → `PASS`.
|
|
44
|
+
Duplicate criterion results retain the worst verdict and all their rationales. Missing
|
|
45
|
+
criterion results remain indeterminate. The treatment's declarative policy fields do
|
|
46
|
+
not independently create another approval or continuation workflow in this runner.
|
|
78
47
|
|
|
79
|
-
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
- a hard-floor failure or evaluator failure blocks.
|
|
48
|
+
A failed model call or unusable treatment produces a skipped/unavailable judge result
|
|
49
|
+
(`judged: false` with `skipped`), not a semantic pass. Check that status before using
|
|
50
|
+
any verdict as evidence that assessment happened.
|
|
83
51
|
|
|
84
|
-
|
|
85
|
-
membrane. Human authorization of the top-down → bottom-up transition remains a
|
|
86
|
-
separate, explicit boundary and must not be inferred from a passing semantic
|
|
87
|
-
assessment. Use `journey-report` to surface the assessment and
|
|
88
|
-
`journey-approve` only when the authority workflow is active.
|
|
52
|
+
## Read the result and decide what to do
|
|
89
53
|
|
|
90
|
-
|
|
54
|
+
The response reports `assessed: true`, the loaded `subjects`, a `reviewGuide`, the
|
|
55
|
+
judge result when supplied, and `accepted: false`. The judge is advisory: this call
|
|
56
|
+
does not automatically revise families, request authority, switch phases or block a
|
|
57
|
+
transition based on its verdict. Use the findings to choose the next work and review
|
|
58
|
+
its outcome through the application's actual workflow.
|
|
91
59
|
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
|
|
96
|
-
assessment basis.
|
|
60
|
+
This invocation performs one assessment. Do not infer enforced revision or
|
|
61
|
+
additional-evidence loops from the playbook's declared budget or continuation fields.
|
|
62
|
+
When an input changes, reassess the new values rather than treating an old verdict as
|
|
63
|
+
proof about the changed product.
|
|
@@ -2,13 +2,8 @@
|
|
|
2
2
|
"ref": "top_down.phase-gate",
|
|
3
3
|
"version": "0.2.0",
|
|
4
4
|
"phase": "top_down",
|
|
5
|
-
"intent": "Assess whether the validated top-down definition set is cross-artifact coherent enough for the current horizon. Deterministic family validation remains a non-bypassable eligibility floor; this playbook contributes
|
|
6
|
-
"functionalTopics": [],
|
|
5
|
+
"intent": "Assess whether the validated top-down definition set is cross-artifact coherent enough for the current horizon. Deterministic family validation remains a non-bypassable eligibility floor; this playbook contributes an advisory semantic evaluation and never mutates application truth.",
|
|
7
6
|
"preconditions": [
|
|
8
|
-
{
|
|
9
|
-
"kind": "phase_is",
|
|
10
|
-
"phase": "top_down"
|
|
11
|
-
},
|
|
12
7
|
{
|
|
13
8
|
"kind": "artifact_valid",
|
|
14
9
|
"selector": {
|
|
@@ -55,16 +50,24 @@
|
|
|
55
50
|
}
|
|
56
51
|
],
|
|
57
52
|
"outputs": [],
|
|
53
|
+
"stepOutputs": [],
|
|
58
54
|
"method": {
|
|
59
|
-
"guidance": "# Top-Down
|
|
55
|
+
"guidance": "# Top-Down Coherence Assessment\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## Purpose\n\nAssess whether the current top-down definitions agree well enough to guide the next\nwork. This playbook writes no application specification and accepts nothing. It can\nbe rerun after the working definitions change.\n\n## Readiness and inputs\n\nUse `journey-status` to inspect the loaded specification values. `vision-brief`,\n`market-snapshot`, `requirements` and `roadmap` must each pass their declared\nfamily-validity precondition. A cross-family assessment cannot replace that validation.\n\nThe evaluator reads those families plus `feature-drafts` and `business-model` when\npresent. These optional inputs add implementation and commercial context; their\nabsence does not introduce another readiness gate. The runtime loads the exported\nworking-tree values. There is no evidence-sealing step or accepted-head projection.\n\nThe computed coherence report (the declared `coherence_report` context section of your brief) supplies the\nsupported dangling-reference and coverage checks. Interpret their consequences;\ndo not invent checks or recompute the arithmetic in prose.\n\n## Evaluation\n\nThe compiled evaluation treatment supplies the criteria and their guidance. For each\ncriterion, relate the verdict to the available evidence and explain what should change.\nUse `INDETERMINATE` when evidence does not support a semantic conclusion.\n\nThe current judge aggregates by worst severity:\n`GAP` → `INDETERMINATE` → `CONCERN` → `PASS`.\nDuplicate criterion results retain the worst verdict and all their rationales. Missing\ncriterion results remain indeterminate. The treatment's declarative policy fields do\nnot independently create another approval or continuation workflow in this runner.\n\nA failed model call or unusable treatment produces a skipped/unavailable judge result\n(`judged: false` with `skipped`), not a semantic pass. Check that status before using\nany verdict as evidence that assessment happened.\n\n## Read the result and decide what to do\n\nThe response reports `assessed: true`, the loaded `subjects`, a `reviewGuide`, the\njudge result when supplied, and `accepted: false`. The judge is advisory: this call\ndoes not automatically revise families, request authority, switch phases or block a\ntransition based on its verdict. Use the findings to choose the next work and review\nits outcome through the application's actual workflow.\n\nThis invocation performs one assessment. Do not infer enforced revision or\nadditional-evidence loops from the playbook's declared budget or continuation fields.\nWhen an input changes, reassess the new values rather than treating an old verdict as\nproof about the changed product.\n",
|
|
60
56
|
"skillRefs": [
|
|
61
57
|
"journey-status",
|
|
62
58
|
"journey-report",
|
|
63
59
|
"journey-approve"
|
|
64
|
-
]
|
|
60
|
+
],
|
|
61
|
+
"skillBodyRefs": [],
|
|
62
|
+
"contextSources": [
|
|
63
|
+
"coherence_report"
|
|
64
|
+
],
|
|
65
|
+
"draftableDocumentDefinitionRefs": [],
|
|
66
|
+
"suspendsForClarification": false,
|
|
67
|
+
"briefAdequacyGate": false,
|
|
68
|
+
"briefAdequacyExcludedSources": []
|
|
65
69
|
},
|
|
66
70
|
"executor": "companion_agent",
|
|
67
|
-
"qualityGates": [],
|
|
68
71
|
"approval": "approve_result",
|
|
69
72
|
"budget": {
|
|
70
73
|
"maxRuns": 3
|
|
@@ -44,10 +44,14 @@ The deterministic minimum-content finding and semantic coherence evaluation are
|
|
|
44
44
|
separate contributions. Application composition selects exactly one bounded
|
|
45
45
|
next action from hard floors, scoped risk, maturity, uncertainty, active
|
|
46
46
|
resource authority and playbook bounds. A model may explain a proposal but it
|
|
47
|
-
cannot override a hard floor
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
47
|
+
cannot override a hard floor or rewrite accepted truth: it writes files into the
|
|
48
|
+
working tree and nothing more. Acceptance is a git commit: under the current
|
|
49
|
+
autonomy posture the development companion commits a run's writes before the
|
|
50
|
+
next build task starts, and a person reads the history and reverts what they
|
|
51
|
+
disagree with. A protected consequence is MARKED: under this posture it notifies
|
|
52
|
+
and proceeds, and it holds for an operator decision only once gates are armed.
|
|
53
|
+
|
|
54
|
+
Git is not a later materialization of an acceptance that happened somewhere else
|
|
55
|
+
— it IS the acceptance. Replacing accepted application requirements therefore
|
|
56
|
+
means committing over them, with the commit's author and instant standing as who
|
|
57
|
+
accepted and when.
|
|
@@ -3,12 +3,7 @@
|
|
|
3
3
|
"version": "0.1.0",
|
|
4
4
|
"phase": "top_down",
|
|
5
5
|
"intent": "Derive a validated, current-horizon requirements snapshot from accepted vision and market truth. The provider proposes strict semantic content; the trusted runtime stamps family refs/version and keeps provenance, scope, evidence and authority outside model output.",
|
|
6
|
-
"functionalTopics": [],
|
|
7
6
|
"preconditions": [
|
|
8
|
-
{
|
|
9
|
-
"kind": "phase_is",
|
|
10
|
-
"phase": "top_down"
|
|
11
|
-
},
|
|
12
7
|
{
|
|
13
8
|
"kind": "artifact_valid",
|
|
14
9
|
"selector": {
|
|
@@ -29,32 +24,33 @@
|
|
|
29
24
|
{
|
|
30
25
|
"family": "market-snapshot",
|
|
31
26
|
"intent": "value"
|
|
27
|
+
},
|
|
28
|
+
{
|
|
29
|
+
"family": "requirements"
|
|
32
30
|
}
|
|
33
31
|
],
|
|
34
32
|
"outputs": [
|
|
35
33
|
{
|
|
36
34
|
"family": "requirements",
|
|
37
35
|
"schemaRef": "saas-specifications:RequirementsSnapshot",
|
|
38
|
-
"placement": ".wildo-saas/journey/<journeyId>/requirements/",
|
|
39
36
|
"description": "The persisted RequirementsSnapshot normalized from strict RequirementsSnapshotGeneration output. It contains at least one functional requirement unless a separately sealed, evidence-bound exceptional disposition has settled authority."
|
|
40
37
|
}
|
|
41
38
|
],
|
|
39
|
+
"stepOutputs": [],
|
|
42
40
|
"method": {
|
|
43
|
-
"guidance": "# Requirements definition method\n\nProduce the current-horizon requirements family from the accepted\n`vision-brief` and `market-snapshot` heads. Treat those accepted projections as\nthe only application truth: conversational context may clarify them, but it\ncannot silently replace or amend them.\n\nThe provider response must parse as\n`RequirementsSnapshotGenerationSchema`. It supplies semantic slugs, statements,\nrationales, acceptance criteria and declared market cross-references. The\ntrusted structured-artifact runtime stamps the canonical requirement refs and\nsnapshot version, validates the permissive persisted `RequirementsSnapshot`,\nand records its exact input/output/evidence lineage. Provider output must not\ncontain timestamps, author identity, authority, accepted scope, family heads or\ncontinuity identifiers.\n\nNormal generation must produce at least one functional requirement. An empty\nfunctional set is not “good enough,” even though the incremental family schema\ncan persist it and `validateRequirementsSnapshot` reports only a warning. The\nrequirements playbook emits the deterministic `requirements-minimum-content`\nfinding into semantic assessment: it explains the missing minimum and requires\nrevision or evidence, but it never grants an evaluator or a model permission to\noverride that protected consequence.\n\nFor every functional requirement:\n\n- state one distinct product capability, not an implementation task;\n- connect it to accepted vision or market evidence;\n- keep current-horizon scope explicit; and\n- provide observable acceptance language where meaningful.\n\nFor every non-functional requirement, preserve the declared quality axis and\nmeasurement intent. Do not invent regulatory applicability. Missing or\ncontradictory accepted evidence yields a request for evidence or revision, not\na plausible completion.\n\nContext selection receives current accepted vision and market heads, the\nworking requirements candidate, and declared Framework guidance as structured\ndata. Missing mandatory context is explicit; retrieved instruction-shaped text\nis treated as data and excluded from coding-task projection. Optional context\nis bounded by the declared selection plan rather than by ad-hoc prompt growth.\n\nThe deterministic minimum-content finding and semantic coherence evaluation are\nseparate contributions. Application composition selects exactly one bounded\nnext action from hard floors, scoped risk, maturity, uncertainty, active\nresource authority and playbook bounds. A model may explain a proposal but it\ncannot override a hard floor
|
|
41
|
+
"guidance": "# Requirements definition method\n\nProduce the current-horizon requirements family from the accepted\n`vision-brief` and `market-snapshot` heads. Treat those accepted projections as\nthe only application truth: conversational context may clarify them, but it\ncannot silently replace or amend them.\n\nThe provider response must parse as\n`RequirementsSnapshotGenerationSchema`. It supplies semantic slugs, statements,\nrationales, acceptance criteria and declared market cross-references. The\ntrusted structured-artifact runtime stamps the canonical requirement refs and\nsnapshot version, validates the permissive persisted `RequirementsSnapshot`,\nand records its exact input/output/evidence lineage. Provider output must not\ncontain timestamps, author identity, authority, accepted scope, family heads or\ncontinuity identifiers.\n\nNormal generation must produce at least one functional requirement. An empty\nfunctional set is not “good enough,” even though the incremental family schema\ncan persist it and `validateRequirementsSnapshot` reports only a warning. The\nrequirements playbook emits the deterministic `requirements-minimum-content`\nfinding into semantic assessment: it explains the missing minimum and requires\nrevision or evidence, but it never grants an evaluator or a model permission to\noverride that protected consequence.\n\nFor every functional requirement:\n\n- state one distinct product capability, not an implementation task;\n- connect it to accepted vision or market evidence;\n- keep current-horizon scope explicit; and\n- provide observable acceptance language where meaningful.\n\nFor every non-functional requirement, preserve the declared quality axis and\nmeasurement intent. Do not invent regulatory applicability. Missing or\ncontradictory accepted evidence yields a request for evidence or revision, not\na plausible completion.\n\nContext selection receives current accepted vision and market heads, the\nworking requirements candidate, and declared Framework guidance as structured\ndata. Missing mandatory context is explicit; retrieved instruction-shaped text\nis treated as data and excluded from coding-task projection. Optional context\nis bounded by the declared selection plan rather than by ad-hoc prompt growth.\n\nThe deterministic minimum-content finding and semantic coherence evaluation are\nseparate contributions. Application composition selects exactly one bounded\nnext action from hard floors, scoped risk, maturity, uncertainty, active\nresource authority and playbook bounds. A model may explain a proposal but it\ncannot override a hard floor or rewrite accepted truth: it writes files into the\nworking tree and nothing more. Acceptance is a git commit: under the current\nautonomy posture the development companion commits a run's writes before the\nnext build task starts, and a person reads the history and reverts what they\ndisagree with. A protected consequence is MARKED: under this posture it notifies\nand proceeds, and it holds for an operator decision only once gates are armed.\n\nGit is not a later materialization of an acceptance that happened somewhere else\n— it IS the acceptance. Replacing accepted application requirements therefore\nmeans committing over them, with the commit's author and instant standing as who\naccepted and when.\n",
|
|
44
42
|
"skillRefs": [
|
|
45
43
|
"journey-status",
|
|
46
44
|
"journey-report"
|
|
47
|
-
]
|
|
45
|
+
],
|
|
46
|
+
"skillBodyRefs": [],
|
|
47
|
+
"contextSources": [],
|
|
48
|
+
"draftableDocumentDefinitionRefs": [],
|
|
49
|
+
"suspendsForClarification": false,
|
|
50
|
+
"briefAdequacyGate": false,
|
|
51
|
+
"briefAdequacyExcludedSources": []
|
|
48
52
|
},
|
|
49
53
|
"executor": "companion_agent",
|
|
50
|
-
"qualityGates": [
|
|
51
|
-
{
|
|
52
|
-
"ref": "requirements-snapshot-valid",
|
|
53
|
-
"kind": "deterministic_validator",
|
|
54
|
-
"validatorRef": "saas-specifications:validateRequirementsSnapshot",
|
|
55
|
-
"required": true
|
|
56
|
-
}
|
|
57
|
-
],
|
|
58
54
|
"approval": "approve_result",
|
|
59
55
|
"budget": {
|
|
60
56
|
"maxInputTokens": 15000000,
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"aggregationPolicyRef":"application-creation:aggregation/worst-risk-register-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/risk-register-arguable-statements-and-grounded-weighting","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/risk-register-arguable-statements-and-grounded-weighting","requirementVersion":1}],"instruction":"Determine whether each statement is one a reader can argue with in this application's own terms (naming the providers, fields, operations or users concerned) rather than a truism, and whether likelihood and impact are qualitative bands grounded in what is IMPLEMENTED, with no score, rating or product anywhere. Where the application declares a posture the measurement contradicts, the contradiction is noted in the weighting grounding, not resolved.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Statements are specific but a band's grounding would be equally true of any application, or a declared-posture contradiction is noted only weakly.","GAP":"A truistic statement, a band grounded in how the risk sounds, a score or rating, or a posture contradiction silently resolved.","INDETERMINATE":"The register's entries are not in evidence.","PASS":"Every statement is checkable and specific, every band is grounded in the implementation, and no number is multiplied."}},{"criterionRef":"application-creation:criterion/risk-register-boundary-with-other-mechanisms","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/risk-register-boundary-with-other-mechanisms","requirementVersion":1}],"instruction":"Determine whether the register stays a register: it binds no control objective, asserts no control as discharged, writes no audit plan, and neither restates nor contradicts configuration the application already declares (retention periods, provider deployment choices, jurisdictions).","schemaVersion":1,"verdictGuidance":{"CONCERN":"An entry mentions a control or a configured value in a way that reads as a decision rather than a reference.","GAP":"An entry binds a control, claims discharge, prescribes audit depth, or contradicts a declared configuration.","INDETERMINATE":"The application's declarations are not in evidence, so contradictions cannot be checked.","PASS":"Every entry states a risk and nothing more."}},{"criterionRef":"application-creation:criterion/risk-register-entry-origin-honesty","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/risk-register-entry-origin-honesty","requirementVersion":1}],"instruction":"Determine whether every entry's origin is honest: a SIGNAL_DERIVED entry names the derived signal it was completed from, one entry per signal; a PROPOSED entry is grounded in the vision, the business model or the market snapshot and is never anchored to a signal; and when signals were not supplied to the run, the register states plainly that the derived half is absent rather than treating an absent measurement as an absent risk.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Origins are honest but a proposed entry's grounding is generic, or the absent-derivation statement is buried.","GAP":"A proposed entry anchored to a signal, a derived entry naming no signal, an entry grounded in nothing, or a register that silently omits the derived half.","INDETERMINATE":"The vision, business model or market snapshot are not in evidence, so grounding cannot be checked.","PASS":"Every derived entry names its signal, every proposed entry is grounded in an authored family, and an absent derivation is stated."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/risk-register","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.risk-register"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-risk-register","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/risk-register-arguable-statements-and-grounded-weighting"],"requirementRef":"application-creation:authority-requirement/risk-register-result","requirementVersion":1,"riskClassRef":"application-creation:risk/risk-register-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/risk-register","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/risk-register-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/risk-register","policyVersion":1},"decisionPointRef":"application-creation:decision-point/risk-register-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/risk-register-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/risk-register","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/risk-register-arguable-statements-and-grounded-weighting","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/risk-register-boundary-with-other-mechanisms","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/risk-register-entry-origin-honesty","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/risk-register-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-risk-register-change","triggerRefs":["application-creation:trigger/risk-register-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-risk-register-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/risk-register-entry-origin-honesty"],"hardFloorRef":"application-creation:hard-floor/risk-register-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/risk-register-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/risk-register","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-risk-register-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/risk-register-arguable-statements-and-grounded-weighting","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/risk-register-arguable-statements-and-grounded-weighting","requirementVersion":1}],"instruction":"Determine whether each statement is one a reader can argue with in this application's own terms (naming the providers, fields, operations or users concerned) rather than a truism, and whether likelihood and impact are qualitative bands grounded in what is IMPLEMENTED, with no score, rating or product anywhere. Where the application declares a posture the measurement contradicts, the contradiction is noted in the weighting grounding, not resolved.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Statements are specific but a band's grounding would be equally true of any application, or a declared-posture contradiction is noted only weakly.","GAP":"A truistic statement, a band grounded in how the risk sounds, a score or rating, or a posture contradiction silently resolved.","INDETERMINATE":"The register's entries are not in evidence.","PASS":"Every statement is checkable and specific, every band is grounded in the implementation, and no number is multiplied."}},{"criterionRef":"application-creation:criterion/risk-register-boundary-with-other-mechanisms","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/risk-register-boundary-with-other-mechanisms","requirementVersion":1}],"instruction":"Determine whether the register stays a register: it binds no control objective, asserts no control as discharged, writes no audit plan, and neither restates nor contradicts configuration the application already declares (retention periods, provider deployment choices, jurisdictions).","schemaVersion":1,"verdictGuidance":{"CONCERN":"An entry mentions a control or a configured value in a way that reads as a decision rather than a reference.","GAP":"An entry binds a control, claims discharge, prescribes audit depth, or contradicts a declared configuration.","INDETERMINATE":"The application's declarations are not in evidence, so contradictions cannot be checked.","PASS":"Every entry states a risk and nothing more."}},{"criterionRef":"application-creation:criterion/risk-register-entry-origin-honesty","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/risk-register-entry-origin-honesty","requirementVersion":1}],"instruction":"Determine whether every entry's origin is honest: a SIGNAL_DERIVED entry names the derived signal it was completed from, one entry per signal; a PROPOSED entry is grounded in the vision, the business model or the market snapshot and is never anchored to a signal; and when signals were not supplied to the run, the register states plainly that the derived half is absent rather than treating an absent measurement as an absent risk.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Origins are honest but a proposed entry's grounding is generic, or the absent-derivation statement is buried.","GAP":"A proposed entry anchored to a signal, a derived entry naming no signal, an entry grounded in nothing, or a register that silently omits the derived half.","INDETERMINATE":"The vision, business model or market snapshot are not in evidence, so grounding cannot be checked.","PASS":"Every derived entry names its signal, every proposed entry is grounded in an authored family, and an absent derivation is stated."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/risk-register","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.risk-register"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/risk-register","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-risk-register-inputs-and-candidate","criterionRef":"application-creation:criterion/risk-register-arguable-statements-and-grounded-weighting","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":5,"minCount":2,"requirementRef":"application-creation:evidence-requirement/risk-register-arguable-statements-and-grounded-weighting","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-business-model-market-and-risk-register-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-risk-register-inputs-and-candidate","criterionRef":"application-creation:criterion/risk-register-boundary-with-other-mechanisms","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":5,"minCount":2,"requirementRef":"application-creation:evidence-requirement/risk-register-boundary-with-other-mechanisms","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-business-model-market-and-risk-register-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-risk-register-inputs-and-candidate","criterionRef":"application-creation:criterion/risk-register-entry-origin-honesty","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":5,"minCount":2,"requirementRef":"application-creation:evidence-requirement/risk-register-entry-origin-honesty","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-business-model-market-and-risk-register-candidate"}],"schemaVersion":1}
|
|
@@ -0,0 +1,46 @@
|
|
|
1
|
+
# Complete the risk register
|
|
2
|
+
|
|
3
|
+
The derivation layer says what is PRESENT in this application — how many providers are vendor-hosted, how many operations an external agent can reach, which retention classes have a declared period, which resources have said nothing about personal data. Those are facts, and they are deliberately silent about what they MEAN.
|
|
4
|
+
|
|
5
|
+
This step writes what they mean for this product and these users, and proposes the risks no derivation reaches.
|
|
6
|
+
|
|
7
|
+
## You are drafting, not deciding
|
|
8
|
+
|
|
9
|
+
A model proposes; a human accepts; the accepted register is the committed file. Nothing you write here takes effect by being written, and the value of the artifact is that a person can disagree with it line by line. So:
|
|
10
|
+
|
|
11
|
+
- Write statements a reader can argue with. "Personal data is processed by third parties" is unarguable and says nothing; "two vendor-hosted LLM providers receive task titles and user names, which are the fields customers type freely" is a claim someone can check and correct.
|
|
12
|
+
- Never write a statement you cannot ground. If the evidence for a risk is that it sounds prudent, it is a PROPOSED entry and must be marked as one.
|
|
13
|
+
- Do not soften a derived fact to make the register read better. The register is read by people deciding how deeply to audit something; a reassuring one is worse than none.
|
|
14
|
+
|
|
15
|
+
After landing, the advisory judge reads the register against three criteria — honest entry origins, arguable statements with grounded bands, and the boundary with other mechanisms — and its verdicts reach the person accepting the register as notes. A verdict never refuses a landing.
|
|
16
|
+
|
|
17
|
+
## Two kinds of entry, and the difference is what may be believed
|
|
18
|
+
|
|
19
|
+
**SIGNAL_DERIVED** — completed from a derived signal, which the entry names. The measurement can be re-run, so the entry's premise is falsifiable: if the signal stops reporting the exposure, the statement resting on it is stale rather than merely old. One derived entry per signal.
|
|
20
|
+
|
|
21
|
+
**PROPOSED** — a business risk nothing measures. This is why the step exists rather than the derivation being the whole answer: a register limited to what code can compute would omit most of what a product actually carries. Ground each one in the vision, the business model and the market snapshot, which this application has already authored, and never anchor it to a signal — a proposal pointing at a measurement is a derived entry wearing the wrong label.
|
|
22
|
+
|
|
23
|
+
## Weighting is two qualitative bands and NOTHING is multiplied
|
|
24
|
+
|
|
25
|
+
Likelihood and impact are each one of five bands. There is no score, no rating and no product of the two anywhere in the register, and this is not a stylistic preference: the derivation layer beneath this one asserts structurally that it emits no score, because a number is what a reader trusts without checking. Two judgements multiplied into a third judgement would put exactly that underneath a layer built to refuse it.
|
|
26
|
+
|
|
27
|
+
Ground the bands in what is IMPLEMENTED, not in how the risk sounds. "Impact HIGH because the erasure path is manual" is grounded. "Impact HIGH because data breaches are serious" is not — it would be equally true of every application ever built, which is the test for a weighting that carries no information.
|
|
28
|
+
|
|
29
|
+
Where the application has declared a posture for the signal, record it on the entry. A posture of AVOIDED that the measurement contradicts is not yours to resolve: state the risk as measured, note the contradiction in the weighting grounding, and let the person accepting the register decide whether the declaration or the product is wrong.
|
|
30
|
+
|
|
31
|
+
## The signals, and what to do when they are not all there
|
|
32
|
+
|
|
33
|
+
The derived signals arrive in the declared `risk_signals` context section of your brief — measured facts about this application's own declarations, each with the inputs it came from and none with a score. Ground your weighting in them. Do not restate a signal as a risk, do not treat their order as a priority, and never re-derive or estimate one: they are computed, and a number you produced yourself would be indistinguishable on the page from one that was measured.
|
|
34
|
+
|
|
35
|
+
Four of them are read from the application's configuration and always arrive. The two that need every resource materialized — the personal-data inventory and the MCP exposure — can be absent when the application cannot be introspected, and the section simply will not carry them.
|
|
36
|
+
|
|
37
|
+
The register does not require the derivation to have run. If signals were not supplied to this run, or only some were, produce the PROPOSED entries you can ground in the authored specification families, state plainly in the register which derived half is absent, and finish.
|
|
38
|
+
|
|
39
|
+
Do not stop, do not ask for evidence to be collected first, and do not treat an absent measurement as an absent risk. A step that cannot proceed until evidence exists has made a measurement into a precondition, and a compliance workflow may never stand in front of the mechanism it describes.
|
|
40
|
+
|
|
41
|
+
## What belongs to other mechanisms
|
|
42
|
+
|
|
43
|
+
- **Which control objectives this application claims** — the compliance programme. A register entry may mention a control; it never binds one.
|
|
44
|
+
- **Whether a control's evidence is adequate** — the evidence-adequacy step. The register says a risk exists, never that it has been discharged.
|
|
45
|
+
- **How deeply to audit a demand** — a consumer of this register, not part of it. Write the risk; do not write the audit plan.
|
|
46
|
+
- **Retention periods, provider deployment choices, jurisdictions** — configuration the application already declares. Read them; do not restate them as risks, and never contradict them here.
|
|
@@ -0,0 +1,59 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ref": "top_down.risk-register",
|
|
3
|
+
"version": "0.1.1",
|
|
4
|
+
"phase": "top_down",
|
|
5
|
+
"intent": "Complete this application's risk register: turn each DERIVED risk signal into a statement about what the exposure means for THIS product and these users, weight it qualitatively against what is actually implemented, and propose the business risks no derivation reaches. The signals say what is present; this says what it means. A model proposes and a human accepts — the accepted register is the committed file, so this playbook never decides anything, it drafts. Runtime evidence, control-objective binding and audit depth belong to their own mechanisms; this produces the register they read.",
|
|
6
|
+
"preconditions": [
|
|
7
|
+
{
|
|
8
|
+
"kind": "artifact_exists",
|
|
9
|
+
"selector": {
|
|
10
|
+
"family": "vision-brief"
|
|
11
|
+
}
|
|
12
|
+
},
|
|
13
|
+
{
|
|
14
|
+
"kind": "artifact_exists",
|
|
15
|
+
"selector": {
|
|
16
|
+
"family": "business-model"
|
|
17
|
+
}
|
|
18
|
+
}
|
|
19
|
+
],
|
|
20
|
+
"inputs": [
|
|
21
|
+
{
|
|
22
|
+
"family": "vision-brief"
|
|
23
|
+
},
|
|
24
|
+
{
|
|
25
|
+
"family": "business-model"
|
|
26
|
+
},
|
|
27
|
+
{
|
|
28
|
+
"family": "market-snapshot"
|
|
29
|
+
}
|
|
30
|
+
],
|
|
31
|
+
"outputs": [
|
|
32
|
+
{
|
|
33
|
+
"family": "risk-register",
|
|
34
|
+
"schemaRef": "saas-specifications:ApplicationRiskRegister",
|
|
35
|
+
"description": "The accepted register: one entry per risk, each carrying its origin (SIGNAL_DERIVED with the signal it was completed from, or PROPOSED where no derivation reaches it), a statement in this application's own terms, qualitative likelihood and impact bands with the grounding for them, and the Layer 2 posture the risk is carried under where one is declared. Validated by validateApplicationRiskRegister."
|
|
36
|
+
}
|
|
37
|
+
],
|
|
38
|
+
"stepOutputs": [],
|
|
39
|
+
"method": {
|
|
40
|
+
"guidance": "# Complete the risk register\n\nThe derivation layer says what is PRESENT in this application — how many providers are vendor-hosted, how many operations an external agent can reach, which retention classes have a declared period, which resources have said nothing about personal data. Those are facts, and they are deliberately silent about what they MEAN.\n\nThis step writes what they mean for this product and these users, and proposes the risks no derivation reaches.\n\n## You are drafting, not deciding\n\nA model proposes; a human accepts; the accepted register is the committed file. Nothing you write here takes effect by being written, and the value of the artifact is that a person can disagree with it line by line. So:\n\n- Write statements a reader can argue with. \"Personal data is processed by third parties\" is unarguable and says nothing; \"two vendor-hosted LLM providers receive task titles and user names, which are the fields customers type freely\" is a claim someone can check and correct.\n- Never write a statement you cannot ground. If the evidence for a risk is that it sounds prudent, it is a PROPOSED entry and must be marked as one.\n- Do not soften a derived fact to make the register read better. The register is read by people deciding how deeply to audit something; a reassuring one is worse than none.\n\nAfter landing, the advisory judge reads the register against three criteria — honest entry origins, arguable statements with grounded bands, and the boundary with other mechanisms — and its verdicts reach the person accepting the register as notes. A verdict never refuses a landing.\n\n## Two kinds of entry, and the difference is what may be believed\n\n**SIGNAL_DERIVED** — completed from a derived signal, which the entry names. The measurement can be re-run, so the entry's premise is falsifiable: if the signal stops reporting the exposure, the statement resting on it is stale rather than merely old. One derived entry per signal.\n\n**PROPOSED** — a business risk nothing measures. This is why the step exists rather than the derivation being the whole answer: a register limited to what code can compute would omit most of what a product actually carries. Ground each one in the vision, the business model and the market snapshot, which this application has already authored, and never anchor it to a signal — a proposal pointing at a measurement is a derived entry wearing the wrong label.\n\n## Weighting is two qualitative bands and NOTHING is multiplied\n\nLikelihood and impact are each one of five bands. There is no score, no rating and no product of the two anywhere in the register, and this is not a stylistic preference: the derivation layer beneath this one asserts structurally that it emits no score, because a number is what a reader trusts without checking. Two judgements multiplied into a third judgement would put exactly that underneath a layer built to refuse it.\n\nGround the bands in what is IMPLEMENTED, not in how the risk sounds. \"Impact HIGH because the erasure path is manual\" is grounded. \"Impact HIGH because data breaches are serious\" is not — it would be equally true of every application ever built, which is the test for a weighting that carries no information.\n\nWhere the application has declared a posture for the signal, record it on the entry. A posture of AVOIDED that the measurement contradicts is not yours to resolve: state the risk as measured, note the contradiction in the weighting grounding, and let the person accepting the register decide whether the declaration or the product is wrong.\n\n## The signals, and what to do when they are not all there\n\nThe derived signals arrive in the declared `risk_signals` context section of your brief — measured facts about this application's own declarations, each with the inputs it came from and none with a score. Ground your weighting in them. Do not restate a signal as a risk, do not treat their order as a priority, and never re-derive or estimate one: they are computed, and a number you produced yourself would be indistinguishable on the page from one that was measured.\n\nFour of them are read from the application's configuration and always arrive. The two that need every resource materialized — the personal-data inventory and the MCP exposure — can be absent when the application cannot be introspected, and the section simply will not carry them.\n\nThe register does not require the derivation to have run. If signals were not supplied to this run, or only some were, produce the PROPOSED entries you can ground in the authored specification families, state plainly in the register which derived half is absent, and finish.\n\nDo not stop, do not ask for evidence to be collected first, and do not treat an absent measurement as an absent risk. A step that cannot proceed until evidence exists has made a measurement into a precondition, and a compliance workflow may never stand in front of the mechanism it describes.\n\n## What belongs to other mechanisms\n\n- **Which control objectives this application claims** — the compliance programme. A register entry may mention a control; it never binds one.\n- **Whether a control's evidence is adequate** — the evidence-adequacy step. The register says a risk exists, never that it has been discharged.\n- **How deeply to audit a demand** — a consumer of this register, not part of it. Write the risk; do not write the audit plan.\n- **Retention periods, provider deployment choices, jurisdictions** — configuration the application already declares. Read them; do not restate them as risks, and never contradict them here.\n",
|
|
41
|
+
"skillRefs": [
|
|
42
|
+
"journey-status"
|
|
43
|
+
],
|
|
44
|
+
"skillBodyRefs": [],
|
|
45
|
+
"contextSources": [
|
|
46
|
+
"risk_signals"
|
|
47
|
+
],
|
|
48
|
+
"draftableDocumentDefinitionRefs": [],
|
|
49
|
+
"suspendsForClarification": false,
|
|
50
|
+
"briefAdequacyGate": false,
|
|
51
|
+
"briefAdequacyExcludedSources": []
|
|
52
|
+
},
|
|
53
|
+
"executor": "companion_agent",
|
|
54
|
+
"approval": "approve_result",
|
|
55
|
+
"budget": {
|
|
56
|
+
"maxRuns": 3
|
|
57
|
+
},
|
|
58
|
+
"onFailure": "keep_and_flag"
|
|
59
|
+
}
|
|
@@ -76,7 +76,10 @@ planning anything:
|
|
|
76
76
|
(it owns the read; do not re-derive it here). Confirm a `market-snapshot`
|
|
77
77
|
exists and check whether a `roadmap` already exists from an earlier run.
|
|
78
78
|
2. Read the capability-mapped **MarketSnapshot** (benefits + their
|
|
79
|
-
`deliveredByFeatureRefs
|
|
79
|
+
`deliveredByFeatureRefs`, and their authored Kano categories). The FIT half of
|
|
80
|
+
that signal is COMPUTED for you and arrives in
|
|
81
|
+
the declared `market_fit_scores` context section of your brief — read it there rather than deriving or
|
|
82
|
+
estimating it. Then the **feature-drafts** (the prose
|
|
80
83
|
capability contracts — what each delivering feature actually is, so you can
|
|
81
84
|
weigh how much of the product a requirement pulls in and whether it is
|
|
82
85
|
MVP-critical), the **requirements** (`requirements` family — the
|
|
@@ -84,8 +87,8 @@ planning anything:
|
|
|
84
87
|
**VisionSnapshot** (`vision-brief` — the success criteria to deliver and the
|
|
85
88
|
differentiation that anchors what belongs in the MVP).
|
|
86
89
|
|
|
87
|
-
|
|
88
|
-
|
|
90
|
+
(A previously landed roadmap arrives in your brief as the `roadmap` input section — refine those
|
|
91
|
+
phases rather than re-cutting them blind.)
|
|
89
92
|
|
|
90
93
|
You **read** `market-snapshot` + `feature-drafts` + `requirements` +
|
|
91
94
|
`vision-brief`; you **write** the `roadmap` family.
|
|
@@ -265,7 +268,7 @@ scaffold depth — depth is a dedicated later pass done once, holistically.
|
|
|
265
268
|
## What you emit
|
|
266
269
|
|
|
267
270
|
One artifact for this journey: the **roadmap** at
|
|
268
|
-
|
|
271
|
+
`specifications/src/roadmap/index.ts` — a `RoadmapSnapshot` whose `phases`
|
|
269
272
|
are the ordered, MVP-first releases, each with a distinct `sequence`, a coarse
|
|
270
273
|
`horizon` + `kind`, and its `deliversRequirementRefs` / `deliversSuccessCriterionRefs`
|
|
271
274
|
wired — passing the `roadmap-valid` gate.
|
|
@@ -275,6 +278,10 @@ accepted as the journey's roadmap.
|
|
|
275
278
|
|
|
276
279
|
## References
|
|
277
280
|
|
|
278
|
-
|
|
281
|
+
These are skill FOLDERS installed in the application, named so each piece of work has an
|
|
282
|
+
authoring contract a later coding agent can open. This step has no tools and does not open them;
|
|
283
|
+
what reaches you is this method, your declared inputs, and the brief's own sections.
|
|
284
|
+
|
|
285
|
+
- `journey-status` — read the current journey state and
|
|
279
286
|
scope, and confirm a `market-snapshot` (the capability map) already exists to
|
|
280
287
|
plan releases from.
|