@wildo-ai/framework-knowledge 1.1.2 → 1.1.4
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 +351 -18
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.d.ts +1 -2
- package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.js.map +1 -1
- package/dist/esm/index.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +3 -4
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +4 -4
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +3 -4
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +4 -4
- 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 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +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 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +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 +1 -2
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +1 -2
- 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 +2 -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 +3 -3
- 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 +1 -2
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -2
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +0 -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 +0 -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 +0 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +0 -1
- 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 +0 -1
- 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 +0 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +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 +0 -1
- 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 +0 -2
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +2 -2
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +0 -1
- 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 +0 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +0 -2
- 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 +9 -4
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +0 -1
- 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 +0 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +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 +0 -1
- 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 +0 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +0 -1
- 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/manifest.json +8 -9
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +13 -70
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +11 -19
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +5 -88
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +15 -8
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +4 -5
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +15 -8
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +4 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -7
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +22 -49
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +8 -17
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +15 -780
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +11 -11
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +20 -141
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +15 -10
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +3 -2
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +16 -11
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +14 -6
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +4 -2
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +16 -7
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +4 -21
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +65 -16
- package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-analysis/method.md +165 -51
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +43 -23
- package/dist/knowledge/playbooks/top_down.phase-gate/method.md +4 -8
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +7 -9
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +7 -9
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +15 -7
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +3 -3
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +16 -11
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +4 -2
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +15 -7
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +16 -11
- package/dist/knowledge/references/build-plan.task-graph.config.md +1 -45
- package/dist/knowledge/references/companion.technical-doc.service.md +2 -102
- package/dist/knowledge/references/example.config.app-shell.full.md +5 -0
- package/dist/knowledge/references/example.module.companion-exports.full.md +0 -1
- package/dist/knowledge/references/example.provider.backend-module-shape.md +0 -7
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +1 -0
- package/dist/knowledge/references/platform.config.saas.md +0 -51
- package/dist/knowledge/references/presets.models.surface-policy.md +10 -19
- package/dist/knowledge/references/saas.external-data.admin-endpoints.md +48 -0
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +11 -31
- package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +1 -0
- package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +0 -45
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +0 -198
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -164
- package/dist/knowledge/references/saas.models.engine-capabilities.md +6 -26
- package/dist/knowledge/references/saas.models.http-api-binding.md +29 -3
- package/dist/knowledge/references/saas.models.provider-capabilities.md +3 -4
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +2 -4
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +0 -2
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +0 -14
- package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +31 -11
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +2 -32
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +6 -29
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +0 -56
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +0 -22
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +0 -26
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +0 -45
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +1 -7
- package/dist/knowledge/references/zod.decorators.field-spec-params.md +5 -31
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +1 -44
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +0 -3
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +0 -1
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +0 -15
- package/dist/knowledge/registries/assurance-authority-bases.json +2 -3
- package/dist/knowledge/registries/framework-topics.json +11 -146
- package/dist/knowledge/registries/playbooks.json +18 -154
- package/dist/knowledge/registries/source-tags.json +630 -883
- package/dist/knowledge/skills/INDEX.md +3 -4
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +1 -2
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -16
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +9 -31
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +74 -252
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +8 -26
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +53 -97
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +21 -84
- package/dist/knowledge/skills/config-app-shell/SKILL.md +9 -31
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +12 -31
- package/dist/knowledge/skills/config-design-system/SKILL.md +1 -23
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +10 -19
- package/dist/knowledge/skills/config-navigation/SKILL.md +2 -75
- package/dist/knowledge/skills/config-saas/SKILL.md +2 -19
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +9 -30
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +0 -51
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +0 -7
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +1 -2
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +3 -4
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +0 -56
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +0 -56
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +0 -1
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +0 -56
- 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 +0 -213
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +1 -2
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +2 -4
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +0 -15
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +2 -224
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +0 -198
- package/dist/knowledge/skills/resource-external-data/SKILL.md +2 -0
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +29 -3
- package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +70 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +1 -22
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +8 -28
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +0 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +0 -17
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +0 -46
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +0 -15
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +0 -26
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +1 -7
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +0 -198
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +1 -44
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +0 -3
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +0 -1
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +0 -56
- package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +5 -31
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +0 -22
- package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +0 -45
- package/dist/knowledge/topic-index.json +220 -725
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +0 -1
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +0 -51
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +0 -43
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +0 -185
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +0 -64
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +0 -41
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +0 -100
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +0 -117
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +0 -86
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +0 -61
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +0 -41
- package/dist/knowledge/playbooks/top_down.compliance-research/method.md +0 -76
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +0 -42
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +0 -56
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +0 -42
- package/dist/knowledge/playbooks/top_down.market-research/method.md +0 -68
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -44
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +0 -239
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +0 -67
- package/dist/knowledge/references/placement-plan.config.md +0 -330
- package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +0 -34
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +0 -45
- package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +0 -65
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +0 -58
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +0 -118
- package/dist/knowledge/references/saas.models.file-upload-grant.md +0 -179
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +0 -124
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +0 -99
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +0 -127
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +0 -42
- package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +0 -29
- package/dist/knowledge/references/zod.decorators.data-categories.md +0 -197
- package/dist/knowledge/rules/resource-schema-awareness.md +0 -77
- package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +0 -124
- package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +0 -47
- package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +0 -98
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +0 -54
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +0 -232
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +0 -149
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +0 -114
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +0 -133
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +0 -111
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +0 -622
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +0 -192
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +0 -245
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +0 -134
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +0 -65
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +0 -127
- /package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/structured-artifact-action.json +0 -0
|
@@ -1,782 +1,17 @@
|
|
|
1
1
|
# Compliance document candidate method
|
|
2
2
|
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
| `document:governance.document-record-control` | how governed documents are themselves controlled |
|
|
19
|
-
|
|
20
|
-
Draft the **privacy notice** unless the run tells you otherwise. It is the one every application
|
|
21
|
-
holding personal data needs, and the only one whose facts the current derivation supplies.
|
|
22
|
-
|
|
23
|
-
Naming a document outside this set is not a smaller decision than it looks. Each of the six has a
|
|
24
|
-
concern composition the framework measures a draft against, so a seventh name is a document nobody can
|
|
25
|
-
state the gaps in — and stating the gaps is the whole point.
|
|
26
|
-
|
|
27
|
-
## One section per concern, and SAY which concern
|
|
28
|
-
|
|
29
|
-
Every section carries `concernRef`, from the closed compliance-concern vocabulary. **The composition
|
|
30
|
-
for each document is inlined at the end of this method** — one entry per concern, saying what it
|
|
31
|
-
asserts, what in the application it derives from, what state it usually reaches, and what closes it
|
|
32
|
-
when it cannot. Draft one section per concern, in the order given, and produce **every** one:
|
|
33
|
-
a concern nothing can answer becomes a section with a marked clause, never a missing heading.
|
|
34
|
-
|
|
35
|
-
Those entries are the difference between a draft that states its gaps and one that guesses at them.
|
|
36
|
-
Where a concern's entry names an issue number as the remedy, say so in `incompleteness.closedBy` —
|
|
37
|
-
`#89`, `#91` — because a numbered issue is a remedy a reader can open, and "application configuration
|
|
38
|
-
owner" is not.
|
|
39
|
-
|
|
40
|
-
Use `concernRef: null` only for a section that genuinely answers no concern: a preamble, a contact
|
|
41
|
-
block. It is not a way past a concern you found hard. A concern you cannot establish gets a SECTION,
|
|
42
|
-
with a clause marked incomplete — which is the mechanism this whole document exists around.
|
|
43
|
-
|
|
44
|
-
The value must be the concern's exact name. A near miss (`retention` for `retention-and-deletion`) is
|
|
45
|
-
worse than a null: it reports the concern as unaddressed while the document addresses it.
|
|
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.
|
|
88
|
-
## What a clause may say
|
|
89
|
-
|
|
90
|
-
The rule is ASSERT versus MARK, and the skill states it in full. In short: a clause may say "this is
|
|
91
|
-
not yet established"; it may not say something untrue.
|
|
92
|
-
|
|
93
|
-
- `DERIVED` — established by a fact this application has declared. Cite it in `factRefs`. A `DERIVED`
|
|
94
|
-
clause citing a fact the facts file does not declare is REFUSED before the write.
|
|
95
|
-
|
|
96
|
-
**A fact the application declared NOT APPLICABLE is a fact, and a clause may rest on it.** *"No
|
|
97
|
-
external analytics provider is configured"* is `DERIVED`, not incomplete: the application settled the
|
|
98
|
-
question and recorded the answer. Marking such a concern incomplete says the application does not
|
|
99
|
-
know something it does know, which is as wrong as overstating. What is refused is citing a fact the
|
|
100
|
-
facts file does not declare AT ALL.
|
|
101
|
-
- `NEEDS_FRAMEWORK` / `NEEDS_DECISION` / `NEEDS_CONFIGURATION` — mark it, and say in `incompleteness`
|
|
102
|
-
what is missing and who closes it. Four distinct suppliers, four distinct remedies; do not merge them.
|
|
103
|
-
|
|
104
|
-
**`NEEDS_DECISION` and `NEEDS_FRAMEWORK` are the pair most easily confused, and the difference is
|
|
105
|
-
the REMEDY.** `NEEDS_DECISION` means a surface exists and nobody filled it in — the reader goes and
|
|
106
|
-
answers. `NEEDS_FRAMEWORK` means there is NOWHERE to record the answer; telling a reader to decide
|
|
107
|
-
is telling them to write into a void.
|
|
108
|
-
|
|
109
|
-
Measured on 2026-08-30, a produced notice marked operator identity `NEEDS_DECISION` when no surface
|
|
110
|
-
for it existed at all, beside retention periods marked identically and genuinely just unfilled. Two
|
|
111
|
-
remedies, rendered the same, and a reader could act on neither.
|
|
112
|
-
|
|
113
|
-
**So every incomplete clause must NAME THE SURFACE its answer goes to**, or say plainly that none
|
|
114
|
-
exists. A gap with a named surface is a task; a gap without one is a request for work nobody has
|
|
115
|
-
scoped. The fragment you are working from names the surface where there is one — carry it into
|
|
116
|
-
`incompleteness` rather than leaving the reader to find it.
|
|
117
|
-
|
|
118
|
-
**`closedBy` must name WHO can reach that surface, and an ENGINE resource is not the application
|
|
119
|
-
author's to edit.** `retentionPolicy`, `systemAccessPolicy.exportSubject` and `.dataCategories()`
|
|
120
|
-
on an engine resource live in engine source. Writing "application authors must declare
|
|
121
|
-
`retentionPolicy` for each affected engine resource" hands the reader a task they cannot perform —
|
|
122
|
-
and a produced notice said exactly that, for 83 resources, in the same confident register as the
|
|
123
|
-
remedies that ARE actionable. An unreachable remedy is worse than an unnamed one: it looks like
|
|
124
|
-
work, gets scheduled, and fails when someone tries it.
|
|
125
|
-
|
|
126
|
-
Where the closer is the FRAMEWORK, say so plainly — "the framework must declare these on its own
|
|
127
|
-
resources" — and keep it separate from what this application owes.
|
|
128
|
-
|
|
129
|
-
Never fill an unresolved fact, infer a legal decision, or describe the draft as approved, compliant,
|
|
130
|
-
legally valid, released or published. Locale and jurisdiction are review inputs; leaving them
|
|
131
|
-
unresolved is a legitimate answer and never a reason not to draft.
|
|
132
|
-
|
|
133
|
-
## The refs you write, and their exact shape
|
|
134
|
-
|
|
135
|
-
Every `…Ref` field is a **namespaced ref**: `namespace:slug`, both halves lowercase, words joined by
|
|
136
|
-
hyphens. `clause:retention-duration-not-declared` is one; `clause:Retention Duration` is not, and a
|
|
137
|
-
whole draft is rejected for a single malformed one. Ref ARRAYS are arrays of those strings — never
|
|
138
|
-
objects, never `{ ref: … }`.
|
|
139
|
-
|
|
140
|
-
Per clause, all three ref arrays are required, and two need at least one entry:
|
|
141
|
-
|
|
142
|
-
- `factRefs` — the facts this clause rests on, exactly as the facts file declares them. It may be
|
|
143
|
-
EMPTY for a clause that establishes nothing (a marked clause often does).
|
|
144
|
-
- `sourcePolicyRefs` — at least one: what governs the statement. Use the fact authority the clause
|
|
145
|
-
rests on where there is one (`document-fact-authority:<slug>` from the facts file), otherwise the
|
|
146
|
-
policy area it belongs to (`policy:retention`, `policy:recipients`).
|
|
147
|
-
- `claimGuardRefs` — at least one: what this clause must NOT be read as claiming. These are the
|
|
148
|
-
boundaries you are already holding — `claim-guard:no-legal-applicability-claim`,
|
|
149
|
-
`claim-guard:no-invented-retention-period`, `claim-guard:known-fact-only`. Name the ones that apply
|
|
150
|
-
to this clause; do not repeat the same guard on every clause out of habit.
|
|
151
|
-
|
|
152
|
-
`reviewChecklistRefs` needs at least one (`review-checklist:<slug>`) — what a human must confirm before
|
|
153
|
-
this draft is worth anything. `limitationRefs` may be empty, but rarely should be: it is where you say
|
|
154
|
-
what the document does NOT cover, in your own words as the drafter, rather than leaving the reader to
|
|
155
|
-
discover it.
|
|
156
|
-
|
|
157
|
-
## Where the draft goes
|
|
158
|
-
|
|
159
|
-
It lands as a FILE in the application's specifications package, as an ordinary working edit. It is
|
|
160
|
-
accepted when a human commits it, and by nothing else. Landing is not approval, release or publication.
|
|
161
|
-
|
|
162
|
-
|
|
163
|
-
---
|
|
164
|
-
|
|
165
|
-
# The compositions
|
|
166
|
-
|
|
167
|
-
Each of the following is one document's full concern list. Use the one matching your `documentRef`
|
|
168
|
-
and ignore the rest.
|
|
169
|
-
|
|
170
|
-
## `document:public.privacy-notice` — thirteen concerns
|
|
171
|
-
|
|
172
|
-
### Concern: operator identity
|
|
173
|
-
|
|
174
|
-
**Asserts** — who legally operates the service: entity name, registered address, contact route for
|
|
175
|
-
data-protection questions, and a representative where one is required.
|
|
176
|
-
|
|
177
|
-
**Derives from** — `operatorComplianceIdentity` in `wildo.saas.config.ts`: the legal entity, its
|
|
178
|
-
registered address, the privacy contact route, and an Art. 27 representative where one is required.
|
|
179
|
-
|
|
180
|
-
The VALUE is never derivable — a legal entity is a fact about the world, not a property of a codebase.
|
|
181
|
-
What the framework provides is the PLACE to record it, and until 2026-08-30 it did not: this fragment
|
|
182
|
-
said "no engine change would close it", which was right about derivation and wrong about the home.
|
|
183
|
-
The consequence was concrete. A landing REPLACES the produced document on every run, so an operator
|
|
184
|
-
who answered by editing the document lost the answer at the next regeneration — the answer has to live
|
|
185
|
-
in the application or it does not survive.
|
|
186
|
-
|
|
187
|
-
**Completeness** — `DERIVED` when the identity is declared; `NEEDS_DECISION` when it is not.
|
|
188
|
-
|
|
189
|
-
⚠️ `NEEDS_DECISION`, not `NEEDS_FRAMEWORK`, and the distinction is load-bearing now that the surface
|
|
190
|
-
exists. `NEEDS_FRAMEWORK` means there is nowhere to record the answer; `NEEDS_DECISION` means there is
|
|
191
|
-
and nobody has. They have different remedies — build something, versus fill something in — and a
|
|
192
|
-
reader who cannot tell them apart cannot act on either. Say which surface the answer goes to.
|
|
193
|
-
|
|
194
|
-
**What closes it** — the operator declaring `operatorComplianceIdentity`. It is cheap and it can be
|
|
195
|
-
filled in later without redrafting anything around it, which is the reason it is not a blocker.
|
|
196
|
-
|
|
197
|
-
**Never infer it.** Not from the application name, not from a domain, not from another application,
|
|
198
|
-
not from model memory. A published legal document naming the wrong entity is worse than one that says
|
|
199
|
-
the entity is not yet recorded — the first misdirects a person exercising a right, the second tells
|
|
200
|
-
them the document is incomplete.
|
|
201
|
-
|
|
202
|
-
**Every document needs this fragment**, which makes it the clearest demonstration of why producing
|
|
203
|
-
with gaps beats blocking: the whole document set would be unproducible until one form is filled in.
|
|
204
|
-
|
|
205
|
-
|
|
206
|
-
### Concern: legal basis and controller/processor role
|
|
207
|
-
|
|
208
|
-
**Asserts** — the lawful basis for each processing purpose, and whether the operator acts as
|
|
209
|
-
controller or processor for it.
|
|
210
|
-
|
|
211
|
-
**Derives from** — `operatorComplianceIdentity.lawfulBases` and `.roleAllocations` in
|
|
212
|
-
`wildo.saas.config.ts`.
|
|
213
|
-
|
|
214
|
-
The DETERMINATIONS are never derivable — both are legal conclusions about the operator's own
|
|
215
|
-
arrangements, and the framework can show WHAT is processed and BY WHICH MECHANISM without establishing
|
|
216
|
-
under which basis or in which role. What it now provides is where to record the conclusion, so that a
|
|
217
|
-
regeneration reproduces it instead of destroying it.
|
|
218
|
-
|
|
219
|
-
**The role is a LIST, not a field, and the produced notice said so before the surface existed:**
|
|
220
|
-
*"This notice therefore does not assign a single legal role to all data processed in a workspace."* A
|
|
221
|
-
B2B SaaS is typically a processor for the records its customers put in and a controller for its
|
|
222
|
-
account holders' own data, simultaneously. `roleAllocations` carries one role per population, and a
|
|
223
|
-
document that collapses them into one is wrong about both.
|
|
224
|
-
|
|
225
|
-
**`LEGITIMATE_INTERESTS` cannot be declared without its assessment** — the schema refuses it. It is
|
|
226
|
-
the only Art. 6(1) basis whose lawfulness depends on a balancing test, so the bare claim asserts a
|
|
227
|
-
conclusion nobody reached.
|
|
228
|
-
|
|
229
|
-
**Completeness** — `DERIVED` when declared; `NEEDS_DECISION` when not. Never `NEEDS_FRAMEWORK`: there
|
|
230
|
-
is a surface, so the remedy is to fill it in, not to build something. Name the surface when reporting
|
|
231
|
-
the gap.
|
|
232
|
-
|
|
233
|
-
**What closes it** — the operator determining, per purpose, the basis and the role, ideally with
|
|
234
|
-
counsel, and declaring them in `operatorComplianceIdentity`. The tenancy fragment describes the SHAPE this usually takes in a B2B SaaS — processor for
|
|
235
|
-
the data a customer stores about its own people, controller for the data the operator holds about
|
|
236
|
-
account holders — but describing the common shape is not the same as determining this operator's, and
|
|
237
|
-
the produced document must not present the first as the second.
|
|
238
|
-
|
|
239
|
-
**This is the fragment most likely to be filled in by a confident guess**, because the shape is
|
|
240
|
-
familiar and the sentence is easy to write. Resist it. A basis stated in a published notice is a
|
|
241
|
-
position the operator has taken; a basis that was never determined is a position nobody can defend.
|
|
242
|
-
|
|
243
|
-
|
|
244
|
-
### Concern: personal data held
|
|
245
|
-
|
|
246
|
-
**Asserts** — which of the application's own records are about identifiable people, and which hold no
|
|
247
|
-
personal data of their own.
|
|
248
|
-
|
|
249
|
-
**Derives from** — each resource's `retentionPolicy.mode` (`ErasureRetentionMode`, in
|
|
250
|
-
`@wildo-ai/saas-models`), read for every resource the application declares:
|
|
251
|
-
|
|
252
|
-
| declaration | what the document may state |
|
|
253
|
-
|---|---|
|
|
254
|
-
| `RETAIN_AND_IMPERSONALIZE` | this record holds personal data; the fields marked `.impersonalizeWith()` are what is scrubbed on erasure |
|
|
255
|
-
| `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 |
|
|
256
|
-
| absent | the application has not said |
|
|
257
|
-
|
|
258
|
-
Read `dataSubjectPolicy.kind` for the SESSION question only. `NO_PRINCIPAL` is equally true of an
|
|
259
|
-
invoice and of a CRM contact, so it never tells you whether a record is about a person — the
|
|
260
|
-
retention mode does.
|
|
261
|
-
|
|
262
|
-
**Completeness** — `DERIVED` for every resource that declares a retention policy.
|
|
263
|
-
|
|
264
|
-
**An erasure-coverage gap does NOT license a claim about whether personal data is held.** The two are
|
|
265
|
-
different axes and the facts report them separately: `retentionPolicy` answers *what happens to this
|
|
266
|
-
row on erasure*, while a field's `.dataCategories()` answers *what kind of data is in it*. A resource
|
|
267
|
-
can declare the second and not the first, and 48 of the engine's 85 do.
|
|
268
|
-
|
|
269
|
-
So writing "N resources have no declared erasure treatment, so this notice cannot establish whether
|
|
270
|
-
they hold personal data" is an over-reach, and it contradicts the data-categories section of the same
|
|
271
|
-
document — which enumerates categories drawn from those very resources. It was produced twice on
|
|
272
|
-
2026-08-30 before this paragraph existed.
|
|
273
|
-
|
|
274
|
-
State the gap as what it is: those resources have not declared an erasure TREATMENT, so a notice
|
|
275
|
-
cannot say what an erasure does to them. Where the facts also report a category coverage for the same
|
|
276
|
-
origin, say what IS established alongside it.
|
|
277
|
-
`NEEDS_CONFIGURATION` for every resource that does not.
|
|
278
|
-
|
|
279
|
-
**What closes it** — the application's own authors declaring `retentionPolicy` on the resource. Name
|
|
280
|
-
the resources individually: the remedy is per-resource, and a count is not actionable.
|
|
281
|
-
|
|
282
|
-
|
|
283
|
-
### Concern: data categories
|
|
284
|
-
|
|
285
|
-
**Asserts** — which CATEGORIES of personal data are held: identity, contact details, credentials,
|
|
286
|
-
financial, usage, location, user content, professional, and any GDPR Art. 9 special-category or
|
|
287
|
-
Art. 10 criminal-offence data.
|
|
288
|
-
|
|
289
|
-
**Derives from** — each field's `.dataCategories()` declaration, reported per resource and unioned
|
|
290
|
-
across the application in the compliance-primary-facts section. One category is DERIVED rather than
|
|
291
|
-
declared: `credentials`, from `.isPassword()` / `.isOtp()` / `.isWriteOnlySecret()`, which are
|
|
292
|
-
markers the author already wrote.
|
|
293
|
-
|
|
294
|
-
**Nothing is derived from a field NAME.** `email`, `phone` and `dateOfBirth` are suggestive while
|
|
295
|
-
`notes` is not, so a category list assembled by pattern-matching identifiers is a guess presented as
|
|
296
|
-
an inventory — and its failure mode is silent, because whatever the guess misses is simply not
|
|
297
|
-
disclosed. The declaration exists so that never happens.
|
|
298
|
-
|
|
299
|
-
**Completeness** — `DERIVED` when the application declares categories; `NEEDS_CONFIGURATION` when it
|
|
300
|
-
declares none, or when the facts section lists OUTSTANDING fields.
|
|
301
|
-
|
|
302
|
-
**The two gaps are different and must not be written the same way.**
|
|
303
|
-
|
|
304
|
-
- A resource that declares no category at all may genuinely hold no personal data. Nothing
|
|
305
|
-
distinguishes "considered and not applicable" from "never asked", so state that the question is
|
|
306
|
-
unanswered — never that the application holds no personal data.
|
|
307
|
-
- A field the facts section lists as OUTSTANDING is a provable omission. The application already
|
|
308
|
-
declared that field personal by another door — an erasure scrub treatment, a portability
|
|
309
|
-
provenance, or a credential marker — so the missing category is an omission, not a judgement.
|
|
310
|
-
Name the field and its basis. Do not guess what it contains.
|
|
311
|
-
|
|
312
|
-
**Say WHICH special category, not that there is one.** A `special-category:*` value is Art. 9 data
|
|
313
|
-
and carries a lawful-basis condition of its own beyond Art. 6; `criminal-offence` is Art. 10, a
|
|
314
|
-
separate article with a different condition. "We process special category data" is not a disclosure —
|
|
315
|
-
the enum names the kind precisely so a notice can.
|
|
316
|
-
|
|
317
|
-
**Do NOT point at `Compliance_DataClassification`.** It exists, it is a four-level SENSITIVITY ladder
|
|
318
|
-
(public / internal / confidential / restricted) applied only to flows-actors configuration, and it
|
|
319
|
-
answers "how protected must this be" rather than "what kind of personal data is this". Using it here
|
|
320
|
-
would produce a notice describing protection levels where a reader expects data types. It is named
|
|
321
|
-
explicitly because it is a near-miss a reader will otherwise find and assume answers this concern.
|
|
322
|
-
|
|
323
|
-
|
|
324
|
-
### Concern: consent and preferences
|
|
325
|
-
|
|
326
|
-
**Asserts** — what the application asks consent for, at what granularity, and what a person's choice
|
|
327
|
-
actually controls.
|
|
328
|
-
|
|
329
|
-
**Derives from**
|
|
330
|
-
|
|
331
|
-
- `DataProcessingConsent` (`saas-models` → `compliance/privacy/privacy.shared.schemas.ts`):
|
|
332
|
-
`NONE` · `BASIC` · `ANALYTICS` · `MARKETING` · `FULL` — a ladder, so a level implies the ones below it.
|
|
333
|
-
- `analytics.requiredConsent` (`app-configuration-shared.shared.schemas.ts`, default `ANALYTICS`) —
|
|
334
|
-
the minimum consent level for ANALYTICS, and nothing wider.
|
|
335
|
-
- per-user `dataProcessingConsent` — the level each person actually chose.
|
|
336
|
-
|
|
337
|
-
⚠️ **`requiredConsent` is ANALYTICS-SCOPED, and this fragment claimed otherwise until 2026-08-30.**
|
|
338
|
-
It read "the minimum a person must give to use the service", which is a different and much larger
|
|
339
|
-
claim; the field sits inside `AnalyticsConfigSchema` and governs analytics alone. A drafter following
|
|
340
|
-
the old wording would have published that a person must consent to analytics in order to use the
|
|
341
|
-
product — false, and false about the one subject where a reader is most likely to act on it.
|
|
342
|
-
|
|
343
|
-
- `operatorComplianceIdentity.serviceConsentRequirement` (`wildo.saas.config.ts`) — what a person
|
|
344
|
-
must agree to in order to use the service AT ALL, and what that gate covers.
|
|
345
|
-
|
|
346
|
-
**`NONE` is a POSITIVE answer and the usual one.** The operator declaring that nothing is gated on
|
|
347
|
-
consent has answered the question; a document must state it as settled rather than treating it as an
|
|
348
|
-
absence. ABSENT is the different case — nobody was asked — and the brief distinguishes the two.
|
|
349
|
-
|
|
350
|
-
**A consent GATE is not a lawful BASIS.** For most B2B SaaS the basis for core processing is CONTRACT:
|
|
351
|
-
a person uses the product because their employer signed for it. A notice that reads a gate as a basis
|
|
352
|
-
states that their data is processed on consent they could withdraw, which is wrong about the single
|
|
353
|
-
most consequential thing in the document. The basis is declared per purpose in `lawfulBases`.
|
|
354
|
-
|
|
355
|
-
**Completeness** — `DERIVED` for the analytics gate, the per-user level, and the service-wide
|
|
356
|
-
requirement once declared; `NEEDS_DECISION` naming `serviceConsentRequirement` when it is not.
|
|
357
|
-
|
|
358
|
-
This was `NEEDS_FRAMEWORK` until 2026-08-30, correctly: there was nowhere to record the answer. Issue
|
|
359
|
-
#139 built the surface, so the remedy changed from "someone must build this" to "fill this in" — a
|
|
360
|
-
different party and a different task, which is why the two states are never interchangeable.
|
|
361
|
-
|
|
362
|
-
**Say the thing readers get wrong.** Consent is one lawful basis among several, and it is not the one
|
|
363
|
-
most B2B processing rests on. **Never write that all processing rests on consent, and never write
|
|
364
|
-
that accepting terms supplies a lawful basis** — accepting a contract is a different basis with
|
|
365
|
-
different consequences, and conflating them is the single most common defect in a generated privacy
|
|
366
|
-
notice. Which basis applies is a `NEEDS_DECISION`; see the legal-basis fragment.
|
|
367
|
-
|
|
368
|
-
|
|
369
|
-
### Concern: retention and deletion
|
|
370
|
-
|
|
371
|
-
**Asserts** — what happens to a record when its subject is erased, and how long records are kept.
|
|
372
|
-
|
|
373
|
-
Two questions, and the framework answers only the first.
|
|
374
|
-
|
|
375
|
-
**Derives from (the HOW — answerable)** — each resource's `retentionPolicy.mode`:
|
|
376
|
-
`RETAIN_AND_IMPERSONALIZE` keeps the row, freezes it, hides it from normal reads and scrubs the fields
|
|
377
|
-
marked `.impersonalizeWith()`; `RETAIN_ONLY` keeps and freezes a row that holds no personal data of
|
|
378
|
-
its own. Reading the per-field treatments tells the document exactly WHICH values are destroyed and
|
|
379
|
-
which survive, which is a genuinely strong statement most notices cannot make.
|
|
380
|
-
|
|
381
|
-
**Derives from (the HOW LONG)** — the application's `dataRetention` schedule, declared in its config
|
|
382
|
-
over four data classes: `RESOURCE_DATA` (its records), `FILES` (uploaded bytes), `AUDIT_LOGS` (the
|
|
383
|
-
tamper-evident trail, kept longest and for a different reason — it is the evidence an operator may
|
|
384
|
-
lawfully retain under GDPR Art. 17(3)) and `OPERATIONAL_LOGS`. Each declared class carries a period in
|
|
385
|
-
days AND the operator's stated reason for it.
|
|
386
|
-
|
|
387
|
-
The classes are the STORES on purpose: the same declaration answers what a notice must state and what
|
|
388
|
-
a backup-and-restore inventory must protect (issue #8).
|
|
389
|
-
|
|
390
|
-
**Completeness** — `DERIVED` for the treatment, and for each retention class the application HAS
|
|
391
|
-
declared. `NEEDS_DECISION` for each class it has not: the mechanism exists, so what is missing is an
|
|
392
|
-
operator's decision rather than an engine change. Do not let the derivable half hide the missing one —
|
|
393
|
-
a statement about erasure mechanics reads to a reader as an answer about retention, so both go in the
|
|
394
|
-
same breath.
|
|
395
|
-
|
|
396
|
-
**What closes it** — the operator deciding a period, and saying why. Not a framework change: issue #89
|
|
397
|
-
delivered the declaration surface, so an undeclared class is now an unanswered question rather than an
|
|
398
|
-
unaskable one.
|
|
399
|
-
|
|
400
|
-
**An UNDECLARED class is not "kept indefinitely" and not "deleted immediately".** It is a decision
|
|
401
|
-
nobody has taken, and the document must say exactly that.
|
|
402
|
-
|
|
403
|
-
**Never write a placeholder period.** "Typically 12 months" in a published notice is a commitment
|
|
404
|
-
nobody made and nothing enforces.
|
|
405
|
-
|
|
406
|
-
|
|
407
|
-
### Concern: recipients and processors
|
|
408
|
-
|
|
409
|
-
**Asserts** — who else receives personal data, in what role, and where they process it.
|
|
410
|
-
|
|
411
|
-
**Derives from (partial)** — the engine capabilities the application has a provider configured for
|
|
412
|
-
(`EngineCapability` in `saas-models` → `external-providers/engine-capabilities.shared.schemas.ts`).
|
|
413
|
-
That establishes THAT a third party is involved and WHAT FUNCTION it performs — email delivery,
|
|
414
|
-
storage, payments, LLM inference, observability.
|
|
415
|
-
|
|
416
|
-
**Derives from (the identities)** — the application's PROCESSOR REGISTER, which your brief renders
|
|
417
|
-
under *"Who else processes personal data"*. Per entry: the processor's **legal entity**, the
|
|
418
|
-
**regions** it processes in, and its own **subprocessors** with their regions.
|
|
419
|
-
|
|
420
|
-
**The register holds two kinds of entry and the brief labels them differently — say which.** A
|
|
421
|
-
CONFIGURED PROVIDER entry joins to the application's composition, so it can be checked against it: a
|
|
422
|
-
claim about a provider the application does not configure is detectable, and a configured provider
|
|
423
|
-
with no entry is reported as UNDECLARED. An AUTHORED entry — a hosting company, a CDN, a support desk
|
|
424
|
-
— joins to nothing, because no configuration mentions it. The framework can neither confirm it nor
|
|
425
|
-
notice its absence.
|
|
426
|
-
|
|
427
|
-
Both are real processors and both belong in the notice. What must not happen is presenting the second
|
|
428
|
-
with the authority of the first: an authored entry is the operator's word, and a document that reads
|
|
429
|
-
as though the framework verified it overstates what anyone checked.
|
|
430
|
-
|
|
431
|
-
**A SELF-HOSTED provider is not a recipient either, and this is the second way to get the section
|
|
432
|
-
wrong.** The brief's *"Who RUNS each bound provider"* block splits runtime-bound providers three ways:
|
|
433
|
-
THIRD-PARTY RECIPIENTS (vendor-hosted, so data reaches a third party — enumerate these with their
|
|
434
|
-
region), OPERATOR-RUN (self-hosted, so no third party receives anything — state them as processing
|
|
435
|
-
under the operator's own control, never as recipients), and UNANSWERED.
|
|
436
|
-
|
|
437
|
-
An UNANSWERED provider is bound to a runtime with no declared deployment model. **Do not assume
|
|
438
|
-
vendor-hosted.** It looks like the cautious reading and it is not: it publishes that a person's data
|
|
439
|
-
goes to a third party when nobody said so. Report it as not established, and name the surface —
|
|
440
|
-
`providerComplianceChoices` in `wildo.saas.config.ts`.
|
|
441
|
-
|
|
442
|
-
**A provider PROFILE is not a recipient.** The brief separates providers BOUND TO A RUNTIME — backend,
|
|
443
|
-
companion, workers, minions, a frontend service, which can process the application's data — from
|
|
444
|
-
provider profiles with no runtime binding. A profile says how to reach a provider; build-time tooling
|
|
445
|
-
lives there, and a coding agent operating on the workspace receives no customer records. Never name a
|
|
446
|
-
profile-only provider as a recipient. Naming one reads as caution and is a false statement about
|
|
447
|
-
somebody's data, exactly like omitting a real one.
|
|
448
|
-
|
|
449
|
-
The section joins the register to the RUNTIME-BOUND providers, so it tells you three different things
|
|
450
|
-
and they are not interchangeable:
|
|
451
|
-
|
|
452
|
-
- a provider WITH an entry — state its legal entity and regions. `DERIVED`.
|
|
453
|
-
- a provider listed **UNDECLARED** — it IS in use and nobody has established who it is. Name the
|
|
454
|
-
function it performs (the capability says that) and state that its identity and location are
|
|
455
|
-
outstanding. `NEEDS_DECISION`, closed by the operator establishing it.
|
|
456
|
-
- a provider listed **STALE** — declared but no longer configured. Do NOT name it as a recipient; it
|
|
457
|
-
receives nothing.
|
|
458
|
-
|
|
459
|
-
**Completeness** — `DERIVED` per provider that is declared, `NEEDS_DECISION` per provider that is not.
|
|
460
|
-
Not `NEEDS_FRAMEWORK` any more: issue #88 delivered the declaration surface, so an undeclared processor
|
|
461
|
-
is an unanswered question rather than an unaskable one.
|
|
462
|
-
|
|
463
|
-
**Never infer a region from a vendor's brand.** "It is a US company" is not a processing location, and
|
|
464
|
-
a transfer statement built on it is a claim about somebody's data made from a guess.
|
|
465
|
-
|
|
466
|
-
**Where the register is empty, the honest statement names the FUNCTIONS and admits the identities are
|
|
467
|
-
outstanding.**
|
|
468
|
-
"Third parties process data for email delivery, file storage and payments; their identities and
|
|
469
|
-
processing locations are not yet established in this document" is true, useful and specific. What is
|
|
470
|
-
forbidden is the other two moves: inventing a plausible vendor list, and omitting the section — the
|
|
471
|
-
first is false and the second lets a reader assume there are no recipients at all.
|
|
472
|
-
|
|
473
|
-
|
|
474
|
-
### Concern: international transfers
|
|
475
|
-
|
|
476
|
-
**Asserts** — whether personal data leaves its origin jurisdiction, to where, and under which transfer
|
|
477
|
-
mechanism.
|
|
478
|
-
|
|
479
|
-
**Derives from** — the processor register's regions, at BOTH levels: each declared processor and
|
|
480
|
-
each processor's own subprocessors. Your brief renders them under *"Personal data reaches processors
|
|
481
|
-
in: …"*.
|
|
482
|
-
|
|
483
|
-
Both levels, because the chain is what makes a transfer statement hard. An operator in France using a
|
|
484
|
-
French vendor that runs on a US cloud HAS a transfer, and reading only the vendor's region misses it.
|
|
485
|
-
|
|
486
|
-
**The question has three inputs and the framework holds ONE.** Where declared processors process is
|
|
487
|
-
derivable. Which jurisdiction is the ORIGIN, and which MECHANISM makes a given transfer lawful, are
|
|
488
|
-
legal determinations with a shelf life — adequacy decisions move by court ruling, so a list baked into
|
|
489
|
-
the engine would go stale silently and emit a false compliance statement. That is the worst failure
|
|
490
|
-
this lane has, so it is deliberately not modelled.
|
|
491
|
-
|
|
492
|
-
**Completeness** — three states, and they are three different claims. Do not round any of them up.
|
|
493
|
-
|
|
494
|
-
| the register | what you may state | completeness |
|
|
495
|
-
|---|---|---|
|
|
496
|
-
| ABSENT | nothing — where data lands is unknown | `NEEDS_CONFIGURATION` |
|
|
497
|
-
| declares NO processor | no personal data reaches a third party, so none is transferred THROUGH one | `DERIVED`, with the residual stated |
|
|
498
|
-
| declares processors | where data lands, region by region | `DERIVED` for location; the transfer POSITION stays `NEEDS_DECISION` |
|
|
499
|
-
|
|
500
|
-
**The residual is not optional wording.** "No processor receives personal data" establishes nothing
|
|
501
|
-
about the operator's OWN processing — its infrastructure, its staff, its own establishment. A document
|
|
502
|
-
that says "we do not transfer data internationally" on the strength of an empty register has answered
|
|
503
|
-
a larger question than it was asked.
|
|
504
|
-
|
|
505
|
-
**What closes the rest** — the transfer MECHANISM (adequacy, standard contractual clauses, binding
|
|
506
|
-
corporate rules, a derogation), recorded per subprocessor entry by a human informed by research. It is
|
|
507
|
-
chosen and documented rather than derived, and it is parked deliberately: transfers arrive late in a
|
|
508
|
-
company's life, and building the model before a real case exists would be guessing at its shape.
|
|
509
|
-
|
|
510
|
-
**"We do not transfer data internationally" is a claim, not a default.** It may be true, and it is
|
|
511
|
-
citable when an application has declared it as a fact — but it must never be produced because nothing
|
|
512
|
-
said otherwise. Absence of a region declaration means the region is unknown, which is the opposite of
|
|
513
|
-
knowing it stays put.
|
|
514
|
-
|
|
515
|
-
|
|
516
|
-
### Concern: automated decisions and AI
|
|
517
|
-
|
|
518
|
-
**Asserts** — where the application uses AI, on what data, and whether any of it decides something
|
|
519
|
-
about a person.
|
|
520
|
-
|
|
521
|
-
**Derives from (partial)** — the AI capabilities the application has a provider configured for:
|
|
522
|
-
`AI_LLM`, `AI_EMBEDDINGS`, `AI_DOCUMENT_EXTRACTION`, `AI_CODING_AGENT`. That establishes that AI is in
|
|
523
|
-
use and for what function.
|
|
524
|
-
|
|
525
|
-
**Not derivable** — whether any of it produces a **decision with a legal or similarly significant
|
|
526
|
-
effect** on a person, and whether a human reviews it. Nothing in the framework declares consequence or
|
|
527
|
-
human-review posture, and neither can be inferred from a capability being enabled.
|
|
528
|
-
|
|
529
|
-
**Derives from (the consequence)** — the AI POSTURE section of your brief, per ENABLED AI capability:
|
|
530
|
-
what it is used for, whether it `NO_DECISION` / `ASSISTS_HUMAN_DECISION` / `DECIDES_AUTONOMOUSLY`, and —
|
|
531
|
-
where it decides anything — how a person obtains human intervention.
|
|
532
|
-
|
|
533
|
-
An application enabling NO AI capability gets a plain statement to that effect: it performs no AI
|
|
534
|
-
processing of personal data. That is a positive, checkable answer, not a gap.
|
|
535
|
-
|
|
536
|
-
**Completeness** — `DERIVED` per capability with a declared posture; `NEEDS_DECISION` per capability
|
|
537
|
-
listed OUTSTANDING. Not `NEEDS_FRAMEWORK` any more: issue #92 delivered the declaration, so an
|
|
538
|
-
undeclared posture is an unanswered question rather than an unaskable one.
|
|
539
|
-
|
|
540
|
-
**An OUTSTANDING capability is not a harmless one.** This is the one concern where silence is more
|
|
541
|
-
dangerous than elsewhere: a notice describing AI use and saying nothing about consequence does not read
|
|
542
|
-
as "unknown", it reads as "nothing significant happens here" — which is the exemption, claimed for
|
|
543
|
-
free. State the gap explicitly.
|
|
544
|
-
|
|
545
|
-
**Why the distinction carries weight.** Automated decision-making with significant effects attracts
|
|
546
|
-
specific obligations — information about the logic, and a right to human intervention. A generated
|
|
547
|
-
notice must not silently claim the exemption by describing AI use without addressing consequence. The
|
|
548
|
-
honest statement says AI is used for these functions, and that whether any of it decides something
|
|
549
|
-
about a person is not yet established.
|
|
550
|
-
|
|
551
|
-
|
|
552
|
-
### Concern: analytics and tracking
|
|
553
|
-
|
|
554
|
-
**Asserts** — what is observed about how people use the service, and what a person's consent controls.
|
|
555
|
-
|
|
556
|
-
**Derives from (partial)** — the observability and analytics capabilities the application has
|
|
557
|
-
configured (`FRONTEND_PRODUCT_ANALYTICS`, `LLM_OBSERVABILITY`, `OBSERVABILITY_TELEMETRY`), together
|
|
558
|
-
with the consent ladder: `requiredConsent` and per-user `dataProcessingConsent` make
|
|
559
|
-
`DataProcessingConsent.ANALYTICS` a real, enforced boundary rather than a stated intention.
|
|
560
|
-
|
|
561
|
-
**Derives from (the inventory)** — the CLIENT STORAGE section of your brief: each cookie and storage
|
|
562
|
-
key, its mechanism, purpose, necessity and lifetime, split by who sets it.
|
|
563
|
-
|
|
564
|
-
The FRAMEWORK's own entries are listed first and belong in every application's table — `__wildo_refresh`
|
|
565
|
-
and `__wildo_anon_session`, both strictly necessary, both with lifetimes taken from the application's
|
|
566
|
-
session configuration. **No application authored these and every application sets them**, so a table
|
|
567
|
-
built only from what the application declared would omit the session cookie, which is the entry a
|
|
568
|
-
visitor is most certain to have.
|
|
569
|
-
|
|
570
|
-
Then, per frontend surface: its declared entries, an explicit "sets nothing of its own", or
|
|
571
|
-
UNINVENTORIED.
|
|
572
|
-
|
|
573
|
-
**UNINVENTORIED is not "sets nothing".** The first says nobody catalogued that surface; the second is a
|
|
574
|
-
positive statement. Writing the second from the first tells a visitor they are tracked by less than they
|
|
575
|
-
are, which is the under-reporting direction a notice must never fail in.
|
|
576
|
-
|
|
577
|
-
**Completeness** — `DERIVED` for the capability and consent posture, and for each surface that IS
|
|
578
|
-
inventoried; `NEEDS_DECISION` per uninventoried surface. Not `NEEDS_FRAMEWORK` any more: issue #91
|
|
579
|
-
delivered the declaration surface, so an uninventoried surface is an unanswered question rather than an
|
|
580
|
-
unaskable one.
|
|
581
|
-
|
|
582
|
-
Say both halves: which analytics are in use and what consent gates them (strong, derived, enforced), and
|
|
583
|
-
what the table still lacks — naming the surfaces, not the concern.
|
|
584
|
-
|
|
585
|
-
|
|
586
|
-
### Concern: subject rights
|
|
587
|
-
|
|
588
|
-
**Asserts** — which rights the application can actually honour, and through which mechanism. Not what
|
|
589
|
-
the law grants; what this application will do when asked.
|
|
590
|
-
|
|
591
|
-
**Derives from**
|
|
592
|
-
|
|
593
|
-
- `SubjectExportPurpose.ACCESS_ART_15` and `PORTABILITY_ART_20`
|
|
594
|
-
(`saas-models` → `compliance/privacy/subject-export.shared.schemas.ts`) — the two distinct export
|
|
595
|
-
bundles. Access is the broader one: every row concerning the subject, including rows they do not
|
|
596
|
-
own, such as an audit entry about them or a membership an administrator created.
|
|
597
|
-
- each resource's `systemAccessPolicy.exportSubject` — whether an export can answer for that resource
|
|
598
|
-
at all. **Absent means the resource is excluded from every export**, so an application that has not
|
|
599
|
-
declared it cannot honour Art. 15 over that data.
|
|
600
|
-
- `portabilityPolicy` and per-field `.portabilityProvenance()` — Art. 20 covers what the subject
|
|
601
|
-
supplied, not what the controller derived about them, and an Art. 20 export refuses on any field
|
|
602
|
-
that has declared neither.
|
|
603
|
-
- erasure: `eraseSubjectAsSystem(resourceType, rowIds)`, which takes a resource type and row ids and
|
|
604
|
-
needs no session. **An account is not required to be a data subject** — a contact, a lead or a
|
|
605
|
-
subscriber is erased by exactly this path.
|
|
606
|
-
|
|
607
|
-
**Completeness** — `DERIVED` where the resources hold `exportSubject` declarations.
|
|
608
|
-
|
|
609
|
-
**What closes it** — per-resource `exportSubject` and, for portability, a `portabilityPolicy` default
|
|
610
|
-
plus provenance on the fields that differ from it.
|
|
611
|
-
|
|
612
|
-
**Never state** that a right is honoured for a resource whose `exportSubject` is absent. The export
|
|
613
|
-
will not include it, and the notice would be describing a capability the application does not have.
|
|
614
|
-
|
|
615
|
-
|
|
616
|
-
### Concern: data exit
|
|
617
|
-
|
|
618
|
-
**Asserts** — what a customer gets back when they leave, in what form, and what happens to what
|
|
619
|
-
remains.
|
|
620
|
-
|
|
621
|
-
**Derives from** — `SubjectExportPurpose.PORTABILITY_ART_20` and the resources declaring
|
|
622
|
-
`exportSubject`; the account-closure path; and each resource's `retentionPolicy.mode`, which decides
|
|
623
|
-
whether a record is removed or **retained and impersonalized** on erasure.
|
|
624
|
-
|
|
625
|
-
**Completeness** — `DERIVED` for the mechanism.
|
|
626
|
-
|
|
627
|
-
**Retained-and-impersonalized is the part a reader must not be surprised by**, and the part a
|
|
628
|
-
generated document most often gets wrong by omission. A retained row is kept, frozen, hidden from
|
|
629
|
-
normal reads and reachable only through an audited privileged path — it is not deleted. Say so. A
|
|
630
|
-
notice that implies everything is erased, when financial and audit records are lawfully retained with
|
|
631
|
-
their personal fields scrubbed, is inaccurate in the direction that damages trust when discovered.
|
|
632
|
-
|
|
633
|
-
**How LONG anything is retained is not derivable** — see the retention-and-deletion fragment.
|
|
634
|
-
|
|
635
|
-
|
|
636
|
-
### Concern: tenancy model
|
|
637
|
-
|
|
638
|
-
**Asserts** — that customer data is separated per organization, and where the boundary between the
|
|
639
|
-
operator's responsibilities and the customer's lies.
|
|
640
|
-
|
|
641
|
-
**Derives from** — the `ORGANIZATIONS` engine capability, the organization scoping applied to every
|
|
642
|
-
tenant-scoped resource, and the cross-tenant admission rules (a crossing must be declared on the
|
|
643
|
-
operation and carries a usable access grant).
|
|
644
|
-
|
|
645
|
-
**Completeness** — `DERIVED`.
|
|
646
|
-
|
|
647
|
-
**This fragment is where shared responsibility is described, and it must never be flattened.** In a
|
|
648
|
-
B2B SaaS the operator is a PROCESSOR for the data a customer stores about its own people, and a
|
|
649
|
-
CONTROLLER for the data it holds about the customer's users as account holders. Those are different
|
|
650
|
-
roles with different duties over the same database. Say which is which; do not pick one and apply it
|
|
651
|
-
to everything.
|
|
652
|
-
|
|
653
|
-
**The attribution has a home now.** `operatorComplianceIdentity.roleAllocations` in
|
|
654
|
-
`wildo.saas.config.ts` carries one role per population of data — PROCESSOR for the records a customer
|
|
655
|
-
stores about its own people, CONTROLLER for the account data of the people who administer them. It is
|
|
656
|
-
a LIST for exactly the reason this fragment gives: those are different roles over the same database,
|
|
657
|
-
and a single field would force one of them to be wrong.
|
|
658
|
-
|
|
659
|
-
Where the attribution is not established, that is a `NEEDS_DECISION` — never a guess — and the
|
|
660
|
-
surface to name is `roleAllocations`. Not `NEEDS_FRAMEWORK`: there is somewhere to write the answer,
|
|
661
|
-
so the remedy is to fill it in rather than to build something. See the legal-basis fragment.
|
|
662
|
-
|
|
663
|
-
|
|
664
|
-
## `document:public.service-terms` — six concerns
|
|
665
|
-
|
|
666
|
-
### Concern: service scope
|
|
667
|
-
|
|
668
|
-
**Asserts** — what the service actually is: the modules it runs, the resources it manages, and the
|
|
669
|
-
surfaces it exposes.
|
|
670
|
-
|
|
671
|
-
**Derives from** — the application's declared modules and their resources, and the surfaces it builds
|
|
672
|
-
(application, API, public website, technical documentation).
|
|
673
|
-
|
|
674
|
-
**Completeness** — `DERIVED`.
|
|
675
|
-
|
|
676
|
-
**Derive it; do not describe the product from its marketing.** Scope in a governed document is the
|
|
677
|
-
boundary of what the statements around it apply to, so an aspirational description silently widens
|
|
678
|
-
every other clause. The declared modules are the honest boundary, and a capability the application
|
|
679
|
-
does not run does not belong here even if it is on the roadmap.
|
|
680
|
-
|
|
681
|
-
|
|
682
|
-
### Concern: commercial terms
|
|
683
|
-
|
|
684
|
-
**Asserts** — what is sold, how it is charged, and what happens on renewal, change and cancellation.
|
|
685
|
-
|
|
686
|
-
**Derives from** — the application's billing declarations
|
|
687
|
-
(`saas-models` → `billing/billing-enums.shared.schemas.ts`): `ProductType`, `BillingTiming`,
|
|
688
|
-
`ProrationBehavior`, `TaxCalculationMode`, plus the declared products and any usage metering.
|
|
689
|
-
|
|
690
|
-
**Completeness** — `DERIVED` where billing is configured; `NEEDS_CONFIGURATION` where the application
|
|
691
|
-
declares no products, in which case say that the commercial terms are not yet established rather than
|
|
692
|
-
describing a plan nobody has authored.
|
|
693
|
-
|
|
694
|
-
**Keep consumer and business audiences apart.** Consumer pre-contract obligations (withdrawal
|
|
695
|
-
periods, pre-contractual information) apply only when a declared audience includes consumers. A terms
|
|
696
|
-
document that blends both into one ambiguous set is worse than one that states which audience it is
|
|
697
|
-
for — so read the declared audience before writing a single clause about cancellation rights.
|
|
698
|
-
|
|
699
|
-
|
|
700
|
-
### Concern: governing law and liability
|
|
701
|
-
|
|
702
|
-
**Asserts** — which law governs the agreement, where disputes are heard, and how liability is limited.
|
|
703
|
-
|
|
704
|
-
**Derives from** — nothing. These are negotiated commercial and legal positions.
|
|
705
|
-
|
|
706
|
-
**Completeness** — `NEEDS_DECISION`.
|
|
707
|
-
|
|
708
|
-
**What closes it** — the operator deciding, with counsel. Note that liability limits interact with
|
|
709
|
-
the declared audience: consumer-facing terms cannot limit liability as freely as business-to-business
|
|
710
|
-
ones, so this fragment cannot be settled before the commercial-terms fragment establishes who the
|
|
711
|
-
terms are for.
|
|
712
|
-
|
|
713
|
-
**Never produce a liability clause from a template.** A limitation of liability that was copied
|
|
714
|
-
rather than decided is either unenforceable or committing the operator to something nobody agreed —
|
|
715
|
-
and unlike most gaps in a produced document, this one is not discovered until it matters.
|
|
716
|
-
|
|
717
|
-
|
|
718
|
-
## `document:governance.*` — the governance concerns
|
|
719
|
-
|
|
720
|
-
### Concern: security controls
|
|
721
|
-
|
|
722
|
-
**Asserts** — the security measures the application actually runs, at the level of detail a notice
|
|
723
|
-
needs and no further.
|
|
724
|
-
|
|
725
|
-
**Derives from** — the application's authored authentication configuration (methods enabled, MFA,
|
|
726
|
-
password policy, lockout, step-up, session lifetimes), its access floors, its encryption of stored
|
|
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.
|
|
732
|
-
|
|
733
|
-
**Completeness** — `DERIVED`, bounded.
|
|
734
|
-
|
|
735
|
-
**Bounded is the operative word.** A public notice states that measures exist and their general
|
|
736
|
-
nature. **It must not enumerate the control set**: a published list of exactly which protections are
|
|
737
|
-
in place, and by implication which are not, is a map for somebody attacking the service. Detail
|
|
738
|
-
belongs in a security addendum shared under agreement, not on a public page — so this fragment reads
|
|
739
|
-
very differently in `public.privacy-notice` than in a security schedule, and that difference is
|
|
740
|
-
deliberate rather than an omission.
|
|
741
|
-
|
|
742
|
-
**Never state a certification.** "Compliant", "certified", "audited" and "ISO/SOC" claims are not
|
|
743
|
-
derivable from configuration and are not this document's to make.
|
|
744
|
-
|
|
745
|
-
|
|
746
|
-
### Concern: audit and accountability
|
|
747
|
-
|
|
748
|
-
**Asserts** — that security-relevant actions are recorded, what kinds are recorded, and where those
|
|
749
|
-
records can be sent.
|
|
750
|
-
|
|
751
|
-
**Derives from** — the `COMPLIANCE_AUDIT_TRAIL` engine capability
|
|
752
|
-
(`saas-models` → `external-providers/engine-capabilities.shared.schemas.ts`), the auditable-event
|
|
753
|
-
catalog the engine emits (authentication, authorization grants, consent decisions, token lifecycle,
|
|
754
|
-
configuration and permission changes, cross-tenant administrative access), and per-organization SIEM
|
|
755
|
-
routing where a tenant has configured it.
|
|
756
|
-
|
|
757
|
-
**Completeness** — `DERIVED`.
|
|
758
|
-
|
|
759
|
-
This is one of the fragments where the ENGINE answers for the application. Every generated
|
|
760
|
-
application inherits the event catalog and the emitters; a document may state it without the
|
|
761
|
-
application having configured anything. Where a tenant has additionally routed events to its own
|
|
762
|
-
SIEM, that is the tenant's configuration and belongs in a shared-responsibility statement rather than
|
|
763
|
-
in the operator's own notice.
|
|
764
|
-
|
|
765
|
-
|
|
766
|
-
### Concern: access control and roles
|
|
767
|
-
|
|
768
|
-
**Asserts** — who inside the operator and inside a customer tenant can reach personal data, and what
|
|
769
|
-
constrains them.
|
|
770
|
-
|
|
771
|
-
**Derives from** — `CORE_APP_ROLES` and `CORE_ORG_ROLES`
|
|
772
|
-
(`saas-models` → `security/authorizations/roles.shared.schemas.ts`) plus the application's own role
|
|
773
|
-
table; the administrative-continuity floors (a tenant cannot be left with no usable owner, the
|
|
774
|
-
application cannot be left with no super-administrator); and the platform-access-grant mechanism,
|
|
775
|
-
under which a platform operator reaching into a customer tenant requires a granted, time-bounded
|
|
776
|
-
authorization rather than standing privilege, and every crossing is audited.
|
|
777
|
-
|
|
778
|
-
**Completeness** — `DERIVED`.
|
|
779
|
-
|
|
780
|
-
Worth stating plainly in a B2B notice, because it is the question a customer's own reviewer asks
|
|
781
|
-
first: **operator access to tenant data is not ambient.** It is declared per operation, requires a
|
|
782
|
-
usable grant, and is recorded when it happens.
|
|
3
|
+
Use the `compliance-document-authoring` skill and the exact host-supplied
|
|
4
|
+
blueprint and fact projection. Produce only the structured
|
|
5
|
+
`ApplicationAssuranceDocumentCandidateContentDraftV1` proposal requested by the
|
|
6
|
+
host.
|
|
7
|
+
|
|
8
|
+
Preserve section and clause order, exact semantic refs, fact bindings,
|
|
9
|
+
source-policy refs, claim-guard refs, variant selections, review checklists and
|
|
10
|
+
limitations. Do not fill an unresolved fact, infer a legal decision, copy
|
|
11
|
+
restricted text, or describe the candidate as approved, compliant, legally
|
|
12
|
+
valid, released or published.
|
|
13
|
+
|
|
14
|
+
Locale and jurisdiction are candidate review inputs, not proof of legal
|
|
15
|
+
applicability. Leave every unresolved or unsupported item visible. The trusted
|
|
16
|
+
runtime—not this method—validates the proposal, derives candidate status and
|
|
17
|
+
seals exact content and provenance digests.
|