@wildo-ai/framework-knowledge 1.1.2 → 1.1.3
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 +228 -6
- package/dist/esm/framework-knowledge.definitions.js.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/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,192 +0,0 @@
|
|
|
1
|
-
# File upload grant — the contract behind `…upload_grant.<field>` tools
|
|
2
|
-
|
|
3
|
-
Read this when an exposed CREATE or UPDATE carries a `z_file()` field and you need to know what an
|
|
4
|
-
agent receives from the derived upload-grant tool, what it does with it, and what bounds apply.
|
|
5
|
-
|
|
6
|
-
- Every exposed default CREATE / UPDATE whose request carries a user-uploadable file field ALSO
|
|
7
|
-
advertises `<resource>__<operation>.upload_grant.<fieldSegment>` (e.g.
|
|
8
|
-
`todos__create.upload_grant.attachments`). You author nothing for it — it is derived from the same
|
|
9
|
-
`mcp: { exposed: true }` opt-in and inherits the parent's gating.
|
|
10
|
-
- Calling it mints a single-use grant and returns the object below: `uploadCommand` for an agent that
|
|
11
|
-
can execute commands, `uploadPageUrl` for one that must hand a human a link (`null` on a headless
|
|
12
|
-
application). The token travels in the `uploadHeader`, never in the upload URL.
|
|
13
|
-
- The agent then reads the produced `fileId` (from the upload response, or from `statusUrl` when a
|
|
14
|
-
human uploaded) and passes it as the field's `fileId` / `fileIds` in the parent tool.
|
|
15
|
-
|
|
16
|
-
## Import Origins
|
|
17
|
-
|
|
18
|
-
- `@wildo-ai/saas-models`
|
|
19
|
-
|
|
20
|
-
## Source Excerpts
|
|
21
|
-
|
|
22
|
-
### Origin Package: `@wildo-ai/saas-models`
|
|
23
|
-
|
|
24
|
-
```typescript
|
|
25
|
-
*
|
|
26
|
-
* Lifetime bounds of an upload grant, in minutes. The ceiling is fixed by the framework and enforced
|
|
27
|
-
* when the grant is minted — a request above it is REFUSED, never clamped, so a caller that asked for
|
|
28
|
-
* two hours learns from an error that the bound is sixty minutes rather than from an expiry it did not
|
|
29
|
-
* expect. The bound is the framework's to own because the grant is designed to leave the trust
|
|
30
|
-
* boundary: it lands in an AI agent's transcript, a model provider's logs, a shell history.
|
|
31
|
-
*/
|
|
32
|
-
export const FILE_UPLOAD_GRANT_DEFAULT_MINUTES = 15;
|
|
33
|
-
export const FILE_UPLOAD_GRANT_ABSOLUTE_MAX_MINUTES = 60;
|
|
34
|
-
|
|
35
|
-
/**
|
|
36
|
-
* Which write the grant is for. A grant minted on the CREATE upload route uploads a file that a
|
|
37
|
-
* later CREATE will reference; one minted on the UPDATE route (`…/{resourceId}/files/<field>`) is
|
|
38
|
-
* bound to that row. The two routes authorize differently, so a grant may not cross from one to the
|
|
39
|
-
* other — the upload middleware checks this against the route it is presented on.
|
|
40
|
-
*/
|
|
41
|
-
export const FILE_UPLOAD_GRANT_OPERATIONS = [CoreResourceOperation.CREATE, CoreResourceOperation.UPDATE] as const;
|
|
42
|
-
export type FileUploadGrantOperation = (typeof FILE_UPLOAD_GRANT_OPERATIONS)[number];
|
|
43
|
-
/** Derived from `CoreResourceOperation` — the named source — rather than a second enum spelling the same two words. */
|
|
44
|
-
export const FileUploadGrantOperationSchema: z.ZodEnum<{ [K in FileUploadGrantOperation]: K }> = z.enum(FILE_UPLOAD_GRANT_OPERATIONS);
|
|
45
|
-
|
|
46
|
-
/**
|
|
47
|
-
* Lifecycle of a grant as the status read reports it. Derived from the token row — `isConsumed`,
|
|
48
|
-
* `expiresAt`, `revokedAt` — never stored, so it cannot drift from the row.
|
|
49
|
-
*/
|
|
50
|
-
export enum FileUploadGrantState {
|
|
51
|
-
/** Minted, unexpired, unrevoked, not yet redeemed: an upload will be accepted. */
|
|
52
|
-
PENDING = 'pending',
|
|
53
|
-
/** Redeemed by exactly one upload. `file` names what it produced when the write-back succeeded. */
|
|
54
|
-
REDEEMED = 'redeemed',
|
|
55
|
-
/** Past `expiresAt` without being redeemed. Mint a new one. */
|
|
56
|
-
EXPIRED = 'expired',
|
|
57
|
-
/** Revoked by the minter or an administrator before redemption. */
|
|
58
|
-
REVOKED = 'revoked',
|
|
59
|
-
}
|
|
60
|
-
export const FileUploadGrantStateSchema: z.ZodEnum<typeof FileUploadGrantState> = z.enum(FileUploadGrantState);
|
|
61
|
-
|
|
62
|
-
/**
|
|
63
|
-
* The `metadata` a FILE_UPLOAD_GRANT token carries — the ROUTE binding, as opposed to the identity
|
|
64
|
-
* the typed token fields carry. The upload middleware reads this; the execution-context creator
|
|
65
|
-
* deliberately does not.
|
|
66
|
-
*/
|
|
67
|
-
export const FileUploadGrantMetadataSchema: z.ZodObject<{
|
|
68
|
-
fieldName: z.ZodString;
|
|
69
|
-
operation: z.ZodEnum<{ [K in FileUploadGrantOperation]: K }>;
|
|
70
|
-
minter: z.ZodObject<{ entityType: z.ZodString; id: z.ZodString }>;
|
|
71
|
-
uploadUrl: z.ZodString;
|
|
72
|
-
producedFileId: z.ZodOptional<z.ZodString>;
|
|
73
|
-
}> = z.object({
|
|
74
|
-
/** The `z_file()` field the upload lands on, as authored (dotted for nested fields). */
|
|
75
|
-
fieldName: z.string().min(1),
|
|
76
|
-
operation: FileUploadGrantOperationSchema,
|
|
77
|
-
/**
|
|
78
|
-
* Who minted — recorded so the uploaded file is attributed to a PERSON or MACHINE, not to the
|
|
79
|
-
* grant. `entityType` is a `FileUploaderEntityType` value; kept as a string here because the
|
|
80
|
-
* uploader enum lives in `zod-decorators`, upstream of this package.
|
|
81
|
-
*/
|
|
82
|
-
minter: z.object({ entityType: z.string().min(1), id: z.string().min(1) }),
|
|
83
|
-
/** The concrete upload URL the grant was minted for — recorded so the status read can hand it to the drop page. */
|
|
84
|
-
uploadUrl: z.string().url(),
|
|
85
|
-
/** Written after a successful redemption; absent until then. */
|
|
86
|
-
producedFileId: z.string().min(1).optional(),
|
|
87
|
-
});
|
|
88
|
-
export type FileUploadGrantMetadata = z.infer<typeof FileUploadGrantMetadataSchema>;
|
|
89
|
-
|
|
90
|
-
/**
|
|
91
|
-
* What a mint returns — identical on the REST door and the MCP tool. Two affordances for one
|
|
92
|
-
* token: `uploadCommand` for a caller that can execute, `uploadPageUrl` for one that must hand a
|
|
93
|
-
* human a link. The token appears in `uploadHeader.value` and inside both commands and the page URL;
|
|
94
|
-
* it is the credential and cannot be omitted. It never appears in any audit row.
|
|
95
|
-
*/
|
|
96
|
-
export const FileUploadGrantSchema: z.ZodObject<{
|
|
97
|
-
grantId: z.ZodString;
|
|
98
|
-
state: z.ZodEnum<typeof FileUploadGrantState>;
|
|
99
|
-
expiresAt: z.ZodString;
|
|
100
|
-
singleUse: z.ZodLiteral<true>;
|
|
101
|
-
target: z.ZodObject<{
|
|
102
|
-
resourceType: z.ZodString;
|
|
103
|
-
fieldName: z.ZodString;
|
|
104
|
-
operation: z.ZodEnum<{ [K in FileUploadGrantOperation]: K }>;
|
|
105
|
-
resourceId: z.ZodNullable<z.ZodString>;
|
|
106
|
-
}>;
|
|
107
|
-
constraints: z.ZodObject<{
|
|
108
|
-
maxBytes: z.ZodNumber;
|
|
109
|
-
allowedMimeTypes: z.ZodArray<z.ZodString>;
|
|
110
|
-
}>;
|
|
111
|
-
uploadUrl: z.ZodString;
|
|
112
|
-
uploadHeader: z.ZodObject<{ name: z.ZodString; value: z.ZodString }>;
|
|
113
|
-
uploadCommand: z.ZodString;
|
|
114
|
-
uploadCommandPowerShell: z.ZodString;
|
|
115
|
-
uploadPageUrl: z.ZodNullable<z.ZodString>;
|
|
116
|
-
statusUrl: z.ZodString;
|
|
117
|
-
note: z.ZodString;
|
|
118
|
-
}> = z.object({
|
|
119
|
-
grantId: z.string().min(1),
|
|
120
|
-
state: FileUploadGrantStateSchema,
|
|
121
|
-
expiresAt: z.string().datetime(),
|
|
122
|
-
singleUse: z.literal(true),
|
|
123
|
-
target: z.object({
|
|
124
|
-
resourceType: z.string().min(1),
|
|
125
|
-
fieldName: z.string().min(1),
|
|
126
|
-
operation: FileUploadGrantOperationSchema,
|
|
127
|
-
resourceId: z.string().min(1).nullable(),
|
|
128
|
-
}),
|
|
129
|
-
/** From the field's own constraint resolver — the same one the upload enforces, so the two cannot disagree. */
|
|
130
|
-
constraints: z.object({
|
|
131
|
-
maxBytes: z.number().int().positive(),
|
|
132
|
-
/** Empty means every type is accepted. */
|
|
133
|
-
allowedMimeTypes: z.array(z.string()),
|
|
134
|
-
}),
|
|
135
|
-
uploadUrl: z.string().url(),
|
|
136
|
-
/** The credential travels in a HEADER on the curl form: paths are logged by every proxy, headers are not. */
|
|
137
|
-
uploadHeader: z.object({ name: z.string().min(1), value: z.string().min(1) }),
|
|
138
|
-
/** No `-f`: on a refusal the JSON error body is the only thing that tells the caller why. */
|
|
139
|
-
uploadCommand: z.string().min(1),
|
|
140
|
-
/** In PowerShell `curl` aliases Invoke-WebRequest, which does not understand `-F`; the real binary is `curl.exe`. */
|
|
141
|
-
uploadCommandPowerShell: z.string().min(1),
|
|
142
|
-
/** `null` when the application declares no frontend service — a headless API has no page to hand a human. */
|
|
143
|
-
uploadPageUrl: z.string().url().nullable(),
|
|
144
|
-
statusUrl: z.string().url(),
|
|
145
|
-
note: z.string().min(1),
|
|
146
|
-
});
|
|
147
|
-
export type FileUploadGrant = z.infer<typeof FileUploadGrantSchema>;
|
|
148
|
-
|
|
149
|
-
/**
|
|
150
|
-
* What the public status read returns. The token is the credential, so the read is unauthenticated
|
|
151
|
-
* and returns only what the drop page needs to render and the agent needs to learn the `fileId`:
|
|
152
|
-
* never the file's name (the status URL may be pasted around).
|
|
153
|
-
*/
|
|
154
|
-
export const FileUploadGrantStatusSchema: z.ZodObject<{
|
|
155
|
-
grantId: z.ZodString;
|
|
156
|
-
state: z.ZodEnum<typeof FileUploadGrantState>;
|
|
157
|
-
expiresAt: z.ZodString;
|
|
158
|
-
target: z.ZodObject<{
|
|
159
|
-
resourceType: z.ZodString;
|
|
160
|
-
fieldName: z.ZodString;
|
|
161
|
-
operation: z.ZodEnum<{ [K in FileUploadGrantOperation]: K }>;
|
|
162
|
-
resourceId: z.ZodNullable<z.ZodString>;
|
|
163
|
-
}>;
|
|
164
|
-
constraints: z.ZodObject<{ maxBytes: z.ZodNumber; allowedMimeTypes: z.ZodArray<z.ZodString> }>;
|
|
165
|
-
uploadUrl: z.ZodString;
|
|
166
|
-
uploadHeaderName: z.ZodString;
|
|
167
|
-
file: z.ZodNullable<z.ZodObject<{ fileId: z.ZodString; status: z.ZodEnum<typeof FileStatus> }>>;
|
|
168
|
-
}> = z.object({
|
|
169
|
-
grantId: z.string().min(1),
|
|
170
|
-
state: FileUploadGrantStateSchema,
|
|
171
|
-
expiresAt: z.string().datetime(),
|
|
172
|
-
target: z.object({
|
|
173
|
-
resourceType: z.string().min(1),
|
|
174
|
-
fieldName: z.string().min(1),
|
|
175
|
-
operation: FileUploadGrantOperationSchema,
|
|
176
|
-
resourceId: z.string().min(1).nullable(),
|
|
177
|
-
}),
|
|
178
|
-
constraints: z.object({ maxBytes: z.number().int().positive(), allowedMimeTypes: z.array(z.string()) }),
|
|
179
|
-
uploadUrl: z.string().url(),
|
|
180
|
-
/** The page sets this header itself; the token it already holds is the value. */
|
|
181
|
-
uploadHeaderName: z.string().min(1),
|
|
182
|
-
/** `null` until redeemed, or when the post-redemption write-back failed (re-read the resource instead). */
|
|
183
|
-
file: z.object({ fileId: z.string().min(1), status: z.enum(FileStatus) }).nullable(),
|
|
184
|
-
});
|
|
185
|
-
export type FileUploadGrantStatus = z.infer<typeof FileUploadGrantStatusSchema>;
|
|
186
|
-
|
|
187
|
-
/** Body accepted by both mint doors. */
|
|
188
|
-
export const FileUploadGrantMintRequestSchema: z.ZodObject<{ expiresInMinutes: z.ZodOptional<z.ZodNumber> }> = z.object({
|
|
189
|
-
expiresInMinutes: z.number().int().min(1).max(FILE_UPLOAD_GRANT_ABSOLUTE_MAX_MINUTES).optional(),
|
|
190
|
-
}).strict();
|
|
191
|
-
export type FileUploadGrantMintRequest = z.infer<typeof FileUploadGrantMintRequestSchema>;
|
|
192
|
-
```
|
|
@@ -1,245 +0,0 @@
|
|
|
1
|
-
# Framework Personal-Data Category API
|
|
2
|
-
|
|
3
|
-
This file exposes the **per-field personal-data category declaration** — `.dataCategories(...)` —
|
|
4
|
-
and the `PersonalDataCategory` vocabulary behind it.
|
|
5
|
-
|
|
6
|
-
Read it when a field holds data about a PERSON and you need to say what kind. That is the question a
|
|
7
|
-
privacy notice answers first, and the only way the application can answer it is by declaring it here:
|
|
8
|
-
nothing in the framework infers a category from a field's name.
|
|
9
|
-
|
|
10
|
-
Use it when you need the real source contracts for:
|
|
11
|
-
|
|
12
|
-
- the closed `PersonalDataCategory` vocabulary — including which members are GDPR Art. 9 special
|
|
13
|
-
category data and why Art. 10 criminal-offence data sits outside that set
|
|
14
|
-
- the fluent `.dataCategories(...)` signature (single value or array)
|
|
15
|
-
- the `addDataCategories(schema, ...)` escape hatch, for a schema with no fluent surface —
|
|
16
|
-
`z_phone()` returns one, and a phone number is contact-detail personal data by definition
|
|
17
|
-
- the `getDataCategories(schema)` reader
|
|
18
|
-
|
|
19
|
-
## When to declare one
|
|
20
|
-
|
|
21
|
-
Declare a category on a field that holds personal data. Leave every other field undeclared — absence
|
|
22
|
-
is the normal state and is what the compliance gap report reads.
|
|
23
|
-
|
|
24
|
-
Two shortcuts to avoid:
|
|
25
|
-
|
|
26
|
-
- **Do not declare from the field's NAME.** `email`, `phone` and `dateOfBirth` are suggestive while
|
|
27
|
-
`notes` is not, so a category list assembled that way is a guess whose misses are silently
|
|
28
|
-
undisclosed. `credentials` is the one category the framework derives, and it derives it from the
|
|
29
|
-
`.isPassword()` / `.isOtp()` / `.isWriteOnlySecret()` markers you already wrote.
|
|
30
|
-
- **Do not reach for `Compliance_DataClassification`.** It is a four-level SENSITIVITY ladder
|
|
31
|
-
(public / internal / confidential / restricted) for flows-actors configuration, and it answers
|
|
32
|
-
"how protected must this be" rather than "what kind of personal data is this".
|
|
33
|
-
|
|
34
|
-
## Adjacent axes it is NOT
|
|
35
|
-
|
|
36
|
-
A single field is routinely all four at once, and each has its own declaration:
|
|
37
|
-
|
|
38
|
-
| Question | Declaration |
|
|
39
|
-
|---|---|
|
|
40
|
-
| What KIND of personal data is this? | `.dataCategories(...)` |
|
|
41
|
-
| What happens to it on ERASURE? | `.impersonalizeWith(...)` |
|
|
42
|
-
| Where did it COME FROM (Art. 20 scope)? | `.portabilityProvenance(...)` |
|
|
43
|
-
| How long is it kept? | the application's `dataRetention` schedule, by retention class |
|
|
44
|
-
|
|
45
|
-
If you declare `.impersonalizeWith()` on a field, declare a category too — the framework reports a
|
|
46
|
-
field that is personal by one declaration and uncategorized by another as an OUTSTANDING gap, by
|
|
47
|
-
name, in every compliance document it produces.
|
|
48
|
-
|
|
49
|
-
## Personal-Data Category
|
|
50
|
-
|
|
51
|
-
## Import Origins
|
|
52
|
-
|
|
53
|
-
- `@wildo-ai/saas-models`
|
|
54
|
-
- `@wildo-ai/zod-decorators`
|
|
55
|
-
|
|
56
|
-
## Source Excerpts
|
|
57
|
-
|
|
58
|
-
### Origin Package: `@wildo-ai/saas-models`
|
|
59
|
-
|
|
60
|
-
```typescript
|
|
61
|
-
*/
|
|
62
|
-
export enum PersonalDataCategory {
|
|
63
|
-
/** Who the person is: name, username, display name, account identifier, avatar. */
|
|
64
|
-
IDENTITY = 'identity',
|
|
65
|
-
/** How the person is reached: email address, telephone number, postal address. */
|
|
66
|
-
CONTACT_DETAILS = 'contact-details',
|
|
67
|
-
/**
|
|
68
|
-
* What proves the person is who they claim: passwords, MFA secrets, API keys, session tokens.
|
|
69
|
-
*
|
|
70
|
-
* Rarely authored by hand — the fact producer DERIVES this category from `.isPassword()`,
|
|
71
|
-
* `.isOtp()` and `.isWriteOnlySecret()`, which are declarations the application already makes.
|
|
72
|
-
* Declare it explicitly only for a credential those markers do not cover.
|
|
73
|
-
*/
|
|
74
|
-
CREDENTIALS = 'credentials',
|
|
75
|
-
/** Money: payment-method references, invoices, billing details, transaction history. */
|
|
76
|
-
FINANCIAL = 'financial',
|
|
77
|
-
/** What the person did in the product: activity records, timestamps, device and telemetry data. */
|
|
78
|
-
USAGE = 'usage',
|
|
79
|
-
/** Where the person is or was: coordinates, derived region, IP-inferred location. */
|
|
80
|
-
LOCATION = 'location',
|
|
81
|
-
/**
|
|
82
|
-
* What the person wrote or uploaded: free text, notes, attachments.
|
|
83
|
-
*
|
|
84
|
-
* ⚠️ Free text is the category that can silently contain any other one — a "notes" field may hold
|
|
85
|
-
* health information nobody declared. Declaring `USER_CONTENT` states what the field is FOR; it
|
|
86
|
-
* does not certify what it will contain, and no schema can. Where a free-text field is
|
|
87
|
-
* FORESEEABLY used for a special category, declare that member alongside.
|
|
88
|
-
*/
|
|
89
|
-
USER_CONTENT = 'user-content',
|
|
90
|
-
/** The person's working life: employer, job title, professional relationship to the operator. */
|
|
91
|
-
PROFESSIONAL = 'professional',
|
|
92
|
-
|
|
93
|
-
// ── GDPR Art. 9(1), verbatim and closed. Processing needs an Art. 9(2) condition of its own,
|
|
94
|
-
// over and above the Art. 6 lawful basis every other member already needs.
|
|
95
|
-
/** Art. 9(1): racial or ethnic origin. */
|
|
96
|
-
SPECIAL_CATEGORY_RACIAL_OR_ETHNIC_ORIGIN = 'special-category:racial-or-ethnic-origin',
|
|
97
|
-
/** Art. 9(1): political opinions. */
|
|
98
|
-
SPECIAL_CATEGORY_POLITICAL_OPINIONS = 'special-category:political-opinions',
|
|
99
|
-
/** Art. 9(1): religious or philosophical beliefs. */
|
|
100
|
-
SPECIAL_CATEGORY_RELIGIOUS_OR_PHILOSOPHICAL_BELIEFS = 'special-category:religious-or-philosophical-beliefs',
|
|
101
|
-
/** Art. 9(1): trade union membership. */
|
|
102
|
-
SPECIAL_CATEGORY_TRADE_UNION_MEMBERSHIP = 'special-category:trade-union-membership',
|
|
103
|
-
/** Art. 9(1): genetic data. */
|
|
104
|
-
SPECIAL_CATEGORY_GENETIC = 'special-category:genetic',
|
|
105
|
-
/**
|
|
106
|
-
* Art. 9(1): biometric data processed FOR THE PURPOSE OF uniquely identifying a natural person.
|
|
107
|
-
*
|
|
108
|
-
* The purpose qualifier is part of the law's definition, not a footnote: a photograph is ordinary
|
|
109
|
-
* `IDENTITY` data until it is put through facial recognition, at which point it becomes this.
|
|
110
|
-
*/
|
|
111
|
-
SPECIAL_CATEGORY_BIOMETRIC = 'special-category:biometric',
|
|
112
|
-
/** Art. 9(1): data concerning health. */
|
|
113
|
-
SPECIAL_CATEGORY_HEALTH = 'special-category:health',
|
|
114
|
-
/** Art. 9(1): data concerning a natural person's sex life or sexual orientation. */
|
|
115
|
-
SPECIAL_CATEGORY_SEX_LIFE_OR_SEXUAL_ORIENTATION = 'special-category:sex-life-or-sexual-orientation',
|
|
116
|
-
|
|
117
|
-
/**
|
|
118
|
-
* GDPR Art. 10: criminal convictions and offences.
|
|
119
|
-
*
|
|
120
|
-
* Deliberately NOT a member of {@link SPECIAL_CATEGORY_PERSONAL_DATA_CATEGORIES}. Art. 10 is a
|
|
121
|
-
* separate article with a different condition — processing requires official authority or a
|
|
122
|
-
* Member State law — so folding it into the Art. 9 set would attach the wrong legal test to it.
|
|
123
|
-
*/
|
|
124
|
-
CRIMINAL_OFFENCE = 'criminal-offence',
|
|
125
|
-
}
|
|
126
|
-
|
|
127
|
-
/**
|
|
128
|
-
* What the ENGINE deliberately does NOT declare, so its silence reads as a decision.
|
|
129
|
-
*
|
|
130
|
-
* Measured 2026-08-30: 48 of the 85 engine resource configurations declare at least one category. The rest are silent on
|
|
131
|
-
* purpose, in four groups:
|
|
132
|
-
*
|
|
133
|
-
* - **System machinery is not personal data, even when the row carries a `userId`.** A queue
|
|
134
|
-
* execution, an entitlement limit, an unread counter, a token-budget counter — each exists so the
|
|
135
|
-
* platform can do its work, and the person's identifier on it is the LINK, not the datum. This
|
|
136
|
-
* group is the one that is easiest to get wrong, because such rows legitimately appear in a
|
|
137
|
-
* subject export: `systemAccessPolicy.exportSubject` means *rows here relate to a subject and
|
|
138
|
-
* belong in their bundle*, which is true by linkage alone. It does not mean the row holds a datum
|
|
139
|
-
* about them, and reading it that way once put `jobExecutions` in this inventory.
|
|
140
|
-
*
|
|
141
|
-
* - **A legal person is not a data subject.** `organizations`, `organizationUnits`,
|
|
142
|
-
* `organizationProfiles`, `organizationPreferences` and their siblings describe a COMPANY. GDPR
|
|
143
|
-
* Recital 14 excludes the processing of data concerning legal persons, so declaring
|
|
144
|
-
* `CONTACT_DETAILS` on an organization's switchboard number would make every notice claim the
|
|
145
|
-
* operator holds an individual's contact details that it does not. A small company's number is
|
|
146
|
-
* often a person's — that is a fact about the customer's data, not about this field's meaning.
|
|
147
|
-
* - **Configuration is not data about anyone.** SSO/SCIM/webhook configuration, API keys and OAuth
|
|
148
|
-
* clients owned by an organization, products, prices, promotions, ETL cursors. An organization's
|
|
149
|
-
* API key is a bearer secret whose subject is the organization; the person who minted it is not
|
|
150
|
-
* recorded on the row.
|
|
151
|
-
* - **A foreign key is LINKAGE, not a category.** `userId` on a usage row is what makes that usage
|
|
152
|
-
* personal; the category of the row's CONTENT is what a notice enumerates. Declaring `IDENTITY`
|
|
153
|
-
* on every owner FK would put "identity data" against resources holding no name, and tell a
|
|
154
|
-
* reader nothing the linkage does not already imply. The machinery group above is this same rule
|
|
155
|
-
* applied one level up, at the row rather than the field.
|
|
156
|
-
*
|
|
157
|
-
* The line between the first group and a real answer is not always obvious, and one pair is worth
|
|
158
|
-
* keeping side by side: a metered USAGE RECORD is declared while a TOKEN-BUDGET counter is not.
|
|
159
|
-
* Both count something a person consumed. The usage record is a per-event history with a timestamp —
|
|
160
|
-
* a record of what they did, which an Art. 15 copy must contain. The budget counter is a single
|
|
161
|
-
* mutable number that exists so a limiter can refuse the next call; nothing about the person
|
|
162
|
-
* survives in it. Ask what the row is FOR, not what it counts.
|
|
163
|
-
*
|
|
164
|
-
* Recorded here because absence is invisible. A future reader finding `organizationProfiles`
|
|
165
|
-
* undeclared should be able to see that it was considered, not assume it was missed — the same
|
|
166
|
-
* discipline a justified `N/A` serves in a verification matrix.
|
|
167
|
-
*/
|
|
168
|
-
|
|
169
|
-
/** Zod form of {@link PersonalDataCategory}. */
|
|
170
|
-
export const PersonalDataCategorySchema: z.ZodEnum<typeof PersonalDataCategory> = z.enum(PersonalDataCategory);
|
|
171
|
-
|
|
172
|
-
/**
|
|
173
|
-
* The GDPR Art. 9(1) members, as a set — the one place the Art. 9 line is drawn.
|
|
174
|
-
*
|
|
175
|
-
* Derived by PREFIX rather than hand-listed: every Art. 9 member's wire value begins
|
|
176
|
-
* `special-category:`, so a member added to the enum joins this set automatically. A hand-written
|
|
177
|
-
* list would be a second enumeration of a closed vocabulary, and the failure mode is silent — a new
|
|
178
|
-
* Art. 9 member omitted from it reads as ordinary personal data.
|
|
179
|
-
*/
|
|
180
|
-
export const SPECIAL_CATEGORY_PERSONAL_DATA_CATEGORIES: ReadonlySet<PersonalDataCategory> = new Set(
|
|
181
|
-
Object.values(PersonalDataCategory).filter((category) => category.startsWith('special-category:')),
|
|
182
|
-
);
|
|
183
|
-
|
|
184
|
-
/**
|
|
185
|
-
* Does this category carry the GDPR Art. 9 condition?
|
|
186
|
-
*
|
|
187
|
-
* `false` for {@link PersonalDataCategory.CRIMINAL_OFFENCE} — see that member's note. Callers that
|
|
188
|
-
* need "needs a condition beyond Art. 6" must test both.
|
|
189
|
-
*/
|
|
190
|
-
export function isSpecialCategoryPersonalData(category: PersonalDataCategory): boolean {
|
|
191
|
-
return SPECIAL_CATEGORY_PERSONAL_DATA_CATEGORIES.has(category);
|
|
192
|
-
}
|
|
193
|
-
```
|
|
194
|
-
|
|
195
|
-
### Origin Package: `@wildo-ai/zod-decorators`
|
|
196
|
-
|
|
197
|
-
```typescript
|
|
198
|
-
*/
|
|
199
|
-
export function getDataCategories(schema: z.ZodTypeAny): readonly string[] | undefined {
|
|
200
|
-
const metadata = getMetadataRecursive(schema);
|
|
201
|
-
const value = metadata?.[ZodDecorator.DATA_CATEGORIES];
|
|
202
|
-
return Array.isArray(value) && value.length > 0 ? (value as readonly string[]) : undefined;
|
|
203
|
-
}
|
|
204
|
-
```
|
|
205
|
-
|
|
206
|
-
### Origin Package: `@wildo-ai/zod-decorators`
|
|
207
|
-
|
|
208
|
-
```typescript
|
|
209
|
-
*
|
|
210
|
-
* Declare WHICH KINDS of personal data this field holds — the vocabulary a privacy notice
|
|
211
|
-
* enumerates. Import `PersonalDataCategory` from `@wildo-ai/saas-models`.
|
|
212
|
-
*
|
|
213
|
-
* Accepts a single category (the common case) or an array when a field genuinely spans two. At
|
|
214
|
-
* least one is required: a field that holds NO personal data carries no declaration at all, and
|
|
215
|
-
* that absence is exactly what the compliance gap report reads.
|
|
216
|
-
*
|
|
217
|
-
* Declare it on the field that holds the value. Never on a field merely because its NAME suggests
|
|
218
|
-
* a category — `credentials` is the one category the framework derives for you, and it derives it
|
|
219
|
-
* from `.isPassword()` / `.isOtp()` / `.isWriteOnlySecret()`, never from an identifier.
|
|
220
|
-
*
|
|
221
|
-
* @example
|
|
222
|
-
* fullName: z.string().dataCategories(PersonalDataCategory.IDENTITY)
|
|
223
|
-
* @example
|
|
224
|
-
* email: z.email().nullish().dataCategories(PersonalDataCategory.CONTACT_DETAILS)
|
|
225
|
-
* @example
|
|
226
|
-
* // A field that genuinely spans two — an array never forces you to pick a lie.
|
|
227
|
-
* dietaryNotes: z.string().dataCategories([PersonalDataCategory.USER_CONTENT, PersonalDataCategory.SPECIAL_CATEGORY_HEALTH])
|
|
228
|
-
*/
|
|
229
|
-
[ZodDecorator.DATA_CATEGORIES](categories: string | readonly string[]): DecoratedPrimitiveZodType<T>;
|
|
230
|
-
```
|
|
231
|
-
|
|
232
|
-
### Origin Package: `@wildo-ai/zod-decorators`
|
|
233
|
-
|
|
234
|
-
```typescript
|
|
235
|
-
*/
|
|
236
|
-
export function addDataCategories<T extends z.ZodTypeAny>(
|
|
237
|
-
schema: T,
|
|
238
|
-
categories: string | readonly string[],
|
|
239
|
-
): T {
|
|
240
|
-
ensureZodDecoratorsLoaded(z);
|
|
241
|
-
return addDecorators(schema, [
|
|
242
|
-
{ ref: ZodDecorator.DATA_CATEGORIES, params: categories },
|
|
243
|
-
]);
|
|
244
|
-
}
|
|
245
|
-
```
|
|
@@ -1,134 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: settings-placement-authoring
|
|
3
|
-
description: Author your application's Settings rail — which sections appear, in which category, in what order, under what name. Use when you want to "add a settings section", "remove billing from settings", "reorder the settings tabs", "rename a settings section", "put SSO under a different group", "my settings section is not showing", or "the settings menu opens the wrong page".
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# Settings placement
|
|
7
|
-
|
|
8
|
-
### Target Application Framing
|
|
9
|
-
|
|
10
|
-
This knowledge is for configuring behavior in the target application.
|
|
11
|
-
Wildo is the framework surface being used, not the product being built.
|
|
12
|
-
|
|
13
|
-
Read and apply these patterns from the application-developer point of view:
|
|
14
|
-
|
|
15
|
-
- how the application should configure the relevant app-level file
|
|
16
|
-
- how the application should use framework-provided factories, enums, and helpers
|
|
17
|
-
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
## Overview
|
|
21
|
-
|
|
22
|
-
Your application's Settings surface is a rail of sections grouped into
|
|
23
|
-
categories. The framework ships the SECTIONS themselves — what each one renders,
|
|
24
|
-
and who is allowed to see it — but ships no arrangement at all. Which sections
|
|
25
|
-
exist in YOUR settings, how they are grouped, ordered and named, is a file you
|
|
26
|
-
own.
|
|
27
|
-
|
|
28
|
-
The boundary this keeps: the framework owns what a settings destination MEANS,
|
|
29
|
-
you own where it sits. Nothing is placed implicitly, so a section you do not
|
|
30
|
-
place does not appear — deleting a placement is how you remove a section.
|
|
31
|
-
|
|
32
|
-
## App Paths
|
|
33
|
-
|
|
34
|
-
| Surface | Path |
|
|
35
|
-
|---|---|
|
|
36
|
-
| Your settings rail | `./frontend/src/config/settings-hub.config.ts` |
|
|
37
|
-
| Wired into the app config | `./frontend/src/modules-registry.frontend.ts` (`settingsHub:`) |
|
|
38
|
-
| Exposed to the companion for label generation | `./frontend/src/companion-exports.ts` |
|
|
39
|
-
|
|
40
|
-
## When to Use
|
|
41
|
-
|
|
42
|
-
- Adding, removing, reordering or renaming a settings section.
|
|
43
|
-
- Adding a settings category, or moving a section between categories.
|
|
44
|
-
- A settings section is missing, or a menu entry opens the wrong panel.
|
|
45
|
-
|
|
46
|
-
## When NOT to Use
|
|
47
|
-
|
|
48
|
-
- Changing the SIDEBAR — a different vocabulary, and deliberately separate. Use
|
|
49
|
-
`config-app-shell`.
|
|
50
|
-
- Changing what a section RENDERS, or who may see it. That is the destination's
|
|
51
|
-
own contract, which the framework owns.
|
|
52
|
-
- Adding a settings entry to the user dropdown — same file family, but see
|
|
53
|
-
`config-app-shell` for `settingsEntries`.
|
|
54
|
-
|
|
55
|
-
## Workflow
|
|
56
|
-
|
|
57
|
-
### Step 1 — decide what the rail should contain
|
|
58
|
-
|
|
59
|
-
Read `references/framework-settings-destinations-catalog.md` for the complete
|
|
60
|
-
list of destinations you can place. Place only what your product needs; a new
|
|
61
|
-
application is scaffolded with all of them so you can edit DOWN, which is the
|
|
62
|
-
direction that shows you what exists.
|
|
63
|
-
|
|
64
|
-
### Step 2 — author the placements
|
|
65
|
-
|
|
66
|
-
Open `./frontend/src/config/settings-hub.config.ts`. Each placement names a
|
|
67
|
-
destination and says where it goes:
|
|
68
|
-
|
|
69
|
-
- `destinationRef` — from the catalog in Step 1.
|
|
70
|
-
- `categoryRef` — one of your own `categories`.
|
|
71
|
-
- `order` — lower is higher within its category.
|
|
72
|
-
- `label` — optional override; omit it once label generation runs.
|
|
73
|
-
|
|
74
|
-
Read `references/framework-settings-placement-api.md` for the exact contract.
|
|
75
|
-
|
|
76
|
-
### Step 3 — verify at startup
|
|
77
|
-
|
|
78
|
-
Start the app in development. The startup verifier refuses a placement naming a
|
|
79
|
-
destination that does not exist, and refuses a launcher (command menu, sidebar,
|
|
80
|
-
user dropdown) that opens a section you did not place. Read the console before
|
|
81
|
-
concluding the rail is correct.
|
|
82
|
-
|
|
83
|
-
### Step 4 — regenerate labels
|
|
84
|
-
|
|
85
|
-
Section and category names are generated into the `settings_hub.*` namespace
|
|
86
|
-
from your placements. Re-run label generation after adding or removing a
|
|
87
|
-
placement.
|
|
88
|
-
Run `wildo generate labels`.
|
|
89
|
-
|
|
90
|
-
## References
|
|
91
|
-
|
|
92
|
-
- `references/framework-settings-placement-api.md` — the destination / placement / registry contract.
|
|
93
|
-
- `references/framework-settings-destinations-catalog.md` — every destination you can place.
|
|
94
|
-
|
|
95
|
-
## Verification
|
|
96
|
-
|
|
97
|
-
- [ ] Every `destinationRef` exists in the engine catalog.
|
|
98
|
-
- [ ] Every `categoryRef` used by a placement is declared in `categories`.
|
|
99
|
-
- [ ] `defaultSectionRef`, if set, names a destination you placed.
|
|
100
|
-
- [ ] No two placements name the same destination.
|
|
101
|
-
- [ ] The app starts with no settings-hub or launcher verification errors.
|
|
102
|
-
|
|
103
|
-
### Grep invariants
|
|
104
|
-
|
|
105
|
-
```bash
|
|
106
|
-
# Every categoryRef a placement uses must be a declared category.
|
|
107
|
-
rg -o "categoryRef: '([a-z-]+)'" -r '$1' frontend/src/config/settings-hub.config.ts | sort -u
|
|
108
|
-
rg -o "^\s*\{ ref: '([a-z-]+)'" -r '$1' frontend/src/config/settings-hub.config.ts | sort -u
|
|
109
|
-
|
|
110
|
-
# No duplicate placements.
|
|
111
|
-
rg -o "destinationRef: '([a-z-]+)'" -r '$1' frontend/src/config/settings-hub.config.ts | sort | uniq -d
|
|
112
|
-
```
|
|
113
|
-
|
|
114
|
-
## Common Rationalizations
|
|
115
|
-
|
|
116
|
-
| Rationalization | Reality |
|
|
117
|
-
|---|---|
|
|
118
|
-
| "I removed the section but it still shows" | You removed the LABEL, not the placement. Delete the placement entry. |
|
|
119
|
-
| "The framework will fill in the sections I did not place" | It will not. There is no default arrangement — absence is how you remove a section, so nothing re-adds one. |
|
|
120
|
-
| "I can rename a section by changing its `destinationRef`" | `destinationRef` is the engine's id and the URL segment. Rename with `label`. |
|
|
121
|
-
| "The section is missing, so the destination must not exist" | Far more likely you placed it under a `categoryRef` you never declared. The startup verifier says which. |
|
|
122
|
-
| "I'll point the command menu at a section I have not placed yet" | The hub silently opens its DEFAULT section for an unknown ref, so this fails as a wrong page rather than an error. The startup verifier refuses it. |
|
|
123
|
-
|
|
124
|
-
## Red Flags
|
|
125
|
-
|
|
126
|
-
- A `categoryRef` that appears in no `categories` entry — catch with the categoryRef grep above.
|
|
127
|
-
- The same `destinationRef` placed twice — catch with the duplicate grep above.
|
|
128
|
-
- A `defaultSectionRef` naming a destination you did not place — the startup verifier warns.
|
|
129
|
-
- Editing a settings section's TARGET or `requiredRoles` in your app config — those live on the engine destination, not on your placement; if you are reaching for them, you want a different skill.
|
|
130
|
-
|
|
131
|
-
## Related Skills
|
|
132
|
-
|
|
133
|
-
- `config-app-shell` — the sidebar, command menu, user dropdown, and the dropdown's `settingsEntries`.
|
|
134
|
-
- `i18n-rerun-pipeline` — regenerating the `settings_hub.*` labels after a placement change.
|
|
@@ -1,65 +0,0 @@
|
|
|
1
|
-
# The engine's settings destinations
|
|
2
|
-
|
|
3
|
-
The complete list of refs your application can place. Read it when deciding what
|
|
4
|
-
your settings rail should contain, or when a placement is refused at startup for
|
|
5
|
-
naming a destination that does not exist.
|
|
6
|
-
|
|
7
|
-
Your application places these by STRING (a placement is authored data). The enum
|
|
8
|
-
is how engine code addresses them; you do not import it.
|
|
9
|
-
|
|
10
|
-
## Import Origins
|
|
11
|
-
|
|
12
|
-
- `@wildo-ai/saas-frontend-lib`
|
|
13
|
-
|
|
14
|
-
## Source Excerpts
|
|
15
|
-
|
|
16
|
-
### Origin Package: `@wildo-ai/saas-frontend-lib`
|
|
17
|
-
|
|
18
|
-
```typescript
|
|
19
|
-
/**
|
|
20
|
-
* Every settings destination the engine ships, as a named vocabulary.
|
|
21
|
-
*
|
|
22
|
-
* Exists because these refs are a CLOSED vocabulary that engine code addresses
|
|
23
|
-
* by name — the billing command-menu entry opens `/settings/billing`, and any
|
|
24
|
-
* future engine launcher will do the same. Before this enum, `'billing'` was a
|
|
25
|
-
* bare literal in `billing-launcher.ts` with nothing tying it to the catalog
|
|
26
|
-
* entry it names: rename the destination and the command silently resolves to
|
|
27
|
-
* the hub's DEFAULT section instead of failing, so a menu item labelled
|
|
28
|
-
* "Billing" would open Profile.
|
|
29
|
-
*
|
|
30
|
-
* **Engine code must address a destination through this enum. Application
|
|
31
|
-
* config addresses one by string**, deliberately: a placement is authored data,
|
|
32
|
-
* an application should not import an engine enum to write its own rail, and a
|
|
33
|
-
* typo there is caught at DEV startup by `verifySettingsHubContent`.
|
|
34
|
-
*/
|
|
35
|
-
export enum EngineSettingsDestinationRef {
|
|
36
|
-
/** The signed-in user's own profile record. */
|
|
37
|
-
PROFILE = 'profile',
|
|
38
|
-
/** Password, MFA, sessions — a bespoke engine panel. */
|
|
39
|
-
SECURITY = 'security',
|
|
40
|
-
/** Theme and appearance preferences — a bespoke engine panel. */
|
|
41
|
-
APPEARANCE = 'appearance',
|
|
42
|
-
/** The signed-in user's own preference record. */
|
|
43
|
-
PREFERENCES = 'preferences',
|
|
44
|
-
/** Invitations addressed TO the signed-in user, across organizations they have not joined. */
|
|
45
|
-
MY_INVITATIONS = 'my-invitations',
|
|
46
|
-
/** The current organization's own record. Org owner/admin only. */
|
|
47
|
-
ORGANIZATION_GENERAL = 'organization-general',
|
|
48
|
-
/** Organization membership list, including INVITED rows. Org owner/admin only. */
|
|
49
|
-
MEMBERS = 'members',
|
|
50
|
-
/** Billing home — subscription, plans, usage, invoices. Gated on the `billingEnabled` capability. */
|
|
51
|
-
BILLING = 'billing',
|
|
52
|
-
/** Organization API keys. Org owner/admin only. */
|
|
53
|
-
API_KEYS = 'api-keys',
|
|
54
|
-
/** Single sign-on configuration and connections. */
|
|
55
|
-
SSO = 'sso',
|
|
56
|
-
/** SCIM directory provisioning configuration and tokens. */
|
|
57
|
-
SCIM = 'scim',
|
|
58
|
-
/** Audit-event streaming configuration and failed-delivery queue. */
|
|
59
|
-
SIEM = 'siem',
|
|
60
|
-
/** Outbound webhook endpoints and delivery log. */
|
|
61
|
-
WEBHOOKS = 'webhooks',
|
|
62
|
-
/** The organization's audit log. Org owner/admin only. */
|
|
63
|
-
AUDIT_LOGS = 'audit-logs',
|
|
64
|
-
}
|
|
65
|
-
```
|