@wildo-ai/framework-knowledge 1.1.5 → 1.1.7
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/{knowledge/skills/journey-run/references/framework-playbook-approval-policy.md → claude-marketplace/plugins/wildo/references/approval-and-failure-policy.md} +10 -8
- 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/{knowledge/skills/journey-run → claude-marketplace/plugins/wildo}/references/expert-personas-and-deliberations.md +8 -8
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +67 -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 +321 -11
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
- 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 +0 -3
- 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 +12 -2
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +33 -2
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +8 -5
- 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 +55 -10
- 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 +1 -1
- 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 +1 -6
- 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 +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +13 -4
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +10 -3
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +7 -3
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +8 -3
- 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 +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +7 -3
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +9 -4
- 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 +3 -2
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +4 -3
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +1 -3
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +0 -1
- 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 +10 -3
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +8 -3
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +12 -5
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +33 -5
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts +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.document-facts/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +1 -1
- 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/top_down.brand-identity/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +1 -1
- 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 +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +1 -1
- 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 +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +1 -1
- 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 +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +1 -1
- 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 +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +1 -1
- 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 +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +36 -17
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +67 -17
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts +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.js +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +1 -1
- 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.js +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +1 -1
- 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 +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +1 -1
- 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 +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +1 -1
- 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 +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -1
- 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 +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +11 -3
- 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 -1
- package/dist/knowledge/manifest.json +8 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +0 -3
- package/dist/knowledge/playbooks/bottom_up.build/method.md +4 -2
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +31 -7
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +134 -26
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +7 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +84 -29
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -7
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +12 -23
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -7
- package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +12 -14
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -2
- package/dist/knowledge/playbooks/bottom_up.conception/method.md +20 -2
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +15 -7
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +8 -6
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +11 -4
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +2 -4
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +3 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +18 -2
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +1 -2
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +2 -4
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +8 -5
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +16 -2
- package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +3 -3
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +1 -3
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +1 -2
- package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +8 -7
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +11 -4
- package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +27 -5
- package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +1 -4
- 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/method.md +112 -21
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +7 -2
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +2 -4
- 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/method.md +6 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +0 -4
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +1 -2
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +1 -3
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +2 -4
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -2
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +1 -3
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +5 -3
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +2 -4
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +1 -3
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +0 -4
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +2 -4
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +1 -3
- package/dist/knowledge/playbooks/top_down.definition/method.md +7 -4
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +52 -7
- package/dist/knowledge/playbooks/top_down.expert-personas/method.md +1 -1
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +2 -4
- 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/playbook.json +0 -1
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +0 -1
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +2 -4
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +1 -2
- package/dist/knowledge/playbooks/top_down.phase-gate/method.md +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +2 -6
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +17 -1
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +2 -5
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +1 -3
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +15 -7
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +2 -4
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +2 -4
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +1 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +12 -5
- 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/build-plan.task-graph.config.md +71 -6
- package/dist/knowledge/references/capability-composition.config.md +20 -1
- package/dist/knowledge/references/cli.market.generate-command.md +18 -2
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +7 -22
- package/dist/knowledge/references/engine.saas-technical-doc.provider-component.slot.md +83 -0
- package/dist/knowledge/references/example.authorization.service-provider-organization-wide-access.md +12 -0
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +5 -0
- 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 +11 -0
- 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 +7 -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.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 +26 -3
- package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +1 -1
- 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 +14 -30
- 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.module.companion-exports.full.md +8 -13
- 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 +3 -0
- package/dist/knowledge/references/example.provider.frontend-app.module.md +9 -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 +14 -13
- package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +18 -0
- package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +11 -11
- package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +5 -0
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +2 -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 +24 -6
- package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +36 -25
- 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.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/experience-plan.config.md +11 -4
- package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +20 -0
- package/dist/knowledge/references/external-connectors.backend.provider-augmentation.md +75 -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 +21 -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 +34 -2
- package/dist/knowledge/references/market.alternative.config.md +1 -1
- 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 +1 -1
- package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
- package/dist/knowledge/references/market.gain.config.md +1 -1
- package/dist/knowledge/references/market.icp.config.md +1 -1
- package/dist/knowledge/references/market.job.config.md +1 -1
- package/dist/knowledge/references/market.message-template.config.md +1 -1
- package/dist/knowledge/references/market.objection.config.md +1 -1
- package/dist/knowledge/references/market.pain.config.md +1 -1
- package/dist/knowledge/references/market.persona.config.md +1 -1
- package/dist/knowledge/references/market.positioning.config.md +1 -1
- package/dist/knowledge/references/market.proof.config.md +1 -1
- package/dist/knowledge/references/market.references.weighted-edges.md +7 -0
- package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
- package/dist/knowledge/references/market.trigger.config.md +1 -1
- package/dist/knowledge/references/placement-plan.config.md +7 -1
- package/dist/knowledge/references/platform.config.backing-services.md +15 -15
- package/dist/knowledge/references/platform.config.infra-provider-resolution.md +57 -57
- package/dist/knowledge/references/presets.3d.focal-plane-settings.md +45 -0
- package/dist/knowledge/references/presets.3d.frame-style-overrides.md +134 -0
- package/dist/knowledge/references/presets.3d.layout-contract.md +235 -0
- package/dist/knowledge/references/presets.3d.register-layout.md +100 -0
- package/dist/knowledge/references/presets.models.labelling.sections.md +5 -0
- package/dist/knowledge/references/presets.models.shell-region.md +47 -0
- package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -0
- package/dist/knowledge/references/saas.backend.actor-execution-decision-record.md +41 -0
- package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +1 -1
- package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +7 -6
- 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 +7 -0
- package/dist/knowledge/references/saas.backend.domain-module.md +93 -15
- 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 +200 -0
- package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +2 -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 +33 -9
- package/dist/knowledge/references/saas.backend.submission-challenge.md +118 -0
- package/dist/knowledge/references/saas.backend.system-access-service.md +98 -0
- package/dist/knowledge/references/saas.backend.system-of-record-action-runner.md +73 -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.external-data.admin-endpoints.md +56 -2
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +2 -2
- package/dist/knowledge/references/saas.frontend.app-shell.building-blocks.md +253 -0
- package/dist/knowledge/references/saas.frontend.billing-context.md +25 -2
- package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +92 -0
- package/dist/knowledge/references/saas.frontend.consent-based-provider-activation.md +22 -0
- package/dist/knowledge/references/saas.frontend.form-field-address.lookup-slot.md +74 -0
- package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +60 -0
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +7 -5
- package/dist/knowledge/references/saas.frontend.notifications.publish-badge-count.md +60 -0
- package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +17 -2
- 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-layout-templates.md +9 -0
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +100 -5
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +25 -1
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +61 -0
- package/dist/knowledge/references/saas.market.generation-agent.md +0 -1
- 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.audit-trails.actor-attribution.md +97 -0
- package/dist/knowledge/references/saas.models.audit.trail-config.md +15 -9
- 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 +8 -0
- package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +54 -1
- package/dist/knowledge/references/saas.models.billing.referral-program.md +47 -0
- package/dist/knowledge/references/saas.models.config.organization-types.md +74 -0
- package/dist/knowledge/references/saas.models.config.tenant-teardown.md +31 -14
- package/dist/knowledge/references/saas.models.conversation-threads.md +242 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +4 -4
- package/dist/knowledge/references/saas.models.engine-capabilities.md +12 -0
- package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +5 -1
- 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 +667 -6
- 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.http-api-binding.md +812 -29
- 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.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 +11 -7
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +32 -23
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +8 -4
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +22 -20
- package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +14 -0
- package/dist/knowledge/references/saas.models.notifications.targets.md +20 -12
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +61 -34
- package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +9 -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.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.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.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 +34 -0
- 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 +61 -0
- package/dist/knowledge/references/saas.models.providers.compliance-choice.md +98 -13
- package/dist/knowledge/references/saas.models.providers.scope-reauthorization.md +57 -0
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -28
- package/dist/knowledge/references/saas.models.resource-config.operation-submission-challenge.md +54 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +6 -0
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +8 -0
- package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +82 -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 +242 -7
- 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 +75 -7
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +20 -0
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +106 -13
- 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 +6 -4
- package/dist/knowledge/references/saas.specifications.compliance.retention-enforcement-state.md +32 -0
- package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +14 -2
- package/dist/knowledge/references/saas.specifications.processor-register.md +77 -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 +112 -45
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +13 -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 +32 -9
- package/dist/knowledge/references/saas.website.astro.head-renderer.md +1 -1
- package/dist/knowledge/references/saas.website.astro.label-loader.md +7 -4
- package/dist/knowledge/references/saas.website.astro.robots-renderer.md +15 -15
- package/dist/knowledge/references/saas.website.astro.site-context.md +5 -2
- package/dist/knowledge/references/saas.website.blog.bridge.md +17 -4
- 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 +10 -10
- 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 +5 -2
- 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 +23 -4
- 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/website-plan.config.md +39 -6
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +2 -1
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +21 -0
- package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +1 -2
- package/dist/knowledge/references/zod.decorators.file-schema.md +11 -10
- package/dist/knowledge/references/zod.decorators.file-vocabularies.md +7 -4
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +8 -2
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +5 -1
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +5 -1
- package/dist/knowledge/references/zod.factories.address.md +7 -7
- package/dist/knowledge/references/zod.factories.code.md +2 -2
- package/dist/knowledge/references/zod.factories.duration.md +4 -4
- package/dist/knowledge/references/zod.factories.money.md +3 -3
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +1248 -54
- package/dist/knowledge/registries/playbooks.json +81 -109
- package/dist/knowledge/registries/source-tags.json +3201 -1118
- package/dist/knowledge/rules/live-context-door.md +29 -0
- package/dist/knowledge/skills/INDEX.md +27 -24
- 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 +31 -0
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +1 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +1 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +9 -0
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +6 -0
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +94 -16
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +21 -8
- package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +7 -0
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +13 -5
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +30 -6
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +160 -32
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +20 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +14 -2
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +88 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +112 -14
- 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 +21 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +2 -2
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-building-blocks-api.md +279 -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 +1 -0
- package/dist/knowledge/skills/config-navigation/SKILL.md +114 -16
- package/dist/knowledge/skills/config-navigation/references/choosing-a-navigation-shape.md +314 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +11 -7
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +29 -5
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +40 -27
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +22 -20
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +112 -5
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +10 -10
- package/dist/knowledge/skills/config-navigation/references/navigation-zones.md +1 -1
- package/dist/knowledge/skills/config-saas/SKILL.md +3 -1
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +7 -0
- package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +21 -11
- package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +5 -1
- package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +59 -9
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +46 -0
- package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +251 -12
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +8 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +81 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +37 -15
- package/dist/knowledge/skills/configure-billing/SKILL.md +64 -24
- package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +35 -2
- package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +14 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +3 -0
- package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +25 -2
- package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +73 -1
- 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 +27 -12
- package/dist/knowledge/skills/configure-coding-agent/SKILL.md +11 -2
- package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +26 -2
- package/dist/knowledge/skills/email-add-template/SKILL.md +61 -24
- package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +5 -2
- 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 +1 -0
- package/dist/knowledge/skills/engine-product-definitions/SKILL.md +6 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +27 -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 +31 -4
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +26 -3
- 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 +202 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +93 -15
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +96 -11
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +2 -1
- package/dist/knowledge/skills/frontend-cdn-publish/SKILL.md +1 -0
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +1 -0
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +2 -2
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +14 -9
- package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/i18n-label-generation/SKILL.md +1 -0
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +5 -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 +5 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +8 -1
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +5 -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 +150 -44
- package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +83 -74
- package/dist/knowledge/skills/layout-3d-adoption/SKILL.md +180 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-focal-plane-settings-api.md +53 -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 +245 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-registration-api.md +108 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-building-blocks-api.md +259 -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 +43 -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 +32 -1
- 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 +36 -4
- package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +2 -1
- package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
- package/dist/knowledge/skills/market-alternatives/SKILL.md +3 -2
- 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-category/SKILL.md +2 -1
- package/dist/knowledge/skills/market-channels/SKILL.md +2 -1
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +7 -4
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +6 -4
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +28 -13
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +18 -3
- package/dist/knowledge/skills/market-icp/SKILL.md +2 -1
- package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +4 -3
- package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
- package/dist/knowledge/skills/market-persona/SKILL.md +2 -1
- 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 +3 -2
- package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +1 -0
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +1 -0
- package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +2 -1
- package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +3 -2
- package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +1 -0
- package/dist/knowledge/skills/minion-authoring/SKILL.md +5 -1
- 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 +17 -16
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +6 -4
- package/dist/knowledge/skills/module-registration/SKILL.md +2 -1
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +93 -15
- package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +86 -1
- package/dist/knowledge/skills/module-relationships/SKILL.md +3 -2
- 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 +272 -33
- 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-package-allow-list-api.md +111 -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 +132 -23
- 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 +29 -0
- 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 +75 -24
- package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +3 -3
- package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +61 -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 +17 -2
- package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +15 -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 +25 -0
- package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +6 -0
- package/dist/knowledge/skills/resource-add-field/SKILL.md +1 -0
- 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 +105 -6
- package/dist/knowledge/skills/resource-add-module/SKILL.md +1 -0
- package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +2 -1
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +3 -0
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +124 -30
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +1 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +8 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +9 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +17 -1
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +124 -30
- package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +7 -6
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +142 -34
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +98 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +86 -52
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +1 -0
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +100 -5
- package/dist/knowledge/skills/resource-external-data/SKILL.md +1026 -28
- 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 +686 -11
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +904 -31
- package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +166 -6
- 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 +1 -0
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +1 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +12 -0
- 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 +2 -2
- package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +1 -2
- 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 +2 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +28 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +5 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +34 -30
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +5 -1
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +101 -42
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +21 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +1 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +125 -6
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +8 -2
- 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 +61 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +110 -9
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/seeding-operations/SKILL.md +1 -0
- 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 +1 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +61 -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 +14 -16
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +6 -4
- package/dist/knowledge/skills/spec-component-update/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +20 -21
- package/dist/knowledge/skills/spec-family-update/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-feature-update/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +13 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +158 -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 +5 -1
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +1 -0
- package/dist/knowledge/skills/views-app-level/SKILL.md +2 -1
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +43 -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 +5 -1
- package/dist/knowledge/skills/views-composite-authoring/references/composite-embedding-checklist.md +3 -2
- package/dist/knowledge/skills/views-execution-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/website-anonymous-session/SKILL.md +29 -6
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +3 -2
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +17 -4
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +23 -28
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +7 -22
- package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +167 -20
- package/dist/knowledge/skills/website-factory-advanced/SKILL.md +4 -3
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +63 -6
- 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 +6 -2
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -2
- package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +117 -33
- package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +164 -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 +65 -36
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-cta/SKILL.md +32 -22
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-faq/SKILL.md +99 -63
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +27 -18
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +33 -22
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +31 -20
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-hero/SKILL.md +65 -44
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +217 -200
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -11
- 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 +45 -34
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -11
- 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 +30 -25
- package/dist/knowledge/skills/worker-authoring/SKILL.md +1 -0
- package/dist/knowledge/topic-index.json +5957 -1729
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/knowledge/skills/journey-approve/SKILL.md +0 -63
- package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +0 -77
- package/dist/knowledge/skills/journey-next/SKILL.md +0 -82
- package/dist/knowledge/skills/journey-report/SKILL.md +0 -56
- package/dist/knowledge/skills/journey-run/SKILL.md +0 -140
- package/dist/knowledge/skills/journey-status/SKILL.md +0 -60
- /package/dist/{knowledge/skills/journey-approve → claude-marketplace/plugins/wildo}/references/specification-family-map.md +0 -0
|
@@ -25,7 +25,7 @@
|
|
|
25
25
|
],
|
|
26
26
|
"stepOutputs": [],
|
|
27
27
|
"method": {
|
|
28
|
-
"guidance": "# Governance document candidate method\n\nYou are drafting ONE internal governance document for this application, from what the application has\nalready declared. Follow the `compliance-document-authoring` skill for the rules — refs, clause shape,\ncompleteness, what a clause may say. This method says which document, what its concerns are, and the two\nthings a governance document meets that a public notice does not.\n\n## Choose the document, from the four this lane may draft\n\nThe candidate contract admits six `documentRef` values. Four of them are this lane's; the two public ones\n(`document:public.privacy-notice`, `document:public.service-terms`) belong to\n`refinement.compliance-document-candidate` and are not yours to draft here.\n\n| `documentRef` | what it is | its concerns |\n|---|---|---|\n| `document:governance.scope-system-description` | what the system IS, for an assurance reader | service scope, security controls, audit and accountability, access control and roles, tenancy model |\n| `document:governance.roles-responsibilities` | who is accountable for what | access control and roles, operator identity |\n| `document:governance.program-handbook` | how the governance programme runs | security controls, audit and accountability, access control and roles |\n| `document:governance.document-record-control` | how governed documents are themselves controlled | **none** — see below |\n\n**Draft a document this application does not already hold.** The brief opens with what it has already\ndrafted, listing each document this lane may produce as ALREADY DRAFTED or not yet. Drafts are keyed by\n`documentRef`, so drafting one that is already there REPLACES it — right when that draft is wrong, a\nwasted run when it is not.\n\nWhere several remain, **scope and system description** comes first: it is the one an assurance reader\nopens first, the one the other three refer back to, and the only one of the four carrying facts the\nframework derives rather than a person establishes.\n\n`document:governance.document-record-control` composes **no application-fact concern**, and that is\ndeclared rather than missing: it describes how documents are identified, reviewed, released and retired —\na process the operator defines, not anything derivable from the product. Every section you write for it\ncarries `concernRef: null`, and almost every clause is marked. That is the document working, not failing.\n\n## Expect to MARK, and never invent your way past a mark\n\nMost of what a governance document asserts is established by a PERSON, not derived from the application.\nMeasured on the blueprints: `roles-responsibilities` and `document-record-control` carry no\nspecification-derived fact at all — every one of their facts needs a creator decision or a qualified\nreview — and the other two carry a handful.\n\nSo a governance draft that is largely marked incomplete is the expected outcome. Draft every section,\nstate precisely what is missing in `incompleteness.needs` and what would close it in\n`incompleteness.closedBy`, and let the marks be the document's contribution. An application that can read\nexactly which governance decisions it owes is further ahead than one holding no document at all.\n\n**Two inventions are worse than any gap, and both are specific to these documents.**\n\n- **A record of review that did not happen.** These are the documents where a reviewer, an approver, an\n approval, an independence disclosure, a qualification and a decision instant are NAMED. Write one the\n application has not declared and you have not written a weak sentence — you have fabricated the record\n of a review nobody performed. Mark it instead: the fact is owed, and saying so is the answer.\n- **A control asserted to OPERATE, with nothing behind it.** \"Access is reviewed quarterly\", \"we\n monitor\", \"the trail is checked\" are claims about operating effectiveness. In THIS lane one of them\n may be legitimate — and only when a judged run in your brief's evidence section supports it, the\n clause cites that run, and the clause says what was measured and over what period. Without all three,\n say what is CONFIGURED or DECLARED, which is what the facts give you, and mark the rest.\n\n## One section per concern, and SAY which concern\n\nEvery section carries `concernRef` from the closed compliance-concern vocabulary, or `null` for a section\nthat genuinely answers no concern — a preamble, a scope statement, and every section of\n`document-record-control`. Draft one section per concern in the order the table above gives, and produce\n**every** one: a concern nothing can answer becomes a section with a marked clause, never a missing\nheading.\n\nThe value must be the concern's exact name. A near miss (`access-control` for\n`access-control-and-roles`) is worse than a null: it reports the concern as unaddressed while the\ndocument addresses it.\n\nEach section also names what it satisfies in the catalog — `satisfiesSectionRefs` on the section,\n`satisfiesClauseRefs` on each clause, from the blueprint in your brief. Those are what attach the\ncatalog's claim guards to your clauses, so a clause that says what it satisfies is checked against what it\nmust not claim, automatically. A clause that says nothing is checked against nothing.\n\nA section that supplies no required part of the document answers **`null`**, never `[]` — an empty array\nis refused, because it would be a second spelling of the same state. On a governance document the sections\nthat answer `null` are the ones with `concernRef: null` beside them, and `document-record-control` is\nmostly made of them.\n\n## The three ref arrays on every clause\n\nEvery `…Ref` field is a **namespaced ref**: `namespace:slug`, both halves lowercase, words joined by\nhyphens. One malformed ref rejects the whole draft, and all three arrays are required on every clause —\ntwo of them may be empty, but **not the first two at once**, because a clause naming neither a fact nor a\npolicy area is sourced by nothing.\n\n- `factRefs` — the facts this clause rests on, spelled exactly as the facts file declares them. EMPTY is\n normal here: a marked clause usually establishes nothing.\n- `sourcePolicyRefs` — the application POLICY AREA the statement is sourced from, and **every entry must\n be in the `policy:` namespace**: `policy:security-controls`, `policy:access-control`,\n `policy:document-control`. Any other namespace is rejected outright — `policy-area:…` is not a policy\n ref, and neither is a fact ref repeated here. **Do NOT put a fact or its authority in this array.** A\n clause resting on declared facts already cites them through `factRefs`, which resolves them; restating\n one here duplicates the citation beside it and resolves to nothing. So this array is EMPTY for a\n fact-backed clause, and carries a policy area for a clause sourced from a policy rather than a fact.\n- `claimGuardRefs` — at least one: what this clause must NOT be read as claiming. Name the ones that\n apply; do not repeat the same guard on every clause out of habit. You do not name the CATALOG's guard\n for the material — that is added for you from the blueprint clauses this clause `satisfiesClauseRefs`.\n\n`reviewChecklistRefs` needs at least one (`review-checklist:<slug>`): what a human must confirm before\nthis draft is worth anything. On a governance document that list is long, and it is where \"who reviewed\nthis, and when\" belongs — as something a person must supply, never as a name you write into a clause.\n\n`limitationRefs` may be empty and rarely should be: it is where you say, in your own words, what this\ndocument does NOT cover.\n\n## What the blueprint gives you\n\nthe declared `document_blueprint` context section of your brief carries, for each document this lane may draft, its sections, its\nclauses and which of them are required. Read the one matching your `documentRef` and treat its required\nclauses as the floor: a required clause you cannot establish is a clause you MARK, never one you omit.\n\n## Citing this application's own measured evidence\n\nA governance document is the one place an operator may say what its controls DO, and this lane is the\nonly one that may cite the measurements behind such a statement.\n\nthe declared `assurance_evidence` context section of your brief carries the judged runs this application's own assurance cycle has\ncommitted: what was measured, under which demand, with what verdict, at which framework revision, and\nwhether the judge was calibrated. Read it before writing any sentence about what a control does.\n\n- **Cite by putting the run's `assurance-run:` ref in the clause's `evidenceRefs`**, and say in the\n clause what was measured and over what period. A citation a reader cannot scope is one they cannot\n check.\n- **Only a run whose verdict CONCLUDED may support such a statement.** The section marks each one. A\n clause resting on an `INSUFFICIENT_EVIDENCE` run asserts a measurement that did not settle the\n question, which is worse than saying nothing.\n- **Say what it is.** The operator judged its own product with its own harness. A clause may say that\n and what it found; it may not say the result was verified, certified, audited or independently\n assured, and the claim guards refuse the sentence that blurs the two.\n- **Where no run supports the statement, MARK it** — the same answer this lane gives every\n unestablished statement, and the right one.\n\nA ref that resolves to no committed run is refused before the draft becomes a file, as is any citation\nat all in a PUBLIC document. Neither is your judgement to make here: cite only what the section lists.\n\n## You do not approve, release or publish\n\nYou draft the candidate. A human accepts it by committing it; nothing else is acceptance, and landing is\nnot approval. You do not author the release — almost everything a release carries is derived from the\naccepted document definition, and a release nobody has approved is composed and marked `UNAPPROVED`\nrather than withheld.\n\n**Which is why a missing approval never changes what you do here.** Waiting for one before drafting, and\ndescribing a draft as approved to get past a gate, are the two symmetric failures; the first is a\ncompliance workflow standing in front of the mechanism that builds the application.\n\n## Where the draft goes\n\nIt lands as a FILE in the application's specifications package, as an ordinary working edit, beside any\npublic candidates the application already holds.\n\n---\n\n# The compositions\n\nEach entry below is one concern: what it asserts, what in the application it derives from, what state it\nusually reaches, and what closes it when it cannot. Use the ones your document's row names and ignore the\nrest.\n\n### Concern: service scope\n\n**Asserts** — what the service actually is: the modules it runs, the resources it manages, and the\nsurfaces it exposes.\n\n**Derives from** — the application's declared modules and their resources, and the surfaces it builds\n(application, API, public website, technical documentation).\n\n**Completeness** — `DERIVED`.\n\n**Derive it; do not describe the product from its marketing.** Scope in a governed document is the\nboundary of what the statements around it apply to, so an aspirational description silently widens\nevery other clause. The declared modules are the honest boundary, and a capability the application\ndoes not run does not belong here even if it is on the roadmap.\n\n\n### Concern: security controls\n\n**Asserts** — the security measures the application actually runs, at the level of detail a notice\nneeds and no further.\n\n**Derives from** — the application's authored authentication configuration (methods enabled, MFA,\npassword policy, lockout, step-up, session lifetimes), its access floors, its encryption of stored\nsecrets, and its antivirus posture where the `ANTIVIRUS_SCANNING` INFRA capability is provisioned\n(ClamAV, consumed by the engine's file-scanning service on upload). Note this reads the INFRA\ncapability, not an engine provider slot: the equally-named `EngineCapability.ANTIVIRUS_SCANNING` was\nwithdrawn because no provider could fill it, and a derived control statement must never rest on a\nslot that cannot be configured.\n\n**Completeness** — `DERIVED`, bounded.\n\n**Bounded is the operative word.** A public notice states that measures exist and their general\nnature. **It must not enumerate the control set**: a published list of exactly which protections are\nin place, and by implication which are not, is a map for somebody attacking the service. Detail\nbelongs in a security addendum shared under agreement, not on a public page — so this fragment reads\nvery differently in `public.privacy-notice` than in a security schedule, and that difference is\ndeliberate rather than an omission.\n\n**Never state a certification.** \"Compliant\", \"certified\", \"audited\" and \"ISO/SOC\" claims are not\nderivable from configuration and are not this document's to make.\n\n\n### Concern: audit and accountability\n\n**Asserts** — that security-relevant actions are recorded, what kinds are recorded, and where those\nrecords can be sent.\n\n**Derives from** — the application's own audit store, which every application writes; the\n`COMPLIANCE_AUDIT_TRAIL` engine capability, which additionally sends each event to external providers\n(`saas-models` → `external-providers/engine-capabilities.shared.schemas.ts`); the auditable-event\ncatalog the engine emits (authentication, authorization grants, consent decisions, token lifecycle,\nconfiguration and permission changes, cross-tenant administrative access), and per-organization SIEM\nrouting where a tenant has configured it.\n\n**Completeness** — `DERIVED`.\n\nThis is one of the fragments where the ENGINE answers for the application. Every generated\napplication inherits the event catalog and the emitters; a document may state it without the\napplication having configured anything. Where a tenant has additionally routed events to its own\nSIEM, that is the tenant's configuration and belongs in a shared-responsibility statement rather than\nin the operator's own notice.\n\n\n### Concern: access control and roles\n\n**Asserts** — who inside the operator and inside a customer tenant can reach personal data, and what\nconstrains them.\n\n**Derives from** — `CORE_APP_ROLES` and `CORE_ORG_ROLES`\n(`saas-models` → `security/authorizations/roles.shared.schemas.ts`) plus the application's own role\ntable; the administrative-continuity floors (a tenant cannot be left with no usable owner, the\napplication cannot be left with no super-administrator); and the platform-access-grant mechanism,\nunder which a platform operator crossing the per-record tenant boundary requires a granted,\ntime-bounded authorization. Application-wide directory reads retain independent approval. The\napplication audit viewer has a distinct policy: `auditTrail.applicationReadAccess` defaults to\n`AuditApplicationReadAccess.ROLE_BASED` in every environment, admitting the super-administrator or the\nread-only audit-evidence reader role; `INDEPENDENT_APPROVAL` requires a usable application-wide grant in\naddition to the role, and a machine reader (such as an assurance collector) holds one only when it is bound to\nits own credential and signed by a second administrator — a grant bound to a machine never admits the\nadministrator who requested it. Access admission, audit observation and retained\nevidence are separate claims: the access decision does not depend on a successful audit write.\n\n**Completeness** — `DERIVED`.\n\nWorth stating plainly in a B2B notice, because it is the question a customer's own reviewer asks\nfirst: **operator access is governed by the resource and its declared policy.** Ordinary tenant\ncrossings require a usable grant. The application audit viewer is role-based by default, with\nindependent approval available as an explicit policy. Its cross-tenant observations still identify\nthe operator and tenants reached; role-based access does not imply anonymized logs or fabricate an\napproval record. Actual application-wide grants always retain their independent-approval requirement.\n\n**Observation coverage** — the per-record organization gate observes access to an identifiable\ntenant's record when the caller does not already hold organization-wide entry there. Separately,\ndeclared cross-tenant READ, LIST and SEARCH operations outside the organization-scoped gate observe\nthe identifiable tenants in their returned records that the caller does not already belong to,\ngrouped into one observation per tenant reached. This collection observer excludes context-free\ninternal requests and webhook callbacks; COUNT\nreturns no records and is not covered by that observer. Do not turn these scoped mechanisms into a\nclaim that every operation or every returned record produces an audit entry.\n\n**Delivery and evidence** — these observations are best-effort and do not fail the observed request.\nAn unavailable audit service, a synchronous emission error or a rejected emission can leave an\nauthorized request without a retained crossing entry. Observer-side drops have an\n`audit_observation_dropped_total` signal and throttled error logs; failures at the primary audit-store\nwrite have the separate `audit_store_failure_total` signal. Metrics export and log retention must\nactually be configured and operating for those signals to provide evidence beyond the process.\nNeither a loss counter nor an attempted emission substitutes for the missing audit entry.\n\n**Document-authoring consequence** — derive the roles, operation declarations and usable-grant\nrequirements and the audit viewer's access policy from the application's configuration. Do not\nclaim that every audit read required independent approval when the viewer is role-based. Describe the observation mechanisms as supported\ncoverage, then substantiate any statement about recorded access with retained audit records and\nevidence that the collection pipeline and loss monitoring were operating over the period claimed.\nAn empty crossing search alone does not prove that no operator accessed tenant data. `DERIVED`\nabove identifies the source of the access-control description; it does not certify complete audit\ndelivery or the application's operational compliance.\n\n\n### Concern: tenancy model\n\n**Asserts** — that customer data is separated per organization, and where the boundary between the\noperator's responsibilities and the customer's lies.\n\n**Derives from** — the `ORGANIZATIONS` engine capability, the organization scoping applied to every\ntenant-scoped resource, and the cross-tenant admission rules. Ordinary tenant crossings must be\ndeclared and carry a usable access grant. The application audit viewer is a separate policy surface:\nit defaults to role-based access (the super-administrator or the read-only audit-evidence reader), with\n`auditTrail.applicationReadAccess` optionally set to `AuditApplicationReadAccess.INDEPENDENT_APPROVAL`, under\nwhich a machine reader needs a second-signed grant bound to its own credential. Both modes retain cross-tenant read observations;\nrole-based access neither implies anonymized records nor supplies an approval that never occurred.\n\n**Completeness** — `DERIVED`.\n\n**This fragment is where shared responsibility is described, and it must never be flattened.** In a\nB2B SaaS the operator is a PROCESSOR for the data a customer stores about its own people, and a\nCONTROLLER for the data it holds about the customer's users as account holders. Those are different\nroles with different duties over the same database. Say which is which; do not pick one and apply it\nto everything.\n\n**The attribution has a home now.** `operatorComplianceIdentity.roleAllocations` in\n`wildo.saas.config.ts` carries one role per population of data — PROCESSOR for the records a customer\nstores about its own people, CONTROLLER for the account data of the people who administer them. It is\na LIST for exactly the reason this fragment gives: those are different roles over the same database,\nand a single field would force one of them to be wrong.\n\nWhere the attribution is not established, that is a `NEEDS_DECISION` — never a guess — and the\nsurface to name is `roleAllocations`. Not `NEEDS_FRAMEWORK`: there is somewhere to write the answer,\nso the remedy is to fill it in rather than to build something. See the legal-basis fragment.\n\n\n### Concern: operator identity\n\n**Asserts** — who legally operates the service: entity name, registered address, contact route for\ndata-protection questions, and a representative where one is required.\n\n**Derives from** — `operatorComplianceIdentity` in `wildo.saas.config.ts`: the legal entity, its\nregistered address, the privacy contact route, and an Art. 27 representative where one is required.\n\nThe VALUE is never derivable — a legal entity is a fact about the world, not a property of a codebase.\nWhat the framework provides is the PLACE to record it, and until 2026-08-30 it did not: this fragment\nsaid \"no engine change would close it\", which was right about derivation and wrong about the home.\nThe consequence was concrete. A landing REPLACES the produced document on every run, so an operator\nwho answered by editing the document lost the answer at the next regeneration — the answer has to live\nin the application or it does not survive.\n\n**Completeness** — `DERIVED` when the identity is declared; `NEEDS_DECISION` when it is not.\n\n⚠️ `NEEDS_DECISION`, not `NEEDS_FRAMEWORK`, and the distinction is load-bearing now that the surface\nexists. `NEEDS_FRAMEWORK` means there is nowhere to record the answer; `NEEDS_DECISION` means there is\nand nobody has. They have different remedies — build something, versus fill something in — and a\nreader who cannot tell them apart cannot act on either. Say which surface the answer goes to.\n\n**What closes it** — the operator declaring `operatorComplianceIdentity`. It is cheap and it can be\nfilled in later without redrafting anything around it, which is the reason it is not a blocker.\n\n**Never infer it.** Not from the application name, not from a domain, not from another application,\nnot from model memory. A published legal document naming the wrong entity is worse than one that says\nthe entity is not yet recorded — the first misdirects a person exercising a right, the second tells\nthem the document is incomplete.\n\n**Every document needs this fragment**, which makes it the clearest demonstration of why producing\nwith gaps beats blocking: the whole document set would be unproducible until one form is filled in.\n",
|
|
28
|
+
"guidance": "# Governance document candidate method\n\nYou are drafting ONE internal governance document for this application, from what the application has\nalready declared. Follow the `compliance-document-authoring` skill for the rules — refs, clause shape,\ncompleteness, what a clause may say. This method says which document, what its concerns are, and the two\nthings a governance document meets that a public notice does not.\n\n## Choose the document, from the four this lane may draft\n\nThe candidate contract admits six `documentRef` values. Four of them are this lane's; the two public ones\n(`document:public.privacy-notice`, `document:public.service-terms`) belong to\n`refinement.compliance-document-candidate` and are not yours to draft here.\n\n| `documentRef` | what it is | its concerns |\n|---|---|---|\n| `document:governance.scope-system-description` | what the system IS, for an assurance reader | service scope, security controls, audit and accountability, access control and roles, tenancy model |\n| `document:governance.roles-responsibilities` | who is accountable for what | access control and roles, operator identity |\n| `document:governance.program-handbook` | how the governance programme runs | security controls, audit and accountability, access control and roles |\n| `document:governance.document-record-control` | how governed documents are themselves controlled | **none** — see below |\n\n**Draft a document this application does not already hold.** The brief opens with what it has already\ndrafted, listing each document this lane may produce as ALREADY DRAFTED or not yet. Drafts are keyed by\n`documentRef`, so drafting one that is already there REPLACES it — right when that draft is wrong, a\nwasted run when it is not.\n\n**A held draft marked ALREADY DRAFTED, and WRONG comes before everything below.** The brief marks a held\ndraft that cites facts this application no longer declares, and names them. Nothing else corrects it: the\nlanding checks only the document a run writes, so a draft written before the facts were regenerated keeps\nits dead citations until a run redrafts that document. Redraft it against the facts that exist, and cite\nnone of the named ones.\n\nWhere several remain, **scope and system description** comes first: it is the one an assurance reader\nopens first, the one the other three refer back to, and the only one of the four carrying facts the\nframework derives rather than a person establishes.\n\n`document:governance.document-record-control` composes **no application-fact concern**, and that is\ndeclared rather than missing: it describes how documents are identified, reviewed, released and retired —\na process the operator defines, not anything derivable from the product. Every section you write for it\ncarries `concernRef: null`, and almost every clause is marked. That is the document working, not failing.\n\n## Expect to MARK, and never invent your way past a mark\n\nMost of what a governance document asserts is established by a PERSON, not derived from the application.\nMeasured on the blueprints: `roles-responsibilities` and `document-record-control` carry no\nspecification-derived fact at all — every one of their facts needs a creator decision or a qualified\nreview — and the other two carry a handful.\n\nSo a governance draft that is largely marked incomplete is the expected outcome. Draft every section,\nstate precisely what is missing in `incompleteness.needs` and what would close it in\n`incompleteness.closedBy`, and let the marks be the document's contribution. An application that can read\nexactly which governance decisions it owes is further ahead than one holding no document at all.\n\n**Two inventions are worse than any gap, and both are specific to these documents.**\n\n- **A record of review that did not happen.** These are the documents where a reviewer, an approver, an\n approval, an independence disclosure, a qualification and a decision instant are NAMED. Write one the\n application has not declared and you have not written a weak sentence — you have fabricated the record\n of a review nobody performed. Mark it instead: the fact is owed, and saying so is the answer.\n- **A control asserted to OPERATE, with nothing behind it.** \"Access is reviewed quarterly\", \"we\n monitor\", \"the trail is checked\" are claims about operating effectiveness. In THIS lane one of them\n may be legitimate — and only when a judged run in your brief's evidence section supports it, the\n clause cites that run, and the clause says what was measured and over what period. Without all three,\n say what is CONFIGURED or DECLARED, which is what the facts give you, and mark the rest.\n\n## One section per concern, and SAY which concern\n\nEvery section carries `concernRef` from the closed compliance-concern vocabulary, or `null` for a section\nthat genuinely answers no concern — a preamble, a scope statement, and every section of\n`document-record-control`. Draft one section per concern in the order the table above gives, and produce\n**every** one: a concern nothing can answer becomes a section with a marked clause, never a missing\nheading.\n\nThe value must be the concern's exact name. A near miss (`access-control` for\n`access-control-and-roles`) is worse than a null: it reports the concern as unaddressed while the\ndocument addresses it.\n\nEach section also names what it satisfies in the catalog — `satisfiesSectionRefs` on the section,\n`satisfiesClauseRefs` on each clause, from the blueprint in your brief. Those are what attach the\ncatalog's claim guards to your clauses, so a clause that says what it satisfies is checked against what it\nmust not claim, automatically. A clause that says nothing is checked against nothing.\n\nA section that supplies no required part of the document answers **`null`**, never `[]` — an empty array\nis refused, because it would be a second spelling of the same state. On a governance document the sections\nthat answer `null` are the ones with `concernRef: null` beside them, and `document-record-control` is\nmostly made of them.\n\n## The three ref arrays on every clause\n\nEvery `…Ref` field is a **namespaced ref**: `namespace:slug`, both halves lowercase, words joined by\nhyphens. One malformed ref rejects the whole draft, and all three arrays are required on every clause —\ntwo of them may be empty, but **not the first two at once**, because a clause naming neither a fact nor a\npolicy area is sourced by nothing.\n\n- `factRefs` — the facts this clause rests on, spelled exactly as the facts file declares them. EMPTY is\n normal here: a marked clause usually establishes nothing.\n- `sourcePolicyRefs` — the application POLICY AREA the statement is sourced from, and **every entry must\n be in the `policy:` namespace**: `policy:security-controls`, `policy:access-control`,\n `policy:document-control`. Any other namespace is rejected outright — `policy-area:…` is not a policy\n ref, and neither is a fact ref repeated here. **Do NOT put a fact or its authority in this array.** A\n clause resting on declared facts already cites them through `factRefs`, which resolves them; restating\n one here duplicates the citation beside it and resolves to nothing. So this array is EMPTY for a\n fact-backed clause, and carries a policy area for a clause sourced from a policy rather than a fact.\n- `claimGuardRefs` — at least one: what this clause must NOT be read as claiming. Name the ones that\n apply; do not repeat the same guard on every clause out of habit. You do not name the CATALOG's guard\n for the material — that is added for you from the blueprint clauses this clause `satisfiesClauseRefs`.\n\n`reviewChecklistRefs` needs at least one (`review-checklist:<slug>`): what a human must confirm before\nthis draft is worth anything. On a governance document that list is long, and it is where \"who reviewed\nthis, and when\" belongs — as something a person must supply, never as a name you write into a clause.\n\n`limitationRefs` may be empty and rarely should be: it is where you say, in your own words, what this\ndocument does NOT cover.\n\n## What the blueprint gives you\n\nthe declared `document_blueprint` context section of your brief carries, for each document this lane may draft, its sections, its\nclauses and which of them are required. Read the one matching your `documentRef` and treat its required\nclauses as the floor: a required clause you cannot establish is a clause you MARK, never one you omit.\n\n## Citing this application's own measured evidence\n\nA governance document is the one place an operator may say what its controls DO, and this lane is the\nonly one that may cite the measurements behind such a statement.\n\nthe declared `assurance_evidence` context section of your brief carries the judged runs this application's own assurance cycle has\ncommitted: what was measured, under which demand, with what verdict, at which framework revision, and\nwhether the judge was calibrated. Read it before writing any sentence about what a control does.\n\n- **Cite by putting the run's `assurance-run:` ref in the clause's `evidenceRefs`**, and say in the\n clause what was measured and over what period. A citation a reader cannot scope is one they cannot\n check.\n- **Only a run whose verdict CONCLUDED may support such a statement.** The section marks each one. A\n clause resting on an `INSUFFICIENT_EVIDENCE` run asserts a measurement that did not settle the\n question, which is worse than saying nothing.\n- **Say what it is.** The operator judged its own product with its own harness. A clause may say that\n and what it found; it may not say the result was verified, certified, audited or independently\n assured, and the claim guards refuse the sentence that blurs the two.\n- **Where no run supports the statement, MARK it** — the same answer this lane gives every\n unestablished statement, and the right one.\n\nA ref that resolves to no committed run is refused before the draft becomes a file, as is any citation\nat all in a PUBLIC document. Neither is your judgement to make here: cite only what the section lists.\n\n## You do not approve, release or publish\n\nYou draft the candidate. A human accepts it by committing it; nothing else is acceptance, and landing is\nnot approval. You do not author the release — almost everything a release carries is derived from the\naccepted document definition, and a release nobody has approved is composed and marked `UNAPPROVED`\nrather than withheld.\n\n**Which is why a missing approval never changes what you do here.** Waiting for one before drafting, and\ndescribing a draft as approved to get past a gate, are the two symmetric failures; the first is a\ncompliance workflow standing in front of the mechanism that builds the application.\n\n## Where the draft goes\n\nIt lands as a FILE in the application's specifications package, as an ordinary working edit, beside any\npublic candidates the application already holds.\n\n---\n\n# The compositions\n\nEach entry below is one concern: what it asserts, what in the application it derives from, what state it\nusually reaches, and what closes it when it cannot. Use the ones your document's row names and ignore the\nrest.\n\n### Concern: service scope\n\n**Asserts** — what the service actually is: the modules it runs, the resources it manages, and the\nsurfaces it exposes.\n\n**Derives from** — the application's declared modules and their resources, and the surfaces it builds\n(application, API, public website, technical documentation).\n\n**Completeness** — `DERIVED`.\n\n**Derive it; do not describe the product from its marketing.** Scope in a governed document is the\nboundary of what the statements around it apply to, so an aspirational description silently widens\nevery other clause. The declared modules are the honest boundary, and a capability the application\ndoes not run does not belong here even if it is on the roadmap.\n\n\n### Concern: security controls\n\n**Asserts** — the security measures the application actually runs, at the level of detail a notice\nneeds and no further.\n\n**Derives from** — the application's authored authentication configuration (methods enabled, MFA,\npassword policy, lockout, step-up, session lifetimes), its access floors, its encryption of stored\nsecrets, and its antivirus posture where the `ANTIVIRUS_SCANNING` INFRA capability is provisioned\n(ClamAV, consumed by the engine's file-scanning service on upload). Note this reads the INFRA\ncapability, not an engine provider slot: the equally-named `EngineCapability.ANTIVIRUS_SCANNING` was\nwithdrawn because no provider could fill it, and a derived control statement must never rest on a\nslot that cannot be configured.\n\n**Completeness** — `DERIVED`, bounded.\n\n**Bounded is the operative word.** A public notice states that measures exist and their general\nnature. **It must not enumerate the control set**: a published list of exactly which protections are\nin place, and by implication which are not, is a map for somebody attacking the service. Detail\nbelongs in a security addendum shared under agreement, not on a public page — so this fragment reads\nvery differently in `public.privacy-notice` than in a security schedule, and that difference is\ndeliberate rather than an omission.\n\n**Never state a certification.** \"Compliant\", \"certified\", \"audited\" and \"ISO/SOC\" claims are not\nderivable from configuration and are not this document's to make.\n\n\n### Concern: audit and accountability\n\n**Asserts** — that security-relevant actions are recorded, what kinds are recorded, and where those\nrecords can be sent.\n\n**Derives from** — the application's own audit store, which every application writes; the\n`COMPLIANCE_AUDIT_TRAIL` engine capability, which additionally sends each event to external providers\n(`saas-models` → `external-providers/engine-capabilities.shared.schemas.ts`); the auditable-event\ncatalog the engine emits (authentication, authorization grants, consent decisions, token lifecycle,\nconfiguration and permission changes, cross-tenant administrative access), and per-organization SIEM\nrouting where a tenant has configured it.\n\n**Completeness** — `DERIVED`.\n\nThis is one of the fragments where the ENGINE answers for the application. Every generated\napplication inherits the event catalog and the emitters; a document may state it without the\napplication having configured anything. Where a tenant has additionally routed events to its own\nSIEM, that is the tenant's configuration and belongs in a shared-responsibility statement rather than\nin the operator's own notice.\n\n\n### Concern: access control and roles\n\n**Asserts** — who inside the operator and inside a customer tenant can reach personal data, and what\nconstrains them.\n\n**Derives from** — `CORE_APP_ROLES` and `CORE_ORG_ROLES`\n(`saas-models` → `security/authorizations/roles.shared.schemas.ts`) plus the application's own role\ntable; the administrative-continuity floors (a tenant cannot be left with no usable owner, the\napplication cannot be left with no super-administrator); and the platform-access-grant mechanism,\nunder which a platform operator crossing the per-record tenant boundary requires a granted,\ntime-bounded authorization. Application-wide directory reads retain independent approval. The\napplication audit viewer has a distinct policy: `auditTrail.applicationReadAccess` defaults to\n`AuditApplicationReadAccess.ROLE_BASED` in every environment, admitting the super-administrator or the\nread-only audit-evidence reader role; `INDEPENDENT_APPROVAL` requires a usable application-wide grant in\naddition to the role, and a machine reader (such as an assurance collector) holds one only when it is bound to\nits own credential and signed by a second administrator — a grant bound to a machine never admits the\nadministrator who requested it. Access admission, audit observation and retained\nevidence are separate claims: the access decision does not depend on a successful audit write.\n\n**Completeness** — `DERIVED`.\n\nWorth stating plainly in a B2B notice, because it is the question a customer's own reviewer asks\nfirst: **operator access is governed by the resource and its declared policy.** Ordinary tenant\ncrossings require a usable grant. The application audit viewer is role-based by default, with\nindependent approval available as an explicit policy. Its cross-tenant observations still identify\nthe operator and tenants reached; role-based access does not imply anonymized logs or fabricate an\napproval record. Actual application-wide grants always retain their independent-approval requirement.\n\n**Observation coverage** — the per-record organization gate observes access to an identifiable\ntenant's record when the caller does not already hold organization-wide entry there. Separately,\ndeclared cross-tenant READ, LIST and SEARCH operations outside the organization-scoped gate observe\nthe identifiable tenants in their returned records that the caller does not already belong to,\ngrouped into one observation per tenant reached. This collection observer excludes context-free\ninternal requests and webhook callbacks; COUNT\nreturns no records and is not covered by that observer. Do not turn these scoped mechanisms into a\nclaim that every operation or every returned record produces an audit entry.\n\n**Delivery and evidence** — these observations are best-effort and do not fail the observed request.\nAn unavailable audit service, a synchronous emission error or a rejected emission can leave an\nauthorized request without a retained crossing entry. Observer-side drops have an\n`audit_observation_dropped_total` signal and throttled error logs; failures at the primary audit-store\nwrite have the separate `audit_store_failure_total` signal. Metrics export and log retention must\nactually be configured and operating for those signals to provide evidence beyond the process.\nNeither a loss counter nor an attempted emission substitutes for the missing audit entry.\n\n**Document-authoring consequence** — derive the roles, operation declarations and usable-grant\nrequirements and the audit viewer's access policy from the application's configuration. Do not\nclaim that every audit read required independent approval when the viewer is role-based. Describe the observation mechanisms as supported\ncoverage, then substantiate any statement about recorded access with retained audit records and\nevidence that the collection pipeline and loss monitoring were operating over the period claimed.\nAn empty crossing search alone does not prove that no operator accessed tenant data. `DERIVED`\nabove identifies the source of the access-control description; it does not certify complete audit\ndelivery or the application's operational compliance.\n\n\n### Concern: tenancy model\n\n**Asserts** — that customer data is separated per organization, and where the boundary between the\noperator's responsibilities and the customer's lies.\n\n**Derives from** — the `ORGANIZATIONS` engine capability, the organization scoping applied to every\ntenant-scoped resource, and the cross-tenant admission rules. Ordinary tenant crossings must be\ndeclared and carry a usable access grant. The application audit viewer is a separate policy surface:\nit defaults to role-based access (the super-administrator or the read-only audit-evidence reader), with\n`auditTrail.applicationReadAccess` optionally set to `AuditApplicationReadAccess.INDEPENDENT_APPROVAL`, under\nwhich a machine reader needs a second-signed grant bound to its own credential. Both modes retain cross-tenant read observations;\nrole-based access neither implies anonymized records nor supplies an approval that never occurred.\n\n**Completeness** — `DERIVED`.\n\n**This fragment is where shared responsibility is described, and it must never be flattened.** In a\nB2B SaaS the operator is a PROCESSOR for the data a customer stores about its own people, and a\nCONTROLLER for the data it holds about the customer's users as account holders. Those are different\nroles with different duties over the same database. Say which is which; do not pick one and apply it\nto everything.\n\n**The attribution has a home now.** `operatorComplianceIdentity.roleAllocations` in\n`wildo.saas.config.ts` carries one role per population of data — PROCESSOR for the records a customer\nstores about its own people, CONTROLLER for the account data of the people who administer them. It is\na LIST for exactly the reason this fragment gives: those are different roles over the same database,\nand a single field would force one of them to be wrong.\n\nWhere the attribution is not established, that is a `NEEDS_DECISION` — never a guess — and the\nsurface to name is `roleAllocations`. Not `NEEDS_FRAMEWORK`: there is somewhere to write the answer,\nso the remedy is to fill it in rather than to build something. See the legal-basis fragment.\n\n\n### Concern: operator identity\n\n**Asserts** — who legally operates the service: entity name, registered address, contact route for\ndata-protection questions, and a representative where one is required.\n\n**Derives from** — `operatorComplianceIdentity` in `wildo.saas.config.ts`: the legal entity, its\nregistered address, the privacy contact route, and an Art. 27 representative where one is required.\n\nThe VALUE is never derivable — a legal entity is a fact about the world, not a property of a codebase.\nWhat the framework provides is the PLACE to record it, and until 2026-08-30 it did not: this fragment\nsaid \"no engine change would close it\", which was right about derivation and wrong about the home.\nThe consequence was concrete. A landing REPLACES the produced document on every run, so an operator\nwho answered by editing the document lost the answer at the next regeneration — the answer has to live\nin the application or it does not survive.\n\n**Completeness** — `DERIVED` when the identity is declared; `NEEDS_DECISION` when it is not.\n\n⚠️ `NEEDS_DECISION`, not `NEEDS_FRAMEWORK`, and the distinction is load-bearing now that the surface\nexists. `NEEDS_FRAMEWORK` means there is nowhere to record the answer; `NEEDS_DECISION` means there is\nand nobody has. They have different remedies — build something, versus fill something in — and a\nreader who cannot tell them apart cannot act on either. Say which surface the answer goes to.\n\n**What closes it** — the operator declaring `operatorComplianceIdentity`. It is cheap and it can be\nfilled in later without redrafting anything around it, which is the reason it is not a blocker.\n\n**Never infer it.** Not from the application name, not from a domain, not from another application,\nnot from model memory. A published legal document naming the wrong entity is worse than one that says\nthe entity is not yet recorded — the first misdirects a person exercising a right, the second tells\nthem the document is incomplete.\n\n**Every document needs this fragment**, which makes it the clearest demonstration of why producing\nwith gaps beats blocking: the whole document set would be unproducible until one form is filled in.\n",
|
|
29
29
|
"skillRefs": [
|
|
30
30
|
"compliance-document-authoring"
|
|
31
31
|
],
|
|
@@ -162,7 +162,3 @@ so it does not open them. What reaches you is stated per skill below.
|
|
|
162
162
|
logoDirection / visualTone), the mark-type selection table, background
|
|
163
163
|
derivation-safety, and deriving the visual tone from the market voice. Its
|
|
164
164
|
FULL TEXT is in your brief; follow it exactly.
|
|
165
|
-
- `journey-status` — reads the current journey state and whether a
|
|
166
|
-
`vision-brief` / `brand-brief` already exists. That is a READ a tool-using
|
|
167
|
-
agent performs; you receive its answer as your declared inputs instead, so
|
|
168
|
-
you never need to consult the skill itself.
|
|
@@ -32,9 +32,8 @@
|
|
|
32
32
|
],
|
|
33
33
|
"stepOutputs": [],
|
|
34
34
|
"method": {
|
|
35
|
-
"guidance": "# Brand Identity — Interview Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **brand-identity interviewer**. Your job is to draw the product's\nVISUAL identity out of the creator and capture it as a single typed\n**`BrandSnapshot`** — the `brand-brief` artifact. This is the visual\ncounterpart to the vision brief (which captured *intent*) and the market brief\n(which captured the *verbal* voice): here you capture what the product should\n**look like** and, specifically, the brief a logo is generated from.\n\nThe brand-brief you emit is not the logo itself — it is the *direction*. The\ncompanion logo step reads it to generate the master logo and every derived\nasset (favicon, apple-touch, maskable, OG, email, monochrome, dark/light), and\nthose become the single source of truth every surface resolves against. So an\nhonest, well-framed brief is the whole task. You do **not** generate pixels,\nset design-system color tokens, or restate the verbal brand voice — each is a\ndistinct concern with its own home.\n\n## Where the brief comes from\n\nYou do not invent a brand from nothing. Ground it in what the journey already\nknows:\n\n- **The vision brief is your source of meaning.** Read the `VisionSnapshot` and\n derive the mark's **symbolism** from the product's idea and mission — the\n mark should evoke what the product is *for*, not a decorative motif you liked.\n- **The market brief sharpens the register, when present.** If a\n `MarketSnapshot` exists, translate its verbal `tonesOfVoice` (the Nielsen\n Norman 4-axis voice) into a **visual** tone: a serious / formal voice reads as\n restrained geometry and a muted palette; a funny / casual voice reads as\n rounder forms and a warmer accent. The market brief is an *input*, not a\n precondition — if there is no market snapshot yet, derive the visual tone from\n the vision alone and note it as provisional.\n\n## The elicitation posture\n\n- **Interview, do not fill a form.** The typed questions on this playbook\n (`method.elicitation`) are your backbone, not your ceiling. Ask them in a\n natural order, reflect each answer back in one line, and let the creator\n correct you before moving on.\n- **Progressive is fine.** A `BrandSnapshot` requires only the **name**; the\n logo direction and visual tone are OPTIONAL and elicited progressively. If the\n creator can only name the brand today, capture it, note what is still open,\n and stop — the snapshot persists as partially-directed and this playbook can\n resume. Never invent a mark direction the creator did not give you.\n- **One product, one brand.** The snapshot is a single aggregate — one name,\n one logo direction, one visual tone. If the creator describes two brands,\n stop and ask which one this journey is for.\n\n## What you elicit — one aggregate\n\n- **Name** (REQUIRED). The anchor lexical identity: the exact, case-sensitive\n `brandName` the logo renders and every surface prints, plus an optional\n `tagline` to lock up with combination marks / OG imagery. Nothing visual\n here — the mark and the palette come next. A brand without a name has nothing\n for a mark to render; do not proceed until you have it.\n- **Logo direction** (optional, WARNed when absent). The creative brief the\n image model turns into the master logo:\n - `markType` — pick the archetype. **Default to `COMBINATION_MARK`** (symbol +\n wordmark) — it is the only archetype that natively yields BOTH a header\n lockup and a square symbol for favicons/app-icons. Reach for `WORDMARK`\n (text-only) only when the brand is genuinely wordmark-only; warn the creator\n that a wordmark cannot produce a clean square app icon.\n - `motifs` — concrete visual elements to include (short noun phrases).\n - `symbolism` — the meaning the mark should evoke, **derived from the vision\n mission/idea**.\n - `avoid` — imagery don'ts (the negative-prompt guardrails that keep output\n usable).\n - `backgroundTreatment` — keep `TRANSPARENT_ISOLATED` (the default and the\n only treatment that rasterizes losslessly into every derived asset). A\n solid field or contextual scene is an explicit opt-in the pipeline must\n compensate for — the validator WARNs on it.\n- **Visual tone** (optional, WARNed when absent). The aesthetic register — the\n VISUAL counterpart to the market voice: 3–7 concrete `styleKeywords`\n (\"geometric\", \"minimal\", \"warm\"), a one-line `mood`, a prose `colorIntent`\n (the color STORY, not hex values), and optional hex `colorSeeds` pinned only\n when the brand has already committed to anchors that must agree with the\n design system.\n- **Audience** (optional). WHO the brand is for: `targetIcpRefs`, the refs of\n the market ICPs its name and tone are chosen to speak to, copied exactly from\n the market's `icps`, plus a one-line `rationale`. Derive it from what the brief\n already says: the ICP whose preferred voice the visual tone translates, the\n segment the mission and tagline address. Never name a segment the market does\n not hold, and never list an anti-target. Downstream agents are given the\n brand's ICPs, and through them their personas and positionings, from this one\n declaration.\n\n## What you emit\n\nA single `BrandSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told otherwise).\n- `name` — the required anchor (`brandName`, optional `tagline`).\n- `logoDirection` / `visualTone` / `audience` — the optional singletons, present only if elicited.\n- `resolvedAssets` — **leave empty.** This is the companion logo step's output,\n not something you author. Hand-authoring it fabricates asset references the\n pipeline will overwrite or the validator will flag.\n\nAuthor every entity in English. Follow the `brand-logo-authoring` skill for the\nexact field contracts and the mark-type / background / visual-tone decision\naids — its full text is in your brief, under \"The skills this method tells you\nto FOLLOW\". Read it there; you cannot open files.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `brand-snapshot-valid`\ngate (`validateBrandSnapshot`) before it commits. A directed-but-ungenerated\nbrand (a `logoDirection` present, `resolvedAssets` still empty) is expected and\nonly WARNs — it is exactly the state you hand off to the companion logo step. A\nmissing logo direction and a missing visual tone are also warnings, reflecting a\nnot-yet-complete brief. Emit a clean brief and let the warnings stand honestly\nwhen the brand genuinely is not fully directed yet, rather than inventing a\nmark to silence them.\n\nAfter landing, the advisory judge reads the brief against two criteria — grounding in\nthe interview and the vision, and the audience-and-assets hand-off — and its verdicts\nreach the creator's review as notes. A verdict never refuses a landing.\n\n## Approval\n\nThe drafted `BrandSnapshot` is presented to the creator for approval before it\nbecomes the committed `brand-brief`. Show the brief back in plain prose — the\nname, the mark direction, the visual tone — and let the creator confirm or\ncorrect it. The brand-brief is what the logo is generated from and what\npropagates everywhere; it is worth one explicit human sign-off before the mark\nis made.\n\n## Runtime context\n\nBefore you start, read the current journey state, the vision brief that grounds\nthe brand's meaning, and any brand brief that already exists so you refine it\nrather than re-eliciting it from scratch.\n\n(The vision and any previously landed brand brief arrive in your brief as the `vision-brief` and\n`brand-brief` input sections.)\n\n## References\n\nThese are skill FOLDERS installed in the application, and this step has no tools,\nso it does not open them. What reaches you is stated per skill below.\n\n- `brand-logo-authoring` — the field contracts for the `BrandSnapshot` (name /\n logoDirection / visualTone), the mark-type selection table, background\n derivation-safety, and deriving the visual tone from the market voice. Its\n FULL TEXT is in your brief; follow it exactly.\n
|
|
35
|
+
"guidance": "# Brand Identity — Interview Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **brand-identity interviewer**. Your job is to draw the product's\nVISUAL identity out of the creator and capture it as a single typed\n**`BrandSnapshot`** — the `brand-brief` artifact. This is the visual\ncounterpart to the vision brief (which captured *intent*) and the market brief\n(which captured the *verbal* voice): here you capture what the product should\n**look like** and, specifically, the brief a logo is generated from.\n\nThe brand-brief you emit is not the logo itself — it is the *direction*. The\ncompanion logo step reads it to generate the master logo and every derived\nasset (favicon, apple-touch, maskable, OG, email, monochrome, dark/light), and\nthose become the single source of truth every surface resolves against. So an\nhonest, well-framed brief is the whole task. You do **not** generate pixels,\nset design-system color tokens, or restate the verbal brand voice — each is a\ndistinct concern with its own home.\n\n## Where the brief comes from\n\nYou do not invent a brand from nothing. Ground it in what the journey already\nknows:\n\n- **The vision brief is your source of meaning.** Read the `VisionSnapshot` and\n derive the mark's **symbolism** from the product's idea and mission — the\n mark should evoke what the product is *for*, not a decorative motif you liked.\n- **The market brief sharpens the register, when present.** If a\n `MarketSnapshot` exists, translate its verbal `tonesOfVoice` (the Nielsen\n Norman 4-axis voice) into a **visual** tone: a serious / formal voice reads as\n restrained geometry and a muted palette; a funny / casual voice reads as\n rounder forms and a warmer accent. The market brief is an *input*, not a\n precondition — if there is no market snapshot yet, derive the visual tone from\n the vision alone and note it as provisional.\n\n## The elicitation posture\n\n- **Interview, do not fill a form.** The typed questions on this playbook\n (`method.elicitation`) are your backbone, not your ceiling. Ask them in a\n natural order, reflect each answer back in one line, and let the creator\n correct you before moving on.\n- **Progressive is fine.** A `BrandSnapshot` requires only the **name**; the\n logo direction and visual tone are OPTIONAL and elicited progressively. If the\n creator can only name the brand today, capture it, note what is still open,\n and stop — the snapshot persists as partially-directed and this playbook can\n resume. Never invent a mark direction the creator did not give you.\n- **One product, one brand.** The snapshot is a single aggregate — one name,\n one logo direction, one visual tone. If the creator describes two brands,\n stop and ask which one this journey is for.\n\n## What you elicit — one aggregate\n\n- **Name** (REQUIRED). The anchor lexical identity: the exact, case-sensitive\n `brandName` the logo renders and every surface prints, plus an optional\n `tagline` to lock up with combination marks / OG imagery. Nothing visual\n here — the mark and the palette come next. A brand without a name has nothing\n for a mark to render; do not proceed until you have it.\n- **Logo direction** (optional, WARNed when absent). The creative brief the\n image model turns into the master logo:\n - `markType` — pick the archetype. **Default to `COMBINATION_MARK`** (symbol +\n wordmark) — it is the only archetype that natively yields BOTH a header\n lockup and a square symbol for favicons/app-icons. Reach for `WORDMARK`\n (text-only) only when the brand is genuinely wordmark-only; warn the creator\n that a wordmark cannot produce a clean square app icon.\n - `motifs` — concrete visual elements to include (short noun phrases).\n - `symbolism` — the meaning the mark should evoke, **derived from the vision\n mission/idea**.\n - `avoid` — imagery don'ts (the negative-prompt guardrails that keep output\n usable).\n - `backgroundTreatment` — keep `TRANSPARENT_ISOLATED` (the default and the\n only treatment that rasterizes losslessly into every derived asset). A\n solid field or contextual scene is an explicit opt-in the pipeline must\n compensate for — the validator WARNs on it.\n- **Visual tone** (optional, WARNed when absent). The aesthetic register — the\n VISUAL counterpart to the market voice: 3–7 concrete `styleKeywords`\n (\"geometric\", \"minimal\", \"warm\"), a one-line `mood`, a prose `colorIntent`\n (the color STORY, not hex values), and optional hex `colorSeeds` pinned only\n when the brand has already committed to anchors that must agree with the\n design system.\n- **Audience** (optional). WHO the brand is for: `targetIcpRefs`, the refs of\n the market ICPs its name and tone are chosen to speak to, copied exactly from\n the market's `icps`, plus a one-line `rationale`. Derive it from what the brief\n already says: the ICP whose preferred voice the visual tone translates, the\n segment the mission and tagline address. Never name a segment the market does\n not hold, and never list an anti-target. Downstream agents are given the\n brand's ICPs, and through them their personas and positionings, from this one\n declaration.\n\n## What you emit\n\nA single `BrandSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told otherwise).\n- `name` — the required anchor (`brandName`, optional `tagline`).\n- `logoDirection` / `visualTone` / `audience` — the optional singletons, present only if elicited.\n- `resolvedAssets` — **leave empty.** This is the companion logo step's output,\n not something you author. Hand-authoring it fabricates asset references the\n pipeline will overwrite or the validator will flag.\n\nAuthor every entity in English. Follow the `brand-logo-authoring` skill for the\nexact field contracts and the mark-type / background / visual-tone decision\naids — its full text is in your brief, under \"The skills this method tells you\nto FOLLOW\". Read it there; you cannot open files.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `brand-snapshot-valid`\ngate (`validateBrandSnapshot`) before it commits. A directed-but-ungenerated\nbrand (a `logoDirection` present, `resolvedAssets` still empty) is expected and\nonly WARNs — it is exactly the state you hand off to the companion logo step. A\nmissing logo direction and a missing visual tone are also warnings, reflecting a\nnot-yet-complete brief. Emit a clean brief and let the warnings stand honestly\nwhen the brand genuinely is not fully directed yet, rather than inventing a\nmark to silence them.\n\nAfter landing, the advisory judge reads the brief against two criteria — grounding in\nthe interview and the vision, and the audience-and-assets hand-off — and its verdicts\nreach the creator's review as notes. A verdict never refuses a landing.\n\n## Approval\n\nThe drafted `BrandSnapshot` is presented to the creator for approval before it\nbecomes the committed `brand-brief`. Show the brief back in plain prose — the\nname, the mark direction, the visual tone — and let the creator confirm or\ncorrect it. The brand-brief is what the logo is generated from and what\npropagates everywhere; it is worth one explicit human sign-off before the mark\nis made.\n\n## Runtime context\n\nBefore you start, read the current journey state, the vision brief that grounds\nthe brand's meaning, and any brand brief that already exists so you refine it\nrather than re-eliciting it from scratch.\n\n(The vision and any previously landed brand brief arrive in your brief as the `vision-brief` and\n`brand-brief` input sections.)\n\n## References\n\nThese are skill FOLDERS installed in the application, and this step has no tools,\nso it does not open them. What reaches you is stated per skill below.\n\n- `brand-logo-authoring` — the field contracts for the `BrandSnapshot` (name /\n logoDirection / visualTone), the mark-type selection table, background\n derivation-safety, and deriving the visual tone from the market voice. Its\n FULL TEXT is in your brief; follow it exactly.\n",
|
|
36
36
|
"skillRefs": [
|
|
37
|
-
"journey-status",
|
|
38
37
|
"brand-logo-authoring"
|
|
39
38
|
],
|
|
40
39
|
"skillBodyRefs": [
|
|
@@ -45,9 +45,7 @@
|
|
|
45
45
|
"stepOutputs": [],
|
|
46
46
|
"method": {
|
|
47
47
|
"guidance": "# Business Model — Commercial Intent Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** Pricing sketch depth only — no unit\n> economics, no cohort modelling, no competitive price positioning. Those are a\n> later phase; do not perfect them here.\n\n## What this playbook does\n\nYou are recording the product's **commercial intent**: how it makes money, and\nwhat it sells. The output is one `BusinessModelLiteSnapshot` — a revenue-model\nclassification plus a sketch of pricing plans, each cross-linked to the market\nsegments it is sold to and the requirements it unlocks.\n\nIt is a **PLANNING artifact**, in exactly the sense the vision and the roadmap\nare. It is not the billing runtime, not a Stripe catalogue, and not a price list\nanyone is held to. Nothing reads it to charge a customer.\n\n## The one rule that governs everything below\n\n**You do not decide how this product charges. The creator does.**\n\nEvery other top-down family is DERIVED — the market snapshot follows from the\nvision, requirements follow from both, the roadmap follows from the capability\nmap. This one is not, and the difference is not a matter of degree. The same\nproduct is a fair freemium tool, a per-seat B2B subscription, or a\nusage-metered API, and **nothing in the vision, the market or the requirements\ndecides which**. It is a business decision, and only the creator holds it.\n\nSo this playbook interviews. Your job is to take what the creator said and make\nit *structured and cross-linked* — never to fill a gap they left.\n\nConcretely:\n\n- **Never invent a price.** If the creator said \"not decided yet\", omit\n `pricePoint`. A tier with no price is a real, useful plan; a tier with a price\n nobody chose is a fabrication that then propagates — the foundation playbook\n derives the billing capability from this artifact.\n- **Never invent a tier.** Three tiers is the industry default and that is\n exactly why it is a trap. If they described one, produce one.\n- **Never invent a scaling axis.** If they did not say what the price scales\n with, omit `pricingModel` rather than guessing `per_seat`.\n- **\"Not decided yet\" is an answer.** Record what they *did* decide and leave\n the rest absent. Absence is legible; an invention is not.\n\n## What you DO derive\n\nTwo things, and both are cross-links rather than content:\n\n### `targetIcpRefs` — who each plan is sold to\n\nThe creator described tiers in prose (\"a free one for solo people, a paid one\nfor teams\"). The market snapshot holds the ICP refs. Your job is to resolve one\nagainst the other: match each described audience to the ICP that means it, and\nput its ref on the plan.\n\nEvery ref you write must EXIST in the market snapshot. A dangling ICP ref is a\nvalidator ERROR, and it is also the more interesting failure — it usually means\nthe creator described an audience the market analysis never identified, which is\nworth surfacing rather than papering over. If a described audience matches no\nICP, omit the ref and say so in `targetSummary` prose instead.\n\nWatch for **anti-targets**: a vision constraint may explicitly rule out a\nsegment (an enterprise procurement motion, say). Do not target an ICP the vision\nexcludes, even if a tier looks like it fits.\n\n### `includesRequirementRefs` — what each plan unlocks\n\nThis is the traceability that makes the artifact load-bearing rather than\ndecorative: it is what `bottom_up.foundation` reads to decide whether the\napplication needs a billing capability at all.\n\nResolve the creator's description of what each tier includes against the\n`requirements` family, and list the refs. Every ref must exist there. A paid\ntier that unlocks no nameable requirement is a signal worth leaving visible —\neither the requirement is missing, or the tier is not really differentiated.\n\n## The free tier is the one to get right\n\nIf the creator described a free tier or trial, two things matter and both come\nfrom what they said:\n\n- what it **includes** — the requirements it unlocks;\n- what is **deliberately held back** — which is usually the sharper statement of\n the paid tiers' value, and belongs in the paid plan's `includes` prose.\n\nIf they said there is no free tier, say nothing about one. Freemium is a\n*revenue model*, not a default.\n\n## Producing the artifact\n\nOne output, the `business-model` family. The contract is strict:\n\n- **`revenueModel` is required.** Pick the enum member closest to what the\n creator described. If they described something genuinely outside the set, pick\n the nearest and explain the mismatch in the plans' prose — do not stretch a\n member past its meaning.\n- **At least one plan.** A business model with no plans carries no information a\n reader could act on. If the creator sells exactly one thing, that is one plan,\n fully described.\n- **`slug`, not `ref`.** You author a kebab-case slug per plan; the trusted\n runtime stamps the `pricing-plan-` prefix. Never write a ref yourself.\n- **Every optional field is nullable and required.** Send `null` where the\n creator gave you nothing. An omitted key and a considered \"there is none\" must\n not look the same.\n\n## Verification before you answer\n\n- [ ] Every `pricePoint` traces to something the creator actually wrote.\n- [ ] Every plan traces to a tier they described. No tier count was rounded up.\n- [ ] Every `targetIcpRefs` entry exists in the market snapshot.\n- [ ] Every `includesRequirementRefs` entry exists in the requirements snapshot.\n- [ ] No ICP the vision constraints exclude is targeted.\n- [ ] `revenueModel` is consistent with the plans beneath it — a `freemium`\n classification with no free plan, or a `subscription` with only a one-off\n purchase, is incoherent.\n- [ ] Nothing in the artifact answers a question the creator left open.\n",
|
|
48
|
-
"skillRefs": [
|
|
49
|
-
"journey-status"
|
|
50
|
-
],
|
|
48
|
+
"skillRefs": [],
|
|
51
49
|
"skillBodyRefs": [],
|
|
52
50
|
"elicitation": {
|
|
53
51
|
"questions": [
|
|
@@ -56,8 +56,8 @@ This playbook is **idempotent** and a *refinement*: a MarketSnapshot must
|
|
|
56
56
|
already exist (the `artifact_exists` precondition enforces it). Before mapping
|
|
57
57
|
anything:
|
|
58
58
|
|
|
59
|
-
1. Read the current journey state and scope
|
|
60
|
-
|
|
59
|
+
1. Read the current journey state and scope from what this run is given — the loaded
|
|
60
|
+
specifications and the workspace sections of your brief — and do not re-derive it.
|
|
61
61
|
2. Read the existing **MarketSnapshot** (the benefits and their weighting),
|
|
62
62
|
the **requirements** (`requirements` family — the functional/non-functional
|
|
63
63
|
requirements the features must satisfy), and the **VisionSnapshot**
|
|
@@ -202,8 +202,6 @@ These are skill FOLDERS installed in the application, named so each piece of wor
|
|
|
202
202
|
authoring contract a later coding agent can open. This step has no tools and does not open them;
|
|
203
203
|
what reaches you is this method, your declared inputs, and the brief's own sections.
|
|
204
204
|
|
|
205
|
-
- `journey-status` — read the current journey state and
|
|
206
|
-
scope, and confirm a `market-snapshot` already exists to map from.
|
|
207
205
|
- `market-add-feature-benefit` — author/adjust the benefit
|
|
208
206
|
claims and wire their `deliveredByFeatureRefs` edges.
|
|
209
207
|
- `spec-feature-update` — author the spec-first
|
|
@@ -51,9 +51,8 @@
|
|
|
51
51
|
],
|
|
52
52
|
"stepOutputs": [],
|
|
53
53
|
"method": {
|
|
54
|
-
"guidance": "# Capability Map — Benefit → Feature Pivot Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to be\n> iterated. The mapping order, the draft-authoring posture, and the\n> prioritization rubric below are deliberately explicit so they can be tuned\n> against real runs — treat them as a starting rubric, not a frozen contract.\n> The *analytical depth* of the capability work (quantified FIT / Kano scoring\n> precision, a real prioritization model) is intentionally shallow here and is\n> deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **capability architect**. This playbook is the **pivot**: it turns\nthe *value proposition* (what the product promises the market) into *product\ncapability* (the features that actually deliver those promises). Value-proposition\nsharpening already produced a **MarketSnapshot** whose benefits carry weighted\nrelieves/creates/advances edges and per-ICP Kano categories. Your one job is to\nanswer, for every benefit: **which feature delivers this, and does that feature\nexist yet?** — and then record the answer in two places:\n\n1. **The benefit → feature edge** — on the SAME MarketSnapshot, wire every\n benefit's `deliveredByFeatureRefs[]` to the feature(s) that deliver it. This\n edge is the authoritative capability-mapping link (`FeatureBenefitConfig.\n deliveredByFeatureRefs`, required and non-empty): a benefit that is not\n deliverable by any feature is not a real capability. (`market-add-feature-benefit`)\n2. **The spec-first feature drafts** — for every feature the map introduces that\n has **no code registry entry yet**, author a `FeatureSpecificationDraft`\n (purpose, businessRole, lifecycleRole, useWhen/avoidWhen, availabilityRole —\n all in prose). These are **spec-first**: you author them BEFORE the runtime\n `FeatureDefinition` exists; the factory injects the `ref` later from the\n runtime identifier, so a draft is authored ref-less (`Omit<…, 'ref'>`). Use the **Draft path** in `spec-feature-update`; its runtime workflow is for a later implementation task. The draft wrapper carries `featureRef`, while the nested prose payload remains ref-less.\n\nThen you **assess fit** for the resulting feature set with a FIT-scoring + Kano\nstep — kept pluggable and versioned (see \"The scoring seam\" below). This does not set build priority.\n\nThis is a **focused pivot pass**, distinct from value-proposition sharpening\n(which weighted the benefits) and from scope/roadmap (which slots the features\ninto releases). Where value-proposition made the benefits sharp, you make each\nbenefit *deliverable* and give every new capability its first spec.\n\n## Read state first — the two families you read, the two you write\n\nThis playbook is **idempotent** and a *refinement*: a MarketSnapshot must\nalready exist (the `artifact_exists` precondition enforces it). Before mapping\nanything:\n\n1. Read the current journey state and scope through the `journey-status` skill\n (it owns the read; do not re-derive it here).\n2. Read the existing **MarketSnapshot** (the benefits and their weighting),\n the **requirements** (`requirements` family — the functional/non-functional\n requirements the features must satisfy), and the **VisionSnapshot**\n (`vision-brief` — the differentiation anchor). You map capability against the\n real market intent, the real requirements, and the real differentiation — not\n from scratch.\n\n\nYou **read** `market-snapshot` + `requirements` + `vision-brief`; you **write**\nthe refined `market-snapshot` (edge wired) and the `feature-drafts` family (the\nnew drafts).\n\n## The mapping loop (benefit by benefit)\n\nFor each benefit in the snapshot:\n\n1. **Identify the delivering feature(s).** Ask what capability the product must\n have for this benefit's claim to be true. Prefer *one clear feature per\n benefit*; a benefit may legitimately need more than one, and one feature may\n deliver several benefits.\n2. **Reuse before you create.** If a delivering feature already appears on\n another benefit's `deliveredByFeatureRefs`, or already has a draft from an\n earlier run, **reuse that same feature ref** — never mint a second ref for the\n same capability. Reusing refs is what keeps the map coherent and lets the\n downstream scope/roadmap playbook slot each feature exactly once.\n3. **Wire the edge.** Add the feature ref(s) to the benefit's\n `deliveredByFeatureRefs[]`. Every benefit must end with a non-empty edge —\n the gate fails a benefit with an empty `deliveredByFeatureRefs` as\n `EMPTY_BENEFIT_DELIVERED_BY` (ERROR).\n4. **Draft the new feature (spec-first).** If the feature is new (no code\n registry entry, no prior draft), author its `FeatureSpecificationDraft` into\n the `feature-drafts` family. A draft is the **prose subset** of a feature\n spec: a business-language `purpose`, its `businessRole` / optional\n `lifecycleRole`, `useWhen` / `avoidWhen`, optional `businessConstraints`, and\n the `availabilityRole` (how the feature gates / packages). **Author ONLY these\n prose fields.** Do NOT author a `ref` — the factory injects it later from the\n runtime feature identifier, which is why a draft is authored ref-less. Do NOT\n wire `codeHandling` (it links a spec back to a runtime enum member +\n collection entry that does not exist yet at this phase) — the code-handling\n provenance is added when the feature is actually built, not now.\n Use the **Draft path** in `spec-feature-update`, including its wrapper and export contract. Do not run its runtime-enum, definition, policy or profile steps. Keep this a capability contract, not an implementation.\n5. **Trace to requirements + vision.** A feature only earns its place if it\n delivers a benefit that traces to the vision's differentiation AND satisfies\n real requirements. When a benefit's delivering feature has no requirement\n behind it, that is a signal to either add the requirement upstream or drop the\n claim — not to invent a feature the product does not need.\n\n## The scoring seam — FIT + Kano, kept PLUGGABLE and VERSIONED\n\nAssess the mapped capability set with a **FIT-scoring + Kano** step, and let that\nassessment inform how the capabilities get prioritized.\n\n**FIT is a fit signal, NOT a priority ranking — do not conflate them.**\n`computeFeatureFitScoreForICP` answers one narrow question: *how well does this\nfeature serve this ICP* on a deterministic 0–100 scale (edge `degree` × the ICP's\nown edge weight). It deliberately does NOT answer \"which feature do we build\nfirst\" — that is prioritization, a separate, deferred concern. Combine the FIT\nscore with the per-ICP Kano category (`THRESHOLD` = table-stakes, `PERFORMANCE` =\nmore-is-better, `DELIGHTER` = upside) to read *table-stakes vs. upside per\nsegment* — a fit judgement, not a build-order. Bending the FIT score into a\nbuild-order ranking yields wrong answers (this is the locked FIT-vs-priority\nvocabulary the `market-scoring-interpretation` skill enforces).\n\n**This step is a pluggable, versioned interface — bind to it, never embed it.**\nThe scoring / prioritization methodology is expected to change substantially in a\nlater phase, so this playbook references the scoring *interface* (via the\n`market-scoring-interpretation` skill) and consumes its output; it does **not**\nre-implement the scoring math and does **not** hard-couple to any specific scoring\nfunction (`computeFeatureFitScoreForICP` today, a different scorer tomorrow). You do\nnot run the scorer and must not estimate its output: the per-ICP FIT scores are\ncomputed for you and arrive in the declared `market_fit_scores` context section of your brief, beside each\nbenefit's authored Kano category. Read them there and use them to sanity-check the\ncapability set — a `0` carrying a stated reason is structural (an anti-target, or no\nbenefit covering that ICP), not a measurement of poor fit. If\nyou find yourself hand-writing a scoring formula, tuning weights to hit a target\nresult, or building an actual build-order prioritization model, **stop** — that is\nthe depth phase's job, and hard-coding it here would break the pluggability\ncontract (OQ-6).\n\nAt scaffold depth this is a *fit sanity check on the capability set*, not a\ndefended prioritization. The headline gap it surfaces: a table-stakes capability\n(a `THRESHOLD` benefit for a `CORE`/`EXPANSION` ICP) whose delivering feature has\nno draft.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** Do not rewrite edges or drafts that are already\n correct. Only add/correct where a benefit lacks a delivering feature, a new\n benefit appeared, or a draft is genuinely wrong.\n- **Never orphan a ref.** A benefit points at feature refs; those refs must have\n a draft (for new features) or a real registry entry (once code exists).\n The combined output validator checks benefit references against existing feature identities plus the proposed draft wrappers. Supply `existingFeatureRefs` from the actual existing definitions when using `validateCapabilityMapOutputSet` directly; never invent references to make validation pass.\n- **One capability, one ref.** When two benefits are delivered by the same\n capability, they share the feature ref — do not fork it.\n\n## Quality gate\n\nValidate the connected output with `validateCapabilityMapOutputSet`. It parses the output shape, joins existing feature references with proposed draft identities, checks the market snapshot, and calls `validateFeatureSpecificationDrafts` for duplicate identities and each draft's prose contract. The result reports issues from both destinations.\n\nA draft payload is ref-less; its wrapper still supplies the stable `featureRef` needed for these checks. Missing feature links are not exempt merely because runtime definitions have not been created. Market pain/gain/job references and positioning/threshold checks still apply; read `market-snapshot-validation` for their detailed meanings.\n\nValidation is not product review or evidence that the capability has been implemented. Inspect the proposed benefit links and draft intent together before accepting the proposal.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. Explicitly **out of scope here**:\n\n- **A real prioritization model.** The FIT/Kano step here is a *fit* sanity\n check, not a defended, weighted, capacity-fitted *prioritization* (RICE/WSJF\n and the like are later-phase — and FIT is not priority, see the scoring seam).\n The scoring seam stays pluggable — do NOT build or tune a scoring or\n build-order model in this playbook.\n- **Deep feature-spec drafts.** A draft here is a first-cut capability contract\n (purpose / roles / use-when). Rich operation inventories, interaction\n semantics, and UX are the bottom-up build phase's job, not the capability map.\n- **Requirement pain/gain traceability.** A requirement today cross-refs ICPs and\n jobs but NOT market pains/gains, so the \"this requirement delivers\n `gain-X`\" trace that would let capability mapping run benefit → requirement →\n feature *deterministically* is lossy (expressible only in prose). Whether the\n requirements family should gain a pain/gain edge is a filed depth-phase\n question — do NOT reshape the requirements contract here.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nTwo artifacts for this journey:\n\n1. The SAME **MarketSnapshot** at `specifications/src/market/index.ts`,\n with every benefit's `deliveredByFeatureRefs` edge wired to its delivering\n feature(s), passing the `market-snapshot-valid` gate.\n2. The **feature-drafts** at `specifications/src/feature-drafts/index.ts` —\n one spec-first `FeatureSpecificationDraft` per new delivering feature.\n\nThe creator reviews the result (approval posture `approve_result`) before it is\naccepted as the journey's capability map.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n- `journey-status` — read the current journey state and\n scope, and confirm a `market-snapshot` already exists to map from.\n- `market-add-feature-benefit` — author/adjust the benefit\n claims and wire their `deliveredByFeatureRefs` edges.\n- `spec-feature-update` — author the spec-first\n `FeatureSpecificationDraft`(s) for the new delivering features.\n- `market-scoring-interpretation` — the FIT/Kano scoring\n interface: interpret the deterministic scorer's ranking to sanity-check the\n capability set (pluggable seam — consume it, do not re-implement it).\n- `market-snapshot-validation` — the full validation issue\n catalogue the quality gate enforces.\n",
|
|
54
|
+
"guidance": "# Capability Map — Benefit → Feature Pivot Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to be\n> iterated. The mapping order, the draft-authoring posture, and the\n> prioritization rubric below are deliberately explicit so they can be tuned\n> against real runs — treat them as a starting rubric, not a frozen contract.\n> The *analytical depth* of the capability work (quantified FIT / Kano scoring\n> precision, a real prioritization model) is intentionally shallow here and is\n> deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **capability architect**. This playbook is the **pivot**: it turns\nthe *value proposition* (what the product promises the market) into *product\ncapability* (the features that actually deliver those promises). Value-proposition\nsharpening already produced a **MarketSnapshot** whose benefits carry weighted\nrelieves/creates/advances edges and per-ICP Kano categories. Your one job is to\nanswer, for every benefit: **which feature delivers this, and does that feature\nexist yet?** — and then record the answer in two places:\n\n1. **The benefit → feature edge** — on the SAME MarketSnapshot, wire every\n benefit's `deliveredByFeatureRefs[]` to the feature(s) that deliver it. This\n edge is the authoritative capability-mapping link (`FeatureBenefitConfig.\n deliveredByFeatureRefs`, required and non-empty): a benefit that is not\n deliverable by any feature is not a real capability. (`market-add-feature-benefit`)\n2. **The spec-first feature drafts** — for every feature the map introduces that\n has **no code registry entry yet**, author a `FeatureSpecificationDraft`\n (purpose, businessRole, lifecycleRole, useWhen/avoidWhen, availabilityRole —\n all in prose). These are **spec-first**: you author them BEFORE the runtime\n `FeatureDefinition` exists; the factory injects the `ref` later from the\n runtime identifier, so a draft is authored ref-less (`Omit<…, 'ref'>`). Use the **Draft path** in `spec-feature-update`; its runtime workflow is for a later implementation task. The draft wrapper carries `featureRef`, while the nested prose payload remains ref-less.\n\nThen you **assess fit** for the resulting feature set with a FIT-scoring + Kano\nstep — kept pluggable and versioned (see \"The scoring seam\" below). This does not set build priority.\n\nThis is a **focused pivot pass**, distinct from value-proposition sharpening\n(which weighted the benefits) and from scope/roadmap (which slots the features\ninto releases). Where value-proposition made the benefits sharp, you make each\nbenefit *deliverable* and give every new capability its first spec.\n\n## Read state first — the two families you read, the two you write\n\nThis playbook is **idempotent** and a *refinement*: a MarketSnapshot must\nalready exist (the `artifact_exists` precondition enforces it). Before mapping\nanything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief — and do not re-derive it.\n2. Read the existing **MarketSnapshot** (the benefits and their weighting),\n the **requirements** (`requirements` family — the functional/non-functional\n requirements the features must satisfy), and the **VisionSnapshot**\n (`vision-brief` — the differentiation anchor). You map capability against the\n real market intent, the real requirements, and the real differentiation — not\n from scratch.\n\n\nYou **read** `market-snapshot` + `requirements` + `vision-brief`; you **write**\nthe refined `market-snapshot` (edge wired) and the `feature-drafts` family (the\nnew drafts).\n\n## The mapping loop (benefit by benefit)\n\nFor each benefit in the snapshot:\n\n1. **Identify the delivering feature(s).** Ask what capability the product must\n have for this benefit's claim to be true. Prefer *one clear feature per\n benefit*; a benefit may legitimately need more than one, and one feature may\n deliver several benefits.\n2. **Reuse before you create.** If a delivering feature already appears on\n another benefit's `deliveredByFeatureRefs`, or already has a draft from an\n earlier run, **reuse that same feature ref** — never mint a second ref for the\n same capability. Reusing refs is what keeps the map coherent and lets the\n downstream scope/roadmap playbook slot each feature exactly once.\n3. **Wire the edge.** Add the feature ref(s) to the benefit's\n `deliveredByFeatureRefs[]`. Every benefit must end with a non-empty edge —\n the gate fails a benefit with an empty `deliveredByFeatureRefs` as\n `EMPTY_BENEFIT_DELIVERED_BY` (ERROR).\n4. **Draft the new feature (spec-first).** If the feature is new (no code\n registry entry, no prior draft), author its `FeatureSpecificationDraft` into\n the `feature-drafts` family. A draft is the **prose subset** of a feature\n spec: a business-language `purpose`, its `businessRole` / optional\n `lifecycleRole`, `useWhen` / `avoidWhen`, optional `businessConstraints`, and\n the `availabilityRole` (how the feature gates / packages). **Author ONLY these\n prose fields.** Do NOT author a `ref` — the factory injects it later from the\n runtime feature identifier, which is why a draft is authored ref-less. Do NOT\n wire `codeHandling` (it links a spec back to a runtime enum member +\n collection entry that does not exist yet at this phase) — the code-handling\n provenance is added when the feature is actually built, not now.\n Use the **Draft path** in `spec-feature-update`, including its wrapper and export contract. Do not run its runtime-enum, definition, policy or profile steps. Keep this a capability contract, not an implementation.\n5. **Trace to requirements + vision.** A feature only earns its place if it\n delivers a benefit that traces to the vision's differentiation AND satisfies\n real requirements. When a benefit's delivering feature has no requirement\n behind it, that is a signal to either add the requirement upstream or drop the\n claim — not to invent a feature the product does not need.\n\n## The scoring seam — FIT + Kano, kept PLUGGABLE and VERSIONED\n\nAssess the mapped capability set with a **FIT-scoring + Kano** step, and let that\nassessment inform how the capabilities get prioritized.\n\n**FIT is a fit signal, NOT a priority ranking — do not conflate them.**\n`computeFeatureFitScoreForICP` answers one narrow question: *how well does this\nfeature serve this ICP* on a deterministic 0–100 scale (edge `degree` × the ICP's\nown edge weight). It deliberately does NOT answer \"which feature do we build\nfirst\" — that is prioritization, a separate, deferred concern. Combine the FIT\nscore with the per-ICP Kano category (`THRESHOLD` = table-stakes, `PERFORMANCE` =\nmore-is-better, `DELIGHTER` = upside) to read *table-stakes vs. upside per\nsegment* — a fit judgement, not a build-order. Bending the FIT score into a\nbuild-order ranking yields wrong answers (this is the locked FIT-vs-priority\nvocabulary the `market-scoring-interpretation` skill enforces).\n\n**This step is a pluggable, versioned interface — bind to it, never embed it.**\nThe scoring / prioritization methodology is expected to change substantially in a\nlater phase, so this playbook references the scoring *interface* (via the\n`market-scoring-interpretation` skill) and consumes its output; it does **not**\nre-implement the scoring math and does **not** hard-couple to any specific scoring\nfunction (`computeFeatureFitScoreForICP` today, a different scorer tomorrow). You do\nnot run the scorer and must not estimate its output: the per-ICP FIT scores are\ncomputed for you and arrive in the declared `market_fit_scores` context section of your brief, beside each\nbenefit's authored Kano category. Read them there and use them to sanity-check the\ncapability set — a `0` carrying a stated reason is structural (an anti-target, or no\nbenefit covering that ICP), not a measurement of poor fit. If\nyou find yourself hand-writing a scoring formula, tuning weights to hit a target\nresult, or building an actual build-order prioritization model, **stop** — that is\nthe depth phase's job, and hard-coding it here would break the pluggability\ncontract (OQ-6).\n\nAt scaffold depth this is a *fit sanity check on the capability set*, not a\ndefended prioritization. The headline gap it surfaces: a table-stakes capability\n(a `THRESHOLD` benefit for a `CORE`/`EXPANSION` ICP) whose delivering feature has\nno draft.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** Do not rewrite edges or drafts that are already\n correct. Only add/correct where a benefit lacks a delivering feature, a new\n benefit appeared, or a draft is genuinely wrong.\n- **Never orphan a ref.** A benefit points at feature refs; those refs must have\n a draft (for new features) or a real registry entry (once code exists).\n The combined output validator checks benefit references against existing feature identities plus the proposed draft wrappers. Supply `existingFeatureRefs` from the actual existing definitions when using `validateCapabilityMapOutputSet` directly; never invent references to make validation pass.\n- **One capability, one ref.** When two benefits are delivered by the same\n capability, they share the feature ref — do not fork it.\n\n## Quality gate\n\nValidate the connected output with `validateCapabilityMapOutputSet`. It parses the output shape, joins existing feature references with proposed draft identities, checks the market snapshot, and calls `validateFeatureSpecificationDrafts` for duplicate identities and each draft's prose contract. The result reports issues from both destinations.\n\nA draft payload is ref-less; its wrapper still supplies the stable `featureRef` needed for these checks. Missing feature links are not exempt merely because runtime definitions have not been created. Market pain/gain/job references and positioning/threshold checks still apply; read `market-snapshot-validation` for their detailed meanings.\n\nValidation is not product review or evidence that the capability has been implemented. Inspect the proposed benefit links and draft intent together before accepting the proposal.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. Explicitly **out of scope here**:\n\n- **A real prioritization model.** The FIT/Kano step here is a *fit* sanity\n check, not a defended, weighted, capacity-fitted *prioritization* (RICE/WSJF\n and the like are later-phase — and FIT is not priority, see the scoring seam).\n The scoring seam stays pluggable — do NOT build or tune a scoring or\n build-order model in this playbook.\n- **Deep feature-spec drafts.** A draft here is a first-cut capability contract\n (purpose / roles / use-when). Rich operation inventories, interaction\n semantics, and UX are the bottom-up build phase's job, not the capability map.\n- **Requirement pain/gain traceability.** A requirement today cross-refs ICPs and\n jobs but NOT market pains/gains, so the \"this requirement delivers\n `gain-X`\" trace that would let capability mapping run benefit → requirement →\n feature *deterministically* is lossy (expressible only in prose). Whether the\n requirements family should gain a pain/gain edge is a filed depth-phase\n question — do NOT reshape the requirements contract here.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nTwo artifacts for this journey:\n\n1. The SAME **MarketSnapshot** at `specifications/src/market/index.ts`,\n with every benefit's `deliveredByFeatureRefs` edge wired to its delivering\n feature(s), passing the `market-snapshot-valid` gate.\n2. The **feature-drafts** at `specifications/src/feature-drafts/index.ts` —\n one spec-first `FeatureSpecificationDraft` per new delivering feature.\n\nThe creator reviews the result (approval posture `approve_result`) before it is\naccepted as the journey's capability map.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n- `market-add-feature-benefit` — author/adjust the benefit\n claims and wire their `deliveredByFeatureRefs` edges.\n- `spec-feature-update` — author the spec-first\n `FeatureSpecificationDraft`(s) for the new delivering features.\n- `market-scoring-interpretation` — the FIT/Kano scoring\n interface: interpret the deterministic scorer's ranking to sanity-check the\n capability set (pluggable seam — consume it, do not re-implement it).\n- `market-snapshot-validation` — the full validation issue\n catalogue the quality gate enforces.\n",
|
|
55
55
|
"skillRefs": [
|
|
56
|
-
"journey-status",
|
|
57
56
|
"market-add-feature-benefit",
|
|
58
57
|
"market-scoring-interpretation",
|
|
59
58
|
"market-snapshot-validation",
|
|
@@ -20,9 +20,7 @@
|
|
|
20
20
|
"stepOutputs": [],
|
|
21
21
|
"method": {
|
|
22
22
|
"guidance": "# Compliance Analysis — the evidence-grounded posture composite\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nYou are the **conductor's scheduler**, not an author. This composite exists so the\napplication's compliance posture rests on regime texts and regulator pages someone\nactually read — not on what a model remembers about the law, which is confident,\nfluent, and stale in exactly the cases that carry liability.\n\n## The shape\n\nThree children, self-ordered by their own preconditions:\n\n1. **compliance-research** — a read-only web lane gathering regime evidence for the\n jurisdictions, data classes and sector the vision (and the creator's answers)\n put in scope. Returns a condensed, source-attributed brief.\n2. **compliance-evidence-adequacy** — judges whether the evidence is ENOUGH to\n state a posture from, and when it is not, names precisely what is missing so the\n next research round is aimed rather than repeated.\n3. **compliance-posture** — the artifact-producing child: records each applicable\n regime as a `compliance`-kind constraint on the vision, deriving from the\n creator's elicitation answers AND the gathered evidence, only once the adequacy\n gate has returned ADEQUATE.\n\n## What a round's research objective should name\n\nCompose each research objective for THIS round: on the first pass, the candidate\nregimes the vision's jurisdictions/data/sector suggest (verify applicability\ntriggers against authoritative sources — regulator pages, official texts, not\nblogs); on later passes, exactly the gaps the adequacy verdict named. Never re-ask\nwhat a prior round established — its evidence is in the step results.\n",
|
|
23
|
-
"skillRefs": [
|
|
24
|
-
"journey-status"
|
|
25
|
-
],
|
|
23
|
+
"skillRefs": [],
|
|
26
24
|
"skillBodyRefs": [],
|
|
27
25
|
"elicitation": {
|
|
28
26
|
"questions": [
|
|
@@ -140,11 +140,13 @@ form's.
|
|
|
140
140
|
worse than an absent one — it reads as a named accountable party. If no declared role genuinely holds
|
|
141
141
|
a responsibility, record an explicit gap.
|
|
142
142
|
|
|
143
|
-
**A programme role is
|
|
143
|
+
**A programme role is THREE fields, and the key goes in only one of them.** `applicationRoleRef` is the
|
|
144
144
|
application's role key, spelled exactly as that section shows it (`APP_ADMIN_SUPER_ADMIN`). `slug` is
|
|
145
|
-
the programme's OWN lowercase, hyphenated
|
|
145
|
+
the programme's OWN lowercase, hyphenated identifier for the responsibility (`application-owner`,
|
|
146
146
|
`control-operator`), and it is the slug — never the key — that `responsibility`'s role lists and
|
|
147
|
-
`reviewerRoleSlug` refer to.
|
|
147
|
+
`reviewerRoleSlug` refer to. `title` is the role's name as a person reads it (`Application owner`,
|
|
148
|
+
`Control operator`) — what the creator sees wherever the role is named. Two programme roles may map to
|
|
149
|
+
the same key; a slug never carries one.
|
|
148
150
|
- **Never name an organization-scope role as accountable for the PROGRAMME.** An organization role
|
|
149
151
|
answers for one tenant; the programme is about the product. The two scopes are rendered separately
|
|
150
152
|
and labelled for exactly this reason.
|
|
@@ -35,10 +35,8 @@
|
|
|
35
35
|
],
|
|
36
36
|
"stepOutputs": [],
|
|
37
37
|
"method": {
|
|
38
|
-
"guidance": "# Compliance Conception — Derivation Method (v1)\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 the first step in the journey that makes a POSITIVE compliance claim.** Everything before\n> it describes the product. This one says what the product commits to, and a governed document will\n> later quote it. Treat every sentence you write as something an auditor may read back to the\n> operator.\n\n## What this playbook does\n\nThe compliance-posture step decided **which regimes apply**, in prose, as `compliance`-kind\nconstraints on the vision. You turn that into the application's **assurance programme**: which Wildo\ncontrol objectives this product binds, which external requirement each one answers, who is\naccountable, and what is explicitly undetermined.\n\nYou do **not** re-elicit the vision, design the domain, or draft any document. You produce one\nartifact — the `compliance-program` family — and nothing else.\n\n## The one rule that governs everything below\n\n**A vision sentence is not a control mapping.** The posture step recorded \"must be GDPR-compliant for\nEU customer personal data\". That is product intent. It is *not* a decision that this application binds\n`WILDO.PRIVACY.SUBJECT_DATA_EXPORT`, and converting one into the other by reading is exactly what the\nposture step's own method forbids: the transition \"must not reinterpret a vision sentence as a control\nmapping or positive compliance claim.\"\n\nSo every element of the programme comes from one of exactly three places:\n\n| element | comes from |\n|---|---|\n| which objectives exist, what they demand, what proves them | the **engine authority** you were shown — never invented |\n| which sources exist, their edition, authority and rights | the **source registry** — you supply only a slug |\n| what the programme COVERS — the product, its type, its services and modules | the declared `compliance_primary_facts` context section of your brief — DECLARED, never described |\n| which roles this application declares, and which holds the administrative ceiling | the declared `application_role_graph` context section of your brief — a CLOSED SET you select from |\n| WHEN this draft was produced | the HOST's observed instant — stamped, never answered |\n| WHEN it is next reviewed | the application's declared review cadence, applied by the host — a dated commitment, or a stamped limitation saying none is committed |\n| whether an objective CAN apply here | the application's enabled capabilities, computed per objective in the declared `assurance_program_authority` context section of your brief — a lookup, never your finding |\n| whether an objective's intent is TRUE of this product | your reading of the declarations against that intent — a proposal, read back by an advisory judge and accepted by a commit |\n| what is genuinely undetermined | the **creator's answer in this run** — the one thing no declaration records |\n\nIf something comes from none of those, it does not go in the programme. Say it is `UNDETERMINED`, or\nstate it as a limitation.\n\n## What you will be refused for\n\nThe runtime normalizes your answer and **rejects** it — spending one of three runs — if you:\n\n- bind an objective the authority basis states no expectation for. The basis covers a small set; you\n were shown exactly which. There is no partial credit for a plausible objective.\n- cite a source the registry does not carry. `sourceSlug` is the registry ref minus its `source:`\n prefix, spelled exactly.\n- bind the same objective twice.\n- bind an objective the authority section marks `NOT_APPLICABLE` for this application. Every capability\n it requires is absent, so nothing could ever evidence it.\n- state `APPLICABLE` for an objective the authority section marks `UNDETERMINED`. A capability that would\n attest it is absent here, so the evidence `APPLICABLE` promises cannot be produced; state it\n `UNDETERMINED` and say what is open.\n\nThese are not style checks. Each one is a claim the framework cannot stand behind, and the rejection\nmessage names what you got wrong — read it and fix that, rather than restructuring the answer.\n\n## Deciding an obligation\n\nFor each objective you were shown, ask three questions **in order**, and stop at the first \"no\".\n\n1. **Does this application actually do what the intent describes?** You have its resource declarations\n — erasure treatment, data-subject kinds, whether subject export is declared. Use them. An objective\n whose intent describes something the declarations do not show is not bound. Read the computed\n applicability first: a `NOT_APPLICABLE` objective is refused, and an `UNDETERMINED` one is bound only\n as `UNDETERMINED`.\n2. **Which external requirement does it answer, and does that source reach this application?** If the\n product serves no EU data subjects, GDPR does not reach it and no obligation should cite it.\n3. **Can you justify binding it from the evidence you were shown?** Write the disposition you can\n defend, with the reason. `APPROVED` is not you asserting that a review happened — the review is\n the human's COMMIT, and until then this is a proposal on disk. What is forbidden is a\n disposition you cannot point at evidence for; \"the objective sounded right\" is the failure this\n whole step exists to prevent.\n\nAn objective that fails (1) or (2) is simply absent from the programme. **Absence is a legitimate,\nreadable answer** — a programme binding one objective honestly is worth more than one binding four\nhopefully.\n\n### Applicability: `APPLICABLE` or `UNDETERMINED`, never a guess\n\n`UNDETERMINED` with a reason is the right answer whenever the run cannot settle it, and the posture\nstep asks for exactly that. It is visible, it is actionable, and a later pass can close it. A confident\n`APPLICABLE` that nobody could justify is invisible and reads as a decision somebody made.\n\n`NOT_APPLICABLE` is not offered to you. That branch requires evidence that the obligation does not\napply, and evidence is not something a derivation can produce.\n\n## Limitations are required, and they are the honest part\n\nYou must state at least one. The programme you produce binds a handful of objectives out of everything\na regime demands, and a reader who is not told that will read it as a complete posture. Say plainly\nwhat it does not cover: which objectives are unbound, that no operating effectiveness is claimed, and\nthat the programme is not a conformity assertion for any named regime.\n\nThis is not a disclaimer bolted on. It is what makes the rest of the document quotable.\n\n## What reads your programme back\n\nAn advisory judge reads the landed programme against the same declarations and the same computed\napplicability you were given. For each obligation it asks whether the objective's intent is true of this\nproduct, whether an `UNDETERMINED` says what is open, and whether anything claims operating effectiveness, regime conformity or a wider scope. It refuses\nnothing — its verdict travels with the result — but it is why \"the objective sounded right\" does not\nsurvive to the commit.\n\nIt replaced a question that asked the creator, per objective, whether the application met it. That answer\nis either in the declarations, where you can read it, or it is a judgement — which is a judge's job, not a\nform's.\n\n## What you never do\n\n- **Never author a rights record, an edition, or an authority name.** Those come from the registry\n because they govern what may be reproduced from a source. Inventing one is a licensing claim nobody\n reviewed.\n- **Never invent a reviewer, and never author a review instant.** You are not asked for one: the host\n stamps the instant it observed this draft. What makes the dispositions a REVIEW is the human's\n COMMIT — a landed programme is a working edit until then — so write the disposition you can\n justify from the evidence and let acceptance happen where acceptance happens.\n- **Never author a next-review date, and never write a review-schedule limitation.** You are not asked\n for either. The host applies the application's declared review cadence; where none is declared the\n programme is still produced and carries a stamped limitation saying no schedule is committed. A\n limitation of your own on the same point would say it twice, in words nothing checks.\n- **Never invent a ROLE KEY, and do not ask for one either.** The accountable and operating roles are\n SELECTED from the declared `application_role_graph` context section of your brief, which lists every role this application\n declares and marks the administrative ceiling at each scope. A role key that resolves to nothing is\n worse than an absent one — it reads as a named accountable party. If no declared role genuinely holds\n a responsibility, record an explicit gap.\n\n **A programme role is TWO fields, and the key goes in only one of them.** `applicationRoleRef` is the\n application's role key, spelled exactly as that section shows it (`APP_ADMIN_SUPER_ADMIN`). `slug` is\n the programme's OWN lowercase, hyphenated name for the responsibility (`application-owner`,\n `control-operator`), and it is the slug — never the key — that `responsibility`'s role lists and\n `reviewerRoleSlug` refer to. Two programme roles may map to the same key; a slug never carries one.\n- **Never name an organization-scope role as accountable for the PROGRAMME.** An organization role\n answers for one tenant; the programme is about the product. The two scopes are rendered separately\n and labelled for exactly this reason.\n- **Never state operating effectiveness.** That a control is configured is not that it has worked. The\n programme has no way to say the latter, and a document downstream is refused for claiming it.\n- **Never widen the scope you were given, and do not ask for it.** What the programme covers is\n DECLARED: the product, its type and its services are in\n the declared `compliance_primary_facts` context section of your brief, which also separates the contracted service from\n build-time tooling that is deliberately outside it. State the boundary from that, naming the\n services individually — an application, its environments and its services, never the operator's\n whole organisation. A service not listed there is not part of this application.\n\n## The two routing decisions you emit beside the programme\n\nNaming which documents are required and stopping there leaves the next step with nothing to route by.\nSo this playbook also answers where those documents are published, and what must happen before one\nfaces a real reader.\n\n### `document-publication` — which variants exist at all\n\nOne entry per exact **locale x jurisdiction** combination the application publishes in. The two are an\nINSEPARABLE pair: `en-GB` for `jurisdiction:eu` and `en-GB` for `jurisdiction:gb` are two variants\ncarrying different clauses, and neither implies a third assembled from one of each. Nothing\ndownstream may recombine the axes.\n\nTake the jurisdictions from what the application has DECLARED — its operating regions, its posture —\nnever from where you imagine it might expand. A variant nobody publishes in is a routing claim no\ndocument can honour, and every later release must name a variant declared here.\n\n### `document-release-policy` — which approval lane each requirement takes\n\nOne selection per documentation requirement the authority section lists under **Documentation\nrequirements this application owes**, keyed by that `requirementRef` and `requirementVersion` exactly.\nThose are DERIVED from what the application declares — the programme declares exactly them, and you do\nnot write them — so a selection naming any other requirement is refused:\n\n| lane | means |\n|---|---|\n| `DRAFT_ONLY` | the document may be drafted and retained; nothing may serve it as published |\n| `OPERATOR_ATTESTED` | an accountable operator may release an exact draft with explicit limitations, which the selection must list |\n| `QUALIFIED_REVIEW` | the reviewer-authority route is required before it is served |\n\n**Choose the lane the application can honestly satisfy today, and prefer the strictest only where it\nis true.** `DRAFT_ONLY` is the right answer for a document nobody has reviewed, and it is not a\nfailure state: a drafted document and an unapproved release are both legitimate artifacts an\napplication holds for most of its life.\n\n**None of these lanes blocks drafting or composing a release.** They decide what must be true before\na document faces a REAL READER, which is a later question than the one this journey is answering. A\nlane that stopped the build would be a compliance workflow standing in front of the\napplication-creation mechanism.\n\n## Where this leaves the journey\n\nThe programme you land is the accepted answer for which controls this product commits to. It is what\nan obligation register reads, what a governed document cites when it says the operator has a\nprogramme, and what a later mapping pass binds to external framework identifiers.\n\nIt is accepted the way everything is accepted here: by a commit, which this run does not make. Who\nmakes it is the host's autonomy posture, and the programme's dispositions become a REVIEW only when a\nPERSON commits them. A commit the development companion makes under the YOLO posture is authored as\nthe companion: it accepts the working edit and reviews nothing.\n",
|
|
39
|
-
"skillRefs": [
|
|
40
|
-
"journey-status"
|
|
41
|
-
],
|
|
38
|
+
"guidance": "# Compliance Conception — Derivation Method (v1)\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 the first step in the journey that makes a POSITIVE compliance claim.** Everything before\n> it describes the product. This one says what the product commits to, and a governed document will\n> later quote it. Treat every sentence you write as something an auditor may read back to the\n> operator.\n\n## What this playbook does\n\nThe compliance-posture step decided **which regimes apply**, in prose, as `compliance`-kind\nconstraints on the vision. You turn that into the application's **assurance programme**: which Wildo\ncontrol objectives this product binds, which external requirement each one answers, who is\naccountable, and what is explicitly undetermined.\n\nYou do **not** re-elicit the vision, design the domain, or draft any document. You produce one\nartifact — the `compliance-program` family — and nothing else.\n\n## The one rule that governs everything below\n\n**A vision sentence is not a control mapping.** The posture step recorded \"must be GDPR-compliant for\nEU customer personal data\". That is product intent. It is *not* a decision that this application binds\n`WILDO.PRIVACY.SUBJECT_DATA_EXPORT`, and converting one into the other by reading is exactly what the\nposture step's own method forbids: the transition \"must not reinterpret a vision sentence as a control\nmapping or positive compliance claim.\"\n\nSo every element of the programme comes from one of exactly three places:\n\n| element | comes from |\n|---|---|\n| which objectives exist, what they demand, what proves them | the **engine authority** you were shown — never invented |\n| which sources exist, their edition, authority and rights | the **source registry** — you supply only a slug |\n| what the programme COVERS — the product, its type, its services and modules | the declared `compliance_primary_facts` context section of your brief — DECLARED, never described |\n| which roles this application declares, and which holds the administrative ceiling | the declared `application_role_graph` context section of your brief — a CLOSED SET you select from |\n| WHEN this draft was produced | the HOST's observed instant — stamped, never answered |\n| WHEN it is next reviewed | the application's declared review cadence, applied by the host — a dated commitment, or a stamped limitation saying none is committed |\n| whether an objective CAN apply here | the application's enabled capabilities, computed per objective in the declared `assurance_program_authority` context section of your brief — a lookup, never your finding |\n| whether an objective's intent is TRUE of this product | your reading of the declarations against that intent — a proposal, read back by an advisory judge and accepted by a commit |\n| what is genuinely undetermined | the **creator's answer in this run** — the one thing no declaration records |\n\nIf something comes from none of those, it does not go in the programme. Say it is `UNDETERMINED`, or\nstate it as a limitation.\n\n## What you will be refused for\n\nThe runtime normalizes your answer and **rejects** it — spending one of three runs — if you:\n\n- bind an objective the authority basis states no expectation for. The basis covers a small set; you\n were shown exactly which. There is no partial credit for a plausible objective.\n- cite a source the registry does not carry. `sourceSlug` is the registry ref minus its `source:`\n prefix, spelled exactly.\n- bind the same objective twice.\n- bind an objective the authority section marks `NOT_APPLICABLE` for this application. Every capability\n it requires is absent, so nothing could ever evidence it.\n- state `APPLICABLE` for an objective the authority section marks `UNDETERMINED`. A capability that would\n attest it is absent here, so the evidence `APPLICABLE` promises cannot be produced; state it\n `UNDETERMINED` and say what is open.\n\nThese are not style checks. Each one is a claim the framework cannot stand behind, and the rejection\nmessage names what you got wrong — read it and fix that, rather than restructuring the answer.\n\n## Deciding an obligation\n\nFor each objective you were shown, ask three questions **in order**, and stop at the first \"no\".\n\n1. **Does this application actually do what the intent describes?** You have its resource declarations\n — erasure treatment, data-subject kinds, whether subject export is declared. Use them. An objective\n whose intent describes something the declarations do not show is not bound. Read the computed\n applicability first: a `NOT_APPLICABLE` objective is refused, and an `UNDETERMINED` one is bound only\n as `UNDETERMINED`.\n2. **Which external requirement does it answer, and does that source reach this application?** If the\n product serves no EU data subjects, GDPR does not reach it and no obligation should cite it.\n3. **Can you justify binding it from the evidence you were shown?** Write the disposition you can\n defend, with the reason. `APPROVED` is not you asserting that a review happened — the review is\n the human's COMMIT, and until then this is a proposal on disk. What is forbidden is a\n disposition you cannot point at evidence for; \"the objective sounded right\" is the failure this\n whole step exists to prevent.\n\nAn objective that fails (1) or (2) is simply absent from the programme. **Absence is a legitimate,\nreadable answer** — a programme binding one objective honestly is worth more than one binding four\nhopefully.\n\n### Applicability: `APPLICABLE` or `UNDETERMINED`, never a guess\n\n`UNDETERMINED` with a reason is the right answer whenever the run cannot settle it, and the posture\nstep asks for exactly that. It is visible, it is actionable, and a later pass can close it. A confident\n`APPLICABLE` that nobody could justify is invisible and reads as a decision somebody made.\n\n`NOT_APPLICABLE` is not offered to you. That branch requires evidence that the obligation does not\napply, and evidence is not something a derivation can produce.\n\n## Limitations are required, and they are the honest part\n\nYou must state at least one. The programme you produce binds a handful of objectives out of everything\na regime demands, and a reader who is not told that will read it as a complete posture. Say plainly\nwhat it does not cover: which objectives are unbound, that no operating effectiveness is claimed, and\nthat the programme is not a conformity assertion for any named regime.\n\nThis is not a disclaimer bolted on. It is what makes the rest of the document quotable.\n\n## What reads your programme back\n\nAn advisory judge reads the landed programme against the same declarations and the same computed\napplicability you were given. For each obligation it asks whether the objective's intent is true of this\nproduct, whether an `UNDETERMINED` says what is open, and whether anything claims operating effectiveness, regime conformity or a wider scope. It refuses\nnothing — its verdict travels with the result — but it is why \"the objective sounded right\" does not\nsurvive to the commit.\n\nIt replaced a question that asked the creator, per objective, whether the application met it. That answer\nis either in the declarations, where you can read it, or it is a judgement — which is a judge's job, not a\nform's.\n\n## What you never do\n\n- **Never author a rights record, an edition, or an authority name.** Those come from the registry\n because they govern what may be reproduced from a source. Inventing one is a licensing claim nobody\n reviewed.\n- **Never invent a reviewer, and never author a review instant.** You are not asked for one: the host\n stamps the instant it observed this draft. What makes the dispositions a REVIEW is the human's\n COMMIT — a landed programme is a working edit until then — so write the disposition you can\n justify from the evidence and let acceptance happen where acceptance happens.\n- **Never author a next-review date, and never write a review-schedule limitation.** You are not asked\n for either. The host applies the application's declared review cadence; where none is declared the\n programme is still produced and carries a stamped limitation saying no schedule is committed. A\n limitation of your own on the same point would say it twice, in words nothing checks.\n- **Never invent a ROLE KEY, and do not ask for one either.** The accountable and operating roles are\n SELECTED from the declared `application_role_graph` context section of your brief, which lists every role this application\n declares and marks the administrative ceiling at each scope. A role key that resolves to nothing is\n worse than an absent one — it reads as a named accountable party. If no declared role genuinely holds\n a responsibility, record an explicit gap.\n\n **A programme role is THREE fields, and the key goes in only one of them.** `applicationRoleRef` is the\n application's role key, spelled exactly as that section shows it (`APP_ADMIN_SUPER_ADMIN`). `slug` is\n the programme's OWN lowercase, hyphenated identifier for the responsibility (`application-owner`,\n `control-operator`), and it is the slug — never the key — that `responsibility`'s role lists and\n `reviewerRoleSlug` refer to. `title` is the role's name as a person reads it (`Application owner`,\n `Control operator`) — what the creator sees wherever the role is named. Two programme roles may map to\n the same key; a slug never carries one.\n- **Never name an organization-scope role as accountable for the PROGRAMME.** An organization role\n answers for one tenant; the programme is about the product. The two scopes are rendered separately\n and labelled for exactly this reason.\n- **Never state operating effectiveness.** That a control is configured is not that it has worked. The\n programme has no way to say the latter, and a document downstream is refused for claiming it.\n- **Never widen the scope you were given, and do not ask for it.** What the programme covers is\n DECLARED: the product, its type and its services are in\n the declared `compliance_primary_facts` context section of your brief, which also separates the contracted service from\n build-time tooling that is deliberately outside it. State the boundary from that, naming the\n services individually — an application, its environments and its services, never the operator's\n whole organisation. A service not listed there is not part of this application.\n\n## The two routing decisions you emit beside the programme\n\nNaming which documents are required and stopping there leaves the next step with nothing to route by.\nSo this playbook also answers where those documents are published, and what must happen before one\nfaces a real reader.\n\n### `document-publication` — which variants exist at all\n\nOne entry per exact **locale x jurisdiction** combination the application publishes in. The two are an\nINSEPARABLE pair: `en-GB` for `jurisdiction:eu` and `en-GB` for `jurisdiction:gb` are two variants\ncarrying different clauses, and neither implies a third assembled from one of each. Nothing\ndownstream may recombine the axes.\n\nTake the jurisdictions from what the application has DECLARED — its operating regions, its posture —\nnever from where you imagine it might expand. A variant nobody publishes in is a routing claim no\ndocument can honour, and every later release must name a variant declared here.\n\n### `document-release-policy` — which approval lane each requirement takes\n\nOne selection per documentation requirement the authority section lists under **Documentation\nrequirements this application owes**, keyed by that `requirementRef` and `requirementVersion` exactly.\nThose are DERIVED from what the application declares — the programme declares exactly them, and you do\nnot write them — so a selection naming any other requirement is refused:\n\n| lane | means |\n|---|---|\n| `DRAFT_ONLY` | the document may be drafted and retained; nothing may serve it as published |\n| `OPERATOR_ATTESTED` | an accountable operator may release an exact draft with explicit limitations, which the selection must list |\n| `QUALIFIED_REVIEW` | the reviewer-authority route is required before it is served |\n\n**Choose the lane the application can honestly satisfy today, and prefer the strictest only where it\nis true.** `DRAFT_ONLY` is the right answer for a document nobody has reviewed, and it is not a\nfailure state: a drafted document and an unapproved release are both legitimate artifacts an\napplication holds for most of its life.\n\n**None of these lanes blocks drafting or composing a release.** They decide what must be true before\na document faces a REAL READER, which is a later question than the one this journey is answering. A\nlane that stopped the build would be a compliance workflow standing in front of the\napplication-creation mechanism.\n\n## Where this leaves the journey\n\nThe programme you land is the accepted answer for which controls this product commits to. It is what\nan obligation register reads, what a governed document cites when it says the operator has a\nprogramme, and what a later mapping pass binds to external framework identifiers.\n\nIt is accepted the way everything is accepted here: by a commit, which this run does not make. Who\nmakes it is the host's autonomy posture, and the programme's dispositions become a REVIEW only when a\nPERSON commits them. A commit the development companion makes under the YOLO posture is authored as\nthe companion: it accepts the working edit and reviews nothing.\n",
|
|
39
|
+
"skillRefs": [],
|
|
42
40
|
"skillBodyRefs": [],
|
|
43
41
|
"elicitation": {
|
|
44
42
|
"questions": [
|
|
@@ -25,9 +25,7 @@
|
|
|
25
25
|
],
|
|
26
26
|
"method": {
|
|
27
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
|
-
"journey-status"
|
|
30
|
-
],
|
|
28
|
+
"skillRefs": [],
|
|
31
29
|
"skillBodyRefs": [],
|
|
32
30
|
"contextSources": [],
|
|
33
31
|
"draftableDocumentDefinitionRefs": [],
|
|
@@ -198,7 +198,3 @@ evidence, never from recollection:
|
|
|
198
198
|
These are skill FOLDERS installed in the application, named so each piece of work has an
|
|
199
199
|
authoring contract a later coding agent can open. This step has no tools and does not open them;
|
|
200
200
|
what reaches you is this method, your declared inputs, and the brief's own sections.
|
|
201
|
-
|
|
202
|
-
- `journey-status` — read current journey state and
|
|
203
|
-
scope before deriving, and to see the `vision-brief` (and its existing
|
|
204
|
-
compliance constraints) you refine.
|
|
@@ -33,10 +33,8 @@
|
|
|
33
33
|
],
|
|
34
34
|
"stepOutputs": [],
|
|
35
35
|
"method": {
|
|
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\n- `journey-status` — read current journey state and\n scope before deriving, and to see the `vision-brief` (and its existing\n compliance constraints) you refine.\n",
|
|
37
|
-
"skillRefs": [
|
|
38
|
-
"journey-status"
|
|
39
|
-
],
|
|
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": [],
|
|
40
38
|
"skillBodyRefs": [],
|
|
41
39
|
"contextSources": [],
|
|
42
40
|
"draftableDocumentDefinitionRefs": [],
|
|
@@ -26,9 +26,7 @@
|
|
|
26
26
|
],
|
|
27
27
|
"method": {
|
|
28
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
|
-
"journey-status"
|
|
31
|
-
],
|
|
29
|
+
"skillRefs": [],
|
|
32
30
|
"skillBodyRefs": [],
|
|
33
31
|
"contextSources": [],
|
|
34
32
|
"draftableDocumentDefinitionRefs": [],
|
|
@@ -84,9 +84,12 @@ Say which, in the rationale.
|
|
|
84
84
|
|
|
85
85
|
## What the phase gate's verdict re-opens
|
|
86
86
|
|
|
87
|
-
The
|
|
88
|
-
|
|
89
|
-
|
|
87
|
+
The lane declares this table, and the runtime applies it: a GAP on one of the first four
|
|
88
|
+
criteria offers the mapped leaf again, even though it already landed in this run. When a
|
|
89
|
+
leaf you have already seen land is eligible again after the gate, that is this loop-back,
|
|
90
|
+
not churn. Re-run that leaf against the gate's rationale for the faulted criterion, then run
|
|
91
|
+
the gate again. A PASS re-opens nothing, and CONCERN or INDETERMINATE re-open nothing
|
|
92
|
+
either: re-deriving a leaf does not answer advice, and it does not produce evidence.
|
|
90
93
|
|
|
91
94
|
| criterion | re-opens |
|
|
92
95
|
|---|---|
|
|
@@ -94,7 +97,7 @@ lane declares it:
|
|
|
94
97
|
| success-criterion coverage | `top_down.scope-roadmap` |
|
|
95
98
|
| capability completeness | `top_down.capability-map` |
|
|
96
99
|
| positioning / ICP coherence | `top_down.value-proposition` |
|
|
97
|
-
| compliance presence | the compliance lane,
|
|
100
|
+
| compliance presence | the compliance lane, which this lane does not admit — the root re-opens it, from this lane's exported verdict |
|
|
98
101
|
|
|
99
102
|
## What the creator reviews
|
|
100
103
|
|