@wildo-ai/saas-specifications 1.1.3 → 1.1.5
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/assurance/external-framework-mapping.json +1228 -0
- package/dist/esm/_core/application-maturity/application-maturity-validation.d.ts +34 -0
- package/dist/esm/_core/application-maturity/application-maturity-validation.d.ts.map +1 -0
- package/dist/esm/_core/application-maturity/application-maturity-validation.js +66 -0
- package/dist/esm/_core/application-maturity/application-maturity-validation.js.map +1 -0
- package/dist/esm/_core/application-maturity/application-maturity.family-aspects.d.ts +3 -0
- package/dist/esm/_core/application-maturity/application-maturity.family-aspects.d.ts.map +1 -0
- package/dist/esm/_core/application-maturity/application-maturity.family-aspects.js +48 -0
- package/dist/esm/_core/application-maturity/application-maturity.family-aspects.js.map +1 -0
- package/dist/esm/_core/application-maturity/application-maturity.schemas.d.ts +201 -0
- package/dist/esm/_core/application-maturity/application-maturity.schemas.d.ts.map +1 -0
- package/dist/esm/_core/application-maturity/application-maturity.schemas.js +306 -0
- package/dist/esm/_core/application-maturity/application-maturity.schemas.js.map +1 -0
- package/dist/esm/_core/application-specification-family-identity.schemas.d.ts +304 -0
- package/dist/esm/_core/application-specification-family-identity.schemas.d.ts.map +1 -0
- package/dist/esm/_core/application-specification-family-identity.schemas.js +314 -0
- package/dist/esm/_core/application-specification-family-identity.schemas.js.map +1 -0
- package/dist/esm/_core/assertions/assertion-authored-metadata.schemas.d.ts +2 -1
- package/dist/esm/_core/assertions/assertion-authored-metadata.schemas.d.ts.map +1 -1
- package/dist/esm/_core/assertions/assertion-authored-metadata.schemas.js +4 -1
- package/dist/esm/_core/assertions/assertion-authored-metadata.schemas.js.map +1 -1
- package/dist/esm/_core/assertions/assertion-behaviors.schemas.d.ts +4 -4
- package/dist/esm/_core/assertions/assertion-specification.schemas.d.ts +5 -4
- package/dist/esm/_core/assertions/assertion-specification.schemas.d.ts.map +1 -1
- package/dist/esm/_core/assertions/assertion-specification.schemas.js +4 -1
- package/dist/esm/_core/assertions/assertion-specification.schemas.js.map +1 -1
- package/dist/esm/_core/brand/brand-asset.schemas.d.ts +5 -4
- package/dist/esm/_core/brand/brand-asset.schemas.d.ts.map +1 -1
- package/dist/esm/_core/brand/brand-asset.schemas.js +7 -4
- package/dist/esm/_core/brand/brand-asset.schemas.js.map +1 -1
- package/dist/esm/_core/brand/brand-audience.schemas.d.ts +31 -0
- package/dist/esm/_core/brand/brand-audience.schemas.d.ts.map +1 -0
- package/dist/esm/_core/brand/brand-audience.schemas.js +29 -0
- package/dist/esm/_core/brand/brand-audience.schemas.js.map +1 -0
- package/dist/esm/_core/brand/brand-authored-metadata.schemas.d.ts +3 -2
- package/dist/esm/_core/brand/brand-authored-metadata.schemas.d.ts.map +1 -1
- package/dist/esm/_core/brand/brand-authored-metadata.schemas.js +5 -2
- package/dist/esm/_core/brand/brand-authored-metadata.schemas.js.map +1 -1
- package/dist/esm/_core/brand/brand-generation.schemas.d.ts +4 -4
- package/dist/esm/_core/brand/brand-logo-direction.schemas.d.ts +12 -9
- package/dist/esm/_core/brand/brand-logo-direction.schemas.d.ts.map +1 -1
- package/dist/esm/_core/brand/brand-logo-direction.schemas.js +12 -7
- package/dist/esm/_core/brand/brand-logo-direction.schemas.js.map +1 -1
- package/dist/esm/_core/brand/brand-name.schemas.d.ts +2 -2
- package/dist/esm/_core/brand/brand-snapshot-validation.d.ts.map +1 -1
- package/dist/esm/_core/brand/brand-snapshot-validation.js +1 -8
- package/dist/esm/_core/brand/brand-snapshot-validation.js.map +1 -1
- package/dist/esm/_core/brand/brand-snapshot.schemas.d.ts +23 -12
- package/dist/esm/_core/brand/brand-snapshot.schemas.d.ts.map +1 -1
- package/dist/esm/_core/brand/brand-snapshot.schemas.js +7 -0
- package/dist/esm/_core/brand/brand-snapshot.schemas.js.map +1 -1
- package/dist/esm/_core/brand/brand-visual-tone.schemas.d.ts +2 -2
- package/dist/esm/_core/brand/brand.family-aspects.d.ts.map +1 -1
- package/dist/esm/_core/brand/brand.family-aspects.js +12 -1
- package/dist/esm/_core/brand/brand.family-aspects.js.map +1 -1
- package/dist/esm/_core/build-plan/build-plan-task-graph-generation.schemas.d.ts +252 -2
- package/dist/esm/_core/build-plan/build-plan-task-graph-generation.schemas.d.ts.map +1 -1
- package/dist/esm/_core/build-plan/build-plan-task-graph-generation.schemas.js +19 -1
- package/dist/esm/_core/build-plan/build-plan-task-graph-generation.schemas.js.map +1 -1
- package/dist/esm/_core/build-plan/build-plan-task-graph-validation.d.ts +121 -1
- package/dist/esm/_core/build-plan/build-plan-task-graph-validation.d.ts.map +1 -1
- package/dist/esm/_core/build-plan/build-plan-task-graph-validation.js +215 -2
- package/dist/esm/_core/build-plan/build-plan-task-graph-validation.js.map +1 -1
- package/dist/esm/_core/build-plan/build-plan-task-graph.schemas.d.ts +703 -14
- package/dist/esm/_core/build-plan/build-plan-task-graph.schemas.d.ts.map +1 -1
- package/dist/esm/_core/build-plan/build-plan-task-graph.schemas.js +536 -7
- package/dist/esm/_core/build-plan/build-plan-task-graph.schemas.js.map +1 -1
- package/dist/esm/_core/build-plan/build-plan.family-aspects.d.ts.map +1 -1
- package/dist/esm/_core/build-plan/build-plan.family-aspects.js +82 -2
- package/dist/esm/_core/build-plan/build-plan.family-aspects.js.map +1 -1
- package/dist/esm/_core/business-model-lite/business-model-authored-metadata.schemas.d.ts +3 -2
- package/dist/esm/_core/business-model-lite/business-model-authored-metadata.schemas.d.ts.map +1 -1
- package/dist/esm/_core/business-model-lite/business-model-authored-metadata.schemas.js +5 -2
- package/dist/esm/_core/business-model-lite/business-model-authored-metadata.schemas.js.map +1 -1
- package/dist/esm/_core/business-model-lite/business-model-lite-snapshot.schemas.d.ts +3 -3
- package/dist/esm/_core/business-model-lite/business-model.family-aspects.js +1 -1
- package/dist/esm/_core/business-model-lite/business-model.family-aspects.js.map +1 -1
- package/dist/esm/_core/business-model-lite/pricing-plan.schemas.d.ts +4 -3
- package/dist/esm/_core/business-model-lite/pricing-plan.schemas.d.ts.map +1 -1
- package/dist/esm/_core/business-model-lite/pricing-plan.schemas.js +4 -1
- package/dist/esm/_core/business-model-lite/pricing-plan.schemas.js.map +1 -1
- package/dist/esm/_core/business-semantics.specifications.schemas.d.ts +36 -0
- package/dist/esm/_core/business-semantics.specifications.schemas.d.ts.map +1 -1
- package/dist/esm/_core/business-semantics.specifications.schemas.js +52 -1
- package/dist/esm/_core/business-semantics.specifications.schemas.js.map +1 -1
- package/dist/esm/_core/capability-composition/capability-composition-validation.d.ts +22 -0
- package/dist/esm/_core/capability-composition/capability-composition-validation.d.ts.map +1 -0
- package/dist/esm/_core/capability-composition/capability-composition-validation.js +89 -0
- package/dist/esm/_core/capability-composition/capability-composition-validation.js.map +1 -0
- package/dist/esm/_core/capability-composition/capability-composition.family-aspects.d.ts +3 -0
- package/dist/esm/_core/capability-composition/capability-composition.family-aspects.d.ts.map +1 -0
- package/dist/esm/_core/capability-composition/capability-composition.family-aspects.js +26 -0
- package/dist/esm/_core/capability-composition/capability-composition.family-aspects.js.map +1 -0
- package/dist/esm/_core/capability-composition/capability-composition.schemas.d.ts +141 -0
- package/dist/esm/_core/capability-composition/capability-composition.schemas.d.ts.map +1 -0
- package/dist/esm/_core/capability-composition/capability-composition.schemas.js +147 -0
- package/dist/esm/_core/capability-composition/capability-composition.schemas.js.map +1 -0
- package/dist/esm/_core/compliance-documents/compliance-document-candidate-generation.schemas.d.ts +160 -0
- package/dist/esm/_core/compliance-documents/compliance-document-candidate-generation.schemas.d.ts.map +1 -1
- package/dist/esm/_core/compliance-documents/compliance-document-candidate-generation.schemas.js +124 -4
- package/dist/esm/_core/compliance-documents/compliance-document-candidate-generation.schemas.js.map +1 -1
- package/dist/esm/_core/compliance-documents/compliance-document-candidate-set.schemas.d.ts +95 -0
- package/dist/esm/_core/compliance-documents/compliance-document-candidate-set.schemas.d.ts.map +1 -0
- package/dist/esm/_core/compliance-documents/compliance-document-candidate-set.schemas.js +85 -0
- package/dist/esm/_core/compliance-documents/compliance-document-candidate-set.schemas.js.map +1 -0
- package/dist/esm/_core/compliance-documents/compliance-document-candidate.schemas.d.ts +743 -14
- package/dist/esm/_core/compliance-documents/compliance-document-candidate.schemas.d.ts.map +1 -1
- package/dist/esm/_core/compliance-documents/compliance-document-candidate.schemas.js +699 -22
- package/dist/esm/_core/compliance-documents/compliance-document-candidate.schemas.js.map +1 -1
- package/dist/esm/_core/compliance-documents/compliance-documents.family-aspects.d.ts +98 -6
- package/dist/esm/_core/compliance-documents/compliance-documents.family-aspects.d.ts.map +1 -1
- package/dist/esm/_core/compliance-documents/compliance-documents.family-aspects.js +197 -8
- package/dist/esm/_core/compliance-documents/compliance-documents.family-aspects.js.map +1 -1
- package/dist/esm/_core/compliance-documents/computed-document-facts.schemas.d.ts +64 -0
- package/dist/esm/_core/compliance-documents/computed-document-facts.schemas.d.ts.map +1 -0
- package/dist/esm/_core/compliance-documents/computed-document-facts.schemas.js +283 -0
- package/dist/esm/_core/compliance-documents/computed-document-facts.schemas.js.map +1 -0
- package/dist/esm/_core/compliance-documents/document-fact-specification-generation.schemas.d.ts.map +1 -1
- package/dist/esm/_core/compliance-documents/document-fact-specification-generation.schemas.js +30 -1
- package/dist/esm/_core/compliance-documents/document-fact-specification-generation.schemas.js.map +1 -1
- package/dist/esm/_core/compliance-documents/processor-register.family-aspects.js +1 -1
- package/dist/esm/_core/compliance-documents/processor-register.family-aspects.js.map +1 -1
- package/dist/esm/_core/compliance-documents/processor-register.schemas.d.ts +220 -4
- package/dist/esm/_core/compliance-documents/processor-register.schemas.d.ts.map +1 -1
- package/dist/esm/_core/compliance-documents/processor-register.schemas.js +149 -2
- package/dist/esm/_core/compliance-documents/processor-register.schemas.js.map +1 -1
- package/dist/esm/_core/compliance-documents/required-document-set.schemas.d.ts +70 -3
- package/dist/esm/_core/compliance-documents/required-document-set.schemas.d.ts.map +1 -1
- package/dist/esm/_core/compliance-documents/required-document-set.schemas.js +75 -3
- package/dist/esm/_core/compliance-documents/required-document-set.schemas.js.map +1 -1
- package/dist/esm/_core/composite-view-specification.schemas.d.ts +14 -0
- package/dist/esm/_core/composite-view-specification.schemas.d.ts.map +1 -1
- package/dist/esm/_core/composite-view-specification.schemas.js +13 -0
- package/dist/esm/_core/composite-view-specification.schemas.js.map +1 -1
- package/dist/esm/_core/cross-registry-assertions.d.ts +6 -4
- package/dist/esm/_core/cross-registry-assertions.d.ts.map +1 -1
- package/dist/esm/_core/cross-registry-assertions.js +7 -5
- package/dist/esm/_core/cross-registry-assertions.js.map +1 -1
- package/dist/esm/_core/domain-plan/domain-plan-output-set.schemas.d.ts +5 -4
- package/dist/esm/_core/domain-plan/domain-plan-output-set.schemas.d.ts.map +1 -1
- package/dist/esm/_core/domain-plan/domain-plan-output-set.schemas.js +5 -2
- package/dist/esm/_core/domain-plan/domain-plan-output-set.schemas.js.map +1 -1
- package/dist/esm/_core/domain-plan/domain-plan.family-aspects.d.ts +30 -0
- package/dist/esm/_core/domain-plan/domain-plan.family-aspects.d.ts.map +1 -1
- package/dist/esm/_core/domain-plan/domain-plan.family-aspects.js +99 -6
- package/dist/esm/_core/domain-plan/domain-plan.family-aspects.js.map +1 -1
- package/dist/esm/_core/experience-plan/experience-plan-generation.schemas.d.ts +58 -0
- package/dist/esm/_core/experience-plan/experience-plan-generation.schemas.d.ts.map +1 -0
- package/dist/esm/_core/experience-plan/experience-plan-generation.schemas.js +71 -0
- package/dist/esm/_core/experience-plan/experience-plan-generation.schemas.js.map +1 -0
- package/dist/esm/_core/experience-plan/experience-plan-validation.d.ts +37 -0
- package/dist/esm/_core/experience-plan/experience-plan-validation.d.ts.map +1 -0
- package/dist/esm/_core/experience-plan/experience-plan-validation.js +83 -0
- package/dist/esm/_core/experience-plan/experience-plan-validation.js.map +1 -0
- package/dist/esm/_core/experience-plan/experience-plan.family-aspects.d.ts +3 -0
- package/dist/esm/_core/experience-plan/experience-plan.family-aspects.d.ts.map +1 -0
- package/dist/esm/_core/experience-plan/experience-plan.family-aspects.js +78 -0
- package/dist/esm/_core/experience-plan/experience-plan.family-aspects.js.map +1 -0
- package/dist/esm/_core/experience-plan/experience-plan.schemas.d.ts +285 -0
- package/dist/esm/_core/experience-plan/experience-plan.schemas.d.ts.map +1 -0
- package/dist/esm/_core/experience-plan/experience-plan.schemas.js +293 -0
- package/dist/esm/_core/experience-plan/experience-plan.schemas.js.map +1 -0
- package/dist/esm/_core/expert-personas/expert-persona-authored-metadata.schemas.d.ts +3 -2
- package/dist/esm/_core/expert-personas/expert-persona-authored-metadata.schemas.d.ts.map +1 -1
- package/dist/esm/_core/expert-personas/expert-persona-authored-metadata.schemas.js +5 -2
- package/dist/esm/_core/expert-personas/expert-persona-authored-metadata.schemas.js.map +1 -1
- package/dist/esm/_core/expert-personas/expert-persona-charter.schemas.d.ts +9 -2
- package/dist/esm/_core/expert-personas/expert-persona-charter.schemas.d.ts.map +1 -1
- package/dist/esm/_core/expert-personas/expert-persona-charter.schemas.js +7 -0
- package/dist/esm/_core/expert-personas/expert-persona-charter.schemas.js.map +1 -1
- package/dist/esm/_core/expert-personas/expert-personas.family-aspects.d.ts +18 -0
- package/dist/esm/_core/expert-personas/expert-personas.family-aspects.d.ts.map +1 -0
- package/dist/esm/_core/expert-personas/expert-personas.family-aspects.js +21 -0
- package/dist/esm/_core/expert-personas/expert-personas.family-aspects.js.map +1 -0
- package/dist/esm/_core/expert-personas/expert-role-template.schemas.d.ts +19 -0
- package/dist/esm/_core/expert-personas/expert-role-template.schemas.d.ts.map +1 -1
- package/dist/esm/_core/expert-personas/expert-role-template.schemas.js +23 -0
- package/dist/esm/_core/expert-personas/expert-role-template.schemas.js.map +1 -1
- package/dist/esm/_core/family-aspects.registry.d.ts.map +1 -1
- package/dist/esm/_core/family-aspects.registry.js +22 -1
- package/dist/esm/_core/family-aspects.registry.js.map +1 -1
- package/dist/esm/_core/family-aspects.schemas.d.ts +64 -1
- package/dist/esm/_core/family-aspects.schemas.d.ts.map +1 -1
- package/dist/esm/_core/family-aspects.schemas.js.map +1 -1
- package/dist/esm/_core/feature-drafts/capability-map-output-set-generation.schemas.d.ts +27 -27
- package/dist/esm/_core/feature-drafts/capability-map-output-set.schemas.d.ts +59 -59
- package/dist/esm/_core/feature-drafts/feature-drafts.family-aspects.js +1 -1
- package/dist/esm/_core/feature-drafts/feature-drafts.family-aspects.js.map +1 -1
- package/dist/esm/_core/feature-drafts/feature-specification-drafts.schemas.d.ts.map +1 -1
- package/dist/esm/_core/feature-drafts/feature-specification-drafts.schemas.js +6 -1
- package/dist/esm/_core/feature-drafts/feature-specification-drafts.schemas.js.map +1 -1
- package/dist/esm/_core/guidance-flow-specification.schemas.d.ts +11 -15
- package/dist/esm/_core/guidance-flow-specification.schemas.d.ts.map +1 -1
- package/dist/esm/_core/guidance-flow-specification.schemas.js +12 -11
- package/dist/esm/_core/guidance-flow-specification.schemas.js.map +1 -1
- package/dist/esm/_core/index.d.ts +16 -0
- package/dist/esm/_core/index.d.ts.map +1 -1
- package/dist/esm/_core/index.js +16 -0
- package/dist/esm/_core/index.js.map +1 -1
- package/dist/esm/_core/integration-plan/integration-plan-generation.schemas.d.ts +52 -0
- package/dist/esm/_core/integration-plan/integration-plan-generation.schemas.d.ts.map +1 -0
- package/dist/esm/_core/integration-plan/integration-plan-generation.schemas.js +50 -0
- package/dist/esm/_core/integration-plan/integration-plan-generation.schemas.js.map +1 -0
- package/dist/esm/_core/integration-plan/integration-plan-validation.d.ts +27 -0
- package/dist/esm/_core/integration-plan/integration-plan-validation.d.ts.map +1 -0
- package/dist/esm/_core/integration-plan/integration-plan-validation.js +63 -0
- package/dist/esm/_core/integration-plan/integration-plan-validation.js.map +1 -0
- package/dist/esm/_core/integration-plan/integration-plan.family-aspects.d.ts +3 -0
- package/dist/esm/_core/integration-plan/integration-plan.family-aspects.d.ts.map +1 -0
- package/dist/esm/_core/integration-plan/integration-plan.family-aspects.js +52 -0
- package/dist/esm/_core/integration-plan/integration-plan.family-aspects.js.map +1 -0
- package/dist/esm/_core/integration-plan/integration-plan.schemas.d.ts +168 -0
- package/dist/esm/_core/integration-plan/integration-plan.schemas.d.ts.map +1 -0
- package/dist/esm/_core/integration-plan/integration-plan.schemas.js +170 -0
- package/dist/esm/_core/integration-plan/integration-plan.schemas.js.map +1 -0
- package/dist/esm/_core/market/feature-benefit.schemas.d.ts +6 -5
- package/dist/esm/_core/market/feature-benefit.schemas.d.ts.map +1 -1
- package/dist/esm/_core/market/feature-benefit.schemas.js +5 -2
- package/dist/esm/_core/market/feature-benefit.schemas.js.map +1 -1
- package/dist/esm/_core/market/market-alternative.schemas.d.ts +4 -3
- package/dist/esm/_core/market/market-alternative.schemas.d.ts.map +1 -1
- package/dist/esm/_core/market/market-alternative.schemas.js +4 -1
- package/dist/esm/_core/market/market-alternative.schemas.js.map +1 -1
- package/dist/esm/_core/market/market-authored-metadata.schemas.d.ts +11 -9
- package/dist/esm/_core/market/market-authored-metadata.schemas.d.ts.map +1 -1
- package/dist/esm/_core/market/market-authored-metadata.schemas.js +13 -10
- package/dist/esm/_core/market/market-authored-metadata.schemas.js.map +1 -1
- package/dist/esm/_core/market/market-buying-journey.schemas.d.ts +5 -4
- package/dist/esm/_core/market/market-buying-journey.schemas.d.ts.map +1 -1
- package/dist/esm/_core/market/market-buying-journey.schemas.js +4 -1
- package/dist/esm/_core/market/market-buying-journey.schemas.js.map +1 -1
- package/dist/esm/_core/market/market-category.schemas.d.ts +2 -2
- package/dist/esm/_core/market/market-channel.schemas.d.ts +6 -5
- package/dist/esm/_core/market/market-channel.schemas.d.ts.map +1 -1
- package/dist/esm/_core/market/market-channel.schemas.js +6 -3
- package/dist/esm/_core/market/market-channel.schemas.js.map +1 -1
- package/dist/esm/_core/market/market-gain.schemas.d.ts +4 -3
- package/dist/esm/_core/market/market-gain.schemas.d.ts.map +1 -1
- package/dist/esm/_core/market/market-gain.schemas.js +4 -1
- package/dist/esm/_core/market/market-gain.schemas.js.map +1 -1
- package/dist/esm/_core/market/market-icp.schemas.d.ts +12 -11
- package/dist/esm/_core/market/market-icp.schemas.d.ts.map +1 -1
- package/dist/esm/_core/market/market-icp.schemas.js +12 -9
- package/dist/esm/_core/market/market-icp.schemas.js.map +1 -1
- package/dist/esm/_core/market/market-job.schemas.d.ts +4 -3
- package/dist/esm/_core/market/market-job.schemas.d.ts.map +1 -1
- package/dist/esm/_core/market/market-job.schemas.js +4 -1
- package/dist/esm/_core/market/market-job.schemas.js.map +1 -1
- package/dist/esm/_core/market/market-message-template.schemas.d.ts +5 -4
- package/dist/esm/_core/market/market-message-template.schemas.d.ts.map +1 -1
- package/dist/esm/_core/market/market-message-template.schemas.js +5 -2
- package/dist/esm/_core/market/market-message-template.schemas.js.map +1 -1
- package/dist/esm/_core/market/market-objection.schemas.d.ts +4 -3
- package/dist/esm/_core/market/market-objection.schemas.d.ts.map +1 -1
- package/dist/esm/_core/market/market-objection.schemas.js +4 -1
- package/dist/esm/_core/market/market-objection.schemas.js.map +1 -1
- package/dist/esm/_core/market/market-pain.schemas.d.ts +4 -3
- package/dist/esm/_core/market/market-pain.schemas.d.ts.map +1 -1
- package/dist/esm/_core/market/market-pain.schemas.js +4 -1
- package/dist/esm/_core/market/market-pain.schemas.js.map +1 -1
- package/dist/esm/_core/market/market-persona.schemas.d.ts +5 -4
- package/dist/esm/_core/market/market-persona.schemas.d.ts.map +1 -1
- package/dist/esm/_core/market/market-persona.schemas.js +5 -2
- package/dist/esm/_core/market/market-persona.schemas.js.map +1 -1
- package/dist/esm/_core/market/market-positioning.schemas.d.ts +2 -2
- package/dist/esm/_core/market/market-proof.schemas.d.ts +4 -3
- package/dist/esm/_core/market/market-proof.schemas.d.ts.map +1 -1
- package/dist/esm/_core/market/market-proof.schemas.js +4 -1
- package/dist/esm/_core/market/market-proof.schemas.js.map +1 -1
- package/dist/esm/_core/market/market-snapshot-generation.schemas.d.ts +54 -54
- package/dist/esm/_core/market/market-snapshot.schemas.d.ts +59 -59
- package/dist/esm/_core/market/market-tone-of-voice.schemas.d.ts +4 -3
- package/dist/esm/_core/market/market-tone-of-voice.schemas.d.ts.map +1 -1
- package/dist/esm/_core/market/market-tone-of-voice.schemas.js +4 -1
- package/dist/esm/_core/market/market-tone-of-voice.schemas.js.map +1 -1
- package/dist/esm/_core/market/market-trigger.schemas.d.ts +4 -3
- package/dist/esm/_core/market/market-trigger.schemas.d.ts.map +1 -1
- package/dist/esm/_core/market/market-trigger.schemas.js +4 -1
- package/dist/esm/_core/market/market-trigger.schemas.js.map +1 -1
- package/dist/esm/_core/market/market.family-aspects.d.ts.map +1 -1
- package/dist/esm/_core/market/market.family-aspects.js +25 -1
- package/dist/esm/_core/market/market.family-aspects.js.map +1 -1
- package/dist/esm/_core/onboarding-view-specification.schemas.d.ts +27 -22
- package/dist/esm/_core/onboarding-view-specification.schemas.d.ts.map +1 -1
- package/dist/esm/_core/onboarding-view-specification.schemas.js +7 -12
- package/dist/esm/_core/onboarding-view-specification.schemas.js.map +1 -1
- package/dist/esm/_core/placement-plan/placement-plan-generation.schemas.d.ts +21 -21
- package/dist/esm/_core/placement-plan/placement-plan-validation.d.ts +30 -16
- package/dist/esm/_core/placement-plan/placement-plan-validation.d.ts.map +1 -1
- package/dist/esm/_core/placement-plan/placement-plan-validation.js +34 -12
- package/dist/esm/_core/placement-plan/placement-plan-validation.js.map +1 -1
- package/dist/esm/_core/placement-plan/placement-plan.family-aspects.d.ts.map +1 -1
- package/dist/esm/_core/placement-plan/placement-plan.family-aspects.js +24 -1
- package/dist/esm/_core/placement-plan/placement-plan.family-aspects.js.map +1 -1
- package/dist/esm/_core/placement-plan/placement-plan.schemas.d.ts +78 -47
- package/dist/esm/_core/placement-plan/placement-plan.schemas.d.ts.map +1 -1
- package/dist/esm/_core/placement-plan/placement-plan.schemas.js +62 -24
- package/dist/esm/_core/placement-plan/placement-plan.schemas.js.map +1 -1
- package/dist/esm/_core/provider-specification.schemas.d.ts +19 -0
- package/dist/esm/_core/provider-specification.schemas.d.ts.map +1 -1
- package/dist/esm/_core/provider-specification.schemas.js +0 -20
- package/dist/esm/_core/provider-specification.schemas.js.map +1 -1
- package/dist/esm/_core/requirements/functional-requirement.schemas.d.ts +2 -2
- package/dist/esm/_core/requirements/non-functional-requirement.schemas.d.ts +2 -2
- package/dist/esm/_core/requirements/requirements-authored-metadata.schemas.d.ts +3 -2
- package/dist/esm/_core/requirements/requirements-authored-metadata.schemas.d.ts.map +1 -1
- package/dist/esm/_core/requirements/requirements-authored-metadata.schemas.js +5 -2
- package/dist/esm/_core/requirements/requirements-authored-metadata.schemas.js.map +1 -1
- package/dist/esm/_core/requirements/requirements-snapshot.schemas.d.ts +4 -4
- package/dist/esm/_core/requirements/requirements.family-aspects.d.ts.map +1 -1
- package/dist/esm/_core/requirements/requirements.family-aspects.js +3 -1
- package/dist/esm/_core/requirements/requirements.family-aspects.js.map +1 -1
- package/dist/esm/_core/resource-specification.schemas.d.ts +8 -0
- package/dist/esm/_core/resource-specification.schemas.d.ts.map +1 -1
- package/dist/esm/_core/resource-specification.schemas.js.map +1 -1
- package/dist/esm/_core/roadmap/roadmap-authored-metadata.schemas.d.ts +3 -2
- package/dist/esm/_core/roadmap/roadmap-authored-metadata.schemas.d.ts.map +1 -1
- package/dist/esm/_core/roadmap/roadmap-authored-metadata.schemas.js +5 -2
- package/dist/esm/_core/roadmap/roadmap-authored-metadata.schemas.js.map +1 -1
- package/dist/esm/_core/roadmap/roadmap-phase.schemas.d.ts +2 -2
- package/dist/esm/_core/roadmap/roadmap-snapshot-validation.d.ts +5 -0
- package/dist/esm/_core/roadmap/roadmap-snapshot-validation.d.ts.map +1 -1
- package/dist/esm/_core/roadmap/roadmap-snapshot-validation.js +1 -8
- package/dist/esm/_core/roadmap/roadmap-snapshot-validation.js.map +1 -1
- package/dist/esm/_core/roadmap/roadmap-snapshot.schemas.d.ts +2 -2
- package/dist/esm/_core/roadmap/roadmap.family-aspects.js +1 -1
- package/dist/esm/_core/roadmap/roadmap.family-aspects.js.map +1 -1
- package/dist/esm/_core/utils/extract-field-specs.d.ts.map +1 -1
- package/dist/esm/_core/utils/extract-field-specs.js +4 -2
- package/dist/esm/_core/utils/extract-field-specs.js.map +1 -1
- package/dist/esm/_core/vision/vision-authored-metadata.schemas.d.ts +3 -2
- package/dist/esm/_core/vision/vision-authored-metadata.schemas.d.ts.map +1 -1
- package/dist/esm/_core/vision/vision-authored-metadata.schemas.js +5 -2
- package/dist/esm/_core/vision/vision-authored-metadata.schemas.js.map +1 -1
- package/dist/esm/_core/vision/vision-constraint.schemas.d.ts +2 -2
- package/dist/esm/_core/vision/vision-idea.schemas.d.ts +2 -2
- package/dist/esm/_core/vision/vision-mission.schemas.d.ts +2 -2
- package/dist/esm/_core/vision/vision-problem.schemas.d.ts +2 -2
- package/dist/esm/_core/vision/vision-snapshot.schemas.d.ts +10 -10
- package/dist/esm/_core/vision/vision-success-criterion.schemas.d.ts +2 -2
- package/dist/esm/_core/vision/vision.family-aspects.js +1 -1
- package/dist/esm/_core/vision/vision.family-aspects.js.map +1 -1
- package/dist/esm/_core/website-plan/website-plan-generation.schemas.d.ts +45 -0
- package/dist/esm/_core/website-plan/website-plan-generation.schemas.d.ts.map +1 -0
- package/dist/esm/_core/website-plan/website-plan-generation.schemas.js +55 -0
- package/dist/esm/_core/website-plan/website-plan-generation.schemas.js.map +1 -0
- package/dist/esm/_core/website-plan/website-plan-validation.d.ts +37 -0
- package/dist/esm/_core/website-plan/website-plan-validation.d.ts.map +1 -0
- package/dist/esm/_core/website-plan/website-plan-validation.js +77 -0
- package/dist/esm/_core/website-plan/website-plan-validation.js.map +1 -0
- package/dist/esm/_core/website-plan/website-plan.family-aspects.d.ts +3 -0
- package/dist/esm/_core/website-plan/website-plan.family-aspects.d.ts.map +1 -0
- package/dist/esm/_core/website-plan/website-plan.family-aspects.js +35 -0
- package/dist/esm/_core/website-plan/website-plan.family-aspects.js.map +1 -0
- package/dist/esm/_core/website-plan/website-plan.schemas.d.ts +194 -0
- package/dist/esm/_core/website-plan/website-plan.schemas.d.ts.map +1 -0
- package/dist/esm/_core/website-plan/website-plan.schemas.js +193 -0
- package/dist/esm/_core/website-plan/website-plan.schemas.js.map +1 -0
- package/dist/esm/_core/zod-core-nameability.d.ts +47 -0
- package/dist/esm/_core/zod-core-nameability.d.ts.map +1 -0
- package/dist/esm/_core/zod-core-nameability.js +1 -0
- package/dist/esm/_core/zod-core-nameability.js.map +1 -0
- package/dist/esm/application-creation/application-creator-inputs.application-creation.schemas.d.ts +86 -0
- package/dist/esm/application-creation/application-creator-inputs.application-creation.schemas.d.ts.map +1 -0
- package/dist/esm/application-creation/application-creator-inputs.application-creation.schemas.js +96 -0
- package/dist/esm/application-creation/application-creator-inputs.application-creation.schemas.js.map +1 -0
- package/dist/esm/application-creation/application-document-fact-specification.application-creation.schemas.d.ts +139 -34
- package/dist/esm/application-creation/application-document-fact-specification.application-creation.schemas.d.ts.map +1 -1
- package/dist/esm/application-creation/application-document-fact-specification.application-creation.schemas.js +182 -11
- package/dist/esm/application-creation/application-document-fact-specification.application-creation.schemas.js.map +1 -1
- package/dist/esm/application-creation/application-document-release-policy-specification.application-creation.schemas.d.ts +71 -2
- package/dist/esm/application-creation/application-document-release-policy-specification.application-creation.schemas.d.ts.map +1 -1
- package/dist/esm/application-creation/application-document-release-policy-specification.application-creation.schemas.js +88 -1
- package/dist/esm/application-creation/application-document-release-policy-specification.application-creation.schemas.js.map +1 -1
- package/dist/esm/application-creation/creator-inputs.family-aspects.d.ts +14 -0
- package/dist/esm/application-creation/creator-inputs.family-aspects.d.ts.map +1 -0
- package/dist/esm/application-creation/creator-inputs.family-aspects.js +17 -0
- package/dist/esm/application-creation/creator-inputs.family-aspects.js.map +1 -0
- package/dist/esm/application-creation/document-facts.family-aspects.d.ts.map +1 -1
- package/dist/esm/application-creation/document-facts.family-aspects.js +25 -1
- package/dist/esm/application-creation/document-facts.family-aspects.js.map +1 -1
- package/dist/esm/application-creation/document-release-policy.family-aspects.js +1 -1
- package/dist/esm/application-creation/document-release-policy.family-aspects.js.map +1 -1
- package/dist/esm/application-creation/journey.application-creation.schemas.d.ts +14 -48
- package/dist/esm/application-creation/journey.application-creation.schemas.d.ts.map +1 -1
- package/dist/esm/application-creation/journey.application-creation.schemas.js +52 -52
- package/dist/esm/application-creation/journey.application-creation.schemas.js.map +1 -1
- package/dist/esm/application-creation/playbooks.application-creation.schemas.d.ts +209 -495
- package/dist/esm/application-creation/playbooks.application-creation.schemas.d.ts.map +1 -1
- package/dist/esm/application-creation/playbooks.application-creation.schemas.js +257 -534
- package/dist/esm/application-creation/playbooks.application-creation.schemas.js.map +1 -1
- package/dist/esm/application-creation/structured-artifact-landing.application-creation.schemas.d.ts +10 -0
- package/dist/esm/application-creation/structured-artifact-landing.application-creation.schemas.d.ts.map +1 -1
- package/dist/esm/application-creation/structured-artifact-landing.application-creation.schemas.js +10 -0
- package/dist/esm/application-creation/structured-artifact-landing.application-creation.schemas.js.map +1 -1
- package/dist/esm/application-creation.exports.d.ts +73 -8
- package/dist/esm/application-creation.exports.d.ts.map +1 -1
- package/dist/esm/application-creation.exports.js +103 -8
- package/dist/esm/application-creation.exports.js.map +1 -1
- package/dist/esm/assurance/__tests__/authority-evaluation-instant.fixture.d.ts +24 -0
- package/dist/esm/assurance/__tests__/authority-evaluation-instant.fixture.d.ts.map +1 -0
- package/dist/esm/assurance/__tests__/authority-evaluation-instant.fixture.js +24 -0
- package/dist/esm/assurance/__tests__/authority-evaluation-instant.fixture.js.map +1 -0
- package/dist/esm/assurance/application-document-publication.schemas.d.ts +49 -0
- package/dist/esm/assurance/application-document-publication.schemas.d.ts.map +1 -1
- package/dist/esm/assurance/application-document-publication.schemas.js +51 -0
- package/dist/esm/assurance/application-document-publication.schemas.js.map +1 -1
- package/dist/esm/assurance/application-document-release-set.schemas.d.ts +161 -0
- package/dist/esm/assurance/application-document-release-set.schemas.d.ts.map +1 -0
- package/dist/esm/assurance/application-document-release-set.schemas.js +138 -0
- package/dist/esm/assurance/application-document-release-set.schemas.js.map +1 -0
- package/dist/esm/assurance/application-risk-register.family-aspects.d.ts +28 -0
- package/dist/esm/assurance/application-risk-register.family-aspects.d.ts.map +1 -0
- package/dist/esm/assurance/application-risk-register.family-aspects.js +58 -0
- package/dist/esm/assurance/application-risk-register.family-aspects.js.map +1 -0
- package/dist/esm/assurance/application-risk-register.schemas.d.ts +172 -0
- package/dist/esm/assurance/application-risk-register.schemas.d.ts.map +1 -0
- package/dist/esm/assurance/application-risk-register.schemas.js +192 -0
- package/dist/esm/assurance/application-risk-register.schemas.js.map +1 -0
- package/dist/esm/assurance/application-risk-signals.derivations.d.ts +177 -0
- package/dist/esm/assurance/application-risk-signals.derivations.d.ts.map +1 -0
- package/dist/esm/assurance/application-risk-signals.derivations.js +229 -0
- package/dist/esm/assurance/application-risk-signals.derivations.js.map +1 -0
- package/dist/esm/assurance/assurance-authority-basis.definitions.d.ts +257 -13
- package/dist/esm/assurance/assurance-authority-basis.definitions.d.ts.map +1 -1
- package/dist/esm/assurance/assurance-authority-basis.definitions.js +836 -69
- package/dist/esm/assurance/assurance-authority-basis.definitions.js.map +1 -1
- package/dist/esm/assurance/assurance-authority-basis.schemas.d.ts +99 -33
- package/dist/esm/assurance/assurance-authority-basis.schemas.d.ts.map +1 -1
- package/dist/esm/assurance/assurance-authority-basis.schemas.js +38 -1
- package/dist/esm/assurance/assurance-authority-basis.schemas.js.map +1 -1
- package/dist/esm/assurance/assurance-document-blueprint-selection.d.ts +30 -0
- package/dist/esm/assurance/assurance-document-blueprint-selection.d.ts.map +1 -1
- package/dist/esm/assurance/assurance-document-blueprint-selection.js +40 -0
- package/dist/esm/assurance/assurance-document-blueprint-selection.js.map +1 -1
- package/dist/esm/assurance/assurance-document-system.definitions.d.ts.map +1 -1
- package/dist/esm/assurance/assurance-document-system.definitions.js +99 -8
- package/dist/esm/assurance/assurance-document-system.definitions.js.map +1 -1
- package/dist/esm/assurance/assurance-document-system.schemas.d.ts +133 -41
- package/dist/esm/assurance/assurance-document-system.schemas.d.ts.map +1 -1
- package/dist/esm/assurance/assurance-document-system.schemas.js +60 -11
- package/dist/esm/assurance/assurance-document-system.schemas.js.map +1 -1
- package/dist/esm/assurance/assurance-evidence-judgement.schemas.d.ts +470 -0
- package/dist/esm/assurance/assurance-evidence-judgement.schemas.d.ts.map +1 -0
- package/dist/esm/assurance/assurance-evidence-judgement.schemas.js +451 -0
- package/dist/esm/assurance/assurance-evidence-judgement.schemas.js.map +1 -0
- package/dist/esm/assurance/assurance-evidence-requirement-bodies.definitions.d.ts +0 -33
- package/dist/esm/assurance/assurance-evidence-requirement-bodies.definitions.d.ts.map +1 -1
- package/dist/esm/assurance/assurance-evidence-requirement-bodies.definitions.js +3339 -159
- package/dist/esm/assurance/assurance-evidence-requirement-bodies.definitions.js.map +1 -1
- package/dist/esm/assurance/assurance-foundation.schemas.d.ts +21 -0
- package/dist/esm/assurance/assurance-foundation.schemas.d.ts.map +1 -1
- package/dist/esm/assurance/assurance-foundation.schemas.js +21 -0
- package/dist/esm/assurance/assurance-foundation.schemas.js.map +1 -1
- package/dist/esm/assurance/assurance-objective-catalog.definitions.d.ts +32 -2
- package/dist/esm/assurance/assurance-objective-catalog.definitions.d.ts.map +1 -1
- package/dist/esm/assurance/assurance-objective-catalog.definitions.js +148 -5
- package/dist/esm/assurance/assurance-objective-catalog.definitions.js.map +1 -1
- package/dist/esm/assurance/assurance-program-generation.schemas.d.ts +257 -14
- package/dist/esm/assurance/assurance-program-generation.schemas.d.ts.map +1 -1
- package/dist/esm/assurance/assurance-program-generation.schemas.js +588 -45
- package/dist/esm/assurance/assurance-program-generation.schemas.js.map +1 -1
- package/dist/esm/assurance/assurance-program.family-aspects.d.ts +32 -8
- package/dist/esm/assurance/assurance-program.family-aspects.d.ts.map +1 -1
- package/dist/esm/assurance/assurance-program.family-aspects.js +288 -10
- package/dist/esm/assurance/assurance-program.family-aspects.js.map +1 -1
- package/dist/esm/assurance/assurance-program.schemas.d.ts +1182 -333
- package/dist/esm/assurance/assurance-program.schemas.d.ts.map +1 -1
- package/dist/esm/assurance/assurance-program.schemas.js +460 -68
- package/dist/esm/assurance/assurance-program.schemas.js.map +1 -1
- package/dist/esm/assurance/assurance-source-registry.definitions.d.ts.map +1 -1
- package/dist/esm/assurance/assurance-source-registry.definitions.js +70 -2
- package/dist/esm/assurance/assurance-source-registry.definitions.js.map +1 -1
- package/dist/esm/assurance/assurance-sources.schemas.d.ts +17 -0
- package/dist/esm/assurance/assurance-sources.schemas.d.ts.map +1 -1
- package/dist/esm/assurance/assurance-sources.schemas.js +17 -0
- package/dist/esm/assurance/assurance-sources.schemas.js.map +1 -1
- package/dist/esm/assurance/assurance-verification-requirement-bodies.definitions.d.ts.map +1 -1
- package/dist/esm/assurance/assurance-verification-requirement-bodies.definitions.js +205 -3
- package/dist/esm/assurance/assurance-verification-requirement-bodies.definitions.js.map +1 -1
- package/dist/esm/assurance/document-publication.family-aspects.js +1 -1
- package/dist/esm/assurance/document-publication.family-aspects.js.map +1 -1
- package/dist/esm/assurance/document-release-set.family-aspects.d.ts +11 -0
- package/dist/esm/assurance/document-release-set.family-aspects.d.ts.map +1 -0
- package/dist/esm/assurance/document-release-set.family-aspects.js +36 -0
- package/dist/esm/assurance/document-release-set.family-aspects.js.map +1 -0
- package/dist/esm/assurance/governed-document-release.d.ts +211 -0
- package/dist/esm/assurance/governed-document-release.d.ts.map +1 -0
- package/dist/esm/assurance/governed-document-release.js +314 -0
- package/dist/esm/assurance/governed-document-release.js.map +1 -0
- package/dist/esm/assurance.exports.d.ts +5 -0
- package/dist/esm/assurance.exports.d.ts.map +1 -1
- package/dist/esm/assurance.exports.js +5 -0
- package/dist/esm/assurance.exports.js.map +1 -1
- package/dist/esm/companion-exports.d.ts +135 -11
- package/dist/esm/companion-exports.d.ts.map +1 -1
- package/dist/esm/companion-exports.js.map +1 -1
- package/dist/esm/engine/_bootstrap.d.ts +1 -1
- package/dist/esm/engine/_bootstrap.js +1 -1
- package/dist/esm/engine/_bootstrap.js.map +1 -1
- package/dist/esm/engine/applications/resources/application-metadata.resource.specification.d.ts +1 -1
- package/dist/esm/engine/applications/resources/application-metadata.resource.specification.js +1 -1
- package/dist/esm/engine/applications/resources/application-metadata.resource.specification.js.map +1 -1
- package/dist/esm/engine/applications/resources/application-oauth-clients.resource.specification.d.ts +0 -23
- package/dist/esm/engine/applications/resources/application-oauth-clients.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/applications/resources/application-oauth-clients.resource.specification.js +110 -28
- package/dist/esm/engine/applications/resources/application-oauth-clients.resource.specification.js.map +1 -1
- package/dist/esm/engine/applications/resources/application-versions.resource.specification.d.ts +1 -1
- package/dist/esm/engine/applications/resources/application-versions.resource.specification.js +1 -1
- package/dist/esm/engine/applications/resources/application-versions.resource.specification.js.map +1 -1
- package/dist/esm/engine/applications/resources/applications.resource.specification.d.ts +1 -0
- package/dist/esm/engine/applications/resources/applications.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/auth/resources/application-access-grants.resource.specification.d.ts +57 -0
- package/dist/esm/engine/auth/resources/application-access-grants.resource.specification.d.ts.map +1 -0
- package/dist/esm/engine/auth/resources/application-access-grants.resource.specification.js +412 -0
- package/dist/esm/engine/auth/resources/application-access-grants.resource.specification.js.map +1 -0
- package/dist/esm/engine/auth/resources/index.d.ts +2 -0
- package/dist/esm/engine/auth/resources/index.d.ts.map +1 -1
- package/dist/esm/engine/auth/resources/index.js +2 -0
- package/dist/esm/engine/auth/resources/index.js.map +1 -1
- package/dist/esm/engine/auth/resources/organization-oauth-clients.resource.specification.d.ts +4 -4
- package/dist/esm/engine/auth/resources/organization-oauth-clients.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/auth/resources/organization-oauth-clients.resource.specification.js +57 -6
- package/dist/esm/engine/auth/resources/organization-oauth-clients.resource.specification.js.map +1 -1
- package/dist/esm/engine/auth/resources/organization-onboarding-operations.resource.specification.d.ts +9 -0
- package/dist/esm/engine/auth/resources/organization-onboarding-operations.resource.specification.d.ts.map +1 -0
- package/dist/esm/engine/auth/resources/organization-onboarding-operations.resource.specification.js +141 -0
- package/dist/esm/engine/auth/resources/organization-onboarding-operations.resource.specification.js.map +1 -0
- package/dist/esm/engine/auth/resources/organization-provider-credentials.resource.specification.d.ts +4 -1
- package/dist/esm/engine/auth/resources/organization-provider-credentials.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/auth/resources/organization-provider-credentials.resource.specification.js +10 -6
- package/dist/esm/engine/auth/resources/organization-provider-credentials.resource.specification.js.map +1 -1
- package/dist/esm/engine/auth/resources/scim-provisioning-config.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/auth/resources/scim-provisioning-config.resource.specification.js +5 -4
- package/dist/esm/engine/auth/resources/scim-provisioning-config.resource.specification.js.map +1 -1
- package/dist/esm/engine/auth/resources/siem-delivery-outbox.resource.specification.d.ts +4 -0
- package/dist/esm/engine/auth/resources/siem-delivery-outbox.resource.specification.d.ts.map +1 -0
- package/dist/esm/engine/auth/resources/siem-delivery-outbox.resource.specification.js +129 -0
- package/dist/esm/engine/auth/resources/siem-delivery-outbox.resource.specification.js.map +1 -0
- package/dist/esm/engine/auth/resources/siem-export-config.resource.specification.d.ts +19 -7
- package/dist/esm/engine/auth/resources/siem-export-config.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/auth/resources/siem-export-config.resource.specification.js +24 -13
- package/dist/esm/engine/auth/resources/siem-export-config.resource.specification.js.map +1 -1
- package/dist/esm/engine/auth/resources/sso-config.resource.specification.d.ts +0 -40
- package/dist/esm/engine/auth/resources/sso-config.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/auth/resources/sso-config.resource.specification.js +14 -27
- package/dist/esm/engine/auth/resources/sso-config.resource.specification.js.map +1 -1
- package/dist/esm/engine/auth/resources/sso-connections.resource.specification.d.ts +8 -2
- package/dist/esm/engine/auth/resources/sso-connections.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/auth/resources/sso-connections.resource.specification.js +16 -3
- package/dist/esm/engine/auth/resources/sso-connections.resource.specification.js.map +1 -1
- package/dist/esm/engine/auth/resources/user-provider-credentials.resource.specification.d.ts +5 -2
- package/dist/esm/engine/auth/resources/user-provider-credentials.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/auth/resources/user-provider-credentials.resource.specification.js +10 -16
- package/dist/esm/engine/auth/resources/user-provider-credentials.resource.specification.js.map +1 -1
- package/dist/esm/engine/billing/resources/billing-accounts.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/billing/resources/billing-accounts.resource.specification.js +15 -5
- package/dist/esm/engine/billing/resources/billing-accounts.resource.specification.js.map +1 -1
- package/dist/esm/engine/billing/resources/billing-effect-outbox.resource.specification.d.ts +9 -0
- package/dist/esm/engine/billing/resources/billing-effect-outbox.resource.specification.d.ts.map +1 -0
- package/dist/esm/engine/billing/resources/billing-effect-outbox.resource.specification.js +164 -0
- package/dist/esm/engine/billing/resources/billing-effect-outbox.resource.specification.js.map +1 -0
- package/dist/esm/engine/billing/resources/billing-provider-event-settlements.resource.specification.d.ts +14 -0
- package/dist/esm/engine/billing/resources/billing-provider-event-settlements.resource.specification.d.ts.map +1 -0
- package/dist/esm/engine/billing/resources/billing-provider-event-settlements.resource.specification.js +124 -0
- package/dist/esm/engine/billing/resources/billing-provider-event-settlements.resource.specification.js.map +1 -0
- package/dist/esm/engine/billing/resources/billing-subscription-mutation-completions.resource.specification.d.ts +9 -0
- package/dist/esm/engine/billing/resources/billing-subscription-mutation-completions.resource.specification.d.ts.map +1 -0
- package/dist/esm/engine/billing/resources/billing-subscription-mutation-completions.resource.specification.js +123 -0
- package/dist/esm/engine/billing/resources/billing-subscription-mutation-completions.resource.specification.js.map +1 -0
- package/dist/esm/engine/billing/resources/billing-subscription-mutation-intents.resource.specification.d.ts +11 -0
- package/dist/esm/engine/billing/resources/billing-subscription-mutation-intents.resource.specification.d.ts.map +1 -0
- package/dist/esm/engine/billing/resources/billing-subscription-mutation-intents.resource.specification.js +172 -0
- package/dist/esm/engine/billing/resources/billing-subscription-mutation-intents.resource.specification.js.map +1 -0
- package/dist/esm/engine/billing/resources/index.d.ts +4 -0
- package/dist/esm/engine/billing/resources/index.d.ts.map +1 -1
- package/dist/esm/engine/billing/resources/index.js +4 -0
- package/dist/esm/engine/billing/resources/index.js.map +1 -1
- package/dist/esm/engine/billing/resources/prices.resource.specification.d.ts +3 -3
- package/dist/esm/engine/billing/resources/products.resource.specification.d.ts +3 -3
- package/dist/esm/engine/billing/resources/products.resource.specification.js +1 -1
- package/dist/esm/engine/billing/resources/products.resource.specification.js.map +1 -1
- package/dist/esm/engine/billing/resources/subscriptions.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/billing/resources/subscriptions.resource.specification.js +92 -36
- package/dist/esm/engine/billing/resources/subscriptions.resource.specification.js.map +1 -1
- package/dist/esm/engine/compliance/resources/application-audit-logs.resource.specification.d.ts +77 -0
- package/dist/esm/engine/compliance/resources/application-audit-logs.resource.specification.d.ts.map +1 -0
- package/dist/esm/engine/compliance/resources/application-audit-logs.resource.specification.js +375 -0
- package/dist/esm/engine/compliance/resources/application-audit-logs.resource.specification.js.map +1 -0
- package/dist/esm/engine/compliance/resources/audit-logs.resource.specification.d.ts +1 -1
- package/dist/esm/engine/compliance/resources/index.d.ts +2 -0
- package/dist/esm/engine/compliance/resources/index.d.ts.map +1 -1
- package/dist/esm/engine/compliance/resources/index.js +2 -0
- package/dist/esm/engine/compliance/resources/index.js.map +1 -1
- package/dist/esm/engine/compliance/resources/user-governed-document-acceptances.resource.specification.d.ts +16 -0
- package/dist/esm/engine/compliance/resources/user-governed-document-acceptances.resource.specification.d.ts.map +1 -0
- package/dist/esm/engine/compliance/resources/user-governed-document-acceptances.resource.specification.js +183 -0
- package/dist/esm/engine/compliance/resources/user-governed-document-acceptances.resource.specification.js.map +1 -0
- package/dist/esm/engine/engine-resource-specifications.registry.d.ts.map +1 -1
- package/dist/esm/engine/engine-resource-specifications.registry.js +28 -0
- package/dist/esm/engine/engine-resource-specifications.registry.js.map +1 -1
- package/dist/esm/engine/errors/error-messages.specification.d.ts.map +1 -1
- package/dist/esm/engine/errors/error-messages.specification.js +123 -19
- package/dist/esm/engine/errors/error-messages.specification.js.map +1 -1
- package/dist/esm/engine/features/resources/application-features.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/features/resources/application-features.resource.specification.js +2 -1
- package/dist/esm/engine/features/resources/application-features.resource.specification.js.map +1 -1
- package/dist/esm/engine/features/resources/organization-features.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/features/resources/organization-features.resource.specification.js +1 -0
- package/dist/esm/engine/features/resources/organization-features.resource.specification.js.map +1 -1
- package/dist/esm/engine/features/resources/user-features.resource.specification.d.ts +1 -1
- package/dist/esm/engine/features/resources/user-features.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/features/resources/user-features.resource.specification.js +4 -1
- package/dist/esm/engine/features/resources/user-features.resource.specification.js.map +1 -1
- package/dist/esm/engine/files/resources/files.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/files/resources/files.resource.specification.js +15 -3
- package/dist/esm/engine/files/resources/files.resource.specification.js.map +1 -1
- package/dist/esm/engine/flows-actors/resources/flow-actor-executions.resource.specification.d.ts +3 -0
- package/dist/esm/engine/flows-actors/resources/flow-actor-executions.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/flows-actors/resources/flow-actor-executions.resource.specification.js +1 -1
- package/dist/esm/engine/flows-actors/resources/flow-actor-executions.resource.specification.js.map +1 -1
- package/dist/esm/engine/flows-actors/resources/flow-actor-tasks.resource.specification.d.ts +3 -3
- package/dist/esm/engine/flows-actors/resources/provider-call-records.resource.specification.d.ts +14 -0
- package/dist/esm/engine/flows-actors/resources/provider-call-records.resource.specification.d.ts.map +1 -0
- package/dist/esm/engine/flows-actors/resources/provider-call-records.resource.specification.js +184 -0
- package/dist/esm/engine/flows-actors/resources/provider-call-records.resource.specification.js.map +1 -0
- package/dist/esm/engine/frontend-components/actions/button-group-separator.frontend-component.specification.js +3 -3
- package/dist/esm/engine/frontend-components/actions/button-group-separator.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/actions/button-group.frontend-component.specification.d.ts.map +1 -1
- package/dist/esm/engine/frontend-components/actions/button-group.frontend-component.specification.js +3 -2
- package/dist/esm/engine/frontend-components/actions/button-group.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/actions/button.frontend-component.specification.d.ts.map +1 -1
- package/dist/esm/engine/frontend-components/actions/button.frontend-component.specification.js +18 -0
- package/dist/esm/engine/frontend-components/actions/button.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/ai-elements/artifacts/ai-diff-block.frontend-component.specification.d.ts +4 -0
- package/dist/esm/engine/frontend-components/ai-elements/artifacts/ai-diff-block.frontend-component.specification.d.ts.map +1 -0
- package/dist/esm/engine/frontend-components/ai-elements/artifacts/ai-diff-block.frontend-component.specification.js +21 -0
- package/dist/esm/engine/frontend-components/ai-elements/artifacts/ai-diff-block.frontend-component.specification.js.map +1 -0
- package/dist/esm/engine/frontend-components/ai-elements/trace/ai-chain-of-thought.frontend-component.specification.js +1 -1
- package/dist/esm/engine/frontend-components/ai-elements/trace/ai-chain-of-thought.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/app/app-layout-billing-settings.frontend-component.specification.d.ts +5 -0
- package/dist/esm/engine/frontend-components/app/app-layout-billing-settings.frontend-component.specification.d.ts.map +1 -0
- package/dist/esm/engine/frontend-components/app/app-layout-billing-settings.frontend-component.specification.js +82 -0
- package/dist/esm/engine/frontend-components/app/app-layout-billing-settings.frontend-component.specification.js.map +1 -0
- package/dist/esm/engine/frontend-components/app/app-layout-connected-accounts-settings.frontend-component.specification.d.ts.map +1 -1
- package/dist/esm/engine/frontend-components/app/app-layout-connected-accounts-settings.frontend-component.specification.js +6 -5
- package/dist/esm/engine/frontend-components/app/app-layout-connected-accounts-settings.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/app/app-layout-consent-gate.frontend-component.specification.d.ts +4 -0
- package/dist/esm/engine/frontend-components/app/app-layout-consent-gate.frontend-component.specification.d.ts.map +1 -0
- package/dist/esm/engine/frontend-components/app/app-layout-consent-gate.frontend-component.specification.js +22 -0
- package/dist/esm/engine/frontend-components/app/app-layout-consent-gate.frontend-component.specification.js.map +1 -0
- package/dist/esm/engine/frontend-components/app/app-layout-document-acceptance-gate.frontend-component.specification.d.ts +4 -0
- package/dist/esm/engine/frontend-components/app/app-layout-document-acceptance-gate.frontend-component.specification.d.ts.map +1 -0
- package/dist/esm/engine/frontend-components/app/app-layout-document-acceptance-gate.frontend-component.specification.js +22 -0
- package/dist/esm/engine/frontend-components/app/app-layout-document-acceptance-gate.frontend-component.specification.js.map +1 -0
- package/dist/esm/engine/frontend-components/app/app-layout-surface-error-boundary.frontend-component.specification.d.ts +5 -0
- package/dist/esm/engine/frontend-components/app/app-layout-surface-error-boundary.frontend-component.specification.d.ts.map +1 -0
- package/dist/esm/engine/frontend-components/app/app-layout-surface-error-boundary.frontend-component.specification.js +81 -0
- package/dist/esm/engine/frontend-components/app/app-layout-surface-error-boundary.frontend-component.specification.js.map +1 -0
- package/dist/esm/engine/frontend-components/app/public-layout-main-container.frontend-component.specification.d.ts.map +1 -1
- package/dist/esm/engine/frontend-components/app/public-layout-main-container.frontend-component.specification.js +4 -2
- package/dist/esm/engine/frontend-components/app/public-layout-main-container.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/app/public-layout-terms.frontend-component.specification.js +4 -4
- package/dist/esm/engine/frontend-components/app/public-layout-terms.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/auth/public-layout-auth-callback.frontend-component.specification.d.ts.map +1 -1
- package/dist/esm/engine/frontend-components/auth/public-layout-auth-callback.frontend-component.specification.js +3 -2
- package/dist/esm/engine/frontend-components/auth/public-layout-auth-callback.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/auth/public-layout-enrollment-required.frontend-component.specification.js +4 -4
- package/dist/esm/engine/frontend-components/auth/public-layout-enrollment-required.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/auth/public-layout-magic-link-verify.frontend-component.specification.js +1 -1
- package/dist/esm/engine/frontend-components/auth/public-layout-magic-link-verify.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/auth/public-layout-organization-onboarding.frontend-component.specification.d.ts +4 -0
- package/dist/esm/engine/frontend-components/auth/public-layout-organization-onboarding.frontend-component.specification.d.ts.map +1 -0
- package/dist/esm/engine/frontend-components/auth/public-layout-organization-onboarding.frontend-component.specification.js +22 -0
- package/dist/esm/engine/frontend-components/auth/public-layout-organization-onboarding.frontend-component.specification.js.map +1 -0
- package/dist/esm/engine/frontend-components/auth/public-layout-user-auth.frontend-component.specification.js +1 -1
- package/dist/esm/engine/frontend-components/auth/public-layout-user-auth.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/auth/public-layout-user-register.frontend-component.specification.d.ts.map +1 -1
- package/dist/esm/engine/frontend-components/auth/public-layout-user-register.frontend-component.specification.js +4 -4
- package/dist/esm/engine/frontend-components/auth/public-layout-user-register.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/billing/billing-invoice-history.frontend-component.specification.js +1 -1
- package/dist/esm/engine/frontend-components/billing/billing-invoice-history.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/billing/billing-plan-change-preview.frontend-component.specification.d.ts +4 -0
- package/dist/esm/engine/frontend-components/billing/billing-plan-change-preview.frontend-component.specification.d.ts.map +1 -0
- package/dist/esm/engine/frontend-components/billing/billing-plan-change-preview.frontend-component.specification.js +21 -0
- package/dist/esm/engine/frontend-components/billing/billing-plan-change-preview.frontend-component.specification.js.map +1 -0
- package/dist/esm/engine/frontend-components/billing/billing-portal-link.frontend-component.specification.js +1 -1
- package/dist/esm/engine/frontend-components/billing/billing-portal-link.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/billing/billing-pricing-table.frontend-component.specification.js +2 -2
- package/dist/esm/engine/frontend-components/billing/billing-pricing-table.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/billing/billing-subscription-status.frontend-component.specification.js +1 -1
- package/dist/esm/engine/frontend-components/billing/billing-subscription-status.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/billing/billing-usage-dashboard.frontend-component.specification.js +1 -1
- package/dist/esm/engine/frontend-components/billing/billing-usage-dashboard.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/data-display/description-list.frontend-component.specification.d.ts.map +1 -1
- package/dist/esm/engine/frontend-components/data-display/description-list.frontend-component.specification.js +20 -2
- package/dist/esm/engine/frontend-components/data-display/description-list.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/data-display/duration.frontend-component.specification.d.ts +5 -0
- package/dist/esm/engine/frontend-components/data-display/duration.frontend-component.specification.d.ts.map +1 -0
- package/dist/esm/engine/frontend-components/data-display/duration.frontend-component.specification.js +177 -0
- package/dist/esm/engine/frontend-components/data-display/duration.frontend-component.specification.js.map +1 -0
- package/dist/esm/engine/frontend-components/data-display/formatters/display-field-address.frontend-component.specification.d.ts +5 -0
- package/dist/esm/engine/frontend-components/data-display/formatters/display-field-address.frontend-component.specification.d.ts.map +1 -0
- package/dist/esm/engine/frontend-components/data-display/formatters/display-field-address.frontend-component.specification.js +22 -0
- package/dist/esm/engine/frontend-components/data-display/formatters/display-field-address.frontend-component.specification.js.map +1 -0
- package/dist/esm/engine/frontend-components/data-display/formatters/display-field-file-document.frontend-component.specification.d.ts.map +1 -1
- package/dist/esm/engine/frontend-components/data-display/formatters/display-field-file-document.frontend-component.specification.js +10 -2
- package/dist/esm/engine/frontend-components/data-display/formatters/display-field-file-document.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/data-display/identifier.frontend-component.specification.d.ts +5 -0
- package/dist/esm/engine/frontend-components/data-display/identifier.frontend-component.specification.d.ts.map +1 -0
- package/dist/esm/engine/frontend-components/data-display/identifier.frontend-component.specification.js +166 -0
- package/dist/esm/engine/frontend-components/data-display/identifier.frontend-component.specification.js.map +1 -0
- package/dist/esm/engine/frontend-components/data-display/kbd.frontend-component.specification.d.ts +5 -0
- package/dist/esm/engine/frontend-components/data-display/kbd.frontend-component.specification.d.ts.map +1 -0
- package/dist/esm/engine/frontend-components/data-display/kbd.frontend-component.specification.js +122 -0
- package/dist/esm/engine/frontend-components/data-display/kbd.frontend-component.specification.js.map +1 -0
- package/dist/esm/engine/frontend-components/data-display/timeline.frontend-component.specification.d.ts +5 -0
- package/dist/esm/engine/frontend-components/data-display/timeline.frontend-component.specification.d.ts.map +1 -0
- package/dist/esm/engine/frontend-components/data-display/timeline.frontend-component.specification.js +152 -0
- package/dist/esm/engine/frontend-components/data-display/timeline.frontend-component.specification.js.map +1 -0
- package/dist/esm/engine/frontend-components/feedback/celebration-overlay.frontend-component.specification.d.ts.map +1 -1
- package/dist/esm/engine/frontend-components/feedback/celebration-overlay.frontend-component.specification.js +13 -0
- package/dist/esm/engine/frontend-components/feedback/celebration-overlay.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/flows-actors/low-level-ai-approval.frontend-component.specification.js +1 -1
- package/dist/esm/engine/frontend-components/flows-actors/low-level-ai-approval.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/form/controls/string/inline-edit-text.frontend-component.specification.d.ts +5 -0
- package/dist/esm/engine/frontend-components/form/controls/string/inline-edit-text.frontend-component.specification.d.ts.map +1 -0
- package/dist/esm/engine/frontend-components/form/controls/string/inline-edit-text.frontend-component.specification.js +92 -0
- package/dist/esm/engine/frontend-components/form/controls/string/inline-edit-text.frontend-component.specification.js.map +1 -0
- package/dist/esm/engine/frontend-components/form/fields/form-field-address.frontend-component.specification.d.ts +5 -0
- package/dist/esm/engine/frontend-components/form/fields/form-field-address.frontend-component.specification.d.ts.map +1 -0
- package/dist/esm/engine/frontend-components/form/fields/form-field-address.frontend-component.specification.js +29 -0
- package/dist/esm/engine/frontend-components/form/fields/form-field-address.frontend-component.specification.js.map +1 -0
- package/dist/esm/engine/frontend-components/form/fields/form-field-enum.frontend-component.specification.js +1 -1
- package/dist/esm/engine/frontend-components/form/fields/form-field-enum.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/form/fields/form-field-file.frontend-component.specification.js +1 -1
- package/dist/esm/engine/frontend-components/form/fields/form-field-file.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/index.d.ts +12 -0
- package/dist/esm/engine/frontend-components/index.d.ts.map +1 -1
- package/dist/esm/engine/frontend-components/index.js +40 -0
- package/dist/esm/engine/frontend-components/index.js.map +1 -1
- package/dist/esm/engine/frontend-components/internal/_tier2-virtual-slot-spec.factory.d.ts +25 -1
- package/dist/esm/engine/frontend-components/internal/_tier2-virtual-slot-spec.factory.d.ts.map +1 -1
- package/dist/esm/engine/frontend-components/internal/_tier2-virtual-slot-spec.factory.js +16 -2
- package/dist/esm/engine/frontend-components/internal/_tier2-virtual-slot-spec.factory.js.map +1 -1
- package/dist/esm/engine/frontend-components/navigation/app-level/navigation-back.frontend-component.specification.js +1 -1
- package/dist/esm/engine/frontend-components/navigation/app-level/navigation-back.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/progression/progression-milestone-tracker.frontend-component.specification.d.ts +9 -0
- package/dist/esm/engine/frontend-components/progression/progression-milestone-tracker.frontend-component.specification.d.ts.map +1 -1
- package/dist/esm/engine/frontend-components/progression/progression-milestone-tracker.frontend-component.specification.js +91 -7
- package/dist/esm/engine/frontend-components/progression/progression-milestone-tracker.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/sections/accordion.frontend-component.specification.d.ts.map +1 -1
- package/dist/esm/engine/frontend-components/sections/accordion.frontend-component.specification.js +9 -3
- package/dist/esm/engine/frontend-components/sections/accordion.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/sections/card.frontend-component.specification.d.ts.map +1 -1
- package/dist/esm/engine/frontend-components/sections/card.frontend-component.specification.js +41 -1
- package/dist/esm/engine/frontend-components/sections/card.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/sections/collapsible.frontend-component.specification.js +2 -2
- package/dist/esm/engine/frontend-components/sections/collapsible.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/sections/tabs.frontend-component.specification.d.ts.map +1 -1
- package/dist/esm/engine/frontend-components/sections/tabs.frontend-component.specification.js +19 -1
- package/dist/esm/engine/frontend-components/sections/tabs.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/typography/link.frontend-component.specification.js +3 -3
- package/dist/esm/engine/frontend-components/typography/link.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/frontend-components/typography/text.frontend-component.specification.d.ts.map +1 -1
- package/dist/esm/engine/frontend-components/typography/text.frontend-component.specification.js +21 -1
- package/dist/esm/engine/frontend-components/typography/text.frontend-component.specification.js.map +1 -1
- package/dist/esm/engine/guidance/resources/progression-state.resource.specification.d.ts +2 -0
- package/dist/esm/engine/guidance/resources/progression-state.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/infrastructure/resources/external-data-pipeline-membership.resource.specification.d.ts +4 -0
- package/dist/esm/engine/infrastructure/resources/external-data-pipeline-membership.resource.specification.d.ts.map +1 -0
- package/dist/esm/engine/infrastructure/resources/external-data-pipeline-membership.resource.specification.js +48 -0
- package/dist/esm/engine/infrastructure/resources/external-data-pipeline-membership.resource.specification.js.map +1 -0
- package/dist/esm/engine/infrastructure/resources/external-data-pipeline-states.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/infrastructure/resources/external-data-pipeline-states.resource.specification.js +3 -2
- package/dist/esm/engine/infrastructure/resources/external-data-pipeline-states.resource.specification.js.map +1 -1
- package/dist/esm/engine/infrastructure/resources/job-executions.resource.specification.d.ts +77 -3
- package/dist/esm/engine/infrastructure/resources/job-executions.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/infrastructure/resources/job-executions.resource.specification.js +11 -3
- package/dist/esm/engine/infrastructure/resources/job-executions.resource.specification.js.map +1 -1
- package/dist/esm/engine/infrastructure/resources/job-payload-storage.resource.specification.d.ts +26 -1
- package/dist/esm/engine/infrastructure/resources/job-payload-storage.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/infrastructure/resources/job-payload-storage.resource.specification.js +17 -8
- package/dist/esm/engine/infrastructure/resources/job-payload-storage.resource.specification.js.map +1 -1
- package/dist/esm/engine/infrastructure/resources/system-of-record-partition-assignments.resource.specification.d.ts +49 -0
- package/dist/esm/engine/infrastructure/resources/system-of-record-partition-assignments.resource.specification.d.ts.map +1 -0
- package/dist/esm/engine/infrastructure/resources/system-of-record-partition-assignments.resource.specification.js +293 -0
- package/dist/esm/engine/infrastructure/resources/system-of-record-partition-assignments.resource.specification.js.map +1 -0
- package/dist/esm/engine/notifications/resources/m2m-webhook-delivery-log.resource.specification.js +5 -5
- package/dist/esm/engine/notifications/resources/m2m-webhook-delivery-log.resource.specification.js.map +1 -1
- package/dist/esm/engine/notifications/resources/notification-badges.resource.specification.d.ts +1 -1
- package/dist/esm/engine/notifications/resources/webhook-config.resource.specification.js +6 -6
- package/dist/esm/engine/notifications/resources/webhook-config.resource.specification.js.map +1 -1
- package/dist/esm/engine/notifications/system-emails/security.system-emails.specification.js +3 -3
- package/dist/esm/engine/notifications/system-emails/security.system-emails.specification.js.map +1 -1
- package/dist/esm/engine/organizations/resources/organization-members.resource.specification.d.ts +1 -1
- package/dist/esm/engine/organizations/resources/organization-profiles.resource.specification.js +2 -2
- package/dist/esm/engine/organizations/resources/organization-profiles.resource.specification.js.map +1 -1
- package/dist/esm/engine/organizations/resources/organization-units.resource.specification.d.ts +3 -1
- package/dist/esm/engine/organizations/resources/organization-units.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/organizations/resources/organization-units.resource.specification.js +27 -5
- package/dist/esm/engine/organizations/resources/organization-units.resource.specification.js.map +1 -1
- package/dist/esm/engine/organizations/resources/organizations.resource.specification.d.ts +1 -1
- package/dist/esm/engine/organizations/resources/organizations.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/organizations/resources/organizations.resource.specification.js +31 -12
- package/dist/esm/engine/organizations/resources/organizations.resource.specification.js.map +1 -1
- package/dist/esm/engine/providers/anthropic.provider.specification.d.ts.map +1 -1
- package/dist/esm/engine/providers/anthropic.provider.specification.js +10 -1
- package/dist/esm/engine/providers/anthropic.provider.specification.js.map +1 -1
- package/dist/esm/engine/providers/apple.provider.specification.d.ts.map +1 -1
- package/dist/esm/engine/providers/apple.provider.specification.js +12 -1
- package/dist/esm/engine/providers/apple.provider.specification.js.map +1 -1
- package/dist/esm/engine/providers/email-preview.provider.specification.d.ts.map +1 -1
- package/dist/esm/engine/providers/email-preview.provider.specification.js +9 -1
- package/dist/esm/engine/providers/email-preview.provider.specification.js.map +1 -1
- package/dist/esm/engine/providers/github.provider.specification.d.ts.map +1 -1
- package/dist/esm/engine/providers/github.provider.specification.js +12 -1
- package/dist/esm/engine/providers/github.provider.specification.js.map +1 -1
- package/dist/esm/engine/providers/google.provider.specification.d.ts.map +1 -1
- package/dist/esm/engine/providers/google.provider.specification.js +12 -1
- package/dist/esm/engine/providers/google.provider.specification.js.map +1 -1
- package/dist/esm/engine/providers/grok.provider.specification.d.ts.map +1 -1
- package/dist/esm/engine/providers/grok.provider.specification.js +10 -1
- package/dist/esm/engine/providers/grok.provider.specification.js.map +1 -1
- package/dist/esm/engine/providers/microsoft.provider.specification.d.ts.map +1 -1
- package/dist/esm/engine/providers/microsoft.provider.specification.js +22 -1
- package/dist/esm/engine/providers/microsoft.provider.specification.js.map +1 -1
- package/dist/esm/engine/providers/mistral.provider.specification.d.ts.map +1 -1
- package/dist/esm/engine/providers/mistral.provider.specification.js +10 -1
- package/dist/esm/engine/providers/mistral.provider.specification.js.map +1 -1
- package/dist/esm/engine/providers/openai.provider.specification.d.ts.map +1 -1
- package/dist/esm/engine/providers/openai.provider.specification.js +10 -1
- package/dist/esm/engine/providers/openai.provider.specification.js.map +1 -1
- package/dist/esm/engine/providers/opencode.provider.specification.d.ts.map +1 -1
- package/dist/esm/engine/providers/opencode.provider.specification.js +9 -1
- package/dist/esm/engine/providers/opencode.provider.specification.js.map +1 -1
- package/dist/esm/engine/providers/perplexity.provider.specification.d.ts.map +1 -1
- package/dist/esm/engine/providers/perplexity.provider.specification.js +10 -1
- package/dist/esm/engine/providers/perplexity.provider.specification.js.map +1 -1
- package/dist/esm/engine/providers/resend.provider.specification.d.ts.map +1 -1
- package/dist/esm/engine/providers/resend.provider.specification.js +10 -1
- package/dist/esm/engine/providers/resend.provider.specification.js.map +1 -1
- package/dist/esm/engine/providers/stripe.provider.specification.d.ts.map +1 -1
- package/dist/esm/engine/providers/stripe.provider.specification.js +10 -1
- package/dist/esm/engine/providers/stripe.provider.specification.js.map +1 -1
- package/dist/esm/engine/providers/twilio.provider.specification.d.ts.map +1 -1
- package/dist/esm/engine/providers/twilio.provider.specification.js +10 -1
- package/dist/esm/engine/providers/twilio.provider.specification.js.map +1 -1
- package/dist/esm/engine/roles/app-audit-evidence-reader.role.specification.d.ts +2 -0
- package/dist/esm/engine/roles/app-audit-evidence-reader.role.specification.d.ts.map +1 -0
- package/dist/esm/engine/roles/app-audit-evidence-reader.role.specification.js +21 -0
- package/dist/esm/engine/roles/app-audit-evidence-reader.role.specification.js.map +1 -0
- package/dist/esm/engine/roles/index.d.ts +4 -3
- package/dist/esm/engine/roles/index.d.ts.map +1 -1
- package/dist/esm/engine/roles/index.js +6 -4
- package/dist/esm/engine/roles/index.js.map +1 -1
- package/dist/esm/engine/users/resources/anonymous-users.resource.specification.d.ts +5 -3
- package/dist/esm/engine/users/resources/anonymous-users.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/users/resources/anonymous-users.resource.specification.js +2 -2
- package/dist/esm/engine/users/resources/anonymous-users.resource.specification.js.map +1 -1
- package/dist/esm/engine/users/resources/inbound-contacts.resource.specification.d.ts +2 -1
- package/dist/esm/engine/users/resources/inbound-contacts.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/users/resources/inbound-contacts.resource.specification.js +2 -2
- package/dist/esm/engine/users/resources/inbound-contacts.resource.specification.js.map +1 -1
- package/dist/esm/engine/users/resources/user-identity-links.resource.specification.d.ts +1 -0
- package/dist/esm/engine/users/resources/user-identity-links.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/users/resources/user-identity-links.resource.specification.js +8 -3
- package/dist/esm/engine/users/resources/user-identity-links.resource.specification.js.map +1 -1
- package/dist/esm/engine/users/resources/user-preferences-api-reference.examples.d.ts +2 -2
- package/dist/esm/engine/users/resources/user-preferences-api-reference.examples.js +2 -2
- package/dist/esm/engine/users/resources/user-preferences-api-reference.examples.js.map +1 -1
- package/dist/esm/engine/users/resources/user-preferences.resource.specification.d.ts +5 -5
- package/dist/esm/engine/users/resources/user-preferences.resource.specification.js +1 -1
- package/dist/esm/engine/users/resources/user-preferences.resource.specification.js.map +1 -1
- package/dist/esm/engine/users/resources/user-self-preferences.resource.specification.d.ts +4 -4
- package/dist/esm/engine/users/resources/user-self-preferences.resource.specification.js +3 -3
- package/dist/esm/engine/users/resources/user-self-preferences.resource.specification.js.map +1 -1
- package/dist/esm/engine/users/resources/user-self.resource.specification.d.ts +1 -0
- package/dist/esm/engine/users/resources/user-self.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/users/resources/user-self.resource.specification.js +1 -1
- package/dist/esm/engine/users/resources/user-self.resource.specification.js.map +1 -1
- package/dist/esm/engine/users/resources/users.resource.specification.d.ts +1 -0
- package/dist/esm/engine/users/resources/users.resource.specification.d.ts.map +1 -1
- package/dist/esm/engine/users/resources/users.resource.specification.js +2 -2
- package/dist/esm/engine/users/resources/users.resource.specification.js.map +1 -1
- package/dist/esm/index.d.ts +39 -0
- package/dist/esm/index.d.ts.map +1 -1
- package/dist/esm/index.js +39 -0
- package/dist/esm/index.js.map +1 -1
- package/dist/esm/technical-documentation/application-documentation-chapters.schemas.d.ts +134 -0
- package/dist/esm/technical-documentation/application-documentation-chapters.schemas.d.ts.map +1 -0
- package/dist/esm/technical-documentation/application-documentation-chapters.schemas.js +142 -0
- package/dist/esm/technical-documentation/application-documentation-chapters.schemas.js.map +1 -0
- package/dist/esm/technical-documentation/application-documentation-plan-generation.schemas.d.ts +35 -0
- package/dist/esm/technical-documentation/application-documentation-plan-generation.schemas.d.ts.map +1 -0
- package/dist/esm/technical-documentation/application-documentation-plan-generation.schemas.js +45 -0
- package/dist/esm/technical-documentation/application-documentation-plan-generation.schemas.js.map +1 -0
- package/dist/esm/technical-documentation/application-documentation-plan-validation.d.ts +33 -0
- package/dist/esm/technical-documentation/application-documentation-plan-validation.d.ts.map +1 -0
- package/dist/esm/technical-documentation/application-documentation-plan-validation.js +77 -0
- package/dist/esm/technical-documentation/application-documentation-plan-validation.js.map +1 -0
- package/dist/esm/technical-documentation/application-documentation-plan.family-aspects.d.ts +3 -0
- package/dist/esm/technical-documentation/application-documentation-plan.family-aspects.d.ts.map +1 -0
- package/dist/esm/technical-documentation/application-documentation-plan.family-aspects.js +40 -0
- package/dist/esm/technical-documentation/application-documentation-plan.family-aspects.js.map +1 -0
- package/dist/esm/technical-documentation/application-documentation-plan.schemas.d.ts +122 -0
- package/dist/esm/technical-documentation/application-documentation-plan.schemas.d.ts.map +1 -0
- package/dist/esm/technical-documentation/application-documentation-plan.schemas.js +138 -0
- package/dist/esm/technical-documentation/application-documentation-plan.schemas.js.map +1 -0
- package/dist/esm/technical-documentation/engine-documentation-specification-catalog.companion.d.ts.map +1 -1
- package/dist/esm/technical-documentation/engine-documentation-specification-catalog.companion.js +7 -15
- package/dist/esm/technical-documentation/engine-documentation-specification-catalog.companion.js.map +1 -1
- package/dist/esm/technical-documentation/technical-documentation-assets.schemas.js +1 -1
- package/dist/esm/technical-documentation/technical-documentation-assets.schemas.js.map +1 -1
- package/dist/esm/technical-documentation/technical-documentation-capture.schemas.js +1 -1
- package/dist/esm/technical-documentation/technical-documentation-capture.schemas.js.map +1 -1
- package/dist/esm/technical-documentation/technical-documentation-common.schemas.js +1 -1
- package/dist/esm/technical-documentation/technical-documentation-common.schemas.js.map +1 -1
- package/dist/esm/technical-documentation/technical-documentation-evidence.schemas.js +1 -1
- package/dist/esm/technical-documentation/technical-documentation-evidence.schemas.js.map +1 -1
- package/dist/esm/technical-documentation/technical-documentation-lifecycle.schemas.js +1 -1
- package/dist/esm/technical-documentation/technical-documentation-lifecycle.schemas.js.map +1 -1
- package/dist/esm/technical-documentation/technical-documentation-publication.schemas.js +1 -1
- package/dist/esm/technical-documentation/technical-documentation-publication.schemas.js.map +1 -1
- package/dist/esm/technical-documentation/technical-documentation-units.schemas.d.ts +14 -0
- package/dist/esm/technical-documentation/technical-documentation-units.schemas.d.ts.map +1 -1
- package/dist/esm/technical-documentation/technical-documentation-units.schemas.js +16 -3
- package/dist/esm/technical-documentation/technical-documentation-units.schemas.js.map +1 -1
- package/dist/esm/technical-documentation.exports.d.ts +4 -0
- package/dist/esm/technical-documentation.exports.d.ts.map +1 -1
- package/dist/esm/technical-documentation.exports.js +24 -0
- package/dist/esm/technical-documentation.exports.js.map +1 -1
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/package.json +8 -13
- package/dist/esm/application-creation/application-coding-tasks.application-creation.schemas.d.ts +0 -103
- package/dist/esm/application-creation/application-coding-tasks.application-creation.schemas.d.ts.map +0 -1
- package/dist/esm/application-creation/application-coding-tasks.application-creation.schemas.js +0 -76
- package/dist/esm/application-creation/application-coding-tasks.application-creation.schemas.js.map +0 -1
- package/dist/esm/application-creation/application-specification-family-identity.application-creation.schemas.d.ts +0 -108
- package/dist/esm/application-creation/application-specification-family-identity.application-creation.schemas.d.ts.map +0 -1
- package/dist/esm/application-creation/application-specification-family-identity.application-creation.schemas.js +0 -119
- package/dist/esm/application-creation/application-specification-family-identity.application-creation.schemas.js.map +0 -1
- package/dist/esm/application-creation-playbook-runtime.exports.d.ts +0 -3
- package/dist/esm/application-creation-playbook-runtime.exports.d.ts.map +0 -1
- package/dist/esm/application-creation-playbook-runtime.exports.js +0 -3
- package/dist/esm/application-creation-playbook-runtime.exports.js.map +0 -1
- package/dist/esm/engine/frontend-components/billing/billing-promotion-code-input.frontend-component.specification.d.ts +0 -0
- package/dist/esm/engine/frontend-components/billing/billing-promotion-code-input.frontend-component.specification.d.ts.map +0 -0
- package/dist/esm/engine/frontend-components/billing/billing-promotion-code-input.frontend-component.specification.js +0 -0
- package/dist/esm/engine/frontend-components/billing/billing-promotion-code-input.frontend-component.specification.js.map +0 -0
|
@@ -1,4 +1,5 @@
|
|
|
1
1
|
import { z } from "zod";
|
|
2
|
+
import '@wildo-ai/zod-decorators';
|
|
2
3
|
import { type ApplicationDocumentFactDeclarationSet } from "../../application-creation/application-document-fact-specification.application-creation.schemas";
|
|
3
4
|
/**
|
|
4
5
|
* A proposed governed-document draft — a privacy notice or service terms — as CONTENT.
|
|
@@ -33,6 +34,79 @@ import { type ApplicationDocumentFactDeclarationSet } from "../../application-cr
|
|
|
33
34
|
* a provider answer would pass generation and fail the family parse it is normalized into.
|
|
34
35
|
*/
|
|
35
36
|
export declare const ComplianceDocumentNamespacedRefSchema: z.ZodString;
|
|
37
|
+
/**
|
|
38
|
+
* The one namespace `sourcePolicyRefs` may use — see the field's own JSDoc for the measurement.
|
|
39
|
+
*
|
|
40
|
+
* Exported so the family schema and its generation contract share ONE definition, for the reason the
|
|
41
|
+
* ref regex above is shared: two copies of a namespace rule is two things that can disagree, and the
|
|
42
|
+
* disagreement is invisible until a provider answer passes generation and fails the family parse it is
|
|
43
|
+
* normalized into.
|
|
44
|
+
*/
|
|
45
|
+
export declare const COMPLIANCE_DOCUMENT_SOURCE_POLICY_NAMESPACE = "policy:";
|
|
46
|
+
/**
|
|
47
|
+
* Which `sourcePolicyRefs` entries are not policy refs — the check both schemas apply.
|
|
48
|
+
*
|
|
49
|
+
* Returns the offenders rather than a boolean so each message can NAME the ref the author must fix. A
|
|
50
|
+
* generation rejection goes back to the drafting model verbatim as a retry finding, and "one of your
|
|
51
|
+
* source policy refs is wrong" costs an attempt without telling it which.
|
|
52
|
+
*/
|
|
53
|
+
export declare const nonPolicySourceRefs: (sourcePolicyRefs: readonly string[]) => readonly string[];
|
|
54
|
+
/**
|
|
55
|
+
* The message a clause citing a fact authority as a source policy gets, at BOTH schemas.
|
|
56
|
+
*
|
|
57
|
+
* Names the FIX rather than the fault, like every other message in this family, because a generation
|
|
58
|
+
* rejection goes back to the drafting model verbatim as a retry finding and a message that only says
|
|
59
|
+
* "wrong" costs an attempt.
|
|
60
|
+
*
|
|
61
|
+
* It used to carry a second job. The drafting method — the playbook's `method.md`, which this package
|
|
62
|
+
* does not own — told every model to put `document-fact-authority:<slug>` here, so this message was
|
|
63
|
+
* the only surface correcting guidance the drafter had just been given, and the first attempt of every
|
|
64
|
+
* draft was rejected for following it. That prose was corrected on 2026-09-10 and now says the field
|
|
65
|
+
* takes `policy:` only and is empty for a fact-backed clause. Keep the message naming the fix anyway:
|
|
66
|
+
* the two documents are owned by different packages and can drift again, and a model that arrives here
|
|
67
|
+
* with a wrong ref still needs to be told what to write instead.
|
|
68
|
+
*/
|
|
69
|
+
export declare const sourcePolicyNamespaceMessage: (clauseRef: string, offenders: readonly string[]) => string;
|
|
70
|
+
/**
|
|
71
|
+
* The one namespace `evidenceRefs` may use: a JUDGED RUN in the application's own assurance repository.
|
|
72
|
+
*
|
|
73
|
+
* Not a finding, not a measurement, not a demand. A run is the unit that carries what a citation must
|
|
74
|
+
* state to be worth anything — the demand judged, the verdict, the window it covers, the framework
|
|
75
|
+
* revision it was judged at, and whether the judge was calibrated — and it is the only one of the four
|
|
76
|
+
* that is committed and addressable. Citing a measurement would cite a number with no verdict over it;
|
|
77
|
+
* citing a finding would cite a defect rather than the pass that answers a clause.
|
|
78
|
+
*/
|
|
79
|
+
export declare const COMPLIANCE_DOCUMENT_EVIDENCE_NAMESPACE = "assurance-run:";
|
|
80
|
+
/**
|
|
81
|
+
* The claim policy under which a document may cite NO internal evidence.
|
|
82
|
+
*
|
|
83
|
+
* Named here rather than compared inline because it is the whole of the public/internal boundary for
|
|
84
|
+
* #297, and because the check is stated as "anything that is not this is internal": a policy the caller
|
|
85
|
+
* could not resolve admits nothing, and a seventh public document is covered the day it is catalogued.
|
|
86
|
+
*/
|
|
87
|
+
export declare const COMPLIANCE_DOCUMENT_PUBLIC_CLAIM_POLICY_REF = "document-claim-policy:public-safe-baseline";
|
|
88
|
+
/**
|
|
89
|
+
* Which `evidenceRefs` entries are not assurance-run refs — the check both schemas apply.
|
|
90
|
+
*
|
|
91
|
+
* ## Why the FIELD is a plain string and this is the shape rule
|
|
92
|
+
*
|
|
93
|
+
* The sibling ref fields use `NamespacedRefSchema`, whose regex is lowercase-only with one colon. A real
|
|
94
|
+
* run ref satisfies neither half: `assurance-run:wonder-todos.2026-09-22:WILDO.ACCESS.LEAST_PRIVILEGE:operation-role-declaration`
|
|
95
|
+
* carries three colons, uppercase objective names and an underscore, because it is composed from the
|
|
96
|
+
* application, the date, the objective and the demand. Typing the field as a namespaced ref would have
|
|
97
|
+
* made every genuine citation unrepresentable — caught by the first test written against a real ref, and
|
|
98
|
+
* the reason this rule is a predicate rather than a regex on the field.
|
|
99
|
+
*
|
|
100
|
+
* Stated as a prefix check rather than a full grammar deliberately: the run ref's composition belongs to
|
|
101
|
+
* the assurance plane, which may extend it, and a second grammar here would be a copy that can disagree
|
|
102
|
+
* with the one place that mints them. What this owes is that the citation names a RUN — the rest is the
|
|
103
|
+
* resolution check, which asks the repository itself.
|
|
104
|
+
*/
|
|
105
|
+
export declare const nonAssuranceRunEvidenceRefs: (evidenceRefs: readonly string[]) => readonly string[];
|
|
106
|
+
/** The message a clause citing something other than a judged run as evidence gets, at BOTH schemas. */
|
|
107
|
+
export declare const evidenceNamespaceMessage: (clauseRef: string, offenders: readonly string[]) => string;
|
|
108
|
+
/** The message a clause naming no source at all gets, at BOTH schemas. */
|
|
109
|
+
export declare const clauseNamesNoSourceMessage: (clauseRef: string) => string;
|
|
36
110
|
/**
|
|
37
111
|
* How completely a single statement is established — and, when it is not, WHO can close it.
|
|
38
112
|
*
|
|
@@ -89,6 +163,46 @@ export declare const ComplianceStatementIncompletenessSchema: z.ZodObject<{
|
|
|
89
163
|
* configuration surface to edit. A row whose remedy is unnamed is a row nobody picks up.
|
|
90
164
|
*/
|
|
91
165
|
closedBy: z.ZodString;
|
|
166
|
+
/**
|
|
167
|
+
* The declared facts whose ARRIVAL would close this gap — the derivable half of `needs`.
|
|
168
|
+
*
|
|
169
|
+
* ## Why prose alone rots, measured
|
|
170
|
+
*
|
|
171
|
+
* `needs` and `closedBy` are prose, and prose asserting the ABSENCE of a configuration value is true
|
|
172
|
+
* at the instant it is written and false the instant somebody declares that value. Nothing observes
|
|
173
|
+
* the transition. Wonder CRM's `clause:purposes-and-lawful-bases-not-declared` said *"The lawful
|
|
174
|
+
* basis for each purpose has not yet been declared"* and named `operatorComplianceIdentity.lawfulBases`
|
|
175
|
+
* as what it needed; the application declared exactly that on 2026-09-02, and the notice went on
|
|
176
|
+
* telling a reader something untrue about the application's own configuration for a week. It was found
|
|
177
|
+
* by a human reading the file — the same way the dangling fact refs were found, and for the same
|
|
178
|
+
* reason: a marked clause is precisely the one nobody re-reads.
|
|
179
|
+
*
|
|
180
|
+
* So a clause that asserts an absence owes a DERIVATION rather than a sentence
|
|
181
|
+
* (`.claude/rules/derive-before-you-ask.md`). This field is that derivation's subject: name the fact
|
|
182
|
+
* whose absence you are asserting, and `validateComplianceDocumentCandidateFactBinding` reports the
|
|
183
|
+
* clause as STALE the moment the application declares it — total over
|
|
184
|
+
* {@link ComplianceDocumentFactAvailability}, so an availability member added tomorrow forces an
|
|
185
|
+
* answer here rather than being silently omitted.
|
|
186
|
+
*
|
|
187
|
+
* ## Optional, and the residual is stated rather than hidden
|
|
188
|
+
*
|
|
189
|
+
* `.optional()` because not every gap is expressible as a declared fact. Two of Wonder CRM's five
|
|
190
|
+
* marked clauses wait on something no fact family models — an effective-date decision, a security
|
|
191
|
+
* summary the framework cannot yet express — and requiring a ref there would refuse a legitimately
|
|
192
|
+
* marked clause with a remedy that does not exist.
|
|
193
|
+
*
|
|
194
|
+
* **The residual is therefore real and is named here so it is not mistaken for coverage: a clause
|
|
195
|
+
* that names no awaited fact can still rot, and nothing will say so.** Narrowing it means modelling
|
|
196
|
+
* more gaps as facts, not tightening this field. The GENERATION contract states it as
|
|
197
|
+
* required-and-nullable for the reason every sibling field there does — an omitted key and a
|
|
198
|
+
* considered "no fact models this" are different answers, and a model that may drop the key gives no
|
|
199
|
+
* way to tell them apart.
|
|
200
|
+
*
|
|
201
|
+
* Not the same field as the clause's `factRefs`. `factRefs` are the facts a clause RESTS ON; these
|
|
202
|
+
* are the facts it is WAITING FOR, and a clause routinely has both — Wonder CRM's lawful-bases clause
|
|
203
|
+
* rests on `document-fact:processing-purposes` while waiting on the bases.
|
|
204
|
+
*/
|
|
205
|
+
awaitingFactRefs: z.ZodOptional<z.ZodArray<z.ZodString>>;
|
|
92
206
|
}, z.core.$strict>;
|
|
93
207
|
export type ComplianceStatementIncompleteness = z.infer<typeof ComplianceStatementIncompletenessSchema>;
|
|
94
208
|
/** One clause of the draft: the prose a reader sees, and what it rests on. */
|
|
@@ -129,7 +243,7 @@ export declare const ComplianceDocumentCandidateClauseSchema: z.ZodObject<{
|
|
|
129
243
|
* contract must require it explicitly instead: a model permitted to omit the key would silently
|
|
130
244
|
* claim `DERIVED`, which is the one direction that lets invention back in.
|
|
131
245
|
*/
|
|
132
|
-
completeness: z.ZodDefault<z.ZodEnum<typeof ComplianceStatementCompleteness
|
|
246
|
+
completeness: z.ZodDefault<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<z.ZodEnum<typeof ComplianceStatementCompleteness>>>;
|
|
133
247
|
/** Required when `completeness` is not `DERIVED`, forbidden when it is — see the superRefine below. */
|
|
134
248
|
incompleteness: z.ZodOptional<z.ZodObject<{
|
|
135
249
|
/** The missing information, in the reader's terms — not "factRef absent" but "how long we keep it". */
|
|
@@ -139,13 +253,125 @@ export declare const ComplianceDocumentCandidateClauseSchema: z.ZodObject<{
|
|
|
139
253
|
* configuration surface to edit. A row whose remedy is unnamed is a row nobody picks up.
|
|
140
254
|
*/
|
|
141
255
|
closedBy: z.ZodString;
|
|
256
|
+
/**
|
|
257
|
+
* The declared facts whose ARRIVAL would close this gap — the derivable half of `needs`.
|
|
258
|
+
*
|
|
259
|
+
* ## Why prose alone rots, measured
|
|
260
|
+
*
|
|
261
|
+
* `needs` and `closedBy` are prose, and prose asserting the ABSENCE of a configuration value is true
|
|
262
|
+
* at the instant it is written and false the instant somebody declares that value. Nothing observes
|
|
263
|
+
* the transition. Wonder CRM's `clause:purposes-and-lawful-bases-not-declared` said *"The lawful
|
|
264
|
+
* basis for each purpose has not yet been declared"* and named `operatorComplianceIdentity.lawfulBases`
|
|
265
|
+
* as what it needed; the application declared exactly that on 2026-09-02, and the notice went on
|
|
266
|
+
* telling a reader something untrue about the application's own configuration for a week. It was found
|
|
267
|
+
* by a human reading the file — the same way the dangling fact refs were found, and for the same
|
|
268
|
+
* reason: a marked clause is precisely the one nobody re-reads.
|
|
269
|
+
*
|
|
270
|
+
* So a clause that asserts an absence owes a DERIVATION rather than a sentence
|
|
271
|
+
* (`.claude/rules/derive-before-you-ask.md`). This field is that derivation's subject: name the fact
|
|
272
|
+
* whose absence you are asserting, and `validateComplianceDocumentCandidateFactBinding` reports the
|
|
273
|
+
* clause as STALE the moment the application declares it — total over
|
|
274
|
+
* {@link ComplianceDocumentFactAvailability}, so an availability member added tomorrow forces an
|
|
275
|
+
* answer here rather than being silently omitted.
|
|
276
|
+
*
|
|
277
|
+
* ## Optional, and the residual is stated rather than hidden
|
|
278
|
+
*
|
|
279
|
+
* `.optional()` because not every gap is expressible as a declared fact. Two of Wonder CRM's five
|
|
280
|
+
* marked clauses wait on something no fact family models — an effective-date decision, a security
|
|
281
|
+
* summary the framework cannot yet express — and requiring a ref there would refuse a legitimately
|
|
282
|
+
* marked clause with a remedy that does not exist.
|
|
283
|
+
*
|
|
284
|
+
* **The residual is therefore real and is named here so it is not mistaken for coverage: a clause
|
|
285
|
+
* that names no awaited fact can still rot, and nothing will say so.** Narrowing it means modelling
|
|
286
|
+
* more gaps as facts, not tightening this field. The GENERATION contract states it as
|
|
287
|
+
* required-and-nullable for the reason every sibling field there does — an omitted key and a
|
|
288
|
+
* considered "no fact models this" are different answers, and a model that may drop the key gives no
|
|
289
|
+
* way to tell them apart.
|
|
290
|
+
*
|
|
291
|
+
* Not the same field as the clause's `factRefs`. `factRefs` are the facts a clause RESTS ON; these
|
|
292
|
+
* are the facts it is WAITING FOR, and a clause routinely has both — Wonder CRM's lawful-bases clause
|
|
293
|
+
* rests on `document-fact:processing-purposes` while waiting on the bases.
|
|
294
|
+
*/
|
|
295
|
+
awaitingFactRefs: z.ZodOptional<z.ZodArray<z.ZodString>>;
|
|
142
296
|
}, z.core.$strict>>;
|
|
143
297
|
/** The document facts this clause asserts. A clause that asserts none cites none — an empty list is valid. */
|
|
144
298
|
factRefs: z.ZodArray<z.ZodString>;
|
|
145
|
-
/**
|
|
299
|
+
/**
|
|
300
|
+
* The application POLICY AREAS this clause is sourced from — `policy:retention`, `policy:security-controls`.
|
|
301
|
+
*
|
|
302
|
+
* ## Two corrections, and the second is what the field is for
|
|
303
|
+
*
|
|
304
|
+
* This carried `.min(1)` and no namespace constraint until 2026-09-09. Measured on Wonder CRM's
|
|
305
|
+
* landed privacy notice: **37 refs, 32 of them in the `document-fact-authority:` namespace, and 0 of
|
|
306
|
+
* those 32 resolved to any authority the application declares.** They were not a different
|
|
307
|
+
* vocabulary — every one was a NEAR-MISS of a real declared authority, three of them a literal
|
|
308
|
+
* prefix of one (`…governance-system-boundaries-and-lifecycle` for the declared
|
|
309
|
+
* `…governance-system-boundaries`). The drafter had invented each slug rather than reading it,
|
|
310
|
+
* exactly the rename drift that broke the fact citations one level down, and nothing could see it
|
|
311
|
+
* because this field resolves against nothing.
|
|
312
|
+
*
|
|
313
|
+
* **`.min(1)` is what produced them.** Per clause, the 32 were a 1:1 restatement of that clause's own
|
|
314
|
+
* `factRefs` in longer phrasing — the operator-identity clause cites `document-fact:controller-and-contact`
|
|
315
|
+
* and `document-fact:operator-legal-identity`, then names those same two subjects again here. A clause
|
|
316
|
+
* resting on declared facts already NAMES its source; the constraint demanded a second naming, and the
|
|
317
|
+
* only material available was the facts it had just cited. So the field's own guard manufactured the
|
|
318
|
+
* duplication it was meant to prevent.
|
|
319
|
+
*
|
|
320
|
+
* ## What it is now
|
|
321
|
+
*
|
|
322
|
+
* A fact authority is reached THROUGH `factRefs` — the facts file declares each fact's
|
|
323
|
+
* `authority.authorityRef`, so restating it here is hand-maintaining a derivable value at N sites
|
|
324
|
+
* (`.claude/rules/derive-before-you-ask.md`). This field therefore carries the `policy:` namespace
|
|
325
|
+
* only, and is EMPTY for a clause whose source is its facts.
|
|
326
|
+
*
|
|
327
|
+
* The guard that matters survives, stated over both fields rather than over this one: a clause must
|
|
328
|
+
* name a source — at least one `factRef` or at least one `sourcePolicyRef` — because prose with no
|
|
329
|
+
* source is invention. See the `superRefine` below.
|
|
330
|
+
*
|
|
331
|
+
* **What this does NOT close:** `policy:*` names a policy AREA, not a record, and no registry
|
|
332
|
+
* resolves it. That is honest — a topic label is what a reviewer needs when a clause rests on no
|
|
333
|
+
* fact — but it means this field is still unresolvable, and the check below constrains its SHAPE
|
|
334
|
+
* rather than its referent.
|
|
335
|
+
*/
|
|
146
336
|
sourcePolicyRefs: z.ZodArray<z.ZodString>;
|
|
147
|
-
/**
|
|
337
|
+
/**
|
|
338
|
+
* The claim guards a reviewer checks this clause against: the drafter's own restrictions, plus — derived
|
|
339
|
+
* when a generated candidate is normalized — the catalog guard of every blueprint clause this clause
|
|
340
|
+
* `satisfiesClauseRefs` (#1452). A hand-authored candidate supplies both itself.
|
|
341
|
+
*/
|
|
148
342
|
claimGuardRefs: z.ZodArray<z.ZodString>;
|
|
343
|
+
/**
|
|
344
|
+
* The judged runs in this application's OWN assurance repository that this clause rests on (#297).
|
|
345
|
+
*
|
|
346
|
+
* ## What it is for, and the one thing it is not
|
|
347
|
+
*
|
|
348
|
+
* A governance document is where an operator says what its controls DO, and until this existed no
|
|
349
|
+
* clause could say that at all: assurance findings and clean passes were produced, judged, committed
|
|
350
|
+
* — and citable by nothing. So an operating statement had exactly two forms, an unsupported claim or
|
|
351
|
+
* a mark, and the mark was correct.
|
|
352
|
+
*
|
|
353
|
+
* It is SELF-ATTESTED INTERNAL EVIDENCE and must never read as anything else. The application judged
|
|
354
|
+
* its own product with its own harness; that is worth stating to an assurance reader inside the
|
|
355
|
+
* operator's organisation, and it is not an audit, an attestation or an independent opinion. The
|
|
356
|
+
* brief that carries these runs to a drafter labels them so, and the claim guards refuse the
|
|
357
|
+
* sentence that would launder them.
|
|
358
|
+
*
|
|
359
|
+
* ## Why it is OPTIONAL and empty is the norm
|
|
360
|
+
*
|
|
361
|
+
* Almost every clause rests on facts, and a clause that cites a run it does not need has made its
|
|
362
|
+
* reader check a citation for nothing. Empty is not a gap here — it is the ordinary case — which is
|
|
363
|
+
* why this array is absent from the "names no source" rule: a fact or a policy area is what sources
|
|
364
|
+
* a statement, and a run is what SUPPORTS one that asserts operation.
|
|
365
|
+
*
|
|
366
|
+
* ## Where it is refused
|
|
367
|
+
*
|
|
368
|
+
* Two refusals, and both live outside this schema because both need something it cannot see. A ref
|
|
369
|
+
* that resolves to no committed run is refused by the binding validator, which can read the
|
|
370
|
+
* repository. ANY entry in a document under `document-claim-policy:public-safe-baseline` is refused
|
|
371
|
+
* there too — the claim POLICY decides, never the namespace, because what makes a public operating
|
|
372
|
+
* claim wrong is the reader it reaches rather than the evidence behind it (Paul, 2026-09-21).
|
|
373
|
+
*/
|
|
374
|
+
evidenceRefs: z.ZodOptional<z.ZodArray<z.ZodString>>;
|
|
149
375
|
}, z.core.$strict>;
|
|
150
376
|
export type ComplianceDocumentCandidateClause = z.infer<typeof ComplianceDocumentCandidateClauseSchema>;
|
|
151
377
|
/** One titled section, whose clauses are contiguously ordered. */
|
|
@@ -245,7 +471,7 @@ export declare const ComplianceDocumentCandidateSectionSchema: z.ZodObject<{
|
|
|
245
471
|
* contract must require it explicitly instead: a model permitted to omit the key would silently
|
|
246
472
|
* claim `DERIVED`, which is the one direction that lets invention back in.
|
|
247
473
|
*/
|
|
248
|
-
completeness: z.ZodDefault<z.ZodEnum<typeof ComplianceStatementCompleteness
|
|
474
|
+
completeness: z.ZodDefault<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<z.ZodEnum<typeof ComplianceStatementCompleteness>>>;
|
|
249
475
|
/** Required when `completeness` is not `DERIVED`, forbidden when it is — see the superRefine below. */
|
|
250
476
|
incompleteness: z.ZodOptional<z.ZodObject<{
|
|
251
477
|
/** The missing information, in the reader's terms — not "factRef absent" but "how long we keep it". */
|
|
@@ -255,13 +481,125 @@ export declare const ComplianceDocumentCandidateSectionSchema: z.ZodObject<{
|
|
|
255
481
|
* configuration surface to edit. A row whose remedy is unnamed is a row nobody picks up.
|
|
256
482
|
*/
|
|
257
483
|
closedBy: z.ZodString;
|
|
484
|
+
/**
|
|
485
|
+
* The declared facts whose ARRIVAL would close this gap — the derivable half of `needs`.
|
|
486
|
+
*
|
|
487
|
+
* ## Why prose alone rots, measured
|
|
488
|
+
*
|
|
489
|
+
* `needs` and `closedBy` are prose, and prose asserting the ABSENCE of a configuration value is true
|
|
490
|
+
* at the instant it is written and false the instant somebody declares that value. Nothing observes
|
|
491
|
+
* the transition. Wonder CRM's `clause:purposes-and-lawful-bases-not-declared` said *"The lawful
|
|
492
|
+
* basis for each purpose has not yet been declared"* and named `operatorComplianceIdentity.lawfulBases`
|
|
493
|
+
* as what it needed; the application declared exactly that on 2026-09-02, and the notice went on
|
|
494
|
+
* telling a reader something untrue about the application's own configuration for a week. It was found
|
|
495
|
+
* by a human reading the file — the same way the dangling fact refs were found, and for the same
|
|
496
|
+
* reason: a marked clause is precisely the one nobody re-reads.
|
|
497
|
+
*
|
|
498
|
+
* So a clause that asserts an absence owes a DERIVATION rather than a sentence
|
|
499
|
+
* (`.claude/rules/derive-before-you-ask.md`). This field is that derivation's subject: name the fact
|
|
500
|
+
* whose absence you are asserting, and `validateComplianceDocumentCandidateFactBinding` reports the
|
|
501
|
+
* clause as STALE the moment the application declares it — total over
|
|
502
|
+
* {@link ComplianceDocumentFactAvailability}, so an availability member added tomorrow forces an
|
|
503
|
+
* answer here rather than being silently omitted.
|
|
504
|
+
*
|
|
505
|
+
* ## Optional, and the residual is stated rather than hidden
|
|
506
|
+
*
|
|
507
|
+
* `.optional()` because not every gap is expressible as a declared fact. Two of Wonder CRM's five
|
|
508
|
+
* marked clauses wait on something no fact family models — an effective-date decision, a security
|
|
509
|
+
* summary the framework cannot yet express — and requiring a ref there would refuse a legitimately
|
|
510
|
+
* marked clause with a remedy that does not exist.
|
|
511
|
+
*
|
|
512
|
+
* **The residual is therefore real and is named here so it is not mistaken for coverage: a clause
|
|
513
|
+
* that names no awaited fact can still rot, and nothing will say so.** Narrowing it means modelling
|
|
514
|
+
* more gaps as facts, not tightening this field. The GENERATION contract states it as
|
|
515
|
+
* required-and-nullable for the reason every sibling field there does — an omitted key and a
|
|
516
|
+
* considered "no fact models this" are different answers, and a model that may drop the key gives no
|
|
517
|
+
* way to tell them apart.
|
|
518
|
+
*
|
|
519
|
+
* Not the same field as the clause's `factRefs`. `factRefs` are the facts a clause RESTS ON; these
|
|
520
|
+
* are the facts it is WAITING FOR, and a clause routinely has both — Wonder CRM's lawful-bases clause
|
|
521
|
+
* rests on `document-fact:processing-purposes` while waiting on the bases.
|
|
522
|
+
*/
|
|
523
|
+
awaitingFactRefs: z.ZodOptional<z.ZodArray<z.ZodString>>;
|
|
258
524
|
}, z.core.$strict>>;
|
|
259
525
|
/** The document facts this clause asserts. A clause that asserts none cites none — an empty list is valid. */
|
|
260
526
|
factRefs: z.ZodArray<z.ZodString>;
|
|
261
|
-
/**
|
|
527
|
+
/**
|
|
528
|
+
* The application POLICY AREAS this clause is sourced from — `policy:retention`, `policy:security-controls`.
|
|
529
|
+
*
|
|
530
|
+
* ## Two corrections, and the second is what the field is for
|
|
531
|
+
*
|
|
532
|
+
* This carried `.min(1)` and no namespace constraint until 2026-09-09. Measured on Wonder CRM's
|
|
533
|
+
* landed privacy notice: **37 refs, 32 of them in the `document-fact-authority:` namespace, and 0 of
|
|
534
|
+
* those 32 resolved to any authority the application declares.** They were not a different
|
|
535
|
+
* vocabulary — every one was a NEAR-MISS of a real declared authority, three of them a literal
|
|
536
|
+
* prefix of one (`…governance-system-boundaries-and-lifecycle` for the declared
|
|
537
|
+
* `…governance-system-boundaries`). The drafter had invented each slug rather than reading it,
|
|
538
|
+
* exactly the rename drift that broke the fact citations one level down, and nothing could see it
|
|
539
|
+
* because this field resolves against nothing.
|
|
540
|
+
*
|
|
541
|
+
* **`.min(1)` is what produced them.** Per clause, the 32 were a 1:1 restatement of that clause's own
|
|
542
|
+
* `factRefs` in longer phrasing — the operator-identity clause cites `document-fact:controller-and-contact`
|
|
543
|
+
* and `document-fact:operator-legal-identity`, then names those same two subjects again here. A clause
|
|
544
|
+
* resting on declared facts already NAMES its source; the constraint demanded a second naming, and the
|
|
545
|
+
* only material available was the facts it had just cited. So the field's own guard manufactured the
|
|
546
|
+
* duplication it was meant to prevent.
|
|
547
|
+
*
|
|
548
|
+
* ## What it is now
|
|
549
|
+
*
|
|
550
|
+
* A fact authority is reached THROUGH `factRefs` — the facts file declares each fact's
|
|
551
|
+
* `authority.authorityRef`, so restating it here is hand-maintaining a derivable value at N sites
|
|
552
|
+
* (`.claude/rules/derive-before-you-ask.md`). This field therefore carries the `policy:` namespace
|
|
553
|
+
* only, and is EMPTY for a clause whose source is its facts.
|
|
554
|
+
*
|
|
555
|
+
* The guard that matters survives, stated over both fields rather than over this one: a clause must
|
|
556
|
+
* name a source — at least one `factRef` or at least one `sourcePolicyRef` — because prose with no
|
|
557
|
+
* source is invention. See the `superRefine` below.
|
|
558
|
+
*
|
|
559
|
+
* **What this does NOT close:** `policy:*` names a policy AREA, not a record, and no registry
|
|
560
|
+
* resolves it. That is honest — a topic label is what a reviewer needs when a clause rests on no
|
|
561
|
+
* fact — but it means this field is still unresolvable, and the check below constrains its SHAPE
|
|
562
|
+
* rather than its referent.
|
|
563
|
+
*/
|
|
262
564
|
sourcePolicyRefs: z.ZodArray<z.ZodString>;
|
|
263
|
-
/**
|
|
565
|
+
/**
|
|
566
|
+
* The claim guards a reviewer checks this clause against: the drafter's own restrictions, plus — derived
|
|
567
|
+
* when a generated candidate is normalized — the catalog guard of every blueprint clause this clause
|
|
568
|
+
* `satisfiesClauseRefs` (#1452). A hand-authored candidate supplies both itself.
|
|
569
|
+
*/
|
|
264
570
|
claimGuardRefs: z.ZodArray<z.ZodString>;
|
|
571
|
+
/**
|
|
572
|
+
* The judged runs in this application's OWN assurance repository that this clause rests on (#297).
|
|
573
|
+
*
|
|
574
|
+
* ## What it is for, and the one thing it is not
|
|
575
|
+
*
|
|
576
|
+
* A governance document is where an operator says what its controls DO, and until this existed no
|
|
577
|
+
* clause could say that at all: assurance findings and clean passes were produced, judged, committed
|
|
578
|
+
* — and citable by nothing. So an operating statement had exactly two forms, an unsupported claim or
|
|
579
|
+
* a mark, and the mark was correct.
|
|
580
|
+
*
|
|
581
|
+
* It is SELF-ATTESTED INTERNAL EVIDENCE and must never read as anything else. The application judged
|
|
582
|
+
* its own product with its own harness; that is worth stating to an assurance reader inside the
|
|
583
|
+
* operator's organisation, and it is not an audit, an attestation or an independent opinion. The
|
|
584
|
+
* brief that carries these runs to a drafter labels them so, and the claim guards refuse the
|
|
585
|
+
* sentence that would launder them.
|
|
586
|
+
*
|
|
587
|
+
* ## Why it is OPTIONAL and empty is the norm
|
|
588
|
+
*
|
|
589
|
+
* Almost every clause rests on facts, and a clause that cites a run it does not need has made its
|
|
590
|
+
* reader check a citation for nothing. Empty is not a gap here — it is the ordinary case — which is
|
|
591
|
+
* why this array is absent from the "names no source" rule: a fact or a policy area is what sources
|
|
592
|
+
* a statement, and a run is what SUPPORTS one that asserts operation.
|
|
593
|
+
*
|
|
594
|
+
* ## Where it is refused
|
|
595
|
+
*
|
|
596
|
+
* Two refusals, and both live outside this schema because both need something it cannot see. A ref
|
|
597
|
+
* that resolves to no committed run is refused by the binding validator, which can read the
|
|
598
|
+
* repository. ANY entry in a document under `document-claim-policy:public-safe-baseline` is refused
|
|
599
|
+
* there too — the claim POLICY decides, never the namespace, because what makes a public operating
|
|
600
|
+
* claim wrong is the reader it reaches rather than the evidence behind it (Paul, 2026-09-21).
|
|
601
|
+
*/
|
|
602
|
+
evidenceRefs: z.ZodOptional<z.ZodArray<z.ZodString>>;
|
|
265
603
|
}, z.core.$strict>>;
|
|
266
604
|
}, z.core.$strict>;
|
|
267
605
|
export type ComplianceDocumentCandidateSection = z.infer<typeof ComplianceDocumentCandidateSectionSchema>;
|
|
@@ -394,7 +732,7 @@ export declare const ComplianceDocumentCandidateSchema: z.ZodObject<{
|
|
|
394
732
|
* contract must require it explicitly instead: a model permitted to omit the key would silently
|
|
395
733
|
* claim `DERIVED`, which is the one direction that lets invention back in.
|
|
396
734
|
*/
|
|
397
|
-
completeness: z.ZodDefault<z.ZodEnum<typeof ComplianceStatementCompleteness
|
|
735
|
+
completeness: z.ZodDefault<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<z.ZodEnum<typeof ComplianceStatementCompleteness>>>;
|
|
398
736
|
/** Required when `completeness` is not `DERIVED`, forbidden when it is — see the superRefine below. */
|
|
399
737
|
incompleteness: z.ZodOptional<z.ZodObject<{
|
|
400
738
|
/** The missing information, in the reader's terms — not "factRef absent" but "how long we keep it". */
|
|
@@ -404,13 +742,125 @@ export declare const ComplianceDocumentCandidateSchema: z.ZodObject<{
|
|
|
404
742
|
* configuration surface to edit. A row whose remedy is unnamed is a row nobody picks up.
|
|
405
743
|
*/
|
|
406
744
|
closedBy: z.ZodString;
|
|
745
|
+
/**
|
|
746
|
+
* The declared facts whose ARRIVAL would close this gap — the derivable half of `needs`.
|
|
747
|
+
*
|
|
748
|
+
* ## Why prose alone rots, measured
|
|
749
|
+
*
|
|
750
|
+
* `needs` and `closedBy` are prose, and prose asserting the ABSENCE of a configuration value is true
|
|
751
|
+
* at the instant it is written and false the instant somebody declares that value. Nothing observes
|
|
752
|
+
* the transition. Wonder CRM's `clause:purposes-and-lawful-bases-not-declared` said *"The lawful
|
|
753
|
+
* basis for each purpose has not yet been declared"* and named `operatorComplianceIdentity.lawfulBases`
|
|
754
|
+
* as what it needed; the application declared exactly that on 2026-09-02, and the notice went on
|
|
755
|
+
* telling a reader something untrue about the application's own configuration for a week. It was found
|
|
756
|
+
* by a human reading the file — the same way the dangling fact refs were found, and for the same
|
|
757
|
+
* reason: a marked clause is precisely the one nobody re-reads.
|
|
758
|
+
*
|
|
759
|
+
* So a clause that asserts an absence owes a DERIVATION rather than a sentence
|
|
760
|
+
* (`.claude/rules/derive-before-you-ask.md`). This field is that derivation's subject: name the fact
|
|
761
|
+
* whose absence you are asserting, and `validateComplianceDocumentCandidateFactBinding` reports the
|
|
762
|
+
* clause as STALE the moment the application declares it — total over
|
|
763
|
+
* {@link ComplianceDocumentFactAvailability}, so an availability member added tomorrow forces an
|
|
764
|
+
* answer here rather than being silently omitted.
|
|
765
|
+
*
|
|
766
|
+
* ## Optional, and the residual is stated rather than hidden
|
|
767
|
+
*
|
|
768
|
+
* `.optional()` because not every gap is expressible as a declared fact. Two of Wonder CRM's five
|
|
769
|
+
* marked clauses wait on something no fact family models — an effective-date decision, a security
|
|
770
|
+
* summary the framework cannot yet express — and requiring a ref there would refuse a legitimately
|
|
771
|
+
* marked clause with a remedy that does not exist.
|
|
772
|
+
*
|
|
773
|
+
* **The residual is therefore real and is named here so it is not mistaken for coverage: a clause
|
|
774
|
+
* that names no awaited fact can still rot, and nothing will say so.** Narrowing it means modelling
|
|
775
|
+
* more gaps as facts, not tightening this field. The GENERATION contract states it as
|
|
776
|
+
* required-and-nullable for the reason every sibling field there does — an omitted key and a
|
|
777
|
+
* considered "no fact models this" are different answers, and a model that may drop the key gives no
|
|
778
|
+
* way to tell them apart.
|
|
779
|
+
*
|
|
780
|
+
* Not the same field as the clause's `factRefs`. `factRefs` are the facts a clause RESTS ON; these
|
|
781
|
+
* are the facts it is WAITING FOR, and a clause routinely has both — Wonder CRM's lawful-bases clause
|
|
782
|
+
* rests on `document-fact:processing-purposes` while waiting on the bases.
|
|
783
|
+
*/
|
|
784
|
+
awaitingFactRefs: z.ZodOptional<z.ZodArray<z.ZodString>>;
|
|
407
785
|
}, z.core.$strict>>;
|
|
408
786
|
/** The document facts this clause asserts. A clause that asserts none cites none — an empty list is valid. */
|
|
409
787
|
factRefs: z.ZodArray<z.ZodString>;
|
|
410
|
-
/**
|
|
788
|
+
/**
|
|
789
|
+
* The application POLICY AREAS this clause is sourced from — `policy:retention`, `policy:security-controls`.
|
|
790
|
+
*
|
|
791
|
+
* ## Two corrections, and the second is what the field is for
|
|
792
|
+
*
|
|
793
|
+
* This carried `.min(1)` and no namespace constraint until 2026-09-09. Measured on Wonder CRM's
|
|
794
|
+
* landed privacy notice: **37 refs, 32 of them in the `document-fact-authority:` namespace, and 0 of
|
|
795
|
+
* those 32 resolved to any authority the application declares.** They were not a different
|
|
796
|
+
* vocabulary — every one was a NEAR-MISS of a real declared authority, three of them a literal
|
|
797
|
+
* prefix of one (`…governance-system-boundaries-and-lifecycle` for the declared
|
|
798
|
+
* `…governance-system-boundaries`). The drafter had invented each slug rather than reading it,
|
|
799
|
+
* exactly the rename drift that broke the fact citations one level down, and nothing could see it
|
|
800
|
+
* because this field resolves against nothing.
|
|
801
|
+
*
|
|
802
|
+
* **`.min(1)` is what produced them.** Per clause, the 32 were a 1:1 restatement of that clause's own
|
|
803
|
+
* `factRefs` in longer phrasing — the operator-identity clause cites `document-fact:controller-and-contact`
|
|
804
|
+
* and `document-fact:operator-legal-identity`, then names those same two subjects again here. A clause
|
|
805
|
+
* resting on declared facts already NAMES its source; the constraint demanded a second naming, and the
|
|
806
|
+
* only material available was the facts it had just cited. So the field's own guard manufactured the
|
|
807
|
+
* duplication it was meant to prevent.
|
|
808
|
+
*
|
|
809
|
+
* ## What it is now
|
|
810
|
+
*
|
|
811
|
+
* A fact authority is reached THROUGH `factRefs` — the facts file declares each fact's
|
|
812
|
+
* `authority.authorityRef`, so restating it here is hand-maintaining a derivable value at N sites
|
|
813
|
+
* (`.claude/rules/derive-before-you-ask.md`). This field therefore carries the `policy:` namespace
|
|
814
|
+
* only, and is EMPTY for a clause whose source is its facts.
|
|
815
|
+
*
|
|
816
|
+
* The guard that matters survives, stated over both fields rather than over this one: a clause must
|
|
817
|
+
* name a source — at least one `factRef` or at least one `sourcePolicyRef` — because prose with no
|
|
818
|
+
* source is invention. See the `superRefine` below.
|
|
819
|
+
*
|
|
820
|
+
* **What this does NOT close:** `policy:*` names a policy AREA, not a record, and no registry
|
|
821
|
+
* resolves it. That is honest — a topic label is what a reviewer needs when a clause rests on no
|
|
822
|
+
* fact — but it means this field is still unresolvable, and the check below constrains its SHAPE
|
|
823
|
+
* rather than its referent.
|
|
824
|
+
*/
|
|
411
825
|
sourcePolicyRefs: z.ZodArray<z.ZodString>;
|
|
412
|
-
/**
|
|
826
|
+
/**
|
|
827
|
+
* The claim guards a reviewer checks this clause against: the drafter's own restrictions, plus — derived
|
|
828
|
+
* when a generated candidate is normalized — the catalog guard of every blueprint clause this clause
|
|
829
|
+
* `satisfiesClauseRefs` (#1452). A hand-authored candidate supplies both itself.
|
|
830
|
+
*/
|
|
413
831
|
claimGuardRefs: z.ZodArray<z.ZodString>;
|
|
832
|
+
/**
|
|
833
|
+
* The judged runs in this application's OWN assurance repository that this clause rests on (#297).
|
|
834
|
+
*
|
|
835
|
+
* ## What it is for, and the one thing it is not
|
|
836
|
+
*
|
|
837
|
+
* A governance document is where an operator says what its controls DO, and until this existed no
|
|
838
|
+
* clause could say that at all: assurance findings and clean passes were produced, judged, committed
|
|
839
|
+
* — and citable by nothing. So an operating statement had exactly two forms, an unsupported claim or
|
|
840
|
+
* a mark, and the mark was correct.
|
|
841
|
+
*
|
|
842
|
+
* It is SELF-ATTESTED INTERNAL EVIDENCE and must never read as anything else. The application judged
|
|
843
|
+
* its own product with its own harness; that is worth stating to an assurance reader inside the
|
|
844
|
+
* operator's organisation, and it is not an audit, an attestation or an independent opinion. The
|
|
845
|
+
* brief that carries these runs to a drafter labels them so, and the claim guards refuse the
|
|
846
|
+
* sentence that would launder them.
|
|
847
|
+
*
|
|
848
|
+
* ## Why it is OPTIONAL and empty is the norm
|
|
849
|
+
*
|
|
850
|
+
* Almost every clause rests on facts, and a clause that cites a run it does not need has made its
|
|
851
|
+
* reader check a citation for nothing. Empty is not a gap here — it is the ordinary case — which is
|
|
852
|
+
* why this array is absent from the "names no source" rule: a fact or a policy area is what sources
|
|
853
|
+
* a statement, and a run is what SUPPORTS one that asserts operation.
|
|
854
|
+
*
|
|
855
|
+
* ## Where it is refused
|
|
856
|
+
*
|
|
857
|
+
* Two refusals, and both live outside this schema because both need something it cannot see. A ref
|
|
858
|
+
* that resolves to no committed run is refused by the binding validator, which can read the
|
|
859
|
+
* repository. ANY entry in a document under `document-claim-policy:public-safe-baseline` is refused
|
|
860
|
+
* there too — the claim POLICY decides, never the namespace, because what makes a public operating
|
|
861
|
+
* claim wrong is the reader it reaches rather than the evidence behind it (Paul, 2026-09-21).
|
|
862
|
+
*/
|
|
863
|
+
evidenceRefs: z.ZodOptional<z.ZodArray<z.ZodString>>;
|
|
414
864
|
}, z.core.$strict>>;
|
|
415
865
|
}, z.core.$strict>>;
|
|
416
866
|
/** What a reviewer must check before this becomes a published document. */
|
|
@@ -475,11 +925,137 @@ export declare enum ComplianceDocumentFactAvailability {
|
|
|
475
925
|
export declare enum ComplianceDocumentCandidateFactBindingIssueKind {
|
|
476
926
|
/** A clause asserts a fact the application never declared. The defect this check exists for. */
|
|
477
927
|
UNDECLARED_CLAUSE_FACT = "UNDECLARED_CLAUSE_FACT",
|
|
928
|
+
/**
|
|
929
|
+
* A clause MARKED incomplete cites a fact ref that resolves to nothing.
|
|
930
|
+
*
|
|
931
|
+
* Separate from {@link ComplianceDocumentCandidateFactBindingIssueKind.UNDECLARED_CLAUSE_FACT}
|
|
932
|
+
* because the two are different defects with different remedies, and merging them would say
|
|
933
|
+
* something false about the marked one. A `DERIVED` clause citing an undeclared fact has ASSERTED
|
|
934
|
+
* something nobody established — invention. A marked clause asserts nothing, so its broken citation
|
|
935
|
+
* is not invention; it is a reference that points at no fact, and the fix is to drop it (an empty
|
|
936
|
+
* `factRefs` is valid and is what a clause asserting nothing carries) or to cite one that exists.
|
|
937
|
+
*
|
|
938
|
+
* Added 2026-09-09. Until then a marked clause was exempt from the check ENTIRELY, so a dangling ref
|
|
939
|
+
* on one was invisible — measured on wonder-crm, where three refs resolving to nothing sat on two
|
|
940
|
+
* `NEEDS_DECISION` clauses while the check answered `ok: true` and the coherence report answered
|
|
941
|
+
* "Dangling references: None". Fact refs are model-named and unstable across runs, so re-landing the
|
|
942
|
+
* facts renames them out from under a document that still cites them; the marked clauses are exactly
|
|
943
|
+
* the ones whose citations nobody re-reads.
|
|
944
|
+
*/
|
|
945
|
+
UNRESOLVED_MARKED_CLAUSE_FACT = "UNRESOLVED_MARKED_CLAUSE_FACT",
|
|
946
|
+
/**
|
|
947
|
+
* A clause MARKED incomplete is WAITING for a fact the application has since DECLARED. The clause rotted.
|
|
948
|
+
*
|
|
949
|
+
* Added 2026-09-09, against a live instance. Wonder CRM's `clause:purposes-and-lawful-bases-not-declared`
|
|
950
|
+
* asserted *"The lawful basis for each purpose has not yet been declared"* and named
|
|
951
|
+
* `operatorComplianceIdentity.lawfulBases` as what it needed; the application declared exactly that on
|
|
952
|
+
* 2026-09-02, and every check in this family answered clean — because every check asked whether a
|
|
953
|
+
* citation RESOLVES, and this clause's defect is the opposite: what it waits for arrived.
|
|
954
|
+
*
|
|
955
|
+
* The other three kinds are about a reference pointing at nothing. This one is about a reference
|
|
956
|
+
* pointing at something that did not exist when the sentence was written. Merging it with
|
|
957
|
+
* {@link ComplianceDocumentCandidateFactBindingIssueKind.UNRESOLVED_MARKED_CLAUSE_FACT} would invert the
|
|
958
|
+
* remedy: there the fix is to DROP the reference, here it is to REDRAFT the clause, because the document
|
|
959
|
+
* now states something untrue about the application's own configuration.
|
|
960
|
+
*
|
|
961
|
+
* A `DECLARED_NOT_APPLICABLE` fact triggers it too, and deliberately: the family schema requires a
|
|
962
|
+
* `reason` on such a declaration, so "does not apply" is a considered answer to the very question the
|
|
963
|
+
* clause says is open. A clause waiting for an answer that has been recorded is stale either way.
|
|
964
|
+
*/
|
|
965
|
+
STALE_MARKED_CLAUSE = "STALE_MARKED_CLAUSE",
|
|
478
966
|
/** A variant selection is justified by a fact the application never declared. */
|
|
967
|
+
/**
|
|
968
|
+
* A clause cites a judged run this application's assurance repository does not hold (#297).
|
|
969
|
+
*
|
|
970
|
+
* The evidence twin of {@link UNDECLARED_CLAUSE_FACT}, and refused for the same reason with a sharper
|
|
971
|
+
* edge: a citation that resolves to nothing is bad in a fact and worse in EVIDENCE, because the whole
|
|
972
|
+
* point of citing a run is that a reader can open it and see what was measured. An unresolvable
|
|
973
|
+
* `assurance-run:` ref is a claim of having been measured, with nothing behind it.
|
|
974
|
+
*
|
|
975
|
+
* Raised only when the repository COULD be read. An unreadable repository says nothing about whether a
|
|
976
|
+
* run exists, and refusing on it would turn a missing tool into a false finding about a document
|
|
977
|
+
* (`negative-results-require-a-positive-probe.md`).
|
|
978
|
+
*/
|
|
979
|
+
UNRESOLVED_CLAUSE_EVIDENCE = "UNRESOLVED_CLAUSE_EVIDENCE",
|
|
980
|
+
/**
|
|
981
|
+
* A clause cites a run that EXISTS and whose judgement never settled the question (#297).
|
|
982
|
+
*
|
|
983
|
+
* The citation resolves, the run is real, and it supports nothing: `INSUFFICIENT_EVIDENCE` says the
|
|
984
|
+
* evidence needed to decide was not obtained, and `NONCONFORMITY` says the control fell short. A
|
|
985
|
+
* clause resting on either asserts that a measurement established something it did not — which is a
|
|
986
|
+
* worse sentence than the mark it replaced, because it arrives wearing a citation.
|
|
987
|
+
*
|
|
988
|
+
* Mechanically decidable, which is why it is refused here rather than left to the advisory judge: the
|
|
989
|
+
* caller that read the repository already knows each run's verdict, and "may this run support an
|
|
990
|
+
* operating claim" is a property of the run, not a judgement about the prose.
|
|
991
|
+
*/
|
|
992
|
+
UNCONCLUDED_CLAUSE_EVIDENCE = "UNCONCLUDED_CLAUSE_EVIDENCE",
|
|
993
|
+
/**
|
|
994
|
+
* A clause in a PUBLIC document cites internal evidence at all (#297, decided by Paul 2026-09-21).
|
|
995
|
+
*
|
|
996
|
+
* Not about the run, and not about whether the evidence is good. Self-attested internal evidence may be
|
|
997
|
+
* cited by the four internal governance documents and by nothing else until Gate 3 arms the publication
|
|
998
|
+
* gate, because what makes a public operating claim wrong is the READER it reaches: a data subject
|
|
999
|
+
* reading a privacy notice cannot weigh "the operator judged its own product with its own harness",
|
|
1000
|
+
* and a sentence that invites them to is the laundering this whole lane exists to prevent.
|
|
1001
|
+
*
|
|
1002
|
+
* Keyed on the document's CLAIM POLICY rather than on its ref, so a seventh public document is covered
|
|
1003
|
+
* the day it is catalogued, and a governance document that is ever placed under the public baseline
|
|
1004
|
+
* loses the citation with it.
|
|
1005
|
+
*/
|
|
1006
|
+
PUBLIC_DOCUMENT_EVIDENCE_CITATION = "PUBLIC_DOCUMENT_EVIDENCE_CITATION",
|
|
479
1007
|
UNDECLARED_VARIANT_FACT = "UNDECLARED_VARIANT_FACT",
|
|
480
1008
|
/** A variant selection is justified by a fact the application declared NOT APPLICABLE. */
|
|
481
1009
|
NOT_APPLICABLE_VARIANT_FACT = "NOT_APPLICABLE_VARIANT_FACT"
|
|
482
1010
|
}
|
|
1011
|
+
/**
|
|
1012
|
+
* Which issue kinds mean *the citation resolves to nothing*, as opposed to *it resolves to an answer a
|
|
1013
|
+
* reviewer should look at*.
|
|
1014
|
+
*
|
|
1015
|
+
* Exported because a consumer that wants only the first group must not hand-list the members. The
|
|
1016
|
+
* coherence report did exactly that — `kind === UNDECLARED_CLAUSE_FACT || kind === UNDECLARED_VARIANT_FACT`
|
|
1017
|
+
* — which is a second enumeration of a vocabulary owned here, and the shape that silently omits the
|
|
1018
|
+
* next member added (`.claude/rules/invariant-call-site-enumeration.md`). A `Record` keyed by the enum
|
|
1019
|
+
* makes a new member a COMPILE ERROR at this one site instead of a silent omission at each consumer.
|
|
1020
|
+
*
|
|
1021
|
+
* A `NOT_APPLICABLE_*` citation is `false`: the fact exists and carries a recorded "does not apply", so
|
|
1022
|
+
* nothing dangles — it is a drafting observation the generation loop already shows a reviewer, and
|
|
1023
|
+
* promoting it to a dangling-reference finding would make that report mostly not about dangling
|
|
1024
|
+
* references.
|
|
1025
|
+
*/
|
|
1026
|
+
export declare const COMPLIANCE_DOCUMENT_FACT_BINDING_ISSUE_RESOLVES_TO_NOTHING: Readonly<Record<ComplianceDocumentCandidateFactBindingIssueKind, boolean>>;
|
|
1027
|
+
/**
|
|
1028
|
+
* Whether an issue kind can only be decided when the application's DECLARED FACTS were loaded.
|
|
1029
|
+
*
|
|
1030
|
+
* A caller that could not load them must skip the fact rules — an unloaded map is not an empty one, and
|
|
1031
|
+
* refusing every citation because nobody read the facts file would make a document unproducible for a
|
|
1032
|
+
* reason that is about the HOST rather than the document. What that caller must NOT skip is the evidence
|
|
1033
|
+
* rules: the claim policy is a property of the document's own catalog entry and needs no facts at all,
|
|
1034
|
+
* and run resolution needs the assurance repository rather than the facts.
|
|
1035
|
+
*
|
|
1036
|
+
* Measured 2026-09-22: the landing's `collectUndeclaredDocumentFactFindings` returned EARLY on absent
|
|
1037
|
+
* facts, before the validator ran, so a host with no facts loaded got no evidence enforcement either —
|
|
1038
|
+
* one guard's precondition silently disabling another. This record is what lets the skip be precise.
|
|
1039
|
+
*
|
|
1040
|
+
* A `Record` keyed by the enum rather than a list, for the reason its sibling above is one: a derivation
|
|
1041
|
+
* that is not TOTAL over its vocabulary silently omits the member added tomorrow. A new issue kind is a
|
|
1042
|
+
* compile error here, at the vocabulary's owner, rather than a rule that quietly stops being applied.
|
|
1043
|
+
*/
|
|
1044
|
+
export declare const COMPLIANCE_DOCUMENT_FACT_BINDING_ISSUE_NEEDS_DECLARED_FACTS: Readonly<Record<ComplianceDocumentCandidateFactBindingIssueKind, boolean>>;
|
|
1045
|
+
/**
|
|
1046
|
+
* Whether a given availability means the awaited question HAS BEEN ANSWERED, and the clause waiting for
|
|
1047
|
+
* it is therefore stale.
|
|
1048
|
+
*
|
|
1049
|
+
* A `Record` keyed by the enum rather than a comparison, for the reason the sibling record above exists:
|
|
1050
|
+
* this is the derivation that replaces a sentence asserting an absence, and a derivation that is not
|
|
1051
|
+
* TOTAL over its vocabulary silently omits the member added tomorrow
|
|
1052
|
+
* (`.claude/rules/derive-before-you-ask.md`, rule 3). A third availability member is a compile error
|
|
1053
|
+
* here, at the vocabulary's owner, instead of a case the staleness check quietly does not report.
|
|
1054
|
+
*
|
|
1055
|
+
* Absence from the map is the remaining case and is handled where the map is read: a fact nobody declared
|
|
1056
|
+
* has not arrived, so the clause is still legitimately waiting.
|
|
1057
|
+
*/
|
|
1058
|
+
export declare const COMPLIANCE_DOCUMENT_FACT_AVAILABILITY_ANSWERS_THE_QUESTION: Readonly<Record<ComplianceDocumentFactAvailability, boolean>>;
|
|
483
1059
|
export interface ComplianceDocumentCandidateFactBindingIssue {
|
|
484
1060
|
readonly kind: ComplianceDocumentCandidateFactBindingIssueKind;
|
|
485
1061
|
readonly path: string;
|
|
@@ -492,15 +1068,35 @@ export interface ComplianceDocumentCandidateFactBindingIssue {
|
|
|
492
1068
|
*
|
|
493
1069
|
* | clause completeness | cited fact | verdict |
|
|
494
1070
|
* |---|---|---|
|
|
495
|
-
* | `DERIVED` | undeclared |
|
|
496
|
-
* | `DERIVED` | declared `NOT_APPLICABLE` | **
|
|
497
|
-
* | `NEEDS_*` | undeclared |
|
|
498
|
-
* | `NEEDS_*` | declared
|
|
1071
|
+
* | `DERIVED` | undeclared | **`UNDECLARED_CLAUSE_FACT`** — invention |
|
|
1072
|
+
* | `DERIVED` | declared `NOT_APPLICABLE` | **OK** — a recorded absence supports a negative statement (corrected 2026-08-29) |
|
|
1073
|
+
* | `NEEDS_*` | undeclared | **`UNRESOLVED_MARKED_CLAUSE_FACT`** — the citation resolves to nothing (corrected 2026-09-09) |
|
|
1074
|
+
* | `NEEDS_*` | declared, either way | **OK** — incomplete for some other reason |
|
|
499
1075
|
*
|
|
500
1076
|
* The distinction the whole capability turns on is ASSERT versus MARK. A clause may say "this is not
|
|
501
1077
|
* yet established"; it may not say something untrue. Incompleteness is CONTENT — the reader sees it,
|
|
502
1078
|
* the register lists it, a human closes it later — and it never gates producing the document.
|
|
503
1079
|
*
|
|
1080
|
+
* ## THREE questions, not one — and only the first depends on completeness
|
|
1081
|
+
*
|
|
1082
|
+
* A clause is exempt from what it may ASSERT when it marks itself incomplete. It is never exempt from
|
|
1083
|
+
* whether its citations RESOLVE: a ref pointing at no declared fact is broken whatever the clause
|
|
1084
|
+
* claims. Conflating the two hid three dangling refs on two `NEEDS_DECISION` clauses in a landed
|
|
1085
|
+
* wonder-crm notice, behind `ok: true` — see the split at the clause loop for the measurement.
|
|
1086
|
+
*
|
|
1087
|
+
* The third runs the other way and was added 2026-09-09: does a marked clause's stated gap still EXIST?
|
|
1088
|
+
* A clause asserting that something is not declared rots the moment somebody declares it, and every
|
|
1089
|
+
* resolution rule above answers clean over a rotted clause, because its references resolve perfectly.
|
|
1090
|
+
* `incompleteness.awaitingFactRefs` names the fact whose absence the clause asserts, and a fact that has
|
|
1091
|
+
* since been declared raises {@link ComplianceDocumentCandidateFactBindingIssueKind.STALE_MARKED_CLAUSE}
|
|
1092
|
+
* — total over {@link ComplianceDocumentFactAvailability} rather than comparing to one member, so a new
|
|
1093
|
+
* availability cannot be silently skipped. Its bound is stated at the field: a clause that names no
|
|
1094
|
+
* awaited fact can still rot, and narrowing that means modelling more gaps as facts.
|
|
1095
|
+
*
|
|
1096
|
+
* Marking therefore costs nothing a drafter should mind: `factRefs` is "the facts this clause asserts"
|
|
1097
|
+
* and an empty list is valid, so a clause waiting for a fact names it in `incompleteness.needs` rather
|
|
1098
|
+
* than citing a ref nobody declared.
|
|
1099
|
+
*
|
|
504
1100
|
* ## Variant selections stay strict, and that is not an oversight
|
|
505
1101
|
*
|
|
506
1102
|
* A clause STATES something and may state that it does not know. A variant selection DECIDES something
|
|
@@ -550,7 +1146,40 @@ export interface ComplianceDocumentCandidateFactBindingIssue {
|
|
|
550
1146
|
* An earlier revision of this comment justified the branch as "the application declared no facts", which
|
|
551
1147
|
* names a state the schema forbids and would send the next reader looking for it.
|
|
552
1148
|
*/
|
|
553
|
-
export declare function validateComplianceDocumentCandidateFactBinding(candidate: ComplianceDocumentCandidate, declaredFacts: ReadonlyMap<string, ComplianceDocumentFactAvailability
|
|
1149
|
+
export declare function validateComplianceDocumentCandidateFactBinding(candidate: ComplianceDocumentCandidate, declaredFacts: ReadonlyMap<string, ComplianceDocumentFactAvailability>,
|
|
1150
|
+
/**
|
|
1151
|
+
* What a clause's `evidenceRefs` may bind to, and whether this document may carry any (#297).
|
|
1152
|
+
*
|
|
1153
|
+
* REQUIRED, with no default, and that is the design decision. An optional parameter would make every
|
|
1154
|
+
* caller that forgot it silently exempt from both evidence rules — the shape
|
|
1155
|
+
* `.claude/rules/invariant-call-site-enumeration.md` is written about — while a required one makes the
|
|
1156
|
+
* compiler enumerate the call sites for whoever adds the next one.
|
|
1157
|
+
*/
|
|
1158
|
+
evidenceBinding: {
|
|
1159
|
+
/**
|
|
1160
|
+
* The runs this application's assurance repository holds, or `undefined` when it could not be read.
|
|
1161
|
+
*
|
|
1162
|
+
* `undefined` is NOT an empty map. An empty map says the repository was read and holds no run, so
|
|
1163
|
+
* every citation resolves to nothing and is refused; `undefined` says nobody could look, and refusing
|
|
1164
|
+
* on it would turn an absent tool into a finding about the document.
|
|
1165
|
+
*
|
|
1166
|
+
* A MAP rather than two sets, because "this run exists" and "this run may support an operating claim"
|
|
1167
|
+
* are two facts about the same run and two sets can be passed inconsistent. The caller decides the
|
|
1168
|
+
* second — it holds the verdict vocabulary, which this module deliberately does not.
|
|
1169
|
+
*/
|
|
1170
|
+
readonly committedRuns: ReadonlyMap<string, {
|
|
1171
|
+
readonly maySupportOperatingClaim: boolean;
|
|
1172
|
+
}> | undefined;
|
|
1173
|
+
/**
|
|
1174
|
+
* The claim policy of the document being validated, from the engine catalog — or `undefined` when the
|
|
1175
|
+
* caller could not resolve it.
|
|
1176
|
+
*
|
|
1177
|
+
* `undefined` does NOT admit a citation. A document whose policy nobody could resolve is one nobody
|
|
1178
|
+
* can say is allowed to cite internal evidence, and the fail-closed direction is the one whose cost is
|
|
1179
|
+
* a refusal a human can answer.
|
|
1180
|
+
*/
|
|
1181
|
+
readonly claimPolicyRef: string | undefined;
|
|
1182
|
+
}): {
|
|
554
1183
|
readonly ok: boolean;
|
|
555
1184
|
readonly issues: readonly ComplianceDocumentCandidateFactBindingIssue[];
|
|
556
1185
|
};
|
|
@@ -580,4 +1209,104 @@ export declare function validateComplianceDocumentCandidateFactBinding(candidate
|
|
|
580
1209
|
* Order between the two is therefore not significant, and a caller must not read it as significant.
|
|
581
1210
|
*/
|
|
582
1211
|
export declare function collectComplianceDocumentFactAvailability(...specifications: readonly (ApplicationDocumentFactDeclarationSet | undefined)[]): ReadonlyMap<string, ComplianceDocumentFactAvailability>;
|
|
1212
|
+
/**
|
|
1213
|
+
* Which way a document FAILS TO COVER a fact its blueprint requires.
|
|
1214
|
+
*
|
|
1215
|
+
* Distinct vocabulary from {@link ComplianceDocumentCandidateFactBindingIssueKind}, and the split is
|
|
1216
|
+
* the point rather than tidiness. That one answers *does a citation RESOLVE* — it reads the refs a
|
|
1217
|
+
* candidate WROTE and asks whether each points at something. This one answers the opposite direction:
|
|
1218
|
+
* *does the candidate write the refs it OWES* — it reads the blueprint's demand and asks whether the
|
|
1219
|
+
* document reaches it at all.
|
|
1220
|
+
*
|
|
1221
|
+
* No resolution check can see this defect, because a document that omits a required fact cites nothing
|
|
1222
|
+
* broken. Measured on the landed Wonder CRM privacy notice (#454): the blueprint requires eight facts,
|
|
1223
|
+
* the candidate cited four, every fact-binding check answered clean, and the omission was found by a
|
|
1224
|
+
* human reading the file against the blueprint.
|
|
1225
|
+
*/
|
|
1226
|
+
export declare enum ComplianceDocumentCandidateFactCoverageIssueKind {
|
|
1227
|
+
/**
|
|
1228
|
+
* A fact the blueprint's REQUIRED clauses demand is cited by no clause in the candidate.
|
|
1229
|
+
*
|
|
1230
|
+
* The document is silently short of its own blueprint. Silently is the operative word: nothing the
|
|
1231
|
+
* document says is false, so every check that reads what it SAYS passes.
|
|
1232
|
+
*/
|
|
1233
|
+
UNCOVERED_REQUIRED_FACT = "UNCOVERED_REQUIRED_FACT",
|
|
1234
|
+
/**
|
|
1235
|
+
* A required fact is cited ONLY by clauses marked incomplete — never by a `DERIVED` one.
|
|
1236
|
+
*
|
|
1237
|
+
* Reported rather than refused, and reported SEPARATELY, because it is the state #454 actually
|
|
1238
|
+
* found: the four absent facts were *"partly covered by clauses marked as needing a decision or a
|
|
1239
|
+
* framework change, rather than by the required facts themselves"*. A count of covered facts calls
|
|
1240
|
+
* that covered; a reviewer deciding whether the notice may be published needs to know it is not.
|
|
1241
|
+
*
|
|
1242
|
+
* Never a blocker. Producing a document with its gaps MARKED is the standing preference, and a
|
|
1243
|
+
* marked clause is the mechanism that expresses one — refusing here would punish the honest shape
|
|
1244
|
+
* and push a drafter toward silence, which is the direction this whole family must never fail in.
|
|
1245
|
+
*/
|
|
1246
|
+
REQUIRED_FACT_ONLY_MARKED = "REQUIRED_FACT_ONLY_MARKED"
|
|
1247
|
+
}
|
|
1248
|
+
/** One coverage finding. Same shape as its resolution-side sibling so a caller can fold both alike. */
|
|
1249
|
+
export interface ComplianceDocumentCandidateFactCoverageIssue {
|
|
1250
|
+
readonly kind: ComplianceDocumentCandidateFactCoverageIssueKind;
|
|
1251
|
+
readonly path: string;
|
|
1252
|
+
readonly message: string;
|
|
1253
|
+
}
|
|
1254
|
+
/**
|
|
1255
|
+
* Which coverage kinds mean *the document does not reach the fact at all*, as opposed to *it reaches
|
|
1256
|
+
* it only through a marked clause*.
|
|
1257
|
+
*
|
|
1258
|
+
* Exported for the same reason as
|
|
1259
|
+
* {@link COMPLIANCE_DOCUMENT_FACT_BINDING_ISSUE_RESOLVES_TO_NOTHING}: a consumer wanting only the
|
|
1260
|
+
* blocking group must not hand-list the members, because a hand-list silently omits the next kind
|
|
1261
|
+
* added. A `Record` keyed by the enum makes that a compile error here instead.
|
|
1262
|
+
*/
|
|
1263
|
+
export declare const COMPLIANCE_DOCUMENT_FACT_COVERAGE_ISSUE_IS_ABSENT: Readonly<Record<ComplianceDocumentCandidateFactCoverageIssueKind, boolean>>;
|
|
1264
|
+
/**
|
|
1265
|
+
* Does this candidate cite the facts its blueprint REQUIRES?
|
|
1266
|
+
*
|
|
1267
|
+
* ## Why this exists, and why no existing check could have caught it
|
|
1268
|
+
*
|
|
1269
|
+
* Every other check in this family reads what a candidate WROTE. This one reads what it OWES. A
|
|
1270
|
+
* document that omits a required fact writes nothing wrong — it simply does not mention the thing —
|
|
1271
|
+
* so a resolution check, a schema, and a coherence report all pass over it in silence.
|
|
1272
|
+
*
|
|
1273
|
+
* #454, measured: the privacy-notice blueprint requires **eight** facts and the landed Wonder CRM
|
|
1274
|
+
* candidate cited **four**. The `_core` candidate schema did not bind facts to a blueprint at all, so
|
|
1275
|
+
* there was nothing to notice the other four with. The same gap is why six cited fact suffixes that
|
|
1276
|
+
* existed nowhere survived in a landed notice: the relation between a blueprint's demand and a
|
|
1277
|
+
* candidate's citations had no home.
|
|
1278
|
+
*
|
|
1279
|
+
* ## The denominator is the blueprint's REQUIRED clauses, and choosing it is the whole design
|
|
1280
|
+
*
|
|
1281
|
+
* A blueprint clause is `REQUIRED` or `CONDITIONAL`, and a conditional clause is included only when
|
|
1282
|
+
* its condition groups hold — which depends on the application's own facts. So the set every
|
|
1283
|
+
* candidate owes is the union of `requiredFactRefs` over the **REQUIRED** clauses, and nothing wider.
|
|
1284
|
+
*
|
|
1285
|
+
* Counting against the definition's document-level `requiredFactRefs` instead would report a
|
|
1286
|
+
* conditional clause's facts as missing from every application the condition does not apply to: an
|
|
1287
|
+
* arithmetically correct ratio over a population nobody owes
|
|
1288
|
+
* (`.claude/rules/derive-before-you-ask.md`, shape 2 — *"a ratio whose denominator you chose yourself
|
|
1289
|
+
* is not a measurement"*). The caller derives the set; see the derivation's own named home rather than
|
|
1290
|
+
* re-deriving it per call site.
|
|
1291
|
+
*
|
|
1292
|
+
* ## Absent is not empty
|
|
1293
|
+
*
|
|
1294
|
+
* A caller that could not resolve the blueprint must NOT call this with an empty array — it expresses
|
|
1295
|
+
* that case by not calling. An empty required set here means *the blueprint demands nothing*, and
|
|
1296
|
+
* every candidate trivially covers it. Conflating "I could not read the blueprint" with "it requires
|
|
1297
|
+
* nothing" turns a wiring failure into a clean verdict, which is the failure mode
|
|
1298
|
+
* `.claude/rules/negative-results-require-a-positive-probe.md` exists for and which this file's
|
|
1299
|
+
* resolution sibling states in the same words.
|
|
1300
|
+
*
|
|
1301
|
+
* ## What it deliberately does NOT do
|
|
1302
|
+
*
|
|
1303
|
+
* It never refuses. `REQUIRED_FACT_ONLY_MARKED` in particular is a signal for a reviewer, not a gate:
|
|
1304
|
+
* producing a document whose gaps are MARKED is the standing preference, and blocking on a marked
|
|
1305
|
+
* clause would push a drafter toward omitting the concern entirely — silence instead of a visible
|
|
1306
|
+
* gap, which is the under-reporting direction a compliance statement must never fail in.
|
|
1307
|
+
*/
|
|
1308
|
+
export declare function validateComplianceDocumentCandidateFactCoverage(candidate: ComplianceDocumentCandidate, blueprintRequiredFactRefs: readonly string[]): {
|
|
1309
|
+
readonly ok: boolean;
|
|
1310
|
+
readonly issues: readonly ComplianceDocumentCandidateFactCoverageIssue[];
|
|
1311
|
+
};
|
|
583
1312
|
//# sourceMappingURL=compliance-document-candidate.schemas.d.ts.map
|