@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
|
@@ -0,0 +1,61 @@
|
|
|
1
|
+
# Compliance Evidence Adequacy — is this enough to state a posture from?
|
|
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
|
+
You are the **gate**, not the author. You read what the research rounds gathered
|
|
16
|
+
and answer one question: is this enough to record the product's compliance posture
|
|
17
|
+
— or what, precisely, is still missing?
|
|
18
|
+
|
|
19
|
+
## What ADEQUATE means here
|
|
20
|
+
|
|
21
|
+
Evidence is adequate when, for the jurisdictions, data classes and sector the
|
|
22
|
+
vision (and the creator's answers) put in scope:
|
|
23
|
+
|
|
24
|
+
1. **Every plausible candidate regime has a settled applicability answer** —
|
|
25
|
+
applies, does not apply, or genuinely cannot be established — grounded in an
|
|
26
|
+
authoritative source, never in recollection.
|
|
27
|
+
2. **No scope dimension is unexamined.** A jurisdiction the vision names with no
|
|
28
|
+
regime evidence at all is a gap, whatever was gathered elsewhere.
|
|
29
|
+
3. **The claims carry sources.** An unsourced applicability claim counts as
|
|
30
|
+
missing, not as weak — the posture that cites it would be recollection wearing
|
|
31
|
+
evidence's clothes.
|
|
32
|
+
|
|
33
|
+
## A regime whose triggering facts are DECLARED OPEN is settled as CONDITIONAL
|
|
34
|
+
|
|
35
|
+
"Settled" has three answers, and the third is not a failure: **applies**, **does
|
|
36
|
+
not apply**, and **conditional on named open facts**. When the creator's own
|
|
37
|
+
answers declare a triggering fact undecided — a hosting region not chosen, a
|
|
38
|
+
market not yet targeted, a threshold nobody can know before launch — the settled
|
|
39
|
+
answer for every regime that turns on that fact is *conditional on it*, stated
|
|
40
|
+
with the exact facts that would decide it. That answer is ADEQUATE as it stands.
|
|
41
|
+
|
|
42
|
+
Do not send research after statute-level verification of conditional regimes.
|
|
43
|
+
The measured failure this paragraph exists for: a run whose creator had declared
|
|
44
|
+
US targeting undecided spent its final rounds demanding primary-source triggers
|
|
45
|
+
and thresholds for twelve individual US state statutes — evidence that decides
|
|
46
|
+
nothing until the open fact is decided, purchased at the cost of the rounds the
|
|
47
|
+
DECIDED scope needed. Reserve the authoritative-source bar for the regimes the
|
|
48
|
+
declared facts actually reach; for the conditional tier, the deliverable is the
|
|
49
|
+
precise list of deciding facts, and the posture records exactly that.
|
|
50
|
+
|
|
51
|
+
## What INSUFFICIENT must do
|
|
52
|
+
|
|
53
|
+
Name the gaps so the next round is AIMED: which regime, which trigger question,
|
|
54
|
+
which jurisdiction. "More research needed" is not a gap — it is the shape that
|
|
55
|
+
made the market loop's early rounds spend tokens converging on nothing.
|
|
56
|
+
|
|
57
|
+
## What you never do
|
|
58
|
+
|
|
59
|
+
You never lower the bar because rounds are running out — the composite's breaker
|
|
60
|
+
owns that trade, not you. And you never fill a gap yourself: a gate that authors
|
|
61
|
+
evidence has measured nothing.
|
|
@@ -0,0 +1,40 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ref": "top_down.compliance-evidence-adequacy",
|
|
3
|
+
"version": "0.1.1",
|
|
4
|
+
"phase": "top_down",
|
|
5
|
+
"intent": "Judge whether the regime evidence gathered so far is ENOUGH to state a compliance posture from, and when it is not, name precisely what is missing so the next research round is aimed rather than repeated. Returns a verdict a sibling's precondition READS; it authors nothing and lands nothing.",
|
|
6
|
+
"preconditions": [
|
|
7
|
+
{
|
|
8
|
+
"kind": "step_available",
|
|
9
|
+
"ref": "compliance-evidence"
|
|
10
|
+
}
|
|
11
|
+
],
|
|
12
|
+
"inputs": [
|
|
13
|
+
{
|
|
14
|
+
"family": "vision-brief"
|
|
15
|
+
}
|
|
16
|
+
],
|
|
17
|
+
"outputs": [],
|
|
18
|
+
"stepOutputs": [
|
|
19
|
+
{
|
|
20
|
+
"ref": "compliance-adequacy",
|
|
21
|
+
"schemaRef": "saas-models:MetaWorkflow_EvidenceAdequacy",
|
|
22
|
+
"condensation": "A verdict, the gaps that produced it, and a rationale grounded in what was actually gathered.",
|
|
23
|
+
"description": "The adequacy gate the posture step is conditioned on."
|
|
24
|
+
}
|
|
25
|
+
],
|
|
26
|
+
"method": {
|
|
27
|
+
"guidance": "# Compliance Evidence Adequacy — is this enough to state a posture from?\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nYou are the **gate**, not the author. You read what the research rounds gathered\nand answer one question: is this enough to record the product's compliance posture\n— or what, precisely, is still missing?\n\n## What ADEQUATE means here\n\nEvidence is adequate when, for the jurisdictions, data classes and sector the\nvision (and the creator's answers) put in scope:\n\n1. **Every plausible candidate regime has a settled applicability answer** —\n applies, does not apply, or genuinely cannot be established — grounded in an\n authoritative source, never in recollection.\n2. **No scope dimension is unexamined.** A jurisdiction the vision names with no\n regime evidence at all is a gap, whatever was gathered elsewhere.\n3. **The claims carry sources.** An unsourced applicability claim counts as\n missing, not as weak — the posture that cites it would be recollection wearing\n evidence's clothes.\n\n## A regime whose triggering facts are DECLARED OPEN is settled as CONDITIONAL\n\n\"Settled\" has three answers, and the third is not a failure: **applies**, **does\nnot apply**, and **conditional on named open facts**. When the creator's own\nanswers declare a triggering fact undecided — a hosting region not chosen, a\nmarket not yet targeted, a threshold nobody can know before launch — the settled\nanswer for every regime that turns on that fact is *conditional on it*, stated\nwith the exact facts that would decide it. That answer is ADEQUATE as it stands.\n\nDo not send research after statute-level verification of conditional regimes.\nThe measured failure this paragraph exists for: a run whose creator had declared\nUS targeting undecided spent its final rounds demanding primary-source triggers\nand thresholds for twelve individual US state statutes — evidence that decides\nnothing until the open fact is decided, purchased at the cost of the rounds the\nDECIDED scope needed. Reserve the authoritative-source bar for the regimes the\ndeclared facts actually reach; for the conditional tier, the deliverable is the\nprecise list of deciding facts, and the posture records exactly that.\n\n## What INSUFFICIENT must do\n\nName the gaps so the next round is AIMED: which regime, which trigger question,\nwhich jurisdiction. \"More research needed\" is not a gap — it is the shape that\nmade the market loop's early rounds spend tokens converging on nothing.\n\n## What you never do\n\nYou never lower the bar because rounds are running out — the composite's breaker\nowns that trade, not you. And you never fill a gap yourself: a gate that authors\nevidence has measured nothing.\n",
|
|
28
|
+
"skillRefs": [],
|
|
29
|
+
"skillBodyRefs": [],
|
|
30
|
+
"contextSources": [],
|
|
31
|
+
"draftableDocumentDefinitionRefs": [],
|
|
32
|
+
"suspendsForClarification": false,
|
|
33
|
+
"briefAdequacyGate": false,
|
|
34
|
+
"briefAdequacyExcludedSources": []
|
|
35
|
+
},
|
|
36
|
+
"executor": "companion_agent",
|
|
37
|
+
"approval": "auto",
|
|
38
|
+
"budget": {},
|
|
39
|
+
"onFailure": "keep_and_flag"
|
|
40
|
+
}
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"aggregationPolicyRef":"application-creation:aggregation/worst-compliance-posture-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["vision.constraint"],"criterionRef":"application-creation:criterion/compliance-posture-one-regime-one-constraint-and-convergence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-one-regime-one-constraint-and-convergence","requirementVersion":1}],"instruction":"Determine whether the posture is written as one constraint per regime with a stable kebab-case ref prefixed `constraint-`, unique across the set; whether a regime already present in the vision (under any slug the vision-elicitation step chose) was matched by the regime its statement names and updated IN PLACE under its existing ref; and whether re-running would converge to one entry per regime rather than accumulating near-duplicates.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Regimes are separate but a ref is minted for a regime that already existed under another slug, or two statements overlap in scope.","GAP":"An omnibus constraint merging several regimes, a duplicate entry for one regime, or a malformed ref.","INDETERMINATE":"The vision's prior constraints are not in evidence, so convergence cannot be compared.","PASS":"One entry per regime, stable unique refs, and every pre-existing regime refined under its own ref."}},{"criterionRef":"application-creation:criterion/compliance-posture-regime-derivation-grounding","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-regime-derivation-grounding","requirementVersion":1}],"instruction":"Determine whether each compliance constraint is derived rather than recalled: its statement names the regime, the trigger (jurisdiction, data class, sector or commitment) and what it governs, in the terms of the regime evidence and the creator's facts this run carried; a regime the evidence EXCLUDES is not written as a constraint and, where the creator's answers suggested it, the exclusion is made legible on a neighbouring constraint; a trigger the evidence could NOT establish becomes a constraint stating the open question, never a guessed answer; and a product with no triggers honestly carries no compliance constraints.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, but a statement is thinner than the evidence allows, or an exclusion is dropped silently where the creator had suggested the regime.","GAP":"A regime stated as settled that the evidence did not establish, a regime invented to look thorough, or a regime the evidence establishes that is absent.","INDETERMINATE":"The regime evidence or the creator's facts are not in evidence, so derivation cannot be checked.","PASS":"Every constraint is grounded in the evidence, exclusions are legible, and open triggers are stated as open."}},{"assessesAspects":["vision.constraint","vision.idea","vision.problem","vision.mission","vision.success-criterion"],"criterionRef":"application-creation:criterion/compliance-posture-slice-discipline","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-slice-discipline","requirementVersion":1}],"instruction":"Determine whether the run touched exactly the `kind: compliance` entries of the vision's constraints and nothing else: the idea, problem, mission, success criteria and every non-compliance constraint are unchanged, and no constraint models controls, obligation graphs, residency matrices, retention schedules or audit configuration, which belong to the later compliance-conception step.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A non-compliance entity was reworded incidentally, or a constraint drifts toward listing controls.","GAP":"A vision entity outside the compliance constraints altered, or a constraint that models controls or obligations.","INDETERMINATE":"The vision as it was BEFORE this run is not in evidence.","PASS":"Only compliance constraints changed, and each stays a prose regime statement at scaffold depth."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/compliance-posture","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.compliance-posture"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
|
|
@@ -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-vision-brief","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/compliance-posture-one-regime-one-constraint-and-convergence"],"requirementRef":"application-creation:authority-requirement/compliance-posture-result","requirementVersion":1,"riskClassRef":"application-creation:risk/vision-brief-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/compliance-posture","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/compliance-posture-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/compliance-posture","policyVersion":1},"decisionPointRef":"application-creation:decision-point/compliance-posture-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/compliance-posture-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/compliance-posture","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-one-regime-one-constraint-and-convergence","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/compliance-posture-regime-derivation-grounding","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/compliance-posture-slice-discipline","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/vision-brief-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-vision-brief-change","triggerRefs":["application-creation:trigger/vision-brief-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-compliance-posture-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/compliance-posture-regime-derivation-grounding"],"hardFloorRef":"application-creation:hard-floor/vision-brief-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/compliance-posture-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/compliance-posture","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-compliance-posture-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["vision.constraint"],"criterionRef":"application-creation:criterion/compliance-posture-one-regime-one-constraint-and-convergence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-one-regime-one-constraint-and-convergence","requirementVersion":1}],"instruction":"Determine whether the posture is written as one constraint per regime with a stable kebab-case ref prefixed `constraint-`, unique across the set; whether a regime already present in the vision (under any slug the vision-elicitation step chose) was matched by the regime its statement names and updated IN PLACE under its existing ref; and whether re-running would converge to one entry per regime rather than accumulating near-duplicates.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Regimes are separate but a ref is minted for a regime that already existed under another slug, or two statements overlap in scope.","GAP":"An omnibus constraint merging several regimes, a duplicate entry for one regime, or a malformed ref.","INDETERMINATE":"The vision's prior constraints are not in evidence, so convergence cannot be compared.","PASS":"One entry per regime, stable unique refs, and every pre-existing regime refined under its own ref."}},{"criterionRef":"application-creation:criterion/compliance-posture-regime-derivation-grounding","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-regime-derivation-grounding","requirementVersion":1}],"instruction":"Determine whether each compliance constraint is derived rather than recalled: its statement names the regime, the trigger (jurisdiction, data class, sector or commitment) and what it governs, in the terms of the regime evidence and the creator's facts this run carried; a regime the evidence EXCLUDES is not written as a constraint and, where the creator's answers suggested it, the exclusion is made legible on a neighbouring constraint; a trigger the evidence could NOT establish becomes a constraint stating the open question, never a guessed answer; and a product with no triggers honestly carries no compliance constraints.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, but a statement is thinner than the evidence allows, or an exclusion is dropped silently where the creator had suggested the regime.","GAP":"A regime stated as settled that the evidence did not establish, a regime invented to look thorough, or a regime the evidence establishes that is absent.","INDETERMINATE":"The regime evidence or the creator's facts are not in evidence, so derivation cannot be checked.","PASS":"Every constraint is grounded in the evidence, exclusions are legible, and open triggers are stated as open."}},{"assessesAspects":["vision.constraint","vision.idea","vision.problem","vision.mission","vision.success-criterion"],"criterionRef":"application-creation:criterion/compliance-posture-slice-discipline","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-slice-discipline","requirementVersion":1}],"instruction":"Determine whether the run touched exactly the `kind: compliance` entries of the vision's constraints and nothing else: the idea, problem, mission, success criteria and every non-compliance constraint are unchanged, and no constraint models controls, obligation graphs, residency matrices, retention schedules or audit configuration, which belong to the later compliance-conception step.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A non-compliance entity was reworded incidentally, or a constraint drifts toward listing controls.","GAP":"A vision entity outside the compliance constraints altered, or a constraint that models controls or obligations.","INDETERMINATE":"The vision as it was BEFORE this run is not in evidence.","PASS":"Only compliance constraints changed, and each stays a prose regime statement at scaffold depth."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/compliance-posture","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.compliance-posture"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/compliance-posture","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-compliance-posture-inputs-and-candidate","criterionRef":"application-creation:criterion/compliance-posture-one-regime-one-constraint-and-convergence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-posture-one-regime-one-constraint-and-convergence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-and-regime-evidence-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-compliance-posture-inputs-and-candidate","criterionRef":"application-creation:criterion/compliance-posture-regime-derivation-grounding","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-posture-regime-derivation-grounding","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-and-regime-evidence-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-compliance-posture-inputs-and-candidate","criterionRef":"application-creation:criterion/compliance-posture-slice-discipline","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-posture-slice-discipline","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-and-regime-evidence-candidate"}],"schemaVersion":1}
|
|
@@ -69,19 +69,21 @@ requirements and explicit gaps.
|
|
|
69
69
|
The transition is not an automatic conversion and must not reinterpret a
|
|
70
70
|
vision sentence as a control mapping or positive compliance claim. Preserve
|
|
71
71
|
the vision constraint as product intent, record any missing detail as
|
|
72
|
-
`UNDETERMINED` or an explicit gap, and
|
|
73
|
-
|
|
72
|
+
`UNDETERMINED` or an explicit gap, and land the structured family as files in the
|
|
73
|
+
specifications package. Landing is not accepting: the run leaves working edits,
|
|
74
|
+
and acceptance is a later commit. Who makes it is the host's autonomy posture, and only a
|
|
75
|
+
person's commit reviews what it accepts. Runtime organizations, assignees, evidence,
|
|
74
76
|
control occurrences and assessments remain outside both artifacts.
|
|
75
77
|
|
|
76
78
|
## The derivation posture
|
|
77
79
|
|
|
78
|
-
- **Derive
|
|
79
|
-
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
|
|
80
|
+
- **Derive from the product and gathered evidence.** Read the existing vision,
|
|
81
|
+
product facts and cumulative regime evidence supplied by the parent choreography.
|
|
82
|
+
The current `compliance-adequacy` verdict establishes readiness. This playbook
|
|
83
|
+
declares no interview: do not fabricate answers or submit arbitrary
|
|
84
|
+
`elicitationAnswers`. Preserve source-backed applicability reasoning and explicit
|
|
85
|
+
uncertainty. Creator-owned facts that remain unresolved need a supported input or
|
|
86
|
+
clarification path; do not ask the creator to reconstruct externally researchable obligations.
|
|
85
87
|
- **Regime derivation rubric (v1).** Use these as the starting triggers, and
|
|
86
88
|
follow up where an answer is thin:
|
|
87
89
|
- **GDPR / UK GDPR** — serving EU/EEA (or UK) individuals, or processing
|
|
@@ -151,6 +153,11 @@ unique refs the first time. Note that a vision with no compliance constraints
|
|
|
151
153
|
is perfectly valid — an honestly unregulated product should pass the gate with
|
|
152
154
|
none.
|
|
153
155
|
|
|
156
|
+
Beyond the deterministic gate, the advisory judge reads the refined vision against
|
|
157
|
+
three criteria — regime derivation grounded in the evidence, one regime per constraint
|
|
158
|
+
converging on re-run, and slice discipline — and its verdicts reach the creator's
|
|
159
|
+
review as notes. A verdict never refuses a landing.
|
|
160
|
+
|
|
154
161
|
## Approval
|
|
155
162
|
|
|
156
163
|
The refined `VisionSnapshot` is presented to the creator for approval before it
|
|
@@ -167,11 +174,27 @@ Before you start, read the current journey state and scope, and read the
|
|
|
167
174
|
existing vision so you refine its compliance constraints rather than writing a
|
|
168
175
|
fresh, disconnected set.
|
|
169
176
|
|
|
170
|
-
|
|
171
|
-
|
|
177
|
+
(The existing vision and its current constraints are already in your brief as the `vision-brief`
|
|
178
|
+
input section.)
|
|
179
|
+
|
|
180
|
+
## The evidence, and how to use it
|
|
181
|
+
|
|
182
|
+
Your run carries what sibling steps gathered — source-attributed regime evidence and the adequacy
|
|
183
|
+
verdict that admitted this step. Derive each constraint from the creator's answers AND that
|
|
184
|
+
evidence, never from recollection:
|
|
185
|
+
|
|
186
|
+
- A regime the evidence establishes as APPLICABLE becomes a `compliance` constraint whose statement
|
|
187
|
+
names the regime, the trigger (jurisdiction / data class / sector / commitment), and what it
|
|
188
|
+
governs — in the evidence's terms.
|
|
189
|
+
- A regime the evidence EXCLUDES is not written as a constraint, and is not silently dropped either:
|
|
190
|
+
where the creator's answers suggested it, the statement of a neighbouring constraint may note the
|
|
191
|
+
exclusion so the decision is legible.
|
|
192
|
+
- A trigger the evidence could NOT establish becomes a constraint stating the OPEN QUESTION, never a
|
|
193
|
+
guessed answer — an unestablished regime stated as settled is the defect this composite exists to
|
|
194
|
+
end.
|
|
172
195
|
|
|
173
196
|
## References
|
|
174
197
|
|
|
175
|
-
|
|
176
|
-
|
|
177
|
-
|
|
198
|
+
These are skill FOLDERS installed in the application, named so each piece of work has an
|
|
199
|
+
authoring contract a later coding agent can open. This step has no tools and does not open them;
|
|
200
|
+
what reaches you is this method, your declared inputs, and the brief's own sections.
|
|
@@ -1,19 +1,22 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.compliance-posture",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.2.2",
|
|
4
4
|
"phase": "top_down",
|
|
5
|
-
"intent": "
|
|
6
|
-
"functionalTopics": [],
|
|
5
|
+
"intent": "Derive compliance constraints for the existing product vision from its jurisdictions, data classes, sector, customer commitments and gathered regime evidence. This is the artifact-producing child of top_down.compliance-analysis: it runs when the current compliance-adequacy assessment is adequate, and sharpens the vision-brief rather than re-eliciting it. Record source-backed applicability and unresolved product facts as compliance constraints; runtime controls, evidence assignments and organization assessments belong to their own mechanisms.",
|
|
7
6
|
"preconditions": [
|
|
8
|
-
{
|
|
9
|
-
"kind": "phase_is",
|
|
10
|
-
"phase": "top_down"
|
|
11
|
-
},
|
|
12
7
|
{
|
|
13
8
|
"kind": "artifact_exists",
|
|
14
9
|
"selector": {
|
|
15
10
|
"family": "vision-brief"
|
|
16
11
|
}
|
|
12
|
+
},
|
|
13
|
+
{
|
|
14
|
+
"kind": "step_available",
|
|
15
|
+
"ref": "compliance-adequacy",
|
|
16
|
+
"requires": {
|
|
17
|
+
"path": "verdict",
|
|
18
|
+
"equals": "adequate"
|
|
19
|
+
}
|
|
17
20
|
}
|
|
18
21
|
],
|
|
19
22
|
"inputs": [
|
|
@@ -25,74 +28,21 @@
|
|
|
25
28
|
{
|
|
26
29
|
"family": "vision-brief",
|
|
27
30
|
"schemaRef": "saas-specifications:VisionSnapshot",
|
|
28
|
-
"placement": ".wildo-saas/journey/<journeyId>/vision-brief/",
|
|
29
31
|
"description": "The same VisionSnapshot the vision-elicitation step seeded, refined in place: this playbook adds/updates the `constraints[]` entries whose `kind` is `compliance`, each a prose `statement` naming an applicable regime and the data / jurisdiction it governs. Other vision entities (idea, problem, mission, success criteria, non-compliance constraints) are left untouched. Validated by validateVisionSnapshot."
|
|
30
32
|
}
|
|
31
33
|
],
|
|
34
|
+
"stepOutputs": [],
|
|
32
35
|
"method": {
|
|
33
|
-
"guidance": "# Compliance Posture — Derivation Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** The regime-derivation rubric below\n> (which triggers imply which regime, how much to capture) is a deliberately\n> explicit first cut meant to be tuned against real runs. Treat it as a\n> starting rubric, not a frozen contract. Crucially, it derives compliance\n> **posture at scaffold depth** — prose constraints, not a per-regime\n> obligation model.\n\n## What this playbook does\n\nYou determine the product's **compliance posture** — which regulatory regimes\nit must be built to satisfy — and record each as a `compliance`-kind constraint\non the existing vision. The vision-elicitation step already named the\ncompliance _seam_ in passing (a single \"we handle EU personal data\" line). Your\njob is the focused, deliberate pass over that seam: reason from the product's\njurisdictions, the classes of data it handles, and its sector to the concrete\nset of regimes, and write each one down as its own constraint with a clear\nprose statement.\n\nYou do **not** re-elicit the whole vision, design the domain, or draft\nrequirements. You touch exactly one slice of the `VisionSnapshot`: its\n`constraints[]` entries of `kind: compliance`. Everything else on the snapshot\n— the idea, the problem, the mission, the success criteria, the\nnon-compliance constraints — you leave exactly as you found it.\n\n## The scaffold-depth boundary (read this before you start)\n\nAt this stage compliance is captured as **prose constraints only**. Each\napplicable regime becomes one constraint entry whose `statement` names the\nregime and the data / jurisdiction it governs — e.g. _\"Must be GDPR-compliant\nfor EU/EEA customer personal data.\"_ That is the whole deliverable.\n\nDo **not** build, and do not try to author into the snapshot:\n\n- per-regime control catalogs or obligation graphs (legal-article mappings,\n sector safeguards, external-assurance criteria),\n- data-flow / residency matrices,\n- retention schedules, DPA registries, or audit-config derivations.\n\nThat deep per-regime obligation model is a deliberately deferred later concern.\nIf you catch yourself modelling controls or obligations, **stop** — you have\nleft scaffold depth. Naming the regime seam accurately here is exactly what\nlets that later, deeper step engage. Getting the _set of applicable regimes_\nright, in prose, is the win.\n\n### Transition to structured compliance conception\n\nThis playbook does not write the dedicated `compliance-program` family. Its\naccepted vision constraints are precursor facts for a later, separately\napproved compliance-conception step. That step may initialize or revise the\noptional structured family only after it resolves exact source versions and\nrights records, declarative application scope, applicability authority, Wildo\nobjective bindings, implementation choices, responsibilities, documentation\nrequirements and explicit gaps.\n\nThe transition is not an automatic conversion and must not reinterpret a\nvision sentence as a control mapping or positive compliance claim. Preserve\nthe vision constraint as product intent, record any missing detail as\n`UNDETERMINED` or an explicit gap, and accept the structured family through the\nnormal semantic-delta authority. Runtime organizations, assignees, evidence,\ncontrol occurrences and assessments remain outside both artifacts.\n\n## The derivation posture\n\n- **Derive, then confirm — do not just transcribe.** The typed questions on\n this playbook (`method.elicitation`) gather the raw triggers: jurisdictions,\n data classes, sector, and direct yes/no reads on the common regimes. Your\n value is reasoning from those triggers to the regime set, then reflecting\n each derived regime back to the creator for confirmation. If EU users +\n personal data are present, GDPR applies whether or not the creator named it;\n surface that, don't wait to be told.\n- **Regime derivation rubric (v1).** Use these as the starting triggers, and\n follow up where an answer is thin:\n - **GDPR / UK GDPR** — serving EU/EEA (or UK) individuals, or processing\n their personal data. Triggered by jurisdiction (EU/EEA/UK) + any personal\n data.\n - **HIPAA** — handling US protected health information as, or on behalf of, a\n covered entity or business associate. Triggered by health data + US\n healthcare context.\n - **External assurance commitments** — enterprise customers or the product's own security posture\n require an independent attestation or certification over security / availability /\n confidentiality. Often contractual rather than statutory — capture the requested target as\n externally supplied source metadata when the go-to-market depends on it.\n - **Data residency / sovereignty** — a requirement that certain data stay\n within a region or country. Triggered by residency answers or sector rules;\n record as its own compliance constraint even when it rides alongside GDPR.\n - **Sector & additional regimes** — payment-card, consumer-privacy, children's-data,\n government-security, contractual-assurance and sector-code obligations. Add each that\n the triggers imply; preserve the exact named source only in the later source registry.\n - When the triggers are genuinely absent (no personal data, no regulated\n sector), the honest posture is _no compliance constraints_ — say so and add\n none. Do not invent a regime to look thorough.\n- **One regime, one constraint.** Keep regimes as separate constraint entries\n rather than one omnibus \"must be compliant\" line — the set is read\n downstream, and a merged statement loses which regimes are actually in play.\n\n## What you emit\n\nYou refine the **existing** `VisionSnapshot` in place. Concretely, you\nadd or update entries in `constraints[]`:\n\n- Each applicable regime is one entry with `kind: compliance`.\n- Each entry has a stable kebab-case `ref` prefixed `constraint-`\n (e.g. `constraint-gdpr-eu-personal-data`,\n `constraint-hipaa-us-phi`, `constraint-external-assurance-security`,\n `constraint-data-residency-eu`), unique across the whole `constraints[]` set.\n- Each entry's `statement` is a prose sentence naming the regime and the data /\n jurisdiction it governs. Where the creator gave the source of the limit\n (a customer contract, a specific law), capture it as the constraint's\n rationale.\n\nLeave every non-`compliance` constraint, and every other vision entity,\nuntouched.\n\n**Idempotent — refine, do not duplicate.** Read the vision first. If compliance\nconstraints already exist (the vision-elicitation step, or a prior run of this\nplaybook, may have written some), reconcile against them: update a statement\nthat is now sharper, add a regime that was missed, and remove one only if the\ncreator confirms it never applied. **Match existing constraints by the REGIME\ntheir `statement` names, not by their `ref` slug** — the vision-elicitation step\nwrites compliance prose without following this playbook's ref convention, so a\nGDPR line it left may sit under any slug (`constraint-gdpr`,\n`constraint-eu-data`, …). When you refine a regime that is already present,\n**reuse that entry's existing `ref`** so it updates in place rather than\nforking; only mint a fresh `constraint-<regime>-<scope>` slug for a regime that\nis genuinely new. Re-running this playbook on an already-posture'd vision must\nconverge to one entry per regime, never accumulate near-duplicate\n`constraint-gdpr-*` entries.\n\n## Quality gate\n\nYour refined snapshot is checked by the deterministic `vision-snapshot-valid`\ngate (`validateVisionSnapshot`) before it commits — the same gate the\nvision-elicitation step uses, because you write to the same family. Duplicate\nrefs and malformed refs (a constraint ref that is not kebab-case with the\n`constraint-` prefix) are hard **errors**; the gate rejects them. Emit clean,\nunique refs the first time. Note that a vision with no compliance constraints\nis perfectly valid — an honestly unregulated product should pass the gate with\nnone.\n\n## Approval\n\nThe refined `VisionSnapshot` is presented to the creator for approval before it\nbecomes the committed `vision-brief`. Show the derived compliance posture back\nin plain prose — the list of regimes, each with the data / jurisdiction it\ngoverns and why it applies — and let the creator confirm or correct it.\nCompliance drives real downstream engine capability, audit, and retention\nchoices, so it is worth one explicit human sign-off that the regime set is\nright.\n\n## Runtime context\n\nBefore you start, read the current journey state and scope, and read the\nexisting vision so you refine its compliance constraints rather than writing a\nfresh, disconnected set.\n\n// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)\n// TODO CLI COMMAND: wildo context vision-brief (read the existing vision + its current constraints)\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read current journey state and\n scope before deriving, and to see the `vision-brief` (and its existing\n compliance constraints) you refine.\n",
|
|
34
|
-
"skillRefs": [
|
|
35
|
-
|
|
36
|
-
],
|
|
37
|
-
"
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
"question": "Does the product store, process, or transmit personal data or otherwise regulated data (health, financial, biometric, children's, government) — either from end users or on behalf of customers?",
|
|
42
|
-
"kind": "confirm"
|
|
43
|
-
},
|
|
44
|
-
{
|
|
45
|
-
"ref": "data-classes",
|
|
46
|
-
"question": "Which classes of sensitive data does the product touch? List them (e.g. names/emails, health records, payment card data, government IDs, precise location, employee data). Answer \"none\" if it handles no personal or sensitive data.",
|
|
47
|
-
"kind": "free_text"
|
|
48
|
-
},
|
|
49
|
-
{
|
|
50
|
-
"ref": "jurisdictions",
|
|
51
|
-
"question": "In which jurisdictions do your users live and your data reside or transit (e.g. EU/EEA, UK, US, California, Canada, specific countries)? This is what drives which privacy regimes apply.",
|
|
52
|
-
"kind": "free_text"
|
|
53
|
-
},
|
|
54
|
-
{
|
|
55
|
-
"ref": "sector",
|
|
56
|
-
"question": "Does the product operate in a regulated sector with its own rules (healthcare, finance/banking, insurance, education, government, telecoms)? Name the sector, or answer \"none\".",
|
|
57
|
-
"kind": "free_text"
|
|
58
|
-
},
|
|
59
|
-
{
|
|
60
|
-
"ref": "gdpr-applies",
|
|
61
|
-
"question": "Do you serve EU/EEA (or UK) individuals or process their personal data? (This is the primary trigger for GDPR / UK GDPR.)",
|
|
62
|
-
"kind": "confirm"
|
|
63
|
-
},
|
|
64
|
-
{
|
|
65
|
-
"ref": "hipaa-applies",
|
|
66
|
-
"question": "Do you handle US protected health information as, or on behalf of, a covered entity or business associate? (This is the primary trigger for HIPAA.)",
|
|
67
|
-
"kind": "confirm"
|
|
68
|
-
},
|
|
69
|
-
{
|
|
70
|
-
"ref": "external-assurance-applies",
|
|
71
|
-
"question": "Do enterprise customers (or your own security posture) require an independent attestation or certification covering security / availability / confidentiality of the service? Name the requested target only as an external source requirement.",
|
|
72
|
-
"kind": "confirm"
|
|
73
|
-
},
|
|
74
|
-
{
|
|
75
|
-
"ref": "data-residency",
|
|
76
|
-
"question": "Are there data-residency or sovereignty requirements — must certain data stay within a region or country (e.g. EU-only hosting, in-country storage)? Describe them, or answer \"none\".",
|
|
77
|
-
"kind": "free_text"
|
|
78
|
-
},
|
|
79
|
-
{
|
|
80
|
-
"ref": "additional-regimes",
|
|
81
|
-
"question": "Any other legal regimes, sector frameworks, government programs, or contractual security commitments that apply? List the externally named sources, or answer \"none\".",
|
|
82
|
-
"kind": "free_text"
|
|
83
|
-
}
|
|
84
|
-
]
|
|
85
|
-
}
|
|
36
|
+
"guidance": "# Compliance Posture — Derivation Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** The regime-derivation rubric below\n> (which triggers imply which regime, how much to capture) is a deliberately\n> explicit first cut meant to be tuned against real runs. Treat it as a\n> starting rubric, not a frozen contract. Crucially, it derives compliance\n> **posture at scaffold depth** — prose constraints, not a per-regime\n> obligation model.\n\n## What this playbook does\n\nYou determine the product's **compliance posture** — which regulatory regimes\nit must be built to satisfy — and record each as a `compliance`-kind constraint\non the existing vision. The vision-elicitation step already named the\ncompliance _seam_ in passing (a single \"we handle EU personal data\" line). Your\njob is the focused, deliberate pass over that seam: reason from the product's\njurisdictions, the classes of data it handles, and its sector to the concrete\nset of regimes, and write each one down as its own constraint with a clear\nprose statement.\n\nYou do **not** re-elicit the whole vision, design the domain, or draft\nrequirements. You touch exactly one slice of the `VisionSnapshot`: its\n`constraints[]` entries of `kind: compliance`. Everything else on the snapshot\n— the idea, the problem, the mission, the success criteria, the\nnon-compliance constraints — you leave exactly as you found it.\n\n## The scaffold-depth boundary (read this before you start)\n\nAt this stage compliance is captured as **prose constraints only**. Each\napplicable regime becomes one constraint entry whose `statement` names the\nregime and the data / jurisdiction it governs — e.g. _\"Must be GDPR-compliant\nfor EU/EEA customer personal data.\"_ That is the whole deliverable.\n\nDo **not** build, and do not try to author into the snapshot:\n\n- per-regime control catalogs or obligation graphs (legal-article mappings,\n sector safeguards, external-assurance criteria),\n- data-flow / residency matrices,\n- retention schedules, DPA registries, or audit-config derivations.\n\nThat deep per-regime obligation model is a deliberately deferred later concern.\nIf you catch yourself modelling controls or obligations, **stop** — you have\nleft scaffold depth. Naming the regime seam accurately here is exactly what\nlets that later, deeper step engage. Getting the _set of applicable regimes_\nright, in prose, is the win.\n\n### Transition to structured compliance conception\n\nThis playbook does not write the dedicated `compliance-program` family. Its\naccepted vision constraints are precursor facts for a later, separately\napproved compliance-conception step. That step may initialize or revise the\noptional structured family only after it resolves exact source versions and\nrights records, declarative application scope, applicability authority, Wildo\nobjective bindings, implementation choices, responsibilities, documentation\nrequirements and explicit gaps.\n\nThe transition is not an automatic conversion and must not reinterpret a\nvision sentence as a control mapping or positive compliance claim. Preserve\nthe vision constraint as product intent, record any missing detail as\n`UNDETERMINED` or an explicit gap, and land the structured family as files in the\nspecifications package. Landing is not accepting: the run leaves working edits,\nand acceptance is a later commit. Who makes it is the host's autonomy posture, and only a\nperson's commit reviews what it accepts. Runtime organizations, assignees, evidence,\ncontrol occurrences and assessments remain outside both artifacts.\n\n## The derivation posture\n\n- **Derive from the product and gathered evidence.** Read the existing vision,\n product facts and cumulative regime evidence supplied by the parent choreography.\n The current `compliance-adequacy` verdict establishes readiness. This playbook\n declares no interview: do not fabricate answers or submit arbitrary\n `elicitationAnswers`. Preserve source-backed applicability reasoning and explicit\n uncertainty. Creator-owned facts that remain unresolved need a supported input or\n clarification path; do not ask the creator to reconstruct externally researchable obligations.\n- **Regime derivation rubric (v1).** Use these as the starting triggers, and\n follow up where an answer is thin:\n - **GDPR / UK GDPR** — serving EU/EEA (or UK) individuals, or processing\n their personal data. Triggered by jurisdiction (EU/EEA/UK) + any personal\n data.\n - **HIPAA** — handling US protected health information as, or on behalf of, a\n covered entity or business associate. Triggered by health data + US\n healthcare context.\n - **External assurance commitments** — enterprise customers or the product's own security posture\n require an independent attestation or certification over security / availability /\n confidentiality. Often contractual rather than statutory — capture the requested target as\n externally supplied source metadata when the go-to-market depends on it.\n - **Data residency / sovereignty** — a requirement that certain data stay\n within a region or country. Triggered by residency answers or sector rules;\n record as its own compliance constraint even when it rides alongside GDPR.\n - **Sector & additional regimes** — payment-card, consumer-privacy, children's-data,\n government-security, contractual-assurance and sector-code obligations. Add each that\n the triggers imply; preserve the exact named source only in the later source registry.\n - When the triggers are genuinely absent (no personal data, no regulated\n sector), the honest posture is _no compliance constraints_ — say so and add\n none. Do not invent a regime to look thorough.\n- **One regime, one constraint.** Keep regimes as separate constraint entries\n rather than one omnibus \"must be compliant\" line — the set is read\n downstream, and a merged statement loses which regimes are actually in play.\n\n## What you emit\n\nYou refine the **existing** `VisionSnapshot` in place. Concretely, you\nadd or update entries in `constraints[]`:\n\n- Each applicable regime is one entry with `kind: compliance`.\n- Each entry has a stable kebab-case `ref` prefixed `constraint-`\n (e.g. `constraint-gdpr-eu-personal-data`,\n `constraint-hipaa-us-phi`, `constraint-external-assurance-security`,\n `constraint-data-residency-eu`), unique across the whole `constraints[]` set.\n- Each entry's `statement` is a prose sentence naming the regime and the data /\n jurisdiction it governs. Where the creator gave the source of the limit\n (a customer contract, a specific law), capture it as the constraint's\n rationale.\n\nLeave every non-`compliance` constraint, and every other vision entity,\nuntouched.\n\n**Idempotent — refine, do not duplicate.** Read the vision first. If compliance\nconstraints already exist (the vision-elicitation step, or a prior run of this\nplaybook, may have written some), reconcile against them: update a statement\nthat is now sharper, add a regime that was missed, and remove one only if the\ncreator confirms it never applied. **Match existing constraints by the REGIME\ntheir `statement` names, not by their `ref` slug** — the vision-elicitation step\nwrites compliance prose without following this playbook's ref convention, so a\nGDPR line it left may sit under any slug (`constraint-gdpr`,\n`constraint-eu-data`, …). When you refine a regime that is already present,\n**reuse that entry's existing `ref`** so it updates in place rather than\nforking; only mint a fresh `constraint-<regime>-<scope>` slug for a regime that\nis genuinely new. Re-running this playbook on an already-posture'd vision must\nconverge to one entry per regime, never accumulate near-duplicate\n`constraint-gdpr-*` entries.\n\n## Quality gate\n\nYour refined snapshot is checked by the deterministic `vision-snapshot-valid`\ngate (`validateVisionSnapshot`) before it commits — the same gate the\nvision-elicitation step uses, because you write to the same family. Duplicate\nrefs and malformed refs (a constraint ref that is not kebab-case with the\n`constraint-` prefix) are hard **errors**; the gate rejects them. Emit clean,\nunique refs the first time. Note that a vision with no compliance constraints\nis perfectly valid — an honestly unregulated product should pass the gate with\nnone.\n\nBeyond the deterministic gate, the advisory judge reads the refined vision against\nthree criteria — regime derivation grounded in the evidence, one regime per constraint\nconverging on re-run, and slice discipline — and its verdicts reach the creator's\nreview as notes. A verdict never refuses a landing.\n\n## Approval\n\nThe refined `VisionSnapshot` is presented to the creator for approval before it\nbecomes the committed `vision-brief`. Show the derived compliance posture back\nin plain prose — the list of regimes, each with the data / jurisdiction it\ngoverns and why it applies — and let the creator confirm or correct it.\nCompliance drives real downstream engine capability, audit, and retention\nchoices, so it is worth one explicit human sign-off that the regime set is\nright.\n\n## Runtime context\n\nBefore you start, read the current journey state and scope, and read the\nexisting vision so you refine its compliance constraints rather than writing a\nfresh, disconnected set.\n\n(The existing vision and its current constraints are already in your brief as the `vision-brief`\ninput section.)\n\n## The evidence, and how to use it\n\nYour run carries what sibling steps gathered — source-attributed regime evidence and the adequacy\nverdict that admitted this step. Derive each constraint from the creator's answers AND that\nevidence, never from recollection:\n\n- A regime the evidence establishes as APPLICABLE becomes a `compliance` constraint whose statement\n names the regime, the trigger (jurisdiction / data class / sector / commitment), and what it\n governs — in the evidence's terms.\n- A regime the evidence EXCLUDES is not written as a constraint, and is not silently dropped either:\n where the creator's answers suggested it, the statement of a neighbouring constraint may note the\n exclusion so the decision is legible.\n- A trigger the evidence could NOT establish becomes a constraint stating the OPEN QUESTION, never a\n guessed answer — an unestablished regime stated as settled is the defect this composite exists to\n end.\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",
|
|
37
|
+
"skillRefs": [],
|
|
38
|
+
"skillBodyRefs": [],
|
|
39
|
+
"contextSources": [],
|
|
40
|
+
"draftableDocumentDefinitionRefs": [],
|
|
41
|
+
"suspendsForClarification": false,
|
|
42
|
+
"briefAdequacyGate": false,
|
|
43
|
+
"briefAdequacyExcludedSources": []
|
|
86
44
|
},
|
|
87
45
|
"executor": "companion_agent",
|
|
88
|
-
"qualityGates": [
|
|
89
|
-
{
|
|
90
|
-
"ref": "vision-snapshot-valid",
|
|
91
|
-
"kind": "deterministic_validator",
|
|
92
|
-
"validatorRef": "saas-specifications:validateVisionSnapshot",
|
|
93
|
-
"required": true
|
|
94
|
-
}
|
|
95
|
-
],
|
|
96
46
|
"approval": "approve_result",
|
|
97
47
|
"budget": {
|
|
98
48
|
"maxRuns": 3
|
|
@@ -0,0 +1,78 @@
|
|
|
1
|
+
# Compliance Research — gather the regime evidence
|
|
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
|
+
You are the **researcher**. Your one job is to find out which regimes plausibly
|
|
16
|
+
apply to this product and report it with sources. You do not decide the posture,
|
|
17
|
+
author constraints, or touch any file — a sibling does that, from what you bring
|
|
18
|
+
back.
|
|
19
|
+
|
|
20
|
+
## Why this step exists
|
|
21
|
+
|
|
22
|
+
The playbook that records the compliance posture used to derive it from nine
|
|
23
|
+
interview answers plus what the model remembered about the law. Recollection is
|
|
24
|
+
confident, fluent, and wrong in exactly the cases that matter here: thresholds
|
|
25
|
+
change, regimes gain territorial reach, sector rules turn on definitions no one
|
|
26
|
+
remembers precisely — and a wrongly excluded regime is a legal statement about the
|
|
27
|
+
product, not a stale price.
|
|
28
|
+
|
|
29
|
+
This step exists so the posture rests on pages someone actually read.
|
|
30
|
+
|
|
31
|
+
## What counts as a regime
|
|
32
|
+
|
|
33
|
+
A regime is **public law or a regulator's instrument** — a statute, a regulation, a
|
|
34
|
+
directive as transposed, a supervisory authority's binding guidance. Those are what
|
|
35
|
+
you research, name and quote: they bind the product whether or not anyone agreed to
|
|
36
|
+
them, so applicability is a question of fact you can settle from a source.
|
|
37
|
+
|
|
38
|
+
A **voluntary security certification or attestation framework is not a regime.** It
|
|
39
|
+
binds only where the creator has committed to it, which makes it an elicited fact
|
|
40
|
+
rather than a researched one — so there is nothing for you to establish and no
|
|
41
|
+
threshold to test. Report the whole class as one line ("voluntary
|
|
42
|
+
security-certification and attestation frameworks — commitments, not legal
|
|
43
|
+
obligations; none committed" or whatever the creator's answers say), and do not name
|
|
44
|
+
an individual proprietary standard or reproduce any of its control identifiers: those
|
|
45
|
+
catalogues are licensed material, and this evidence store is committed into the
|
|
46
|
+
application's repository.
|
|
47
|
+
|
|
48
|
+
The distinction is not bookkeeping. A list that mixes the two invites a posture to
|
|
49
|
+
read a certification as an obligation the product is failing, which is a false legal
|
|
50
|
+
statement about the product — the exact defect this lane exists to prevent, arriving
|
|
51
|
+
from the other direction.
|
|
52
|
+
|
|
53
|
+
## What to establish
|
|
54
|
+
|
|
55
|
+
Work the objective you were given — it was composed for THIS round, and on a later
|
|
56
|
+
round it names what the earlier rounds could not establish. Where it is broad,
|
|
57
|
+
these are the questions worth answering, per candidate regime:
|
|
58
|
+
|
|
59
|
+
1. **The applicability trigger, exactly.** What makes it apply — territorial scope,
|
|
60
|
+
data classes, sector, size thresholds — quoted or closely paraphrased from an
|
|
61
|
+
authoritative source, with enough precision that a reader can test THIS product
|
|
62
|
+
against it. Name a customer commitment only where the regime's OWN text makes one
|
|
63
|
+
part of its trigger; a commitment is otherwise an elicited fact, and treating it as
|
|
64
|
+
a research question is what pulled voluntary certification into this lane.
|
|
65
|
+
2. **Whether THIS product trips it**, given the vision's jurisdictions, data
|
|
66
|
+
classes and sector — stated as your reading, distinct from the trigger itself.
|
|
67
|
+
3. **What the regime obliges at posture level.** One or two sentences — the deep
|
|
68
|
+
obligation model is a later concern; the posture needs "applies / does not
|
|
69
|
+
apply / cannot be established, because …".
|
|
70
|
+
|
|
71
|
+
## How to report
|
|
72
|
+
|
|
73
|
+
- **Authoritative sources first.** A regulator's page or the official text over any
|
|
74
|
+
vendor summary; name the source beside every claim, with its URL.
|
|
75
|
+
- **Say what you could NOT establish.** The gaps aim the next round; hiding them
|
|
76
|
+
produces a posture that reads complete and is not — the exact defect this lane
|
|
77
|
+
replaces.
|
|
78
|
+
- **Never pad.** A regime you found no trigger for is one line, not a paragraph.
|
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ref": "top_down.compliance-research",
|
|
3
|
+
"version": "0.1.0",
|
|
4
|
+
"phase": "top_down",
|
|
5
|
+
"intent": "Gather EVIDENCE about which legal and regulatory regimes plausibly apply to this product — the applicability trigger of each candidate regime (jurisdiction, data class, sector), verified against authoritative sources — and return a condensed, source-attributed brief. A voluntary security certification or attestation is NOT a regime and is not researched here: it binds only if the creator commits to it, so it is a one-line category note and the commitment itself comes from elicitation. Produces no specification family: its whole deliverable is evidence a sibling derives from. It can fetch and search, read prior evidence, and consolidate findings within specifications/research-evidence/. That evidence store is its permitted write scope; this is not an application-implementation run. The companion also attempts to persist the completed brief with provenance as a best-effort backstop. A cancelled final response is not stored as completed evidence.",
|
|
6
|
+
"preconditions": [
|
|
7
|
+
{
|
|
8
|
+
"kind": "artifact_valid",
|
|
9
|
+
"selector": {
|
|
10
|
+
"family": "vision-brief"
|
|
11
|
+
}
|
|
12
|
+
}
|
|
13
|
+
],
|
|
14
|
+
"inputs": [
|
|
15
|
+
{
|
|
16
|
+
"family": "vision-brief"
|
|
17
|
+
}
|
|
18
|
+
],
|
|
19
|
+
"outputs": [],
|
|
20
|
+
"stepOutputs": [
|
|
21
|
+
{
|
|
22
|
+
"ref": "compliance-evidence",
|
|
23
|
+
"condensation": "A brief of at most ~2000 words: each candidate regime by NAME — public law and regulator instruments, never a proprietary certification standard — with the applicability trigger that makes it apply or not apply to THIS product (jurisdiction, data class, sector), the authoritative source consulted (regulator page, official text — never a vendor blog when an official source exists), and an explicit list of what could NOT be established. Every claim carries the URL it came from. Raw page text is never returned — the parent reasons at ITS resolution, and a dump is how a parent context stops fitting.",
|
|
24
|
+
"description": "Source-attributed regime-applicability evidence, condensed for the sibling that derives from it."
|
|
25
|
+
}
|
|
26
|
+
],
|
|
27
|
+
"method": {
|
|
28
|
+
"guidance": "# Compliance Research — gather the regime evidence\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nYou are the **researcher**. Your one job is to find out which regimes plausibly\napply to this product and report it with sources. You do not decide the posture,\nauthor constraints, or touch any file — a sibling does that, from what you bring\nback.\n\n## Why this step exists\n\nThe playbook that records the compliance posture used to derive it from nine\ninterview answers plus what the model remembered about the law. Recollection is\nconfident, fluent, and wrong in exactly the cases that matter here: thresholds\nchange, regimes gain territorial reach, sector rules turn on definitions no one\nremembers precisely — and a wrongly excluded regime is a legal statement about the\nproduct, not a stale price.\n\nThis step exists so the posture rests on pages someone actually read.\n\n## What counts as a regime\n\nA regime is **public law or a regulator's instrument** — a statute, a regulation, a\ndirective as transposed, a supervisory authority's binding guidance. Those are what\nyou research, name and quote: they bind the product whether or not anyone agreed to\nthem, so applicability is a question of fact you can settle from a source.\n\nA **voluntary security certification or attestation framework is not a regime.** It\nbinds only where the creator has committed to it, which makes it an elicited fact\nrather than a researched one — so there is nothing for you to establish and no\nthreshold to test. Report the whole class as one line (\"voluntary\nsecurity-certification and attestation frameworks — commitments, not legal\nobligations; none committed\" or whatever the creator's answers say), and do not name\nan individual proprietary standard or reproduce any of its control identifiers: those\ncatalogues are licensed material, and this evidence store is committed into the\napplication's repository.\n\nThe distinction is not bookkeeping. A list that mixes the two invites a posture to\nread a certification as an obligation the product is failing, which is a false legal\nstatement about the product — the exact defect this lane exists to prevent, arriving\nfrom the other direction.\n\n## What to establish\n\nWork the objective you were given — it was composed for THIS round, and on a later\nround it names what the earlier rounds could not establish. Where it is broad,\nthese are the questions worth answering, per candidate regime:\n\n1. **The applicability trigger, exactly.** What makes it apply — territorial scope,\n data classes, sector, size thresholds — quoted or closely paraphrased from an\n authoritative source, with enough precision that a reader can test THIS product\n against it. Name a customer commitment only where the regime's OWN text makes one\n part of its trigger; a commitment is otherwise an elicited fact, and treating it as\n a research question is what pulled voluntary certification into this lane.\n2. **Whether THIS product trips it**, given the vision's jurisdictions, data\n classes and sector — stated as your reading, distinct from the trigger itself.\n3. **What the regime obliges at posture level.** One or two sentences — the deep\n obligation model is a later concern; the posture needs \"applies / does not\n apply / cannot be established, because …\".\n\n## How to report\n\n- **Authoritative sources first.** A regulator's page or the official text over any\n vendor summary; name the source beside every claim, with its URL.\n- **Say what you could NOT establish.** The gaps aim the next round; hiding them\n produces a posture that reads complete and is not — the exact defect this lane\n replaces.\n- **Never pad.** A regime you found no trigger for is one line, not a paragraph.\n",
|
|
29
|
+
"skillRefs": [],
|
|
30
|
+
"skillBodyRefs": [],
|
|
31
|
+
"contextSources": [],
|
|
32
|
+
"draftableDocumentDefinitionRefs": [],
|
|
33
|
+
"suspendsForClarification": false,
|
|
34
|
+
"briefAdequacyGate": false,
|
|
35
|
+
"briefAdequacyExcludedSources": []
|
|
36
|
+
},
|
|
37
|
+
"executor": "research_agent",
|
|
38
|
+
"approval": "auto",
|
|
39
|
+
"budget": {},
|
|
40
|
+
"onFailure": "keep_and_flag"
|
|
41
|
+
}
|