@wildo-ai/framework-knowledge 1.1.4 → 1.1.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/claude-marketplace/.claude-plugin/marketplace.json +14 -0
- package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +8 -0
- package/dist/claude-marketplace/plugins/wildo/agents/wildo-deriver.md +41 -0
- package/dist/claude-marketplace/plugins/wildo/hooks/hooks.json +18 -0
- package/dist/claude-marketplace/plugins/wildo/monitors/monitors.json +8 -0
- package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +38 -0
- package/dist/claude-marketplace/plugins/wildo/references/approval-and-failure-policy.md +110 -0
- package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +29 -0
- package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +61 -0
- package/dist/claude-marketplace/plugins/wildo/references/expert-personas-and-deliberations.md +46 -0
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +67 -0
- package/dist/claude-marketplace/plugins/wildo/references/specification-family-map.md +88 -0
- package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +43 -0
- package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +70 -0
- package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +38 -0
- package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +23 -0
- package/dist/claude-marketplace/plugins/wildo/skills/next/SKILL.md +39 -0
- package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +39 -0
- package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +38 -0
- package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +38 -0
- package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +37 -0
- package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +547 -17
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts +19 -0
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js +47 -1
- package/dist/esm/framework-knowledge.loader.js.map +1 -1
- package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.js.map +1 -1
- package/dist/esm/index.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -4
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +135 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +208 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +218 -9
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +374 -11
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +6 -4
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +22 -20
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -6
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +57 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +62 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +132 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +188 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +74 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +80 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +5 -4
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +18 -8
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +67 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +81 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +31 -11
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +132 -10
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +68 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +84 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +69 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +69 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -2
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +78 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +93 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +104 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +184 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +115 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +152 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts +59 -0
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js +72 -0
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +66 -0
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +115 -0
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +188 -8
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +167 -9
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +172 -2
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +147 -2
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +50 -0
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +54 -0
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts +248 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js +248 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +158 -5
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +173 -5
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +6 -5
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +9 -8
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +3 -2
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +23 -4
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +6 -4
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +22 -13
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +193 -28
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +173 -34
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +3 -2
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +7 -3
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +183 -6
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +192 -6
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +3 -2
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +4 -3
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +173 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +264 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +44 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +51 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts +45 -0
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js +46 -0
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +3 -2
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +7 -3
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +3 -2
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +7 -4
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +33 -5
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +28 -4
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +3 -3
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +5 -3
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +199 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +227 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +6 -4
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +19 -5
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +156 -5
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +187 -5
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +7 -6
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +28 -19
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
- package/dist/knowledge/manifest.json +9 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +75 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +40 -0
- package/dist/knowledge/playbooks/bottom_up.build/method.md +81 -0
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +89 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +1234 -80
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +53 -14
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +743 -64
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +10 -21
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +34 -49
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -21
- package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +93 -0
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +61 -0
- package/dist/knowledge/playbooks/bottom_up.conception/method.md +98 -0
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +98 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +109 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +77 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +9 -11
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +16 -16
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +181 -0
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +73 -0
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +222 -145
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +60 -24
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +152 -0
- package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +70 -0
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +87 -0
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +67 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +236 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +62 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +117 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +86 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +71 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +92 -0
- package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +83 -0
- package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +65 -0
- package/dist/knowledge/playbooks/cross_cutting.feature-development/method.md +42 -0
- package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +73 -0
- package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +46 -0
- package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +108 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +964 -15
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +19 -12
- package/dist/knowledge/playbooks/refinement.document-facts/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.document-facts/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +191 -21
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +12 -18
- package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +48 -0
- package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +66 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +349 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +54 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +24 -11
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -18
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +9 -18
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +26 -52
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +14 -18
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +99 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +211 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +66 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +40 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +37 -14
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +19 -69
- package/dist/knowledge/playbooks/top_down.compliance-research/method.md +78 -0
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +41 -0
- package/dist/knowledge/playbooks/top_down.definition/method.md +106 -0
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +120 -0
- package/dist/knowledge/playbooks/top_down.expert-personas/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +46 -0
- package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +72 -0
- package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +57 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/method.md +51 -165
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +25 -45
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +42 -0
- package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +44 -0
- package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +245 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +70 -0
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/method.md +36 -69
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +12 -13
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +28 -8
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +12 -19
- package/dist/knowledge/playbooks/top_down.risk-register/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.risk-register/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +46 -0
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +57 -0
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +25 -10
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +16 -20
- package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +24 -17
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +12 -18
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +12 -4
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +23 -20
- package/dist/knowledge/references/acp.execution-profile.md +266 -0
- package/dist/knowledge/references/acp.host-configuration-inheritance.md +29 -0
- package/dist/knowledge/references/acp.permission-ceiling.md +105 -0
- package/dist/knowledge/references/acp.permission-escalation.md +37 -0
- package/dist/knowledge/references/application-documentation-chapters.config.md +152 -0
- package/dist/knowledge/references/application-documentation-plan.config.md +136 -0
- package/dist/knowledge/references/application-maturity.config.md +319 -0
- package/dist/knowledge/references/assertions.authored-metadata.config.md +1 -1
- package/dist/knowledge/references/assertions.specification.config.md +1 -1
- package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +212 -0
- package/dist/knowledge/references/backend.inbound-handlers.agents.md +45 -0
- package/dist/knowledge/references/backend.inbound-handlers.definition.md +218 -0
- package/dist/knowledge/references/brand.asset.config.md +8 -16
- package/dist/knowledge/references/brand.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/brand.logo-direction.config.md +9 -7
- package/dist/knowledge/references/brand.snapshot.config.md +16 -2
- package/dist/knowledge/references/brand.snapshot.validation.md +0 -7
- package/dist/knowledge/references/build-plan.task-graph.config.md +649 -10
- package/dist/knowledge/references/business-model.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/business-model.pricing-plan.config.md +1 -1
- package/dist/knowledge/references/business-model.snapshot.validation.md +15 -0
- package/dist/knowledge/references/capability-composition.config.md +174 -0
- package/dist/knowledge/references/cli.market.generate-command.md +18 -2
- package/dist/knowledge/references/cli.market.utils.md +1 -0
- package/dist/knowledge/references/companion.technical-doc.service.md +453 -98
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +28 -22
- package/dist/knowledge/references/engine.client-bundle.external-connectors-public.discipline.md +20 -1
- package/dist/knowledge/references/engine.saas-technical-doc.config.md +8 -4
- package/dist/knowledge/references/engine.saas-technical-doc.provider-component.slot.md +83 -0
- package/dist/knowledge/references/engine.saas-website.config.md +22 -10
- package/dist/knowledge/references/example.authorization.service-provider-organization-wide-access.md +12 -0
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +13 -12
- package/dist/knowledge/references/example.backend.custom-operation.create-postfix.md +7 -3
- package/dist/knowledge/references/example.config.app-shell.command-menu-items.md +7 -0
- package/dist/knowledge/references/example.config.app-shell.full.md +53 -7
- package/dist/knowledge/references/example.config.backend.billing-enable.md +14 -0
- package/dist/knowledge/references/example.config.backend.inbound-email.md +14 -0
- package/dist/knowledge/references/example.config.backend.required-floors.md +11 -0
- package/dist/knowledge/references/example.config.design-system.full.md +3 -0
- package/dist/knowledge/references/example.config.navigation.full.md +45 -2
- package/dist/knowledge/references/example.config.provider-usage-pricing.md +36 -0
- package/dist/knowledge/references/example.config.provider.backend-scope-billing.md +5 -3
- package/dist/knowledge/references/example.config.provider.backend-scope-inbound-email.md +16 -0
- package/dist/knowledge/references/example.engine.product-definitions.feature-and-profiles.md +19 -7
- package/dist/knowledge/references/example.features.connected-feature.declaration.md +66 -0
- package/dist/knowledge/references/example.features.connected-feature.surface.md +42 -0
- package/dist/knowledge/references/example.flows-actors.autonomous-agent.md +23 -0
- package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +36 -0
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +30 -6
- package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +7 -11
- package/dist/knowledge/references/example.guidance.bound-survey-flow.md +82 -0
- package/dist/knowledge/references/example.inbound.application-endpoint-handler.md +72 -0
- package/dist/knowledge/references/example.inbound.email-channel-handler.md +47 -0
- package/dist/knowledge/references/example.inbound.email-to-todo.md +150 -0
- package/dist/knowledge/references/example.infra.environment-config.local.md +104 -43
- package/dist/knowledge/references/example.layout-3d.own-layout.md +16 -0
- package/dist/knowledge/references/example.layout-3d.registration.md +15 -0
- package/dist/knowledge/references/example.milestones.module-definitions.md +73 -0
- package/dist/knowledge/references/example.minion.contained-tick.md +79 -0
- package/dist/knowledge/references/example.module.companion-exports.full.md +46 -16
- package/dist/knowledge/references/example.module.relationships.discriminator.md +2 -2
- package/dist/knowledge/references/example.organizations.serves-as-provider.md +12 -0
- package/dist/knowledge/references/example.provider.address-lookup.adapter.md +64 -0
- package/dist/knowledge/references/example.provider.backend-module-shape.md +34 -13
- package/dist/knowledge/references/example.provider.frontend-app.module.md +112 -0
- package/dist/knowledge/references/example.provider.frontend-facet.package-module.md +85 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +34 -13
- package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +25 -3
- package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +30 -0
- package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +16 -0
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +5 -0
- package/dist/knowledge/references/example.resource.retention-binding.closure-event.md +21 -0
- package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +1 -2
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +112 -10
- package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +90 -0
- package/dist/knowledge/references/example.resource.work-unit.declaration.md +13 -0
- package/dist/knowledge/references/example.spec.composite-view.workspace.md +0 -12
- package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +18 -0
- package/dist/knowledge/references/example.views.app-level.composite-views-config.md +1 -1
- package/dist/knowledge/references/example.views.chart-view.resource-owned.md +27 -0
- package/dist/knowledge/references/example.views.composite-view.workspace.md +4 -1
- package/dist/knowledge/references/example.website.page.manifest.md +30 -0
- package/dist/knowledge/references/example.worker.node-route.md +94 -0
- package/dist/knowledge/references/experience-plan.config.md +318 -0
- package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +152 -9
- package/dist/knowledge/references/external-connectors.backend.provider-augmentation.md +75 -0
- package/dist/knowledge/references/external-connectors.backend.provider-package-convention.md +36 -0
- package/dist/knowledge/references/external-connectors.frontend-provider-component-declaration.md +85 -0
- package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +52 -0
- package/dist/knowledge/references/external-connectors.models.connection-rate-budgets.md +113 -0
- package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +165 -0
- package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +133 -0
- package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +44 -0
- package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +290 -0
- package/dist/knowledge/references/external-connectors.provider-component-load-state.md +45 -0
- package/dist/knowledge/references/external-connectors.provider-component-loader-contribution.md +32 -0
- package/dist/knowledge/references/external-connectors.provider-component-registry.md +190 -0
- package/dist/knowledge/references/external-connectors.techdoc.frontend-provider-module.md +91 -0
- package/dist/knowledge/references/external-connectors.website.frontend-provider-module.md +91 -0
- package/dist/knowledge/references/integration-plan.config.md +217 -0
- package/dist/knowledge/references/market.alternative.config.md +2 -2
- package/dist/knowledge/references/market.authored-metadata.config.md +12 -9
- package/dist/knowledge/references/market.buying-journey.config.md +1 -1
- package/dist/knowledge/references/market.category.config.md +1 -1
- package/dist/knowledge/references/market.channel.config.md +4 -4
- package/dist/knowledge/references/market.feature-benefit.config.md +2 -2
- package/dist/knowledge/references/market.gain.config.md +2 -2
- package/dist/knowledge/references/market.icp.config.md +3 -3
- package/dist/knowledge/references/market.job.config.md +2 -2
- package/dist/knowledge/references/market.message-template.config.md +3 -3
- package/dist/knowledge/references/market.objection.config.md +2 -2
- package/dist/knowledge/references/market.pain.config.md +2 -2
- package/dist/knowledge/references/market.persona.config.md +3 -3
- package/dist/knowledge/references/market.positioning.config.md +1 -1
- package/dist/knowledge/references/market.proof.config.md +2 -2
- package/dist/knowledge/references/market.references.weighted-edges.md +7 -0
- package/dist/knowledge/references/market.snapshot.validation.md +15 -0
- package/dist/knowledge/references/market.tone-of-voice.config.md +2 -2
- package/dist/knowledge/references/market.trigger.config.md +2 -2
- package/dist/knowledge/references/minions.tick-contract.md +83 -0
- package/dist/knowledge/references/placement-plan.config.md +375 -0
- package/dist/knowledge/references/platform.config.application-database.md +5 -2
- package/dist/knowledge/references/platform.config.backing-services.md +15 -36
- package/dist/knowledge/references/platform.config.environment.deployment.md +206 -14
- package/dist/knowledge/references/platform.config.infra-provider-resolution.md +170 -0
- package/dist/knowledge/references/platform.config.infrastructure-host.md +87 -0
- package/dist/knowledge/references/platform.config.saas.md +261 -9
- package/dist/knowledge/references/presets.3d.frame-style-overrides.md +134 -0
- package/dist/knowledge/references/presets.3d.layout-contract.md +213 -0
- package/dist/knowledge/references/presets.3d.register-layout.md +95 -0
- package/dist/knowledge/references/presets.models.labelling.sections.md +19 -0
- package/dist/knowledge/references/presets.models.shell-region.md +47 -0
- package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
- package/dist/knowledge/references/requirements.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -0
- package/dist/knowledge/references/requirements.snapshot.validation.md +15 -0
- package/dist/knowledge/references/roadmap.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/roadmap.snapshot.validation.md +15 -7
- package/dist/knowledge/references/saas.backend.a2a.token-budget.md +71 -0
- package/dist/knowledge/references/saas.backend.actor-execution-decision-record.md +41 -0
- package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +1 -2
- package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +1 -1
- package/dist/knowledge/references/saas.backend.auth.federated-identity-provider-private-networks.md +62 -0
- package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +87 -0
- package/dist/knowledge/references/saas.backend.billing.catalog-sync-result.md +37 -0
- package/dist/knowledge/references/saas.backend.billing.resolution-failure-reasons.md +24 -5
- package/dist/knowledge/references/saas.backend.compliance.governed-documents-pdf-template.md +370 -0
- package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +194 -0
- package/dist/knowledge/references/saas.backend.domain-module.md +118 -16
- package/dist/knowledge/references/saas.backend.error-builder.user-guidance.md +82 -0
- package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-declaration.md +66 -0
- package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-schedule.md +31 -0
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +206 -0
- package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +22 -4
- package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +19 -4
- package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +84 -0
- package/dist/knowledge/references/saas.backend.health-readiness-contributor.md +73 -0
- package/dist/knowledge/references/saas.backend.pdf-template.collection-definition.md +73 -0
- package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +224 -0
- package/dist/knowledge/references/saas.backend.providers.operation-executor.md +51 -0
- package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +71 -0
- package/dist/knowledge/references/saas.backend.queue.worker-topology.md +39 -0
- package/dist/knowledge/references/saas.backend.submission-challenge.md +118 -0
- package/dist/knowledge/references/saas.backend.system-access-service.md +148 -41
- package/dist/knowledge/references/saas.backend.system-of-record-action-runner.md +73 -0
- package/dist/knowledge/references/saas.composition.scenario-apply.md +51 -0
- package/dist/knowledge/references/saas.config.content-security-policy.md +97 -0
- package/dist/knowledge/references/saas.config.providers.augmentations.md +61 -0
- package/dist/knowledge/references/saas.config.providers.packages.md +59 -0
- package/dist/knowledge/references/saas.config.providers.shared-connections.md +84 -0
- package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +91 -21
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +4 -0
- package/dist/knowledge/references/saas.external-data.admin-endpoints.md +56 -2
- package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +38 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +27 -27
- package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +65 -16
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +43 -13
- package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +44 -8
- package/dist/knowledge/references/saas.frontend.app-shell.building-blocks.md +250 -0
- package/dist/knowledge/references/saas.frontend.billing-context.md +131 -0
- package/dist/knowledge/references/saas.frontend.brand-identity.md +38 -0
- package/dist/knowledge/references/saas.frontend.celebration-overlay-contract.md +41 -0
- package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +92 -0
- package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +64 -0
- package/dist/knowledge/references/saas.frontend.consent-based-provider-activation.md +22 -0
- package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
- package/dist/knowledge/references/saas.frontend.errors.user-facing-error-message.md +47 -0
- package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.per-action-retry-loop.md +7 -1
- package/dist/knowledge/references/saas.frontend.execution-view.definition.md +3 -3
- package/dist/knowledge/references/saas.frontend.flows-actors-view.md +7 -4
- package/dist/knowledge/references/saas.frontend.form-field-address.lookup-slot.md +74 -0
- package/dist/knowledge/references/saas.frontend.form-fields.file-provider-constraints.md +30 -48
- package/dist/knowledge/references/saas.frontend.full-custom-view.definition.md +24 -0
- package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +60 -0
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +47 -0
- package/dist/knowledge/references/saas.frontend.notifications.publish-badge-count.md +60 -0
- package/dist/knowledge/references/saas.frontend.onboarding-view.md +84 -0
- package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +80 -0
- package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
- package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +49 -0
- package/dist/knowledge/references/saas.frontend.related-resource-sections.md +8 -1
- package/dist/knowledge/references/saas.frontend.resource-header-title.md +28 -4
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +136 -1
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +422 -11
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +25 -1
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +259 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +220 -0
- package/dist/knowledge/references/saas.market.generation-agent.md +26 -10
- package/dist/knowledge/references/saas.models.agent-work-capture-settings.md +34 -0
- package/dist/knowledge/references/saas.models.agent-work-decision-surface.md +45 -0
- package/dist/knowledge/references/saas.models.agent-work-decision-vocabulary.md +107 -0
- package/dist/knowledge/references/saas.models.agent-work-output-review.md +36 -0
- package/dist/knowledge/references/saas.models.agent-work-override-rate.md +50 -0
- package/dist/knowledge/references/saas.models.agent-work-review-config.md +24 -0
- package/dist/knowledge/references/saas.models.analytics.value-moments.md +132 -0
- package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +97 -0
- package/dist/knowledge/references/saas.models.audit.trail-config.md +161 -0
- package/dist/knowledge/references/saas.models.auth.methods.md +513 -0
- package/dist/knowledge/references/saas.models.auth.service-provider-client-authentication.md +169 -0
- package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +90 -0
- package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +130 -0
- package/dist/knowledge/references/saas.models.billing.referral-program.md +47 -0
- package/dist/knowledge/references/saas.models.config.organization-types.md +266 -0
- package/dist/knowledge/references/saas.models.config.registration.md +188 -0
- package/dist/knowledge/references/saas.models.config.tenant-teardown.md +98 -0
- package/dist/knowledge/references/saas.models.conversation-threads.md +242 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +173 -3
- package/dist/knowledge/references/saas.models.email.template-type.md +40 -0
- package/dist/knowledge/references/saas.models.engine-capabilities.md +97 -7
- package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +65 -0
- package/dist/knowledge/references/saas.models.evaluation-dataset-export.md +39 -0
- package/dist/knowledge/references/saas.models.evaluation-export-authorization.md +38 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +710 -10
- package/dist/knowledge/references/saas.models.features.definition-builders.md +162 -0
- package/dist/knowledge/references/saas.models.file-upload-grant.md +222 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +54 -5
- package/dist/knowledge/references/saas.models.flows-actors.autonomous-agents-vocabulary.md +98 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-decision-vocabulary.md +52 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-calendar.md +42 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-deadline-vocabulary.md +84 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +69 -0
- package/dist/knowledge/references/saas.models.frontend-provider-public-config-contract.md +72 -0
- package/dist/knowledge/references/saas.models.governed-document-acceptance-mode.md +116 -0
- package/dist/knowledge/references/saas.models.guidance-flow.md +160 -0
- package/dist/knowledge/references/saas.models.http-api-binding.md +884 -135
- package/dist/knowledge/references/saas.models.http-api-binding.rest-write-operations.md +81 -0
- package/dist/knowledge/references/saas.models.human-decision-review-marker.md +20 -0
- package/dist/knowledge/references/saas.models.inbound-channels.md +277 -0
- package/dist/knowledge/references/saas.models.inbound-email-domains.md +101 -0
- package/dist/knowledge/references/saas.models.inbound-email.md +111 -0
- package/dist/knowledge/references/saas.models.milestone-celebration.md +69 -0
- package/dist/knowledge/references/saas.models.milestone-definition.md +209 -0
- package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +28 -0
- package/dist/knowledge/references/saas.models.model-cost-summary.md +87 -0
- package/dist/knowledge/references/saas.models.navigation.layout.md +13 -9
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +133 -0
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +103 -0
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +152 -0
- package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +84 -0
- package/dist/knowledge/references/saas.models.notifications.targets.md +146 -0
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +283 -0
- package/dist/knowledge/references/saas.models.onboarding-elements.md +375 -0
- package/dist/knowledge/references/saas.models.onboarding-trigger.md +52 -0
- package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +59 -0
- package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +129 -0
- package/dist/knowledge/references/saas.models.organizations.service-provider-activity-feed.md +121 -0
- package/dist/knowledge/references/saas.models.organizations.service-provider-capability-grants.md +152 -0
- package/dist/knowledge/references/saas.models.organizations.service-provider-client-controls.md +49 -0
- package/dist/knowledge/references/saas.models.organizations.service-provider-relationships.md +567 -0
- package/dist/knowledge/references/saas.models.privacy.client-instance-id-scope.md +49 -0
- package/dist/knowledge/references/saas.models.privacy.legal-holds.md +172 -0
- package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +104 -0
- package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +106 -0
- package/dist/knowledge/references/saas.models.privacy.retention-binding.md +103 -0
- package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +120 -0
- package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +147 -0
- package/dist/knowledge/references/saas.models.privacy.statutory-retention-ground.md +50 -0
- package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +388 -0
- package/dist/knowledge/references/saas.models.progression-tracker-variant.md +76 -0
- package/dist/knowledge/references/saas.models.provider-address-lookup-contract.md +139 -0
- package/dist/knowledge/references/saas.models.provider-address-lookup-declaration.md +61 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +42 -5
- package/dist/knowledge/references/saas.models.provider-credential-identity.md +67 -0
- package/dist/knowledge/references/saas.models.provider-usage-pricing-authority.md +139 -0
- package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +133 -0
- package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +50 -0
- package/dist/knowledge/references/saas.models.providers.capability-surface.md +58 -0
- package/dist/knowledge/references/saas.models.providers.compliance-choice.md +196 -0
- package/dist/knowledge/references/saas.models.providers.scope-reauthorization.md +57 -0
- package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +156 -0
- package/dist/knowledge/references/saas.models.rate-limit-configuration.md +11 -1
- package/dist/knowledge/references/saas.models.relationship-handling-settings.md +23 -1
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +244 -32
- package/dist/knowledge/references/saas.models.resource-config.forwarded-label.md +5 -4
- package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +69 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +15 -2
- package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +66 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-base.md +24 -1
- package/dist/knowledge/references/saas.models.resource-config.operation-cron-job.md +59 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +55 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +5 -4
- package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +158 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-step-up.md +77 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-submission-challenge.md +54 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-for-key.md +6 -1
- package/dist/knowledge/references/saas.models.resource-config.queue-policy.md +49 -0
- package/dist/knowledge/references/saas.models.resource-config.required-features.md +84 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +16 -0
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +22 -0
- package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +82 -0
- package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +111 -4
- package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +39 -0
- package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +48 -0
- package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +38 -0
- package/dist/knowledge/references/saas.models.resource-primary-scope.md +11 -2
- package/dist/knowledge/references/saas.models.scope-membership.md +3 -4
- package/dist/knowledge/references/saas.models.shared-saas-module.md +25 -0
- package/dist/knowledge/references/saas.models.system-of-record-actions.md +226 -0
- package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +461 -0
- package/dist/knowledge/references/saas.models.systems-of-record.facet-augmentation.md +63 -0
- package/dist/knowledge/references/saas.models.systems-of-record.md +870 -0
- package/dist/knowledge/references/saas.models.work-attribution-vocabulary.md +109 -0
- package/dist/knowledge/references/saas.models.work-unit-ref.md +28 -0
- package/dist/knowledge/references/saas.public-runtime.contract.md +268 -3
- package/dist/knowledge/references/saas.rag.retrieval-result.md +19 -8
- package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
- package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +15 -36
- package/dist/knowledge/references/saas.specifications.application-document-publication.contract.md +9 -5
- package/dist/knowledge/references/saas.specifications.application-document-publication.generation.md +63 -0
- package/dist/knowledge/references/saas.specifications.application-document-release-set.contract.md +74 -0
- package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +123 -0
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +108 -7
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +880 -66
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +14 -13
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.discriminated-union.md +36 -14
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-aggregate-offer.md +4 -3
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-product.md +4 -4
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-software-application.md +71 -0
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +217 -18
- package/dist/knowledge/references/saas.specifications.compliance.retention-enforcement-state.md +32 -0
- package/dist/knowledge/references/saas.specifications.composite-view-specification.md +10 -0
- package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +376 -0
- package/dist/knowledge/references/saas.specifications.playbook-approval-and-failure-policies.md +96 -0
- package/dist/knowledge/references/saas.specifications.processor-register.md +410 -0
- package/dist/knowledge/references/saas.specifications.recipient-disclosures.md +71 -0
- package/dist/knowledge/references/saas.specifications.recipient-population.md +549 -0
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +120 -45
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +35 -1
- package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +17 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-frontend-prose.md +16 -0
- package/dist/knowledge/references/saas.specifications.subject-data-recipients.md +98 -0
- package/dist/knowledge/references/saas.website.astro.bridge.md +92 -7
- package/dist/knowledge/references/saas.website.astro.head-renderer.md +33 -13
- package/dist/knowledge/references/saas.website.astro.label-loader.md +10 -4
- package/dist/knowledge/references/saas.website.astro.robots-renderer.md +29 -16
- package/dist/knowledge/references/saas.website.astro.site-context.md +5 -2
- package/dist/knowledge/references/saas.website.blog.bridge.md +34 -1
- package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +61 -0
- package/dist/knowledge/references/saas.website.config.site-context-loader.md +154 -0
- package/dist/knowledge/references/saas.website.consent.banner.md +218 -0
- package/dist/knowledge/references/saas.website.consent.context.md +162 -0
- package/dist/knowledge/references/saas.website.consent.gate.md +38 -0
- package/dist/knowledge/references/saas.website.design-tokens.colors.md +7 -4
- package/dist/knowledge/references/saas.website.design-tokens.radius.md +1 -1
- package/dist/knowledge/references/saas.website.factories.define-section.md +3 -3
- package/dist/knowledge/references/saas.website.page-layout.component.md +70 -1
- package/dist/knowledge/references/saas.website.page.context.md +4 -3
- package/dist/knowledge/references/saas.website.pricing-offer-structured-data.md +140 -0
- package/dist/knowledge/references/saas.website.provider-component.slot.md +99 -0
- package/dist/knowledge/references/saas.website.root-config.schema.md +6 -6
- package/dist/knowledge/references/saas.website.runtime.context.md +66 -11
- package/dist/knowledge/references/saas.website.section.context.md +3 -2
- package/dist/knowledge/references/saas.website.sections.category-enum.md +19 -20
- package/dist/knowledge/references/saas.website.sections.definition-schema.md +14 -7
- package/dist/knowledge/references/saas.website.seo.robots-config.md +4 -3
- package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +7 -5
- package/dist/knowledge/references/saas.website.submission-challenge.md +77 -0
- package/dist/knowledge/references/saas.website.use-pricing-catalog.hook.md +36 -0
- package/dist/knowledge/references/saas.website.use-runtime.hook.md +3 -2
- package/dist/knowledge/references/vision.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/website-plan.config.md +238 -0
- package/dist/knowledge/references/workers.node.worker-init-contract.md +57 -0
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +43 -2
- package/dist/knowledge/references/zod.decorators.data-categories.md +197 -0
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +53 -5
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +75 -1
- package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +36 -2
- package/dist/knowledge/references/zod.decorators.field-spec-params.md +32 -5
- package/dist/knowledge/references/zod.decorators.file-nature-constraints.md +86 -0
- package/dist/knowledge/references/zod.decorators.file-readiness-metadata.md +67 -0
- package/dist/knowledge/references/zod.decorators.file-schema.md +95 -18
- package/dist/knowledge/references/zod.decorators.file-vocabularies.md +87 -0
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +148 -6
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
- package/dist/knowledge/references/zod.decorators.rag-source.md +6 -2
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +24 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +35 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +50 -12
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +35 -12
- package/dist/knowledge/references/zod.factories.address.md +118 -0
- package/dist/knowledge/references/zod.factories.code.md +4 -2
- package/dist/knowledge/references/zod.factories.duration.md +6 -4
- package/dist/knowledge/references/zod.factories.money.md +5 -3
- package/dist/knowledge/references/zod.factories.phone.md +14 -1
- package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
- package/dist/knowledge/registries/framework-topics.json +2602 -214
- package/dist/knowledge/registries/playbooks.json +468 -92
- package/dist/knowledge/registries/source-tags.json +6171 -1996
- package/dist/knowledge/rules/database-migration-obligation.md +110 -0
- package/dist/knowledge/rules/live-context-door.md +137 -0
- package/dist/knowledge/rules/resource-schema-awareness.md +75 -0
- package/dist/knowledge/skills/INDEX.md +67 -29
- package/dist/knowledge/skills/agent-work-review/SKILL.md +141 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-capture-settings-api.md +38 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-output-review-api.md +40 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-override-rate-api.md +54 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-config-api.md +28 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +108 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-vocabulary-api.md +111 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-dataset-export-api.md +43 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-export-authorization-api.md +42 -0
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +111 -37
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +167 -0
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +6 -3
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +11 -3
- package/dist/knowledge/skills/application-database-migrations/references/framework-application-database-api.md +5 -2
- package/dist/knowledge/skills/application-database-migrations/references/migration-refusals.md +32 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +95 -3
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +59 -0
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +32 -19
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +119 -17
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-readiness-contributor-api.md +135 -0
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +96 -20
- package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +137 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-error-user-guidance-api.md +112 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +72 -1
- package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +214 -0
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +39 -1
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-asset-api.md +8 -16
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +25 -9
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +162 -8
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +80 -17
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +518 -132
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +32 -10
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +103 -58
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-publication-contract.md +19 -13
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +162 -26
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +734 -23
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +436 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +221 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +209 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-population.md +577 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +549 -0
- package/dist/knowledge/skills/config-app-shell/SKILL.md +95 -11
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +87 -21
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-building-blocks-api.md +276 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +70 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-shell-region-markers-api.md +66 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +44 -3
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
- package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
- package/dist/knowledge/skills/config-design-system/references/surface-policy-authoring.md +19 -10
- package/dist/knowledge/skills/config-navigation/SKILL.md +200 -19
- package/dist/knowledge/skills/config-navigation/references/choosing-a-navigation-shape.md +314 -0
- package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +13 -9
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +78 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +245 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +174 -0
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +253 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +141 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-zones.md +1 -1
- package/dist/knowledge/skills/config-saas/SKILL.md +88 -9
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +206 -0
- package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +189 -0
- package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +493 -0
- package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +157 -0
- package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +292 -0
- package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +161 -0
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +139 -12
- package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +1024 -0
- package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +172 -0
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +261 -9
- package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +9 -0
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +66 -3
- package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +151 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-auth-methods-api.md +579 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +8 -2
- package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +96 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +397 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-registration-config-api.md +221 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +143 -0
- package/dist/knowledge/skills/config-saas-backend/references/managed-startup-configuration.md +46 -0
- package/dist/knowledge/skills/configure-billing/SKILL.md +91 -46
- package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +62 -17
- package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +55 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +39 -17
- package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +30 -28
- package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +192 -0
- package/dist/knowledge/skills/configure-billing/references/framework-billing-resolution-failure-api.md +44 -11
- package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +259 -0
- package/dist/knowledge/skills/configure-billing/references/framework-referral-program.md +110 -0
- package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +91 -0
- package/dist/knowledge/skills/configure-coding-agent/SKILL.md +289 -0
- package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +192 -0
- package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +504 -0
- package/dist/knowledge/skills/email-add-template/SKILL.md +100 -91
- package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +15 -7
- package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +123 -0
- package/dist/knowledge/skills/email-definition-wiring/SKILL.md +1 -0
- package/dist/knowledge/skills/email-labels-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/email-template-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/engine-component-registration/SKILL.md +20 -12
- package/dist/knowledge/skills/engine-product-definitions/SKILL.md +60 -31
- package/dist/knowledge/skills/engine-product-definitions/references/connected-feature-workflow.md +130 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-engine-product-definitions-api.md +25 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-feature-builders-api.md +215 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +78 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +60 -27
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +121 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
- package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +180 -0
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +56 -0
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-autonomous-agent-api.md +208 -0
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-inbound-agents-api.md +51 -0
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/tool-posture.md +27 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +41 -12
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +31 -7
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +148 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +287 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +248 -9
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +127 -22
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +236 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +8 -11
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +54 -5
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +75 -21
- package/dist/knowledge/skills/frontend-cdn-publish/SKILL.md +1 -0
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +259 -0
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +480 -0
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +3988 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +212 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +165 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-elements-api.md +381 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-trigger-api.md +57 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-view-api.md +89 -0
- package/dist/knowledge/skills/i18n-label-generation/SKILL.md +14 -1
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +19 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +11 -9
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +19 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +11 -2
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +19 -0
- package/dist/knowledge/skills/i18n-translation-rerun/references/translation-workflow.md +5 -0
- package/dist/knowledge/skills/inbound-channels/SKILL.md +301 -0
- package/dist/knowledge/skills/inbound-channels/references/email-channel.md +133 -0
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +800 -0
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-email-api.md +222 -0
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +231 -0
- package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +135 -0
- package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +297 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +387 -81
- package/dist/knowledge/skills/infra-environment-config/references/framework-application-database-api.md +5 -2
- package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +198 -36
- package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +206 -14
- package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +95 -0
- package/dist/knowledge/skills/layout-3d-adoption/SKILL.md +176 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +141 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-contract-api.md +223 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-registration-api.md +103 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-building-blocks-api.md +256 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-region-marker-api.md +52 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/layouts-and-transitions.md +29 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +25 -0
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +184 -46
- package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +119 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/initialization-recovery-recipe.md +7 -4
- package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +2 -1
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +289 -37
- package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +3 -2
- package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +2 -2
- package/dist/knowledge/skills/market-alternatives/SKILL.md +4 -3
- package/dist/knowledge/skills/market-authoring-overview/SKILL.md +1 -0
- package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +7 -0
- package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +12 -9
- package/dist/knowledge/skills/market-category/SKILL.md +2 -1
- package/dist/knowledge/skills/market-channels/SKILL.md +5 -4
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +233 -18
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +232 -18
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +77 -15
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +50 -12
- package/dist/knowledge/skills/market-icp/SKILL.md +4 -3
- package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +7 -6
- package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +4 -3
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +18 -3
- package/dist/knowledge/skills/market-persona/SKILL.md +4 -3
- package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/market-positioning-authoring/references/framework-positioning-api.md +1 -1
- package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +5 -4
- package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +1 -0
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +16 -0
- package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +15 -0
- package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +3 -2
- package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +4 -3
- package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +199 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-celebration-overlay-contract.md +51 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-celebration-api.md +79 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-definition-api.md +220 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-progression-tracker-api.md +86 -0
- package/dist/knowledge/skills/minion-authoring/SKILL.md +144 -0
- package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +84 -0
- package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +91 -0
- package/dist/knowledge/skills/model-cost-attribution/SKILL.md +143 -0
- package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +211 -0
- package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-summary-api.md +95 -0
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-attribution-api.md +117 -0
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +677 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +55 -19
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +217 -18
- package/dist/knowledge/skills/module-registration/SKILL.md +50 -32
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +143 -16
- package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +227 -0
- package/dist/knowledge/skills/module-registration/references/registry-files.md +14 -5
- package/dist/knowledge/skills/module-relationships/SKILL.md +65 -2
- package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +26 -5
- package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +34 -2
- package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-collection-template-api.md +447 -0
- package/dist/knowledge/skills/provider-address-lookup/SKILL.md +207 -0
- package/dist/knowledge/skills/provider-address-lookup/references/framework-address-field-lookup-slot-api.md +82 -0
- package/dist/knowledge/skills/provider-address-lookup/references/framework-address-lookup-contract-api.md +214 -0
- package/dist/knowledge/skills/provider-address-lookup/references/framework-browser-operation-policy-api.md +143 -0
- package/dist/knowledge/skills/provider-address-lookup/references/google-places-setup.md +73 -0
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +518 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +80 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-augmentation-api.md +227 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-credential-identity-api.md +101 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +245 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +88 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +55 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-allow-list-api.md +111 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-convention-api.md +48 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +309 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +165 -29
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-file-provider-constraints-api.md +99 -47
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +399 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +270 -9
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-public-config-api.md +115 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-provider-component-registry-api.md +386 -0
- package/dist/knowledge/skills/provider-frontend-module/SKILL.md +258 -0
- package/dist/knowledge/skills/provider-frontend-module/references/framework-frontend-facet-contracts-api.md +463 -0
- package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +61 -0
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +247 -0
- package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +50 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +141 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-connection-rate-budgets-api.md +176 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +86 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +73 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-scope-reauthorization-api.md +127 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +300 -0
- package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +70 -11
- package/dist/knowledge/skills/rate-limit-authoring/references/fixed-window-and-environment-multiplier.md +27 -0
- package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +19 -6
- package/dist/knowledge/skills/resource-add-field/SKILL.md +13 -5
- package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +1 -2
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +472 -23
- package/dist/knowledge/skills/resource-add-module/SKILL.md +117 -265
- package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +134 -0
- package/dist/knowledge/skills/resource-add-module/references/framework-new-module-wiring-api.md +25 -0
- package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +12 -12
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +29 -3
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +244 -32
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +26 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +101 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +145 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +101 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +133 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +141 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-step-up-api.md +126 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +953 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +122 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +125 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +97 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +595 -45
- package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +197 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +259 -45
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +486 -0
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +6 -0
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +422 -11
- package/dist/knowledge/skills/resource-custom-view/references/framework-user-facing-error-message-api.md +50 -0
- package/dist/knowledge/skills/resource-external-data/SKILL.md +1242 -31
- package/dist/knowledge/skills/resource-external-data/references/declared-expressions.md +144 -0
- package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +68 -0
- package/dist/knowledge/skills/resource-external-data/references/facet-augmentations.md +154 -0
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +739 -17
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +987 -140
- package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +175 -10
- package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +152 -0
- package/dist/knowledge/skills/resource-external-data/references/odata-v2-sources.md +60 -0
- package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +179 -0
- package/dist/knowledge/skills/resource-external-data/references/pipeline-destination-schema.md +1 -1
- package/dist/knowledge/skills/resource-external-data/references/provenance-cue.md +63 -0
- package/dist/knowledge/skills/resource-external-data/references/rate-budgets-and-pacing.md +122 -0
- package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +745 -0
- package/dist/knowledge/skills/resource-external-data/references/remote-references.md +85 -0
- package/dist/knowledge/skills/resource-external-data/references/rest-keyset-sources.md +85 -0
- package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +442 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +70 -26
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +246 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +7 -6
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +5 -3
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +44 -48
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +108 -14
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +47 -15
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +6 -2
- package/dist/knowledge/skills/resource-retention-binding/SKILL.md +186 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +200 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +111 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +173 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +155 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +139 -0
- package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +55 -0
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +34 -4
- package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +1 -2
- package/dist/knowledge/skills/resource-schema-authoring/examples/basic-resource-schema.example.md +2 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +17 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +3 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +77 -5
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +210 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +245 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +35 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +50 -12
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +497 -28
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +67 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +78 -14
- package/dist/knowledge/skills/resource-schema-authoring/references/polymorphic-per-scope-resources.md +28 -5
- package/dist/knowledge/skills/resource-schema-authoring/references/schema-variants-and-discriminators.md +25 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +34 -0
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +300 -23
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +75 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +36 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +447 -12
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +148 -6
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +57 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +216 -6
- package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +266 -0
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +10 -1
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +4 -0
- package/dist/knowledge/skills/seeding-operations/SKILL.md +34 -29
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +13 -5
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-cron-scheduler.md +67 -74
- package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +97 -24
- package/dist/knowledge/skills/service-provider-relationships/SKILL.md +455 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-organization-types-api.md +270 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-activity-feed-api.md +129 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-capability-grants-api.md +161 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-client-authentication-api.md +224 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-relationships-api.md +576 -0
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +206 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +266 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +229 -0
- package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +43 -37
- package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +15 -14
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +52 -19
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +217 -18
- package/dist/knowledge/skills/spec-component-update/SKILL.md +31 -11
- package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +20 -21
- package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +10 -0
- package/dist/knowledge/skills/spec-family-update/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-feature-update/SKILL.md +48 -9
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +16 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +32 -5
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +188 -46
- package/dist/knowledge/skills/spec-update-after-change/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +17 -0
- package/dist/knowledge/skills/views-add-composite-view/SKILL.md +6 -1
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +14 -2
- package/dist/knowledge/skills/views-add-custom-view/references/framework-view-scope-and-full-custom-api.md +24 -0
- package/dist/knowledge/skills/views-app-level/SKILL.md +3 -1
- package/dist/knowledge/skills/views-app-level/references/framework-view-scope-and-full-custom-api.md +24 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +44 -1
- package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +102 -0
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +6 -1
- package/dist/knowledge/skills/views-composite-authoring/references/composite-embedding-checklist.md +3 -2
- package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +64 -0
- package/dist/knowledge/skills/views-execution-authoring/SKILL.md +4 -0
- package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +3 -3
- package/dist/knowledge/skills/views-execution-authoring/references/framework-user-facing-error-message-api.md +50 -0
- package/dist/knowledge/skills/website-anonymous-session/SKILL.md +72 -13
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +3 -2
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +34 -1
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +44 -28
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +48 -23
- package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +882 -211
- package/dist/knowledge/skills/website-factory-advanced/SKILL.md +4 -3
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +117 -13
- package/dist/knowledge/skills/website-inbound-contact-forms/references/framework-submission-challenge-api.md +275 -0
- package/dist/knowledge/skills/website-label-pack/SKILL.md +13 -5
- package/dist/knowledge/skills/website-layout-overrides/SKILL.md +71 -1
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +22 -2
- package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +21 -6
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +206 -35
- package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +164 -0
- package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +126 -0
- package/dist/knowledge/skills/website-page-variants/SKILL.md +1 -0
- package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +1 -0
- package/dist/knowledge/skills/website-section-contact/SKILL.md +159 -180
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +38 -31
- package/dist/knowledge/skills/website-section-cta/SKILL.md +51 -42
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +38 -31
- package/dist/knowledge/skills/website-section-faq/SKILL.md +118 -83
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +38 -31
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +46 -38
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +38 -31
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +52 -42
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +38 -31
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +50 -40
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +38 -31
- package/dist/knowledge/skills/website-section-hero/SKILL.md +101 -69
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +38 -31
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +236 -220
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +38 -31
- package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +248 -0
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +64 -54
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +38 -31
- package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +8 -3
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +64 -34
- package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +44 -26
- package/dist/knowledge/skills/worker-authoring/SKILL.md +165 -0
- package/dist/knowledge/skills/worker-authoring/examples/worker-route.example.md +98 -0
- package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +65 -0
- package/dist/knowledge/topic-index.json +12659 -4142
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/knowledge/references/example.provider.contribution.backend-billing.md +0 -12
- package/dist/knowledge/skills/configure-billing/references/example-provider-contribution-and-backend-config.md +0 -48
- package/dist/knowledge/skills/journey-approve/SKILL.md +0 -43
- package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +0 -42
- package/dist/knowledge/skills/journey-next/SKILL.md +0 -42
- package/dist/knowledge/skills/journey-report/SKILL.md +0 -43
- package/dist/knowledge/skills/journey-run/SKILL.md +0 -55
- package/dist/knowledge/skills/journey-status/SKILL.md +0 -50
- /package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/structured-artifact-action.json +0 -0
|
@@ -3,12 +3,7 @@
|
|
|
3
3
|
"version": "0.1.0",
|
|
4
4
|
"phase": "refinement",
|
|
5
5
|
"intent": "Derive the application's governed-document FACTS from truth it has already accepted — its vision (including the compliance regimes the posture pass recorded), its domain and its requirements — and land them as the `document-facts` family. A fact is a plain statement about how this application actually behaves: what data it holds, how long it keeps it, who it discloses to, what rights it honours. This produces the raw material a privacy notice or service terms is drafted FROM; it never drafts the document, never decides a legal question, and never states a fact the application's own code and accepted specifications do not support. Mechanism facts — retention treatment, data-subject kind, subject export — are read from the resource configurations, which declare what the application will actually do to a row; specifications supply purpose, not mechanism.",
|
|
6
|
-
"functionalTopics": [],
|
|
7
6
|
"preconditions": [
|
|
8
|
-
{
|
|
9
|
-
"kind": "phase_is",
|
|
10
|
-
"phase": "refinement"
|
|
11
|
-
},
|
|
12
7
|
{
|
|
13
8
|
"kind": "artifact_valid",
|
|
14
9
|
"selector": {
|
|
@@ -37,25 +32,24 @@
|
|
|
37
32
|
{
|
|
38
33
|
"family": "document-facts",
|
|
39
34
|
"schemaRef": "saas-specifications:ApplicationDocumentFactSpecification",
|
|
40
|
-
"placement": "specifications/src/document-facts/",
|
|
41
35
|
"description": "The application's declared governed-document facts, one declaration per fact, each either KNOWN with its value or NOT_APPLICABLE with a reason. Authority is APPLICATION_SPECIFICATION throughout: these are facts the application's own accepted specifications establish. A fact needing a named human decision is deliberately ABSENT rather than dressed in an authority nobody holds."
|
|
42
36
|
}
|
|
43
37
|
],
|
|
38
|
+
"stepOutputs": [],
|
|
44
39
|
"method": {
|
|
45
|
-
"guidance": "# Governed-document facts — derivation method\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## What you produce\n\nOne `document-facts` file for the application: a list of **facts**, each a plain statement about how\nthis application actually behaves. Not prose for a notice — the raw material a notice is later drafted\nfrom, and the thing a drafted clause is checked against.\n\nA fact is the answer to a question a reader of a legal document would want settled:\n\n- what categories of personal data does the application hold, and where do they come from;\n- what does it do with them, and for how long does it keep them;\n- who else sees them — providers, processors, other tenants;\n- what rights does it actually honour, and through which mechanism;\n- who operates the service, and how is it contacted.\n\n## The rule that governs everything here\n\n**Every fact you write must be supported by something the application has already accepted** — and the\nstrongest support is not prose about the application, it is **the application's own code**.\n\nRead in this order:\n\n1. **The resource configurations** — the `compliance-primary-facts` introspection behavior reads them\n for you, per resource: `retentionPolicy.mode` (what erasure does to a row), `dataSubjectPolicy.kind`\n (whether those rows are a person), `systemAccessPolicy.exportSubject` (whether an Art. 15 / Art. 20\n export can answer for them) and `seeRetained` (the audited path to retained data). These are\n DECLARATIONS, already written down and enforced at runtime. They are the best evidence a governed\n document can rest on, and they need no interpretation — only phrasing.\n2. **The compliance constraints on the vision**, which tell you which facts a reader will need.\n3. **The domain plan and requirements**, for what the product is FOR — purpose, not mechanism.\n\nThe split between 1 and 3 is the point. A specification says what the application is meant to do; a\nresource configuration says what it will actually do to a row tomorrow morning. Where they disagree,\nthe configuration is the fact.\n\nNote the behavior reports engine-declared and application-declared coverage **separately**, and you\nshould keep them apart in your facts too. The engine already answers most of the personal-data core —\nidentity, credentials, sessions, membership — for every application. What it cannot answer is the\napplication's own domain data, which is usually what a reader most wants to know about.\n\nYou are **not** deciding anything. A legal basis, a controller-versus-processor role, a governing law,\na liability position and a retention *duration the product has not chosen* are all decisions, and none\nof them is yours. If a fact needs a human to decide it, **leave it out**. Do not write a plausible\nplaceholder, and do not soften a decision into a fact by hedging the wording.\n\nLeaving it out is not a failure — it is the designed behaviour, and it does **not** block anything\ndownstream. A document clause that would have rested on a fact you did not declare is still written:\nit is marked as not yet established, names what it needs and who can supply it, and the document is\nproduced. So an absence costs the reader a precise statement of a gap, which is useful. A guessed fact\ncosts them a published false statement about somebody's data, which is not.\n\n## KNOWN and NOT_APPLICABLE are different answers — and both are different from absence\n\nThree states, and confusing them is the most common way this pass goes wrong.\n\n| state | means | how you write it |\n|---|---|---|\n| `KNOWN` | the application does this, and here is what it does | `resolution: KNOWN` with `value` |\n| `NOT_APPLICABLE` | this was considered and it genuinely does not apply | `resolution: NOT_APPLICABLE` with `reason` |\n| absent | nobody has established this yet | omit the declaration entirely |\n\n`NOT_APPLICABLE` is a real, useful answer — \"this application performs no international transfers\"\ntells a reviewer something. It is **not** a way to dispose of a fact you could not find. If you do not\nknow, the honest output is absence.\n\nA `KNOWN` fact must carry an actual value. An empty string, a blank one or an empty object is rejected\nby the validator: a fact that exists and says nothing is worse than a missing one, because a document\ncan cite it and learn nothing.\n\n## Read the compliance constraints first\n\n`top_down.compliance-posture` records each applicable regime as a `compliance`-kind constraint on the\nvision. Those constraints tell you which facts matter. A GDPR constraint means a reader will need data\ncategories, purposes, retention, recipients, transfers and rights mechanisms. A data-residency\nconstraint means where data lives is a fact worth stating.\n\nDerive the fact SET from the regimes, then answer each one from the application's own truth — the\nconfigurations first. Where the regime implies a fact the application has not settled, that is an\nabsence: record nothing, and let the document state the gap in place.\n\n## Scope: one operator, deliberately\n\nEvery fact you write is attributed to one application-operator governance scope. The family can carry\nfacts for a tenant organization or a shared-responsibility boundary too, but choosing a different\nsubject per fact is deciding **shared-responsibility attribution**, which is exactly the thing that\nmust never be guessed or flattened. One operator scope is the honest output of a derivation; a second\nsubject is a human's edit.\n\nThe `operatorSlug` you supply is an operator identity, **not** a legal-entity assertion. It names who\nruns the service, not which company is on the contract — that is a decision, and it is absent until a\nhuman makes it.\n\n## What you never write\n\n- A legal basis, a lawful-processing justification, or a controller/processor role.\n- A retention period the product has not chosen, or one you inferred from a default.\n- A named human, a reviewer, a qualification or an independence statement. Every fact you produce\n carries `APPLICATION_SPECIFICATION` authority — the accepted specification is the authority, and it\n is the only one a derivation can honestly claim.\n- A decision instant. You have no clock, and the honest instant for a human decision is the commit that\n records it.\n- A security claim beyond what the application's configuration actually shows.\n- A fact about a provider, region or capability the application has not configured.\n\n## Refs are stamped for you\n\nSupply slugs — `retention-rules`, `data-categories-and-sources`, `recipients-and-processors`. The\nruntime turns each into its namespaced ref, attaches the governance scope and authority, assigns\nversions and sorts the declarations. Do not author a ref, a version or an ordering; a contract that\nasked you to would be asking you to fail on form rather than on substance.\n\nUse a stable, descriptive `factSlug` — it is the name a document clause will cite, so it should read as\nthe question it answers.\n\n## Verification\n\nBefore you finish, check each declaration against these:\n\n- [ ] every `KNOWN` value states something a reader could act on, and is traceable to accepted truth;\n- [ ] no declaration encodes a decision (legal basis, role, governing law, liability, chosen retention);\n- [ ] every `NOT_APPLICABLE` reason says why it does not apply, not that it could not be found;\n- [ ] a fact you could not establish is ABSENT, not guessed and not marked not-applicable;\n- [ ] the fact set is derived from the vision's compliance constraints, not from a generic SaaS template;\n- [ ] no `factSlug` is declared twice.\n\n## Approval\n\nThe derived fact set is presented to the creator before it becomes the committed `document-facts`\nfamily. Show it back as plain statements grouped by the question each answers, and name what you left\nout and why — the absences are the part a human most needs to see, because each one is a decision\nsomebody still owes.\n\n## Runtime context\n\n// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)\n// TODO CLI COMMAND: wildo context vision-brief (read the vision and its compliance constraints)\n// TODO CLI COMMAND: wildo context resources (read the resources and fields whose data these facts describe)\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read current journey state and the artifacts you derive from.\n",
|
|
46
|
-
"skillRefs": [
|
|
47
|
-
|
|
48
|
-
|
|
40
|
+
"guidance": "# Governed-document facts — derivation method\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## What you produce\n\nOne `document-facts` file for the application: a list of **facts**, each a plain statement about how\nthis application actually behaves. Not prose for a notice — the raw material a notice is later drafted\nfrom, and the thing a drafted clause is checked against.\n\nA fact is the answer to a question a reader of a legal document would want settled:\n\n- what categories of personal data does the application hold, and where do they come from;\n- what does it do with them, and for how long does it keep them;\n- who else sees them — providers, processors, other tenants;\n- what rights does it actually honour, and through which mechanism;\n- who operates the service, and how is it contacted.\n\n## The rule that governs everything here\n\n**Every fact you write must be supported by something the application has already accepted** — and the\nstrongest support is not prose about the application, it is **the application's own code**.\n\nRead in this order:\n\n1. **The resource declarations**, which are already in this brief, under *\"The application's\n compliance-relevant resource declarations (read from its CODE)\"*. Per resource:\n `retentionPolicy.mode` (what erasure does to a row), `dataSubjectPolicy.kind` (whose login session\n an erasure ends), `systemAccessPolicy.exportSubject` (whether an Art. 15 / Art. 20 export can answer\n for them) and `seeRetained` (the audited path to retained data). These are DECLARATIONS, already\n written down and enforced at runtime. They are the best evidence a governed document can rest on,\n and they need no interpretation — only phrasing.\n\n **Use them.** A fact about a mechanism — what is kept, what is scrubbed, what can be exported — that\n does not correspond to a declaration in that section is not derived, it is recalled, and this\n playbook's whole reason for existing is the difference.\n2. **The compliance constraints on the vision**, which tell you which facts a reader will need.\n3. **The domain plan and requirements**, for what the product is FOR — purpose, not mechanism.\n\nThe split between 1 and 3 is the point. A specification says what the application is meant to do; a\nresource configuration says what it will actually do to a row tomorrow morning. Where they disagree,\nthe configuration is the fact.\n\nThat section reports engine-declared and application-declared coverage **separately**, and you should\nkeep them apart in your facts too: the two have different owners, so they have different remedies. An\napplication's authors cannot close an engine gap, and the engine's maintainers cannot close theirs.\n\nDo not assume the engine half is the settled half. Read the counts. On the first real application to\nbe measured, the engine declared an erasure treatment on **two of eighty-five** resources — the user\naccount and its self-view — and nothing on credentials, profiles, audit logs, files or membership.\nWhatever the numbers say in your own brief, they are the fact; a sentence crediting the framework with\ndeclarations it has not made is exactly as false as one crediting the application.\n\n## COVER THE WHOLE SET — this is the half a first attempt gets wrong\n\nThe facts you declare here are the only thing a later document can state as established. A concern you\nsay nothing about does not become a cautious sentence in the notice; it becomes a clause reading *\"this\nhas not yet been established\"*, in a document about somebody's personal data, when the application had\nalready established it.\n\nMeasured on the first real application (wonder-crm, 2026-08-29): this pass produced **three** facts, and\nthe notice drafted from them marked **ten of thirteen** concerns incomplete — including subject rights,\nwhich every one of that application's resources declares, and analytics, which it does not enable. Both\nwere answerable from the brief in front of it. That is the failure mode to avoid, and it is not caution:\na notice that understates what an application does is as wrong as one that overstates it.\n\nWork through this list and declare a fact for each one you can answer:\n\n| what a document will need | where the answer is |\n|---|---|\n| what personal data is held, and in which records | the resource declarations + the domain plan |\n| what erasure does to each record | `retentionPolicy.mode` per resource |\n| how long records are kept | the RETENTION SCHEDULE in your brief — four classes, each declared or UNDECIDED |\n| whether a subject-access or portability export can answer for a record | `systemAccessPolicy.exportSubject` per resource |\n| whether retained data stays reachable, and audited | `systemAccessPolicy.seeRetained` per resource |\n| who else can see the data inside the application | the domain model — roles, membership, sharing |\n| which third parties receive data, WHO they are and WHERE they process | the PROCESSOR REGISTER section — declared entries, plus the providers it lists UNDECLARED |\n| whether the application makes automated decisions or uses AI | the AI POSTURE section — per enabled capability, a declared consequence or OUTSTANDING |\n| what analytics or tracking runs, and what is stored in a browser | the declared capabilities + the CLIENT STORAGE section (framework entries, then per surface) |\n| what consent the application asks for | the declared capabilities + the domain plan |\n| how organizations are separated from each other | the domain model and the tenancy declarations |\n\n## RECORD THE GAPS AS FACTS TOO — nothing downstream can see this brief\n\nThe sections above are yours alone. The pass that drafts the document reads the `document-facts` FILE\nand nothing else — it never sees the resource declarations, the retention schedule, the processor\nregister, the AI posture or the client-storage inventory. **A gap you notice and do not write down is a\ngap that disappears**, and the document then states the half that was answered as though it were the\nwhole.\n\nSo when a section names something as `UNDECIDED`, `UNDECLARED`, `OUTSTANDING` or `UNINVENTORIED`,\ndeclare a fact recording it, naming what is missing:\n\n- *\"No retention period is declared for any of the four data classes; all four require an operator\n decision.\"*\n- *\"The `app` frontend surface's own client storage has not been catalogued.\"*\n\nThis is the failure mode to avoid, measured on a real run: the facts stated that no consent-gated\nbrowser storage is configured — true — and said nothing about the frontend surface nobody had\ninventoried. A reader of the notice would take the first as the whole answer.\n\nA gap recorded as a fact is `KNOWN`: the thing that is known IS the gap. Do not use `NOT_APPLICABLE`\nfor it — that says the question does not arise, and it does.\n\n**An UNDECIDED retention period is an OPERATOR's decision, not a framework gap.** The application can\ndeclare a period for each of the four data classes and has not for some of them. State which classes\nare declared, with their periods and the reasons given, and state plainly which are still undecided —\nthe remedy is an operator deciding, not the framework growing a mechanism. Never write a period the\napplication has not declared, and never soften an absent one into \"as long as necessary\": that is a\ncommitment nobody made and nothing enforces.\n\n**An absent capability is a fact, not a silence.** If no analytics provider is configured, that is\n`KNOWN`: *\"no external analytics provider is configured\"*. If no AI capability is declared, say so. These\nare the answers that let a notice state something true instead of confessing ignorance about a decision\nthe application already made — and the composition section in your brief lists them exactly.\n\n**Declare mechanism facts per RESOURCE where the resources differ.** \"All eight application resources\ndeclare a subject-export mode\" is a usable fact; \"the application supports exports\" is not, because a\nreader cannot tell which records it covers.\n\nYou are **not** deciding anything. A legal basis, a controller-versus-processor role, a governing law,\na liability position and a retention *duration the product has not chosen* are all decisions, and none\nof them is yours. If a fact needs a human to decide it, **leave it out**. Do not write a plausible\nplaceholder, and do not soften a decision into a fact by hedging the wording.\n\nLeaving it out is not a failure — it is the designed behaviour, and it does **not** block anything\ndownstream. A document clause that would have rested on a fact you did not declare is still written:\nit is marked as not yet established, names what it needs and who can supply it, and the document is\nproduced. So an absence costs the reader a precise statement of a gap, which is useful. A guessed fact\ncosts them a published false statement about somebody's data, which is not.\n\n## The shape of a declaration — get this right or the whole file is rejected\n\nEach declaration carries three slugs, all lowercase kebab-case (`retention-treatment-per-resource`),\nand **every one of them must be UNIQUE across the file**:\n\n- `slug` — names THIS declaration. Two declarations sharing a `slug` are rejected, and this is the\n single most common way a good fact set fails: a drafter answering several facts about retention\n gives them all `slug: \"retention\"`. Make each one describe its own fact.\n- `factSlug` — names the FACT being answered. One governance scope carries one answer per fact, so two\n declarations may not share a `factSlug` either. If you want to say two things about retention, they\n are two facts (`retention-treatment-per-resource`, `retention-duration`), not one fact twice.\n- `sensitivitySlug` — how sensitive the fact itself is (`public`, `internal-governance`). This one MAY\n repeat; it is a classification, not an identity.\n\nA rejection naming `declarations.N.slug` is almost always a COLLISION rather than a bad character:\nre-read your list for two entries sharing a name.\n\n## KNOWN and NOT_APPLICABLE are different answers — and both are different from absence\n\nThree states, and confusing them is the most common way this pass goes wrong.\n\n| state | means | how you write it |\n|---|---|---|\n| `KNOWN` | the application does this, and here is what it does | `resolution: KNOWN` with `value` |\n| `NOT_APPLICABLE` | this was considered and it genuinely does not apply | `resolution: NOT_APPLICABLE` with `reason` |\n| absent | nobody has established this yet | omit the declaration entirely |\n\n`NOT_APPLICABLE` is a real, useful answer — \"this application performs no international transfers\"\ntells a reviewer something. It is **not** a way to dispose of a fact you could not find. If you do not\nknow, the honest output is absence.\n\nA `KNOWN` fact must carry an actual value. An empty string, a blank one or an empty object is rejected\nby the validator: a fact that exists and says nothing is worse than a missing one, because a document\ncan cite it and learn nothing.\n\n## Read the compliance constraints first\n\n`top_down.compliance-posture` records each applicable regime as a `compliance`-kind constraint on the\nvision. Those constraints tell you which facts matter. A GDPR constraint means a reader will need data\ncategories, purposes, retention, recipients, transfers and rights mechanisms. A data-residency\nconstraint means where data lives is a fact worth stating.\n\nDerive the fact SET from the regimes, then answer each one from the application's own truth — the\nconfigurations first. Where the regime implies a fact the application has not settled, that is an\nabsence: record nothing, and let the document state the gap in place.\n\n## Scope: one operator, deliberately\n\nEvery fact you write is attributed to one application-operator governance scope. The family can carry\nfacts for a tenant organization or a shared-responsibility boundary too, but choosing a different\nsubject per fact is deciding **shared-responsibility attribution**, which is exactly the thing that\nmust never be guessed or flattened. One operator scope is the honest output of a derivation; a second\nsubject is a human's edit.\n\nThe `operatorSlug` you supply is an operator identity, **not** a legal-entity assertion. It names who\nruns the service, not which company is on the contract — that is a decision, and it is absent until a\nhuman makes it.\n\n## What you never write\n\n- A legal basis, a lawful-processing justification, or a controller/processor role.\n- A retention period the product has not chosen, or one you inferred from a default.\n- A named human, a reviewer, a qualification or an independence statement. Every fact you produce\n carries `APPLICATION_SPECIFICATION` authority — the accepted specification is the authority, and it\n is the only one a derivation can honestly claim, and since 2026-09-03 the only one the family's TYPE\n accepts. A declaration carrying any other authority is refused before it reaches a file.\n- A decision instant. You have no clock, and the honest instant for a human decision is the commit that\n records it.\n- A security claim beyond what the application's configuration actually shows.\n- A fact about a provider, region or capability the application has not configured.\n\n## The file you write is REGENERATED WHOLE, and a second family holds what you must not touch\n\nYour output replaces `document-facts` entirely on every run. That is why the facts only a human may\nestablish — a creator decision, a qualified review — live in a SEPARATE family,\n`document-facts-authored`, which you neither read nor write. Before the two were split they shared one\nfile, and a producer run silently deleted the human half.\n\nSo an absent fact is never something for you to fill in \"because nobody else will\". The brief already\nnames which facts are yours; anything it withholds has a home you cannot reach, and leaving it absent\nis the correct outcome rather than a gap you are working around.\n\n## Some facts are COMPUTED, and you do not declare them\n\nA few facts are not written by anyone. The runtime computes them from the application's own typed\ndeclarations every time the facts are read:\n\n- `controller-and-contact` is computed from `operatorComplianceIdentity`;\n- `recipients-and-processors` is computed from the processor register and the providers' deployment\n choices;\n- `lawful-bases` is computed from `operatorComplianceIdentity.lawfulBases`;\n- `retention-rules` is computed from the `dataRetention` schedule and each resource's erasure treatment;\n- `international-transfers` is computed from each register entry's `transferDetermination`;\n- `rights-and-complaint-route` is computed from the operating jurisdictions, the lawful bases, the\n privacy contact, the identity-verification procedure and the role allocations;\n- `retention-enforcement` is computed from the retention-enforcement records the evidence plane\n collected;\n- `system-of-record-sources` is computed from the resources bound to, or copied from, a declared\n system of record, and the purposes their bindings link.\n\nThis list is a convenience. The brief's \"do not declare\" heading is the authority.\n\nThe brief lists them under a separate \"do not declare\" heading. Declaring one is refused at\ngeneration, and a copy in the file is refused by the family's validator.\n\nThe reason is drift. Your answer would be a paraphrase of a declaration that already exists, and it\nwould go stale the day that declaration changes. If the declaration a computed fact reads is missing,\nthe fact stays absent, and the documents mark it as owed. Leave that gap alone. Do not state a\ncontroller, a recipient, a basis, a period, a transfer or a right in prose to fill it: say what is missing in a fact you do own, or leave it to\nthe document's gap marking.\n\n## A judge reads your facts against what you were given\n\nAfter the file lands, an advisory judge reads every declaration beside the same evidence you had: the\ninput families, the application's compliance-relevant declarations and the computed facts. It reports\ntwo kinds of finding. A **gap** is a claim a governed document would publish as true that nothing\nestablishes: a recipient, a transfer, a retention period, a lawful basis or an AI use that no\ndeclaration names, or an undeclared matter stated as settled. A **concern** is wording drift a reader\nwould not act on differently.\n\nThe judge refuses nothing, and a finding does not undo your file. It is written so that an unsupported\nclaim is named before a document cites it. Write each fact so that its source is obvious from the\nwords.\n\n## Refs are stamped for you\n\nSupply slugs. The runtime turns each into its namespaced ref, attaches the governance scope and\nauthority, assigns versions and sorts the declarations. Do not author a ref, a version or an ordering;\na contract that asked you to would be asking you to fail on form rather than on substance.\n\n(This paragraph listed `retention-rules`, `data-categories-and-sources` and\n`recipients-and-processors` as examples. All three are required fact names, and naming three of eight\nas \"examples\" invited a drafter to treat them as a style to imitate rather than a set to use. The\nauthoritative list now arrives in the brief.)\n\n**For a concern a governed document requires, the slug is NOT yours to choose.** The brief you were\ngiven lists the exact `factSlug` for each one, taken from the engine catalog. Use it verbatim.\n\nThis is not a style preference. A clause cites a fact BY REF, the ref is stamped from your slug, and a\nfact answering the right question under a different name is a fact the document cannot cite — it reads\nas missing while your answer sits in the file. Measured on a real run: twenty facts declared, zero of\nthe eight a privacy notice requires, because the names were semantically adjacent and lexically\ndisjoint (`retention-period-schedule-status` for `retention-rules`).\n\nFor anything the catalog does NOT name, the slug is yours: use a stable, descriptive one that reads as\nthe question it answers. An application legitimately declares facts no document requires.\n\n## Verification\n\nBefore you finish, check each declaration against these:\n\n- [ ] every `KNOWN` value states something a reader could act on, and is traceable to accepted truth;\n- [ ] no declaration encodes a decision (legal basis, role, governing law, liability, chosen retention);\n- [ ] every `NOT_APPLICABLE` reason says why it does not apply, not that it could not be found;\n- [ ] a fact you could not establish is ABSENT, not guessed and not marked not-applicable;\n- [ ] the fact set is derived from the vision's compliance constraints, not from a generic SaaS template;\n- [ ] no `factSlug` is declared twice.\n\n## Approval\n\nThe derived fact set is presented to the creator before it becomes the committed `document-facts`\nfamily. Show it back as plain statements grouped by the question each answers, and name what you left\nout and why — the absences are the part a human most needs to see, because each one is a decision\nsomebody still owes.\n\n## Runtime context\n\nEverything above is already in your brief: `vision-brief` / `domain-plan` / `requirements` render as\ninput sections under \"# Accepted application truth\", and the application's live resource\nDECLARATIONS (retention mode, data-subject kind, subject export, retained see-through) arrive as\nthe declared `compliance_primary_facts` context section of your brief. Derive facts from those sections; there is no command to\nrun in this mode.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n\n## External sign-in assurance\n\nDerive `document-fact:external-sign-in-assurance` from the brief's declared authentication policy, including organization restrictions. Do not infer an active enterprise connection from an enabled method. Describe enterprise OAuth2/OIDC responsibility delegation separately from observed MFA. For social login, name the configured warning/strict treatment and provider evidence limitations. An unreadable configuration remains unresolved, never “no external login”. Feed this fact into the service-terms account-duties clause; liability conclusions still require qualified review.\n",
|
|
41
|
+
"skillRefs": [],
|
|
42
|
+
"skillBodyRefs": [],
|
|
43
|
+
"contextSources": [
|
|
44
|
+
"compliance_primary_facts",
|
|
45
|
+
"document_fact_obligations"
|
|
46
|
+
],
|
|
47
|
+
"draftableDocumentDefinitionRefs": [],
|
|
48
|
+
"suspendsForClarification": false,
|
|
49
|
+
"briefAdequacyGate": false,
|
|
50
|
+
"briefAdequacyExcludedSources": []
|
|
49
51
|
},
|
|
50
52
|
"executor": "companion_agent",
|
|
51
|
-
"qualityGates": [
|
|
52
|
-
{
|
|
53
|
-
"ref": "document-fact-specification-valid",
|
|
54
|
-
"kind": "deterministic_validator",
|
|
55
|
-
"validatorRef": "saas-specifications:validateApplicationDocumentFactSpecification",
|
|
56
|
-
"required": true
|
|
57
|
-
}
|
|
58
|
-
],
|
|
59
53
|
"approval": "approve_result",
|
|
60
54
|
"budget": {
|
|
61
55
|
"maxRuns": 3
|
|
@@ -0,0 +1,48 @@
|
|
|
1
|
+
# Feature contribution — one feature, added to the product model
|
|
2
|
+
|
|
3
|
+
### Target Application Framing
|
|
4
|
+
|
|
5
|
+
This knowledge is for configuring behavior in the target application.
|
|
6
|
+
Wildo is the framework surface being used, not the product being built.
|
|
7
|
+
|
|
8
|
+
Read and apply these patterns from the application-developer point of view:
|
|
9
|
+
|
|
10
|
+
- how the application should configure the relevant app-level file
|
|
11
|
+
- how the application should use framework-provided factories, enums, and helpers
|
|
12
|
+
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
13
|
+
|
|
14
|
+
|
|
15
|
+
This step runs for a **feature-development line**: work opened beside the application's main line to add
|
|
16
|
+
ONE feature. What the line is for is written above, under "What this run is for", in the creator's own
|
|
17
|
+
words. That is the feature. Nothing else is in scope.
|
|
18
|
+
|
|
19
|
+
## What you return
|
|
20
|
+
|
|
21
|
+
Two outputs, and each holds **only what this feature adds**:
|
|
22
|
+
|
|
23
|
+
- **Requirements.** The functional requirements the feature adds, in the `functional` list, each with a
|
|
24
|
+
ref that does not exist yet (`functional-requirement-<slug>`). Leave `nonFunctional` empty: the
|
|
25
|
+
application's qualities are the main line's.
|
|
26
|
+
- **Feature drafts.** One draft per capability the feature needs, each with a feature ref that does not
|
|
27
|
+
exist yet, its purpose and business role tracing to the requirements you add.
|
|
28
|
+
|
|
29
|
+
What you return is ADDED beside what the application already holds, and each element is recorded as this
|
|
30
|
+
line's. So:
|
|
31
|
+
|
|
32
|
+
- Do not copy the application's existing requirements or drafts into your output. An element you hand back
|
|
33
|
+
unchanged is ignored; an element you hand back CHANGED under an existing ref is refused, and the whole
|
|
34
|
+
run with it, because a line never redrafts what someone else decided.
|
|
35
|
+
- If the feature genuinely changes an existing requirement, say so in the new requirement's rationale
|
|
36
|
+
(which existing ref it extends or supersedes). Changing the existing one is the main line's decision.
|
|
37
|
+
- Re-running this step for the same line updates the elements this line added. It never removes one: an
|
|
38
|
+
element you leave out stays as it was.
|
|
39
|
+
|
|
40
|
+
## How to describe the feature
|
|
41
|
+
|
|
42
|
+
Read the vision and the requirements whole, and the domain plan as a map of what the application already
|
|
43
|
+
models. Describe the feature against them: name the resources it touches in the requirement's statement
|
|
44
|
+
when that helps, but design nothing. The domain plan and the build are re-derived from your requirements
|
|
45
|
+
afterwards, by the application, and that is where the design happens.
|
|
46
|
+
|
|
47
|
+
Prefer fewer, sharper requirements. Each must be checkable: give acceptance criteria a reviewer could
|
|
48
|
+
test against the built feature.
|
|
@@ -0,0 +1,66 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ref": "refinement.feature-contribution",
|
|
3
|
+
"version": "0.1.0",
|
|
4
|
+
"phase": "refinement",
|
|
5
|
+
"intent": "Add ONE feature to the product model, as the feature-development line it runs for describes it: the functional requirements the feature adds, and one spec-first, ref-less feature draft per capability it needs, each tracing to those requirements. Return only what the feature adds; everything the application already holds stays as it is.",
|
|
6
|
+
"preconditions": [
|
|
7
|
+
{
|
|
8
|
+
"kind": "artifact_valid",
|
|
9
|
+
"selector": {
|
|
10
|
+
"family": "vision-brief"
|
|
11
|
+
}
|
|
12
|
+
},
|
|
13
|
+
{
|
|
14
|
+
"kind": "artifact_valid",
|
|
15
|
+
"selector": {
|
|
16
|
+
"family": "requirements"
|
|
17
|
+
}
|
|
18
|
+
}
|
|
19
|
+
],
|
|
20
|
+
"inputs": [
|
|
21
|
+
{
|
|
22
|
+
"family": "vision-brief"
|
|
23
|
+
},
|
|
24
|
+
{
|
|
25
|
+
"family": "requirements"
|
|
26
|
+
},
|
|
27
|
+
{
|
|
28
|
+
"family": "feature-drafts"
|
|
29
|
+
},
|
|
30
|
+
{
|
|
31
|
+
"family": "domain-plan",
|
|
32
|
+
"render": "map"
|
|
33
|
+
}
|
|
34
|
+
],
|
|
35
|
+
"outputs": [
|
|
36
|
+
{
|
|
37
|
+
"family": "requirements",
|
|
38
|
+
"schemaRef": "saas-specifications:RequirementsSnapshot",
|
|
39
|
+
"description": "ONLY the functional requirements this feature adds, each with a new `functional-requirement-` ref; no non-functional requirements."
|
|
40
|
+
},
|
|
41
|
+
{
|
|
42
|
+
"family": "feature-drafts",
|
|
43
|
+
"schemaRef": "saas-specifications:FeatureSpecificationDrafts",
|
|
44
|
+
"description": "ONLY the feature drafts this feature adds, each with a new feature ref."
|
|
45
|
+
}
|
|
46
|
+
],
|
|
47
|
+
"stepOutputs": [],
|
|
48
|
+
"method": {
|
|
49
|
+
"guidance": "# Feature contribution — one feature, added to the product model\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 step runs for a **feature-development line**: work opened beside the application's main line to add\nONE feature. What the line is for is written above, under \"What this run is for\", in the creator's own\nwords. That is the feature. Nothing else is in scope.\n\n## What you return\n\nTwo outputs, and each holds **only what this feature adds**:\n\n- **Requirements.** The functional requirements the feature adds, in the `functional` list, each with a\n ref that does not exist yet (`functional-requirement-<slug>`). Leave `nonFunctional` empty: the\n application's qualities are the main line's.\n- **Feature drafts.** One draft per capability the feature needs, each with a feature ref that does not\n exist yet, its purpose and business role tracing to the requirements you add.\n\nWhat you return is ADDED beside what the application already holds, and each element is recorded as this\nline's. So:\n\n- Do not copy the application's existing requirements or drafts into your output. An element you hand back\n unchanged is ignored; an element you hand back CHANGED under an existing ref is refused, and the whole\n run with it, because a line never redrafts what someone else decided.\n- If the feature genuinely changes an existing requirement, say so in the new requirement's rationale\n (which existing ref it extends or supersedes). Changing the existing one is the main line's decision.\n- Re-running this step for the same line updates the elements this line added. It never removes one: an\n element you leave out stays as it was.\n\n## How to describe the feature\n\nRead the vision and the requirements whole, and the domain plan as a map of what the application already\nmodels. Describe the feature against them: name the resources it touches in the requirement's statement\nwhen that helps, but design nothing. The domain plan and the build are re-derived from your requirements\nafterwards, by the application, and that is where the design happens.\n\nPrefer fewer, sharper requirements. Each must be checkable: give acceptance criteria a reviewer could\ntest against the built feature.\n",
|
|
50
|
+
"skillRefs": [
|
|
51
|
+
"spec-feature-update"
|
|
52
|
+
],
|
|
53
|
+
"skillBodyRefs": [],
|
|
54
|
+
"contextSources": [],
|
|
55
|
+
"draftableDocumentDefinitionRefs": [],
|
|
56
|
+
"suspendsForClarification": false,
|
|
57
|
+
"briefAdequacyGate": false,
|
|
58
|
+
"briefAdequacyExcludedSources": []
|
|
59
|
+
},
|
|
60
|
+
"executor": "companion_agent",
|
|
61
|
+
"approval": "approve_result",
|
|
62
|
+
"budget": {
|
|
63
|
+
"maxRuns": 3
|
|
64
|
+
},
|
|
65
|
+
"onFailure": "keep_and_flag"
|
|
66
|
+
}
|
package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-protocol.json
ADDED
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"aggregationPolicyRef":"application-creation:aggregation/worst-governance-document-claims-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/governance-document-claims-within-guard","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/governance-document-claims-within-guard","requirementVersion":1}],"instruction":"The subject under judgment is each landed `compliance-document-candidate` for an INTERNAL governance document. 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. Two things are judged here that a public notice does not meet. FIRST, a FABRICATED RECORD OF REVIEW: a named reviewer, an approver, an approval, an independence disclosure, a qualification or a decision instant that the application has not declared is a GAP, whatever else the clause gets right — a governance document is where those are recorded, and inventing one records a review that did not happen. SECOND, an UNSUPPORTED OPERATING claim: a sentence asserting that a control operates, works or worked ('we monitor', 'access is reviewed quarterly', 'the trail is checked') rather than that something is configured or declared. In an INTERNAL governance document such a claim is legitimate when THREE things hold together: the clause cites a judged run in `evidenceRefs`, that run's verdict CONCLUDED (CONFORMANT or OBSERVATION, never INSUFFICIENT_EVIDENCE or NONCONFORMITY), and the clause states what was measured and over what period. An operating claim missing any of the three is a GAP — uncited it rests on nothing, citing an unconcluded run it rests on a question nobody settled, and without scope or period the reader it is written for cannot check it. A citation may never be laundered either: the runs are the operator judging its own product, so a clause may say what was measured and may NOT say it was verified, certified, audited or independently assured. Also look for: certification, attestation or audit claimed without the authority to make it; a legal conclusion rather than a statement of what the operator does; a NIST publication presented as legal equivalence; self-attestation presented as independent assurance; and an unscoped compliance claim (\"fully secure\", \"ISO-ready\"). Do NOT re-check whether cited facts exist — landing already decided that exactly — and do NOT treat a clause MARKED as not established as a defect: marking is what this lane is for. Name every finding by its `clauseRef`, quote the words, and name the prohibited claim it falls under. Separate severities by CONSEQUENCE: a claim an assurance reader 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 an assurance reader could take as the claim — a softened operating assertion, a review implied by the passive voice, a scope left implicit. Name each clauseRef and quote it.","GAP":"At least one clause asserts a prohibited claim an assurance reader would rely on — most seriously, a record of review nobody performed, or a control asserted to operate with nothing able to support it. 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: none names a reviewer, approval, independence or decision instant the application has not declared; none asserts that a control operates; none certifies, concludes the law, equates NIST with law, presents self-attestation as independence, or claims unscoped compliance. Marked clauses are not findings."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/governance-document-claims","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:refinement.governance-document-candidate"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
|
package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-treatment.json
ADDED
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-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/governance-document-claims-within-guard"],"requirementRef":"application-creation:authority-requirement/governance-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/governance-document-claims","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/governance-document-claims","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/governance-document-claims","policyVersion":1},"decisionPointRef":"application-creation:decision-point/governance-document-claims","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/governance-document-claims","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/governance-document-claims","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/governance-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-governance-document-claims-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/governance-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/governance-document-claims","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/governance-document-claims","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-governance-document-claims-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/governance-document-claims-within-guard","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/governance-document-claims-within-guard","requirementVersion":1}],"instruction":"The subject under judgment is each landed `compliance-document-candidate` for an INTERNAL governance document. 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. Two things are judged here that a public notice does not meet. FIRST, a FABRICATED RECORD OF REVIEW: a named reviewer, an approver, an approval, an independence disclosure, a qualification or a decision instant that the application has not declared is a GAP, whatever else the clause gets right — a governance document is where those are recorded, and inventing one records a review that did not happen. SECOND, an UNSUPPORTED OPERATING claim: a sentence asserting that a control operates, works or worked ('we monitor', 'access is reviewed quarterly', 'the trail is checked') rather than that something is configured or declared. In an INTERNAL governance document such a claim is legitimate when THREE things hold together: the clause cites a judged run in `evidenceRefs`, that run's verdict CONCLUDED (CONFORMANT or OBSERVATION, never INSUFFICIENT_EVIDENCE or NONCONFORMITY), and the clause states what was measured and over what period. An operating claim missing any of the three is a GAP — uncited it rests on nothing, citing an unconcluded run it rests on a question nobody settled, and without scope or period the reader it is written for cannot check it. A citation may never be laundered either: the runs are the operator judging its own product, so a clause may say what was measured and may NOT say it was verified, certified, audited or independently assured. Also look for: certification, attestation or audit claimed without the authority to make it; a legal conclusion rather than a statement of what the operator does; a NIST publication presented as legal equivalence; self-attestation presented as independent assurance; and an unscoped compliance claim (\"fully secure\", \"ISO-ready\"). Do NOT re-check whether cited facts exist — landing already decided that exactly — and do NOT treat a clause MARKED as not established as a defect: marking is what this lane is for. Name every finding by its `clauseRef`, quote the words, and name the prohibited claim it falls under. Separate severities by CONSEQUENCE: a claim an assurance reader 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 an assurance reader could take as the claim — a softened operating assertion, a review implied by the passive voice, a scope left implicit. Name each clauseRef and quote it.","GAP":"At least one clause asserts a prohibited claim an assurance reader would rely on — most seriously, a record of review nobody performed, or a control asserted to operate with nothing able to support it. 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: none names a reviewer, approval, independence or decision instant the application has not declared; none asserts that a control operates; none certifies, concludes the law, equates NIST with law, presents self-attestation as independence, or claims unscoped compliance. Marked clauses are not findings."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/governance-document-claims","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:refinement.governance-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/governance-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/governance-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/governance-document-claims-within-guard","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/governance-document-candidates-and-catalog-claim-guards"}],"schemaVersion":1}
|
|
@@ -0,0 +1,349 @@
|
|
|
1
|
+
# Governance document candidate method
|
|
2
|
+
|
|
3
|
+
You are drafting ONE internal governance document for this application, from what the application has
|
|
4
|
+
already declared. Follow the `compliance-document-authoring` skill for the rules — refs, clause shape,
|
|
5
|
+
completeness, what a clause may say. This method says which document, what its concerns are, and the two
|
|
6
|
+
things a governance document meets that a public notice does not.
|
|
7
|
+
|
|
8
|
+
## Choose the document, from the four this lane may draft
|
|
9
|
+
|
|
10
|
+
The candidate contract admits six `documentRef` values. Four of them are this lane's; the two public ones
|
|
11
|
+
(`document:public.privacy-notice`, `document:public.service-terms`) belong to
|
|
12
|
+
`refinement.compliance-document-candidate` and are not yours to draft here.
|
|
13
|
+
|
|
14
|
+
| `documentRef` | what it is | its concerns |
|
|
15
|
+
|---|---|---|
|
|
16
|
+
| `document:governance.scope-system-description` | what the system IS, for an assurance reader | service scope, security controls, audit and accountability, access control and roles, tenancy model |
|
|
17
|
+
| `document:governance.roles-responsibilities` | who is accountable for what | access control and roles, operator identity |
|
|
18
|
+
| `document:governance.program-handbook` | how the governance programme runs | security controls, audit and accountability, access control and roles |
|
|
19
|
+
| `document:governance.document-record-control` | how governed documents are themselves controlled | **none** — see below |
|
|
20
|
+
|
|
21
|
+
**Draft a document this application does not already hold.** The brief opens with what it has already
|
|
22
|
+
drafted, listing each document this lane may produce as ALREADY DRAFTED or not yet. Drafts are keyed by
|
|
23
|
+
`documentRef`, so drafting one that is already there REPLACES it — right when that draft is wrong, a
|
|
24
|
+
wasted run when it is not.
|
|
25
|
+
|
|
26
|
+
**A held draft marked ALREADY DRAFTED, and WRONG comes before everything below.** The brief marks a held
|
|
27
|
+
draft that cites facts this application no longer declares, and names them. Nothing else corrects it: the
|
|
28
|
+
landing checks only the document a run writes, so a draft written before the facts were regenerated keeps
|
|
29
|
+
its dead citations until a run redrafts that document. Redraft it against the facts that exist, and cite
|
|
30
|
+
none of the named ones.
|
|
31
|
+
|
|
32
|
+
Where several remain, **scope and system description** comes first: it is the one an assurance reader
|
|
33
|
+
opens first, the one the other three refer back to, and the only one of the four carrying facts the
|
|
34
|
+
framework derives rather than a person establishes.
|
|
35
|
+
|
|
36
|
+
`document:governance.document-record-control` composes **no application-fact concern**, and that is
|
|
37
|
+
declared rather than missing: it describes how documents are identified, reviewed, released and retired —
|
|
38
|
+
a process the operator defines, not anything derivable from the product. Every section you write for it
|
|
39
|
+
carries `concernRef: null`, and almost every clause is marked. That is the document working, not failing.
|
|
40
|
+
|
|
41
|
+
## Expect to MARK, and never invent your way past a mark
|
|
42
|
+
|
|
43
|
+
Most of what a governance document asserts is established by a PERSON, not derived from the application.
|
|
44
|
+
Measured on the blueprints: `roles-responsibilities` and `document-record-control` carry no
|
|
45
|
+
specification-derived fact at all — every one of their facts needs a creator decision or a qualified
|
|
46
|
+
review — and the other two carry a handful.
|
|
47
|
+
|
|
48
|
+
So a governance draft that is largely marked incomplete is the expected outcome. Draft every section,
|
|
49
|
+
state precisely what is missing in `incompleteness.needs` and what would close it in
|
|
50
|
+
`incompleteness.closedBy`, and let the marks be the document's contribution. An application that can read
|
|
51
|
+
exactly which governance decisions it owes is further ahead than one holding no document at all.
|
|
52
|
+
|
|
53
|
+
**Two inventions are worse than any gap, and both are specific to these documents.**
|
|
54
|
+
|
|
55
|
+
- **A record of review that did not happen.** These are the documents where a reviewer, an approver, an
|
|
56
|
+
approval, an independence disclosure, a qualification and a decision instant are NAMED. Write one the
|
|
57
|
+
application has not declared and you have not written a weak sentence — you have fabricated the record
|
|
58
|
+
of a review nobody performed. Mark it instead: the fact is owed, and saying so is the answer.
|
|
59
|
+
- **A control asserted to OPERATE, with nothing behind it.** "Access is reviewed quarterly", "we
|
|
60
|
+
monitor", "the trail is checked" are claims about operating effectiveness. In THIS lane one of them
|
|
61
|
+
may be legitimate — and only when a judged run in your brief's evidence section supports it, the
|
|
62
|
+
clause cites that run, and the clause says what was measured and over what period. Without all three,
|
|
63
|
+
say what is CONFIGURED or DECLARED, which is what the facts give you, and mark the rest.
|
|
64
|
+
|
|
65
|
+
## One section per concern, and SAY which concern
|
|
66
|
+
|
|
67
|
+
Every section carries `concernRef` from the closed compliance-concern vocabulary, or `null` for a section
|
|
68
|
+
that genuinely answers no concern — a preamble, a scope statement, and every section of
|
|
69
|
+
`document-record-control`. Draft one section per concern in the order the table above gives, and produce
|
|
70
|
+
**every** one: a concern nothing can answer becomes a section with a marked clause, never a missing
|
|
71
|
+
heading.
|
|
72
|
+
|
|
73
|
+
The value must be the concern's exact name. A near miss (`access-control` for
|
|
74
|
+
`access-control-and-roles`) is worse than a null: it reports the concern as unaddressed while the
|
|
75
|
+
document addresses it.
|
|
76
|
+
|
|
77
|
+
Each section also names what it satisfies in the catalog — `satisfiesSectionRefs` on the section,
|
|
78
|
+
`satisfiesClauseRefs` on each clause, from the blueprint in your brief. Those are what attach the
|
|
79
|
+
catalog's claim guards to your clauses, so a clause that says what it satisfies is checked against what it
|
|
80
|
+
must not claim, automatically. A clause that says nothing is checked against nothing.
|
|
81
|
+
|
|
82
|
+
A section that supplies no required part of the document answers **`null`**, never `[]` — an empty array
|
|
83
|
+
is refused, because it would be a second spelling of the same state. On a governance document the sections
|
|
84
|
+
that answer `null` are the ones with `concernRef: null` beside them, and `document-record-control` is
|
|
85
|
+
mostly made of them.
|
|
86
|
+
|
|
87
|
+
## The three ref arrays on every clause
|
|
88
|
+
|
|
89
|
+
Every `…Ref` field is a **namespaced ref**: `namespace:slug`, both halves lowercase, words joined by
|
|
90
|
+
hyphens. One malformed ref rejects the whole draft, and all three arrays are required on every clause —
|
|
91
|
+
two of them may be empty, but **not the first two at once**, because a clause naming neither a fact nor a
|
|
92
|
+
policy area is sourced by nothing.
|
|
93
|
+
|
|
94
|
+
- `factRefs` — the facts this clause rests on, spelled exactly as the facts file declares them. EMPTY is
|
|
95
|
+
normal here: a marked clause usually establishes nothing.
|
|
96
|
+
- `sourcePolicyRefs` — the application POLICY AREA the statement is sourced from, and **every entry must
|
|
97
|
+
be in the `policy:` namespace**: `policy:security-controls`, `policy:access-control`,
|
|
98
|
+
`policy:document-control`. Any other namespace is rejected outright — `policy-area:…` is not a policy
|
|
99
|
+
ref, and neither is a fact ref repeated here. **Do NOT put a fact or its authority in this array.** A
|
|
100
|
+
clause resting on declared facts already cites them through `factRefs`, which resolves them; restating
|
|
101
|
+
one here duplicates the citation beside it and resolves to nothing. So this array is EMPTY for a
|
|
102
|
+
fact-backed clause, and carries a policy area for a clause sourced from a policy rather than a fact.
|
|
103
|
+
- `claimGuardRefs` — at least one: what this clause must NOT be read as claiming. Name the ones that
|
|
104
|
+
apply; do not repeat the same guard on every clause out of habit. You do not name the CATALOG's guard
|
|
105
|
+
for the material — that is added for you from the blueprint clauses this clause `satisfiesClauseRefs`.
|
|
106
|
+
|
|
107
|
+
`reviewChecklistRefs` needs at least one (`review-checklist:<slug>`): what a human must confirm before
|
|
108
|
+
this draft is worth anything. On a governance document that list is long, and it is where "who reviewed
|
|
109
|
+
this, and when" belongs — as something a person must supply, never as a name you write into a clause.
|
|
110
|
+
|
|
111
|
+
`limitationRefs` may be empty and rarely should be: it is where you say, in your own words, what this
|
|
112
|
+
document does NOT cover.
|
|
113
|
+
|
|
114
|
+
## What the blueprint gives you
|
|
115
|
+
|
|
116
|
+
the declared `document_blueprint` context section of your brief carries, for each document this lane may draft, its sections, its
|
|
117
|
+
clauses and which of them are required. Read the one matching your `documentRef` and treat its required
|
|
118
|
+
clauses as the floor: a required clause you cannot establish is a clause you MARK, never one you omit.
|
|
119
|
+
|
|
120
|
+
## Citing this application's own measured evidence
|
|
121
|
+
|
|
122
|
+
A governance document is the one place an operator may say what its controls DO, and this lane is the
|
|
123
|
+
only one that may cite the measurements behind such a statement.
|
|
124
|
+
|
|
125
|
+
the declared `assurance_evidence` context section of your brief carries the judged runs this application's own assurance cycle has
|
|
126
|
+
committed: what was measured, under which demand, with what verdict, at which framework revision, and
|
|
127
|
+
whether the judge was calibrated. Read it before writing any sentence about what a control does.
|
|
128
|
+
|
|
129
|
+
- **Cite by putting the run's `assurance-run:` ref in the clause's `evidenceRefs`**, and say in the
|
|
130
|
+
clause what was measured and over what period. A citation a reader cannot scope is one they cannot
|
|
131
|
+
check.
|
|
132
|
+
- **Only a run whose verdict CONCLUDED may support such a statement.** The section marks each one. A
|
|
133
|
+
clause resting on an `INSUFFICIENT_EVIDENCE` run asserts a measurement that did not settle the
|
|
134
|
+
question, which is worse than saying nothing.
|
|
135
|
+
- **Say what it is.** The operator judged its own product with its own harness. A clause may say that
|
|
136
|
+
and what it found; it may not say the result was verified, certified, audited or independently
|
|
137
|
+
assured, and the claim guards refuse the sentence that blurs the two.
|
|
138
|
+
- **Where no run supports the statement, MARK it** — the same answer this lane gives every
|
|
139
|
+
unestablished statement, and the right one.
|
|
140
|
+
|
|
141
|
+
A ref that resolves to no committed run is refused before the draft becomes a file, as is any citation
|
|
142
|
+
at all in a PUBLIC document. Neither is your judgement to make here: cite only what the section lists.
|
|
143
|
+
|
|
144
|
+
## You do not approve, release or publish
|
|
145
|
+
|
|
146
|
+
You draft the candidate. A human accepts it by committing it; nothing else is acceptance, and landing is
|
|
147
|
+
not approval. You do not author the release — almost everything a release carries is derived from the
|
|
148
|
+
accepted document definition, and a release nobody has approved is composed and marked `UNAPPROVED`
|
|
149
|
+
rather than withheld.
|
|
150
|
+
|
|
151
|
+
**Which is why a missing approval never changes what you do here.** Waiting for one before drafting, and
|
|
152
|
+
describing a draft as approved to get past a gate, are the two symmetric failures; the first is a
|
|
153
|
+
compliance workflow standing in front of the mechanism that builds the application.
|
|
154
|
+
|
|
155
|
+
## Where the draft goes
|
|
156
|
+
|
|
157
|
+
It lands as a FILE in the application's specifications package, as an ordinary working edit, beside any
|
|
158
|
+
public candidates the application already holds.
|
|
159
|
+
|
|
160
|
+
---
|
|
161
|
+
|
|
162
|
+
# The compositions
|
|
163
|
+
|
|
164
|
+
Each entry below is one concern: what it asserts, what in the application it derives from, what state it
|
|
165
|
+
usually reaches, and what closes it when it cannot. Use the ones your document's row names and ignore the
|
|
166
|
+
rest.
|
|
167
|
+
|
|
168
|
+
### Concern: service scope
|
|
169
|
+
|
|
170
|
+
**Asserts** — what the service actually is: the modules it runs, the resources it manages, and the
|
|
171
|
+
surfaces it exposes.
|
|
172
|
+
|
|
173
|
+
**Derives from** — the application's declared modules and their resources, and the surfaces it builds
|
|
174
|
+
(application, API, public website, technical documentation).
|
|
175
|
+
|
|
176
|
+
**Completeness** — `DERIVED`.
|
|
177
|
+
|
|
178
|
+
**Derive it; do not describe the product from its marketing.** Scope in a governed document is the
|
|
179
|
+
boundary of what the statements around it apply to, so an aspirational description silently widens
|
|
180
|
+
every other clause. The declared modules are the honest boundary, and a capability the application
|
|
181
|
+
does not run does not belong here even if it is on the roadmap.
|
|
182
|
+
|
|
183
|
+
|
|
184
|
+
### Concern: security controls
|
|
185
|
+
|
|
186
|
+
**Asserts** — the security measures the application actually runs, at the level of detail a notice
|
|
187
|
+
needs and no further.
|
|
188
|
+
|
|
189
|
+
**Derives from** — the application's authored authentication configuration (methods enabled, MFA,
|
|
190
|
+
password policy, lockout, step-up, session lifetimes), its access floors, its encryption of stored
|
|
191
|
+
secrets, and its antivirus posture where the `ANTIVIRUS_SCANNING` INFRA capability is provisioned
|
|
192
|
+
(ClamAV, consumed by the engine's file-scanning service on upload). Note this reads the INFRA
|
|
193
|
+
capability, not an engine provider slot: the equally-named `EngineCapability.ANTIVIRUS_SCANNING` was
|
|
194
|
+
withdrawn because no provider could fill it, and a derived control statement must never rest on a
|
|
195
|
+
slot that cannot be configured.
|
|
196
|
+
|
|
197
|
+
**Completeness** — `DERIVED`, bounded.
|
|
198
|
+
|
|
199
|
+
**Bounded is the operative word.** A public notice states that measures exist and their general
|
|
200
|
+
nature. **It must not enumerate the control set**: a published list of exactly which protections are
|
|
201
|
+
in place, and by implication which are not, is a map for somebody attacking the service. Detail
|
|
202
|
+
belongs in a security addendum shared under agreement, not on a public page — so this fragment reads
|
|
203
|
+
very differently in `public.privacy-notice` than in a security schedule, and that difference is
|
|
204
|
+
deliberate rather than an omission.
|
|
205
|
+
|
|
206
|
+
**Never state a certification.** "Compliant", "certified", "audited" and "ISO/SOC" claims are not
|
|
207
|
+
derivable from configuration and are not this document's to make.
|
|
208
|
+
|
|
209
|
+
|
|
210
|
+
### Concern: audit and accountability
|
|
211
|
+
|
|
212
|
+
**Asserts** — that security-relevant actions are recorded, what kinds are recorded, and where those
|
|
213
|
+
records can be sent.
|
|
214
|
+
|
|
215
|
+
**Derives from** — the application's own audit store, which every application writes; the
|
|
216
|
+
`COMPLIANCE_AUDIT_TRAIL` engine capability, which additionally sends each event to external providers
|
|
217
|
+
(`saas-models` → `external-providers/engine-capabilities.shared.schemas.ts`); the auditable-event
|
|
218
|
+
catalog the engine emits (authentication, authorization grants, consent decisions, token lifecycle,
|
|
219
|
+
configuration and permission changes, cross-tenant administrative access), and per-organization SIEM
|
|
220
|
+
routing where a tenant has configured it.
|
|
221
|
+
|
|
222
|
+
**Completeness** — `DERIVED`.
|
|
223
|
+
|
|
224
|
+
This is one of the fragments where the ENGINE answers for the application. Every generated
|
|
225
|
+
application inherits the event catalog and the emitters; a document may state it without the
|
|
226
|
+
application having configured anything. Where a tenant has additionally routed events to its own
|
|
227
|
+
SIEM, that is the tenant's configuration and belongs in a shared-responsibility statement rather than
|
|
228
|
+
in the operator's own notice.
|
|
229
|
+
|
|
230
|
+
|
|
231
|
+
### Concern: access control and roles
|
|
232
|
+
|
|
233
|
+
**Asserts** — who inside the operator and inside a customer tenant can reach personal data, and what
|
|
234
|
+
constrains them.
|
|
235
|
+
|
|
236
|
+
**Derives from** — `CORE_APP_ROLES` and `CORE_ORG_ROLES`
|
|
237
|
+
(`saas-models` → `security/authorizations/roles.shared.schemas.ts`) plus the application's own role
|
|
238
|
+
table; the administrative-continuity floors (a tenant cannot be left with no usable owner, the
|
|
239
|
+
application cannot be left with no super-administrator); and the platform-access-grant mechanism,
|
|
240
|
+
under which a platform operator crossing the per-record tenant boundary requires a granted,
|
|
241
|
+
time-bounded authorization. Application-wide directory reads retain independent approval. The
|
|
242
|
+
application audit viewer has a distinct policy: `auditTrail.applicationReadAccess` defaults to
|
|
243
|
+
`AuditApplicationReadAccess.ROLE_BASED` in every environment, admitting the super-administrator or the
|
|
244
|
+
read-only audit-evidence reader role; `INDEPENDENT_APPROVAL` requires a usable application-wide grant in
|
|
245
|
+
addition to the role, and a machine reader (such as an assurance collector) holds one only when it is bound to
|
|
246
|
+
its own credential and signed by a second administrator — a grant bound to a machine never admits the
|
|
247
|
+
administrator who requested it. Access admission, audit observation and retained
|
|
248
|
+
evidence are separate claims: the access decision does not depend on a successful audit write.
|
|
249
|
+
|
|
250
|
+
**Completeness** — `DERIVED`.
|
|
251
|
+
|
|
252
|
+
Worth stating plainly in a B2B notice, because it is the question a customer's own reviewer asks
|
|
253
|
+
first: **operator access is governed by the resource and its declared policy.** Ordinary tenant
|
|
254
|
+
crossings require a usable grant. The application audit viewer is role-based by default, with
|
|
255
|
+
independent approval available as an explicit policy. Its cross-tenant observations still identify
|
|
256
|
+
the operator and tenants reached; role-based access does not imply anonymized logs or fabricate an
|
|
257
|
+
approval record. Actual application-wide grants always retain their independent-approval requirement.
|
|
258
|
+
|
|
259
|
+
**Observation coverage** — the per-record organization gate observes access to an identifiable
|
|
260
|
+
tenant's record when the caller does not already hold organization-wide entry there. Separately,
|
|
261
|
+
declared cross-tenant READ, LIST and SEARCH operations outside the organization-scoped gate observe
|
|
262
|
+
the identifiable tenants in their returned records that the caller does not already belong to,
|
|
263
|
+
grouped into one observation per tenant reached. This collection observer excludes context-free
|
|
264
|
+
internal requests and webhook callbacks; COUNT
|
|
265
|
+
returns no records and is not covered by that observer. Do not turn these scoped mechanisms into a
|
|
266
|
+
claim that every operation or every returned record produces an audit entry.
|
|
267
|
+
|
|
268
|
+
**Delivery and evidence** — these observations are best-effort and do not fail the observed request.
|
|
269
|
+
An unavailable audit service, a synchronous emission error or a rejected emission can leave an
|
|
270
|
+
authorized request without a retained crossing entry. Observer-side drops have an
|
|
271
|
+
`audit_observation_dropped_total` signal and throttled error logs; failures at the primary audit-store
|
|
272
|
+
write have the separate `audit_store_failure_total` signal. Metrics export and log retention must
|
|
273
|
+
actually be configured and operating for those signals to provide evidence beyond the process.
|
|
274
|
+
Neither a loss counter nor an attempted emission substitutes for the missing audit entry.
|
|
275
|
+
|
|
276
|
+
**Document-authoring consequence** — derive the roles, operation declarations and usable-grant
|
|
277
|
+
requirements and the audit viewer's access policy from the application's configuration. Do not
|
|
278
|
+
claim that every audit read required independent approval when the viewer is role-based. Describe the observation mechanisms as supported
|
|
279
|
+
coverage, then substantiate any statement about recorded access with retained audit records and
|
|
280
|
+
evidence that the collection pipeline and loss monitoring were operating over the period claimed.
|
|
281
|
+
An empty crossing search alone does not prove that no operator accessed tenant data. `DERIVED`
|
|
282
|
+
above identifies the source of the access-control description; it does not certify complete audit
|
|
283
|
+
delivery or the application's operational compliance.
|
|
284
|
+
|
|
285
|
+
|
|
286
|
+
### Concern: tenancy model
|
|
287
|
+
|
|
288
|
+
**Asserts** — that customer data is separated per organization, and where the boundary between the
|
|
289
|
+
operator's responsibilities and the customer's lies.
|
|
290
|
+
|
|
291
|
+
**Derives from** — the `ORGANIZATIONS` engine capability, the organization scoping applied to every
|
|
292
|
+
tenant-scoped resource, and the cross-tenant admission rules. Ordinary tenant crossings must be
|
|
293
|
+
declared and carry a usable access grant. The application audit viewer is a separate policy surface:
|
|
294
|
+
it defaults to role-based access (the super-administrator or the read-only audit-evidence reader), with
|
|
295
|
+
`auditTrail.applicationReadAccess` optionally set to `AuditApplicationReadAccess.INDEPENDENT_APPROVAL`, under
|
|
296
|
+
which a machine reader needs a second-signed grant bound to its own credential. Both modes retain cross-tenant read observations;
|
|
297
|
+
role-based access neither implies anonymized records nor supplies an approval that never occurred.
|
|
298
|
+
|
|
299
|
+
**Completeness** — `DERIVED`.
|
|
300
|
+
|
|
301
|
+
**This fragment is where shared responsibility is described, and it must never be flattened.** In a
|
|
302
|
+
B2B SaaS the operator is a PROCESSOR for the data a customer stores about its own people, and a
|
|
303
|
+
CONTROLLER for the data it holds about the customer's users as account holders. Those are different
|
|
304
|
+
roles with different duties over the same database. Say which is which; do not pick one and apply it
|
|
305
|
+
to everything.
|
|
306
|
+
|
|
307
|
+
**The attribution has a home now.** `operatorComplianceIdentity.roleAllocations` in
|
|
308
|
+
`wildo.saas.config.ts` carries one role per population of data — PROCESSOR for the records a customer
|
|
309
|
+
stores about its own people, CONTROLLER for the account data of the people who administer them. It is
|
|
310
|
+
a LIST for exactly the reason this fragment gives: those are different roles over the same database,
|
|
311
|
+
and a single field would force one of them to be wrong.
|
|
312
|
+
|
|
313
|
+
Where the attribution is not established, that is a `NEEDS_DECISION` — never a guess — and the
|
|
314
|
+
surface to name is `roleAllocations`. Not `NEEDS_FRAMEWORK`: there is somewhere to write the answer,
|
|
315
|
+
so the remedy is to fill it in rather than to build something. See the legal-basis fragment.
|
|
316
|
+
|
|
317
|
+
|
|
318
|
+
### Concern: operator identity
|
|
319
|
+
|
|
320
|
+
**Asserts** — who legally operates the service: entity name, registered address, contact route for
|
|
321
|
+
data-protection questions, and a representative where one is required.
|
|
322
|
+
|
|
323
|
+
**Derives from** — `operatorComplianceIdentity` in `wildo.saas.config.ts`: the legal entity, its
|
|
324
|
+
registered address, the privacy contact route, and an Art. 27 representative where one is required.
|
|
325
|
+
|
|
326
|
+
The VALUE is never derivable — a legal entity is a fact about the world, not a property of a codebase.
|
|
327
|
+
What the framework provides is the PLACE to record it, and until 2026-08-30 it did not: this fragment
|
|
328
|
+
said "no engine change would close it", which was right about derivation and wrong about the home.
|
|
329
|
+
The consequence was concrete. A landing REPLACES the produced document on every run, so an operator
|
|
330
|
+
who answered by editing the document lost the answer at the next regeneration — the answer has to live
|
|
331
|
+
in the application or it does not survive.
|
|
332
|
+
|
|
333
|
+
**Completeness** — `DERIVED` when the identity is declared; `NEEDS_DECISION` when it is not.
|
|
334
|
+
|
|
335
|
+
⚠️ `NEEDS_DECISION`, not `NEEDS_FRAMEWORK`, and the distinction is load-bearing now that the surface
|
|
336
|
+
exists. `NEEDS_FRAMEWORK` means there is nowhere to record the answer; `NEEDS_DECISION` means there is
|
|
337
|
+
and nobody has. They have different remedies — build something, versus fill something in — and a
|
|
338
|
+
reader who cannot tell them apart cannot act on either. Say which surface the answer goes to.
|
|
339
|
+
|
|
340
|
+
**What closes it** — the operator declaring `operatorComplianceIdentity`. It is cheap and it can be
|
|
341
|
+
filled in later without redrafting anything around it, which is the reason it is not a blocker.
|
|
342
|
+
|
|
343
|
+
**Never infer it.** Not from the application name, not from a domain, not from another application,
|
|
344
|
+
not from model memory. A published legal document naming the wrong entity is worse than one that says
|
|
345
|
+
the entity is not yet recorded — the first misdirects a person exercising a right, the second tells
|
|
346
|
+
them the document is incomplete.
|
|
347
|
+
|
|
348
|
+
**Every document needs this fragment**, which makes it the clearest demonstration of why producing
|
|
349
|
+
with gaps beats blocking: the whole document set would be unproducible until one form is filled in.
|