@wildo-ai/framework-knowledge 1.1.4 → 1.1.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +227 -6
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts +19 -0
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js +47 -1
- package/dist/esm/framework-knowledge.loader.js.map +1 -1
- package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.js.map +1 -1
- package/dist/esm/index.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +125 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +177 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +213 -7
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +326 -8
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +5 -3
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +21 -14
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +57 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +63 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +132 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +179 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +67 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +76 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +5 -4
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +10 -5
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +67 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +82 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +25 -9
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +124 -7
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +67 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +83 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +69 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +71 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +71 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +88 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +97 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +156 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +115 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +152 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +188 -8
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +167 -9
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +171 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +146 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts +248 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js +248 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +157 -4
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +172 -4
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +5 -4
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +8 -7
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +3 -2
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +22 -3
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +5 -3
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +21 -12
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +192 -27
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +172 -33
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +6 -2
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +182 -5
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +191 -5
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +3 -2
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +154 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +214 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +44 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +51 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +2 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +6 -2
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +2 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +7 -3
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +32 -4
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +27 -3
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +4 -2
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +199 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +227 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +5 -3
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +18 -4
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +155 -4
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +187 -4
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +6 -5
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +18 -17
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
- package/dist/knowledge/manifest.json +9 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +75 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
- package/dist/knowledge/playbooks/bottom_up.build/method.md +79 -0
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +65 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +1122 -76
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +49 -13
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +671 -47
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +10 -16
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +31 -35
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -16
- package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +95 -0
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +62 -0
- package/dist/knowledge/playbooks/bottom_up.conception/method.md +80 -0
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +90 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +107 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +70 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +8 -8
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +14 -13
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +165 -0
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +74 -0
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +219 -140
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +55 -22
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +138 -0
- package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +70 -0
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +87 -0
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +69 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +236 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +63 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +116 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +79 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +71 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +70 -0
- package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +83 -0
- package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +68 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +873 -15
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +19 -12
- package/dist/knowledge/playbooks/refinement.document-facts/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.document-facts/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +186 -21
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +12 -16
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +343 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +54 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +28 -11
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -17
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +8 -15
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +25 -49
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +14 -17
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +101 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +209 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +68 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +42 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +39 -12
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +18 -66
- package/dist/knowledge/playbooks/top_down.compliance-research/method.md +78 -0
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +43 -0
- package/dist/knowledge/playbooks/top_down.definition/method.md +103 -0
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +75 -0
- package/dist/knowledge/playbooks/top_down.expert-personas/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +48 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/method.md +51 -165
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +25 -44
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +43 -0
- package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +45 -0
- package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +247 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +71 -0
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/method.md +36 -69
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +12 -9
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +11 -7
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +12 -16
- package/dist/knowledge/playbooks/top_down.risk-register/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.risk-register/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +46 -0
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +59 -0
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +12 -5
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +15 -17
- package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +23 -14
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +12 -17
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +13 -17
- package/dist/knowledge/references/acp.execution-profile.md +266 -0
- package/dist/knowledge/references/acp.host-configuration-inheritance.md +29 -0
- package/dist/knowledge/references/acp.permission-ceiling.md +105 -0
- package/dist/knowledge/references/acp.permission-escalation.md +37 -0
- package/dist/knowledge/references/application-documentation-chapters.config.md +152 -0
- package/dist/knowledge/references/application-documentation-plan.config.md +136 -0
- package/dist/knowledge/references/application-maturity.config.md +319 -0
- package/dist/knowledge/references/assertions.authored-metadata.config.md +1 -1
- package/dist/knowledge/references/assertions.specification.config.md +1 -1
- package/dist/knowledge/references/brand.asset.config.md +8 -16
- package/dist/knowledge/references/brand.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/brand.logo-direction.config.md +9 -7
- package/dist/knowledge/references/brand.snapshot.config.md +16 -2
- package/dist/knowledge/references/brand.snapshot.validation.md +0 -7
- package/dist/knowledge/references/build-plan.task-graph.config.md +581 -7
- package/dist/knowledge/references/business-model.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/business-model.pricing-plan.config.md +1 -1
- package/dist/knowledge/references/business-model.snapshot.validation.md +15 -0
- package/dist/knowledge/references/capability-composition.config.md +155 -0
- package/dist/knowledge/references/cli.market.utils.md +1 -0
- package/dist/knowledge/references/companion.technical-doc.service.md +453 -98
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +21 -0
- package/dist/knowledge/references/engine.client-bundle.external-connectors-public.discipline.md +20 -1
- package/dist/knowledge/references/engine.saas-technical-doc.config.md +8 -4
- package/dist/knowledge/references/engine.saas-website.config.md +22 -10
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +8 -12
- package/dist/knowledge/references/example.config.app-shell.full.md +42 -7
- package/dist/knowledge/references/example.config.backend.required-floors.md +4 -0
- package/dist/knowledge/references/example.config.design-system.full.md +3 -0
- package/dist/knowledge/references/example.engine.product-definitions.feature-and-profiles.md +19 -7
- package/dist/knowledge/references/example.features.connected-feature.declaration.md +66 -0
- package/dist/knowledge/references/example.features.connected-feature.surface.md +42 -0
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +4 -3
- package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +6 -10
- package/dist/knowledge/references/example.guidance.bound-survey-flow.md +82 -0
- package/dist/knowledge/references/example.infra.environment-config.local.md +88 -11
- package/dist/knowledge/references/example.milestones.module-definitions.md +73 -0
- package/dist/knowledge/references/example.minion.contained-tick.md +79 -0
- package/dist/knowledge/references/example.module.companion-exports.full.md +38 -3
- package/dist/knowledge/references/example.provider.backend-module-shape.md +31 -13
- package/dist/knowledge/references/example.provider.frontend-app.module.md +103 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +20 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +7 -3
- package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +30 -0
- package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +11 -0
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +3 -0
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +94 -10
- package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +79 -0
- package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +18 -0
- package/dist/knowledge/references/example.worker.node-route.md +94 -0
- package/dist/knowledge/references/experience-plan.config.md +311 -0
- package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +132 -9
- package/dist/knowledge/references/external-connectors.backend.provider-package-convention.md +36 -0
- package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +269 -0
- package/dist/knowledge/references/integration-plan.config.md +185 -0
- package/dist/knowledge/references/market.alternative.config.md +1 -1
- package/dist/knowledge/references/market.authored-metadata.config.md +12 -9
- package/dist/knowledge/references/market.channel.config.md +3 -3
- package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
- package/dist/knowledge/references/market.gain.config.md +1 -1
- package/dist/knowledge/references/market.icp.config.md +2 -2
- package/dist/knowledge/references/market.job.config.md +1 -1
- package/dist/knowledge/references/market.message-template.config.md +2 -2
- package/dist/knowledge/references/market.objection.config.md +1 -1
- package/dist/knowledge/references/market.pain.config.md +1 -1
- package/dist/knowledge/references/market.persona.config.md +2 -2
- package/dist/knowledge/references/market.proof.config.md +1 -1
- package/dist/knowledge/references/market.snapshot.validation.md +15 -0
- package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
- package/dist/knowledge/references/market.trigger.config.md +1 -1
- package/dist/knowledge/references/minions.tick-contract.md +83 -0
- package/dist/knowledge/references/placement-plan.config.md +369 -0
- package/dist/knowledge/references/platform.config.application-database.md +5 -2
- package/dist/knowledge/references/platform.config.backing-services.md +0 -21
- package/dist/knowledge/references/platform.config.environment.deployment.md +206 -14
- package/dist/knowledge/references/platform.config.infra-provider-resolution.md +170 -0
- package/dist/knowledge/references/platform.config.infrastructure-host.md +87 -0
- package/dist/knowledge/references/platform.config.saas.md +261 -9
- package/dist/knowledge/references/presets.models.labelling.sections.md +14 -0
- package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
- package/dist/knowledge/references/requirements.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/requirements.snapshot.validation.md +15 -0
- package/dist/knowledge/references/roadmap.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/roadmap.snapshot.validation.md +15 -7
- package/dist/knowledge/references/saas.backend.a2a.token-budget.md +71 -0
- package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +1 -2
- package/dist/knowledge/references/saas.backend.auth.federated-identity-provider-private-networks.md +62 -0
- package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +86 -0
- package/dist/knowledge/references/saas.backend.billing.catalog-sync-result.md +37 -0
- package/dist/knowledge/references/saas.backend.billing.resolution-failure-reasons.md +24 -5
- package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +187 -0
- package/dist/knowledge/references/saas.backend.domain-module.md +25 -1
- package/dist/knowledge/references/saas.backend.error-builder.user-guidance.md +82 -0
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +6 -0
- package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +22 -4
- package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +17 -4
- package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +84 -0
- package/dist/knowledge/references/saas.backend.health-readiness-contributor.md +73 -0
- package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +200 -0
- package/dist/knowledge/references/saas.backend.providers.operation-executor.md +51 -0
- package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +71 -0
- package/dist/knowledge/references/saas.backend.queue.worker-topology.md +39 -0
- package/dist/knowledge/references/saas.backend.system-access-service.md +51 -42
- package/dist/knowledge/references/saas.composition.scenario-apply.md +51 -0
- package/dist/knowledge/references/saas.config.content-security-policy.md +97 -0
- package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +91 -21
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +4 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +38 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +27 -27
- package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +65 -16
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +41 -11
- package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +44 -8
- package/dist/knowledge/references/saas.frontend.billing-context.md +108 -0
- package/dist/knowledge/references/saas.frontend.brand-identity.md +38 -0
- package/dist/knowledge/references/saas.frontend.celebration-overlay-contract.md +41 -0
- package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +64 -0
- package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
- package/dist/knowledge/references/saas.frontend.errors.user-facing-error-message.md +47 -0
- package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.per-action-retry-loop.md +7 -1
- package/dist/knowledge/references/saas.frontend.execution-view.definition.md +3 -3
- package/dist/knowledge/references/saas.frontend.flows-actors-view.md +7 -4
- package/dist/knowledge/references/saas.frontend.form-fields.file-provider-constraints.md +30 -48
- package/dist/knowledge/references/saas.frontend.full-custom-view.definition.md +24 -0
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
- package/dist/knowledge/references/saas.frontend.onboarding-view.md +84 -0
- package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +65 -0
- package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
- package/dist/knowledge/references/saas.frontend.resource-header-title.md +28 -4
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +127 -1
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +327 -11
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +198 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +220 -0
- package/dist/knowledge/references/saas.market.generation-agent.md +26 -9
- package/dist/knowledge/references/saas.models.analytics.value-moments.md +132 -0
- package/dist/knowledge/references/saas.models.audit.trail-config.md +155 -0
- package/dist/knowledge/references/saas.models.auth.methods.md +513 -0
- package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +82 -0
- package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +77 -0
- package/dist/knowledge/references/saas.models.config.organization-types.md +192 -0
- package/dist/knowledge/references/saas.models.config.registration.md +188 -0
- package/dist/knowledge/references/saas.models.config.tenant-teardown.md +81 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +173 -3
- package/dist/knowledge/references/saas.models.email.template-type.md +40 -0
- package/dist/knowledge/references/saas.models.engine-capabilities.md +85 -7
- package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +61 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +43 -4
- package/dist/knowledge/references/saas.models.features.definition-builders.md +162 -0
- package/dist/knowledge/references/saas.models.file-upload-grant.md +222 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +54 -5
- package/dist/knowledge/references/saas.models.governed-document-acceptance-mode.md +116 -0
- package/dist/knowledge/references/saas.models.guidance-flow.md +160 -0
- package/dist/knowledge/references/saas.models.http-api-binding.md +76 -110
- package/dist/knowledge/references/saas.models.milestone-celebration.md +69 -0
- package/dist/knowledge/references/saas.models.milestone-definition.md +209 -0
- package/dist/knowledge/references/saas.models.navigation.layout.md +2 -2
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +150 -0
- package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +70 -0
- package/dist/knowledge/references/saas.models.notifications.targets.md +138 -0
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +256 -0
- package/dist/knowledge/references/saas.models.onboarding-elements.md +375 -0
- package/dist/knowledge/references/saas.models.onboarding-trigger.md +52 -0
- package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +50 -0
- package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +129 -0
- package/dist/knowledge/references/saas.models.privacy.client-instance-id-scope.md +49 -0
- package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +106 -0
- package/dist/knowledge/references/saas.models.progression-tracker-variant.md +76 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +8 -5
- package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +72 -0
- package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +50 -0
- package/dist/knowledge/references/saas.models.providers.capability-surface.md +58 -0
- package/dist/knowledge/references/saas.models.providers.compliance-choice.md +111 -0
- package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +156 -0
- package/dist/knowledge/references/saas.models.rate-limit-configuration.md +11 -1
- package/dist/knowledge/references/saas.models.relationship-handling-settings.md +23 -1
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -4
- package/dist/knowledge/references/saas.models.resource-config.forwarded-label.md +5 -4
- package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +69 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +15 -2
- package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +66 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-base.md +24 -1
- package/dist/knowledge/references/saas.models.resource-config.operation-cron-job.md +59 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +55 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +5 -4
- package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +158 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-step-up.md +77 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-for-key.md +6 -1
- package/dist/knowledge/references/saas.models.resource-config.queue-policy.md +49 -0
- package/dist/knowledge/references/saas.models.resource-config.required-features.md +84 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +10 -0
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +14 -0
- package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +111 -4
- package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +39 -0
- package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +48 -0
- package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +38 -0
- package/dist/knowledge/references/saas.models.resource-primary-scope.md +11 -2
- package/dist/knowledge/references/saas.models.scope-membership.md +3 -4
- package/dist/knowledge/references/saas.models.shared-saas-module.md +25 -0
- package/dist/knowledge/references/saas.models.systems-of-record.md +635 -0
- package/dist/knowledge/references/saas.public-runtime.contract.md +198 -1
- package/dist/knowledge/references/saas.rag.retrieval-result.md +19 -8
- package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
- package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +15 -36
- package/dist/knowledge/references/saas.specifications.application-document-publication.contract.md +9 -5
- package/dist/knowledge/references/saas.specifications.application-document-publication.generation.md +63 -0
- package/dist/knowledge/references/saas.specifications.application-document-release-set.contract.md +74 -0
- package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +123 -0
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +88 -7
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +774 -53
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +211 -14
- package/dist/knowledge/references/saas.specifications.composite-view-specification.md +10 -0
- package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +364 -0
- package/dist/knowledge/references/saas.specifications.playbook-approval-and-failure-policies.md +96 -0
- package/dist/knowledge/references/saas.specifications.processor-register.md +333 -0
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +8 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
- package/dist/knowledge/references/saas.website.astro.bridge.md +64 -2
- package/dist/knowledge/references/saas.website.astro.head-renderer.md +32 -12
- package/dist/knowledge/references/saas.website.astro.label-loader.md +3 -0
- package/dist/knowledge/references/saas.website.astro.robots-renderer.md +14 -1
- package/dist/knowledge/references/saas.website.blog.bridge.md +21 -1
- package/dist/knowledge/references/saas.website.consent.banner.md +218 -0
- package/dist/knowledge/references/saas.website.consent.context.md +162 -0
- package/dist/knowledge/references/saas.website.consent.gate.md +38 -0
- package/dist/knowledge/references/saas.website.page-layout.component.md +67 -1
- package/dist/knowledge/references/saas.website.page.context.md +4 -3
- package/dist/knowledge/references/saas.website.runtime.context.md +43 -7
- package/dist/knowledge/references/saas.website.section.context.md +3 -2
- package/dist/knowledge/references/saas.website.sections.category-enum.md +19 -20
- package/dist/knowledge/references/vision.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/website-plan.config.md +205 -0
- package/dist/knowledge/references/workers.node.worker-init-contract.md +57 -0
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +43 -2
- package/dist/knowledge/references/zod.decorators.data-categories.md +197 -0
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +51 -4
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +54 -1
- package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +35 -0
- package/dist/knowledge/references/zod.decorators.field-spec-params.md +32 -5
- package/dist/knowledge/references/zod.decorators.file-nature-constraints.md +86 -0
- package/dist/knowledge/references/zod.decorators.file-readiness-metadata.md +67 -0
- package/dist/knowledge/references/zod.decorators.file-schema.md +90 -14
- package/dist/knowledge/references/zod.decorators.file-vocabularies.md +84 -0
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +140 -4
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
- package/dist/knowledge/references/zod.decorators.rag-source.md +6 -2
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +24 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +35 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +46 -12
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +31 -12
- package/dist/knowledge/references/zod.factories.address.md +118 -0
- package/dist/knowledge/references/zod.factories.code.md +2 -0
- package/dist/knowledge/references/zod.factories.duration.md +2 -0
- package/dist/knowledge/references/zod.factories.money.md +2 -0
- package/dist/knowledge/references/zod.factories.phone.md +14 -1
- package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
- package/dist/knowledge/registries/framework-topics.json +1215 -11
- package/dist/knowledge/registries/playbooks.json +454 -50
- package/dist/knowledge/registries/source-tags.json +3153 -1043
- package/dist/knowledge/rules/database-migration-obligation.md +110 -0
- package/dist/knowledge/rules/live-context-door.md +108 -0
- package/dist/knowledge/rules/resource-schema-awareness.md +75 -0
- package/dist/knowledge/skills/INDEX.md +46 -11
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +80 -37
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +167 -0
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +6 -3
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -3
- package/dist/knowledge/skills/application-database-migrations/references/framework-application-database-api.md +5 -2
- package/dist/knowledge/skills/application-database-migrations/references/migration-refusals.md +32 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +94 -3
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +50 -0
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +26 -19
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +25 -1
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-readiness-contributor-api.md +135 -0
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +75 -12
- package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +137 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-error-user-guidance-api.md +112 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +72 -1
- package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +207 -0
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +31 -1
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-asset-api.md +8 -16
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +25 -9
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +135 -5
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +80 -17
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +369 -111
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +32 -10
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +103 -58
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-publication-contract.md +19 -13
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +142 -26
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +722 -23
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +348 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +123 -0
- package/dist/knowledge/skills/config-app-shell/SKILL.md +74 -11
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +85 -19
- package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +70 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +43 -3
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
- package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
- package/dist/knowledge/skills/config-design-system/references/surface-policy-authoring.md +19 -10
- package/dist/knowledge/skills/config-navigation/SKILL.md +85 -2
- package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +2 -2
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +172 -0
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +146 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +141 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +86 -9
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +199 -0
- package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +179 -0
- package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +493 -0
- package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +153 -0
- package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +242 -0
- package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +161 -0
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +93 -12
- package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +785 -0
- package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +172 -0
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +261 -9
- package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +9 -0
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +58 -3
- package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +151 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-auth-methods-api.md +579 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +8 -2
- package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +96 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +316 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-registration-config-api.md +221 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +121 -0
- package/dist/knowledge/skills/config-saas-backend/references/managed-startup-configuration.md +46 -0
- package/dist/knowledge/skills/configure-billing/SKILL.md +27 -22
- package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +27 -15
- package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +41 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +36 -17
- package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +30 -28
- package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +169 -0
- package/dist/knowledge/skills/configure-billing/references/framework-billing-resolution-failure-api.md +44 -11
- package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +187 -0
- package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +76 -0
- package/dist/knowledge/skills/configure-coding-agent/SKILL.md +280 -0
- package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +168 -0
- package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +504 -0
- package/dist/knowledge/skills/email-add-template/SKILL.md +41 -69
- package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +15 -7
- package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +120 -0
- package/dist/knowledge/skills/engine-component-registration/SKILL.md +19 -12
- package/dist/knowledge/skills/engine-product-definitions/SKILL.md +54 -31
- package/dist/knowledge/skills/engine-product-definitions/references/connected-feature-workflow.md +130 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-engine-product-definitions-api.md +25 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-feature-builders-api.md +215 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +78 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +33 -24
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +121 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -8
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +5 -4
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +46 -9
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +34 -7
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +151 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +6 -10
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +54 -5
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +75 -21
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +258 -0
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +480 -0
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +3983 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +211 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +165 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-elements-api.md +381 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-trigger-api.md +57 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-view-api.md +89 -0
- package/dist/knowledge/skills/i18n-label-generation/SKILL.md +13 -1
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +14 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +14 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +3 -1
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +14 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +237 -37
- package/dist/knowledge/skills/infra-environment-config/references/framework-application-database-api.md +5 -2
- package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +174 -21
- package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +206 -14
- package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +95 -0
- package/dist/knowledge/skills/journey-approve/SKILL.md +28 -8
- package/dist/knowledge/skills/journey-approve/references/specification-family-map.md +88 -0
- package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +37 -2
- package/dist/knowledge/skills/journey-next/SKILL.md +41 -1
- package/dist/knowledge/skills/journey-report/SKILL.md +16 -3
- package/dist/knowledge/skills/journey-run/SKILL.md +92 -7
- package/dist/knowledge/skills/journey-run/references/expert-personas-and-deliberations.md +46 -0
- package/dist/knowledge/skills/journey-run/references/framework-playbook-approval-policy.md +108 -0
- package/dist/knowledge/skills/journey-status/SKILL.md +14 -4
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +153 -46
- package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +119 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/initialization-recovery-recipe.md +7 -4
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +253 -33
- package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +1 -1
- package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
- package/dist/knowledge/skills/market-alternatives/SKILL.md +1 -1
- package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +12 -9
- package/dist/knowledge/skills/market-channels/SKILL.md +3 -3
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +226 -14
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +226 -14
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +56 -9
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +32 -9
- package/dist/knowledge/skills/market-icp/SKILL.md +2 -2
- package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +3 -3
- package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -2
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +17 -2
- package/dist/knowledge/skills/market-persona/SKILL.md +2 -2
- package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +2 -2
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -0
- package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +15 -0
- package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +1 -1
- package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +1 -1
- package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +198 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-celebration-overlay-contract.md +51 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-celebration-api.md +79 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-definition-api.md +220 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-progression-tracker-api.md +86 -0
- package/dist/knowledge/skills/minion-authoring/SKILL.md +140 -0
- package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +84 -0
- package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +91 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +38 -3
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +211 -14
- package/dist/knowledge/skills/module-registration/SKILL.md +50 -33
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +50 -1
- package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +142 -0
- package/dist/knowledge/skills/module-registration/references/registry-files.md +14 -5
- package/dist/knowledge/skills/module-relationships/SKILL.md +62 -0
- package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +26 -5
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +279 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +80 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +55 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-convention-api.md +48 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +33 -6
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-file-provider-constraints-api.md +99 -47
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +241 -9
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +196 -0
- package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +50 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +80 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +71 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +58 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +275 -0
- package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +64 -11
- package/dist/knowledge/skills/rate-limit-authoring/references/fixed-window-and-environment-multiplier.md +27 -0
- package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +19 -6
- package/dist/knowledge/skills/resource-add-field/SKILL.md +12 -5
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +373 -23
- package/dist/knowledge/skills/resource-add-module/SKILL.md +116 -265
- package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +133 -0
- package/dist/knowledge/skills/resource-add-module/references/framework-new-module-wiring-api.md +25 -0
- package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +12 -12
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +26 -3
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +122 -4
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +25 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +93 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +136 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +85 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +133 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +141 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-step-up-api.md +126 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +859 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +122 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +124 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +97 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +457 -15
- package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +197 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +162 -46
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +452 -0
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +5 -0
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +327 -11
- package/dist/knowledge/skills/resource-custom-view/references/framework-user-facing-error-message-api.md +50 -0
- package/dist/knowledge/skills/resource-external-data/SKILL.md +228 -15
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +54 -7
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +87 -113
- package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +13 -8
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +69 -26
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +246 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +7 -6
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +5 -3
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +43 -48
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +96 -14
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +47 -15
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +6 -2
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +32 -2
- package/dist/knowledge/skills/resource-schema-authoring/examples/basic-resource-schema.example.md +2 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +17 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +75 -4
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +182 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +245 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +35 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +46 -12
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +480 -15
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +67 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +74 -14
- package/dist/knowledge/skills/resource-schema-authoring/references/polymorphic-per-scope-resources.md +28 -5
- package/dist/knowledge/skills/resource-schema-authoring/references/schema-variants-and-discriminators.md +25 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +34 -0
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +236 -18
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +54 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +35 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +327 -11
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +140 -4
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +155 -5
- package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +165 -0
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +9 -1
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +4 -0
- package/dist/knowledge/skills/seeding-operations/SKILL.md +33 -29
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +13 -5
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-cron-scheduler.md +67 -74
- package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +97 -24
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +205 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +205 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +229 -0
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +38 -3
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +211 -14
- package/dist/knowledge/skills/spec-component-update/SKILL.md +30 -11
- package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +10 -0
- package/dist/knowledge/skills/spec-feature-update/SKILL.md +47 -9
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +3 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +32 -5
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +30 -0
- package/dist/knowledge/skills/views-add-composite-view/SKILL.md +1 -0
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +13 -2
- package/dist/knowledge/skills/views-add-custom-view/references/framework-view-scope-and-full-custom-api.md +24 -0
- package/dist/knowledge/skills/views-app-level/SKILL.md +1 -0
- package/dist/knowledge/skills/views-app-level/references/framework-view-scope-and-full-custom-api.md +24 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +64 -0
- package/dist/knowledge/skills/views-execution-authoring/SKILL.md +3 -0
- package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +3 -3
- package/dist/knowledge/skills/views-execution-authoring/references/framework-user-facing-error-message-api.md +50 -0
- package/dist/knowledge/skills/website-anonymous-session/SKILL.md +43 -7
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +21 -1
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +21 -0
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +41 -1
- package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +735 -211
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +54 -7
- package/dist/knowledge/skills/website-layout-overrides/SKILL.md +67 -1
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -0
- package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +19 -5
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +94 -7
- package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +126 -0
- package/dist/knowledge/skills/website-section-contact/SKILL.md +96 -146
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-cta/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-faq/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-hero/SKILL.md +37 -26
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +14 -1
- package/dist/knowledge/skills/worker-authoring/SKILL.md +164 -0
- package/dist/knowledge/skills/worker-authoring/examples/worker-route.example.md +98 -0
- package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +65 -0
- package/dist/knowledge/topic-index.json +5335 -1010
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/knowledge/references/example.provider.contribution.backend-billing.md +0 -12
- package/dist/knowledge/skills/configure-billing/references/example-provider-contribution-and-backend-config.md +0 -48
- /package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/structured-artifact-action.json +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: journey-approve
|
|
3
|
-
description: "Guide the creator through ACCEPTING landed application-creation work — review the working edits and commit them. Use when the user says \"journey approve\", \"accept this run\", \"approve the landed files\", or asks how acceptance works. Acceptance is a git commit by
|
|
3
|
+
description: "Guide the creator through ACCEPTING landed application-creation work — review the working edits and commit them. Use when the user says \"journey approve\", \"accept this run\", \"approve the landed files\", or asks how acceptance works. Acceptance is a git commit, made by the creation runtime under the current autonomy posture or by the creator; there is no other approval mechanism."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Journey Approve — Acceptance Is a Commit
|
|
@@ -20,24 +20,44 @@ Read and apply these patterns from the application-developer point of view:
|
|
|
20
20
|
## Overview
|
|
21
21
|
|
|
22
22
|
There are no authority requests, approval queues or acceptance ceremonies. A playbook run lands
|
|
23
|
-
FILES in the specifications package; they are working edits until
|
|
24
|
-
|
|
23
|
+
FILES in the specifications package; they are working edits until they are committed — by the
|
|
24
|
+
creation runtime under the current autonomy posture, or by the creator. Git gives the whole safety
|
|
25
|
+
story: diff to review, commit to accept, revert to undo, log as the audit trail.
|
|
25
26
|
|
|
26
27
|
## Workflow
|
|
27
28
|
|
|
28
29
|
1. **Show what is awaiting acceptance** — `git status` and `git diff` in the application's
|
|
29
|
-
`specifications/` package, grouped by family.
|
|
30
|
+
`specifications/` package, grouped by family. What each family is, and what committing it
|
|
31
|
+
decides, is in `references/specification-family-map.md` — including why the domain plan and the
|
|
32
|
+
business model must be committed before the foundation step runs.
|
|
30
33
|
2. **Bring the evidence to the review**: the run's `generation` findings and the advisory
|
|
31
34
|
`judge` verdicts (from the run response or `GET /api/companion/traces/<sessionId>`) are the
|
|
32
35
|
reviewer's briefing — surface `CONCERN`/`GAP` rationales beside the diff they concern.
|
|
33
36
|
3. **The creator decides**, per file or wholesale: commit (accept), amend and commit, or discard
|
|
34
37
|
with `git checkout -- <path>` / re-run the playbook.
|
|
35
|
-
4. **
|
|
36
|
-
|
|
37
|
-
|
|
38
|
+
4. **Who commits depends on the autonomy posture, and the current posture is `yolo`.** Under it
|
|
39
|
+
the development companion commits for the creator: a finished coding run's writes, a
|
|
40
|
+
generation step's writes, and every pending playbook run's writes — the last just before the
|
|
41
|
+
next build task takes its baseline. Each such commit's body says it was *accepted
|
|
42
|
+
automatically under the application-creation autonomy posture*, so `git log` tells a person's
|
|
43
|
+
acceptance from the system's. The creator is informed by that history and by the board, and
|
|
44
|
+
overrides with `git revert`. The posture is not an application setting — you cannot switch it
|
|
45
|
+
from here. Under `guided` nothing is committed on the creator's behalf and the HUMAN runs every
|
|
46
|
+
commit; compose a message naming the playbook and families, and let them run it.
|
|
47
|
+
5. **Undoing a run** — discard with git, or revert the whole run in one call through the write
|
|
48
|
+
register (see `journey-run`), which refuses files edited since the run.
|
|
38
49
|
|
|
39
50
|
## Rules
|
|
40
51
|
|
|
41
|
-
- Never commit on the creator's behalf
|
|
52
|
+
- Never commit on the creator's behalf yourself. The companion's posture-governed commits are the
|
|
53
|
+
only automatic ones; an agent helping with acceptance reviews, explains and composes a message —
|
|
54
|
+
it does not run `git commit`.
|
|
55
|
+
- A playbook's declared approval policy gates nothing either. A step that says its result must be
|
|
56
|
+
approved has not been held for approval — the working edits are simply there to review.
|
|
42
57
|
- Rejecting the judge's concern and committing anyway is a legitimate outcome — record nothing;
|
|
43
58
|
the commit itself is the decision.
|
|
59
|
+
|
|
60
|
+
## References
|
|
61
|
+
|
|
62
|
+
- `references/specification-family-map.md` — where each family lands, what committing it decides,
|
|
63
|
+
tenancy, the build plan's task kinds, and how to revise a placement decision by hand.
|
|
@@ -0,0 +1,88 @@
|
|
|
1
|
+
# What each landed specification family is
|
|
2
|
+
|
|
3
|
+
Read this when:
|
|
4
|
+
|
|
5
|
+
- you are reviewing landed files and need to know what committing each one decides;
|
|
6
|
+
- a file you edited was overwritten by a run;
|
|
7
|
+
- a later step behaves as though an earlier decision was different from what you meant.
|
|
8
|
+
|
|
9
|
+
## A landing replaces the file
|
|
10
|
+
|
|
11
|
+
A run lands a family by writing `specifications/src/<directory>/index.ts`. **An existing file is
|
|
12
|
+
replaced, not refused.** A committed edit comes back with `git checkout -- <path>`; an uncommitted one
|
|
13
|
+
does not. Before re-running a playbook whose board entry lists that family in `wouldReplace`, commit
|
|
14
|
+
the edit you want to keep.
|
|
15
|
+
|
|
16
|
+
## The families
|
|
17
|
+
|
|
18
|
+
| Family | Lands in `specifications/src/…` | What committing it decides |
|
|
19
|
+
|---|---|---|
|
|
20
|
+
| `vision-brief` | `vision/` | What the product is. Only the idea is required. A valid vision brief is what the market and compliance research steps gate on. |
|
|
21
|
+
| `market-snapshot` | `market/` | Who the product is for and why they buy. See the `market-*` skills. |
|
|
22
|
+
| `requirements` | `requirements/` | What the product must do. A build task names what it serves in `servesRefs`, which is traceability only — never scope authority. |
|
|
23
|
+
| `roadmap` | `roadmap/` | Which requirements and success criteria each phase delivers. |
|
|
24
|
+
| `feature-drafts` | `feature-drafts/` | Draft features the market's benefits point at. The engineering feature specification is a separate artifact — see `spec-feature-update`. |
|
|
25
|
+
| `business-model` | `business-model/` | The revenue model and pricing sketch. **Never the billing catalogue**: landing a plan creates no product and no price. The foundation step reads it, when present, to decide which capabilities — billing among them — to enable, so review it before foundation runs. |
|
|
26
|
+
| `domain-plan` | `domain-plan/` | The modules, their resources, relationship intents, and **tenancy** (below). |
|
|
27
|
+
| `build-plan` | `build-plan/` | The ordered task graph the coding lane executes (below). |
|
|
28
|
+
| `placement-plan` | `placement-plan/` | Where each destination, operation and view appears in the shell (below). |
|
|
29
|
+
| `brand-brief` | `brand/` | The brand direction the logo pipeline reads. See `brand-logo-authoring`. |
|
|
30
|
+
| `compliance-program`, `document-facts`, `document-facts-authored`, `processor-register`, `document-publication`, `document-release-policy`, `document-release-set`, `compliance-document-candidate-set` | `compliance/`, `document-facts/`, `document-facts-authored/`, `processor-register/`, `document-publication/`, `document-release-policy/`, `document-releases/`, `compliance-document-candidates/` | The compliance and governed-document lane. See `compliance-document-authoring`. |
|
|
31
|
+
|
|
32
|
+
## Accepting a compliance programme pins a basis generation
|
|
33
|
+
|
|
34
|
+
A compliance programme records, on its postures and authorities, the `basisRef` and `basisVersion`
|
|
35
|
+
of the framework's assurance-authority basis its controls were accepted against. Two equal
|
|
36
|
+
generations promise the same meaning; a framework change that alters what a control means ships a new
|
|
37
|
+
generation, and the application re-accepts deliberately.
|
|
38
|
+
|
|
39
|
+
```bash
|
|
40
|
+
wildo context assurance-basis # report only
|
|
41
|
+
wildo context assurance-basis --check # exit non-zero when a pinned generation is not shipped
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
A pin the installed framework no longer ships is reported NOT SHIPPED: what those controls mean can no
|
|
45
|
+
longer be resolved. Either install the framework release that ships it, or re-accept against a shipped
|
|
46
|
+
generation — as a decision, not a find-and-replace. An application with no compliance specification is
|
|
47
|
+
reported as NOT DECLARED and never fails — but a specifications package that cannot be loaded fails,
|
|
48
|
+
because "could not read it" is not "declares nothing".
|
|
49
|
+
|
|
50
|
+
## Tenancy is decided in the domain plan
|
|
51
|
+
|
|
52
|
+
`tenancy` is `organizations` or `users`:
|
|
53
|
+
|
|
54
|
+
- `organizations` — users collaborate in shared workspaces. It enables the organizations capability,
|
|
55
|
+
and every resource is composed organization-scoped.
|
|
56
|
+
- `users` — every user's data is their own, and resources are user-scoped.
|
|
57
|
+
|
|
58
|
+
The foundation step takes tenancy from the domain plan first and falls back to the creator's interview
|
|
59
|
+
answer, refusing when neither supplies one. It treats the plan as the approved decision, so review and
|
|
60
|
+
commit the domain plan you mean before foundation runs.
|
|
61
|
+
|
|
62
|
+
## The build plan's task kinds
|
|
63
|
+
|
|
64
|
+
| Kind | What a task builds |
|
|
65
|
+
|---|---|
|
|
66
|
+
| `MODULE` | A whole application module's skeleton. |
|
|
67
|
+
| `RESOURCE_STAGE` | One stage of one resource, in the order `SCHEMA` → `CONFIG` → `UI_BEHAVIOR` → `SPEC`. |
|
|
68
|
+
| `RELATIONSHIP` | One relationship between two resources. |
|
|
69
|
+
| `COMPANION_GENERATION_STEP` | A deterministic step the framework runs itself (labels, email templates, logo, migrations) — never a coding-agent run. |
|
|
70
|
+
| `SHELL_PLACEMENT` | One shell surface's configuration, from the accepted placement plan. |
|
|
71
|
+
|
|
72
|
+
Order comes only from each task's prerequisites. A task's functional topic is context handed to the
|
|
73
|
+
agent, not a schedule.
|
|
74
|
+
|
|
75
|
+
## Editing a placement decision by hand
|
|
76
|
+
|
|
77
|
+
Each decision is one `(subject, surface)` pair: `PLACED` at an address or `DECLINED`, and a
|
|
78
|
+
`rationale` is required either way. The surfaces are `SETTINGS_HUB`, `SIDEBAR`, `USER_MENU` and
|
|
79
|
+
`COMMAND_MENU`.
|
|
80
|
+
|
|
81
|
+
Every decision carries an `origin`. When you change one:
|
|
82
|
+
|
|
83
|
+
1. set `origin` to `REVISED`;
|
|
84
|
+
2. move the panel's previous reasoning into `supersedes: { rationale }`;
|
|
85
|
+
3. write your own `rationale`.
|
|
86
|
+
|
|
87
|
+
The schema refuses a `REVISED` decision without `supersedes`, and a `DELIBERATED` one with it. Git
|
|
88
|
+
already shows what changed; `supersedes` keeps the argument the diff cannot show.
|
|
@@ -25,8 +25,17 @@ answer by name — so collect the full set before running.
|
|
|
25
25
|
|
|
26
26
|
## Workflow
|
|
27
27
|
|
|
28
|
-
1. **Discover the questions
|
|
29
|
-
|
|
28
|
+
1. **Discover the questions — and know that NO SURFACE SERVES THEM TODAY.** This step used to say
|
|
29
|
+
the playbook entry on `GET /api/companion/playbooks` carries its declared elicitation. It does
|
|
30
|
+
not: those entries are `PlaybookEligibility`, which says only `requiresElicitation: true` and
|
|
31
|
+
never what is asked. The questions are compiled into the playbook catalog the companion loads,
|
|
32
|
+
and no declared package entrypoint or companion route exposes them, so there is nothing an
|
|
33
|
+
application-side agent may read. A refused run names the missing refs — refs only, never the
|
|
34
|
+
question text — so it is a check on a set you already hold, not a way to discover one.
|
|
35
|
+
|
|
36
|
+
Until a read surface exists (tracked on the operator-answer epic), get the interview from the
|
|
37
|
+
creator or from whoever holds the framework catalog, and treat the declared `ref` values as the
|
|
38
|
+
contract: your answers are matched by ref, and an unknown ref is refused rather than guessed.
|
|
30
39
|
2. **Interview the creator** in their own words; map each answer onto the declared question refs
|
|
31
40
|
and vocabularies. Never invent or default an answer the creator did not give.
|
|
32
41
|
3. **Submit** — pass `elicitationAnswers` to `POST /api/companion/playbooks/<ref>/run`.
|
|
@@ -35,6 +44,32 @@ answer by name — so collect the full set before running.
|
|
|
35
44
|
legal-regulatory decisions, public sector/critical infrastructure). Ask them explicitly —
|
|
36
45
|
their answers shape which compliance playbooks matter later.
|
|
37
46
|
|
|
47
|
+
> **Protected companion requests need the local token.** The custom `/api/companion/**`
|
|
48
|
+
> router exempts `GET`, `HEAD` and `OPTIONS`, plus its explicitly listed browser paths:
|
|
49
|
+
> `/playbooks/refresh-board`, `/compliance/governance-facts` and `/coding-agent/cancel`.
|
|
50
|
+
> Other requests must carry `x-wildo-companion-token`, read from
|
|
51
|
+
> `./.wildo-saas/state/companion.token` (mode 0600). This is an HTTP-method/path policy,
|
|
52
|
+
> not a classification of business intent: read-only introspection uses protected `POST`.
|
|
53
|
+
> Targeted CLI requests attach the token automatically. A direct client must supply it
|
|
54
|
+
> for protected requests; never paste token contents into examples or logs.
|
|
55
|
+
>
|
|
56
|
+
> A missing or wrong token answers `401`; the sanitized body carries the authentication
|
|
57
|
+
> error type and a correlation id. The companion's warning log names the header/file
|
|
58
|
+
> under that correlation id. Exempt diagnostic methods remain reachable if a client holds
|
|
59
|
+
> an old token. The named browser exemptions do not exempt other POST reads or mutations.
|
|
60
|
+
>
|
|
61
|
+
> **The companion is a DEVELOPMENT surface. Never call it from application code.** It runs on
|
|
62
|
+
> loopback beside your checkout, it has no deployed counterpart and no production host, and a
|
|
63
|
+
> running application never reaches it. So a backend service, a frontend component or a worker that
|
|
64
|
+
> fetches `/api/companion/**` works on your machine and is simply gone in every deployed
|
|
65
|
+
> environment — with nothing failing at build time to tell you.
|
|
66
|
+
>
|
|
67
|
+
> The routes in this skill are for YOU, the agent working in the checkout, and for the command line
|
|
68
|
+
> and the creation workbench. When the application itself needs a fact at runtime, it must come from
|
|
69
|
+
> the application's own configuration, its own resources or its own services — never from the
|
|
70
|
+
> companion.
|
|
71
|
+
|
|
72
|
+
|
|
38
73
|
## Rules
|
|
39
74
|
|
|
40
75
|
- Intake only: answers feed generation; they accept nothing and unlock nothing by themselves.
|
|
@@ -33,10 +33,50 @@ those two clearly separated when proposing.
|
|
|
33
33
|
3. If nothing is eligible, say exactly which readiness preconditions are unmet and which playbook
|
|
34
34
|
would satisfy each — that IS the next step.
|
|
35
35
|
4. For unattended chaining, offer `POST /api/companion/playbooks/loop` with a goal and
|
|
36
|
-
`maximumIterations` instead of proposing one step at a time.
|
|
36
|
+
`maximumIterations` instead of proposing one step at a time. Say what the loop will NOT do:
|
|
37
|
+
- It never runs a playbook that declares an interview — those are filtered out, because a
|
|
38
|
+
model handed no answers can only invent or omit them. Run them with `journey-run` and the
|
|
39
|
+
creator's answers, before or between loops.
|
|
40
|
+
- One loop per companion. A second is refused, not queued.
|
|
41
|
+
- It stops for one of four named reasons: nothing eligible, the model chose to stop, the
|
|
42
|
+
iteration ceiling, or every lane of one iteration failed. Lanes per iteration default to 3
|
|
43
|
+
and cap at 5. Both limits are circuit breakers; nothing in the loop reads cost.
|
|
44
|
+
|
|
45
|
+
> **Protected companion requests need the local token.** The custom `/api/companion/**`
|
|
46
|
+
> router exempts `GET`, `HEAD` and `OPTIONS`, plus its explicitly listed browser paths:
|
|
47
|
+
> `/playbooks/refresh-board`, `/compliance/governance-facts` and `/coding-agent/cancel`.
|
|
48
|
+
> Other requests must carry `x-wildo-companion-token`, read from
|
|
49
|
+
> `./.wildo-saas/state/companion.token` (mode 0600). This is an HTTP-method/path policy,
|
|
50
|
+
> not a classification of business intent: read-only introspection uses protected `POST`.
|
|
51
|
+
> Targeted CLI requests attach the token automatically. A direct client must supply it
|
|
52
|
+
> for protected requests; never paste token contents into examples or logs.
|
|
53
|
+
>
|
|
54
|
+
> A missing or wrong token answers `401`; the sanitized body carries the authentication
|
|
55
|
+
> error type and a correlation id. The companion's warning log names the header/file
|
|
56
|
+
> under that correlation id. Exempt diagnostic methods remain reachable if a client holds
|
|
57
|
+
> an old token. The named browser exemptions do not exempt other POST reads or mutations.
|
|
58
|
+
>
|
|
59
|
+
> **The companion is a DEVELOPMENT surface. Never call it from application code.** It runs on
|
|
60
|
+
> loopback beside your checkout, it has no deployed counterpart and no production host, and a
|
|
61
|
+
> running application never reaches it. So a backend service, a frontend component or a worker that
|
|
62
|
+
> fetches `/api/companion/**` works on your machine and is simply gone in every deployed
|
|
63
|
+
> environment — with nothing failing at build time to tell you.
|
|
64
|
+
>
|
|
65
|
+
> The routes in this skill are for YOU, the agent working in the checkout, and for the command line
|
|
66
|
+
> and the creation workbench. When the application itself needs a fact at runtime, it must come from
|
|
67
|
+
> the application's own configuration, its own resources or its own services — never from the
|
|
68
|
+
> companion.
|
|
69
|
+
|
|
37
70
|
|
|
38
71
|
## Rules
|
|
39
72
|
|
|
40
73
|
- Never soften a failed READINESS precondition into a proposal.
|
|
74
|
+
- Eligible does not mean not yet done. The board keeps no record of what ran, so a playbook
|
|
75
|
+
that already landed is offered again whenever its preconditions still hold. Check
|
|
76
|
+
`wouldReplace` before proposing it: a re-run regenerates what exists. The one exception is build
|
|
77
|
+
decomposition, withheld once the build plan is fully executed and none of its inputs has moved.
|
|
78
|
+
- `staleOutputs` is an annotation, never a gate — nothing refuses a run because an output looks
|
|
79
|
+
stale. It is also only as complete as the playbook's DECLARED inputs, so an output that does
|
|
80
|
+
not read as stale is not thereby proven current.
|
|
41
81
|
- A SEQUENCING-only block is the creator's call: present it as "runnable out of sequence".
|
|
42
82
|
- Do not execute anything from this skill — hand the chosen ref to `journey-run`.
|
|
@@ -30,14 +30,27 @@ IN FLIGHT = uncommitted working edits. WHAT HAPPENED = the companion's execution
|
|
|
30
30
|
2. **Capability position** — `GET /api/companion/playbooks`: which playbooks have already landed
|
|
31
31
|
their families, which are eligible, what remains blocked and why.
|
|
32
32
|
3. **Build progress** — `GET /api/companion/build/next`: where the coding lane stands against the
|
|
33
|
-
committed build plan.
|
|
33
|
+
committed build plan. Report `plan: null` as finished only when `exhausted` is present; with
|
|
34
|
+
`stuckTasks` it means every ready task is stuck, and each entry's `reason` names the remedy.
|
|
34
35
|
4. **Run evidence** — `GET /api/companion/traces` and per-session detail: model attempts,
|
|
35
36
|
validator findings, judge verdicts. Cite sessions by id so every claim is checkable.
|
|
36
|
-
5.
|
|
37
|
-
|
|
37
|
+
5. **Coherence** — `GET /api/companion/playbooks/coherence`: what the working tree states with
|
|
38
|
+
nothing behind it, and what references something that is absent. This is the ONLY surface that
|
|
39
|
+
answers cross-family questions. A family's own validator sees one family and cannot resolve a
|
|
40
|
+
reference into another's vocabulary unless a caller hands it that family's refs, and nothing in
|
|
41
|
+
the running lane does — so a roadmap phase naming a requirement that does not exist, or a notice
|
|
42
|
+
citing a fact that was regenerated out from under it, is silent everywhere else and named here.
|
|
43
|
+
The response carries a rendered `markdown` alongside the structured report.
|
|
44
|
+
6. Compose: accepted → in flight → blocked (with reasons) → coherence findings → judge findings
|
|
45
|
+
worth review → next proposed step.
|
|
38
46
|
|
|
39
47
|
## Rules
|
|
40
48
|
|
|
41
49
|
- Every claim carries its source (a commit, a route response, a trace session id).
|
|
42
50
|
- Never present a judge verdict as a gate outcome; it is recorded review input.
|
|
43
51
|
- Never reconstruct "approvals" from conversation — acceptance exists only as commits.
|
|
52
|
+
- The coherence report REPORTS and never refuses, exactly like the judge — a dangling reference has
|
|
53
|
+
not blocked anything, and the remedy is usually to re-run the step that should have re-landed.
|
|
54
|
+
- Report its `familiesAbsent` and `familiesUnreadable` alongside its findings. An absent family is a
|
|
55
|
+
normal state and its questions were simply skipped, so a clean report over half the families is not
|
|
56
|
+
the same claim as a clean report over all of them.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: journey-run
|
|
3
|
-
description: "Execute one selected playbook and read what it landed. Use when the user says \"journey run\", \"run the selected playbook\", \"execute this playbook\", or after journey-next produced a choice. Files land in the specifications package as working edits; a
|
|
3
|
+
description: "Execute one selected playbook and read what it landed. Use when the user says \"journey run\", \"run the selected playbook\", \"execute this playbook\", or after journey-next produced a choice. Files land in the specifications package as working edits; acceptance is a commit, made by the creator or by the development companion under the current autonomy posture."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Journey Run — Execute One Playbook
|
|
@@ -19,9 +19,12 @@ Read and apply these patterns from the application-developer point of view:
|
|
|
19
19
|
|
|
20
20
|
## Overview
|
|
21
21
|
|
|
22
|
-
A run
|
|
23
|
-
|
|
24
|
-
|
|
22
|
+
A structured-generation run produces schema-constrained outputs, validates each against its
|
|
23
|
+
family's semantic validator, and feeds rejection findings back through bounded retries
|
|
24
|
+
(default: three total attempts per output). It lands the complete valid set as working files,
|
|
25
|
+
then asks the advisory judge when evaluation criteria are declared. Other playbooks assess,
|
|
26
|
+
research, choreograph, verify or dispatch coding work; read the returned result kind before
|
|
27
|
+
interpreting fields such as `landed`, `generation`, `assessed` or `dispatched`.
|
|
25
28
|
|
|
26
29
|
## Workflow
|
|
27
30
|
|
|
@@ -45,11 +48,93 @@ when the playbook carries evaluation criteria — asks the ADVISORY judge for ve
|
|
|
45
48
|
4. **Hand back to the creator**: the files are working edits. Review with `git diff`; a human
|
|
46
49
|
`git commit` in the specifications package is the acceptance. Nothing else accepts anything.
|
|
47
50
|
|
|
51
|
+
> **Protected companion requests need the local token.** The custom `/api/companion/**`
|
|
52
|
+
> router exempts `GET`, `HEAD` and `OPTIONS`, plus its explicitly listed browser paths:
|
|
53
|
+
> `/playbooks/refresh-board`, `/compliance/governance-facts` and `/coding-agent/cancel`.
|
|
54
|
+
> Other requests must carry `x-wildo-companion-token`, read from
|
|
55
|
+
> `./.wildo-saas/state/companion.token` (mode 0600). This is an HTTP-method/path policy,
|
|
56
|
+
> not a classification of business intent: read-only introspection uses protected `POST`.
|
|
57
|
+
> Targeted CLI requests attach the token automatically. A direct client must supply it
|
|
58
|
+
> for protected requests; never paste token contents into examples or logs.
|
|
59
|
+
>
|
|
60
|
+
> A missing or wrong token answers `401`; the sanitized body carries the authentication
|
|
61
|
+
> error type and a correlation id. The companion's warning log names the header/file
|
|
62
|
+
> under that correlation id. Exempt diagnostic methods remain reachable if a client holds
|
|
63
|
+
> an old token. The named browser exemptions do not exempt other POST reads or mutations.
|
|
64
|
+
>
|
|
65
|
+
> **The companion is a DEVELOPMENT surface. Never call it from application code.** It runs on
|
|
66
|
+
> loopback beside your checkout, it has no deployed counterpart and no production host, and a
|
|
67
|
+
> running application never reaches it. So a backend service, a frontend component or a worker that
|
|
68
|
+
> fetches `/api/companion/**` works on your machine and is simply gone in every deployed
|
|
69
|
+
> environment — with nothing failing at build time to tell you.
|
|
70
|
+
>
|
|
71
|
+
> The routes in this skill are for YOU, the agent working in the checkout, and for the command line
|
|
72
|
+
> and the creation workbench. When the application itself needs a fact at runtime, it must come from
|
|
73
|
+
> the application's own configuration, its own resources or its own services — never from the
|
|
74
|
+
> companion.
|
|
75
|
+
|
|
76
|
+
|
|
48
77
|
## Rules
|
|
49
78
|
|
|
50
79
|
- READINESS refusals are final until the missing input exists; SEQUENCING is ignored for an
|
|
51
|
-
explicit run — asking for the playbook by name IS the acknowledgement.
|
|
80
|
+
explicit run — asking for the playbook by name IS the acknowledgement. Running a COMPOSITE
|
|
81
|
+
explicitly admits its children past sequencing too; readiness still refuses each of them.
|
|
82
|
+
- One composite runs per companion. A second — the same one or a different one — is refused, not
|
|
83
|
+
queued; watch the live one with `GET /api/companion/playbooks/runs`.
|
|
84
|
+
- A composite checkpoints after every iteration. When a run ends because of the environment
|
|
85
|
+
(infrastructure or quota took every failing child), the response says `resumableFromCheckpoint`,
|
|
86
|
+
and re-running the same playbook ref resumes the paid-for iterations. The iteration count
|
|
87
|
+
CONTINUES — a run that finished 4 of 10 gets 6 more, not 10. A resumed run says so in
|
|
88
|
+
`resumedFrom`.
|
|
52
89
|
- The judge is advisory: a `GAP` verdict never un-lands a file. Surface it as review input and,
|
|
53
90
|
when the creator agrees, feed it into a re-run's `creatorBrief`.
|
|
54
|
-
-
|
|
55
|
-
|
|
91
|
+
- Inspect recorded execution evidence through `GET /api/companion/traces/<sessionId>`: it returns
|
|
92
|
+
events and step artifact filenames. Fetch a selected body through
|
|
93
|
+
`GET /api/companion/traces/<sessionId>/steps/<stepDirName>/artifacts/<fileName>`,
|
|
94
|
+
using the names returned by the session. Briefs and model answers are separate artifacts when
|
|
95
|
+
recorded; their presence is diagnostic evidence, not proof that the generated behavior works.
|
|
96
|
+
- A playbook's declared `approval` policy gates NOTHING, and neither does its failure policy. Never
|
|
97
|
+
report a run as held pending approval — see `references/framework-playbook-approval-policy.md`.
|
|
98
|
+
|
|
99
|
+
- **A run can stop and ASK.** When a step meets a product decision it cannot derive, it suspends
|
|
100
|
+
before producing anything and answers with its `runId`. The response is the only place that id
|
|
101
|
+
appears, so `GET /api/companion/playbooks/suspended` lists every waiting run with its `requests`
|
|
102
|
+
— each question and the `ref` you answer it by. Continue one with
|
|
103
|
+
`POST /api/companion/playbooks/runs/<runId>/resume`:
|
|
104
|
+
- `{ "action": "accept", "answers": [{ "ref": "<question ref>", "answer": "<string>" }] }` —
|
|
105
|
+
`accept` with no answers is refused, because "I answered" and "you decide" produce different
|
|
106
|
+
artifacts;
|
|
107
|
+
- `{ "action": "decline" }` — the run continues on a stated assumption, which is recorded;
|
|
108
|
+
- `{ "action": "cancel" }` — nothing is generated and nothing is written.
|
|
109
|
+
|
|
110
|
+
Question rounds default to 3; once spent, the run proceeds with what it has rather than failing.
|
|
111
|
+
The unattended loop supplies no answers. Today no playbook the loop may run can suspend — the
|
|
112
|
+
one that can also declares an interview, which the loop never runs — but that is a property of the
|
|
113
|
+
catalogue, not a rule the loop enforces.
|
|
114
|
+
- **Nothing in the playbook lane caps spend.** Its only bound on model calls is a runaway breaker
|
|
115
|
+
(1000 calls an hour by default, `WILDO_PLAYBOOK_MODEL_CALL_HOURLY_BREAKER` to change). Set real
|
|
116
|
+
spend limits on the model provider account.
|
|
117
|
+
- **The judge can only judge groundedness against what the creator said.** Pass the `creatorBrief`
|
|
118
|
+
and `elicitationAnswers` on the run; without them, criteria that ask whether the artifacts are
|
|
119
|
+
grounded in the creator's input come back `INDETERMINATE`. The overall verdict is the worst one
|
|
120
|
+
present (`PASS` < `CONCERN` < `INDETERMINATE` < `GAP`). A judge that could not run returns
|
|
121
|
+
`judged: false` with the reason in `skipped` — that is not a pass. To judge values again, send
|
|
122
|
+
them to `POST /api/companion/playbooks/<playbookRef>/judge` as `artifacts: [{ family, value }]`
|
|
123
|
+
(with the brief and answers) — it reads no files and lands nothing.
|
|
124
|
+
- **On a composite that researches, read `provenance`.** Each landing child reports how many
|
|
125
|
+
gathered evidence URLs it actually cited (`citedUrlCount`) against how many were available
|
|
126
|
+
(`evidenceUrlCount`). Zero cited against a non-zero gathered is an ungrounded artifact that
|
|
127
|
+
otherwise looks like a success.
|
|
128
|
+
- **A whole run can be undone without git.** `GET /api/companion/runs/writes` lists what each
|
|
129
|
+
playbook run wrote; `POST /api/companion/runs/writes/<runId>/revert` restores the previous bytes.
|
|
130
|
+
It refuses a file edited since the run — `{ "force": true }` reverts it anyway and discards that
|
|
131
|
+
edit. A coding-agent run is not in this register; its undo is git.
|
|
132
|
+
- A step that convenes expert reviewers needs their charters derived, accepted and loaded first —
|
|
133
|
+
see `references/expert-personas-and-deliberations.md`.
|
|
134
|
+
|
|
135
|
+
## References
|
|
136
|
+
|
|
137
|
+
- `references/framework-playbook-approval-policy.md` — why a playbook declaring `approve_before` is
|
|
138
|
+
not thereby gated, and why its failure policy keeps and flags nothing.
|
|
139
|
+
- `references/expert-personas-and-deliberations.md` — deriving, accepting and protecting reviewer
|
|
140
|
+
charters, and what a deliberation refuses.
|
|
@@ -0,0 +1,46 @@
|
|
|
1
|
+
# Expert personas and deliberations
|
|
2
|
+
|
|
3
|
+
Read this when:
|
|
4
|
+
|
|
5
|
+
- a run or a deliberation refuses because a reviewer role has no charter;
|
|
6
|
+
- you want a panel of reviewers to choose between several candidate texts (a logo brief, a piece of
|
|
7
|
+
copy) instead of accepting one generation;
|
|
8
|
+
- you hand-edited a reviewer charter and need to know whether re-deriving it will overwrite you.
|
|
9
|
+
|
|
10
|
+
## Charters are derived from YOUR application, then committed
|
|
11
|
+
|
|
12
|
+
A reviewer is not a generic model. It is a **charter** compiled from a framework role template and
|
|
13
|
+
this application's own artifacts (vision, market, brand, design system). Five role templates exist:
|
|
14
|
+
`information-architect`, `art-director`, `design-system-guardian`, `brand-strategist` and
|
|
15
|
+
`copy-chief`. An application only has the charters it has derived.
|
|
16
|
+
|
|
17
|
+
1. `POST /api/companion/expert-personas/derive` with `{ "roleRef": "<role>" }` — stages a proposal.
|
|
18
|
+
Every call derives; there is no cache.
|
|
19
|
+
2. `POST /api/companion/expert-personas/accept` with the same `roleRef` — writes the charter into
|
|
20
|
+
`specifications/src/personas/`, where it is reviewed and committed like any other artifact.
|
|
21
|
+
3. **Restart the companion.** Charters are loaded into reviewer agents at startup, so a charter
|
|
22
|
+
accepted afterwards has no agent until the next start.
|
|
23
|
+
|
|
24
|
+
## Hand-tuning is protected
|
|
25
|
+
|
|
26
|
+
Add an `authored` block to a committed charter when you edit it by hand. Accept then **refuses to
|
|
27
|
+
overwrite** that charter and tells you to merge the new proposal yourself or remove the block. Without
|
|
28
|
+
the block, the next accept replaces your edit.
|
|
29
|
+
|
|
30
|
+
Accept validates the whole resulting charter set before writing anything: an ERROR refuses the write,
|
|
31
|
+
and WARN-severity findings come back on the response for you to read. Nothing re-derives a charter on
|
|
32
|
+
its own when your application changes — re-derive and accept when you want it to reflect the
|
|
33
|
+
application as it now stands.
|
|
34
|
+
|
|
35
|
+
## Deliberations
|
|
36
|
+
|
|
37
|
+
`POST /api/companion/deliberations/run` convenes the reviewers over several TEXT candidates: a rubric,
|
|
38
|
+
bounded review rounds, then a synthesis.
|
|
39
|
+
|
|
40
|
+
- **It fails closed on charters.** A named role with no loaded charter is refused with an instruction
|
|
41
|
+
to derive and accept it, then restart the companion — it never silently degrades into a single
|
|
42
|
+
generation.
|
|
43
|
+
- **Only text.** A non-text candidate is refused.
|
|
44
|
+
- **It is expensive by construction** — candidates × reviewers per round, plus the rubric and the
|
|
45
|
+
synthesis. Use it where a decision has several defensible answers, not where the artifacts already
|
|
46
|
+
determine the answer.
|
|
@@ -0,0 +1,108 @@
|
|
|
1
|
+
# The `approval` value in a playbook is not a gate
|
|
2
|
+
|
|
3
|
+
Every playbook in the installed catalogue carries an `approval` value, and several read
|
|
4
|
+
`approve_before` or `approve_result`. Nothing reads the field.
|
|
5
|
+
|
|
6
|
+
Read this when:
|
|
7
|
+
|
|
8
|
+
- a playbook you are about to run declares that its result must be approved;
|
|
9
|
+
- you are about to tell a creator that a run is waiting for approval;
|
|
10
|
+
- you are wondering what happens to partial work when a run fails.
|
|
11
|
+
|
|
12
|
+
The short answer to all three: running is unattended, and acceptance is a human `git commit` because
|
|
13
|
+
no other path exists — not because a policy said so.
|
|
14
|
+
|
|
15
|
+
## Import Origins
|
|
16
|
+
|
|
17
|
+
- `@wildo-ai/saas-models`
|
|
18
|
+
|
|
19
|
+
## Source Excerpts
|
|
20
|
+
|
|
21
|
+
### Origin Package: `@wildo-ai/saas-models`
|
|
22
|
+
|
|
23
|
+
```typescript
|
|
24
|
+
/**
|
|
25
|
+
* Per-playbook approval posture (design plan OQ-3).
|
|
26
|
+
*
|
|
27
|
+
* ⚠️ **Read since 2026-09-22 (#111) at ONE KIND of place: the boundary of a COMPOSITE run.** When a
|
|
28
|
+
* lane (a playbook declaring `method.choreography`) ends, ITS OWN `approval` decides whether the run
|
|
29
|
+
* leaves a person an `approve_result` decision on the decision plane about the files its children
|
|
30
|
+
* landed — `auto` owes nothing, `notify` owes a record, `approve_result` and `approve_before` owe the
|
|
31
|
+
* decision (nothing suspends BEFORE a run, so the stronger reading of `approve_before` is honoured
|
|
32
|
+
* at the boundary that exists). One run can therefore leave SEVERAL: a root composite's own, plus
|
|
33
|
+
* one for every nested lane that owed one, because a lane is where the question genuinely arises —
|
|
34
|
+
* inside one run a lane lands the domain plan and the next builds on it. The autonomy posture
|
|
35
|
+
* decides what a decision DOES: under the decided YOLO posture it is recorded on the run's row and
|
|
36
|
+
* the run concludes — a marked gate that notifies and proceeds; holding the run for it is the GUIDED
|
|
37
|
+
* posture's and is not built.
|
|
38
|
+
*
|
|
39
|
+
* On a LEAF playbook the field is still authored intent only: a leaf run is not gated, and a leaf
|
|
40
|
+
* whose JSON reads `"approval": "approve_before"` runs when it is asked to run. Do not tell a creator
|
|
41
|
+
* a leaf run is held pending approval. The same holds for the failure policy below, which the same
|
|
42
|
+
* lane boundary reads to frame the decision (discard first under `revert_changeset`) and never to
|
|
43
|
+
* revert on its own.
|
|
44
|
+
*
|
|
45
|
+
* **Measured 2026-08-29 alongside issue #103,** before the boundary existed:
|
|
46
|
+
* `MetaWorkflow_ApprovalPolicy` had zero consumers outside this file and the 20 playbook
|
|
47
|
+
* definitions that author it. The same is true of the journey-level `Journey_AutonomyPreset` that
|
|
48
|
+
* was to map over it, and of the `wildo journey set-autonomy` command its JSDoc names — that
|
|
49
|
+
* command exists in no CLI. So a playbook declaring `APPROVE_BEFORE` is not gated, and one
|
|
50
|
+
* declaring `AUTO` is not thereby unattended.
|
|
51
|
+
*
|
|
52
|
+
* It is kept rather than deleted because — unlike the `qualityGates` field removed in the same
|
|
53
|
+
* pass — nothing else delivers it. `qualityGates` was a second description of live checks;
|
|
54
|
+
* this is a real posture nobody has built, and deleting it would discard the design rather than
|
|
55
|
+
* the duplication. Build-or-delete is a decision, tracked as its own issue (#111).
|
|
56
|
+
*
|
|
57
|
+
* **DECIDED 2026-08-30: DEFERRED, and the deferral is the point.** Not "we did not get to it" —
|
|
58
|
+
* `application-creation-directive.md` says the system must WORK first and that restrictions arrive
|
|
59
|
+
* later, from a real incident, as judge-style guards rather than ceremony wired into the mechanism.
|
|
60
|
+
* An inert approval policy is therefore the INTENDED posture right now, not a hole to plug.
|
|
61
|
+
*
|
|
62
|
+
* So read the effective state precisely, because the two halves differ:
|
|
63
|
+
*
|
|
64
|
+
* - **Running is unattended.** Nothing gates a playbook run — no preset, no policy, no failure
|
|
65
|
+
* handling. That is full-YOLO behaviour, arrived at by absence rather than by declaration.
|
|
66
|
+
* - **Accepting is not — but by ABSENCE, not by rule.** Nothing in the runtime performs a commit
|
|
67
|
+
* (re-verified 2026-09-06), so acceptance is a human `git commit` because no other path exists.
|
|
68
|
+
*
|
|
69
|
+
* The rule conflict this comment used to record — `one-source-of-truth.md` Rule 3 read as "only a
|
|
70
|
+
* human commits" against the directive's YOLO row — was SETTLED by D5's amendment on 2026-09-03: the
|
|
71
|
+
* autonomy posture governs who commits, the posture is YOLO for all, and "only a human commits"
|
|
72
|
+
* describes GUIDED rather than a floor. So this is now a missing mechanism, not an undecided rule;
|
|
73
|
+
* see `journey.application-creation.schemas.ts` for what building it still owes.
|
|
74
|
+
*
|
|
75
|
+
* The paragraph here claimed until 2026-08-29 that "the non-bypassable floor (budgets,
|
|
76
|
+
* destructive operations, off-machine effects — implementation-spec P-28) hard-gates in ALL
|
|
77
|
+
* presets regardless of this field." Do not restore that sentence: no such gate runs, and a
|
|
78
|
+
* safety claim is the worst thing to leave standing on an unbuilt mechanism.
|
|
79
|
+
*/
|
|
80
|
+
export enum MetaWorkflow_ApprovalPolicy {
|
|
81
|
+
AUTO = "auto",
|
|
82
|
+
NOTIFY = "notify",
|
|
83
|
+
APPROVE_RESULT = "approve_result",
|
|
84
|
+
APPROVE_BEFORE = "approve_before",
|
|
85
|
+
}
|
|
86
|
+
|
|
87
|
+
/**
|
|
88
|
+
* What the runner does when a playbook run fails mid-flight (review F-5) —
|
|
89
|
+
* a failed CODING_AGENT run must never leave a silent half-applied
|
|
90
|
+
* change-set: it is either reverted or kept and flagged for human triage.
|
|
91
|
+
*/
|
|
92
|
+
/**
|
|
93
|
+
* What a playbook run does with its partial work when it fails.
|
|
94
|
+
*
|
|
95
|
+
* **Read at the lane boundary since 2026-09-22 (#111), and only there.** A composite run that ended
|
|
96
|
+
* with every child of an iteration failed carries this policy into the boundary decision it leaves
|
|
97
|
+
* for a person: `revert_changeset` puts DISCARD first among the options, `keep_and_flag` keeps the
|
|
98
|
+
* landings and flags the failure. Neither is performed by the runtime — git already makes every
|
|
99
|
+
* landing visible and reversible, and a lane that failed on its last iteration may have landed good
|
|
100
|
+
* work before it — so the reader decides. On a LEAF run the field is still authored intent only
|
|
101
|
+
* (measured 2026-08-29, issue #103: zero consumers then), and `revert_changeset` has never been
|
|
102
|
+
* performed by anything.
|
|
103
|
+
*/
|
|
104
|
+
export enum MetaWorkflow_FailurePolicy {
|
|
105
|
+
REVERT_CHANGESET = "revert_changeset",
|
|
106
|
+
KEEP_AND_FLAG = "keep_and_flag",
|
|
107
|
+
}
|
|
108
|
+
```
|
|
@@ -28,12 +28,22 @@ There is no separate journey database — never infer state from conversation me
|
|
|
28
28
|
|
|
29
29
|
1. **Read the eligibility board** — `GET /api/companion/playbooks`.
|
|
30
30
|
Each entry reports `eligible`, its `phase`, every precondition verdict, `unmet` reasons,
|
|
31
|
-
`wouldReplace` (families
|
|
31
|
+
`wouldReplace` (existing output families), `staleOutputs` (changed inputs), and `unlandableFamilies`.
|
|
32
|
+
These impact annotations include the outputs of composed children. `outputOwners` names the
|
|
33
|
+
declaring playbooks; `unresolvedPlaybookRefs` names children missing from the catalog, so unknown
|
|
34
|
+
scope is never mistaken for no output. Child impact is descriptive: the parent’s readiness still
|
|
35
|
+
follows its own preconditions and direct landing contract.
|
|
32
36
|
2. **Read the coding lane** — `GET /api/companion/build/next` names the next build-plan task the
|
|
33
|
-
dispatcher would execute, derived from the committed build plan and git.
|
|
37
|
+
dispatcher would execute, derived from the committed build plan and git. `plan: null` has two
|
|
38
|
+
meanings: with `exhausted`, every task landed; with a non-empty `stuckTasks`, nothing ready can
|
|
39
|
+
run, and each entry's `reason` says what unblocks it. The usual one is a run that wrote its work
|
|
40
|
+
without committing it: a task lands only once its product is committed.
|
|
34
41
|
3. **Read recent activity** — `GET /api/companion/traces` lists recent execution sessions;
|
|
35
|
-
`GET /api/companion/traces/<sessionId>`
|
|
36
|
-
|
|
42
|
+
`GET /api/companion/traces/<sessionId>` returns ordered events and each step’s artifact filenames.
|
|
43
|
+
Use the returned `stepDirName` and filename with
|
|
44
|
+
`GET /api/companion/traces/<sessionId>/steps/<stepDirName>/artifacts/<fileName>`
|
|
45
|
+
to read a recorded brief or model answer. An event summary is not the artifact body;
|
|
46
|
+
a session can have events without a corresponding recorded artifact.
|
|
37
47
|
4. **Read acceptance state** — `git status` inside the application's `specifications/` package.
|
|
38
48
|
Uncommitted files are working edits; committed files are the accepted application.
|
|
39
49
|
|