@wildo-ai/saas-specifications 1.1.8 → 1.1.9

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.
Files changed (147) hide show
  1. package/dist/esm/_core/application-specification-family-identity.schemas.d.ts +9 -0
  2. package/dist/esm/_core/application-specification-family-identity.schemas.d.ts.map +1 -1
  3. package/dist/esm/_core/application-specification-family-identity.schemas.js +9 -0
  4. package/dist/esm/_core/application-specification-family-identity.schemas.js.map +1 -1
  5. package/dist/esm/_core/brand/brand-name-choice.d.ts +136 -0
  6. package/dist/esm/_core/brand/brand-name-choice.d.ts.map +1 -0
  7. package/dist/esm/_core/brand/brand-name-choice.js +193 -0
  8. package/dist/esm/_core/brand/brand-name-choice.js.map +1 -0
  9. package/dist/esm/_core/brand/brand-name-screening-generation.schemas.d.ts +108 -0
  10. package/dist/esm/_core/brand/brand-name-screening-generation.schemas.d.ts.map +1 -0
  11. package/dist/esm/_core/brand/brand-name-screening-generation.schemas.js +59 -0
  12. package/dist/esm/_core/brand/brand-name-screening-generation.schemas.js.map +1 -0
  13. package/dist/esm/_core/brand/brand-name-screening-validation.d.ts +51 -0
  14. package/dist/esm/_core/brand/brand-name-screening-validation.d.ts.map +1 -0
  15. package/dist/esm/_core/brand/brand-name-screening-validation.js +157 -0
  16. package/dist/esm/_core/brand/brand-name-screening-validation.js.map +1 -0
  17. package/dist/esm/_core/brand/brand-name-screening-view.d.ts +120 -0
  18. package/dist/esm/_core/brand/brand-name-screening-view.d.ts.map +1 -0
  19. package/dist/esm/_core/brand/brand-name-screening-view.js +47 -0
  20. package/dist/esm/_core/brand/brand-name-screening-view.js.map +1 -0
  21. package/dist/esm/_core/brand/brand-name-screening.family-aspects.d.ts +3 -0
  22. package/dist/esm/_core/brand/brand-name-screening.family-aspects.d.ts.map +1 -0
  23. package/dist/esm/_core/brand/brand-name-screening.family-aspects.js +42 -0
  24. package/dist/esm/_core/brand/brand-name-screening.family-aspects.js.map +1 -0
  25. package/dist/esm/_core/brand/brand-name-screening.schemas.d.ts +310 -0
  26. package/dist/esm/_core/brand/brand-name-screening.schemas.d.ts.map +1 -0
  27. package/dist/esm/_core/brand/brand-name-screening.schemas.js +272 -0
  28. package/dist/esm/_core/brand/brand-name-screening.schemas.js.map +1 -0
  29. package/dist/esm/_core/brand/brand-snapshot.schemas.d.ts +23 -0
  30. package/dist/esm/_core/brand/brand-snapshot.schemas.d.ts.map +1 -1
  31. package/dist/esm/_core/brand/brand-snapshot.schemas.js +32 -0
  32. package/dist/esm/_core/brand/brand-snapshot.schemas.js.map +1 -1
  33. package/dist/esm/_core/build-plan/build-plan-task-graph-generation.schemas.d.ts +10 -0
  34. package/dist/esm/_core/build-plan/build-plan-task-graph-generation.schemas.d.ts.map +1 -1
  35. package/dist/esm/_core/build-plan/build-plan-task-graph-validation.d.ts +57 -0
  36. package/dist/esm/_core/build-plan/build-plan-task-graph-validation.d.ts.map +1 -1
  37. package/dist/esm/_core/build-plan/build-plan-task-graph-validation.js +89 -0
  38. package/dist/esm/_core/build-plan/build-plan-task-graph-validation.js.map +1 -1
  39. package/dist/esm/_core/build-plan/build-plan-task-graph.schemas.d.ts +79 -19
  40. package/dist/esm/_core/build-plan/build-plan-task-graph.schemas.d.ts.map +1 -1
  41. package/dist/esm/_core/build-plan/build-plan-task-graph.schemas.js +61 -11
  42. package/dist/esm/_core/build-plan/build-plan-task-graph.schemas.js.map +1 -1
  43. package/dist/esm/_core/build-plan/build-plan.family-aspects.d.ts.map +1 -1
  44. package/dist/esm/_core/build-plan/build-plan.family-aspects.js +18 -2
  45. package/dist/esm/_core/build-plan/build-plan.family-aspects.js.map +1 -1
  46. package/dist/esm/_core/business-model-lite/business-model-lite-snapshot-generation.schemas.d.ts +28 -4
  47. package/dist/esm/_core/business-model-lite/business-model-lite-snapshot-generation.schemas.d.ts.map +1 -1
  48. package/dist/esm/_core/business-model-lite/business-model-lite-snapshot-generation.schemas.js +53 -5
  49. package/dist/esm/_core/business-model-lite/business-model-lite-snapshot-generation.schemas.js.map +1 -1
  50. package/dist/esm/_core/business-model-lite/business-model-lite-snapshot-validation.d.ts +24 -4
  51. package/dist/esm/_core/business-model-lite/business-model-lite-snapshot-validation.d.ts.map +1 -1
  52. package/dist/esm/_core/business-model-lite/business-model-lite-snapshot-validation.js +64 -4
  53. package/dist/esm/_core/business-model-lite/business-model-lite-snapshot-validation.js.map +1 -1
  54. package/dist/esm/_core/business-model-lite/business-model-lite-snapshot.schemas.d.ts +59 -0
  55. package/dist/esm/_core/business-model-lite/business-model-lite-snapshot.schemas.d.ts.map +1 -1
  56. package/dist/esm/_core/business-model-lite/business-model-lite-snapshot.schemas.js +64 -0
  57. package/dist/esm/_core/business-model-lite/business-model-lite-snapshot.schemas.js.map +1 -1
  58. package/dist/esm/_core/business-model-lite/pricing-plan.schemas.d.ts +3 -0
  59. package/dist/esm/_core/business-model-lite/pricing-plan.schemas.d.ts.map +1 -1
  60. package/dist/esm/_core/business-model-lite/pricing-plan.schemas.js +16 -0
  61. package/dist/esm/_core/business-model-lite/pricing-plan.schemas.js.map +1 -1
  62. package/dist/esm/_core/capability-composition/capability-composition-validation.d.ts +7 -1
  63. package/dist/esm/_core/capability-composition/capability-composition-validation.d.ts.map +1 -1
  64. package/dist/esm/_core/capability-composition/capability-composition-validation.js +34 -28
  65. package/dist/esm/_core/capability-composition/capability-composition-validation.js.map +1 -1
  66. package/dist/esm/_core/capability-composition/capability-composition.schemas.d.ts +75 -4
  67. package/dist/esm/_core/capability-composition/capability-composition.schemas.d.ts.map +1 -1
  68. package/dist/esm/_core/capability-composition/capability-composition.schemas.js +62 -4
  69. package/dist/esm/_core/capability-composition/capability-composition.schemas.js.map +1 -1
  70. package/dist/esm/_core/compliance-documents/computed-document-facts.schemas.d.ts.map +1 -1
  71. package/dist/esm/_core/compliance-documents/computed-document-facts.schemas.js +7 -0
  72. package/dist/esm/_core/compliance-documents/computed-document-facts.schemas.js.map +1 -1
  73. package/dist/esm/_core/compliance-documents/launch-blockers.schemas.d.ts +153 -0
  74. package/dist/esm/_core/compliance-documents/launch-blockers.schemas.d.ts.map +1 -0
  75. package/dist/esm/_core/compliance-documents/launch-blockers.schemas.js +241 -0
  76. package/dist/esm/_core/compliance-documents/launch-blockers.schemas.js.map +1 -0
  77. package/dist/esm/_core/domain-plan/domain-plan-output-set-validation.d.ts +8 -1
  78. package/dist/esm/_core/domain-plan/domain-plan-output-set-validation.d.ts.map +1 -1
  79. package/dist/esm/_core/domain-plan/domain-plan-output-set-validation.js +19 -1
  80. package/dist/esm/_core/domain-plan/domain-plan-output-set-validation.js.map +1 -1
  81. package/dist/esm/_core/domain-plan/domain-plan-output-set.schemas.d.ts +61 -3
  82. package/dist/esm/_core/domain-plan/domain-plan-output-set.schemas.d.ts.map +1 -1
  83. package/dist/esm/_core/domain-plan/domain-plan-output-set.schemas.js +73 -3
  84. package/dist/esm/_core/domain-plan/domain-plan-output-set.schemas.js.map +1 -1
  85. package/dist/esm/_core/experience-plan/experience-plan.family-aspects.js +1 -1
  86. package/dist/esm/_core/experience-plan/experience-plan.family-aspects.js.map +1 -1
  87. package/dist/esm/_core/experience-plan/experience-plan.schemas.d.ts.map +1 -1
  88. package/dist/esm/_core/experience-plan/experience-plan.schemas.js +1 -0
  89. package/dist/esm/_core/experience-plan/experience-plan.schemas.js.map +1 -1
  90. package/dist/esm/_core/family-aspects.registry.d.ts.map +1 -1
  91. package/dist/esm/_core/family-aspects.registry.js +2 -0
  92. package/dist/esm/_core/family-aspects.registry.js.map +1 -1
  93. package/dist/esm/_core/index.d.ts +6 -0
  94. package/dist/esm/_core/index.d.ts.map +1 -1
  95. package/dist/esm/_core/index.js +6 -0
  96. package/dist/esm/_core/index.js.map +1 -1
  97. package/dist/esm/_core/integration-plan/integration-plan.family-aspects.d.ts.map +1 -1
  98. package/dist/esm/_core/integration-plan/integration-plan.family-aspects.js +5 -1
  99. package/dist/esm/_core/integration-plan/integration-plan.family-aspects.js.map +1 -1
  100. package/dist/esm/_core/market/market-icp.schemas.d.ts +7 -0
  101. package/dist/esm/_core/market/market-icp.schemas.d.ts.map +1 -1
  102. package/dist/esm/_core/market/market-icp.schemas.js +7 -0
  103. package/dist/esm/_core/market/market-icp.schemas.js.map +1 -1
  104. package/dist/esm/_core/market/market-language-coverage.d.ts +62 -0
  105. package/dist/esm/_core/market/market-language-coverage.d.ts.map +1 -0
  106. package/dist/esm/_core/market/market-language-coverage.js +48 -0
  107. package/dist/esm/_core/market/market-language-coverage.js.map +1 -0
  108. package/dist/esm/_core/market/market-snapshot-validation.js +2 -2
  109. package/dist/esm/_core/market/market-snapshot-validation.js.map +1 -1
  110. package/dist/esm/application-creation/application-creator-inputs.application-creation.schemas.d.ts +63 -2
  111. package/dist/esm/application-creation/application-creator-inputs.application-creation.schemas.d.ts.map +1 -1
  112. package/dist/esm/application-creation/application-creator-inputs.application-creation.schemas.js +73 -5
  113. package/dist/esm/application-creation/application-creator-inputs.application-creation.schemas.js.map +1 -1
  114. package/dist/esm/application-creation/application-line.application-creation.schemas.d.ts.map +1 -1
  115. package/dist/esm/application-creation/application-line.application-creation.schemas.js +2 -0
  116. package/dist/esm/application-creation/application-line.application-creation.schemas.js.map +1 -1
  117. package/dist/esm/application-creation/playbooks.application-creation.schemas.d.ts +28 -0
  118. package/dist/esm/application-creation/playbooks.application-creation.schemas.d.ts.map +1 -1
  119. package/dist/esm/application-creation/playbooks.application-creation.schemas.js +19 -1
  120. package/dist/esm/application-creation/playbooks.application-creation.schemas.js.map +1 -1
  121. package/dist/esm/application-creation/structured-artifact-landing.application-creation.schemas.d.ts +1 -0
  122. package/dist/esm/application-creation/structured-artifact-landing.application-creation.schemas.d.ts.map +1 -1
  123. package/dist/esm/application-creation/structured-artifact-landing.application-creation.schemas.js +1 -0
  124. package/dist/esm/application-creation/structured-artifact-landing.application-creation.schemas.js.map +1 -1
  125. package/dist/esm/application-creation.exports.d.ts +7 -0
  126. package/dist/esm/application-creation.exports.d.ts.map +1 -1
  127. package/dist/esm/application-creation.exports.js +7 -0
  128. package/dist/esm/application-creation.exports.js.map +1 -1
  129. package/dist/esm/assurance/application-risk-signals.derivations.d.ts +20 -0
  130. package/dist/esm/assurance/application-risk-signals.derivations.d.ts.map +1 -1
  131. package/dist/esm/assurance/application-risk-signals.derivations.js +81 -0
  132. package/dist/esm/assurance/application-risk-signals.derivations.js.map +1 -1
  133. package/dist/esm/assurance/governed-document-release.d.ts +9 -0
  134. package/dist/esm/assurance/governed-document-release.d.ts.map +1 -1
  135. package/dist/esm/assurance/governed-document-release.js +9 -0
  136. package/dist/esm/assurance/governed-document-release.js.map +1 -1
  137. package/dist/esm/companion-exports.d.ts +10 -1
  138. package/dist/esm/companion-exports.d.ts.map +1 -1
  139. package/dist/esm/companion-exports.js.map +1 -1
  140. package/dist/esm/engine/infrastructure/resources/job-executions.resource.specification.d.ts +1 -0
  141. package/dist/esm/engine/infrastructure/resources/job-executions.resource.specification.d.ts.map +1 -1
  142. package/package.json +8 -8
  143. package/dist/esm/assurance/__tests__/authority-evaluation-instant.fixture.d.ts +0 -24
  144. package/dist/esm/assurance/__tests__/authority-evaluation-instant.fixture.d.ts.map +0 -1
  145. package/dist/esm/assurance/__tests__/authority-evaluation-instant.fixture.js +0 -24
  146. package/dist/esm/assurance/__tests__/authority-evaluation-instant.fixture.js.map +0 -1
  147. package/dist/tsconfig.build.tsbuildinfo +0 -1
@@ -1 +1 @@
1
- {"version":3,"file":"companion-exports.js","sourceRoot":"","sources":["../../../src/companion-exports.ts"],"names":[],"mappings":"AAoDA,cAAc,gFAAgF,CAAC;AA6qB/F,4EAA4E","sourcesContent":["import type { AssertionSpecificationSnapshot } from './_core/assertions/assertion-specification.schemas';\nimport type { BrandSnapshot } from './_core/brand/brand-snapshot.schemas';\nimport type { BuildPlanTaskGraph } from './_core/build-plan/build-plan-task-graph.schemas';\nimport type { PlacementPlan } from './_core/placement-plan/placement-plan.schemas';\nimport type { DomainPlanOutputSet } from './_core/domain-plan/domain-plan-output-set.schemas';\nimport type { ExpertPersonaCharter } from './_core/expert-personas/expert-persona-charter.schemas';\nimport type { BusinessModelLiteSnapshot } from './_core/business-model-lite/business-model-lite-snapshot.schemas';\nimport type { BusinessSemanticsSnapshotDeclaration } from './_core/business-semantics.specifications.schemas';\nimport type { ChartViewSpecification } from './_core/chart-view-specification.schemas';\nimport type { CompositeViewSpecification } from './_core/composite-view-specification.schemas';\nimport type { DataSeedSpecification } from './_core/data-seed-specification.schemas';\nimport type {\n FeatureSpecification,\n MilestoneSpecification,\n ProductSpecification,\n RoleSpecification,\n} from './_core/definition-specification.schemas';\nimport type { ExecutionViewSpecification } from './_core/execution-view-specification.schemas';\nimport type { FlowsActorsViewSpecification } from './_core/flows-actors-view-specification.schemas';\nimport type { FrontendComponentSpecification } from './_core/frontend-component-specification.schemas';\nimport type { FeatureSpecificationDrafts } from './_core/feature-drafts/feature-specification-drafts.schemas';\nimport type { FullCustomViewSpecification } from './_core/full-custom-view-specification.schemas';\nimport type { GuidanceFlowSpecification } from './_core/guidance-flow-specification.schemas';\nimport type { MarketSnapshot } from './_core/market/market-snapshot.schemas';\nimport type { OnboardingViewSpecification } from './_core/onboarding-view-specification.schemas';\nimport type { RequirementsSnapshot } from './_core/requirements/requirements-snapshot.schemas';\nimport type { ResourceSpecification } from './_core/resource-specification.schemas';\nimport type { RoadmapSnapshot } from './_core/roadmap/roadmap-snapshot.schemas';\nimport type { SidebarSectionSpecification } from './_core/sidebar-section-specification.schemas';\nimport type { SystemEmailTemplateSpecification } from './_core/system-email-template-specification.schemas';\nimport type { VisionSnapshot } from './_core/vision/vision-snapshot.schemas';\nimport type { SchemaOrgCatalogEntryBase } from './_catalogs/schema-org';\nimport type { ApplicationDocumentPublicationSpecification } from './assurance/application-document-publication.schemas';\nimport type {\n ApplicationAuthoredDocumentFactSpecification,\n ApplicationDocumentFactSpecification,\n} from './application-creation/application-document-fact-specification.application-creation.schemas';\nimport type { ApplicationProcessorRegister } from './_core/compliance-documents/processor-register.schemas';\nimport type { ApplicationRiskRegister } from './assurance/application-risk-register.schemas';\nimport type { ApplicationCreatorInputs } from './application-creation/application-creator-inputs.application-creation.schemas';\nimport type { CapabilityComposition } from './_core/capability-composition/capability-composition.schemas';\nimport type { WebsitePlan } from './_core/website-plan/website-plan.schemas';\nimport type { ExperiencePlan } from './_core/experience-plan/experience-plan.schemas';\nimport type { ApplicationDocumentationPlan } from './technical-documentation/application-documentation-plan.schemas';\nimport type { ApplicationDocumentationChapterSet } from './technical-documentation/application-documentation-chapters.schemas';\nimport type { IntegrationPlan } from './_core/integration-plan/integration-plan.schemas';\nimport type { ApplicationMaturity } from './_core/application-maturity/application-maturity.schemas';\nimport type { ApplicationDocumentReleasePolicySpecification } from './application-creation/application-document-release-policy-specification.application-creation.schemas';\nimport type { ApplicationDocumentReleaseSet } from './assurance/application-document-release-set.schemas';\nimport type { GovernedDocumentReleaseComposition } from './assurance/governed-document-release';\nimport type { AssuranceProgramSpecification } from './assurance/assurance-program.schemas';\n\nexport * from './technical-documentation/engine-documentation-specification-catalog.companion';\n\n/**\n * @wildo_source:part:start saas.specifications.companion-exports.contract facet:layer:specification facet:family:companion\n *\n * Typed companion export surface: registries of resource specs, definitions, and view specs the dev companion materializes.\n */\nexport interface SpecificationsCompanionExports<\n TResourceSpecifications = ResourceSpecification,\n // The AUTHORED shape: a companion reader parses it with `BusinessSemanticsSnapshotSchema`.\n TBusinessSemanticsSnapshot = BusinessSemanticsSnapshotDeclaration,\n TFeatureSpecifications = FeatureSpecification,\n TMilestoneSpecifications = MilestoneSpecification,\n TProductSpecifications = ProductSpecification,\n TRoleSpecifications = RoleSpecification,\n TFrontendComponentSpecifications = FrontendComponentSpecification,\n TCompositeViewSpecifications = CompositeViewSpecification,\n TFullCustomViewSpecifications = FullCustomViewSpecification,\n TFlowsActorsViewSpecifications = FlowsActorsViewSpecification,\n TChartViewSpecifications = ChartViewSpecification,\n TExecutionViewSpecifications = ExecutionViewSpecification,\n TSystemEmailTemplateSpecifications = SystemEmailTemplateSpecification,\n TOnboardingViewSpecifications = OnboardingViewSpecification,\n TGuidanceFlowSpecifications = GuidanceFlowSpecification,\n TDataSeedSpecifications = DataSeedSpecification,\n TMarketSnapshot = MarketSnapshot,\n TCatalogSpecifications = CatalogSpecifications,\n // Appended LAST (not inserted mid-list): consumers pass these generics\n // positionally (see the app companion-exports), so a new param must go at the\n // end to avoid shifting existing ones onto the wrong types.\n TSidebarSectionSpecifications = SidebarSectionSpecification,\n TAssertionSpecifications = AssertionSpecificationSnapshot,\n // ── app-creation meta-workflows C-4 definition families (U1–U4) — RESERVED SLOTS ──\n // Four sibling `_core` families each register ONE companion-exports slot here,\n // appended STRICTLY LAST in this FIXED order. Each session appends its generic\n // param (below) AND its interface field (further down) AFTER the previous\n // family's — NEVER re-order, NEVER insert mid-list. Consumers pass generics\n // positionally, so re-ordering silently shifts every later app onto the wrong\n // type. The reservation order (do not change):\n // All four reserved families are now registered (U1–U4 done); the\n // reserved-slots block below is fully filled and no further reservation\n // follows. The final order (do not change):\n // 1. vision (U1 — registered below)\n // 2. requirements (U2 — registered below)\n // 3. roadmap (U3 — registered below)\n // 4. business-model-lite (U4 — registered below, LAST)\n TVisionSnapshot = VisionSnapshot,\n TRequirementsSnapshot = RequirementsSnapshot,\n TRoadmapSnapshot = RoadmapSnapshot,\n TBuildPlanTaskGraph = BuildPlanTaskGraph,\n TPlacementPlan = PlacementPlan,\n TDomainPlanOutputSet = DomainPlanOutputSet,\n TBusinessModelLiteSnapshot = BusinessModelLiteSnapshot,\n // Appended STRICTLY LAST (positional generics — never insert mid-list):\n // the brand visual-identity definition family (`brand-brief`).\n TBrandSnapshot = BrandSnapshot,\n // Appended STRICTLY LAST: the expert-personas family (derived worker-persona\n // charters — plural array, unlike the singleton snapshot families above).\n TExpertPersonaCharters = ExpertPersonaCharter[],\n // Appended STRICTLY LAST: accepted spec-first feature intent. This is\n // deliberately distinct from `featureSpecifications`, whose entries already\n // decorate runtime FeatureDefinitions and therefore represent a later stage.\n TFeatureSpecificationDrafts = FeatureSpecificationDrafts,\n // Appended STRICTLY LAST: accepted application compliance policy. The slot\n // remains optional so applications that do not opt into `compliance-program`\n // preserve their existing projection and family-head behavior.\n TComplianceSpecification = AssuranceProgramSpecification,\n // Appended STRICTLY LAST: the application's accepted public-document\n // publication variants (`document-publication` family). Separate from\n // `complianceSpecification` on purpose — see the field's JSDoc.\n TDocumentPublicationSpecification = ApplicationDocumentPublicationSpecification,\n // Appended STRICTLY LAST: accepted document facts that cannot be inferred\n // from other semantic families. Raw decisions only; runtime grants,\n // approvals and releases never enter companion exports.\n TDocumentFactSpecification = ApplicationDocumentFactSpecification,\n // Appended STRICTLY LAST: release-process selection is a separate accepted\n // decision, never an implicit default of routing or document necessity.\n TDocumentReleasePolicySpecification = ApplicationDocumentReleasePolicySpecification,\n TDocumentReleaseSet = ApplicationDocumentReleaseSet,\n // Appended STRICTLY LAST: WHO else processes personal data, under what legal\n // identity and where (issue #88). Optional, and the optionality is the design:\n // a partial register is useful and its holes are REPORTED per provider against\n // the application's configured set, rather than blocking anything.\n TProcessorRegister = ApplicationProcessorRegister,\n // Appended STRICTLY LAST: the human half of the document facts, in its own\n // family, because the derived one is REGENERATED whole (#192).\n TAuthoredDocumentFactSpecification = ApplicationAuthoredDocumentFactSpecification,\n // Appended STRICTLY LAST: the releases the application has DECIDED to make,\n // which `wildo config document-releases` composes into recorded data (#968).\n TDocumentReleaseCompositions = readonly GovernedDocumentReleaseComposition[],\n // Appended STRICTLY LAST: WHICH RISKS the application carries and under what\n // posture (#300). Optional like every family slot, and the companion is what\n // reads it — see the field below for why a family without a slot is invisible.\n TRiskRegister = ApplicationRiskRegister,\n // Appended STRICTLY LAST: the creator's interview answers — the dossier's\n // committed half (#1454). Optional like every family slot; a playbook run\n // reads its interview from here by default.\n TCreatorInputs = ApplicationCreatorInputs,\n // Appended STRICTLY LAST: which composition scenarios the application needs,\n // derived from its definition families (#1491). Optional like every family\n // slot; the foundation executor is what reads it.\n TCapabilityComposition = CapabilityComposition,\n // Appended STRICTLY LAST: what the marketing website says, page by page (#1492).\n // Optional like every family slot; the decomposer is what reads it.\n TWebsitePlan = WebsitePlan,\n // Appended STRICTLY LAST: the application's views, shell and navigation composition (#1493).\n TExperiencePlan = ExperiencePlan,\n // Appended STRICTLY LAST: which chapters the documentation portal carries (#1494).\n TApplicationDocumentationPlan = ApplicationDocumentationPlan,\n // Appended STRICTLY LAST: the workers, minions and provider bindings (#1495).\n TIntegrationPlan = IntegrationPlan,\n // Appended STRICTLY LAST: where the application stands against its own requirements (#1496).\n TApplicationMaturity = ApplicationMaturity,\n> {\n resourceSpecifications: TResourceSpecifications;\n applicationBusinessSemanticsSnapshot?: TBusinessSemanticsSnapshot;\n /**\n * Feature overlays exposed to the dev companion.\n *\n * **Required** (promoted 2026-04-22, carryforward #5 of the\n * `non-view-specification-coverage` plan). The engine ships 7 explicit\n * `CoreFeature` overlays plus an `EngineCapability`-derived programmatic\n * module via `engineFeatureSpecifications`, so apps always have\n * something to expose. Apps with no app-level feature overlays should\n * pass `engineFeatureSpecifications` directly; apps with overlays\n * should merge their own bi-scoped map on top using the same\n * `buildFeatureSpecificationMap(...)` factory used by Wonder Todos.\n */\n featureSpecifications: TFeatureSpecifications;\n /**\n * Milestone overlays exposed to the dev companion.\n *\n * **Required** (promoted 2026-04-22, carryforward #5). Engine ships\n * zero milestone overlays today (apps own the catalog), but the\n * required discipline forces apps to either pass an explicit\n * `buildMilestoneSpecificationMap()` (empty or otherwise) or wire a\n * real overlay registry — eliminating the silent \"I forgot to wire\n * this surface\" failure mode the optional shape allowed.\n */\n milestoneSpecifications: TMilestoneSpecifications;\n /**\n * Product overlays exposed to the dev companion.\n *\n * **Required** (promoted 2026-04-22, carryforward #5). Same rationale\n * as `milestoneSpecifications` — engine ships zero today, but the\n * required shape eliminates the silent-omission failure mode.\n */\n productSpecifications: TProductSpecifications;\n /**\n * Role overlays exposed to the dev companion.\n *\n * **Required** (promoted 2026-04-22, carryforward #5). Engine ships\n * 13 explicit core-role overlays via `engineRoleSpecifications` (one\n * per `CORE_APP_ROLES.*` member), so apps always have something to\n * expose. Apps with no app-level roles should pass\n * `engineRoleSpecifications` directly.\n */\n roleSpecifications: TRoleSpecifications;\n frontendComponentSpecifications?: TFrontendComponentSpecifications;\n compositeViewSpecifications?: TCompositeViewSpecifications;\n fullCustomViewSpecifications?: TFullCustomViewSpecifications;\n flowsActorsViewSpecifications?: TFlowsActorsViewSpecifications;\n chartViewSpecifications?: TChartViewSpecifications;\n executionViewSpecifications?: TExecutionViewSpecifications;\n /**\n * Sidebar-section overlays exposed to the dev companion. Optional: sidebar\n * sections are structural app-shell config with no prose of their own; an app\n * that wants grounded sidebar labels authors a\n * `buildSidebarSectionSpecificationMap(...)` here, otherwise the family falls\n * back to keys-only generation.\n */\n sidebarSectionSpecifications?: TSidebarSectionSpecifications;\n /**\n * System-email template overlays exposed to the dev companion.\n *\n * **Required** because the engine ships 12 templates out of the box\n * (`engineSystemEmailTemplateSpecifications`); apps therefore always have\n * something to expose, and forgetting to wire this surface would silently\n * lose the entire system-email companion family. Apps with no app-level\n * templates should pass `engineSystemEmailTemplateSpecifications` directly.\n */\n systemEmailTemplateSpecifications: TSystemEmailTemplateSpecifications;\n /**\n * Onboarding-view overlays exposed to the dev companion.\n *\n * **Required** (promoted 2026-04-22, carryforward #5). Engine ships\n * zero onboarding views by default, but the required shape eliminates\n * the silent-omission failure mode. Apps with no app-level onboarding\n * views should pass an empty `buildOnboardingViewSpecificationMap()`\n * rather than omitting the field.\n */\n onboardingViewSpecifications: TOnboardingViewSpecifications;\n /**\n * Guidance-flow overlays exposed to the dev companion.\n *\n * **Required** (promoted 2026-04-22, carryforward #5). Same discipline\n * as `onboardingViewSpecifications` — engine ships zero by default,\n * but the required shape eliminates the silent-omission failure mode.\n * Apps with no app-level guidance flows should pass an empty\n * `buildGuidanceFlowSpecificationMap()` rather than omitting the field.\n */\n guidanceFlowSpecifications: TGuidanceFlowSpecifications;\n /**\n * Data-seeding overlays exposed to the dev companion.\n *\n * **Optional** in Phase 1 because the engine ships zero seeds yet — the\n * `DataSeedRegistry` and the dispatcher land in Phase 2. Authoring a seed\n * spec without the runtime declaration is allowed (the spec slice is\n * useful as design documentation on its own); authoring a runtime seed\n * without a spec is also allowed (no companion grounding, dispatcher\n * still runs it). Once Phase 2 ships engine seeds this field will be\n * promoted to required, mirroring `systemEmailTemplateSpecifications`.\n *\n * Apps with no app-level seeds should pass an empty\n * `buildDataSeedSpecificationMap()` rather than omitting the field once\n * Phase 2 lands.\n */\n dataSeedSpecifications?: TDataSeedSpecifications;\n /**\n * Application market specification — the English-authored marketing /\n * positioning truth (category, ICPs, personas, jobs/pains/gains, tones\n * of voice, benefits, positionings, message templates). Optional today\n * because not every example app authors a market snapshot yet; once it\n * graduates to required, app bootstraps should run\n * `validateMarketSnapshot` on the value before wiring it here.\n *\n * Authored entirely in English. Geographic targeting (the only\n * \"localization\" the slice models) lives inside\n * `MarketICP.profile.geographies`.\n */\n marketSpecification?: TMarketSnapshot;\n /**\n * Catalog specifications — declarations of EXTERNAL vocabularies the\n * framework reasons about (Schema.org JSON-LD today; future:\n * OpenAPI, RSS, JSON-Feed). Distinct from overlay specs above —\n * overlay specs decorate registry entries (resources, features,\n * views); catalog specs OWN the contract for an external\n * vocabulary's per-entity shape (required / optional / deprecated\n * field declarations).\n *\n * **Composition**: apps spread the engine catalog (e.g.\n * `ENGINE_SCHEMA_ORG_CATALOG`) and append app-side extensions /\n * overrides. The companion's catalog reconciliation runs against\n * this merged surface — emission sites in `@wildo-ai/saas-website`\n * sections (via `getStructuredData()`) are checked against the\n * merged `schemaOrg` catalog, with warnings on missing required\n * fields, deprecated-field usage, and (when wired) missing\n * recommended optionals. Catalog overrides (app entry redefining\n * an engine entry's `@type`) emit a `catalog-override` boot\n * warning.\n *\n * **Optional**: an application that declares no catalog is reconciled\n * against the engine's (`resolveApplicationSchemaOrgCatalog`), which is\n * the one answer the CLI audit and the companion share. Populate the\n * slot only to override engine entries.\n */\n catalogSpecifications?: TCatalogSpecifications;\n /**\n * Assertion surface — the authored layer of the dynamic Assertion\n * Surface (app-creation meta-workflows, master plan S1): statements\n * about the platform served via the companion `assertions-list` /\n * `assertions-resolve` / `assertions-reconcile` behaviors, with\n * status computed by reconcile rather than hand-maintained.\n *\n * **Optional** — the launch posture of every new family: not every\n * example app authors assertions yet, and the family must not break\n * existing companion exports on arrival. Once it graduates to\n * required, app bootstraps should run\n * `validateAssertionSpecificationSnapshot` on the value before\n * wiring it here (the behavior resolver validates on entry either\n * way, market-style).\n *\n * Lane discipline: entries carrying\n * `lane: AssertionLane.FRAMEWORK_DEV` are framework-development\n * knowledge (end-state platform bets authored in the dogfood app\n * during the framework-parallel era) and must NEVER compile into\n * shipped app knowledge — consumers filter on `lane` deliberately.\n */\n assertionSpecifications?: TAssertionSpecifications;\n // ── app-creation meta-workflows C-4 definition families (U1–U4) — FIELDS ──\n // One field per family, in the SAME fixed order as the generic params\n // above. All four are now registered (U1–U4 done); no reservation remains:\n // 1. visionSpecification (U1 — below)\n // 2. requirementsSpecification (U2 — below)\n // 3. roadmapSpecification (U3 — below)\n // 4. businessModelLiteSpecification (U4 — below, LAST)\n /**\n * Application **vision** specification — the foundational-intent truth\n * (idea, problem statement, mission, success criteria, constraints incl.\n * compliance) the app-creation top-down catalog reads/writes (C-4\n * definition families). A single aggregate per app (market-snapshot\n * style), validated by `validateVisionSnapshot`.\n *\n * **Optional** — the launch posture of every new family (market /\n * assertions parity): not every example app authors a vision snapshot\n * yet, and the family must not break existing companion exports on\n * arrival. Once it graduates to required, app bootstraps should run\n * `validateVisionSnapshot` on the value before wiring it here.\n */\n visionSpecification?: TVisionSnapshot;\n /**\n * Application **requirements** specification — the requirements-layer\n * truth (functional requirements + non-functional requirements, each\n * optionally cross-referencing market ICPs / jobs) the app-creation\n * top-down capability-map catalog reads/writes (C-4 definition\n * families). A single aggregate per app (market-snapshot style),\n * validated by `validateRequirementsSnapshot`.\n *\n * **Optional** — the launch posture of every new family (vision /\n * market / assertions parity): not every example app authors a\n * requirements snapshot yet, and the family must not break existing\n * companion exports on arrival. Once it graduates to required, app\n * bootstraps should run `validateRequirementsSnapshot` on the value\n * before wiring it here.\n */\n requirementsSpecification?: TRequirementsSnapshot;\n /**\n * Application **roadmap** specification — the delivery-roadmap truth (a\n * product's delivery plan as an ordered collection of releases/phases,\n * each optionally cross-referencing the requirements /\n * vision-success-criteria it delivers) the app-creation top-down\n * scope/roadmap catalog reads/writes (C-4 definition families). A single\n * aggregate per app (market-snapshot style), validated by\n * `validateRoadmapSnapshot`. Distinct from `milestoneSpecifications` (a\n * dated registry-overlay surface) — a roadmap phase is a planning\n * artifact, not a runtime milestone.\n *\n * **Optional** — the launch posture of every new family (vision /\n * requirements / market / assertions parity): not every example app\n * authors a roadmap snapshot yet, and the family must not break existing\n * companion exports on arrival. Once it graduates to required, app\n * bootstraps should run `validateRoadmapSnapshot` on the value before\n * wiring it here.\n */\n roadmapSpecification?: TRoadmapSnapshot;\n /**\n * Application **build-plan** specification — the ORDERED typed task graph\n * (`BuildPlanTaskGraph`, `_core/build-plan/`) that turns the accepted domain\n * plan into buildable units; produced by the build-decompose playbook and\n * consumed one READY task at a time by build-dispatch. Optional until an\n * application reaches the bottom-up phase; app bootstraps should run\n * `validateBuildPlanTaskGraph` on the value before wiring it here.\n */\n buildPlanSpecification?: TBuildPlanTaskGraph;\n /**\n * Application **placement** specification — WHERE every settings destination,\n * resource operation and app view sits in the shell, and WHY (`PlacementPlan`,\n * `_core/placement-plan/`).\n *\n * Produced by the `bottom_up.placement-plan` playbook as an expert-panel\n * DELIBERATION rather than a creator elicitation: the creator does not choose\n * placement, so each decision carries a `rationale` that answers \"why is this\n * here?\" without re-running the panel. Consumed by build-decompose, which\n * turns it into the coding tasks that author `settings-hub.config.ts` and\n * `app-shell.config.ts`.\n *\n * Optional until an application reaches the bottom-up phase; app bootstraps\n * should run `validatePlacementPlan` on the value before wiring it here.\n */\n placementPlanSpecification?: TPlacementPlan;\n /**\n * Application **domain-plan** specification — the atomic module decomposition\n * PLUS relationship drafts (`DomainPlanOutputSet`, `_core/domain-plan/`);\n * produced by the domain-plan playbook, decomposed by build-decompose.\n * Optional until an application reaches the bottom-up phase.\n */\n domainPlanSpecification?: TDomainPlanOutputSet;\n /**\n * Application **business-model-lite** specification — the lightweight\n * business-model truth (a coarse product-level revenue model + a pricing-\n * plan sketch, each plan optionally cross-referencing the market ICPs it\n * targets and the requirements it includes) the app-creation top-down\n * catalog reads/writes (C-4 definition families). A single aggregate per\n * app (market-snapshot style), validated by\n * `validateBusinessModelLiteSnapshot`. A PLANNING artifact — deliberately\n * NOT the live billing / Stripe product-catalog runtime (it models\n * pricing INTENT, never chargeable state). The `-lite` is the\n * scaffold-depth qualifier of the Phase-J1 increment; the artifact-family\n * id is `business-model`.\n *\n * **Optional** — the launch posture of every new family (vision /\n * requirements / roadmap / market / assertions parity): not every example\n * app authors a business-model snapshot yet, and the family must not break\n * existing companion exports on arrival. Once it graduates to required,\n * app bootstraps should run `validateBusinessModelLiteSnapshot` on the\n * value before wiring it here.\n */\n businessModelLiteSpecification?: TBusinessModelLiteSnapshot;\n /**\n * Application **brand** specification — the visual-identity brief (brand\n * name + logo direction + visual tone; `resolvedAssets` populated by the\n * companion logo step) the app-creation top-down `brand-identity` playbook\n * reads/writes. A single aggregate per app (vision-snapshot style),\n * validated by `validateBrandSnapshot`. Read by the companion\n * `brand-render-prompt` behavior to assemble the logo generation prompt;\n * the artifact-family id is `brand-brief`.\n *\n * **Optional** — the launch posture of every new family: not every example\n * app authors a brand snapshot yet, and the family must not break existing\n * companion exports on arrival.\n */\n brandSpecification?: TBrandSnapshot;\n /**\n * Application **expert-persona charters** — the DERIVED worker-persona\n * instances (`ExpertPersonaCharter[]`) of the framework's\n * `EXPERT_ROLE_TEMPLATES` (art-director, copy-chief, …), committed under\n * `specifications/src/personas/` by the companion's derive→accept flow\n * (and hand-editable thereafter; a human edit is recorded in `authored`).\n *\n * Consumed by the companion's `expert-persona-charters` introspection\n * behavior: the deliberation system builds each expert's agent from the\n * committed charter at startup, and the accept step reads the set for its\n * human-edit overwrite guard + `validateExpertPersonaCharters` run.\n *\n * PLURAL by design (unlike the singleton snapshot families above): an app\n * has one charter per role, several roles. Distinct from the market\n * family's `personas` (BUYER personas — who the app sells to); these are\n * WORKER personas (who does the creative work).\n *\n * **Optional** — the launch posture of every new family: not every example\n * app has derived charters yet, and the family must not break existing\n * companion exports on arrival. Apps with charters should export the\n * generated `appExpertPersonaCharters` aggregate from\n * `specifications/src/personas/`.\n */\n expertPersonaCharters?: TExpertPersonaCharters;\n /**\n * Accepted **feature drafts** produced by the top-down capability-map.\n *\n * Drafts carry product intent only: purpose, business role, lifecycle and\n * availability guidance. They deliberately exclude runtime-definition\n * provenance and executable scope. Phase-gate and domain-planning evidence\n * consume this member; `featureSpecifications` remains the separate\n * runtime-backed overlay surface used after capabilities are implemented.\n *\n * **Optional** at the aggregate contract boundary because applications that\n * have not entered the app-creation workflow may not have accepted drafts.\n * A treatment selecting the `feature-drafts` family fails closed when the\n * member is absent.\n */\n featureDraftsSpecification?: TFeatureSpecificationDrafts;\n /**\n * Accepted application **compliance program** policy.\n *\n * This is the configured application's reusable source/scope/objective,\n * implementation-choice, responsibility, gap/exception and documentation\n * truth. It deliberately excludes live organizations, assignees, reviewer\n * identities, evidence bytes and operating-effectiveness claims.\n *\n * **Optional** at launch. If the application declares the\n * `compliance-program` family, the semantic family authority requires this\n * member and validates it fail closed. Applications without that family must\n * not synthesize this value or receive positive compliance-program claims.\n */\n complianceSpecification?: TComplianceSpecification;\n /**\n * Accepted application **public-document publication variants**.\n *\n * The exact locale × jurisdiction combinations in which this application\n * publishes public governed documents. It is the ONLY source a governed\n * document candidate may take its locale and jurisdictions from.\n *\n * That is a contract statement, not a running check: there is no candidate host binding these\n * bytes to the `document-publication` family's retained head, and nothing today refuses a\n * combination that is not an exact member. Whatever begins producing candidates owes the refusal.\n *\n * Distinct from `complianceSpecification` by design. The assurance program\n * decides which documents are required and who approves them; this slot\n * decides where and in which language they are published. Folding the two\n * would let a document requirement widen its own publication routing.\n *\n * **Optional** at the aggregate contract boundary. An application that\n * declares no `document-publication` family publishes no public governed\n * document. Candidate creation is INTENDED to fail closed there rather than default to a locale\n * or jurisdiction nobody accepted; as above, no code enforces that yet.\n */\n documentPublicationSpecification?: TDocumentPublicationSpecification;\n /**\n * Accepted application selection of the human release lane for each exact\n * governed-document requirement. Optional at the aggregate boundary: an\n * application with no policy can still generate a working draft, but every\n * exposure attempt fails closed rather than assuming operator attestation or\n * qualified review.\n */\n documentReleasePolicySpecification?: TDocumentReleasePolicySpecification;\n /**\n * The governed-document **releases** the application has composed.\n *\n * Optional, and an EMPTY set is the honest answer for an application that has\n * drafted nothing yet. What this slot must never be read as is a list of\n * PUBLISHED documents: every release states its own `approvalState`, and one\n * nobody has approved is `UNAPPROVED` and present here anyway — approval is a\n * workflow act that happens at the end, so an application holds its releases\n * from the moment they are composed.\n *\n * A surface serving a REAL reader obeys `compliance.governedDocumentApprovalGate`; nothing in\n * this slot does that filtering for it.\n */\n documentReleaseSet?: TDocumentReleaseSet;\n /**\n * The governed-document releases the application has **decided** to make — which draft, which\n * declared variant, when it takes effect — as composer inputs (wildo-ai/wildo-ai#968).\n *\n * Decisions, not releases. `wildo config document-releases` composes each decision whose release\n * identity is not yet in `documentReleaseSet` and records the finished release, text included, as\n * committed data. A recorded release is never recomposed, so editing a draft afterwards changes no\n * release; publishing new text is a new decision with the next `releaseVersion`.\n *\n * Optional: an application that composes no releases declares none, and one that already records\n * its releases some other way loses nothing.\n */\n documentReleaseCompositions?: TDocumentReleaseCompositions;\n /**\n * Accepted application **governed-document facts**.\n *\n * This optional slot carries the `document-facts` family: declarations answered from the accepted\n * specification, under `APPLICATION_SPECIFICATION` authority only. `refinement.document-facts`\n * produces it and a commit accepts it; creator decisions and qualified reviews live in the authored\n * slot below. Nothing is sealed or digested — validation re-reads the file.\n *\n * Candidates and releases belong to their own families and are not carried here.\n * Omitting it is honest: unresolved document facts remain visible gaps.\n */\n documentFactSpecification?: TDocumentFactSpecification;\n /**\n * Accepted application governed-document facts **only a human may establish** — a creator decision\n * or a qualified review (`document-facts-authored`).\n *\n * The same shape as the slot above, and a separate family on purpose. `refinement.document-facts`\n * rewrites the derived file whole, so a human decision sharing that file is destroyed on the next\n * run with nothing to notice: there is no compare-and-swap here, deliberately — nothing is kept\n * that cannot branch and merge on git. Two families put the two writers out of each\n * other's reach.\n *\n * No producer may write this family — it has no generation contract, and that absence is the design\n * rather than an omission.\n *\n * A reader wanting \"the application's facts\" needs BOTH slots. `collectComplianceDocumentFactAvailability`\n * is variadic for exactly that reason.\n */\n authoredDocumentFactSpecification?: TAuthoredDocumentFactSpecification;\n /**\n * WHO else processes this application's personal data — legal identity, processing region and the\n * processor's own subprocessors (issue #88).\n *\n * A configured provider already establishes THAT a third party is involved and what function it\n * performs. None of that is what a privacy notice's recipient statement needs, and an\n * international-transfer statement cannot be made at all without a region.\n *\n * Optional, and its holes are reported rather than blocking: the companion compares this register\n * against the application's CONFIGURED providers and names each one that is undeclared, so a partial\n * register is useful and an empty one still produces an actionable document. An absent entry means\n * nobody has established that processor's identity — never that the provider is unused.\n */\n processorRegister?: TProcessorRegister;\n /**\n * WHICH RISKS this application carries, and under what posture — the accepted risk register (#300).\n *\n * ## Why a family that \"the runtime does not consume\" still needs a slot\n *\n * This slot was almost omitted on the reasoning that the application RUNTIME never reads the\n * register: it is accepted by a human and read by assurance tooling over the committed file, which\n * is exactly the case `ApplicationSpecificationSemanticSchemaBinding.companionExportsField`\n * describes as \"lands as a file to review, and is deliberately not wired\".\n *\n * That reasoning is about the runtime and the question is about the COMPANION.\n * `family-aspects.behavior.ts` reads a landed family through this aggregate and nowhere else — a\n * binding with no slot yields an undefined snapshot, so every aspect of that family projects an\n * empty item list. The register's rows would have been addressable, navigable, labelled, and\n * permanently absent: a resource that cannot ever hold a row.\n *\n * Optional, like every family slot: an application that has not accepted a register simply has\n * none, and the aspect resource is empty because there is nothing rather than because nothing can\n * reach it.\n */\n riskRegister?: TRiskRegister;\n /**\n * WHAT THE CREATOR SAID — every interview answer, by playbook and question ref (#1454, Step 5).\n *\n * The slot is what makes the dossier READABLE by the companion, exactly as the risk register's\n * note above explains: a playbook run resolves its interview answers through this aggregate and\n * nowhere else, so a landed dossier with no slot would be a file nobody reads. Optional, because\n * an application that has answered nothing simply has no dossier yet.\n */\n creatorInputs?: TCreatorInputs;\n /**\n * WHICH COMPOSITION SCENARIOS the application needs — website, documentation portal, workers,\n * minions, locales — one decision per scenario the framework ships, each naming the declaration\n * it was derived from (#1491). The foundation executor reads it through this slot and applies\n * the NEEDED ones; a landed composition with no slot would be a file nobody reads, exactly as\n * the risk register's note above explains.\n */\n capabilityComposition?: TCapabilityComposition;\n /**\n * WHAT THE MARKETING WEBSITE SAYS — its pages, their sections in reading order, and the market\n * entries each draws on (#1492). Read by `bottom_up.build-decompose`, which turns each page and\n * each section into a build task bound to the skill that authors it. Optional: an application\n * whose capability composition declined a website lands a NOT_APPLICABLE plan, and one that has\n * not reached the website step has none at all.\n */\n websitePlan?: TWebsitePlan;\n /**\n * WHAT THE APPLICATION'S EXPERIENCE IS — the views it carries beyond its resources' generated\n * screens, the shell and navigation composition, and the preset components each view reuses\n * (#1493). Read by `bottom_up.build-decompose`, which turns each entry into a build task bound to\n * the skill its kind names. Optional: an application that has not reached the experience step has\n * none, and its build plan simply carries no view or configuration task.\n */\n experiencePlan?: TExperiencePlan;\n /**\n * WHICH CHAPTERS the documentation portal carries, what each documents and who it is for (#1494).\n * Read by `bottom_up.build-decompose`, which turns each chapter into a task, and by the documentation\n * publication, which takes each chapter's identity from here and its body from\n * `documentationChapters` below (#874).\n */\n documentationPlan?: TApplicationDocumentationPlan;\n /**\n * THE AUTHORED BODY of each chapter `documentationPlan` declares, keyed by `chapterRef` (#874) —\n * from `specifications/src/technical-documentation/index.ts`, accepted by being committed.\n *\n * Read by the documentation publication, which joins each body to its planned chapter and publishes\n * it as a guide: a chapter the plan does not declare, and a `RESTRICTED` or unapproved one, is\n * withheld and reported, and an API reference that does not resolve against the rendered reference\n * fails the publication. Optional, and absent is honest: the portal then carries only its derived pages.\n *\n * Typed directly rather than through a positional generic: no application narrows it, and a new\n * positional parameter would only add a slot for every consumer to skip.\n */\n documentationChapters?: ApplicationDocumentationChapterSet;\n /**\n * WHAT RUNS BESIDE THE BACKEND — the application's workers and minions, what each is for, what a\n * minion's tick may touch, and the providers this application binds (#1495). Read by\n * `bottom_up.build-decompose`, which turns each into a build task bound to `worker-authoring`,\n * `minion-authoring` or the provider skills.\n */\n integrationPlan?: TIntegrationPlan;\n /**\n * WHERE THIS APPLICATION STANDS against what it asked of itself (#1496) — one row per requirement\n * with the evidence that exists for it, and the stage that follows. A READING: derived from the\n * requirements, the decided-element graph and the build plan's landing probe, never generated and\n * never a gate. Read by the coherence report and the workbench.\n */\n applicationMaturity?: TApplicationMaturity;\n /**\n * Accepted application-declared semantic causality between whole\n * specification-family states. This is not the registry's physical\n * dependency graph and not Actor/Flow execution order. The runtime resolves\n * these declarations only through the exact CURRENT accepted projection,\n * then may derive a rebuildable impact index; this export itself does not\n * authorize a journal write, review queue or application mutation.\n *\n * Optional because semantic impact is an advanced application-creation\n * capability. An application that declares the dedicated\n * `semantic-dependencies` family must provide this field; a resolver refuses\n * a missing or malformed value rather than infer dependencies from imports\n * or registry edges.\n */\n}\n\n/**\n * Aggregate of every catalog vocabulary an app can wire on the\n * `catalogSpecifications` companion-exports slot.\n *\n * Each vocabulary is a flat array of validated entries (engine\n * + app entries merged at wiring time). The companion harness keys\n * each vocabulary by its discriminator (`@type` for Schema.org;\n * future vocabularies can use `operationId`, `kind`, etc.); app\n * entries silently override engine entries on collision and the\n * harness emits a `catalog-override` warning for each override at\n * boot.\n *\n * **Why an aggregate type and not per-slot fields**: every future\n * vocabulary lands as a sibling field on this single type rather\n * than as a new top-level companion-exports field. This keeps the\n * `SpecificationsCompanionExports` shape stable as the catalog\n * surface grows.\n */\nexport interface CatalogSpecifications {\n /**\n * Schema.org JSON-LD vocabulary catalog. Compose with\n * `ENGINE_SCHEMA_ORG_CATALOG` (engine-shipped standard entries)\n * spread, then append app-side extensions / overrides.\n */\n schemaOrg?: readonly SchemaOrgCatalogEntryBase[];\n}\n/** @wildo_source:part:end saas.specifications.companion-exports.contract */\n"]}
1
+ {"version":3,"file":"companion-exports.js","sourceRoot":"","sources":["../../../src/companion-exports.ts"],"names":[],"mappings":"AAqDA,cAAc,gFAAgF,CAAC;AAurB/F,4EAA4E","sourcesContent":["import type { AssertionSpecificationSnapshot } from './_core/assertions/assertion-specification.schemas';\nimport type { BrandSnapshot } from './_core/brand/brand-snapshot.schemas';\nimport type { BuildPlanTaskGraph } from './_core/build-plan/build-plan-task-graph.schemas';\nimport type { PlacementPlan } from './_core/placement-plan/placement-plan.schemas';\nimport type { DomainPlanOutputSet } from './_core/domain-plan/domain-plan-output-set.schemas';\nimport type { ExpertPersonaCharter } from './_core/expert-personas/expert-persona-charter.schemas';\nimport type { BusinessModelLiteSnapshot } from './_core/business-model-lite/business-model-lite-snapshot.schemas';\nimport type { BusinessSemanticsSnapshotDeclaration } from './_core/business-semantics.specifications.schemas';\nimport type { ChartViewSpecification } from './_core/chart-view-specification.schemas';\nimport type { CompositeViewSpecification } from './_core/composite-view-specification.schemas';\nimport type { DataSeedSpecification } from './_core/data-seed-specification.schemas';\nimport type {\n FeatureSpecification,\n MilestoneSpecification,\n ProductSpecification,\n RoleSpecification,\n} from './_core/definition-specification.schemas';\nimport type { ExecutionViewSpecification } from './_core/execution-view-specification.schemas';\nimport type { FlowsActorsViewSpecification } from './_core/flows-actors-view-specification.schemas';\nimport type { FrontendComponentSpecification } from './_core/frontend-component-specification.schemas';\nimport type { FeatureSpecificationDrafts } from './_core/feature-drafts/feature-specification-drafts.schemas';\nimport type { FullCustomViewSpecification } from './_core/full-custom-view-specification.schemas';\nimport type { GuidanceFlowSpecification } from './_core/guidance-flow-specification.schemas';\nimport type { MarketSnapshot } from './_core/market/market-snapshot.schemas';\nimport type { OnboardingViewSpecification } from './_core/onboarding-view-specification.schemas';\nimport type { RequirementsSnapshot } from './_core/requirements/requirements-snapshot.schemas';\nimport type { ResourceSpecification } from './_core/resource-specification.schemas';\nimport type { RoadmapSnapshot } from './_core/roadmap/roadmap-snapshot.schemas';\nimport type { SidebarSectionSpecification } from './_core/sidebar-section-specification.schemas';\nimport type { SystemEmailTemplateSpecification } from './_core/system-email-template-specification.schemas';\nimport type { VisionSnapshot } from './_core/vision/vision-snapshot.schemas';\nimport type { SchemaOrgCatalogEntryBase } from './_catalogs/schema-org';\nimport type { ApplicationDocumentPublicationSpecification } from './assurance/application-document-publication.schemas';\nimport type {\n ApplicationAuthoredDocumentFactSpecification,\n ApplicationDocumentFactSpecification,\n} from './application-creation/application-document-fact-specification.application-creation.schemas';\nimport type { ApplicationProcessorRegister } from './_core/compliance-documents/processor-register.schemas';\nimport type { ApplicationRiskRegister } from './assurance/application-risk-register.schemas';\nimport type { ApplicationCreatorInputs } from './application-creation/application-creator-inputs.application-creation.schemas';\nimport type { CapabilityComposition } from './_core/capability-composition/capability-composition.schemas';\nimport type { WebsitePlan } from './_core/website-plan/website-plan.schemas';\nimport type { ExperiencePlan } from './_core/experience-plan/experience-plan.schemas';\nimport type { ApplicationDocumentationPlan } from './technical-documentation/application-documentation-plan.schemas';\nimport type { ApplicationDocumentationChapterSet } from './technical-documentation/application-documentation-chapters.schemas';\nimport type { IntegrationPlan } from './_core/integration-plan/integration-plan.schemas';\nimport type { ApplicationMaturity } from './_core/application-maturity/application-maturity.schemas';\nimport type { BrandNameScreening } from './_core/brand/brand-name-screening.schemas';\nimport type { ApplicationDocumentReleasePolicySpecification } from './application-creation/application-document-release-policy-specification.application-creation.schemas';\nimport type { ApplicationDocumentReleaseSet } from './assurance/application-document-release-set.schemas';\nimport type { GovernedDocumentReleaseComposition } from './assurance/governed-document-release';\nimport type { AssuranceProgramSpecification } from './assurance/assurance-program.schemas';\n\nexport * from './technical-documentation/engine-documentation-specification-catalog.companion';\n\n/**\n * @wildo_source:part:start saas.specifications.companion-exports.contract facet:layer:specification facet:family:companion\n *\n * Typed companion export surface: registries of resource specs, definitions, and view specs the dev companion materializes.\n */\nexport interface SpecificationsCompanionExports<\n TResourceSpecifications = ResourceSpecification,\n // The AUTHORED shape: a companion reader parses it with `BusinessSemanticsSnapshotSchema`.\n TBusinessSemanticsSnapshot = BusinessSemanticsSnapshotDeclaration,\n TFeatureSpecifications = FeatureSpecification,\n TMilestoneSpecifications = MilestoneSpecification,\n TProductSpecifications = ProductSpecification,\n TRoleSpecifications = RoleSpecification,\n TFrontendComponentSpecifications = FrontendComponentSpecification,\n TCompositeViewSpecifications = CompositeViewSpecification,\n TFullCustomViewSpecifications = FullCustomViewSpecification,\n TFlowsActorsViewSpecifications = FlowsActorsViewSpecification,\n TChartViewSpecifications = ChartViewSpecification,\n TExecutionViewSpecifications = ExecutionViewSpecification,\n TSystemEmailTemplateSpecifications = SystemEmailTemplateSpecification,\n TOnboardingViewSpecifications = OnboardingViewSpecification,\n TGuidanceFlowSpecifications = GuidanceFlowSpecification,\n TDataSeedSpecifications = DataSeedSpecification,\n TMarketSnapshot = MarketSnapshot,\n TCatalogSpecifications = CatalogSpecifications,\n // Appended LAST (not inserted mid-list): consumers pass these generics\n // positionally (see the app companion-exports), so a new param must go at the\n // end to avoid shifting existing ones onto the wrong types.\n TSidebarSectionSpecifications = SidebarSectionSpecification,\n TAssertionSpecifications = AssertionSpecificationSnapshot,\n // ── app-creation meta-workflows C-4 definition families (U1–U4) — RESERVED SLOTS ──\n // Four sibling `_core` families each register ONE companion-exports slot here,\n // appended STRICTLY LAST in this FIXED order. Each session appends its generic\n // param (below) AND its interface field (further down) AFTER the previous\n // family's — NEVER re-order, NEVER insert mid-list. Consumers pass generics\n // positionally, so re-ordering silently shifts every later app onto the wrong\n // type. The reservation order (do not change):\n // All four reserved families are now registered (U1–U4 done); the\n // reserved-slots block below is fully filled and no further reservation\n // follows. The final order (do not change):\n // 1. vision (U1 — registered below)\n // 2. requirements (U2 — registered below)\n // 3. roadmap (U3 — registered below)\n // 4. business-model-lite (U4 — registered below, LAST)\n TVisionSnapshot = VisionSnapshot,\n TRequirementsSnapshot = RequirementsSnapshot,\n TRoadmapSnapshot = RoadmapSnapshot,\n TBuildPlanTaskGraph = BuildPlanTaskGraph,\n TPlacementPlan = PlacementPlan,\n TDomainPlanOutputSet = DomainPlanOutputSet,\n TBusinessModelLiteSnapshot = BusinessModelLiteSnapshot,\n // Appended STRICTLY LAST (positional generics — never insert mid-list):\n // the brand visual-identity definition family (`brand-brief`).\n TBrandSnapshot = BrandSnapshot,\n // Appended STRICTLY LAST: the expert-personas family (derived worker-persona\n // charters — plural array, unlike the singleton snapshot families above).\n TExpertPersonaCharters = ExpertPersonaCharter[],\n // Appended STRICTLY LAST: accepted spec-first feature intent. This is\n // deliberately distinct from `featureSpecifications`, whose entries already\n // decorate runtime FeatureDefinitions and therefore represent a later stage.\n TFeatureSpecificationDrafts = FeatureSpecificationDrafts,\n // Appended STRICTLY LAST: accepted application compliance policy. The slot\n // remains optional so applications that do not opt into `compliance-program`\n // preserve their existing projection and family-head behavior.\n TComplianceSpecification = AssuranceProgramSpecification,\n // Appended STRICTLY LAST: the application's accepted public-document\n // publication variants (`document-publication` family). Separate from\n // `complianceSpecification` on purpose — see the field's JSDoc.\n TDocumentPublicationSpecification = ApplicationDocumentPublicationSpecification,\n // Appended STRICTLY LAST: accepted document facts that cannot be inferred\n // from other semantic families. Raw decisions only; runtime grants,\n // approvals and releases never enter companion exports.\n TDocumentFactSpecification = ApplicationDocumentFactSpecification,\n // Appended STRICTLY LAST: release-process selection is a separate accepted\n // decision, never an implicit default of routing or document necessity.\n TDocumentReleasePolicySpecification = ApplicationDocumentReleasePolicySpecification,\n TDocumentReleaseSet = ApplicationDocumentReleaseSet,\n // Appended STRICTLY LAST: WHO else processes personal data, under what legal\n // identity and where (issue #88). Optional, and the optionality is the design:\n // a partial register is useful and its holes are REPORTED per provider against\n // the application's configured set, rather than blocking anything.\n TProcessorRegister = ApplicationProcessorRegister,\n // Appended STRICTLY LAST: the human half of the document facts, in its own\n // family, because the derived one is REGENERATED whole (#192).\n TAuthoredDocumentFactSpecification = ApplicationAuthoredDocumentFactSpecification,\n // Appended STRICTLY LAST: the releases the application has DECIDED to make,\n // which `wildo config document-releases` composes into recorded data (#968).\n TDocumentReleaseCompositions = readonly GovernedDocumentReleaseComposition[],\n // Appended STRICTLY LAST: WHICH RISKS the application carries and under what\n // posture (#300). Optional like every family slot, and the companion is what\n // reads it — see the field below for why a family without a slot is invisible.\n TRiskRegister = ApplicationRiskRegister,\n // Appended STRICTLY LAST: the creator's interview answers — the dossier's\n // committed half (#1454). Optional like every family slot; a playbook run\n // reads its interview from here by default.\n TCreatorInputs = ApplicationCreatorInputs,\n // Appended STRICTLY LAST: which composition scenarios the application needs,\n // derived from its definition families (#1491). Optional like every family\n // slot; the foundation executor is what reads it.\n TCapabilityComposition = CapabilityComposition,\n // Appended STRICTLY LAST: what the marketing website says, page by page (#1492).\n // Optional like every family slot; the decomposer is what reads it.\n TWebsitePlan = WebsitePlan,\n // Appended STRICTLY LAST: the application's views, shell and navigation composition (#1493).\n TExperiencePlan = ExperiencePlan,\n // Appended STRICTLY LAST: which chapters the documentation portal carries (#1494).\n TApplicationDocumentationPlan = ApplicationDocumentationPlan,\n // Appended STRICTLY LAST: the workers, minions and provider bindings (#1495).\n TIntegrationPlan = IntegrationPlan,\n // Appended STRICTLY LAST: where the application stands against its own requirements (#1496).\n TApplicationMaturity = ApplicationMaturity,\n // Appended STRICTLY LAST: the screened brand-name candidates the brand-identity interview chooses from.\n TBrandNameScreening = BrandNameScreening,\n> {\n resourceSpecifications: TResourceSpecifications;\n applicationBusinessSemanticsSnapshot?: TBusinessSemanticsSnapshot;\n /**\n * Feature overlays exposed to the dev companion.\n *\n * **Required** (promoted 2026-04-22, carryforward #5 of the\n * `non-view-specification-coverage` plan). The engine ships 7 explicit\n * `CoreFeature` overlays plus an `EngineCapability`-derived programmatic\n * module via `engineFeatureSpecifications`, so apps always have\n * something to expose. Apps with no app-level feature overlays should\n * pass `engineFeatureSpecifications` directly; apps with overlays\n * should merge their own bi-scoped map on top using the same\n * `buildFeatureSpecificationMap(...)` factory used by Wonder Todos.\n */\n featureSpecifications: TFeatureSpecifications;\n /**\n * Milestone overlays exposed to the dev companion.\n *\n * **Required** (promoted 2026-04-22, carryforward #5). Engine ships\n * zero milestone overlays today (apps own the catalog), but the\n * required discipline forces apps to either pass an explicit\n * `buildMilestoneSpecificationMap()` (empty or otherwise) or wire a\n * real overlay registry — eliminating the silent \"I forgot to wire\n * this surface\" failure mode the optional shape allowed.\n */\n milestoneSpecifications: TMilestoneSpecifications;\n /**\n * Product overlays exposed to the dev companion.\n *\n * **Required** (promoted 2026-04-22, carryforward #5). Same rationale\n * as `milestoneSpecifications` — engine ships zero today, but the\n * required shape eliminates the silent-omission failure mode.\n */\n productSpecifications: TProductSpecifications;\n /**\n * Role overlays exposed to the dev companion.\n *\n * **Required** (promoted 2026-04-22, carryforward #5). Engine ships\n * 13 explicit core-role overlays via `engineRoleSpecifications` (one\n * per `CORE_APP_ROLES.*` member), so apps always have something to\n * expose. Apps with no app-level roles should pass\n * `engineRoleSpecifications` directly.\n */\n roleSpecifications: TRoleSpecifications;\n frontendComponentSpecifications?: TFrontendComponentSpecifications;\n compositeViewSpecifications?: TCompositeViewSpecifications;\n fullCustomViewSpecifications?: TFullCustomViewSpecifications;\n flowsActorsViewSpecifications?: TFlowsActorsViewSpecifications;\n chartViewSpecifications?: TChartViewSpecifications;\n executionViewSpecifications?: TExecutionViewSpecifications;\n /**\n * Sidebar-section overlays exposed to the dev companion. Optional: sidebar\n * sections are structural app-shell config with no prose of their own; an app\n * that wants grounded sidebar labels authors a\n * `buildSidebarSectionSpecificationMap(...)` here, otherwise the family falls\n * back to keys-only generation.\n */\n sidebarSectionSpecifications?: TSidebarSectionSpecifications;\n /**\n * System-email template overlays exposed to the dev companion.\n *\n * **Required** because the engine ships 12 templates out of the box\n * (`engineSystemEmailTemplateSpecifications`); apps therefore always have\n * something to expose, and forgetting to wire this surface would silently\n * lose the entire system-email companion family. Apps with no app-level\n * templates should pass `engineSystemEmailTemplateSpecifications` directly.\n */\n systemEmailTemplateSpecifications: TSystemEmailTemplateSpecifications;\n /**\n * Onboarding-view overlays exposed to the dev companion.\n *\n * **Required** (promoted 2026-04-22, carryforward #5). Engine ships\n * zero onboarding views by default, but the required shape eliminates\n * the silent-omission failure mode. Apps with no app-level onboarding\n * views should pass an empty `buildOnboardingViewSpecificationMap()`\n * rather than omitting the field.\n */\n onboardingViewSpecifications: TOnboardingViewSpecifications;\n /**\n * Guidance-flow overlays exposed to the dev companion.\n *\n * **Required** (promoted 2026-04-22, carryforward #5). Same discipline\n * as `onboardingViewSpecifications` — engine ships zero by default,\n * but the required shape eliminates the silent-omission failure mode.\n * Apps with no app-level guidance flows should pass an empty\n * `buildGuidanceFlowSpecificationMap()` rather than omitting the field.\n */\n guidanceFlowSpecifications: TGuidanceFlowSpecifications;\n /**\n * Data-seeding overlays exposed to the dev companion.\n *\n * **Optional** in Phase 1 because the engine ships zero seeds yet — the\n * `DataSeedRegistry` and the dispatcher land in Phase 2. Authoring a seed\n * spec without the runtime declaration is allowed (the spec slice is\n * useful as design documentation on its own); authoring a runtime seed\n * without a spec is also allowed (no companion grounding, dispatcher\n * still runs it). Once Phase 2 ships engine seeds this field will be\n * promoted to required, mirroring `systemEmailTemplateSpecifications`.\n *\n * Apps with no app-level seeds should pass an empty\n * `buildDataSeedSpecificationMap()` rather than omitting the field once\n * Phase 2 lands.\n */\n dataSeedSpecifications?: TDataSeedSpecifications;\n /**\n * Application market specification — the English-authored marketing /\n * positioning truth (category, ICPs, personas, jobs/pains/gains, tones\n * of voice, benefits, positionings, message templates). Optional today\n * because not every example app authors a market snapshot yet; once it\n * graduates to required, app bootstraps should run\n * `validateMarketSnapshot` on the value before wiring it here.\n *\n * Authored entirely in English. Geographic targeting (the only\n * \"localization\" the slice models) lives inside\n * `MarketICP.profile.geographies`.\n */\n marketSpecification?: TMarketSnapshot;\n /**\n * Catalog specifications — declarations of EXTERNAL vocabularies the\n * framework reasons about (Schema.org JSON-LD today; future:\n * OpenAPI, RSS, JSON-Feed). Distinct from overlay specs above —\n * overlay specs decorate registry entries (resources, features,\n * views); catalog specs OWN the contract for an external\n * vocabulary's per-entity shape (required / optional / deprecated\n * field declarations).\n *\n * **Composition**: apps spread the engine catalog (e.g.\n * `ENGINE_SCHEMA_ORG_CATALOG`) and append app-side extensions /\n * overrides. The companion's catalog reconciliation runs against\n * this merged surface — emission sites in `@wildo-ai/saas-website`\n * sections (via `getStructuredData()`) are checked against the\n * merged `schemaOrg` catalog, with warnings on missing required\n * fields, deprecated-field usage, and (when wired) missing\n * recommended optionals. Catalog overrides (app entry redefining\n * an engine entry's `@type`) emit a `catalog-override` boot\n * warning.\n *\n * **Optional**: an application that declares no catalog is reconciled\n * against the engine's (`resolveApplicationSchemaOrgCatalog`), which is\n * the one answer the CLI audit and the companion share. Populate the\n * slot only to override engine entries.\n */\n catalogSpecifications?: TCatalogSpecifications;\n /**\n * Assertion surface — the authored layer of the dynamic Assertion\n * Surface (app-creation meta-workflows, master plan S1): statements\n * about the platform served via the companion `assertions-list` /\n * `assertions-resolve` / `assertions-reconcile` behaviors, with\n * status computed by reconcile rather than hand-maintained.\n *\n * **Optional** — the launch posture of every new family: not every\n * example app authors assertions yet, and the family must not break\n * existing companion exports on arrival. Once it graduates to\n * required, app bootstraps should run\n * `validateAssertionSpecificationSnapshot` on the value before\n * wiring it here (the behavior resolver validates on entry either\n * way, market-style).\n *\n * Lane discipline: entries carrying\n * `lane: AssertionLane.FRAMEWORK_DEV` are framework-development\n * knowledge (end-state platform bets authored in the dogfood app\n * during the framework-parallel era) and must NEVER compile into\n * shipped app knowledge — consumers filter on `lane` deliberately.\n */\n assertionSpecifications?: TAssertionSpecifications;\n // ── app-creation meta-workflows C-4 definition families (U1–U4) — FIELDS ──\n // One field per family, in the SAME fixed order as the generic params\n // above. All four are now registered (U1–U4 done); no reservation remains:\n // 1. visionSpecification (U1 — below)\n // 2. requirementsSpecification (U2 — below)\n // 3. roadmapSpecification (U3 — below)\n // 4. businessModelLiteSpecification (U4 — below, LAST)\n /**\n * Application **vision** specification — the foundational-intent truth\n * (idea, problem statement, mission, success criteria, constraints incl.\n * compliance) the app-creation top-down catalog reads/writes (C-4\n * definition families). A single aggregate per app (market-snapshot\n * style), validated by `validateVisionSnapshot`.\n *\n * **Optional** — the launch posture of every new family (market /\n * assertions parity): not every example app authors a vision snapshot\n * yet, and the family must not break existing companion exports on\n * arrival. Once it graduates to required, app bootstraps should run\n * `validateVisionSnapshot` on the value before wiring it here.\n */\n visionSpecification?: TVisionSnapshot;\n /**\n * Application **requirements** specification — the requirements-layer\n * truth (functional requirements + non-functional requirements, each\n * optionally cross-referencing market ICPs / jobs) the app-creation\n * top-down capability-map catalog reads/writes (C-4 definition\n * families). A single aggregate per app (market-snapshot style),\n * validated by `validateRequirementsSnapshot`.\n *\n * **Optional** — the launch posture of every new family (vision /\n * market / assertions parity): not every example app authors a\n * requirements snapshot yet, and the family must not break existing\n * companion exports on arrival. Once it graduates to required, app\n * bootstraps should run `validateRequirementsSnapshot` on the value\n * before wiring it here.\n */\n requirementsSpecification?: TRequirementsSnapshot;\n /**\n * Application **roadmap** specification — the delivery-roadmap truth (a\n * product's delivery plan as an ordered collection of releases/phases,\n * each optionally cross-referencing the requirements /\n * vision-success-criteria it delivers) the app-creation top-down\n * scope/roadmap catalog reads/writes (C-4 definition families). A single\n * aggregate per app (market-snapshot style), validated by\n * `validateRoadmapSnapshot`. Distinct from `milestoneSpecifications` (a\n * dated registry-overlay surface) — a roadmap phase is a planning\n * artifact, not a runtime milestone.\n *\n * **Optional** — the launch posture of every new family (vision /\n * requirements / market / assertions parity): not every example app\n * authors a roadmap snapshot yet, and the family must not break existing\n * companion exports on arrival. Once it graduates to required, app\n * bootstraps should run `validateRoadmapSnapshot` on the value before\n * wiring it here.\n */\n roadmapSpecification?: TRoadmapSnapshot;\n /**\n * Application **build-plan** specification — the ORDERED typed task graph\n * (`BuildPlanTaskGraph`, `_core/build-plan/`) that turns the accepted domain\n * plan into buildable units; produced by the build-decompose playbook and\n * consumed one READY task at a time by build-dispatch. Optional until an\n * application reaches the bottom-up phase; app bootstraps should run\n * `validateBuildPlanTaskGraph` on the value before wiring it here.\n */\n buildPlanSpecification?: TBuildPlanTaskGraph;\n /**\n * Application **placement** specification — WHERE every settings destination,\n * resource operation and app view sits in the shell, and WHY (`PlacementPlan`,\n * `_core/placement-plan/`).\n *\n * Produced by the `bottom_up.placement-plan` playbook as an expert-panel\n * DELIBERATION rather than a creator elicitation: the creator does not choose\n * placement, so each decision carries a `rationale` that answers \"why is this\n * here?\" without re-running the panel. Consumed by build-decompose, which\n * turns it into the coding tasks that author `settings-hub.config.ts` and\n * `app-shell.config.ts`.\n *\n * Optional until an application reaches the bottom-up phase; app bootstraps\n * should run `validatePlacementPlan` on the value before wiring it here.\n */\n placementPlanSpecification?: TPlacementPlan;\n /**\n * Application **domain-plan** specification — the atomic module decomposition\n * PLUS relationship drafts (`DomainPlanOutputSet`, `_core/domain-plan/`);\n * produced by the domain-plan playbook, decomposed by build-decompose.\n * Optional until an application reaches the bottom-up phase.\n */\n domainPlanSpecification?: TDomainPlanOutputSet;\n /**\n * Application **business-model-lite** specification — the lightweight\n * business-model truth (a coarse product-level revenue model + a pricing-\n * plan sketch, each plan optionally cross-referencing the market ICPs it\n * targets and the requirements it includes) the app-creation top-down\n * catalog reads/writes (C-4 definition families). A single aggregate per\n * app (market-snapshot style), validated by\n * `validateBusinessModelLiteSnapshot`. A PLANNING artifact — deliberately\n * NOT the live billing / Stripe product-catalog runtime (it models\n * pricing INTENT, never chargeable state). The `-lite` is the\n * scaffold-depth qualifier of the Phase-J1 increment; the artifact-family\n * id is `business-model`.\n *\n * **Optional** — the launch posture of every new family (vision /\n * requirements / roadmap / market / assertions parity): not every example\n * app authors a business-model snapshot yet, and the family must not break\n * existing companion exports on arrival. Once it graduates to required,\n * app bootstraps should run `validateBusinessModelLiteSnapshot` on the\n * value before wiring it here.\n */\n businessModelLiteSpecification?: TBusinessModelLiteSnapshot;\n /**\n * Application **brand** specification — the visual-identity brief (brand\n * name + logo direction + visual tone; `resolvedAssets` populated by the\n * companion logo step) the app-creation top-down `brand-identity` playbook\n * reads/writes. A single aggregate per app (vision-snapshot style),\n * validated by `validateBrandSnapshot`. Read by the companion\n * `brand-render-prompt` behavior to assemble the logo generation prompt;\n * the artifact-family id is `brand-brief`.\n *\n * **Optional** — the launch posture of every new family: not every example\n * app authors a brand snapshot yet, and the family must not break existing\n * companion exports on arrival.\n */\n brandSpecification?: TBrandSnapshot;\n /**\n * Application **expert-persona charters** — the DERIVED worker-persona\n * instances (`ExpertPersonaCharter[]`) of the framework's\n * `EXPERT_ROLE_TEMPLATES` (art-director, copy-chief, …), committed under\n * `specifications/src/personas/` by the companion's derive→accept flow\n * (and hand-editable thereafter; a human edit is recorded in `authored`).\n *\n * Consumed by the companion's `expert-persona-charters` introspection\n * behavior: the deliberation system builds each expert's agent from the\n * committed charter at startup, and the accept step reads the set for its\n * human-edit overwrite guard + `validateExpertPersonaCharters` run.\n *\n * PLURAL by design (unlike the singleton snapshot families above): an app\n * has one charter per role, several roles. Distinct from the market\n * family's `personas` (BUYER personas — who the app sells to); these are\n * WORKER personas (who does the creative work).\n *\n * **Optional** — the launch posture of every new family: not every example\n * app has derived charters yet, and the family must not break existing\n * companion exports on arrival. Apps with charters should export the\n * generated `appExpertPersonaCharters` aggregate from\n * `specifications/src/personas/`.\n */\n expertPersonaCharters?: TExpertPersonaCharters;\n /**\n * Accepted **feature drafts** produced by the top-down capability-map.\n *\n * Drafts carry product intent only: purpose, business role, lifecycle and\n * availability guidance. They deliberately exclude runtime-definition\n * provenance and executable scope. Phase-gate and domain-planning evidence\n * consume this member; `featureSpecifications` remains the separate\n * runtime-backed overlay surface used after capabilities are implemented.\n *\n * **Optional** at the aggregate contract boundary because applications that\n * have not entered the app-creation workflow may not have accepted drafts.\n * A treatment selecting the `feature-drafts` family fails closed when the\n * member is absent.\n */\n featureDraftsSpecification?: TFeatureSpecificationDrafts;\n /**\n * Accepted application **compliance program** policy.\n *\n * This is the configured application's reusable source/scope/objective,\n * implementation-choice, responsibility, gap/exception and documentation\n * truth. It deliberately excludes live organizations, assignees, reviewer\n * identities, evidence bytes and operating-effectiveness claims.\n *\n * **Optional** at launch. If the application declares the\n * `compliance-program` family, the semantic family authority requires this\n * member and validates it fail closed. Applications without that family must\n * not synthesize this value or receive positive compliance-program claims.\n */\n complianceSpecification?: TComplianceSpecification;\n /**\n * Accepted application **public-document publication variants**.\n *\n * The exact locale × jurisdiction combinations in which this application\n * publishes public governed documents. It is the ONLY source a governed\n * document candidate may take its locale and jurisdictions from.\n *\n * That is a contract statement, not a running check: there is no candidate host binding these\n * bytes to the `document-publication` family's retained head, and nothing today refuses a\n * combination that is not an exact member. Whatever begins producing candidates owes the refusal.\n *\n * Distinct from `complianceSpecification` by design. The assurance program\n * decides which documents are required and who approves them; this slot\n * decides where and in which language they are published. Folding the two\n * would let a document requirement widen its own publication routing.\n *\n * **Optional** at the aggregate contract boundary. An application that\n * declares no `document-publication` family publishes no public governed\n * document. Candidate creation is INTENDED to fail closed there rather than default to a locale\n * or jurisdiction nobody accepted; as above, no code enforces that yet.\n */\n documentPublicationSpecification?: TDocumentPublicationSpecification;\n /**\n * Accepted application selection of the human release lane for each exact\n * governed-document requirement. Optional at the aggregate boundary: an\n * application with no policy can still generate a working draft, but every\n * exposure attempt fails closed rather than assuming operator attestation or\n * qualified review.\n */\n documentReleasePolicySpecification?: TDocumentReleasePolicySpecification;\n /**\n * The governed-document **releases** the application has composed.\n *\n * Optional, and an EMPTY set is the honest answer for an application that has\n * drafted nothing yet. What this slot must never be read as is a list of\n * PUBLISHED documents: every release states its own `approvalState`, and one\n * nobody has approved is `UNAPPROVED` and present here anyway — approval is a\n * workflow act that happens at the end, so an application holds its releases\n * from the moment they are composed.\n *\n * A surface serving a REAL reader obeys `compliance.governedDocumentApprovalGate`; nothing in\n * this slot does that filtering for it.\n */\n documentReleaseSet?: TDocumentReleaseSet;\n /**\n * The governed-document releases the application has **decided** to make — which draft, which\n * declared variant, when it takes effect — as composer inputs (wildo-ai/wildo-ai#968).\n *\n * Decisions, not releases. `wildo config document-releases` composes each decision whose release\n * identity is not yet in `documentReleaseSet` and records the finished release, text included, as\n * committed data. A recorded release is never recomposed, so editing a draft afterwards changes no\n * release; publishing new text is a new decision with the next `releaseVersion`.\n *\n * Optional: an application that composes no releases declares none, and one that already records\n * its releases some other way loses nothing.\n */\n documentReleaseCompositions?: TDocumentReleaseCompositions;\n /**\n * Accepted application **governed-document facts**.\n *\n * This optional slot carries the `document-facts` family: declarations answered from the accepted\n * specification, under `APPLICATION_SPECIFICATION` authority only. `refinement.document-facts`\n * produces it and a commit accepts it; creator decisions and qualified reviews live in the authored\n * slot below. Nothing is sealed or digested — validation re-reads the file.\n *\n * Candidates and releases belong to their own families and are not carried here.\n * Omitting it is honest: unresolved document facts remain visible gaps.\n */\n documentFactSpecification?: TDocumentFactSpecification;\n /**\n * Accepted application governed-document facts **only a human may establish** — a creator decision\n * or a qualified review (`document-facts-authored`).\n *\n * The same shape as the slot above, and a separate family on purpose. `refinement.document-facts`\n * rewrites the derived file whole, so a human decision sharing that file is destroyed on the next\n * run with nothing to notice: there is no compare-and-swap here, deliberately — nothing is kept\n * that cannot branch and merge on git. Two families put the two writers out of each\n * other's reach.\n *\n * No producer may write this family — it has no generation contract, and that absence is the design\n * rather than an omission.\n *\n * A reader wanting \"the application's facts\" needs BOTH slots. `collectComplianceDocumentFactAvailability`\n * is variadic for exactly that reason.\n */\n authoredDocumentFactSpecification?: TAuthoredDocumentFactSpecification;\n /**\n * WHO else processes this application's personal data — legal identity, processing region and the\n * processor's own subprocessors (issue #88).\n *\n * A configured provider already establishes THAT a third party is involved and what function it\n * performs. None of that is what a privacy notice's recipient statement needs, and an\n * international-transfer statement cannot be made at all without a region.\n *\n * Optional, and its holes are reported rather than blocking: the companion compares this register\n * against the application's CONFIGURED providers and names each one that is undeclared, so a partial\n * register is useful and an empty one still produces an actionable document. An absent entry means\n * nobody has established that processor's identity — never that the provider is unused.\n */\n processorRegister?: TProcessorRegister;\n /**\n * WHICH RISKS this application carries, and under what posture — the accepted risk register (#300).\n *\n * ## Why a family that \"the runtime does not consume\" still needs a slot\n *\n * This slot was almost omitted on the reasoning that the application RUNTIME never reads the\n * register: it is accepted by a human and read by assurance tooling over the committed file, which\n * is exactly the case `ApplicationSpecificationSemanticSchemaBinding.companionExportsField`\n * describes as \"lands as a file to review, and is deliberately not wired\".\n *\n * That reasoning is about the runtime and the question is about the COMPANION.\n * `family-aspects.behavior.ts` reads a landed family through this aggregate and nowhere else — a\n * binding with no slot yields an undefined snapshot, so every aspect of that family projects an\n * empty item list. The register's rows would have been addressable, navigable, labelled, and\n * permanently absent: a resource that cannot ever hold a row.\n *\n * Optional, like every family slot: an application that has not accepted a register simply has\n * none, and the aspect resource is empty because there is nothing rather than because nothing can\n * reach it.\n */\n riskRegister?: TRiskRegister;\n /**\n * WHAT THE CREATOR SAID — every interview answer, by playbook and question ref (#1454, Step 5).\n *\n * The slot is what makes the dossier READABLE by the companion, exactly as the risk register's\n * note above explains: a playbook run resolves its interview answers through this aggregate and\n * nowhere else, so a landed dossier with no slot would be a file nobody reads. Optional, because\n * an application that has answered nothing simply has no dossier yet.\n */\n creatorInputs?: TCreatorInputs;\n /**\n * WHICH COMPOSITION SCENARIOS the application needs — website, documentation portal, workers,\n * minions, locales — one decision per scenario the framework ships, each naming the declaration\n * it was derived from (#1491). The foundation executor reads it through this slot and applies\n * the NEEDED ones; a landed composition with no slot would be a file nobody reads, exactly as\n * the risk register's note above explains.\n */\n capabilityComposition?: TCapabilityComposition;\n /**\n * WHAT THE MARKETING WEBSITE SAYS — its pages, their sections in reading order, and the market\n * entries each draws on (#1492). Read by `bottom_up.build-decompose`, which turns each page and\n * each section into a build task bound to the skill that authors it. Optional: an application\n * whose capability composition declined a website lands a NOT_APPLICABLE plan, and one that has\n * not reached the website step has none at all.\n */\n websitePlan?: TWebsitePlan;\n /**\n * WHAT THE APPLICATION'S EXPERIENCE IS — the views it carries beyond its resources' generated\n * screens, the shell and navigation composition, and the preset components each view reuses\n * (#1493). Read by `bottom_up.build-decompose`, which turns each entry into a build task bound to\n * the skill its kind names. Optional: an application that has not reached the experience step has\n * none, and its build plan simply carries no view or configuration task.\n */\n experiencePlan?: TExperiencePlan;\n /**\n * WHICH CHAPTERS the documentation portal carries, what each documents and who it is for (#1494).\n * Read by `bottom_up.build-decompose`, which turns each chapter into a task, and by the documentation\n * publication, which takes each chapter's identity from here and its body from\n * `documentationChapters` below (#874).\n */\n documentationPlan?: TApplicationDocumentationPlan;\n /**\n * THE AUTHORED BODY of each chapter `documentationPlan` declares, keyed by `chapterRef` (#874) —\n * from `specifications/src/technical-documentation/index.ts`, accepted by being committed.\n *\n * Read by the documentation publication, which joins each body to its planned chapter and publishes\n * it as a guide: a chapter the plan does not declare, and a `RESTRICTED` or unapproved one, is\n * withheld and reported, and an API reference that does not resolve against the rendered reference\n * fails the publication. Optional, and absent is honest: the portal then carries only its derived pages.\n *\n * Typed directly rather than through a positional generic: no application narrows it, and a new\n * positional parameter would only add a slot for every consumer to skip.\n */\n documentationChapters?: ApplicationDocumentationChapterSet;\n /**\n * WHAT RUNS BESIDE THE BACKEND — the application's workers and minions, what each is for, what a\n * minion's tick may touch, and the providers this application binds (#1495). Read by\n * `bottom_up.build-decompose`, which turns each into a build task bound to `worker-authoring`,\n * `minion-authoring` or the provider skills.\n */\n integrationPlan?: TIntegrationPlan;\n /**\n * WHERE THIS APPLICATION STANDS against what it asked of itself (#1496) — one row per requirement\n * with the evidence that exists for it, and the stage that follows. A READING: derived from the\n * requirements, the decided-element graph and the build plan's landing probe, never generated and\n * never a gate. Read by the coherence report and the workbench.\n */\n applicationMaturity?: TApplicationMaturity;\n /**\n * WHICH NAMES were proposed for the brand and what a minimal trademark screening of each found —\n * registers, classes and jurisdictions searched, per-register results with sources and dates, and the\n * competitor collisions beside them. Produced by `top_down.brand-naming`; the brand-identity interview's\n * `brand-name` CHOICE is computed from it, and the coherence report reads it to say where the chosen\n * brand name stands. A screening, never a legal clearance opinion.\n */\n brandNameScreening?: TBrandNameScreening;\n /**\n * Accepted application-declared semantic causality between whole\n * specification-family states. This is not the registry's physical\n * dependency graph and not Actor/Flow execution order. The runtime resolves\n * these declarations only through the exact CURRENT accepted projection,\n * then may derive a rebuildable impact index; this export itself does not\n * authorize a journal write, review queue or application mutation.\n *\n * Optional because semantic impact is an advanced application-creation\n * capability. An application that declares the dedicated\n * `semantic-dependencies` family must provide this field; a resolver refuses\n * a missing or malformed value rather than infer dependencies from imports\n * or registry edges.\n */\n}\n\n/**\n * Aggregate of every catalog vocabulary an app can wire on the\n * `catalogSpecifications` companion-exports slot.\n *\n * Each vocabulary is a flat array of validated entries (engine\n * + app entries merged at wiring time). The companion harness keys\n * each vocabulary by its discriminator (`@type` for Schema.org;\n * future vocabularies can use `operationId`, `kind`, etc.); app\n * entries silently override engine entries on collision and the\n * harness emits a `catalog-override` warning for each override at\n * boot.\n *\n * **Why an aggregate type and not per-slot fields**: every future\n * vocabulary lands as a sibling field on this single type rather\n * than as a new top-level companion-exports field. This keeps the\n * `SpecificationsCompanionExports` shape stable as the catalog\n * surface grows.\n */\nexport interface CatalogSpecifications {\n /**\n * Schema.org JSON-LD vocabulary catalog. Compose with\n * `ENGINE_SCHEMA_ORG_CATALOG` (engine-shipped standard entries)\n * spread, then append app-side extensions / overrides.\n */\n schemaOrg?: readonly SchemaOrgCatalogEntryBase[];\n}\n/** @wildo_source:part:end saas.specifications.companion-exports.contract */\n"]}
@@ -91,6 +91,7 @@ export declare const jobExecutionsResourceSpecification: import("../../../_core"
91
91
  attemptCount: import("zod").ZodNumber;
92
92
  reconciledSafe: import("zod").ZodDefault<import("zod").ZodBoolean>;
93
93
  reason: import("zod").ZodOptional<import("zod").ZodString>;
94
+ lateness: import("zod").ZodOptional<import("zod").ZodEnum<typeof import("@wildo-ai/saas-models").ScheduledDeliveryLateness>>;
94
95
  attempts: import("zod").ZodArray<import("zod").ZodObject<{
95
96
  attemptId: import("zod").ZodUUID;
96
97
  phase: import("zod").ZodEnum<typeof import("@wildo-ai/saas-models").ScheduledExecutionPhase>;
@@ -1 +1 @@
1
- {"version":3,"file":"job-executions.resource.specification.d.ts","sourceRoot":"","sources":["../../../../../../src/engine/infrastructure/resources/job-executions.resource.specification.ts"],"names":[],"mappings":"AAMA,OAAO,EACL,qBAAqB,IAAI,EAAE,EAE3B,kBAAkB,EAIlB,OAAO,EAGR,MAAM,uBAAuB,CAAC;AAI/B;;;;;;GAMG;AACH,eAAO,MAAM,kCAAkC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;iCAyR9C,CAAC"}
1
+ {"version":3,"file":"job-executions.resource.specification.d.ts","sourceRoot":"","sources":["../../../../../../src/engine/infrastructure/resources/job-executions.resource.specification.ts"],"names":[],"mappings":"AAMA,OAAO,EACL,qBAAqB,IAAI,EAAE,EAE3B,kBAAkB,EAIlB,OAAO,EAGR,MAAM,uBAAuB,CAAC;AAI/B;;;;;;GAMG;AACH,eAAO,MAAM,kCAAkC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;iCAyR9C,CAAC"}
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@wildo-ai/saas-specifications",
3
- "version": "1.1.8",
3
+ "version": "1.1.9",
4
4
  "license": "SEE LICENSE IN LICENSE",
5
5
  "description": "Product specification layer for Wildo SaaS applications — business semantics, capabilities vocabulary, and application-level specification contracts.",
6
6
  "type": "module",
@@ -47,13 +47,13 @@
47
47
  "test:watch": "vitest"
48
48
  },
49
49
  "dependencies": {
50
- "@wildo-ai/zod-decorators": "1.1.8",
51
- "@wildo-ai/saas-models": "1.1.8",
52
- "@wildo-ai/saas-frontend-lib": "1.1.8",
53
- "@wildo-ai/saas-backend-lib": "1.1.8",
54
- "@wildo-ai/presets-components-models": "1.1.8",
55
- "@wildo-ai/presets-components": "1.1.8",
56
- "@wildo-ai/external-connectors-models": "1.1.8"
50
+ "@wildo-ai/zod-decorators": "1.1.9",
51
+ "@wildo-ai/saas-models": "1.1.9",
52
+ "@wildo-ai/saas-frontend-lib": "1.1.9",
53
+ "@wildo-ai/saas-backend-lib": "1.1.9",
54
+ "@wildo-ai/presets-components-models": "1.1.9",
55
+ "@wildo-ai/presets-components": "1.1.9",
56
+ "@wildo-ai/external-connectors-models": "1.1.9"
57
57
  },
58
58
  "peerDependencies": {
59
59
  "zod": "^4.3.6"
@@ -1,24 +0,0 @@
1
- /**
2
- * The instant every assurance-authority fixture evaluates the basis AT.
3
- *
4
- * It must not precede anything the basis carries — the objective catalog's `verifiedAt` and every
5
- * source-requirement `reviewedAt` are refused when they are later than the evaluation instant, which
6
- * is the schema working: an authority cannot have been reviewed in the future of the evaluation
7
- * reading it.
8
- *
9
- * ## Why it lives in its own module
10
- *
11
- * It was a `const` in each of three test files, and the comment on one of them already recorded what
12
- * that costs: when the basis gained the 2026-09-01 mapping tranche, *"three separately-spelled
13
- * `2026-08-14` fixtures each failed with 'cannot be later than evaluatedAt', which reads as the BASIS
14
- * being wrong rather than the fixture being old"*. The remedy it drew from that — one constant rather
15
- * than a literal per call site — was applied WITHIN each file and not across them, so the 2026-09-17
16
- * authenticator-strength tranche reproduced the identical three-file failure verbatim (#1247). A
17
- * constant copied into every file that needs it is not one constant.
18
- *
19
- * **Advance this when you add a tranche whose review instant is later**, and nothing else. A test
20
- * failing on it is telling you the fixture is old, which is the message the three copies could not
21
- * deliver.
22
- */
23
- export declare const AUTHORITY_EVALUATED_AT = "2026-09-25T12:00:00.000Z";
24
- //# sourceMappingURL=authority-evaluation-instant.fixture.d.ts.map
@@ -1 +0,0 @@
1
- {"version":3,"file":"authority-evaluation-instant.fixture.d.ts","sourceRoot":"","sources":["../../../../../src/assurance/__tests__/authority-evaluation-instant.fixture.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,eAAO,MAAM,sBAAsB,6BAA6B,CAAC"}
@@ -1,24 +0,0 @@
1
- /**
2
- * The instant every assurance-authority fixture evaluates the basis AT.
3
- *
4
- * It must not precede anything the basis carries — the objective catalog's `verifiedAt` and every
5
- * source-requirement `reviewedAt` are refused when they are later than the evaluation instant, which
6
- * is the schema working: an authority cannot have been reviewed in the future of the evaluation
7
- * reading it.
8
- *
9
- * ## Why it lives in its own module
10
- *
11
- * It was a `const` in each of three test files, and the comment on one of them already recorded what
12
- * that costs: when the basis gained the 2026-09-01 mapping tranche, *"three separately-spelled
13
- * `2026-08-14` fixtures each failed with 'cannot be later than evaluatedAt', which reads as the BASIS
14
- * being wrong rather than the fixture being old"*. The remedy it drew from that — one constant rather
15
- * than a literal per call site — was applied WITHIN each file and not across them, so the 2026-09-17
16
- * authenticator-strength tranche reproduced the identical three-file failure verbatim (#1247). A
17
- * constant copied into every file that needs it is not one constant.
18
- *
19
- * **Advance this when you add a tranche whose review instant is later**, and nothing else. A test
20
- * failing on it is telling you the fixture is old, which is the message the three copies could not
21
- * deliver.
22
- */
23
- export const AUTHORITY_EVALUATED_AT = "2026-09-25T12:00:00.000Z";
24
- //# sourceMappingURL=authority-evaluation-instant.fixture.js.map
@@ -1 +0,0 @@
1
- {"version":3,"file":"authority-evaluation-instant.fixture.js","sourceRoot":"","sources":["../../../../../src/assurance/__tests__/authority-evaluation-instant.fixture.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,CAAC,MAAM,sBAAsB,GAAG,0BAA0B,CAAC","sourcesContent":["/**\n * The instant every assurance-authority fixture evaluates the basis AT.\n *\n * It must not precede anything the basis carries — the objective catalog's `verifiedAt` and every\n * source-requirement `reviewedAt` are refused when they are later than the evaluation instant, which\n * is the schema working: an authority cannot have been reviewed in the future of the evaluation\n * reading it.\n *\n * ## Why it lives in its own module\n *\n * It was a `const` in each of three test files, and the comment on one of them already recorded what\n * that costs: when the basis gained the 2026-09-01 mapping tranche, *\"three separately-spelled\n * `2026-08-14` fixtures each failed with 'cannot be later than evaluatedAt', which reads as the BASIS\n * being wrong rather than the fixture being old\"*. The remedy it drew from that — one constant rather\n * than a literal per call site — was applied WITHIN each file and not across them, so the 2026-09-17\n * authenticator-strength tranche reproduced the identical three-file failure verbatim (#1247). A\n * constant copied into every file that needs it is not one constant.\n *\n * **Advance this when you add a tranche whose review instant is later**, and nothing else. A test\n * failing on it is telling you the fixture is old, which is the message the three copies could not\n * deliver.\n */\nexport const AUTHORITY_EVALUATED_AT = \"2026-09-25T12:00:00.000Z\";\n"]}