@wildo-ai/framework-knowledge 1.1.4 → 1.1.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/claude-marketplace/.claude-plugin/marketplace.json +14 -0
- package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +8 -0
- package/dist/claude-marketplace/plugins/wildo/agents/wildo-deriver.md +41 -0
- package/dist/claude-marketplace/plugins/wildo/hooks/hooks.json +18 -0
- package/dist/claude-marketplace/plugins/wildo/monitors/monitors.json +8 -0
- package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +38 -0
- package/dist/claude-marketplace/plugins/wildo/references/approval-and-failure-policy.md +110 -0
- package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +29 -0
- package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +61 -0
- package/dist/claude-marketplace/plugins/wildo/references/expert-personas-and-deliberations.md +46 -0
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +67 -0
- package/dist/claude-marketplace/plugins/wildo/references/specification-family-map.md +88 -0
- package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +43 -0
- package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +70 -0
- package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +38 -0
- package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +23 -0
- package/dist/claude-marketplace/plugins/wildo/skills/next/SKILL.md +39 -0
- package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +39 -0
- package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +38 -0
- package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +38 -0
- package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +37 -0
- 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 +547 -17
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts +19 -0
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js +47 -1
- package/dist/esm/framework-knowledge.loader.js.map +1 -1
- package/dist/esm/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 +2 -2
- 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 -4
- 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 +135 -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 +208 -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 +218 -9
- 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 +374 -11
- 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 +6 -4
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +22 -20
- 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 +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 +1 -6
- 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 +62 -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 +188 -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 +74 -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 +80 -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 +18 -8
- 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 +81 -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 +31 -11
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +132 -10
- 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 +68 -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 +84 -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 +69 -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 +2 -2
- 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 -2
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +78 -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 +93 -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 +104 -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 +184 -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/cross_cutting.feature-development/playbook.definition.d.ts +59 -0
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js +72 -0
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +66 -0
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +115 -0
- package/dist/esm/playbooks/cross_cutting.refinement/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 +172 -2
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +147 -2
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +50 -0
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +54 -0
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -0
- 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 +158 -5
- 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 +173 -5
- 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 +6 -5
- 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 +9 -8
- 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 +23 -4
- 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 +6 -4
- 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 +22 -13
- 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 +193 -28
- 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 +173 -34
- 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 +3 -2
- 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 +7 -3
- 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 +183 -6
- 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 +192 -6
- 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 +3 -2
- 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 +4 -3
- 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 +173 -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 +264 -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.feature-drafts/playbook.definition.d.ts +45 -0
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js +46 -0
- package/dist/esm/playbooks/top_down.feature-drafts/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 +3 -2
- 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 +7 -3
- 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 +3 -2
- 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 -4
- 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 +33 -5
- 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 +28 -4
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +3 -3
- 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 +5 -3
- 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 +6 -4
- 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 +19 -5
- 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 +156 -5
- 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 -5
- 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 +7 -6
- 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 +28 -19
- 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 +40 -0
- package/dist/knowledge/playbooks/bottom_up.build/method.md +81 -0
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +89 -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 +1234 -80
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +53 -14
- 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 +743 -64
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +10 -21
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +34 -49
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -21
- package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +93 -0
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +61 -0
- package/dist/knowledge/playbooks/bottom_up.conception/method.md +98 -0
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +98 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +109 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +77 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +9 -11
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +16 -16
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +181 -0
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +73 -0
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +222 -145
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +60 -24
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +152 -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 +67 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +236 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +62 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +117 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +86 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +71 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +92 -0
- package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +83 -0
- package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +65 -0
- package/dist/knowledge/playbooks/cross_cutting.feature-development/method.md +42 -0
- package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +73 -0
- package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +46 -0
- package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +108 -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 +964 -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 +191 -21
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +12 -18
- package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +48 -0
- package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +66 -0
- 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 +349 -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 +24 -11
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -18
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +9 -18
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +26 -52
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +14 -18
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +99 -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 +211 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +66 -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 +40 -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 +37 -14
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +19 -69
- package/dist/knowledge/playbooks/top_down.compliance-research/method.md +78 -0
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +41 -0
- package/dist/knowledge/playbooks/top_down.definition/method.md +106 -0
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +120 -0
- package/dist/knowledge/playbooks/top_down.expert-personas/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +46 -0
- package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +72 -0
- package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +57 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/method.md +51 -165
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +25 -45
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +42 -0
- package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +44 -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 +245 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +70 -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 -13
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +28 -8
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +12 -19
- 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 +57 -0
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +25 -10
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +16 -20
- 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 +24 -17
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +12 -18
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +12 -4
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +23 -20
- 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/backend.inbound-channels.handler-definition.md +212 -0
- package/dist/knowledge/references/backend.inbound-handlers.agents.md +45 -0
- package/dist/knowledge/references/backend.inbound-handlers.definition.md +218 -0
- 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 +649 -10
- 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 +174 -0
- package/dist/knowledge/references/cli.market.generate-command.md +18 -2
- 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 +28 -22
- 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-technical-doc.provider-component.slot.md +83 -0
- package/dist/knowledge/references/engine.saas-website.config.md +22 -10
- package/dist/knowledge/references/example.authorization.service-provider-organization-wide-access.md +12 -0
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +13 -12
- package/dist/knowledge/references/example.backend.custom-operation.create-postfix.md +7 -3
- package/dist/knowledge/references/example.config.app-shell.command-menu-items.md +7 -0
- package/dist/knowledge/references/example.config.app-shell.full.md +53 -7
- package/dist/knowledge/references/example.config.backend.billing-enable.md +14 -0
- package/dist/knowledge/references/example.config.backend.inbound-email.md +14 -0
- package/dist/knowledge/references/example.config.backend.required-floors.md +11 -0
- package/dist/knowledge/references/example.config.design-system.full.md +3 -0
- package/dist/knowledge/references/example.config.navigation.full.md +45 -2
- package/dist/knowledge/references/example.config.provider-usage-pricing.md +36 -0
- package/dist/knowledge/references/example.config.provider.backend-scope-billing.md +5 -3
- package/dist/knowledge/references/example.config.provider.backend-scope-inbound-email.md +16 -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.autonomous-agent.md +23 -0
- package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +36 -0
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +30 -6
- package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +7 -11
- package/dist/knowledge/references/example.guidance.bound-survey-flow.md +82 -0
- package/dist/knowledge/references/example.inbound.application-endpoint-handler.md +72 -0
- package/dist/knowledge/references/example.inbound.email-channel-handler.md +47 -0
- package/dist/knowledge/references/example.inbound.email-to-todo.md +150 -0
- package/dist/knowledge/references/example.infra.environment-config.local.md +104 -43
- package/dist/knowledge/references/example.layout-3d.own-layout.md +16 -0
- package/dist/knowledge/references/example.layout-3d.registration.md +15 -0
- 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 +46 -16
- package/dist/knowledge/references/example.module.relationships.discriminator.md +2 -2
- package/dist/knowledge/references/example.organizations.serves-as-provider.md +12 -0
- package/dist/knowledge/references/example.provider.address-lookup.adapter.md +64 -0
- package/dist/knowledge/references/example.provider.backend-module-shape.md +34 -13
- package/dist/knowledge/references/example.provider.frontend-app.module.md +112 -0
- package/dist/knowledge/references/example.provider.frontend-facet.package-module.md +85 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +34 -13
- package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +25 -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 +16 -0
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +5 -0
- package/dist/knowledge/references/example.resource.retention-binding.closure-event.md +21 -0
- package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +1 -2
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +112 -10
- package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +90 -0
- package/dist/knowledge/references/example.resource.work-unit.declaration.md +13 -0
- package/dist/knowledge/references/example.spec.composite-view.workspace.md +0 -12
- package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +18 -0
- package/dist/knowledge/references/example.views.app-level.composite-views-config.md +1 -1
- package/dist/knowledge/references/example.views.chart-view.resource-owned.md +27 -0
- package/dist/knowledge/references/example.views.composite-view.workspace.md +4 -1
- package/dist/knowledge/references/example.website.page.manifest.md +30 -0
- package/dist/knowledge/references/example.worker.node-route.md +94 -0
- package/dist/knowledge/references/experience-plan.config.md +318 -0
- package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +152 -9
- package/dist/knowledge/references/external-connectors.backend.provider-augmentation.md +75 -0
- package/dist/knowledge/references/external-connectors.backend.provider-package-convention.md +36 -0
- package/dist/knowledge/references/external-connectors.frontend-provider-component-declaration.md +85 -0
- package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +52 -0
- package/dist/knowledge/references/external-connectors.models.connection-rate-budgets.md +113 -0
- package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +165 -0
- package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +133 -0
- package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +44 -0
- package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +290 -0
- package/dist/knowledge/references/external-connectors.provider-component-load-state.md +45 -0
- package/dist/knowledge/references/external-connectors.provider-component-loader-contribution.md +32 -0
- package/dist/knowledge/references/external-connectors.provider-component-registry.md +190 -0
- package/dist/knowledge/references/external-connectors.techdoc.frontend-provider-module.md +91 -0
- package/dist/knowledge/references/external-connectors.website.frontend-provider-module.md +91 -0
- package/dist/knowledge/references/integration-plan.config.md +217 -0
- package/dist/knowledge/references/market.alternative.config.md +2 -2
- package/dist/knowledge/references/market.authored-metadata.config.md +12 -9
- package/dist/knowledge/references/market.buying-journey.config.md +1 -1
- package/dist/knowledge/references/market.category.config.md +1 -1
- package/dist/knowledge/references/market.channel.config.md +4 -4
- package/dist/knowledge/references/market.feature-benefit.config.md +2 -2
- package/dist/knowledge/references/market.gain.config.md +2 -2
- package/dist/knowledge/references/market.icp.config.md +3 -3
- package/dist/knowledge/references/market.job.config.md +2 -2
- package/dist/knowledge/references/market.message-template.config.md +3 -3
- package/dist/knowledge/references/market.objection.config.md +2 -2
- package/dist/knowledge/references/market.pain.config.md +2 -2
- package/dist/knowledge/references/market.persona.config.md +3 -3
- package/dist/knowledge/references/market.positioning.config.md +1 -1
- package/dist/knowledge/references/market.proof.config.md +2 -2
- package/dist/knowledge/references/market.references.weighted-edges.md +7 -0
- package/dist/knowledge/references/market.snapshot.validation.md +15 -0
- package/dist/knowledge/references/market.tone-of-voice.config.md +2 -2
- package/dist/knowledge/references/market.trigger.config.md +2 -2
- package/dist/knowledge/references/minions.tick-contract.md +83 -0
- package/dist/knowledge/references/placement-plan.config.md +375 -0
- package/dist/knowledge/references/platform.config.application-database.md +5 -2
- package/dist/knowledge/references/platform.config.backing-services.md +15 -36
- 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.3d.frame-style-overrides.md +134 -0
- package/dist/knowledge/references/presets.3d.layout-contract.md +213 -0
- package/dist/knowledge/references/presets.3d.register-layout.md +95 -0
- package/dist/knowledge/references/presets.models.labelling.sections.md +19 -0
- package/dist/knowledge/references/presets.models.shell-region.md +47 -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.functional-requirement.config.md +8 -0
- 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.actor-execution-decision-record.md +41 -0
- package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +1 -2
- package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +1 -1
- 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 +87 -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.compliance.governed-documents-pdf-template.md +370 -0
- package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +194 -0
- package/dist/knowledge/references/saas.backend.domain-module.md +118 -16
- package/dist/knowledge/references/saas.backend.error-builder.user-guidance.md +82 -0
- package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-declaration.md +66 -0
- package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-schedule.md +31 -0
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +206 -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 +19 -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.pdf-template.collection-definition.md +73 -0
- package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +224 -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.submission-challenge.md +118 -0
- package/dist/knowledge/references/saas.backend.system-access-service.md +148 -41
- package/dist/knowledge/references/saas.backend.system-of-record-action-runner.md +73 -0
- 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.config.providers.augmentations.md +61 -0
- package/dist/knowledge/references/saas.config.providers.packages.md +59 -0
- package/dist/knowledge/references/saas.config.providers.shared-connections.md +84 -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-data.admin-endpoints.md +56 -2
- 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 +43 -13
- package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +44 -8
- package/dist/knowledge/references/saas.frontend.app-shell.building-blocks.md +250 -0
- package/dist/knowledge/references/saas.frontend.billing-context.md +131 -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.chart-view.resource-chart-data.md +92 -0
- package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +64 -0
- package/dist/knowledge/references/saas.frontend.consent-based-provider-activation.md +22 -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-field-address.lookup-slot.md +74 -0
- 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.linked-conversations-embed.md +60 -0
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +47 -0
- package/dist/knowledge/references/saas.frontend.notifications.publish-badge-count.md +60 -0
- package/dist/knowledge/references/saas.frontend.onboarding-view.md +84 -0
- package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +80 -0
- package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
- package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +49 -0
- package/dist/knowledge/references/saas.frontend.related-resource-sections.md +8 -1
- package/dist/knowledge/references/saas.frontend.resource-header-title.md +28 -4
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +136 -1
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +422 -11
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +25 -1
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +259 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +220 -0
- package/dist/knowledge/references/saas.market.generation-agent.md +26 -10
- package/dist/knowledge/references/saas.models.agent-work-capture-settings.md +34 -0
- package/dist/knowledge/references/saas.models.agent-work-decision-surface.md +45 -0
- package/dist/knowledge/references/saas.models.agent-work-decision-vocabulary.md +107 -0
- package/dist/knowledge/references/saas.models.agent-work-output-review.md +36 -0
- package/dist/knowledge/references/saas.models.agent-work-override-rate.md +50 -0
- package/dist/knowledge/references/saas.models.agent-work-review-config.md +24 -0
- package/dist/knowledge/references/saas.models.analytics.value-moments.md +132 -0
- package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +97 -0
- package/dist/knowledge/references/saas.models.audit.trail-config.md +161 -0
- package/dist/knowledge/references/saas.models.auth.methods.md +513 -0
- package/dist/knowledge/references/saas.models.auth.service-provider-client-authentication.md +169 -0
- package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +90 -0
- package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +130 -0
- package/dist/knowledge/references/saas.models.billing.referral-program.md +47 -0
- package/dist/knowledge/references/saas.models.config.organization-types.md +266 -0
- package/dist/knowledge/references/saas.models.config.registration.md +188 -0
- package/dist/knowledge/references/saas.models.config.tenant-teardown.md +98 -0
- package/dist/knowledge/references/saas.models.conversation-threads.md +242 -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 +97 -7
- package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +65 -0
- package/dist/knowledge/references/saas.models.evaluation-dataset-export.md +39 -0
- package/dist/knowledge/references/saas.models.evaluation-export-authorization.md +38 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +710 -10
- 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.flows-actors.autonomous-agents-vocabulary.md +98 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-decision-vocabulary.md +52 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-calendar.md +42 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-deadline-vocabulary.md +84 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +69 -0
- package/dist/knowledge/references/saas.models.frontend-provider-public-config-contract.md +72 -0
- 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 +884 -135
- package/dist/knowledge/references/saas.models.http-api-binding.rest-write-operations.md +81 -0
- package/dist/knowledge/references/saas.models.human-decision-review-marker.md +20 -0
- package/dist/knowledge/references/saas.models.inbound-channels.md +277 -0
- package/dist/knowledge/references/saas.models.inbound-email-domains.md +101 -0
- package/dist/knowledge/references/saas.models.inbound-email.md +111 -0
- 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.model-cost-accounting-config.md +28 -0
- package/dist/knowledge/references/saas.models.model-cost-summary.md +87 -0
- package/dist/knowledge/references/saas.models.navigation.layout.md +13 -9
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +133 -0
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +103 -0
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +152 -0
- package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +84 -0
- package/dist/knowledge/references/saas.models.notifications.targets.md +146 -0
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +283 -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 +59 -0
- package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +129 -0
- package/dist/knowledge/references/saas.models.organizations.service-provider-activity-feed.md +121 -0
- package/dist/knowledge/references/saas.models.organizations.service-provider-capability-grants.md +152 -0
- package/dist/knowledge/references/saas.models.organizations.service-provider-client-controls.md +49 -0
- package/dist/knowledge/references/saas.models.organizations.service-provider-relationships.md +567 -0
- package/dist/knowledge/references/saas.models.privacy.client-instance-id-scope.md +49 -0
- package/dist/knowledge/references/saas.models.privacy.legal-holds.md +172 -0
- package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +104 -0
- package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +106 -0
- package/dist/knowledge/references/saas.models.privacy.retention-binding.md +103 -0
- package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +120 -0
- package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +147 -0
- package/dist/knowledge/references/saas.models.privacy.statutory-retention-ground.md +50 -0
- package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +388 -0
- package/dist/knowledge/references/saas.models.progression-tracker-variant.md +76 -0
- package/dist/knowledge/references/saas.models.provider-address-lookup-contract.md +139 -0
- package/dist/knowledge/references/saas.models.provider-address-lookup-declaration.md +61 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +42 -5
- package/dist/knowledge/references/saas.models.provider-credential-identity.md +67 -0
- package/dist/knowledge/references/saas.models.provider-usage-pricing-authority.md +139 -0
- package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +133 -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 +196 -0
- package/dist/knowledge/references/saas.models.providers.scope-reauthorization.md +57 -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 +244 -32
- 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-submission-challenge.md +54 -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 +16 -0
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +22 -0
- package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +82 -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.system-of-record-actions.md +226 -0
- package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +461 -0
- package/dist/knowledge/references/saas.models.systems-of-record.facet-augmentation.md +63 -0
- package/dist/knowledge/references/saas.models.systems-of-record.md +870 -0
- package/dist/knowledge/references/saas.models.work-attribution-vocabulary.md +109 -0
- package/dist/knowledge/references/saas.models.work-unit-ref.md +28 -0
- package/dist/knowledge/references/saas.public-runtime.contract.md +268 -3
- 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 +108 -7
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +880 -66
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +14 -13
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.discriminated-union.md +36 -14
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-aggregate-offer.md +4 -3
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-product.md +4 -4
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-software-application.md +71 -0
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +217 -18
- package/dist/knowledge/references/saas.specifications.compliance.retention-enforcement-state.md +32 -0
- package/dist/knowledge/references/saas.specifications.composite-view-specification.md +10 -0
- package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +376 -0
- package/dist/knowledge/references/saas.specifications.playbook-approval-and-failure-policies.md +96 -0
- package/dist/knowledge/references/saas.specifications.processor-register.md +410 -0
- package/dist/knowledge/references/saas.specifications.recipient-disclosures.md +71 -0
- package/dist/knowledge/references/saas.specifications.recipient-population.md +549 -0
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +120 -45
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +35 -1
- package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +17 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-frontend-prose.md +16 -0
- package/dist/knowledge/references/saas.specifications.subject-data-recipients.md +98 -0
- package/dist/knowledge/references/saas.website.astro.bridge.md +92 -7
- package/dist/knowledge/references/saas.website.astro.head-renderer.md +33 -13
- package/dist/knowledge/references/saas.website.astro.label-loader.md +10 -4
- package/dist/knowledge/references/saas.website.astro.robots-renderer.md +29 -16
- package/dist/knowledge/references/saas.website.astro.site-context.md +5 -2
- package/dist/knowledge/references/saas.website.blog.bridge.md +34 -1
- package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +61 -0
- package/dist/knowledge/references/saas.website.config.site-context-loader.md +154 -0
- 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.design-tokens.colors.md +7 -4
- package/dist/knowledge/references/saas.website.design-tokens.radius.md +1 -1
- package/dist/knowledge/references/saas.website.factories.define-section.md +3 -3
- package/dist/knowledge/references/saas.website.page-layout.component.md +70 -1
- package/dist/knowledge/references/saas.website.page.context.md +4 -3
- package/dist/knowledge/references/saas.website.pricing-offer-structured-data.md +140 -0
- package/dist/knowledge/references/saas.website.provider-component.slot.md +99 -0
- package/dist/knowledge/references/saas.website.root-config.schema.md +6 -6
- package/dist/knowledge/references/saas.website.runtime.context.md +66 -11
- 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/saas.website.sections.definition-schema.md +14 -7
- package/dist/knowledge/references/saas.website.seo.robots-config.md +4 -3
- package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +7 -5
- package/dist/knowledge/references/saas.website.submission-challenge.md +77 -0
- package/dist/knowledge/references/saas.website.use-pricing-catalog.hook.md +36 -0
- package/dist/knowledge/references/saas.website.use-runtime.hook.md +3 -2
- package/dist/knowledge/references/vision.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/website-plan.config.md +238 -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 +53 -5
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +75 -1
- package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +36 -2
- 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 +95 -18
- package/dist/knowledge/references/zod.decorators.file-vocabularies.md +87 -0
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +148 -6
- 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 +50 -12
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +35 -12
- package/dist/knowledge/references/zod.factories.address.md +118 -0
- package/dist/knowledge/references/zod.factories.code.md +4 -2
- package/dist/knowledge/references/zod.factories.duration.md +6 -4
- package/dist/knowledge/references/zod.factories.money.md +5 -3
- 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 +2602 -214
- package/dist/knowledge/registries/playbooks.json +468 -92
- package/dist/knowledge/registries/source-tags.json +6171 -1996
- package/dist/knowledge/rules/database-migration-obligation.md +110 -0
- package/dist/knowledge/rules/live-context-door.md +137 -0
- package/dist/knowledge/rules/resource-schema-awareness.md +75 -0
- package/dist/knowledge/skills/INDEX.md +67 -29
- package/dist/knowledge/skills/agent-work-review/SKILL.md +141 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-capture-settings-api.md +38 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-output-review-api.md +40 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-override-rate-api.md +54 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-config-api.md +28 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +108 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-vocabulary-api.md +111 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-dataset-export-api.md +43 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-export-authorization-api.md +42 -0
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +111 -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 +11 -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 +95 -3
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +59 -0
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +32 -19
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +119 -17
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-readiness-contributor-api.md +135 -0
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +96 -20
- 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 +214 -0
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +39 -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 +162 -8
- 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 +518 -132
- 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 +162 -26
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +734 -23
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +436 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +221 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +209 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-population.md +577 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +549 -0
- package/dist/knowledge/skills/config-app-shell/SKILL.md +95 -11
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +87 -21
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-building-blocks-api.md +276 -0
- 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-app-shell/references/framework-shell-region-markers-api.md +66 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +44 -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 +200 -19
- package/dist/knowledge/skills/config-navigation/references/choosing-a-navigation-shape.md +314 -0
- 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 +13 -9
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +78 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +245 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +174 -0
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +253 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +141 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-zones.md +1 -1
- package/dist/knowledge/skills/config-saas/SKILL.md +88 -9
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +206 -0
- package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +189 -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 +157 -0
- package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +292 -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 +139 -12
- package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +1024 -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 +66 -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 +397 -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 +143 -0
- package/dist/knowledge/skills/config-saas-backend/references/managed-startup-configuration.md +46 -0
- package/dist/knowledge/skills/configure-billing/SKILL.md +91 -46
- package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +62 -17
- package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +55 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +39 -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 +192 -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 +259 -0
- package/dist/knowledge/skills/configure-billing/references/framework-referral-program.md +110 -0
- package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +91 -0
- package/dist/knowledge/skills/configure-coding-agent/SKILL.md +289 -0
- package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +192 -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 +100 -91
- 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 +123 -0
- package/dist/knowledge/skills/email-definition-wiring/SKILL.md +1 -0
- package/dist/knowledge/skills/email-labels-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/email-template-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/engine-component-registration/SKILL.md +20 -12
- package/dist/knowledge/skills/engine-product-definitions/SKILL.md +60 -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 +60 -27
- 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-autonomous-agents/SKILL.md +180 -0
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +56 -0
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-autonomous-agent-api.md +208 -0
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-inbound-agents-api.md +51 -0
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/tool-posture.md +27 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +41 -12
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +31 -7
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +148 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +287 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +248 -9
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +127 -22
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +236 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +8 -11
- 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-cdn-publish/SKILL.md +1 -0
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +259 -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 +3988 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +212 -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 +14 -1
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +19 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +11 -9
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +19 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +11 -2
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +19 -0
- package/dist/knowledge/skills/i18n-translation-rerun/references/translation-workflow.md +5 -0
- package/dist/knowledge/skills/inbound-channels/SKILL.md +301 -0
- package/dist/knowledge/skills/inbound-channels/references/email-channel.md +133 -0
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +800 -0
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-email-api.md +222 -0
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +231 -0
- package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +135 -0
- package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +297 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +387 -81
- 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 +198 -36
- 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/layout-3d-adoption/SKILL.md +176 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +141 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-contract-api.md +223 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-registration-api.md +103 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-building-blocks-api.md +256 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-region-marker-api.md +52 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/layouts-and-transitions.md +29 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +25 -0
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +184 -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/local-environment-troubleshooting.md +2 -1
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +289 -37
- package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +3 -2
- package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +2 -2
- package/dist/knowledge/skills/market-alternatives/SKILL.md +4 -3
- package/dist/knowledge/skills/market-authoring-overview/SKILL.md +1 -0
- package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +7 -0
- package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +12 -9
- package/dist/knowledge/skills/market-category/SKILL.md +2 -1
- package/dist/knowledge/skills/market-channels/SKILL.md +5 -4
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +233 -18
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +232 -18
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +77 -15
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +50 -12
- package/dist/knowledge/skills/market-icp/SKILL.md +4 -3
- package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +7 -6
- package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +4 -3
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +18 -3
- package/dist/knowledge/skills/market-persona/SKILL.md +4 -3
- package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/market-positioning-authoring/references/framework-positioning-api.md +1 -1
- package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +5 -4
- package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +1 -0
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +16 -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 +3 -2
- package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +4 -3
- package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +199 -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 +144 -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/model-cost-attribution/SKILL.md +143 -0
- package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +211 -0
- package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-summary-api.md +95 -0
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-attribution-api.md +117 -0
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +677 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +55 -19
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +217 -18
- package/dist/knowledge/skills/module-registration/SKILL.md +50 -32
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +143 -16
- package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +227 -0
- package/dist/knowledge/skills/module-registration/references/registry-files.md +14 -5
- package/dist/knowledge/skills/module-relationships/SKILL.md +65 -2
- package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +26 -5
- package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +34 -2
- package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-collection-template-api.md +447 -0
- package/dist/knowledge/skills/provider-address-lookup/SKILL.md +207 -0
- package/dist/knowledge/skills/provider-address-lookup/references/framework-address-field-lookup-slot-api.md +82 -0
- package/dist/knowledge/skills/provider-address-lookup/references/framework-address-lookup-contract-api.md +214 -0
- package/dist/knowledge/skills/provider-address-lookup/references/framework-browser-operation-policy-api.md +143 -0
- package/dist/knowledge/skills/provider-address-lookup/references/google-places-setup.md +73 -0
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +518 -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-augmentation-api.md +227 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-credential-identity-api.md +101 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +245 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +88 -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-allow-list-api.md +111 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-convention-api.md +48 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +309 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +165 -29
- 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-consent-api.md +399 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +270 -9
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-public-config-api.md +115 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-provider-component-registry-api.md +386 -0
- package/dist/knowledge/skills/provider-frontend-module/SKILL.md +258 -0
- package/dist/knowledge/skills/provider-frontend-module/references/framework-frontend-facet-contracts-api.md +463 -0
- package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +61 -0
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +247 -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 +141 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-connection-rate-budgets-api.md +176 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +86 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +73 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-scope-reauthorization-api.md +127 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +300 -0
- package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +70 -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 +13 -5
- package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +1 -2
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +472 -23
- package/dist/knowledge/skills/resource-add-module/SKILL.md +117 -265
- package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +134 -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 +29 -3
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +244 -32
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +26 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +101 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +145 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +101 -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 +953 -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 +125 -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 +595 -45
- 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 +259 -45
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +486 -0
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +6 -0
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +422 -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 +1242 -31
- package/dist/knowledge/skills/resource-external-data/references/declared-expressions.md +144 -0
- package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +68 -0
- package/dist/knowledge/skills/resource-external-data/references/facet-augmentations.md +154 -0
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +739 -17
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +987 -140
- package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +175 -10
- package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +152 -0
- package/dist/knowledge/skills/resource-external-data/references/odata-v2-sources.md +60 -0
- package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +179 -0
- package/dist/knowledge/skills/resource-external-data/references/pipeline-destination-schema.md +1 -1
- package/dist/knowledge/skills/resource-external-data/references/provenance-cue.md +63 -0
- package/dist/knowledge/skills/resource-external-data/references/rate-budgets-and-pacing.md +122 -0
- package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +745 -0
- package/dist/knowledge/skills/resource-external-data/references/remote-references.md +85 -0
- package/dist/knowledge/skills/resource-external-data/references/rest-keyset-sources.md +85 -0
- package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +442 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +70 -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 +44 -48
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +108 -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-retention-binding/SKILL.md +186 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +200 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +111 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +173 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +155 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +139 -0
- package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +55 -0
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +34 -4
- package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +1 -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/field-type-selection.md +3 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +77 -5
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +210 -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 +50 -12
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +497 -28
- 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 +78 -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 +300 -23
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +75 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +36 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +447 -12
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +148 -6
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +57 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +216 -6
- package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +266 -0
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +10 -1
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +4 -0
- package/dist/knowledge/skills/seeding-operations/SKILL.md +34 -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/service-provider-relationships/SKILL.md +455 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-organization-types-api.md +270 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-activity-feed-api.md +129 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-capability-grants-api.md +161 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-client-authentication-api.md +224 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-relationships-api.md +576 -0
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +206 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +266 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +229 -0
- package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +43 -37
- package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +15 -14
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +52 -19
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +217 -18
- package/dist/knowledge/skills/spec-component-update/SKILL.md +31 -11
- package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +20 -21
- package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +10 -0
- package/dist/knowledge/skills/spec-family-update/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-feature-update/SKILL.md +48 -9
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +16 -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 +188 -46
- package/dist/knowledge/skills/spec-update-after-change/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +17 -0
- package/dist/knowledge/skills/views-add-composite-view/SKILL.md +6 -1
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +14 -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 +3 -1
- 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 +44 -1
- package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +102 -0
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +6 -1
- package/dist/knowledge/skills/views-composite-authoring/references/composite-embedding-checklist.md +3 -2
- 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 +4 -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 +72 -13
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +3 -2
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +34 -1
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +44 -28
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +48 -23
- package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +882 -211
- package/dist/knowledge/skills/website-factory-advanced/SKILL.md +4 -3
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +117 -13
- package/dist/knowledge/skills/website-inbound-contact-forms/references/framework-submission-challenge-api.md +275 -0
- package/dist/knowledge/skills/website-label-pack/SKILL.md +13 -5
- package/dist/knowledge/skills/website-layout-overrides/SKILL.md +71 -1
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +22 -2
- package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +21 -6
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +206 -35
- package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +164 -0
- package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +126 -0
- package/dist/knowledge/skills/website-page-variants/SKILL.md +1 -0
- package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +1 -0
- package/dist/knowledge/skills/website-section-contact/SKILL.md +159 -180
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +38 -31
- package/dist/knowledge/skills/website-section-cta/SKILL.md +51 -42
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +38 -31
- package/dist/knowledge/skills/website-section-faq/SKILL.md +118 -83
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +38 -31
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +46 -38
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +38 -31
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +52 -42
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +38 -31
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +50 -40
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +38 -31
- package/dist/knowledge/skills/website-section-hero/SKILL.md +101 -69
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +38 -31
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +236 -220
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +38 -31
- package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +248 -0
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +64 -54
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +38 -31
- package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +8 -3
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +64 -34
- package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +44 -26
- package/dist/knowledge/skills/worker-authoring/SKILL.md +165 -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 +12659 -4142
- 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/skills/journey-approve/SKILL.md +0 -43
- package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +0 -42
- package/dist/knowledge/skills/journey-next/SKILL.md +0 -42
- package/dist/knowledge/skills/journey-report/SKILL.md +0 -43
- package/dist/knowledge/skills/journey-run/SKILL.md +0 -55
- package/dist/knowledge/skills/journey-status/SKILL.md +0 -50
- /package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/structured-artifact-action.json +0 -0
|
@@ -1 +1 @@
|
|
|
1
|
-
{"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-market-snapshot","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/market-evidence-and-vision-coherence"],"requirementRef":"application-creation:authority-requirement/market-analysis-result","requirementVersion":1,"riskClassRef":"application-creation:risk/market-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/market-analysis","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/market-analysis-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/market-analysis","policyVersion":1},"decisionPointRef":"application-creation:decision-point/market-analysis-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/market-analysis-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/market-analysis","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/market-snapshot-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/market-definition-change","triggerRefs":["application-creation:trigger/market-snapshot-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-market-analysis-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/market-evidence-and-vision-coherence"],"hardFloorRef":"application-creation:hard-floor/market-snapshot-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/market-analysis-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/market-analysis","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-market-analysis-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/market-evidence-and-vision-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1}],"instruction":"Assess whether the validated market graph is meaningfully grounded in accepted vision and sealed research evidence, distinguishes facts from hypotheses, and is coherent enough for current-horizon requirements and capability work. Do not reward exhaustive taxonomy when the targeting or evidence basis is weak.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The graph is usable but material targeting or evidence uncertainty is explicitly unresolved.","GAP":"The market graph materially contradicts the vision, lacks a usable target, or presents unsupported claims as truth.","INDETERMINATE":"Accepted vision, research evidence or candidate output is absent, stale or insufficient.","PASS":"The market graph is valid, evidence-aware and coherent with the accepted vision."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/market-analysis","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.market-
|
|
1
|
+
{"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-market-snapshot","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/market-evidence-and-vision-coherence"],"requirementRef":"application-creation:authority-requirement/market-analysis-result","requirementVersion":1,"riskClassRef":"application-creation:risk/market-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/market-analysis","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/market-analysis-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/market-analysis","policyVersion":1},"decisionPointRef":"application-creation:decision-point/market-analysis-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/market-analysis-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/market-analysis","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/market-snapshot-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/market-definition-change","triggerRefs":["application-creation:trigger/market-snapshot-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-market-analysis-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/market-evidence-and-vision-coherence"],"hardFloorRef":"application-creation:hard-floor/market-snapshot-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/market-analysis-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/market-analysis","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-market-analysis-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/market-evidence-and-vision-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1}],"instruction":"Assess whether the validated market graph is meaningfully grounded in accepted vision and sealed research evidence, distinguishes facts from hypotheses, and is coherent enough for current-horizon requirements and capability work. Do not reward exhaustive taxonomy when the targeting or evidence basis is weak.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The graph is usable but material targeting or evidence uncertainty is explicitly unresolved.","GAP":"The market graph materially contradicts the vision, lacks a usable target, or presents unsupported claims as truth.","INDETERMINATE":"Accepted vision, research evidence or candidate output is absent, stale or insufficient.","PASS":"The market graph is valid, evidence-aware and coherent with the accepted vision."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/market-analysis","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.market-snapshot-produce"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/market-analysis","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-market-input-and-candidate","criterionRef":"application-creation:criterion/market-evidence-and-vision-coherence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":2,"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/accepted-vision-research-and-market-candidate"}],"schemaVersion":1}
|
|
@@ -0,0 +1,245 @@
|
|
|
1
|
+
# Market Analysis — Produce Method (v1 scaffold)
|
|
2
|
+
|
|
3
|
+
### Target Application Framing
|
|
4
|
+
|
|
5
|
+
This knowledge is for configuring behavior in the target application.
|
|
6
|
+
Wildo is the framework surface being used, not the product being built.
|
|
7
|
+
|
|
8
|
+
Read and apply these patterns from the application-developer point of view:
|
|
9
|
+
|
|
10
|
+
- how the application should configure the relevant app-level file
|
|
11
|
+
- how the application should use framework-provided factories, enums, and helpers
|
|
12
|
+
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
13
|
+
|
|
14
|
+
|
|
15
|
+
> **This is a v1 scaffold methodology.** It is a working first cut meant to
|
|
16
|
+
> be iterated. The authoring order, research posture, and the "produce vs.
|
|
17
|
+
> refine" rules below are deliberately explicit so they can be tuned against
|
|
18
|
+
> real runs — treat them as a starting rubric, not a frozen contract. The
|
|
19
|
+
> *analytical depth* of the market work (research rigor, competitive
|
|
20
|
+
> teardown, quantified FIT/Kano scoring) is intentionally shallow here and is
|
|
21
|
+
> deepened in a later phase; do not perfect it in this playbook.
|
|
22
|
+
|
|
23
|
+
## What this playbook does
|
|
24
|
+
|
|
25
|
+
You are the **market analyst**. Your one job is to produce — or refine an
|
|
26
|
+
existing — **MarketSnapshot** for this product: the single artifact that
|
|
27
|
+
declares *who the product is for*, *what they are trying to get done*, and
|
|
28
|
+
*how the product is positioned* to them. You reason top-down from the
|
|
29
|
+
product idea (there is no code yet in this phase); you do not model the
|
|
30
|
+
domain, author resources, or write features — later playbooks consume your
|
|
31
|
+
snapshot to do that.
|
|
32
|
+
|
|
33
|
+
## The shape you return is FLAT, not nested
|
|
34
|
+
|
|
35
|
+
Read this before the slice list below, because the slices read like a hierarchy and the object is
|
|
36
|
+
not one.
|
|
37
|
+
|
|
38
|
+
A MarketSnapshot is **~16 sibling top-level collections** — `category`, `icps`, `personas`, `jobs`,
|
|
39
|
+
`pains`, `gains`, `tonesOfVoice`, `benefits`, `positionings`, `channels`, `alternatives`,
|
|
40
|
+
`triggers`, `buyingJourneys`, `proofs`, `objections`, `messageTemplates` — and entities point at
|
|
41
|
+
each other with flat **ref strings** (`jobRef`, `painRef`, `gainRef`, `personaRef`, `alternativeRef`,
|
|
42
|
+
…). An ICP does not CONTAIN its jobs; it names them:
|
|
43
|
+
|
|
44
|
+
```
|
|
45
|
+
jobs: [ { ref: 'job-close-the-week', statement: '…' } ] // the job itself, top level
|
|
46
|
+
icps: [ { ref: 'icp-small-team',
|
|
47
|
+
jobs: [ { jobRef: 'job-close-the-week', importance: … } ] } ] // the ICP's REFERENCE to it
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
⚠ **Measured on this playbook, 2026-08-29.** A first attempt returned 41,098 characters that were
|
|
51
|
+
rejected wholesale: it had nested `personas`, `benefits`, `positionings`, `channels`, `alternatives`,
|
|
52
|
+
`triggers`, `proofs` and `objections` INSIDE `icps[0]`, left every top-level collection empty, and
|
|
53
|
+
wrote whole job objects where `{ jobRef, importance }` belongs. The retry recovered it, but a full
|
|
54
|
+
generation was spent discovering the shape. The slice ordering below is a THINKING order — what to
|
|
55
|
+
work out first — never the structure of the answer.
|
|
56
|
+
|
|
57
|
+
A MarketSnapshot is assembled from these slices, each owned by a dedicated
|
|
58
|
+
`market_*` app-knowledge skill. Those skills are named here so you know which
|
|
59
|
+
authoring contract each slice belongs to, and so a later CODING agent can open
|
|
60
|
+
the right one — you cannot: this step has no tools, and sixteen skill bodies do
|
|
61
|
+
not fit in one brief. Everything you need to author the snapshot is in THIS
|
|
62
|
+
method and your declared inputs; where a detail is genuinely only in a skill,
|
|
63
|
+
say so on what you author rather than inventing it. You author them in
|
|
64
|
+
dependency order because later slices reference earlier refs:
|
|
65
|
+
|
|
66
|
+
1. **Category** — the one market category the product competes in, plus the
|
|
67
|
+
rejected adjacent categories. (`market-category`)
|
|
68
|
+
2. **ICPs** — the Ideal Customer Profiles: the firmographic / demographic
|
|
69
|
+
segments the product is sold to. (`market-icp`)
|
|
70
|
+
3. **Personas** — the human roles inside each ICP, including buying-group
|
|
71
|
+
members. Every ICP needs at least one persona. (`market-persona`)
|
|
72
|
+
4. **Jobs / Pains / Gains** — the Strategyzer customer-profile triplet for
|
|
73
|
+
the personas: what they are trying to do, what blocks them, what a win
|
|
74
|
+
looks like. (`market-jobs-pains-gains`)
|
|
75
|
+
5. **Tones of voice** — the named brand voices the product speaks in.
|
|
76
|
+
(`market-tone-of-voice`)
|
|
77
|
+
6. **Benefits** — the outcome claims the product delivers, weighted against
|
|
78
|
+
the pains/gains they relieve/create. (`market-add-feature-benefit`)
|
|
79
|
+
7. **Positionings** — the per-ICP marketing-truth promise. Author one per
|
|
80
|
+
ICP that the product actually targets. (`market-positioning-authoring`)
|
|
81
|
+
8. **Reach surfaces** — the go-to-market context: channels, competing
|
|
82
|
+
alternatives, buying triggers + per-ICP buying journeys, proofs, and the
|
|
83
|
+
objections proofs answer. (`market-channels`, `market-alternatives`,
|
|
84
|
+
`market-triggers-and-journey`, `market-proof-and-objection`)
|
|
85
|
+
9. **Message templates** — reusable prompt templates that render from the
|
|
86
|
+
snapshot above. Author last; they reference the earlier slices.
|
|
87
|
+
(`market-message-templates-authoring`)
|
|
88
|
+
|
|
89
|
+
Author only the slices the product's stage warrants — a first pass may stop
|
|
90
|
+
after positionings and leave the phase-3/4 reach surfaces empty (they
|
|
91
|
+
default to `[]`). A snapshot with a category, at least one ICP, its
|
|
92
|
+
personas, the jobs/pains/gains triplet, and at least one positioning is a
|
|
93
|
+
legitimate v1; the reach surfaces and message templates are additive.
|
|
94
|
+
|
|
95
|
+
## Where the snapshot lives
|
|
96
|
+
|
|
97
|
+
The MarketSnapshot for this journey is placed under
|
|
98
|
+
`specifications/src/market/index.ts`. That is the artifact this
|
|
99
|
+
playbook owns and the rest of the top-down phase reads. When the product's
|
|
100
|
+
definition later stabilises, the snapshot is what seeds the durable market
|
|
101
|
+
specification under `./specifications/` — but at this phase it is a journey
|
|
102
|
+
artifact, not yet app source.
|
|
103
|
+
|
|
104
|
+
## Produce vs. refine — read state first
|
|
105
|
+
|
|
106
|
+
This playbook is **idempotent** on the journey's market artifact. Before
|
|
107
|
+
authoring anything:
|
|
108
|
+
|
|
109
|
+
1. Read the current journey state and scope from what this run is given — the loaded
|
|
110
|
+
specifications and the workspace sections of your brief; do not re-derive it. That state tells you which
|
|
111
|
+
scope the snapshot must be complete *for*.
|
|
112
|
+
2. Check whether a MarketSnapshot already exists by reading the artifact at the
|
|
113
|
+
`market-snapshot` family's landing path, `specifications/src/market/index.ts`.
|
|
114
|
+
The path belongs to the FAMILY, not to this playbook — every playbook that
|
|
115
|
+
writes a market snapshot writes that same file. Its presence or absence
|
|
116
|
+
selects the mode below.
|
|
117
|
+
|
|
118
|
+
- **No snapshot yet** — produce a fresh one, authoring the slices in the
|
|
119
|
+
order above.
|
|
120
|
+
- **A snapshot exists** — *refine* it: read every slice, keep what still
|
|
121
|
+
holds, and only add/correct the slices the current steering notes or new
|
|
122
|
+
research call for. Never silently discard authored refs — a downstream
|
|
123
|
+
positioning or benefit may depend on an ICP or persona ref, and dropping
|
|
124
|
+
it orphans them (the validator will catch this, but honest refinement
|
|
125
|
+
should not create the orphan in the first place).
|
|
126
|
+
|
|
127
|
+
## Provenance — record where a claim came from
|
|
128
|
+
|
|
129
|
+
You are given the evidence a sibling research step gathered, with the URLs it read.
|
|
130
|
+
Where an entity's content rests on one of those sources, RECORD that URL on the entity
|
|
131
|
+
— in the schema's own provenance fields, which exist for exactly this:
|
|
132
|
+
|
|
133
|
+
| field | for |
|
|
134
|
+
|---|---|
|
|
135
|
+
| `pains[].evidence[]`, `gains[].evidence[]`, `benefits[].evidence` | what a source shows about the pain, gain or claim |
|
|
136
|
+
| `proofs[].evidenceUrl`, `proofs[].attribution.url` | the page a proof points at |
|
|
137
|
+
| `alternatives[].notes[]`, `category.notes[]`, `icps[].notes[]` | where the framing came from |
|
|
138
|
+
|
|
139
|
+
⚠ An earlier revision of this section told you to use `authoredMetadata.notes` instead.
|
|
140
|
+
That was wrong, and the correction is recorded rather than quietly applied because the
|
|
141
|
+
run that exposed it did better than the instruction: handed the evidence, the model
|
|
142
|
+
put 10 URLs into the typed `evidence`/`evidenceUrl` fields above and none into the
|
|
143
|
+
generic metadata block it had been pointed at. Typed provenance is machine-readable
|
|
144
|
+
and the generic block is prose; prefer the specific field every time one exists.
|
|
145
|
+
|
|
146
|
+
This is not bookkeeping. Measured on this playbook's first composite run
|
|
147
|
+
(2026-08-29): the snapshot it produced carried **zero** source URLs and was, on that
|
|
148
|
+
dimension, indistinguishable from the single-call version it replaced — the judge
|
|
149
|
+
called the older one's evidence "self-referential statements such as 'The vision
|
|
150
|
+
specifies…'". A sourced claim and an invented one must not look the same in what you
|
|
151
|
+
land, because nobody downstream can tell them apart afterwards.
|
|
152
|
+
|
|
153
|
+
So:
|
|
154
|
+
|
|
155
|
+
- An entity grounded in a fetched page carries its URL in `authoredMetadata.notes`.
|
|
156
|
+
- An entity you INFERRED carries that word, and `confidence` set honestly — `LOW` for
|
|
157
|
+
a hypothesis, not `HIGH` because it reads well.
|
|
158
|
+
- An entity the evidence did not cover is still authorable, and says so.
|
|
159
|
+
|
|
160
|
+
Omit `authoredMetadata` only where the content is so self-evident that provenance
|
|
161
|
+
would be noise. A competitor's price is never that.
|
|
162
|
+
|
|
163
|
+
## Research posture (scaffold depth)
|
|
164
|
+
|
|
165
|
+
Ground each slice in evidence, not invention. At this scaffold depth the
|
|
166
|
+
research is whatever the executing agent can gather about the product's
|
|
167
|
+
category, competitors, and buyers; capture the *shape* faithfully (real
|
|
168
|
+
category, real competing alternatives, plausible ICPs and personas) rather
|
|
169
|
+
than aspirational fiction. Where you are inferring rather than citing, say so
|
|
170
|
+
in the slice's authored prose so a later, deeper research pass can tighten
|
|
171
|
+
it. Do **not** build a research pipeline or block on external tooling here —
|
|
172
|
+
richer web-research capability is a later-phase concern; this playbook
|
|
173
|
+
consumes whatever the agent already knows plus the creator's steering.
|
|
174
|
+
|
|
175
|
+
## Quality gate
|
|
176
|
+
|
|
177
|
+
Your emitted snapshot is checked by the deterministic `market-snapshot-valid`
|
|
178
|
+
gate (`validateMarketSnapshot`) before anything downstream consumes it. It
|
|
179
|
+
enforces the cross-slice invariants — orphan refs (a positioning naming a
|
|
180
|
+
missing ICP, a benefit naming a missing pain/gain), an ICP with no persona,
|
|
181
|
+
influence cycles, duplicate edges, proofs without support, message-template
|
|
182
|
+
placeholder mismatches, and more. Duplicate or malformed refs and
|
|
183
|
+
`ERROR`-severity issues are hard failures; the snapshot does not advance
|
|
184
|
+
until they clear. `WARN`-severity issues (e.g. stale-authored, a missing
|
|
185
|
+
positioning for a targeted ICP) do not block but should be resolved. Read
|
|
186
|
+
`market-snapshot-validation` for the full issue catalogue and emit a clean
|
|
187
|
+
snapshot the first time.
|
|
188
|
+
|
|
189
|
+
## Scaffold-depth boundary (deferred to a later depth phase)
|
|
190
|
+
|
|
191
|
+
Keep this playbook at scaffold depth. The following are explicitly **out of
|
|
192
|
+
scope here** and are deepened in the methodology-depth phase, not now:
|
|
193
|
+
|
|
194
|
+
- **Deep competitive teardown** — the reach surfaces capture *that* an
|
|
195
|
+
alternative exists and *why* a buyer might pick it; a quantified,
|
|
196
|
+
feature-by-feature competitor matrix is later-phase work.
|
|
197
|
+
- **Quantified FIT / Kano scoring** — `market-scoring-interpretation` reads
|
|
198
|
+
the deterministic FIT scorer; at scaffold depth you consume it to sanity-
|
|
199
|
+
check benefit weighting, not to drive a precise prioritization model. The
|
|
200
|
+
prioritization seam stays pluggable (see the capability-map playbook).
|
|
201
|
+
- **Opportunity / TAM sizing and evidence depth** — jobs/pains/gains are
|
|
202
|
+
authored as framing, not as a sized, sourced market model.
|
|
203
|
+
|
|
204
|
+
If you find yourself perfecting any of the above, stop and leave the slice at
|
|
205
|
+
scaffold depth — depth is a dedicated later pass done once, holistically.
|
|
206
|
+
|
|
207
|
+
## What you emit
|
|
208
|
+
|
|
209
|
+
A single MarketSnapshot at `specifications/src/market/index.ts`,
|
|
210
|
+
assembled from the slices above via their `market_*` skills, passing the
|
|
211
|
+
`market-snapshot-valid` gate. The creator reviews the result (approval posture
|
|
212
|
+
`approve_result`) before it is accepted as the journey's market intent.
|
|
213
|
+
|
|
214
|
+
## References
|
|
215
|
+
|
|
216
|
+
These are skill FOLDERS installed in the application, listed so each slice's
|
|
217
|
+
authoring contract has a name. This step has no tools and does not open them.
|
|
218
|
+
|
|
219
|
+
- `market-authoring-overview` — the orchestrator for
|
|
220
|
+
the whole market slice; read it first to see how the slices fit together.
|
|
221
|
+
- `market-category` — author the singular market
|
|
222
|
+
category.
|
|
223
|
+
- `market-icp` — author the Ideal Customer Profiles.
|
|
224
|
+
- `market-persona` — author the personas per ICP.
|
|
225
|
+
- `market-jobs-pains-gains` — author the Strategyzer
|
|
226
|
+
jobs/pains/gains triplet.
|
|
227
|
+
- `market-tone-of-voice` — author the named brand
|
|
228
|
+
voices.
|
|
229
|
+
- `market-add-feature-benefit` — author the benefit
|
|
230
|
+
claims and their pain/gain weighting.
|
|
231
|
+
- `market-positioning-authoring` — author the per-ICP
|
|
232
|
+
positioning promise.
|
|
233
|
+
- `market-channels` — author the reach channels.
|
|
234
|
+
- `market-alternatives` — author the competing
|
|
235
|
+
alternatives.
|
|
236
|
+
- `market-triggers-and-journey` — author buying
|
|
237
|
+
triggers and per-ICP buying journeys.
|
|
238
|
+
- `market-proof-and-objection` — author proofs and
|
|
239
|
+
the objections they answer.
|
|
240
|
+
- `market-message-templates-authoring` — author the
|
|
241
|
+
reusable message templates (last).
|
|
242
|
+
- `market-scoring-interpretation` — interpret the
|
|
243
|
+
deterministic FIT scorer to sanity-check benefit weighting.
|
|
244
|
+
- `market-snapshot-validation` — the full validation
|
|
245
|
+
issue catalogue the quality gate enforces.
|
|
@@ -0,0 +1,70 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ref": "top_down.market-snapshot-produce",
|
|
3
|
+
"version": "0.1.0",
|
|
4
|
+
"phase": "top_down",
|
|
5
|
+
"intent": "Derive a validated market snapshot from the vision and from the EVIDENCE a sibling research step gathered — the artifact-producing child of the `top_down.market-analysis` composite. The provider proposes the market graph; the trusted runtime stamps entity refs/version and keeps provenance, authority and accepted-family mutation outside model output. Its intent used to claim derivation from \"sealed research evidence\" while nothing supplied any; it now runs only once an adequacy gate has read the evidence and returned ADEQUATE.",
|
|
6
|
+
"preconditions": [
|
|
7
|
+
{
|
|
8
|
+
"kind": "artifact_valid",
|
|
9
|
+
"selector": {
|
|
10
|
+
"family": "vision-brief"
|
|
11
|
+
}
|
|
12
|
+
},
|
|
13
|
+
{
|
|
14
|
+
"kind": "step_available",
|
|
15
|
+
"ref": "evidence-adequacy",
|
|
16
|
+
"requires": {
|
|
17
|
+
"path": "verdict",
|
|
18
|
+
"equals": "adequate"
|
|
19
|
+
}
|
|
20
|
+
}
|
|
21
|
+
],
|
|
22
|
+
"inputs": [
|
|
23
|
+
{
|
|
24
|
+
"family": "vision-brief"
|
|
25
|
+
},
|
|
26
|
+
{
|
|
27
|
+
"family": "market-snapshot"
|
|
28
|
+
}
|
|
29
|
+
],
|
|
30
|
+
"outputs": [
|
|
31
|
+
{
|
|
32
|
+
"family": "market-snapshot",
|
|
33
|
+
"schemaRef": "saas-specifications:MarketSnapshot",
|
|
34
|
+
"description": "The assembled market category, ICP, persona, jobs/pains/gains, benefit, positioning and reach graph validated by validateMarketSnapshot."
|
|
35
|
+
}
|
|
36
|
+
],
|
|
37
|
+
"stepOutputs": [],
|
|
38
|
+
"method": {
|
|
39
|
+
"guidance": "# Market Analysis — Produce Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The authoring order, research posture, and the \"produce vs.\n> refine\" rules below are deliberately explicit so they can be tuned against\n> real runs — treat them as a starting rubric, not a frozen contract. The\n> *analytical depth* of the market work (research rigor, competitive\n> teardown, quantified FIT/Kano scoring) is intentionally shallow here and is\n> deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **market analyst**. Your one job is to produce — or refine an\nexisting — **MarketSnapshot** for this product: the single artifact that\ndeclares *who the product is for*, *what they are trying to get done*, and\n*how the product is positioned* to them. You reason top-down from the\nproduct idea (there is no code yet in this phase); you do not model the\ndomain, author resources, or write features — later playbooks consume your\nsnapshot to do that.\n\n## The shape you return is FLAT, not nested\n\nRead this before the slice list below, because the slices read like a hierarchy and the object is\nnot one.\n\nA MarketSnapshot is **~16 sibling top-level collections** — `category`, `icps`, `personas`, `jobs`,\n`pains`, `gains`, `tonesOfVoice`, `benefits`, `positionings`, `channels`, `alternatives`,\n`triggers`, `buyingJourneys`, `proofs`, `objections`, `messageTemplates` — and entities point at\neach other with flat **ref strings** (`jobRef`, `painRef`, `gainRef`, `personaRef`, `alternativeRef`,\n…). An ICP does not CONTAIN its jobs; it names them:\n\n```\njobs: [ { ref: 'job-close-the-week', statement: '…' } ] // the job itself, top level\nicps: [ { ref: 'icp-small-team',\n jobs: [ { jobRef: 'job-close-the-week', importance: … } ] } ] // the ICP's REFERENCE to it\n```\n\n⚠ **Measured on this playbook, 2026-08-29.** A first attempt returned 41,098 characters that were\nrejected wholesale: it had nested `personas`, `benefits`, `positionings`, `channels`, `alternatives`,\n`triggers`, `proofs` and `objections` INSIDE `icps[0]`, left every top-level collection empty, and\nwrote whole job objects where `{ jobRef, importance }` belongs. The retry recovered it, but a full\ngeneration was spent discovering the shape. The slice ordering below is a THINKING order — what to\nwork out first — never the structure of the answer.\n\nA MarketSnapshot is assembled from these slices, each owned by a dedicated\n`market_*` app-knowledge skill. Those skills are named here so you know which\nauthoring contract each slice belongs to, and so a later CODING agent can open\nthe right one — you cannot: this step has no tools, and sixteen skill bodies do\nnot fit in one brief. Everything you need to author the snapshot is in THIS\nmethod and your declared inputs; where a detail is genuinely only in a skill,\nsay so on what you author rather than inventing it. You author them in\ndependency order because later slices reference earlier refs:\n\n1. **Category** — the one market category the product competes in, plus the\n rejected adjacent categories. (`market-category`)\n2. **ICPs** — the Ideal Customer Profiles: the firmographic / demographic\n segments the product is sold to. (`market-icp`)\n3. **Personas** — the human roles inside each ICP, including buying-group\n members. Every ICP needs at least one persona. (`market-persona`)\n4. **Jobs / Pains / Gains** — the Strategyzer customer-profile triplet for\n the personas: what they are trying to do, what blocks them, what a win\n looks like. (`market-jobs-pains-gains`)\n5. **Tones of voice** — the named brand voices the product speaks in.\n (`market-tone-of-voice`)\n6. **Benefits** — the outcome claims the product delivers, weighted against\n the pains/gains they relieve/create. (`market-add-feature-benefit`)\n7. **Positionings** — the per-ICP marketing-truth promise. Author one per\n ICP that the product actually targets. (`market-positioning-authoring`)\n8. **Reach surfaces** — the go-to-market context: channels, competing\n alternatives, buying triggers + per-ICP buying journeys, proofs, and the\n objections proofs answer. (`market-channels`, `market-alternatives`,\n `market-triggers-and-journey`, `market-proof-and-objection`)\n9. **Message templates** — reusable prompt templates that render from the\n snapshot above. Author last; they reference the earlier slices.\n (`market-message-templates-authoring`)\n\nAuthor only the slices the product's stage warrants — a first pass may stop\nafter positionings and leave the phase-3/4 reach surfaces empty (they\ndefault to `[]`). A snapshot with a category, at least one ICP, its\npersonas, the jobs/pains/gains triplet, and at least one positioning is a\nlegitimate v1; the reach surfaces and message templates are additive.\n\n## Where the snapshot lives\n\nThe MarketSnapshot for this journey is placed under\n`specifications/src/market/index.ts`. That is the artifact this\nplaybook owns and the rest of the top-down phase reads. When the product's\ndefinition later stabilises, the snapshot is what seeds the durable market\nspecification under `./specifications/` — but at this phase it is a journey\nartifact, not yet app source.\n\n## Produce vs. refine — read state first\n\nThis playbook is **idempotent** on the journey's market artifact. Before\nauthoring anything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief; do not re-derive it. That state tells you which\n scope the snapshot must be complete *for*.\n2. Check whether a MarketSnapshot already exists by reading the artifact at the\n `market-snapshot` family's landing path, `specifications/src/market/index.ts`.\n The path belongs to the FAMILY, not to this playbook — every playbook that\n writes a market snapshot writes that same file. Its presence or absence\n selects the mode below.\n\n- **No snapshot yet** — produce a fresh one, authoring the slices in the\n order above.\n- **A snapshot exists** — *refine* it: read every slice, keep what still\n holds, and only add/correct the slices the current steering notes or new\n research call for. Never silently discard authored refs — a downstream\n positioning or benefit may depend on an ICP or persona ref, and dropping\n it orphans them (the validator will catch this, but honest refinement\n should not create the orphan in the first place).\n\n## Provenance — record where a claim came from\n\nYou are given the evidence a sibling research step gathered, with the URLs it read.\nWhere an entity's content rests on one of those sources, RECORD that URL on the entity\n— in the schema's own provenance fields, which exist for exactly this:\n\n| field | for |\n|---|---|\n| `pains[].evidence[]`, `gains[].evidence[]`, `benefits[].evidence` | what a source shows about the pain, gain or claim |\n| `proofs[].evidenceUrl`, `proofs[].attribution.url` | the page a proof points at |\n| `alternatives[].notes[]`, `category.notes[]`, `icps[].notes[]` | where the framing came from |\n\n⚠ An earlier revision of this section told you to use `authoredMetadata.notes` instead.\nThat was wrong, and the correction is recorded rather than quietly applied because the\nrun that exposed it did better than the instruction: handed the evidence, the model\nput 10 URLs into the typed `evidence`/`evidenceUrl` fields above and none into the\ngeneric metadata block it had been pointed at. Typed provenance is machine-readable\nand the generic block is prose; prefer the specific field every time one exists.\n\nThis is not bookkeeping. Measured on this playbook's first composite run\n(2026-08-29): the snapshot it produced carried **zero** source URLs and was, on that\ndimension, indistinguishable from the single-call version it replaced — the judge\ncalled the older one's evidence \"self-referential statements such as 'The vision\nspecifies…'\". A sourced claim and an invented one must not look the same in what you\nland, because nobody downstream can tell them apart afterwards.\n\nSo:\n\n- An entity grounded in a fetched page carries its URL in `authoredMetadata.notes`.\n- An entity you INFERRED carries that word, and `confidence` set honestly — `LOW` for\n a hypothesis, not `HIGH` because it reads well.\n- An entity the evidence did not cover is still authorable, and says so.\n\nOmit `authoredMetadata` only where the content is so self-evident that provenance\nwould be noise. A competitor's price is never that.\n\n## Research posture (scaffold depth)\n\nGround each slice in evidence, not invention. At this scaffold depth the\nresearch is whatever the executing agent can gather about the product's\ncategory, competitors, and buyers; capture the *shape* faithfully (real\ncategory, real competing alternatives, plausible ICPs and personas) rather\nthan aspirational fiction. Where you are inferring rather than citing, say so\nin the slice's authored prose so a later, deeper research pass can tighten\nit. Do **not** build a research pipeline or block on external tooling here —\nricher web-research capability is a later-phase concern; this playbook\nconsumes whatever the agent already knows plus the creator's steering.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. It\nenforces the cross-slice invariants — orphan refs (a positioning naming a\nmissing ICP, a benefit naming a missing pain/gain), an ICP with no persona,\ninfluence cycles, duplicate edges, proofs without support, message-template\nplaceholder mismatches, and more. Duplicate or malformed refs and\n`ERROR`-severity issues are hard failures; the snapshot does not advance\nuntil they clear. `WARN`-severity issues (e.g. stale-authored, a missing\npositioning for a targeted ICP) do not block but should be resolved. Read\n`market-snapshot-validation` for the full issue catalogue and emit a clean\nsnapshot the first time.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. The following are explicitly **out of\nscope here** and are deepened in the methodology-depth phase, not now:\n\n- **Deep competitive teardown** — the reach surfaces capture *that* an\n alternative exists and *why* a buyer might pick it; a quantified,\n feature-by-feature competitor matrix is later-phase work.\n- **Quantified FIT / Kano scoring** — `market-scoring-interpretation` reads\n the deterministic FIT scorer; at scaffold depth you consume it to sanity-\n check benefit weighting, not to drive a precise prioritization model. The\n prioritization seam stays pluggable (see the capability-map playbook).\n- **Opportunity / TAM sizing and evidence depth** — jobs/pains/gains are\n authored as framing, not as a sized, sourced market model.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nA single MarketSnapshot at `specifications/src/market/index.ts`,\nassembled from the slices above via their `market_*` skills, passing the\n`market-snapshot-valid` gate. The creator reviews the result (approval posture\n`approve_result`) before it is accepted as the journey's market intent.\n\n## References\n\nThese are skill FOLDERS installed in the application, listed so each slice's\nauthoring contract has a name. This step has no tools and does not open them.\n\n- `market-authoring-overview` — the orchestrator for\n the whole market slice; read it first to see how the slices fit together.\n- `market-category` — author the singular market\n category.\n- `market-icp` — author the Ideal Customer Profiles.\n- `market-persona` — author the personas per ICP.\n- `market-jobs-pains-gains` — author the Strategyzer\n jobs/pains/gains triplet.\n- `market-tone-of-voice` — author the named brand\n voices.\n- `market-add-feature-benefit` — author the benefit\n claims and their pain/gain weighting.\n- `market-positioning-authoring` — author the per-ICP\n positioning promise.\n- `market-channels` — author the reach channels.\n- `market-alternatives` — author the competing\n alternatives.\n- `market-triggers-and-journey` — author buying\n triggers and per-ICP buying journeys.\n- `market-proof-and-objection` — author proofs and\n the objections they answer.\n- `market-message-templates-authoring` — author the\n reusable message templates (last).\n- `market-scoring-interpretation` — interpret the\n deterministic FIT scorer to sanity-check benefit weighting.\n- `market-snapshot-validation` — the full validation\n issue catalogue the quality gate enforces.\n",
|
|
40
|
+
"skillRefs": [
|
|
41
|
+
"market-authoring-overview",
|
|
42
|
+
"market-category",
|
|
43
|
+
"market-icp",
|
|
44
|
+
"market-persona",
|
|
45
|
+
"market-jobs-pains-gains",
|
|
46
|
+
"market-tone-of-voice",
|
|
47
|
+
"market-add-feature-benefit",
|
|
48
|
+
"market-positioning-authoring",
|
|
49
|
+
"market-channels",
|
|
50
|
+
"market-alternatives",
|
|
51
|
+
"market-triggers-and-journey",
|
|
52
|
+
"market-proof-and-objection",
|
|
53
|
+
"market-message-templates-authoring",
|
|
54
|
+
"market-scoring-interpretation",
|
|
55
|
+
"market-snapshot-validation"
|
|
56
|
+
],
|
|
57
|
+
"skillBodyRefs": [],
|
|
58
|
+
"contextSources": [],
|
|
59
|
+
"draftableDocumentDefinitionRefs": [],
|
|
60
|
+
"suspendsForClarification": false,
|
|
61
|
+
"briefAdequacyGate": false,
|
|
62
|
+
"briefAdequacyExcludedSources": []
|
|
63
|
+
},
|
|
64
|
+
"executor": "companion_agent",
|
|
65
|
+
"approval": "approve_result",
|
|
66
|
+
"budget": {
|
|
67
|
+
"maxRuns": 3
|
|
68
|
+
},
|
|
69
|
+
"onFailure": "keep_and_flag"
|
|
70
|
+
}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"aggregationPolicyRef":"application-creation:aggregation/worst-top-down-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/capability-completeness","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1}],"instruction":"Determine whether every current-horizon market benefit is connected to at least one resolvable delivering feature. Treat an unwired benefit as a material gap; do not infer a connection from thematic similarity alone.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All benefits are wired, but one or more connections are weak, indirect, or insufficiently explained.","GAP":"At least one current-horizon benefit has no resolvable delivering feature.","INDETERMINATE":"The accepted evidence cannot establish the benefit-to-feature wiring completely.","PASS":"Every current-horizon benefit has at least one resolvable delivering feature."}},{"criterionRef":"application-creation:criterion/compliance-presence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1}],"instruction":"Determine whether a product handling regulated or sensitive data declares at least one applicable compliance constraint. Do not invent regulation applicability; report indeterminate when the accepted evidence does not establish the data or sector posture.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A compliance constraint exists, but its applicability or coverage is weakly established.","GAP":"A regulated-data trigger is established and no applicable compliance constraint is declared.","INDETERMINATE":"The evidence cannot establish the regulated-data trigger or the applicable constraint posture.","PASS":"The evidence establishes either no regulated-data trigger or an applicable declared compliance constraint."}},{"criterionRef":"application-creation:criterion/positioning-icp-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1}],"instruction":"Determine whether positioning pillars address the declared core ICPs without centring an anti-target segment. Preserve the authored ICP classifications and do not silently reclassify a segment.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Positioning is broadly coherent but under-serves a core ICP or approaches an anti-target boundary.","GAP":"Positioning ignores the core ICPs or explicitly centres an anti-target segment.","INDETERMINATE":"The accepted evidence cannot connect positioning pillars to the classified ICP set.","PASS":"Positioning addresses the core ICPs and does not centre an anti-target segment."}},{"criterionRef":"application-creation:criterion/requirement-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon functional requirement is delivered by a roadmap phase or explicitly deferred in accepted roadmap intent. Do not treat absence as deliberate deferral.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete, but one or more deferrals are weakly justified or difficult to trace.","GAP":"At least one functional requirement is neither delivered nor explicitly deferred.","INDETERMINATE":"The accepted evidence cannot establish complete requirement-to-roadmap accounting.","PASS":"Every current-horizon functional requirement is delivered or explicitly deferred."}},{"criterionRef":"application-creation:criterion/success-criterion-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon vision success criterion is delivered by at least one roadmap phase. Keep success criteria distinct from implementation tasks or generic aspirations.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All criteria are covered, but one or more delivery links are weak or overly indirect.","GAP":"At least one current-horizon success criterion is not delivered by any roadmap phase.","INDETERMINATE":"The accepted evidence cannot establish complete success-criterion-to-roadmap coverage.","PASS":"Every current-horizon success criterion is delivered by at least one roadmap phase."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/top-down-phase-gate","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.phase-gate"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
|
|
1
|
+
{"aggregationPolicyRef":"application-creation:aggregation/worst-top-down-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["market.benefit","feature-drafts.draft"],"criterionRef":"application-creation:criterion/capability-completeness","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1}],"instruction":"Determine whether every current-horizon market benefit is connected to at least one resolvable delivering feature. Treat an unwired benefit as a material gap; do not infer a connection from thematic similarity alone.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All benefits are wired, but one or more connections are weak, indirect, or insufficiently explained.","GAP":"At least one current-horizon benefit has no resolvable delivering feature.","INDETERMINATE":"The accepted evidence cannot establish the benefit-to-feature wiring completely.","PASS":"Every current-horizon benefit has at least one resolvable delivering feature."}},{"criterionRef":"application-creation:criterion/compliance-presence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1}],"instruction":"Determine whether a product handling regulated or sensitive data declares at least one applicable compliance constraint. Do not invent regulation applicability; report indeterminate when the accepted evidence does not establish the data or sector posture.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A compliance constraint exists, but its applicability or coverage is weakly established.","GAP":"A regulated-data trigger is established and no applicable compliance constraint is declared.","INDETERMINATE":"The evidence cannot establish the regulated-data trigger or the applicable constraint posture.","PASS":"The evidence establishes either no regulated-data trigger or an applicable declared compliance constraint."}},{"assessesAspects":["market.icp","market.positioning"],"criterionRef":"application-creation:criterion/positioning-icp-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1}],"instruction":"Determine whether positioning pillars address the declared core ICPs without centring an anti-target segment. Preserve the authored ICP classifications and do not silently reclassify a segment.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Positioning is broadly coherent but under-serves a core ICP or approaches an anti-target boundary.","GAP":"Positioning ignores the core ICPs or explicitly centres an anti-target segment.","INDETERMINATE":"The accepted evidence cannot connect positioning pillars to the classified ICP set.","PASS":"Positioning addresses the core ICPs and does not centre an anti-target segment."}},{"assessesAspects":["requirements.functional","roadmap.phase"],"criterionRef":"application-creation:criterion/requirement-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon functional requirement is delivered by a roadmap phase or explicitly deferred in accepted roadmap intent. Do not treat absence as deliberate deferral.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete, but one or more deferrals are weakly justified or difficult to trace.","GAP":"At least one functional requirement is neither delivered nor explicitly deferred.","INDETERMINATE":"The accepted evidence cannot establish complete requirement-to-roadmap accounting.","PASS":"Every current-horizon functional requirement is delivered or explicitly deferred."}},{"assessesAspects":["vision.success-criterion","roadmap.phase"],"criterionRef":"application-creation:criterion/success-criterion-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon vision success criterion is delivered by at least one roadmap phase. Keep success criteria distinct from implementation tasks or generic aspirations.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All criteria are covered, but one or more delivery links are weak or overly indirect.","GAP":"At least one current-horizon success criterion is not delivered by any roadmap phase.","INDETERMINATE":"The accepted evidence cannot establish complete success-criterion-to-roadmap coverage.","PASS":"Every current-horizon success criterion is delivered by at least one roadmap phase."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/top-down-phase-gate","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.phase-gate"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/journey-phase-transition","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/capability-completeness","application-creation:evidence-requirement/compliance-presence","application-creation:evidence-requirement/positioning-icp-coherence","application-creation:evidence-requirement/requirement-coverage","application-creation:evidence-requirement/success-criterion-coverage"],"requirementRef":"application-creation:authority-requirement/top-down-to-bottom-up-transition","requirementVersion":1,"riskClassRef":"application-creation:risk/bootstrap-non-regulated-phase-transition","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/top-down-phase-gate","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/top-down-to-bottom-up-transition","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/top-down-phase-gate","policyVersion":1},"decisionPointRef":"application-creation:decision-point/top-down-phase-gate","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/top-down-phase-gate","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/top-down-phase-gate","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/required-family-validity"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-transition","triggerRefs":["application-creation:trigger/top-down-definition-set-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-top-down-coherence-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/capability-completeness","application-creation:evidence-requirement/compliance-presence","application-creation:evidence-requirement/positioning-icp-coherence","application-creation:evidence-requirement/requirement-coverage","application-creation:evidence-requirement/success-criterion-coverage"],"hardFloorRef":"application-creation:hard-floor/required-family-validity"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/top-down-phase-gate","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/top-down-phase-gate","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-top-down-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/capability-completeness","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1}],"instruction":"Determine whether every current-horizon market benefit is connected to at least one resolvable delivering feature. Treat an unwired benefit as a material gap; do not infer a connection from thematic similarity alone.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All benefits are wired, but one or more connections are weak, indirect, or insufficiently explained.","GAP":"At least one current-horizon benefit has no resolvable delivering feature.","INDETERMINATE":"The accepted evidence cannot establish the benefit-to-feature wiring completely.","PASS":"Every current-horizon benefit has at least one resolvable delivering feature."}},{"criterionRef":"application-creation:criterion/compliance-presence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1}],"instruction":"Determine whether a product handling regulated or sensitive data declares at least one applicable compliance constraint. Do not invent regulation applicability; report indeterminate when the accepted evidence does not establish the data or sector posture.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A compliance constraint exists, but its applicability or coverage is weakly established.","GAP":"A regulated-data trigger is established and no applicable compliance constraint is declared.","INDETERMINATE":"The evidence cannot establish the regulated-data trigger or the applicable constraint posture.","PASS":"The evidence establishes either no regulated-data trigger or an applicable declared compliance constraint."}},{"criterionRef":"application-creation:criterion/positioning-icp-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1}],"instruction":"Determine whether positioning pillars address the declared core ICPs without centring an anti-target segment. Preserve the authored ICP classifications and do not silently reclassify a segment.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Positioning is broadly coherent but under-serves a core ICP or approaches an anti-target boundary.","GAP":"Positioning ignores the core ICPs or explicitly centres an anti-target segment.","INDETERMINATE":"The accepted evidence cannot connect positioning pillars to the classified ICP set.","PASS":"Positioning addresses the core ICPs and does not centre an anti-target segment."}},{"criterionRef":"application-creation:criterion/requirement-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon functional requirement is delivered by a roadmap phase or explicitly deferred in accepted roadmap intent. Do not treat absence as deliberate deferral.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete, but one or more deferrals are weakly justified or difficult to trace.","GAP":"At least one functional requirement is neither delivered nor explicitly deferred.","INDETERMINATE":"The accepted evidence cannot establish complete requirement-to-roadmap accounting.","PASS":"Every current-horizon functional requirement is delivered or explicitly deferred."}},{"criterionRef":"application-creation:criterion/success-criterion-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon vision success criterion is delivered by at least one roadmap phase. Keep success criteria distinct from implementation tasks or generic aspirations.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All criteria are covered, but one or more delivery links are weak or overly indirect.","GAP":"At least one current-horizon success criterion is not delivered by any roadmap phase.","INDETERMINATE":"The accepted evidence cannot establish complete success-criterion-to-roadmap coverage.","PASS":"Every current-horizon success criterion is delivered by at least one roadmap phase."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/top-down-phase-gate","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.phase-gate"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/top-down-phase-gate","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-benefits","criterionRef":"application-creation:criterion/capability-completeness","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-capability-wiring"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/regulated-data-and-compliance-constraints","criterionRef":"application-creation:criterion/compliance-presence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-compliance"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/core-and-anti-target-icps","criterionRef":"application-creation:criterion/positioning-icp-coherence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-positioning"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-functional-requirements","criterionRef":"application-creation:criterion/requirement-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/requirements-roadmap"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-success-criteria","criterionRef":"application-creation:criterion/success-criterion-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-roadmap"}],"schemaVersion":1}
|
|
1
|
+
{"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/journey-phase-transition","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/capability-completeness","application-creation:evidence-requirement/compliance-presence","application-creation:evidence-requirement/positioning-icp-coherence","application-creation:evidence-requirement/requirement-coverage","application-creation:evidence-requirement/success-criterion-coverage"],"requirementRef":"application-creation:authority-requirement/top-down-to-bottom-up-transition","requirementVersion":1,"riskClassRef":"application-creation:risk/bootstrap-non-regulated-phase-transition","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/top-down-phase-gate","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/top-down-to-bottom-up-transition","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/top-down-phase-gate","policyVersion":1},"decisionPointRef":"application-creation:decision-point/top-down-phase-gate","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/top-down-phase-gate","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/top-down-phase-gate","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/required-family-validity"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-transition","triggerRefs":["application-creation:trigger/top-down-definition-set-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-top-down-coherence-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/capability-completeness","application-creation:evidence-requirement/compliance-presence","application-creation:evidence-requirement/positioning-icp-coherence","application-creation:evidence-requirement/requirement-coverage","application-creation:evidence-requirement/success-criterion-coverage"],"hardFloorRef":"application-creation:hard-floor/required-family-validity"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/top-down-phase-gate","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/top-down-phase-gate","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-top-down-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["market.benefit","feature-drafts.draft"],"criterionRef":"application-creation:criterion/capability-completeness","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1}],"instruction":"Determine whether every current-horizon market benefit is connected to at least one resolvable delivering feature. Treat an unwired benefit as a material gap; do not infer a connection from thematic similarity alone.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All benefits are wired, but one or more connections are weak, indirect, or insufficiently explained.","GAP":"At least one current-horizon benefit has no resolvable delivering feature.","INDETERMINATE":"The accepted evidence cannot establish the benefit-to-feature wiring completely.","PASS":"Every current-horizon benefit has at least one resolvable delivering feature."}},{"criterionRef":"application-creation:criterion/compliance-presence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1}],"instruction":"Determine whether a product handling regulated or sensitive data declares at least one applicable compliance constraint. Do not invent regulation applicability; report indeterminate when the accepted evidence does not establish the data or sector posture.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A compliance constraint exists, but its applicability or coverage is weakly established.","GAP":"A regulated-data trigger is established and no applicable compliance constraint is declared.","INDETERMINATE":"The evidence cannot establish the regulated-data trigger or the applicable constraint posture.","PASS":"The evidence establishes either no regulated-data trigger or an applicable declared compliance constraint."}},{"assessesAspects":["market.icp","market.positioning"],"criterionRef":"application-creation:criterion/positioning-icp-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1}],"instruction":"Determine whether positioning pillars address the declared core ICPs without centring an anti-target segment. Preserve the authored ICP classifications and do not silently reclassify a segment.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Positioning is broadly coherent but under-serves a core ICP or approaches an anti-target boundary.","GAP":"Positioning ignores the core ICPs or explicitly centres an anti-target segment.","INDETERMINATE":"The accepted evidence cannot connect positioning pillars to the classified ICP set.","PASS":"Positioning addresses the core ICPs and does not centre an anti-target segment."}},{"assessesAspects":["requirements.functional","roadmap.phase"],"criterionRef":"application-creation:criterion/requirement-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon functional requirement is delivered by a roadmap phase or explicitly deferred in accepted roadmap intent. Do not treat absence as deliberate deferral.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete, but one or more deferrals are weakly justified or difficult to trace.","GAP":"At least one functional requirement is neither delivered nor explicitly deferred.","INDETERMINATE":"The accepted evidence cannot establish complete requirement-to-roadmap accounting.","PASS":"Every current-horizon functional requirement is delivered or explicitly deferred."}},{"assessesAspects":["vision.success-criterion","roadmap.phase"],"criterionRef":"application-creation:criterion/success-criterion-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon vision success criterion is delivered by at least one roadmap phase. Keep success criteria distinct from implementation tasks or generic aspirations.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All criteria are covered, but one or more delivery links are weak or overly indirect.","GAP":"At least one current-horizon success criterion is not delivered by any roadmap phase.","INDETERMINATE":"The accepted evidence cannot establish complete success-criterion-to-roadmap coverage.","PASS":"Every current-horizon success criterion is delivered by at least one roadmap phase."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/top-down-phase-gate","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.phase-gate"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/top-down-phase-gate","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-benefits","criterionRef":"application-creation:criterion/capability-completeness","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-capability-wiring"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/regulated-data-and-compliance-constraints","criterionRef":"application-creation:criterion/compliance-presence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-compliance"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/core-and-anti-target-icps","criterionRef":"application-creation:criterion/positioning-icp-coherence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-positioning"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-functional-requirements","criterionRef":"application-creation:criterion/requirement-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/requirements-roadmap"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-success-criteria","criterionRef":"application-creation:criterion/success-criterion-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-roadmap"}],"schemaVersion":1}
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
# Top-Down
|
|
1
|
+
# Top-Down Coherence Assessment
|
|
2
2
|
|
|
3
3
|
### Target Application Framing
|
|
4
4
|
|
|
@@ -14,83 +14,50 @@ Read and apply these patterns from the application-developer point of view:
|
|
|
14
14
|
|
|
15
15
|
## Purpose
|
|
16
16
|
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
17
|
+
Assess whether the current top-down definitions agree well enough to guide the next
|
|
18
|
+
work. This playbook writes no application specification and accepts nothing. It can
|
|
19
|
+
be rerun after the working definitions change.
|
|
20
20
|
|
|
21
|
-
|
|
22
|
-
application-feature, requirements, vision, or roadmap state may invalidate
|
|
23
|
-
earlier evidence and make the decision point eligible again.
|
|
21
|
+
## Readiness and inputs
|
|
24
22
|
|
|
25
|
-
|
|
23
|
+
Inspect the loaded specification values this run is given. `vision-brief`,
|
|
24
|
+
`market-snapshot`, `requirements` and `roadmap` must each pass their declared
|
|
25
|
+
family-validity precondition. A cross-family assessment cannot replace that validation.
|
|
26
26
|
|
|
27
|
-
|
|
27
|
+
The evaluator reads those families plus `feature-drafts` and `business-model` when
|
|
28
|
+
present. These optional inputs add implementation and commercial context; their
|
|
29
|
+
absence does not introduce another readiness gate. The runtime loads the exported
|
|
30
|
+
working-tree values. There is no evidence-sealing step or accepted-head projection.
|
|
28
31
|
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
valid. This floor is non-bypassable.
|
|
33
|
-
2. The compiled Evaluation Protocol interprets cross-family coherence from an
|
|
34
|
-
exact sealed evidence set. It cannot make an invalid family valid or replace
|
|
35
|
-
missing evidence with an assumption.
|
|
36
|
-
|
|
37
|
-
The canonical criterion instructions, evidence identities, verdict guidance,
|
|
38
|
-
prompt-assembly strategy, and aggregation precedence live in
|
|
39
|
-
`playbook.definition.ts`. This method explains how to operate the treatment; it
|
|
40
|
-
does not duplicate that executable meaning.
|
|
41
|
-
|
|
42
|
-
## Evidence preparation
|
|
43
|
-
|
|
44
|
-
Use `journey-status` to identify the current accepted heads for:
|
|
45
|
-
|
|
46
|
-
- `vision-brief`
|
|
47
|
-
- `market-snapshot`
|
|
48
|
-
- `requirements`
|
|
49
|
-
- `roadmap`
|
|
50
|
-
- `feature-drafts`
|
|
51
|
-
|
|
52
|
-
Project only the accepted, current-horizon data required by the five protocol
|
|
53
|
-
criteria. Seal the projected artifacts and their provenance before evaluation.
|
|
54
|
-
If the evidence projection cannot account for a mandatory requirement, request
|
|
55
|
-
evidence; do not invoke the evaluator on an incomplete set.
|
|
56
|
-
|
|
57
|
-
Business model is not an input to this treatment version and must not be loaded
|
|
58
|
-
into its knowledge projection. A later treatment version may add a distinct
|
|
59
|
-
business-model criterion when the structured family contracts can support it
|
|
60
|
-
without prose-only inference.
|
|
32
|
+
The computed coherence report (the declared `coherence_report` context section of your brief) supplies the
|
|
33
|
+
supported dangling-reference and coverage checks. Interpret their consequences;
|
|
34
|
+
do not invent checks or recompute the arithmetic in prose.
|
|
61
35
|
|
|
62
36
|
## Evaluation
|
|
63
37
|
|
|
64
|
-
The
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
Aggregation uses the protocol’s declared worst-verdict precedence:
|
|
69
|
-
|
|
70
|
-
`GAP` → `INDETERMINATE` → `CONCERN` → `PASS`
|
|
71
|
-
|
|
72
|
-
`INDETERMINATE` means that the available evidence is missing, conflicting, or
|
|
73
|
-
too uncertain to decide. A transport, model, timeout, or output-validation
|
|
74
|
-
failure is an evaluator failure and blocks the treatment; it is never rewritten
|
|
75
|
-
as semantic uncertainty.
|
|
38
|
+
The compiled evaluation treatment supplies the criteria and their guidance. For each
|
|
39
|
+
criterion, relate the verdict to the available evidence and explain what should change.
|
|
40
|
+
Use `INDETERMINATE` when evidence does not support a semantic conclusion.
|
|
76
41
|
|
|
77
|
-
|
|
42
|
+
The current judge aggregates by worst severity:
|
|
43
|
+
`GAP` → `INDETERMINATE` → `CONCERN` → `PASS`.
|
|
44
|
+
Duplicate criterion results retain the worst verdict and all their rationales. Missing
|
|
45
|
+
criterion results remain indeterminate. The treatment's declarative policy fields do
|
|
46
|
+
not independently create another approval or continuation workflow in this runner.
|
|
78
47
|
|
|
79
|
-
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
- a hard-floor failure or evaluator failure blocks.
|
|
48
|
+
A failed model call or unusable treatment produces a skipped/unavailable judge result
|
|
49
|
+
(`judged: false` with `skipped`), not a semantic pass. Check that status before using
|
|
50
|
+
any verdict as evidence that assessment happened.
|
|
83
51
|
|
|
84
|
-
|
|
85
|
-
membrane. Human authorization of the top-down → bottom-up transition remains a
|
|
86
|
-
separate, explicit boundary and must not be inferred from a passing semantic
|
|
87
|
-
assessment. Use `journey-report` to surface the assessment and
|
|
88
|
-
`journey-approve` only when the authority workflow is active.
|
|
52
|
+
## Read the result and decide what to do
|
|
89
53
|
|
|
90
|
-
|
|
54
|
+
The response reports `assessed: true`, the loaded `subjects`, a `reviewGuide`, the
|
|
55
|
+
judge result when supplied, and `accepted: false`. The judge is advisory: this call
|
|
56
|
+
does not automatically revise families, request authority, switch phases or block a
|
|
57
|
+
transition based on its verdict. Use the findings to choose the next work and review
|
|
58
|
+
its outcome through the application's actual workflow.
|
|
91
59
|
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
|
|
96
|
-
assessment basis.
|
|
60
|
+
This invocation performs one assessment. Do not infer enforced revision or
|
|
61
|
+
additional-evidence loops from the playbook's declared budget or continuation fields.
|
|
62
|
+
When an input changes, reassess the new values rather than treating an old verdict as
|
|
63
|
+
proof about the changed product.
|