@wildo-ai/framework-knowledge 1.1.1 → 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 +271 -8
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts +19 -0
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js +32 -0
- package/dist/esm/framework-knowledge.loader.js.map +1 -1
- package/dist/esm/framework-knowledge.schemas.d.ts +13 -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 +45 -0
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +55 -0
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +6 -7
- 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 +6 -6
- 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 -4
- 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 -2
- 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 -4
- 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 -2
- 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 +3 -9
- 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 -3
- 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 +10 -6
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +25 -4
- 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 -5
- 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 -3
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +4 -2
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +4 -2
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -2
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -14
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +3 -5
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +3 -4
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +2 -8
- 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 -2
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +2 -8
- 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 -2
- 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 +52 -0
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +127 -0
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +75 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +91 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +29 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +28 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +9 -45
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +4 -54
- 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 +30 -0
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +25 -0
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -9
- 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 -5
- 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 -9
- 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 -2
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +2 -8
- 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 -2
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -8
- 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 -2
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +2 -8
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +5 -4
- 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 -4
- 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 -2
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +4 -6
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +25 -5
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/knowledge/manifest.json +6 -7
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +7 -47
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +6 -13
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +1 -82
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +11 -6
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -5
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +3 -4
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +3 -4
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +15 -735
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +11 -7
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +16 -123
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +15 -8
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +10 -4
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +10 -4
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +12 -5
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +10 -4
- 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 +39 -21
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +2 -6
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +10 -4
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +1 -1
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +11 -5
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +11 -5
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +10 -4
- package/dist/knowledge/references/build-plan.task-graph.config.md +1 -45
- package/dist/knowledge/references/example.config.app-shell.full.md +4 -0
- 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 -50
- package/dist/knowledge/references/saas.external-data.admin-endpoints.md +48 -0
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +10 -6
- package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +1 -0
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +0 -109
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -137
- package/dist/knowledge/references/saas.models.http-api-binding.md +29 -3
- 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 +1 -1
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +0 -36
- 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 -1
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +1 -1
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +0 -1
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +11 -48
- package/dist/knowledge/registries/playbooks.json +11 -74
- package/dist/knowledge/registries/source-tags.json +538 -622
- package/dist/knowledge/skills/INDEX.md +0 -1
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -16
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +8 -26
- 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 +21 -36
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +19 -49
- package/dist/knowledge/skills/config-app-shell/SKILL.md +8 -6
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +11 -6
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +0 -50
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +0 -7
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +0 -36
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +0 -36
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +0 -36
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +0 -109
- 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 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +2 -157
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +0 -109
- 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-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-zod-lifecycle-and-chainable-api.md +0 -26
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +1 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +0 -109
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +1 -1
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +0 -36
- package/dist/knowledge/topic-index.json +128 -285
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/esm/.builder.pid +0 -9
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +0 -185
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +0 -66
- 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 -40
- package/dist/knowledge/playbooks/top_down.market-research/method.md +0 -68
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -42
- 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 -69
- package/dist/knowledge/references/placement-plan.config.md +0 -330
- 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/zod.decorators.data-categories.md +0 -197
- package/dist/knowledge/rules/resource-schema-awareness.md +0 -77
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +0 -622
- 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,40 +1,25 @@
|
|
|
1
|
-
#
|
|
1
|
+
# Accepted application document-fact declaration contract
|
|
2
2
|
|
|
3
|
-
Read this before
|
|
4
|
-
qualified-review
|
|
3
|
+
Read this before adding a fact that the standard application/infrastructure
|
|
4
|
+
projectors cannot derive, or before changing a creator or qualified-review
|
|
5
|
+
decision used by a governed document.
|
|
5
6
|
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
-
|
|
18
|
-
|
|
19
|
-
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
- One current value for each fact version and governance scope. Replace it with a new
|
|
23
|
-
declaration/specification version; do not retain two current values and hide the conflict.
|
|
24
|
-
- Keep candidate reviews, approvals and releases out of the specification.
|
|
25
|
-
- Omitting this family, or a declaration a document needs, leaves a visible blocking fact gap. Never
|
|
26
|
-
create an empty family or a placeholder value to make a candidate look configured — an invented
|
|
27
|
-
value in a governed document is the one failure this whole lane exists to prevent.
|
|
28
|
-
|
|
29
|
-
## Acceptance is a commit, and there is nothing to copy
|
|
30
|
-
|
|
31
|
-
An earlier version said to author through "normal family acceptance" and warned against copying
|
|
32
|
-
"contribution, accepted-head, semantic-member or validation-receipt digests", alongside reviewer
|
|
33
|
-
authority grants.
|
|
34
|
-
|
|
35
|
-
None of those exist. Accepted means committed: a declared fact is a file, a human commits it, and
|
|
36
|
-
`git log` is the record of who accepted what and when. A warning against copying a digest is worse
|
|
37
|
-
than silent — it tells a reader the digest exists somewhere and that finding it is part of the job.
|
|
7
|
+
- Declare raw current facts in the dedicated accepted `document-facts`
|
|
8
|
+
specification family and expose it as `documentFactSpecification`.
|
|
9
|
+
- Use the authority kind required by the exact blueprint question. An accepted
|
|
10
|
+
TypeScript module never upgrades a creator decision into qualified review or
|
|
11
|
+
turns a human decision into runtime evidence.
|
|
12
|
+
- Author fact value or explicit not-applicable rationale, governance scope,
|
|
13
|
+
sensitivity and human decision metadata only. Never copy contribution,
|
|
14
|
+
accepted-head, semantic-member or validation-receipt digests.
|
|
15
|
+
- One current declaration is allowed for each fact version and governance
|
|
16
|
+
scope. Replace it through a new declaration/specification version and normal
|
|
17
|
+
family acceptance; do not retain two current values and hide the conflict.
|
|
18
|
+
- Keep reviewer grants, candidate reviews, approvals and releases out of the
|
|
19
|
+
specification. They are separate private runtime records.
|
|
20
|
+
- Omitting this optional family or a required declaration leaves a visible
|
|
21
|
+
blocking fact gap. Do not create an empty family or placeholder value to make
|
|
22
|
+
a candidate appear configured.
|
|
38
23
|
|
|
39
24
|
## Import Origins
|
|
40
25
|
|
|
@@ -66,7 +51,7 @@ than silent — it tells a reader the digest exists somewhere and that finding i
|
|
|
66
51
|
export const ApplicationDocumentFactSpecificationSchema = z
|
|
67
52
|
.strictObject({
|
|
68
53
|
schemaVersion: z.literal(1),
|
|
69
|
-
specificationRef:
|
|
54
|
+
specificationRef: AssuranceNamespacedRefSchema,
|
|
70
55
|
specificationVersion: GovernedDocumentPositiveSafeIntegerSchema,
|
|
71
56
|
declarations: z.array(ApplicationDocumentFactDeclarationSchema).min(1),
|
|
72
57
|
})
|
|
@@ -1,54 +1,24 @@
|
|
|
1
1
|
# Assurance document-blueprint contract
|
|
2
2
|
|
|
3
|
-
The engine owns the source-neutral document catalog and its blueprints.
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
From `catalogVersion` 5 onward each qualified-review policy binds reviewer qualifications to the exact
|
|
24
|
-
review kind rather than carrying one flat policy; the retained versions must keep the historical flat
|
|
25
|
-
shape, so the two are not interchangeable. `catalogVersion` 6 additionally requires
|
|
26
|
-
`structuredValueContracts`, each selected by exactly one annex binding — which is why moving the
|
|
27
|
-
shipped catalog forward is authoring work rather than a version bump.
|
|
28
|
-
|
|
29
|
-
Questions declare answer type, fact authority, sensitivity, not-applicable posture and semantic
|
|
30
|
-
options. Sections own visible order. Clauses own drafting purpose, fact variables, monitored source
|
|
31
|
-
policies, claim guards and optional declarative inclusion conditions. Conditions inside a group are
|
|
32
|
-
ANDed and groups are ORed; no executable expression is accepted. A REQUIRED clause carries no
|
|
33
|
-
condition groups. Review checklists cover every review kind the definition's review policies select.
|
|
34
|
-
|
|
35
|
-
The contract contains drafting structure, not jurisdiction-specific legal prose, an application fact,
|
|
36
|
-
an approval decision, a publication release or an interaction receipt.
|
|
37
|
-
|
|
38
|
-
## Nothing here is sealed, and nothing needs verifying before you author
|
|
39
|
-
|
|
40
|
-
An earlier version of this page said the engine owned "sealed blueprints", that a blueprint and its
|
|
41
|
-
catalog carried "independent canonical digests", and that "both must verify before authoring."
|
|
42
|
-
|
|
43
|
-
No such digests exist. They went with the rest of the digest machinery, and the engine source records
|
|
44
|
-
why beside the identities that used to carry them: a digest chain cannot merge, so two branches that
|
|
45
|
-
change different blueprints produce a merged catalog whose digests belong to neither — while git
|
|
46
|
-
already carries exactly the history the digests were imitating.
|
|
47
|
-
|
|
48
|
-
The instruction mattered more than the mechanism did. It told a drafting agent to perform a
|
|
49
|
-
verification step that has no implementation, before doing the work it was actually asked for. There
|
|
50
|
-
is nothing to verify: read the catalog, answer its questions from declared facts, and let the diff be
|
|
51
|
-
the evidence.
|
|
3
|
+
The engine owns the source-neutral document catalog and its sealed blueprints.
|
|
4
|
+
Applications contribute accepted facts and explicit decisions; they do not
|
|
5
|
+
copy blueprint definitions or engine digests into application specifications.
|
|
6
|
+
|
|
7
|
+
Catalog `schemaVersion: 1` is retained only for historical parsing. New
|
|
8
|
+
authoring uses `schemaVersion: 2`, where every document definition has exactly
|
|
9
|
+
one blueprint. Each blueprint and the enclosing catalog have independent
|
|
10
|
+
canonical digests. Both must verify before authoring.
|
|
11
|
+
|
|
12
|
+
Questions declare answer type, fact authority, sensitivity, not-applicable
|
|
13
|
+
posture and semantic options. Sections own visible order. Clauses own drafting
|
|
14
|
+
purpose, fact variables, monitored source policies, claim guards and optional
|
|
15
|
+
declarative inclusion conditions. Conditions inside a group are ANDed and
|
|
16
|
+
groups are ORed. Review checklists cover every review kind selected by the
|
|
17
|
+
definition's review policies.
|
|
18
|
+
|
|
19
|
+
The contract contains drafting structure, not jurisdiction-specific legal
|
|
20
|
+
prose, an application fact, an approval decision, a publication release or an
|
|
21
|
+
interaction receipt.
|
|
52
22
|
|
|
53
23
|
The complete source-neutral contract is:
|
|
54
24
|
|
|
@@ -296,8 +296,12 @@ export const appShellConfig : AppConfiguration_Frontend['appComponentsConfigurat
|
|
|
296
296
|
],
|
|
297
297
|
showOrgSwitcher: true,
|
|
298
298
|
showLogout: true,
|
|
299
|
+
mergeSettings: false,
|
|
299
300
|
},
|
|
300
301
|
|
|
302
|
+
[ApplicationLevelComponentType.SETTINGS_DROPDOWN]: {
|
|
303
|
+
mergedWith: ApplicationLevelComponentType.USER_DROPDOWN,
|
|
304
|
+
},
|
|
301
305
|
|
|
302
306
|
[ApplicationLevelComponentType.NAVIGATION_CONTROL]: true,
|
|
303
307
|
|
|
@@ -359,12 +363,10 @@ What earns its place:
|
|
|
359
363
|
`[ApplicationLevelComponentType.HOTKEY]: true` to the platform hotkey
|
|
360
364
|
provider, which is what makes `Cmd+K` reachable.
|
|
361
365
|
- `USER_DROPDOWN.sections: [UserDropdownSection.*, ...]` orders the
|
|
362
|
-
dropdown contents. `
|
|
363
|
-
|
|
364
|
-
|
|
365
|
-
|
|
366
|
-
the same vocabulary `settings-hub.config.ts` places — never sidebar
|
|
367
|
-
section refs. There is no separate enable flag: the list is the intent.
|
|
366
|
+
dropdown contents. `mergeSettings: false` keeps the settings
|
|
367
|
+
dropdown separate; `SETTINGS_DROPDOWN.mergedWith` then lets a
|
|
368
|
+
separate dropdown declare it merges into another — this is the
|
|
369
|
+
framework's idiom for "two surfaces, one popover".
|
|
368
370
|
- Deferred surfaces (`ACTIVITY_BAR`, `UTILITY_PANEL`,
|
|
369
371
|
`CONTROL_PANEL`) are explicitly set to `false`. This is **not**
|
|
370
372
|
optional — explicit disable signals "we know this exists, we chose
|
|
@@ -35,6 +35,7 @@ export enum ApplicationLevelComponentType {
|
|
|
35
35
|
* renders the same preset. Exists to allow separate config entries while reusing
|
|
36
36
|
* the user dropdown component. For distinct UX, register a dedicated preset.
|
|
37
37
|
*/
|
|
38
|
+
SETTINGS_DROPDOWN = 'settings_dropdown',
|
|
38
39
|
NAVIGATION_CONTROL = 'navigation_control',
|
|
39
40
|
/** Mode selector — renders available `AppMode`s as selectable icons. */
|
|
40
41
|
ACTIVITY_BAR = 'activity_bar',
|
|
@@ -372,12 +373,16 @@ export const AppLevelComponentConfigurationSchema = z.object({
|
|
|
372
373
|
sections: z.array(z.enum(UserDropdownSection)).optional(),
|
|
373
374
|
showOrgSwitcher: z.boolean().default(true),
|
|
374
375
|
showLogout: z.boolean().default(true),
|
|
375
|
-
|
|
376
|
-
|
|
377
|
-
|
|
378
|
-
|
|
379
|
-
|
|
380
|
-
|
|
376
|
+
mergeSettings: z.boolean().default(false),
|
|
377
|
+
/** Sidebar section ref for the single settings block merged into the dropdown when `mergeSettings` is true. */
|
|
378
|
+
settingsSectionRef: z.string().optional(),
|
|
379
|
+
}),
|
|
380
|
+
]).default(true),
|
|
381
|
+
|
|
382
|
+
[ApplicationLevelComponentType.SETTINGS_DROPDOWN]: z.union([
|
|
383
|
+
z.boolean().default(true),
|
|
384
|
+
z.object({
|
|
385
|
+
mergedWith: z.literal(ApplicationLevelComponentType.USER_DROPDOWN),
|
|
381
386
|
}),
|
|
382
387
|
]).default(true),
|
|
383
388
|
|
|
@@ -96,56 +96,6 @@ export const WildoSaasConfigSchema = z.strictObject({
|
|
|
96
96
|
bootstrap: AppBootstrapSchema.optional(),
|
|
97
97
|
dataServices: AppDataServicesSchema,
|
|
98
98
|
|
|
99
|
-
/**
|
|
100
|
-
* How long this application keeps each class of data, and why.
|
|
101
|
-
*
|
|
102
|
-
* Declared HERE, beside `dataServices`, because the two describe the same thing from opposite ends:
|
|
103
|
-
* `dataServices` says which stores exist, and this says how long what is in them is kept. Both are
|
|
104
|
-
* application-wide operator decisions rather than per-resource authoring.
|
|
105
|
-
*
|
|
106
|
-
* Optional as a whole, and partial within itself. An application that has decided nothing omits it;
|
|
107
|
-
* one that has decided only its customer-data period declares only that. Absence is never read as
|
|
108
|
-
* "kept forever" — a compliance document states the classes that ARE declared and marks the rest as
|
|
109
|
-
* needing an operator decision, which is what lets the document be produced today rather than
|
|
110
|
-
* waiting on a number nobody has yet.
|
|
111
|
-
*
|
|
112
|
-
* Two consumers, and the second is why the classes are the STORES: a privacy notice's retention
|
|
113
|
-
* paragraph (issue #89, which is why this exists), and the backup-and-restore inventory a remote
|
|
114
|
-
* environment still has none of (issue #8) — one declaration answers both instead of two that drift.
|
|
115
|
-
*/
|
|
116
|
-
dataRetention: ApplicationRetentionScheduleSchema.optional(),
|
|
117
|
-
|
|
118
|
-
/**
|
|
119
|
-
* Whether each AI capability this application enables DECIDES something about a person, and who
|
|
120
|
-
* reviews it if so.
|
|
121
|
-
*
|
|
122
|
-
* A capability establishes that AI is in use and for what function; it cannot establish consequence,
|
|
123
|
-
* because the same `AI_LLM` backs a summariser that decides nothing and a screener that decides a
|
|
124
|
-
* great deal (issue #92).
|
|
125
|
-
*
|
|
126
|
-
* Optional and partial, like `dataRetention` — but the silence here is the more dangerous one. A
|
|
127
|
-
* notice describing AI use without addressing consequence does not read as "unknown", it reads as
|
|
128
|
-
* "nothing significant happens", which silently claims an exemption. So an enabled AI capability with
|
|
129
|
-
* no entry is REPORTED as outstanding rather than assumed harmless.
|
|
130
|
-
*/
|
|
131
|
-
aiUsePosture: ApplicationAiUsePostureSchema.optional(),
|
|
132
|
-
|
|
133
|
-
/**
|
|
134
|
-
* What this application stores in a visitor's browser, per FRONTEND SURFACE — the itemised table a
|
|
135
|
-
* cookie notice IS (issue #91).
|
|
136
|
-
*
|
|
137
|
-
* Per surface because a public marketing site and the authenticated application set different things,
|
|
138
|
-
* and one merged list would be wrong for both. The FRAMEWORK's own cookies are not declared here:
|
|
139
|
-
* every application inherits them and none authored them, so they are answered by
|
|
140
|
-
* `ENGINE_CLIENT_STORAGE_ENTRIES` and reported separately.
|
|
141
|
-
*
|
|
142
|
-
* Optional and partial. A surface with no entry has not been inventoried and is reported as such; an
|
|
143
|
-
* empty ARRAY is the different, positive answer — this surface sets nothing of its own.
|
|
144
|
-
*/
|
|
145
|
-
clientStorage: ApplicationClientStorageInventorySchema.optional(),
|
|
146
|
-
operatorComplianceIdentity: ApplicationOperatorComplianceIdentitySchema.optional(),
|
|
147
|
-
providerComplianceChoices: ApplicationProviderComplianceChoicesSchema.optional(),
|
|
148
|
-
|
|
149
99
|
/**
|
|
150
100
|
* Module registries the app pulls modules from. Each entry pairs a
|
|
151
101
|
* stable id (used by lockfile entries + the `--registry <id>` CLI
|
package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md
CHANGED
|
@@ -39,13 +39,6 @@ export const StripeBackendProvider: BackendProviderModule = {
|
|
|
39
39
|
ref: "stripe",
|
|
40
40
|
displayNameLabelKey: buildProviderDisplayNameLabelKey('stripe'),
|
|
41
41
|
},
|
|
42
|
-
// WHO can run this, and where its vendor processes — read by the compliance-document lane to
|
|
43
|
-
// decide whether this provider is a third-party recipient at all (issue #130).
|
|
44
|
-
complianceProfile: {
|
|
45
|
-
deploymentModels: [ProviderDeploymentModel.VENDOR_HOSTED],
|
|
46
|
-
processingRegions: ['us-east-1', 'eu-west-1'],
|
|
47
|
-
vendorLegalEntityName: 'Stripe, Inc.',
|
|
48
|
-
},
|
|
49
42
|
providerCapabilities: [
|
|
50
43
|
BUILTIN_PROVIDER_CAPABILITY.BILLING,
|
|
51
44
|
],
|
|
@@ -857,7 +857,6 @@ export interface SpecificationsCompanionExports<
|
|
|
857
857
|
TRequirementsSnapshot = RequirementsSnapshot,
|
|
858
858
|
TRoadmapSnapshot = RoadmapSnapshot,
|
|
859
859
|
TBuildPlanTaskGraph = BuildPlanTaskGraph,
|
|
860
|
-
TPlacementPlan = PlacementPlan,
|
|
861
860
|
TDomainPlanOutputSet = DomainPlanOutputSet,
|
|
862
861
|
TBusinessModelLiteSnapshot = BusinessModelLiteSnapshot,
|
|
863
862
|
// Appended STRICTLY LAST (positional generics — never insert mid-list):
|
|
@@ -885,11 +884,6 @@ export interface SpecificationsCompanionExports<
|
|
|
885
884
|
// Appended STRICTLY LAST: release-process selection is a separate accepted
|
|
886
885
|
// decision, never an implicit default of routing or document necessity.
|
|
887
886
|
TDocumentReleasePolicySpecification = ApplicationDocumentReleasePolicySpecification,
|
|
888
|
-
// Appended STRICTLY LAST: WHO else processes personal data, under what legal
|
|
889
|
-
// identity and where (issue #88). Optional, and the optionality is the design:
|
|
890
|
-
// a partial register is useful and its holes are REPORTED per provider against
|
|
891
|
-
// the application's configured set, rather than blocking anything.
|
|
892
|
-
TProcessorRegister = ApplicationProcessorRegister,
|
|
893
887
|
> {
|
|
894
888
|
resourceSpecifications: TResourceSpecifications;
|
|
895
889
|
applicationBusinessSemanticsSnapshot?: TBusinessSemanticsSnapshot;
|
|
@@ -1120,22 +1114,6 @@ export interface SpecificationsCompanionExports<
|
|
|
1120
1114
|
* `validateBuildPlanTaskGraph` on the value before wiring it here.
|
|
1121
1115
|
*/
|
|
1122
1116
|
buildPlanSpecification?: TBuildPlanTaskGraph;
|
|
1123
|
-
/**
|
|
1124
|
-
* Application **placement** specification — WHERE every settings destination,
|
|
1125
|
-
* resource operation and app view sits in the shell, and WHY (`PlacementPlan`,
|
|
1126
|
-
* `_core/placement-plan/`).
|
|
1127
|
-
*
|
|
1128
|
-
* Produced by the `bottom_up.placement-plan` playbook as an expert-panel
|
|
1129
|
-
* DELIBERATION rather than a creator elicitation: the creator does not choose
|
|
1130
|
-
* placement, so each decision carries a `rationale` that answers "why is this
|
|
1131
|
-
* here?" without re-running the panel. Consumed by build-decompose, which
|
|
1132
|
-
* turns it into the coding tasks that author `settings-hub.config.ts` and
|
|
1133
|
-
* `app-shell.config.ts`.
|
|
1134
|
-
*
|
|
1135
|
-
* Optional until an application reaches the bottom-up phase; app bootstraps
|
|
1136
|
-
* should run `validatePlacementPlan` on the value before wiring it here.
|
|
1137
|
-
*/
|
|
1138
|
-
placementPlanSpecification?: TPlacementPlan;
|
|
1139
1117
|
/**
|
|
1140
1118
|
* Application **domain-plan** specification — the atomic module decomposition
|
|
1141
1119
|
* PLUS relationship drafts (`DomainPlanOutputSet`, `_core/domain-plan/`);
|
|
@@ -1274,20 +1252,6 @@ export interface SpecificationsCompanionExports<
|
|
|
1274
1252
|
* Omitting it is honest: unresolved document facts remain visible gaps.
|
|
1275
1253
|
*/
|
|
1276
1254
|
documentFactSpecification?: TDocumentFactSpecification;
|
|
1277
|
-
/**
|
|
1278
|
-
* WHO else processes this application's personal data — legal identity, processing region and the
|
|
1279
|
-
* processor's own subprocessors (issue #88).
|
|
1280
|
-
*
|
|
1281
|
-
* A configured provider already establishes THAT a third party is involved and what function it
|
|
1282
|
-
* performs. None of that is what a privacy notice's recipient statement needs, and an
|
|
1283
|
-
* international-transfer statement cannot be made at all without a region.
|
|
1284
|
-
*
|
|
1285
|
-
* Optional, and its holes are reported rather than blocking: the companion compares this register
|
|
1286
|
-
* against the application's CONFIGURED providers and names each one that is undeclared, so a partial
|
|
1287
|
-
* register is useful and an empty one still produces an actionable document. An absent entry means
|
|
1288
|
-
* nobody has established that processor's identity — never that the provider is unused.
|
|
1289
|
-
*/
|
|
1290
|
-
processorRegister?: TProcessorRegister;
|
|
1291
1255
|
/**
|
|
1292
1256
|
* Accepted application-declared semantic causality between whole
|
|
1293
1257
|
* specification-family states. This is not the registry's physical
|
|
@@ -763,7 +763,6 @@ export interface SpecificationsCompanionExports<
|
|
|
763
763
|
TRequirementsSnapshot = RequirementsSnapshot,
|
|
764
764
|
TRoadmapSnapshot = RoadmapSnapshot,
|
|
765
765
|
TBuildPlanTaskGraph = BuildPlanTaskGraph,
|
|
766
|
-
TPlacementPlan = PlacementPlan,
|
|
767
766
|
TDomainPlanOutputSet = DomainPlanOutputSet,
|
|
768
767
|
TBusinessModelLiteSnapshot = BusinessModelLiteSnapshot,
|
|
769
768
|
// Appended STRICTLY LAST (positional generics — never insert mid-list):
|
|
@@ -791,11 +790,6 @@ export interface SpecificationsCompanionExports<
|
|
|
791
790
|
// Appended STRICTLY LAST: release-process selection is a separate accepted
|
|
792
791
|
// decision, never an implicit default of routing or document necessity.
|
|
793
792
|
TDocumentReleasePolicySpecification = ApplicationDocumentReleasePolicySpecification,
|
|
794
|
-
// Appended STRICTLY LAST: WHO else processes personal data, under what legal
|
|
795
|
-
// identity and where (issue #88). Optional, and the optionality is the design:
|
|
796
|
-
// a partial register is useful and its holes are REPORTED per provider against
|
|
797
|
-
// the application's configured set, rather than blocking anything.
|
|
798
|
-
TProcessorRegister = ApplicationProcessorRegister,
|
|
799
793
|
> {
|
|
800
794
|
resourceSpecifications: TResourceSpecifications;
|
|
801
795
|
applicationBusinessSemanticsSnapshot?: TBusinessSemanticsSnapshot;
|
|
@@ -1026,22 +1020,6 @@ export interface SpecificationsCompanionExports<
|
|
|
1026
1020
|
* `validateBuildPlanTaskGraph` on the value before wiring it here.
|
|
1027
1021
|
*/
|
|
1028
1022
|
buildPlanSpecification?: TBuildPlanTaskGraph;
|
|
1029
|
-
/**
|
|
1030
|
-
* Application **placement** specification — WHERE every settings destination,
|
|
1031
|
-
* resource operation and app view sits in the shell, and WHY (`PlacementPlan`,
|
|
1032
|
-
* `_core/placement-plan/`).
|
|
1033
|
-
*
|
|
1034
|
-
* Produced by the `bottom_up.placement-plan` playbook as an expert-panel
|
|
1035
|
-
* DELIBERATION rather than a creator elicitation: the creator does not choose
|
|
1036
|
-
* placement, so each decision carries a `rationale` that answers "why is this
|
|
1037
|
-
* here?" without re-running the panel. Consumed by build-decompose, which
|
|
1038
|
-
* turns it into the coding tasks that author `settings-hub.config.ts` and
|
|
1039
|
-
* `app-shell.config.ts`.
|
|
1040
|
-
*
|
|
1041
|
-
* Optional until an application reaches the bottom-up phase; app bootstraps
|
|
1042
|
-
* should run `validatePlacementPlan` on the value before wiring it here.
|
|
1043
|
-
*/
|
|
1044
|
-
placementPlanSpecification?: TPlacementPlan;
|
|
1045
1023
|
/**
|
|
1046
1024
|
* Application **domain-plan** specification — the atomic module decomposition
|
|
1047
1025
|
* PLUS relationship drafts (`DomainPlanOutputSet`, `_core/domain-plan/`);
|
|
@@ -1180,20 +1158,6 @@ export interface SpecificationsCompanionExports<
|
|
|
1180
1158
|
* Omitting it is honest: unresolved document facts remain visible gaps.
|
|
1181
1159
|
*/
|
|
1182
1160
|
documentFactSpecification?: TDocumentFactSpecification;
|
|
1183
|
-
/**
|
|
1184
|
-
* WHO else processes this application's personal data — legal identity, processing region and the
|
|
1185
|
-
* processor's own subprocessors (issue #88).
|
|
1186
|
-
*
|
|
1187
|
-
* A configured provider already establishes THAT a third party is involved and what function it
|
|
1188
|
-
* performs. None of that is what a privacy notice's recipient statement needs, and an
|
|
1189
|
-
* international-transfer statement cannot be made at all without a region.
|
|
1190
|
-
*
|
|
1191
|
-
* Optional, and its holes are reported rather than blocking: the companion compares this register
|
|
1192
|
-
* against the application's CONFIGURED providers and names each one that is undeclared, so a partial
|
|
1193
|
-
* register is useful and an empty one still produces an actionable document. An absent entry means
|
|
1194
|
-
* nobody has established that processor's identity — never that the provider is unused.
|
|
1195
|
-
*/
|
|
1196
|
-
processorRegister?: TProcessorRegister;
|
|
1197
1161
|
/**
|
|
1198
1162
|
* Accepted application-declared semantic causality between whole
|
|
1199
1163
|
* specification-family states. This is not the registry's physical
|
package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md
CHANGED
|
@@ -68,7 +68,6 @@ export interface SpecificationsCompanionExports<
|
|
|
68
68
|
TRequirementsSnapshot = RequirementsSnapshot,
|
|
69
69
|
TRoadmapSnapshot = RoadmapSnapshot,
|
|
70
70
|
TBuildPlanTaskGraph = BuildPlanTaskGraph,
|
|
71
|
-
TPlacementPlan = PlacementPlan,
|
|
72
71
|
TDomainPlanOutputSet = DomainPlanOutputSet,
|
|
73
72
|
TBusinessModelLiteSnapshot = BusinessModelLiteSnapshot,
|
|
74
73
|
// Appended STRICTLY LAST (positional generics — never insert mid-list):
|
|
@@ -96,11 +95,6 @@ export interface SpecificationsCompanionExports<
|
|
|
96
95
|
// Appended STRICTLY LAST: release-process selection is a separate accepted
|
|
97
96
|
// decision, never an implicit default of routing or document necessity.
|
|
98
97
|
TDocumentReleasePolicySpecification = ApplicationDocumentReleasePolicySpecification,
|
|
99
|
-
// Appended STRICTLY LAST: WHO else processes personal data, under what legal
|
|
100
|
-
// identity and where (issue #88). Optional, and the optionality is the design:
|
|
101
|
-
// a partial register is useful and its holes are REPORTED per provider against
|
|
102
|
-
// the application's configured set, rather than blocking anything.
|
|
103
|
-
TProcessorRegister = ApplicationProcessorRegister,
|
|
104
98
|
> {
|
|
105
99
|
resourceSpecifications: TResourceSpecifications;
|
|
106
100
|
applicationBusinessSemanticsSnapshot?: TBusinessSemanticsSnapshot;
|
|
@@ -331,22 +325,6 @@ export interface SpecificationsCompanionExports<
|
|
|
331
325
|
* `validateBuildPlanTaskGraph` on the value before wiring it here.
|
|
332
326
|
*/
|
|
333
327
|
buildPlanSpecification?: TBuildPlanTaskGraph;
|
|
334
|
-
/**
|
|
335
|
-
* Application **placement** specification — WHERE every settings destination,
|
|
336
|
-
* resource operation and app view sits in the shell, and WHY (`PlacementPlan`,
|
|
337
|
-
* `_core/placement-plan/`).
|
|
338
|
-
*
|
|
339
|
-
* Produced by the `bottom_up.placement-plan` playbook as an expert-panel
|
|
340
|
-
* DELIBERATION rather than a creator elicitation: the creator does not choose
|
|
341
|
-
* placement, so each decision carries a `rationale` that answers "why is this
|
|
342
|
-
* here?" without re-running the panel. Consumed by build-decompose, which
|
|
343
|
-
* turns it into the coding tasks that author `settings-hub.config.ts` and
|
|
344
|
-
* `app-shell.config.ts`.
|
|
345
|
-
*
|
|
346
|
-
* Optional until an application reaches the bottom-up phase; app bootstraps
|
|
347
|
-
* should run `validatePlacementPlan` on the value before wiring it here.
|
|
348
|
-
*/
|
|
349
|
-
placementPlanSpecification?: TPlacementPlan;
|
|
350
328
|
/**
|
|
351
329
|
* Application **domain-plan** specification — the atomic module decomposition
|
|
352
330
|
* PLUS relationship drafts (`DomainPlanOutputSet`, `_core/domain-plan/`);
|
|
@@ -485,20 +463,6 @@ export interface SpecificationsCompanionExports<
|
|
|
485
463
|
* Omitting it is honest: unresolved document facts remain visible gaps.
|
|
486
464
|
*/
|
|
487
465
|
documentFactSpecification?: TDocumentFactSpecification;
|
|
488
|
-
/**
|
|
489
|
-
* WHO else processes this application's personal data — legal identity, processing region and the
|
|
490
|
-
* processor's own subprocessors (issue #88).
|
|
491
|
-
*
|
|
492
|
-
* A configured provider already establishes THAT a third party is involved and what function it
|
|
493
|
-
* performs. None of that is what a privacy notice's recipient statement needs, and an
|
|
494
|
-
* international-transfer statement cannot be made at all without a region.
|
|
495
|
-
*
|
|
496
|
-
* Optional, and its holes are reported rather than blocking: the companion compares this register
|
|
497
|
-
* against the application's CONFIGURED providers and names each one that is undeclared, so a partial
|
|
498
|
-
* register is useful and an empty one still produces an actionable document. An absent entry means
|
|
499
|
-
* nobody has established that processor's identity — never that the provider is unused.
|
|
500
|
-
*/
|
|
501
|
-
processorRegister?: TProcessorRegister;
|
|
502
466
|
/**
|
|
503
467
|
* Accepted application-declared semantic causality between whole
|
|
504
468
|
* specification-family states. This is not the registry's physical
|
package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md
CHANGED
|
@@ -457,106 +457,6 @@ export enum ActionPlacement {
|
|
|
457
457
|
DANGER_ZONE = 'danger_zone',
|
|
458
458
|
}
|
|
459
459
|
|
|
460
|
-
/**
|
|
461
|
-
* HOW an operation's action collects its input and shows its result — the chrome the user meets
|
|
462
|
-
* when they click the button.
|
|
463
|
-
*
|
|
464
|
-
* ## Why this axis exists
|
|
465
|
-
*
|
|
466
|
-
* Until this axis, one rule decided the answer for every custom operation:
|
|
467
|
-
* *has a `requestDto` ⇒ navigate*. So an action asking for a single reason string got the same
|
|
468
|
-
* full-page treatment as a multi-step wizard, and the only way out was to author
|
|
469
|
-
* `navigationOverrides` — per operation, in terms of a zone, a transition verb and an appearance.
|
|
470
|
-
* Three concepts to answer one question.
|
|
471
|
-
*
|
|
472
|
-
* This is that one question. It is a **display-only** axis: backend authorization is untouched and
|
|
473
|
-
* `roles` remain the only security authority, exactly like its siblings {@link ActionVisibility},
|
|
474
|
-
* {@link ActionPlacement} and {@link ResourceOperationActionScope}.
|
|
475
|
-
*
|
|
476
|
-
* ## It is an ALIAS, not a parallel mechanism
|
|
477
|
-
*
|
|
478
|
-
* `MODAL` and `PAGE` do not render anything themselves — they resolve to the navigation transitions
|
|
479
|
-
* that already exist (`OVERLAY`, and the ordinary chain), so there is one runtime mechanism and one
|
|
480
|
-
* set of zone/appearance/URL semantics. `DIRECT`, `POPOVER` and `INLINE` never enter navigation at
|
|
481
|
-
* all, because none of them is a destination: nothing is pushed, no zone changes, and there is
|
|
482
|
-
* nothing for a back button to pop. `INLINE` is hosted by the collection the element belongs to —
|
|
483
|
-
* see `InPlaceOperationContext` for why that is not the navigation layer's job.
|
|
484
|
-
*
|
|
485
|
-
* Consequently an explicit `navigationOverrides` entry still WINS over a presentation authored here
|
|
486
|
-
* (it is the more specific instrument, and it is checked first in the resolution chain). Author this
|
|
487
|
-
* axis to say what KIND of chrome the action wants; author `navigationOverrides` when you need to
|
|
488
|
-
* name the zone, the appearance or the viewport yourself.
|
|
489
|
-
*
|
|
490
|
-
* ## When omitted
|
|
491
|
-
*
|
|
492
|
-
* It is DERIVED from the operation — see `resolveResourceOperationActionPresentation()`. An
|
|
493
|
-
* operation that asks for nothing executes directly; a small field set opens a modal; input the
|
|
494
|
-
* framework cannot fit in an overlay (files, nested writes, a large field set) keeps the page it
|
|
495
|
-
* has always had. An operation whose `surface` is `ADDRESSABLE` always keeps its page: the author
|
|
496
|
-
* has already said it is a deep-linkable destination.
|
|
497
|
-
*/
|
|
498
|
-
export enum ResourceOperationActionPresentation {
|
|
499
|
-
/**
|
|
500
|
-
* Execute on click, with no form at all — the confirmation dialog for a risky operation is the
|
|
501
|
-
* only thing between the click and the request.
|
|
502
|
-
*
|
|
503
|
-
* Only meaningful for an operation that needs no caller input. Declaring it on an operation that
|
|
504
|
-
* DOES have required request fields would send an empty body, so the resolver refuses to derive it
|
|
505
|
-
* there and an author who declares it anyway gets the operation's fields dropped — check
|
|
506
|
-
* `requestDto` before reaching for this.
|
|
507
|
-
*/
|
|
508
|
-
DIRECT = 'direct',
|
|
509
|
-
/**
|
|
510
|
-
* A small form anchored to the button that opened it, dismissed by clicking away.
|
|
511
|
-
*
|
|
512
|
-
* The single-input idiom ("assign to…", "snooze until…"). Transient by construction: no URL, no
|
|
513
|
-
* history entry, nothing to deep-link. Use it when the surrounding context is the point — the user
|
|
514
|
-
* is reading the row they are acting on and must not lose sight of it.
|
|
515
|
-
*/
|
|
516
|
-
POPOVER = 'popover',
|
|
517
|
-
/**
|
|
518
|
-
* The element being acted on transforms in place to collect the input, leaving its neighbours
|
|
519
|
-
* visible — the row becomes the form rather than being covered by one.
|
|
520
|
-
*
|
|
521
|
-
* Use it when the surrounding rows are the point: the user is comparing, and an overlay would hide
|
|
522
|
-
* the very thing that made them act on this row.
|
|
523
|
-
*
|
|
524
|
-
* **Transient, like {@link POPOVER}, and for the same reason.** Nothing is pushed, no URL changes,
|
|
525
|
-
* and a reload returns the list to rest. An inline row-edit is a momentary state of a listing, not
|
|
526
|
-
* a place — which is also why no admin framework deep-links one, and why anything that SHOULD be
|
|
527
|
-
* linkable, reloadable or reachable by a back button wants {@link PAGE}.
|
|
528
|
-
*
|
|
529
|
-
* **It requires a collection.** The host is provided by the list the element belongs to
|
|
530
|
-
* (`InPlaceOperationProvider`); the same action rendered on a detail page, in a danger zone or in a
|
|
531
|
-
* picker has no row to transform and degrades to an overlay rather than becoming a dead button.
|
|
532
|
-
*
|
|
533
|
-
* Note it does NOT resolve to `NavigationTransition.INPLACE`. Element-level hosting uses none of
|
|
534
|
-
* what the navigation layer offers — no zone, no stack entry, no appearance — and routing it there
|
|
535
|
-
* is exactly why that transition has never done what its own docstring promises. See
|
|
536
|
-
* `InPlaceOperationContext`.
|
|
537
|
-
*/
|
|
538
|
-
INLINE = 'inline',
|
|
539
|
-
/**
|
|
540
|
-
* An overlay above the layout — the workhorse for "a handful of fields", and the default the
|
|
541
|
-
* derivation reaches for.
|
|
542
|
-
*
|
|
543
|
-
* Resolves to {@link NavigationTransition.OVERLAY}. The concrete appearance (dialog / sheet /
|
|
544
|
-
* drawer / panel) stays the app's decision, resolved from its navigation layout exactly as any
|
|
545
|
-
* other overlay: this axis says "an overlay", not "a dialog specifically". Author
|
|
546
|
-
* `navigationOverrides` when you need to name one.
|
|
547
|
-
*/
|
|
548
|
-
MODAL = 'modal',
|
|
549
|
-
/**
|
|
550
|
-
* A routable page, resolved through the ordinary navigation chain (zone transitions, viewport
|
|
551
|
-
* overrides, the framework `PUSH` fallback) — i.e. exactly the behaviour every parameterised
|
|
552
|
-
* action had before this axis existed.
|
|
553
|
-
*
|
|
554
|
-
* The right answer for complex or multi-step input, and for anything a user should be able to
|
|
555
|
-
* link to, reload, or reach with a back button.
|
|
556
|
-
*/
|
|
557
|
-
PAGE = 'page',
|
|
558
|
-
}
|
|
559
|
-
|
|
560
460
|
/**
|
|
561
461
|
* Does an operation's action target a SINGLE resource instance, or the WHOLE
|
|
562
462
|
* collection in the current scope?
|
|
@@ -731,15 +631,6 @@ export const ResourceOperationFrontendConfigSchema = z.object({
|
|
|
731
631
|
* row id still rides the URL path too, which the handler may ignore.)
|
|
732
632
|
*/
|
|
733
633
|
rowTargetRequestField: z.string().optional(),
|
|
734
|
-
/**
|
|
735
|
-
* HOW this action collects its input — see {@link ResourceOperationActionPresentation}.
|
|
736
|
-
* Omitted derives from the operation (`resolveResourceOperationActionPresentation`): no input
|
|
737
|
-
* executes directly, a small field set opens a modal, complex input keeps its page.
|
|
738
|
-
*
|
|
739
|
-
* Display-only. An explicit `navigationOverrides` entry is the more specific instrument and wins
|
|
740
|
-
* over whatever this resolves to.
|
|
741
|
-
*/
|
|
742
|
-
actionPresentation: z.enum(ResourceOperationActionPresentation).optional(),
|
|
743
634
|
customView: z.any().optional(),
|
|
744
635
|
displayPresetOverride: z.object({
|
|
745
636
|
resourceLayoutPresetKey: z.string().optional(),
|
|
@@ -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
|
|