@wildo-ai/framework-knowledge 1.1.11 → 1.1.13
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 +180 -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 +30 -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 +87 -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 +55 -8
- 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 +19 -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/method.md +14 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +11 -7
- 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 +70 -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.config-wiring.retention-policy-operations.md +21 -0
- 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 +1 -1
- package/dist/knowledge/references/platform.config.platform-key-management.md +89 -10
- 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.engine-substance.md +38 -0
- package/dist/knowledge/references/requirements.functional-requirement.config.md +11 -0
- package/dist/knowledge/references/requirements.non-functional-requirement.config.md +15 -4
- package/dist/knowledge/references/requirements.snapshot.config.md +2 -3
- package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +49 -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 +435 -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 +133 -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.chart-dashboard-tile-sizes.md +40 -0
- 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-content-guardrails-environment.md +52 -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-dashboard-layout.md +61 -0
- 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 +455 -2
- package/dist/knowledge/registries/playbooks.json +51 -39
- package/dist/knowledge/registries/source-tags.json +2505 -1627
- 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 +90 -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 +240 -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 +78 -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 +13 -3
- 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 +34 -11
- 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 +188 -10
- 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 +447 -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 +13 -3
- 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 +13 -3
- 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/SKILL.md +1 -1
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +6 -5
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +50 -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 +149 -77
- package/dist/knowledge/skills/infra-environment-config/references/framework-agent-content-guardrails-environment-api.md +67 -0
- 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 +1 -1
- package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +89 -10
- 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 +272 -15
- 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 +34 -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 +28 -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 +371 -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 +2422 -723
- 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": "bottom_up.placement-plan",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.8",
|
|
4
4
|
"phase": "bottom_up",
|
|
5
5
|
"intent": "Decide WHERE every settings destination, resource operation and application view sits in the application shell, and WHY. Reads the domain plan (the modules, their resources and what they mean), the requirements (which tasks matter), the customer profile (who the customers are, which decides whether an enterprise destination belongs at all) and what the creator stated about the user groups, and produces a PLACEMENT PLAN: for each subject, either a PLACED decision naming one surface (the settings hub rail, the sidebar, the user menu, the command palette) and its address on that surface, or an explicit DECLINED decision with a reason. Both carry a rationale. It also declares the GROUPS that should exist on the grouped surfaces (settings rail categories, sidebar sections) with the product purpose behind each, which is what grounds their generated labels in authored intent instead of filler. This playbook DECIDES placement; it does NOT author configuration — turning a decision into `frontend/src/config/settings-hub.config.ts` and `app-shell.config.ts` is a coding task the build lane dispatches, through the `settings-placement-authoring` skill for the settings rail and the `config-app-shell` skill for the sidebar, command palette and user menu. A sidebar group or a sidebar or palette decision may name the roles it is shown to (`requiredRoles`), when one audience only opens it. It runs BEFORE build-decompose, which consumes the plan and emits those tasks — the reverse order would be a cycle, since build-decompose is what produces the build plan. It writes no TypeScript, invents no destination refs, and authors no labels. It exists because the alternative is the framework defaulting placement, which is what made an application's settings rail unauthorable: nothing is placed implicitly, so a subject nobody decided about is a visible coverage gap rather than a silent framework default.",
|
|
6
6
|
"preconditions": [
|
|
@@ -27,6 +27,12 @@
|
|
|
27
27
|
},
|
|
28
28
|
{
|
|
29
29
|
"family": "vision-brief"
|
|
30
|
+
},
|
|
31
|
+
{
|
|
32
|
+
"family": "experience-plan",
|
|
33
|
+
"aspects": [
|
|
34
|
+
"experience-plan.view"
|
|
35
|
+
]
|
|
30
36
|
}
|
|
31
37
|
],
|
|
32
38
|
"outputs": [
|
|
@@ -38,13 +44,14 @@
|
|
|
38
44
|
],
|
|
39
45
|
"stepOutputs": [],
|
|
40
46
|
"method": {
|
|
41
|
-
"guidance": "# Placement Plan — Where Each Thing Belongs in the Shell, and Why\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 methodology.** The criteria below are deliberately explicit so\n> they can be tuned against real runs. What is NOT provisional is the shape of the\n> output: a decision per subject, on a named surface, with a rationale.\n\n## Where you are in the journey\n\nYou run in the **bottom-up phase**, after the **domain plan** exists and **before**\nthe build is decomposed. By now the application knows what its modules and resources\nARE; what nobody has decided is **where any of it appears**.\n\nThat order matters and was corrected during authoring. Placing things *after* the\nbuild plan reads natural — you would know every task — but `bottom_up.build-decompose`\nis what PRODUCES the build plan and it consumes this one to emit the placement tasks.\nRequiring its output would be a cycle. It is also the better order on its own merits:\nplacement is a design decision that should INFORM the decomposition, not trail it. You\ndo not need the task graph to know that a `deals` resource will have a list.\n\nThat question used to have no owner. The framework shipped a placed settings rail,\nso an application could not add, remove, reorder or rename a section without the\nframework agreeing — and the application's own config file did not tell you what a\nuser would see. Placement is now the application's, which means somebody has to\ndecide it. That is this playbook.\n\n## What this playbook does\n\nYou produce a **placement plan**: for every subject, one decision per surface.\n\nA **subject** is one of three things:\n\n- an **engine settings destination**, named by its ref from the engine catalog\n (`profile`, `security`, `billing`, `sso`, …) — the engine owns what each MEANS\n (its target, its required roles, its entitlement); it owns nothing about where it\n goes;\n- a **resource operation** — a resource's LIST, its READ, a custom verb;\n- an **application view** — composite, chart, execution, full-custom.\n\nA **surface** is one of four:\n\n| surface | grouped by | authoring home |\n|---|---|---|\n| `SETTINGS_HUB` | a rail **category** | `frontend/src/config/settings-hub.config.ts` |\n| `SIDEBAR` | a sidebar **section** | `appShellConfig[SIDEBAR].contentSections` |\n| `USER_MENU` | flat | the user dropdown's settings entries |\n| `COMMAND_MENU` | flat | the command palette |\n\nA subject may legitimately be placed on **several** surfaces — billing is a settings\nrail section AND answers to the command palette. One decision per (subject, surface);\ntwo placements of one subject on ONE surface is a contradiction and the validator\nrefuses it.\n\n**Not every surface can carry every kind of subject**, and the validator refuses a\nplacement that no configuration could realise (`SUBJECT_NOT_EXPRESSIBLE_ON_SURFACE`,\na hard floor):\n\n| surface | engine destination | resource operation | application view |\n|---|---|---|---|\n| `SETTINGS_HUB` | yes | yes — as a settings section the application declares for it | **no** |\n| `USER_MENU` | yes | yes — the same application settings section, opened from the dropdown | **no** |\n| `SIDEBAR` | yes | yes | yes |\n| `COMMAND_MENU` | yes | yes | yes |\n\nThe settings rail and the user dropdown hold settings SECTIONS. A section can show a\nresource operation (a list of the team's members, say), a framework panel, or a\ncomponent the application registers; it cannot show an application view. A view\nthat people reach from settings belongs on the sidebar or the palette.\n\n## Decline explicitly; never omit\n\nEvery decision is `PLACED` or `DECLINED`, and **both require a rationale**.\n\nThis is the rule most worth getting right. A subject recorded as `DECLINED` is a\ndecision a later reader can disagree with. A subject simply missing from the plan is\na **coverage gap** — nobody looked. If those two were the same thing, \"we considered\nthe audit log and this app has no compliance audience\" would be indistinguishable\nfrom forgetting the audit log existed.\n\nSo: if a destination should not appear anywhere in this application, say so, and say\nwhy.\n\n## First: does this application need it at all? (the fit test)\n\nBefore WHERE comes WHETHER. Every engine settings destination exists in the framework; that is not\na reason to show it. A destination is placed only when something this application declared calls\nfor it:\n\n- **a requirement** that needs it (single sign-on because a requirement says customers sign in with\n their company identity);\n- **an attribute of the customer profile** in your `market-snapshot` input (the ICPs and personas:\n company size, the tools they already run, their technical staff); or\n- **a capability the application enables** (billing settings because billing is on). What is on is\n not yours to guess: the declared `application_enabled_surface` context section of your brief lists the enabled engine\n capabilities, the billing declaration and each user type's sign-in methods, read from the\n configuration. A capability it does not list is off; one it marks UNREADABLE is unknown, and you\n say so rather than treating it as off. A destination whose capability is off serves nothing yet:\n offer it only when the customer evidence asks for it, and say its capability must be switched on.\n\nOtherwise it is DECLINED, with the profile reason. One earlier run, for a 1–20 person trade firm,\ndeclined single sign-on because such a firm \"is not assumed to operate an enterprise identity\nprovider\". Another, from the same inputs, placed SSO, SCIM, SIEM export, webhooks and legal holds\nbecause \"an admin would look here\". Only the first answered the question that comes first.\n\nThe test cuts both ways. For a 2,000-person insurer whose personas name an identity team and whose\nrequirements say staff sign in with their company account, declining single sign-on would be the\nerror: there the profile and a requirement both call for it, and it is placed, with both cited. Fit\nis read from THIS application's evidence, never from a habit of declining enterprise features.\n\n**Enterprise destinations cite their evidence in the rationale.** Single sign-on, directory sync\n(SCIM), security-event export (SIEM), webhooks, legal holds, API clients and data residency are\nplaced only with the requirement, profile attribute or capability named in the rationale. \"An admin\nwould look here\" is findability, not fit; it answers a question you have not earned yet.\n\nRead who uses the product from what the creator stated (the declared `creator_stated_facts` context section of your brief):\nthe user groups and the devices they use. A field worker on a phone and an office manager at a desk\nwant different things first, and the sidebar's order should serve the group that opens it most.\n\n**When a section or an entry is for one audience only, say so with `requiredRoles`.** A sidebar group and\na sidebar or command-menu decision may carry `requiredRoles`: the role keys that see it (a field\ntechnician does not see the office's \"Invoices\" section). Use it only when the creator's user groups\nreally differ in what they open, and name the application's own roles, or core ones like `ORG_ADMIN`.\nRoles count through the role hierarchy, custom roles included: a role that inherits a listed one sees it. Absent means everyone,\nand that is the right answer for most groups. It is refused on the settings rail and the user menu,\nwhose destinations carry their own role gating.\n\nHiding is not access control: the person who cannot see \"Invoices\" can still be allowed to open it.\nIf the field technician must not read invoices, that is a role decision on the operation, not a\nplacement, and an entry for an operation a viewer cannot perform is hidden from them already. So\n`requiredRoles` is only for narrowing further: an operation everyone may use that only one group\nneeds in its navigation.\n\n## The criteria, in the order you apply them\n\n1. **Scope correctness.** A thing that acts on the whole organization does not sit\n among a person's own preferences, and the reverse. This is first because it is\n the only criterion that is objectively *wrong* rather than debatable.\n2. **Findability.** Would the user who wants this look here FIRST — unprompted?\n Not \"would they accept it once shown\". Those are different tests and only the\n first one predicts behaviour.\n3. **Grouping coherence.** Everything in a group answers one question a user\n actually asks. A group that needs \"and other things\" in its name is two groups.\n4. **Convention fit.** Users arrive with expectations already formed by comparable\n products. A novel arrangement must EARN the cost of surprising them.\n5. **Depth discipline.** One more level of nesting must buy more than it costs. A\n section reachable only after three guesses is not placed, it is hidden.\n\nReject placements justified by implementation convenience (\"it renders there\nalready\"), by the shape of the data model rather than the user's task, or by symmetry\nfor its own sake. Surfacing something everywhere is a **cost**, not thoroughness.\n\n## Groups carry a purpose, and the purpose is load-bearing\n\nWhen you declare a group, state its `purpose` in product terms. It is not decoration:\nit is what grounds the generated `settings_hub.categories.<ref>.label` and\n`sidebar_sections.<ref>.title` labels in authored intent. Without it a model invents\nfiller from the ref alone — which is exactly how a sidebar section came to be\ndescribed as \"various tools and utilities\".\n\n## A crowded settings category gets sub-categories\n\nA settings rail category can hold **sub-categories**: headings inside the category that\ngather its sections. Declare them INSIDE the category's group, as its `subGroups` (each with a\n`groupRef`, a `purpose` and an `order`), and place a section under one with `subGroupRef` on the\nsection's address (beside the `groupRef` that names the category). A sub-category's ref is scoped\nto its category, so two categories can each have a `people` sub-category.\n\nWhen to use them:\n\n- **Group a category of more than about eight sections.** Below that, a flat list is found\n faster than a heading and the list under it. Above it, people scan for a heading first.\n- **Start from the engine's proposal.** People · Billing & entitlements · Security & access ·\n Integrations · Compliance · AI is what a new application is scaffolded with, for both the\n organization and the administration categories. Using the same headings in both lets the\n same kind of surface sit under the same heading in each. Depart from it when this\n application's sections answer different questions, and say why in the purpose.\n- **Leave a category's general entries ungrouped.** The entries that name the scope itself\n (its general settings, the directory of its members' organizations) sit directly in the\n category, above the sub-categories: omit `subGroupRef` on them.\n- **One level only.** A sub-category has no sub-categories of its own; the plan cannot express\n one. Depth discipline applies: a heading inside a heading inside a category is a section\n nobody finds.\n- **A sub-category is a group, so it carries a `purpose`** like any other, and it must have\n something placed in it.\n\n## Placing an operator surface commits the application to an AUDIENCE — say which\n\nSome subjects exist for whoever OPERATES the product rather than for the people who use it:\napplication-wide single sign-on, the application's own API keys and OAuth clients, the\nentitlement state of every tenant, the plans and prices on sale, the application-wide audit\ntrail. The framework keeps them in a separate preset scope from the end-user surfaces, and it\nkeeps them separate ON PURPOSE — an application may legitimately never render them.\n\n**So placing one is a decision about what this application IS, and the plan must state it.**\nTwo answers, both correct:\n\n- **ONE application.** Operators and users share a frontend and are told apart by their roles.\n Place the operator subjects in their own group — an `administration` category beside the\n account and organization ones — and record that this application composes BOTH preset scopes.\n- **TWO applications.** A separate operator frontend. Decline the operator subjects here, with\n that as the rationale, and they belong to the other application's plan.\n\nState the answer in the plan even when it is the obvious one, because the failure it prevents is\nsilent: an application that places operator subjects while composing only the end-user scope gets\nrail entries that OPEN AND RENDER NOTHING. An operation no composed preset surfaces is\ncallable-from-code with no interface, so the section is not missing and does not error — it is\nblank, and it reads as a slow load or a broken backend rather than as an application that was\nassembled without an audience. Seventeen sections were in exactly that state on the dogfood\napplication before this was written down.\n\nYou are not choosing the composition here — that is a coding task the build lane dispatches\nthrough `settings-placement-authoring`. You are stating WHICH audience the arrangement assumes,\nso the task that follows has something to implement rather than a default to guess.\n\n## What you do NOT do\n\n- **You do not author configuration.** Turning a decision into\n `settings-hub.config.ts` or `app-shell.config.ts` is a coding task the build lane\n dispatches through the `settings-placement-authoring` skill. If you catch yourself\n writing a config key, a file path or a label string, stop.\n- **You do not invent destination refs.** The workspace-truth section lists every engine\n settings destination under **\"Settings destinations the engine ships\"**, with what each\n one shows and its role gating. That list is the whole universe: a ref outside it is an\n `UNKNOWN_SUBJECT` and the validator REFUSES the plan — a hard floor, not a warning. Rule\n on all of them where you can; a destination your plan says nothing about is reported\n undecided.\n- **You do not decide what a destination MEANS.** Its target, roles and entitlement\n are the engine's. You decide only where it sits.\n- **You do not re-open the build plan.** What is being built is settled.\n\n## Verification\n\n- Every subject the workspace offers is either PLACED or DECLINED — nothing omitted.\n- No subject placed twice on one surface.\n- No application view placed on the settings rail or the user dropdown.\n- Every grouped placement names a group this plan declares, for that same surface.\n- Every `subGroupRef` names a sub-category this plan declares under that placement's category.\n- Sub-categories are declared only on `SETTINGS_HUB` categories, each ref once per category.\n- Every group, sub-categories included, has something in it.\n- Every decision, both arms, carries a rationale that would satisfy a reader who\n disagrees with it.\n- The plan states which AUDIENCE it assumes — one application or two — whenever it places or\n declines an operator subject.\n\n## WHO decides — a panel, not you alone and not the creator\n\n**The creator does not choose placement.** This playbook convenes an expert panel and\ntakes its winner.\n\nConcretely, on every run: three candidate arrangements are generated independently\nagainst this brief, each schema-valid before anyone sees it and each told to take a\ngenuinely different position; the **information-architect** derives the rubric (it\nowns the domain); it and the **design-system-guardian** review every candidate; the\nguardian coordinates, shortlists, and synthesises a winner. What lands is that winner.\n\nTwo consequences for how you write:\n\n- **Take a position and commit to it.** You are one candidate among three, and the\n panel cannot compare three hedged arrangements. State what your arrangement makes\n WORSE — an arrangement with no cost has not been thought about, and the reviewers\n are instructed to notice.\n- **The rationale on each decision is the durable part.** It is what a creator asking\n \"why is Billing under Organization?\" reads, and it is the only trace of the argument\n once the winner has landed.\n\n**Fail-closed on charters.** Every panel role needs a committed charter, and the\ncompanion indexes agents at startup — a charter accepted after boot has no agent until\na restart, and the error says exactly that. The run does NOT quietly degrade to a\nsingle generation: an artifact carrying a panel's authority over a decision no panel\nsaw is the worst outcome available here, so fewer than two usable candidates returns\nto the ordinary retry instead.\n\n## And when the placement is wrong\n\nTwo different things can change, and conflating them is how a plan starts lying.\n\n**The config file** — `settings-hub.config.ts`, `app-shell.config.ts` — is what actually\nrenders. A creator who disagrees edits it directly. That works today, needs no companion,\nand is a git commit, which is the accepted state.\n\n**The plan** is the decision record, and it is what a later reader consults to ask why.\nIt can be changed two ways:\n\n- **Re-run this playbook.** The panel deliberates again and the landing REPLACES the\n existing file. Nothing refuses it; that is the design.\n- **Edit the landed plan.** It is an application-owned source like any other.\n\nEither way, a decision that no longer reflects the panel must say so. Set its `origin`\nto `REVISED` and record what the panel had decided in `supersedes.rationale`. Both are\nrequired together — the schema refuses a `REVISED` decision with nothing superseded, and\nrefuses a `DELIBERATED` one that supersedes something, because no panel run produces\neither shape.\n\n**Why the artifact carries this when git already records the change.** Git knows who\nchanged the line, when, and with what message, and that is not being duplicated here. What\ngit cannot tell someone READING the file — in an editor, asking \"why is Billing under\nAccount?\" — is that this particular decision is no longer the panel's. Without it, the\n`rationale` field goes on asserting panel reasoning for a decision the panel never took,\nand there is no way to notice.\n\nDo not paraphrase the panel's rationale into the new one. A `supersedes.rationale` that\nrepeats the decision's own text word for word satisfies the schema and tells a reader\nnothing; the validator reports it as an authoring warning.\n",
|
|
47
|
+
"guidance": "# Placement Plan — Where Each Thing Belongs in the Shell, and Why\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 methodology.** The criteria below are deliberately explicit so\n> they can be tuned against real runs. What is NOT provisional is the shape of the\n> output: a decision per subject, on a named surface, with a rationale.\n\n## Where you are in the journey\n\nYou run in the **bottom-up phase**, after the **domain plan** exists and **before**\nthe build is decomposed. By now the application knows what its modules and resources\nARE; what nobody has decided is **where any of it appears**.\n\nThat order matters and was corrected during authoring. Placing things *after* the\nbuild plan reads natural — you would know every task — but `bottom_up.build-decompose`\nis what PRODUCES the build plan and it consumes this one to emit the placement tasks.\nRequiring its output would be a cycle. It is also the better order on its own merits:\nplacement is a design decision that should INFORM the decomposition, not trail it. You\ndo not need the task graph to know that a `deals` resource will have a list.\n\nThat question used to have no owner. The framework shipped a placed settings rail,\nso an application could not add, remove, reorder or rename a section without the\nframework agreeing — and the application's own config file did not tell you what a\nuser would see. Placement is now the application's, which means somebody has to\ndecide it. That is this playbook.\n\n## What this playbook does\n\nYou produce a **placement plan**: for every subject, one decision per surface.\n\nA **subject** is one of three things:\n\n- an **engine settings destination**, named by its ref from the engine catalog\n (`profile`, `security`, `billing`, `sso`, …) — the engine owns what each MEANS\n (its target, its required roles, its entitlement); it owns nothing about where it\n goes;\n- a **resource operation** — a resource's LIST, its READ, a custom verb;\n- an **application view** — composite, chart, execution, full-custom.\n\nA **surface** is one of four:\n\n| surface | grouped by | authoring home |\n|---|---|---|\n| `SETTINGS_HUB` | a rail **category** | `frontend/src/config/settings-hub.config.ts` |\n| `SIDEBAR` | a sidebar **section** | `appShellConfig[SIDEBAR].contentSections` |\n| `USER_MENU` | flat | the user dropdown's settings entries |\n| `COMMAND_MENU` | flat | the command palette |\n\nA subject may legitimately be placed on **several** surfaces — billing is a settings\nrail section AND answers to the command palette. One decision per (subject, surface);\ntwo placements of one subject on ONE surface is a contradiction and the validator\nrefuses it.\n\n**Not every surface can carry every kind of subject**, and the validator refuses a\nplacement that no configuration could realise (`SUBJECT_NOT_EXPRESSIBLE_ON_SURFACE`,\na hard floor):\n\n| surface | engine destination | resource operation | application view |\n|---|---|---|---|\n| `SETTINGS_HUB` | yes | yes — as a settings section the application declares for it | **no** |\n| `USER_MENU` | yes | yes — the same application settings section, opened from the dropdown | **no** |\n| `SIDEBAR` | yes | yes | yes |\n| `COMMAND_MENU` | yes | yes | yes |\n\nThe settings rail and the user dropdown hold settings SECTIONS. A section can show a\nresource operation (a list of the team's members, say), a framework panel, or a\ncomponent the application registers; it cannot show an application view. A view\nthat people reach from settings belongs on the sidebar or the palette.\n\n## Decline explicitly; never omit\n\nEvery decision is `PLACED` or `DECLINED`, and **both require a rationale**.\n\nThis is the rule most worth getting right. A subject recorded as `DECLINED` is a\ndecision a later reader can disagree with. A subject simply missing from the plan is\na **coverage gap** — nobody looked. If those two were the same thing, \"we considered\nthe audit log and this app has no compliance audience\" would be indistinguishable\nfrom forgetting the audit log existed.\n\nSo: if a destination should not appear anywhere in this application, say so, and say\nwhy.\n\n## First: does this application need it at all? (the fit test)\n\nBefore WHERE comes WHETHER. Every engine settings destination exists in the framework; that is not\na reason to show it. A destination is placed only when something this application declared calls\nfor it:\n\n- **a requirement** that needs it (single sign-on because a requirement says customers sign in with\n their company identity);\n- **an attribute of the customer profile** in your `market-snapshot` input (the ICPs and personas:\n company size, the tools they already run, their technical staff); or\n- **a capability the application enables** (billing settings because billing is on). What is on is\n not yours to guess: the declared `application_enabled_surface` context section of your brief lists the enabled engine\n capabilities, the billing declaration and each user type's sign-in methods, read from the\n configuration. A capability it does not list is off; one it marks UNREADABLE is unknown, and you\n say so rather than treating it as off. A destination whose capability is off serves nothing yet:\n offer it only when the customer evidence asks for it, and say its capability must be switched on.\n\nOtherwise it is DECLINED, with the profile reason. One earlier run, for a 1–20 person trade firm,\ndeclined single sign-on because such a firm \"is not assumed to operate an enterprise identity\nprovider\". Another, from the same inputs, placed SSO, SCIM, SIEM export, webhooks and legal holds\nbecause \"an admin would look here\". Only the first answered the question that comes first.\n\nThe test cuts both ways. For a 2,000-person insurer whose personas name an identity team and whose\nrequirements say staff sign in with their company account, declining single sign-on would be the\nerror: there the profile and a requirement both call for it, and it is placed, with both cited. Fit\nis read from THIS application's evidence, never from a habit of declining enterprise features.\n\n**Enterprise destinations cite their evidence in the rationale.** Single sign-on, directory sync\n(SCIM), security-event export (SIEM), webhooks, legal holds, API clients and data residency are\nplaced only with the requirement, profile attribute or capability named in the rationale. \"An admin\nwould look here\" is findability, not fit; it answers a question you have not earned yet.\n\nRead who uses the product from what the creator stated (the declared `creator_stated_facts` context section of your brief):\nthe user groups and the devices they use. A field worker on a phone and an office manager at a desk\nwant different things first, and the sidebar's order should serve the group that opens it most.\n\n**When a section or an entry is for one audience only, say so with `requiredRoles`.** A sidebar group and\na sidebar or command-menu decision may carry `requiredRoles`: the role keys that see it (a field\ntechnician does not see the office's \"Invoices\" section). Use it only when the creator's user groups\nreally differ in what they open, and name the application's own roles, or core ones like `ORG_ADMIN`.\nRoles count through the role hierarchy, custom roles included: a role that inherits a listed one sees it. Absent means everyone,\nand that is the right answer for most groups. It is refused on the settings rail and the user menu,\nwhose destinations carry their own role gating.\n\nHiding is not access control: the person who cannot see \"Invoices\" can still be allowed to open it.\nIf the field technician must not read invoices, that is a role decision on the operation, not a\nplacement, and an entry for an operation a viewer cannot perform is hidden from them already. So\n`requiredRoles` is only for narrowing further: an operation everyone may use that only one group\nneeds in its navigation.\n\n## The criteria, in the order you apply them\n\n1. **Scope correctness.** A thing that acts on the whole organization does not sit\n among a person's own preferences, and the reverse. This is first because it is\n the only criterion that is objectively *wrong* rather than debatable.\n2. **Findability.** Would the user who wants this look here FIRST — unprompted?\n Not \"would they accept it once shown\". Those are different tests and only the\n first one predicts behaviour.\n3. **Grouping coherence.** Everything in a group answers one question a user\n actually asks. A group that needs \"and other things\" in its name is two groups.\n4. **Convention fit.** Users arrive with expectations already formed by comparable\n products. A novel arrangement must EARN the cost of surprising them.\n5. **Depth discipline.** One more level of nesting must buy more than it costs. A\n section reachable only after three guesses is not placed, it is hidden.\n\nReject placements justified by implementation convenience (\"it renders there\nalready\"), by the shape of the data model rather than the user's task, or by symmetry\nfor its own sake. Surfacing something everywhere is a **cost**, not thoroughness.\n\n**One business concept, one sidebar entry.** The domain plan sometimes keeps one\nconcept's records in two resources: read through live from another system AND copied\ninto the application (its `organizationModel.recordLocations` names both lanes for the\nrecords of one system), or a directory and the records people adopt from it. The\nconcept's one sidebar entry is the application VIEW that shows both lists (the\nexperience plan names it, with the resources it is the entry for, in\n`entryForResourceRefs`; `config-navigation`, `references/one-entry-per-concept.md`).\nSo PLACE that view on the SIDEBAR, and PLACE each list on the COMMAND_MENU only, so it\nstays reachable by name. Never DECLINE one of these lists: a declined decision means\nthe subject is shown NOWHERE, so a list declined and also placed on the command menu is\na contradiction no shell can carry. Two entries for one concept is criterion 2 failing\ntwice — Wonder Procurement put \"Supplier Directory\" and \"Suppliers\" side by side, and\nnobody could tell which to use or why a supplier was in one and not the other. Read the\nexperience plan's views when you are given them: place the view whose\n`entryForResourceRefs` names the concept's resources, by its slug (without `view-`).\nWhen there is no experience plan yet, name the concept's view by the concept's slug\n(`suppliers`), the slug the experience plan is told to give it. Where the two plans still\ndisagree, the coherence report marks it (`concept-list-on-sidebar`,\n`concept-view-not-on-sidebar`, `concept-list-not-on-command-menu`); it refuses nothing, and\nthe next run of the plan that is wrong resolves it.\n\n**Every view you place is one the experience plan holds.** When you are given the\nexperience plan's views, an `APP_VIEW` subject names one of them, by its slug (its\n`viewRef` without `view-`), and nothing else: a view the experience plan does not plan is\na view no task builds, and the sidebar task that must carry it can never land. One\napplication placed `guided-onboarding`, `manager-pipeline-adoption-overview` and\n`field-workspace` while its experience plan held `view-getting-started`,\n`view-management-overview` and `view-field-work-overview`. A placement plan naming a\nview the landed experience plan does not hold is refused, with the planned views named\n(`placement-places-unknown-view`). Do not rename a view to suit the sidebar's wording:\nthe section's label is the placement's, the view's ref is the experience plan's.\n\n## Groups carry a purpose, and the purpose is load-bearing\n\nWhen you declare a group, state its `purpose` in product terms. It is not decoration:\nit is what grounds the generated `settings_hub.categories.<ref>.label` and\n`sidebar_sections.<ref>.title` labels in authored intent. Without it a model invents\nfiller from the ref alone — which is exactly how a sidebar section came to be\ndescribed as \"various tools and utilities\".\n\n## A crowded settings category gets sub-categories\n\nA settings rail category can hold **sub-categories**: headings inside the category that\ngather its sections. Declare them INSIDE the category's group, as its `subGroups` (each with a\n`groupRef`, a `purpose` and an `order`), and place a section under one with `subGroupRef` on the\nsection's address (beside the `groupRef` that names the category). A sub-category's ref is scoped\nto its category, so two categories can each have a `people` sub-category.\n\nWhen to use them:\n\n- **Group a category of more than about eight sections.** Below that, a flat list is found\n faster than a heading and the list under it. Above it, people scan for a heading first.\n- **Start from the engine's proposal.** People · Billing & entitlements · Security & access ·\n Integrations · Compliance · AI is what a new application is scaffolded with, for both the\n organization and the administration categories. Using the same headings in both lets the\n same kind of surface sit under the same heading in each. Depart from it when this\n application's sections answer different questions, and say why in the purpose.\n- **Leave a category's general entries ungrouped.** The entries that name the scope itself\n (its general settings, the directory of its members' organizations) sit directly in the\n category, above the sub-categories: omit `subGroupRef` on them.\n- **One level only.** A sub-category has no sub-categories of its own; the plan cannot express\n one. Depth discipline applies: a heading inside a heading inside a category is a section\n nobody finds.\n- **A sub-category is a group, so it carries a `purpose`** like any other, and it must have\n something placed in it.\n\n## Placing an operator surface commits the application to an AUDIENCE — say which\n\nSome subjects exist for whoever OPERATES the product rather than for the people who use it:\napplication-wide single sign-on, the application's own API keys and OAuth clients, the\nentitlement state of every tenant, the plans and prices on sale, the application-wide audit\ntrail. The framework keeps them in a separate preset scope from the end-user surfaces, and it\nkeeps them separate ON PURPOSE — an application may legitimately never render them.\n\n**So placing one is a decision about what this application IS, and the plan must state it.**\nTwo answers, both correct:\n\n- **ONE application.** Operators and users share a frontend and are told apart by their roles.\n Place the operator subjects in their own group — an `administration` category beside the\n account and organization ones — and record that this application composes BOTH preset scopes.\n- **TWO applications.** A separate operator frontend. Decline the operator subjects here, with\n that as the rationale, and they belong to the other application's plan.\n\nState the answer in the plan even when it is the obvious one, because the failure it prevents is\nsilent: an application that places operator subjects while composing only the end-user scope gets\nrail entries that OPEN AND RENDER NOTHING. An operation no composed preset surfaces is\ncallable-from-code with no interface, so the section is not missing and does not error — it is\nblank, and it reads as a slow load or a broken backend rather than as an application that was\nassembled without an audience. Seventeen sections were in exactly that state on the dogfood\napplication before this was written down.\n\nYou are not choosing the composition here — that is a coding task the build lane dispatches\nthrough `settings-placement-authoring`. You are stating WHICH audience the arrangement assumes,\nso the task that follows has something to implement rather than a default to guess.\n\n## What you do NOT do\n\n- **You do not author configuration.** Turning a decision into\n `settings-hub.config.ts` or `app-shell.config.ts` is a coding task the build lane\n dispatches through the `settings-placement-authoring` skill. If you catch yourself\n writing a config key, a file path or a label string, stop.\n- **You do not invent destination refs.** The workspace-truth section lists every engine\n settings destination under **\"Settings destinations the engine ships\"**, with what each\n one shows and its role gating. That list is the whole universe: a ref outside it is an\n `UNKNOWN_SUBJECT` and the validator REFUSES the plan — a hard floor, not a warning. Rule\n on all of them where you can; a destination your plan says nothing about is reported\n undecided.\n- **You do not decide what a destination MEANS.** Its target, roles and entitlement\n are the engine's. You decide only where it sits.\n- **You do not re-open the build plan.** What is being built is settled.\n\n## Verification\n\n- Every subject the workspace offers is either PLACED or DECLINED — nothing omitted.\n- No subject placed twice on one surface.\n- No business concept on the sidebar twice: a concept held in two resources (read through and\n copied) has its view on the sidebar and each of its lists on the command menu, none declined.\n- No application view placed on the settings rail or the user dropdown.\n- Every grouped placement names a group this plan declares, for that same surface.\n- Every `subGroupRef` names a sub-category this plan declares under that placement's category.\n- Sub-categories are declared only on `SETTINGS_HUB` categories, each ref once per category.\n- Every group, sub-categories included, has something in it.\n- Every decision, both arms, carries a rationale that would satisfy a reader who\n disagrees with it.\n- The plan states which AUDIENCE it assumes — one application or two — whenever it places or\n declines an operator subject.\n\n## WHO decides — a panel, not you alone and not the creator\n\n**The creator does not choose placement.** This playbook convenes an expert panel and\ntakes its winner.\n\nConcretely, on every run: three candidate arrangements are generated independently\nagainst this brief, each schema-valid before anyone sees it and each told to take a\ngenuinely different position; the **information-architect** derives the rubric (it\nowns the domain); it and the **design-system-guardian** review every candidate; the\nguardian coordinates, shortlists, and synthesises a winner. What lands is that winner.\n\nTwo consequences for how you write:\n\n- **Take a position and commit to it.** You are one candidate among three, and the\n panel cannot compare three hedged arrangements. State what your arrangement makes\n WORSE — an arrangement with no cost has not been thought about, and the reviewers\n are instructed to notice.\n- **The rationale on each decision is the durable part.** It is what a creator asking\n \"why is Billing under Organization?\" reads, and it is the only trace of the argument\n once the winner has landed.\n\n**Fail-closed on charters.** Every panel role needs a committed charter, and the\ncompanion indexes agents at startup — a charter accepted after boot has no agent until\na restart, and the error says exactly that. The run does NOT quietly degrade to a\nsingle generation: an artifact carrying a panel's authority over a decision no panel\nsaw is the worst outcome available here, so fewer than two usable candidates returns\nto the ordinary retry instead.\n\n## And when the placement is wrong\n\nTwo different things can change, and conflating them is how a plan starts lying.\n\n**The config file** — `settings-hub.config.ts`, `app-shell.config.ts` — is what actually\nrenders. A creator who disagrees edits it directly. That works today, needs no companion,\nand is a git commit, which is the accepted state.\n\n**The plan** is the decision record, and it is what a later reader consults to ask why.\nIt can be changed two ways:\n\n- **Re-run this playbook.** The panel deliberates again and the landing REPLACES the\n existing file. Nothing refuses it; that is the design.\n- **Edit the landed plan.** It is an application-owned source like any other.\n\nEither way, a decision that no longer reflects the panel must say so. Set its `origin`\nto `REVISED` and record what the panel had decided in `supersedes.rationale`. Both are\nrequired together — the schema refuses a `REVISED` decision with nothing superseded, and\nrefuses a `DELIBERATED` one that supersedes something, because no panel run produces\neither shape.\n\n**Why the artifact carries this when git already records the change.** Git knows who\nchanged the line, when, and with what message, and that is not being duplicated here. What\ngit cannot tell someone READING the file — in an editor, asking \"why is Billing under\nAccount?\" — is that this particular decision is no longer the panel's. Without it, the\n`rationale` field goes on asserting panel reasoning for a decision the panel never took,\nand there is no way to notice.\n\nDo not paraphrase the panel's rationale into the new one. A `supersedes.rationale` that\nrepeats the decision's own text word for word satisfies the schema and tells a reader\nnothing; the validator reports it as an authoring warning.\n",
|
|
42
48
|
"skillRefs": [
|
|
43
49
|
"settings-placement-authoring",
|
|
44
50
|
"config-app-shell",
|
|
45
51
|
"config-navigation"
|
|
46
52
|
],
|
|
47
53
|
"skillBodyRefs": [],
|
|
54
|
+
"derivedFromAnswers": [],
|
|
48
55
|
"contextSources": [
|
|
49
56
|
"workspace_truth",
|
|
50
57
|
"creator_stated_facts",
|
|
@@ -12,16 +12,21 @@ Read and apply these patterns from the application-developer point of view:
|
|
|
12
12
|
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
13
13
|
|
|
14
14
|
|
|
15
|
-
This playbook IS the creation of the application. It produces nothing itself: it
|
|
16
|
-
four lanes, each of which drives its own leaves, and it ends
|
|
17
|
-
the application is against its own requirements — a stage,
|
|
15
|
+
This playbook IS the creation of the application. It produces nothing itself: it runs
|
|
16
|
+
the vision interview, drives four lanes, each of which drives its own leaves, and it ends
|
|
17
|
+
on a reading of how mature the application is against its own requirements — a stage,
|
|
18
|
+
never a "done".
|
|
18
19
|
|
|
19
20
|
## The lanes, and why the order is not written here
|
|
20
21
|
|
|
21
|
-
- **`top_down.
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
22
|
+
- **`top_down.vision-elicitation`** — not a lane but the vision interview itself, from the
|
|
23
|
+
creator's answers. Opens on an empty application, and on an empty application it is the
|
|
24
|
+
only thing that can run: both lanes that follow need the vision, so it lands in a round
|
|
25
|
+
of its own and they start together.
|
|
26
|
+
- **`top_down.definition`** — what the application IS: the market and its evidence, the
|
|
27
|
+
value proposition, the requirements, the capability map, the business model, the
|
|
28
|
+
roadmap, and the phase gate that judges their coherence. Brand identity and the risk
|
|
29
|
+
register run beside the chain. Opens on a valid vision.
|
|
25
30
|
- **`cross_cutting.compliance`** — which regimes apply and what the application must be
|
|
26
31
|
able to say: the posture from researched evidence, the assurance programme, the facts
|
|
27
32
|
read from the product, and the drafted governed documents. Opens on a valid vision, so
|
|
@@ -40,11 +45,21 @@ whatever is not.
|
|
|
40
45
|
|
|
41
46
|
## Selecting the next lane
|
|
42
47
|
|
|
43
|
-
- **
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
+
- **The vision first, alone.** When the application has no vision, the interview is the
|
|
49
|
+
only thing on offer: run it. Once it has landed, the definition and compliance lanes are
|
|
50
|
+
both on offer, and they belong in the same round.
|
|
51
|
+
- **Up to two lanes per round.** A round waits for both of its lanes, so pick two that do
|
|
52
|
+
not write the same work. Compliance pairs with any other lane, and the definition with the
|
|
53
|
+
conception or the build. The conception lane and the build do not pair, and the vision
|
|
54
|
+
interview, when the creator's answers change, does not pair with the definition lane.
|
|
55
|
+
- **The build lane, whenever it can dispatch.** While the build plan has tasks that are
|
|
56
|
+
ready, or that only wait on a staffing repair, the build lane is one of the round's
|
|
57
|
+
two. Leaving it out leaves the build idle for the whole round.
|
|
58
|
+
- **Furthest first, for the other slot.** Choose the lane that can advance the
|
|
59
|
+
application most from what is on record, and prefer a lane waiting on nothing to one
|
|
60
|
+
waiting on the creator.
|
|
61
|
+
- **Do not re-select a lane that has just landed,** except the build lane while tasks
|
|
62
|
+
remain to dispatch. The round history says what ran.
|
|
48
63
|
- **A lane that stopped because the creator owes it an answer is a real stop.** Say so
|
|
49
64
|
in the rationale rather than re-selecting it.
|
|
50
65
|
|
|
@@ -1,13 +1,17 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "cross_cutting.application-creation",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.3.0",
|
|
4
4
|
"phase": "cross_cutting",
|
|
5
|
-
"intent": "Create the application: drive the definition (
|
|
5
|
+
"intent": "Create the application: elicit the vision, then drive the definition (market, requirements, capabilities, business model, roadmap, phase gate), the compliance posture and its governed documents, the conception (domain plan, foundation, placement) and the build (decompose, dispatch, assemble) as four LANES, each of which drives its own leaves. An umbrella over umbrellas: it authors nothing itself, and the order between the lanes is decided by their own preconditions against the working tree rather than declared here — on a fresh application only the vision interview can run, and it runs alone; the definition and compliance lanes both open on a valid vision and run side by side, conception opens once requirements and the market snapshot are on record, the build once the domain and placement plans are. Select up to TWO lanes per round whose work does not overlap: while the build lane can dispatch a task, it is always one of them, and the other is the lane that can advance the application furthest (compliance pairs with any lane). Prefer a lane that is waiting on nothing to one waiting on the creator. Do not re-select a lane that has just landed its families, except the build lane while tasks remain to dispatch. STOP when no lane can advance the application — that is a STAGE the maturity reading names, never a finished application.",
|
|
6
6
|
"preconditions": [],
|
|
7
7
|
"inputs": [
|
|
8
8
|
{
|
|
9
9
|
"family": "vision-brief"
|
|
10
10
|
},
|
|
11
|
+
{
|
|
12
|
+
"family": "compliance-posture",
|
|
13
|
+
"render": "map"
|
|
14
|
+
},
|
|
11
15
|
{
|
|
12
16
|
"family": "market-snapshot",
|
|
13
17
|
"render": "map"
|
|
@@ -40,9 +44,10 @@
|
|
|
40
44
|
"outputs": [],
|
|
41
45
|
"stepOutputs": [],
|
|
42
46
|
"method": {
|
|
43
|
-
"guidance": "# Creating the application — the root\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\nThis playbook IS the creation of the application. It produces nothing itself: it
|
|
47
|
+
"guidance": "# Creating the application — the root\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\nThis playbook IS the creation of the application. It produces nothing itself: it runs\nthe vision interview, drives four lanes, each of which drives its own leaves, and it ends\non a reading of how mature the application is against its own requirements — a stage,\nnever a \"done\".\n\n## The lanes, and why the order is not written here\n\n- **`top_down.vision-elicitation`** — not a lane but the vision interview itself, from the\n creator's answers. Opens on an empty application, and on an empty application it is the\n only thing that can run: both lanes that follow need the vision, so it lands in a round\n of its own and they start together.\n- **`top_down.definition`** — what the application IS: the market and its evidence, the\n value proposition, the requirements, the capability map, the business model, the\n roadmap, and the phase gate that judges their coherence. Brand identity and the risk\n register run beside the chain. Opens on a valid vision.\n- **`cross_cutting.compliance`** — which regimes apply and what the application must be\n able to say: the posture from researched evidence, the assurance programme, the facts\n read from the product, and the drafted governed documents. Opens on a valid vision, so\n it runs beside the definition rather than after it.\n- **`bottom_up.conception`** — the structure: the domain plan, the expert charters that\n staff the panels, the composed foundation, the placement plan. Opens once the\n requirements and the market snapshot are on record.\n- **`bottom_up.build`** — the application itself: the build plan, the dispatch of its\n tasks, the assembly check, and the maturity reading it ends on. Opens once the domain\n and placement plans are on record.\n\nNothing above is a sequence. Each lane declares what it needs and the runtime re-reads\nthe tree after every round; that is the waterfall, and it is why this playbook can be\nrun again on an application at any stage — whatever is on record satisfies the gates of\nwhatever is not.\n\n## Selecting the next lane\n\n- **The vision first, alone.** When the application has no vision, the interview is the\n only thing on offer: run it. Once it has landed, the definition and compliance lanes are\n both on offer, and they belong in the same round.\n- **Up to two lanes per round.** A round waits for both of its lanes, so pick two that do\n not write the same work. Compliance pairs with any other lane, and the definition with the\n conception or the build. The conception lane and the build do not pair, and the vision\n interview, when the creator's answers change, does not pair with the definition lane.\n- **The build lane, whenever it can dispatch.** While the build plan has tasks that are\n ready, or that only wait on a staffing repair, the build lane is one of the round's\n two. Leaving it out leaves the build idle for the whole round.\n- **Furthest first, for the other slot.** Choose the lane that can advance the\n application most from what is on record, and prefer a lane waiting on nothing to one\n waiting on the creator.\n- **Do not re-select a lane that has just landed,** except the build lane while tasks\n remain to dispatch. The round history says what ran.\n- **A lane that stopped because the creator owes it an answer is a real stop.** Say so\n in the rationale rather than re-selecting it.\n\n## Composing an objective for a lane\n\nName what the application already holds and what this lane should add — \"the vision and\nmarket are on record, the requirements are not; take the definition through to the phase\ngate\". A later round names what changed: \"the domain plan moved; re-open the document\nfacts that were derived from it\".\n\n## When to stop\n\nStop when no lane can advance the application from what is on record. **That is a\nSTAGE, not a finished application** — the maturity reading is what names it, measured\nagainst the application's own requirements, and it moves every time a later run lands\nsomething. Stop also when every remaining lane is waiting on the creator, and say which\nanswers are owed.\n\n## What the creator reviews\n\nOne decision at the end: the work every lane kept, to accept, to revise with a note, or\nto discard. Under the current posture it is notified rather than awaited. Each lane has\nalready ended on its own decision, and each leaf's own review guide still applies to\nwhat it landed.\n",
|
|
44
48
|
"skillRefs": [],
|
|
45
49
|
"skillBodyRefs": [],
|
|
50
|
+
"derivedFromAnswers": [],
|
|
46
51
|
"contextSources": [],
|
|
47
52
|
"draftableDocumentDefinitionRefs": [],
|
|
48
53
|
"choreography": {
|
|
@@ -50,10 +55,11 @@
|
|
|
50
55
|
"bottom_up.build",
|
|
51
56
|
"bottom_up.conception",
|
|
52
57
|
"cross_cutting.compliance",
|
|
53
|
-
"top_down.definition"
|
|
58
|
+
"top_down.definition",
|
|
59
|
+
"top_down.vision-elicitation"
|
|
54
60
|
],
|
|
55
61
|
"maximumIterations": 10,
|
|
56
|
-
"maximumLanesPerIteration":
|
|
62
|
+
"maximumLanesPerIteration": 2,
|
|
57
63
|
"maximumDepth": 3,
|
|
58
64
|
"maximumDurationMs": 86400000,
|
|
59
65
|
"reopenOnVerdict": [
|
|
@@ -23,7 +23,7 @@ marked and notified, never composed by the mechanism.
|
|
|
23
23
|
the product facts that decide which regimes apply (data classes, where the vendor is
|
|
24
24
|
established, jurisdictions, sector, residency), gathers regime evidence from
|
|
25
25
|
authoritative sources, judges whether it is enough, and records the applicable regimes
|
|
26
|
-
|
|
26
|
+
in the `compliance-posture` family only once it is. Its evidence loop and its interview are
|
|
27
27
|
its own; this lane sees only that a posture landed.
|
|
28
28
|
- **`top_down.compliance-conception`** — the assurance programme, the publication
|
|
29
29
|
specification and the release policy, from the posture. Asks one question.
|
|
@@ -41,8 +41,8 @@ the facts need the domain plan; the drafters expect the facts.
|
|
|
41
41
|
|
|
42
42
|
## Two halves, and the lane may stop between them
|
|
43
43
|
|
|
44
|
-
The lane is eligible on a vision alone, on purpose: the
|
|
45
|
-
|
|
44
|
+
The lane is eligible on a vision alone, on purpose: the posture needs nothing else, so
|
|
45
|
+
it can land before conception has run. On
|
|
46
46
|
an application whose domain plan is not yet on record, land the posture and the
|
|
47
47
|
conception, then stop — the lane resumes once the conception lane has landed the plan,
|
|
48
48
|
and the first round then offers the facts.
|
|
@@ -78,6 +78,6 @@ gap twice and a further round could not close it. Say which, in the rationale.
|
|
|
78
78
|
|
|
79
79
|
## What the creator reviews
|
|
80
80
|
|
|
81
|
-
The posture
|
|
81
|
+
The compliance posture, the programme, the facts, and each drafted document with its
|
|
82
82
|
marked statements — and the release decision: a legally-binding statement leaving the
|
|
83
83
|
system, notified under the current posture and awaited once Gate 3 arms it.
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
"ref": "cross_cutting.compliance",
|
|
3
3
|
"version": "0.1.0",
|
|
4
4
|
"phase": "cross_cutting",
|
|
5
|
-
"intent": "Drive the COMPLIANCE of the application as one lane: the posture (regime evidence, judged adequate, recorded
|
|
5
|
+
"intent": "Drive the COMPLIANCE of the application as one lane: the posture (regime evidence, judged adequate, recorded in the compliance-posture family), the compliance conception (the programme, the publication and release policies), the document facts read from the product, and the drafted governed documents — public and governance — ending on one decision: the document release, marked and notified. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round. Select what is MISSING from the accepted truth shown to you, in the order the chain implies: the posture before the conception, the facts before the candidates, and never a candidate re-drafted while its facts are unchanged. The posture half needs only the vision; the facts need a valid domain plan — when it is not on record, land the posture and the conception and STOP: the lane resumes when the conception lane has landed the plan. STOP when the candidates are drafted: the release is this lane's closing decision. A child whose interview the creator has not answered is not offered; run everything else and stop when nothing eligible advances the compliance.",
|
|
6
6
|
"preconditions": [
|
|
7
7
|
{
|
|
8
8
|
"kind": "artifact_valid",
|
|
@@ -15,6 +15,10 @@
|
|
|
15
15
|
{
|
|
16
16
|
"family": "vision-brief"
|
|
17
17
|
},
|
|
18
|
+
{
|
|
19
|
+
"family": "compliance-posture",
|
|
20
|
+
"render": "map"
|
|
21
|
+
},
|
|
18
22
|
{
|
|
19
23
|
"family": "domain-plan",
|
|
20
24
|
"render": "map"
|
|
@@ -37,9 +41,10 @@
|
|
|
37
41
|
"outputs": [],
|
|
38
42
|
"stepOutputs": [],
|
|
39
43
|
"method": {
|
|
40
|
-
"guidance": "# The Compliance Lane — the umbrella\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\nThis playbook produces nothing itself. It drives the steps that establish the\napplication's COMPLIANCE — the posture, the programme, the facts, the governed\ndocuments — and it ends on the document release, which is the lane's closing decision:\nmarked and notified, never composed by the mechanism.\n\n## The children, and why the order is not written here\n\n- **`top_down.compliance-analysis`** — a NESTED LANE, not a leaf: it asks the creator\n the product facts that decide which regimes apply (data classes, where the vendor is\n established, jurisdictions, sector, residency), gathers regime evidence from\n authoritative sources, judges whether it is enough, and records the applicable regimes\n
|
|
44
|
+
"guidance": "# The Compliance Lane — the umbrella\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\nThis playbook produces nothing itself. It drives the steps that establish the\napplication's COMPLIANCE — the posture, the programme, the facts, the governed\ndocuments — and it ends on the document release, which is the lane's closing decision:\nmarked and notified, never composed by the mechanism.\n\n## The children, and why the order is not written here\n\n- **`top_down.compliance-analysis`** — a NESTED LANE, not a leaf: it asks the creator\n the product facts that decide which regimes apply (data classes, where the vendor is\n established, jurisdictions, sector, residency), gathers regime evidence from\n authoritative sources, judges whether it is enough, and records the applicable regimes\n in the `compliance-posture` family only once it is. Its evidence loop and its interview are\n its own; this lane sees only that a posture landed.\n- **`top_down.compliance-conception`** — the assurance programme, the publication\n specification and the release policy, from the posture. Asks one question.\n- **`refinement.document-facts`** — the facts a governed document rests on, READ FROM\n THE PRODUCT (the resource configurations, the declared identity). Needs a valid\n domain plan.\n- **`refinement.compliance-document-candidate`** — the public documents (privacy\n notice, service terms), drafted from the facts.\n- **`refinement.governance-document-candidate`** — the governance documents, drafted\n from the facts and the assurance evidence.\n\nNothing above is a sequence. Each child declares what it needs and the runtime\nre-computes what may run after every round. The posture half needs only the vision;\nthe facts need the domain plan; the drafters expect the facts.\n\n## Two halves, and the lane may stop between them\n\nThe lane is eligible on a vision alone, on purpose: the posture needs nothing else, so\nit can land before conception has run. On\nan application whose domain plan is not yet on record, land the posture and the\nconception, then stop — the lane resumes once the conception lane has landed the plan,\nand the first round then offers the facts.\n\n## Selecting the next children\n\n- **The chain's order, stated as a preference the gates do not enforce.** The runner\n admits a child past a sequencing expectation inside a lane, so the drafters are\n offered before the facts land. Land the facts first. A document drafted without them\n marks what it could not establish and is re-drafted when they land — honest, and the\n weaker document.\n- **Missing beats present.** A drafted candidate is not re-drafted while its facts are\n unchanged; a landed posture is not re-recorded while the vision is unchanged.\n- **Independent children share a round.** The two drafters read the same facts and can\n run beside each other; several research lanes with different jurisdictions in their\n objectives return more than one asked everything.\n- **A child waiting on the creator is not offered** — which for this lane means the\n posture umbrella, until its product-fact questions are answered. The document half\n needs the domain plan rather than the jurisdictions, so it runs meanwhile.\n\n## Composing an objective for a child\n\nFor research, the umbrella's rule: the first round aimed at the jurisdictions and data\nclasses the creator named, a later round at the gap the gate named. For the drafters,\nname the documents the publication specification declares and the facts on record.\n\n## When to stop\n\nStop when the candidates are drafted: the release is the decision this lane ends on.\nStop when the domain plan is not on record and the posture and the conception are —\nthe second half waits on another lane. Stop when the evidence gate has named the same\ngap twice and a further round could not close it. Say which, in the rationale.\n\n## What the creator reviews\n\nThe compliance posture, the programme, the facts, and each drafted document with its\nmarked statements — and the release decision: a legally-binding statement leaving the\nsystem, notified under the current posture and awaited once Gate 3 arms it.\n",
|
|
41
45
|
"skillRefs": [],
|
|
42
46
|
"skillBodyRefs": [],
|
|
47
|
+
"derivedFromAnswers": [],
|
|
43
48
|
"contextSources": [],
|
|
44
49
|
"draftableDocumentDefinitionRefs": [],
|
|
45
50
|
"choreography": {
|
|
@@ -44,6 +44,7 @@
|
|
|
44
44
|
"guidance": "# The feature-development line — the umbrella\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\nThis playbook produces nothing itself. It develops ONE feature, the one the line was opened for (see \"What\nthis run is for\"), beside the application's main line, and through the product model: the feature is\nwritten down as requirements and drafts first, and everything built from those is re-derived from them.\n\n## The children\n\n- **`refinement.feature-contribution`** — adds the feature to the requirements and the feature drafts, as\n this line's own elements. Nothing it returns replaces what the application already holds.\n- **`bottom_up.domain-plan`** — the application's domain plan, re-derived from requirements that now hold\n the feature. It runs for the whole application, not for this line.\n- **`bottom_up.experience-plan`** — the screens and journeys, re-derived the same way, when the feature\n changes what a person sees.\n- **`bottom_up.build`** — the build lane: it decomposes the changed plan into tasks and dispatches them to\n the coding agent. A long lane with its own rounds.\n\n## Choosing\n\nNothing above is a sequence the runtime enforces; each child declares what it needs. Read what exists:\n\n- If the requirements do not yet hold this feature, run the feature contribution. Nothing downstream can\n reflect a feature the requirements do not name.\n- Once they do, the domain plan is out of date with respect to them: re-derive it.\n- Then the experience plan, if the feature has anything a person sees.\n- Then the build.\n\nStop when the feature is built, or when no eligible child advances it. Do not re-run the contribution to\n\"improve\" a feature that has landed: a refinement of the feature is a new run of this line, asked for by\nthe person who opened it.\n",
|
|
45
45
|
"skillRefs": [],
|
|
46
46
|
"skillBodyRefs": [],
|
|
47
|
+
"derivedFromAnswers": [],
|
|
47
48
|
"contextSources": [],
|
|
48
49
|
"draftableDocumentDefinitionRefs": [],
|
|
49
50
|
"choreography": {
|
|
@@ -23,14 +23,14 @@ Each child re-derives one whole family for the application. They come in two kin
|
|
|
23
23
|
|
|
24
24
|
- **What can be refined** (what the line may name), each from its own prior output: the vision, the
|
|
25
25
|
requirements, the feature drafts, the value proposition and the capability map (both refine the market),
|
|
26
|
-
the roadmap, the brand
|
|
27
|
-
plan (`bottom_up.build-decompose`).
|
|
26
|
+
the roadmap, the brand, the business model, the risk register and the service method; the domain,
|
|
27
|
+
experience, integration, website and documentation plans, and the build plan (`bottom_up.build-decompose`).
|
|
28
28
|
- **What can only be refreshed**, re-derived from its inputs when a refinement made it stale: the placement
|
|
29
|
-
plan, the capability composition, the
|
|
30
|
-
governed documents, and the expert staffing (`top_down.expert-personas`), which staffs a panel role whose
|
|
31
|
-
inputs the refinement has just landed and leaves every committed charter alone.
|
|
29
|
+
plan, the capability composition, the document facts and the governed documents.
|
|
32
30
|
- **`bottom_up.build`** — the build lane: it decomposes the changed plan into tasks and dispatches them to
|
|
33
|
-
the coding agent. A long lane with its own rounds.
|
|
31
|
+
the coding agent. A long lane with its own rounds. It also runs the expert staffing
|
|
32
|
+
(`top_down.expert-personas`) when a change made a panel's charters stale, so the staffing is not a child
|
|
33
|
+
of its own here.
|
|
34
34
|
|
|
35
35
|
## Choosing
|
|
36
36
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "cross_cutting.refinement",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.3",
|
|
4
4
|
"phase": "cross_cutting",
|
|
5
5
|
"intent": "Refine what this line was opened for: re-derive each named family from what it already holds, guided by the purpose, then refresh what that made out of date and build it. An umbrella: it authors nothing itself. The first move is fixed: the producers of the named families. After that, select only children whose outputs are STALE, upstream before downstream, the build last. STOP when nothing is stale any more and the build has run, or when nothing eligible advances the refinement.",
|
|
6
6
|
"preconditions": [
|
|
@@ -39,9 +39,10 @@
|
|
|
39
39
|
"outputs": [],
|
|
40
40
|
"stepOutputs": [],
|
|
41
41
|
"method": {
|
|
42
|
-
"guidance": "# The refinement line — the umbrella\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\nThis playbook produces nothing itself. It refines what the line was opened for (see \"What this run is for\",\nwhich names the purpose and the families to refine), beside the application's main line. A refinement\nre-derives a family the application ALREADY holds, from what it already says: keep what still holds, change\nwhat the purpose asks, and do not re-author the rest.\n\n## The children\n\nEach child re-derives one whole family for the application. They come in two kinds:\n\n- **What can be refined** (what the line may name), each from its own prior output: the vision, the\n requirements, the feature drafts, the value proposition and the capability map (both refine the market),\n the roadmap, the brand; the domain
|
|
42
|
+
"guidance": "# The refinement line — the umbrella\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\nThis playbook produces nothing itself. It refines what the line was opened for (see \"What this run is for\",\nwhich names the purpose and the families to refine), beside the application's main line. A refinement\nre-derives a family the application ALREADY holds, from what it already says: keep what still holds, change\nwhat the purpose asks, and do not re-author the rest.\n\n## The children\n\nEach child re-derives one whole family for the application. They come in two kinds:\n\n- **What can be refined** (what the line may name), each from its own prior output: the vision, the\n requirements, the feature drafts, the value proposition and the capability map (both refine the market),\n the roadmap, the brand, the business model, the risk register and the service method; the domain,\n experience, integration, website and documentation plans, and the build plan (`bottom_up.build-decompose`).\n- **What can only be refreshed**, re-derived from its inputs when a refinement made it stale: the placement\n plan, the capability composition, the document facts and the governed documents.\n- **`bottom_up.build`** — the build lane: it decomposes the changed plan into tasks and dispatches them to\n the coding agent. A long lane with its own rounds. It also runs the expert staffing\n (`top_down.expert-personas`) when a change made a panel's charters stale, so the staffing is not a child\n of its own here.\n\n## Choosing\n\n- **The first rounds are fixed.** While a family this line names has not been re-derived, you are offered\n only its producers, upstream ones first. Pass the purpose on in the child's objective, in the person's\n terms: it is what the refinement must change.\n- **Then refresh what the change made stale, and nothing else.** Each eligible child shows the outputs that\n are stale and the inputs they wait on. Refresh a family only when it is stale, and its own stale inputs\n first: the requirements before the domain plan, the domain plan before the experience plan, a plan before\n the build plan.\n- **Build last**, once the plans the change touched are current.\n- **Stop** when nothing is stale any more and the build has run, or when no eligible child advances the\n refinement. Do not re-run a named family's producer to \"improve\" it further: a further refinement is a new\n run of this line, asked for by the person who opened it.\n",
|
|
43
43
|
"skillRefs": [],
|
|
44
44
|
"skillBodyRefs": [],
|
|
45
|
+
"derivedFromAnswers": [],
|
|
45
46
|
"contextSources": [],
|
|
46
47
|
"draftableDocumentDefinitionRefs": [],
|
|
47
48
|
"choreography": {
|
|
@@ -61,7 +62,6 @@
|
|
|
61
62
|
"top_down.compliance-conception",
|
|
62
63
|
"top_down.risk-register",
|
|
63
64
|
"top_down.service-method",
|
|
64
|
-
"top_down.expert-personas",
|
|
65
65
|
"top_down.business-model",
|
|
66
66
|
"top_down.brand-identity",
|
|
67
67
|
"top_down.scope-roadmap",
|
|
@@ -91,7 +91,6 @@
|
|
|
91
91
|
"top_down.compliance-conception",
|
|
92
92
|
"top_down.risk-register",
|
|
93
93
|
"top_down.service-method",
|
|
94
|
-
"top_down.expert-personas",
|
|
95
94
|
"top_down.business-model",
|
|
96
95
|
"top_down.brand-identity",
|
|
97
96
|
"top_down.scope-roadmap",
|
package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"aggregationPolicyRef":"application-creation:aggregation/worst-compliance-document-claims-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/compliance-document-claims-within-guard","criterionVersion":
|
|
1
|
+
{"aggregationPolicyRef":"application-creation:aggregation/worst-compliance-document-claims-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/compliance-document-claims-within-guard","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-document-claims-within-guard","requirementVersion":1}],"instruction":"The subject under judgment is each landed `compliance-document-candidate`. For EVERY clause, find the catalog claim guards it names in `claimGuardRefs` in the \"Catalog claim guards\" section of the evidence. A clause's `claimGuardRefs` mixes TWO vocabularies and only one is defined anywhere: a `document-claim-guard:` ref is the CATALOG's, added from the blueprint clauses the clause satisfies, and the evidence section carries its prohibited claims and reviewer instruction. A bare `claim-guard:` ref is the DRAFTER'S OWN statement of what its clause must not be read as claiming; no catalog defines it and none will be supplied. Read it as context about the clause's intent, and NEVER answer INDETERMINATE because its definition is absent — that is not missing evidence, it is a vocabulary that has no definitions, and read the clause's `bodyMarkdown` against each guard's prohibited claims and reviewer instruction. Look for: a claim of certification, attestation or audit without the authority to make it; a legal conclusion or legal advice (\"you are protected\", \"this is lawful\") rather than a statement of what the operator does; a NIST publication presented as legal equivalence; OPERATING EFFECTIVENESS — a sentence asserting that a control operates, works or worked (\"we monitor\", \"we detect\", \"access is always reviewed\") rather than that something is configured or declared; self-attestation presented as independent assurance; and an unscoped compliance claim (\"GDPR compliant\", \"fully secure\"). In a document whose guard names `document-claim-policy:public-safe-baseline`, an operating-effectiveness assertion is prohibited, with ONE exception (decided 2026-11-06, #3343): a statement of what the application's OWN RECORDS show, taken from a fact the runtime computes from records (`retention-enforcement`, `ai-content-guardrails`) and scoped to that fact's observation (\"as of <date>\", \"in the window <from>–<to>\"), is permitted, because it reports a record rather than the operator's judgement. Still prohibited in a public document: such a statement with no date or window, one that generalizes beyond it (\"runs on every call\", \"is always enforced\"), one that reads a quiet window as having run or as not having run, and any assertion resting on a judged run or an evidence citation. Do NOT re-check whether cited facts exist — landing already decided that exactly. Name every finding by its `clauseRef`, quote the words, and name the prohibited claim it falls under. Separate severities by CONSEQUENCE: a prohibited claim a reader of the published document would rely on is a GAP; wording that leans toward one without asserting it is a CONCERN.","schemaVersion":1,"verdictGuidance":{"CONCERN":"No prohibited claim is asserted, but wording leans toward one in a way a reader could take as the claim — a softened operating assertion, a scope left implicit. Name each clauseRef and quote it.","GAP":"At least one clause asserts a prohibited claim a reader would rely on. Name each clauseRef, quote the words, and name the prohibited claim.","INDETERMINATE":"The CATALOG guards of the drafted documents are absent from the evidence, or a document has no catalog guard at all, so the clauses cannot be judged against what they must not claim. Say which. A clause-level `claim-guard:` ref having no definition is NOT this: that vocabulary has none anywhere.","PASS":"No clause asserts a prohibited claim: nothing certifies, concludes the law, equates NIST with law, asserts a control operates in a public document, presents self-attestation as independence, or claims unscoped compliance."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/compliance-document-claims","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:refinement.compliance-document-candidate"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
|
package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json
CHANGED
|
@@ -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-compliance-document-candidate","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/compliance-document-claims-within-guard"],"requirementRef":"application-creation:authority-requirement/compliance-document-claims","requirementVersion":1,"riskClassRef":"application-creation:risk/compliance-claim-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/compliance-document-claims","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/compliance-document-claims","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/compliance-document-claims","policyVersion":1},"decisionPointRef":"application-creation:decision-point/compliance-document-claims","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/compliance-document-claims","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/compliance-document-claims","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-document-claims-within-guard","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/compliance-document-candidate-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/compliance-document-change","triggerRefs":["application-creation:trigger/compliance-document-candidate-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-compliance-document-claims-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/compliance-document-claims-within-guard"],"hardFloorRef":"application-creation:hard-floor/compliance-document-candidate-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/compliance-document-claims","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/compliance-document-claims","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-compliance-document-claims-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/compliance-document-claims-within-guard","criterionVersion":
|
|
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-compliance-document-candidate","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/compliance-document-claims-within-guard"],"requirementRef":"application-creation:authority-requirement/compliance-document-claims","requirementVersion":1,"riskClassRef":"application-creation:risk/compliance-claim-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/compliance-document-claims","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/compliance-document-claims","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/compliance-document-claims","policyVersion":1},"decisionPointRef":"application-creation:decision-point/compliance-document-claims","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/compliance-document-claims","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/compliance-document-claims","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-document-claims-within-guard","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/compliance-document-candidate-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/compliance-document-change","triggerRefs":["application-creation:trigger/compliance-document-candidate-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-compliance-document-claims-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/compliance-document-claims-within-guard"],"hardFloorRef":"application-creation:hard-floor/compliance-document-candidate-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/compliance-document-claims","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/compliance-document-claims","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-compliance-document-claims-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/compliance-document-claims-within-guard","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-document-claims-within-guard","requirementVersion":1}],"instruction":"The subject under judgment is each landed `compliance-document-candidate`. For EVERY clause, find the catalog claim guards it names in `claimGuardRefs` in the \"Catalog claim guards\" section of the evidence. A clause's `claimGuardRefs` mixes TWO vocabularies and only one is defined anywhere: a `document-claim-guard:` ref is the CATALOG's, added from the blueprint clauses the clause satisfies, and the evidence section carries its prohibited claims and reviewer instruction. A bare `claim-guard:` ref is the DRAFTER'S OWN statement of what its clause must not be read as claiming; no catalog defines it and none will be supplied. Read it as context about the clause's intent, and NEVER answer INDETERMINATE because its definition is absent — that is not missing evidence, it is a vocabulary that has no definitions, and read the clause's `bodyMarkdown` against each guard's prohibited claims and reviewer instruction. Look for: a claim of certification, attestation or audit without the authority to make it; a legal conclusion or legal advice (\"you are protected\", \"this is lawful\") rather than a statement of what the operator does; a NIST publication presented as legal equivalence; OPERATING EFFECTIVENESS — a sentence asserting that a control operates, works or worked (\"we monitor\", \"we detect\", \"access is always reviewed\") rather than that something is configured or declared; self-attestation presented as independent assurance; and an unscoped compliance claim (\"GDPR compliant\", \"fully secure\"). In a document whose guard names `document-claim-policy:public-safe-baseline`, an operating-effectiveness assertion is prohibited, with ONE exception (decided 2026-11-06, #3343): a statement of what the application's OWN RECORDS show, taken from a fact the runtime computes from records (`retention-enforcement`, `ai-content-guardrails`) and scoped to that fact's observation (\"as of <date>\", \"in the window <from>–<to>\"), is permitted, because it reports a record rather than the operator's judgement. Still prohibited in a public document: such a statement with no date or window, one that generalizes beyond it (\"runs on every call\", \"is always enforced\"), one that reads a quiet window as having run or as not having run, and any assertion resting on a judged run or an evidence citation. Do NOT re-check whether cited facts exist — landing already decided that exactly. Name every finding by its `clauseRef`, quote the words, and name the prohibited claim it falls under. Separate severities by CONSEQUENCE: a prohibited claim a reader of the published document would rely on is a GAP; wording that leans toward one without asserting it is a CONCERN.","schemaVersion":1,"verdictGuidance":{"CONCERN":"No prohibited claim is asserted, but wording leans toward one in a way a reader could take as the claim — a softened operating assertion, a scope left implicit. Name each clauseRef and quote it.","GAP":"At least one clause asserts a prohibited claim a reader would rely on. Name each clauseRef, quote the words, and name the prohibited claim.","INDETERMINATE":"The CATALOG guards of the drafted documents are absent from the evidence, or a document has no catalog guard at all, so the clauses cannot be judged against what they must not claim. Say which. A clause-level `claim-guard:` ref having no definition is NOT this: that vocabulary has none anywhere.","PASS":"No clause asserts a prohibited claim: nothing certifies, concludes the law, equates NIST with law, asserts a control operates in a public document, presents self-attestation as independence, or claims unscoped compliance."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/compliance-document-claims","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:refinement.compliance-document-candidate"},"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/compliance-document-claims","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-catalog-claim-guards-of-drafted-documents","criterionRef":"application-creation:criterion/compliance-document-claims-within-guard","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-document-claims-within-guard","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/compliance-document-candidates-and-catalog-claim-guards"}],"schemaVersion":1}
|