@wildo-ai/framework-knowledge 1.1.11 → 1.1.12
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 +1 -1
- package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +4 -0
- package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +25 -3
- package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +40 -12
- package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +3 -3
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +12 -0
- package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +19 -2
- package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +33 -9
- package/dist/esm/framework-knowledge.definitions.d.ts +2 -3
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +170 -32
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js.map +1 -1
- package/dist/esm/framework-knowledge.research-provenance.d.ts +6 -4
- package/dist/esm/framework-knowledge.research-provenance.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.research-provenance.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/index.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -3
- 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 +4 -12
- 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.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +12 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +7 -4
- 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 +76 -14
- 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 +0 -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 +3 -15
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -1
- 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 +35 -14
- 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 +16 -8
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +19 -8
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +29 -3
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +80 -16
- 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.map +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +2 -2
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +5 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +3 -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.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +45 -10
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +61 -21
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +4 -3
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +8 -5
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +3 -5
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +1 -1
- 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 +3 -3
- 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.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +8 -6
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +5 -0
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +8 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +4 -1
- 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 +11 -3
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +6 -4
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +3 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +4 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +10 -1
- 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 +36 -13
- 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 +8 -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 +7 -1
- 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 +4 -1
- 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 +34 -6
- 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 +5 -2
- 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 +4 -3
- 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.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +2 -2
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +22 -10
- 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 +39 -29
- 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.map +1 -1
- 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 +8 -3
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -7
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -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.map +1 -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 +2 -2
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +1 -1
- 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.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +13 -5
- 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 -7
- 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 +12 -14
- 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 +3 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +2 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +3 -1
- 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 +2 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts +4 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.js +14 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +3 -1
- 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 +4 -2
- 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 +34 -1
- 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 +35 -17
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/esm/source-anchor-grammar.d.ts.map +1 -1
- package/dist/esm/source-anchor-grammar.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 -1
- package/dist/knowledge/manifest.json +7 -7
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +6 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +4 -4
- package/dist/knowledge/playbooks/bottom_up.build/method.md +12 -2
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +5 -3
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +439 -27
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +15 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +203 -7
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -5
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +2 -2
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +2 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +104 -2
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +59 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +18 -6
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +121 -24
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +51 -7
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +15 -8
- package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +2 -1
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +10 -2
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +4 -3
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +34 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +9 -2
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +1 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +27 -12
- package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +11 -5
- package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +4 -4
- package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +7 -2
- package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +1 -0
- package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +6 -6
- package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +3 -4
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +56 -5
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +3 -2
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +6 -4
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +5 -1
- package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +8 -1
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -3
- package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +11 -4
- package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +3 -2
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +16 -6
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +3 -2
- package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +5 -1
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/method.md +43 -11
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +24 -8
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +6 -2
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +49 -14
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +3 -3
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +6 -2
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +20 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +4 -3
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +69 -65
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +11 -7
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.definition/method.md +3 -1
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +11 -3
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +4 -2
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +4 -3
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +3 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +3 -2
- 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/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +10 -6
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +7 -0
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +5 -1
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +6 -1
- package/dist/knowledge/playbooks/top_down.service-method/method.md +19 -1
- package/dist/knowledge/playbooks/top_down.service-method/playbook.json +16 -4
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +5 -2
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +9 -3
- package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +17 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +59 -15
- package/dist/knowledge/references/application-documentation-chapters.config.md +45 -10
- package/dist/knowledge/references/application-documentation-plan.config.md +2 -2
- package/dist/knowledge/references/application-maturity.config.md +27 -1
- package/dist/knowledge/references/backend.inbound-channels.attachment-adoption.md +4 -2
- package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +52 -11
- package/dist/knowledge/references/backend.inbound-handlers.definition.md +38 -1
- package/dist/knowledge/references/brand.name-screening.config.md +30 -3
- package/dist/knowledge/references/build-plan.task-graph.config.md +200 -4
- package/dist/knowledge/references/business-model.pricing-plan.config.md +12 -9
- package/dist/knowledge/references/business-model.snapshot.config.md +29 -2
- package/dist/knowledge/references/business-model.snapshot.validation.md +11 -8
- package/dist/knowledge/references/companion.introspection.behaviors.market.md +3 -0
- package/dist/knowledge/references/companion.market.generation-service.md +46 -5
- package/dist/knowledge/references/companion.market.prompt-renderer.md +1 -1
- package/dist/knowledge/references/companion.technical-doc.service.md +195 -63
- package/dist/knowledge/references/domain-plan.record-partition.md +105 -0
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +3 -1
- package/dist/knowledge/references/engine.saas-technical-doc.config.md +69 -15
- package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +10 -0
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +6 -0
- package/dist/knowledge/references/example.backend.custom-operation.declared-refusal-code.md +41 -0
- package/dist/knowledge/references/example.backend.custom-operation.external-effect-reservation.md +107 -0
- package/dist/knowledge/references/example.blueprint.definition.internal-tool.md +4 -2
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +8 -5
- package/dist/knowledge/references/example.infra.environment-config.local.md +13 -66
- package/dist/knowledge/references/example.module.companion-exports.full.md +1 -0
- package/dist/knowledge/references/example.module.relationships.actor-edge-back-to-scope-owner.md +35 -35
- package/dist/knowledge/references/example.navigation.one-entry-per-concept.md +47 -0
- package/dist/knowledge/references/example.organization-identity.system-of-record-partitions.md +18 -0
- package/dist/knowledge/references/example.provider.backend-module-shape.md +28 -4
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +0 -4
- package/dist/knowledge/references/example.resource.custom-view.backend-refusal.md +75 -0
- package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +8 -7
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +37 -2
- package/dist/knowledge/references/example.resource.ui-behavior.record-template.md +0 -1
- package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +1 -1
- package/dist/knowledge/references/example.resource.ui-behavior.workflow-record-page.md +212 -0
- package/dist/knowledge/references/example.subject-export.portability-archive.md +42 -0
- package/dist/knowledge/references/example.views.app-level.workflow-home.md +238 -0
- package/dist/knowledge/references/example.website.demo.complete-items.md +3 -3
- package/dist/knowledge/references/example.website.pricing.audit-payloads.md +38 -0
- package/dist/knowledge/references/example.website.pricing.catalog-load.md +77 -0
- package/dist/knowledge/references/example.website.pricing.offers.md +43 -0
- package/dist/knowledge/references/example.website.pricing.plans-section.md +20 -0
- package/dist/knowledge/references/example.website.pricing.plans.md +88 -0
- package/dist/knowledge/references/example.website.section.stats.md +1 -1
- package/dist/knowledge/references/experience-plan.config.md +111 -1
- package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +2 -0
- package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +8 -1
- package/dist/knowledge/references/external-connectors.models.hook-signature-algorithms.md +104 -0
- package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +11 -6
- package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +165 -0
- package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +1035 -19
- package/dist/knowledge/references/external-connectors.private.provider-compliance-state-collector.md +36 -0
- package/dist/knowledge/references/external-connectors.private.provider-configuration-check.md +69 -0
- package/dist/knowledge/references/integration-plan.config.md +7 -7
- package/dist/knowledge/references/placement-plan.config.md +19 -0
- package/dist/knowledge/references/platform.config.backing-services.md +9 -11
- package/dist/knowledge/references/platform.config.environment.deployment.md +133 -8
- package/dist/knowledge/references/platform.config.infra-provider-resolution.md +3 -3
- package/dist/knowledge/references/platform.config.infrastructure-host.md +0 -1
- package/dist/knowledge/references/platform.config.platform-key-management.md +84 -8
- package/dist/knowledge/references/platform.config.saas.md +20 -18
- package/dist/knowledge/references/presets.3d.frame-style-resolution.md +65 -0
- package/dist/knowledge/references/presets.layouts-2d.authoring.md +1 -1
- package/dist/knowledge/references/presets.models.field-form-control-variant.md +32 -0
- package/dist/knowledge/references/presets.models.labelling.sections.md +39 -0
- package/dist/knowledge/references/presets.models.surface-policy.defaults.md +3 -3
- package/dist/knowledge/references/presets.models.surface-variant.md +5 -4
- package/dist/knowledge/references/presets.themes.compose-theme.md +2 -1
- package/dist/knowledge/references/requirements.non-functional-requirement.config.md +4 -4
- package/dist/knowledge/references/requirements.snapshot.config.md +2 -3
- package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +29 -2
- package/dist/knowledge/references/saas.backend.a2a.token-budget.md +11 -4
- package/dist/knowledge/references/saas.backend.actor-execution-continuation.md +21 -0
- package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +5 -1
- package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +1 -1
- package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +13 -1
- package/dist/knowledge/references/saas.backend.custom-operation.authoritative-fields.md +4 -1
- package/dist/knowledge/references/saas.backend.custom-operation.core-write-precondition.md +38 -0
- package/dist/knowledge/references/saas.backend.custom-operation.external-effect-reservation.md +109 -0
- package/dist/knowledge/references/saas.backend.custom-operation.hook-transaction-posture.md +43 -0
- package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +1 -1
- package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +62 -13
- package/dist/knowledge/references/saas.backend.domain-module.md +30 -1
- package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +26 -3
- package/dist/knowledge/references/saas.backend.flows-actors.chat-reply-handler.md +13 -1
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +363 -2
- package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +5 -3
- package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +1 -1
- package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +9 -4
- package/dist/knowledge/references/saas.backend.flows.start-flow-method.md +2 -1
- package/dist/knowledge/references/saas.backend.privacy.subject-export-archive.md +26 -0
- package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +21 -19
- package/dist/knowledge/references/saas.backend.system-access-service.md +159 -4
- package/dist/knowledge/references/saas.config.content-security-policy.md +26 -9
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +1 -1
- package/dist/knowledge/references/saas.data-seeding.modes.md +4 -1
- package/dist/knowledge/references/saas.data-seeding.row-reference.md +2 -4
- package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +6 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +2 -0
- package/dist/knowledge/references/saas.frontend.chart-dashboard-view.md +43 -0
- package/dist/knowledge/references/saas.frontend.chart-dashboard.md +130 -0
- package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +8 -4
- package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +76 -9
- package/dist/knowledge/references/saas.frontend.command-menu.search-resource.md +3 -3
- package/dist/knowledge/references/saas.frontend.errors.backend-refusal.md +96 -0
- package/dist/knowledge/references/saas.frontend.execution-view.definition.md +40 -0
- package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +4 -0
- package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +3 -5
- package/dist/knowledge/references/saas.frontend.record-page-parts.md +117 -0
- package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +46 -16
- package/dist/knowledge/references/saas.frontend.related-resource-sections.md +6 -0
- package/dist/knowledge/references/saas.frontend.resource-header-title.md +1 -1
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +43 -9
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +259 -15
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -2
- package/dist/knowledge/references/saas.frontend.section-stages.md +63 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +42 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +6 -9
- package/dist/knowledge/references/saas.frontend.viewer-may-perform-operation.md +52 -0
- package/dist/knowledge/references/saas.models.agent-suspension.md +8 -8
- package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +21 -0
- package/dist/knowledge/references/saas.models.auth.relationship-grantor-authentication.md +2 -2
- package/dist/knowledge/references/saas.models.config.declared-type-renames.md +246 -0
- package/dist/knowledge/references/saas.models.config.organization-types.md +20 -0
- package/dist/knowledge/references/saas.models.conversation-threads.md +39 -3
- package/dist/knowledge/references/saas.models.crypto-keys.floors.md +10 -0
- package/dist/knowledge/references/saas.models.crypto-keys.local-provider.md +2 -0
- package/dist/knowledge/references/saas.models.crypto-keys.purpose-descriptor.md +39 -0
- package/dist/knowledge/references/saas.models.crypto-keys.purposes.md +7 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -78
- package/dist/knowledge/references/saas.models.engine-capabilities.md +11 -2
- package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +3 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +15 -8
- package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report.md +13 -9
- package/dist/knowledge/references/saas.models.flows-actors.agent-configuration.md +29 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-operation-record.md +7 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-decision-decider.md +8 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-input-form.md +47 -12
- package/dist/knowledge/references/saas.models.flows-actors.operation-approval-requirement.md +31 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +3 -3
- package/dist/knowledge/references/saas.models.flows.runnable-model.md +21 -2
- package/dist/knowledge/references/saas.models.guidance-flow.md +1 -1
- package/dist/knowledge/references/saas.models.http-api-binding.md +19 -8
- package/dist/knowledge/references/saas.models.human-decision-review-marker.md +1 -1
- package/dist/knowledge/references/saas.models.inbound-channels.md +71 -2
- package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +1 -1
- package/dist/knowledge/references/saas.models.notifications.targets.md +3 -1
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +201 -15
- package/dist/knowledge/references/saas.models.organization-assigned-rows-declaration.md +2 -1
- package/dist/knowledge/references/saas.models.organization-own-rows-declaration.md +5 -2
- package/dist/knowledge/references/saas.models.organizations.identity-declaration.md +201 -0
- package/dist/knowledge/references/saas.models.organizations.organization-relationships.md +25 -3
- package/dist/knowledge/references/saas.models.organizations.relationship-invitations.md +6 -2
- package/dist/knowledge/references/saas.models.organizations.relationship-kinds.md +14 -0
- package/dist/knowledge/references/saas.models.organizations.relationship-record-separation.md +1 -0
- package/dist/knowledge/references/saas.models.privacy.data-residency.md +676 -0
- package/dist/knowledge/references/saas.models.privacy.legal-holds.md +46 -2
- package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +6 -0
- package/dist/knowledge/references/saas.models.privacy.retention-binding.md +84 -1
- package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +10 -0
- package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +5 -3
- package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +2 -0
- package/dist/knowledge/references/saas.models.privacy.subject-export.md +134 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +5 -0
- package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +12 -6
- package/dist/knowledge/references/saas.models.providers.compliance-choice.md +15 -0
- package/dist/knowledge/references/saas.models.providers.processing-region-reach.md +132 -0
- package/dist/knowledge/references/saas.models.providers.processing-region-selection.md +139 -0
- package/dist/knowledge/references/saas.models.representative-activity.md +4 -0
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +107 -42
- package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +35 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +4 -2
- package/dist/knowledge/references/saas.models.resource-config.operation-condition-parameters.md +56 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +16 -6
- package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +38 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +14 -16
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +2 -2
- package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +21 -0
- package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +32 -15
- package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +5 -4
- package/dist/knowledge/references/saas.models.roles.definition.md +12 -1
- package/dist/knowledge/references/saas.models.roles.organization-defaults.md +6 -0
- package/dist/knowledge/references/saas.models.schema-family-builder.md +17 -2
- package/dist/knowledge/references/saas.models.system-of-record-actions.md +65 -1
- package/dist/knowledge/references/saas.models.system-of-record-capabilities.md +3 -1
- package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +16 -0
- package/dist/knowledge/references/saas.models.systems-of-record.md +75 -14
- package/dist/knowledge/references/saas.public-runtime.contract.md +41 -23
- package/dist/knowledge/references/saas.rag.retrieval-refusals.md +3 -2
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +12 -4
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +21 -2
- package/dist/knowledge/references/saas.specifications.engine-resource-sub-domain.md +105 -0
- package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +6 -2
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +20 -3
- package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +100 -71
- package/dist/knowledge/references/saas.specifications.translation-glossary.md +80 -0
- package/dist/knowledge/references/saas.website.astro.label-loader.md +44 -10
- package/dist/knowledge/references/saas.website.astro.runtime-helper.md +3 -2
- package/dist/knowledge/references/saas.website.blog.collection-config.md +36 -32
- package/dist/knowledge/references/saas.website.blog.cover-resolver.md +1 -1
- package/dist/knowledge/references/saas.website.blog.frontmatter.md +2 -2
- package/dist/knowledge/references/saas.website.blog.post-renderer.md +2 -2
- package/dist/knowledge/references/saas.website.blog.react-mdx-integration.md +26 -19
- package/dist/knowledge/references/saas.website.blog.react-mdx-query.md +1 -1
- package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +3 -1
- package/dist/knowledge/references/saas.website.config.site-context-loader.md +6 -3
- package/dist/knowledge/references/saas.website.label-keys.format.md +3 -2
- package/dist/knowledge/references/saas.website.label-pack.validator.md +3 -1
- package/dist/knowledge/references/service-method.config.md +35 -2
- package/dist/knowledge/references/vision.constraint.config.md +4 -2
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +60 -0
- package/dist/knowledge/references/zod.decorators.data-categories.md +46 -46
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +24 -0
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +11 -0
- package/dist/knowledge/references/zod.decorators.file-schema.md +4 -3
- package/dist/knowledge/references/zod.decorators.rag-source.md +20 -20
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +2 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +30 -24
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +63 -0
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +63 -0
- package/dist/knowledge/references/zod.factories.bigdecimal.md +4 -4
- package/dist/knowledge/references/zod.factories.code.md +4 -4
- package/dist/knowledge/references/zod.factories.duration.md +4 -4
- package/dist/knowledge/references/zod.factories.money.md +4 -4
- package/dist/knowledge/references/zod.factories.phone.md +4 -4
- package/dist/knowledge/references/zod.factories.year-month.md +79 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +415 -2
- package/dist/knowledge/registries/playbooks.json +51 -39
- package/dist/knowledge/registries/source-tags.json +2412 -1604
- package/dist/knowledge/rules/database-migration-obligation.md +6 -7
- package/dist/knowledge/rules/live-context-door.md +1 -1
- package/dist/knowledge/skills/INDEX.md +3 -1
- package/dist/knowledge/skills/agent-work-review/references/framework-actor-execution-continuation-api.md +24 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +1 -1
- package/dist/knowledge/skills/agent-work-review/references/framework-human-input-form-api.md +47 -12
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +30 -19
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +48 -13
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +2 -2
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -11
- package/dist/knowledge/skills/application-database-migrations/references/postgresql-supported-surfaces.md +64 -0
- package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +13 -11
- package/dist/knowledge/skills/application-roles-authoring/SKILL.md +28 -3
- package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +18 -1
- package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +22 -1
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +46 -2
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-assigned-rows-declaration-api.md +5 -3
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-organization-identity-declaration-api.md +247 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-own-rows-declaration-api.md +12 -5
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +6 -0
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +31 -2
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +51 -14
- package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +4 -1
- package/dist/knowledge/skills/backend-custom-operation/references/declared-refusal-codes.md +95 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +2 -2
- package/dist/knowledge/skills/backend-custom-operation/references/framework-core-write-precondition-api.md +73 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-error-handling-api.md +5 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-external-effect-reservation-api.md +276 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-hook-transaction-posture-api.md +79 -0
- package/dist/knowledge/skills/blueprint-authoring/SKILL.md +4 -2
- package/dist/knowledge/skills/brand-name-screening/SKILL.md +13 -2
- package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +30 -3
- package/dist/knowledge/skills/chat-agent-conversations/SKILL.md +3 -0
- package/dist/knowledge/skills/chat-agent-conversations/references/framework-chat-conversations-api.md +13 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +45 -4
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +17 -7
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +859 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +6 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +2 -0
- package/dist/knowledge/skills/config-app-shell/SKILL.md +5 -1
- package/dist/knowledge/skills/config-app-shell/references/framework-command-menu-omnibox-api.md +3 -3
- package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +4 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +1 -1
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +8 -7
- package/dist/knowledge/skills/config-design-system/references/framework-theme-composition-api.md +44 -1
- package/dist/knowledge/skills/config-navigation/SKILL.md +2 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +5 -0
- package/dist/knowledge/skills/config-navigation/references/one-entry-per-concept.md +101 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +2 -2
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +40 -3
- package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +20 -1
- package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +75 -11
- package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +21 -19
- package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +26 -9
- package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +197 -9
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +16 -2
- package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +116 -16
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +20 -18
- package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +1 -1
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +11 -1
- package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +5 -1
- package/dist/knowledge/skills/config-saas-backend/references/framework-declared-type-renames-api.md +261 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +20 -0
- package/dist/knowledge/skills/config-saas-backend/references/renaming-organization-and-user-types.md +69 -0
- package/dist/knowledge/skills/configure-billing/SKILL.md +6 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +28 -4
- package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +2 -0
- package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +4 -1
- package/dist/knowledge/skills/electronic-signature-deliverables/SKILL.md +131 -0
- package/dist/knowledge/skills/electronic-signature-deliverables/references/what-makes-a-request-signed.md +61 -0
- package/dist/knowledge/skills/email-add-template/SKILL.md +1 -1
- package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +11 -8
- package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +3 -2
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +31 -9
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +11 -4
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +26 -3
- package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +1 -1
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +27 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +18 -7
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +8 -5
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-behavior-reports-api.md +13 -9
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +44 -4
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-operation-record-api.md +7 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-suspension-api.md +11 -9
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +21 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +3 -3
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-realtime-catalog.md +7 -1
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +375 -8
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +30 -1
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-model-spend-limits-api.md +36 -15
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +8 -0
- package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +1 -1
- package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-flow-model-api.md +21 -2
- package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +2 -1
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +1 -1
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +33 -1
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +5 -3
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +3 -3
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +37 -14
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +1 -1
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +31 -2
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-translation-glossary-api.md +87 -0
- package/dist/knowledge/skills/inbound-channels/SKILL.md +31 -9
- package/dist/knowledge/skills/inbound-channels/references/email-channel.md +16 -4
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +169 -23
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +38 -1
- package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +43 -4
- package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +15 -3
- package/dist/knowledge/skills/inbound-channels/references/sms-channel.md +93 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +125 -77
- package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +12 -14
- package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +133 -8
- package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +0 -1
- package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +84 -8
- package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-authoring-api.md +1 -1
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-focal-plane-settings-api.md +16 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +72 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +2 -2
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +12 -9
- package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +3 -3
- package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +2 -2
- package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +18 -10
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +7 -7
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +24 -2
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +33 -2
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +47 -6
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +61 -8
- package/dist/knowledge/skills/model-cost-attribution/SKILL.md +3 -1
- package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +1 -1
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +107 -42
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +21 -2
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +30 -1
- package/dist/knowledge/skills/module-relationships/SKILL.md +92 -91
- package/dist/knowledge/skills/organization-relationships/references/framework-organization-relationships-api.md +31 -5
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-grantor-authentication-api.md +2 -2
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-kinds-api.md +34 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-record-separation-api.md +1 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-representative-activity-api.md +4 -0
- package/dist/knowledge/skills/professional-qualifications/references/framework-operation-approval-requirement-api.md +31 -0
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +255 -12
- package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +4 -5
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-compliance-state-collector-api.md +96 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-configuration-check-api.md +130 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +8 -1
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-inbound-endpoint-api.md +124 -3
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +165 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +6 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-processing-region-api.md +340 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +11 -6
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +2 -0
- package/dist/knowledge/skills/provider-frontend-module/SKILL.md +5 -2
- package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +1 -1
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +17 -3
- package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +1035 -19
- package/dist/knowledge/skills/resource-add-field/SKILL.md +7 -0
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +322 -15
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +9 -5
- package/dist/knowledge/skills/resource-add-resource/references/framework-engine-api-reference-categories-api.md +119 -0
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +107 -42
- package/dist/knowledge/skills/resource-chat-commands/SKILL.md +2 -1
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +71 -5
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +2 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-approval-api.md +48 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +33 -7
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-bulk-api.md +15 -11
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +66 -27
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +140 -58
- package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +7 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +34 -10
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +5 -4
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +158 -138
- package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +52 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +205 -19
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +253 -25
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +126 -1
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +259 -15
- package/dist/knowledge/skills/resource-custom-view/references/framework-backend-refusal-api.md +110 -0
- package/dist/knowledge/skills/resource-external-data/SKILL.md +46 -12
- package/dist/knowledge/skills/resource-external-data/references/bidirectional-pipelines.md +1 -1
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +15 -8
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +19 -8
- package/dist/knowledge/skills/resource-external-data/references/framework-system-of-record-capabilities-api.md +3 -1
- package/dist/knowledge/skills/resource-external-data/references/local-test-doubles.md +121 -0
- package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +1 -1
- package/dist/knowledge/skills/resource-external-data/references/partition-from-the-domain-plan.md +230 -0
- package/dist/knowledge/skills/resource-external-data/references/presenting-a-copy-and-a-read-through.md +73 -0
- package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +26 -5
- package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +76 -6
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +8 -0
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +12 -9
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +11 -2
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +29 -2
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +20 -20
- package/dist/knowledge/skills/resource-retention-binding/SKILL.md +18 -2
- package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +46 -2
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +84 -1
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +10 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +5 -3
- package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +21 -0
- package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +14 -2
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +1 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +4 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +78 -17
- package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +2 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +26 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +46 -46
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +17 -2
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +36 -24
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +63 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +104 -23
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +123 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +72 -0
- package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +42 -2
- package/dist/knowledge/skills/resource-status-lifecycle/references/framework-operation-condition-parameters-api.md +67 -0
- package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +16 -12
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +66 -3
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +89 -10
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +11 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +263 -17
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-record-page-parts-api.md +155 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +83 -16
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +44 -10
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-section-stages-api.md +102 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/record-page-anatomy.md +9 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +33 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/visual-quality-rubric.md +19 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/workflow-record-page.md +264 -0
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +24 -4
- package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +12 -0
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +7 -6
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +6 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +42 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +6 -9
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +21 -2
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +26 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +121 -75
- package/dist/knowledge/skills/spec-resource-update/references/workflow-record-page-specification.md +237 -0
- package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +100 -71
- package/dist/knowledge/skills/subject-data-export/SKILL.md +176 -0
- package/dist/knowledge/skills/subject-data-export/references/file-content-exclusions.md +15 -0
- package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-api.md +142 -0
- package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-archive-api.md +33 -0
- package/dist/knowledge/skills/views-app-level/SKILL.md +3 -1
- package/dist/knowledge/skills/views-app-level/references/workflow-home.md +373 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +36 -5
- package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +9 -5
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +4 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-chart-dashboard-api.md +244 -0
- package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +40 -0
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +8 -6
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +70 -59
- package/dist/knowledge/skills/website-building-blocks/SKILL.md +1 -1
- package/dist/knowledge/skills/website-building-blocks/references/framework-website-demo-examples.md +3 -3
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +4 -2
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +3 -1
- package/dist/knowledge/skills/website-label-pack/SKILL.md +20 -5
- package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +6 -3
- package/dist/knowledge/skills/website-section-comparison/SKILL.md +2 -2
- package/dist/knowledge/skills/website-section-contact/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-cta/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-faq/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-hero/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-how-it-works/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-integrations/SKILL.md +3 -3
- package/dist/knowledge/skills/website-section-latest-posts/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +142 -98
- package/dist/knowledge/skills/website-section-pricing/examples/pricing-offers.example.md +178 -66
- package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +3 -1
- package/dist/knowledge/skills/website-section-problem/SKILL.md +3 -3
- package/dist/knowledge/skills/website-section-product-showcase/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-roadmap/SKILL.md +4 -4
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-solution-paths/SKILL.md +2 -2
- package/dist/knowledge/skills/website-section-stats/SKILL.md +3 -3
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +3 -2
- package/dist/knowledge/skills/worker-authoring/SKILL.md +4 -2
- package/dist/knowledge/topic-index.json +2275 -715
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/package.json +6 -6
- package/dist/tsconfig.tsbuildinfo +0 -1
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.brand-name-screening-produce",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.3.0",
|
|
4
4
|
"phase": "top_down",
|
|
5
5
|
"intent": "Derive the validated brand-name screening from the vision, the market snapshot and the evidence a sibling research step gathered: the jurisdictions and Nice classes searched, and per candidate its origin, why it fits, every register query with its result, conflicting marks, source and date, the competitor collisions, and the domain and same-category signals. Transcribes, never concludes: a candidate's standing is derived from its queries. A minimal trademark screening, never a legal clearance opinion.",
|
|
6
6
|
"preconditions": [
|
|
@@ -41,13 +41,14 @@
|
|
|
41
41
|
],
|
|
42
42
|
"stepOutputs": [],
|
|
43
43
|
"method": {
|
|
44
|
-
"guidance": "# Brand Name Screening — land what the research found\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\nYou turn the evidence a sibling research step gathered into the validated\n**`BrandNameScreening`** — the `brand-name-screening` family. The creator chooses the\nbrand name from what you land, so the record must say exactly what was checked and\nwhat each register returned, and nothing more.\n\nYou are a **transcriber, not a judge.** There is no field for \"this name is clear\":\na candidate's standing is computed from its register queries. Your job is to record\nevery query faithfully.\n\n## Where your inputs are\n\n- The research brief is in your brief under \"Evidence gathered for this run\".\n- The vision and the market snapshot are in your brief as input sections.\n- A screening already on record, if any, is in your brief too. Keep its candidates and\n their slugs, and re-record them with the new evidence. A re-run adds to the list; it\n does not forget it.\n- The creator's own names are in the interview answers of `top_down.brand-naming`\n (`names-to-screen`). Every one of them is a candidate with origin `CREATOR_SUPPLIED`.\n\n## What you emit\n\n- `screenedOn` — today's date.\n- `jurisdictions` — the UNION of what the vision, the market snapshot, the application's declared\n operating jurisdictions (the declared `operating_jurisdictions` context section of your brief) and the creator's own\n `target-jurisdictions` answer (in the interview answers of `top_down.brand-naming`) target:\n `EU` for the EU trade mark, `WO` for international registrations, ISO country codes otherwise,\n each with what declared it. Every country the creator names is a jurisdiction even when the\n research did not search it: an unsearched target is recorded, and reads as not cleared, rather\n than silently dropped. Where data is hosted is not a trademark jurisdiction.\n- `niceClasses` — each class searched, with why this product lives in it.\n- `candidates` — one per name, with a kebab-case `slug`, the exact `name`, its `origin`,\n a one-line `rationale` for proposals, and:\n - `trademarkQueries` — one per register search the evidence reports: register,\n `accessPath` (`MACHINE_INTERFACE` when
|
|
44
|
+
"guidance": "# Brand Name Screening — land what the research found\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\nYou turn the evidence a sibling research step gathered into the validated\n**`BrandNameScreening`** — the `brand-name-screening` family. The creator chooses the\nbrand name from what you land, so the record must say exactly what was checked and\nwhat each register returned, and nothing more.\n\nYou are a **transcriber, not a judge.** There is no field for \"this name is clear\":\na candidate's standing is computed from its register queries. Your job is to record\nevery query faithfully.\n\n## Where your inputs are\n\n- The research brief is in your brief under \"Evidence gathered for this run\".\n- The vision and the market snapshot are in your brief as input sections.\n- A screening already on record, if any, is in your brief too. Keep its candidates and\n their slugs, and re-record them with the new evidence. A re-run adds to the list; it\n does not forget it.\n- The creator's own names are in the interview answers of `top_down.brand-naming`\n (`names-to-screen`). Every one of them is a candidate with origin `CREATOR_SUPPLIED`.\n\n## What you emit\n\n- `screenedOn` — today's date.\n- `jurisdictions` — the UNION of what the vision, the market snapshot, the application's declared\n operating jurisdictions (the declared `operating_jurisdictions` context section of your brief) and the creator's own\n `target-jurisdictions` answer (in the interview answers of `top_down.brand-naming`) target:\n `EU` for the EU trade mark, `WO` for international registrations, ISO country codes otherwise,\n each with what declared it. Every country the creator names is a jurisdiction even when the\n research did not search it: an unsearched target is recorded, and reads as not cleared, rather\n than silently dropped. Where data is hosted is not a trademark jurisdiction. When the creator left\n `target-jurisdictions` NOT DECIDED YET and no other source names a place, emit `jurisdictions: []`:\n never invent a target. The screening still records every search the evidence reports (`WO` is always\n searched), is marked as having no target, and clears no name until one is declared.\n- `niceClasses` — each class searched, with why this product lives in it.\n- `candidates` — one per name, with a kebab-case `slug`, the exact `name`, its `origin`,\n a one-line `rationale` for proposals, and:\n - `trademarkQueries` — one per register search the evidence reports FOR THIS NAME: register,\n `searchedName` (the term the search actually ran with), `accessPath` (`MACHINE_INTERFACE` when\n the register's published interface answered, `WEB_PAGE` when its web page was fetched),\n jurisdictions covered, classes and match types searched, outcome, conflicting marks, source URL,\n date, and a note for anything a reader needs. A TMview search covers every office it included:\n list each of those countries.\n - `competitorCollisions` — any market competitor or alternative the name is identical\n or close to, AND any product the evidence found doing the same job under an identical or\n near-identical name.\n - `sameCategoryUses` — every company or product trading under the name, each with its\n `categoryRelation`: `SAME_JOB` (the same work for the same kind of customer, or the same Nice\n class), `ADJACENT`, or `UNRELATED`.\n - `domainSignals` — as the evidence reports them.\n\n## The rules that keep it true\n\n- **A register the evidence could not query or read is `UNKNOWN`, with a note saying\n why.** Never `CLEAR`. Never omit it either: an unrecorded register is an uncovered\n jurisdiction, and the candidate reads as not cleared anyway.\n- **A search is recorded only for the name it was run with.** When the research tried a register\n once, for one name, and stopped because the register failed, the other candidates were NOT\n searched there: record each of them as `NOT_SEARCHED`, with `searchedName` and `sourceUrl`\n citing the attempt that was made and a note saying so. Never copy one name's search onto\n another as if it had been run: a query whose `searchedName` or source URL is another\n candidate's is refused at landing.\n- **`CONFLICT` exactly when the query found a live identical or near-identical mark**,\n and then every such mark is listed with its source. A conflict with no mark, or a\n mark beside a `CLEAR`, is refused at landing.\n- **Only what the evidence says.** No mark, URL, date or result from memory. A claim\n without a source in the evidence is left out and named in a query note.\n- **A same-job product with an identical or near-identical name is a collision.** Record it in\n `competitorCollisions` and also, with `categoryRelation: SAME_JOB`, in `sameCategoryUses`.\n Filing it only as a same-category use with no relation is how a creator once chose a name\n without being told a quote-to-invoice suite for tradespeople already traded under it. The\n choice computation treats a `SAME_JOB` use of a colliding name as a collision anyway, but the\n relation is what lets it decide: state it for every use.\n- **Unread registers need no link from you.** Each `UNKNOWN` query becomes a check the creator\n can run by hand, with a search link the companion builds from the query; never invent a URL.\n- **Keep conflicting proposals on record.** A proposal that conflicts is never offered\n to the creator, and the record of why it was dropped is still worth keeping.\n- **Never write \"available\", \"free to use\" or \"cleared\".** This is a minimal trademark\n screening, not a legal clearance opinion.\n\nFollow the `brand-name-screening` skill for the field contracts. Its full text is in\nyour brief under \"The skills this method tells you to FOLLOW\". Read it there; you cannot\nopen files.\n\n## Quality gate\n\nThe deterministic `validateBrandNameScreening` runs before anything lands. It refuses a\ncontradictory record and REPORTS the rest for the creator's review: an incomplete\nscreening, a screening that read no register at all, a conflicting proposal kept for the\nrecord, fewer than three offerable proposals, a missing EU trade mark for an EU target, or a\nmissing class 9 or 42. Let\nthose findings stand honestly rather than inventing results to silence them.\n\nAfter landing, an advisory judge reads the screening for coverage and honesty, and checks\nthat the proposals are grounded and distinct from the competitors. A screening that read no\nregister for any candidate is its worst verdict: honest, and still a screening of nothing. Its verdict is a note\nfor the creator's review.\n",
|
|
45
45
|
"skillRefs": [
|
|
46
46
|
"brand-name-screening"
|
|
47
47
|
],
|
|
48
48
|
"skillBodyRefs": [
|
|
49
49
|
"brand-name-screening"
|
|
50
50
|
],
|
|
51
|
+
"derivedFromAnswers": [],
|
|
51
52
|
"contextSources": [
|
|
52
53
|
"operating_jurisdictions"
|
|
53
54
|
],
|
|
@@ -50,10 +50,14 @@
|
|
|
50
50
|
"questionRef": "jurisdictions"
|
|
51
51
|
},
|
|
52
52
|
"depth": "essential",
|
|
53
|
-
"regulatedDomain": true
|
|
53
|
+
"regulatedDomain": true,
|
|
54
|
+
"nonAnswers": [
|
|
55
|
+
"deferred"
|
|
56
|
+
]
|
|
54
57
|
}
|
|
55
58
|
]
|
|
56
59
|
},
|
|
60
|
+
"derivedFromAnswers": [],
|
|
57
61
|
"contextSources": [],
|
|
58
62
|
"draftableDocumentDefinitionRefs": [],
|
|
59
63
|
"choreography": {
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"aggregationPolicyRef":"application-creation:aggregation/worst-business-model-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/business-model-grounding-and-plan-coherence","criterionVersion":
|
|
1
|
+
{"aggregationPolicyRef":"application-creation:aggregation/worst-business-model-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/business-model-grounding-and-plan-coherence","criterionVersion":3,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/business-model-grounding-and-plan-coherence","requirementVersion":1}],"instruction":"Assess whether the business model is GROUNDED in what the creator actually stated and coherent with the accepted market and requirements truth. Read each pricing answer WITH its standing: a DECIDED answer is the creator's; an ASSUMED answer was proposed for the creator and never stated by them. First check that `pricingTiers` matches the pricing-tiers answer and its standing: \"creator_stated\" when a DECIDED answer named tiers, \"proposed\" when a DECIDED answer asked for tiers to be proposed, \"assumed\" when the answer is ASSUMED and names tiers or a proposal, \"undecided\" when the answer (decided or assumed) says the tiers are not decided and asks for no proposal. Then, per status: a \"creator_stated\" plan must trace to a tier the creator named; a \"proposed\" plan is legitimate BECAUSE the creator asked for it; an \"assumed\" plan is a hypothesis marked as one, and that marking is correct provenance, never drift; a \"proposed\" or \"assumed\" plan must carry a `proposalBasis` that names an ICP present in the market snapshot and requirements present in the requirements snapshot (and, for an assumed one, what the assumption rested on); an \"undecided\" sketch has no plans, and that is a complete, honest artifact. Across every status: every targeted ICP and unlocked requirement must exist, the revenue model must be consistent with the plans (an empty undecided sketch is consistent with any revenue model), and no plan may carry a price or scaling axis that a DECIDED answer did not give — not a proposed one, and not one an ASSUMED price-points or scaling answer suggested, since an assumed price is nobody's decision. Treat as a GAP: an invented price or scaling axis, or a price taken from an ASSUMED answer; a creator-stated plan the creator never named; a status that contradicts the interview or its standing (for example \"creator_stated\" when the tiers answer is ASSUMED — presenting an assumption as the creator's statement — \"assumed\" when the creator decided it, \"undecided\" when tiers were named, or plans present when the answer neither named nor asked for them); a proposed or assumed plan with no basis; a free tier or revenue model taken only from an ASSUMED answer and presented as the creator's own decision. This family exists to carry the creator's commercial intent, not the evaluator's.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The model is faithful to the interview but a cross-link or a proposal basis is weaker than the accepted truth supports. An undecided answer the creator chose is NOT a concern — it is the honest artifact, and neither is an assumed sketch marked as assumed.","GAP":"A price, scaling axis or stated tier appears that a decided answer did not give; the tiers status contradicts the interview or its standing (an assumed answer presented as creator_stated); a proposed or assumed plan has no basis; or a cross-link names an ICP or requirement that does not exist.","INDETERMINATE":"The interview answers or the accepted market/requirements evidence are absent, stale or insufficient.","PASS":"The tiers status matches the interview and each answer's standing; every stated plan traces to what the creator named, every proposed or assumed plan carries a basis in the accepted market and requirements truth, an undecided sketch carries no plans, no price or scaling axis is invented or taken from an assumed answer, and every cross-link resolves."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/business-model","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.business-model"},"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/accept-business-model-lite-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/business-model-grounding-and-plan-coherence"],"requirementRef":"application-creation:authority-requirement/business-model-result","requirementVersion":1,"riskClassRef":"application-creation:risk/business-model-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/business-model","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/business-model-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/business-model","policyVersion":1},"decisionPointRef":"application-creation:decision-point/business-model-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/business-model-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/business-model","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/business-model-grounding-and-plan-coherence","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/business-model-lite-snapshot-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-business-model-change","triggerRefs":["application-creation:trigger/business-model-lite-snapshot-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-business-model-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/business-model-grounding-and-plan-coherence"],"hardFloorRef":"application-creation:hard-floor/business-model-lite-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/business-model-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/business-model","definitionVersion":
|
|
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-business-model-lite-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/business-model-grounding-and-plan-coherence"],"requirementRef":"application-creation:authority-requirement/business-model-result","requirementVersion":1,"riskClassRef":"application-creation:risk/business-model-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/business-model","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/business-model-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/business-model","policyVersion":1},"decisionPointRef":"application-creation:decision-point/business-model-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/business-model-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/business-model","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/business-model-grounding-and-plan-coherence","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/business-model-lite-snapshot-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-business-model-change","triggerRefs":["application-creation:trigger/business-model-lite-snapshot-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-business-model-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/business-model-grounding-and-plan-coherence"],"hardFloorRef":"application-creation:hard-floor/business-model-lite-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/business-model-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/business-model","definitionVersion":3,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-business-model-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/business-model-grounding-and-plan-coherence","criterionVersion":3,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/business-model-grounding-and-plan-coherence","requirementVersion":1}],"instruction":"Assess whether the business model is GROUNDED in what the creator actually stated and coherent with the accepted market and requirements truth. Read each pricing answer WITH its standing: a DECIDED answer is the creator's; an ASSUMED answer was proposed for the creator and never stated by them. First check that `pricingTiers` matches the pricing-tiers answer and its standing: \"creator_stated\" when a DECIDED answer named tiers, \"proposed\" when a DECIDED answer asked for tiers to be proposed, \"assumed\" when the answer is ASSUMED and names tiers or a proposal, \"undecided\" when the answer (decided or assumed) says the tiers are not decided and asks for no proposal. Then, per status: a \"creator_stated\" plan must trace to a tier the creator named; a \"proposed\" plan is legitimate BECAUSE the creator asked for it; an \"assumed\" plan is a hypothesis marked as one, and that marking is correct provenance, never drift; a \"proposed\" or \"assumed\" plan must carry a `proposalBasis` that names an ICP present in the market snapshot and requirements present in the requirements snapshot (and, for an assumed one, what the assumption rested on); an \"undecided\" sketch has no plans, and that is a complete, honest artifact. Across every status: every targeted ICP and unlocked requirement must exist, the revenue model must be consistent with the plans (an empty undecided sketch is consistent with any revenue model), and no plan may carry a price or scaling axis that a DECIDED answer did not give — not a proposed one, and not one an ASSUMED price-points or scaling answer suggested, since an assumed price is nobody's decision. Treat as a GAP: an invented price or scaling axis, or a price taken from an ASSUMED answer; a creator-stated plan the creator never named; a status that contradicts the interview or its standing (for example \"creator_stated\" when the tiers answer is ASSUMED — presenting an assumption as the creator's statement — \"assumed\" when the creator decided it, \"undecided\" when tiers were named, or plans present when the answer neither named nor asked for them); a proposed or assumed plan with no basis; a free tier or revenue model taken only from an ASSUMED answer and presented as the creator's own decision. This family exists to carry the creator's commercial intent, not the evaluator's.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The model is faithful to the interview but a cross-link or a proposal basis is weaker than the accepted truth supports. An undecided answer the creator chose is NOT a concern — it is the honest artifact, and neither is an assumed sketch marked as assumed.","GAP":"A price, scaling axis or stated tier appears that a decided answer did not give; the tiers status contradicts the interview or its standing (an assumed answer presented as creator_stated); a proposed or assumed plan has no basis; or a cross-link names an ICP or requirement that does not exist.","INDETERMINATE":"The interview answers or the accepted market/requirements evidence are absent, stale or insufficient.","PASS":"The tiers status matches the interview and each answer's standing; every stated plan traces to what the creator named, every proposed or assumed plan carries a basis in the accepted market and requirements truth, an undecided sketch carries no plans, no price or scaling axis is invented or taken from an assumed answer, and every cross-link resolves."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/business-model","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.business-model"},"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/business-model","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-business-model-inputs-and-candidate","criterionRef":"application-creation:criterion/business-model-grounding-and-plan-coherence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":5,"minCount":4,"requirementRef":"application-creation:evidence-requirement/business-model-grounding-and-plan-coherence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-vision-and-business-model-candidate"}],"schemaVersion":1}
|
|
@@ -61,14 +61,20 @@ Concretely:
|
|
|
61
61
|
|
|
62
62
|
## Where the tiers came from: `pricingTiers`
|
|
63
63
|
|
|
64
|
-
The tiers answer has exactly
|
|
64
|
+
The tiers answer has exactly four honest readings, and you record which one it
|
|
65
65
|
was. This status is what lets an empty sketch be an answer instead of a gap.
|
|
66
66
|
|
|
67
|
-
|
|
67
|
+
Read the answer's **standing** first. An answer marked ASSUMED was proposed for
|
|
68
|
+
the creator (a quick interview, or a creator who did not know) and they never
|
|
69
|
+
stated it. It is still the input you build on, but it is not the creator's word,
|
|
70
|
+
so a tier it names is not `creator_stated`.
|
|
71
|
+
|
|
72
|
+
| The tiers answer | `pricingTiers` | `plans` |
|
|
68
73
|
|---|---|---|
|
|
69
|
-
| named one or more tiers ("one tier" counts) | `creator_stated` | exactly the tiers they named, `proposalBasis: null` on each |
|
|
70
|
-
| asked for tiers to be proposed ("propose them", "derive them from the market research") | `proposed` | your proposal, each plan with a `proposalBasis` |
|
|
71
|
-
|
|
|
74
|
+
| the creator named one or more tiers ("one tier" counts) | `creator_stated` | exactly the tiers they named, `proposalBasis: null` on each |
|
|
75
|
+
| the creator asked for tiers to be proposed ("propose them", "derive them from the market research") | `proposed` | your proposal, each plan with a `proposalBasis` |
|
|
76
|
+
| is ASSUMED, and names tiers or asks for a proposal | `assumed` | the tiers it names (or your proposal), each plan with a `proposalBasis` saying what the assumption rested on |
|
|
77
|
+
| says the tiers are not decided, and asks for no proposal (assumed or not) | `undecided` | **empty** |
|
|
72
78
|
|
|
73
79
|
A creator who says "not decided — let the plan propose them" has asked for a
|
|
74
80
|
proposal: that is `proposed`, not `undecided`. Read the whole answer, not its
|
|
@@ -105,6 +111,23 @@ invention. Derive them from what the inputs hold:
|
|
|
105
111
|
The creator accepts or revises the proposal at the approval step; you do not
|
|
106
112
|
need to be cautious on their behalf by proposing nothing.
|
|
107
113
|
|
|
114
|
+
### An assumed sketch is a hypothesis, and says so
|
|
115
|
+
|
|
116
|
+
`assumed` is the honest status when the tiers answer was assumed: the run goes
|
|
117
|
+
ahead on it, and the artifact marks it so nobody downstream reads it as the
|
|
118
|
+
creator's decision. Never write `creator_stated` for an assumed answer; a judge
|
|
119
|
+
reads that as presenting an assumption as the creator's statement. Never write
|
|
120
|
+
`proposed` either: the creator did not ask for a proposal.
|
|
121
|
+
|
|
122
|
+
**An assumed price is not a price.** When the price-points or scaling-axis answer
|
|
123
|
+
is ASSUMED, leave `pricePoint`, `billingPeriod` and `pricingModel` `null`, exactly
|
|
124
|
+
as for an undecided answer. A tier with no price is a real plan; a price nobody
|
|
125
|
+
decided would reach the billing catalogue as if someone had.
|
|
126
|
+
|
|
127
|
+
The same holds for the other answers: a free tier or revenue model the creator
|
|
128
|
+
never stated, because its answer was ASSUMED, is built on but never described as
|
|
129
|
+
the creator's decision.
|
|
130
|
+
|
|
108
131
|
## What you DO derive
|
|
109
132
|
|
|
110
133
|
Two things, and both are cross-links rather than content:
|
|
@@ -158,7 +181,7 @@ One output, the `business-model` family. The contract is strict:
|
|
|
158
181
|
the nearest and explain the mismatch in the plans' prose — do not stretch a
|
|
159
182
|
member past its meaning.
|
|
160
183
|
- **`pricingTiers` is required**, and it decides how many plans there are (see
|
|
161
|
-
the table above). `creator_stated` and `
|
|
184
|
+
the table above). `creator_stated`, `proposed` and `assumed` carry at least one plan;
|
|
162
185
|
`undecided` carries none. If the creator sells exactly one thing, that is one
|
|
163
186
|
`creator_stated` plan, fully described.
|
|
164
187
|
- **`slug`, not `ref`.** You author a kebab-case slug per plan; the trusted
|
|
@@ -169,14 +192,16 @@ One output, the `business-model` family. The contract is strict:
|
|
|
169
192
|
|
|
170
193
|
## Verification before you answer
|
|
171
194
|
|
|
172
|
-
- [ ] `pricingTiers` is the reading of the tiers answer
|
|
173
|
-
|
|
174
|
-
|
|
195
|
+
- [ ] `pricingTiers` is the reading of the tiers answer and its standing from
|
|
196
|
+
the table above — `assumed`, never `creator_stated`, for an ASSUMED answer.
|
|
197
|
+
- [ ] Every `pricePoint` and `pricingModel` traces to a DECIDED answer — on a
|
|
198
|
+
proposed or assumed plan too; an ASSUMED price-points answer sets none.
|
|
175
199
|
- [ ] Every `per_usage` plan names its `usageUnit`, and no other plan names one.
|
|
176
200
|
- [ ] Every `creator_stated` plan traces to a tier they described. No tier count
|
|
177
201
|
was rounded up.
|
|
178
|
-
- [ ] Every `proposed` plan carries a `proposalBasis` naming an ICP
|
|
179
|
-
requirements that separate it; every `creator_stated` plan carries
|
|
202
|
+
- [ ] Every `proposed` or `assumed` plan carries a `proposalBasis` naming an ICP
|
|
203
|
+
and the requirements that separate it; every `creator_stated` plan carries
|
|
204
|
+
none.
|
|
180
205
|
- [ ] An `undecided` sketch has no plans, and no placeholder was added.
|
|
181
206
|
- [ ] Every `targetIcpRefs` entry exists in the market snapshot.
|
|
182
207
|
- [ ] Every `includesRequirementRefs` entry exists in the requirements snapshot.
|
|
@@ -186,3 +211,10 @@ One output, the `business-model` family. The contract is strict:
|
|
|
186
211
|
purchase, is incoherent. An `undecided` sketch with no plans is coherent
|
|
187
212
|
with any revenue model.
|
|
188
213
|
- [ ] Nothing in the artifact answers a question the creator left open.
|
|
214
|
+
|
|
215
|
+
## Refine, don't re-author
|
|
216
|
+
|
|
217
|
+
When a business model is already on record, it is an input of this run: refine it. Keep every ref that still names
|
|
218
|
+
the same thing, because other artifacts and committed work name it: the build plan's billing products name each pricing plan. Mint a new ref only for something
|
|
219
|
+
that did not exist before, and drop one only when its subject is gone. A reworded entry under a new ref reads
|
|
220
|
+
everywhere downstream as one thing removed and another added (#3449).
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.business-model",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.3.0",
|
|
4
4
|
"phase": "top_down",
|
|
5
|
-
"intent": "Turn the accepted market and requirements truth, plus the creator's own pricing intent, into a non-vacuous BusinessModelLiteSnapshot: the product-level revenue model, where its pricing tiers came from (stated by the creator, proposed at the creator's request, or not decided yet), and a sketch of pricing plans, each cross-linked to the market ICPs it is sold to and the requirements it unlocks. A PLANNING artifact carrying commercial INTENT — never the billing runtime, and never a price the creator did not state.",
|
|
5
|
+
"intent": "Turn the accepted market and requirements truth, plus the creator's own pricing intent, into a non-vacuous BusinessModelLiteSnapshot: the product-level revenue model, where its pricing tiers came from (stated by the creator, proposed at the creator's request, taken from an answer assumed for the creator, or not decided yet), and a sketch of pricing plans, each cross-linked to the market ICPs it is sold to and the requirements it unlocks. A PLANNING artifact carrying commercial INTENT — never the billing runtime, and never a price the creator did not state.",
|
|
6
6
|
"preconditions": [
|
|
7
7
|
{
|
|
8
8
|
"kind": "artifact_valid",
|
|
@@ -33,18 +33,21 @@
|
|
|
33
33
|
},
|
|
34
34
|
{
|
|
35
35
|
"family": "vision-brief"
|
|
36
|
+
},
|
|
37
|
+
{
|
|
38
|
+
"family": "business-model"
|
|
36
39
|
}
|
|
37
40
|
],
|
|
38
41
|
"outputs": [
|
|
39
42
|
{
|
|
40
43
|
"family": "business-model",
|
|
41
44
|
"schemaRef": "saas-specifications:BusinessModelLiteSnapshot",
|
|
42
|
-
"description": "A validated revenue-model classification, the status of the pricing tiers (creator-stated, proposed for the creator's review, or undecided), and the pricing plans that status implies — none when undecided — each cross-linked to the market ICPs it targets and the requirements it unlocks."
|
|
45
|
+
"description": "A validated revenue-model classification, the status of the pricing tiers (creator-stated, proposed for the creator's review, assumed on the creator's behalf, or undecided), and the pricing plans that status implies — none when undecided — each cross-linked to the market ICPs it targets and the requirements it unlocks."
|
|
43
46
|
}
|
|
44
47
|
],
|
|
45
48
|
"stepOutputs": [],
|
|
46
49
|
"method": {
|
|
47
|
-
"guidance": "# Business Model — Commercial Intent 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.** Pricing sketch depth only — no unit\n> economics, no cohort modelling, no competitive price positioning. Those are a\n> later phase; do not perfect them here.\n\n## What this playbook does\n\nYou are recording the product's **commercial intent**: how it makes money, and\nwhat it sells. The output is one `BusinessModelLiteSnapshot` — a revenue-model\nclassification plus a sketch of pricing plans, each cross-linked to the market\nsegments it is sold to and the requirements it unlocks.\n\nIt is a **PLANNING artifact**, in exactly the sense the vision and the roadmap\nare. It is not the billing runtime, not a Stripe catalogue, and not a price list\nanyone is held to. Nothing reads it to charge a customer.\n\n## The one rule that governs everything below\n\n**You do not decide how this product charges. The creator does.**\n\nEvery other top-down family is DERIVED — the market snapshot follows from the\nvision, requirements follow from both, the roadmap follows from the capability\nmap. This one is not, and the difference is not a matter of degree. The same\nproduct is a fair freemium tool, a per-seat B2B subscription, or a\nusage-metered API, and **nothing in the vision, the market or the requirements\ndecides which**. It is a business decision, and only the creator holds it.\n\nSo this playbook interviews. Your job is to take what the creator said and make\nit *structured and cross-linked* — never to fill a gap they left.\n\nConcretely:\n\n- **Never invent a price.** If the creator said \"not decided yet\", omit\n `pricePoint`. A tier with no price is a real, useful plan; a tier with a price\n nobody chose is a fabrication that then propagates — the foundation playbook\n derives the billing capability from this artifact.\n- **Never invent a tier.** Three tiers is the industry default and that is\n exactly why it is a trap. If they described one, produce one.\n- **Never invent a scaling axis.** If they did not say what the price scales\n with, omit `pricingModel` rather than guessing `per_seat`.\n- **A price per usage names its unit.** When a plan's `pricingModel` is\n `per_usage`, `usageUnit` is what ONE unit counts, singular and in the\n creator's words: \"API call\", \"export\", \"close\". A firm that bills each case\n (\"we charge per monthly close\", \"a fixed fee per audit\") is pricing per usage,\n and its unit is the case. Every other plan has `usageUnit: null`.\n- **\"Not decided yet\" is an answer.** Record what they *did* decide and leave\n the rest absent. Absence is legible; an invention is not.\n\n## Where the tiers came from: `pricingTiers`\n\nThe tiers answer has exactly three honest readings, and you record which one it\nwas. This status is what lets an empty sketch be an answer instead of a gap.\n\n| The creator said | `pricingTiers` | `plans` |\n|---|---|---|\n| named one or more tiers (\"one tier\" counts) | `creator_stated` | exactly the tiers they named, `proposalBasis: null` on each |\n| asked for tiers to be proposed (\"propose them\", \"derive them from the market research\") | `proposed` | your proposal, each plan with a `proposalBasis` |\n| the tiers are not decided, and asked for no proposal | `undecided` | **empty** |\n\nA creator who says \"not decided — let the plan propose them\" has asked for a\nproposal: that is `proposed`, not `undecided`. Read the whole answer, not its\nfirst words.\n\n### An undecided sketch is complete\n\n`undecided` with no plans, plus the `revenueModel` they chose, IS the artifact.\nDo not add a placeholder tier to make it look fuller. The revenue model still\ntells every reader how the product makes money, so an empty `plans` never means\n\"free\" or \"no billing\".\n\n### A proposal is work the creator delegated, and it stays marked as one\n\nWhen the creator asks for a proposal, deriving tiers is the job, not an\ninvention. Derive them from what the inputs hold:\n\n- **one tier per ICP that would pay differently.** The market snapshot's ICPs\n are the segments; a tier exists because a segment needs a different package,\n never because three tiers is customary. An anti-target the vision excludes\n gets no tier.\n- **what separates each tier is a set of requirements.** Put the requirement\n refs it unlocks in `includesRequirementRefs`, and say in `includes` what it\n holds back relative to the tier beside it.\n- **`proposalBasis` names the evidence**: the ICP ref it serves and the\n requirements that distinguish it (\"serves icp-indie-maker; holds back the\n team-planning requirements the Team tier unlocks\"). A proposal with no basis\n is a tier nobody can check.\n- **A proposal still never sets a price or a scaling axis.** Unless the creator\n stated one, `pricePoint`, `billingPeriod` and `pricingModel` are `null` on a\n proposed plan exactly as on a stated one. The creator delegated the tiers, not\n the prices.\n\nThe creator accepts or revises the proposal at the approval step; you do not\nneed to be cautious on their behalf by proposing nothing.\n\n## What you DO derive\n\nTwo things, and both are cross-links rather than content:\n\n### `targetIcpRefs` — who each plan is sold to\n\nThe creator described tiers in prose (\"a free one for solo people, a paid one\nfor teams\"). The market snapshot holds the ICP refs. Your job is to resolve one\nagainst the other: match each described audience to the ICP that means it, and\nput its ref on the plan.\n\nEvery ref you write must EXIST in the market snapshot. A dangling ICP ref is a\nvalidator ERROR, and it is also the more interesting failure — it usually means\nthe creator described an audience the market analysis never identified, which is\nworth surfacing rather than papering over. If a described audience matches no\nICP, omit the ref and say so in `targetSummary` prose instead.\n\nWatch for **anti-targets**: a vision constraint may explicitly rule out a\nsegment (an enterprise procurement motion, say). Do not target an ICP the vision\nexcludes, even if a tier looks like it fits.\n\n### `includesRequirementRefs` — what each plan unlocks\n\nThis is the traceability that makes the artifact load-bearing rather than\ndecorative: it is what `bottom_up.foundation` reads to decide whether the\napplication needs a billing capability at all.\n\nResolve the creator's description of what each tier includes against the\n`requirements` family, and list the refs. Every ref must exist there. A paid\ntier that unlocks no nameable requirement is a signal worth leaving visible —\neither the requirement is missing, or the tier is not really differentiated.\n\n## The free tier is the one to get right\n\nIf the creator described a free tier or trial, two things matter and both come\nfrom what they said:\n\n- what it **includes** — the requirements it unlocks;\n- what is **deliberately held back** — which is usually the sharper statement of\n the paid tiers' value, and belongs in the paid plan's `includes` prose.\n\nIf they said there is no free tier, say nothing about one. Freemium is a\n*revenue model*, not a default.\n\n## Producing the artifact\n\nOne output, the `business-model` family. The contract is strict:\n\n- **`revenueModel` is required.** Pick the enum member closest to what the\n creator described. If they described something genuinely outside the set, pick\n the nearest and explain the mismatch in the plans' prose — do not stretch a\n member past its meaning.\n- **`pricingTiers` is required**, and it decides how many plans there are (see\n the table above). `creator_stated` and `proposed` carry at least one plan;\n `undecided` carries none. If the creator sells exactly one thing, that is one\n `creator_stated` plan, fully described.\n- **`slug`, not `ref`.** You author a kebab-case slug per plan; the trusted\n runtime stamps the `pricing-plan-` prefix. Never write a ref yourself.\n- **Every optional field is nullable and required.** Send `null` where the\n creator gave you nothing. An omitted key and a considered \"there is none\" must\n not look the same.\n\n## Verification before you answer\n\n- [ ] `pricingTiers` is the reading of the tiers answer from the table above.\n- [ ] Every `pricePoint` and `pricingModel` traces to something the creator\n actually wrote — on a proposed plan too.\n- [ ] Every `per_usage` plan names its `usageUnit`, and no other plan names one.\n- [ ] Every `creator_stated` plan traces to a tier they described. No tier count\n was rounded up.\n- [ ] Every `proposed` plan carries a `proposalBasis` naming an ICP and the\n requirements that separate it; every `creator_stated` plan carries none.\n- [ ] An `undecided` sketch has no plans, and no placeholder was added.\n- [ ] Every `targetIcpRefs` entry exists in the market snapshot.\n- [ ] Every `includesRequirementRefs` entry exists in the requirements snapshot.\n- [ ] No ICP the vision constraints exclude is targeted.\n- [ ] `revenueModel` is consistent with the plans beneath it — a `freemium`\n classification with no free plan, or a `subscription` with only a one-off\n purchase, is incoherent. An `undecided` sketch with no plans is coherent\n with any revenue model.\n- [ ] Nothing in the artifact answers a question the creator left open.\n",
|
|
50
|
+
"guidance": "# Business Model — Commercial Intent 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.** Pricing sketch depth only — no unit\n> economics, no cohort modelling, no competitive price positioning. Those are a\n> later phase; do not perfect them here.\n\n## What this playbook does\n\nYou are recording the product's **commercial intent**: how it makes money, and\nwhat it sells. The output is one `BusinessModelLiteSnapshot` — a revenue-model\nclassification plus a sketch of pricing plans, each cross-linked to the market\nsegments it is sold to and the requirements it unlocks.\n\nIt is a **PLANNING artifact**, in exactly the sense the vision and the roadmap\nare. It is not the billing runtime, not a Stripe catalogue, and not a price list\nanyone is held to. Nothing reads it to charge a customer.\n\n## The one rule that governs everything below\n\n**You do not decide how this product charges. The creator does.**\n\nEvery other top-down family is DERIVED — the market snapshot follows from the\nvision, requirements follow from both, the roadmap follows from the capability\nmap. This one is not, and the difference is not a matter of degree. The same\nproduct is a fair freemium tool, a per-seat B2B subscription, or a\nusage-metered API, and **nothing in the vision, the market or the requirements\ndecides which**. It is a business decision, and only the creator holds it.\n\nSo this playbook interviews. Your job is to take what the creator said and make\nit *structured and cross-linked* — never to fill a gap they left.\n\nConcretely:\n\n- **Never invent a price.** If the creator said \"not decided yet\", omit\n `pricePoint`. A tier with no price is a real, useful plan; a tier with a price\n nobody chose is a fabrication that then propagates — the foundation playbook\n derives the billing capability from this artifact.\n- **Never invent a tier.** Three tiers is the industry default and that is\n exactly why it is a trap. If they described one, produce one.\n- **Never invent a scaling axis.** If they did not say what the price scales\n with, omit `pricingModel` rather than guessing `per_seat`.\n- **A price per usage names its unit.** When a plan's `pricingModel` is\n `per_usage`, `usageUnit` is what ONE unit counts, singular and in the\n creator's words: \"API call\", \"export\", \"close\". A firm that bills each case\n (\"we charge per monthly close\", \"a fixed fee per audit\") is pricing per usage,\n and its unit is the case. Every other plan has `usageUnit: null`.\n- **\"Not decided yet\" is an answer.** Record what they *did* decide and leave\n the rest absent. Absence is legible; an invention is not.\n\n## Where the tiers came from: `pricingTiers`\n\nThe tiers answer has exactly four honest readings, and you record which one it\nwas. This status is what lets an empty sketch be an answer instead of a gap.\n\nRead the answer's **standing** first. An answer marked ASSUMED was proposed for\nthe creator (a quick interview, or a creator who did not know) and they never\nstated it. It is still the input you build on, but it is not the creator's word,\nso a tier it names is not `creator_stated`.\n\n| The tiers answer | `pricingTiers` | `plans` |\n|---|---|---|\n| the creator named one or more tiers (\"one tier\" counts) | `creator_stated` | exactly the tiers they named, `proposalBasis: null` on each |\n| the creator asked for tiers to be proposed (\"propose them\", \"derive them from the market research\") | `proposed` | your proposal, each plan with a `proposalBasis` |\n| is ASSUMED, and names tiers or asks for a proposal | `assumed` | the tiers it names (or your proposal), each plan with a `proposalBasis` saying what the assumption rested on |\n| says the tiers are not decided, and asks for no proposal (assumed or not) | `undecided` | **empty** |\n\nA creator who says \"not decided — let the plan propose them\" has asked for a\nproposal: that is `proposed`, not `undecided`. Read the whole answer, not its\nfirst words.\n\n### An undecided sketch is complete\n\n`undecided` with no plans, plus the `revenueModel` they chose, IS the artifact.\nDo not add a placeholder tier to make it look fuller. The revenue model still\ntells every reader how the product makes money, so an empty `plans` never means\n\"free\" or \"no billing\".\n\n### A proposal is work the creator delegated, and it stays marked as one\n\nWhen the creator asks for a proposal, deriving tiers is the job, not an\ninvention. Derive them from what the inputs hold:\n\n- **one tier per ICP that would pay differently.** The market snapshot's ICPs\n are the segments; a tier exists because a segment needs a different package,\n never because three tiers is customary. An anti-target the vision excludes\n gets no tier.\n- **what separates each tier is a set of requirements.** Put the requirement\n refs it unlocks in `includesRequirementRefs`, and say in `includes` what it\n holds back relative to the tier beside it.\n- **`proposalBasis` names the evidence**: the ICP ref it serves and the\n requirements that distinguish it (\"serves icp-indie-maker; holds back the\n team-planning requirements the Team tier unlocks\"). A proposal with no basis\n is a tier nobody can check.\n- **A proposal still never sets a price or a scaling axis.** Unless the creator\n stated one, `pricePoint`, `billingPeriod` and `pricingModel` are `null` on a\n proposed plan exactly as on a stated one. The creator delegated the tiers, not\n the prices.\n\nThe creator accepts or revises the proposal at the approval step; you do not\nneed to be cautious on their behalf by proposing nothing.\n\n### An assumed sketch is a hypothesis, and says so\n\n`assumed` is the honest status when the tiers answer was assumed: the run goes\nahead on it, and the artifact marks it so nobody downstream reads it as the\ncreator's decision. Never write `creator_stated` for an assumed answer; a judge\nreads that as presenting an assumption as the creator's statement. Never write\n`proposed` either: the creator did not ask for a proposal.\n\n**An assumed price is not a price.** When the price-points or scaling-axis answer\nis ASSUMED, leave `pricePoint`, `billingPeriod` and `pricingModel` `null`, exactly\nas for an undecided answer. A tier with no price is a real plan; a price nobody\ndecided would reach the billing catalogue as if someone had.\n\nThe same holds for the other answers: a free tier or revenue model the creator\nnever stated, because its answer was ASSUMED, is built on but never described as\nthe creator's decision.\n\n## What you DO derive\n\nTwo things, and both are cross-links rather than content:\n\n### `targetIcpRefs` — who each plan is sold to\n\nThe creator described tiers in prose (\"a free one for solo people, a paid one\nfor teams\"). The market snapshot holds the ICP refs. Your job is to resolve one\nagainst the other: match each described audience to the ICP that means it, and\nput its ref on the plan.\n\nEvery ref you write must EXIST in the market snapshot. A dangling ICP ref is a\nvalidator ERROR, and it is also the more interesting failure — it usually means\nthe creator described an audience the market analysis never identified, which is\nworth surfacing rather than papering over. If a described audience matches no\nICP, omit the ref and say so in `targetSummary` prose instead.\n\nWatch for **anti-targets**: a vision constraint may explicitly rule out a\nsegment (an enterprise procurement motion, say). Do not target an ICP the vision\nexcludes, even if a tier looks like it fits.\n\n### `includesRequirementRefs` — what each plan unlocks\n\nThis is the traceability that makes the artifact load-bearing rather than\ndecorative: it is what `bottom_up.foundation` reads to decide whether the\napplication needs a billing capability at all.\n\nResolve the creator's description of what each tier includes against the\n`requirements` family, and list the refs. Every ref must exist there. A paid\ntier that unlocks no nameable requirement is a signal worth leaving visible —\neither the requirement is missing, or the tier is not really differentiated.\n\n## The free tier is the one to get right\n\nIf the creator described a free tier or trial, two things matter and both come\nfrom what they said:\n\n- what it **includes** — the requirements it unlocks;\n- what is **deliberately held back** — which is usually the sharper statement of\n the paid tiers' value, and belongs in the paid plan's `includes` prose.\n\nIf they said there is no free tier, say nothing about one. Freemium is a\n*revenue model*, not a default.\n\n## Producing the artifact\n\nOne output, the `business-model` family. The contract is strict:\n\n- **`revenueModel` is required.** Pick the enum member closest to what the\n creator described. If they described something genuinely outside the set, pick\n the nearest and explain the mismatch in the plans' prose — do not stretch a\n member past its meaning.\n- **`pricingTiers` is required**, and it decides how many plans there are (see\n the table above). `creator_stated`, `proposed` and `assumed` carry at least one plan;\n `undecided` carries none. If the creator sells exactly one thing, that is one\n `creator_stated` plan, fully described.\n- **`slug`, not `ref`.** You author a kebab-case slug per plan; the trusted\n runtime stamps the `pricing-plan-` prefix. Never write a ref yourself.\n- **Every optional field is nullable and required.** Send `null` where the\n creator gave you nothing. An omitted key and a considered \"there is none\" must\n not look the same.\n\n## Verification before you answer\n\n- [ ] `pricingTiers` is the reading of the tiers answer and its standing from\n the table above — `assumed`, never `creator_stated`, for an ASSUMED answer.\n- [ ] Every `pricePoint` and `pricingModel` traces to a DECIDED answer — on a\n proposed or assumed plan too; an ASSUMED price-points answer sets none.\n- [ ] Every `per_usage` plan names its `usageUnit`, and no other plan names one.\n- [ ] Every `creator_stated` plan traces to a tier they described. No tier count\n was rounded up.\n- [ ] Every `proposed` or `assumed` plan carries a `proposalBasis` naming an ICP\n and the requirements that separate it; every `creator_stated` plan carries\n none.\n- [ ] An `undecided` sketch has no plans, and no placeholder was added.\n- [ ] Every `targetIcpRefs` entry exists in the market snapshot.\n- [ ] Every `includesRequirementRefs` entry exists in the requirements snapshot.\n- [ ] No ICP the vision constraints exclude is targeted.\n- [ ] `revenueModel` is consistent with the plans beneath it — a `freemium`\n classification with no free plan, or a `subscription` with only a one-off\n purchase, is incoherent. An `undecided` sketch with no plans is coherent\n with any revenue model.\n- [ ] Nothing in the artifact answers a question the creator left open.\n\n## Refine, don't re-author\n\nWhen a business model is already on record, it is an input of this run: refine it. Keep every ref that still names\nthe same thing, because other artifacts and committed work name it: the build plan's billing products name each pricing plan. Mint a new ref only for something\nthat did not exist before, and drop one only when its subject is gone. A reworded entry under a new ref reads\neverywhere downstream as one thing removed and another added (#3449).\n",
|
|
48
51
|
"skillRefs": [],
|
|
49
52
|
"skillBodyRefs": [],
|
|
50
53
|
"elicitation": {
|
|
@@ -67,28 +70,41 @@
|
|
|
67
70
|
"ref": "pricing-tiers",
|
|
68
71
|
"question": "What tiers or packages do you plan to sell? Name each one and say who it is for — answer \"one tier\" if there is only one. Answer \"not decided yet\" if you have not chosen, or \"propose them\" to have tiers proposed from the market research and requirements for you to review (a proposal never sets a price).",
|
|
69
72
|
"kind": "free_text",
|
|
70
|
-
"depth": "detail"
|
|
73
|
+
"depth": "detail",
|
|
74
|
+
"nonAnswers": [
|
|
75
|
+
"deferred"
|
|
76
|
+
]
|
|
71
77
|
},
|
|
72
78
|
{
|
|
73
79
|
"ref": "pricing-scaling-axis",
|
|
74
80
|
"question": "What does the price scale with — seats, usage, a flat fee, or is it negotiated per customer? Answer \"not decided yet\" if you have not chosen.",
|
|
75
81
|
"kind": "free_text",
|
|
76
|
-
"depth": "detail"
|
|
82
|
+
"depth": "detail",
|
|
83
|
+
"nonAnswers": [
|
|
84
|
+
"deferred"
|
|
85
|
+
]
|
|
77
86
|
},
|
|
78
87
|
{
|
|
79
88
|
"ref": "price-points",
|
|
80
89
|
"question": "Do you already have price points in mind for those tiers? Give them as you would write them (\"$29 / user / month\", \"contact us\"). Answer \"not decided yet\" if not — a tier with no price is still a real plan.",
|
|
81
90
|
"kind": "free_text",
|
|
82
|
-
"depth": "detail"
|
|
91
|
+
"depth": "detail",
|
|
92
|
+
"nonAnswers": [
|
|
93
|
+
"deferred"
|
|
94
|
+
]
|
|
83
95
|
},
|
|
84
96
|
{
|
|
85
97
|
"ref": "free-tier",
|
|
86
98
|
"question": "Is there a free tier or trial? If so, what does it include, and what is deliberately held back for the paid tiers?",
|
|
87
99
|
"kind": "free_text",
|
|
88
|
-
"depth": "detail"
|
|
100
|
+
"depth": "detail",
|
|
101
|
+
"nonAnswers": [
|
|
102
|
+
"not_applicable"
|
|
103
|
+
]
|
|
89
104
|
}
|
|
90
105
|
]
|
|
91
106
|
},
|
|
107
|
+
"derivedFromAnswers": [],
|
|
92
108
|
"contextSources": [],
|
|
93
109
|
"draftableDocumentDefinitionRefs": [],
|
|
94
110
|
"suspendsForClarification": false,
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.capability-map",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.2.0",
|
|
4
4
|
"phase": "top_down",
|
|
5
5
|
"intent": "Map accepted market benefits and requirements to coherent product capabilities, atomically refining the market benefit-to-feature edges and producing ref-less feature specification drafts. FIT/Kano remains a pluggable fit signal, never an implicit build-order ranking.",
|
|
6
6
|
"preconditions": [
|
|
@@ -41,7 +41,10 @@
|
|
|
41
41
|
{
|
|
42
42
|
"family": "market-snapshot",
|
|
43
43
|
"schemaRef": "saas-specifications:MarketSnapshot",
|
|
44
|
-
"description": "The same market snapshot, refined so every benefit names its delivering feature refs."
|
|
44
|
+
"description": "The same market snapshot, refined so every benefit names its delivering feature refs.",
|
|
45
|
+
"aspects": [
|
|
46
|
+
"market.benefit"
|
|
47
|
+
]
|
|
45
48
|
},
|
|
46
49
|
{
|
|
47
50
|
"family": "feature-drafts",
|
|
@@ -59,6 +62,7 @@
|
|
|
59
62
|
"spec-feature-update"
|
|
60
63
|
],
|
|
61
64
|
"skillBodyRefs": [],
|
|
65
|
+
"derivedFromAnswers": [],
|
|
62
66
|
"contextSources": [
|
|
63
67
|
"market_fit_scores"
|
|
64
68
|
],
|
|
@@ -28,7 +28,7 @@ Three children, self-ordered by their own preconditions:
|
|
|
28
28
|
state a posture from, and when it is not, names precisely what is missing so the
|
|
29
29
|
next research round is aimed rather than repeated.
|
|
30
30
|
3. **compliance-posture** — the artifact-producing child: records each applicable
|
|
31
|
-
regime as a
|
|
31
|
+
regime as a constraint in the `compliance-posture` family, deriving from the
|
|
32
32
|
creator's elicitation answers AND the gathered evidence, only once the adequacy
|
|
33
33
|
gate has returned ADEQUATE.
|
|
34
34
|
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.compliance-analysis",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.2.0",
|
|
4
4
|
"phase": "top_down",
|
|
5
|
-
"intent": "Establish the compliance posture by gathering regime EVIDENCE from authoritative sources, judging whether it is enough, and recording the applicable regimes
|
|
5
|
+
"intent": "Establish the compliance posture by gathering regime EVIDENCE from authoritative sources, judging whether it is enough, and recording the applicable regimes in the compliance posture only once it is. An umbrella: it authors nothing itself — its deliverable is what its children land, and the order between them is decided by their own preconditions rather than declared here.",
|
|
6
6
|
"preconditions": [
|
|
7
7
|
{
|
|
8
8
|
"kind": "artifact_valid",
|
|
@@ -19,7 +19,7 @@
|
|
|
19
19
|
"outputs": [],
|
|
20
20
|
"stepOutputs": [],
|
|
21
21
|
"method": {
|
|
22
|
-
"guidance": "# Compliance Analysis — the evidence-grounded posture composite\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\nYou are the **conductor's scheduler**, not an author. This composite exists so the\napplication's compliance posture rests on regime texts and regulator pages someone\nactually read — not on what a model remembers about the law, which is confident,\nfluent, and stale in exactly the cases that carry liability.\n\n## The shape\n\nThree children, self-ordered by their own preconditions:\n\n1. **compliance-research** — a read-only web lane gathering regime evidence for the\n jurisdictions, data classes and sector the vision (and the creator's answers)\n put in scope. Returns a condensed, source-attributed brief.\n2. **compliance-evidence-adequacy** — judges whether the evidence is ENOUGH to\n state a posture from, and when it is not, names precisely what is missing so the\n next research round is aimed rather than repeated.\n3. **compliance-posture** — the artifact-producing child: records each applicable\n regime as a
|
|
22
|
+
"guidance": "# Compliance Analysis — the evidence-grounded posture composite\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\nYou are the **conductor's scheduler**, not an author. This composite exists so the\napplication's compliance posture rests on regime texts and regulator pages someone\nactually read — not on what a model remembers about the law, which is confident,\nfluent, and stale in exactly the cases that carry liability.\n\n## The shape\n\nThree children, self-ordered by their own preconditions:\n\n1. **compliance-research** — a read-only web lane gathering regime evidence for the\n jurisdictions, data classes and sector the vision (and the creator's answers)\n put in scope. Returns a condensed, source-attributed brief.\n2. **compliance-evidence-adequacy** — judges whether the evidence is ENOUGH to\n state a posture from, and when it is not, names precisely what is missing so the\n next research round is aimed rather than repeated.\n3. **compliance-posture** — the artifact-producing child: records each applicable\n regime as a constraint in the `compliance-posture` family, deriving from the\n creator's elicitation answers AND the gathered evidence, only once the adequacy\n gate has returned ADEQUATE.\n\n## What a round's research objective should name\n\nCompose each research objective for THIS round: on the first pass, the candidate\nregimes the vision's jurisdictions/data/sector suggest (verify applicability\ntriggers against authoritative sources — regulator pages, official texts, not\nblogs); on later passes, exactly the gaps the adequacy verdict named. Never re-ask\nwhat a prior round established — its evidence is in the step results.\n",
|
|
23
23
|
"skillRefs": [],
|
|
24
24
|
"skillBodyRefs": [],
|
|
25
25
|
"elicitation": {
|
|
@@ -29,73 +29,108 @@
|
|
|
29
29
|
"question": "Does the product store, process, or transmit personal data or otherwise regulated data (health, financial, biometric, children's, government) — either from end users or on behalf of customers?",
|
|
30
30
|
"kind": "confirm",
|
|
31
31
|
"depth": "detail",
|
|
32
|
-
"regulatedDomain": true
|
|
32
|
+
"regulatedDomain": true,
|
|
33
|
+
"nonAnswers": [
|
|
34
|
+
"deferred"
|
|
35
|
+
]
|
|
33
36
|
},
|
|
34
37
|
{
|
|
35
38
|
"ref": "data-classes",
|
|
36
39
|
"question": "Which classes of sensitive data does the product touch? List them (e.g. names/emails, health records, payment card data, government IDs, precise location, employee data). Answer \"none\" if it handles no personal or sensitive data.",
|
|
37
40
|
"kind": "free_text",
|
|
38
41
|
"depth": "detail",
|
|
39
|
-
"regulatedDomain": true
|
|
42
|
+
"regulatedDomain": true,
|
|
43
|
+
"nonAnswers": [
|
|
44
|
+
"not_applicable",
|
|
45
|
+
"deferred"
|
|
46
|
+
]
|
|
40
47
|
},
|
|
41
48
|
{
|
|
42
49
|
"ref": "vendor-establishment",
|
|
43
50
|
"question": "Where is the VENDOR established — the legal entity (or intended entity) operating the product, its country/region, and where is the product hosted or planned to be hosted? Territorial-scope tests (GDPR Art. 3, UK GDPR, CCPA \"doing business\") turn on the vendor's establishment and conduct, not only on where users live. Answer \"not yet decided\" for whatever is genuinely open.",
|
|
44
51
|
"kind": "free_text",
|
|
45
52
|
"depth": "essential",
|
|
46
|
-
"regulatedDomain": true
|
|
53
|
+
"regulatedDomain": true,
|
|
54
|
+
"nonAnswers": [
|
|
55
|
+
"deferred"
|
|
56
|
+
]
|
|
47
57
|
},
|
|
48
58
|
{
|
|
49
59
|
"ref": "jurisdictions",
|
|
50
60
|
"question": "In which jurisdictions do your users live and your data reside or transit (e.g. EU/EEA, UK, US, California, Canada, specific countries)? This is what drives which privacy regimes apply.",
|
|
51
61
|
"kind": "free_text",
|
|
52
62
|
"depth": "essential",
|
|
53
|
-
"regulatedDomain": true
|
|
63
|
+
"regulatedDomain": true,
|
|
64
|
+
"nonAnswers": [
|
|
65
|
+
"deferred"
|
|
66
|
+
]
|
|
54
67
|
},
|
|
55
68
|
{
|
|
56
69
|
"ref": "sector",
|
|
57
70
|
"question": "Does the product operate in a regulated sector with its own rules (healthcare, finance/banking, insurance, education, government, telecoms)? Name the sector, or answer \"none\".",
|
|
58
71
|
"kind": "free_text",
|
|
59
72
|
"depth": "detail",
|
|
60
|
-
"regulatedDomain": true
|
|
73
|
+
"regulatedDomain": true,
|
|
74
|
+
"nonAnswers": [
|
|
75
|
+
"not_applicable",
|
|
76
|
+
"deferred"
|
|
77
|
+
]
|
|
61
78
|
},
|
|
62
79
|
{
|
|
63
80
|
"ref": "gdpr-applies",
|
|
64
81
|
"question": "Do you serve EU/EEA (or UK) individuals or process their personal data? (This is the primary trigger for GDPR / UK GDPR.)",
|
|
65
82
|
"kind": "confirm",
|
|
66
83
|
"depth": "detail",
|
|
67
|
-
"regulatedDomain": true
|
|
84
|
+
"regulatedDomain": true,
|
|
85
|
+
"nonAnswers": [
|
|
86
|
+
"deferred"
|
|
87
|
+
]
|
|
68
88
|
},
|
|
69
89
|
{
|
|
70
90
|
"ref": "hipaa-applies",
|
|
71
91
|
"question": "Do you handle US protected health information as, or on behalf of, a covered entity or business associate? (This is the primary trigger for HIPAA.)",
|
|
72
92
|
"kind": "confirm",
|
|
73
93
|
"depth": "detail",
|
|
74
|
-
"regulatedDomain": true
|
|
94
|
+
"regulatedDomain": true,
|
|
95
|
+
"nonAnswers": [
|
|
96
|
+
"deferred"
|
|
97
|
+
]
|
|
75
98
|
},
|
|
76
99
|
{
|
|
77
100
|
"ref": "external-assurance-applies",
|
|
78
101
|
"question": "Do enterprise customers (or your own security posture) require an independent attestation or certification covering security / availability / confidentiality of the service? Name the requested target only as an external source requirement.",
|
|
79
102
|
"kind": "confirm",
|
|
80
103
|
"depth": "detail",
|
|
81
|
-
"regulatedDomain": true
|
|
104
|
+
"regulatedDomain": true,
|
|
105
|
+
"nonAnswers": [
|
|
106
|
+
"deferred"
|
|
107
|
+
]
|
|
82
108
|
},
|
|
83
109
|
{
|
|
84
110
|
"ref": "data-residency",
|
|
85
111
|
"question": "Are there data-residency or sovereignty requirements — must certain data stay within a region or country (e.g. EU-only hosting, in-country storage)? Describe them, or answer \"none\".",
|
|
86
112
|
"kind": "free_text",
|
|
87
113
|
"depth": "detail",
|
|
88
|
-
"regulatedDomain": true
|
|
114
|
+
"regulatedDomain": true,
|
|
115
|
+
"nonAnswers": [
|
|
116
|
+
"not_applicable",
|
|
117
|
+
"deferred"
|
|
118
|
+
]
|
|
89
119
|
},
|
|
90
120
|
{
|
|
91
121
|
"ref": "additional-regimes",
|
|
92
122
|
"question": "Any other legal regimes, sector frameworks, government programs, or contractual security commitments that apply? List the externally named sources, or answer \"none\".",
|
|
93
123
|
"kind": "free_text",
|
|
94
124
|
"depth": "detail",
|
|
95
|
-
"regulatedDomain": true
|
|
125
|
+
"regulatedDomain": true,
|
|
126
|
+
"nonAnswers": [
|
|
127
|
+
"not_applicable",
|
|
128
|
+
"deferred"
|
|
129
|
+
]
|
|
96
130
|
}
|
|
97
131
|
]
|
|
98
132
|
},
|
|
133
|
+
"derivedFromAnswers": [],
|
|
99
134
|
"contextSources": [],
|
|
100
135
|
"draftableDocumentDefinitionRefs": [],
|
|
101
136
|
"choreography": {
|
|
@@ -104,7 +139,7 @@
|
|
|
104
139
|
"top_down.compliance-research",
|
|
105
140
|
"top_down.compliance-evidence-adequacy"
|
|
106
141
|
],
|
|
107
|
-
"maximumIterations":
|
|
142
|
+
"maximumIterations": 8,
|
|
108
143
|
"maximumLanesPerIteration": 3,
|
|
109
144
|
"maximumDepth": 1,
|
|
110
145
|
"maximumDurationMs": 4800000
|
|
@@ -19,8 +19,8 @@ Read and apply these patterns from the application-developer point of view:
|
|
|
19
19
|
|
|
20
20
|
## What this playbook does
|
|
21
21
|
|
|
22
|
-
The compliance-posture step decided **which regimes apply**, in prose, as
|
|
23
|
-
|
|
22
|
+
The compliance-posture step decided **which regimes apply**, in prose, as the constraints of the
|
|
23
|
+
`compliance-posture` family; the vision may also carry `kind: compliance` constraints the creator stated. You turn that into the application's **assurance programme**: which Wildo
|
|
24
24
|
control objectives this product binds, which external requirement each one answers, who is
|
|
25
25
|
accountable, and what is explicitly undetermined.
|
|
26
26
|
|
|
@@ -29,7 +29,7 @@ artifact — the `compliance-program` family — and nothing else.
|
|
|
29
29
|
|
|
30
30
|
## The one rule that governs everything below
|
|
31
31
|
|
|
32
|
-
**A
|
|
32
|
+
**A posture sentence is not a control mapping.** The posture step recorded "must be GDPR-compliant for
|
|
33
33
|
EU customer personal data". That is product intent. It is *not* a decision that this application binds
|
|
34
34
|
`WILDO.PRIVACY.SUBJECT_DATA_EXPORT`, and converting one into the other by reading is exactly what the
|
|
35
35
|
posture step's own method forbids: the transition "must not reinterpret a vision sentence as a control
|