@wildo-ai/framework-knowledge 1.1.8 → 1.1.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/claude-marketplace/.claude-plugin/marketplace.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +11 -0
- package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +9 -2
- package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +21 -0
- package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +121 -0
- package/dist/claude-marketplace/plugins/wildo/references/expert-personas-and-deliberations.md +26 -7
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +31 -5
- package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +4 -2
- package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +29 -2
- package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +69 -24
- package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +10 -0
- package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +21 -5
- package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +31 -5
- package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +2 -0
- package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +20 -4
- 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 +95 -5
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/index.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +2 -2
- 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 +11 -11
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +29 -22
- 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 +41 -3
- 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 +175 -14
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +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 +3 -3
- 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.js +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +8 -4
- 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 -6
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +4 -2
- 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 +90 -13
- 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 +4 -3
- 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 +4 -3
- 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 +8 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +12 -4
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +12 -3
- 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 +8 -4
- 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 +4 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +2 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -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.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +25 -27
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +91 -43
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +41 -0
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +43 -0
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +200 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +203 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +81 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +93 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +3 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +27 -18
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +11 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +11 -11
- 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 +2 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +3 -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.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +2 -0
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +3 -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.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +5 -2
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -4
- 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 +27 -6
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +32 -12
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -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 +13 -5
- 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 +7 -3
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +71 -2
- 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 +2 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +23 -8
- 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 +7 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +4 -2
- 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 +9 -3
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +3 -3
- 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.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +35 -2
- 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 +41 -17
- 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/method.md +22 -7
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
- package/dist/knowledge/playbooks/bottom_up.build/method.md +17 -15
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +4 -3
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +261 -34
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +42 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +188 -59
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +169 -276
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -2
- package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +8 -1
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.conception/method.md +3 -2
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +11 -3
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +129 -17
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +7 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +28 -6
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +5 -4
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +13 -5
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +50 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +16 -4
- package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +19 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +5 -2
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +7 -3
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +8 -0
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +3 -2
- package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +5 -2
- package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +75 -37
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +35 -38
- package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +145 -0
- package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +57 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +99 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +65 -0
- package/dist/knowledge/playbooks/top_down.brand-naming/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +76 -0
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/method.md +60 -6
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +15 -10
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +10 -9
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +30 -10
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +3 -1
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +4 -1
- package/dist/knowledge/playbooks/top_down.definition/method.md +8 -3
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +6 -4
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +16 -2
- package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +5 -2
- package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +26 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +4 -2
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +11 -1
- package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +84 -9
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +6 -3
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +21 -0
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +8 -2
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +4 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +29 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +58 -17
- package/dist/knowledge/references/brand.name-choice.config.md +144 -0
- package/dist/knowledge/references/brand.name-screening.config.md +308 -0
- package/dist/knowledge/references/build-plan.task-graph.config.md +119 -11
- package/dist/knowledge/references/business-model.pricing-plan.config.md +16 -0
- package/dist/knowledge/references/business-model.snapshot.config.md +64 -0
- package/dist/knowledge/references/business-model.snapshot.validation.md +68 -4
- package/dist/knowledge/references/capability-composition.config.md +67 -4
- package/dist/knowledge/references/companion.market.prompt-renderer.md +11 -6
- package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +44 -0
- package/dist/knowledge/references/example.backend.custom-operation.audit-event.md +81 -0
- package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +258 -0
- package/dist/knowledge/references/example.backend.custom-operation.computed-total.md +153 -0
- package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +107 -0
- package/dist/knowledge/references/example.data-seeding.minimal.md +39 -10
- package/dist/knowledge/references/example.data-seeding.row-reference.md +80 -0
- package/dist/knowledge/references/example.email.template.minimal.md +1 -1
- package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +74 -0
- package/dist/knowledge/references/example.resource.personal-data.free-text-field.md +19 -0
- package/dist/knowledge/references/example.resource.personal-data.person-without-account.md +27 -0
- package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +152 -0
- package/dist/knowledge/references/example.resource.ui-behavior.filter-presets.md +15 -0
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +8 -0
- package/dist/knowledge/references/example.views.app-level.home-definition.md +13 -0
- package/dist/knowledge/references/example.views.chart-definition.shared.md +83 -0
- package/dist/knowledge/references/experience-plan.config.md +60 -7
- package/dist/knowledge/references/market.context-block.builder.md +1 -1
- package/dist/knowledge/references/market.snapshot.validation.md +1 -1
- package/dist/knowledge/references/placement-plan.config.md +43 -0
- package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -2
- package/dist/knowledge/references/requirements.non-functional-requirement.config.md +2 -0
- package/dist/knowledge/references/requirements.references.conventions.md +1 -1
- package/dist/knowledge/references/requirements.snapshot.config.md +57 -1
- package/dist/knowledge/references/requirements.snapshot.validation.md +35 -1
- package/dist/knowledge/references/saas.backend.audit-logs.log-event.md +63 -0
- package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +60 -0
- package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +156 -0
- package/dist/knowledge/references/saas.backend.email.send.md +77 -0
- package/dist/knowledge/references/saas.backend.notifications.operation-email-template-ref.md +60 -0
- package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +7 -1
- package/dist/knowledge/references/saas.data-seeding.computed-entry.md +43 -0
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +14 -2
- package/dist/knowledge/references/saas.data-seeding.row-reference.md +93 -0
- package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +124 -0
- package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +316 -0
- package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +106 -0
- package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +60 -0
- package/dist/knowledge/references/saas.frontend.resource-label-params.md +52 -0
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +47 -18
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -1
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destination-roles.md +25 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +2 -2
- package/dist/knowledge/references/saas.models.audit.trail-config.md +45 -0
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +5 -3
- package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +81 -2
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +26 -0
- package/dist/knowledge/references/saas.models.roles.definition.md +61 -0
- package/dist/knowledge/references/saas.models.roles.organization-defaults.md +97 -0
- package/dist/knowledge/references/saas.public-runtime.contract.md +26 -0
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +10 -0
- package/dist/knowledge/references/saas.website.astro.bridge.md +10 -0
- package/dist/knowledge/references/saas.website.astro.label-loader.md +12 -0
- package/dist/knowledge/references/saas.website.astro.llms-txt-server.md +14 -1
- package/dist/knowledge/references/saas.website.astro.site-context.md +13 -0
- package/dist/knowledge/references/saas.website.blog.bridge.md +4 -0
- package/dist/knowledge/references/saas.website.config.site-context-loader.md +3 -0
- package/dist/knowledge/references/saas.website.factories.define-section.md +4 -0
- package/dist/knowledge/references/saas.website.legal.public-document-links.md +76 -0
- package/dist/knowledge/references/saas.website.page-manifest.schema.md +12 -3
- package/dist/knowledge/references/saas.website.page-sections.component.md +72 -0
- package/dist/knowledge/references/saas.website.root-config.seo.md +2 -1
- package/dist/knowledge/references/saas.website.runtime.context.md +7 -0
- package/dist/knowledge/references/saas.website.sections.definition-schema.md +11 -0
- package/dist/knowledge/references/saas.website.seo.llms-txt-config.md +2 -0
- package/dist/knowledge/references/website-plan.config.md +26 -0
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +13 -0
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +7 -0
- package/dist/knowledge/references/zod.decorators.document-sequence.md +65 -0
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +1 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +21 -0
- package/dist/knowledge/references/zod.factories.bigdecimal.md +1 -0
- package/dist/knowledge/references/zod.factories.code.md +1 -0
- package/dist/knowledge/references/zod.factories.duration.md +1 -0
- package/dist/knowledge/references/zod.factories.money.md +1 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +374 -1
- package/dist/knowledge/registries/playbooks.json +76 -28
- package/dist/knowledge/registries/source-tags.json +1513 -898
- package/dist/knowledge/rules/live-context-door.md +5 -2
- package/dist/knowledge/skills/INDEX.md +5 -2
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +16 -3
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +14 -3
- package/dist/knowledge/skills/application-roles-authoring/SKILL.md +158 -0
- package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +169 -0
- package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +63 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +6 -1
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +256 -9
- package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +42 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +220 -0
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +5 -0
- package/dist/knowledge/skills/brand-name-screening/SKILL.md +178 -0
- package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +466 -0
- package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +87 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +7 -3
- package/dist/knowledge/skills/config-app-shell/SKILL.md +58 -5
- package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +461 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +80 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +28 -6
- package/dist/knowledge/skills/config-navigation/SKILL.md +14 -3
- package/dist/knowledge/skills/config-saas/SKILL.md +56 -15
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +65 -2
- package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +62 -2
- package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +81 -2
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +6 -1
- package/dist/knowledge/skills/configure-billing/SKILL.md +18 -4
- package/dist/knowledge/skills/email-add-template/SKILL.md +28 -6
- package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +1 -1
- package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +128 -0
- package/dist/knowledge/skills/email-add-template/references/framework-operation-email-template-ref-api.md +99 -0
- package/dist/knowledge/skills/engine-component-registration/SKILL.md +6 -1
- package/dist/knowledge/skills/engine-product-definitions/SKILL.md +21 -8
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -2
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +18 -4
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +11 -3
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +2 -1
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +8 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +19 -5
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +10 -2
- package/dist/knowledge/skills/inbound-channels/SKILL.md +2 -2
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +6 -1
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +17 -2
- package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +122 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +11 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +9 -2
- package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +10 -2
- package/dist/knowledge/skills/market-alternatives/SKILL.md +10 -2
- package/dist/knowledge/skills/market-authoring-overview/SKILL.md +10 -2
- package/dist/knowledge/skills/market-category/SKILL.md +21 -7
- package/dist/knowledge/skills/market-channels/SKILL.md +6 -1
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +22 -4
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +12 -2
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +21 -11
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +11 -6
- package/dist/knowledge/skills/market-icp/SKILL.md +10 -2
- package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +6 -1
- package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +6 -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 +14 -3
- package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +6 -1
- package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +10 -2
- package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +6 -1
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -4
- package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +1 -1
- package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +6 -1
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +26 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +7 -1
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +10 -0
- package/dist/knowledge/skills/module-relationships/SKILL.md +37 -8
- package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +4 -2
- package/dist/knowledge/skills/provider-address-lookup/SKILL.md +14 -3
- package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +6 -1
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +14 -3
- package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +10 -2
- package/dist/knowledge/skills/resource-add-field/SKILL.md +10 -2
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +46 -17
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +14 -2
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +26 -0
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +29 -3
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +19 -4
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +5 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +103 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +135 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +26 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +26 -7
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +10 -2
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +46 -17
- package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +2 -2
- package/dist/knowledge/skills/resource-retention-binding/SKILL.md +5 -1
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +15 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +569 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +358 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +8 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +21 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +7 -2
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +13 -0
- package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +153 -0
- package/dist/knowledge/skills/resource-status-lifecycle/references/commercial-documents.md +46 -0
- package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +198 -0
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +30 -4
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +157 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +101 -19
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +202 -39
- package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +67 -0
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +154 -4
- package/dist/knowledge/skills/seeding-authoring/references/seed-row-overlay.md +22 -0
- package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +7 -1
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +43 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +2 -2
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +6 -1
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +10 -0
- package/dist/knowledge/skills/spec-component-update/SKILL.md +10 -2
- package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +2 -2
- package/dist/knowledge/skills/spec-family-update/SKILL.md +71 -66
- package/dist/knowledge/skills/spec-family-update/references/family-spec-routing.md +1 -1
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +30 -10
- package/dist/knowledge/skills/spec-resource-update/references/resource-spec-field-routing.md +28 -0
- package/dist/knowledge/skills/spec-update-after-change/SKILL.md +22 -5
- package/dist/knowledge/skills/views-add-composite-view/SKILL.md +6 -1
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +10 -2
- package/dist/knowledge/skills/views-app-level/SKILL.md +13 -3
- package/dist/knowledge/skills/views-app-level/references/application-home.md +56 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +221 -37
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +22 -5
- package/dist/knowledge/skills/views-execution-authoring/SKILL.md +1 -1
- package/dist/knowledge/skills/website-anonymous-session/SKILL.md +32 -2
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +16 -3
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +4 -0
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +7 -1
- package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +13 -1
- package/dist/knowledge/skills/website-factory-advanced/SKILL.md +14 -2
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +13 -1
- package/dist/knowledge/skills/website-layout-overrides/SKILL.md +6 -1
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +19 -1
- package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +55 -18
- package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +98 -0
- package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +8 -11
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +100 -8
- package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +3 -0
- package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +6 -1
- package/dist/knowledge/skills/website-section-contact/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-cta/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-faq/SKILL.md +21 -1
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +21 -1
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +25 -2
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-hero/SKILL.md +33 -10
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +21 -1
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +27 -2
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +16 -4
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +11 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +16 -1
- package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +2 -1
- package/dist/knowledge/topic-index.json +1590 -292
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "bottom_up.placement-plan",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.4",
|
|
4
4
|
"phase": "bottom_up",
|
|
5
|
-
"intent": "Decide WHERE every settings destination, resource operation and application view sits in the application shell, and WHY. Reads the domain plan (the modules, their resources and what they mean)
|
|
5
|
+
"intent": "Decide WHERE every settings destination, resource operation and application view sits in the application shell, and WHY. Reads the domain plan (the modules, their resources and what they mean), the requirements (which tasks matter), the customer profile (who the customers are, which decides whether an enterprise destination belongs at all) and what the creator stated about the user groups, and produces a PLACEMENT PLAN: for each subject, either a PLACED decision naming one surface (the settings hub rail, the sidebar, the user menu, the command palette) and its address on that surface, or an explicit DECLINED decision with a reason. Both carry a rationale. It also declares the GROUPS that should exist on the grouped surfaces (settings rail categories, sidebar sections) with the product purpose behind each, which is what grounds their generated labels in authored intent instead of filler. This playbook DECIDES placement; it does NOT author configuration — turning a decision into `frontend/src/config/settings-hub.config.ts` and `app-shell.config.ts` is a coding task the build lane dispatches, through the `settings-placement-authoring` skill for the settings rail and the `config-app-shell` skill for the sidebar, command palette and user menu. A sidebar group or a sidebar or palette decision may name the roles it is shown to (`visibleToRoles`), when one audience only opens it. It runs BEFORE build-decompose, which consumes the plan and emits those tasks — the reverse order would be a cycle, since build-decompose is what produces the build plan. It writes no TypeScript, invents no destination refs, and authors no labels. It exists because the alternative is the framework defaulting placement, which is what made an application's settings rail unauthorable: nothing is placed implicitly, so a subject nobody decided about is a visible coverage gap rather than a silent framework default.",
|
|
6
6
|
"preconditions": [
|
|
7
7
|
{
|
|
8
8
|
"kind": "artifact_exists",
|
|
@@ -17,6 +17,16 @@
|
|
|
17
17
|
},
|
|
18
18
|
{
|
|
19
19
|
"family": "requirements"
|
|
20
|
+
},
|
|
21
|
+
{
|
|
22
|
+
"family": "market-snapshot",
|
|
23
|
+
"aspects": [
|
|
24
|
+
"market.icp",
|
|
25
|
+
"market.persona"
|
|
26
|
+
]
|
|
27
|
+
},
|
|
28
|
+
{
|
|
29
|
+
"family": "vision-brief"
|
|
20
30
|
}
|
|
21
31
|
],
|
|
22
32
|
"outputs": [
|
|
@@ -28,7 +38,7 @@
|
|
|
28
38
|
],
|
|
29
39
|
"stepOutputs": [],
|
|
30
40
|
"method": {
|
|
31
|
-
"guidance": "# Placement Plan — Where Each Thing Belongs in the Shell, and Why\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 methodology.** The criteria below are deliberately explicit so\n> they can be tuned against real runs. What is NOT provisional is the shape of the\n> output: a decision per subject, on a named surface, with a rationale.\n\n## Where you are in the journey\n\nYou run in the **bottom-up phase**, after the **domain plan** exists and **before**\nthe build is decomposed. By now the application knows what its modules and resources\nARE; what nobody has decided is **where any of it appears**.\n\nThat order matters and was corrected during authoring. Placing things *after* the\nbuild plan reads natural — you would know every task — but `bottom_up.build-decompose`\nis what PRODUCES the build plan and it consumes this one to emit the placement tasks.\nRequiring its output would be a cycle. It is also the better order on its own merits:\nplacement is a design decision that should INFORM the decomposition, not trail it. You\ndo not need the task graph to know that a `deals` resource will have a list.\n\nThat question used to have no owner. The framework shipped a placed settings rail,\nso an application could not add, remove, reorder or rename a section without the\nframework agreeing — and the application's own config file did not tell you what a\nuser would see. Placement is now the application's, which means somebody has to\ndecide it. That is this playbook.\n\n## What this playbook does\n\nYou produce a **placement plan**: for every subject, one decision per surface.\n\nA **subject** is one of three things:\n\n- an **engine settings destination**, named by its ref from the engine catalog\n (`profile`, `security`, `billing`, `sso`, …) — the engine owns what each MEANS\n (its target, its required roles, its entitlement); it owns nothing about where it\n goes;\n- a **resource operation** — a resource's LIST, its READ, a custom verb;\n- an **application view** — composite, chart, execution, full-custom.\n\nA **surface** is one of four:\n\n| surface | grouped by | authoring home |\n|---|---|---|\n| `SETTINGS_HUB` | a rail **category** | `frontend/src/config/settings-hub.config.ts` |\n| `SIDEBAR` | a sidebar **section** | `appShellConfig[SIDEBAR].contentSections` |\n| `USER_MENU` | flat | the user dropdown's settings entries |\n| `COMMAND_MENU` | flat | the command palette |\n\nA subject may legitimately be placed on **several** surfaces — billing is a settings\nrail section AND answers to the command palette. One decision per (subject, surface);\ntwo placements of one subject on ONE surface is a contradiction and the validator\nrefuses it.\n\n**Not every surface can carry every kind of subject**, and the validator refuses a\nplacement that no configuration could realise (`SUBJECT_NOT_EXPRESSIBLE_ON_SURFACE`,\na hard floor):\n\n| surface | engine destination | resource operation | application view |\n|---|---|---|---|\n| `SETTINGS_HUB` | yes | yes — as a settings section the application declares for it | **no** |\n| `USER_MENU` | yes | yes — the same application settings section, opened from the dropdown | **no** |\n| `SIDEBAR` | yes | yes | yes |\n| `COMMAND_MENU` | yes | yes | yes |\n\nThe settings rail and the user dropdown hold settings SECTIONS. A section can show a\nresource operation (a list of the team's members, say), a framework panel, or a\ncomponent the application registers; it cannot show an application view. A view\nthat people reach from settings belongs on the sidebar or the palette.\n\n## Decline explicitly; never omit\n\nEvery decision is `PLACED` or `DECLINED`, and **both require a rationale**.\n\nThis is the rule most worth getting right. A subject recorded as `DECLINED` is a\ndecision a later reader can disagree with. A subject simply missing from the plan is\na **coverage gap** — nobody looked. If those two were the same thing, \"we considered\nthe audit log and this app has no compliance audience\" would be indistinguishable\nfrom forgetting the audit log existed.\n\nSo: if a destination should not appear anywhere in this application, say so, and say\nwhy.\n\n## The criteria, in the order you apply them\n\n1. **Scope correctness.** A thing that acts on the whole organization does not sit\n among a person's own preferences, and the reverse. This is first because it is\n the only criterion that is objectively *wrong* rather than debatable.\n2. **Findability.** Would the user who wants this look here FIRST — unprompted?\n Not \"would they accept it once shown\". Those are different tests and only the\n first one predicts behaviour.\n3. **Grouping coherence.** Everything in a group answers one question a user\n actually asks. A group that needs \"and other things\" in its name is two groups.\n4. **Convention fit.** Users arrive with expectations already formed by comparable\n products. A novel arrangement must EARN the cost of surprising them.\n5. **Depth discipline.** One more level of nesting must buy more than it costs. A\n section reachable only after three guesses is not placed, it is hidden.\n\nReject placements justified by implementation convenience (\"it renders there\nalready\"), by the shape of the data model rather than the user's task, or by symmetry\nfor its own sake. Surfacing something everywhere is a **cost**, not thoroughness.\n\n## Groups carry a purpose, and the purpose is load-bearing\n\nWhen you declare a group, state its `purpose` in product terms. It is not decoration:\nit is what grounds the generated `settings_hub.categories.<ref>.label` and\n`sidebar_sections.<ref>.title` labels in authored intent. Without it a model invents\nfiller from the ref alone — which is exactly how a sidebar section came to be\ndescribed as \"various tools and utilities\".\n\n## Placing an operator surface commits the application to an AUDIENCE — say which\n\nSome subjects exist for whoever OPERATES the product rather than for the people who use it:\napplication-wide single sign-on, the application's own API keys and OAuth clients, the\nentitlement state of every tenant, the plans and prices on sale, the application-wide audit\ntrail. The framework keeps them in a separate preset scope from the end-user surfaces, and it\nkeeps them separate ON PURPOSE — an application may legitimately never render them.\n\n**So placing one is a decision about what this application IS, and the plan must state it.**\nTwo answers, both correct:\n\n- **ONE application.** Operators and users share a frontend and are told apart by their roles.\n Place the operator subjects in their own group — an `administration` category beside the\n account and organization ones — and record that this application composes BOTH preset scopes.\n- **TWO applications.** A separate operator frontend. Decline the operator subjects here, with\n that as the rationale, and they belong to the other application's plan.\n\nState the answer in the plan even when it is the obvious one, because the failure it prevents is\nsilent: an application that places operator subjects while composing only the end-user scope gets\nrail entries that OPEN AND RENDER NOTHING. An operation no composed preset surfaces is\ncallable-from-code with no interface, so the section is not missing and does not error — it is\nblank, and it reads as a slow load or a broken backend rather than as an application that was\nassembled without an audience. Seventeen sections were in exactly that state on the dogfood\napplication before this was written down.\n\nYou are not choosing the composition here — that is a coding task the build lane dispatches\nthrough `settings-placement-authoring`. You are stating WHICH audience the arrangement assumes,\nso the task that follows has something to implement rather than a default to guess.\n\n## What you do NOT do\n\n- **You do not author configuration.** Turning a decision into\n `settings-hub.config.ts` or `app-shell.config.ts` is a coding task the build lane\n dispatches through the `settings-placement-authoring` skill. If you catch yourself\n writing a config key, a file path or a label string, stop.\n- **You do not invent destination refs.** The workspace-truth section lists every engine\n settings destination under **\"Settings destinations the engine ships\"**, with what each\n one shows and its role gating. That list is the whole universe: a ref outside it is an\n `UNKNOWN_SUBJECT` and the validator REFUSES the plan — a hard floor, not a warning. Rule\n on all of them where you can; a destination your plan says nothing about is reported\n undecided.\n- **You do not decide what a destination MEANS.** Its target, roles and entitlement\n are the engine's. You decide only where it sits.\n- **You do not re-open the build plan.** What is being built is settled.\n\n## Verification\n\n- Every subject the workspace offers is either PLACED or DECLINED — nothing omitted.\n- No subject placed twice on one surface.\n- No application view placed on the settings rail or the user dropdown.\n- Every grouped placement names a group this plan declares, for that same surface.\n- Every group has something in it.\n- Every decision, both arms, carries a rationale that would satisfy a reader who\n disagrees with it.\n- The plan states which AUDIENCE it assumes — one application or two — whenever it places or\n declines an operator subject.\n\n## WHO decides — a panel, not you alone and not the creator\n\n**The creator does not choose placement.** This playbook convenes an expert panel and\ntakes its winner.\n\nConcretely, on every run: three candidate arrangements are generated independently\nagainst this brief, each schema-valid before anyone sees it and each told to take a\ngenuinely different position; the **information-architect** derives the rubric (it\nowns the domain); it and the **design-system-guardian** review every candidate; the\nguardian coordinates, shortlists, and synthesises a winner. What lands is that winner.\n\nTwo consequences for how you write:\n\n- **Take a position and commit to it.** You are one candidate among three, and the\n panel cannot compare three hedged arrangements. State what your arrangement makes\n WORSE — an arrangement with no cost has not been thought about, and the reviewers\n are instructed to notice.\n- **The rationale on each decision is the durable part.** It is what a creator asking\n \"why is Billing under Organization?\" reads, and it is the only trace of the argument\n once the winner has landed.\n\n**Fail-closed on charters.** Every panel role needs a committed charter, and the\ncompanion indexes agents at startup — a charter accepted after boot has no agent until\na restart, and the error says exactly that. The run does NOT quietly degrade to a\nsingle generation: an artifact carrying a panel's authority over a decision no panel\nsaw is the worst outcome available here, so fewer than two usable candidates returns\nto the ordinary retry instead.\n\n## And when the placement is wrong\n\nTwo different things can change, and conflating them is how a plan starts lying.\n\n**The config file** — `settings-hub.config.ts`, `app-shell.config.ts` — is what actually\nrenders. A creator who disagrees edits it directly. That works today, needs no companion,\nand is a git commit, which is the accepted state.\n\n**The plan** is the decision record, and it is what a later reader consults to ask why.\nIt can be changed two ways:\n\n- **Re-run this playbook.** The panel deliberates again and the landing REPLACES the\n existing file. Nothing refuses it; that is the design.\n- **Edit the landed plan.** It is an application-owned source like any other.\n\nEither way, a decision that no longer reflects the panel must say so. Set its `origin`\nto `REVISED` and record what the panel had decided in `supersedes.rationale`. Both are\nrequired together — the schema refuses a `REVISED` decision with nothing superseded, and\nrefuses a `DELIBERATED` one that supersedes something, because no panel run produces\neither shape.\n\n**Why the artifact carries this when git already records the change.** Git knows who\nchanged the line, when, and with what message, and that is not being duplicated here. What\ngit cannot tell someone READING the file — in an editor, asking \"why is Billing under\nAccount?\" — is that this particular decision is no longer the panel's. Without it, the\n`rationale` field goes on asserting panel reasoning for a decision the panel never took,\nand there is no way to notice.\n\nDo not paraphrase the panel's rationale into the new one. A `supersedes.rationale` that\nrepeats the decision's own text word for word satisfies the schema and tells a reader\nnothing; the validator reports it as an authoring warning.\n",
|
|
41
|
+
"guidance": "# Placement Plan — Where Each Thing Belongs in the Shell, and Why\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 methodology.** The criteria below are deliberately explicit so\n> they can be tuned against real runs. What is NOT provisional is the shape of the\n> output: a decision per subject, on a named surface, with a rationale.\n\n## Where you are in the journey\n\nYou run in the **bottom-up phase**, after the **domain plan** exists and **before**\nthe build is decomposed. By now the application knows what its modules and resources\nARE; what nobody has decided is **where any of it appears**.\n\nThat order matters and was corrected during authoring. Placing things *after* the\nbuild plan reads natural — you would know every task — but `bottom_up.build-decompose`\nis what PRODUCES the build plan and it consumes this one to emit the placement tasks.\nRequiring its output would be a cycle. It is also the better order on its own merits:\nplacement is a design decision that should INFORM the decomposition, not trail it. You\ndo not need the task graph to know that a `deals` resource will have a list.\n\nThat question used to have no owner. The framework shipped a placed settings rail,\nso an application could not add, remove, reorder or rename a section without the\nframework agreeing — and the application's own config file did not tell you what a\nuser would see. Placement is now the application's, which means somebody has to\ndecide it. That is this playbook.\n\n## What this playbook does\n\nYou produce a **placement plan**: for every subject, one decision per surface.\n\nA **subject** is one of three things:\n\n- an **engine settings destination**, named by its ref from the engine catalog\n (`profile`, `security`, `billing`, `sso`, …) — the engine owns what each MEANS\n (its target, its required roles, its entitlement); it owns nothing about where it\n goes;\n- a **resource operation** — a resource's LIST, its READ, a custom verb;\n- an **application view** — composite, chart, execution, full-custom.\n\nA **surface** is one of four:\n\n| surface | grouped by | authoring home |\n|---|---|---|\n| `SETTINGS_HUB` | a rail **category** | `frontend/src/config/settings-hub.config.ts` |\n| `SIDEBAR` | a sidebar **section** | `appShellConfig[SIDEBAR].contentSections` |\n| `USER_MENU` | flat | the user dropdown's settings entries |\n| `COMMAND_MENU` | flat | the command palette |\n\nA subject may legitimately be placed on **several** surfaces — billing is a settings\nrail section AND answers to the command palette. One decision per (subject, surface);\ntwo placements of one subject on ONE surface is a contradiction and the validator\nrefuses it.\n\n**Not every surface can carry every kind of subject**, and the validator refuses a\nplacement that no configuration could realise (`SUBJECT_NOT_EXPRESSIBLE_ON_SURFACE`,\na hard floor):\n\n| surface | engine destination | resource operation | application view |\n|---|---|---|---|\n| `SETTINGS_HUB` | yes | yes — as a settings section the application declares for it | **no** |\n| `USER_MENU` | yes | yes — the same application settings section, opened from the dropdown | **no** |\n| `SIDEBAR` | yes | yes | yes |\n| `COMMAND_MENU` | yes | yes | yes |\n\nThe settings rail and the user dropdown hold settings SECTIONS. A section can show a\nresource operation (a list of the team's members, say), a framework panel, or a\ncomponent the application registers; it cannot show an application view. A view\nthat people reach from settings belongs on the sidebar or the palette.\n\n## Decline explicitly; never omit\n\nEvery decision is `PLACED` or `DECLINED`, and **both require a rationale**.\n\nThis is the rule most worth getting right. A subject recorded as `DECLINED` is a\ndecision a later reader can disagree with. A subject simply missing from the plan is\na **coverage gap** — nobody looked. If those two were the same thing, \"we considered\nthe audit log and this app has no compliance audience\" would be indistinguishable\nfrom forgetting the audit log existed.\n\nSo: if a destination should not appear anywhere in this application, say so, and say\nwhy.\n\n## First: does this application need it at all? (the fit test)\n\nBefore WHERE comes WHETHER. Every engine settings destination exists in the framework; that is not\na reason to show it. A destination is placed only when something this application declared calls\nfor it:\n\n- **a requirement** that needs it (single sign-on because a requirement says customers sign in with\n their company identity);\n- **an attribute of the customer profile** in your `market-snapshot` input (the ICPs and personas:\n company size, the tools they already run, their technical staff); or\n- **a capability the application enables** (billing settings because billing is on). What is on is\n not yours to guess: the declared `application_enabled_surface` context section of your brief lists the enabled engine\n capabilities, the billing declaration and each user type's sign-in methods, read from the\n configuration. A capability it does not list is off; one it marks UNREADABLE is unknown, and you\n say so rather than treating it as off. A destination whose capability is off serves nothing yet:\n offer it only when the customer evidence asks for it, and say its capability must be switched on.\n\nOtherwise it is DECLINED, with the profile reason. One earlier run, for a 1–20 person trade firm,\ndeclined single sign-on because such a firm \"is not assumed to operate an enterprise identity\nprovider\". Another, from the same inputs, placed SSO, SCIM, SIEM export, webhooks and legal holds\nbecause \"an admin would look here\". Only the first answered the question that comes first.\n\nThe test cuts both ways. For a 2,000-person insurer whose personas name an identity team and whose\nrequirements say staff sign in with their company account, declining single sign-on would be the\nerror: there the profile and a requirement both call for it, and it is placed, with both cited. Fit\nis read from THIS application's evidence, never from a habit of declining enterprise features.\n\n**Enterprise destinations cite their evidence in the rationale.** Single sign-on, directory sync\n(SCIM), security-event export (SIEM), webhooks, legal holds, API clients and data residency are\nplaced only with the requirement, profile attribute or capability named in the rationale. \"An admin\nwould look here\" is findability, not fit; it answers a question you have not earned yet.\n\nRead who uses the product from what the creator stated (the declared `creator_stated_facts` context section of your brief):\nthe user groups and the devices they use. A field worker on a phone and an office manager at a desk\nwant different things first, and the sidebar's order should serve the group that opens it most.\n\n**When a section or an entry is for one audience only, say so with `visibleToRoles`.** A sidebar group and\na sidebar or command-menu decision may carry `visibleToRoles`: the role keys that see it (a field\ntechnician does not see the office's \"Invoices\" section). Use it only when the creator's user groups\nreally differ in what they open, and name the application's own roles, or core ones like `ORG_ADMIN`.\nA custom role counts only as itself, so list every role that should see it. Absent means everyone,\nand that is the right answer for most groups. It is refused on the settings rail and the user menu,\nwhose destinations carry their own role gating.\n\nHiding is not access control: the person who cannot see \"Invoices\" can still be allowed to open it.\nIf the field technician must not read invoices, that is a role decision on the operation, not a\nplacement, and an entry for an operation a viewer cannot perform is hidden from them already. So\n`visibleToRoles` is only for narrowing further: an operation everyone may use that only one group\nneeds in its navigation.\n\n## The criteria, in the order you apply them\n\n1. **Scope correctness.** A thing that acts on the whole organization does not sit\n among a person's own preferences, and the reverse. This is first because it is\n the only criterion that is objectively *wrong* rather than debatable.\n2. **Findability.** Would the user who wants this look here FIRST — unprompted?\n Not \"would they accept it once shown\". Those are different tests and only the\n first one predicts behaviour.\n3. **Grouping coherence.** Everything in a group answers one question a user\n actually asks. A group that needs \"and other things\" in its name is two groups.\n4. **Convention fit.** Users arrive with expectations already formed by comparable\n products. A novel arrangement must EARN the cost of surprising them.\n5. **Depth discipline.** One more level of nesting must buy more than it costs. A\n section reachable only after three guesses is not placed, it is hidden.\n\nReject placements justified by implementation convenience (\"it renders there\nalready\"), by the shape of the data model rather than the user's task, or by symmetry\nfor its own sake. Surfacing something everywhere is a **cost**, not thoroughness.\n\n## Groups carry a purpose, and the purpose is load-bearing\n\nWhen you declare a group, state its `purpose` in product terms. It is not decoration:\nit is what grounds the generated `settings_hub.categories.<ref>.label` and\n`sidebar_sections.<ref>.title` labels in authored intent. Without it a model invents\nfiller from the ref alone — which is exactly how a sidebar section came to be\ndescribed as \"various tools and utilities\".\n\n## Placing an operator surface commits the application to an AUDIENCE — say which\n\nSome subjects exist for whoever OPERATES the product rather than for the people who use it:\napplication-wide single sign-on, the application's own API keys and OAuth clients, the\nentitlement state of every tenant, the plans and prices on sale, the application-wide audit\ntrail. The framework keeps them in a separate preset scope from the end-user surfaces, and it\nkeeps them separate ON PURPOSE — an application may legitimately never render them.\n\n**So placing one is a decision about what this application IS, and the plan must state it.**\nTwo answers, both correct:\n\n- **ONE application.** Operators and users share a frontend and are told apart by their roles.\n Place the operator subjects in their own group — an `administration` category beside the\n account and organization ones — and record that this application composes BOTH preset scopes.\n- **TWO applications.** A separate operator frontend. Decline the operator subjects here, with\n that as the rationale, and they belong to the other application's plan.\n\nState the answer in the plan even when it is the obvious one, because the failure it prevents is\nsilent: an application that places operator subjects while composing only the end-user scope gets\nrail entries that OPEN AND RENDER NOTHING. An operation no composed preset surfaces is\ncallable-from-code with no interface, so the section is not missing and does not error — it is\nblank, and it reads as a slow load or a broken backend rather than as an application that was\nassembled without an audience. Seventeen sections were in exactly that state on the dogfood\napplication before this was written down.\n\nYou are not choosing the composition here — that is a coding task the build lane dispatches\nthrough `settings-placement-authoring`. You are stating WHICH audience the arrangement assumes,\nso the task that follows has something to implement rather than a default to guess.\n\n## What you do NOT do\n\n- **You do not author configuration.** Turning a decision into\n `settings-hub.config.ts` or `app-shell.config.ts` is a coding task the build lane\n dispatches through the `settings-placement-authoring` skill. If you catch yourself\n writing a config key, a file path or a label string, stop.\n- **You do not invent destination refs.** The workspace-truth section lists every engine\n settings destination under **\"Settings destinations the engine ships\"**, with what each\n one shows and its role gating. That list is the whole universe: a ref outside it is an\n `UNKNOWN_SUBJECT` and the validator REFUSES the plan — a hard floor, not a warning. Rule\n on all of them where you can; a destination your plan says nothing about is reported\n undecided.\n- **You do not decide what a destination MEANS.** Its target, roles and entitlement\n are the engine's. You decide only where it sits.\n- **You do not re-open the build plan.** What is being built is settled.\n\n## Verification\n\n- Every subject the workspace offers is either PLACED or DECLINED — nothing omitted.\n- No subject placed twice on one surface.\n- No application view placed on the settings rail or the user dropdown.\n- Every grouped placement names a group this plan declares, for that same surface.\n- Every group has something in it.\n- Every decision, both arms, carries a rationale that would satisfy a reader who\n disagrees with it.\n- The plan states which AUDIENCE it assumes — one application or two — whenever it places or\n declines an operator subject.\n\n## WHO decides — a panel, not you alone and not the creator\n\n**The creator does not choose placement.** This playbook convenes an expert panel and\ntakes its winner.\n\nConcretely, on every run: three candidate arrangements are generated independently\nagainst this brief, each schema-valid before anyone sees it and each told to take a\ngenuinely different position; the **information-architect** derives the rubric (it\nowns the domain); it and the **design-system-guardian** review every candidate; the\nguardian coordinates, shortlists, and synthesises a winner. What lands is that winner.\n\nTwo consequences for how you write:\n\n- **Take a position and commit to it.** You are one candidate among three, and the\n panel cannot compare three hedged arrangements. State what your arrangement makes\n WORSE — an arrangement with no cost has not been thought about, and the reviewers\n are instructed to notice.\n- **The rationale on each decision is the durable part.** It is what a creator asking\n \"why is Billing under Organization?\" reads, and it is the only trace of the argument\n once the winner has landed.\n\n**Fail-closed on charters.** Every panel role needs a committed charter, and the\ncompanion indexes agents at startup — a charter accepted after boot has no agent until\na restart, and the error says exactly that. The run does NOT quietly degrade to a\nsingle generation: an artifact carrying a panel's authority over a decision no panel\nsaw is the worst outcome available here, so fewer than two usable candidates returns\nto the ordinary retry instead.\n\n## And when the placement is wrong\n\nTwo different things can change, and conflating them is how a plan starts lying.\n\n**The config file** — `settings-hub.config.ts`, `app-shell.config.ts` — is what actually\nrenders. A creator who disagrees edits it directly. That works today, needs no companion,\nand is a git commit, which is the accepted state.\n\n**The plan** is the decision record, and it is what a later reader consults to ask why.\nIt can be changed two ways:\n\n- **Re-run this playbook.** The panel deliberates again and the landing REPLACES the\n existing file. Nothing refuses it; that is the design.\n- **Edit the landed plan.** It is an application-owned source like any other.\n\nEither way, a decision that no longer reflects the panel must say so. Set its `origin`\nto `REVISED` and record what the panel had decided in `supersedes.rationale`. Both are\nrequired together — the schema refuses a `REVISED` decision with nothing superseded, and\nrefuses a `DELIBERATED` one that supersedes something, because no panel run produces\neither shape.\n\n**Why the artifact carries this when git already records the change.** Git knows who\nchanged the line, when, and with what message, and that is not being duplicated here. What\ngit cannot tell someone READING the file — in an editor, asking \"why is Billing under\nAccount?\" — is that this particular decision is no longer the panel's. Without it, the\n`rationale` field goes on asserting panel reasoning for a decision the panel never took,\nand there is no way to notice.\n\nDo not paraphrase the panel's rationale into the new one. A `supersedes.rationale` that\nrepeats the decision's own text word for word satisfies the schema and tells a reader\nnothing; the validator reports it as an authoring warning.\n",
|
|
32
42
|
"skillRefs": [
|
|
33
43
|
"settings-placement-authoring",
|
|
34
44
|
"config-app-shell",
|
|
@@ -36,7 +46,9 @@
|
|
|
36
46
|
],
|
|
37
47
|
"skillBodyRefs": [],
|
|
38
48
|
"contextSources": [
|
|
39
|
-
"workspace_truth"
|
|
49
|
+
"workspace_truth",
|
|
50
|
+
"creator_stated_facts",
|
|
51
|
+
"application_enabled_surface"
|
|
40
52
|
],
|
|
41
53
|
"draftableDocumentDefinitionRefs": [],
|
|
42
54
|
"suspendsForClarification": false,
|
|
@@ -73,6 +73,23 @@ objection, job, pain, ICP or tone refs, exactly as the snapshot authored them. T
|
|
|
73
73
|
claim checkable: a reader opens the snapshot and finds the entry. A section that draws on nothing is
|
|
74
74
|
a section somebody invented, and the validator reports a page where no section names anything.
|
|
75
75
|
|
|
76
|
+
**A section that says what the product DOES names the requirement behind it** (`backedByRequirementRefs`).
|
|
77
|
+
A market benefit says what a buyer wants; it does not say the product delivers it. An earlier site
|
|
78
|
+
promised "country workflow guidance with its limits stated", drawn from a benefit, while the product
|
|
79
|
+
shipped an empty page for an administrator to write guidance into.
|
|
80
|
+
|
|
81
|
+
- Every `FEATURE_DETAIL` and `FEATURE_BENEFIT_SUMMARY` section cites the requirements (functional, or
|
|
82
|
+
non-functional such as working on a phone in the field), by their refs in your `requirements` input,
|
|
83
|
+
that commit the product to what it describes. The validator reports one that cites none.
|
|
84
|
+
- Any other section (a hero, an FAQ, a pricing table) may cite requirements too, and should when its
|
|
85
|
+
copy will say what the product does. A section that cites none describes no capability as available.
|
|
86
|
+
- A citation is necessary, not sufficient. When the section is built, its author is told where each
|
|
87
|
+
cited requirement stands: delivered, still being built, reported unmet by the run that built it, or
|
|
88
|
+
only on a later roadmap phase. Only what is delivered is written as available; the rest is written as
|
|
89
|
+
planned. So cite what the section is ABOUT, and do not drop a requirement because it is not built yet.
|
|
90
|
+
- A benefit no requirement backs is not presented as a capability: leave it out, or give it a section
|
|
91
|
+
whose purpose says it is planned.
|
|
92
|
+
|
|
76
93
|
Lead with fit. The brief carries the computed fit matrix beside each benefit's authored Kano
|
|
77
94
|
category; a page for an ICP argues the benefits that score for THAT ICP first, rather than the ones
|
|
78
95
|
the model finds most interesting.
|
|
@@ -92,6 +109,8 @@ do not renumber.
|
|
|
92
109
|
## Verification
|
|
93
110
|
|
|
94
111
|
- Every `drawsOnRefs` entry names an entry that exists in the market snapshot.
|
|
112
|
+
- Every `FEATURE_DETAIL` and `FEATURE_BENEFIT_SUMMARY` section names at least one `backedByRequirementRefs`
|
|
113
|
+
entry, and each names a requirement in the requirements.
|
|
95
114
|
- Every page opens on a `HERO`, and exactly one page reads as the landing page.
|
|
96
115
|
- `rg -n "sectionRef" specifications/src/website-plan/index.ts | wc -l` — the number of website
|
|
97
116
|
section tasks the build lane will emit.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "bottom_up.website-plan",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.1",
|
|
4
4
|
"phase": "bottom_up",
|
|
5
5
|
"intent": "Website plan — decide WHAT THE MARKETING WEBSITE SAYS for this application: which pages it has, what each page is for and who it is written for, and the sections that carry each page's argument in reading order, each drawing on the market entries the top-down lane authored (benefits, proofs, objections, jobs, pains, ICPs, tones of voice). Runs only once the capability composition decides the website is NEEDED (a declined website is never planned, and a plan landed before a later decline is set aside). A section's KIND (hero, benefits summary, benefit in detail, pricing, proof, objections answered, call to action, closing call to action, contact) names the shipped `website-section-*` skill that authors it, so the build lane can bind each emitted task to its skill without a model naming folders. Produces the plan; `bottom_up.build-decompose` turns it into the page and section tasks a coding agent runs, and the `add-website` composition scenario is what creates the `website/` workspace they write in.",
|
|
6
6
|
"preconditions": [
|
|
@@ -42,6 +42,9 @@
|
|
|
42
42
|
{
|
|
43
43
|
"family": "vision-brief"
|
|
44
44
|
},
|
|
45
|
+
{
|
|
46
|
+
"family": "requirements"
|
|
47
|
+
},
|
|
45
48
|
{
|
|
46
49
|
"family": "website-plan"
|
|
47
50
|
}
|
|
@@ -55,7 +58,7 @@
|
|
|
55
58
|
],
|
|
56
59
|
"stepOutputs": [],
|
|
57
60
|
"method": {
|
|
58
|
-
"guidance": "# Website Plan — What the Marketing Site Says\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## Where you are in the journey\n\nThe top-down lane has produced a market snapshot — ICPs, jobs, pains, gains, benefits with their\nweighting, positioning per ICP, tones of voice, proofs and objections — and a brand. The capability\ncomposition has decided whether this application has a marketing website. You decide **what that\nsite says**: its pages, and the sections that carry each page's argument.\n\nYou do not write the site. `bottom_up.build-decompose` turns each page and each section into a\nbuild task, and a coding agent authors it against the shipped `website-*` skills. The `website/`\nworkspace itself is composed by the `add-website` scenario, which the foundation applies from the\nsame capability composition you read here.\n\n## Step 1 — Read the capability composition FIRST\n\nFind the `add-website` decision. This playbook runs only once the composition decides it is\n**NEEDED**: its eligibility is gated on that decision, so a declined website is never planned, and a\nplan landed while it was needed is set aside for every reader if the composition later declines it.\n\n- **Needed** (the normal case): `disposition: PLANNED`, and continue.\n- **Declined** in the record you are given (it changed after you were started): land a plan with\n `disposition: NOT_APPLICABLE`, no pages, and a `rationale` naming what the composition said. Do not\n plan a site the application will never compose — the pages would become tasks with nowhere to write.\n\n## Step 2 — Decide the pages, from what the product actually declares\n\nA page exists because something the application declared needs a place to be said. Derive first,\nand invent nothing:\n\n| page | exists when |\n|---|---|\n| the landing page | always — it is the origin every canonical URL derives from |\n| a pricing page | the business model declares pricing plans |\n| a features page | the market snapshot carries benefits worth arguing one at a time |\n| a contact page | the product's audience buys through a conversation (an inbound channel, a legal-entity ICP) |\n\nEach page names the ICPs it is **written for** and the tone of voice it speaks in, both by their\nmarket-snapshot refs. A page written for everybody is written for nobody: the positioning the\nmarket pass produced is per ICP, and a page that names none cannot use it.\n\n## Step 3 — Compose each page's sections, in reading order\n\nOrder is the plan's substance. A page opens on a **HERO** — the promise, before any detail — and\nargues from there. The section kinds are closed, and each one names the skill that authors it:\n\n| kind | what it does |\n|---|---|\n| `HERO` | the opening promise: headline, sub-headline, primary call to action |\n| `FEATURE_BENEFIT_SUMMARY` | the benefits in one line each, for a reader who will not read the detail |\n| `FEATURE_DETAIL` | one benefit argued: the job it advances, the pain it relieves, what the product does |\n| `PRICING` | the plans, as the business model declares them |\n| `SOCIAL_PROOF` | the proofs the market pass authored |\n| `FAQ` | the objections, answered |\n| `CTA` | a call to action inside the page's flow |\n| `FOOTER_CTA` | the closing call to action |\n| `CONTACT` | a way to reach a human |\n\n**Every section names the market entries it draws on** (`drawsOnRefs`) — the benefit, proof,\nobjection, job, pain, ICP or tone refs, exactly as the snapshot authored them. That is what makes a\nclaim checkable: a reader opens the snapshot and finds the entry. A section that draws on nothing is\na section somebody invented, and the validator reports a page where no section names anything.\n\nLead with fit. The brief carries the computed fit matrix beside each benefit's authored Kano\ncategory; a page for an ICP argues the benefits that score for THAT ICP first, rather than the ones\nthe model finds most interesting.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every page ref that still has a reason to exist — build tasks\nname them, and a ref that moves orphans the task that produced its page. Add, sharpen and reorder;\ndo not renumber.\n\n## What you emit\n\n- The **website plan** at `specifications/src/website-plan/index.ts` — a disposition with its\n rationale, and the pages in navigation order, each with its purpose, audience, tone and ordered\n sections.\n\n## Verification\n\n- Every `drawsOnRefs` entry names an entry that exists in the market snapshot.\n- Every page opens on a `HERO`, and exactly one page reads as the landing page.\n- `rg -n \"sectionRef\" specifications/src/website-plan/index.ts | wc -l` — the number of website\n section tasks the build lane will emit.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem: naming a path here would be an instruction answered from\nrecollection (#1435). So each skill is named by its REF, and only `website-page-authoring` reaches\nthis step as a BODY (`method.skillBodyRefs`) — it is the one contract the plan must not contradict,\nbecause it says what a page IS in this engine: a manifest, a route adapter, a sections file and a\nlabel pack that fails the build closed on a missing key. A page planned against anything else is a\npage the build lane cannot author.\n\nThe others below are the contracts the CODING AGENT opens when it builds each task, listed so a\nreader knows the plan's decisions land somewhere:\n\n- `website-navigation-authoring` — how pages reach each other, which bounds how many top-level pages are worth planning.\n- `website-seo-aeo-geo` — what a page owes a search engine and an answer engine.\n- `website-label-pack` — every string a section renders is a label key, and the build fails closed on a missing one.\n- `website-marketing-metadata-extension` — the metadata a page carries beyond its sections.\n- `website-section-*` — one per section KIND, bound to the emitted task by `WEBSITE_SECTION_SKILL_REF`.\n- `market-positioning-authoring`, `market-tone-of-voice`, `market-proof-and-objection` — the market\n vocabularies a section draws on, which arrive here as the market snapshot itself rather than as prose.\n",
|
|
61
|
+
"guidance": "# Website Plan — What the Marketing Site Says\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## Where you are in the journey\n\nThe top-down lane has produced a market snapshot — ICPs, jobs, pains, gains, benefits with their\nweighting, positioning per ICP, tones of voice, proofs and objections — and a brand. The capability\ncomposition has decided whether this application has a marketing website. You decide **what that\nsite says**: its pages, and the sections that carry each page's argument.\n\nYou do not write the site. `bottom_up.build-decompose` turns each page and each section into a\nbuild task, and a coding agent authors it against the shipped `website-*` skills. The `website/`\nworkspace itself is composed by the `add-website` scenario, which the foundation applies from the\nsame capability composition you read here.\n\n## Step 1 — Read the capability composition FIRST\n\nFind the `add-website` decision. This playbook runs only once the composition decides it is\n**NEEDED**: its eligibility is gated on that decision, so a declined website is never planned, and a\nplan landed while it was needed is set aside for every reader if the composition later declines it.\n\n- **Needed** (the normal case): `disposition: PLANNED`, and continue.\n- **Declined** in the record you are given (it changed after you were started): land a plan with\n `disposition: NOT_APPLICABLE`, no pages, and a `rationale` naming what the composition said. Do not\n plan a site the application will never compose — the pages would become tasks with nowhere to write.\n\n## Step 2 — Decide the pages, from what the product actually declares\n\nA page exists because something the application declared needs a place to be said. Derive first,\nand invent nothing:\n\n| page | exists when |\n|---|---|\n| the landing page | always — it is the origin every canonical URL derives from |\n| a pricing page | the business model declares pricing plans |\n| a features page | the market snapshot carries benefits worth arguing one at a time |\n| a contact page | the product's audience buys through a conversation (an inbound channel, a legal-entity ICP) |\n\nEach page names the ICPs it is **written for** and the tone of voice it speaks in, both by their\nmarket-snapshot refs. A page written for everybody is written for nobody: the positioning the\nmarket pass produced is per ICP, and a page that names none cannot use it.\n\n## Step 3 — Compose each page's sections, in reading order\n\nOrder is the plan's substance. A page opens on a **HERO** — the promise, before any detail — and\nargues from there. The section kinds are closed, and each one names the skill that authors it:\n\n| kind | what it does |\n|---|---|\n| `HERO` | the opening promise: headline, sub-headline, primary call to action |\n| `FEATURE_BENEFIT_SUMMARY` | the benefits in one line each, for a reader who will not read the detail |\n| `FEATURE_DETAIL` | one benefit argued: the job it advances, the pain it relieves, what the product does |\n| `PRICING` | the plans, as the business model declares them |\n| `SOCIAL_PROOF` | the proofs the market pass authored |\n| `FAQ` | the objections, answered |\n| `CTA` | a call to action inside the page's flow |\n| `FOOTER_CTA` | the closing call to action |\n| `CONTACT` | a way to reach a human |\n\n**Every section names the market entries it draws on** (`drawsOnRefs`) — the benefit, proof,\nobjection, job, pain, ICP or tone refs, exactly as the snapshot authored them. That is what makes a\nclaim checkable: a reader opens the snapshot and finds the entry. A section that draws on nothing is\na section somebody invented, and the validator reports a page where no section names anything.\n\n**A section that says what the product DOES names the requirement behind it** (`backedByRequirementRefs`).\nA market benefit says what a buyer wants; it does not say the product delivers it. An earlier site\npromised \"country workflow guidance with its limits stated\", drawn from a benefit, while the product\nshipped an empty page for an administrator to write guidance into.\n\n- Every `FEATURE_DETAIL` and `FEATURE_BENEFIT_SUMMARY` section cites the requirements (functional, or\n non-functional such as working on a phone in the field), by their refs in your `requirements` input,\n that commit the product to what it describes. The validator reports one that cites none.\n- Any other section (a hero, an FAQ, a pricing table) may cite requirements too, and should when its\n copy will say what the product does. A section that cites none describes no capability as available.\n- A citation is necessary, not sufficient. When the section is built, its author is told where each\n cited requirement stands: delivered, still being built, reported unmet by the run that built it, or\n only on a later roadmap phase. Only what is delivered is written as available; the rest is written as\n planned. So cite what the section is ABOUT, and do not drop a requirement because it is not built yet.\n- A benefit no requirement backs is not presented as a capability: leave it out, or give it a section\n whose purpose says it is planned.\n\nLead with fit. The brief carries the computed fit matrix beside each benefit's authored Kano\ncategory; a page for an ICP argues the benefits that score for THAT ICP first, rather than the ones\nthe model finds most interesting.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every page ref that still has a reason to exist — build tasks\nname them, and a ref that moves orphans the task that produced its page. Add, sharpen and reorder;\ndo not renumber.\n\n## What you emit\n\n- The **website plan** at `specifications/src/website-plan/index.ts` — a disposition with its\n rationale, and the pages in navigation order, each with its purpose, audience, tone and ordered\n sections.\n\n## Verification\n\n- Every `drawsOnRefs` entry names an entry that exists in the market snapshot.\n- Every `FEATURE_DETAIL` and `FEATURE_BENEFIT_SUMMARY` section names at least one `backedByRequirementRefs`\n entry, and each names a requirement in the requirements.\n- Every page opens on a `HERO`, and exactly one page reads as the landing page.\n- `rg -n \"sectionRef\" specifications/src/website-plan/index.ts | wc -l` — the number of website\n section tasks the build lane will emit.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem: naming a path here would be an instruction answered from\nrecollection (#1435). So each skill is named by its REF, and only `website-page-authoring` reaches\nthis step as a BODY (`method.skillBodyRefs`) — it is the one contract the plan must not contradict,\nbecause it says what a page IS in this engine: a manifest, a route adapter, a sections file and a\nlabel pack that fails the build closed on a missing key. A page planned against anything else is a\npage the build lane cannot author.\n\nThe others below are the contracts the CODING AGENT opens when it builds each task, listed so a\nreader knows the plan's decisions land somewhere:\n\n- `website-navigation-authoring` — how pages reach each other, which bounds how many top-level pages are worth planning.\n- `website-seo-aeo-geo` — what a page owes a search engine and an answer engine.\n- `website-label-pack` — every string a section renders is a label key, and the build fails closed on a missing one.\n- `website-marketing-metadata-extension` — the metadata a page carries beyond its sections.\n- `website-section-*` — one per section KIND, bound to the emitted task by `WEBSITE_SECTION_SKILL_REF`.\n- `market-positioning-authoring`, `market-tone-of-voice`, `market-proof-and-objection` — the market\n vocabularies a section draws on, which arrive here as the market snapshot itself rather than as prose.\n",
|
|
59
62
|
"skillRefs": [
|
|
60
63
|
"website-page-authoring",
|
|
61
64
|
"website-navigation-authoring",
|
|
@@ -390,7 +390,8 @@ cannot say what an erasure does to them. Where the facts also report a category
|
|
|
390
390
|
origin, say what IS established alongside it.
|
|
391
391
|
`NEEDS_CONFIGURATION` for every resource that does not.
|
|
392
392
|
|
|
393
|
-
**What closes it** — the application's own authors declaring `retentionPolicy
|
|
393
|
+
**What closes it** — the application's own authors declaring `retentionPolicy`, with the `dataSubjectPolicy` the
|
|
394
|
+
factory requires beside it, on the resource. Name
|
|
394
395
|
the resources individually: the remedy is per-resource, and a count is not actionable.
|
|
395
396
|
|
|
396
397
|
|
|
@@ -695,8 +696,11 @@ its subprocessors; reaching the processor is the transfer the operator answers f
|
|
|
695
696
|
|
|
696
697
|
**The `international-transfers` fact is COMPUTED from those determinations** — you never declare it.
|
|
697
698
|
It carries each determined entry, the origin jurisdictions, `undeterminedRecipients` — a register entry
|
|
698
|
-
with no determination, or a configured provider the register does not establish —
|
|
699
|
-
a declared origin a TRANSFER names no safeguard for
|
|
699
|
+
with no determination, or a configured provider the register does not establish — `safeguardGaps`:
|
|
700
|
+
a declared origin a TRANSFER names no safeguard for — and `operatorHostingRegions`: where the operator's
|
|
701
|
+
OWN infrastructure holds the data (`operatorComplianceIdentity.hostingRegions`), or `null` when the
|
|
702
|
+
operator has not declared it. State a `null` as the operator's hosting location not yet being declared;
|
|
703
|
+
it never means the data is held nowhere, and it never supports "no international transfer".
|
|
700
704
|
|
|
701
705
|
**Completeness** — do not round any state up.
|
|
702
706
|
|
|
@@ -25,7 +25,7 @@
|
|
|
25
25
|
],
|
|
26
26
|
"stepOutputs": [],
|
|
27
27
|
"method": {
|
|
28
|
-
"guidance": "# Compliance document candidate method\n\nYou are drafting ONE governed document for this application, from what the application has already\ndeclared. Follow the `compliance-document-authoring` skill for the rules — its full text is in your\nbrief, under \"The skills this method tells you to FOLLOW\", because this step has no tools and cannot\nopen a file. This method says which document, what shape, and what the two closed vocabularies are.\n\n## Choose the document, from the two this lane may draft\n\n`documentRef` must be one of six and the contract refuses anything else, but only two of the six are\nYOURS. The four internal `governance.*` documents belong to `refinement.governance-document-candidate`,\nwhich ships their blueprints; drafting one here would mean writing a document whose obligations you were\nnever given.\n\n| `documentRef` | what it is | drafted by |\n|---|---|---|\n| `document:public.privacy-notice` | what personal data the application holds and what happens to it | **this lane** |\n| `document:public.service-terms` | the commercial and service relationship | **this lane** |\n| `document:governance.scope-system-description` | what the system IS, for an assurance reader | `refinement.governance-document-candidate` |\n| `document:governance.roles-responsibilities` | who is accountable for what | `refinement.governance-document-candidate` |\n| `document:governance.program-handbook` | how the governance program runs | `refinement.governance-document-candidate` |\n| `document:governance.document-record-control` | how governed documents are themselves controlled | `refinement.governance-document-candidate` |\n\n**Draft a document this application does not already hold.** The run tells you which those are: the\nbrief opens with what the application has already drafted, listing each document it may produce here\nas ALREADY DRAFTED or not yet drafted. Drafts are keyed by `documentRef`, so drafting one that is\nalready there REPLACES it — right when that draft is wrong, and a wasted 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, the **privacy notice** comes first: it is the one every application holding\npersonal data needs. Where none remains, the honest reason to draft again is that a held draft is\nwrong — say which one and why in your own reasoning, rather than redrafting the first on the list.\n\nThis paragraph used to read \"draft the privacy notice unless the run tells you otherwise\", at a time\nwhen no run told it anything. Measured against a real application on 2026-09-16: with its privacy\nnotice already drafted, two consecutive runs meant to produce the service terms drafted the notice\nagain and replaced it, and the application finished each run holding exactly what it started with.\nThe second sentence was stale as well — it said the privacy notice was \"the only one whose facts the\ncurrent derivation supplies\", which stopped being true once the fact-declaring playbook began\ndeclaring the account, billing and AI facts the service terms rest on.\n\nNaming a document outside this set is not a smaller decision than it looks. Each of the six has a\nconcern composition the framework measures a draft against, so a seventh name is a document nobody can\nstate the gaps in — and stating the gaps is the whole point.\n\n## One section per concern, and SAY which concern\n\nEvery section carries `concernRef`, from the closed compliance-concern vocabulary. **The composition\nfor each document is inlined at the end of this method** — one entry per concern, saying what it\nasserts, what in the application it derives from, what state it usually reaches, and what closes it\nwhen it cannot. Draft one section per concern, in the order given, and produce **every** one:\na concern nothing can answer becomes a section with a marked clause, never a missing heading.\n\nThose entries are the difference between a draft that states its gaps and one that guesses at them.\nWhere a concern's entry names an issue number as the remedy, say so in `incompleteness.closedBy` —\n`#89`, `#91` — because a numbered issue is a remedy a reader can open, and \"application configuration\nowner\" is not.\n\nUse `concernRef: null` only for a section that genuinely answers no concern: a preamble, a contact\nblock. It is not a way past a concern you found hard. A concern you cannot establish gets a SECTION,\nwith a clause marked incomplete — which is the mechanism this whole document exists around.\n\nThe value must be the concern's exact name. A near miss (`retention` for `retention-and-deletion`) is\nworse than a null: it reports the concern as unaddressed while the document addresses it.\n\n\n## And SAY which required parts the section supplies\n\nEvery section also carries `satisfiesSectionRefs`: the refs, from the document definition rendered in\nyour brief, that this section actually addresses. This is a different question from `concernRef` and\nboth are answered — the concern says what compliance TOPIC the section is about, the satisfied refs\nsay what part of THIS document it supplies.\n\nYou are asked for the join because you are the only reader that holds both. The concern set is one\nflat vocabulary spanning every document type; the required parts are defined per document, and the\nsame concern does not sit under the same heading in a privacy notice and a governance handbook. A\nmapping written once in the framework would have to pick one answer and be wrong somewhere.\n\n- A section may claim several refs, and several sections may claim one between them.\n- A section that answers no required part — a preamble, a contact block — answers `null`. Not an\n empty list: `null` and `[]` would be two spellings of one state, and the contract refuses the second.\n- **Claim honestly.** A required ref nobody claims is reported as a part the document may not address,\n which is a true and useful finding. Claiming one you did not address hides that, and nothing\n downstream reads your prose to catch it.\n\nDo NOT adopt the definition's refs as your own `sectionRef` values. Your section set is the concern\nrule above; these are a claim you attach to it, not names you take.\n\n**Clauses carry the same claim**, as `satisfiesClauseRefs`, and answer `null` the same way. Your brief\nlists the blueprint's clauses under each section, each marked REQUIRED or CONDITIONAL; name the ones\nyour clause supplies.\n\nBoth keys were ASKED FOR HERE and absent from the strict contract you answer until 2026-09-02, so a\ndraft that followed this section could not parse and every landed document claimed nothing. If you\nare reading a document produced before then, its empty coverage is that defect and not a finding\nabout the document.\n\n- Several of your clauses may supply one blueprint clause between them, and one clause may supply\n several.\n- A clause supplying none — a transition, a heading gloss — claims none.\n- **Only the clauses marked REQUIRED are owed.** A CONDITIONAL clause is supplied when its condition\n holds and correctly omitted otherwise, so leaving one unclaimed is not a gap.\n\nThis is the anchor a clause did not previously have. A fact is named by the catalog and a section\ncarries its concern, so both survive a redraft; a clause was named freely and joined to nothing, which\nis why a reviewer who approved one could not find it in the next revision.\n## What a clause may say\n\nThe rule is ASSERT versus MARK, and the skill states it in full. In short: a clause may say \"this is\nnot yet established\"; it may not say something untrue.\n\n- `DERIVED` — established by a fact this application has declared. Cite it in `factRefs`. A `DERIVED`\n clause citing a fact the facts file does not declare is REFUSED before the write.\n\n **This is decided against the facts file as it stands NOW, not against any earlier draft.** You are\n producing the whole document from what the application currently declares, so a concern the facts\n answer today is `DERIVED` today — even if a previous version of this document marked it incomplete\n and is still in the tree. Re-running this playbook is how a document that went stale is repaired,\n and it only repairs anything if the re-draft is willing to close a mark.\n\n **Never fold a declared fact into a marked clause.** When one concern has a declared half and a\n missing half — retention periods declared while retention enforcement is not evidenced, a\n processor register that names most recipients while some providers have no recorded identity —\n write TWO clauses: a `DERIVED` clause stating what is declared, and a separate marked clause naming\n what is missing. A clause is marked as a whole, so one clause carrying both states nothing: every\n clause citing the declared fact is then incomplete, and the standing coherence report correctly\n records that the document mentions the fact without stating it. A redraft that marked its retention\n and recipients clauses because each also carried a gap stopped stating two facts the previous draft\n had stated.\n\n **A fact the application declared NOT APPLICABLE is a fact, and a clause may rest on it.** *\"No\n external analytics provider is configured\"* is `DERIVED`, not incomplete: the application settled the\n question and recorded the answer. Marking such a concern incomplete says the application does not\n know something it does know, which is as wrong as overstating. What is refused is citing a fact the\n facts file does not declare AT ALL.\n- `NEEDS_FRAMEWORK` / `NEEDS_DECISION` / `NEEDS_CONFIGURATION` — mark it, and say in `incompleteness`\n what is missing and who closes it. Four distinct suppliers, four distinct remedies; do not merge them.\n\n **When what is missing is a FACT, name it in `incompleteness.awaitingFactRefs`.** The skill argues\n this in full; the short version is that a marked clause asserts an ABSENCE in the application's own\n configuration, and that assertion goes false the moment someone declares the thing — silently, since\n nothing about the document changes. The awaited ref is what lets generation, landing and the\n standing coherence report all say the clause has gone stale. A clause that awaits nothing rots\n unobserved, and one already has.\n\n **`NEEDS_DECISION` and `NEEDS_FRAMEWORK` are the pair most easily confused, and the difference is\n the REMEDY.** `NEEDS_DECISION` means a surface exists and nobody filled it in — the reader goes and\n answers. `NEEDS_FRAMEWORK` means there is NOWHERE to record the answer; telling a reader to decide\n is telling them to write into a void.\n\n Measured on 2026-08-30, a produced notice marked operator identity `NEEDS_DECISION` when no surface\n for it existed at all, beside retention periods marked identically and genuinely just unfilled. Two\n remedies, rendered the same, and a reader could act on neither.\n\n **So every incomplete clause must NAME THE SURFACE its answer goes to**, or say plainly that none\n exists. A gap with a named surface is a task; a gap without one is a request for work nobody has\n scoped. The fragment you are working from names the surface where there is one — carry it into\n `incompleteness` rather than leaving the reader to find it.\n\n **`closedBy` must name WHO can reach that surface, and an ENGINE resource is not the application\n author's to edit.** `retentionPolicy`, `systemAccessPolicy.exportSubject` and `.dataCategories()`\n on an engine resource live in engine source. Writing \"application authors must declare\n `retentionPolicy` for each affected engine resource\" hands the reader a task they cannot perform —\n and a produced notice said exactly that, for 83 resources, in the same confident register as the\n remedies that ARE actionable. An unreachable remedy is worse than an unnamed one: it looks like\n work, gets scheduled, and fails when someone tries it.\n\n Where the closer is the FRAMEWORK, say so plainly — \"the framework must declare these on its own\n resources\" — and keep it separate from what this application owes.\n\nNever fill an unresolved fact, infer a legal decision, or describe the draft as approved, compliant,\nlegally valid, released or published. Locale and jurisdiction are review inputs; leaving them\nunresolved is a legitimate answer and never a reason not to draft.\n\n**And the mirror of that, which matters just as much: a missing approval never stops you.** Approval\nhappens at the END and is a human commit; a downstream release can be composed and MARKED\n`UNAPPROVED`. So the absence of one is a STATE to record, never a reason to produce nothing and never\nan outcome to report as blocked. The two failures are symmetric — claiming an approval that did not\nhappen, and refusing to act because it has not happened yet — and a compliance workflow standing in\nfront of the application-creation mechanism is the second one.\n\n## The refs you write, and their exact shape\n\nEvery `…Ref` field is a **namespaced ref**: `namespace:slug`, both halves lowercase, words joined by\nhyphens. `clause:retention-duration-not-declared` is one; `clause:Retention Duration` is not, and a\nwhole draft is rejected for a single malformed one. Ref ARRAYS are arrays of those strings — never\nobjects, never `{ ref: … }`.\n\nPer clause, all three ref arrays are required. Two of them may be empty, but **not both of the\nfirst two at once** — a clause that names no fact and no policy is sourced by nothing and is\nrejected:\n\n- `factRefs` — the facts this clause rests on, exactly as the facts file declares them. It may be\n EMPTY for a clause that establishes nothing (a marked clause often does).\n- `sourcePolicyRefs` — the application POLICY AREA the statement is sourced from, and nothing else.\n Every entry must be in the `policy:` namespace (`policy:retention`, `policy:recipients`,\n `policy:security-controls`); any other namespace is rejected outright. **Do NOT put a fact\n authority here.** A clause resting on declared facts already cites its authorities through\n `factRefs`, which resolves them — repeating them here duplicates the citation beside it and\n resolves to nothing. So this array is EMPTY for a fact-backed clause, and carries a policy area\n for a clause that is sourced from a policy rather than from a fact.\n- `claimGuardRefs` — at least one: what this clause must NOT be read as claiming. These are the\n boundaries you are already holding — `claim-guard:no-legal-applicability-claim`,\n `claim-guard:no-invented-retention-period`, `claim-guard:known-fact-only`. Name the ones that apply\n to this clause; do not repeat the same guard on every clause out of habit. You do not name the\n CATALOG's guard for the material: it is added for you from the blueprint clauses this clause\n `satisfiesClauseRefs`, so a clause that says what it satisfies is checked against it automatically.\n\n`evidenceRefs` is **`null` on every clause of a public document**, and that is not a gap to work around.\nIt cites a judged run from this application's own assurance repository — self-attested internal\nevidence — and a public notice may carry none, whatever the run says: a reader of one cannot weigh an\noperator's judgement of its own product, and any citation here is refused before the draft becomes a\nfile. That evidence belongs to the internal governance documents, which\n`refinement.governance-document-candidate` draws. Where you would have leaned on a measurement, say\nwhat is CONFIGURED or DECLARED, or MARK the statement.\n\n**The same holds when a FACT is phrased as behaviour, and that is where drafts go wrong.** The facts\nyou cite describe the product in the present tense — *\"the running application reaches\"*, *\"the\nframework sets\"*, *\"acceptance joins the member\"*, *\"kept 30 days, then erased\"* — which is accurate\nfor a fact and is an operating claim in a public notice. Do not carry the verb across: restate each as\na declaration (*\"the configuration enables\"*, *\"the framework declares\"*, *\"the configured membership\nmodel admits\"*, *\"the declared period is 30 days, after which the data is due for erasure\"*). The\njudge reads every clause of a public document for exactly this, and a sentence copied from a fact is\nthe one it finds.\n\n`reviewChecklistRefs` needs at least one (`review-checklist:<slug>`) — what a human must confirm before\nthis draft is worth anything. `limitationRefs` may be empty, but rarely should be: it is where you say\nwhat the document does NOT cover, in your own words as the drafter, rather than leaving the reader to\ndiscover it.\n\n## You do not compose the release — and a release nobody approved is marked UNAPPROVED\n\nYou draft the candidate. You do NOT author its release, and that is a boundary rather than an\nomission: almost everything a release carries is DERIVED from the accepted document definition — the\ndocument's class, who it addresses, which channels may carry it, which interactions it permits — and\na model restating those would create five ways to disagree with the catalog, invisibly. The rest\n(which declared variant, when it takes effect) is a composition over families you are not holding.\n\nA human declares a release DECISION in the application's\n`specifications/src/document-releases/compositions.ts`, and `wildo config document-releases` composes\neach decision not yet recorded — your candidate plus the declared variant and release policy — and\nrecords the finished release, text included. Nothing records a release because you landed a draft: an\napplication with no decision holds no release yet, which is a valid state and not yours to fix from\nthis playbook. Until a public document (privacy notice, service terms) has a release, its public page\nshows your latest draft, marked as a draft — so what you mark as not established is what a reader sees.\nWhat matters for your work is what composition produces when it runs: a release carrying\n`approvalState`, and one nobody has approved is `UNAPPROVED` and exists anyway.\n\n**Which is why a missing approval never changes what you do here.** Draft the document completely,\nmark every statement you cannot establish, and let the release be composed and marked. Waiting for an\napproval before drafting — or describing a draft as approved to get past the gate — are the two\nsymmetric failures, and the first is a compliance workflow standing in front of the mechanism that\nbuilds 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. It is\naccepted by a commit and by nothing else; who makes that commit is the host's autonomy posture, and\nonly a PERSON's commit is an approval. Landing is not approval, release or publication — and neither is\na commit the development companion authors under the YOLO posture.\n\n\n---\n\n# The compositions\n\nEach of the following is one document's full concern list. Use the one matching your `documentRef`\nand ignore the rest.\n\n## `document:public.privacy-notice` — thirteen concerns\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\n\n### Concern: legal basis and controller/processor role\n\n**Asserts** — the lawful basis for each processing purpose, and whether the operator acts as\ncontroller or processor for it.\n\n**Derives from** — `operatorComplianceIdentity.lawfulBases` and `.roleAllocations` in\n`wildo.saas.config.ts`.\n\nThe DETERMINATIONS are never derivable — both are legal conclusions about the operator's own\narrangements, and the framework can show WHAT is processed and BY WHICH MECHANISM without establishing\nunder which basis or in which role. What it now provides is where to record the conclusion, so that a\nregeneration reproduces it instead of destroying it.\n\n**The role is a LIST, not a field, and the produced notice said so before the surface existed:**\n*\"This notice therefore does not assign a single legal role to all data processed in a workspace.\"* A\nB2B SaaS is typically a processor for the records its customers put in and a controller for its\naccount holders' own data, simultaneously. `roleAllocations` carries one role per population, and a\ndocument that collapses them into one is wrong about both.\n\n**The `lawful-bases` fact is COMPUTED from `lawfulBases`** — every purpose, its basis and, for\nlegitimate interests, the assessment. You never declare it: a restatement would be a second copy of the\noperator's decision that nothing compares with the first. Absent bases leave the fact absent.\n\n**Give each purpose a stable `purposeRef`** (`account-security`) when a recipient serves it. A vendor\nnames the purposes it serves in `providerComplianceChoices.<ref>.purposeRefs`, and the recipients fact\njoins the two. The prose `purpose` can then be reworded without breaking the link; a ref naming no\ndeclared purpose is reported, never refused.\n\n**`LEGITIMATE_INTERESTS` cannot be declared without its assessment** — the schema refuses it. It is\nthe only Art. 6(1) basis whose lawfulness depends on a balancing test, so the bare claim asserts a\nconclusion nobody reached.\n\n**Completeness** — `DERIVED` when declared; `NEEDS_DECISION` when not. Never `NEEDS_FRAMEWORK`: there\nis a surface, so the remedy is to fill it in, not to build something. Name the surface when reporting\nthe gap.\n\n**What closes it** — the operator determining, per purpose, the basis and the role, ideally with\ncounsel, and declaring them in `operatorComplianceIdentity`. The tenancy fragment describes the SHAPE this usually takes in a B2B SaaS — processor for\nthe data a customer stores about its own people, controller for the data the operator holds about\naccount holders — but describing the common shape is not the same as determining this operator's, and\nthe produced document must not present the first as the second.\n\n**This is the fragment most likely to be filled in by a confident guess**, because the shape is\nfamiliar and the sentence is easy to write. Resist it. A basis stated in a published notice is a\nposition the operator has taken; a basis that was never determined is a position nobody can defend.\n\n\n### Concern: personal data held\n\n**Asserts** — which of the application's own records are about identifiable people, and which hold no\npersonal data of their own.\n\n**Derives from** — each resource's `retentionPolicy.mode` (`ErasureRetentionMode`, in\n`@wildo-ai/saas-models`), read for every resource the application declares:\n\n| declaration | what the document may state |\n|---|---|\n| `RETAIN_AND_IMPERSONALIZE` | this record holds personal data; the fields marked `.impersonalizeWith()` are what is scrubbed on erasure |\n| `RETAIN_ONLY` | this record holds **no personal data of its own** — a positive, factory-enforced statement, because declaring a scrub treatment under this mode fails at config build |\n| absent | the application has not said |\n\nRead `dataSubjectPolicy.kind` for the SESSION question only. `NO_PRINCIPAL` is equally true of an\ninvoice and of a CRM contact, so it never tells you whether a record is about a person — the\nretention mode does.\n\n**Completeness** — `DERIVED` for every resource that declares a retention policy.\n\n**An erasure-coverage gap does NOT license a claim about whether personal data is held.** The two are\ndifferent axes and the facts report them separately: `retentionPolicy` answers *what happens to this\nrow on erasure*, while a field's `.dataCategories()` answers *what kind of data is in it*. A resource\ncan declare the second and not the first, and 48 of the engine's 85 do.\n\nSo writing \"N resources have no declared erasure treatment, so this notice cannot establish whether\nthey hold personal data\" is an over-reach, and it contradicts the data-categories section of the same\ndocument — which enumerates categories drawn from those very resources. It was produced twice on\n2026-08-30 before this paragraph existed.\n\nState the gap as what it is: those resources have not declared an erasure TREATMENT, so a notice\ncannot say what an erasure does to them. Where the facts also report a category coverage for the same\norigin, say what IS established alongside it.\n`NEEDS_CONFIGURATION` for every resource that does not.\n\n**What closes it** — the application's own authors declaring `retentionPolicy` on the resource. Name\nthe resources individually: the remedy is per-resource, and a count is not actionable.\n\n\n### Concern: data categories\n\n**Asserts** — which CATEGORIES of personal data are held: identity, contact details, credentials,\nfinancial, usage, location, user content, professional, and any GDPR Art. 9 special-category or\nArt. 10 criminal-offence data.\n\n**Derives from** — each field's `.dataCategories()` declaration, reported per resource and unioned\nacross the application in the compliance-primary-facts section. One category is DERIVED rather than\ndeclared: `credentials`, from `.isPassword()` / `.isOtp()` / `.isWriteOnlySecret()`, which are\nmarkers the author already wrote.\n\n**Nothing is derived from a field NAME.** `email`, `phone` and `dateOfBirth` are suggestive while\n`notes` is not, so a category list assembled by pattern-matching identifiers is a guess presented as\nan inventory — and its failure mode is silent, because whatever the guess misses is simply not\ndisclosed. The declaration exists so that never happens.\n\n**Completeness** — `DERIVED` when the application declares categories; `NEEDS_CONFIGURATION` when it\ndeclares none, or when the facts section lists OUTSTANDING fields.\n\n**The two gaps are different and must not be written the same way.**\n\n- A resource that declares no category at all may genuinely hold no personal data. Nothing\n distinguishes \"considered and not applicable\" from \"never asked\", so state that the question is\n unanswered — never that the application holds no personal data.\n- A field the facts section lists as OUTSTANDING is a provable omission. The application already\n declared that field personal by another door — an erasure scrub treatment, a portability\n provenance, or a credential marker — so the missing category is an omission, not a judgement.\n Name the field and its basis. Do not guess what it contains.\n\n**Say WHICH special category, not that there is one.** A `special-category:*` value is Art. 9 data\nand carries a lawful-basis condition of its own beyond Art. 6; `criminal-offence` is Art. 10, a\nseparate article with a different condition. \"We process special category data\" is not a disclosure —\nthe enum names the kind precisely so a notice can.\n\n**Do NOT point at `Compliance_DataClassification`.** It exists, it is a four-level SENSITIVITY ladder\n(public / internal / confidential / restricted) applied only to flows-actors configuration, and it\nanswers \"how protected must this be\" rather than \"what kind of personal data is this\". Using it here\nwould produce a notice describing protection levels where a reader expects data types. It is named\nexplicitly because it is a near-miss a reader will otherwise find and assume answers this concern.\n\n\n### Concern: consent and preferences\n\n**Asserts** — what the application asks consent for, at what granularity, and what a person's choice\nactually controls.\n\n**Derives from**\n\n- `ConsentPurpose` (`@wildo-ai/saas-models`): `ANALYTICS` · `MARKETING` — a SET of purposes, each\n granted or not on its own. There is no ordering: agreeing to marketing says nothing about analytics.\n- per-person `privacy.consentedPurposes` — the purposes each person granted, empty until they grant\n one — and `privacy.consentDecidedAt`, stamped by the server when they decide. An empty set WITH an\n instant is \"declined everything\"; no instant is \"never asked\". A notice must not state the second\n as the first.\n- `analytics.requiresConsent` (default `true`) — whether the application's analytics rest on\n `ANALYTICS`. It governs analytics alone, never use of the service.\n- the visitor tier: a marketing website keeps a visitor's decision in their browser and starts a\n consent-based provider (product analytics) only once its purpose is granted.\n\n- `operatorComplianceIdentity.serviceConsentRequirement` (`wildo.saas.config.ts`) — what a person\n must agree to in order to use the service AT ALL, and what that gate covers.\n\n**An empty `requiredPurposes` is a POSITIVE answer and the usual one.** The operator declaring that nothing is gated on\nconsent has answered the question; a document must state it as settled rather than treating it as an\nabsence. ABSENT is the different case — nobody was asked — and the brief distinguishes the two.\n\n**A consent GATE is not a lawful BASIS.** For most B2B SaaS the basis for core processing is CONTRACT:\na person uses the product because their employer signed for it. A notice that reads a gate as a basis\nstates that their data is processed on consent they could withdraw, which is wrong about the single\nmost consequential thing in the document. The basis is declared per purpose in `lawfulBases`.\n\n**Completeness** — `DERIVED` for the analytics gate, each person's granted purposes, and the\nservice-wide requirement once declared — which the application ENFORCES: until the required purposes are\ngranted, the backend refuses every operation the person initiates — API and MCP operations, queued work,\nWebSocket reads and subscriptions, agent tools, retrieval, charts and analytics, A2A task reads, and A2A or\nWebSocket conversations, including resuming one after an approval — except their own profile and preferences,\nwhere they record the consent, and cancelling an A2A task they already started (signing in and out stay open;\nupdates the server pushes on its own are not held back), and the web\napplication withholds its pages; `NEEDS_DECISION` naming `serviceConsentRequirement` when it is not.\n\nThis was `NEEDS_FRAMEWORK` until 2026-08-30, correctly: there was nowhere to record the answer. Issue\n#139 built the surface, so the remedy changed from \"someone must build this\" to \"fill this in\" — a\ndifferent party and a different task, which is why the two states are never interchangeable.\n\n**Say the thing readers get wrong.** Consent is one lawful basis among several, and it is not the one\nmost B2B processing rests on. **Never write that all processing rests on consent, and never write\nthat accepting terms supplies a lawful basis** — accepting a contract is a different basis with\ndifferent consequences, and conflating them is the single most common defect in a generated privacy\nnotice. Which basis applies is a `NEEDS_DECISION`; see the legal-basis fragment.\n\n\n### Concern: retention and deletion\n\n**Asserts** — what happens to a record when its subject is erased, and how long records are kept.\n\nTwo questions, and the framework answers both — the second only for the resources bound to a class.\n\n**Derives from (the HOW — answerable)** — each resource's `retentionPolicy.mode`:\n`RETAIN_AND_IMPERSONALIZE` keeps the row, freezes it, hides it from normal reads and scrubs the fields\nmarked `.impersonalizeWith()`; `RETAIN_ONLY` keeps and freezes a row that holds no personal data of\nits own. Reading the per-field treatments tells the document exactly WHICH values are destroyed and\nwhich survive, which is a genuinely strong statement most notices cannot make.\n\n**Records a statute keeps survive an erasure RESTRICTED, and the request still completes.** A resource\nbound to `BUSINESS_RECORDS` declares `retentionPolicy.statutoryRetention`: the GDPR Art. 17(3)(b) ground\n(`LEGAL_OBLIGATION`) and the statute in the operator's words. An erasure erases everything else, keeps\nthose rows retained and hidden from any other processing until their statutory period ends, and lists\neach one with its ground and end date — which is what the notice must say: that some records are kept\nbecause the law requires it, which law, and that they are deleted when the period ends. The\n`retention-rules` fact names these resources and their statute under each erasure treatment. Never write\nthat an erasure is refused or delayed because of them.\n\n**Derives from (the HOW LONG)** — the application's `dataRetention` schedule, declared in its config\nover five data classes: `RESOURCE_DATA` (its records), `FILES` (uploaded bytes), `AUDIT_LOGS` (the\ntamper-evident trail, kept longest and for a different reason — it is the evidence an operator may\nlawfully retain under GDPR Art. 17(3)), `OPERATIONAL_LOGS`, and `BUSINESS_RECORDS` (records a statute\nrequires to be kept for a minimum period). Each declared class carries a period in days AND the\noperator's stated reason for it.\n\n**Enforced where a resource is BOUND** — a resource declares `retentionBinding: { retentionClass,\nstartPoint }`, and the retention sweep deletes its rows once the period has passed since the start point\n(the account closing, the record closing, its creation, the end of its calendar year). The period is\ncounted from when the record stops being needed, so a live record is never deleted for its age. The\n`retention-rules` fact names, per class, the resources bound to it and the MECHANISMS that act on it:\n`RETENTION_CLASS_SWEEP`, `FILES_CLEANUP` (file bytes after their row is gone), `AUDIT_ARCHIVAL`. An EMPTY\nmechanism list means nothing is even wired to enforce the class — say exactly that. `AUDIT_ARCHIVAL` means the audit\ntrail is archived after the period and is NEVER deleted: do not write that audit records are deleted.\nThe fact also names the resources bound to no class — kept until erased, because nobody decided otherwise.\n\n**Whether a period IS enforced is a different fact** — `retention-enforcement`, computed from the records the\nretention sweep writes on every run (runtime evidence, not a declaration). Per declared class it reads\n`ENFORCED` (every bound resource shows a recent completed or deferred run), `DECLARED` (a period nothing has\nyet been shown to apply) or `FAILING` (the latest run of a bound resource failed). Say a period is enforced\nONLY where it reads `ENFORCED`, and as of its `observedAt` — and only for the resources bound to the class:\n`mechanismsNotEvidencedByTheseRecords` names what the records cannot see (the audit trail's archival, the files\ncleanup), so never write that the audit trail's or the files' retention is evidenced by this fact. A mechanism in `retention-rules` says the sweep\nWILL act; only this fact says it did. When the fact is absent the records were not collected: say enforcement\nis not yet evidenced, never that it is not happening.\n\nThe classes are the STORES on purpose: the same declaration answers what a notice must state and what\na backup-and-restore inventory must protect (issue #8).\n\n**The `retention-rules` fact is COMPUTED from both** — the declared periods with their reasons and\nmechanisms, the classes with no period, each resource's declared erasure treatment, the resources\ndeclaring none, and the resources bound to no retention class.\nYou never declare it. It is absent when no schedule is declared, because a treatment alone would read as\nthe whole answer.\n\n**Completeness** — `DERIVED` for the treatment, and for each retention class the application HAS\ndeclared. `NEEDS_DECISION` for each class it has not: the mechanism exists, so what is missing is an\noperator's decision rather than an engine change. Do not let the derivable half hide the missing one —\na statement about erasure mechanics reads to a reader as an answer about retention, so both go in the\nsame breath.\n\n**What closes it** — the operator deciding a period, and saying why. Not a framework change: issue #89\ndelivered the declaration surface, so an undeclared class is now an unanswered question rather than an\nunaskable one.\n\n**An UNDECLARED class is not \"kept indefinitely\" and not \"deleted immediately\".** It is a decision\nnobody has taken, and the document must say exactly that.\n\n**A legal hold suspends every deletion of its scope** — the retention sweep, an erasure, the tenant purge,\nfile bytes — until the tier that placed it releases it (`legalHolds`). The notice may say that data is kept\nbeyond its period while a legal claim, an investigation or a legal obligation requires it, and that it is\ndeleted once that ends. Never write that a hold expires, and never name a matter.\n\n**Never write a placeholder period.** \"Typically 12 months\" in a published notice is a commitment\nnobody made and nothing enforces.\n\n\n### Concern: recipients and processors\n\n**Asserts** — who else receives personal data, in what role, and where they process it.\n\n**Derives from (who receives)** — the RECIPIENT POPULATION, which your brief renders under *\"Who\nRECEIVES data, by whose account reaches them\"*. It is computed by `computeRecipientPopulation`\n(`@wildo-ai/saas-specifications/application-creation`) from the configuration and a scan of the\napplication's source, and the privacy notice's recipients fact and the assurance evidence read the SAME\npopulation, so none of them can disagree with the others. Every provider declared under a runtime scope\n(`backend`, `frontendServices.<service>`, `minions.<minion>`, `workers.<worker>`) and every\n`systemsOfRecord` instance lands in exactly ONE of four classes:\n\n| Class | What it means | What the document does with it |\n| --- | --- | --- |\n| **OPERATOR-RUN** | an explicit `SELF_HOSTED` compliance choice | processing under the operator's own control — never a recipient |\n| **OPERATOR SUB-PROCESSOR** | some data path spends the APPLICATION's own account (an engine capability, a wired capability role, a typed client, a browser operation, a system of record) | the operator's recipient; it belongs in the processor register |\n| **TENANT RECIPIENT** | reachable ONLY through a customer's or a person's own connected account | the customer's own vendor, reached at the customer's instruction. Never the operator's sub-processor; you may say a customer can connect its own account |\n| **DECLARED, NO DATA PATH** | configured, and nothing in the application reaches it | receives nothing. Never name it as a recipient; the gap is the declaration itself |\n\nAn engine capability is ONE data path, not the definition of a recipient: a catalogue vendor called\nthrough its typed client receives data with no capability at all, and a vendor declared \"to exercise the\nloading chain\" with nothing calling it receives nothing. The tenant class matters most when the operator\nis a PROCESSOR for the data: listing a customer's own vendor as its sub-processor states an engagement the\noperator never made. The function and its limits are in the `compliance-document-authoring` skill's\n`references/framework-recipient-population.md`.\n\n**Derives from (the identities)** — the application's PROCESSOR REGISTER, which your brief renders\nunder *\"Who else processes personal data\"*. Per entry: the processor's **legal entity**, the\n**regions** it processes in, and its own **subprocessors** with their regions.\n\n**The register holds two kinds of entry and the brief labels them differently — say which.** A\nCONFIGURED PROVIDER entry joins to the application's composition, so it can be checked against it: a\nclaim about a provider the application does not configure is detectable, and a configured provider\nwith no entry is reported as UNDECLARED. An AUTHORED entry — a hosting company, a CDN, a support desk\n— joins to nothing, because no configuration mentions it. The framework can neither confirm it nor\nnotice its absence.\n\nBoth kinds of declared relationship can belong in the notice when their role is established. What\nmust not happen is presenting the second with the authority of the first: an authored entry is the operator's word, and a document that reads\nas though the framework verified it overstates what anyone checked.\n\n**A SELF-HOSTED provider is not a recipient either, and this is the second way to get the section\nwrong.** The brief's *\"Who RUNS each bound provider\"* block splits the members the OPERATOR answers\nfor (operator sub-processors and operator-run) three ways:\nTHIRD-PARTY RECIPIENTS (vendor-hosted, so data reaches a third party — enumerate these with their\nregion), OPERATOR-RUN (self-hosted, so no third party receives anything — state them as processing\nunder the operator's own control, never as recipients), and UNANSWERED.\n\nAn UNANSWERED provider is bound to a runtime with no declared deployment model. **Do not assume\nvendor-hosted.** It looks like the cautious reading and it is not: it publishes that a person's data\ngoes to a third party when nobody said so. Report it as not established, and name the surface —\n`providerComplianceChoices` in `wildo.saas.config.ts`.\n\n**A provider PROFILE is not a recipient.** The brief separates providers BOUND TO A RUNTIME — backend,\ncompanion, workers, minions, a frontend service, which can process the application's data — from\nprovider profiles with no runtime binding. A profile says how to reach a provider; build-time tooling\nlives there, and a coding agent operating on the workspace receives no customer records. Never name a\nprofile-only provider as a recipient. Naming one reads as caution and is a false statement about\nsomebody's data, exactly like omitting a real one.\n\nThe section joins the register to the OPERATOR SUB-PROCESSORS of the recipient population, so it tells\nyou these different things and they are not interchangeable:\n\n- a candidate WITH an entry — its declared identity and regions are available. Establish its\n deployment role before presenting it as a recipient.\n- a candidate listed **UNDECLARED** — a runtime binding has no matching processor entry. Name its\n configured function and unresolved declarations; an unanswered deployment choice remains unknown,\n not automatically vendor-hosted. `NEEDS_DECISION`, resolved by the operator.\n- a provider entry listed **STALE** — no data path reaches it from this operator any more.\n Reconcile the declaration and deployment choice; this check alone does not establish its actual\n historical processing or that all external data has been removed.\n- a provider entry listed **REGISTERED TENANT RECIPIENT** — the register names, as the operator's\n sub-processor, a vendor reached only through customers' own accounts. That entry is a false\n statement about who engaged the vendor; do not publish it as one of the operator's processors.\n\n**Completeness** — `DERIVED` per provider that is declared, `NEEDS_DECISION` per provider that is not.\nNot `NEEDS_FRAMEWORK` any more: issue #88 delivered the declaration surface, so an undeclared processor\nis an unanswered question rather than an unaskable one.\n\n**Never infer a region from a vendor's brand.** \"It is a US company\" is not a processing location, and\na transfer statement built on it is a claim about somebody's data made from a guess.\n\n**Distinguish the register declaration from its reconciliation.**\n\n| Observed state | What it establishes | What the document may say |\n| --- | --- | --- |\n| Register absent | No processor declaration was supplied | The operator has not established the register; do not infer recipients or their absence |\n| Register present with `processors: []` | The operator declares no processors | Report that declaration, then check it against runtime-bound recipient candidates; it is not independent proof that nobody receives data |\n| Recipient candidates have no matching entries, including with an empty register | The composition and declarations leave named questions unresolved | Identify the configured functions and outstanding deployment, identity or location decisions without inventing third parties |\n\nReconcile only operator sub-processors. Exclude operator-run, tenant-recipient, unreached and\nprofile-only providers; keep unanswered deployment choices visible as unanswered. `registerEstablishesNoProcessorRecipients`\nanswers the declaration question; `undeclaredProcessorRefs` answers candidate coverage. A true answer to\nthe first does not erase gaps returned by the second.\n\nName third-party recipients only when their role is established. An empty register does not justify\nan unconditional statement that third parties provide email, storage or payments. Equally, do not\nomit unresolved candidate questions and thereby imply that absence was verified. Authored recipients\nremain operator declarations whose completeness cannot be inferred from runtime bindings.\n\n\n### Concern: international transfers\n\n**Asserts** — whether personal data leaves its origin jurisdiction, to where, and under which transfer\nmechanism.\n\n**Derives from** — the processor register's regions, at BOTH levels: each declared processor and\neach processor's own subprocessors. Your brief renders them under *\"Personal data reaches processors\nin: …\"*.\n\nBoth levels, because the chain is what makes a transfer statement hard. An operator in France using a\nFrench vendor that runs on a US cloud HAS a transfer, and reading only the vendor's region misses it.\n\n**The question has three inputs, and the framework derives only one of them.** Where declared\nprocessors process is declared. Which jurisdiction is the ORIGIN is `operatingJurisdictions`. Which\nMECHANISM makes a given transfer lawful is a legal determination with a shelf life — adequacy decisions\nmove by court ruling — so the framework never computes it: the operator RECORDS it, per register entry,\nas a `transferDetermination`:\n\n- `NO_TRANSFER`, with the reason none of the entry's regions lies outside the origin jurisdictions —\n regions are free text, so this comparison is the operator's and never the framework's;\n- `TRANSFER`, with one safeguard per origin jurisdiction: the GDPR Chapter V mechanism\n (`ADEQUACY_DECISION`, `STANDARD_CONTRACTUAL_CLAUSES`, `BINDING_CORPORATE_RULES`,\n `APPROVED_CODE_OF_CONDUCT`, `APPROVED_CERTIFICATION`, or a `DEROGATION` naming its Art. 49 ground) and\n the instrument a reader could look up.\n\nThe determination sits on the ENTRY because the processor's own contract binds its onward transfers to\nits subprocessors; reaching the processor is the transfer the operator answers for.\n\n**The `international-transfers` fact is COMPUTED from those determinations** — you never declare it.\nIt carries each determined entry, the origin jurisdictions, `undeterminedRecipients` — a register entry\nwith no determination, or a configured provider the register does not establish — and `safeguardGaps`:\na declared origin a TRANSFER names no safeguard for.\n\n**Completeness** — do not round any state up.\n\n| the register | what you may state | completeness |\n|---|---|---|\n| ABSENT | nothing — where data lands is unknown, and the fact is absent | `NEEDS_CONFIGURATION` |\n| a recipient in `undeterminedRecipients` | that its transfer position is not determined; never fold it into \"no transfer\" | `NEEDS_DECISION` for that recipient |\n| declares NO processor | no personal data reaches a third party, so none is transferred THROUGH one | `DERIVED`, with the residual stated |\n| a determined entry | its transfer with the safeguard per jurisdiction, or NO_TRANSFER as such | `DERIVED`; a `safeguardGaps` entry is stated as a transfer with no safeguard recorded for that jurisdiction |\n\n**The residual is not optional wording.** \"No processor receives personal data\" establishes nothing\nabout the operator's OWN processing — its infrastructure, its staff, its own establishment. A document\nthat says \"we do not transfer data internationally\" on the strength of an empty register has answered\na larger question than it was asked.\n\n**What closes an undetermined entry** — the operator researching the vendor's data processing\nagreement and recording what it relies on, per origin jurisdiction. A vendor's DPA usually names it:\nstandard contractual clauses for EU data, the UK Addendum to them for UK data, and sometimes a\ncertification under an adequacy framework beside them. Record what the contract says, not what is\ntypical.\n\n**\"We do not transfer data internationally\" is a claim, not a default.** It may be true, and it is\ncitable when an application has declared it as a fact — but it must never be produced because nothing\nsaid otherwise. Absence of a region declaration means the region is unknown, which is the opposite of\nknowing it stays put.\n\n\n### Concern: automated decisions and AI\n\n**Asserts** — where the application uses AI, on what data, and whether any of it decides something\nabout a person.\n\n**Derives from (partial)** — the AI capabilities the application has a provider configured for:\n`AI_LLM`, `AI_EMBEDDINGS`, `AI_DOCUMENT_EXTRACTION`, `AI_CODING_AGENT`. That establishes that AI is in\nuse and for what function.\n\n**Not derivable** — whether any of it produces a **decision with a legal or similarly significant\neffect** on a person, and whether a human reviews it. Nothing in the framework declares consequence or\nhuman-review posture, and neither can be inferred from a capability being enabled.\n\n**Derives from (the consequence)** — the AI POSTURE section of your brief, per ENABLED AI capability:\nwhat it is used for, whether it `NO_DECISION` / `ASSISTS_HUMAN_DECISION` / `DECIDES_AUTONOMOUSLY`, and —\nwhere it decides anything — how a person obtains human intervention.\n\nAn application enabling NO AI capability gets a plain statement to that effect: it performs no AI\nprocessing of personal data. That is a positive, checkable answer, not a gap.\n\n**Completeness** — `DERIVED` per capability with a declared posture; `NEEDS_DECISION` per capability\nlisted OUTSTANDING. Not `NEEDS_FRAMEWORK` any more: issue #92 delivered the declaration, so an\nundeclared posture is an unanswered question rather than an unaskable one.\n\n**An OUTSTANDING capability is not a harmless one.** This is the one concern where silence is more\ndangerous than elsewhere: a notice describing AI use and saying nothing about consequence does not read\nas \"unknown\", it reads as \"nothing significant happens here\" — which is the exemption, claimed for\nfree. State the gap explicitly.\n\n**Why the distinction carries weight.** Automated decision-making with significant effects attracts\nspecific obligations — information about the logic, and a right to human intervention. A generated\nnotice must not silently claim the exemption by describing AI use without addressing consequence. The\nhonest statement says AI is used for these functions, and that whether any of it decides something\nabout a person is not yet established.\n\n\n### Concern: analytics and tracking\n\n**Asserts** — what is observed about how people use the service, and what a person's consent controls.\n\n**Derives from (partial)** — the observability and analytics capabilities the application has\nconfigured (`FRONTEND_PRODUCT_ANALYTICS`, `LLM_OBSERVABILITY`, `OBSERVABILITY_TELEMETRY`), together\nwith the consent posture: `analytics.requiresConsent` and each person's `privacy.consentedPurposes` make\n`ConsentPurpose.ANALYTICS` a real, enforced boundary rather than a stated intention — in the application,\nwhere a product-analytics provider starts only on the signed-in person's grant and is stopped on\nwithdrawal or sign-out, and on the marketing website, where one does not start until a visitor grants it.\nA consent-based provider must be stoppable in the page, so none is loaded as a `<script>` tag.\n\n**Derives from (the inventory)** — the CLIENT STORAGE section of your brief: each cookie and storage\nkey, its mechanism, purpose, necessity and lifetime, split by who sets it.\n\nThe FRAMEWORK's own entries are listed first and belong in every application's table — the cookies\n`__wildo_refresh` and `__wildo_anon_session`, strictly necessary, with lifetimes taken from the\napplication's session configuration, and the website's `__wildo_website_consent` storage key, strictly\nnecessary because it is what makes a visitor's refusal hold. **No application authored these and every application sets them**, so a table\nbuilt only from what the application declared would omit the session cookie, which is the entry a\nvisitor is most certain to have.\n\nThen, per frontend surface: its declared entries, an explicit \"sets nothing of its own\", or\nUNINVENTORIED.\n\n**UNINVENTORIED is not \"sets nothing\".** The first says nobody catalogued that surface; the second is a\npositive statement. Writing the second from the first tells a visitor they are tracked by less than they\nare, which is the under-reporting direction a notice must never fail in.\n\n**Completeness** — `DERIVED` for the capability and consent posture, and for each surface that IS\ninventoried; `NEEDS_DECISION` per uninventoried surface. Not `NEEDS_FRAMEWORK` any more: issue #91\ndelivered the declaration surface, so an uninventoried surface is an unanswered question rather than an\nunaskable one.\n\nSay both halves: which analytics are in use and what consent gates them (strong, derived, enforced), and\nwhat the table still lacks — naming the surfaces, not the concern.\n\n\n### Concern: subject rights\n\n**Asserts** — which request mechanisms the application configures, what they select and what their\nresults establish. A configured mechanism does not establish that a particular request was fulfilled.\n\n**Derives from**\n\n- `SubjectExportPurpose.ACCESS_ART_15` and `PORTABILITY_ART_20` — two selections over the declared\n subject relationships. Access includes eligible owned rows and non-owned rows referring to the\n subject. Portability applies narrower relationship and field-provenance selection. Neither is an\n unrestricted recursive export of everything reachable from an account.\n- Each participating resource's `systemAccessPolicy.exportSubject` — an explicit disclosure choice,\n checked before collection. Missing and forbidden are different decisions:\n\n| Declaration | Runtime result | Meaning for the request |\n| --- | --- | --- |\n| Absent on a participating resource | Refuses collection | A required disclosure decision is unanswered; no silently incomplete bundle is returned |\n| `ALLOWED` | Passes this disclosure gate | Relationship selection, system-read admission, field security and purpose-specific checks still apply |\n| `FORBIDDEN` on a dependent resource | Excludes that resource and records the reason | A deliberate exclusion; do not change it to ALLOWED merely to remove a reported omission |\n| `FORBIDDEN` on the subject's own resource | Refuses the bundle | The subject cannot be omitted from its own export |\n\n- `portabilityPolicy.defaultProvenance` and per-field `.portabilityProvenance(...)` — the field\n declaration overrides the resource default. `SUBJECT_PROVIDED` and `OBSERVED` values are eligible\n for portability; `DERIVED` values are excluded and reported. Unresolved provenance refuses\n portability collection rather than silently dropping fields. Explicitly forbidden resources do\n not need portability provenance for this export because their rows are not collected. Access uses\n its separate field selection; backend-only and write-only fields remain withheld.\n- Erasure: `eraseSubjectAsSystem(resourceType, rowIds)`, invoked by the application's verified request\n workflow. A contact or lead without a login can still be a data subject. Retention, relationship\n treatments and account linkage are separate declarations; inspect the receipt before claiming\n completion, including dependent execution, session resolution and incomplete external effects.\n\n**The rights a notice states are COMPUTED, in the `rights-and-complaint-route` fact.** Which rights\napply, and where a person may complain, are the law of the regime each `operatingJurisdictions` entry\nfalls under, conditioned on the declared lawful bases: portability only for purposes resting on consent\nor contract, objection only for public task or legitimate interests, withdrawal of consent only where\nconsent is the basis. The channel is `privacyContact`; the verification step is the operator's\n`subjectRequestIdentityVerification`; who answers comes from `roleAllocations` — the operator for data it\ncontrols, the customer (with the operator forwarding and assisting) for data it processes on a\ncustomer's behalf. Two regimes are known: the EU GDPR and the UK's. Their rights match article for article but their\ncomplaint routes do not — since 19 June 2026 a UK notice names a complaint to the operator itself\n(Data Protection Act 2018 s.164A, acknowledged within 30 days) and to the Information Commissioner\n(s.165(2)), and never GDPR Art. 77. State each regime's route from the fact, not from memory. A\njurisdiction no known regime reaches is named in `jurisdictionsWithoutKnownRegime`: state that its\nrights are not established here, never borrow another regime's words for it.\n\n**Completeness** — derive the configured posture from actual resource declarations and the selected\nrelationships. Describe an unresolved declaration as a configuration refusal, an explicit exclusion\nas an exclusion, and an observed request outcome from its report. Declarations alone are not runtime\nproof that a right has been fulfilled.\n\n**What resolves a missing declaration** — the owning resource explicitly declares ALLOWED or FORBIDDEN\naccording to its intended disclosure policy. Portability additionally needs a valid resource default\nor field-level provenance for the fields it would collect. Do not ask a notice author to replace a\nmissing product declaration with a free-text promise.\n\n**Never state** that an undeclared participating resource is merely omitted while the remainder is\nexported. The runtime refuses collection. Preserve deliberate exclusions and explain their recorded\nreasons; the application's request workflow owns verification, protected delivery and any necessary\nfollow-up.\n\n\n### Concern: data exit\n\n**Asserts** — what a customer gets back when they leave, in what form, and what happens to what\nremains.\n\n**Derives from** — `SubjectExportPurpose.PORTABILITY_ART_20` and the resources declaring\n`exportSubject`; the account-closure path; and each resource's `retentionPolicy.mode`, which decides\nwhether a record is removed or **retained and impersonalized** on erasure.\n\n**Completeness** — `DERIVED` for the mechanism.\n\n**Retained-and-impersonalized is the part a reader must not be surprised by**, and the part a\ngenerated document most often gets wrong by omission. A retained row is kept, frozen, hidden from\nnormal reads and reachable only through an audited privileged path — it is not deleted. Say so. A\nnotice that implies everything is erased, when financial and audit records are lawfully retained with\ntheir personal fields scrubbed, is inaccurate in the direction that damages trust when discovered.\n\n**How LONG anything is retained is not derivable** — see the retention-and-deletion fragment.\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## `document:public.service-terms` — six concerns\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: commercial terms\n\n**Asserts** — what is sold, how it is charged, and what happens on renewal, change and cancellation.\n\n**Derives from** — the application's billing declarations\n(`saas-models` → `billing/billing-enums.shared.schemas.ts`): `ProductType`, `BillingTiming`,\n`ProrationBehavior`, `TaxCalculationMode`, plus the declared products and any usage metering.\n\n**Completeness** — `DERIVED` where billing is configured; `NEEDS_CONFIGURATION` where the application\ndeclares no products, in which case say that the commercial terms are not yet established rather than\ndescribing a plan nobody has authored.\n\n**Keep consumer and business audiences apart.** Consumer pre-contract obligations (withdrawal\nperiods, pre-contractual information) apply only when a declared audience includes consumers. A terms\ndocument that blends both into one ambiguous set is worse than one that states which audience it is\nfor — so read the declared audience before writing a single clause about cancellation rights.\n\n\n### Concern: governing law and liability\n\n**Asserts** — which law governs the agreement, where disputes are heard, and how liability is limited.\n\n**Derives from** — nothing. These are negotiated commercial and legal positions.\n\n**Completeness** — `NEEDS_DECISION`.\n\n**What closes it** — the operator deciding, with counsel. Note that liability limits interact with\nthe declared audience: consumer-facing terms cannot limit liability as freely as business-to-business\nones, so this fragment cannot be settled before the commercial-terms fragment establishes who the\nterms are for.\n\n**Never produce a liability clause from a template.** A limitation of liability that was copied\nrather than decided is either unenforceable or committing the operator to something nobody agreed —\nand unlike most gaps in a produced document, this one is not discovered until it matters.\n",
|
|
28
|
+
"guidance": "# Compliance document candidate method\n\nYou are drafting ONE governed document for this application, from what the application has already\ndeclared. Follow the `compliance-document-authoring` skill for the rules — its full text is in your\nbrief, under \"The skills this method tells you to FOLLOW\", because this step has no tools and cannot\nopen a file. This method says which document, what shape, and what the two closed vocabularies are.\n\n## Choose the document, from the two this lane may draft\n\n`documentRef` must be one of six and the contract refuses anything else, but only two of the six are\nYOURS. The four internal `governance.*` documents belong to `refinement.governance-document-candidate`,\nwhich ships their blueprints; drafting one here would mean writing a document whose obligations you were\nnever given.\n\n| `documentRef` | what it is | drafted by |\n|---|---|---|\n| `document:public.privacy-notice` | what personal data the application holds and what happens to it | **this lane** |\n| `document:public.service-terms` | the commercial and service relationship | **this lane** |\n| `document:governance.scope-system-description` | what the system IS, for an assurance reader | `refinement.governance-document-candidate` |\n| `document:governance.roles-responsibilities` | who is accountable for what | `refinement.governance-document-candidate` |\n| `document:governance.program-handbook` | how the governance program runs | `refinement.governance-document-candidate` |\n| `document:governance.document-record-control` | how governed documents are themselves controlled | `refinement.governance-document-candidate` |\n\n**Draft a document this application does not already hold.** The run tells you which those are: the\nbrief opens with what the application has already drafted, listing each document it may produce here\nas ALREADY DRAFTED or not yet drafted. Drafts are keyed by `documentRef`, so drafting one that is\nalready there REPLACES it — right when that draft is wrong, and a wasted 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, the **privacy notice** comes first: it is the one every application holding\npersonal data needs. Where none remains, the honest reason to draft again is that a held draft is\nwrong — say which one and why in your own reasoning, rather than redrafting the first on the list.\n\nThis paragraph used to read \"draft the privacy notice unless the run tells you otherwise\", at a time\nwhen no run told it anything. Measured against a real application on 2026-09-16: with its privacy\nnotice already drafted, two consecutive runs meant to produce the service terms drafted the notice\nagain and replaced it, and the application finished each run holding exactly what it started with.\nThe second sentence was stale as well — it said the privacy notice was \"the only one whose facts the\ncurrent derivation supplies\", which stopped being true once the fact-declaring playbook began\ndeclaring the account, billing and AI facts the service terms rest on.\n\nNaming a document outside this set is not a smaller decision than it looks. Each of the six has a\nconcern composition the framework measures a draft against, so a seventh name is a document nobody can\nstate the gaps in — and stating the gaps is the whole point.\n\n## One section per concern, and SAY which concern\n\nEvery section carries `concernRef`, from the closed compliance-concern vocabulary. **The composition\nfor each document is inlined at the end of this method** — one entry per concern, saying what it\nasserts, what in the application it derives from, what state it usually reaches, and what closes it\nwhen it cannot. Draft one section per concern, in the order given, and produce **every** one:\na concern nothing can answer becomes a section with a marked clause, never a missing heading.\n\nThose entries are the difference between a draft that states its gaps and one that guesses at them.\nWhere a concern's entry names an issue number as the remedy, say so in `incompleteness.closedBy` —\n`#89`, `#91` — because a numbered issue is a remedy a reader can open, and \"application configuration\nowner\" is not.\n\nUse `concernRef: null` only for a section that genuinely answers no concern: a preamble, a contact\nblock. It is not a way past a concern you found hard. A concern you cannot establish gets a SECTION,\nwith a clause marked incomplete — which is the mechanism this whole document exists around.\n\nThe value must be the concern's exact name. A near miss (`retention` for `retention-and-deletion`) is\nworse than a null: it reports the concern as unaddressed while the document addresses it.\n\n\n## And SAY which required parts the section supplies\n\nEvery section also carries `satisfiesSectionRefs`: the refs, from the document definition rendered in\nyour brief, that this section actually addresses. This is a different question from `concernRef` and\nboth are answered — the concern says what compliance TOPIC the section is about, the satisfied refs\nsay what part of THIS document it supplies.\n\nYou are asked for the join because you are the only reader that holds both. The concern set is one\nflat vocabulary spanning every document type; the required parts are defined per document, and the\nsame concern does not sit under the same heading in a privacy notice and a governance handbook. A\nmapping written once in the framework would have to pick one answer and be wrong somewhere.\n\n- A section may claim several refs, and several sections may claim one between them.\n- A section that answers no required part — a preamble, a contact block — answers `null`. Not an\n empty list: `null` and `[]` would be two spellings of one state, and the contract refuses the second.\n- **Claim honestly.** A required ref nobody claims is reported as a part the document may not address,\n which is a true and useful finding. Claiming one you did not address hides that, and nothing\n downstream reads your prose to catch it.\n\nDo NOT adopt the definition's refs as your own `sectionRef` values. Your section set is the concern\nrule above; these are a claim you attach to it, not names you take.\n\n**Clauses carry the same claim**, as `satisfiesClauseRefs`, and answer `null` the same way. Your brief\nlists the blueprint's clauses under each section, each marked REQUIRED or CONDITIONAL; name the ones\nyour clause supplies.\n\nBoth keys were ASKED FOR HERE and absent from the strict contract you answer until 2026-09-02, so a\ndraft that followed this section could not parse and every landed document claimed nothing. If you\nare reading a document produced before then, its empty coverage is that defect and not a finding\nabout the document.\n\n- Several of your clauses may supply one blueprint clause between them, and one clause may supply\n several.\n- A clause supplying none — a transition, a heading gloss — claims none.\n- **Only the clauses marked REQUIRED are owed.** A CONDITIONAL clause is supplied when its condition\n holds and correctly omitted otherwise, so leaving one unclaimed is not a gap.\n\nThis is the anchor a clause did not previously have. A fact is named by the catalog and a section\ncarries its concern, so both survive a redraft; a clause was named freely and joined to nothing, which\nis why a reviewer who approved one could not find it in the next revision.\n## What a clause may say\n\nThe rule is ASSERT versus MARK, and the skill states it in full. In short: a clause may say \"this is\nnot yet established\"; it may not say something untrue.\n\n- `DERIVED` — established by a fact this application has declared. Cite it in `factRefs`. A `DERIVED`\n clause citing a fact the facts file does not declare is REFUSED before the write.\n\n **This is decided against the facts file as it stands NOW, not against any earlier draft.** You are\n producing the whole document from what the application currently declares, so a concern the facts\n answer today is `DERIVED` today — even if a previous version of this document marked it incomplete\n and is still in the tree. Re-running this playbook is how a document that went stale is repaired,\n and it only repairs anything if the re-draft is willing to close a mark.\n\n **Never fold a declared fact into a marked clause.** When one concern has a declared half and a\n missing half — retention periods declared while retention enforcement is not evidenced, a\n processor register that names most recipients while some providers have no recorded identity —\n write TWO clauses: a `DERIVED` clause stating what is declared, and a separate marked clause naming\n what is missing. A clause is marked as a whole, so one clause carrying both states nothing: every\n clause citing the declared fact is then incomplete, and the standing coherence report correctly\n records that the document mentions the fact without stating it. A redraft that marked its retention\n and recipients clauses because each also carried a gap stopped stating two facts the previous draft\n had stated.\n\n **A fact the application declared NOT APPLICABLE is a fact, and a clause may rest on it.** *\"No\n external analytics provider is configured\"* is `DERIVED`, not incomplete: the application settled the\n question and recorded the answer. Marking such a concern incomplete says the application does not\n know something it does know, which is as wrong as overstating. What is refused is citing a fact the\n facts file does not declare AT ALL.\n- `NEEDS_FRAMEWORK` / `NEEDS_DECISION` / `NEEDS_CONFIGURATION` — mark it, and say in `incompleteness`\n what is missing and who closes it. Four distinct suppliers, four distinct remedies; do not merge them.\n\n **When what is missing is a FACT, name it in `incompleteness.awaitingFactRefs`.** The skill argues\n this in full; the short version is that a marked clause asserts an ABSENCE in the application's own\n configuration, and that assertion goes false the moment someone declares the thing — silently, since\n nothing about the document changes. The awaited ref is what lets generation, landing and the\n standing coherence report all say the clause has gone stale. A clause that awaits nothing rots\n unobserved, and one already has.\n\n **`NEEDS_DECISION` and `NEEDS_FRAMEWORK` are the pair most easily confused, and the difference is\n the REMEDY.** `NEEDS_DECISION` means a surface exists and nobody filled it in — the reader goes and\n answers. `NEEDS_FRAMEWORK` means there is NOWHERE to record the answer; telling a reader to decide\n is telling them to write into a void.\n\n Measured on 2026-08-30, a produced notice marked operator identity `NEEDS_DECISION` when no surface\n for it existed at all, beside retention periods marked identically and genuinely just unfilled. Two\n remedies, rendered the same, and a reader could act on neither.\n\n **So every incomplete clause must NAME THE SURFACE its answer goes to**, or say plainly that none\n exists. A gap with a named surface is a task; a gap without one is a request for work nobody has\n scoped. The fragment you are working from names the surface where there is one — carry it into\n `incompleteness` rather than leaving the reader to find it.\n\n **`closedBy` must name WHO can reach that surface, and an ENGINE resource is not the application\n author's to edit.** `retentionPolicy`, `systemAccessPolicy.exportSubject` and `.dataCategories()`\n on an engine resource live in engine source. Writing \"application authors must declare\n `retentionPolicy` for each affected engine resource\" hands the reader a task they cannot perform —\n and a produced notice said exactly that, for 83 resources, in the same confident register as the\n remedies that ARE actionable. An unreachable remedy is worse than an unnamed one: it looks like\n work, gets scheduled, and fails when someone tries it.\n\n Where the closer is the FRAMEWORK, say so plainly — \"the framework must declare these on its own\n resources\" — and keep it separate from what this application owes.\n\nNever fill an unresolved fact, infer a legal decision, or describe the draft as approved, compliant,\nlegally valid, released or published. Locale and jurisdiction are review inputs; leaving them\nunresolved is a legitimate answer and never a reason not to draft.\n\n**And the mirror of that, which matters just as much: a missing approval never stops you.** Approval\nhappens at the END and is a human commit; a downstream release can be composed and MARKED\n`UNAPPROVED`. So the absence of one is a STATE to record, never a reason to produce nothing and never\nan outcome to report as blocked. The two failures are symmetric — claiming an approval that did not\nhappen, and refusing to act because it has not happened yet — and a compliance workflow standing in\nfront of the application-creation mechanism is the second one.\n\n## The refs you write, and their exact shape\n\nEvery `…Ref` field is a **namespaced ref**: `namespace:slug`, both halves lowercase, words joined by\nhyphens. `clause:retention-duration-not-declared` is one; `clause:Retention Duration` is not, and a\nwhole draft is rejected for a single malformed one. Ref ARRAYS are arrays of those strings — never\nobjects, never `{ ref: … }`.\n\nPer clause, all three ref arrays are required. Two of them may be empty, but **not both of the\nfirst two at once** — a clause that names no fact and no policy is sourced by nothing and is\nrejected:\n\n- `factRefs` — the facts this clause rests on, exactly as the facts file declares them. It may be\n EMPTY for a clause that establishes nothing (a marked clause often does).\n- `sourcePolicyRefs` — the application POLICY AREA the statement is sourced from, and nothing else.\n Every entry must be in the `policy:` namespace (`policy:retention`, `policy:recipients`,\n `policy:security-controls`); any other namespace is rejected outright. **Do NOT put a fact\n authority here.** A clause resting on declared facts already cites its authorities through\n `factRefs`, which resolves them — repeating them here duplicates the citation beside it and\n resolves to nothing. So this array is EMPTY for a fact-backed clause, and carries a policy area\n for a clause that is sourced from a policy rather than from a fact.\n- `claimGuardRefs` — at least one: what this clause must NOT be read as claiming. These are the\n boundaries you are already holding — `claim-guard:no-legal-applicability-claim`,\n `claim-guard:no-invented-retention-period`, `claim-guard:known-fact-only`. Name the ones that apply\n to this clause; do not repeat the same guard on every clause out of habit. You do not name the\n CATALOG's guard for the material: it is added for you from the blueprint clauses this clause\n `satisfiesClauseRefs`, so a clause that says what it satisfies is checked against it automatically.\n\n`evidenceRefs` is **`null` on every clause of a public document**, and that is not a gap to work around.\nIt cites a judged run from this application's own assurance repository — self-attested internal\nevidence — and a public notice may carry none, whatever the run says: a reader of one cannot weigh an\noperator's judgement of its own product, and any citation here is refused before the draft becomes a\nfile. That evidence belongs to the internal governance documents, which\n`refinement.governance-document-candidate` draws. Where you would have leaned on a measurement, say\nwhat is CONFIGURED or DECLARED, or MARK the statement.\n\n**The same holds when a FACT is phrased as behaviour, and that is where drafts go wrong.** The facts\nyou cite describe the product in the present tense — *\"the running application reaches\"*, *\"the\nframework sets\"*, *\"acceptance joins the member\"*, *\"kept 30 days, then erased\"* — which is accurate\nfor a fact and is an operating claim in a public notice. Do not carry the verb across: restate each as\na declaration (*\"the configuration enables\"*, *\"the framework declares\"*, *\"the configured membership\nmodel admits\"*, *\"the declared period is 30 days, after which the data is due for erasure\"*). The\njudge reads every clause of a public document for exactly this, and a sentence copied from a fact is\nthe one it finds.\n\n`reviewChecklistRefs` needs at least one (`review-checklist:<slug>`) — what a human must confirm before\nthis draft is worth anything. `limitationRefs` may be empty, but rarely should be: it is where you say\nwhat the document does NOT cover, in your own words as the drafter, rather than leaving the reader to\ndiscover it.\n\n## You do not compose the release — and a release nobody approved is marked UNAPPROVED\n\nYou draft the candidate. You do NOT author its release, and that is a boundary rather than an\nomission: almost everything a release carries is DERIVED from the accepted document definition — the\ndocument's class, who it addresses, which channels may carry it, which interactions it permits — and\na model restating those would create five ways to disagree with the catalog, invisibly. The rest\n(which declared variant, when it takes effect) is a composition over families you are not holding.\n\nA human declares a release DECISION in the application's\n`specifications/src/document-releases/compositions.ts`, and `wildo config document-releases` composes\neach decision not yet recorded — your candidate plus the declared variant and release policy — and\nrecords the finished release, text included. Nothing records a release because you landed a draft: an\napplication with no decision holds no release yet, which is a valid state and not yours to fix from\nthis playbook. Until a public document (privacy notice, service terms) has a release, its public page\nshows your latest draft, marked as a draft — so what you mark as not established is what a reader sees.\nWhat matters for your work is what composition produces when it runs: a release carrying\n`approvalState`, and one nobody has approved is `UNAPPROVED` and exists anyway.\n\n**Which is why a missing approval never changes what you do here.** Draft the document completely,\nmark every statement you cannot establish, and let the release be composed and marked. Waiting for an\napproval before drafting — or describing a draft as approved to get past the gate — are the two\nsymmetric failures, and the first is a compliance workflow standing in front of the mechanism that\nbuilds 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. It is\naccepted by a commit and by nothing else; who makes that commit is the host's autonomy posture, and\nonly a PERSON's commit is an approval. Landing is not approval, release or publication — and neither is\na commit the development companion authors under the YOLO posture.\n\n\n---\n\n# The compositions\n\nEach of the following is one document's full concern list. Use the one matching your `documentRef`\nand ignore the rest.\n\n## `document:public.privacy-notice` — thirteen concerns\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\n\n### Concern: legal basis and controller/processor role\n\n**Asserts** — the lawful basis for each processing purpose, and whether the operator acts as\ncontroller or processor for it.\n\n**Derives from** — `operatorComplianceIdentity.lawfulBases` and `.roleAllocations` in\n`wildo.saas.config.ts`.\n\nThe DETERMINATIONS are never derivable — both are legal conclusions about the operator's own\narrangements, and the framework can show WHAT is processed and BY WHICH MECHANISM without establishing\nunder which basis or in which role. What it now provides is where to record the conclusion, so that a\nregeneration reproduces it instead of destroying it.\n\n**The role is a LIST, not a field, and the produced notice said so before the surface existed:**\n*\"This notice therefore does not assign a single legal role to all data processed in a workspace.\"* A\nB2B SaaS is typically a processor for the records its customers put in and a controller for its\naccount holders' own data, simultaneously. `roleAllocations` carries one role per population, and a\ndocument that collapses them into one is wrong about both.\n\n**The `lawful-bases` fact is COMPUTED from `lawfulBases`** — every purpose, its basis and, for\nlegitimate interests, the assessment. You never declare it: a restatement would be a second copy of the\noperator's decision that nothing compares with the first. Absent bases leave the fact absent.\n\n**Give each purpose a stable `purposeRef`** (`account-security`) when a recipient serves it. A vendor\nnames the purposes it serves in `providerComplianceChoices.<ref>.purposeRefs`, and the recipients fact\njoins the two. The prose `purpose` can then be reworded without breaking the link; a ref naming no\ndeclared purpose is reported, never refused.\n\n**`LEGITIMATE_INTERESTS` cannot be declared without its assessment** — the schema refuses it. It is\nthe only Art. 6(1) basis whose lawfulness depends on a balancing test, so the bare claim asserts a\nconclusion nobody reached.\n\n**Completeness** — `DERIVED` when declared; `NEEDS_DECISION` when not. Never `NEEDS_FRAMEWORK`: there\nis a surface, so the remedy is to fill it in, not to build something. Name the surface when reporting\nthe gap.\n\n**What closes it** — the operator determining, per purpose, the basis and the role, ideally with\ncounsel, and declaring them in `operatorComplianceIdentity`. The tenancy fragment describes the SHAPE this usually takes in a B2B SaaS — processor for\nthe data a customer stores about its own people, controller for the data the operator holds about\naccount holders — but describing the common shape is not the same as determining this operator's, and\nthe produced document must not present the first as the second.\n\n**This is the fragment most likely to be filled in by a confident guess**, because the shape is\nfamiliar and the sentence is easy to write. Resist it. A basis stated in a published notice is a\nposition the operator has taken; a basis that was never determined is a position nobody can defend.\n\n\n### Concern: personal data held\n\n**Asserts** — which of the application's own records are about identifiable people, and which hold no\npersonal data of their own.\n\n**Derives from** — each resource's `retentionPolicy.mode` (`ErasureRetentionMode`, in\n`@wildo-ai/saas-models`), read for every resource the application declares:\n\n| declaration | what the document may state |\n|---|---|\n| `RETAIN_AND_IMPERSONALIZE` | this record holds personal data; the fields marked `.impersonalizeWith()` are what is scrubbed on erasure |\n| `RETAIN_ONLY` | this record holds **no personal data of its own** — a positive, factory-enforced statement, because declaring a scrub treatment under this mode fails at config build |\n| absent | the application has not said |\n\nRead `dataSubjectPolicy.kind` for the SESSION question only. `NO_PRINCIPAL` is equally true of an\ninvoice and of a CRM contact, so it never tells you whether a record is about a person — the\nretention mode does.\n\n**Completeness** — `DERIVED` for every resource that declares a retention policy.\n\n**An erasure-coverage gap does NOT license a claim about whether personal data is held.** The two are\ndifferent axes and the facts report them separately: `retentionPolicy` answers *what happens to this\nrow on erasure*, while a field's `.dataCategories()` answers *what kind of data is in it*. A resource\ncan declare the second and not the first, and 48 of the engine's 85 do.\n\nSo writing \"N resources have no declared erasure treatment, so this notice cannot establish whether\nthey hold personal data\" is an over-reach, and it contradicts the data-categories section of the same\ndocument — which enumerates categories drawn from those very resources. It was produced twice on\n2026-08-30 before this paragraph existed.\n\nState the gap as what it is: those resources have not declared an erasure TREATMENT, so a notice\ncannot say what an erasure does to them. Where the facts also report a category coverage for the same\norigin, say what IS established alongside it.\n`NEEDS_CONFIGURATION` for every resource that does not.\n\n**What closes it** — the application's own authors declaring `retentionPolicy`, with the `dataSubjectPolicy` the\nfactory requires beside it, on the resource. Name\nthe resources individually: the remedy is per-resource, and a count is not actionable.\n\n\n### Concern: data categories\n\n**Asserts** — which CATEGORIES of personal data are held: identity, contact details, credentials,\nfinancial, usage, location, user content, professional, and any GDPR Art. 9 special-category or\nArt. 10 criminal-offence data.\n\n**Derives from** — each field's `.dataCategories()` declaration, reported per resource and unioned\nacross the application in the compliance-primary-facts section. One category is DERIVED rather than\ndeclared: `credentials`, from `.isPassword()` / `.isOtp()` / `.isWriteOnlySecret()`, which are\nmarkers the author already wrote.\n\n**Nothing is derived from a field NAME.** `email`, `phone` and `dateOfBirth` are suggestive while\n`notes` is not, so a category list assembled by pattern-matching identifiers is a guess presented as\nan inventory — and its failure mode is silent, because whatever the guess misses is simply not\ndisclosed. The declaration exists so that never happens.\n\n**Completeness** — `DERIVED` when the application declares categories; `NEEDS_CONFIGURATION` when it\ndeclares none, or when the facts section lists OUTSTANDING fields.\n\n**The two gaps are different and must not be written the same way.**\n\n- A resource that declares no category at all may genuinely hold no personal data. Nothing\n distinguishes \"considered and not applicable\" from \"never asked\", so state that the question is\n unanswered — never that the application holds no personal data.\n- A field the facts section lists as OUTSTANDING is a provable omission. The application already\n declared that field personal by another door — an erasure scrub treatment, a portability\n provenance, or a credential marker — so the missing category is an omission, not a judgement.\n Name the field and its basis. Do not guess what it contains.\n\n**Say WHICH special category, not that there is one.** A `special-category:*` value is Art. 9 data\nand carries a lawful-basis condition of its own beyond Art. 6; `criminal-offence` is Art. 10, a\nseparate article with a different condition. \"We process special category data\" is not a disclosure —\nthe enum names the kind precisely so a notice can.\n\n**Do NOT point at `Compliance_DataClassification`.** It exists, it is a four-level SENSITIVITY ladder\n(public / internal / confidential / restricted) applied only to flows-actors configuration, and it\nanswers \"how protected must this be\" rather than \"what kind of personal data is this\". Using it here\nwould produce a notice describing protection levels where a reader expects data types. It is named\nexplicitly because it is a near-miss a reader will otherwise find and assume answers this concern.\n\n\n### Concern: consent and preferences\n\n**Asserts** — what the application asks consent for, at what granularity, and what a person's choice\nactually controls.\n\n**Derives from**\n\n- `ConsentPurpose` (`@wildo-ai/saas-models`): `ANALYTICS` · `MARKETING` — a SET of purposes, each\n granted or not on its own. There is no ordering: agreeing to marketing says nothing about analytics.\n- per-person `privacy.consentedPurposes` — the purposes each person granted, empty until they grant\n one — and `privacy.consentDecidedAt`, stamped by the server when they decide. An empty set WITH an\n instant is \"declined everything\"; no instant is \"never asked\". A notice must not state the second\n as the first.\n- `analytics.requiresConsent` (default `true`) — whether the application's analytics rest on\n `ANALYTICS`. It governs analytics alone, never use of the service.\n- the visitor tier: a marketing website keeps a visitor's decision in their browser and starts a\n consent-based provider (product analytics) only once its purpose is granted.\n\n- `operatorComplianceIdentity.serviceConsentRequirement` (`wildo.saas.config.ts`) — what a person\n must agree to in order to use the service AT ALL, and what that gate covers.\n\n**An empty `requiredPurposes` is a POSITIVE answer and the usual one.** The operator declaring that nothing is gated on\nconsent has answered the question; a document must state it as settled rather than treating it as an\nabsence. ABSENT is the different case — nobody was asked — and the brief distinguishes the two.\n\n**A consent GATE is not a lawful BASIS.** For most B2B SaaS the basis for core processing is CONTRACT:\na person uses the product because their employer signed for it. A notice that reads a gate as a basis\nstates that their data is processed on consent they could withdraw, which is wrong about the single\nmost consequential thing in the document. The basis is declared per purpose in `lawfulBases`.\n\n**Completeness** — `DERIVED` for the analytics gate, each person's granted purposes, and the\nservice-wide requirement once declared — which the application ENFORCES: until the required purposes are\ngranted, the backend refuses every operation the person initiates — API and MCP operations, queued work,\nWebSocket reads and subscriptions, agent tools, retrieval, charts and analytics, A2A task reads, and A2A or\nWebSocket conversations, including resuming one after an approval — except their own profile and preferences,\nwhere they record the consent, and cancelling an A2A task they already started (signing in and out stay open;\nupdates the server pushes on its own are not held back), and the web\napplication withholds its pages; `NEEDS_DECISION` naming `serviceConsentRequirement` when it is not.\n\nThis was `NEEDS_FRAMEWORK` until 2026-08-30, correctly: there was nowhere to record the answer. Issue\n#139 built the surface, so the remedy changed from \"someone must build this\" to \"fill this in\" — a\ndifferent party and a different task, which is why the two states are never interchangeable.\n\n**Say the thing readers get wrong.** Consent is one lawful basis among several, and it is not the one\nmost B2B processing rests on. **Never write that all processing rests on consent, and never write\nthat accepting terms supplies a lawful basis** — accepting a contract is a different basis with\ndifferent consequences, and conflating them is the single most common defect in a generated privacy\nnotice. Which basis applies is a `NEEDS_DECISION`; see the legal-basis fragment.\n\n\n### Concern: retention and deletion\n\n**Asserts** — what happens to a record when its subject is erased, and how long records are kept.\n\nTwo questions, and the framework answers both — the second only for the resources bound to a class.\n\n**Derives from (the HOW — answerable)** — each resource's `retentionPolicy.mode`:\n`RETAIN_AND_IMPERSONALIZE` keeps the row, freezes it, hides it from normal reads and scrubs the fields\nmarked `.impersonalizeWith()`; `RETAIN_ONLY` keeps and freezes a row that holds no personal data of\nits own. Reading the per-field treatments tells the document exactly WHICH values are destroyed and\nwhich survive, which is a genuinely strong statement most notices cannot make.\n\n**Records a statute keeps survive an erasure RESTRICTED, and the request still completes.** A resource\nbound to `BUSINESS_RECORDS` declares `retentionPolicy.statutoryRetention`: the GDPR Art. 17(3)(b) ground\n(`LEGAL_OBLIGATION`) and the statute in the operator's words. An erasure erases everything else, keeps\nthose rows retained and hidden from any other processing until their statutory period ends, and lists\neach one with its ground and end date — which is what the notice must say: that some records are kept\nbecause the law requires it, which law, and that they are deleted when the period ends. The\n`retention-rules` fact names these resources and their statute under each erasure treatment. Never write\nthat an erasure is refused or delayed because of them.\n\n**Derives from (the HOW LONG)** — the application's `dataRetention` schedule, declared in its config\nover five data classes: `RESOURCE_DATA` (its records), `FILES` (uploaded bytes), `AUDIT_LOGS` (the\ntamper-evident trail, kept longest and for a different reason — it is the evidence an operator may\nlawfully retain under GDPR Art. 17(3)), `OPERATIONAL_LOGS`, and `BUSINESS_RECORDS` (records a statute\nrequires to be kept for a minimum period). Each declared class carries a period in days AND the\noperator's stated reason for it.\n\n**Enforced where a resource is BOUND** — a resource declares `retentionBinding: { retentionClass,\nstartPoint }`, and the retention sweep deletes its rows once the period has passed since the start point\n(the account closing, the record closing, its creation, the end of its calendar year). The period is\ncounted from when the record stops being needed, so a live record is never deleted for its age. The\n`retention-rules` fact names, per class, the resources bound to it and the MECHANISMS that act on it:\n`RETENTION_CLASS_SWEEP`, `FILES_CLEANUP` (file bytes after their row is gone), `AUDIT_ARCHIVAL`. An EMPTY\nmechanism list means nothing is even wired to enforce the class — say exactly that. `AUDIT_ARCHIVAL` means the audit\ntrail is archived after the period and is NEVER deleted: do not write that audit records are deleted.\nThe fact also names the resources bound to no class — kept until erased, because nobody decided otherwise.\n\n**Whether a period IS enforced is a different fact** — `retention-enforcement`, computed from the records the\nretention sweep writes on every run (runtime evidence, not a declaration). Per declared class it reads\n`ENFORCED` (every bound resource shows a recent completed or deferred run), `DECLARED` (a period nothing has\nyet been shown to apply) or `FAILING` (the latest run of a bound resource failed). Say a period is enforced\nONLY where it reads `ENFORCED`, and as of its `observedAt` — and only for the resources bound to the class:\n`mechanismsNotEvidencedByTheseRecords` names what the records cannot see (the audit trail's archival, the files\ncleanup), so never write that the audit trail's or the files' retention is evidenced by this fact. A mechanism in `retention-rules` says the sweep\nWILL act; only this fact says it did. When the fact is absent the records were not collected: say enforcement\nis not yet evidenced, never that it is not happening.\n\nThe classes are the STORES on purpose: the same declaration answers what a notice must state and what\na backup-and-restore inventory must protect (issue #8).\n\n**The `retention-rules` fact is COMPUTED from both** — the declared periods with their reasons and\nmechanisms, the classes with no period, each resource's declared erasure treatment, the resources\ndeclaring none, and the resources bound to no retention class.\nYou never declare it. It is absent when no schedule is declared, because a treatment alone would read as\nthe whole answer.\n\n**Completeness** — `DERIVED` for the treatment, and for each retention class the application HAS\ndeclared. `NEEDS_DECISION` for each class it has not: the mechanism exists, so what is missing is an\noperator's decision rather than an engine change. Do not let the derivable half hide the missing one —\na statement about erasure mechanics reads to a reader as an answer about retention, so both go in the\nsame breath.\n\n**What closes it** — the operator deciding a period, and saying why. Not a framework change: issue #89\ndelivered the declaration surface, so an undeclared class is now an unanswered question rather than an\nunaskable one.\n\n**An UNDECLARED class is not \"kept indefinitely\" and not \"deleted immediately\".** It is a decision\nnobody has taken, and the document must say exactly that.\n\n**A legal hold suspends every deletion of its scope** — the retention sweep, an erasure, the tenant purge,\nfile bytes — until the tier that placed it releases it (`legalHolds`). The notice may say that data is kept\nbeyond its period while a legal claim, an investigation or a legal obligation requires it, and that it is\ndeleted once that ends. Never write that a hold expires, and never name a matter.\n\n**Never write a placeholder period.** \"Typically 12 months\" in a published notice is a commitment\nnobody made and nothing enforces.\n\n\n### Concern: recipients and processors\n\n**Asserts** — who else receives personal data, in what role, and where they process it.\n\n**Derives from (who receives)** — the RECIPIENT POPULATION, which your brief renders under *\"Who\nRECEIVES data, by whose account reaches them\"*. It is computed by `computeRecipientPopulation`\n(`@wildo-ai/saas-specifications/application-creation`) from the configuration and a scan of the\napplication's source, and the privacy notice's recipients fact and the assurance evidence read the SAME\npopulation, so none of them can disagree with the others. Every provider declared under a runtime scope\n(`backend`, `frontendServices.<service>`, `minions.<minion>`, `workers.<worker>`) and every\n`systemsOfRecord` instance lands in exactly ONE of four classes:\n\n| Class | What it means | What the document does with it |\n| --- | --- | --- |\n| **OPERATOR-RUN** | an explicit `SELF_HOSTED` compliance choice | processing under the operator's own control — never a recipient |\n| **OPERATOR SUB-PROCESSOR** | some data path spends the APPLICATION's own account (an engine capability, a wired capability role, a typed client, a browser operation, a system of record) | the operator's recipient; it belongs in the processor register |\n| **TENANT RECIPIENT** | reachable ONLY through a customer's or a person's own connected account | the customer's own vendor, reached at the customer's instruction. Never the operator's sub-processor; you may say a customer can connect its own account |\n| **DECLARED, NO DATA PATH** | configured, and nothing in the application reaches it | receives nothing. Never name it as a recipient; the gap is the declaration itself |\n\nAn engine capability is ONE data path, not the definition of a recipient: a catalogue vendor called\nthrough its typed client receives data with no capability at all, and a vendor declared \"to exercise the\nloading chain\" with nothing calling it receives nothing. The tenant class matters most when the operator\nis a PROCESSOR for the data: listing a customer's own vendor as its sub-processor states an engagement the\noperator never made. The function and its limits are in the `compliance-document-authoring` skill's\n`references/framework-recipient-population.md`.\n\n**Derives from (the identities)** — the application's PROCESSOR REGISTER, which your brief renders\nunder *\"Who else processes personal data\"*. Per entry: the processor's **legal entity**, the\n**regions** it processes in, and its own **subprocessors** with their regions.\n\n**The register holds two kinds of entry and the brief labels them differently — say which.** A\nCONFIGURED PROVIDER entry joins to the application's composition, so it can be checked against it: a\nclaim about a provider the application does not configure is detectable, and a configured provider\nwith no entry is reported as UNDECLARED. An AUTHORED entry — a hosting company, a CDN, a support desk\n— joins to nothing, because no configuration mentions it. The framework can neither confirm it nor\nnotice its absence.\n\nBoth kinds of declared relationship can belong in the notice when their role is established. What\nmust not happen is presenting the second with the authority of the first: an authored entry is the operator's word, and a document that reads\nas though the framework verified it overstates what anyone checked.\n\n**A SELF-HOSTED provider is not a recipient either, and this is the second way to get the section\nwrong.** The brief's *\"Who RUNS each bound provider\"* block splits the members the OPERATOR answers\nfor (operator sub-processors and operator-run) three ways:\nTHIRD-PARTY RECIPIENTS (vendor-hosted, so data reaches a third party — enumerate these with their\nregion), OPERATOR-RUN (self-hosted, so no third party receives anything — state them as processing\nunder the operator's own control, never as recipients), and UNANSWERED.\n\nAn UNANSWERED provider is bound to a runtime with no declared deployment model. **Do not assume\nvendor-hosted.** It looks like the cautious reading and it is not: it publishes that a person's data\ngoes to a third party when nobody said so. Report it as not established, and name the surface —\n`providerComplianceChoices` in `wildo.saas.config.ts`.\n\n**A provider PROFILE is not a recipient.** The brief separates providers BOUND TO A RUNTIME — backend,\ncompanion, workers, minions, a frontend service, which can process the application's data — from\nprovider profiles with no runtime binding. A profile says how to reach a provider; build-time tooling\nlives there, and a coding agent operating on the workspace receives no customer records. Never name a\nprofile-only provider as a recipient. Naming one reads as caution and is a false statement about\nsomebody's data, exactly like omitting a real one.\n\nThe section joins the register to the OPERATOR SUB-PROCESSORS of the recipient population, so it tells\nyou these different things and they are not interchangeable:\n\n- a candidate WITH an entry — its declared identity and regions are available. Establish its\n deployment role before presenting it as a recipient.\n- a candidate listed **UNDECLARED** — a runtime binding has no matching processor entry. Name its\n configured function and unresolved declarations; an unanswered deployment choice remains unknown,\n not automatically vendor-hosted. `NEEDS_DECISION`, resolved by the operator.\n- a provider entry listed **STALE** — no data path reaches it from this operator any more.\n Reconcile the declaration and deployment choice; this check alone does not establish its actual\n historical processing or that all external data has been removed.\n- a provider entry listed **REGISTERED TENANT RECIPIENT** — the register names, as the operator's\n sub-processor, a vendor reached only through customers' own accounts. That entry is a false\n statement about who engaged the vendor; do not publish it as one of the operator's processors.\n\n**Completeness** — `DERIVED` per provider that is declared, `NEEDS_DECISION` per provider that is not.\nNot `NEEDS_FRAMEWORK` any more: issue #88 delivered the declaration surface, so an undeclared processor\nis an unanswered question rather than an unaskable one.\n\n**Never infer a region from a vendor's brand.** \"It is a US company\" is not a processing location, and\na transfer statement built on it is a claim about somebody's data made from a guess.\n\n**Distinguish the register declaration from its reconciliation.**\n\n| Observed state | What it establishes | What the document may say |\n| --- | --- | --- |\n| Register absent | No processor declaration was supplied | The operator has not established the register; do not infer recipients or their absence |\n| Register present with `processors: []` | The operator declares no processors | Report that declaration, then check it against runtime-bound recipient candidates; it is not independent proof that nobody receives data |\n| Recipient candidates have no matching entries, including with an empty register | The composition and declarations leave named questions unresolved | Identify the configured functions and outstanding deployment, identity or location decisions without inventing third parties |\n\nReconcile only operator sub-processors. Exclude operator-run, tenant-recipient, unreached and\nprofile-only providers; keep unanswered deployment choices visible as unanswered. `registerEstablishesNoProcessorRecipients`\nanswers the declaration question; `undeclaredProcessorRefs` answers candidate coverage. A true answer to\nthe first does not erase gaps returned by the second.\n\nName third-party recipients only when their role is established. An empty register does not justify\nan unconditional statement that third parties provide email, storage or payments. Equally, do not\nomit unresolved candidate questions and thereby imply that absence was verified. Authored recipients\nremain operator declarations whose completeness cannot be inferred from runtime bindings.\n\n\n### Concern: international transfers\n\n**Asserts** — whether personal data leaves its origin jurisdiction, to where, and under which transfer\nmechanism.\n\n**Derives from** — the processor register's regions, at BOTH levels: each declared processor and\neach processor's own subprocessors. Your brief renders them under *\"Personal data reaches processors\nin: …\"*.\n\nBoth levels, because the chain is what makes a transfer statement hard. An operator in France using a\nFrench vendor that runs on a US cloud HAS a transfer, and reading only the vendor's region misses it.\n\n**The question has three inputs, and the framework derives only one of them.** Where declared\nprocessors process is declared. Which jurisdiction is the ORIGIN is `operatingJurisdictions`. Which\nMECHANISM makes a given transfer lawful is a legal determination with a shelf life — adequacy decisions\nmove by court ruling — so the framework never computes it: the operator RECORDS it, per register entry,\nas a `transferDetermination`:\n\n- `NO_TRANSFER`, with the reason none of the entry's regions lies outside the origin jurisdictions —\n regions are free text, so this comparison is the operator's and never the framework's;\n- `TRANSFER`, with one safeguard per origin jurisdiction: the GDPR Chapter V mechanism\n (`ADEQUACY_DECISION`, `STANDARD_CONTRACTUAL_CLAUSES`, `BINDING_CORPORATE_RULES`,\n `APPROVED_CODE_OF_CONDUCT`, `APPROVED_CERTIFICATION`, or a `DEROGATION` naming its Art. 49 ground) and\n the instrument a reader could look up.\n\nThe determination sits on the ENTRY because the processor's own contract binds its onward transfers to\nits subprocessors; reaching the processor is the transfer the operator answers for.\n\n**The `international-transfers` fact is COMPUTED from those determinations** — you never declare it.\nIt carries each determined entry, the origin jurisdictions, `undeterminedRecipients` — a register entry\nwith no determination, or a configured provider the register does not establish — `safeguardGaps`:\na declared origin a TRANSFER names no safeguard for — and `operatorHostingRegions`: where the operator's\nOWN infrastructure holds the data (`operatorComplianceIdentity.hostingRegions`), or `null` when the\noperator has not declared it. State a `null` as the operator's hosting location not yet being declared;\nit never means the data is held nowhere, and it never supports \"no international transfer\".\n\n**Completeness** — do not round any state up.\n\n| the register | what you may state | completeness |\n|---|---|---|\n| ABSENT | nothing — where data lands is unknown, and the fact is absent | `NEEDS_CONFIGURATION` |\n| a recipient in `undeterminedRecipients` | that its transfer position is not determined; never fold it into \"no transfer\" | `NEEDS_DECISION` for that recipient |\n| declares NO processor | no personal data reaches a third party, so none is transferred THROUGH one | `DERIVED`, with the residual stated |\n| a determined entry | its transfer with the safeguard per jurisdiction, or NO_TRANSFER as such | `DERIVED`; a `safeguardGaps` entry is stated as a transfer with no safeguard recorded for that jurisdiction |\n\n**The residual is not optional wording.** \"No processor receives personal data\" establishes nothing\nabout the operator's OWN processing — its infrastructure, its staff, its own establishment. A document\nthat says \"we do not transfer data internationally\" on the strength of an empty register has answered\na larger question than it was asked.\n\n**What closes an undetermined entry** — the operator researching the vendor's data processing\nagreement and recording what it relies on, per origin jurisdiction. A vendor's DPA usually names it:\nstandard contractual clauses for EU data, the UK Addendum to them for UK data, and sometimes a\ncertification under an adequacy framework beside them. Record what the contract says, not what is\ntypical.\n\n**\"We do not transfer data internationally\" is a claim, not a default.** It may be true, and it is\ncitable when an application has declared it as a fact — but it must never be produced because nothing\nsaid otherwise. Absence of a region declaration means the region is unknown, which is the opposite of\nknowing it stays put.\n\n\n### Concern: automated decisions and AI\n\n**Asserts** — where the application uses AI, on what data, and whether any of it decides something\nabout a person.\n\n**Derives from (partial)** — the AI capabilities the application has a provider configured for:\n`AI_LLM`, `AI_EMBEDDINGS`, `AI_DOCUMENT_EXTRACTION`, `AI_CODING_AGENT`. That establishes that AI is in\nuse and for what function.\n\n**Not derivable** — whether any of it produces a **decision with a legal or similarly significant\neffect** on a person, and whether a human reviews it. Nothing in the framework declares consequence or\nhuman-review posture, and neither can be inferred from a capability being enabled.\n\n**Derives from (the consequence)** — the AI POSTURE section of your brief, per ENABLED AI capability:\nwhat it is used for, whether it `NO_DECISION` / `ASSISTS_HUMAN_DECISION` / `DECIDES_AUTONOMOUSLY`, and —\nwhere it decides anything — how a person obtains human intervention.\n\nAn application enabling NO AI capability gets a plain statement to that effect: it performs no AI\nprocessing of personal data. That is a positive, checkable answer, not a gap.\n\n**Completeness** — `DERIVED` per capability with a declared posture; `NEEDS_DECISION` per capability\nlisted OUTSTANDING. Not `NEEDS_FRAMEWORK` any more: issue #92 delivered the declaration, so an\nundeclared posture is an unanswered question rather than an unaskable one.\n\n**An OUTSTANDING capability is not a harmless one.** This is the one concern where silence is more\ndangerous than elsewhere: a notice describing AI use and saying nothing about consequence does not read\nas \"unknown\", it reads as \"nothing significant happens here\" — which is the exemption, claimed for\nfree. State the gap explicitly.\n\n**Why the distinction carries weight.** Automated decision-making with significant effects attracts\nspecific obligations — information about the logic, and a right to human intervention. A generated\nnotice must not silently claim the exemption by describing AI use without addressing consequence. The\nhonest statement says AI is used for these functions, and that whether any of it decides something\nabout a person is not yet established.\n\n\n### Concern: analytics and tracking\n\n**Asserts** — what is observed about how people use the service, and what a person's consent controls.\n\n**Derives from (partial)** — the observability and analytics capabilities the application has\nconfigured (`FRONTEND_PRODUCT_ANALYTICS`, `LLM_OBSERVABILITY`, `OBSERVABILITY_TELEMETRY`), together\nwith the consent posture: `analytics.requiresConsent` and each person's `privacy.consentedPurposes` make\n`ConsentPurpose.ANALYTICS` a real, enforced boundary rather than a stated intention — in the application,\nwhere a product-analytics provider starts only on the signed-in person's grant and is stopped on\nwithdrawal or sign-out, and on the marketing website, where one does not start until a visitor grants it.\nA consent-based provider must be stoppable in the page, so none is loaded as a `<script>` tag.\n\n**Derives from (the inventory)** — the CLIENT STORAGE section of your brief: each cookie and storage\nkey, its mechanism, purpose, necessity and lifetime, split by who sets it.\n\nThe FRAMEWORK's own entries are listed first and belong in every application's table — the cookies\n`__wildo_refresh` and `__wildo_anon_session`, strictly necessary, with lifetimes taken from the\napplication's session configuration, and the website's `__wildo_website_consent` storage key, strictly\nnecessary because it is what makes a visitor's refusal hold. **No application authored these and every application sets them**, so a table\nbuilt only from what the application declared would omit the session cookie, which is the entry a\nvisitor is most certain to have.\n\nThen, per frontend surface: its declared entries, an explicit \"sets nothing of its own\", or\nUNINVENTORIED.\n\n**UNINVENTORIED is not \"sets nothing\".** The first says nobody catalogued that surface; the second is a\npositive statement. Writing the second from the first tells a visitor they are tracked by less than they\nare, which is the under-reporting direction a notice must never fail in.\n\n**Completeness** — `DERIVED` for the capability and consent posture, and for each surface that IS\ninventoried; `NEEDS_DECISION` per uninventoried surface. Not `NEEDS_FRAMEWORK` any more: issue #91\ndelivered the declaration surface, so an uninventoried surface is an unanswered question rather than an\nunaskable one.\n\nSay both halves: which analytics are in use and what consent gates them (strong, derived, enforced), and\nwhat the table still lacks — naming the surfaces, not the concern.\n\n\n### Concern: subject rights\n\n**Asserts** — which request mechanisms the application configures, what they select and what their\nresults establish. A configured mechanism does not establish that a particular request was fulfilled.\n\n**Derives from**\n\n- `SubjectExportPurpose.ACCESS_ART_15` and `PORTABILITY_ART_20` — two selections over the declared\n subject relationships. Access includes eligible owned rows and non-owned rows referring to the\n subject. Portability applies narrower relationship and field-provenance selection. Neither is an\n unrestricted recursive export of everything reachable from an account.\n- Each participating resource's `systemAccessPolicy.exportSubject` — an explicit disclosure choice,\n checked before collection. Missing and forbidden are different decisions:\n\n| Declaration | Runtime result | Meaning for the request |\n| --- | --- | --- |\n| Absent on a participating resource | Refuses collection | A required disclosure decision is unanswered; no silently incomplete bundle is returned |\n| `ALLOWED` | Passes this disclosure gate | Relationship selection, system-read admission, field security and purpose-specific checks still apply |\n| `FORBIDDEN` on a dependent resource | Excludes that resource and records the reason | A deliberate exclusion; do not change it to ALLOWED merely to remove a reported omission |\n| `FORBIDDEN` on the subject's own resource | Refuses the bundle | The subject cannot be omitted from its own export |\n\n- `portabilityPolicy.defaultProvenance` and per-field `.portabilityProvenance(...)` — the field\n declaration overrides the resource default. `SUBJECT_PROVIDED` and `OBSERVED` values are eligible\n for portability; `DERIVED` values are excluded and reported. Unresolved provenance refuses\n portability collection rather than silently dropping fields. Explicitly forbidden resources do\n not need portability provenance for this export because their rows are not collected. Access uses\n its separate field selection; backend-only and write-only fields remain withheld.\n- Erasure: `eraseSubjectAsSystem(resourceType, rowIds)`, invoked by the application's verified request\n workflow. A contact or lead without a login can still be a data subject. Retention, relationship\n treatments and account linkage are separate declarations; inspect the receipt before claiming\n completion, including dependent execution, session resolution and incomplete external effects.\n\n**The rights a notice states are COMPUTED, in the `rights-and-complaint-route` fact.** Which rights\napply, and where a person may complain, are the law of the regime each `operatingJurisdictions` entry\nfalls under, conditioned on the declared lawful bases: portability only for purposes resting on consent\nor contract, objection only for public task or legitimate interests, withdrawal of consent only where\nconsent is the basis. The channel is `privacyContact`; the verification step is the operator's\n`subjectRequestIdentityVerification`; who answers comes from `roleAllocations` — the operator for data it\ncontrols, the customer (with the operator forwarding and assisting) for data it processes on a\ncustomer's behalf. Two regimes are known: the EU GDPR and the UK's. Their rights match article for article but their\ncomplaint routes do not — since 19 June 2026 a UK notice names a complaint to the operator itself\n(Data Protection Act 2018 s.164A, acknowledged within 30 days) and to the Information Commissioner\n(s.165(2)), and never GDPR Art. 77. State each regime's route from the fact, not from memory. A\njurisdiction no known regime reaches is named in `jurisdictionsWithoutKnownRegime`: state that its\nrights are not established here, never borrow another regime's words for it.\n\n**Completeness** — derive the configured posture from actual resource declarations and the selected\nrelationships. Describe an unresolved declaration as a configuration refusal, an explicit exclusion\nas an exclusion, and an observed request outcome from its report. Declarations alone are not runtime\nproof that a right has been fulfilled.\n\n**What resolves a missing declaration** — the owning resource explicitly declares ALLOWED or FORBIDDEN\naccording to its intended disclosure policy. Portability additionally needs a valid resource default\nor field-level provenance for the fields it would collect. Do not ask a notice author to replace a\nmissing product declaration with a free-text promise.\n\n**Never state** that an undeclared participating resource is merely omitted while the remainder is\nexported. The runtime refuses collection. Preserve deliberate exclusions and explain their recorded\nreasons; the application's request workflow owns verification, protected delivery and any necessary\nfollow-up.\n\n\n### Concern: data exit\n\n**Asserts** — what a customer gets back when they leave, in what form, and what happens to what\nremains.\n\n**Derives from** — `SubjectExportPurpose.PORTABILITY_ART_20` and the resources declaring\n`exportSubject`; the account-closure path; and each resource's `retentionPolicy.mode`, which decides\nwhether a record is removed or **retained and impersonalized** on erasure.\n\n**Completeness** — `DERIVED` for the mechanism.\n\n**Retained-and-impersonalized is the part a reader must not be surprised by**, and the part a\ngenerated document most often gets wrong by omission. A retained row is kept, frozen, hidden from\nnormal reads and reachable only through an audited privileged path — it is not deleted. Say so. A\nnotice that implies everything is erased, when financial and audit records are lawfully retained with\ntheir personal fields scrubbed, is inaccurate in the direction that damages trust when discovered.\n\n**How LONG anything is retained is not derivable** — see the retention-and-deletion fragment.\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## `document:public.service-terms` — six concerns\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: commercial terms\n\n**Asserts** — what is sold, how it is charged, and what happens on renewal, change and cancellation.\n\n**Derives from** — the application's billing declarations\n(`saas-models` → `billing/billing-enums.shared.schemas.ts`): `ProductType`, `BillingTiming`,\n`ProrationBehavior`, `TaxCalculationMode`, plus the declared products and any usage metering.\n\n**Completeness** — `DERIVED` where billing is configured; `NEEDS_CONFIGURATION` where the application\ndeclares no products, in which case say that the commercial terms are not yet established rather than\ndescribing a plan nobody has authored.\n\n**Keep consumer and business audiences apart.** Consumer pre-contract obligations (withdrawal\nperiods, pre-contractual information) apply only when a declared audience includes consumers. A terms\ndocument that blends both into one ambiguous set is worse than one that states which audience it is\nfor — so read the declared audience before writing a single clause about cancellation rights.\n\n\n### Concern: governing law and liability\n\n**Asserts** — which law governs the agreement, where disputes are heard, and how liability is limited.\n\n**Derives from** — nothing. These are negotiated commercial and legal positions.\n\n**Completeness** — `NEEDS_DECISION`.\n\n**What closes it** — the operator deciding, with counsel. Note that liability limits interact with\nthe declared audience: consumer-facing terms cannot limit liability as freely as business-to-business\nones, so this fragment cannot be settled before the commercial-terms fragment establishes who the\nterms are for.\n\n**Never produce a liability clause from a template.** A limitation of liability that was copied\nrather than decided is either unenforceable or committing the operator to something nobody agreed —\nand unlike most gaps in a produced document, this one is not discovered until it matters.\n",
|
|
29
29
|
"skillRefs": [
|
|
30
30
|
"compliance-document-authoring"
|
|
31
31
|
],
|
|
@@ -124,6 +124,14 @@ commitment nobody made and nothing enforces.
|
|
|
124
124
|
are the answers that let a notice state something true instead of confessing ignorance about a decision
|
|
125
125
|
the application already made — and the composition section in your brief lists them exactly.
|
|
126
126
|
|
|
127
|
+
**Not built yet is not "none".** When your brief says NOT BUILT YET, the build has not yet produced the
|
|
128
|
+
application's own resources, and their absence is a stage of the build, not a decision. Write that the
|
|
129
|
+
application's own data is not yet established. Never write "zero resources", "holds no personal data" or
|
|
130
|
+
"declares nothing" for data that does not exist yet. These facts are dated by the code they were read
|
|
131
|
+
from: once the build commits its resources, configuration or roles, they go stale and are derived again.
|
|
132
|
+
An earlier run wrote "zero personal-data resources" and "no billing" an hour before the build declared
|
|
133
|
+
both, and those sentences stayed in the file.
|
|
134
|
+
|
|
127
135
|
**Declare mechanism facts per RESOURCE where the resources differ.** "All eight application resources
|
|
128
136
|
declare a subject-export mode" is a usable fact; "the application supports exports" is not, because a
|
|
129
137
|
reader cannot tell which records it covers.
|