@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
package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md
CHANGED
|
@@ -41,21 +41,6 @@ export interface ForeignKeyStructuralParams {
|
|
|
41
41
|
* (e.g. `referrerScopeType`). Without it, `polymorphicVariants` is rename-only.
|
|
42
42
|
*/
|
|
43
43
|
polymorphicDiscriminatorField?: string;
|
|
44
|
-
/**
|
|
45
|
-
* EXPLICIT target resource type, for an FK whose FIELD NAME cannot resolve it.
|
|
46
|
-
*
|
|
47
|
-
* The frontend resolves a reference field's target through the field-name → resource map
|
|
48
|
-
* (enriched from relationships' `foreignKeyField`). That works only when the field is named for
|
|
49
|
-
* its target (`assignedToUserId`) or a relationship declares it — and relationship FK names are
|
|
50
|
-
* held to the `Id`/`Ids` convention. A field that references a resource under its OWN vocabulary
|
|
51
|
-
* (`icpRefs` inside a specification document, a rename-only FK) has no honest entry in that map;
|
|
52
|
-
* declaring the target here lets the reference display resolve, label and navigate it without
|
|
53
|
-
* bending the field's name or the map's uniqueness.
|
|
54
|
-
*
|
|
55
|
-
* Takes precedence over the field-name map; polymorphic variants (above) still win over both,
|
|
56
|
-
* because a per-record discriminator is more specific than any static declaration.
|
|
57
|
-
*/
|
|
58
|
-
referencedResourceType?: string;
|
|
59
44
|
}
|
|
60
45
|
```
|
|
61
46
|
|
|
@@ -472,106 +457,6 @@ export enum ActionPlacement {
|
|
|
472
457
|
DANGER_ZONE = 'danger_zone',
|
|
473
458
|
}
|
|
474
459
|
|
|
475
|
-
/**
|
|
476
|
-
* HOW an operation's action collects its input and shows its result — the chrome the user meets
|
|
477
|
-
* when they click the button.
|
|
478
|
-
*
|
|
479
|
-
* ## Why this axis exists
|
|
480
|
-
*
|
|
481
|
-
* Until this axis, one rule decided the answer for every custom operation:
|
|
482
|
-
* *has a `requestDto` ⇒ navigate*. So an action asking for a single reason string got the same
|
|
483
|
-
* full-page treatment as a multi-step wizard, and the only way out was to author
|
|
484
|
-
* `navigationOverrides` — per operation, in terms of a zone, a transition verb and an appearance.
|
|
485
|
-
* Three concepts to answer one question.
|
|
486
|
-
*
|
|
487
|
-
* This is that one question. It is a **display-only** axis: backend authorization is untouched and
|
|
488
|
-
* `roles` remain the only security authority, exactly like its siblings {@link ActionVisibility},
|
|
489
|
-
* {@link ActionPlacement} and {@link ResourceOperationActionScope}.
|
|
490
|
-
*
|
|
491
|
-
* ## It is an ALIAS, not a parallel mechanism
|
|
492
|
-
*
|
|
493
|
-
* `MODAL` and `PAGE` do not render anything themselves — they resolve to the navigation transitions
|
|
494
|
-
* that already exist (`OVERLAY`, and the ordinary chain), so there is one runtime mechanism and one
|
|
495
|
-
* set of zone/appearance/URL semantics. `DIRECT`, `POPOVER` and `INLINE` never enter navigation at
|
|
496
|
-
* all, because none of them is a destination: nothing is pushed, no zone changes, and there is
|
|
497
|
-
* nothing for a back button to pop. `INLINE` is hosted by the collection the element belongs to —
|
|
498
|
-
* see `InPlaceOperationContext` for why that is not the navigation layer's job.
|
|
499
|
-
*
|
|
500
|
-
* Consequently an explicit `navigationOverrides` entry still WINS over a presentation authored here
|
|
501
|
-
* (it is the more specific instrument, and it is checked first in the resolution chain). Author this
|
|
502
|
-
* axis to say what KIND of chrome the action wants; author `navigationOverrides` when you need to
|
|
503
|
-
* name the zone, the appearance or the viewport yourself.
|
|
504
|
-
*
|
|
505
|
-
* ## When omitted
|
|
506
|
-
*
|
|
507
|
-
* It is DERIVED from the operation — see `resolveResourceOperationActionPresentation()`. An
|
|
508
|
-
* operation that asks for nothing executes directly; a small field set opens a modal; input the
|
|
509
|
-
* framework cannot fit in an overlay (files, nested writes, a large field set) keeps the page it
|
|
510
|
-
* has always had. An operation whose `surface` is `ADDRESSABLE` always keeps its page: the author
|
|
511
|
-
* has already said it is a deep-linkable destination.
|
|
512
|
-
*/
|
|
513
|
-
export enum ResourceOperationActionPresentation {
|
|
514
|
-
/**
|
|
515
|
-
* Execute on click, with no form at all — the confirmation dialog for a risky operation is the
|
|
516
|
-
* only thing between the click and the request.
|
|
517
|
-
*
|
|
518
|
-
* Only meaningful for an operation that needs no caller input. Declaring it on an operation that
|
|
519
|
-
* DOES have required request fields would send an empty body, so the resolver refuses to derive it
|
|
520
|
-
* there and an author who declares it anyway gets the operation's fields dropped — check
|
|
521
|
-
* `requestDto` before reaching for this.
|
|
522
|
-
*/
|
|
523
|
-
DIRECT = 'direct',
|
|
524
|
-
/**
|
|
525
|
-
* A small form anchored to the button that opened it, dismissed by clicking away.
|
|
526
|
-
*
|
|
527
|
-
* The single-input idiom ("assign to…", "snooze until…"). Transient by construction: no URL, no
|
|
528
|
-
* history entry, nothing to deep-link. Use it when the surrounding context is the point — the user
|
|
529
|
-
* is reading the row they are acting on and must not lose sight of it.
|
|
530
|
-
*/
|
|
531
|
-
POPOVER = 'popover',
|
|
532
|
-
/**
|
|
533
|
-
* The element being acted on transforms in place to collect the input, leaving its neighbours
|
|
534
|
-
* visible — the row becomes the form rather than being covered by one.
|
|
535
|
-
*
|
|
536
|
-
* Use it when the surrounding rows are the point: the user is comparing, and an overlay would hide
|
|
537
|
-
* the very thing that made them act on this row.
|
|
538
|
-
*
|
|
539
|
-
* **Transient, like {@link POPOVER}, and for the same reason.** Nothing is pushed, no URL changes,
|
|
540
|
-
* and a reload returns the list to rest. An inline row-edit is a momentary state of a listing, not
|
|
541
|
-
* a place — which is also why no admin framework deep-links one, and why anything that SHOULD be
|
|
542
|
-
* linkable, reloadable or reachable by a back button wants {@link PAGE}.
|
|
543
|
-
*
|
|
544
|
-
* **It requires a collection.** The host is provided by the list the element belongs to
|
|
545
|
-
* (`InPlaceOperationProvider`); the same action rendered on a detail page, in a danger zone or in a
|
|
546
|
-
* picker has no row to transform and degrades to an overlay rather than becoming a dead button.
|
|
547
|
-
*
|
|
548
|
-
* Note it does NOT resolve to `NavigationTransition.INPLACE`. Element-level hosting uses none of
|
|
549
|
-
* what the navigation layer offers — no zone, no stack entry, no appearance — and routing it there
|
|
550
|
-
* is exactly why that transition has never done what its own docstring promises. See
|
|
551
|
-
* `InPlaceOperationContext`.
|
|
552
|
-
*/
|
|
553
|
-
INLINE = 'inline',
|
|
554
|
-
/**
|
|
555
|
-
* An overlay above the layout — the workhorse for "a handful of fields", and the default the
|
|
556
|
-
* derivation reaches for.
|
|
557
|
-
*
|
|
558
|
-
* Resolves to {@link NavigationTransition.OVERLAY}. The concrete appearance (dialog / sheet /
|
|
559
|
-
* drawer / panel) stays the app's decision, resolved from its navigation layout exactly as any
|
|
560
|
-
* other overlay: this axis says "an overlay", not "a dialog specifically". Author
|
|
561
|
-
* `navigationOverrides` when you need to name one.
|
|
562
|
-
*/
|
|
563
|
-
MODAL = 'modal',
|
|
564
|
-
/**
|
|
565
|
-
* A routable page, resolved through the ordinary navigation chain (zone transitions, viewport
|
|
566
|
-
* overrides, the framework `PUSH` fallback) — i.e. exactly the behaviour every parameterised
|
|
567
|
-
* action had before this axis existed.
|
|
568
|
-
*
|
|
569
|
-
* The right answer for complex or multi-step input, and for anything a user should be able to
|
|
570
|
-
* link to, reload, or reach with a back button.
|
|
571
|
-
*/
|
|
572
|
-
PAGE = 'page',
|
|
573
|
-
}
|
|
574
|
-
|
|
575
460
|
/**
|
|
576
461
|
* Does an operation's action target a SINGLE resource instance, or the WHOLE
|
|
577
462
|
* collection in the current scope?
|
|
@@ -700,26 +585,6 @@ export const CardActionPlacementSchema = z.object({
|
|
|
700
585
|
/** Authored 2-axis card action placement — inferred from {@link CardActionPlacementSchema}. */
|
|
701
586
|
export type CardActionPlacement = z.infer<typeof CardActionPlacementSchema>;
|
|
702
587
|
|
|
703
|
-
/**
|
|
704
|
-
* Who paints the identity GLYPH on this operation's page header.
|
|
705
|
-
*
|
|
706
|
-
* The header band renders the resource's registry icon beside the identity line by default. A
|
|
707
|
-
* `layout.header` template that composes its own record-linked glyph (a per-row kind icon, a
|
|
708
|
-
* per-family symbol) would otherwise sit BESIDE the resource icon — two glyphs naming one thing.
|
|
709
|
-
*
|
|
710
|
-
* Declared at the OPERATION layer rather than detected from the template, deliberately: the
|
|
711
|
-
* resource icon renders before the template mounts, so detection could only suppress it after the
|
|
712
|
-
* fact — a glyph that flashes and vanishes on every load. Mirrors
|
|
713
|
-
* `SummaryTitlePlacement.TEMPLATE_OWNED`, the same contract one surface over: ceding a
|
|
714
|
-
* framework-owned element to the template is a declaration, not an inference.
|
|
715
|
-
*/
|
|
716
|
-
export enum HeaderIconPlacement {
|
|
717
|
-
/** The framework renders the resource's registry icon (default). */
|
|
718
|
-
AUTO = 'auto',
|
|
719
|
-
/** The header template owns the glyph; the framework renders none. */
|
|
720
|
-
TEMPLATE_OWNED = 'template_owned',
|
|
721
|
-
}
|
|
722
|
-
|
|
723
588
|
export const ResourceOperationFrontendConfigSchema = z.object({
|
|
724
589
|
/**
|
|
725
590
|
* The operation's frontend **surface** — see {@link ResourceOperationFrontendSurface}.
|
|
@@ -731,8 +596,6 @@ export const ResourceOperationFrontendConfigSchema = z.object({
|
|
|
731
596
|
* Replaces the former `isAddressable` boolean — read via `isOperationAddressable()`.
|
|
732
597
|
*/
|
|
733
598
|
surface: z.enum(ResourceOperationFrontendSurface),
|
|
734
|
-
/** Who paints the page header's identity glyph — see {@link HeaderIconPlacement}. Omitted = AUTO. */
|
|
735
|
-
headerIconPlacement: z.enum(HeaderIconPlacement).optional(),
|
|
736
599
|
/**
|
|
737
600
|
* How this operation's action is surfaced — see {@link ActionVisibility}. Omitted
|
|
738
601
|
* (the common case) behaves as `ALWAYS`.
|
|
@@ -768,15 +631,6 @@ export const ResourceOperationFrontendConfigSchema = z.object({
|
|
|
768
631
|
* row id still rides the URL path too, which the handler may ignore.)
|
|
769
632
|
*/
|
|
770
633
|
rowTargetRequestField: z.string().optional(),
|
|
771
|
-
/**
|
|
772
|
-
* HOW this action collects its input — see {@link ResourceOperationActionPresentation}.
|
|
773
|
-
* Omitted derives from the operation (`resolveResourceOperationActionPresentation`): no input
|
|
774
|
-
* executes directly, a small field set opens a modal, complex input keeps its page.
|
|
775
|
-
*
|
|
776
|
-
* Display-only. An explicit `navigationOverrides` entry is the more specific instrument and wins
|
|
777
|
-
* over whatever this resolves to.
|
|
778
|
-
*/
|
|
779
|
-
actionPresentation: z.enum(ResourceOperationActionPresentation).optional(),
|
|
780
634
|
customView: z.any().optional(),
|
|
781
635
|
displayPresetOverride: z.object({
|
|
782
636
|
resourceLayoutPresetKey: z.string().optional(),
|
|
@@ -812,30 +666,6 @@ export const ResourceOperationFrontendConfigSchema = z.object({
|
|
|
812
666
|
* without a date heading rather than being dropped.
|
|
813
667
|
*/
|
|
814
668
|
temporalGroupField: z.string().optional(),
|
|
815
|
-
/**
|
|
816
|
-
* Group CARDS-mode rows into buckets by this ENUM field, rendering the
|
|
817
|
-
* enum value's own label as a heading between groups.
|
|
818
|
-
*
|
|
819
|
-
* Sibling of {@link temporalGroupField}, and deliberately NOT the same
|
|
820
|
-
* algorithm. Temporal grouping ADJACENT-MERGES in server order, because
|
|
821
|
-
* dates are open-ended and a page can legitimately revisit one. An enum is
|
|
822
|
-
* a CLOSED, ORDERED vocabulary, so its buckets are emitted in the enum's
|
|
823
|
-
* DECLARATION ORDER regardless of the order rows arrived in — the
|
|
824
|
-
* declaration is the authority for "which concern comes first", and a
|
|
825
|
-
* server sort cannot express it without a second, drifting copy of that
|
|
826
|
-
* order. Rows are therefore collected across the whole fetched page rather
|
|
827
|
-
* than merged adjacently, and no sort needs pairing with it.
|
|
828
|
-
*
|
|
829
|
-
* Headings resolve through `tResourceFieldEnumValue` — the SAME source the
|
|
830
|
-
* filters panel and the promoted quick-filter tabs use, so a bucket
|
|
831
|
-
* heading and its tab can never disagree.
|
|
832
|
-
*
|
|
833
|
-
* Ignored in TABLE mode (column sorting owns the ordering there). Rows
|
|
834
|
-
* whose value is absent, or outside the vocabulary, render in a trailing
|
|
835
|
-
* bucket with no heading rather than being dropped — the same fail-open
|
|
836
|
-
* the temporal grouping makes.
|
|
837
|
-
*/
|
|
838
|
-
enumGroupField: z.string().optional(),
|
|
839
669
|
/**
|
|
840
670
|
* CARDS-mode arrangement — a single-column bordered LIST (default) or an
|
|
841
671
|
* N-column responsive GRID. See {@link CardLayoutStyle}. `columns` (1–6) is
|
|
@@ -889,49 +719,6 @@ export const ResourceOperationFrontendConfigSchema = z.object({
|
|
|
889
719
|
* into a description via the `.describe()` decorator.
|
|
890
720
|
*/
|
|
891
721
|
hasDescription: z.boolean().optional(),
|
|
892
|
-
/**
|
|
893
|
-
* What happens to an ADJACENT zone (secondary / companion) this operation
|
|
894
|
-
* splits into, once that zone's last content is dismissed — overriding the
|
|
895
|
-
* zone's own `onEmpty` while this operation occupies primary.
|
|
896
|
-
*
|
|
897
|
-
* The zone-level `ZoneConfig.onEmpty` is one value for every destination that
|
|
898
|
-
* splits into that zone, and destinations legitimately disagree: a LIST wants
|
|
899
|
-
* the detail pane to stay put (`EMPTY_STATE`) so the layout does not reflow
|
|
900
|
-
* while a reviewer steps through rows, while a CANVAS wants its width back
|
|
901
|
-
* (`COLLAPSE`) the moment nothing is selected. Both share one secondary zone,
|
|
902
|
-
* so without this override one of them is always wrong.
|
|
903
|
-
*
|
|
904
|
-
* Declared on the SOURCE operation — the one occupying primary — not on the
|
|
905
|
-
* operation that lands in the pane: it answers "what should MY layout do when
|
|
906
|
-
* the detail closes", which is a property of the surface being returned to.
|
|
907
|
-
*
|
|
908
|
-
* Omitted (the common case) defers to the zone, which itself defaults to
|
|
909
|
-
* `ZoneEmptyBehavior.COLLAPSE`. Resolution order is destination → zone →
|
|
910
|
-
* COLLAPSE; see `resolveZoneEmptyBehavior`.
|
|
911
|
-
*/
|
|
912
|
-
adjacentZoneOnEmpty: z.enum(ZoneEmptyBehavior).optional(),
|
|
913
|
-
/**
|
|
914
|
-
* How wide this destination's content may grow in the zone, in the framework's shared width
|
|
915
|
-
* vocabulary — the SAME `ResponsiveMaxWidth` a Surface, a `DisplayLayout` and a `FormLayout` use.
|
|
916
|
-
*
|
|
917
|
-
* Omitted (the common case) is `'content'`: capped and centred at `var(--content-max-width, 80rem)`,
|
|
918
|
-
* right for a form, a list or a detail page and wrong only for content whose value IS the space it
|
|
919
|
-
* occupies — a board, a wide table, a canvas — which declare `'none'`.
|
|
920
|
-
*/
|
|
921
|
-
zoneContentMaxWidth: z.enum(RESPONSIVE_MAX_WIDTH_VALUES).optional(),
|
|
922
|
-
/**
|
|
923
|
-
* Whether this destination's content fills the zone's HEIGHT as well.
|
|
924
|
-
*
|
|
925
|
-
* `true` makes the zone's content boundary a definite-height flex column, so this view's root may use
|
|
926
|
-
* `flex-1 min-h-0` and resolve against something real. Without it a canvas has no intrinsic height
|
|
927
|
-
* and collapses to zero — which is why one had to hand-roll `h-[70vh]`, sizing against the WINDOW
|
|
928
|
-
* rather than the container it sits in. PRIMARY only: an adjacent zone scrolls, so a filling child
|
|
929
|
-
* and a scrolling parent contradict each other.
|
|
930
|
-
*
|
|
931
|
-
* Separate from the width above ON PURPOSE — see `zone-content-geometry.ts` for why the enum that
|
|
932
|
-
* fused them could not express a capped width with a definite height.
|
|
933
|
-
*/
|
|
934
|
-
zoneContentFillsHeight: z.boolean().optional(),
|
|
935
722
|
});
|
|
936
723
|
|
|
937
724
|
/**
|
|
@@ -103,6 +103,7 @@ export const moduleResourcesConfigurationsFactoryMap: ResourceConfiguration_Init
|
|
|
103
103
|
[TasksManager_ResourceType.TEAM_GOALS]: teamGoals_ResourceConfiguration_InitializationFactory,
|
|
104
104
|
[TasksManager_ResourceType.ORGANIZATION_PARTNERSHIPS]: organizationPartnerships_ResourceConfiguration_InitializationFactory,
|
|
105
105
|
[TasksManager_ResourceType.ORGANIZATION_ESCALATION_CONTACTS]: organizationEscalationContacts_ResourceConfiguration_InitializationFactory,
|
|
106
|
+
[TasksManager_ResourceType.EXTERNAL_CUSTOMERS]: externalCustomers_ResourceConfiguration_InitializationFactory,
|
|
106
107
|
[TasksManager_ResourceType.ACCOUNT_ERASURE_REQUESTS]: accountErasureRequests_ResourceConfiguration_InitializationFactory,
|
|
107
108
|
[TasksManager_ResourceType.KNOWLEDGE_DOCUMENTS]: knowledgeDocuments_ResourceConfiguration_InitializationFactory,
|
|
108
109
|
}
|
|
@@ -160,11 +161,9 @@ module barrel (`index.ts`) if siblings re-export theirs.
|
|
|
160
161
|
- `references/scaffold-surfaces-checklist.md` — surface checklist before "done"
|
|
161
162
|
- `references/framework-new-resource-core-config-api.md` — source-backed core operation / resource type / builder params
|
|
162
163
|
- `resource-config-wiring` → `references/framework-saas-models-resource-config-api.md` — typed config surface when authoring `resources-config`
|
|
163
|
-
- `resource-config-wiring` → `references/framework-personal-data-declaration-api.md` — **read once per new resource**: do its rows describe a person, and the four ways to answer
|
|
164
164
|
|
|
165
165
|
## Verification
|
|
166
166
|
|
|
167
|
-
- [ ] **The personal-data question is ANSWERED** — a `retentionPolicy` (`RETAIN_ONLY` says, checkably, that it holds none of its own), a `dataSubjectPolicy`, a `systemAccessPolicy.exportSubject`, or `.dataCategories()` on the fields that hold it. This is the cheapest moment; later means editing a shipped schema, and until it is answered the application's privacy notice can say nothing about this resource.
|
|
168
167
|
- [ ] New value added to the module's `<Module>_ResourceType` enum
|
|
169
168
|
- [ ] `<resource>.schemas.ts` exists and calls `initZodDecorators(z)` before schema definitions
|
|
170
169
|
- [ ] `<resource>.resources-config.ts` exists and matches the module's registration pattern
|
|
@@ -415,9 +415,7 @@ export type ResourceConfiguration_BuilderParameters<
|
|
|
415
415
|
* stance, erasure stance, and remote-call semantics. The factory enforces presence/absence
|
|
416
416
|
* coherence and content-validates the declaration.
|
|
417
417
|
*/
|
|
418
|
-
httpApiBinding?:
|
|
419
|
-
/** REQUIRED when `persistenceAdapter` is INTROSPECTION; meaningless otherwise. */
|
|
420
|
-
introspectionBinding?: IntrospectionResourceBinding,
|
|
418
|
+
httpApiBinding?: HttpApiResourceBindingAuthored,
|
|
421
419
|
|
|
422
420
|
/**
|
|
423
421
|
* OPTIONAL inbound ETL pipeline on an ordinary LOCAL resource — "some resources local, some
|
|
@@ -428,7 +426,7 @@ export type ResourceConfiguration_BuilderParameters<
|
|
|
428
426
|
* targets exist, accept null unless `required`, and are excludeFromCreate/Update; CLOSED
|
|
429
427
|
* population refuses caller CREATE operations).
|
|
430
428
|
*/
|
|
431
|
-
externalDataPipeline?:
|
|
429
|
+
externalDataPipeline?: ExternalDataPipelineDeclarationAuthored,
|
|
432
430
|
|
|
433
431
|
isSystemResource?: boolean, // default false - true for core system resources (organizations, users, etc.), false for tenant-specific resources
|
|
434
432
|
|
|
@@ -102,17 +102,6 @@ sending its email, or send an email without a usable token. Delivery is
|
|
|
102
102
|
best-effort—author an explicit product recovery operation such as RESEND when a
|
|
103
103
|
missing email must be recoverable.
|
|
104
104
|
|
|
105
|
-
For a variant whose synchronous round trip legitimately outlives the frontend's
|
|
106
|
-
30-second HTTP default — an operation that calls a model and waits, a blocking
|
|
107
|
-
generation, a long import — declare `clientRequestTimeoutMs` on that variant.
|
|
108
|
-
The frontend applies it as the per-request timeout on every dispatch shape.
|
|
109
|
-
Without it the request is aborted client-side while the server work succeeds:
|
|
110
|
-
the caller renders a network error and the operation-success refresh chain never
|
|
111
|
-
fires, so lists keep showing the pre-operation world. Do not hard-code timeouts
|
|
112
|
-
in consumer hooks instead — the variant is where the operation's own knowledge
|
|
113
|
-
of its duration belongs. Contract and a worked example:
|
|
114
|
-
`references/framework-saas-models-resource-config-api.md`.
|
|
115
|
-
|
|
116
105
|
### Step 5: Align with UI and spec
|
|
117
106
|
|
|
118
107
|
After config changes, `resource-ui-behavior` may need operation view updates;
|
|
@@ -303,17 +292,14 @@ fields (derived from the schema, never caller-supplied). Distinct from `isSystem
|
|
|
303
292
|
- `references/framework-saas-models-resource-config-api.md` — source-backed `resources-config` / registry types, including transactional token generation, relational `searchableFields`, and `forwardedLabel`
|
|
304
293
|
- `references/framework-saas-models-operation-scope-enums-api.md` — source-backed operation & scope enums
|
|
305
294
|
- `references/framework-system-access-reads-api.md` — source-backed `systemAccessPolicy` opt-in + the `SystemAccessBackendService` read AND trusted-write API (ACL-bypassing system-context reads + writes)
|
|
306
|
-
- `references/framework-personal-data-declaration-api.md` — **read once per resource**: does it hold data about a person, and the four ways to answer (including the checked way to say "no")
|
|
307
295
|
|
|
308
296
|
## Verification
|
|
309
297
|
|
|
310
|
-
- [ ] The resource has ANSWERED the personal-data question — a `retentionPolicy` (`RETAIN_ONLY` is the checked way to say it holds none of its own), a `dataSubjectPolicy`, a `systemAccessPolicy.exportSubject`, or a `.dataCategories()` declaration on the fields that hold it. Startup warns by name for every application resource that has said nothing.
|
|
311
298
|
- [ ] Every FK in the schema has a matching `createResourcesRelationship(...)` entry in the module relationships file
|
|
312
299
|
- [ ] Every relationship that resolves to multiple FKs to the same parent type sets `foreignKeyField` explicitly
|
|
313
300
|
- [ ] Operations referenced from `*.ui-behavior.tsx` exist in `*.resources-config.ts`
|
|
314
301
|
- [ ] Variants and discriminator wiring stays consistent with `createSchemaFamily` usage on the schema
|
|
315
302
|
- [ ] Role constraints (`roles: [...]`) match the product intent for each variant
|
|
316
|
-
- [ ] Any variant whose synchronous work can outlive ~30s declares `clientRequestTimeoutMs` (catch with the timeout grep below)
|
|
317
303
|
- [ ] `accessScopeStrategy` is set on every `REFERENCE` relationship (no implicit defaults relied upon)
|
|
318
304
|
- [ ] `contextPolicy` overrides for `LIST`/`SEARCH` are explicit when the relationship is high-cardinality
|
|
319
305
|
- [ ] Every relational `searchableFields` entry uses a `localField` that exists on this schema (and a `relatedJoinField` that exists on the related resource — defaults to `_id`)
|
|
@@ -331,7 +317,6 @@ Run from the app root and substitute the resource / FK field name:
|
|
|
331
317
|
| Relationship is co-located in the module-level relationships file (not inside config) | `rg -n "createResourcesRelationship" shared-lib/src/modules/*/resources/<resource>/<resource>.resources-config.ts` |
|
|
332
318
|
| Custom operation IDs in the UI exist in the resource config | `rg -n "operationLike:\\s*<Resource>_Operations\\." frontend/src/modules/*/resources/<resource>/<resource>.ui-behavior.tsx` |
|
|
333
319
|
| Same custom operation IDs are defined in the resource config | `rg -n "<Resource>_Operations\\." shared-lib/src/modules/*/resources/<resource>/<resource>.resources-config.ts` |
|
|
334
|
-
| Long-running variants declare their client timeout | `rg -n "clientRequestTimeoutMs" shared-lib/src/modules/*/resources/<resource>/<resource>.resources-config.ts` (expect a hit for any variant that generates/imports synchronously) |
|
|
335
320
|
| The two custom-operation lists agree | `comm -23 <(rg -oN "<Resource>_Operations\\.[A-Z_]+" frontend/src/modules/*/resources/<resource>/*.tsx \\| sort -u) <(rg -oN "<Resource>_Operations\\.[A-Z_]+" shared-lib/src/modules/*/resources/<resource>/*.ts \\| sort -u)` |
|
|
336
321
|
|
|
337
322
|
The third grep MUST return zero matches — relationship declarations in
|
|
@@ -176,174 +176,10 @@ export enum DataMode {
|
|
|
176
176
|
*
|
|
177
177
|
* If not specified at resource level, uses `appConfig.database.defaultAdapter`.
|
|
178
178
|
*/
|
|
179
|
-
/**
|
|
180
|
-
* What an INTROSPECTION-backed resource projects.
|
|
181
|
-
*
|
|
182
|
-
* Declared BY THE AUTHOR beside the resource, exactly as `httpApiBinding` is, and for the same
|
|
183
|
-
* reason: the adapter answers "how rows are reached", and everything specific to THIS resource's
|
|
184
|
-
* reach is a typed declaration rather than runtime inference.
|
|
185
|
-
*
|
|
186
|
-
* Keeping it here rather than in a companion-side lookup table matters. A table keyed by resource
|
|
187
|
-
* type would be a second enumeration of a population the resource configs already define — the
|
|
188
|
-
* shape that silently drifts when one side gains an entry.
|
|
189
|
-
*/
|
|
190
|
-
export enum IntrospectionTenancyStance {
|
|
191
|
-
/**
|
|
192
|
-
* The rows describe the APPLICATION'S OWN STRUCTURE — its modules, resource specifications,
|
|
193
|
-
* design system, compliance declarations — and carry no tenant dimension, so there is nothing for
|
|
194
|
-
* a contextual scope predicate to filter on.
|
|
195
|
-
*
|
|
196
|
-
* This is the only stance implemented, and it is declared rather than inferred for the reason
|
|
197
|
-
* `HttpApiTenancyStance` gives for its own: an unstated stance is indistinguishable from an
|
|
198
|
-
* overlooked one. Every other repository enforces scoping ITSELF — Mongo and PostgreSQL through
|
|
199
|
-
* `buildContextualFilter`, HTTP_API through its tenancy stance — so a read-through adapter that
|
|
200
|
-
* simply returned whatever its source produced would be the one backing kind with no scoping
|
|
201
|
-
* story, and nobody would be asked to notice.
|
|
202
|
-
*/
|
|
203
|
-
APPLICATION_STRUCTURE = 'application-structure',
|
|
204
|
-
|
|
205
|
-
/**
|
|
206
|
-
* The rows are the DEVELOPMENT COMPANION'S OWN RUNTIME PROJECTIONS for the one application it
|
|
207
|
-
* serves — the playbook eligibility board, the build plan, the run write-register, the execution
|
|
208
|
-
* traces. Like `APPLICATION_STRUCTURE` they carry no tenant dimension and no scope predicate can
|
|
209
|
-
* apply; UNLIKE it, they are not derived from the application's source, and the tenancy stance is
|
|
210
|
-
* where that difference must stay visible (added 2026-09-01, creation-board resources plan):
|
|
211
|
-
*
|
|
212
|
-
* - `APPLICATION_STRUCTURE`'s public-read posture (`APP_PUBLIC` variants on the workbench's
|
|
213
|
-
* structural projections) rests on the rows being the application's OWN source, which anyone
|
|
214
|
-
* with the working tree can already read. That argument does NOT extend to runtime state, so a
|
|
215
|
-
* resource declaring this stance is expected to gate its variants on an authenticated role —
|
|
216
|
-
* never `APP_PUBLIC`.
|
|
217
|
-
* - Row-level tenant-anchor checks are bypassed for this stance exactly as for
|
|
218
|
-
* `APPLICATION_STRUCTURE` (the rows carry no anchor BY CONTRACT); authorization comes from the
|
|
219
|
-
* session and the operation's role gate.
|
|
220
|
-
*
|
|
221
|
-
* Fusing this into `APPLICATION_STRUCTURE` was rejected for the enum's own founding reason: an
|
|
222
|
-
* unstated distinction is indistinguishable from an overlooked one, and the next decision site
|
|
223
|
-
* keyed off the stance would inherit a claim nobody checked.
|
|
224
|
-
*/
|
|
225
|
-
APPLICATION_RUNTIME = 'application-runtime',
|
|
226
|
-
|
|
227
|
-
/**
|
|
228
|
-
* The rows carry a tenant dimension and a scope predicate must be pushed into the source.
|
|
229
|
-
*
|
|
230
|
-
* REFUSED AT REGISTRATION today: no introspection behavior takes a scope argument, so the engine
|
|
231
|
-
* has nothing to push down. Declared as a member rather than omitted so the refusal is explicit
|
|
232
|
-
* and a future scoped behavior is a deliberate design step — the alternative is that the first
|
|
233
|
-
* author needing it discovers the gap by shipping unscoped rows.
|
|
234
|
-
*/
|
|
235
|
-
SCOPE_FILTER_PUSHDOWN = 'scope-filter-pushdown',
|
|
236
|
-
}
|
|
237
|
-
|
|
238
|
-
export interface IntrospectionResourceBinding {
|
|
239
|
-
/**
|
|
240
|
-
* The companion introspection behavior whose output becomes this resource's rows.
|
|
241
|
-
*
|
|
242
|
-
* A plain string on purpose: the behavior catalog lives in the companion (23 behaviors as of
|
|
243
|
-
* 2026-08-29) and the engine must not depend on it. An unknown id is refused by the companion at
|
|
244
|
-
* read time, naming the id and the supported set.
|
|
245
|
-
*/
|
|
246
|
-
readonly behavior: string;
|
|
247
|
-
|
|
248
|
-
/**
|
|
249
|
-
* Path into the behavior's result that holds the rows, dot-separated. Omitted means the result
|
|
250
|
-
* itself is the row collection.
|
|
251
|
-
*
|
|
252
|
-
* Behaviors answer their own natural shape — `{ frontendChartRegistrationRefs: [...] }` — and
|
|
253
|
-
* teaching each one to answer a uniform envelope would change 23 working behaviors to suit a
|
|
254
|
-
* consumer that arrived later.
|
|
255
|
-
*/
|
|
256
|
-
readonly rowsPath?: string;
|
|
257
|
-
|
|
258
|
-
/**
|
|
259
|
-
* REQUIRED. Why these rows need no contextual scope predicate, or that they do.
|
|
260
|
-
*
|
|
261
|
-
* Not optional and not defaulted: a default would make "nobody thought about tenancy" and
|
|
262
|
-
* "tenancy does not apply here" the same declaration.
|
|
263
|
-
*/
|
|
264
|
-
readonly tenancy: IntrospectionTenancyStance;
|
|
265
|
-
|
|
266
|
-
/**
|
|
267
|
-
* Fields whose values COMPOSE each row's primary key, in order, when the behavior's rows carry no
|
|
268
|
-
* identifier of their own.
|
|
269
|
-
*
|
|
270
|
-
* Most introspection behaviors answer structural projections rather than records: a module row
|
|
271
|
-
* carries `moduleId` and needs nothing here, while a relationship row carries only the two
|
|
272
|
-
* resource types it joins. Without a key such a resource can be LISTed and never READ, because
|
|
273
|
-
* there is no value to address a row by.
|
|
274
|
-
*
|
|
275
|
-
* Composition is DECLARED rather than derived because only the author knows which fields are
|
|
276
|
-
* jointly unique for a given behavior — and being wrong is not hypothetical. `resourceType1` +
|
|
277
|
-
* `resourceType2` is unique across all 16 relationships in the dogfood application and is still
|
|
278
|
-
* unsafe in general, since the framework permits several edges between the same pair (a junction
|
|
279
|
-
* with two roles, a self-relationship). So the source FAILS LOUDLY when two rows compose the same
|
|
280
|
-
* key rather than serving both under one id, which would make READ return an arbitrary one of
|
|
281
|
-
* them and give no sign anything was wrong.
|
|
282
|
-
*
|
|
283
|
-
* The composed value is written to the resource's own `resourceFieldIdentifier`, which is the one
|
|
284
|
-
* key name resolvable from the registry without introspecting the schema's decorators. A resource
|
|
285
|
-
* declaring `identityFields` must therefore name that field as its primary key.
|
|
286
|
-
*
|
|
287
|
-
* The values are joined verbatim, so the key stays READABLE — `workspace__users__createdByUserId`
|
|
288
|
-
* rather than an opaque hash. That is possible because an INTROSPECTION-backed resource resolves
|
|
289
|
-
* to `ResourceIdFormat.INTROSPECTION_SYNTHESIZED`, which admits a URL-safe charset instead of the
|
|
290
|
-
* ObjectId-or-UUID rule platform rows follow.
|
|
291
|
-
*
|
|
292
|
-
* It was briefly a deterministic UUIDv5, before that format existed. Hashing worked and was the
|
|
293
|
-
* wrong trade: it made every id opaque, and it disguised the real property — a DERIVED id is only
|
|
294
|
-
* as stable as the fields it is derived from, and hiding that behind a hash removes the reader's
|
|
295
|
-
* ability to notice when a row's identity moves.
|
|
296
|
-
*
|
|
297
|
-
* Each value must be URL-safe (`[a-zA-Z0-9_-]`) and the whole key at most 255 characters; the
|
|
298
|
-
* source refuses per row rather than emitting a key that lists and cannot be read.
|
|
299
|
-
*
|
|
300
|
-
* Omit when the behavior's rows already carry an identifier of their own.
|
|
301
|
-
*/
|
|
302
|
-
readonly identityFields?: readonly string[];
|
|
303
|
-
}
|
|
304
|
-
|
|
305
179
|
export enum PersistenceAdapter {
|
|
306
180
|
MONGODB = 'mongodb',
|
|
307
181
|
POSTGRESQL = 'postgresql',
|
|
308
182
|
|
|
309
|
-
/**
|
|
310
|
-
* Rows are DERIVED on demand by asking the running dev companion to introspect the application —
|
|
311
|
-
* its resource registry, specifications, design system, compliance facts, assertions, market and
|
|
312
|
-
* persona context. Nothing is stored: every read recomputes.
|
|
313
|
-
*
|
|
314
|
-
* ## Why this is an adapter and not a service call
|
|
315
|
-
*
|
|
316
|
-
* The companion already computes all of it — 23 named introspection behaviors — and today each is
|
|
317
|
-
* reachable only through a bespoke route. Making it an adapter is what turns those behaviors into
|
|
318
|
-
* ordinary RESOURCES: list, read, filter, search, labels, navigation, all generated, with no
|
|
319
|
-
* per-behavior UI. That is the same argument `HTTP_API` settled on 2026-08-26 — the adapter answers
|
|
320
|
-
* "how rows are reached", and the mechanism behind it is a binding an author declares.
|
|
321
|
-
*
|
|
322
|
-
* Distinct from `HTTP_API`, deliberately, and not merely because the transport differs. Retrieval
|
|
323
|
-
* is the COMPANION's decision per behavior (amended 2026-09-01): the app-import behaviors run a
|
|
324
|
-
* SUBPROCESS that imports the target application's built modules — seconds per read, requiring
|
|
325
|
-
* that application's `dist`, failing as a thrown behavior — while the creation-plane behaviors
|
|
326
|
-
* are IN-PROCESS projections of the companion's own runtime services (playbook eligibility,
|
|
327
|
-
* build plan, write register, traces). Both reach the engine through the same
|
|
328
|
-
* `IntrospectionResourceSourceBackendPort`; the adapter never encodes the mechanism, which is
|
|
329
|
-
* exactly why a behavior id is an engine-opaque string. Collapsing this into `HTTP_API` would
|
|
330
|
-
* still be wrong for the original reason: its failure mode is a source throwing rather than a
|
|
331
|
-
* row being absent, and nothing here is reached over a network API.
|
|
332
|
-
*
|
|
333
|
-
* ## What every adapter decision site must honor
|
|
334
|
-
*
|
|
335
|
-
* - **READ-ONLY, absolutely.** There is no writable target: a row is a projection of the
|
|
336
|
-
* application's own source. Every write method refuses, as `HTTP_API`'s twelve do.
|
|
337
|
-
* - **No provisioning, migration or schema surface.** Nothing is stored, so there is nothing to
|
|
338
|
-
* create, migrate or verify — the platform must never believe it owns a store here.
|
|
339
|
-
* - **Never a legal application-wide DEFAULT adapter.** It is a per-resource declaration only;
|
|
340
|
-
* an application whose default was introspection could persist nothing at all.
|
|
341
|
-
* - **It must DEGRADE, never fail closed at boot.** The companion is the only thing that can run
|
|
342
|
-
* an introspection behavior, so a boot path that refuses on an introspection failure would need
|
|
343
|
-
* the companion to fix the companion — see `continuity-drift-and-cas-basis.md` Rule 3.
|
|
344
|
-
*/
|
|
345
|
-
INTROSPECTION = 'introspection',
|
|
346
|
-
|
|
347
183
|
/**
|
|
348
184
|
* Rows live in a system reached over an authenticated HTTP API and are queried on demand
|
|
349
185
|
* (read-through). Decided 2026-08-26 (ETL workstream, D1): this IS a persistence-adapter answer
|
|
@@ -857,9 +693,7 @@ export type ResourceConfiguration_BuilderParameters<
|
|
|
857
693
|
* stance, erasure stance, and remote-call semantics. The factory enforces presence/absence
|
|
858
694
|
* coherence and content-validates the declaration.
|
|
859
695
|
*/
|
|
860
|
-
httpApiBinding?:
|
|
861
|
-
/** REQUIRED when `persistenceAdapter` is INTROSPECTION; meaningless otherwise. */
|
|
862
|
-
introspectionBinding?: IntrospectionResourceBinding,
|
|
696
|
+
httpApiBinding?: HttpApiResourceBindingAuthored,
|
|
863
697
|
|
|
864
698
|
/**
|
|
865
699
|
* OPTIONAL inbound ETL pipeline on an ordinary LOCAL resource — "some resources local, some
|
|
@@ -870,7 +704,7 @@ export type ResourceConfiguration_BuilderParameters<
|
|
|
870
704
|
* targets exist, accept null unless `required`, and are excludeFromCreate/Update; CLOSED
|
|
871
705
|
* population refuses caller CREATE operations).
|
|
872
706
|
*/
|
|
873
|
-
externalDataPipeline?:
|
|
707
|
+
externalDataPipeline?: ExternalDataPipelineDeclarationAuthored,
|
|
874
708
|
|
|
875
709
|
isSystemResource?: boolean, // default false - true for core system resources (organizations, users, etc.), false for tenant-specific resources
|
|
876
710
|
|
|
@@ -1152,46 +986,6 @@ export type ResourceConfiguration_Operation_ApiCall<
|
|
|
1152
986
|
|
|
1153
987
|
### Origin Package: `@wildo-ai/saas-models`
|
|
1154
988
|
|
|
1155
|
-
```typescript
|
|
1156
|
-
*
|
|
1157
|
-
* Frontend HTTP timeout for THIS variant, in milliseconds — declare it on any operation whose
|
|
1158
|
-
* synchronous round trip legitimately outlives the frontend client's 30-second default (an
|
|
1159
|
-
* operation that calls a model and waits for the answer, a long import, a blocking generation).
|
|
1160
|
-
*
|
|
1161
|
-
* The frontend resources client applies it as the per-request timeout on every dispatch shape
|
|
1162
|
-
* (api-call, api-call-with-callback, search). An explicit caller-supplied
|
|
1163
|
-
* `RequestOptions.timeout` still wins; omitting the field keeps the client default.
|
|
1164
|
-
*
|
|
1165
|
-
* Why it matters: without it, a long-running operation's request is aborted CLIENT-side while
|
|
1166
|
-
* the server work succeeds — the caller renders a network error, and the operation-success
|
|
1167
|
-
* refresh chain never fires, so lists keep showing the pre-operation world. Declare the
|
|
1168
|
-
* expectation on the variant (the operation knows it is long-running); do not hard-code
|
|
1169
|
-
* timeouts in consumer hooks, which duplicates that knowledge at every call site.
|
|
1170
|
-
*
|
|
1171
|
-
* This is a TRANSPORT expectation only — not a UI/observability signal (that is `riskLevel`)
|
|
1172
|
-
* and not a server-side bound: the backend is free to answer sooner or be cut off by its own
|
|
1173
|
-
* limits.
|
|
1174
|
-
*
|
|
1175
|
-
* @example a custom operation that generates a document before answering
|
|
1176
|
-
* variants: [{
|
|
1177
|
-
* variantType: ResourceOperationVariantType.API_CALL,
|
|
1178
|
-
* roles: [CORE_ORG_ROLES.ORG_MEMBER],
|
|
1179
|
-
* riskLevel: ResourceOperationRiskLevel.MEDIUM,
|
|
1180
|
-
* clientRequestTimeoutMs: 300_000, // five minutes — the generation is synchronous
|
|
1181
|
-
* requestDto: GenerateReportRequest_Schema,
|
|
1182
|
-
* customResponseDto: GenerateReportOutcome_Schema,
|
|
1183
|
-
* }]
|
|
1184
|
-
*/
|
|
1185
|
-
clientRequestTimeoutMs?: number;
|
|
1186
|
-
```
|
|
1187
|
-
## Import Origins
|
|
1188
|
-
|
|
1189
|
-
- `@wildo-ai/saas-models`
|
|
1190
|
-
|
|
1191
|
-
## Source Excerpts
|
|
1192
|
-
|
|
1193
|
-
### Origin Package: `@wildo-ai/saas-models`
|
|
1194
|
-
|
|
1195
989
|
```typescript
|
|
1196
990
|
*
|
|
1197
991
|
* Variant builder type that distributes operation-specific fields based on the operation key.
|
|
@@ -1705,8 +1499,6 @@ export type ResourceConfiguration<
|
|
|
1705
1499
|
* (factory-enforced both ways). See the authoring-side declaration for the full contract.
|
|
1706
1500
|
*/
|
|
1707
1501
|
httpApiBinding?: HttpApiResourceBinding,
|
|
1708
|
-
/** REQUIRED when `persistenceAdapter` is INTROSPECTION; meaningless otherwise. */
|
|
1709
|
-
introspectionBinding?: IntrospectionResourceBinding,
|
|
1710
1502
|
|
|
1711
1503
|
/**
|
|
1712
1504
|
* The inbound ETL pipeline, when this LOCAL resource declared one — parsed + coherence-checked
|
|
@@ -1786,20 +1578,6 @@ export type ResourcesRegistry = {
|
|
|
1786
1578
|
resourceConfigurations: {
|
|
1787
1579
|
[key: ResourceType]: AnyResourceConfiguration ;
|
|
1788
1580
|
};
|
|
1789
|
-
/**
|
|
1790
|
-
* The resource types the APPLICATION registered — its own, never the engine's.
|
|
1791
|
-
*
|
|
1792
|
-
* The registry composes app and core factory maps into one `resourceConfigurations`, which is what
|
|
1793
|
-
* every runtime consumer wants. This is the one place the two are still distinguishable, so the
|
|
1794
|
-
* split is recorded HERE rather than re-derived by each consumer from a core key set — which would
|
|
1795
|
-
* be a second enumeration of a population this file already knows.
|
|
1796
|
-
*
|
|
1797
|
-
* Its consumer today is the personal-data declaration report, which asks a question only an
|
|
1798
|
-
* application author can act on: the engine declares its own posture on ~85 resources, and putting
|
|
1799
|
-
* those in front of a reader of a report about THEIR application is how a diagnostic channel stops
|
|
1800
|
-
* being read.
|
|
1801
|
-
*/
|
|
1802
|
-
applicationResourceTypes: ResourceType[];
|
|
1803
1581
|
/**
|
|
1804
1582
|
* Map of ResourceType to its standard field identifier (e.g., USERS -> userId).
|
|
1805
1583
|
* Used for FK field resolution without string manipulation.
|