@wildo-ai/framework-knowledge 1.1.1 → 1.1.2
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 +43 -2
- 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 +12 -0
- 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 +46 -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 +4 -4
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +3 -3
- 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 -3
- 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 -3
- 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 +2 -7
- 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 +0 -1
- 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 +8 -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 +22 -1
- 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 +0 -3
- 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 +0 -1
- 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 -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 +4 -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 +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -13
- 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 -4
- 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 -3
- 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 -7
- 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 +2 -7
- 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 +54 -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 +76 -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 +92 -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 +30 -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 +29 -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 -44
- 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 -53
- 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 +31 -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 +26 -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 -7
- 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 +0 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +0 -8
- 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 +2 -7
- 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 +2 -7
- 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 +2 -7
- 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 -3
- 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 -3
- 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 +4 -5
- 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 -4
- 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/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
- package/dist/knowledge/manifest.json +8 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +51 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +27 -10
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +8 -7
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +6 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +4 -6
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +5 -4
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +4 -6
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +0 -4
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +4 -6
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +49 -22
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +14 -6
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +2 -4
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +46 -1
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +7 -3
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +18 -4
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +4 -2
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +2 -3
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +8 -7
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +3 -5
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +0 -2
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +100 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +117 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +86 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +41 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +21 -4
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +14 -57
- package/dist/knowledge/playbooks/top_down.compliance-research/method.md +76 -0
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +42 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +3 -5
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +3 -1
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +3 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +3 -5
- package/dist/knowledge/playbooks/top_down.phase-gate/method.md +8 -4
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +9 -7
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +8 -7
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +0 -2
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +8 -7
- package/dist/knowledge/references/companion.technical-doc.service.md +102 -2
- package/dist/knowledge/references/example.config.app-shell.full.md +0 -1
- package/dist/knowledge/references/example.module.companion-exports.full.md +1 -0
- package/dist/knowledge/references/platform.config.saas.md +1 -0
- package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +25 -1
- package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +45 -0
- package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
- package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +89 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +31 -4
- package/dist/knowledge/references/saas.models.engine-capabilities.md +26 -6
- package/dist/knowledge/references/saas.models.file-upload-grant.md +179 -0
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +127 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +4 -3
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
- package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
- package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +11 -31
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +32 -2
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +29 -6
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +20 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +6 -0
- package/dist/knowledge/references/zod.decorators.field-spec-params.md +31 -5
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +43 -0
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +15 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
- package/dist/knowledge/registries/framework-topics.json +99 -1
- package/dist/knowledge/registries/playbooks.json +81 -8
- package/dist/knowledge/registries/source-tags.json +757 -588
- package/dist/knowledge/skills/INDEX.md +3 -3
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +5 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +66 -37
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +40 -7
- package/dist/knowledge/skills/config-app-shell/SKILL.md +25 -1
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +25 -1
- package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +23 -1
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
- package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
- package/dist/knowledge/skills/config-navigation/SKILL.md +75 -2
- package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +149 -0
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +114 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +133 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +19 -2
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +111 -0
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +30 -9
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +1 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +2 -1
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +20 -0
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +20 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +20 -0
- 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 +104 -0
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +13 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +71 -4
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +89 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +22 -1
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +192 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +28 -8
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +15 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +6 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +89 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +43 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +1 -1
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +20 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +31 -5
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +22 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +45 -0
- package/dist/knowledge/topic-index.json +504 -156
- 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
|
@@ -0,0 +1,127 @@
|
|
|
1
|
+
# saas.models.navigation.zone-declaration
|
|
2
|
+
|
|
3
|
+
## Import Origins
|
|
4
|
+
|
|
5
|
+
- `@wildo-ai/saas-models`
|
|
6
|
+
|
|
7
|
+
## Source Excerpts
|
|
8
|
+
|
|
9
|
+
### Origin Package: `@wildo-ai/saas-models`
|
|
10
|
+
|
|
11
|
+
```typescript
|
|
12
|
+
*
|
|
13
|
+
* What happens when a zone's last content is dismissed.
|
|
14
|
+
* Only meaningful for secondary and companion zones (primary never empties,
|
|
15
|
+
* overlay auto-dismisses by definition).
|
|
16
|
+
*/
|
|
17
|
+
export enum ZoneEmptyBehavior {
|
|
18
|
+
/**
|
|
19
|
+
* Zone hides, adjacent zones expand to fill the space.
|
|
20
|
+
* Example: closing the last detail → layout returns to list-only.
|
|
21
|
+
* This is the default for all non-primary zones.
|
|
22
|
+
*/
|
|
23
|
+
COLLAPSE = 'collapse',
|
|
24
|
+
/**
|
|
25
|
+
* Zone stays visible with an empty-state placeholder.
|
|
26
|
+
* Example: "Select an item to view details" message. Keeps layout stable.
|
|
27
|
+
* Useful when the user frequently toggles between items.
|
|
28
|
+
*/
|
|
29
|
+
EMPTY_STATE = 'emptyState',
|
|
30
|
+
}
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
### Origin Package: `@wildo-ai/saas-models`
|
|
34
|
+
|
|
35
|
+
```typescript
|
|
36
|
+
*
|
|
37
|
+
* How much of its zone a DESTINATION's content occupies.
|
|
38
|
+
*
|
|
39
|
+
* The primary zone caps and centres its content at `var(--content-max-width, 80rem)` and gives it no
|
|
40
|
+
* definite-height ancestor. That is correct for almost everything a zone hosts — a form, a list, a
|
|
41
|
+
* settings page stretched across a 2560px monitor is unreadable — and wrong for content whose whole
|
|
42
|
+
* value is the space it occupies. Until this enum existed there was no way to tell the two apart, so
|
|
43
|
+
* a canvas had to hand-roll a viewport fraction (`h-[70vh]`), which sizes against the WINDOW rather
|
|
44
|
+
* than the container and therefore ignores whatever chrome sits above it.
|
|
45
|
+
*
|
|
46
|
+
* Declared per DESTINATION rather than per zone: the same primary zone hosts a list that wants the
|
|
47
|
+
* cap, a detail page that caps itself, and a graph that wants neither.
|
|
48
|
+
*
|
|
49
|
+
* Width and height are separable on purpose. A wide data table wants the cap gone and its natural
|
|
50
|
+
* height; collapsing both into one boolean would merge two meanings, and two independent booleans
|
|
51
|
+
* would make "full height, still capped at 80rem" representable — a combination nothing wants and
|
|
52
|
+
* someone would eventually author by accident.
|
|
53
|
+
*/
|
|
54
|
+
|
|
55
|
+
/**
|
|
56
|
+
* Full zone configuration.
|
|
57
|
+
*
|
|
58
|
+
* Each declared zone in the layout owns its complete behavior:
|
|
59
|
+
* which transition fires for each operation, how content appears,
|
|
60
|
+
* and how the zone responds to viewport changes.
|
|
61
|
+
*
|
|
62
|
+
* Note: `minWidth`, `maxWidth`, `defaultVisible`, `onEmpty`,
|
|
63
|
+
* and `responsiveCollapse` are only meaningful for secondary and companion zones.
|
|
64
|
+
* Primary never collapses, never empties, and takes remaining space.
|
|
65
|
+
* Setting these on primary has no effect.
|
|
66
|
+
*/
|
|
67
|
+
export const ZoneConfigSchema = z.object({
|
|
68
|
+
/**
|
|
69
|
+
* How this zone manages multiple items.
|
|
70
|
+
* - `NavigationZoneContentModel.SINGLE` (default): stack-based navigation. One item visible, back pops.
|
|
71
|
+
* - `NavigationZoneContentModel.TABBED`: parallel tabs. Tab bar visible, multiple items accessible.
|
|
72
|
+
* @default NavigationZoneContentModel.SINGLE
|
|
73
|
+
*/
|
|
74
|
+
contentModel: z.enum(NavigationZoneContentModel).default(NavigationZoneContentModel.SINGLE),
|
|
75
|
+
|
|
76
|
+
/** Operation → transition mapping. Defines what happens for each user action in this zone. */
|
|
77
|
+
transitions: ZoneTransitionsSchema,
|
|
78
|
+
|
|
79
|
+
/** Transition → visual appearance. Only split and overlay have appearance choices. */
|
|
80
|
+
appearance: ZoneAppearanceSchema.optional(),
|
|
81
|
+
|
|
82
|
+
/**
|
|
83
|
+
* Minimum pixel width when resizing. Constrains how far this side of the
|
|
84
|
+
* split divider can be dragged. Only meaningful for secondary and companion zones.
|
|
85
|
+
* Works in conjunction with `SplitConfigSchema.resizable`.
|
|
86
|
+
*/
|
|
87
|
+
minWidth: z.number().positive().optional(),
|
|
88
|
+
|
|
89
|
+
/**
|
|
90
|
+
* Maximum pixel width when resizing. Constrains how far this side of the
|
|
91
|
+
* split divider can be dragged. Only meaningful for secondary and companion zones.
|
|
92
|
+
* Works in conjunction with `SplitConfigSchema.resizable`.
|
|
93
|
+
*/
|
|
94
|
+
maxWidth: z.number().positive().optional(),
|
|
95
|
+
|
|
96
|
+
/**
|
|
97
|
+
* Whether this zone is visible on first render (before any transition targets it).
|
|
98
|
+
* - Primary: always visible (this field is ignored).
|
|
99
|
+
* - Secondary: defaults to `true` when `split.autoSplit` is `true`, `false` otherwise.
|
|
100
|
+
* - Companion: defaults to `false` (hidden until a `split` transition targets it or user toggles).
|
|
101
|
+
*/
|
|
102
|
+
defaultVisible: z.boolean().optional(),
|
|
103
|
+
|
|
104
|
+
/**
|
|
105
|
+
* What happens when this zone's last content is dismissed (stack empty, last tab closed).
|
|
106
|
+
* - `ZoneEmptyBehavior.COLLAPSE` (default): zone hides, adjacent zones expand to fill.
|
|
107
|
+
* - `ZoneEmptyBehavior.EMPTY_STATE`: zone stays visible with placeholder ("Select an item to view details").
|
|
108
|
+
* Only meaningful for secondary and companion zones. Primary never empties.
|
|
109
|
+
*/
|
|
110
|
+
onEmpty: z.enum(ZoneEmptyBehavior).optional(),
|
|
111
|
+
|
|
112
|
+
/**
|
|
113
|
+
* Responsive collapse rules: what happens when viewport shrinks below the zone's breakpoint.
|
|
114
|
+
* Accepts a plain `ResponsiveCollapseMode` (all breakpoints) or viewport-discriminated object.
|
|
115
|
+
* Only meaningful for secondary and companion zones. Primary never collapses.
|
|
116
|
+
*
|
|
117
|
+
* When viewport grows back past the breakpoint, collapsed content migrates back
|
|
118
|
+
* to its original zone (content is preserved).
|
|
119
|
+
*
|
|
120
|
+
* @example
|
|
121
|
+
* responsiveCollapse: ResponsiveCollapseMode.PUSH // always push into primary
|
|
122
|
+
* responsiveCollapse: { [ViewportBreakpoint.VERT_TABLET]: ResponsiveCollapseMode.PUSH, [ViewportBreakpoint.MOBILE]: ResponsiveCollapseMode.OVERLAY } // tablet: push, mobile: overlay
|
|
123
|
+
*/
|
|
124
|
+
responsiveCollapse: viewportDiscriminatedSchema(z.enum(ResponsiveCollapseMode)).optional(),
|
|
125
|
+
});
|
|
126
|
+
export type ZoneConfig = z.infer<typeof ZoneConfigSchema>;
|
|
127
|
+
```
|
|
@@ -42,9 +42,10 @@ export const BUILTIN_PROVIDER_CAPABILITY = {
|
|
|
42
42
|
* a read of a PDF's existing text layer. Maps to `EngineCapability.AI_DOCUMENT_EXTRACTION`.
|
|
43
43
|
*
|
|
44
44
|
* A NEW token was genuinely required rather than convenient: `IMAGE_GENERATION` is an OUTPUT
|
|
45
|
-
* capability (text → image), and `
|
|
46
|
-
*
|
|
47
|
-
*
|
|
45
|
+
* capability (text → image), and PDF *generation* — the `pdfTemplates` surface — is this
|
|
46
|
+
* capability's exact opposite. Nothing in the existing vocabulary claimed the document-INPUT
|
|
47
|
+
* slot. (This paragraph used to name `EngineCapability.DOCUMENT_GENERATION`; that member was
|
|
48
|
+
* withdrawn because no provider capability could fill it.)
|
|
48
49
|
*
|
|
49
50
|
* Distinct from `LLM_CHAT` even where a vendor serves both from one API key: the work is
|
|
50
51
|
* different (a page-layout model, billed per page, with no sampling parameters), and fusing
|
package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md
ADDED
|
@@ -0,0 +1,42 @@
|
|
|
1
|
+
# saas.models.resource-config.operation-variant-client-timeout
|
|
2
|
+
|
|
3
|
+
## Import Origins
|
|
4
|
+
|
|
5
|
+
- `@wildo-ai/saas-models`
|
|
6
|
+
|
|
7
|
+
## Source Excerpts
|
|
8
|
+
|
|
9
|
+
### Origin Package: `@wildo-ai/saas-models`
|
|
10
|
+
|
|
11
|
+
```typescript
|
|
12
|
+
*
|
|
13
|
+
* Frontend HTTP timeout for THIS variant, in milliseconds — declare it on any operation whose
|
|
14
|
+
* synchronous round trip legitimately outlives the frontend client's 30-second default (an
|
|
15
|
+
* operation that calls a model and waits for the answer, a long import, a blocking generation).
|
|
16
|
+
*
|
|
17
|
+
* The frontend resources client applies it as the per-request timeout on every dispatch shape
|
|
18
|
+
* (api-call, api-call-with-callback, search). An explicit caller-supplied
|
|
19
|
+
* `RequestOptions.timeout` still wins; omitting the field keeps the client default.
|
|
20
|
+
*
|
|
21
|
+
* Why it matters: without it, a long-running operation's request is aborted CLIENT-side while
|
|
22
|
+
* the server work succeeds — the caller renders a network error, and the operation-success
|
|
23
|
+
* refresh chain never fires, so lists keep showing the pre-operation world. Declare the
|
|
24
|
+
* expectation on the variant (the operation knows it is long-running); do not hard-code
|
|
25
|
+
* timeouts in consumer hooks, which duplicates that knowledge at every call site.
|
|
26
|
+
*
|
|
27
|
+
* This is a TRANSPORT expectation only — not a UI/observability signal (that is `riskLevel`)
|
|
28
|
+
* and not a server-side bound: the backend is free to answer sooner or be cut off by its own
|
|
29
|
+
* limits.
|
|
30
|
+
*
|
|
31
|
+
* @example a custom operation that generates a document before answering
|
|
32
|
+
* variants: [{
|
|
33
|
+
* variantType: ResourceOperationVariantType.API_CALL,
|
|
34
|
+
* roles: [CORE_ORG_ROLES.ORG_MEMBER],
|
|
35
|
+
* riskLevel: ResourceOperationRiskLevel.MEDIUM,
|
|
36
|
+
* clientRequestTimeoutMs: 300_000, // five minutes — the generation is synchronous
|
|
37
|
+
* requestDto: GenerateReportRequest_Schema,
|
|
38
|
+
* customResponseDto: GenerateReportOutcome_Schema,
|
|
39
|
+
* }]
|
|
40
|
+
*/
|
|
41
|
+
clientRequestTimeoutMs?: number;
|
|
42
|
+
```
|
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
# saas.specifications.application-authored-document-fact-specification.contract
|
|
2
|
+
|
|
3
|
+
## Import Origins
|
|
4
|
+
|
|
5
|
+
- `@wildo-ai/saas-specifications`
|
|
6
|
+
|
|
7
|
+
## Source Excerpts
|
|
8
|
+
|
|
9
|
+
### Origin Package: `@wildo-ai/saas-specifications`
|
|
10
|
+
|
|
11
|
+
```typescript
|
|
12
|
+
*
|
|
13
|
+
* Accepted application declaration of governed-document facts ONLY A HUMAN MAY ESTABLISH — a creator's
|
|
14
|
+
* decision, or a qualified review. Import from
|
|
15
|
+
* `@wildo-ai/saas-specifications/application-creation`.
|
|
16
|
+
*
|
|
17
|
+
* Structurally identical to {@link ApplicationDocumentFactSpecificationSchema}: a declaration is a
|
|
18
|
+
* declaration whoever wrote it, and a document reading facts does not care which file one came from.
|
|
19
|
+
* The two are separate FAMILIES so that neither writer can destroy the other's half — the derived file
|
|
20
|
+
* is regenerated by a producer, this one is only ever edited by a person or by a host acting on a
|
|
21
|
+
* person's answers.
|
|
22
|
+
*
|
|
23
|
+
* Nothing in here may carry `APPLICATION_SPECIFICATION` authority. A fact the specification can answer
|
|
24
|
+
* belongs in the derived family, where it is re-derived when the specification moves; pinning it here
|
|
25
|
+
* would freeze yesterday's answer under a human's name.
|
|
26
|
+
*/
|
|
27
|
+
export const ApplicationAuthoredDocumentFactSpecificationSchema = buildDocumentFactSpecificationSchema(ApplicationAuthoredDocumentFactDeclarationSchema);
|
|
28
|
+
export type ApplicationAuthoredDocumentFactSpecification = z.infer<typeof ApplicationAuthoredDocumentFactSpecificationSchema>;
|
|
29
|
+
```
|
|
@@ -10,9 +10,8 @@
|
|
|
10
10
|
|
|
11
11
|
```typescript
|
|
12
12
|
*
|
|
13
|
-
* Accepted application declaration of governed-document facts
|
|
14
|
-
*
|
|
15
|
-
* `@wildo-ai/saas-specifications/application-creation`.
|
|
13
|
+
* Accepted application declaration of governed-document facts THE ACCEPTED SPECIFICATION ANSWERS.
|
|
14
|
+
* Import from `@wildo-ai/saas-specifications/application-creation`.
|
|
16
15
|
*
|
|
17
16
|
* This family carries raw decisions only. It never authors contribution
|
|
18
17
|
* digests, accepted-head identities, validation receipts, reviewer grants,
|
|
@@ -26,34 +25,15 @@
|
|
|
26
25
|
* scope. Replacing a decision requires a new declaration/specification version
|
|
27
26
|
* and normal specification-family acceptance; conflicting current values are
|
|
28
27
|
* rejected at the authoring boundary instead of being hidden downstream.
|
|
28
|
+
*
|
|
29
|
+
* ## This file is REGENERATED, and that is why it accepts one authority kind
|
|
30
|
+
*
|
|
31
|
+
* `refinement.document-facts` rewrites it whole. Before #192 the same file also held the facts only a
|
|
32
|
+
* human may establish, so the next producer run silently deleted them — and there was no compare-and-
|
|
33
|
+
* swap to notice, by design (`.claude/rules/one-source-of-truth.md` Rule 0). The facts a human owns
|
|
34
|
+
* live in {@link ApplicationAuthoredDocumentFactSpecificationSchema}, in their own file, which no
|
|
35
|
+
* producer writes.
|
|
29
36
|
*/
|
|
30
|
-
export const ApplicationDocumentFactSpecificationSchema =
|
|
31
|
-
.strictObject({
|
|
32
|
-
schemaVersion: z.literal(1),
|
|
33
|
-
specificationRef: AuthoredNamespacedRefSchema,
|
|
34
|
-
specificationVersion: GovernedDocumentPositiveSafeIntegerSchema,
|
|
35
|
-
declarations: z.array(ApplicationDocumentFactDeclarationSchema).min(1),
|
|
36
|
-
})
|
|
37
|
-
.superRefine((specification, context) => {
|
|
38
|
-
if (!specification.specificationRef.startsWith("document-fact-specification:")) {
|
|
39
|
-
context.addIssue({
|
|
40
|
-
code: "custom",
|
|
41
|
-
message: "specificationRef must use the document-fact-specification: namespace",
|
|
42
|
-
path: ["specificationRef"],
|
|
43
|
-
});
|
|
44
|
-
}
|
|
45
|
-
const declarationIdentities = specification.declarations.map((declaration) => `${declaration.declarationRef}@${declaration.declarationVersion}`);
|
|
46
|
-
if (!valuesAreUnique(declarationIdentities) || !valuesAreLexicallySorted(declarationIdentities)) {
|
|
47
|
-
context.addIssue({ code: "custom", message: "declarations must be unique and lexically sorted by identity", path: ["declarations"] });
|
|
48
|
-
}
|
|
49
|
-
const factScopeKeys = specification.declarations.map(applicationDocumentFactDeclarationScopeKey);
|
|
50
|
-
if (!valuesAreUnique(factScopeKeys)) {
|
|
51
|
-
context.addIssue({
|
|
52
|
-
code: "custom",
|
|
53
|
-
message: "a specification may declare only one current value for each fact version and governance scope",
|
|
54
|
-
path: ["declarations"],
|
|
55
|
-
});
|
|
56
|
-
}
|
|
57
|
-
});
|
|
37
|
+
export const ApplicationDocumentFactSpecificationSchema = buildDocumentFactSpecificationSchema(ApplicationDerivedDocumentFactDeclarationSchema);
|
|
58
38
|
export type ApplicationDocumentFactSpecification = z.infer<typeof ApplicationDocumentFactSpecificationSchema>;
|
|
59
39
|
```
|
package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md
CHANGED
|
@@ -1039,7 +1039,28 @@ const AssuranceDocumentAuthorityCatalogV2BaseSchema = AssuranceDocumentAuthority
|
|
|
1039
1039
|
});
|
|
1040
1040
|
const AssuranceDocumentAuthorityCatalogV2Schema = AssuranceDocumentAuthorityCatalogV2BaseSchema.superRefine(refineAssuranceDocumentAuthorityCatalogBlueprints);
|
|
1041
1041
|
|
|
1042
|
-
/**
|
|
1042
|
+
/**
|
|
1043
|
+
* Blueprint v2 plus a closed, exactly consumed structured-value-contract registry.
|
|
1044
|
+
*
|
|
1045
|
+
* ASPIRATIONAL, by decision — 2026-08-31, issue #148. The shape is designed, refined and tested, and
|
|
1046
|
+
* it has no instance and no consumer. Measured on that date, `structuredValueContracts` and
|
|
1047
|
+
* `annexBindings` appear in exactly two files: this one, and `assurance-document-structured-contract.schemas.test.ts`.
|
|
1048
|
+
* There is no producer, no reader, and no implementation behind
|
|
1049
|
+
* `AssuranceDocumentStructuredContentProcessorIdentitySchema` — nothing consumes an annex-bound
|
|
1050
|
+
* structured value. `AssuranceDocumentAuthorityCatalogV3Schema` itself is referenced twice, both in
|
|
1051
|
+
* this file: its declaration and the union member below.
|
|
1052
|
+
*
|
|
1053
|
+
* So moving the engine's six document definitions to v3 would mean authoring structured value
|
|
1054
|
+
* contracts that nothing reads, which `.claude/rules/application-creation-directive.md` forbids in
|
|
1055
|
+
* as many words: "If we write a log or record, something or someone actually reads it — otherwise we
|
|
1056
|
+
* do not write it." The migration was rejected on that ground, NOT on effort.
|
|
1057
|
+
*
|
|
1058
|
+
* WHAT WOULD CHANGE THE DECISION: a consumer for annex-bound structured values — something that
|
|
1059
|
+
* renders or validates a document annex from a `structuredValueContract` (a processor register or a
|
|
1060
|
+
* retention schedule as a machine-readable table rather than prose). Build that first; the catalog
|
|
1061
|
+
* migration is then mechanical and worth doing. Until then v2/catalogVersion 5 is the current, correct
|
|
1062
|
+
* and fully-refined shape, and v3 stays available for the author who has that consumer.
|
|
1063
|
+
*/
|
|
1043
1064
|
export const AssuranceDocumentAuthorityCatalogV3Schema = AssuranceDocumentAuthorityCatalogCommonSchema.extend({
|
|
1044
1065
|
schemaVersion: z.literal(3),
|
|
1045
1066
|
catalogVersion: z.literal(6),
|
|
@@ -1103,7 +1124,16 @@ export const AssuranceDocumentAuthorityCatalogV3Schema = AssuranceDocumentAuthor
|
|
|
1103
1124
|
}
|
|
1104
1125
|
});
|
|
1105
1126
|
|
|
1106
|
-
/**
|
|
1127
|
+
/**
|
|
1128
|
+
* All three versions are ACCEPTED for authoring. v3 is available, not mandated — see the note on
|
|
1129
|
+
* `AssuranceDocumentAuthorityCatalogV3Schema`.
|
|
1130
|
+
*
|
|
1131
|
+
* This comment used to read "Retained v1/v2 catalogs remain parse-only; every newly authored catalog
|
|
1132
|
+
* uses v3/catalogVersion 6." That was false in the only way that mattered: the repository's one
|
|
1133
|
+
* catalog — `createInitialAssuranceDocumentAuthorityCatalog()` — is v2/catalogVersion 5, so the
|
|
1134
|
+
* sentence declared the sole live instance non-authorable. A builder who read it, opened the catalog
|
|
1135
|
+
* and found v2 had no way to tell a stale document from a stale catalog (issue #148).
|
|
1136
|
+
*/
|
|
1107
1137
|
export const AssuranceDocumentAuthorityCatalogSchema = z.discriminatedUnion("schemaVersion", [
|
|
1108
1138
|
AssuranceDocumentAuthorityCatalogV1Schema,
|
|
1109
1139
|
AssuranceDocumentAuthorityCatalogV2Schema,
|
|
@@ -695,7 +695,13 @@ export const AssuranceProgramObligationEntrySchema = z
|
|
|
695
695
|
});
|
|
696
696
|
export type AssuranceProgramObligationEntry = z.infer<typeof AssuranceProgramObligationEntrySchema>;
|
|
697
697
|
|
|
698
|
-
/**
|
|
698
|
+
/**
|
|
699
|
+
* Complete application obligation inventory. It is not the governed-document release register.
|
|
700
|
+
*
|
|
701
|
+
* It carried a digest until the Phase-A demolition (`.claude/rules/one-source-of-truth.md` Rule 0) and the JSDoc went on calling it "content-addressed" afterwards. The
|
|
702
|
+
* strict shape below is the whole truth: a ref, a version and the entries. Completeness is proven by `obligationCoverageDecisions` and the uniqueness refinement, not
|
|
703
|
+
* by a hash. A test still named `registerWithoutDigest` is a leftover from when the field existed.
|
|
704
|
+
*/
|
|
699
705
|
export const AssuranceProgramObligationRegisterSchema = z
|
|
700
706
|
.strictObject({
|
|
701
707
|
schemaVersion: z.literal(1),
|
|
@@ -1213,7 +1219,16 @@ const AssuranceProgramV3CommonFieldsSchema = z.strictObject({
|
|
|
1213
1219
|
...AssuranceProgramCommonFieldsAfterObjectiveBindingsSchema.shape,
|
|
1214
1220
|
});
|
|
1215
1221
|
|
|
1216
|
-
/**
|
|
1222
|
+
/**
|
|
1223
|
+
* Historical source-revision-pinned program. Retained payloads remain parseable and replayable.
|
|
1224
|
+
*
|
|
1225
|
+
* This said "new authoring is forbidden by the repository pin checker" until 2026-09-01. **Nothing forbids it.** That checker was
|
|
1226
|
+
* `pnpm check:assurance-revision-pin`, removed on 2026-08-27 with the rest of the digest mechanism, and no successor exists — the
|
|
1227
|
+
* only assurance check in `package.json` is `check:assurance-control-boundary`, which is about marker source-neutrality.
|
|
1228
|
+
*
|
|
1229
|
+
* So v1 is discouraged by this comment and by nothing else. A safety claim standing on a removed mechanism is worse than no claim,
|
|
1230
|
+
* because a reader stops looking for the guard. Building one is #221; until it lands, "forbidden" means "please do not".
|
|
1231
|
+
*/
|
|
1217
1232
|
export const AssuranceProgramSpecificationV1Schema = z
|
|
1218
1233
|
.strictObject({
|
|
1219
1234
|
schemaVersion: z.literal(1),
|
|
@@ -1231,9 +1246,17 @@ export type AssuranceProgramSpecificationV1 = z.infer<typeof AssuranceProgramSpe
|
|
|
1231
1246
|
*
|
|
1232
1247
|
* Validation authorities currently carry one sealed basis snapshot. Accepting several authored bases would make
|
|
1233
1248
|
* every extra basis compare against the wrong inventory and could misclassify an unverified authority as tolerable
|
|
1234
|
-
* host drift. Multi-basis composition therefore requires a later schema version with basis-indexed snapshots.
|
|
1235
|
-
*
|
|
1236
|
-
*
|
|
1249
|
+
* host drift. Multi-basis composition therefore requires a later schema version with basis-indexed snapshots.
|
|
1250
|
+
*
|
|
1251
|
+
* This claimed a "repository checker" recognized v2 authoring "only through the serialized pre-v3 transition" until
|
|
1252
|
+
* 2026-09-01. There is no such checker — see the note on {@link AssuranceProgramSpecificationV1Schema}. The intent
|
|
1253
|
+
* stands and is worth keeping: after an application accepts v3, v2 should remain replayable rather than become a
|
|
1254
|
+
* second current authoring shape. It is an intent, not an enforced one (#221).
|
|
1255
|
+
*
|
|
1256
|
+
* Exactly one v2 programme exists today, `examples/your-app`, and it is the only assurance programme in the
|
|
1257
|
+
* repository. (`examples/wonder-crm/specifications/src/compliance/index.ts` is a PROCESSOR REGISTER, not a
|
|
1258
|
+
* programme — its `schemaVersion: 1` belongs to `ApplicationProcessorRegisterSchema`, and a grep for the first
|
|
1259
|
+
* `schemaVersion` in a file named `compliance/` reads it as a v1 programme.)
|
|
1237
1260
|
*/
|
|
1238
1261
|
export const AssuranceProgramSpecificationV2Schema = z
|
|
1239
1262
|
.strictObject({
|
|
@@ -1249,7 +1272,7 @@ export type AssuranceProgramSpecificationV2 = z.infer<typeof AssuranceProgramSpe
|
|
|
1249
1272
|
|
|
1250
1273
|
/**
|
|
1251
1274
|
* Current application program. It preserves the v2 single-basis authority model while replacing the overlapping
|
|
1252
|
-
* control-objective-binding array with one complete
|
|
1275
|
+
* control-objective-binding array with one complete obligation register and its program-owned review
|
|
1253
1276
|
* records. Activation and operating/evidence truth remain deliberately unrepresentable.
|
|
1254
1277
|
*/
|
|
1255
1278
|
export const AssuranceProgramSpecificationV3Schema = z
|
|
@@ -87,6 +87,9 @@ export interface SpecificationsCompanionExports<
|
|
|
87
87
|
// a partial register is useful and its holes are REPORTED per provider against
|
|
88
88
|
// the application's configured set, rather than blocking anything.
|
|
89
89
|
TProcessorRegister = ApplicationProcessorRegister,
|
|
90
|
+
// Appended STRICTLY LAST: the human half of the document facts, in its own
|
|
91
|
+
// family, because the derived one is REGENERATED whole (#192).
|
|
92
|
+
TAuthoredDocumentFactSpecification = ApplicationAuthoredDocumentFactSpecification,
|
|
90
93
|
> {
|
|
91
94
|
resourceSpecifications: TResourceSpecifications;
|
|
92
95
|
applicationBusinessSemanticsSnapshot?: TBusinessSemanticsSnapshot;
|
|
@@ -471,6 +474,23 @@ export interface SpecificationsCompanionExports<
|
|
|
471
474
|
* Omitting it is honest: unresolved document facts remain visible gaps.
|
|
472
475
|
*/
|
|
473
476
|
documentFactSpecification?: TDocumentFactSpecification;
|
|
477
|
+
/**
|
|
478
|
+
* Accepted application governed-document facts **only a human may establish** — a creator decision
|
|
479
|
+
* or a qualified review (`document-facts-authored`).
|
|
480
|
+
*
|
|
481
|
+
* The same shape as the slot above, and a separate family on purpose. `refinement.document-facts`
|
|
482
|
+
* rewrites the derived file whole, so a human decision sharing that file is destroyed on the next
|
|
483
|
+
* run with nothing to notice: there is no compare-and-swap here, deliberately
|
|
484
|
+
* (`.claude/rules/one-source-of-truth.md` Rule 0). Two families put the two writers out of each
|
|
485
|
+
* other's reach.
|
|
486
|
+
*
|
|
487
|
+
* No producer may write this family — it has no generation contract, and that absence is the design
|
|
488
|
+
* rather than an omission.
|
|
489
|
+
*
|
|
490
|
+
* A reader wanting "the application's facts" needs BOTH slots. `collectComplianceDocumentFactAvailability`
|
|
491
|
+
* is variadic for exactly that reason.
|
|
492
|
+
*/
|
|
493
|
+
authoredDocumentFactSpecification?: TAuthoredDocumentFactSpecification;
|
|
474
494
|
/**
|
|
475
495
|
* WHO else processes this application's personal data — legal identity, processing region and the
|
|
476
496
|
* processor's own subprocessors (issue #88).
|
|
@@ -71,6 +71,28 @@ export type ResourceSpecificationConfig<
|
|
|
71
71
|
businessRole: string;
|
|
72
72
|
/** How the resource evolves over time (lifecycle semantics). */
|
|
73
73
|
lifecycleRole?: string;
|
|
74
|
+
/**
|
|
75
|
+
* Which part of the product this resource belongs to, WITHIN its owner.
|
|
76
|
+
*
|
|
77
|
+
* A second grouping axis under the one that already exists. An application's resources are grouped
|
|
78
|
+
* by the module that registers them; the engine's are grouped by nothing, so every surface that
|
|
79
|
+
* has to present them — the domain-model graph, `wildo context`, generated documentation, an
|
|
80
|
+
* application-creation playbook — meets one flat set of 85 and either shows it undifferentiated or
|
|
81
|
+
* invents a grouping of its own and drifts from the next surface that does the same.
|
|
82
|
+
*
|
|
83
|
+
* Typed `string` and OPEN on purpose. The engine's values are a closed vocabulary with a named
|
|
84
|
+
* runtime source, {@link EngineResourceSubDomain} in this package's `engine` surface, and engine
|
|
85
|
+
* specs must use it. An application's sub-domains are its own — this repository cannot enumerate
|
|
86
|
+
* a vocabulary it does not own, and a union that tried would refuse every real application.
|
|
87
|
+
*
|
|
88
|
+
* Optional, and its absence means exactly "unclassified" rather than "belongs to a default". A
|
|
89
|
+
* consumer grouping by it must carry a bucket for that and say so; silently folding unclassified
|
|
90
|
+
* rows into a real group is how a grouping starts lying.
|
|
91
|
+
*
|
|
92
|
+
* Distinct from {@link ResourceSpecificationConfig.resourcePrimaryScope}, which answers WHO a row
|
|
93
|
+
* belongs to. This answers what it is ABOUT, and one sub-domain spans several scopes.
|
|
94
|
+
*/
|
|
95
|
+
subDomain?: string;
|
|
74
96
|
/**
|
|
75
97
|
* Intended READER of this resource's generated labels — the register the label
|
|
76
98
|
* generator should adopt: {@link LabelAudience.END_USER} for consumer surfaces
|
|
@@ -80,6 +80,12 @@ export const StringDisplayMode = {
|
|
|
80
80
|
* `TEXTAREA` — the edit side stays markdown SOURCE either way.
|
|
81
81
|
*/
|
|
82
82
|
MARKDOWN: 'markdown',
|
|
83
|
+
/**
|
|
84
|
+
* A MACHINE IDENTIFIER — a slug, a ref, an addressable key (`success-criterion-…`). Rendered
|
|
85
|
+
* small, muted and monospace so it stays greppable and verbatim while RECEDING behind the prose
|
|
86
|
+
* it identifies. Use for values a reader needs to copy or trace, never to read as content.
|
|
87
|
+
*/
|
|
88
|
+
IDENTIFIER: 'identifier',
|
|
83
89
|
COLOR: 'color',
|
|
84
90
|
LINK: 'link',
|
|
85
91
|
EMAIL: 'email',
|
|
@@ -82,15 +82,34 @@ export enum CodeDeclarationKind {
|
|
|
82
82
|
}
|
|
83
83
|
|
|
84
84
|
/**
|
|
85
|
-
*
|
|
85
|
+
* Symbol reference used by semantic specifications to address one exported symbol.
|
|
86
86
|
*
|
|
87
|
-
* Downstream transposers
|
|
88
|
-
*
|
|
87
|
+
* Downstream transposers and prompts prefer these refs over file-path guesses, so a
|
|
88
|
+
* ref has to be honest about WHICH KIND of address it carries. Two facts are useful
|
|
89
|
+
* and they are not the same fact, so they have separate fields:
|
|
90
|
+
*
|
|
91
|
+
* - `importPath` is an IMPORT SPECIFIER — something a generated `import` statement
|
|
92
|
+
* can actually resolve, declared in the owning package's `package.json#exports`.
|
|
93
|
+
* - `filePathHint` is a LOCATION — where a maintainer opens the file. It is never
|
|
94
|
+
* rendered as something importable.
|
|
95
|
+
*
|
|
96
|
+
* Authoring a source path in `importPath` is the defect issue #150 records: it made
|
|
97
|
+
* the companion hand a coding agent an import specifier that cannot resolve, because
|
|
98
|
+
* an application package typically declares no export map entry for its internal
|
|
99
|
+
* modules. When in doubt, author `filePathHint` — a location that is merely useful
|
|
100
|
+
* is better than an address that is wrong.
|
|
89
101
|
*/
|
|
90
102
|
export interface CodeSymbolRef {
|
|
91
103
|
/** Package name to import from (for example `@wildo-ai/saas-models`). */
|
|
92
104
|
packageName: string;
|
|
93
|
-
/**
|
|
105
|
+
/**
|
|
106
|
+
* Optional PUBLIC SUBPATH, when the package root is not the import target.
|
|
107
|
+
*
|
|
108
|
+
* Must be a subpath the owning package declares in `package.json#exports`, so that
|
|
109
|
+
* `${packageName}/${importPath}` is a resolvable import specifier. If the symbol has
|
|
110
|
+
* no public door, leave this unset and author `filePathHint` instead — do NOT put a
|
|
111
|
+
* path inside `src/` here.
|
|
112
|
+
*/
|
|
94
113
|
importPath?: string;
|
|
95
114
|
/** Literal exported symbol name. */
|
|
96
115
|
exportName: string;
|
|
@@ -98,7 +117,14 @@ export interface CodeSymbolRef {
|
|
|
98
117
|
symbolKind: CodeSymbolKind;
|
|
99
118
|
/** More specific declaration family for code-generation handling. */
|
|
100
119
|
declarationKind?: CodeDeclarationKind;
|
|
101
|
-
/**
|
|
120
|
+
/**
|
|
121
|
+
* Optional MODULE LOCATION — where the symbol is defined inside the owning package,
|
|
122
|
+
* relative to that package's source root (for example
|
|
123
|
+
* `modules/tasks-manager/resources/tasks/tasks.ui-behavior`).
|
|
124
|
+
*
|
|
125
|
+
* This is a navigation aid, not an import target: it is rendered as a location and
|
|
126
|
+
* must never be concatenated onto `packageName` to build an import specifier.
|
|
127
|
+
*/
|
|
102
128
|
filePathHint?: string;
|
|
103
129
|
/** Extra caveats or usage notes for downstream prompts. */
|
|
104
130
|
notes?: string[];
|
|
@@ -352,11 +352,42 @@ export interface ForeignKeyUIParams {
|
|
|
352
352
|
// ARRAY UI
|
|
353
353
|
//------------------------------------------------------------------------------------------------
|
|
354
354
|
|
|
355
|
+
/**
|
|
356
|
+
* List marker treatment for a PRIMITIVE array's display items.
|
|
357
|
+
*
|
|
358
|
+
* Its own enum rather than a new `DisplayDirection` member on purpose: direction answers "which
|
|
359
|
+
* axis do items flow on", marker style answers "does each item announce itself as one of several" —
|
|
360
|
+
* merging them would make `BULLETS × horizontal` an unrepresentable-but-meaningful combination and
|
|
361
|
+
* overload an enum that alignment code also reads.
|
|
362
|
+
*/
|
|
363
|
+
export enum ArrayListStyle {
|
|
364
|
+
/** Bare stacked values — the historical default. */
|
|
365
|
+
PLAIN = 'plain',
|
|
366
|
+
/** A real bulleted list. For enumerations a reader SCANS — alternatives, consequences, principles — where bare stacked lines read as one run-on paragraph. */
|
|
367
|
+
BULLETS = 'bullets',
|
|
368
|
+
/**
|
|
369
|
+
* A RULED list: one hairline between entries, none above the first or below the last.
|
|
370
|
+
*
|
|
371
|
+
* For OBJECT entries a reader compares — an ICP after an ICP, a persona after a persona — where
|
|
372
|
+
* spacing alone stops saying where one ends. It is the alternative to framing each entry as a
|
|
373
|
+
* card, and the reason to prefer it is compounding chrome: inside a section that is already a
|
|
374
|
+
* bounded region, a card per entry is a third frame around content that has two. Unlike
|
|
375
|
+
* {@link ArrayListStyle.BULLETS}, which is for primitive lines, this is for entries.
|
|
376
|
+
*/
|
|
377
|
+
SEPARATED = 'separated',
|
|
378
|
+
}
|
|
379
|
+
|
|
355
380
|
export interface ArrayUIDisplayParams extends PrimitiveUIBaseDisplayParams {
|
|
356
381
|
/** Direction for rendering items in display context. */
|
|
357
382
|
displayMode?: DisplayDirection;
|
|
358
383
|
/** Max items shown in display (rest truncated). */
|
|
359
384
|
maxItems?: number;
|
|
385
|
+
/**
|
|
386
|
+
* Marker treatment for PRIMITIVE items (see {@link ArrayListStyle}). No effect on object arrays —
|
|
387
|
+
* their items are cards/rows, not list lines — and no effect on horizontal flow, where markers
|
|
388
|
+
* have no line to anchor to.
|
|
389
|
+
*/
|
|
390
|
+
listStyle?: ArrayListStyle;
|
|
360
391
|
}
|
|
361
392
|
|
|
362
393
|
/**
|
|
@@ -447,6 +478,18 @@ export interface ObjectUIDisplayParams extends PrimitiveUIBaseDisplayParams {
|
|
|
447
478
|
displayMode?: DisplayDirection;
|
|
448
479
|
/** Max properties shown in display (rest truncated). */
|
|
449
480
|
maxItems?: number;
|
|
481
|
+
/**
|
|
482
|
+
* The member that IS this object's headline when the object renders as a unit (a nested object
|
|
483
|
+
* block, an array item card): it renders FIRST, label hidden, with title emphasis; the remaining
|
|
484
|
+
* members follow in schema order.
|
|
485
|
+
*
|
|
486
|
+
* Explicit rather than detected: "the first string field" guesses wrong the moment a stable
|
|
487
|
+
* identifier precedes the human statement in the schema — exactly the shape ref-addressable
|
|
488
|
+
* entries have (`ref` first, `statement` second), where detection would headline the machine key.
|
|
489
|
+
* Names a member that does not exist → ignored, so a schema rename degrades to the old uniform
|
|
490
|
+
* rendering instead of crashing the display.
|
|
491
|
+
*/
|
|
492
|
+
primaryField?: string;
|
|
450
493
|
}
|
|
451
494
|
|
|
452
495
|
export type ObjectUIEditParams = PrimitiveUIBaseEditParams;
|
|
@@ -20,6 +20,9 @@ export interface PrimitiveUIBaseDisplayParams {
|
|
|
20
20
|
/** Chrome layout mode for the field wrapper in display context. */
|
|
21
21
|
chromeMode?: ResponsiveAware<DisplayChromeMode>;
|
|
22
22
|
|
|
23
|
+
/** Label styling, orthogonal to `chromeMode` (which decides LAYOUT). See `DisplayLabelStyle`. */
|
|
24
|
+
labelStyle?: DisplayLabelStyle;
|
|
25
|
+
|
|
23
26
|
/** Force-hide specific chrome sub-elements in display context. Plain object = all breakpoints. */
|
|
24
27
|
forceHide?: ResponsiveAware<ForceHideDisplayConfig>;
|
|
25
28
|
|
|
@@ -39,6 +39,21 @@ export interface ForeignKeyStructuralParams {
|
|
|
39
39
|
* (e.g. `referrerScopeType`). Without it, `polymorphicVariants` is rename-only.
|
|
40
40
|
*/
|
|
41
41
|
polymorphicDiscriminatorField?: string;
|
|
42
|
+
/**
|
|
43
|
+
* EXPLICIT target resource type, for an FK whose FIELD NAME cannot resolve it.
|
|
44
|
+
*
|
|
45
|
+
* The frontend resolves a reference field's target through the field-name → resource map
|
|
46
|
+
* (enriched from relationships' `foreignKeyField`). That works only when the field is named for
|
|
47
|
+
* its target (`assignedToUserId`) or a relationship declares it — and relationship FK names are
|
|
48
|
+
* held to the `Id`/`Ids` convention. A field that references a resource under its OWN vocabulary
|
|
49
|
+
* (`icpRefs` inside a specification document, a rename-only FK) has no honest entry in that map;
|
|
50
|
+
* declaring the target here lets the reference display resolve, label and navigate it without
|
|
51
|
+
* bending the field's name or the map's uniqueness.
|
|
52
|
+
*
|
|
53
|
+
* Takes precedence over the field-name map; polymorphic variants (above) still win over both,
|
|
54
|
+
* because a per-record discriminator is more specific than any static declaration.
|
|
55
|
+
*/
|
|
56
|
+
referencedResourceType?: string;
|
|
42
57
|
}
|
|
43
58
|
```
|
|
44
59
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "assurance-authority-bases",
|
|
3
3
|
"metadata": {
|
|
4
|
-
"generatedAt": "2026-
|
|
4
|
+
"generatedAt": "2026-09-05T12:54:53.265Z",
|
|
5
5
|
"description": "Compiled portable assurance-authority bases."
|
|
6
6
|
},
|
|
7
7
|
"entries": {
|
|
@@ -9,7 +9,8 @@
|
|
|
9
9
|
"ref": "assurance-authority-basis:wildo-safe-baseline-v1",
|
|
10
10
|
"version": 1,
|
|
11
11
|
"sourceRevisionRef": "source-revision:wildo-engine-assurance-safe-baseline-v1",
|
|
12
|
-
"filePath": "assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json"
|
|
12
|
+
"filePath": "assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json",
|
|
13
|
+
"externalFrameworkMappingFilePath": "assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json"
|
|
13
14
|
}
|
|
14
15
|
}
|
|
15
16
|
}
|