@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
|
@@ -45,174 +45,10 @@ export enum DataMode {
|
|
|
45
45
|
*
|
|
46
46
|
* If not specified at resource level, uses `appConfig.database.defaultAdapter`.
|
|
47
47
|
*/
|
|
48
|
-
/**
|
|
49
|
-
* What an INTROSPECTION-backed resource projects.
|
|
50
|
-
*
|
|
51
|
-
* Declared BY THE AUTHOR beside the resource, exactly as `httpApiBinding` is, and for the same
|
|
52
|
-
* reason: the adapter answers "how rows are reached", and everything specific to THIS resource's
|
|
53
|
-
* reach is a typed declaration rather than runtime inference.
|
|
54
|
-
*
|
|
55
|
-
* Keeping it here rather than in a companion-side lookup table matters. A table keyed by resource
|
|
56
|
-
* type would be a second enumeration of a population the resource configs already define — the
|
|
57
|
-
* shape that silently drifts when one side gains an entry.
|
|
58
|
-
*/
|
|
59
|
-
export enum IntrospectionTenancyStance {
|
|
60
|
-
/**
|
|
61
|
-
* The rows describe the APPLICATION'S OWN STRUCTURE — its modules, resource specifications,
|
|
62
|
-
* design system, compliance declarations — and carry no tenant dimension, so there is nothing for
|
|
63
|
-
* a contextual scope predicate to filter on.
|
|
64
|
-
*
|
|
65
|
-
* This is the only stance implemented, and it is declared rather than inferred for the reason
|
|
66
|
-
* `HttpApiTenancyStance` gives for its own: an unstated stance is indistinguishable from an
|
|
67
|
-
* overlooked one. Every other repository enforces scoping ITSELF — Mongo and PostgreSQL through
|
|
68
|
-
* `buildContextualFilter`, HTTP_API through its tenancy stance — so a read-through adapter that
|
|
69
|
-
* simply returned whatever its source produced would be the one backing kind with no scoping
|
|
70
|
-
* story, and nobody would be asked to notice.
|
|
71
|
-
*/
|
|
72
|
-
APPLICATION_STRUCTURE = 'application-structure',
|
|
73
|
-
|
|
74
|
-
/**
|
|
75
|
-
* The rows are the DEVELOPMENT COMPANION'S OWN RUNTIME PROJECTIONS for the one application it
|
|
76
|
-
* serves — the playbook eligibility board, the build plan, the run write-register, the execution
|
|
77
|
-
* traces. Like `APPLICATION_STRUCTURE` they carry no tenant dimension and no scope predicate can
|
|
78
|
-
* apply; UNLIKE it, they are not derived from the application's source, and the tenancy stance is
|
|
79
|
-
* where that difference must stay visible (added 2026-09-01, creation-board resources plan):
|
|
80
|
-
*
|
|
81
|
-
* - `APPLICATION_STRUCTURE`'s public-read posture (`APP_PUBLIC` variants on the workbench's
|
|
82
|
-
* structural projections) rests on the rows being the application's OWN source, which anyone
|
|
83
|
-
* with the working tree can already read. That argument does NOT extend to runtime state, so a
|
|
84
|
-
* resource declaring this stance is expected to gate its variants on an authenticated role —
|
|
85
|
-
* never `APP_PUBLIC`.
|
|
86
|
-
* - Row-level tenant-anchor checks are bypassed for this stance exactly as for
|
|
87
|
-
* `APPLICATION_STRUCTURE` (the rows carry no anchor BY CONTRACT); authorization comes from the
|
|
88
|
-
* session and the operation's role gate.
|
|
89
|
-
*
|
|
90
|
-
* Fusing this into `APPLICATION_STRUCTURE` was rejected for the enum's own founding reason: an
|
|
91
|
-
* unstated distinction is indistinguishable from an overlooked one, and the next decision site
|
|
92
|
-
* keyed off the stance would inherit a claim nobody checked.
|
|
93
|
-
*/
|
|
94
|
-
APPLICATION_RUNTIME = 'application-runtime',
|
|
95
|
-
|
|
96
|
-
/**
|
|
97
|
-
* The rows carry a tenant dimension and a scope predicate must be pushed into the source.
|
|
98
|
-
*
|
|
99
|
-
* REFUSED AT REGISTRATION today: no introspection behavior takes a scope argument, so the engine
|
|
100
|
-
* has nothing to push down. Declared as a member rather than omitted so the refusal is explicit
|
|
101
|
-
* and a future scoped behavior is a deliberate design step — the alternative is that the first
|
|
102
|
-
* author needing it discovers the gap by shipping unscoped rows.
|
|
103
|
-
*/
|
|
104
|
-
SCOPE_FILTER_PUSHDOWN = 'scope-filter-pushdown',
|
|
105
|
-
}
|
|
106
|
-
|
|
107
|
-
export interface IntrospectionResourceBinding {
|
|
108
|
-
/**
|
|
109
|
-
* The companion introspection behavior whose output becomes this resource's rows.
|
|
110
|
-
*
|
|
111
|
-
* A plain string on purpose: the behavior catalog lives in the companion (23 behaviors as of
|
|
112
|
-
* 2026-08-29) and the engine must not depend on it. An unknown id is refused by the companion at
|
|
113
|
-
* read time, naming the id and the supported set.
|
|
114
|
-
*/
|
|
115
|
-
readonly behavior: string;
|
|
116
|
-
|
|
117
|
-
/**
|
|
118
|
-
* Path into the behavior's result that holds the rows, dot-separated. Omitted means the result
|
|
119
|
-
* itself is the row collection.
|
|
120
|
-
*
|
|
121
|
-
* Behaviors answer their own natural shape — `{ frontendChartRegistrationRefs: [...] }` — and
|
|
122
|
-
* teaching each one to answer a uniform envelope would change 23 working behaviors to suit a
|
|
123
|
-
* consumer that arrived later.
|
|
124
|
-
*/
|
|
125
|
-
readonly rowsPath?: string;
|
|
126
|
-
|
|
127
|
-
/**
|
|
128
|
-
* REQUIRED. Why these rows need no contextual scope predicate, or that they do.
|
|
129
|
-
*
|
|
130
|
-
* Not optional and not defaulted: a default would make "nobody thought about tenancy" and
|
|
131
|
-
* "tenancy does not apply here" the same declaration.
|
|
132
|
-
*/
|
|
133
|
-
readonly tenancy: IntrospectionTenancyStance;
|
|
134
|
-
|
|
135
|
-
/**
|
|
136
|
-
* Fields whose values COMPOSE each row's primary key, in order, when the behavior's rows carry no
|
|
137
|
-
* identifier of their own.
|
|
138
|
-
*
|
|
139
|
-
* Most introspection behaviors answer structural projections rather than records: a module row
|
|
140
|
-
* carries `moduleId` and needs nothing here, while a relationship row carries only the two
|
|
141
|
-
* resource types it joins. Without a key such a resource can be LISTed and never READ, because
|
|
142
|
-
* there is no value to address a row by.
|
|
143
|
-
*
|
|
144
|
-
* Composition is DECLARED rather than derived because only the author knows which fields are
|
|
145
|
-
* jointly unique for a given behavior — and being wrong is not hypothetical. `resourceType1` +
|
|
146
|
-
* `resourceType2` is unique across all 16 relationships in the dogfood application and is still
|
|
147
|
-
* unsafe in general, since the framework permits several edges between the same pair (a junction
|
|
148
|
-
* with two roles, a self-relationship). So the source FAILS LOUDLY when two rows compose the same
|
|
149
|
-
* key rather than serving both under one id, which would make READ return an arbitrary one of
|
|
150
|
-
* them and give no sign anything was wrong.
|
|
151
|
-
*
|
|
152
|
-
* The composed value is written to the resource's own `resourceFieldIdentifier`, which is the one
|
|
153
|
-
* key name resolvable from the registry without introspecting the schema's decorators. A resource
|
|
154
|
-
* declaring `identityFields` must therefore name that field as its primary key.
|
|
155
|
-
*
|
|
156
|
-
* The values are joined verbatim, so the key stays READABLE — `workspace__users__createdByUserId`
|
|
157
|
-
* rather than an opaque hash. That is possible because an INTROSPECTION-backed resource resolves
|
|
158
|
-
* to `ResourceIdFormat.INTROSPECTION_SYNTHESIZED`, which admits a URL-safe charset instead of the
|
|
159
|
-
* ObjectId-or-UUID rule platform rows follow.
|
|
160
|
-
*
|
|
161
|
-
* It was briefly a deterministic UUIDv5, before that format existed. Hashing worked and was the
|
|
162
|
-
* wrong trade: it made every id opaque, and it disguised the real property — a DERIVED id is only
|
|
163
|
-
* as stable as the fields it is derived from, and hiding that behind a hash removes the reader's
|
|
164
|
-
* ability to notice when a row's identity moves.
|
|
165
|
-
*
|
|
166
|
-
* Each value must be URL-safe (`[a-zA-Z0-9_-]`) and the whole key at most 255 characters; the
|
|
167
|
-
* source refuses per row rather than emitting a key that lists and cannot be read.
|
|
168
|
-
*
|
|
169
|
-
* Omit when the behavior's rows already carry an identifier of their own.
|
|
170
|
-
*/
|
|
171
|
-
readonly identityFields?: readonly string[];
|
|
172
|
-
}
|
|
173
|
-
|
|
174
48
|
export enum PersistenceAdapter {
|
|
175
49
|
MONGODB = 'mongodb',
|
|
176
50
|
POSTGRESQL = 'postgresql',
|
|
177
51
|
|
|
178
|
-
/**
|
|
179
|
-
* Rows are DERIVED on demand by asking the running dev companion to introspect the application —
|
|
180
|
-
* its resource registry, specifications, design system, compliance facts, assertions, market and
|
|
181
|
-
* persona context. Nothing is stored: every read recomputes.
|
|
182
|
-
*
|
|
183
|
-
* ## Why this is an adapter and not a service call
|
|
184
|
-
*
|
|
185
|
-
* The companion already computes all of it — 23 named introspection behaviors — and today each is
|
|
186
|
-
* reachable only through a bespoke route. Making it an adapter is what turns those behaviors into
|
|
187
|
-
* ordinary RESOURCES: list, read, filter, search, labels, navigation, all generated, with no
|
|
188
|
-
* per-behavior UI. That is the same argument `HTTP_API` settled on 2026-08-26 — the adapter answers
|
|
189
|
-
* "how rows are reached", and the mechanism behind it is a binding an author declares.
|
|
190
|
-
*
|
|
191
|
-
* Distinct from `HTTP_API`, deliberately, and not merely because the transport differs. Retrieval
|
|
192
|
-
* is the COMPANION's decision per behavior (amended 2026-09-01): the app-import behaviors run a
|
|
193
|
-
* SUBPROCESS that imports the target application's built modules — seconds per read, requiring
|
|
194
|
-
* that application's `dist`, failing as a thrown behavior — while the creation-plane behaviors
|
|
195
|
-
* are IN-PROCESS projections of the companion's own runtime services (playbook eligibility,
|
|
196
|
-
* build plan, write register, traces). Both reach the engine through the same
|
|
197
|
-
* `IntrospectionResourceSourceBackendPort`; the adapter never encodes the mechanism, which is
|
|
198
|
-
* exactly why a behavior id is an engine-opaque string. Collapsing this into `HTTP_API` would
|
|
199
|
-
* still be wrong for the original reason: its failure mode is a source throwing rather than a
|
|
200
|
-
* row being absent, and nothing here is reached over a network API.
|
|
201
|
-
*
|
|
202
|
-
* ## What every adapter decision site must honor
|
|
203
|
-
*
|
|
204
|
-
* - **READ-ONLY, absolutely.** There is no writable target: a row is a projection of the
|
|
205
|
-
* application's own source. Every write method refuses, as `HTTP_API`'s twelve do.
|
|
206
|
-
* - **No provisioning, migration or schema surface.** Nothing is stored, so there is nothing to
|
|
207
|
-
* create, migrate or verify — the platform must never believe it owns a store here.
|
|
208
|
-
* - **Never a legal application-wide DEFAULT adapter.** It is a per-resource declaration only;
|
|
209
|
-
* an application whose default was introspection could persist nothing at all.
|
|
210
|
-
* - **It must DEGRADE, never fail closed at boot.** The companion is the only thing that can run
|
|
211
|
-
* an introspection behavior, so a boot path that refuses on an introspection failure would need
|
|
212
|
-
* the companion to fix the companion — see `continuity-drift-and-cas-basis.md` Rule 3.
|
|
213
|
-
*/
|
|
214
|
-
INTROSPECTION = 'introspection',
|
|
215
|
-
|
|
216
52
|
/**
|
|
217
53
|
* Rows live in a system reached over an authenticated HTTP API and are queried on demand
|
|
218
54
|
* (read-through). Decided 2026-08-26 (ETL workstream, D1): this IS a persistence-adapter answer
|
|
@@ -55,13 +55,11 @@ export enum EngineCapability {
|
|
|
55
55
|
* extraction into `AI_LLM` would have made one `selection[AI_LLM].primary` decide all three,
|
|
56
56
|
* which is exactly the defect that split `AI_EMBEDDINGS` out of `AI_LLM`.
|
|
57
57
|
*
|
|
58
|
-
* ## Not to be confused with
|
|
58
|
+
* ## Not to be confused with `DOCUMENT_GENERATION`
|
|
59
59
|
*
|
|
60
|
-
* PDF generation — templates and data become bytes
|
|
61
|
-
*
|
|
62
|
-
*
|
|
63
|
-
* `EngineCapability.DOCUMENT_GENERATION` that this paragraph used to name; it was withdrawn
|
|
64
|
-
* because no provider capability could ever fill it.)
|
|
60
|
+
* `DOCUMENT_GENERATION` is PDF *generation* — templates and data become bytes. This is the
|
|
61
|
+
* opposite direction: bytes become text. The names are adjacent and the capabilities are
|
|
62
|
+
* unrelated; nothing routes between them.
|
|
65
63
|
*
|
|
66
64
|
* ## Absence is benign, and that is load-bearing
|
|
67
65
|
*
|
|
@@ -88,26 +86,8 @@ export enum EngineCapability {
|
|
|
88
86
|
*/
|
|
89
87
|
AI_CODING_AGENT = 'AI_CODING_AGENT',
|
|
90
88
|
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
* not any more. Neither could ever be filled — `PROVIDER_CAPABILITY_TO_ENGINE_CAPABILITY` had no
|
|
94
|
-
* entry pointing at either, so no provider capability token could claim the slot — while both were
|
|
95
|
-
* classified `SELECT_ONE`, which asserts that exactly one provider must be selected. Selecting one
|
|
96
|
-
* of zero candidates is not a resolution mode.
|
|
97
|
-
*
|
|
98
|
-
* Both capabilities are real and both are delivered elsewhere, which is why withdrawing the slots
|
|
99
|
-
* costs nothing: antivirus scanning is `InfraCapability.ANTIVIRUS_SCANNING`, fulfilled by ClamAV
|
|
100
|
-
* and consumed by `FileScanningBackendService`; PDF generation is the in-process `pdfTemplates`
|
|
101
|
-
* surface, with `InfraCapability.DOCUMENT_RENDERING` (Gotenberg) provisioned beside it. Neither
|
|
102
|
-
* has an external provider, and neither is planned to.
|
|
103
|
-
*
|
|
104
|
-
* Removing `ANTIVIRUS_SCANNING` also removes a collision: the identical spelling named an engine
|
|
105
|
-
* slot nothing could fill AND a live infra capability, in two packages, so a reader grepping the
|
|
106
|
-
* word landed in whichever they searched first.
|
|
107
|
-
*
|
|
108
|
-
* If a hosted AV or document-rendering vendor is ever adopted, the member comes back WITH its
|
|
109
|
-
* `PROVIDER_CAPABILITY_TO_ENGINE_CAPABILITY` entry and its own JSDoc in the same change.
|
|
110
|
-
*/
|
|
89
|
+
DOCUMENT_GENERATION = 'DOCUMENT_GENERATION',
|
|
90
|
+
ANTIVIRUS_SCANNING = 'ANTIVIRUS_SCANNING',
|
|
111
91
|
|
|
112
92
|
FRONTEND_ERROR_MONITORING = 'FRONTEND_ERROR_MONITORING',
|
|
113
93
|
FRONTEND_PRODUCT_ANALYTICS = 'FRONTEND_PRODUCT_ANALYTICS',
|
|
@@ -11,9 +11,35 @@
|
|
|
11
11
|
```typescript
|
|
12
12
|
export enum HttpApiTransportDialect {
|
|
13
13
|
/**
|
|
14
|
-
* OData v4
|
|
15
|
-
*
|
|
16
|
-
*
|
|
14
|
+
* OData **v4** — one generic client: mechanical pushdown of
|
|
15
|
+
* `$filter`/`$select`/`$top`/`$skip`/`$orderby`/`$count`, with a `$metadata` boot-time
|
|
16
|
+
* verification probe of the committed declaration.
|
|
17
|
+
*
|
|
18
|
+
* ⚠ **This member is v4 ONLY, and that excludes SAP's most-used API.** An earlier revision of
|
|
19
|
+
* this comment named "SAP S/4HANA, Microsoft Dataverse/Dynamics 365" here, which is half right
|
|
20
|
+
* and was load-bearing — it is why nobody looked:
|
|
21
|
+
*
|
|
22
|
+
* | Target | Version | Consumable today |
|
|
23
|
+
* |---|---|---|
|
|
24
|
+
* | Microsoft Dataverse / Dynamics 365 Web API (`/api/data/v9.2/`) | v4 | ✅ |
|
|
25
|
+
* | SAP S/4HANA OData **v4** services (`/sap/opu/odata4/…`) | v4 | ✅ |
|
|
26
|
+
* | SAP `API_BUSINESS_PARTNER` (`/sap/opu/odata/sap/API_BUSINESS_PARTNER`) | **v2** | ❌ |
|
|
27
|
+
*
|
|
28
|
+
* v2 is not a v4 variant with a different header. Its collection envelope is
|
|
29
|
+
* `{ "d": { "results": [...], "__next": …, "__count": … } }` rather than
|
|
30
|
+
* `{ "value": [...], "@odata.nextLink": … }`; `Edm.DateTime` serializes as `"/Date(<ticks>)/"`
|
|
31
|
+
* rather than ISO 8601; `Edm.Decimal` and `Edm.Int64` serialize as JSON STRINGS rather than
|
|
32
|
+
* numbers; and JSON must be requested (`$format=json`) because v2 defaults to Atom/XML. So it
|
|
33
|
+
* changes the envelope, the paging property, the count property AND the value encoding — a
|
|
34
|
+
* reader written for one cannot read the other, and the mapping layer needs coercions the way
|
|
35
|
+
* Odoo needs `ODOO_FALSE_AS_NULL`.
|
|
36
|
+
* spec-cite: OData Version 2.0 JSON Format
|
|
37
|
+
* (https://www.odata.org/documentation/odata-version-2-0/json-format/) — the `d`/`results`/
|
|
38
|
+
* `__next`/`__count` envelope, the `/Date(<ticks>)/` DateTime literal, and Edm.Decimal /
|
|
39
|
+
* Edm.Int64 "formatted as a JSON string".
|
|
40
|
+
*
|
|
41
|
+
* Supporting v2 is an OPEN decision, not an oversight. Until it lands, point an ODATA binding at
|
|
42
|
+
* a v4 service: for SAP that means the OData v4 edition of the API where one is published.
|
|
17
43
|
*/
|
|
18
44
|
ODATA = 'odata',
|
|
19
45
|
|
|
@@ -42,10 +42,9 @@ export const BUILTIN_PROVIDER_CAPABILITY = {
|
|
|
42
42
|
* a read of a PDF's existing text layer. Maps to `EngineCapability.AI_DOCUMENT_EXTRACTION`.
|
|
43
43
|
*
|
|
44
44
|
* A NEW token was genuinely required rather than convenient: `IMAGE_GENERATION` is an OUTPUT
|
|
45
|
-
* capability (text → image), and
|
|
46
|
-
* capability's exact opposite. Nothing in the existing vocabulary claimed the
|
|
47
|
-
* slot.
|
|
48
|
-
* withdrawn because no provider capability could fill it.)
|
|
45
|
+
* capability (text → image), and `EngineCapability.DOCUMENT_GENERATION` is PDF *generation*,
|
|
46
|
+
* which is this capability's exact opposite. Nothing in the existing vocabulary claimed the
|
|
47
|
+
* document-INPUT slot.
|
|
49
48
|
*
|
|
50
49
|
* Distinct from `LLM_CHAT` even where a vendor serves both from one API key: the work is
|
|
51
50
|
* different (a page-layout model, billed per page, with no sampling parameters), and fusing
|
|
@@ -306,9 +306,7 @@ export type ResourceConfiguration_BuilderParameters<
|
|
|
306
306
|
* stance, erasure stance, and remote-call semantics. The factory enforces presence/absence
|
|
307
307
|
* coherence and content-validates the declaration.
|
|
308
308
|
*/
|
|
309
|
-
httpApiBinding?:
|
|
310
|
-
/** REQUIRED when `persistenceAdapter` is INTROSPECTION; meaningless otherwise. */
|
|
311
|
-
introspectionBinding?: IntrospectionResourceBinding,
|
|
309
|
+
httpApiBinding?: HttpApiResourceBindingAuthored,
|
|
312
310
|
|
|
313
311
|
/**
|
|
314
312
|
* OPTIONAL inbound ETL pipeline on an ordinary LOCAL resource — "some resources local, some
|
|
@@ -319,7 +317,7 @@ export type ResourceConfiguration_BuilderParameters<
|
|
|
319
317
|
* targets exist, accept null unless `required`, and are excludeFromCreate/Update; CLOSED
|
|
320
318
|
* population refuses caller CREATE operations).
|
|
321
319
|
*/
|
|
322
|
-
externalDataPipeline?:
|
|
320
|
+
externalDataPipeline?: ExternalDataPipelineDeclarationAuthored,
|
|
323
321
|
|
|
324
322
|
isSystemResource?: boolean, // default false - true for core system resources (organizations, users, etc.), false for tenant-specific resources
|
|
325
323
|
|
|
@@ -60,8 +60,6 @@ export type ResourceConfiguration<
|
|
|
60
60
|
* (factory-enforced both ways). See the authoring-side declaration for the full contract.
|
|
61
61
|
*/
|
|
62
62
|
httpApiBinding?: HttpApiResourceBinding,
|
|
63
|
-
/** REQUIRED when `persistenceAdapter` is INTROSPECTION; meaningless otherwise. */
|
|
64
|
-
introspectionBinding?: IntrospectionResourceBinding,
|
|
65
63
|
|
|
66
64
|
/**
|
|
67
65
|
* The inbound ETL pipeline, when this LOCAL resource declared one — parsed + coherence-checked
|
|
@@ -19,20 +19,6 @@ export type ResourcesRegistry = {
|
|
|
19
19
|
resourceConfigurations: {
|
|
20
20
|
[key: ResourceType]: AnyResourceConfiguration ;
|
|
21
21
|
};
|
|
22
|
-
/**
|
|
23
|
-
* The resource types the APPLICATION registered — its own, never the engine's.
|
|
24
|
-
*
|
|
25
|
-
* The registry composes app and core factory maps into one `resourceConfigurations`, which is what
|
|
26
|
-
* every runtime consumer wants. This is the one place the two are still distinguishable, so the
|
|
27
|
-
* split is recorded HERE rather than re-derived by each consumer from a core key set — which would
|
|
28
|
-
* be a second enumeration of a population this file already knows.
|
|
29
|
-
*
|
|
30
|
-
* Its consumer today is the personal-data declaration report, which asks a question only an
|
|
31
|
-
* application author can act on: the engine declares its own posture on ~85 resources, and putting
|
|
32
|
-
* those in front of a reader of a report about THEIR application is how a diagnostic channel stops
|
|
33
|
-
* being read.
|
|
34
|
-
*/
|
|
35
|
-
applicationResourceTypes: ResourceType[];
|
|
36
22
|
/**
|
|
37
23
|
* Map of ResourceType to its standard field identifier (e.g., USERS -> userId).
|
|
38
24
|
* Used for FK field resolution without string manipulation.
|
|
@@ -10,8 +10,9 @@
|
|
|
10
10
|
|
|
11
11
|
```typescript
|
|
12
12
|
*
|
|
13
|
-
* Accepted application declaration of governed-document facts
|
|
14
|
-
* Import from
|
|
13
|
+
* Accepted application declaration of governed-document facts that cannot be
|
|
14
|
+
* inferred from framework code. Import from
|
|
15
|
+
* `@wildo-ai/saas-specifications/application-creation`.
|
|
15
16
|
*
|
|
16
17
|
* This family carries raw decisions only. It never authors contribution
|
|
17
18
|
* digests, accepted-head identities, validation receipts, reviewer grants,
|
|
@@ -25,15 +26,34 @@
|
|
|
25
26
|
* scope. Replacing a decision requires a new declaration/specification version
|
|
26
27
|
* and normal specification-family acceptance; conflicting current values are
|
|
27
28
|
* rejected at the authoring boundary instead of being hidden downstream.
|
|
28
|
-
*
|
|
29
|
-
* ## This file is REGENERATED, and that is why it accepts one authority kind
|
|
30
|
-
*
|
|
31
|
-
* `refinement.document-facts` rewrites it whole. Before #192 the same file also held the facts only a
|
|
32
|
-
* human may establish, so the next producer run silently deleted them — and there was no compare-and-
|
|
33
|
-
* swap to notice, by design (`.claude/rules/one-source-of-truth.md` Rule 0). The facts a human owns
|
|
34
|
-
* live in {@link ApplicationAuthoredDocumentFactSpecificationSchema}, in their own file, which no
|
|
35
|
-
* producer writes.
|
|
36
29
|
*/
|
|
37
|
-
export const ApplicationDocumentFactSpecificationSchema =
|
|
30
|
+
export const ApplicationDocumentFactSpecificationSchema = z
|
|
31
|
+
.strictObject({
|
|
32
|
+
schemaVersion: z.literal(1),
|
|
33
|
+
specificationRef: AssuranceNamespacedRefSchema,
|
|
34
|
+
specificationVersion: GovernedDocumentPositiveSafeIntegerSchema,
|
|
35
|
+
declarations: z.array(ApplicationDocumentFactDeclarationSchema).min(1),
|
|
36
|
+
})
|
|
37
|
+
.superRefine((specification, context) => {
|
|
38
|
+
if (!specification.specificationRef.startsWith("document-fact-specification:")) {
|
|
39
|
+
context.addIssue({
|
|
40
|
+
code: "custom",
|
|
41
|
+
message: "specificationRef must use the document-fact-specification: namespace",
|
|
42
|
+
path: ["specificationRef"],
|
|
43
|
+
});
|
|
44
|
+
}
|
|
45
|
+
const declarationIdentities = specification.declarations.map((declaration) => `${declaration.declarationRef}@${declaration.declarationVersion}`);
|
|
46
|
+
if (!valuesAreUnique(declarationIdentities) || !valuesAreLexicallySorted(declarationIdentities)) {
|
|
47
|
+
context.addIssue({ code: "custom", message: "declarations must be unique and lexically sorted by identity", path: ["declarations"] });
|
|
48
|
+
}
|
|
49
|
+
const factScopeKeys = specification.declarations.map(applicationDocumentFactDeclarationScopeKey);
|
|
50
|
+
if (!valuesAreUnique(factScopeKeys)) {
|
|
51
|
+
context.addIssue({
|
|
52
|
+
code: "custom",
|
|
53
|
+
message: "a specification may declare only one current value for each fact version and governance scope",
|
|
54
|
+
path: ["declarations"],
|
|
55
|
+
});
|
|
56
|
+
}
|
|
57
|
+
});
|
|
38
58
|
export type ApplicationDocumentFactSpecification = z.infer<typeof ApplicationDocumentFactSpecificationSchema>;
|
|
39
59
|
```
|
package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md
CHANGED
|
@@ -1039,28 +1039,7 @@ const AssuranceDocumentAuthorityCatalogV2BaseSchema = AssuranceDocumentAuthority
|
|
|
1039
1039
|
});
|
|
1040
1040
|
const AssuranceDocumentAuthorityCatalogV2Schema = AssuranceDocumentAuthorityCatalogV2BaseSchema.superRefine(refineAssuranceDocumentAuthorityCatalogBlueprints);
|
|
1041
1041
|
|
|
1042
|
-
/**
|
|
1043
|
-
* Blueprint v2 plus a closed, exactly consumed structured-value-contract registry.
|
|
1044
|
-
*
|
|
1045
|
-
* ASPIRATIONAL, by decision — 2026-08-31, issue #148. The shape is designed, refined and tested, and
|
|
1046
|
-
* it has no instance and no consumer. Measured on that date, `structuredValueContracts` and
|
|
1047
|
-
* `annexBindings` appear in exactly two files: this one, and `assurance-document-structured-contract.schemas.test.ts`.
|
|
1048
|
-
* There is no producer, no reader, and no implementation behind
|
|
1049
|
-
* `AssuranceDocumentStructuredContentProcessorIdentitySchema` — nothing consumes an annex-bound
|
|
1050
|
-
* structured value. `AssuranceDocumentAuthorityCatalogV3Schema` itself is referenced twice, both in
|
|
1051
|
-
* this file: its declaration and the union member below.
|
|
1052
|
-
*
|
|
1053
|
-
* So moving the engine's six document definitions to v3 would mean authoring structured value
|
|
1054
|
-
* contracts that nothing reads, which `.claude/rules/application-creation-directive.md` forbids in
|
|
1055
|
-
* as many words: "If we write a log or record, something or someone actually reads it — otherwise we
|
|
1056
|
-
* do not write it." The migration was rejected on that ground, NOT on effort.
|
|
1057
|
-
*
|
|
1058
|
-
* WHAT WOULD CHANGE THE DECISION: a consumer for annex-bound structured values — something that
|
|
1059
|
-
* renders or validates a document annex from a `structuredValueContract` (a processor register or a
|
|
1060
|
-
* retention schedule as a machine-readable table rather than prose). Build that first; the catalog
|
|
1061
|
-
* migration is then mechanical and worth doing. Until then v2/catalogVersion 5 is the current, correct
|
|
1062
|
-
* and fully-refined shape, and v3 stays available for the author who has that consumer.
|
|
1063
|
-
*/
|
|
1042
|
+
/** Current authoring branch: blueprint v2 plus a closed, exactly consumed structured-value-contract registry. */
|
|
1064
1043
|
export const AssuranceDocumentAuthorityCatalogV3Schema = AssuranceDocumentAuthorityCatalogCommonSchema.extend({
|
|
1065
1044
|
schemaVersion: z.literal(3),
|
|
1066
1045
|
catalogVersion: z.literal(6),
|
|
@@ -1124,16 +1103,7 @@ export const AssuranceDocumentAuthorityCatalogV3Schema = AssuranceDocumentAuthor
|
|
|
1124
1103
|
}
|
|
1125
1104
|
});
|
|
1126
1105
|
|
|
1127
|
-
/**
|
|
1128
|
-
* All three versions are ACCEPTED for authoring. v3 is available, not mandated — see the note on
|
|
1129
|
-
* `AssuranceDocumentAuthorityCatalogV3Schema`.
|
|
1130
|
-
*
|
|
1131
|
-
* This comment used to read "Retained v1/v2 catalogs remain parse-only; every newly authored catalog
|
|
1132
|
-
* uses v3/catalogVersion 6." That was false in the only way that mattered: the repository's one
|
|
1133
|
-
* catalog — `createInitialAssuranceDocumentAuthorityCatalog()` — is v2/catalogVersion 5, so the
|
|
1134
|
-
* sentence declared the sole live instance non-authorable. A builder who read it, opened the catalog
|
|
1135
|
-
* and found v2 had no way to tell a stale document from a stale catalog (issue #148).
|
|
1136
|
-
*/
|
|
1106
|
+
/** Retained v1/v2 catalogs remain parse-only; every newly authored catalog uses v3/catalogVersion 6. */
|
|
1137
1107
|
export const AssuranceDocumentAuthorityCatalogSchema = z.discriminatedUnion("schemaVersion", [
|
|
1138
1108
|
AssuranceDocumentAuthorityCatalogV1Schema,
|
|
1139
1109
|
AssuranceDocumentAuthorityCatalogV2Schema,
|
|
@@ -695,13 +695,7 @@ export const AssuranceProgramObligationEntrySchema = z
|
|
|
695
695
|
});
|
|
696
696
|
export type AssuranceProgramObligationEntry = z.infer<typeof AssuranceProgramObligationEntrySchema>;
|
|
697
697
|
|
|
698
|
-
/**
|
|
699
|
-
* Complete application obligation inventory. It is not the governed-document release register.
|
|
700
|
-
*
|
|
701
|
-
* It carried a digest until the Phase-A demolition (`.claude/rules/one-source-of-truth.md` Rule 0) and the JSDoc went on calling it "content-addressed" afterwards. The
|
|
702
|
-
* strict shape below is the whole truth: a ref, a version and the entries. Completeness is proven by `obligationCoverageDecisions` and the uniqueness refinement, not
|
|
703
|
-
* by a hash. A test still named `registerWithoutDigest` is a leftover from when the field existed.
|
|
704
|
-
*/
|
|
698
|
+
/** Complete, content-addressed application obligation inventory. It is not the governed-document release register. */
|
|
705
699
|
export const AssuranceProgramObligationRegisterSchema = z
|
|
706
700
|
.strictObject({
|
|
707
701
|
schemaVersion: z.literal(1),
|
|
@@ -1219,16 +1213,7 @@ const AssuranceProgramV3CommonFieldsSchema = z.strictObject({
|
|
|
1219
1213
|
...AssuranceProgramCommonFieldsAfterObjectiveBindingsSchema.shape,
|
|
1220
1214
|
});
|
|
1221
1215
|
|
|
1222
|
-
/**
|
|
1223
|
-
* Historical source-revision-pinned program. Retained payloads remain parseable and replayable.
|
|
1224
|
-
*
|
|
1225
|
-
* This said "new authoring is forbidden by the repository pin checker" until 2026-09-01. **Nothing forbids it.** That checker was
|
|
1226
|
-
* `pnpm check:assurance-revision-pin`, removed on 2026-08-27 with the rest of the digest mechanism, and no successor exists — the
|
|
1227
|
-
* only assurance check in `package.json` is `check:assurance-control-boundary`, which is about marker source-neutrality.
|
|
1228
|
-
*
|
|
1229
|
-
* So v1 is discouraged by this comment and by nothing else. A safety claim standing on a removed mechanism is worse than no claim,
|
|
1230
|
-
* because a reader stops looking for the guard. Building one is #221; until it lands, "forbidden" means "please do not".
|
|
1231
|
-
*/
|
|
1216
|
+
/** Historical source-revision-pinned program. Retained payloads remain parseable and replayable but new authoring is forbidden by the repository pin checker. */
|
|
1232
1217
|
export const AssuranceProgramSpecificationV1Schema = z
|
|
1233
1218
|
.strictObject({
|
|
1234
1219
|
schemaVersion: z.literal(1),
|
|
@@ -1246,17 +1231,9 @@ export type AssuranceProgramSpecificationV1 = z.infer<typeof AssuranceProgramSpe
|
|
|
1246
1231
|
*
|
|
1247
1232
|
* Validation authorities currently carry one sealed basis snapshot. Accepting several authored bases would make
|
|
1248
1233
|
* every extra basis compare against the wrong inventory and could misclassify an unverified authority as tolerable
|
|
1249
|
-
* host drift. Multi-basis composition therefore requires a later schema version with basis-indexed snapshots.
|
|
1250
|
-
*
|
|
1251
|
-
*
|
|
1252
|
-
* 2026-09-01. There is no such checker — see the note on {@link AssuranceProgramSpecificationV1Schema}. The intent
|
|
1253
|
-
* stands and is worth keeping: after an application accepts v3, v2 should remain replayable rather than become a
|
|
1254
|
-
* second current authoring shape. It is an intent, not an enforced one (#221).
|
|
1255
|
-
*
|
|
1256
|
-
* Exactly one v2 programme exists today, `examples/your-app`, and it is the only assurance programme in the
|
|
1257
|
-
* repository. (`examples/wonder-crm/specifications/src/compliance/index.ts` is a PROCESSOR REGISTER, not a
|
|
1258
|
-
* programme — its `schemaVersion: 1` belongs to `ApplicationProcessorRegisterSchema`, and a grep for the first
|
|
1259
|
-
* `schemaVersion` in a file named `compliance/` reads it as a v1 programme.)
|
|
1234
|
+
* host drift. Multi-basis composition therefore requires a later schema version with basis-indexed snapshots. The
|
|
1235
|
+
* repository checker continues recognizing existing v2 application authoring only through the serialized pre-v3
|
|
1236
|
+
* transition; after Wonder accepts v3, v2 remains replayable rather than becoming a second current authoring shape.
|
|
1260
1237
|
*/
|
|
1261
1238
|
export const AssuranceProgramSpecificationV2Schema = z
|
|
1262
1239
|
.strictObject({
|
|
@@ -1272,7 +1249,7 @@ export type AssuranceProgramSpecificationV2 = z.infer<typeof AssuranceProgramSpe
|
|
|
1272
1249
|
|
|
1273
1250
|
/**
|
|
1274
1251
|
* Current application program. It preserves the v2 single-basis authority model while replacing the overlapping
|
|
1275
|
-
* control-objective-binding array with one complete obligation register and its program-owned review
|
|
1252
|
+
* control-objective-binding array with one complete, digest-bound obligation register and its program-owned review
|
|
1276
1253
|
* records. Activation and operating/evidence truth remain deliberately unrepresentable.
|
|
1277
1254
|
*/
|
|
1278
1255
|
export const AssuranceProgramSpecificationV3Schema = z
|
|
@@ -54,7 +54,6 @@ export interface SpecificationsCompanionExports<
|
|
|
54
54
|
TRequirementsSnapshot = RequirementsSnapshot,
|
|
55
55
|
TRoadmapSnapshot = RoadmapSnapshot,
|
|
56
56
|
TBuildPlanTaskGraph = BuildPlanTaskGraph,
|
|
57
|
-
TPlacementPlan = PlacementPlan,
|
|
58
57
|
TDomainPlanOutputSet = DomainPlanOutputSet,
|
|
59
58
|
TBusinessModelLiteSnapshot = BusinessModelLiteSnapshot,
|
|
60
59
|
// Appended STRICTLY LAST (positional generics — never insert mid-list):
|
|
@@ -82,14 +81,6 @@ export interface SpecificationsCompanionExports<
|
|
|
82
81
|
// Appended STRICTLY LAST: release-process selection is a separate accepted
|
|
83
82
|
// decision, never an implicit default of routing or document necessity.
|
|
84
83
|
TDocumentReleasePolicySpecification = ApplicationDocumentReleasePolicySpecification,
|
|
85
|
-
// Appended STRICTLY LAST: WHO else processes personal data, under what legal
|
|
86
|
-
// identity and where (issue #88). Optional, and the optionality is the design:
|
|
87
|
-
// a partial register is useful and its holes are REPORTED per provider against
|
|
88
|
-
// the application's configured set, rather than blocking anything.
|
|
89
|
-
TProcessorRegister = ApplicationProcessorRegister,
|
|
90
|
-
// Appended STRICTLY LAST: the human half of the document facts, in its own
|
|
91
|
-
// family, because the derived one is REGENERATED whole (#192).
|
|
92
|
-
TAuthoredDocumentFactSpecification = ApplicationAuthoredDocumentFactSpecification,
|
|
93
84
|
> {
|
|
94
85
|
resourceSpecifications: TResourceSpecifications;
|
|
95
86
|
applicationBusinessSemanticsSnapshot?: TBusinessSemanticsSnapshot;
|
|
@@ -320,22 +311,6 @@ export interface SpecificationsCompanionExports<
|
|
|
320
311
|
* `validateBuildPlanTaskGraph` on the value before wiring it here.
|
|
321
312
|
*/
|
|
322
313
|
buildPlanSpecification?: TBuildPlanTaskGraph;
|
|
323
|
-
/**
|
|
324
|
-
* Application **placement** specification — WHERE every settings destination,
|
|
325
|
-
* resource operation and app view sits in the shell, and WHY (`PlacementPlan`,
|
|
326
|
-
* `_core/placement-plan/`).
|
|
327
|
-
*
|
|
328
|
-
* Produced by the `bottom_up.placement-plan` playbook as an expert-panel
|
|
329
|
-
* DELIBERATION rather than a creator elicitation: the creator does not choose
|
|
330
|
-
* placement, so each decision carries a `rationale` that answers "why is this
|
|
331
|
-
* here?" without re-running the panel. Consumed by build-decompose, which
|
|
332
|
-
* turns it into the coding tasks that author `settings-hub.config.ts` and
|
|
333
|
-
* `app-shell.config.ts`.
|
|
334
|
-
*
|
|
335
|
-
* Optional until an application reaches the bottom-up phase; app bootstraps
|
|
336
|
-
* should run `validatePlacementPlan` on the value before wiring it here.
|
|
337
|
-
*/
|
|
338
|
-
placementPlanSpecification?: TPlacementPlan;
|
|
339
314
|
/**
|
|
340
315
|
* Application **domain-plan** specification — the atomic module decomposition
|
|
341
316
|
* PLUS relationship drafts (`DomainPlanOutputSet`, `_core/domain-plan/`);
|
|
@@ -474,37 +449,6 @@ export interface SpecificationsCompanionExports<
|
|
|
474
449
|
* Omitting it is honest: unresolved document facts remain visible gaps.
|
|
475
450
|
*/
|
|
476
451
|
documentFactSpecification?: TDocumentFactSpecification;
|
|
477
|
-
/**
|
|
478
|
-
* Accepted application governed-document facts **only a human may establish** — a creator decision
|
|
479
|
-
* or a qualified review (`document-facts-authored`).
|
|
480
|
-
*
|
|
481
|
-
* The same shape as the slot above, and a separate family on purpose. `refinement.document-facts`
|
|
482
|
-
* rewrites the derived file whole, so a human decision sharing that file is destroyed on the next
|
|
483
|
-
* run with nothing to notice: there is no compare-and-swap here, deliberately
|
|
484
|
-
* (`.claude/rules/one-source-of-truth.md` Rule 0). Two families put the two writers out of each
|
|
485
|
-
* other's reach.
|
|
486
|
-
*
|
|
487
|
-
* No producer may write this family — it has no generation contract, and that absence is the design
|
|
488
|
-
* rather than an omission.
|
|
489
|
-
*
|
|
490
|
-
* A reader wanting "the application's facts" needs BOTH slots. `collectComplianceDocumentFactAvailability`
|
|
491
|
-
* is variadic for exactly that reason.
|
|
492
|
-
*/
|
|
493
|
-
authoredDocumentFactSpecification?: TAuthoredDocumentFactSpecification;
|
|
494
|
-
/**
|
|
495
|
-
* WHO else processes this application's personal data — legal identity, processing region and the
|
|
496
|
-
* processor's own subprocessors (issue #88).
|
|
497
|
-
*
|
|
498
|
-
* A configured provider already establishes THAT a third party is involved and what function it
|
|
499
|
-
* performs. None of that is what a privacy notice's recipient statement needs, and an
|
|
500
|
-
* international-transfer statement cannot be made at all without a region.
|
|
501
|
-
*
|
|
502
|
-
* Optional, and its holes are reported rather than blocking: the companion compares this register
|
|
503
|
-
* against the application's CONFIGURED providers and names each one that is undeclared, so a partial
|
|
504
|
-
* register is useful and an empty one still produces an actionable document. An absent entry means
|
|
505
|
-
* nobody has established that processor's identity — never that the provider is unused.
|
|
506
|
-
*/
|
|
507
|
-
processorRegister?: TProcessorRegister;
|
|
508
452
|
/**
|
|
509
453
|
* Accepted application-declared semantic causality between whole
|
|
510
454
|
* specification-family states. This is not the registry's physical
|
|
@@ -71,28 +71,6 @@ export type ResourceSpecificationConfig<
|
|
|
71
71
|
businessRole: string;
|
|
72
72
|
/** How the resource evolves over time (lifecycle semantics). */
|
|
73
73
|
lifecycleRole?: string;
|
|
74
|
-
/**
|
|
75
|
-
* Which part of the product this resource belongs to, WITHIN its owner.
|
|
76
|
-
*
|
|
77
|
-
* A second grouping axis under the one that already exists. An application's resources are grouped
|
|
78
|
-
* by the module that registers them; the engine's are grouped by nothing, so every surface that
|
|
79
|
-
* has to present them — the domain-model graph, `wildo context`, generated documentation, an
|
|
80
|
-
* application-creation playbook — meets one flat set of 85 and either shows it undifferentiated or
|
|
81
|
-
* invents a grouping of its own and drifts from the next surface that does the same.
|
|
82
|
-
*
|
|
83
|
-
* Typed `string` and OPEN on purpose. The engine's values are a closed vocabulary with a named
|
|
84
|
-
* runtime source, {@link EngineResourceSubDomain} in this package's `engine` surface, and engine
|
|
85
|
-
* specs must use it. An application's sub-domains are its own — this repository cannot enumerate
|
|
86
|
-
* a vocabulary it does not own, and a union that tried would refuse every real application.
|
|
87
|
-
*
|
|
88
|
-
* Optional, and its absence means exactly "unclassified" rather than "belongs to a default". A
|
|
89
|
-
* consumer grouping by it must carry a bucket for that and say so; silently folding unclassified
|
|
90
|
-
* rows into a real group is how a grouping starts lying.
|
|
91
|
-
*
|
|
92
|
-
* Distinct from {@link ResourceSpecificationConfig.resourcePrimaryScope}, which answers WHO a row
|
|
93
|
-
* belongs to. This answers what it is ABOUT, and one sub-domain spans several scopes.
|
|
94
|
-
*/
|
|
95
|
-
subDomain?: string;
|
|
96
74
|
/**
|
|
97
75
|
* Intended READER of this resource's generated labels — the register the label
|
|
98
76
|
* generator should adopt: {@link LabelAudience.END_USER} for consumer surfaces
|
|
@@ -231,32 +231,6 @@ function applySingleDecorator<T extends z.ZodTypeAny>(
|
|
|
231
231
|
currentMetadata[ZodDecorator.PORTABILITY_PROVENANCE] = raw;
|
|
232
232
|
break;
|
|
233
233
|
}
|
|
234
|
-
case ZodDecorator.DATA_CATEGORIES: {
|
|
235
|
-
// NORMALIZE HERE, not in the doors — the impersonalizeWith discipline. A single value (the
|
|
236
|
-
// common case) and an array both store a deduped ARRAY, so every reader sees one shape and
|
|
237
|
-
// `getDataCategories` answers "is this field categorized?" by presence alone.
|
|
238
|
-
//
|
|
239
|
-
// Fail LOUD on an empty declaration. An UNCATEGORIZED field is a legitimate, common state —
|
|
240
|
-
// most fields are not personal data — and the gap report is built on ABSENCE. A stored empty
|
|
241
|
-
// array would read back as declared-with-no-categories, which is invisible to a report
|
|
242
|
-
// looking for absence: the field would be silently excluded from the notice while looking
|
|
243
|
-
// annotated to anyone reading the schema.
|
|
244
|
-
//
|
|
245
|
-
// WHETHER each value is a real `PersonalDataCategory` member is checked by the resource
|
|
246
|
-
// factory's boot guard, which owns the enum — this layer knows only that non-empty strings
|
|
247
|
-
// were declared.
|
|
248
|
-
const raw = p as unknown;
|
|
249
|
-
const authored: readonly unknown[] = Array.isArray(raw) ? raw : [raw];
|
|
250
|
-
if (authored.length === 0 || authored.some((value) => typeof value !== 'string' || value.trim().length === 0)) {
|
|
251
|
-
throw new Error(
|
|
252
|
-
`dataCategories(categories) requires at least one non-empty PersonalDataCategory value (received ${JSON.stringify(raw)}). ` +
|
|
253
|
-
`A field that holds no personal data carries NO declaration — absence is what a category gap report reads. ` +
|
|
254
|
-
`An empty declaration looks annotated and discloses nothing.`,
|
|
255
|
-
);
|
|
256
|
-
}
|
|
257
|
-
currentMetadata[ZodDecorator.DATA_CATEGORIES] = [...new Set(authored as readonly string[])];
|
|
258
|
-
break;
|
|
259
|
-
}
|
|
260
234
|
case ZodDecorator.IS_AUDIT_EVIDENCE:
|
|
261
235
|
currentMetadata[ZodDecorator.IS_AUDIT_EVIDENCE] = true;
|
|
262
236
|
break;
|