@wildo-ai/framework-knowledge 1.1.0 → 1.1.2
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/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 +43 -2
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts +19 -0
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js +32 -0
- package/dist/esm/framework-knowledge.loader.js.map +1 -1
- package/dist/esm/framework-knowledge.schemas.d.ts +12 -0
- package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +46 -0
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +55 -0
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +4 -4
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +3 -3
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +0 -3
- 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 +0 -1
- 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 +0 -3
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +2 -7
- 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 +0 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +8 -3
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +22 -1
- 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 +0 -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 +0 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +4 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +4 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -13
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +3 -4
- 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 +3 -3
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +2 -7
- 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 +0 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +2 -7
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +54 -0
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +127 -0
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +76 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +92 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +30 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +29 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +9 -44
- 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 +4 -53
- 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 +31 -0
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +26 -0
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -7
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +0 -8
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +2 -7
- 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 +0 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -7
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +2 -7
- 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 +5 -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 +0 -3
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +4 -5
- 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 +25 -4
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
- package/dist/knowledge/manifest.json +8 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +51 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +27 -10
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +8 -7
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +6 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +4 -6
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +5 -4
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +4 -6
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +0 -4
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +4 -6
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +49 -22
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +14 -6
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +2 -4
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +46 -1
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +7 -3
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +18 -4
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +4 -2
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +2 -3
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +8 -7
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +3 -5
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +0 -2
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +100 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +117 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +86 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +41 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +21 -4
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +14 -57
- package/dist/knowledge/playbooks/top_down.compliance-research/method.md +76 -0
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +42 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +3 -5
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +3 -1
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +3 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +3 -5
- package/dist/knowledge/playbooks/top_down.phase-gate/method.md +8 -4
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +9 -7
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +8 -7
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +0 -2
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +8 -7
- package/dist/knowledge/references/companion.technical-doc.service.md +102 -2
- package/dist/knowledge/references/example.config.app-shell.full.md +0 -1
- package/dist/knowledge/references/example.module.companion-exports.full.md +1 -0
- package/dist/knowledge/references/platform.config.saas.md +1 -0
- package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +25 -1
- package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +45 -0
- package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
- package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +89 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +31 -4
- package/dist/knowledge/references/saas.models.engine-capabilities.md +26 -6
- package/dist/knowledge/references/saas.models.file-upload-grant.md +179 -0
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +127 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +4 -3
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
- package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
- package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +11 -31
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +32 -2
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +29 -6
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +20 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +6 -0
- package/dist/knowledge/references/zod.decorators.field-spec-params.md +31 -5
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +43 -0
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +15 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
- package/dist/knowledge/registries/framework-topics.json +99 -1
- package/dist/knowledge/registries/playbooks.json +81 -8
- package/dist/knowledge/registries/source-tags.json +757 -588
- package/dist/knowledge/skills/INDEX.md +3 -3
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +5 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +66 -37
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +40 -7
- package/dist/knowledge/skills/config-app-shell/SKILL.md +25 -1
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +25 -1
- package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +23 -1
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
- package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
- package/dist/knowledge/skills/config-navigation/SKILL.md +75 -2
- package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +149 -0
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +114 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +133 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +19 -2
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +111 -0
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +30 -9
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +1 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +2 -1
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +20 -0
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +20 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +20 -0
- package/dist/knowledge/skills/resource-add-field/SKILL.md +3 -3
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +104 -0
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +13 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +71 -4
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +89 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +22 -1
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +192 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +28 -8
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +15 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +6 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +89 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +43 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +1 -1
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +20 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +31 -5
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +22 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +45 -0
- package/dist/knowledge/topic-index.json +504 -156
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/esm/.builder.pid +0 -9
|
@@ -44,6 +44,47 @@ with a clause marked incomplete — which is the mechanism this whole document e
|
|
|
44
44
|
The value must be the concern's exact name. A near miss (`retention` for `retention-and-deletion`) is
|
|
45
45
|
worse than a null: it reports the concern as unaddressed while the document addresses it.
|
|
46
46
|
|
|
47
|
+
|
|
48
|
+
## And SAY which required parts the section supplies
|
|
49
|
+
|
|
50
|
+
Every section also carries `satisfiesSectionRefs`: the refs, from the document definition rendered in
|
|
51
|
+
your brief, that this section actually addresses. This is a different question from `concernRef` and
|
|
52
|
+
both are answered — the concern says what compliance TOPIC the section is about, the satisfied refs
|
|
53
|
+
say what part of THIS document it supplies.
|
|
54
|
+
|
|
55
|
+
You are asked for the join because you are the only reader that holds both. The concern set is one
|
|
56
|
+
flat vocabulary spanning every document type; the required parts are defined per document, and the
|
|
57
|
+
same concern does not sit under the same heading in a privacy notice and a governance handbook. A
|
|
58
|
+
mapping written once in the framework would have to pick one answer and be wrong somewhere.
|
|
59
|
+
|
|
60
|
+
- A section may claim several refs, and several sections may claim one between them.
|
|
61
|
+
- A section that answers no required part — a preamble, a contact block — answers `null`. Not an
|
|
62
|
+
empty list: `null` and `[]` would be two spellings of one state, and the contract refuses the second.
|
|
63
|
+
- **Claim honestly.** A required ref nobody claims is reported as a part the document may not address,
|
|
64
|
+
which is a true and useful finding. Claiming one you did not address hides that, and nothing
|
|
65
|
+
downstream reads your prose to catch it.
|
|
66
|
+
|
|
67
|
+
Do NOT adopt the definition's refs as your own `sectionRef` values. Your section set is the concern
|
|
68
|
+
rule above; these are a claim you attach to it, not names you take.
|
|
69
|
+
|
|
70
|
+
**Clauses carry the same claim**, as `satisfiesClauseRefs`, and answer `null` the same way. Your brief
|
|
71
|
+
lists the blueprint's clauses under each section, each marked REQUIRED or CONDITIONAL; name the ones
|
|
72
|
+
your clause supplies.
|
|
73
|
+
|
|
74
|
+
Both keys were ASKED FOR HERE and absent from the strict contract you answer until 2026-09-02, so a
|
|
75
|
+
draft that followed this section could not parse and every landed document claimed nothing. If you
|
|
76
|
+
are reading a document produced before then, its empty coverage is that defect and not a finding
|
|
77
|
+
about the document.
|
|
78
|
+
|
|
79
|
+
- Several of your clauses may supply one blueprint clause between them, and one clause may supply
|
|
80
|
+
several.
|
|
81
|
+
- A clause supplying none — a transition, a heading gloss — claims none.
|
|
82
|
+
- **Only the clauses marked REQUIRED are owed.** A CONDITIONAL clause is supplied when its condition
|
|
83
|
+
holds and correctly omitted otherwise, so leaving one unclaimed is not a gap.
|
|
84
|
+
|
|
85
|
+
This is the anchor a clause did not previously have. A fact is named by the catalog and a section
|
|
86
|
+
carries its concern, so both survive a redraft; a clause was named freely and joined to nothing, which
|
|
87
|
+
is why a reviewer who approved one could not find it in the next revision.
|
|
47
88
|
## What a clause may say
|
|
48
89
|
|
|
49
90
|
The rule is ASSERT versus MARK, and the skill states it in full. In short: a clause may say "this is
|
|
@@ -683,7 +724,11 @@ needs and no further.
|
|
|
683
724
|
|
|
684
725
|
**Derives from** — the application's authored authentication configuration (methods enabled, MFA,
|
|
685
726
|
password policy, lockout, step-up, session lifetimes), its access floors, its encryption of stored
|
|
686
|
-
secrets, and the `ANTIVIRUS_SCANNING`
|
|
727
|
+
secrets, and its antivirus posture where the `ANTIVIRUS_SCANNING` INFRA capability is provisioned
|
|
728
|
+
(ClamAV, consumed by the engine's file-scanning service on upload). Note this reads the INFRA
|
|
729
|
+
capability, not an engine provider slot: the equally-named `EngineCapability.ANTIVIRUS_SCANNING` was
|
|
730
|
+
withdrawn because no provider could fill it, and a derived control statement must never rest on a
|
|
731
|
+
slot that cannot be configured.
|
|
687
732
|
|
|
688
733
|
**Completeness** — `DERIVED`, bounded.
|
|
689
734
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "refinement.compliance-document-candidate",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.2.0",
|
|
4
4
|
"phase": "refinement",
|
|
5
5
|
"intent": "Propose structured privacy-notice or service-terms candidate content from the application's accepted document facts. The companion agent may draft prose but cannot invent a fact, decide a legal question, approve, release or publish the document: every clause it writes is checked against the `document-facts` family, and a clause asserting a fact the application never declared is refused before it becomes a file.",
|
|
6
6
|
"functionalTopics": [],
|
|
@@ -26,14 +26,18 @@
|
|
|
26
26
|
],
|
|
27
27
|
"stepOutputs": [],
|
|
28
28
|
"method": {
|
|
29
|
-
"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; this method says which\ndocument, what shape, and what the two closed vocabularies are.\n\n## Choose the document, from a closed set\n\n`documentRef` must be one of six, and the contract refuses anything else:\n\n| `documentRef` | what it is |\n|---|---|\n| `document:public.privacy-notice` | what personal data the application holds and what happens to it |\n| `document:public.service-terms` | the commercial and service relationship |\n| `document:governance.scope-system-description` | what the system IS, for an assurance reader |\n| `document:governance.roles-responsibilities` | who is accountable for what |\n| `document:governance.program-handbook` | how the governance program runs |\n| `document:governance.document-record-control` | how governed documents are themselves controlled |\n\nDraft the **privacy notice** unless the run tells you otherwise. It is the one every application\nholding personal data needs, and the only one whose facts the current derivation supplies.\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## 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 **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 **`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## 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, and two need at least one entry:\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` — at least one: what governs the statement. Use the fact authority the clause\n rests on where there is one (`document-fact-authority:<slug>` from the facts file), otherwise the\n policy area it belongs to (`policy:retention`, `policy:recipients`).\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.\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## Where the draft goes\n\nIt lands as a FILE in the application's specifications package, as an ordinary working edit. It is\naccepted when a human commits it, and by nothing else. Landing is not approval, release or publication.\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**`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- `DataProcessingConsent` (`saas-models` → `compliance/privacy/privacy.shared.schemas.ts`):\n `NONE` · `BASIC` · `ANALYTICS` · `MARKETING` · `FULL` — a ladder, so a level implies the ones below it.\n- `analytics.requiredConsent` (`app-configuration-shared.shared.schemas.ts`, default `ANALYTICS`) —\n the minimum consent level for ANALYTICS, and nothing wider.\n- per-user `dataProcessingConsent` — the level each person actually chose.\n\n⚠️ **`requiredConsent` is ANALYTICS-SCOPED, and this fragment claimed otherwise until 2026-08-30.**\nIt read \"the minimum a person must give to use the service\", which is a different and much larger\nclaim; the field sits inside `AnalyticsConfigSchema` and governs analytics alone. A drafter following\nthe old wording would have published that a person must consent to analytics in order to use the\nproduct — false, and false about the one subject where a reader is most likely to act on it.\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**`NONE` 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, the per-user level, and the service-wide\nrequirement once declared; `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 only the first.\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**Derives from (the HOW LONG)** — the application's `dataRetention` schedule, declared in its config\nover four 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)) and `OPERATIONAL_LOGS`. Each declared class carries a period in\ndays AND the operator's stated reason for it.\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**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**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 (partial)** — the engine capabilities the application has a provider configured for\n(`EngineCapability` in `saas-models` → `external-providers/engine-capabilities.shared.schemas.ts`).\nThat establishes THAT a third party is involved and WHAT FUNCTION it performs — email delivery,\nstorage, payments, LLM inference, observability.\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 are real processors and both belong in the notice. What must not happen is presenting the second\nwith 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 runtime-bound providers 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 RUNTIME-BOUND providers, so it tells you three different things\nand they are not interchangeable:\n\n- a provider WITH an entry — state its legal entity and regions. `DERIVED`.\n- a provider listed **UNDECLARED** — it IS in use and nobody has established who it is. Name the\n function it performs (the capability says that) and state that its identity and location are\n outstanding. `NEEDS_DECISION`, closed by the operator establishing it.\n- a provider listed **STALE** — declared but no longer configured. Do NOT name it as a recipient; it\n receives nothing.\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**Where the register is empty, the honest statement names the FUNCTIONS and admits the identities are\noutstanding.**\n\"Third parties process data for email delivery, file storage and payments; their identities and\nprocessing locations are not yet established in this document\" is true, useful and specific. What is\nforbidden is the other two moves: inventing a plausible vendor list, and omitting the section — the\nfirst is false and the second lets a reader assume there are no recipients at all.\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 holds ONE.** Where declared processors process is\nderivable. Which jurisdiction is the ORIGIN, and which MECHANISM makes a given transfer lawful, are\nlegal determinations with a shelf life — adequacy decisions move by court ruling, so a list baked into\nthe engine would go stale silently and emit a false compliance statement. That is the worst failure\nthis lane has, so it is deliberately not modelled.\n\n**Completeness** — three states, and they are three different claims. Do not round any of them up.\n\n| the register | what you may state | completeness |\n|---|---|---|\n| ABSENT | nothing — where data lands is unknown | `NEEDS_CONFIGURATION` |\n| declares NO processor | no personal data reaches a third party, so none is transferred THROUGH one | `DERIVED`, with the residual stated |\n| declares processors | where data lands, region by region | `DERIVED` for location; the transfer POSITION stays `NEEDS_DECISION` |\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 the rest** — the transfer MECHANISM (adequacy, standard contractual clauses, binding\ncorporate rules, a derogation), recorded per subprocessor entry by a human informed by research. It is\nchosen and documented rather than derived, and it is parked deliberately: transfers arrive late in a\ncompany's life, and building the model before a real case exists would be guessing at its shape.\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 ladder: `requiredConsent` and per-user `dataProcessingConsent` make\n`DataProcessingConsent.ANALYTICS` a real, enforced boundary rather than a stated intention.\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 — `__wildo_refresh`\nand `__wildo_anon_session`, both strictly necessary, both with lifetimes taken from the application's\nsession configuration. **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 rights the application can actually honour, and through which mechanism. Not what\nthe law grants; what this application will do when asked.\n\n**Derives from**\n\n- `SubjectExportPurpose.ACCESS_ART_15` and `PORTABILITY_ART_20`\n (`saas-models` → `compliance/privacy/subject-export.shared.schemas.ts`) — the two distinct export\n bundles. Access is the broader one: every row concerning the subject, including rows they do not\n own, such as an audit entry about them or a membership an administrator created.\n- each resource's `systemAccessPolicy.exportSubject` — whether an export can answer for that resource\n at all. **Absent means the resource is excluded from every export**, so an application that has not\n declared it cannot honour Art. 15 over that data.\n- `portabilityPolicy` and per-field `.portabilityProvenance()` — Art. 20 covers what the subject\n supplied, not what the controller derived about them, and an Art. 20 export refuses on any field\n that has declared neither.\n- erasure: `eraseSubjectAsSystem(resourceType, rowIds)`, which takes a resource type and row ids and\n needs no session. **An account is not required to be a data subject** — a contact, a lead or a\n subscriber is erased by exactly this path.\n\n**Completeness** — `DERIVED` where the resources hold `exportSubject` declarations.\n\n**What closes it** — per-resource `exportSubject` and, for portability, a `portabilityPolicy` default\nplus provenance on the fields that differ from it.\n\n**Never state** that a right is honoured for a resource whose `exportSubject` is absent. The export\nwill not include it, and the notice would be describing a capability the application does not have.\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 (a crossing must be declared on the\noperation and carries a usable access grant).\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\n\n## `document:governance.*` — the governance concerns\n\n### Concern: security controls\n\n**Asserts** — the security measures the application actually runs, at the level of detail a notice\nneeds and no further.\n\n**Derives from** — the application's authored authentication configuration (methods enabled, MFA,\npassword policy, lockout, step-up, session lifetimes), its access floors, its encryption of stored\nsecrets, and the `ANTIVIRUS_SCANNING` engine capability where a provider is configured for it.\n\n**Completeness** — `DERIVED`, bounded.\n\n**Bounded is the operative word.** A public notice states that measures exist and their general\nnature. **It must not enumerate the control set**: a published list of exactly which protections are\nin place, and by implication which are not, is a map for somebody attacking the service. Detail\nbelongs in a security addendum shared under agreement, not on a public page — so this fragment reads\nvery differently in `public.privacy-notice` than in a security schedule, and that difference is\ndeliberate rather than an omission.\n\n**Never state a certification.** \"Compliant\", \"certified\", \"audited\" and \"ISO/SOC\" claims are not\nderivable from configuration and are not this document's to make.\n\n\n### Concern: audit and accountability\n\n**Asserts** — that security-relevant actions are recorded, what kinds are recorded, and where those\nrecords can be sent.\n\n**Derives from** — the `COMPLIANCE_AUDIT_TRAIL` engine capability\n(`saas-models` → `external-providers/engine-capabilities.shared.schemas.ts`), the auditable-event\ncatalog the engine emits (authentication, authorization grants, consent decisions, token lifecycle,\nconfiguration and permission changes, cross-tenant administrative access), and per-organization SIEM\nrouting where a tenant has configured it.\n\n**Completeness** — `DERIVED`.\n\nThis is one of the fragments where the ENGINE answers for the application. Every generated\napplication inherits the event catalog and the emitters; a document may state it without the\napplication having configured anything. Where a tenant has additionally routed events to its own\nSIEM, that is the tenant's configuration and belongs in a shared-responsibility statement rather than\nin the operator's own notice.\n\n\n### Concern: access control and roles\n\n**Asserts** — who inside the operator and inside a customer tenant can reach personal data, and what\nconstrains them.\n\n**Derives from** — `CORE_APP_ROLES` and `CORE_ORG_ROLES`\n(`saas-models` → `security/authorizations/roles.shared.schemas.ts`) plus the application's own role\ntable; the administrative-continuity floors (a tenant cannot be left with no usable owner, the\napplication cannot be left with no super-administrator); and the platform-access-grant mechanism,\nunder which a platform operator reaching into a customer tenant requires a granted, time-bounded\nauthorization rather than standing privilege, and every crossing is audited.\n\n**Completeness** — `DERIVED`.\n\nWorth stating plainly in a B2B notice, because it is the question a customer's own reviewer asks\nfirst: **operator access to tenant data is not ambient.** It is declared per operation, requires a\nusable grant, and is recorded when it happens.\n",
|
|
29
|
+
"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; this method says which\ndocument, what shape, and what the two closed vocabularies are.\n\n## Choose the document, from a closed set\n\n`documentRef` must be one of six, and the contract refuses anything else:\n\n| `documentRef` | what it is |\n|---|---|\n| `document:public.privacy-notice` | what personal data the application holds and what happens to it |\n| `document:public.service-terms` | the commercial and service relationship |\n| `document:governance.scope-system-description` | what the system IS, for an assurance reader |\n| `document:governance.roles-responsibilities` | who is accountable for what |\n| `document:governance.program-handbook` | how the governance program runs |\n| `document:governance.document-record-control` | how governed documents are themselves controlled |\n\nDraft the **privacy notice** unless the run tells you otherwise. It is the one every application\nholding personal data needs, and the only one whose facts the current derivation supplies.\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 **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 **`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## 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, and two need at least one entry:\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` — at least one: what governs the statement. Use the fact authority the clause\n rests on where there is one (`document-fact-authority:<slug>` from the facts file), otherwise the\n policy area it belongs to (`policy:retention`, `policy:recipients`).\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.\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## Where the draft goes\n\nIt lands as a FILE in the application's specifications package, as an ordinary working edit. It is\naccepted when a human commits it, and by nothing else. Landing is not approval, release or publication.\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**`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- `DataProcessingConsent` (`saas-models` → `compliance/privacy/privacy.shared.schemas.ts`):\n `NONE` · `BASIC` · `ANALYTICS` · `MARKETING` · `FULL` — a ladder, so a level implies the ones below it.\n- `analytics.requiredConsent` (`app-configuration-shared.shared.schemas.ts`, default `ANALYTICS`) —\n the minimum consent level for ANALYTICS, and nothing wider.\n- per-user `dataProcessingConsent` — the level each person actually chose.\n\n⚠️ **`requiredConsent` is ANALYTICS-SCOPED, and this fragment claimed otherwise until 2026-08-30.**\nIt read \"the minimum a person must give to use the service\", which is a different and much larger\nclaim; the field sits inside `AnalyticsConfigSchema` and governs analytics alone. A drafter following\nthe old wording would have published that a person must consent to analytics in order to use the\nproduct — false, and false about the one subject where a reader is most likely to act on it.\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**`NONE` 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, the per-user level, and the service-wide\nrequirement once declared; `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 only the first.\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**Derives from (the HOW LONG)** — the application's `dataRetention` schedule, declared in its config\nover four 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)) and `OPERATIONAL_LOGS`. Each declared class carries a period in\ndays AND the operator's stated reason for it.\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**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**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 (partial)** — the engine capabilities the application has a provider configured for\n(`EngineCapability` in `saas-models` → `external-providers/engine-capabilities.shared.schemas.ts`).\nThat establishes THAT a third party is involved and WHAT FUNCTION it performs — email delivery,\nstorage, payments, LLM inference, observability.\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 are real processors and both belong in the notice. What must not happen is presenting the second\nwith 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 runtime-bound providers 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 RUNTIME-BOUND providers, so it tells you three different things\nand they are not interchangeable:\n\n- a provider WITH an entry — state its legal entity and regions. `DERIVED`.\n- a provider listed **UNDECLARED** — it IS in use and nobody has established who it is. Name the\n function it performs (the capability says that) and state that its identity and location are\n outstanding. `NEEDS_DECISION`, closed by the operator establishing it.\n- a provider listed **STALE** — declared but no longer configured. Do NOT name it as a recipient; it\n receives nothing.\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**Where the register is empty, the honest statement names the FUNCTIONS and admits the identities are\noutstanding.**\n\"Third parties process data for email delivery, file storage and payments; their identities and\nprocessing locations are not yet established in this document\" is true, useful and specific. What is\nforbidden is the other two moves: inventing a plausible vendor list, and omitting the section — the\nfirst is false and the second lets a reader assume there are no recipients at all.\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 holds ONE.** Where declared processors process is\nderivable. Which jurisdiction is the ORIGIN, and which MECHANISM makes a given transfer lawful, are\nlegal determinations with a shelf life — adequacy decisions move by court ruling, so a list baked into\nthe engine would go stale silently and emit a false compliance statement. That is the worst failure\nthis lane has, so it is deliberately not modelled.\n\n**Completeness** — three states, and they are three different claims. Do not round any of them up.\n\n| the register | what you may state | completeness |\n|---|---|---|\n| ABSENT | nothing — where data lands is unknown | `NEEDS_CONFIGURATION` |\n| declares NO processor | no personal data reaches a third party, so none is transferred THROUGH one | `DERIVED`, with the residual stated |\n| declares processors | where data lands, region by region | `DERIVED` for location; the transfer POSITION stays `NEEDS_DECISION` |\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 the rest** — the transfer MECHANISM (adequacy, standard contractual clauses, binding\ncorporate rules, a derogation), recorded per subprocessor entry by a human informed by research. It is\nchosen and documented rather than derived, and it is parked deliberately: transfers arrive late in a\ncompany's life, and building the model before a real case exists would be guessing at its shape.\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 ladder: `requiredConsent` and per-user `dataProcessingConsent` make\n`DataProcessingConsent.ANALYTICS` a real, enforced boundary rather than a stated intention.\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 — `__wildo_refresh`\nand `__wildo_anon_session`, both strictly necessary, both with lifetimes taken from the application's\nsession configuration. **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 rights the application can actually honour, and through which mechanism. Not what\nthe law grants; what this application will do when asked.\n\n**Derives from**\n\n- `SubjectExportPurpose.ACCESS_ART_15` and `PORTABILITY_ART_20`\n (`saas-models` → `compliance/privacy/subject-export.shared.schemas.ts`) — the two distinct export\n bundles. Access is the broader one: every row concerning the subject, including rows they do not\n own, such as an audit entry about them or a membership an administrator created.\n- each resource's `systemAccessPolicy.exportSubject` — whether an export can answer for that resource\n at all. **Absent means the resource is excluded from every export**, so an application that has not\n declared it cannot honour Art. 15 over that data.\n- `portabilityPolicy` and per-field `.portabilityProvenance()` — Art. 20 covers what the subject\n supplied, not what the controller derived about them, and an Art. 20 export refuses on any field\n that has declared neither.\n- erasure: `eraseSubjectAsSystem(resourceType, rowIds)`, which takes a resource type and row ids and\n needs no session. **An account is not required to be a data subject** — a contact, a lead or a\n subscriber is erased by exactly this path.\n\n**Completeness** — `DERIVED` where the resources hold `exportSubject` declarations.\n\n**What closes it** — per-resource `exportSubject` and, for portability, a `portabilityPolicy` default\nplus provenance on the fields that differ from it.\n\n**Never state** that a right is honoured for a resource whose `exportSubject` is absent. The export\nwill not include it, and the notice would be describing a capability the application does not have.\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 (a crossing must be declared on the\noperation and carries a usable access grant).\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\n\n## `document:governance.*` — the governance concerns\n\n### Concern: security controls\n\n**Asserts** — the security measures the application actually runs, at the level of detail a notice\nneeds and no further.\n\n**Derives from** — the application's authored authentication configuration (methods enabled, MFA,\npassword policy, lockout, step-up, session lifetimes), its access floors, its encryption of stored\nsecrets, and its antivirus posture where the `ANTIVIRUS_SCANNING` INFRA capability is provisioned\n(ClamAV, consumed by the engine's file-scanning service on upload). Note this reads the INFRA\ncapability, not an engine provider slot: the equally-named `EngineCapability.ANTIVIRUS_SCANNING` was\nwithdrawn because no provider could fill it, and a derived control statement must never rest on a\nslot that cannot be configured.\n\n**Completeness** — `DERIVED`, bounded.\n\n**Bounded is the operative word.** A public notice states that measures exist and their general\nnature. **It must not enumerate the control set**: a published list of exactly which protections are\nin place, and by implication which are not, is a map for somebody attacking the service. Detail\nbelongs in a security addendum shared under agreement, not on a public page — so this fragment reads\nvery differently in `public.privacy-notice` than in a security schedule, and that difference is\ndeliberate rather than an omission.\n\n**Never state a certification.** \"Compliant\", \"certified\", \"audited\" and \"ISO/SOC\" claims are not\nderivable from configuration and are not this document's to make.\n\n\n### Concern: audit and accountability\n\n**Asserts** — that security-relevant actions are recorded, what kinds are recorded, and where those\nrecords can be sent.\n\n**Derives from** — the `COMPLIANCE_AUDIT_TRAIL` engine capability\n(`saas-models` → `external-providers/engine-capabilities.shared.schemas.ts`), the auditable-event\ncatalog the engine emits (authentication, authorization grants, consent decisions, token lifecycle,\nconfiguration and permission changes, cross-tenant administrative access), and per-organization SIEM\nrouting where a tenant has configured it.\n\n**Completeness** — `DERIVED`.\n\nThis is one of the fragments where the ENGINE answers for the application. Every generated\napplication inherits the event catalog and the emitters; a document may state it without the\napplication having configured anything. Where a tenant has additionally routed events to its own\nSIEM, that is the tenant's configuration and belongs in a shared-responsibility statement rather than\nin the operator's own notice.\n\n\n### Concern: access control and roles\n\n**Asserts** — who inside the operator and inside a customer tenant can reach personal data, and what\nconstrains them.\n\n**Derives from** — `CORE_APP_ROLES` and `CORE_ORG_ROLES`\n(`saas-models` → `security/authorizations/roles.shared.schemas.ts`) plus the application's own role\ntable; the administrative-continuity floors (a tenant cannot be left with no usable owner, the\napplication cannot be left with no super-administrator); and the platform-access-grant mechanism,\nunder which a platform operator reaching into a customer tenant requires a granted, time-bounded\nauthorization rather than standing privilege, and every crossing is audited.\n\n**Completeness** — `DERIVED`.\n\nWorth stating plainly in a B2B notice, because it is the question a customer's own reviewer asks\nfirst: **operator access to tenant data is not ambient.** It is declared per operation, requires a\nusable grant, and is recorded when it happens.\n",
|
|
30
30
|
"skillRefs": [
|
|
31
31
|
"compliance-document-authoring"
|
|
32
32
|
],
|
|
33
33
|
"contextSources": [
|
|
34
34
|
"document_blueprint"
|
|
35
35
|
],
|
|
36
|
-
"suspendsForClarification": false
|
|
36
|
+
"suspendsForClarification": false,
|
|
37
|
+
"briefAdequacyGate": true,
|
|
38
|
+
"briefAdequacyExcludedSources": [
|
|
39
|
+
"compliance_primary_facts"
|
|
40
|
+
]
|
|
37
41
|
},
|
|
38
42
|
"executor": "companion_agent",
|
|
39
43
|
"approval": "approve_result",
|
|
@@ -203,12 +203,24 @@ human makes it.
|
|
|
203
203
|
- A retention period the product has not chosen, or one you inferred from a default.
|
|
204
204
|
- A named human, a reviewer, a qualification or an independence statement. Every fact you produce
|
|
205
205
|
carries `APPLICATION_SPECIFICATION` authority — the accepted specification is the authority, and it
|
|
206
|
-
is the only one a derivation can honestly claim
|
|
206
|
+
is the only one a derivation can honestly claim, and since 2026-09-03 the only one the family's TYPE
|
|
207
|
+
accepts. A declaration carrying any other authority is refused before it reaches a file.
|
|
207
208
|
- A decision instant. You have no clock, and the honest instant for a human decision is the commit that
|
|
208
209
|
records it.
|
|
209
210
|
- A security claim beyond what the application's configuration actually shows.
|
|
210
211
|
- A fact about a provider, region or capability the application has not configured.
|
|
211
212
|
|
|
213
|
+
## The file you write is REGENERATED WHOLE, and a second family holds what you must not touch
|
|
214
|
+
|
|
215
|
+
Your output replaces `document-facts` entirely on every run. That is why the facts only a human may
|
|
216
|
+
establish — a creator decision, a qualified review — live in a SEPARATE family,
|
|
217
|
+
`document-facts-authored`, which you neither read nor write. Before the two were split they shared one
|
|
218
|
+
file, and a producer run silently deleted the human half.
|
|
219
|
+
|
|
220
|
+
So an absent fact is never something for you to fill in "because nobody else will". The brief already
|
|
221
|
+
names which facts are yours; anything it withholds has a home you cannot reach, and leaving it absent
|
|
222
|
+
is the correct outcome rather than a gap you are working around.
|
|
223
|
+
|
|
212
224
|
## Refs are stamped for you
|
|
213
225
|
|
|
214
226
|
Supply slugs. The runtime turns each into its namespaced ref, attaches the governance scope and
|
|
@@ -252,9 +264,11 @@ somebody still owes.
|
|
|
252
264
|
|
|
253
265
|
## Runtime context
|
|
254
266
|
|
|
255
|
-
|
|
256
|
-
|
|
257
|
-
|
|
267
|
+
Everything above is already in your brief: `vision-brief` / `domain-plan` / `requirements` render as
|
|
268
|
+
input sections under "# Accepted application truth", and the application's live resource
|
|
269
|
+
DECLARATIONS (retention mode, data-subject kind, subject export, retained see-through) arrive as
|
|
270
|
+
the declared `compliance_primary_facts` context section of your brief. Derive facts from those sections; there is no command to
|
|
271
|
+
run in this mode.
|
|
258
272
|
|
|
259
273
|
## References
|
|
260
274
|
|
|
@@ -38,7 +38,7 @@
|
|
|
38
38
|
],
|
|
39
39
|
"stepOutputs": [],
|
|
40
40
|
"method": {
|
|
41
|
-
"guidance": "# Governed-document facts — derivation method\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What you produce\n\nOne `document-facts` file for the application: a list of **facts**, each a plain statement about how\nthis application actually behaves. Not prose for a notice — the raw material a notice is later drafted\nfrom, and the thing a drafted clause is checked against.\n\nA fact is the answer to a question a reader of a legal document would want settled:\n\n- what categories of personal data does the application hold, and where do they come from;\n- what does it do with them, and for how long does it keep them;\n- who else sees them — providers, processors, other tenants;\n- what rights does it actually honour, and through which mechanism;\n- who operates the service, and how is it contacted.\n\n## The rule that governs everything here\n\n**Every fact you write must be supported by something the application has already accepted** — and the\nstrongest support is not prose about the application, it is **the application's own code**.\n\nRead in this order:\n\n1. **The resource declarations**, which are already in this brief, under *\"The application's\n compliance-relevant resource declarations (read from its CODE)\"*. Per resource:\n `retentionPolicy.mode` (what erasure does to a row), `dataSubjectPolicy.kind` (whose login session\n an erasure ends), `systemAccessPolicy.exportSubject` (whether an Art. 15 / Art. 20 export can answer\n for them) and `seeRetained` (the audited path to retained data). These are DECLARATIONS, already\n written down and enforced at runtime. They are the best evidence a governed document can rest on,\n and they need no interpretation — only phrasing.\n\n **Use them.** A fact about a mechanism — what is kept, what is scrubbed, what can be exported — that\n does not correspond to a declaration in that section is not derived, it is recalled, and this\n playbook's whole reason for existing is the difference.\n2. **The compliance constraints on the vision**, which tell you which facts a reader will need.\n3. **The domain plan and requirements**, for what the product is FOR — purpose, not mechanism.\n\nThe split between 1 and 3 is the point. A specification says what the application is meant to do; a\nresource configuration says what it will actually do to a row tomorrow morning. Where they disagree,\nthe configuration is the fact.\n\nThat section reports engine-declared and application-declared coverage **separately**, and you should\nkeep them apart in your facts too: the two have different owners, so they have different remedies. An\napplication's authors cannot close an engine gap, and the engine's maintainers cannot close theirs.\n\nDo not assume the engine half is the settled half. Read the counts. On the first real application to\nbe measured, the engine declared an erasure treatment on **two of eighty-five** resources — the user\naccount and its self-view — and nothing on credentials, profiles, audit logs, files or membership.\nWhatever the numbers say in your own brief, they are the fact; a sentence crediting the framework with\ndeclarations it has not made is exactly as false as one crediting the application.\n\n## COVER THE WHOLE SET — this is the half a first attempt gets wrong\n\nThe facts you declare here are the only thing a later document can state as established. A concern you\nsay nothing about does not become a cautious sentence in the notice; it becomes a clause reading *\"this\nhas not yet been established\"*, in a document about somebody's personal data, when the application had\nalready established it.\n\nMeasured on the first real application (wonder-crm, 2026-08-29): this pass produced **three** facts, and\nthe notice drafted from them marked **ten of thirteen** concerns incomplete — including subject rights,\nwhich every one of that application's resources declares, and analytics, which it does not enable. Both\nwere answerable from the brief in front of it. That is the failure mode to avoid, and it is not caution:\na notice that understates what an application does is as wrong as one that overstates it.\n\nWork through this list and declare a fact for each one you can answer:\n\n| what a document will need | where the answer is |\n|---|---|\n| what personal data is held, and in which records | the resource declarations + the domain plan |\n| what erasure does to each record | `retentionPolicy.mode` per resource |\n| how long records are kept | the RETENTION SCHEDULE in your brief — four classes, each declared or UNDECIDED |\n| whether a subject-access or portability export can answer for a record | `systemAccessPolicy.exportSubject` per resource |\n| whether retained data stays reachable, and audited | `systemAccessPolicy.seeRetained` per resource |\n| who else can see the data inside the application | the domain model — roles, membership, sharing |\n| which third parties receive data, WHO they are and WHERE they process | the PROCESSOR REGISTER section — declared entries, plus the providers it lists UNDECLARED |\n| whether the application makes automated decisions or uses AI | the AI POSTURE section — per enabled capability, a declared consequence or OUTSTANDING |\n| what analytics or tracking runs, and what is stored in a browser | the declared capabilities + the CLIENT STORAGE section (framework entries, then per surface) |\n| what consent the application asks for | the declared capabilities + the domain plan |\n| how organizations are separated from each other | the domain model and the tenancy declarations |\n\n## RECORD THE GAPS AS FACTS TOO — nothing downstream can see this brief\n\nThe sections above are yours alone. The pass that drafts the document reads the `document-facts` FILE\nand nothing else — it never sees the resource declarations, the retention schedule, the processor\nregister, the AI posture or the client-storage inventory. **A gap you notice and do not write down is a\ngap that disappears**, and the document then states the half that was answered as though it were the\nwhole.\n\nSo when a section names something as `UNDECIDED`, `UNDECLARED`, `OUTSTANDING` or `UNINVENTORIED`,\ndeclare a fact recording it, naming what is missing:\n\n- *\"No retention period is declared for any of the four data classes; all four require an operator\n decision.\"*\n- *\"The `app` frontend surface's own client storage has not been catalogued.\"*\n\nThis is the failure mode to avoid, measured on a real run: the facts stated that no consent-gated\nbrowser storage is configured — true — and said nothing about the frontend surface nobody had\ninventoried. A reader of the notice would take the first as the whole answer.\n\nA gap recorded as a fact is `KNOWN`: the thing that is known IS the gap. Do not use `NOT_APPLICABLE`\nfor it — that says the question does not arise, and it does.\n\n**An UNDECIDED retention period is an OPERATOR's decision, not a framework gap.** The application can\ndeclare a period for each of the four data classes and has not for some of them. State which classes\nare declared, with their periods and the reasons given, and state plainly which are still undecided —\nthe remedy is an operator deciding, not the framework growing a mechanism. Never write a period the\napplication has not declared, and never soften an absent one into \"as long as necessary\": that is a\ncommitment nobody made and nothing enforces.\n\n**An absent capability is a fact, not a silence.** If no analytics provider is configured, that is\n`KNOWN`: *\"no external analytics provider is configured\"*. If no AI capability is declared, say so. These\nare the answers that let a notice state something true instead of confessing ignorance about a decision\nthe application already made — and the composition section in your brief lists them exactly.\n\n**Declare mechanism facts per RESOURCE where the resources differ.** \"All eight application resources\ndeclare a subject-export mode\" is a usable fact; \"the application supports exports\" is not, because a\nreader cannot tell which records it covers.\n\nYou are **not** deciding anything. A legal basis, a controller-versus-processor role, a governing law,\na liability position and a retention *duration the product has not chosen* are all decisions, and none\nof them is yours. If a fact needs a human to decide it, **leave it out**. Do not write a plausible\nplaceholder, and do not soften a decision into a fact by hedging the wording.\n\nLeaving it out is not a failure — it is the designed behaviour, and it does **not** block anything\ndownstream. A document clause that would have rested on a fact you did not declare is still written:\nit is marked as not yet established, names what it needs and who can supply it, and the document is\nproduced. So an absence costs the reader a precise statement of a gap, which is useful. A guessed fact\ncosts them a published false statement about somebody's data, which is not.\n\n## The shape of a declaration — get this right or the whole file is rejected\n\nEach declaration carries three slugs, all lowercase kebab-case (`retention-treatment-per-resource`),\nand **every one of them must be UNIQUE across the file**:\n\n- `slug` — names THIS declaration. Two declarations sharing a `slug` are rejected, and this is the\n single most common way a good fact set fails: a drafter answering several facts about retention\n gives them all `slug: \"retention\"`. Make each one describe its own fact.\n- `factSlug` — names the FACT being answered. One governance scope carries one answer per fact, so two\n declarations may not share a `factSlug` either. If you want to say two things about retention, they\n are two facts (`retention-treatment-per-resource`, `retention-duration`), not one fact twice.\n- `sensitivitySlug` — how sensitive the fact itself is (`public`, `internal-governance`). This one MAY\n repeat; it is a classification, not an identity.\n\nA rejection naming `declarations.N.slug` is almost always a COLLISION rather than a bad character:\nre-read your list for two entries sharing a name.\n\n## KNOWN and NOT_APPLICABLE are different answers — and both are different from absence\n\nThree states, and confusing them is the most common way this pass goes wrong.\n\n| state | means | how you write it |\n|---|---|---|\n| `KNOWN` | the application does this, and here is what it does | `resolution: KNOWN` with `value` |\n| `NOT_APPLICABLE` | this was considered and it genuinely does not apply | `resolution: NOT_APPLICABLE` with `reason` |\n| absent | nobody has established this yet | omit the declaration entirely |\n\n`NOT_APPLICABLE` is a real, useful answer — \"this application performs no international transfers\"\ntells a reviewer something. It is **not** a way to dispose of a fact you could not find. If you do not\nknow, the honest output is absence.\n\nA `KNOWN` fact must carry an actual value. An empty string, a blank one or an empty object is rejected\nby the validator: a fact that exists and says nothing is worse than a missing one, because a document\ncan cite it and learn nothing.\n\n## Read the compliance constraints first\n\n`top_down.compliance-posture` records each applicable regime as a `compliance`-kind constraint on the\nvision. Those constraints tell you which facts matter. A GDPR constraint means a reader will need data\ncategories, purposes, retention, recipients, transfers and rights mechanisms. A data-residency\nconstraint means where data lives is a fact worth stating.\n\nDerive the fact SET from the regimes, then answer each one from the application's own truth — the\nconfigurations first. Where the regime implies a fact the application has not settled, that is an\nabsence: record nothing, and let the document state the gap in place.\n\n## Scope: one operator, deliberately\n\nEvery fact you write is attributed to one application-operator governance scope. The family can carry\nfacts for a tenant organization or a shared-responsibility boundary too, but choosing a different\nsubject per fact is deciding **shared-responsibility attribution**, which is exactly the thing that\nmust never be guessed or flattened. One operator scope is the honest output of a derivation; a second\nsubject is a human's edit.\n\nThe `operatorSlug` you supply is an operator identity, **not** a legal-entity assertion. It names who\nruns the service, not which company is on the contract — that is a decision, and it is absent until a\nhuman makes it.\n\n## What you never write\n\n- A legal basis, a lawful-processing justification, or a controller/processor role.\n- A retention period the product has not chosen, or one you inferred from a default.\n- A named human, a reviewer, a qualification or an independence statement. Every fact you produce\n carries `APPLICATION_SPECIFICATION` authority — the accepted specification is the authority, and it\n is the only one a derivation can honestly claim.\n- A decision instant. You have no clock, and the honest instant for a human decision is the commit that\n records it.\n- A security claim beyond what the application's configuration actually shows.\n- A fact about a provider, region or capability the application has not configured.\n\n## Refs are stamped for you\n\nSupply slugs. The runtime turns each into its namespaced ref, attaches the governance scope and\nauthority, assigns versions and sorts the declarations. Do not author a ref, a version or an ordering;\na contract that asked you to would be asking you to fail on form rather than on substance.\n\n(This paragraph listed `retention-rules`, `data-categories-and-sources` and\n`recipients-and-processors` as examples. All three are required fact names, and naming three of eight\nas \"examples\" invited a drafter to treat them as a style to imitate rather than a set to use. The\nauthoritative list now arrives in the brief.)\n\n**For a concern a governed document requires, the slug is NOT yours to choose.** The brief you were\ngiven lists the exact `factSlug` for each one, taken from the engine catalog. Use it verbatim.\n\nThis is not a style preference. A clause cites a fact BY REF, the ref is stamped from your slug, and a\nfact answering the right question under a different name is a fact the document cannot cite — it reads\nas missing while your answer sits in the file. Measured on a real run: twenty facts declared, zero of\nthe eight a privacy notice requires, because the names were semantically adjacent and lexically\ndisjoint (`retention-period-schedule-status` for `retention-rules`).\n\nFor anything the catalog does NOT name, the slug is yours: use a stable, descriptive one that reads as\nthe question it answers. An application legitimately declares facts no document requires.\n\n## Verification\n\nBefore you finish, check each declaration against these:\n\n- [ ] every `KNOWN` value states something a reader could act on, and is traceable to accepted truth;\n- [ ] no declaration encodes a decision (legal basis, role, governing law, liability, chosen retention);\n- [ ] every `NOT_APPLICABLE` reason says why it does not apply, not that it could not be found;\n- [ ] a fact you could not establish is ABSENT, not guessed and not marked not-applicable;\n- [ ] the fact set is derived from the vision's compliance constraints, not from a generic SaaS template;\n- [ ] no `factSlug` is declared twice.\n\n## Approval\n\nThe derived fact set is presented to the creator before it becomes the committed `document-facts`\nfamily. Show it back as plain statements grouped by the question each answers, and name what you left\nout and why — the absences are the part a human most needs to see, because each one is a decision\nsomebody still owes.\n\n## Runtime context\n\n// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)\n// TODO CLI COMMAND: wildo context vision-brief (read the vision and its compliance constraints)\n// TODO CLI COMMAND: wildo context resources (read the resources and fields whose data these facts describe)\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read current journey state and the artifacts you derive from.\n",
|
|
41
|
+
"guidance": "# Governed-document facts — derivation method\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What you produce\n\nOne `document-facts` file for the application: a list of **facts**, each a plain statement about how\nthis application actually behaves. Not prose for a notice — the raw material a notice is later drafted\nfrom, and the thing a drafted clause is checked against.\n\nA fact is the answer to a question a reader of a legal document would want settled:\n\n- what categories of personal data does the application hold, and where do they come from;\n- what does it do with them, and for how long does it keep them;\n- who else sees them — providers, processors, other tenants;\n- what rights does it actually honour, and through which mechanism;\n- who operates the service, and how is it contacted.\n\n## The rule that governs everything here\n\n**Every fact you write must be supported by something the application has already accepted** — and the\nstrongest support is not prose about the application, it is **the application's own code**.\n\nRead in this order:\n\n1. **The resource declarations**, which are already in this brief, under *\"The application's\n compliance-relevant resource declarations (read from its CODE)\"*. Per resource:\n `retentionPolicy.mode` (what erasure does to a row), `dataSubjectPolicy.kind` (whose login session\n an erasure ends), `systemAccessPolicy.exportSubject` (whether an Art. 15 / Art. 20 export can answer\n for them) and `seeRetained` (the audited path to retained data). These are DECLARATIONS, already\n written down and enforced at runtime. They are the best evidence a governed document can rest on,\n and they need no interpretation — only phrasing.\n\n **Use them.** A fact about a mechanism — what is kept, what is scrubbed, what can be exported — that\n does not correspond to a declaration in that section is not derived, it is recalled, and this\n playbook's whole reason for existing is the difference.\n2. **The compliance constraints on the vision**, which tell you which facts a reader will need.\n3. **The domain plan and requirements**, for what the product is FOR — purpose, not mechanism.\n\nThe split between 1 and 3 is the point. A specification says what the application is meant to do; a\nresource configuration says what it will actually do to a row tomorrow morning. Where they disagree,\nthe configuration is the fact.\n\nThat section reports engine-declared and application-declared coverage **separately**, and you should\nkeep them apart in your facts too: the two have different owners, so they have different remedies. An\napplication's authors cannot close an engine gap, and the engine's maintainers cannot close theirs.\n\nDo not assume the engine half is the settled half. Read the counts. On the first real application to\nbe measured, the engine declared an erasure treatment on **two of eighty-five** resources — the user\naccount and its self-view — and nothing on credentials, profiles, audit logs, files or membership.\nWhatever the numbers say in your own brief, they are the fact; a sentence crediting the framework with\ndeclarations it has not made is exactly as false as one crediting the application.\n\n## COVER THE WHOLE SET — this is the half a first attempt gets wrong\n\nThe facts you declare here are the only thing a later document can state as established. A concern you\nsay nothing about does not become a cautious sentence in the notice; it becomes a clause reading *\"this\nhas not yet been established\"*, in a document about somebody's personal data, when the application had\nalready established it.\n\nMeasured on the first real application (wonder-crm, 2026-08-29): this pass produced **three** facts, and\nthe notice drafted from them marked **ten of thirteen** concerns incomplete — including subject rights,\nwhich every one of that application's resources declares, and analytics, which it does not enable. Both\nwere answerable from the brief in front of it. That is the failure mode to avoid, and it is not caution:\na notice that understates what an application does is as wrong as one that overstates it.\n\nWork through this list and declare a fact for each one you can answer:\n\n| what a document will need | where the answer is |\n|---|---|\n| what personal data is held, and in which records | the resource declarations + the domain plan |\n| what erasure does to each record | `retentionPolicy.mode` per resource |\n| how long records are kept | the RETENTION SCHEDULE in your brief — four classes, each declared or UNDECIDED |\n| whether a subject-access or portability export can answer for a record | `systemAccessPolicy.exportSubject` per resource |\n| whether retained data stays reachable, and audited | `systemAccessPolicy.seeRetained` per resource |\n| who else can see the data inside the application | the domain model — roles, membership, sharing |\n| which third parties receive data, WHO they are and WHERE they process | the PROCESSOR REGISTER section — declared entries, plus the providers it lists UNDECLARED |\n| whether the application makes automated decisions or uses AI | the AI POSTURE section — per enabled capability, a declared consequence or OUTSTANDING |\n| what analytics or tracking runs, and what is stored in a browser | the declared capabilities + the CLIENT STORAGE section (framework entries, then per surface) |\n| what consent the application asks for | the declared capabilities + the domain plan |\n| how organizations are separated from each other | the domain model and the tenancy declarations |\n\n## RECORD THE GAPS AS FACTS TOO — nothing downstream can see this brief\n\nThe sections above are yours alone. The pass that drafts the document reads the `document-facts` FILE\nand nothing else — it never sees the resource declarations, the retention schedule, the processor\nregister, the AI posture or the client-storage inventory. **A gap you notice and do not write down is a\ngap that disappears**, and the document then states the half that was answered as though it were the\nwhole.\n\nSo when a section names something as `UNDECIDED`, `UNDECLARED`, `OUTSTANDING` or `UNINVENTORIED`,\ndeclare a fact recording it, naming what is missing:\n\n- *\"No retention period is declared for any of the four data classes; all four require an operator\n decision.\"*\n- *\"The `app` frontend surface's own client storage has not been catalogued.\"*\n\nThis is the failure mode to avoid, measured on a real run: the facts stated that no consent-gated\nbrowser storage is configured — true — and said nothing about the frontend surface nobody had\ninventoried. A reader of the notice would take the first as the whole answer.\n\nA gap recorded as a fact is `KNOWN`: the thing that is known IS the gap. Do not use `NOT_APPLICABLE`\nfor it — that says the question does not arise, and it does.\n\n**An UNDECIDED retention period is an OPERATOR's decision, not a framework gap.** The application can\ndeclare a period for each of the four data classes and has not for some of them. State which classes\nare declared, with their periods and the reasons given, and state plainly which are still undecided —\nthe remedy is an operator deciding, not the framework growing a mechanism. Never write a period the\napplication has not declared, and never soften an absent one into \"as long as necessary\": that is a\ncommitment nobody made and nothing enforces.\n\n**An absent capability is a fact, not a silence.** If no analytics provider is configured, that is\n`KNOWN`: *\"no external analytics provider is configured\"*. If no AI capability is declared, say so. These\nare the answers that let a notice state something true instead of confessing ignorance about a decision\nthe application already made — and the composition section in your brief lists them exactly.\n\n**Declare mechanism facts per RESOURCE where the resources differ.** \"All eight application resources\ndeclare a subject-export mode\" is a usable fact; \"the application supports exports\" is not, because a\nreader cannot tell which records it covers.\n\nYou are **not** deciding anything. A legal basis, a controller-versus-processor role, a governing law,\na liability position and a retention *duration the product has not chosen* are all decisions, and none\nof them is yours. If a fact needs a human to decide it, **leave it out**. Do not write a plausible\nplaceholder, and do not soften a decision into a fact by hedging the wording.\n\nLeaving it out is not a failure — it is the designed behaviour, and it does **not** block anything\ndownstream. A document clause that would have rested on a fact you did not declare is still written:\nit is marked as not yet established, names what it needs and who can supply it, and the document is\nproduced. So an absence costs the reader a precise statement of a gap, which is useful. A guessed fact\ncosts them a published false statement about somebody's data, which is not.\n\n## The shape of a declaration — get this right or the whole file is rejected\n\nEach declaration carries three slugs, all lowercase kebab-case (`retention-treatment-per-resource`),\nand **every one of them must be UNIQUE across the file**:\n\n- `slug` — names THIS declaration. Two declarations sharing a `slug` are rejected, and this is the\n single most common way a good fact set fails: a drafter answering several facts about retention\n gives them all `slug: \"retention\"`. Make each one describe its own fact.\n- `factSlug` — names the FACT being answered. One governance scope carries one answer per fact, so two\n declarations may not share a `factSlug` either. If you want to say two things about retention, they\n are two facts (`retention-treatment-per-resource`, `retention-duration`), not one fact twice.\n- `sensitivitySlug` — how sensitive the fact itself is (`public`, `internal-governance`). This one MAY\n repeat; it is a classification, not an identity.\n\nA rejection naming `declarations.N.slug` is almost always a COLLISION rather than a bad character:\nre-read your list for two entries sharing a name.\n\n## KNOWN and NOT_APPLICABLE are different answers — and both are different from absence\n\nThree states, and confusing them is the most common way this pass goes wrong.\n\n| state | means | how you write it |\n|---|---|---|\n| `KNOWN` | the application does this, and here is what it does | `resolution: KNOWN` with `value` |\n| `NOT_APPLICABLE` | this was considered and it genuinely does not apply | `resolution: NOT_APPLICABLE` with `reason` |\n| absent | nobody has established this yet | omit the declaration entirely |\n\n`NOT_APPLICABLE` is a real, useful answer — \"this application performs no international transfers\"\ntells a reviewer something. It is **not** a way to dispose of a fact you could not find. If you do not\nknow, the honest output is absence.\n\nA `KNOWN` fact must carry an actual value. An empty string, a blank one or an empty object is rejected\nby the validator: a fact that exists and says nothing is worse than a missing one, because a document\ncan cite it and learn nothing.\n\n## Read the compliance constraints first\n\n`top_down.compliance-posture` records each applicable regime as a `compliance`-kind constraint on the\nvision. Those constraints tell you which facts matter. A GDPR constraint means a reader will need data\ncategories, purposes, retention, recipients, transfers and rights mechanisms. A data-residency\nconstraint means where data lives is a fact worth stating.\n\nDerive the fact SET from the regimes, then answer each one from the application's own truth — the\nconfigurations first. Where the regime implies a fact the application has not settled, that is an\nabsence: record nothing, and let the document state the gap in place.\n\n## Scope: one operator, deliberately\n\nEvery fact you write is attributed to one application-operator governance scope. The family can carry\nfacts for a tenant organization or a shared-responsibility boundary too, but choosing a different\nsubject per fact is deciding **shared-responsibility attribution**, which is exactly the thing that\nmust never be guessed or flattened. One operator scope is the honest output of a derivation; a second\nsubject is a human's edit.\n\nThe `operatorSlug` you supply is an operator identity, **not** a legal-entity assertion. It names who\nruns the service, not which company is on the contract — that is a decision, and it is absent until a\nhuman makes it.\n\n## What you never write\n\n- A legal basis, a lawful-processing justification, or a controller/processor role.\n- A retention period the product has not chosen, or one you inferred from a default.\n- A named human, a reviewer, a qualification or an independence statement. Every fact you produce\n carries `APPLICATION_SPECIFICATION` authority — the accepted specification is the authority, and it\n is the only one a derivation can honestly claim, and since 2026-09-03 the only one the family's TYPE\n accepts. A declaration carrying any other authority is refused before it reaches a file.\n- A decision instant. You have no clock, and the honest instant for a human decision is the commit that\n records it.\n- A security claim beyond what the application's configuration actually shows.\n- A fact about a provider, region or capability the application has not configured.\n\n## The file you write is REGENERATED WHOLE, and a second family holds what you must not touch\n\nYour output replaces `document-facts` entirely on every run. That is why the facts only a human may\nestablish — a creator decision, a qualified review — live in a SEPARATE family,\n`document-facts-authored`, which you neither read nor write. Before the two were split they shared one\nfile, and a producer run silently deleted the human half.\n\nSo an absent fact is never something for you to fill in \"because nobody else will\". The brief already\nnames which facts are yours; anything it withholds has a home you cannot reach, and leaving it absent\nis the correct outcome rather than a gap you are working around.\n\n## Refs are stamped for you\n\nSupply slugs. The runtime turns each into its namespaced ref, attaches the governance scope and\nauthority, assigns versions and sorts the declarations. Do not author a ref, a version or an ordering;\na contract that asked you to would be asking you to fail on form rather than on substance.\n\n(This paragraph listed `retention-rules`, `data-categories-and-sources` and\n`recipients-and-processors` as examples. All three are required fact names, and naming three of eight\nas \"examples\" invited a drafter to treat them as a style to imitate rather than a set to use. The\nauthoritative list now arrives in the brief.)\n\n**For a concern a governed document requires, the slug is NOT yours to choose.** The brief you were\ngiven lists the exact `factSlug` for each one, taken from the engine catalog. Use it verbatim.\n\nThis is not a style preference. A clause cites a fact BY REF, the ref is stamped from your slug, and a\nfact answering the right question under a different name is a fact the document cannot cite — it reads\nas missing while your answer sits in the file. Measured on a real run: twenty facts declared, zero of\nthe eight a privacy notice requires, because the names were semantically adjacent and lexically\ndisjoint (`retention-period-schedule-status` for `retention-rules`).\n\nFor anything the catalog does NOT name, the slug is yours: use a stable, descriptive one that reads as\nthe question it answers. An application legitimately declares facts no document requires.\n\n## Verification\n\nBefore you finish, check each declaration against these:\n\n- [ ] every `KNOWN` value states something a reader could act on, and is traceable to accepted truth;\n- [ ] no declaration encodes a decision (legal basis, role, governing law, liability, chosen retention);\n- [ ] every `NOT_APPLICABLE` reason says why it does not apply, not that it could not be found;\n- [ ] a fact you could not establish is ABSENT, not guessed and not marked not-applicable;\n- [ ] the fact set is derived from the vision's compliance constraints, not from a generic SaaS template;\n- [ ] no `factSlug` is declared twice.\n\n## Approval\n\nThe derived fact set is presented to the creator before it becomes the committed `document-facts`\nfamily. Show it back as plain statements grouped by the question each answers, and name what you left\nout and why — the absences are the part a human most needs to see, because each one is a decision\nsomebody still owes.\n\n## Runtime context\n\nEverything above is already in your brief: `vision-brief` / `domain-plan` / `requirements` render as\ninput sections under \"# Accepted application truth\", and the application's live resource\nDECLARATIONS (retention mode, data-subject kind, subject export, retained see-through) arrive as\nthe declared `compliance_primary_facts` context section of your brief. Derive facts from those sections; there is no command to\nrun in this mode.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read current journey state and the artifacts you derive from.\n",
|
|
42
42
|
"skillRefs": [
|
|
43
43
|
"journey-status"
|
|
44
44
|
],
|
|
@@ -46,7 +46,9 @@
|
|
|
46
46
|
"compliance_primary_facts",
|
|
47
47
|
"document_fact_obligations"
|
|
48
48
|
],
|
|
49
|
-
"suspendsForClarification": false
|
|
49
|
+
"suspendsForClarification": false,
|
|
50
|
+
"briefAdequacyGate": false,
|
|
51
|
+
"briefAdequacyExcludedSources": []
|
|
50
52
|
},
|
|
51
53
|
"executor": "companion_agent",
|
|
52
54
|
"approval": "approve_result",
|
|
@@ -137,9 +137,8 @@ Before you start, read the current journey state, the vision brief that grounds
|
|
|
137
137
|
the brand's meaning, and any brand brief that already exists so you refine it
|
|
138
138
|
rather than re-eliciting it from scratch.
|
|
139
139
|
|
|
140
|
-
|
|
141
|
-
|
|
142
|
-
// TODO CLI COMMAND: wildo context brand-brief (read the existing brand brief, if any, to refine it)
|
|
140
|
+
(The vision and any previously landed brand brief arrive in your brief as the `vision-brief` and
|
|
141
|
+
`brand-brief` input sections.)
|
|
143
142
|
|
|
144
143
|
## References
|
|
145
144
|
|
|
@@ -1,14 +1,10 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.brand-identity",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.1",
|
|
4
4
|
"phase": "top_down",
|
|
5
5
|
"intent": "Brand-identity elicitation: draw the product's VISUAL identity out of the creator — the brand name, the logo creative direction (mark type, motifs, symbolism, imagery don'ts, background), and the visual tone (style keywords, mood, color story) — and capture it as a single validated BrandSnapshot (the `brand-brief` artifact family). The visual counterpart to the vision (intent) and market (verbal voice) briefs: it derives symbolism from the VisionSnapshot's idea/mission and, when a MarketSnapshot exists, translates its verbal `tonesOfVoice` into a visual register. The emitted brand-brief is the INPUT the companion logo step generates the master logo + derived assets from, and via `BrandSnapshot.resolvedAssets` the single source of truth every logo/favicon/brand-image consumer resolves against. Progressive: may persist a partially-directed brand (logoDirection/visualTone optional) and resume. v1 scaffold methodology — iterate the interview.",
|
|
6
6
|
"functionalTopics": [],
|
|
7
7
|
"preconditions": [
|
|
8
|
-
{
|
|
9
|
-
"kind": "phase_is",
|
|
10
|
-
"phase": "top_down"
|
|
11
|
-
},
|
|
12
8
|
{
|
|
13
9
|
"kind": "artifact_exists",
|
|
14
10
|
"selector": {
|
|
@@ -23,6 +19,9 @@
|
|
|
23
19
|
{
|
|
24
20
|
"family": "market-snapshot",
|
|
25
21
|
"intent": "voice"
|
|
22
|
+
},
|
|
23
|
+
{
|
|
24
|
+
"family": "brand-brief"
|
|
26
25
|
}
|
|
27
26
|
],
|
|
28
27
|
"outputs": [
|
|
@@ -34,7 +33,7 @@
|
|
|
34
33
|
],
|
|
35
34
|
"stepOutputs": [],
|
|
36
35
|
"method": {
|
|
37
|
-
"guidance": "# Brand Identity — Interview Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **brand-identity interviewer**. Your job is to draw the product's\nVISUAL identity out of the creator and capture it as a single typed\n**`BrandSnapshot`** — the `brand-brief` artifact. This is the visual\ncounterpart to the vision brief (which captured *intent*) and the market brief\n(which captured the *verbal* voice): here you capture what the product should\n**look like** and, specifically, the brief a logo is generated from.\n\nThe brand-brief you emit is not the logo itself — it is the *direction*. The\ncompanion logo step reads it to generate the master logo and every derived\nasset (favicon, apple-touch, maskable, OG, email, monochrome, dark/light), and\nthose become the single source of truth every surface resolves against. So an\nhonest, well-framed brief is the whole task. You do **not** generate pixels,\nset design-system color tokens, or restate the verbal brand voice — each is a\ndistinct concern with its own home.\n\n## Where the brief comes from\n\nYou do not invent a brand from nothing. Ground it in what the journey already\nknows:\n\n- **The vision brief is your source of meaning.** Read the `VisionSnapshot` and\n derive the mark's **symbolism** from the product's idea and mission — the\n mark should evoke what the product is *for*, not a decorative motif you liked.\n- **The market brief sharpens the register, when present.** If a\n `MarketSnapshot` exists, translate its verbal `tonesOfVoice` (the Nielsen\n Norman 4-axis voice) into a **visual** tone: a serious / formal voice reads as\n restrained geometry and a muted palette; a funny / casual voice reads as\n rounder forms and a warmer accent. The market brief is an *input*, not a\n precondition — if there is no market snapshot yet, derive the visual tone from\n the vision alone and note it as provisional.\n\n## The elicitation posture\n\n- **Interview, do not fill a form.** The typed questions on this playbook\n (`method.elicitation`) are your backbone, not your ceiling. Ask them in a\n natural order, reflect each answer back in one line, and let the creator\n correct you before moving on.\n- **Progressive is fine.** A `BrandSnapshot` requires only the **name**; the\n logo direction and visual tone are OPTIONAL and elicited progressively. If the\n creator can only name the brand today, capture it, note what is still open,\n and stop — the snapshot persists as partially-directed and this playbook can\n resume. Never invent a mark direction the creator did not give you.\n- **One product, one brand.** The snapshot is a single aggregate — one name,\n one logo direction, one visual tone. If the creator describes two brands,\n stop and ask which one this journey is for.\n\n## What you elicit — one aggregate\n\n- **Name** (REQUIRED). The anchor lexical identity: the exact, case-sensitive\n `brandName` the logo renders and every surface prints, plus an optional\n `tagline` to lock up with combination marks / OG imagery. Nothing visual\n here — the mark and the palette come next. A brand without a name has nothing\n for a mark to render; do not proceed until you have it.\n- **Logo direction** (optional, WARNed when absent). The creative brief the\n image model turns into the master logo:\n - `markType` — pick the archetype. **Default to `COMBINATION_MARK`** (symbol +\n wordmark) — it is the only archetype that natively yields BOTH a header\n lockup and a square symbol for favicons/app-icons. Reach for `WORDMARK`\n (text-only) only when the brand is genuinely wordmark-only; warn the creator\n that a wordmark cannot produce a clean square app icon.\n - `motifs` — concrete visual elements to include (short noun phrases).\n - `symbolism` — the meaning the mark should evoke, **derived from the vision\n mission/idea**.\n - `avoid` — imagery don'ts (the negative-prompt guardrails that keep output\n usable).\n - `backgroundTreatment` — keep `TRANSPARENT_ISOLATED` (the default and the\n only treatment that rasterizes losslessly into every derived asset). A\n solid field or contextual scene is an explicit opt-in the pipeline must\n compensate for — the validator WARNs on it.\n- **Visual tone** (optional, WARNed when absent). The aesthetic register — the\n VISUAL counterpart to the market voice: 3–7 concrete `styleKeywords`\n (\"geometric\", \"minimal\", \"warm\"), a one-line `mood`, a prose `colorIntent`\n (the color STORY, not hex values), and optional hex `colorSeeds` pinned only\n when the brand has already committed to anchors that must agree with the\n design system.\n\n## What you emit\n\nA single `BrandSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told otherwise).\n- `name` — the required anchor (`brandName`, optional `tagline`).\n- `logoDirection` / `visualTone` — the optional singletons, present only if elicited.\n- `resolvedAssets` — **leave empty.** This is the companion logo step's output,\n not something you author. Hand-authoring it fabricates asset references the\n pipeline will overwrite or the validator will flag.\n\nAuthor every entity in English. Follow the `brand-logo-authoring` skill for the\nexact field contracts and the mark-type / background / visual-tone decision\naids.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `brand-snapshot-valid`\ngate (`validateBrandSnapshot`) before it commits. A directed-but-ungenerated\nbrand (a `logoDirection` present, `resolvedAssets` still empty) is expected and\nonly WARNs — it is exactly the state you hand off to the companion logo step. A\nmissing logo direction and a missing visual tone are also warnings, reflecting a\nnot-yet-complete brief. Emit a clean brief and let the warnings stand honestly\nwhen the brand genuinely is not fully directed yet, rather than inventing a\nmark to silence them.\n\n## Approval\n\nThe drafted `BrandSnapshot` is presented to the creator for approval before it\nbecomes the committed `brand-brief`. Show the brief back in plain prose — the\nname, the mark direction, the visual tone — and let the creator confirm or\ncorrect it. The brand-brief is what the logo is generated from and what\npropagates everywhere; it is worth one explicit human sign-off before the mark\nis made.\n\n## Runtime context\n\nBefore you start, read the current journey state, the vision brief that grounds\nthe brand's meaning, and any brand brief that already exists so you refine it\nrather than re-eliciting it from scratch.\n\n
|
|
36
|
+
"guidance": "# Brand Identity — Interview Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **brand-identity interviewer**. Your job is to draw the product's\nVISUAL identity out of the creator and capture it as a single typed\n**`BrandSnapshot`** — the `brand-brief` artifact. This is the visual\ncounterpart to the vision brief (which captured *intent*) and the market brief\n(which captured the *verbal* voice): here you capture what the product should\n**look like** and, specifically, the brief a logo is generated from.\n\nThe brand-brief you emit is not the logo itself — it is the *direction*. The\ncompanion logo step reads it to generate the master logo and every derived\nasset (favicon, apple-touch, maskable, OG, email, monochrome, dark/light), and\nthose become the single source of truth every surface resolves against. So an\nhonest, well-framed brief is the whole task. You do **not** generate pixels,\nset design-system color tokens, or restate the verbal brand voice — each is a\ndistinct concern with its own home.\n\n## Where the brief comes from\n\nYou do not invent a brand from nothing. Ground it in what the journey already\nknows:\n\n- **The vision brief is your source of meaning.** Read the `VisionSnapshot` and\n derive the mark's **symbolism** from the product's idea and mission — the\n mark should evoke what the product is *for*, not a decorative motif you liked.\n- **The market brief sharpens the register, when present.** If a\n `MarketSnapshot` exists, translate its verbal `tonesOfVoice` (the Nielsen\n Norman 4-axis voice) into a **visual** tone: a serious / formal voice reads as\n restrained geometry and a muted palette; a funny / casual voice reads as\n rounder forms and a warmer accent. The market brief is an *input*, not a\n precondition — if there is no market snapshot yet, derive the visual tone from\n the vision alone and note it as provisional.\n\n## The elicitation posture\n\n- **Interview, do not fill a form.** The typed questions on this playbook\n (`method.elicitation`) are your backbone, not your ceiling. Ask them in a\n natural order, reflect each answer back in one line, and let the creator\n correct you before moving on.\n- **Progressive is fine.** A `BrandSnapshot` requires only the **name**; the\n logo direction and visual tone are OPTIONAL and elicited progressively. If the\n creator can only name the brand today, capture it, note what is still open,\n and stop — the snapshot persists as partially-directed and this playbook can\n resume. Never invent a mark direction the creator did not give you.\n- **One product, one brand.** The snapshot is a single aggregate — one name,\n one logo direction, one visual tone. If the creator describes two brands,\n stop and ask which one this journey is for.\n\n## What you elicit — one aggregate\n\n- **Name** (REQUIRED). The anchor lexical identity: the exact, case-sensitive\n `brandName` the logo renders and every surface prints, plus an optional\n `tagline` to lock up with combination marks / OG imagery. Nothing visual\n here — the mark and the palette come next. A brand without a name has nothing\n for a mark to render; do not proceed until you have it.\n- **Logo direction** (optional, WARNed when absent). The creative brief the\n image model turns into the master logo:\n - `markType` — pick the archetype. **Default to `COMBINATION_MARK`** (symbol +\n wordmark) — it is the only archetype that natively yields BOTH a header\n lockup and a square symbol for favicons/app-icons. Reach for `WORDMARK`\n (text-only) only when the brand is genuinely wordmark-only; warn the creator\n that a wordmark cannot produce a clean square app icon.\n - `motifs` — concrete visual elements to include (short noun phrases).\n - `symbolism` — the meaning the mark should evoke, **derived from the vision\n mission/idea**.\n - `avoid` — imagery don'ts (the negative-prompt guardrails that keep output\n usable).\n - `backgroundTreatment` — keep `TRANSPARENT_ISOLATED` (the default and the\n only treatment that rasterizes losslessly into every derived asset). A\n solid field or contextual scene is an explicit opt-in the pipeline must\n compensate for — the validator WARNs on it.\n- **Visual tone** (optional, WARNed when absent). The aesthetic register — the\n VISUAL counterpart to the market voice: 3–7 concrete `styleKeywords`\n (\"geometric\", \"minimal\", \"warm\"), a one-line `mood`, a prose `colorIntent`\n (the color STORY, not hex values), and optional hex `colorSeeds` pinned only\n when the brand has already committed to anchors that must agree with the\n design system.\n\n## What you emit\n\nA single `BrandSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told otherwise).\n- `name` — the required anchor (`brandName`, optional `tagline`).\n- `logoDirection` / `visualTone` — the optional singletons, present only if elicited.\n- `resolvedAssets` — **leave empty.** This is the companion logo step's output,\n not something you author. Hand-authoring it fabricates asset references the\n pipeline will overwrite or the validator will flag.\n\nAuthor every entity in English. Follow the `brand-logo-authoring` skill for the\nexact field contracts and the mark-type / background / visual-tone decision\naids.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `brand-snapshot-valid`\ngate (`validateBrandSnapshot`) before it commits. A directed-but-ungenerated\nbrand (a `logoDirection` present, `resolvedAssets` still empty) is expected and\nonly WARNs — it is exactly the state you hand off to the companion logo step. A\nmissing logo direction and a missing visual tone are also warnings, reflecting a\nnot-yet-complete brief. Emit a clean brief and let the warnings stand honestly\nwhen the brand genuinely is not fully directed yet, rather than inventing a\nmark to silence them.\n\n## Approval\n\nThe drafted `BrandSnapshot` is presented to the creator for approval before it\nbecomes the committed `brand-brief`. Show the brief back in plain prose — the\nname, the mark direction, the visual tone — and let the creator confirm or\ncorrect it. The brand-brief is what the logo is generated from and what\npropagates everywhere; it is worth one explicit human sign-off before the mark\nis made.\n\n## Runtime context\n\nBefore you start, read the current journey state, the vision brief that grounds\nthe brand's meaning, and any brand brief that already exists so you refine it\nrather than re-eliciting it from scratch.\n\n(The vision and any previously landed brand brief arrive in your brief as the `vision-brief` and\n`brand-brief` input sections.)\n\n## References\n\n- `.claude/skills/brand-logo-authoring/SKILL.md` — the field contracts for the\n `BrandSnapshot` (name / logoDirection / visualTone), the mark-type selection\n table, background derivation-safety, and deriving the visual tone from the\n market voice.\n- `.claude/skills/journey-status/SKILL.md` — read current journey state and\n whether a `vision-brief` / `brand-brief` already exists.\n",
|
|
38
37
|
"skillRefs": [
|
|
39
38
|
"journey-status",
|
|
40
39
|
"brand-logo-authoring"
|
|
@@ -113,7 +112,9 @@
|
|
|
113
112
|
]
|
|
114
113
|
},
|
|
115
114
|
"contextSources": [],
|
|
116
|
-
"suspendsForClarification": false
|
|
115
|
+
"suspendsForClarification": false,
|
|
116
|
+
"briefAdequacyGate": false,
|
|
117
|
+
"briefAdequacyExcludedSources": []
|
|
117
118
|
},
|
|
118
119
|
"executor": "companion_agent",
|
|
119
120
|
"approval": "approve_result",
|
|
@@ -5,10 +5,6 @@
|
|
|
5
5
|
"intent": "Turn the accepted market and requirements truth, plus the creator's own pricing intent, into a non-vacuous BusinessModelLiteSnapshot: the product-level revenue model and a sketch of pricing plans, each cross-linked to the market ICPs it is sold to and the requirements it unlocks. A PLANNING artifact carrying commercial INTENT — never the billing runtime, and never a price the creator did not state.",
|
|
6
6
|
"functionalTopics": [],
|
|
7
7
|
"preconditions": [
|
|
8
|
-
{
|
|
9
|
-
"kind": "phase_is",
|
|
10
|
-
"phase": "top_down"
|
|
11
|
-
},
|
|
12
8
|
{
|
|
13
9
|
"kind": "artifact_valid",
|
|
14
10
|
"selector": {
|
|
@@ -91,7 +87,9 @@
|
|
|
91
87
|
]
|
|
92
88
|
},
|
|
93
89
|
"contextSources": [],
|
|
94
|
-
"suspendsForClarification": false
|
|
90
|
+
"suspendsForClarification": false,
|
|
91
|
+
"briefAdequacyGate": false,
|
|
92
|
+
"briefAdequacyExcludedSources": []
|
|
95
93
|
},
|
|
96
94
|
"executor": "companion_agent",
|
|
97
95
|
"approval": "approve_result",
|
|
@@ -68,8 +68,6 @@ anything:
|
|
|
68
68
|
real market intent, the real requirements, and the real differentiation — not
|
|
69
69
|
from scratch.
|
|
70
70
|
|
|
71
|
-
// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)
|
|
72
|
-
// TODO CLI COMMAND: wildo context market-snapshot (read the benefits to map + any existing feature edges)
|
|
73
71
|
|
|
74
72
|
You **read** `market-snapshot` + `requirements` + `vision-brief`; you **write**
|
|
75
73
|
the refined `market-snapshot` (edge wired) and the `feature-drafts` family (the
|