@wildo-ai/saas-specifications 1.1.7 → 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.
- package/dist/esm/_core/application-specification-family-identity.schemas.d.ts +9 -0
- package/dist/esm/_core/application-specification-family-identity.schemas.d.ts.map +1 -1
- package/dist/esm/_core/application-specification-family-identity.schemas.js +9 -0
- package/dist/esm/_core/application-specification-family-identity.schemas.js.map +1 -1
- package/dist/esm/_core/brand/brand-name-choice.d.ts +136 -0
- package/dist/esm/_core/brand/brand-name-choice.d.ts.map +1 -0
- package/dist/esm/_core/brand/brand-name-choice.js +193 -0
- package/dist/esm/_core/brand/brand-name-choice.js.map +1 -0
- package/dist/esm/_core/brand/brand-name-screening-generation.schemas.d.ts +108 -0
- package/dist/esm/_core/brand/brand-name-screening-generation.schemas.d.ts.map +1 -0
- package/dist/esm/_core/brand/brand-name-screening-generation.schemas.js +59 -0
- package/dist/esm/_core/brand/brand-name-screening-generation.schemas.js.map +1 -0
- package/dist/esm/_core/brand/brand-name-screening-validation.d.ts +51 -0
- package/dist/esm/_core/brand/brand-name-screening-validation.d.ts.map +1 -0
- package/dist/esm/_core/brand/brand-name-screening-validation.js +157 -0
- package/dist/esm/_core/brand/brand-name-screening-validation.js.map +1 -0
- package/dist/esm/_core/brand/brand-name-screening-view.d.ts +120 -0
- package/dist/esm/_core/brand/brand-name-screening-view.d.ts.map +1 -0
- package/dist/esm/_core/brand/brand-name-screening-view.js +47 -0
- package/dist/esm/_core/brand/brand-name-screening-view.js.map +1 -0
- package/dist/esm/_core/brand/brand-name-screening.family-aspects.d.ts +3 -0
- package/dist/esm/_core/brand/brand-name-screening.family-aspects.d.ts.map +1 -0
- package/dist/esm/_core/brand/brand-name-screening.family-aspects.js +42 -0
- package/dist/esm/_core/brand/brand-name-screening.family-aspects.js.map +1 -0
- package/dist/esm/_core/brand/brand-name-screening.schemas.d.ts +310 -0
- package/dist/esm/_core/brand/brand-name-screening.schemas.d.ts.map +1 -0
- package/dist/esm/_core/brand/brand-name-screening.schemas.js +272 -0
- package/dist/esm/_core/brand/brand-name-screening.schemas.js.map +1 -0
- package/dist/esm/_core/brand/brand-snapshot.schemas.d.ts +23 -0
- package/dist/esm/_core/brand/brand-snapshot.schemas.d.ts.map +1 -1
- package/dist/esm/_core/brand/brand-snapshot.schemas.js +32 -0
- package/dist/esm/_core/brand/brand-snapshot.schemas.js.map +1 -1
- package/dist/esm/_core/build-plan/build-plan-task-graph-generation.schemas.d.ts +10 -0
- package/dist/esm/_core/build-plan/build-plan-task-graph-generation.schemas.d.ts.map +1 -1
- package/dist/esm/_core/build-plan/build-plan-task-graph-validation.d.ts +57 -0
- package/dist/esm/_core/build-plan/build-plan-task-graph-validation.d.ts.map +1 -1
- package/dist/esm/_core/build-plan/build-plan-task-graph-validation.js +89 -0
- package/dist/esm/_core/build-plan/build-plan-task-graph-validation.js.map +1 -1
- package/dist/esm/_core/build-plan/build-plan-task-graph.schemas.d.ts +79 -19
- package/dist/esm/_core/build-plan/build-plan-task-graph.schemas.d.ts.map +1 -1
- package/dist/esm/_core/build-plan/build-plan-task-graph.schemas.js +61 -11
- package/dist/esm/_core/build-plan/build-plan-task-graph.schemas.js.map +1 -1
- package/dist/esm/_core/build-plan/build-plan.family-aspects.d.ts.map +1 -1
- package/dist/esm/_core/build-plan/build-plan.family-aspects.js +18 -2
- package/dist/esm/_core/build-plan/build-plan.family-aspects.js.map +1 -1
- package/dist/esm/_core/business-model-lite/business-model-lite-snapshot-generation.schemas.d.ts +28 -4
- package/dist/esm/_core/business-model-lite/business-model-lite-snapshot-generation.schemas.d.ts.map +1 -1
- package/dist/esm/_core/business-model-lite/business-model-lite-snapshot-generation.schemas.js +53 -5
- package/dist/esm/_core/business-model-lite/business-model-lite-snapshot-generation.schemas.js.map +1 -1
- package/dist/esm/_core/business-model-lite/business-model-lite-snapshot-validation.d.ts +24 -4
- package/dist/esm/_core/business-model-lite/business-model-lite-snapshot-validation.d.ts.map +1 -1
- package/dist/esm/_core/business-model-lite/business-model-lite-snapshot-validation.js +64 -4
- package/dist/esm/_core/business-model-lite/business-model-lite-snapshot-validation.js.map +1 -1
- package/dist/esm/_core/business-model-lite/business-model-lite-snapshot.schemas.d.ts +59 -0
- package/dist/esm/_core/business-model-lite/business-model-lite-snapshot.schemas.d.ts.map +1 -1
- package/dist/esm/_core/business-model-lite/business-model-lite-snapshot.schemas.js +64 -0
- package/dist/esm/_core/business-model-lite/business-model-lite-snapshot.schemas.js.map +1 -1
- package/dist/esm/_core/business-model-lite/pricing-plan.schemas.d.ts +3 -0
- package/dist/esm/_core/business-model-lite/pricing-plan.schemas.d.ts.map +1 -1
- package/dist/esm/_core/business-model-lite/pricing-plan.schemas.js +16 -0
- package/dist/esm/_core/business-model-lite/pricing-plan.schemas.js.map +1 -1
- package/dist/esm/_core/capability-composition/capability-composition-validation.d.ts +7 -1
- package/dist/esm/_core/capability-composition/capability-composition-validation.d.ts.map +1 -1
- package/dist/esm/_core/capability-composition/capability-composition-validation.js +34 -28
- package/dist/esm/_core/capability-composition/capability-composition-validation.js.map +1 -1
- package/dist/esm/_core/capability-composition/capability-composition.schemas.d.ts +75 -4
- package/dist/esm/_core/capability-composition/capability-composition.schemas.d.ts.map +1 -1
- package/dist/esm/_core/capability-composition/capability-composition.schemas.js +62 -4
- package/dist/esm/_core/capability-composition/capability-composition.schemas.js.map +1 -1
- package/dist/esm/_core/compliance-documents/computed-document-facts.schemas.d.ts.map +1 -1
- package/dist/esm/_core/compliance-documents/computed-document-facts.schemas.js +7 -0
- package/dist/esm/_core/compliance-documents/computed-document-facts.schemas.js.map +1 -1
- package/dist/esm/_core/compliance-documents/launch-blockers.schemas.d.ts +153 -0
- package/dist/esm/_core/compliance-documents/launch-blockers.schemas.d.ts.map +1 -0
- package/dist/esm/_core/compliance-documents/launch-blockers.schemas.js +241 -0
- package/dist/esm/_core/compliance-documents/launch-blockers.schemas.js.map +1 -0
- package/dist/esm/_core/domain-plan/domain-plan-output-set-validation.d.ts +8 -1
- package/dist/esm/_core/domain-plan/domain-plan-output-set-validation.d.ts.map +1 -1
- package/dist/esm/_core/domain-plan/domain-plan-output-set-validation.js +19 -1
- package/dist/esm/_core/domain-plan/domain-plan-output-set-validation.js.map +1 -1
- package/dist/esm/_core/domain-plan/domain-plan-output-set.schemas.d.ts +61 -3
- package/dist/esm/_core/domain-plan/domain-plan-output-set.schemas.d.ts.map +1 -1
- package/dist/esm/_core/domain-plan/domain-plan-output-set.schemas.js +73 -3
- package/dist/esm/_core/domain-plan/domain-plan-output-set.schemas.js.map +1 -1
- package/dist/esm/_core/experience-plan/experience-plan.family-aspects.js +1 -1
- package/dist/esm/_core/experience-plan/experience-plan.family-aspects.js.map +1 -1
- package/dist/esm/_core/experience-plan/experience-plan.schemas.d.ts.map +1 -1
- package/dist/esm/_core/experience-plan/experience-plan.schemas.js +1 -0
- package/dist/esm/_core/experience-plan/experience-plan.schemas.js.map +1 -1
- package/dist/esm/_core/family-aspects.registry.d.ts.map +1 -1
- package/dist/esm/_core/family-aspects.registry.js +2 -0
- package/dist/esm/_core/family-aspects.registry.js.map +1 -1
- package/dist/esm/_core/index.d.ts +6 -0
- package/dist/esm/_core/index.d.ts.map +1 -1
- package/dist/esm/_core/index.js +6 -0
- package/dist/esm/_core/index.js.map +1 -1
- package/dist/esm/_core/integration-plan/integration-plan.family-aspects.d.ts.map +1 -1
- package/dist/esm/_core/integration-plan/integration-plan.family-aspects.js +5 -1
- package/dist/esm/_core/integration-plan/integration-plan.family-aspects.js.map +1 -1
- package/dist/esm/_core/market/market-icp.schemas.d.ts +7 -0
- package/dist/esm/_core/market/market-icp.schemas.d.ts.map +1 -1
- package/dist/esm/_core/market/market-icp.schemas.js +7 -0
- package/dist/esm/_core/market/market-icp.schemas.js.map +1 -1
- package/dist/esm/_core/market/market-language-coverage.d.ts +62 -0
- package/dist/esm/_core/market/market-language-coverage.d.ts.map +1 -0
- package/dist/esm/_core/market/market-language-coverage.js +48 -0
- package/dist/esm/_core/market/market-language-coverage.js.map +1 -0
- package/dist/esm/_core/market/market-snapshot-validation.js +2 -2
- package/dist/esm/_core/market/market-snapshot-validation.js.map +1 -1
- package/dist/esm/application-creation/application-creator-inputs.application-creation.schemas.d.ts +63 -2
- package/dist/esm/application-creation/application-creator-inputs.application-creation.schemas.d.ts.map +1 -1
- package/dist/esm/application-creation/application-creator-inputs.application-creation.schemas.js +73 -5
- package/dist/esm/application-creation/application-creator-inputs.application-creation.schemas.js.map +1 -1
- package/dist/esm/application-creation/application-line.application-creation.schemas.d.ts.map +1 -1
- package/dist/esm/application-creation/application-line.application-creation.schemas.js +2 -0
- package/dist/esm/application-creation/application-line.application-creation.schemas.js.map +1 -1
- package/dist/esm/application-creation/playbooks.application-creation.schemas.d.ts +28 -0
- package/dist/esm/application-creation/playbooks.application-creation.schemas.d.ts.map +1 -1
- package/dist/esm/application-creation/playbooks.application-creation.schemas.js +19 -1
- package/dist/esm/application-creation/playbooks.application-creation.schemas.js.map +1 -1
- package/dist/esm/application-creation/structured-artifact-landing.application-creation.schemas.d.ts +1 -0
- package/dist/esm/application-creation/structured-artifact-landing.application-creation.schemas.d.ts.map +1 -1
- package/dist/esm/application-creation/structured-artifact-landing.application-creation.schemas.js +1 -0
- package/dist/esm/application-creation/structured-artifact-landing.application-creation.schemas.js.map +1 -1
- package/dist/esm/application-creation.exports.d.ts +7 -0
- package/dist/esm/application-creation.exports.d.ts.map +1 -1
- package/dist/esm/application-creation.exports.js +7 -0
- package/dist/esm/application-creation.exports.js.map +1 -1
- package/dist/esm/assurance/application-risk-signals.derivations.d.ts +20 -0
- package/dist/esm/assurance/application-risk-signals.derivations.d.ts.map +1 -1
- package/dist/esm/assurance/application-risk-signals.derivations.js +81 -0
- package/dist/esm/assurance/application-risk-signals.derivations.js.map +1 -1
- package/dist/esm/assurance/governed-document-release.d.ts +9 -0
- package/dist/esm/assurance/governed-document-release.d.ts.map +1 -1
- package/dist/esm/assurance/governed-document-release.js +9 -0
- package/dist/esm/assurance/governed-document-release.js.map +1 -1
- package/dist/esm/companion-exports.d.ts +10 -1
- package/dist/esm/companion-exports.d.ts.map +1 -1
- package/dist/esm/companion-exports.js.map +1 -1
- package/dist/esm/engine/infrastructure/resources/job-executions.resource.specification.d.ts +1 -0
- package/dist/esm/engine/infrastructure/resources/job-executions.resource.specification.d.ts.map +1 -1
- package/package.json +8 -8
- package/dist/esm/assurance/__tests__/authority-evaluation-instant.fixture.d.ts +0 -24
- package/dist/esm/assurance/__tests__/authority-evaluation-instant.fixture.d.ts.map +0 -1
- package/dist/esm/assurance/__tests__/authority-evaluation-instant.fixture.js +0 -24
- package/dist/esm/assurance/__tests__/authority-evaluation-instant.fixture.js.map +0 -1
- package/dist/tsconfig.build.tsbuildinfo +0 -1
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbooks.application-creation.schemas.js","sourceRoot":"","sources":["../../../../src/application-creation/playbooks.application-creation.schemas.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAKxB,OAAO,EACL,2BAA2B,EAC3B,mCAAmC,EACnC,mCAAmC,EACnC,+BAA+B,EAC/B,kCAAkC,EAClC,qBAAqB,EACrB,0BAA0B,EAC1B,mCAAmC,EACnC,iCAAiC,EACjC,uCAAuC,EACvC,0BAA0B,EAC1B,qCAAqC,GACtC,MAAM,sCAAsC,CAAC;AAE9C,OAAO,EAAE,yCAAyC,EAAE,MAAM,2EAA2E,CAAC;AAEtI,iEAAiE;AACjE,2BAA2B;AAC3B,4BAA4B;AAC5B,sEAAsE;AACtE,4EAA4E;AAC5E,qEAAqE;AACrE,2EAA2E;AAC3E,0DAA0D;AAC1D,8DAA8D;AAC9D,2EAA2E;AAC3E,eAAe;AACf,sEAAsE;AACtE,EAAE;AACF,mEAAmE;AACnE,kEAAkE;AAClE,2FAA2F;AAC3F,+FAA+F;AAC/F,sFAAsF;AACtF,EAAE;AACF,iGAAiG;AACjG,kGAAkG;AAClG,iGAAiG;AACjG,0DAA0D;AAC1D,EAAE;AACF,8EAA8E;AAC9E,qEAAqE;AACrE,uEAAuE;AACvE,4EAA4E;AAC5E,0EAA0E;AAC1E,8EAA8E;AAC9E,2EAA2E;AAC3E,yEAAyE;AACzE,0EAA0E;AAC1E,+EAA+E;AAC/E,EAAE;AACF,8EAA8E;AAC9E,8EAA8E;AAC9E,+EAA+E;AAC/E,yEAAyE;AACzE,yEAAyE;AACzE,iEAAiE;AACjE,EAAE;AACF,yEAAyE;AACzE,yEAAyE;AACzE,qEAAqE;AACrE,mEAAmE;AACnE,wBAAwB;AACxB,iEAAiE;AAGjE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqCG;AACH,MAAM,CAAN,IAAY,kBASX;AATD,WAAY,kBAAkB;IAC5B,0GAA0G;IAC1G,2CAAqB,CAAA;IACrB,2FAA2F;IAC3F,6CAAuB,CAAA;IACvB,oFAAoF;IACpF,+CAAyB,CAAA;IACzB,gDAAgD;IAChD,qDAA+B,CAAA;AACjC,CAAC,EATW,kBAAkB,KAAlB,kBAAkB,QAS7B;AAGD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAoCG;AACH,MAAM,CAAN,IAAY,4BAQX;AARD,WAAY,4BAA4B;IACtC,qGAAqE,CAAA;IACrE,yEAAyC,CAAA;IACzC,6FAA6D,CAAA;IAC7D,+EAA+C,CAAA;IAC/C,yEAAyC,CAAA;IACzC,uHAAuF,CAAA;IACvF,2FAA2D,CAAA;AAC7D,CAAC,EARW,4BAA4B,KAA5B,4BAA4B,QAQvC;AAED;;;;;;;;;;;;;;;;;GAiBG;AAEH;;;;;;;GAOG;AACH,MAAM,CAAN,IAAY,+BAGX;AAHD,WAAY,+BAA+B;IACzC,8CAAW,CAAA;IACX,4CAAS,CAAA;AACX,CAAC,EAHW,+BAA+B,KAA/B,+BAA+B,QAG1C;AAED;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,MAAM,UAAU,yBAAyB,CAAC,SAAiB;IACzD,kGAAkG;IAClG,MAAM,UAAU,GAAG,SAAS,CAAC,IAAI,EAAE,CAAC,WAAW,EAAE,CAAC,OAAO,CAAC,SAAS,EAAE,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC;IAChF,IAAI,qCAAqC,CAAC,GAAG,CAAC,UAAU,CAAC;QAAE,OAAO,+BAA+B,CAAC,GAAG,CAAC;IACtG,IAAI,kCAAkC,CAAC,GAAG,CAAC,UAAU,CAAC;QAAE,OAAO,+BAA+B,CAAC,EAAE,CAAC;IAClG,OAAO,IAAI,CAAC;AACd,CAAC;AAED,yHAAyH;AACzH,MAAM,qCAAqC,GAAwB,IAAI,GAAG,CAAC,CAAC,KAAK,EAAE,GAAG,EAAE,MAAM,CAAC,CAAC,CAAC;AACjG,gCAAgC;AAChC,MAAM,kCAAkC,GAAwB,IAAI,GAAG,CAAC,CAAC,IAAI,EAAE,GAAG,EAAE,OAAO,CAAC,CAAC,CAAC;AAE9F,yGAAyG;AACzG,MAAM,CAAC,MAAM,kCAAkC,GAAsB,MAAM,CAAC,MAAM,CAAC;IACjF,GAAG,qCAAqC;IACxC,GAAG,kCAAkC;CACtC,CAAC,CAAC;AAEH;;;;GAIG;AACH;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,CAAN,IAAY,0BAgNX;AAhND,WAAY,0BAA0B;IACpC;;;;;OAKG;IACH,iEAAmC,CAAA;IACnC;;;;;;;;;OASG;IACH,6DAA+B,CAAA;IAC/B;;;;;;;;OAQG;IACH,mEAAqC,CAAA;IACrC;;;;;;;;;;;;;;;;;;;OAmBG;IACH,mFAAqD,CAAA;IACrD;;;;;;;;;;;;;;;;;OAiBG;IACH,uEAAyC,CAAA;IACzC;;;;;;;;;;;;;;;;;OAiBG;IACH,qFAAuD,CAAA;IACvD;;;;;;;OAOG;IACH,yFAA2D,CAAA;IAC3D;;;;;;;;;;;;;;;;;;OAkBG;IACH,+EAAiD,CAAA;IACjD;;;;;;;;;;;;;;;;;;;;OAoBG;IACH,uEAAyC,CAAA;IACzC;;;;;;;;;;;;;;;;;;;;;;OAsBG;IACH,iFAAmD,CAAA;IACnD;;;;;;;;;;;;;;;;;;;;;;OAsBG;IACH,qEAAuC,CAAA;IACvC;;;;;;;;;;;;;;;;;;;OAmBG;IACH,2DAA6B,CAAA;AAC/B,CAAC,EAhNW,0BAA0B,KAA1B,0BAA0B,QAgNrC;AAED;;;;GAIG;AACH,MAAM,CAAN,IAAY,wBAQX;AARD,WAAY,wBAAwB;IAClC,2GAA2G;IAC3G,yCAAa,CAAA;IACb;;;OAGG;IACH,uCAAW,CAAA;AACb,CAAC,EARW,wBAAwB,KAAxB,wBAAwB,QAQnC;AAED;;;;GAIG;AACH,MAAM,CAAC,MAAM,qCAAqC,GAAG,CAAC,CAAC;AAEvD,+EAA+E;AAC/E,MAAM,CAAC,MAAM,+BAA+B,GAAG,CAAC,CAAC,YAAY,CAAC;IAC5D;;;OAGG;IACH,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,qCAAqC,CAAC,CAAC,OAAO,CAAC,CAAC,CAAC;IACnF,6FAA6F;IAC7F,aAAa,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,QAAQ,EAAE;CAC5D,CAAC,CAAC;AAGH;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AACH,MAAM,CAAC,MAAM,+BAA+B,GAAG,mCAAmC,CAAC,MAAM,CAAC;IACxF;;;OAGG;IACH,OAAO,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,QAAQ,EAAE;IACrD,sDAAsD;IACtD,MAAM,EAAE,CAAC,CAAC,IAAI,CAAC,wBAAwB,CAAC,CAAC,QAAQ,EAAE;IACnD,OAAO,EAAE,+BAA+B,CAAC,QAAQ,EAAE;CACpD,CAAC,CAAC,WAAW,CAAC,CAAC,KAAK,EAAE,OAAO,EAAE,EAAE;IAChC,IAAI,KAAK,CAAC,OAAO,KAAK,SAAS,IAAI,KAAK,CAAC,MAAM,KAAK,SAAS,EAAE,CAAC;QAC9D,OAAO,CAAC,QAAQ,CAAC;YACf,IAAI,EAAE,QAAQ;YACd,IAAI,EAAE,CAAC,SAAS,CAAC;YACjB,OAAO,EAAE,UAAU,KAAK,CAAC,MAAM,0IAA0I;SAC1K,CAAC,CAAC;IACL,CAAC;AACH,CAAC,CAAC,CAAC;AAGH,MAAM,CAAC,MAAM,0BAA0B,GAAG,CAAC,CAAC,MAAM,CAAC;IACjD,GAAG,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC;IACtB,OAAO,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC;IAC1B,KAAK,EAAE,CAAC,CAAC,IAAI,CAAC,kBAAkB,CAAC;IACjC,MAAM,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC;IACzB;;;;;;;;;;;OAWG;IACH,aAAa,EAAE,CAAC,CAAC,KAAK,CAAC,mCAAmC,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;IACvE,MAAM,EAAE,CAAC,CAAC,KAAK,CAAC,+BAA+B,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;IAC5D,OAAO,EAAE,CAAC,CAAC,KAAK,CAAC,mCAAmC,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;IACjE;;;;;;OAMG;IACH,WAAW,EAAE,CAAC,CAAC,KAAK,CAAC,qCAAqC,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;IACvE,MAAM,EAAE,CAAC,CAAC,MAAM,CAAC;QACf,QAAQ,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC;QAC3B,SAAS,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;QACjD;;;;;;;;;;;;;;;;;;;;;WAqBG;QACH,aAAa,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;QACrD,WAAW,EAAE,kCAAkC,CAAC,QAAQ,EAAE;QAC1D;;;;;WAKG;QACH,cAAc,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,IAAI,CAAC,0BAA0B,CAAC,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;QACvE;;;;;;;;;;;;;;;;;;;;;;;;;WAyBG;QACH,+BAA+B,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;QACvE;;;;WAIG;QACH,YAAY,EAAE,+BAA+B,CAAC,QAAQ,EAAE;QACxD;;;;;;;;;WASG;QACH,wBAAwB,EAAE,CAAC,CAAC,OAAO,EAAE,CAAC,OAAO,CAAC,KAAK,CAAC;QACpD;;;;;;;;;;;;;WAaG;QACH,iBAAiB,EAAE,CAAC,CAAC,OAAO,EAAE,CAAC,OAAO,CAAC,KAAK,CAAC;QAC7C;;;;;;;;WAQG;QACH,4BAA4B,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,IAAI,CAAC,0BAA0B,CAAC,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;QACrF;;;;;;;;;;;;;;;;;;;;;;;;;;;;;WA6BG;QACH,YAAY,EAAE,uCAAuC,CAAC,QAAQ,EAAE;KACjE,CAAC;IACF;;;;;;;OAOG;IACH,QAAQ,EAAE,CAAC,CAAC,IAAI,CAAC,qBAAqB,CAAC,CAAC,QAAQ,EAAE;IAClD;;;;;;;;;;;;;OAaG;IACH;;;;;;;;;;;;;;;;;;;;;;;OAuBG;IACH;;;;;;;;;;;;;;;;;;;;OAoBG;IACH,QAAQ,EAAE,CAAC,CAAC,IAAI,CAAC,2BAA2B,CAAC;IAC7C,MAAM,EAAE,iCAAiC;IACzC,SAAS,EAAE,CAAC,CAAC,IAAI,CAAC,0BAA0B,CAAC;CAC9C,CAAC,CAAC,WAAW,CAAC,CAAC,QAAQ,EAAE,OAAO,EAAE,EAAE;IACnC;;;;OAIG;IACH,QAAQ,CAAC,aAAa,CAAC,OAAO,CAAC,CAAC,SAAS,EAAE,KAAK,EAAE,EAAE;QAClD,IAAI,SAAS,CAAC,IAAI,KAAK,0BAA0B,CAAC,gBAAgB;YAAE,OAAO;QAC3E,MAAM,QAAQ,GAAG,yCAAyC,CAAC,SAAS,CAAC,QAAQ,CAAC,MAAM,EAAE,SAAS,CAAC,QAAQ,CAAC,CAAC;QAC1G,IAAI,QAAQ,KAAK,SAAS,EAAE,CAAC;YAC3B,OAAO,CAAC,QAAQ,CAAC;gBACf,IAAI,EAAE,QAAQ;gBACd,IAAI,EAAE,CAAC,eAAe,EAAE,KAAK,EAAE,UAAU,CAAC;gBAC1C,OAAO,EAAE,IAAI,SAAS,CAAC,QAAQ,CAAC,MAAM,2BAA2B,SAAS,CAAC,QAAQ,iDAAiD;aACrI,CAAC,CAAC;YACH,OAAO;QACT,CAAC;QACD,IAAI,CAAC,QAAQ,CAAC,UAAU,CAAC,QAAQ,CAAC,SAAS,CAAC,MAAM,CAAC,EAAE,CAAC;YACpD,OAAO,CAAC,QAAQ,CAAC;gBACf,IAAI,EAAE,QAAQ;gBACd,IAAI,EAAE,CAAC,eAAe,EAAE,KAAK,EAAE,QAAQ,CAAC;gBACxC,OAAO,EAAE,IAAI,SAAS,CAAC,MAAM,wBAAwB,SAAS,CAAC,QAAQ,CAAC,MAAM,eAAe,SAAS,CAAC,QAAQ,sBAAsB,QAAQ,CAAC,UAAU,CAAC,IAAI,CAAC,IAAI,CAAC,GAAG;aACvK,CAAC,CAAC;QACL,CAAC;IACH,CAAC,CAAC,CAAC;AACL,CAAC,CAAC,CAAC","sourcesContent":["import { z } from \"zod\";\n\nimport {\n HumanDecision_FieldKind,\n} from \"@wildo-ai/saas-models\";\nimport {\n MetaWorkflow_ApprovalPolicy,\n MetaWorkflow_ArtifactContractSchema,\n MetaWorkflow_ArtifactSelectorSchema,\n MetaWorkflow_ChoreographySchema,\n MetaWorkflow_ElicitationSpecSchema,\n MetaWorkflow_Executor,\n MetaWorkflow_FailurePolicy,\n MetaWorkflow_JourneyPredicateSchema,\n MetaWorkflow_PlaybookBudgetSchema,\n MetaWorkflow_PlaybookDeliberationSchema,\n MetaWorkflow_PredicateKind,\n MetaWorkflow_StepOutputContractSchema,\n} from \"@wildo-ai/saas-models/meta-workflows\";\n\nimport { getApplicationSpecificationFamilyDecision } from \"./application-specification-family-decisions.application-creation.schemas\";\n\n//===============================================================\n// Meta-Workflow Playbooks\n// -------------------------\n// A playbook is the declarative, versioned definition of one coherent\n// piece of app-creation work (design plan `app-creation-meta-workflows.md`,\n// section D2). Playbooks are DATA, not code: they are authored under\n// `framework-knowledge/src/playbooks/` (folder-per-playbook: one canonical\n// structured source — contained `playbook.json` or native\n// `playbook.definition.ts` — plus `method.md`), compiled into\n// `dist/knowledge/playbooks/`, and loaded by the framework-knowledge seam.\n// Refining the\n// methodology of a step means editing a playbook — never engine code.\n//\n// A playbook is a STANDALONE root schema, deliberately NOT a third\n// `FlowActorSystem_Kind` (implementation-spec P-1): playbooks are\n// *definitions*, while playbook *runs* are — by contract (P-11) — `ActorSystem` executions\n// identified by the `systemRef: 'meta-workflows.<playbookRef>'` convention. Extending the kind\n// enum would ripple through every `kind` narrow in the engine for zero semantic gain.\n//\n// The run half of that sentence is an OBLIGATION rather than a description, and was written here\n// as fact until 2026-09-19: no playbook run creates an actor execution today (#1343). It does not\n// weaken the argument above — a playbook is a definition either way — but it must not be read as\n// evidence that the run plane is already the actor plane.\n//\n// The STRONGER reason, measured 2026-08-29 and recorded because the one above\n// is an ergonomic argument and will be reopened on its own weakness:\n// `FlowActorSystem_Base` is dominated by RUNTIME AND LIFECYCLE state —\n// `createdAt` / `updatedAt` / `deletedAt` / `deprecatedAt` / `publishedAt`,\n// `circuitBreakerStatus`, `errorItems`, `checkpoint`, `checkpointChecks`,\n// `timestamp`. A playbook has none of that and must not: playbooks are FILES,\n// accepted by being committed, and git owns their history, publication and\n// deprecation (`.claude/rules/one-source-of-truth.md`, Rule 0). Making a\n// playbook a third kind would inherit a durable lifecycle and state model\n// THROUGH THE BASE — re-importing by inheritance the ledger Rule 0 demolished.\n//\n// The actors/flows distinction is real and is already expressed correctly, in\n// two relations that are producer -> artifact and never is-a: a playbook is a\n// DEFINITION; its RUN is an `ActorSystem` execution; and a fully deterministic\n// playbook may COMPILE into a `FlowSystem` when that engine exists. So a\n// playbook never declares which kind it \"is\" — asking it to would be the\n// second authority this contract stays engine-agnostic to avoid.\n//\n// Rejected alternative: authoring playbooks as flows-actors `FlowSystem`\n// step graphs — the step-graph engine is deferred and choreographic work\n// is agentic/plan-driven, not a static step DAG. Fully deterministic\n// playbooks may later COMPILE into FlowSystems; the contract stays\n// engine-agnostic here.\n//===============================================================\n\n\n/**\n * The KIND OF REASONING a playbook embodies — a taxonomy label on the playbook, and nothing else.\n *\n * ## What this is NOT, since 2026-09-04\n *\n * It is not a state an application can be in. There was a `deriveJourneyPhase` that computed one —\n * `bottom_up` the moment `domain-plan` or `build-plan` had content, monotonic and irreversible — and\n * 19 playbooks gated on matching it. It has been deleted, along with the `PHASE_IS` predicate, and\n * neither should come back.\n *\n * The reason is recorded in `.claude/context/app-creation-composite-choreography.md` §13: **an\n * evolving application is not in a phase; it is in a STATE, and the state is the tree.** Top-down and\n * bottom-up are ways of APPROACHING a problem. An application holds artifacts produced by both, all\n * of them still valid inputs, and moving between the modes is ordinary product work. What legitimately\n * constrains what may run is DEPENDENCY, and the ARTIFACT preconditions express that exactly.\n *\n * The derived phase failed in three separate ways at once, all measured before it went:\n *\n * - on the `bottom_up` side it was **provably redundant** — every playbook gated on it already\n * required `domain-plan` or `build-plan`, the two families that DEFINED the phase, so it could\n * refuse nothing readiness had not already refused;\n * - it contained a **deadlock**: `bottom_up.domain-plan` gated on `bottom_up` and PRODUCED the family\n * that creates it, so the unattended loop could never enter that phase at all;\n * - on the `top_down` side it blocked **return**, not incoherence — after a domain plan landed, the\n * loop could never revisit market analysis or requirements, whose real inputs were still valid.\n *\n * Three patches preserved it before it was removed: reclassifying `PHASE_IS` as SEQUENCING so humans\n * could bypass it, removing the gate from one playbook (#116), and threading a\n * `proceedPastSequencing` flag through the choreography so a composite's children inherited the\n * parent's bypass. Each moved the pain to the next caller.\n *\n * ## What it still does\n *\n * It labels a playbook, which is true and useful: it says what kind of thinking that playbook\n * embodies, and it groups the catalog for whoever reads it. Nothing gates on it, so every member is\n * equally usable — {@link MetaWorkflow_Phase.REFINEMENT} and {@link MetaWorkflow_Phase.CROSS_CUTTING}\n * were \"unreachable\" only because a gate demanded a derivation that could not produce them.\n */\nexport enum MetaWorkflow_Phase {\n /** Reasoning from intent down to structure: vision, market, requirements, roadmap, compliance posture. */\n TOP_DOWN = \"top_down\",\n /** Reasoning from structure up: the domain model, the build plan, placement, execution. */\n BOTTOM_UP = \"bottom_up\",\n /** Revisiting a produced artifact against what the application has since become. */\n REFINEMENT = \"refinement\",\n /** Work that belongs to no single direction. */\n CROSS_CUTTING = \"cross_cutting\",\n}\n\n\n/**\n * The seven functional topics of the canonical app-development workflow taxonomy — a **BUILD**\n * taxonomy, in build order: configure the foundation, model the domain, define interaction, shape\n * the experience, extend, connect runtime and external capabilities, assemble and verify.\n *\n * ## What reads this, measured 2026-08-30\n *\n * | Surface | Status |\n * |---|---|\n * | `BuildPlanTask.functionalTopic` | **LIVE** — stamped into the coding-agent dispatch payload as context the agent reads |\n * | `MetaWorkflowPlaybook.functionalTopics` | **REMOVED 2026-09-08 (#488)** — authored intent the compiler copied into the compiled catalog and no runtime read |\n * | `MetaWorkflow_PredicateKind.TOPIC_COMPLETE` | **GONE (2026-09-05)** — it was a real precondition kind whose evaluator always returned `satisfied: false`, because topic completion was a journey-record fact and nothing derives it from the working tree. Zero playbooks ever gated on it |\n *\n * So a topic reaches exactly one decision anywhere: none. Build-task ordering is\n * `prerequisiteTaskRefs` alone, and playbook eligibility is `preconditions` — where the one kind\n * keyed on a topic could never be satisfied, so any playbook declaring it would have been permanently\n * ineligible with nothing reporting it. It followed `PHASE_IS` out on 2026-09-05 for exactly that\n * reason: both gated on a derived global state that nothing derives (see {@link MetaWorkflow_Phase}).\n *\n * The vocabulary itself stays, because `BuildPlanTask.functionalTopic` is live. What went is the idea\n * that a topic could grant PERMISSION. If completion ever becomes derivable from the working tree,\n * it belongs as an artifact-shaped precondition or as a runtime-synthesized verdict — not as a new\n * global state a playbook can demand.\n *\n * ## The claim this replaced\n *\n * This JSDoc said \"Completeness tracking and playbook routing key on these functional nodes\". Both\n * halves were false and had been since the enum was typed: there is no completeness tracking, and\n * routing is `preconditions`. The cost was not a wrong result — it was that the sentence read as a\n * mechanism, so decisions were argued from it. One session declined to author a dedicated playbook\n * partly on the strength of a \"frozen taxonomy\" that no checker enforced and whose cited authority\n * (`fwk-ai-assisted-development-workflow-model.md`) lives in gitignored `.claude/plans/` and does\n * not survive a re-clone. See issue #124 and `.claude/rules/capability-catalog-integration.md`.\n *\n * The enum is the reachable source. Prefer an existing topic; adding one is a deliberate decision,\n * not a prohibition — but note that nothing downstream will react to it.\n */\nexport enum MetaWorkflow_FunctionalTopic {\n CONFIGURE_APPLICATION_FOUNDATION = \"configure_application_foundation\",\n MODEL_DOMAIN_GRAPH = \"model_domain_graph\",\n DEFINE_INTERACTION_SEMANTICS = \"define_interaction_semantics\",\n SHAPE_USER_EXPERIENCE = \"shape_user_experience\",\n EXTEND_APPLICATION = \"extend_application\",\n CONNECT_RUNTIME_AND_EXTERNAL_CAPABILITIES = \"connect_runtime_and_external_capabilities\",\n ASSEMBLE_VERIFY_AND_ITERATE = \"assemble_verify_and_iterate\",\n}\n\n/*\n * `MetaWorkflow_ElicitationQuestionKind` stood here until 2026-09-19 (#1342). It was collapsed onto\n * {@link HumanDecision_FieldKind} on 2026-09-17 and kept as an ALIAS — `export const X: typeof\n * HumanDecision_FieldKind = HumanDecision_FieldKind` — on the reasoning that \"the name stays because\n * every playbook definition and every consumer spells it this way, and the creation layer is where\n * the reader expects to find it.\"\n *\n * That reasoning described the consumers rather than the vocabulary, and the alias was doing real\n * harm: the companion imported the app-creation name specifically to dodge a `TS2742` it hit when\n * naming the engine enum, which is an alias telling you it is the wrong door. A second name for an\n * engine type is also exactly what \"closed vocabularies have ONE named runtime source\" forbids —\n * the rule the collapse itself was invoking.\n *\n * Every consumer now spells {@link HumanDecision_FieldKind} and imports it from `@wildo-ai/saas-models`,\n * which is where the vocabulary always lived. What stays on this side is the CONFIRM-answer\n * resolution below: `saas-models` validates a CONFIRM only as non-empty, and deciding what a\n * creator's free text means is a creation-layer concern.\n */\n\n/**\n * What a {@link HumanDecision_FieldKind.CONFIRM} answer means once resolved.\n *\n * A closed vocabulary with a named source, because the answer DECIDES things: the five CONFIRM\n * questions in `top_down.vision-elicitation` screen for regulated domains — children's data,\n * financial services, healthcare, legal/compliance, public sector — and their answers become the\n * application's declared compliance posture.\n */\nexport enum MetaWorkflow_ConfirmationAnswer {\n YES = \"yes\",\n NO = \"no\",\n}\n\n/**\n * Resolve a creator's free-text answer to a CONFIRM question, or `null` when it is not unambiguous.\n *\n * ## Why this is not a string comparison, and not a prefix match either\n *\n * Until 2026-08-29 nothing validated a CONFIRM answer at all: only CHOICE was branched on, so any\n * non-empty string was accepted and \"probably\" or \"not sure\" flowed into the vision brief as the\n * source of truth for a compliance decision (issue #117).\n *\n * The obvious fix — compare against `\"yes\"`/`\"no\"` exactly — was rejected on MEASURED evidence: the\n * real recorded answers in this repository are `\"No.\"`, capitalised and punctuated. A guard that\n * refuses what creators actually type is a guard with no way past\n * (`.claude/rules/design-philosophy.md`).\n *\n * A PREFIX match was rejected as worse than either. `\"No, but we may later\"` starts with `no` and\n * would resolve to NO, silently discarding the caveat — on a question about whether an application\n * processes children's data. So the WHOLE normalised answer must be a recognised token; anything\n * else returns `null` and the caller refuses, naming the accepted forms.\n *\n * Refusing nuance costs the creator nothing here: the same interview pairs those five questions with\n * a free-text `compliance-detail` question, which is where \"no, but we may later\" belongs and where\n * it survives as prose instead of collapsing into a boolean.\n */\nexport function resolveConfirmationAnswer(rawAnswer: string): MetaWorkflow_ConfirmationAnswer | null {\n // Trailing punctuation and case are presentation, not meaning: `\"No.\"` and `\"no\"` are one answer.\n const normalized = rawAnswer.trim().toLowerCase().replace(/[.!]+$/u, \"\").trim();\n if (CONFIRMATION_ANSWER_AFFIRMATIVE_FORMS.has(normalized)) return MetaWorkflow_ConfirmationAnswer.YES;\n if (CONFIRMATION_ANSWER_NEGATIVE_FORMS.has(normalized)) return MetaWorkflow_ConfirmationAnswer.NO;\n return null;\n}\n\n/** Accepted spellings of YES. Deliberately short and closed — a long list is a prefix match wearing a set's clothing. */\nconst CONFIRMATION_ANSWER_AFFIRMATIVE_FORMS: ReadonlySet<string> = new Set([\"yes\", \"y\", \"true\"]);\n/** Accepted spellings of NO. */\nconst CONFIRMATION_ANSWER_NEGATIVE_FORMS: ReadonlySet<string> = new Set([\"no\", \"n\", \"false\"]);\n\n/** The forms a refusal message should name, so the creator is told what to type rather than guessing. */\nexport const CONFIRMATION_ANSWER_ACCEPTED_FORMS: readonly string[] = Object.freeze([\n ...CONFIRMATION_ANSWER_AFFIRMATIVE_FORMS,\n ...CONFIRMATION_ANSWER_NEGATIVE_FORMS,\n]);\n\n/**\n * Structured questions a HUMAN-executed (or elicitation-bearing) playbook\n * asks the creator. Kept lean in v1 — the method guidance prose carries the\n * interviewing style; this only types the answers' shape.\n */\n/**\n * Derived context a playbook's brief carries BEYOND its declared `inputs[]`.\n *\n * `inputs[]` says which artifact FAMILIES a playbook reads. These are the other sections a brief can\n * carry: facts the runtime computes rather than reads, and catalogs it renders. They are declared\n * because they cost real tokens and only pay for the playbooks whose method actually routes through\n * them — a brief that carries everything for everyone is how a prompt stops fitting.\n *\n * ## Why this is an enum and not a set of booleans\n *\n * It is a closed vocabulary with per-member meaning, which is the case\n * `CLAUDE.md` reserves an enum for: each member needs somewhere to explain what the section IS and\n * when a playbook should ask for it, and a bare `carriesSkillCatalog: true` has nowhere to put that.\n *\n * ## History\n *\n * Each of these was a frozen `readonly string[]` of playbook refs inside the dev companion's run\n * service — a list naming which playbooks got which section. That is the shape the composite work\n * exists to end: a capability reachable only by editing the runtime that dispatches it. The brief\n * already composed its `inputs` and `elicitation` sections FROM DECLARATIONS, so three of its five\n * sections were declared and three were hardcoded; this makes all of them declared.\n */\nexport enum MetaWorkflow_ContextSource {\n /**\n * Real module ids and per-resource present schema fields, read from the application's CODE.\n *\n * For playbooks that plan against what EXISTS rather than against definition artifacts. Without it\n * a planner invents module ids that do not resolve, and every task it emits fails at dispatch.\n */\n WORKSPACE_TRUTH = 'workspace_truth',\n /**\n * The full application-knowledge skill catalog (`skills/INDEX.md`), not just this playbook's own\n * `method.skillRefs`.\n *\n * Only for a method that ROUTES THROUGH the catalog — one that must bind its output to a skill it\n * chooses. Measured 2026-08-27: the one playbook of that shape was choosing from recall because\n * the catalog never reached its brief, and a dangling skill ref is a task the dispatch playbook\n * cannot run. Every other playbook still gets its own `skillRefs` rendered; this is ~25KB and pays\n * only where the choosing happens.\n */\n SKILL_CATALOG = 'skill_catalog',\n /**\n * The DERIVED cross-family coherence report — dangling references and coverage, computed exactly\n * by set operations over the landed families.\n *\n * For a playbook that ASSESSES coherence. Asking a model to re-derive it from five documents is\n * asking it to do worse, slower, what a function already did; the arithmetic goes in so the model\n * can judge what arithmetic cannot — whether an uncovered item is a deliberate deferral or an\n * omission.\n */\n COHERENCE_REPORT = 'coherence_report',\n /**\n * The application's compliance-relevant resource DECLARATIONS, read from its resource\n * configurations and split by origin (engine-declared vs application-declared).\n *\n * For a playbook that must state what the application actually does to a row — erasure retention\n * mode, data-subject kind, subject export, the audited see-through path — rather than what a\n * specification says it is for. A specification carries PURPOSE; a resource configuration carries\n * MECHANISM, and a governed document may only assert the second from the second.\n *\n * Added 2026-08-29, and the gap it closes is the shape this lane keeps producing.\n * `refinement.document-facts` had said in its intent and throughout its method that mechanism facts\n * \"are read from the resource configurations\" since the day it was authored, and nothing read them:\n * (spec-cite: N/A — that phrase is this repository's OWN playbook prose, `refinement.document-facts`'s\n * intent and method, quoted because the runtime did not honour it; it is not attributed to and does\n * not come from any external standard.)\n * the `compliance-primary-facts` introspection behavior existed, was tested, answered correctly over\n * HTTP — and had NO CONSUMER. Its first live production run landed two facts, both paraphrased from\n * prose, neither citing a declaration. A method that describes a derivation the runtime cannot\n * perform is not guidance, it is a claim the output will quietly fail to honour.\n */\n COMPLIANCE_PRIMARY_FACTS = 'compliance_primary_facts',\n /**\n * The engine catalog's DEFINITION and BLUEPRINT for the governed documents a lane may draft: which\n * sections a notice must contain, in what order, which facts each requires, and the typed questions\n * behind them.\n *\n * For a playbook that DRAFTS a governed document. It is the structure half of the same split\n * `COMPLIANCE_PRIMARY_FACTS` makes on the content half — the facts source says what the application\n * does, this says what the document is obliged to address, and a drafter needs both to write a\n * clause that is true AND required.\n *\n * Added 2026-08-30 against a measurement, not a hunch. `document-definition:public.privacy-notice`\n * requires eight facts; wonder-crm's generated notice declared twenty and matched NONE of them,\n * scoring zero dangling citations the whole time — internally consistent, and addressing none of\n * what a privacy notice must address. The catalog had held the answer since it was written and had\n * no runtime lookup of any kind: the only `(definitionRef) → blueprint` resolution in the repository\n * lived inside a schema test. Meanwhile the shipped authoring skill instructed the drafter to \"Read\n * the definition and blueprint\", a step it was told to perform and given nothing to perform it on.\n */\n DOCUMENT_BLUEPRINT = 'document_blueprint',\n /**\n * The exact fact NAMES the engine catalog's documents require, with the question each answers.\n *\n * For the playbook that DECLARES facts, and deliberately separate from `DOCUMENT_BLUEPRINT`: the\n * drafter needs structure, the fact producer needs the closed set of names. Sending it the drafting\n * brief would bury the eight lines that matter under section obligations it never authors.\n *\n * The gap it closes, measured 2026-08-30: a fact's ref is stamped from a slug the model chooses, so\n * a fact answering the right question under a different name is a fact no clause can cite. wonder-crm\n * declared twenty facts and matched ZERO of the eight a privacy notice requires —\n * `retention-period-schedule-status` for `retention-rules`,\n * `configured-external-provider-recipients` for `recipients-and-processors`. Semantically adjacent,\n * lexically disjoint, so nothing joins them and the answers read as absent.\n *\n * The method has asked for stable descriptive slugs, NAMING THREE OF THE EIGHT as examples, since\n * 2026-08-28 — two days before that measurement. Prose has been tried; what was never supplied is\n * the closed set the catalog has held all along.\n */\n DOCUMENT_FACT_OBLIGATIONS = 'document_fact_obligations',\n /**\n * The closed sets a compliance programme may bind and cite: the objectives the assurance authority basis states an\n * expectation for, and the sources the registry carries.\n *\n * Same lesson as {@link DOCUMENT_FACT_OBLIGATIONS}, with a harsher failure. The programme's normalizer REFUSES an\n * objective the basis has no expectation for and a source the registry does not carry, so a producer that guesses does\n * not land a subtly wrong artifact — it spends a run, out of the three a playbook is budgeted.\n */\n ASSURANCE_PROGRAM_AUTHORITY = 'assurance_program_authority',\n /**\n * The application's OWN role graph: the app-scope and organization-scope roles it actually declares,\n * which user type receives which by default, and which role holds the administrative ceiling.\n *\n * For a playbook that must name an ACCOUNTABLE or OPERATING role. It replaces two free-text\n * elicitation questions on `top_down.compliance-conception` that asked a person to type\n * *\"the application's own role key (e.g. APP_ADMIN_SUPER_ADMIN)\"* — a value that is not a judgement\n * at all: the role vocabulary is a closed enum (`CORE_APP_ROLES` / `CORE_ORG_ROLES`), and which\n * roles THIS application grants is declared in its own backend config (`userTypes[].defaultAppRoles`,\n * `organizationTypes[].availableOrgRoles`). Asking for it invited a role key that resolves to\n * nothing, in an artifact whose whole purpose is to say who is accountable.\n *\n * Same lesson as {@link ASSURANCE_PROGRAM_AUTHORITY} and {@link DOCUMENT_FACT_OBLIGATIONS}: supply\n * the closed set rather than describing it. What stays a decision is WHICH of the declared roles is\n * accountable — a selection from a rendered set, not a string somebody invents.\n *\n * Derived from a static enum plus the backend companion exports the runtime already loads, so it\n * needs no new introspection behavior.\n */\n APPLICATION_ROLE_GRAPH = 'application_role_graph',\n /**\n * The judged runs committed in this application's OWN assurance repository — what its controls were\n * measured to do, as SELF-ATTESTED INTERNAL EVIDENCE (#297).\n *\n * For a playbook drafting an INTERNAL governance document, and for nothing else today. Until this\n * existed the assurance cycle produced findings and clean passes that were citable by nobody: an\n * operating statement had exactly two forms, an unsupported claim or a mark, so the mark was always\n * correct and the evidence never reached the only documents entitled to rest on it.\n *\n * It is deliberately NOT a verdict the lane reacts to. Nothing here gates a run, a drafter may cite a\n * run or ignore it, and an application with no repository or no runs gets a section that says so —\n * the clause is then MARKED, exactly as before (`application-creation-directive.md`: a workflow never\n * blocks the mechanism). The one-way street the assurance plane keeps — it reads the product and\n * writes only into its own repository — is unchanged: this carries committed runs INTO a brief and\n * gives the creation lane no way to write back.\n *\n * What a citing clause owes is stated where it is enforced rather than here: the ref must resolve to\n * a committed run, and ANY citation in a document under `document-claim-policy:public-safe-baseline`\n * is refused, because what makes a public operating claim wrong is the reader it reaches rather than\n * the evidence behind it.\n */\n ASSURANCE_EVIDENCE = 'assurance_evidence',\n /**\n * The document facts a PERSON established — the `document-facts-authored` family, which the derived\n * family deliberately does not carry.\n *\n * A drafter reads the derived facts as a declared input. The authored ones it could not read at all,\n * and the cost is measurable: on wonder-todos 2026-09-22 the governance draft CITED\n * `document-fact:governance-scope-review-triggers` and wrote a paraphrase around it — \"change in a way\n * identified by the scope-review decision\" — where the authored value names the triggers outright and\n * adds an annual human review the draft omits entirely. The clause was marked DERIVED and the landing\n * accepted it, because the fact-binding check asks whether a cited fact was DECLARED and never whether\n * the drafter could read it. Citation without readership.\n *\n * It is a CONTEXT SOURCE rather than a declared input for a structural reason, not a stylistic one:\n * the authored family is landed by the companion's governance-facts door rather than by any playbook,\n * so declaring it as an input is an input family no playbook produces — which `wildo fwk audit` rule 23\n * refuses outright. Derived context has no such requirement, and this IS derived context: the lane\n * reads it and never writes it.\n *\n * Kept SEPARATE from the derived facts in the brief rather than merged into them, because the\n * difference is what a drafter most needs to respect. A derived fact is re-derived from the product on\n * the next run; an authored one is a person's decision, and a clause that contradicts it contradicts\n * the human who wrote it.\n */\n AUTHORED_DOCUMENT_FACTS = 'authored_document_facts',\n /**\n * The DETERMINISTIC per-ICP FIT matrix, computed from the decided market snapshot by\n * `computeFeatureFitScoreForICP`, delivered beside each benefit's AUTHORED Kano category.\n *\n * For a playbook whose method consumes a fit signal. Three of them do — `top_down.capability-map`,\n * `top_down.value-proposition`, `top_down.scope-roadmap` — and all three told their model to \"feed\n * the snapshot to the scorer and read back the scores\". A structured generation has no tools, so\n * that instruction named an act the model cannot perform; what it did instead was estimate, which\n * is arithmetic done worse and unfalsifiably.\n *\n * Exactly `COHERENCE_REPORT`'s trade, for the same reason: the arithmetic goes in so the model can\n * judge what arithmetic cannot — whether a low-scoring capability is a mis-mapped benefit or a\n * segment the product deliberately does not serve.\n *\n * Every playbook that declares it ALREADY declares `market-snapshot` as an input, so this adds no\n * new knowledge to the brief; it adds a computation over knowledge that was already there. That is\n * what distinguishes it from a speculative source, which `.claude/context/app-creation-dynamic-context.md`\n * design 8 would hold to a paired-case measurement first.\n *\n * SCORES ONLY, never a ranking. The scorer's own docstring locks the vocabulary — fit is not\n * prioritization — and a section that sorted by score would smuggle in the build-order model the\n * methods explicitly defer.\n */\n MARKET_FIT_SCORES = 'market_fit_scores',\n /**\n * The DERIVED risk signals (#300 Layer 1) — measured facts about this application's own\n * declarations, each with its provenance and none with a score.\n *\n * For a playbook that weighs risk. `top_down.risk-register`'s method says \"if signals were not\n * supplied to this run…\" and, measured 2026-09-22, nothing had ever supplied them: the six\n * derivations were reachable only from an assurance script, so the register's derived half was\n * permanently absent and every run took the fallback branch.\n *\n * NOT the assurance plane. The derivations moved into the engine precisely so the creation lane\n * could read them without importing that plane — `application-creation-directive.md` keeps that\n * street one-way, and its collectors' hard exits are right for an auditor's tool and wrong inside\n * a run that must not stop. What arrives here is a pure function of `wildo.saas.config.ts` and the\n * application's own materialized resources; nothing is measured from a running system, nothing is\n * a verdict, and the section never gates the run.\n *\n * SIGNALS, never conclusions, and the derivation layer asserts that structurally: no score, no\n * weight, no level, no severity. What a signal MEANS is the playbook's question — which is the\n * whole reason the arithmetic is delivered and the judgement is not.\n */\n RISK_SIGNALS = 'risk_signals',\n}\n\n/**\n * How a declared input reaches the brief.\n *\n * Input-only — see {@link MetaWorkflowPlaybookInputSchema} for why this is not on the shared selector.\n */\nexport enum MetaWorkflow_InputRender {\n /** The selected aspects' content, rendered as prose — what every input received before aspects existed. */\n FULL = \"full\",\n /**\n * Only one `ref — label` line per element of the selected aspects. For a step that needs to know WHAT\n * exists (to reference it by ref, or to stay consistent with it) without re-reading its content.\n */\n MAP = \"map\",\n}\n\n/**\n * The deepest RELATED walk anything may ask for — a playbook input's `related.hops` and the\n * `specification-elements` pull door share this one cap. Each hop multiplies what comes back, and\n * nothing measured so far asks for more than one.\n */\nexport const DECIDED_ELEMENTS_MAXIMUM_RELATED_HOPS = 2;\n\n/** Follow the declared reference edges out of an input's selected elements. */\nexport const MetaWorkflow_InputRelatedSchema = z.strictObject({\n /**\n * Edges to follow from each selected element, both directions. Capped at 2: each hop multiplies\n * what the brief carries, and nothing measured so far asks for more than one.\n */\n hops: z.number().int().min(1).max(DECIDED_ELEMENTS_MAXIMUM_RELATED_HOPS).default(1),\n /** Keep only related elements of these aspect keys. The walk itself crosses every aspect. */\n targetAspects: z.array(z.string().min(1)).min(1).optional(),\n});\nexport type MetaWorkflow_InputRelated = z.infer<typeof MetaWorkflow_InputRelatedSchema>;\n\n/**\n * One declared INPUT of a playbook: the shared artifact selector plus what the step reads of it (#1420).\n *\n * ## Why this is not on `MetaWorkflow_ArtifactSelectorSchema`\n *\n * That selector also types PRECONDITIONS. An aspect or a render mode there would read as a readiness\n * gate — \"wait until these aspects exist\" — which eligibility never honours. Narrowing what a playbook\n * READS must never narrow what it WAITS FOR, so the narrowing lives on the input alone.\n *\n * ## By ASPECT, never by ref\n *\n * A playbook is application-agnostic: its author cannot know which ICPs or requirements an\n * application will have. So a static declaration names aspect KINDS (`market.icp`); fetching one\n * element by ref is a run-time act of an agent that has already seen the map.\n *\n * ## What is validated where\n *\n * The keys must exist and must belong to the declared family. That check needs the aspect registry,\n * which this module cannot import (the family schemas it indexes import this module for\n * `MetaWorkflow_FunctionalTopic`, so the import would be a cycle evaluated at load). It runs at\n * `wildo fwk generate-docs`, through `findPlaybookInputAspectViolations` in\n * `@wildo-ai/application-creation-runtime`, and fails the generation closed. What this schema refuses\n * is what it can see on its own: an `aspects` list beside an `intent`, which would be two narrowings of\n * one input with no rule for which wins.\n */\nexport const MetaWorkflowPlaybookInputSchema = MetaWorkflow_ArtifactSelectorSchema.extend({\n /**\n * The aspect keys of `family` this step reads (`['market.icp', 'market.job']`). Absent = the whole\n * family. Everything else in the family is shown as a MAP (ref + label), never silently dropped.\n */\n aspects: z.array(z.string().min(1)).min(1).optional(),\n /** Absent = {@link MetaWorkflow_InputRender.FULL}. */\n render: z.enum(MetaWorkflow_InputRender).optional(),\n related: MetaWorkflow_InputRelatedSchema.optional(),\n}).superRefine((input, context) => {\n if (input.aspects !== undefined && input.intent !== undefined) {\n context.addIssue({\n code: \"custom\",\n path: [\"aspects\"],\n message: `Input \"${input.family}\" declares both \\`intent\\` and \\`aspects\\`. They are two narrowings of one input with no rule for which wins; declare the aspects alone.`,\n });\n }\n});\nexport type MetaWorkflowPlaybookInput = z.infer<typeof MetaWorkflowPlaybookInputSchema>;\n\nexport const MetaWorkflowPlaybookSchema = z.object({\n ref: z.string().min(1),\n version: z.string().min(1),\n phase: z.enum(MetaWorkflow_Phase),\n intent: z.string().min(1),\n /*\n * There is deliberately NO `functionalTopics` on a PLAYBOOK (#488, removed 2026-09-08).\n *\n * Authored intent that nothing branched on: the generator copied it into the compiled catalog and\n * no runtime read it from there. Non-empty on 4 of 26 playbooks, empty on the rest — a taxonomy\n * label kept because it looked like structure.\n *\n * The VOCABULARY stays, because `BuildPlanTask.functionalTopic` — SINGULAR, on the task — is live:\n * required on the task graph, copied through generation, and stamped into the coding-agent dispatch\n * payload as context the agent reads. The two differ by one letter and by which object carries them,\n * which is exactly why this needed measuring rather than grepping the enum.\n */\n preconditions: z.array(MetaWorkflow_JourneyPredicateSchema).default([]),\n inputs: z.array(MetaWorkflowPlaybookInputSchema).default([]),\n outputs: z.array(MetaWorkflow_ArtifactContractSchema).default([]),\n /**\n * Values this playbook returns to its PARENT choreography instead of landing.\n *\n * Orthogonal to `outputs`, not an alternative to it: a playbook may do both, and a child that lands\n * a file lands it exactly as it would standalone. Composition adds a second return channel; it does\n * not intercept the first. That is also why every existing playbook is already a legal child.\n */\n stepOutputs: z.array(MetaWorkflow_StepOutputContractSchema).default([]),\n method: z.object({\n guidance: z.string().min(1),\n skillRefs: z.array(z.string().min(1)).default([]),\n /**\n * The skills whose FULL BODY this method needs in its brief, not just their purpose line.\n *\n * A SUBSET of `skillRefs`, checked by `wildo fwk audit` — naming a skill the method does not\n * declare would put a contract in the brief the guidance never tells the model to follow.\n *\n * Why a second declaration rather than \"render every named skill's body\": the catalog does not\n * fit. Measured 2026-09-22, `top_down.market-snapshot-produce` names SIXTEEN skills and one of\n * them (`market-companion-prompt-enrichment`) is 133KB on its own, so rendering bodies for\n * every named skill would put hundreds of kilobytes into a brief for playbooks that need none\n * of it. The two that genuinely need one — a logo lockup's field contract, a governed\n * document's authoring contract — need ONE each, and say so in their own guidance.\n *\n * So the bound is an AUTHORING decision rather than a lucky total, which is the same shape as\n * `inputs[].aspects`: the method names what it reads, and the runtime resolves exactly that\n * before composition (#251). Empty by default, and that default is the honest one — a body\n * costs tokens on every run and pays only where the guidance says \"follow this skill\".\n *\n * The BODY only. `references/`, `examples/` and `scripts/` stay the on-demand tier a CODING\n * agent opens; a structured generation can open nothing, so inlining them would carry material\n * nobody asked for.\n */\n skillBodyRefs: z.array(z.string().min(1)).default([]),\n elicitation: MetaWorkflow_ElicitationSpecSchema.optional(),\n /**\n * Derived context sections this playbook's brief carries beyond its declared `inputs[]`.\n *\n * Empty by default, and that default is the honest one: a section costs tokens on every run and\n * pays only where the method routes through it.\n */\n contextSources: z.array(z.enum(MetaWorkflow_ContextSource)).default([]),\n /**\n * The governed documents this playbook may DRAFT, as `document-definition:` refs.\n *\n * Meaningless without `MetaWorkflow_ContextSource.DOCUMENT_BLUEPRINT`: it is that source's\n * parameter — which blueprints the brief carries, and therefore which documents the lane may\n * produce. Empty by default, so a playbook that drafts no document declares nothing.\n *\n * **It exists because a drafting lane is defined by its DOCUMENTS, and that was a runtime\n * constant.** The companion held one frozen list, and its own comment said the refs came \"from\n * the playbook's own declaration rather than from a parameter\" — which was the right design and\n * not what the code did. The cost was that a SECOND drafting lane could not exist without editing\n * the companion, and the four internal governance documents therefore had no lane at all (#1453):\n * widening the one list was the only move available, and it would have put all six blueprints in\n * every drafting prompt. Measured 2026-09-22: 21KB for the public pair, 24KB for the governance\n * four, 45KB together — and a prompt section that gets skimmed is indistinguishable from an\n * absent one, which is the same argument that kept the governance documents out in the first\n * place. Declared per playbook, each lane carries only its own.\n *\n * Same shape and same reason as `briefAdequacyExcludedSources`: an authored boundary a prose\n * comment cannot enforce, because unknown keys are stripped at parse and a runtime reads only\n * what the schema admits.\n *\n * A ref naming no blueprint in the engine catalog renders nothing, so the set a lane can draft\n * would silently shrink. `playbook-catalog-document-declarations.test.ts` resolves every declared\n * ref against the catalog, which is where a typo is caught rather than at the next run.\n */\n draftableDocumentDefinitionRefs: z.array(z.string().min(1)).default([]),\n /**\n * Present exactly when this playbook orchestrates children rather than producing an artifact.\n *\n * A composite declares no `outputs` of its own — what commits is what its children land.\n */\n choreography: MetaWorkflow_ChoreographySchema.optional(),\n /**\n * May this playbook SUSPEND mid-run and ask the creator a question it cannot answer from its\n * inputs?\n *\n * Opt-in rather than global, because the channel costs one small model call per output and only\n * pays where a derivation faces a decision a product owner owns rather than one the artifacts\n * determine. A playbook that suspends returns a resumable checkpoint instead of a landed file;\n * the creator answers accept / decline / cancel, and `decline` has the derivation choose and\n * state its assumption rather than stalling.\n */\n suspendsForClarification: z.boolean().default(false),\n /**\n * May this playbook's composed brief be JUDGED for sufficiency before generation, with ONE\n * monotonic repair pass on an INSUFFICIENT verdict?\n *\n * #254's rescoped shape (decision 2026-09-02, built 2026-09-04): a tool-free structured judge\n * reads the composed brief and the closed list of UNDECLARED context sources; `insufficient`\n * adds the proposed sources to the declaration FOR THIS RUN ONLY — add-only, never removing or\n * softening a declared source — and the brief recomposes once. The gate never runs twice, and a\n * gate fault fails OPEN to the static brief: an auxiliary judgment must never withhold a run.\n *\n * Opt-in per playbook, exactly like `suspendsForClarification`, because the gate costs one\n * model call per run and pays only where context needs genuinely vary per application — the\n * document lane, per the recorded pilot decision.\n */\n briefAdequacyGate: z.boolean().default(false),\n /**\n * Sources the gate may NEVER propose, carrying an authored boundary into the mechanism.\n *\n * Monotonic is not the same as safe: an ADD can still violate a deliberate exclusion — the\n * document drafter's own `//contextSources` reason forbids `compliance_primary_facts` because a\n * drafter given raw mechanism could write a clause resting on something the application never\n * DECLARED. A prose reason is invisible to the runtime (unknown keys are stripped at parse);\n * this field is the same decision, enforceable. Meaningless without `briefAdequacyGate`.\n */\n briefAdequacyExcludedSources: z.array(z.enum(MetaWorkflow_ContextSource)).default([]),\n /**\n * Present exactly when this playbook's artifact is DELIBERATED rather than\n * generated in one pass — an expert panel argues over several candidates and a\n * coordinator converges.\n *\n * **This is a substitution at the generation port, not a different executor.**\n * The host produces `candidateCount` candidates through its ordinary structured\n * generation (each already schema-constrained), runs the panel over them as\n * STRUCTURED deliberation candidates, and returns the winner. Everything\n * downstream — validation, findings-fed retry, rendering, landing, the judge —\n * is untouched, because what changes is only how the value was ARRIVED AT.\n *\n * Declaring a `DELIBERATION_PANEL` executor member was the obvious alternative\n * and is wrong: `runPlaybook` never branches on `executor` (only choreography\n * children do), so the member would name a capability nothing dispatches — the\n * declared-but-unrunnable shape this codebase has already paid for once with\n * `build-plan`.\n *\n * Costly by construction — `candidateCount` generations plus a rubric pass plus\n * reviewers × candidates per round plus synthesis — so it belongs only where the\n * decision genuinely has several defensible answers and the creator should not\n * have to pick between them. A derivation the artifacts determine does not need\n * a panel.\n *\n * FAIL-CLOSED on charters: every named role needs a committed charter and the\n * companion indexes agents at startup, so a role accepted after boot has no agent\n * until restart. The panel says exactly that rather than silently degrading to a\n * single pass — a deliberation that quietly became one generation would be the\n * worst outcome, since the artifact would carry a rationale nobody argued over.\n */\n deliberation: MetaWorkflow_PlaybookDeliberationSchema.optional(),\n }),\n /**\n * Which tier runs this playbook's step — OPTIONAL since 2026-08-29 (#115), and the option is the\n * point: a playbook that runs no single step has no truthful value to give. `top_down.market-analysis`\n * composes children and executes nothing itself; `bottom_up.foundation` is a bespoke deterministic\n * executor the host dispatches by ref. Both declared the removed `COMPOSITE` to fill a required\n * field, which is how that member became a catch-all. Absent means \"not one tier\" — read\n * `method.choreography`, or the host's own dispatch, for what actually runs it.\n */\n executor: z.enum(MetaWorkflow_Executor).optional(),\n /*\n * There is deliberately NO `executorPersona`. Declared until 2026-09-08 (#488): authored by 0 of\n * 26 playbooks, not copied into the compiled registry entry, read by no runtime.\n *\n * Note it is NOT `executor`, the live field directly above — the two differ by a word, and a\n * symbol search for the persona enum it referenced looked busy because a blueprint prompt library\n * used that enum heavily and unrelatedly. That resemblance is why it survived: everything about\n * it looked used.\n *\n * Both are gone now. The enum (`AppsBlueprint_AgentPersonas`) and the prompt library were deleted\n * on 2026-09-19 — the library turned out to be commented out and unreachable — so the closed\n * persona vocabulary no longer exists anywhere. A persona is an open `z.string()` on the engine's\n * `FlowsActors_Agent_PromptSpec`, which is what it always should have been.\n */\n /*\n * There is deliberately NO `qualityGates` here. The field existed from the catalog's first day\n * until 2026-08-29 (issue #103): 20 playbooks declared it, 13 with a `validatorRef`, and NO\n * RUNTIME EVER EXECUTED ONE — `validatorRef` was a bare `z.string()` with no resolver anywhere.\n *\n * It was deleted rather than wired because every gate it declared was ALREADY delivered, by a\n * mechanism that runs:\n *\n * - 10 named their own family's `_core` validator, which the semantic authority's per-family\n * `runValidator` runs at landing and the `definition-specifications` behavior runs fail-closed\n * at load. Executing the gate would have bought a second identical call.\n * - 2 named `typecheck`, which `resolveBuildPlanTaskCodingPolicy` runs through\n * `APPLICATION_CODING_TASK_VERIFICATION_CATALOG`, outside the coding agent, in the package the\n * task mutated.\n * - 1 (`capability-map-output-set-valid`) named the one genuinely cross-family check — a market\n * benefit's `deliveredByFeatureRefs` resolving against the drafted features. A per-family\n * validator structurally cannot see a sibling family, so that check belongs to\n * `buildApplicationCoherenceReport`, which reports it as `benefit-delivered-by-unknown-feature`\n * into `src/COHERENCE.md` and into the phase gate's context.\n *\n * Each playbook's `method.md` still carries its `## Quality gate` section, and that prose is the\n * accurate one: it describes the validator the LANDING PATH runs. Do not reintroduce a declared\n * gate to restate it — a second description of a live check is what this field was.\n */\n /**\n * ## KEPT DELIBERATELY, AND NOT ENFORCED YET (#488, decided 2026-09-08)\n *\n * These three — the approval policy, the budget ceilings and the failure policy — are authored by\n * playbook definitions and read by NO runtime. Their intended enforcer was the PlaybookRunner,\n * deleted at the first-activation hard cut.\n *\n * They were kept while `executorPersona`, `functionalTopics` and the depth ceiling were deleted in\n * the same pass, and the distinction is the point: those were dead CLASSIFICATION — a label nothing\n * would ever branch on. These are a governance CAPABILITY that is merely early. A playbook declaring\n * that its result must be approved is stating something the lane will need the day it runs\n * unattended against anything that matters.\n *\n * **So do not read them as enforced, and do not delete them as unused.** The enforcer is built when\n * the lane needs governance, and building it is not a wiring job: it creates a new REFUSAL and a new\n * PERMISSION BOUNDARY — who may run unattended, and on what evidence a run is cut — which is a\n * decision rather than an implementation.\n *\n * The autonomy PRESET at journey level belongs with this block for the same reason, not with the\n * classification axes that went.\n */\n approval: z.enum(MetaWorkflow_ApprovalPolicy),\n budget: MetaWorkflow_PlaybookBudgetSchema,\n onFailure: z.enum(MetaWorkflow_FailurePolicy),\n}).superRefine((playbook, context) => {\n /*\n * An `artifact_decides` gate names a decision its family DECLARES, and one member of that decision's\n * vocabulary (#1606). Refused here, where the generator parses every playbook, because a misspelt\n * decision or value would otherwise make the playbook ineligible forever and report nothing.\n */\n playbook.preconditions.forEach((predicate, index) => {\n if (predicate.kind !== MetaWorkflow_PredicateKind.ARTIFACT_DECIDES) return;\n const decision = getApplicationSpecificationFamilyDecision(predicate.selector.family, predicate.decision);\n if (decision === undefined) {\n context.addIssue({\n code: \"custom\",\n path: [\"preconditions\", index, \"decision\"],\n message: `\"${predicate.selector.family}\" declares no decision \"${predicate.decision}\" (APPLICATION_SPECIFICATION_FAMILY_DECISIONS).`,\n });\n return;\n }\n if (!decision.vocabulary.includes(predicate.equals)) {\n context.addIssue({\n code: \"custom\",\n path: [\"preconditions\", index, \"equals\"],\n message: `\"${predicate.equals}\" is not a value of \"${predicate.selector.family}\" decision \"${predicate.decision}\"; expected one of ${decision.vocabulary.join(\", \")}.`,\n });\n }\n });\n});\nexport type MetaWorkflowPlaybook = z.infer<typeof MetaWorkflowPlaybookSchema>;\n/**\n * Native playbooks are authored before schema defaults are materialized.\n * Keeping this input type distinct from `MetaWorkflowPlaybook` prevents every\n * defaulted field from becoming a meaningless required declaration while the\n * compiled/loaded contract remains the fully parsed output type.\n */\nexport type MetaWorkflowPlaybookAuthoring = z.input<typeof MetaWorkflowPlaybookSchema>;\n"]}
|
|
1
|
+
{"version":3,"file":"playbooks.application-creation.schemas.js","sourceRoot":"","sources":["../../../../src/application-creation/playbooks.application-creation.schemas.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAKxB,OAAO,EACL,2BAA2B,EAC3B,mCAAmC,EACnC,mCAAmC,EACnC,+BAA+B,EAC/B,kCAAkC,EAClC,qBAAqB,EACrB,0BAA0B,EAC1B,mCAAmC,EACnC,iCAAiC,EACjC,uCAAuC,EACvC,0BAA0B,EAC1B,qCAAqC,GACtC,MAAM,sCAAsC,CAAC;AAE9C,OAAO,EAAE,yCAAyC,EAAE,MAAM,2EAA2E,CAAC;AAEtI,iEAAiE;AACjE,2BAA2B;AAC3B,4BAA4B;AAC5B,sEAAsE;AACtE,4EAA4E;AAC5E,qEAAqE;AACrE,2EAA2E;AAC3E,0DAA0D;AAC1D,8DAA8D;AAC9D,2EAA2E;AAC3E,eAAe;AACf,sEAAsE;AACtE,EAAE;AACF,mEAAmE;AACnE,kEAAkE;AAClE,2FAA2F;AAC3F,+FAA+F;AAC/F,sFAAsF;AACtF,EAAE;AACF,iGAAiG;AACjG,kGAAkG;AAClG,iGAAiG;AACjG,0DAA0D;AAC1D,EAAE;AACF,8EAA8E;AAC9E,qEAAqE;AACrE,uEAAuE;AACvE,4EAA4E;AAC5E,0EAA0E;AAC1E,8EAA8E;AAC9E,2EAA2E;AAC3E,yEAAyE;AACzE,0EAA0E;AAC1E,+EAA+E;AAC/E,EAAE;AACF,8EAA8E;AAC9E,8EAA8E;AAC9E,+EAA+E;AAC/E,yEAAyE;AACzE,yEAAyE;AACzE,iEAAiE;AACjE,EAAE;AACF,yEAAyE;AACzE,yEAAyE;AACzE,qEAAqE;AACrE,mEAAmE;AACnE,wBAAwB;AACxB,iEAAiE;AAGjE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqCG;AACH,MAAM,CAAN,IAAY,kBASX;AATD,WAAY,kBAAkB;IAC5B,0GAA0G;IAC1G,2CAAqB,CAAA;IACrB,2FAA2F;IAC3F,6CAAuB,CAAA;IACvB,oFAAoF;IACpF,+CAAyB,CAAA;IACzB,gDAAgD;IAChD,qDAA+B,CAAA;AACjC,CAAC,EATW,kBAAkB,KAAlB,kBAAkB,QAS7B;AAGD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAoCG;AACH,MAAM,CAAN,IAAY,4BAQX;AARD,WAAY,4BAA4B;IACtC,qGAAqE,CAAA;IACrE,yEAAyC,CAAA;IACzC,6FAA6D,CAAA;IAC7D,+EAA+C,CAAA;IAC/C,yEAAyC,CAAA;IACzC,uHAAuF,CAAA;IACvF,2FAA2D,CAAA;AAC7D,CAAC,EARW,4BAA4B,KAA5B,4BAA4B,QAQvC;AAED;;;;;;;;;;;;;;;;;GAiBG;AAEH;;;;;;;GAOG;AACH,MAAM,CAAN,IAAY,+BAGX;AAHD,WAAY,+BAA+B;IACzC,8CAAW,CAAA;IACX,4CAAS,CAAA;AACX,CAAC,EAHW,+BAA+B,KAA/B,+BAA+B,QAG1C;AAED;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,MAAM,UAAU,yBAAyB,CAAC,SAAiB;IACzD,kGAAkG;IAClG,MAAM,UAAU,GAAG,SAAS,CAAC,IAAI,EAAE,CAAC,WAAW,EAAE,CAAC,OAAO,CAAC,SAAS,EAAE,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC;IAChF,IAAI,qCAAqC,CAAC,GAAG,CAAC,UAAU,CAAC;QAAE,OAAO,+BAA+B,CAAC,GAAG,CAAC;IACtG,IAAI,kCAAkC,CAAC,GAAG,CAAC,UAAU,CAAC;QAAE,OAAO,+BAA+B,CAAC,EAAE,CAAC;IAClG,OAAO,IAAI,CAAC;AACd,CAAC;AAED,yHAAyH;AACzH,MAAM,qCAAqC,GAAwB,IAAI,GAAG,CAAC,CAAC,KAAK,EAAE,GAAG,EAAE,MAAM,CAAC,CAAC,CAAC;AACjG,gCAAgC;AAChC,MAAM,kCAAkC,GAAwB,IAAI,GAAG,CAAC,CAAC,IAAI,EAAE,GAAG,EAAE,OAAO,CAAC,CAAC,CAAC;AAE9F,yGAAyG;AACzG,MAAM,CAAC,MAAM,kCAAkC,GAAsB,MAAM,CAAC,MAAM,CAAC;IACjF,GAAG,qCAAqC;IACxC,GAAG,kCAAkC;CACtC,CAAC,CAAC;AAEH;;;;GAIG;AACH;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,CAAN,IAAY,0BAgNX;AAhND,WAAY,0BAA0B;IACpC;;;;;OAKG;IACH,iEAAmC,CAAA;IACnC;;;;;;;;;OASG;IACH,6DAA+B,CAAA;IAC/B;;;;;;;;OAQG;IACH,mEAAqC,CAAA;IACrC;;;;;;;;;;;;;;;;;;;OAmBG;IACH,mFAAqD,CAAA;IACrD;;;;;;;;;;;;;;;;;OAiBG;IACH,uEAAyC,CAAA;IACzC;;;;;;;;;;;;;;;;;OAiBG;IACH,qFAAuD,CAAA;IACvD;;;;;;;OAOG;IACH,yFAA2D,CAAA;IAC3D;;;;;;;;;;;;;;;;;;OAkBG;IACH,+EAAiD,CAAA;IACjD;;;;;;;;;;;;;;;;;;;;OAoBG;IACH,uEAAyC,CAAA;IACzC;;;;;;;;;;;;;;;;;;;;;;OAsBG;IACH,iFAAmD,CAAA;IACnD;;;;;;;;;;;;;;;;;;;;;;OAsBG;IACH,qEAAuC,CAAA;IACvC;;;;;;;;;;;;;;;;;;;OAmBG;IACH,2DAA6B,CAAA;AAC/B,CAAC,EAhNW,0BAA0B,KAA1B,0BAA0B,QAgNrC;AAED;;;;GAIG;AACH,MAAM,CAAN,IAAY,wBAQX;AARD,WAAY,wBAAwB;IAClC,2GAA2G;IAC3G,yCAAa,CAAA;IACb;;;OAGG;IACH,uCAAW,CAAA;AACb,CAAC,EARW,wBAAwB,KAAxB,wBAAwB,QAQnC;AAED;;;;GAIG;AACH,MAAM,CAAC,MAAM,qCAAqC,GAAG,CAAC,CAAC;AAEvD,+EAA+E;AAC/E,MAAM,CAAC,MAAM,+BAA+B,GAAG,CAAC,CAAC,YAAY,CAAC;IAC5D;;;OAGG;IACH,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,qCAAqC,CAAC,CAAC,OAAO,CAAC,CAAC,CAAC;IACnF,6FAA6F;IAC7F,aAAa,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,QAAQ,EAAE;CAC5D,CAAC,CAAC;AAGH;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AACH,MAAM,CAAC,MAAM,+BAA+B,GAAG,mCAAmC,CAAC,MAAM,CAAC;IACxF;;;OAGG;IACH,OAAO,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,QAAQ,EAAE;IACrD,sDAAsD;IACtD,MAAM,EAAE,CAAC,CAAC,IAAI,CAAC,wBAAwB,CAAC,CAAC,QAAQ,EAAE;IACnD,OAAO,EAAE,+BAA+B,CAAC,QAAQ,EAAE;CACpD,CAAC,CAAC,WAAW,CAAC,CAAC,KAAK,EAAE,OAAO,EAAE,EAAE;IAChC,IAAI,KAAK,CAAC,OAAO,KAAK,SAAS,IAAI,KAAK,CAAC,MAAM,KAAK,SAAS,EAAE,CAAC;QAC9D,OAAO,CAAC,QAAQ,CAAC;YACf,IAAI,EAAE,QAAQ;YACd,IAAI,EAAE,CAAC,SAAS,CAAC;YACjB,OAAO,EAAE,UAAU,KAAK,CAAC,MAAM,0IAA0I;SAC1K,CAAC,CAAC;IACL,CAAC;AACH,CAAC,CAAC,CAAC;AAGH;;;;;;;;;;;;;;GAcG;AACH,MAAM,CAAC,MAAM,gCAAgC,GAAG,mCAAmC,CAAC,MAAM,CAAC;IACzF,OAAO,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,QAAQ,EAAE;CACtD,CAAC,CAAC;AAGH,MAAM,CAAC,MAAM,0BAA0B,GAAG,CAAC,CAAC,MAAM,CAAC;IACjD,GAAG,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC;IACtB,OAAO,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC;IAC1B,KAAK,EAAE,CAAC,CAAC,IAAI,CAAC,kBAAkB,CAAC;IACjC,MAAM,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC;IACzB;;;;;;;;;;;OAWG;IACH,aAAa,EAAE,CAAC,CAAC,KAAK,CAAC,mCAAmC,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;IACvE,MAAM,EAAE,CAAC,CAAC,KAAK,CAAC,+BAA+B,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;IAC5D,OAAO,EAAE,CAAC,CAAC,KAAK,CAAC,gCAAgC,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;IAC9D;;;;;;OAMG;IACH,WAAW,EAAE,CAAC,CAAC,KAAK,CAAC,qCAAqC,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;IACvE,MAAM,EAAE,CAAC,CAAC,MAAM,CAAC;QACf,QAAQ,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC;QAC3B,SAAS,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;QACjD;;;;;;;;;;;;;;;;;;;;;WAqBG;QACH,aAAa,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;QACrD,WAAW,EAAE,kCAAkC,CAAC,QAAQ,EAAE;QAC1D;;;;;WAKG;QACH,cAAc,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,IAAI,CAAC,0BAA0B,CAAC,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;QACvE;;;;;;;;;;;;;;;;;;;;;;;;;WAyBG;QACH,+BAA+B,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;QACvE;;;;WAIG;QACH,YAAY,EAAE,+BAA+B,CAAC,QAAQ,EAAE;QACxD;;;;;;;;;WASG;QACH,wBAAwB,EAAE,CAAC,CAAC,OAAO,EAAE,CAAC,OAAO,CAAC,KAAK,CAAC;QACpD;;;;;;;;;;;;;WAaG;QACH,iBAAiB,EAAE,CAAC,CAAC,OAAO,EAAE,CAAC,OAAO,CAAC,KAAK,CAAC;QAC7C;;;;;;;;WAQG;QACH,4BAA4B,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,IAAI,CAAC,0BAA0B,CAAC,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;QACrF;;;;;;;;;;;;;;;;;;;;;;;;;;;;;WA6BG;QACH,YAAY,EAAE,uCAAuC,CAAC,QAAQ,EAAE;KACjE,CAAC;IACF;;;;;;;OAOG;IACH,QAAQ,EAAE,CAAC,CAAC,IAAI,CAAC,qBAAqB,CAAC,CAAC,QAAQ,EAAE;IAClD;;;;;;;;;;;;;OAaG;IACH;;;;;;;;;;;;;;;;;;;;;;;OAuBG;IACH;;;;;;;;;;;;;;;;;;;;OAoBG;IACH,QAAQ,EAAE,CAAC,CAAC,IAAI,CAAC,2BAA2B,CAAC;IAC7C,MAAM,EAAE,iCAAiC;IACzC,SAAS,EAAE,CAAC,CAAC,IAAI,CAAC,0BAA0B,CAAC;CAC9C,CAAC,CAAC,WAAW,CAAC,CAAC,QAAQ,EAAE,OAAO,EAAE,EAAE;IACnC;;;;OAIG;IACH,QAAQ,CAAC,aAAa,CAAC,OAAO,CAAC,CAAC,SAAS,EAAE,KAAK,EAAE,EAAE;QAClD,IAAI,SAAS,CAAC,IAAI,KAAK,0BAA0B,CAAC,gBAAgB;YAAE,OAAO;QAC3E,MAAM,QAAQ,GAAG,yCAAyC,CAAC,SAAS,CAAC,QAAQ,CAAC,MAAM,EAAE,SAAS,CAAC,QAAQ,CAAC,CAAC;QAC1G,IAAI,QAAQ,KAAK,SAAS,EAAE,CAAC;YAC3B,OAAO,CAAC,QAAQ,CAAC;gBACf,IAAI,EAAE,QAAQ;gBACd,IAAI,EAAE,CAAC,eAAe,EAAE,KAAK,EAAE,UAAU,CAAC;gBAC1C,OAAO,EAAE,IAAI,SAAS,CAAC,QAAQ,CAAC,MAAM,2BAA2B,SAAS,CAAC,QAAQ,iDAAiD;aACrI,CAAC,CAAC;YACH,OAAO;QACT,CAAC;QACD,IAAI,CAAC,QAAQ,CAAC,UAAU,CAAC,QAAQ,CAAC,SAAS,CAAC,MAAM,CAAC,EAAE,CAAC;YACpD,OAAO,CAAC,QAAQ,CAAC;gBACf,IAAI,EAAE,QAAQ;gBACd,IAAI,EAAE,CAAC,eAAe,EAAE,KAAK,EAAE,QAAQ,CAAC;gBACxC,OAAO,EAAE,IAAI,SAAS,CAAC,MAAM,wBAAwB,SAAS,CAAC,QAAQ,CAAC,MAAM,eAAe,SAAS,CAAC,QAAQ,sBAAsB,QAAQ,CAAC,UAAU,CAAC,IAAI,CAAC,IAAI,CAAC,GAAG;aACvK,CAAC,CAAC;QACL,CAAC;IACH,CAAC,CAAC,CAAC;AACL,CAAC,CAAC,CAAC","sourcesContent":["import { z } from \"zod\";\n\nimport {\n HumanDecision_FieldKind,\n} from \"@wildo-ai/saas-models\";\nimport {\n MetaWorkflow_ApprovalPolicy,\n MetaWorkflow_ArtifactContractSchema,\n MetaWorkflow_ArtifactSelectorSchema,\n MetaWorkflow_ChoreographySchema,\n MetaWorkflow_ElicitationSpecSchema,\n MetaWorkflow_Executor,\n MetaWorkflow_FailurePolicy,\n MetaWorkflow_JourneyPredicateSchema,\n MetaWorkflow_PlaybookBudgetSchema,\n MetaWorkflow_PlaybookDeliberationSchema,\n MetaWorkflow_PredicateKind,\n MetaWorkflow_StepOutputContractSchema,\n} from \"@wildo-ai/saas-models/meta-workflows\";\n\nimport { getApplicationSpecificationFamilyDecision } from \"./application-specification-family-decisions.application-creation.schemas\";\n\n//===============================================================\n// Meta-Workflow Playbooks\n// -------------------------\n// A playbook is the declarative, versioned definition of one coherent\n// piece of app-creation work (design plan `app-creation-meta-workflows.md`,\n// section D2). Playbooks are DATA, not code: they are authored under\n// `framework-knowledge/src/playbooks/` (folder-per-playbook: one canonical\n// structured source — contained `playbook.json` or native\n// `playbook.definition.ts` — plus `method.md`), compiled into\n// `dist/knowledge/playbooks/`, and loaded by the framework-knowledge seam.\n// Refining the\n// methodology of a step means editing a playbook — never engine code.\n//\n// A playbook is a STANDALONE root schema, deliberately NOT a third\n// `FlowActorSystem_Kind` (implementation-spec P-1): playbooks are\n// *definitions*, while playbook *runs* are — by contract (P-11) — `ActorSystem` executions\n// identified by the `systemRef: 'meta-workflows.<playbookRef>'` convention. Extending the kind\n// enum would ripple through every `kind` narrow in the engine for zero semantic gain.\n//\n// The run half of that sentence is an OBLIGATION rather than a description, and was written here\n// as fact until 2026-09-19: no playbook run creates an actor execution today (#1343). It does not\n// weaken the argument above — a playbook is a definition either way — but it must not be read as\n// evidence that the run plane is already the actor plane.\n//\n// The STRONGER reason, measured 2026-08-29 and recorded because the one above\n// is an ergonomic argument and will be reopened on its own weakness:\n// `FlowActorSystem_Base` is dominated by RUNTIME AND LIFECYCLE state —\n// `createdAt` / `updatedAt` / `deletedAt` / `deprecatedAt` / `publishedAt`,\n// `circuitBreakerStatus`, `errorItems`, `checkpoint`, `checkpointChecks`,\n// `timestamp`. A playbook has none of that and must not: playbooks are FILES,\n// accepted by being committed, and git owns their history, publication and\n// deprecation (`.claude/rules/one-source-of-truth.md`, Rule 0). Making a\n// playbook a third kind would inherit a durable lifecycle and state model\n// THROUGH THE BASE — re-importing by inheritance the ledger Rule 0 demolished.\n//\n// The actors/flows distinction is real and is already expressed correctly, in\n// two relations that are producer -> artifact and never is-a: a playbook is a\n// DEFINITION; its RUN is an `ActorSystem` execution; and a fully deterministic\n// playbook may COMPILE into a `FlowSystem` when that engine exists. So a\n// playbook never declares which kind it \"is\" — asking it to would be the\n// second authority this contract stays engine-agnostic to avoid.\n//\n// Rejected alternative: authoring playbooks as flows-actors `FlowSystem`\n// step graphs — the step-graph engine is deferred and choreographic work\n// is agentic/plan-driven, not a static step DAG. Fully deterministic\n// playbooks may later COMPILE into FlowSystems; the contract stays\n// engine-agnostic here.\n//===============================================================\n\n\n/**\n * The KIND OF REASONING a playbook embodies — a taxonomy label on the playbook, and nothing else.\n *\n * ## What this is NOT, since 2026-09-04\n *\n * It is not a state an application can be in. There was a `deriveJourneyPhase` that computed one —\n * `bottom_up` the moment `domain-plan` or `build-plan` had content, monotonic and irreversible — and\n * 19 playbooks gated on matching it. It has been deleted, along with the `PHASE_IS` predicate, and\n * neither should come back.\n *\n * The reason is recorded in `.claude/context/app-creation-composite-choreography.md` §13: **an\n * evolving application is not in a phase; it is in a STATE, and the state is the tree.** Top-down and\n * bottom-up are ways of APPROACHING a problem. An application holds artifacts produced by both, all\n * of them still valid inputs, and moving between the modes is ordinary product work. What legitimately\n * constrains what may run is DEPENDENCY, and the ARTIFACT preconditions express that exactly.\n *\n * The derived phase failed in three separate ways at once, all measured before it went:\n *\n * - on the `bottom_up` side it was **provably redundant** — every playbook gated on it already\n * required `domain-plan` or `build-plan`, the two families that DEFINED the phase, so it could\n * refuse nothing readiness had not already refused;\n * - it contained a **deadlock**: `bottom_up.domain-plan` gated on `bottom_up` and PRODUCED the family\n * that creates it, so the unattended loop could never enter that phase at all;\n * - on the `top_down` side it blocked **return**, not incoherence — after a domain plan landed, the\n * loop could never revisit market analysis or requirements, whose real inputs were still valid.\n *\n * Three patches preserved it before it was removed: reclassifying `PHASE_IS` as SEQUENCING so humans\n * could bypass it, removing the gate from one playbook (#116), and threading a\n * `proceedPastSequencing` flag through the choreography so a composite's children inherited the\n * parent's bypass. Each moved the pain to the next caller.\n *\n * ## What it still does\n *\n * It labels a playbook, which is true and useful: it says what kind of thinking that playbook\n * embodies, and it groups the catalog for whoever reads it. Nothing gates on it, so every member is\n * equally usable — {@link MetaWorkflow_Phase.REFINEMENT} and {@link MetaWorkflow_Phase.CROSS_CUTTING}\n * were \"unreachable\" only because a gate demanded a derivation that could not produce them.\n */\nexport enum MetaWorkflow_Phase {\n /** Reasoning from intent down to structure: vision, market, requirements, roadmap, compliance posture. */\n TOP_DOWN = \"top_down\",\n /** Reasoning from structure up: the domain model, the build plan, placement, execution. */\n BOTTOM_UP = \"bottom_up\",\n /** Revisiting a produced artifact against what the application has since become. */\n REFINEMENT = \"refinement\",\n /** Work that belongs to no single direction. */\n CROSS_CUTTING = \"cross_cutting\",\n}\n\n\n/**\n * The seven functional topics of the canonical app-development workflow taxonomy — a **BUILD**\n * taxonomy, in build order: configure the foundation, model the domain, define interaction, shape\n * the experience, extend, connect runtime and external capabilities, assemble and verify.\n *\n * ## What reads this, measured 2026-08-30\n *\n * | Surface | Status |\n * |---|---|\n * | `BuildPlanTask.functionalTopic` | **LIVE** — stamped into the coding-agent dispatch payload as context the agent reads |\n * | `MetaWorkflowPlaybook.functionalTopics` | **REMOVED 2026-09-08 (#488)** — authored intent the compiler copied into the compiled catalog and no runtime read |\n * | `MetaWorkflow_PredicateKind.TOPIC_COMPLETE` | **GONE (2026-09-05)** — it was a real precondition kind whose evaluator always returned `satisfied: false`, because topic completion was a journey-record fact and nothing derives it from the working tree. Zero playbooks ever gated on it |\n *\n * So a topic reaches exactly one decision anywhere: none. Build-task ordering is\n * `prerequisiteTaskRefs` alone, and playbook eligibility is `preconditions` — where the one kind\n * keyed on a topic could never be satisfied, so any playbook declaring it would have been permanently\n * ineligible with nothing reporting it. It followed `PHASE_IS` out on 2026-09-05 for exactly that\n * reason: both gated on a derived global state that nothing derives (see {@link MetaWorkflow_Phase}).\n *\n * The vocabulary itself stays, because `BuildPlanTask.functionalTopic` is live. What went is the idea\n * that a topic could grant PERMISSION. If completion ever becomes derivable from the working tree,\n * it belongs as an artifact-shaped precondition or as a runtime-synthesized verdict — not as a new\n * global state a playbook can demand.\n *\n * ## The claim this replaced\n *\n * This JSDoc said \"Completeness tracking and playbook routing key on these functional nodes\". Both\n * halves were false and had been since the enum was typed: there is no completeness tracking, and\n * routing is `preconditions`. The cost was not a wrong result — it was that the sentence read as a\n * mechanism, so decisions were argued from it. One session declined to author a dedicated playbook\n * partly on the strength of a \"frozen taxonomy\" that no checker enforced and whose cited authority\n * (`fwk-ai-assisted-development-workflow-model.md`) lives in gitignored `.claude/plans/` and does\n * not survive a re-clone. See issue #124 and `.claude/rules/capability-catalog-integration.md`.\n *\n * The enum is the reachable source. Prefer an existing topic; adding one is a deliberate decision,\n * not a prohibition — but note that nothing downstream will react to it.\n */\nexport enum MetaWorkflow_FunctionalTopic {\n CONFIGURE_APPLICATION_FOUNDATION = \"configure_application_foundation\",\n MODEL_DOMAIN_GRAPH = \"model_domain_graph\",\n DEFINE_INTERACTION_SEMANTICS = \"define_interaction_semantics\",\n SHAPE_USER_EXPERIENCE = \"shape_user_experience\",\n EXTEND_APPLICATION = \"extend_application\",\n CONNECT_RUNTIME_AND_EXTERNAL_CAPABILITIES = \"connect_runtime_and_external_capabilities\",\n ASSEMBLE_VERIFY_AND_ITERATE = \"assemble_verify_and_iterate\",\n}\n\n/*\n * `MetaWorkflow_ElicitationQuestionKind` stood here until 2026-09-19 (#1342). It was collapsed onto\n * {@link HumanDecision_FieldKind} on 2026-09-17 and kept as an ALIAS — `export const X: typeof\n * HumanDecision_FieldKind = HumanDecision_FieldKind` — on the reasoning that \"the name stays because\n * every playbook definition and every consumer spells it this way, and the creation layer is where\n * the reader expects to find it.\"\n *\n * That reasoning described the consumers rather than the vocabulary, and the alias was doing real\n * harm: the companion imported the app-creation name specifically to dodge a `TS2742` it hit when\n * naming the engine enum, which is an alias telling you it is the wrong door. A second name for an\n * engine type is also exactly what \"closed vocabularies have ONE named runtime source\" forbids —\n * the rule the collapse itself was invoking.\n *\n * Every consumer now spells {@link HumanDecision_FieldKind} and imports it from `@wildo-ai/saas-models`,\n * which is where the vocabulary always lived. What stays on this side is the CONFIRM-answer\n * resolution below: `saas-models` validates a CONFIRM only as non-empty, and deciding what a\n * creator's free text means is a creation-layer concern.\n */\n\n/**\n * What a {@link HumanDecision_FieldKind.CONFIRM} answer means once resolved.\n *\n * A closed vocabulary with a named source, because the answer DECIDES things: the five CONFIRM\n * questions in `top_down.vision-elicitation` screen for regulated domains — children's data,\n * financial services, healthcare, legal/compliance, public sector — and their answers become the\n * application's declared compliance posture.\n */\nexport enum MetaWorkflow_ConfirmationAnswer {\n YES = \"yes\",\n NO = \"no\",\n}\n\n/**\n * Resolve a creator's free-text answer to a CONFIRM question, or `null` when it is not unambiguous.\n *\n * ## Why this is not a string comparison, and not a prefix match either\n *\n * Until 2026-08-29 nothing validated a CONFIRM answer at all: only CHOICE was branched on, so any\n * non-empty string was accepted and \"probably\" or \"not sure\" flowed into the vision brief as the\n * source of truth for a compliance decision (issue #117).\n *\n * The obvious fix — compare against `\"yes\"`/`\"no\"` exactly — was rejected on MEASURED evidence: the\n * real recorded answers in this repository are `\"No.\"`, capitalised and punctuated. A guard that\n * refuses what creators actually type is a guard with no way past\n * (`.claude/rules/design-philosophy.md`).\n *\n * A PREFIX match was rejected as worse than either. `\"No, but we may later\"` starts with `no` and\n * would resolve to NO, silently discarding the caveat — on a question about whether an application\n * processes children's data. So the WHOLE normalised answer must be a recognised token; anything\n * else returns `null` and the caller refuses, naming the accepted forms.\n *\n * Refusing nuance costs the creator nothing here: the same interview pairs those five questions with\n * a free-text `compliance-detail` question, which is where \"no, but we may later\" belongs and where\n * it survives as prose instead of collapsing into a boolean.\n */\nexport function resolveConfirmationAnswer(rawAnswer: string): MetaWorkflow_ConfirmationAnswer | null {\n // Trailing punctuation and case are presentation, not meaning: `\"No.\"` and `\"no\"` are one answer.\n const normalized = rawAnswer.trim().toLowerCase().replace(/[.!]+$/u, \"\").trim();\n if (CONFIRMATION_ANSWER_AFFIRMATIVE_FORMS.has(normalized)) return MetaWorkflow_ConfirmationAnswer.YES;\n if (CONFIRMATION_ANSWER_NEGATIVE_FORMS.has(normalized)) return MetaWorkflow_ConfirmationAnswer.NO;\n return null;\n}\n\n/** Accepted spellings of YES. Deliberately short and closed — a long list is a prefix match wearing a set's clothing. */\nconst CONFIRMATION_ANSWER_AFFIRMATIVE_FORMS: ReadonlySet<string> = new Set([\"yes\", \"y\", \"true\"]);\n/** Accepted spellings of NO. */\nconst CONFIRMATION_ANSWER_NEGATIVE_FORMS: ReadonlySet<string> = new Set([\"no\", \"n\", \"false\"]);\n\n/** The forms a refusal message should name, so the creator is told what to type rather than guessing. */\nexport const CONFIRMATION_ANSWER_ACCEPTED_FORMS: readonly string[] = Object.freeze([\n ...CONFIRMATION_ANSWER_AFFIRMATIVE_FORMS,\n ...CONFIRMATION_ANSWER_NEGATIVE_FORMS,\n]);\n\n/**\n * Structured questions a HUMAN-executed (or elicitation-bearing) playbook\n * asks the creator. Kept lean in v1 — the method guidance prose carries the\n * interviewing style; this only types the answers' shape.\n */\n/**\n * Derived context a playbook's brief carries BEYOND its declared `inputs[]`.\n *\n * `inputs[]` says which artifact FAMILIES a playbook reads. These are the other sections a brief can\n * carry: facts the runtime computes rather than reads, and catalogs it renders. They are declared\n * because they cost real tokens and only pay for the playbooks whose method actually routes through\n * them — a brief that carries everything for everyone is how a prompt stops fitting.\n *\n * ## Why this is an enum and not a set of booleans\n *\n * It is a closed vocabulary with per-member meaning, which is the case\n * `CLAUDE.md` reserves an enum for: each member needs somewhere to explain what the section IS and\n * when a playbook should ask for it, and a bare `carriesSkillCatalog: true` has nowhere to put that.\n *\n * ## History\n *\n * Each of these was a frozen `readonly string[]` of playbook refs inside the dev companion's run\n * service — a list naming which playbooks got which section. That is the shape the composite work\n * exists to end: a capability reachable only by editing the runtime that dispatches it. The brief\n * already composed its `inputs` and `elicitation` sections FROM DECLARATIONS, so three of its five\n * sections were declared and three were hardcoded; this makes all of them declared.\n */\nexport enum MetaWorkflow_ContextSource {\n /**\n * Real module ids and per-resource present schema fields, read from the application's CODE.\n *\n * For playbooks that plan against what EXISTS rather than against definition artifacts. Without it\n * a planner invents module ids that do not resolve, and every task it emits fails at dispatch.\n */\n WORKSPACE_TRUTH = 'workspace_truth',\n /**\n * The full application-knowledge skill catalog (`skills/INDEX.md`), not just this playbook's own\n * `method.skillRefs`.\n *\n * Only for a method that ROUTES THROUGH the catalog — one that must bind its output to a skill it\n * chooses. Measured 2026-08-27: the one playbook of that shape was choosing from recall because\n * the catalog never reached its brief, and a dangling skill ref is a task the dispatch playbook\n * cannot run. Every other playbook still gets its own `skillRefs` rendered; this is ~25KB and pays\n * only where the choosing happens.\n */\n SKILL_CATALOG = 'skill_catalog',\n /**\n * The DERIVED cross-family coherence report — dangling references and coverage, computed exactly\n * by set operations over the landed families.\n *\n * For a playbook that ASSESSES coherence. Asking a model to re-derive it from five documents is\n * asking it to do worse, slower, what a function already did; the arithmetic goes in so the model\n * can judge what arithmetic cannot — whether an uncovered item is a deliberate deferral or an\n * omission.\n */\n COHERENCE_REPORT = 'coherence_report',\n /**\n * The application's compliance-relevant resource DECLARATIONS, read from its resource\n * configurations and split by origin (engine-declared vs application-declared).\n *\n * For a playbook that must state what the application actually does to a row — erasure retention\n * mode, data-subject kind, subject export, the audited see-through path — rather than what a\n * specification says it is for. A specification carries PURPOSE; a resource configuration carries\n * MECHANISM, and a governed document may only assert the second from the second.\n *\n * Added 2026-08-29, and the gap it closes is the shape this lane keeps producing.\n * `refinement.document-facts` had said in its intent and throughout its method that mechanism facts\n * \"are read from the resource configurations\" since the day it was authored, and nothing read them:\n * (spec-cite: N/A — that phrase is this repository's OWN playbook prose, `refinement.document-facts`'s\n * intent and method, quoted because the runtime did not honour it; it is not attributed to and does\n * not come from any external standard.)\n * the `compliance-primary-facts` introspection behavior existed, was tested, answered correctly over\n * HTTP — and had NO CONSUMER. Its first live production run landed two facts, both paraphrased from\n * prose, neither citing a declaration. A method that describes a derivation the runtime cannot\n * perform is not guidance, it is a claim the output will quietly fail to honour.\n */\n COMPLIANCE_PRIMARY_FACTS = 'compliance_primary_facts',\n /**\n * The engine catalog's DEFINITION and BLUEPRINT for the governed documents a lane may draft: which\n * sections a notice must contain, in what order, which facts each requires, and the typed questions\n * behind them.\n *\n * For a playbook that DRAFTS a governed document. It is the structure half of the same split\n * `COMPLIANCE_PRIMARY_FACTS` makes on the content half — the facts source says what the application\n * does, this says what the document is obliged to address, and a drafter needs both to write a\n * clause that is true AND required.\n *\n * Added 2026-08-30 against a measurement, not a hunch. `document-definition:public.privacy-notice`\n * requires eight facts; wonder-crm's generated notice declared twenty and matched NONE of them,\n * scoring zero dangling citations the whole time — internally consistent, and addressing none of\n * what a privacy notice must address. The catalog had held the answer since it was written and had\n * no runtime lookup of any kind: the only `(definitionRef) → blueprint` resolution in the repository\n * lived inside a schema test. Meanwhile the shipped authoring skill instructed the drafter to \"Read\n * the definition and blueprint\", a step it was told to perform and given nothing to perform it on.\n */\n DOCUMENT_BLUEPRINT = 'document_blueprint',\n /**\n * The exact fact NAMES the engine catalog's documents require, with the question each answers.\n *\n * For the playbook that DECLARES facts, and deliberately separate from `DOCUMENT_BLUEPRINT`: the\n * drafter needs structure, the fact producer needs the closed set of names. Sending it the drafting\n * brief would bury the eight lines that matter under section obligations it never authors.\n *\n * The gap it closes, measured 2026-08-30: a fact's ref is stamped from a slug the model chooses, so\n * a fact answering the right question under a different name is a fact no clause can cite. wonder-crm\n * declared twenty facts and matched ZERO of the eight a privacy notice requires —\n * `retention-period-schedule-status` for `retention-rules`,\n * `configured-external-provider-recipients` for `recipients-and-processors`. Semantically adjacent,\n * lexically disjoint, so nothing joins them and the answers read as absent.\n *\n * The method has asked for stable descriptive slugs, NAMING THREE OF THE EIGHT as examples, since\n * 2026-08-28 — two days before that measurement. Prose has been tried; what was never supplied is\n * the closed set the catalog has held all along.\n */\n DOCUMENT_FACT_OBLIGATIONS = 'document_fact_obligations',\n /**\n * The closed sets a compliance programme may bind and cite: the objectives the assurance authority basis states an\n * expectation for, and the sources the registry carries.\n *\n * Same lesson as {@link DOCUMENT_FACT_OBLIGATIONS}, with a harsher failure. The programme's normalizer REFUSES an\n * objective the basis has no expectation for and a source the registry does not carry, so a producer that guesses does\n * not land a subtly wrong artifact — it spends a run, out of the three a playbook is budgeted.\n */\n ASSURANCE_PROGRAM_AUTHORITY = 'assurance_program_authority',\n /**\n * The application's OWN role graph: the app-scope and organization-scope roles it actually declares,\n * which user type receives which by default, and which role holds the administrative ceiling.\n *\n * For a playbook that must name an ACCOUNTABLE or OPERATING role. It replaces two free-text\n * elicitation questions on `top_down.compliance-conception` that asked a person to type\n * *\"the application's own role key (e.g. APP_ADMIN_SUPER_ADMIN)\"* — a value that is not a judgement\n * at all: the role vocabulary is a closed enum (`CORE_APP_ROLES` / `CORE_ORG_ROLES`), and which\n * roles THIS application grants is declared in its own backend config (`userTypes[].defaultAppRoles`,\n * `organizationTypes[].availableOrgRoles`). Asking for it invited a role key that resolves to\n * nothing, in an artifact whose whole purpose is to say who is accountable.\n *\n * Same lesson as {@link ASSURANCE_PROGRAM_AUTHORITY} and {@link DOCUMENT_FACT_OBLIGATIONS}: supply\n * the closed set rather than describing it. What stays a decision is WHICH of the declared roles is\n * accountable — a selection from a rendered set, not a string somebody invents.\n *\n * Derived from a static enum plus the backend companion exports the runtime already loads, so it\n * needs no new introspection behavior.\n */\n APPLICATION_ROLE_GRAPH = 'application_role_graph',\n /**\n * The judged runs committed in this application's OWN assurance repository — what its controls were\n * measured to do, as SELF-ATTESTED INTERNAL EVIDENCE (#297).\n *\n * For a playbook drafting an INTERNAL governance document, and for nothing else today. Until this\n * existed the assurance cycle produced findings and clean passes that were citable by nobody: an\n * operating statement had exactly two forms, an unsupported claim or a mark, so the mark was always\n * correct and the evidence never reached the only documents entitled to rest on it.\n *\n * It is deliberately NOT a verdict the lane reacts to. Nothing here gates a run, a drafter may cite a\n * run or ignore it, and an application with no repository or no runs gets a section that says so —\n * the clause is then MARKED, exactly as before (`application-creation-directive.md`: a workflow never\n * blocks the mechanism). The one-way street the assurance plane keeps — it reads the product and\n * writes only into its own repository — is unchanged: this carries committed runs INTO a brief and\n * gives the creation lane no way to write back.\n *\n * What a citing clause owes is stated where it is enforced rather than here: the ref must resolve to\n * a committed run, and ANY citation in a document under `document-claim-policy:public-safe-baseline`\n * is refused, because what makes a public operating claim wrong is the reader it reaches rather than\n * the evidence behind it.\n */\n ASSURANCE_EVIDENCE = 'assurance_evidence',\n /**\n * The document facts a PERSON established — the `document-facts-authored` family, which the derived\n * family deliberately does not carry.\n *\n * A drafter reads the derived facts as a declared input. The authored ones it could not read at all,\n * and the cost is measurable: on wonder-todos 2026-09-22 the governance draft CITED\n * `document-fact:governance-scope-review-triggers` and wrote a paraphrase around it — \"change in a way\n * identified by the scope-review decision\" — where the authored value names the triggers outright and\n * adds an annual human review the draft omits entirely. The clause was marked DERIVED and the landing\n * accepted it, because the fact-binding check asks whether a cited fact was DECLARED and never whether\n * the drafter could read it. Citation without readership.\n *\n * It is a CONTEXT SOURCE rather than a declared input for a structural reason, not a stylistic one:\n * the authored family is landed by the companion's governance-facts door rather than by any playbook,\n * so declaring it as an input is an input family no playbook produces — which `wildo fwk audit` rule 23\n * refuses outright. Derived context has no such requirement, and this IS derived context: the lane\n * reads it and never writes it.\n *\n * Kept SEPARATE from the derived facts in the brief rather than merged into them, because the\n * difference is what a drafter most needs to respect. A derived fact is re-derived from the product on\n * the next run; an authored one is a person's decision, and a clause that contradicts it contradicts\n * the human who wrote it.\n */\n AUTHORED_DOCUMENT_FACTS = 'authored_document_facts',\n /**\n * The DETERMINISTIC per-ICP FIT matrix, computed from the decided market snapshot by\n * `computeFeatureFitScoreForICP`, delivered beside each benefit's AUTHORED Kano category.\n *\n * For a playbook whose method consumes a fit signal. Three of them do — `top_down.capability-map`,\n * `top_down.value-proposition`, `top_down.scope-roadmap` — and all three told their model to \"feed\n * the snapshot to the scorer and read back the scores\". A structured generation has no tools, so\n * that instruction named an act the model cannot perform; what it did instead was estimate, which\n * is arithmetic done worse and unfalsifiably.\n *\n * Exactly `COHERENCE_REPORT`'s trade, for the same reason: the arithmetic goes in so the model can\n * judge what arithmetic cannot — whether a low-scoring capability is a mis-mapped benefit or a\n * segment the product deliberately does not serve.\n *\n * Every playbook that declares it ALREADY declares `market-snapshot` as an input, so this adds no\n * new knowledge to the brief; it adds a computation over knowledge that was already there. That is\n * what distinguishes it from a speculative source, which `.claude/context/app-creation-dynamic-context.md`\n * design 8 would hold to a paired-case measurement first.\n *\n * SCORES ONLY, never a ranking. The scorer's own docstring locks the vocabulary — fit is not\n * prioritization — and a section that sorted by score would smuggle in the build-order model the\n * methods explicitly defer.\n */\n MARKET_FIT_SCORES = 'market_fit_scores',\n /**\n * The DERIVED risk signals (#300 Layer 1) — measured facts about this application's own\n * declarations, each with its provenance and none with a score.\n *\n * For a playbook that weighs risk. `top_down.risk-register`'s method says \"if signals were not\n * supplied to this run…\" and, measured 2026-09-22, nothing had ever supplied them: the six\n * derivations were reachable only from an assurance script, so the register's derived half was\n * permanently absent and every run took the fallback branch.\n *\n * NOT the assurance plane. The derivations moved into the engine precisely so the creation lane\n * could read them without importing that plane — `application-creation-directive.md` keeps that\n * street one-way, and its collectors' hard exits are right for an auditor's tool and wrong inside\n * a run that must not stop. What arrives here is a pure function of `wildo.saas.config.ts` and the\n * application's own materialized resources; nothing is measured from a running system, nothing is\n * a verdict, and the section never gates the run.\n *\n * SIGNALS, never conclusions, and the derivation layer asserts that structurally: no score, no\n * weight, no level, no severity. What a signal MEANS is the playbook's question — which is the\n * whole reason the arithmetic is delivered and the judgement is not.\n */\n RISK_SIGNALS = 'risk_signals',\n}\n\n/**\n * How a declared input reaches the brief.\n *\n * Input-only — see {@link MetaWorkflowPlaybookInputSchema} for why this is not on the shared selector.\n */\nexport enum MetaWorkflow_InputRender {\n /** The selected aspects' content, rendered as prose — what every input received before aspects existed. */\n FULL = \"full\",\n /**\n * Only one `ref — label` line per element of the selected aspects. For a step that needs to know WHAT\n * exists (to reference it by ref, or to stay consistent with it) without re-reading its content.\n */\n MAP = \"map\",\n}\n\n/**\n * The deepest RELATED walk anything may ask for — a playbook input's `related.hops` and the\n * `specification-elements` pull door share this one cap. Each hop multiplies what comes back, and\n * nothing measured so far asks for more than one.\n */\nexport const DECIDED_ELEMENTS_MAXIMUM_RELATED_HOPS = 2;\n\n/** Follow the declared reference edges out of an input's selected elements. */\nexport const MetaWorkflow_InputRelatedSchema = z.strictObject({\n /**\n * Edges to follow from each selected element, both directions. Capped at 2: each hop multiplies\n * what the brief carries, and nothing measured so far asks for more than one.\n */\n hops: z.number().int().min(1).max(DECIDED_ELEMENTS_MAXIMUM_RELATED_HOPS).default(1),\n /** Keep only related elements of these aspect keys. The walk itself crosses every aspect. */\n targetAspects: z.array(z.string().min(1)).min(1).optional(),\n});\nexport type MetaWorkflow_InputRelated = z.infer<typeof MetaWorkflow_InputRelatedSchema>;\n\n/**\n * One declared INPUT of a playbook: the shared artifact selector plus what the step reads of it (#1420).\n *\n * ## Why this is not on `MetaWorkflow_ArtifactSelectorSchema`\n *\n * That selector also types PRECONDITIONS. An aspect or a render mode there would read as a readiness\n * gate — \"wait until these aspects exist\" — which eligibility never honours. Narrowing what a playbook\n * READS must never narrow what it WAITS FOR, so the narrowing lives on the input alone.\n *\n * ## By ASPECT, never by ref\n *\n * A playbook is application-agnostic: its author cannot know which ICPs or requirements an\n * application will have. So a static declaration names aspect KINDS (`market.icp`); fetching one\n * element by ref is a run-time act of an agent that has already seen the map.\n *\n * ## What is validated where\n *\n * The keys must exist and must belong to the declared family. That check needs the aspect registry,\n * which this module cannot import (the family schemas it indexes import this module for\n * `MetaWorkflow_FunctionalTopic`, so the import would be a cycle evaluated at load). It runs at\n * `wildo fwk generate-docs`, through `findPlaybookInputAspectViolations` in\n * `@wildo-ai/application-creation-runtime`, and fails the generation closed. What this schema refuses\n * is what it can see on its own: an `aspects` list beside an `intent`, which would be two narrowings of\n * one input with no rule for which wins.\n */\nexport const MetaWorkflowPlaybookInputSchema = MetaWorkflow_ArtifactSelectorSchema.extend({\n /**\n * The aspect keys of `family` this step reads (`['market.icp', 'market.job']`). Absent = the whole\n * family. Everything else in the family is shown as a MAP (ref + label), never silently dropped.\n */\n aspects: z.array(z.string().min(1)).min(1).optional(),\n /** Absent = {@link MetaWorkflow_InputRender.FULL}. */\n render: z.enum(MetaWorkflow_InputRender).optional(),\n related: MetaWorkflow_InputRelatedSchema.optional(),\n}).superRefine((input, context) => {\n if (input.aspects !== undefined && input.intent !== undefined) {\n context.addIssue({\n code: \"custom\",\n path: [\"aspects\"],\n message: `Input \"${input.family}\" declares both \\`intent\\` and \\`aspects\\`. They are two narrowings of one input with no rule for which wins; declare the aspects alone.`,\n });\n }\n});\nexport type MetaWorkflowPlaybookInput = z.infer<typeof MetaWorkflowPlaybookInputSchema>;\n\n/**\n * One declared OUTPUT of a playbook: the shared artifact contract plus, optionally, the aspects of that family\n * this playbook WRITES (#2146).\n *\n * Several families have more than one writer, each owning a slice: `top_down.compliance-posture` writes only\n * the vision's constraints, `top_down.vision-elicitation` the whole vision. Without this, a writer of one slice\n * reopened every reader of the whole family: measured on app-creation-test-004, the posture's write into the\n * vision made five definition leaves refresh, among them ones whose brief never uses a constraint.\n *\n * Read by the rerun verdict only: a landing by this writer reopens a reader of the family only when the aspects\n * written meet the aspects the reader reads (`inputs[].aspects`, or the aspects its `intent` resolves to; a\n * reader that narrows nothing reads the whole family and is reopened by any writer). Absent = this playbook may\n * write any aspect of the family, which is the safe reading. Keys are validated against the family at\n * `wildo fwk generate-docs`, exactly like `inputs[].aspects`.\n */\nexport const MetaWorkflowPlaybookOutputSchema = MetaWorkflow_ArtifactContractSchema.extend({\n aspects: z.array(z.string().min(1)).min(1).optional(),\n});\nexport type MetaWorkflowPlaybookOutput = z.infer<typeof MetaWorkflowPlaybookOutputSchema>;\n\nexport const MetaWorkflowPlaybookSchema = z.object({\n ref: z.string().min(1),\n version: z.string().min(1),\n phase: z.enum(MetaWorkflow_Phase),\n intent: z.string().min(1),\n /*\n * There is deliberately NO `functionalTopics` on a PLAYBOOK (#488, removed 2026-09-08).\n *\n * Authored intent that nothing branched on: the generator copied it into the compiled catalog and\n * no runtime read it from there. Non-empty on 4 of 26 playbooks, empty on the rest — a taxonomy\n * label kept because it looked like structure.\n *\n * The VOCABULARY stays, because `BuildPlanTask.functionalTopic` — SINGULAR, on the task — is live:\n * required on the task graph, copied through generation, and stamped into the coding-agent dispatch\n * payload as context the agent reads. The two differ by one letter and by which object carries them,\n * which is exactly why this needed measuring rather than grepping the enum.\n */\n preconditions: z.array(MetaWorkflow_JourneyPredicateSchema).default([]),\n inputs: z.array(MetaWorkflowPlaybookInputSchema).default([]),\n outputs: z.array(MetaWorkflowPlaybookOutputSchema).default([]),\n /**\n * Values this playbook returns to its PARENT choreography instead of landing.\n *\n * Orthogonal to `outputs`, not an alternative to it: a playbook may do both, and a child that lands\n * a file lands it exactly as it would standalone. Composition adds a second return channel; it does\n * not intercept the first. That is also why every existing playbook is already a legal child.\n */\n stepOutputs: z.array(MetaWorkflow_StepOutputContractSchema).default([]),\n method: z.object({\n guidance: z.string().min(1),\n skillRefs: z.array(z.string().min(1)).default([]),\n /**\n * The skills whose FULL BODY this method needs in its brief, not just their purpose line.\n *\n * A SUBSET of `skillRefs`, checked by `wildo fwk audit` — naming a skill the method does not\n * declare would put a contract in the brief the guidance never tells the model to follow.\n *\n * Why a second declaration rather than \"render every named skill's body\": the catalog does not\n * fit. Measured 2026-09-22, `top_down.market-snapshot-produce` names SIXTEEN skills and one of\n * them (`market-companion-prompt-enrichment`) is 133KB on its own, so rendering bodies for\n * every named skill would put hundreds of kilobytes into a brief for playbooks that need none\n * of it. The two that genuinely need one — a logo lockup's field contract, a governed\n * document's authoring contract — need ONE each, and say so in their own guidance.\n *\n * So the bound is an AUTHORING decision rather than a lucky total, which is the same shape as\n * `inputs[].aspects`: the method names what it reads, and the runtime resolves exactly that\n * before composition (#251). Empty by default, and that default is the honest one — a body\n * costs tokens on every run and pays only where the guidance says \"follow this skill\".\n *\n * The BODY only. `references/`, `examples/` and `scripts/` stay the on-demand tier a CODING\n * agent opens; a structured generation can open nothing, so inlining them would carry material\n * nobody asked for.\n */\n skillBodyRefs: z.array(z.string().min(1)).default([]),\n elicitation: MetaWorkflow_ElicitationSpecSchema.optional(),\n /**\n * Derived context sections this playbook's brief carries beyond its declared `inputs[]`.\n *\n * Empty by default, and that default is the honest one: a section costs tokens on every run and\n * pays only where the method routes through it.\n */\n contextSources: z.array(z.enum(MetaWorkflow_ContextSource)).default([]),\n /**\n * The governed documents this playbook may DRAFT, as `document-definition:` refs.\n *\n * Meaningless without `MetaWorkflow_ContextSource.DOCUMENT_BLUEPRINT`: it is that source's\n * parameter — which blueprints the brief carries, and therefore which documents the lane may\n * produce. Empty by default, so a playbook that drafts no document declares nothing.\n *\n * **It exists because a drafting lane is defined by its DOCUMENTS, and that was a runtime\n * constant.** The companion held one frozen list, and its own comment said the refs came \"from\n * the playbook's own declaration rather than from a parameter\" — which was the right design and\n * not what the code did. The cost was that a SECOND drafting lane could not exist without editing\n * the companion, and the four internal governance documents therefore had no lane at all (#1453):\n * widening the one list was the only move available, and it would have put all six blueprints in\n * every drafting prompt. Measured 2026-09-22: 21KB for the public pair, 24KB for the governance\n * four, 45KB together — and a prompt section that gets skimmed is indistinguishable from an\n * absent one, which is the same argument that kept the governance documents out in the first\n * place. Declared per playbook, each lane carries only its own.\n *\n * Same shape and same reason as `briefAdequacyExcludedSources`: an authored boundary a prose\n * comment cannot enforce, because unknown keys are stripped at parse and a runtime reads only\n * what the schema admits.\n *\n * A ref naming no blueprint in the engine catalog renders nothing, so the set a lane can draft\n * would silently shrink. `playbook-catalog-document-declarations.test.ts` resolves every declared\n * ref against the catalog, which is where a typo is caught rather than at the next run.\n */\n draftableDocumentDefinitionRefs: z.array(z.string().min(1)).default([]),\n /**\n * Present exactly when this playbook orchestrates children rather than producing an artifact.\n *\n * A composite declares no `outputs` of its own — what commits is what its children land.\n */\n choreography: MetaWorkflow_ChoreographySchema.optional(),\n /**\n * May this playbook SUSPEND mid-run and ask the creator a question it cannot answer from its\n * inputs?\n *\n * Opt-in rather than global, because the channel costs one small model call per output and only\n * pays where a derivation faces a decision a product owner owns rather than one the artifacts\n * determine. A playbook that suspends returns a resumable checkpoint instead of a landed file;\n * the creator answers accept / decline / cancel, and `decline` has the derivation choose and\n * state its assumption rather than stalling.\n */\n suspendsForClarification: z.boolean().default(false),\n /**\n * May this playbook's composed brief be JUDGED for sufficiency before generation, with ONE\n * monotonic repair pass on an INSUFFICIENT verdict?\n *\n * #254's rescoped shape (decision 2026-09-02, built 2026-09-04): a tool-free structured judge\n * reads the composed brief and the closed list of UNDECLARED context sources; `insufficient`\n * adds the proposed sources to the declaration FOR THIS RUN ONLY — add-only, never removing or\n * softening a declared source — and the brief recomposes once. The gate never runs twice, and a\n * gate fault fails OPEN to the static brief: an auxiliary judgment must never withhold a run.\n *\n * Opt-in per playbook, exactly like `suspendsForClarification`, because the gate costs one\n * model call per run and pays only where context needs genuinely vary per application — the\n * document lane, per the recorded pilot decision.\n */\n briefAdequacyGate: z.boolean().default(false),\n /**\n * Sources the gate may NEVER propose, carrying an authored boundary into the mechanism.\n *\n * Monotonic is not the same as safe: an ADD can still violate a deliberate exclusion — the\n * document drafter's own `//contextSources` reason forbids `compliance_primary_facts` because a\n * drafter given raw mechanism could write a clause resting on something the application never\n * DECLARED. A prose reason is invisible to the runtime (unknown keys are stripped at parse);\n * this field is the same decision, enforceable. Meaningless without `briefAdequacyGate`.\n */\n briefAdequacyExcludedSources: z.array(z.enum(MetaWorkflow_ContextSource)).default([]),\n /**\n * Present exactly when this playbook's artifact is DELIBERATED rather than\n * generated in one pass — an expert panel argues over several candidates and a\n * coordinator converges.\n *\n * **This is a substitution at the generation port, not a different executor.**\n * The host produces `candidateCount` candidates through its ordinary structured\n * generation (each already schema-constrained), runs the panel over them as\n * STRUCTURED deliberation candidates, and returns the winner. Everything\n * downstream — validation, findings-fed retry, rendering, landing, the judge —\n * is untouched, because what changes is only how the value was ARRIVED AT.\n *\n * Declaring a `DELIBERATION_PANEL` executor member was the obvious alternative\n * and is wrong: `runPlaybook` never branches on `executor` (only choreography\n * children do), so the member would name a capability nothing dispatches — the\n * declared-but-unrunnable shape this codebase has already paid for once with\n * `build-plan`.\n *\n * Costly by construction — `candidateCount` generations plus a rubric pass plus\n * reviewers × candidates per round plus synthesis — so it belongs only where the\n * decision genuinely has several defensible answers and the creator should not\n * have to pick between them. A derivation the artifacts determine does not need\n * a panel.\n *\n * FAIL-CLOSED on charters: every named role needs a committed charter and the\n * companion indexes agents at startup, so a role accepted after boot has no agent\n * until restart. The panel says exactly that rather than silently degrading to a\n * single pass — a deliberation that quietly became one generation would be the\n * worst outcome, since the artifact would carry a rationale nobody argued over.\n */\n deliberation: MetaWorkflow_PlaybookDeliberationSchema.optional(),\n }),\n /**\n * Which tier runs this playbook's step — OPTIONAL since 2026-08-29 (#115), and the option is the\n * point: a playbook that runs no single step has no truthful value to give. `top_down.market-analysis`\n * composes children and executes nothing itself; `bottom_up.foundation` is a bespoke deterministic\n * executor the host dispatches by ref. Both declared the removed `COMPOSITE` to fill a required\n * field, which is how that member became a catch-all. Absent means \"not one tier\" — read\n * `method.choreography`, or the host's own dispatch, for what actually runs it.\n */\n executor: z.enum(MetaWorkflow_Executor).optional(),\n /*\n * There is deliberately NO `executorPersona`. Declared until 2026-09-08 (#488): authored by 0 of\n * 26 playbooks, not copied into the compiled registry entry, read by no runtime.\n *\n * Note it is NOT `executor`, the live field directly above — the two differ by a word, and a\n * symbol search for the persona enum it referenced looked busy because a blueprint prompt library\n * used that enum heavily and unrelatedly. That resemblance is why it survived: everything about\n * it looked used.\n *\n * Both are gone now. The enum (`AppsBlueprint_AgentPersonas`) and the prompt library were deleted\n * on 2026-09-19 — the library turned out to be commented out and unreachable — so the closed\n * persona vocabulary no longer exists anywhere. A persona is an open `z.string()` on the engine's\n * `FlowsActors_Agent_PromptSpec`, which is what it always should have been.\n */\n /*\n * There is deliberately NO `qualityGates` here. The field existed from the catalog's first day\n * until 2026-08-29 (issue #103): 20 playbooks declared it, 13 with a `validatorRef`, and NO\n * RUNTIME EVER EXECUTED ONE — `validatorRef` was a bare `z.string()` with no resolver anywhere.\n *\n * It was deleted rather than wired because every gate it declared was ALREADY delivered, by a\n * mechanism that runs:\n *\n * - 10 named their own family's `_core` validator, which the semantic authority's per-family\n * `runValidator` runs at landing and the `definition-specifications` behavior runs fail-closed\n * at load. Executing the gate would have bought a second identical call.\n * - 2 named `typecheck`, which `resolveBuildPlanTaskCodingPolicy` runs through\n * `APPLICATION_CODING_TASK_VERIFICATION_CATALOG`, outside the coding agent, in the package the\n * task mutated.\n * - 1 (`capability-map-output-set-valid`) named the one genuinely cross-family check — a market\n * benefit's `deliveredByFeatureRefs` resolving against the drafted features. A per-family\n * validator structurally cannot see a sibling family, so that check belongs to\n * `buildApplicationCoherenceReport`, which reports it as `benefit-delivered-by-unknown-feature`\n * into `src/COHERENCE.md` and into the phase gate's context.\n *\n * Each playbook's `method.md` still carries its `## Quality gate` section, and that prose is the\n * accurate one: it describes the validator the LANDING PATH runs. Do not reintroduce a declared\n * gate to restate it — a second description of a live check is what this field was.\n */\n /**\n * ## KEPT DELIBERATELY, AND NOT ENFORCED YET (#488, decided 2026-09-08)\n *\n * These three — the approval policy, the budget ceilings and the failure policy — are authored by\n * playbook definitions and read by NO runtime. Their intended enforcer was the PlaybookRunner,\n * deleted at the first-activation hard cut.\n *\n * They were kept while `executorPersona`, `functionalTopics` and the depth ceiling were deleted in\n * the same pass, and the distinction is the point: those were dead CLASSIFICATION — a label nothing\n * would ever branch on. These are a governance CAPABILITY that is merely early. A playbook declaring\n * that its result must be approved is stating something the lane will need the day it runs\n * unattended against anything that matters.\n *\n * **So do not read them as enforced, and do not delete them as unused.** The enforcer is built when\n * the lane needs governance, and building it is not a wiring job: it creates a new REFUSAL and a new\n * PERMISSION BOUNDARY — who may run unattended, and on what evidence a run is cut — which is a\n * decision rather than an implementation.\n *\n * The autonomy PRESET at journey level belongs with this block for the same reason, not with the\n * classification axes that went.\n */\n approval: z.enum(MetaWorkflow_ApprovalPolicy),\n budget: MetaWorkflow_PlaybookBudgetSchema,\n onFailure: z.enum(MetaWorkflow_FailurePolicy),\n}).superRefine((playbook, context) => {\n /*\n * An `artifact_decides` gate names a decision its family DECLARES, and one member of that decision's\n * vocabulary (#1606). Refused here, where the generator parses every playbook, because a misspelt\n * decision or value would otherwise make the playbook ineligible forever and report nothing.\n */\n playbook.preconditions.forEach((predicate, index) => {\n if (predicate.kind !== MetaWorkflow_PredicateKind.ARTIFACT_DECIDES) return;\n const decision = getApplicationSpecificationFamilyDecision(predicate.selector.family, predicate.decision);\n if (decision === undefined) {\n context.addIssue({\n code: \"custom\",\n path: [\"preconditions\", index, \"decision\"],\n message: `\"${predicate.selector.family}\" declares no decision \"${predicate.decision}\" (APPLICATION_SPECIFICATION_FAMILY_DECISIONS).`,\n });\n return;\n }\n if (!decision.vocabulary.includes(predicate.equals)) {\n context.addIssue({\n code: \"custom\",\n path: [\"preconditions\", index, \"equals\"],\n message: `\"${predicate.equals}\" is not a value of \"${predicate.selector.family}\" decision \"${predicate.decision}\"; expected one of ${decision.vocabulary.join(\", \")}.`,\n });\n }\n });\n});\nexport type MetaWorkflowPlaybook = z.infer<typeof MetaWorkflowPlaybookSchema>;\n/**\n * Native playbooks are authored before schema defaults are materialized.\n * Keeping this input type distinct from `MetaWorkflowPlaybook` prevents every\n * defaulted field from becoming a meaningless required declaration while the\n * compiled/loaded contract remains the fully parsed output type.\n */\nexport type MetaWorkflowPlaybookAuthoring = z.input<typeof MetaWorkflowPlaybookSchema>;\n"]}
|
package/dist/esm/application-creation/structured-artifact-landing.application-creation.schemas.d.ts
CHANGED
|
@@ -12,6 +12,7 @@ import { z } from "zod";
|
|
|
12
12
|
*/
|
|
13
13
|
export declare enum ApplicationSpecificationStructuredArtifactLandingRenderProfile {
|
|
14
14
|
BRAND_SNAPSHOT_V1 = "BRAND_SNAPSHOT_V1",
|
|
15
|
+
BRAND_NAME_SCREENING_V1 = "BRAND_NAME_SCREENING_V1",
|
|
15
16
|
BUILD_PLAN_TASK_GRAPH_V1 = "BUILD_PLAN_TASK_GRAPH_V1",
|
|
16
17
|
DOMAIN_PLAN_OUTPUT_SET_V1 = "DOMAIN_PLAN_OUTPUT_SET_V1",
|
|
17
18
|
BUSINESS_MODEL_LITE_SNAPSHOT_V1 = "BUSINESS_MODEL_LITE_SNAPSHOT_V1",
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"structured-artifact-landing.application-creation.schemas.d.ts","sourceRoot":"","sources":["../../../../src/application-creation/structured-artifact-landing.application-creation.schemas.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB;;;;;;;;;;GAUG;AACH,oBAAY,8DAA8D;IACxE,iBAAiB,sBAAsB;IACvC,wBAAwB,6BAA6B;IACrD,yBAAyB,8BAA8B;IACvD,+BAA+B,oCAAoC;IACnE,gCAAgC,qCAAqC;IACrE,oCAAoC,yCAAyC;IAC7E,kCAAkC,uCAAuC;IACzE,iDAAiD,sDAAsD;IACvG,oDAAoD,yDAAyD;IAC7G,mCAAmC,wCAAwC;IAC3E,0CAA0C,+CAA+C;IACzF,mDAAmD,wDAAwD;IAC3G,iCAAiC,sCAAsC;IACvE,4BAA4B,iCAAiC;IAC7D,6BAA6B,kCAAkC;IAC/D,yBAAyB,8BAA8B;IACvD,eAAe,oBAAoB;IACnC,kBAAkB,uBAAuB;IACzC,iCAAiC,sCAAsC;IACvE,mBAAmB,wBAAwB;IAC3C,uBAAuB,4BAA4B;IACnD,+BAA+B,oCAAoC;IACnE,iBAAiB,sBAAsB;IACvC,kBAAkB,uBAAuB;IACzC,wBAAwB,6BAA6B;IACrD,mBAAmB,wBAAwB;IAC3C,kBAAkB,uBAAuB;CAC1C;AAED;;;;;;;GAOG;AACH,eAAO,MAAM,6DAA6D;IACxE,2GAA2G;;IAE3G,8EAA8E;;;;kBAI9E,CAAC;AAEH,MAAM,MAAM,uDAAuD,GAAG,CAAC,CAAC,KAAK,CAC3E,OAAO,6DAA6D,CACrE,CAAC"}
|
|
1
|
+
{"version":3,"file":"structured-artifact-landing.application-creation.schemas.d.ts","sourceRoot":"","sources":["../../../../src/application-creation/structured-artifact-landing.application-creation.schemas.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB;;;;;;;;;;GAUG;AACH,oBAAY,8DAA8D;IACxE,iBAAiB,sBAAsB;IACvC,uBAAuB,4BAA4B;IACnD,wBAAwB,6BAA6B;IACrD,yBAAyB,8BAA8B;IACvD,+BAA+B,oCAAoC;IACnE,gCAAgC,qCAAqC;IACrE,oCAAoC,yCAAyC;IAC7E,kCAAkC,uCAAuC;IACzE,iDAAiD,sDAAsD;IACvG,oDAAoD,yDAAyD;IAC7G,mCAAmC,wCAAwC;IAC3E,0CAA0C,+CAA+C;IACzF,mDAAmD,wDAAwD;IAC3G,iCAAiC,sCAAsC;IACvE,4BAA4B,iCAAiC;IAC7D,6BAA6B,kCAAkC;IAC/D,yBAAyB,8BAA8B;IACvD,eAAe,oBAAoB;IACnC,kBAAkB,uBAAuB;IACzC,iCAAiC,sCAAsC;IACvE,mBAAmB,wBAAwB;IAC3C,uBAAuB,4BAA4B;IACnD,+BAA+B,oCAAoC;IACnE,iBAAiB,sBAAsB;IACvC,kBAAkB,uBAAuB;IACzC,wBAAwB,6BAA6B;IACrD,mBAAmB,wBAAwB;IAC3C,kBAAkB,uBAAuB;CAC1C;AAED;;;;;;;GAOG;AACH,eAAO,MAAM,6DAA6D;IACxE,2GAA2G;;IAE3G,8EAA8E;;;;kBAI9E,CAAC;AAEH,MAAM,MAAM,uDAAuD,GAAG,CAAC,CAAC,KAAK,CAC3E,OAAO,6DAA6D,CACrE,CAAC"}
|
package/dist/esm/application-creation/structured-artifact-landing.application-creation.schemas.js
CHANGED
|
@@ -13,6 +13,7 @@ import { z } from "zod";
|
|
|
13
13
|
export var ApplicationSpecificationStructuredArtifactLandingRenderProfile;
|
|
14
14
|
(function (ApplicationSpecificationStructuredArtifactLandingRenderProfile) {
|
|
15
15
|
ApplicationSpecificationStructuredArtifactLandingRenderProfile["BRAND_SNAPSHOT_V1"] = "BRAND_SNAPSHOT_V1";
|
|
16
|
+
ApplicationSpecificationStructuredArtifactLandingRenderProfile["BRAND_NAME_SCREENING_V1"] = "BRAND_NAME_SCREENING_V1";
|
|
16
17
|
ApplicationSpecificationStructuredArtifactLandingRenderProfile["BUILD_PLAN_TASK_GRAPH_V1"] = "BUILD_PLAN_TASK_GRAPH_V1";
|
|
17
18
|
ApplicationSpecificationStructuredArtifactLandingRenderProfile["DOMAIN_PLAN_OUTPUT_SET_V1"] = "DOMAIN_PLAN_OUTPUT_SET_V1";
|
|
18
19
|
ApplicationSpecificationStructuredArtifactLandingRenderProfile["BUSINESS_MODEL_LITE_SNAPSHOT_V1"] = "BUSINESS_MODEL_LITE_SNAPSHOT_V1";
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"structured-artifact-landing.application-creation.schemas.js","sourceRoot":"","sources":["../../../../src/application-creation/structured-artifact-landing.application-creation.schemas.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB;;;;;;;;;;GAUG;AACH,MAAM,CAAN,IAAY,
|
|
1
|
+
{"version":3,"file":"structured-artifact-landing.application-creation.schemas.js","sourceRoot":"","sources":["../../../../src/application-creation/structured-artifact-landing.application-creation.schemas.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB;;;;;;;;;;GAUG;AACH,MAAM,CAAN,IAAY,8DA6BX;AA7BD,WAAY,8DAA8D;IACxE,yGAAuC,CAAA;IACvC,qHAAmD,CAAA;IACnD,uHAAqD,CAAA;IACrD,yHAAuD,CAAA;IACvD,qIAAmE,CAAA;IACnE,uIAAqE,CAAA;IACrE,+IAA6E,CAAA;IAC7E,2IAAyE,CAAA;IACzE,yKAAuG,CAAA;IACvG,+KAA6G,CAAA;IAC7G,6IAA2E,CAAA;IAC3E,2JAAyF,CAAA;IACzF,6KAA2G,CAAA;IAC3G,yIAAuE,CAAA;IACvE,+HAA6D,CAAA;IAC7D,iIAA+D,CAAA;IAC/D,yHAAuD,CAAA;IACvD,qGAAmC,CAAA;IACnC,2GAAyC,CAAA;IACzC,yIAAuE,CAAA;IACvE,6GAA2C,CAAA;IAC3C,qHAAmD,CAAA;IACnD,qIAAmE,CAAA;IACnE,yGAAuC,CAAA;IACvC,2GAAyC,CAAA;IACzC,uHAAqD,CAAA;IACrD,6GAA2C,CAAA;IAC3C,2GAAyC,CAAA;AAC3C,CAAC,EA7BW,8DAA8D,KAA9D,8DAA8D,QA6BzE;AAED;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,6DAA6D,GAAG,CAAC,CAAC,YAAY,CAAC;IAC1F,2GAA2G;IAC3G,iBAAiB,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,KAAK,CAAC,4BAA4B,CAAC;IACjE,8EAA8E;IAC9E,mBAAmB,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC;IACtC,oBAAoB,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,KAAK,CAAC,6BAA6B,CAAC;IACrE,aAAa,EAAE,CAAC,CAAC,IAAI,CAAC,8DAA8D,CAAC;CACtF,CAAC,CAAC","sourcesContent":["import { z } from \"zod\";\n\n/**\n * How a structured Action output is rendered into an application specification FILE.\n *\n * This is the surviving half of a much larger deleted vocabulary. What went with the accepted-state ledger\n * was every notion of a family record, a locator id and a target manifest entry — bookkeeping about WHERE a\n * file was allowed to live and WHO had accepted it. What remains is the only part that was ever about\n * content: which schema a model output must satisfy, and what its rendered TypeScript should be called.\n *\n * A profile is a closed semantic vocabulary in the sense CLAUDE.md means: each member names the exact\n * snapshot contract a rendered file must parse as, and adding one is a deliberate act.\n */\nexport enum ApplicationSpecificationStructuredArtifactLandingRenderProfile {\n BRAND_SNAPSHOT_V1 = \"BRAND_SNAPSHOT_V1\",\n BRAND_NAME_SCREENING_V1 = \"BRAND_NAME_SCREENING_V1\",\n BUILD_PLAN_TASK_GRAPH_V1 = \"BUILD_PLAN_TASK_GRAPH_V1\",\n DOMAIN_PLAN_OUTPUT_SET_V1 = \"DOMAIN_PLAN_OUTPUT_SET_V1\",\n BUSINESS_MODEL_LITE_SNAPSHOT_V1 = \"BUSINESS_MODEL_LITE_SNAPSHOT_V1\",\n COMPLIANCE_DOCUMENT_CANDIDATE_V1 = \"COMPLIANCE_DOCUMENT_CANDIDATE_V1\",\n COMPLIANCE_DOCUMENT_CANDIDATE_SET_V1 = \"COMPLIANCE_DOCUMENT_CANDIDATE_SET_V1\",\n ASSURANCE_PROGRAM_SPECIFICATION_V1 = \"ASSURANCE_PROGRAM_SPECIFICATION_V1\",\n APPLICATION_DOCUMENT_PUBLICATION_SPECIFICATION_V1 = \"APPLICATION_DOCUMENT_PUBLICATION_SPECIFICATION_V1\",\n APPLICATION_DOCUMENT_RELEASE_POLICY_SPECIFICATION_V1 = \"APPLICATION_DOCUMENT_RELEASE_POLICY_SPECIFICATION_V1\",\n APPLICATION_DOCUMENT_RELEASE_SET_V1 = \"APPLICATION_DOCUMENT_RELEASE_SET_V1\",\n APPLICATION_DOCUMENT_FACT_SPECIFICATION_V1 = \"APPLICATION_DOCUMENT_FACT_SPECIFICATION_V1\",\n APPLICATION_AUTHORED_DOCUMENT_FACT_SPECIFICATION_V1 = \"APPLICATION_AUTHORED_DOCUMENT_FACT_SPECIFICATION_V1\",\n APPLICATION_PROCESSOR_REGISTER_V1 = \"APPLICATION_PROCESSOR_REGISTER_V1\",\n APPLICATION_RISK_REGISTER_V1 = \"APPLICATION_RISK_REGISTER_V1\",\n APPLICATION_CREATOR_INPUTS_V1 = \"APPLICATION_CREATOR_INPUTS_V1\",\n CAPABILITY_COMPOSITION_V1 = \"CAPABILITY_COMPOSITION_V1\",\n WEBSITE_PLAN_V1 = \"WEBSITE_PLAN_V1\",\n EXPERIENCE_PLAN_V1 = \"EXPERIENCE_PLAN_V1\",\n APPLICATION_DOCUMENTATION_PLAN_V1 = \"APPLICATION_DOCUMENTATION_PLAN_V1\",\n INTEGRATION_PLAN_V1 = \"INTEGRATION_PLAN_V1\",\n APPLICATION_MATURITY_V1 = \"APPLICATION_MATURITY_V1\",\n FEATURE_SPECIFICATION_DRAFTS_V1 = \"FEATURE_SPECIFICATION_DRAFTS_V1\",\n PLACEMENT_PLAN_V1 = \"PLACEMENT_PLAN_V1\",\n MARKET_SNAPSHOT_V2 = \"MARKET_SNAPSHOT_V2\",\n REQUIREMENTS_SNAPSHOT_V1 = \"REQUIREMENTS_SNAPSHOT_V1\",\n ROADMAP_SNAPSHOT_V1 = \"ROADMAP_SNAPSHOT_V1\",\n VISION_SNAPSHOT_V1 = \"VISION_SNAPSHOT_V1\",\n}\n\n/**\n * One file a structured Action output lands as.\n *\n * Compare with what this replaces: the deleted member carried `familyId`, `targetLocatorId` and a\n * manifest-relative target path, because a file could only be written where an accepted family record said\n * it could. A path is now just a path — the working tree is the truth, and git decides what is accepted by\n * being committed.\n */\nexport const ApplicationSpecificationStructuredArtifactLandingTargetSchema = z.strictObject({\n /** Where in the Action's output the value lives. Data-only; the profile owns extraction and validation. */\n outputJsonPointer: z.string().regex(/^(?:\\/(?:[^~/]|~0|~1)*)*$/u),\n /** Package-relative path of the file to write, e.g. `src/market/index.ts`. */\n packageRelativePath: z.string().min(1),\n exportedConstantName: z.string().regex(/^[A-Za-z_$][A-Za-z0-9_$]*$/u),\n renderProfile: z.enum(ApplicationSpecificationStructuredArtifactLandingRenderProfile),\n});\n\nexport type ApplicationSpecificationStructuredArtifactLandingTarget = z.infer<\n typeof ApplicationSpecificationStructuredArtifactLandingTargetSchema\n>;\n"]}
|
|
@@ -76,6 +76,7 @@ export * from "./_core/compliance-documents/compliance-completeness-statement.sc
|
|
|
76
76
|
export * from "./_core/compliance-documents/document-fact-specification-generation.schemas";
|
|
77
77
|
export * from "./_core/compliance-documents/computed-document-facts.schemas";
|
|
78
78
|
export * from "./_core/compliance-documents/retention-enforcement-facts.schemas";
|
|
79
|
+
export * from "./_core/compliance-documents/launch-blockers.schemas";
|
|
79
80
|
export * from "./application-creation/journey.application-creation.schemas";
|
|
80
81
|
export * from "./application-creation/playbooks.application-creation.schemas";
|
|
81
82
|
export * from "./application-creation/domain-plan-evaluation-identities.application-creation.definitions";
|
|
@@ -87,6 +88,11 @@ export * from "./_core/brand/brand-snapshot.schemas";
|
|
|
87
88
|
export * from "./_core/brand/brand-visual-tone.schemas";
|
|
88
89
|
export * from "./_core/brand/brand-audience.schemas";
|
|
89
90
|
export * from "./_core/brand/brand-snapshot-validation";
|
|
91
|
+
export * from "./_core/brand/brand-name-screening.schemas";
|
|
92
|
+
export * from "./_core/brand/brand-name-screening-generation.schemas";
|
|
93
|
+
export * from "./_core/brand/brand-name-screening-validation";
|
|
94
|
+
export * from "./_core/brand/brand-name-choice";
|
|
95
|
+
export * from "./_core/brand/brand-name-screening-view";
|
|
90
96
|
export * from "./_core/brand/brand-logo-direction.schemas";
|
|
91
97
|
export * from "./_core/brand/brand-asset.schemas";
|
|
92
98
|
export * from "./_core/business-model-lite/pricing-plan.schemas";
|
|
@@ -107,6 +113,7 @@ export * from "./_core/feature-drafts/feature-specification-drafts.schemas";
|
|
|
107
113
|
export * from "./_core/feature-specification.schemas";
|
|
108
114
|
export * from "./_core/market/market-category.schemas";
|
|
109
115
|
export * from "./_core/market/market-icp.schemas";
|
|
116
|
+
export * from "./_core/market/market-language-coverage";
|
|
110
117
|
export * from "./_core/market/feature-benefit.schemas";
|
|
111
118
|
export * from "./_core/market/market-alternative.schemas";
|
|
112
119
|
export * from "./_core/market/market-buying-journey.schemas";
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"application-creation.exports.d.ts","sourceRoot":"","sources":["../../../src/application-creation.exports.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqDG;AACH,cAAc,6FAA6F,CAAC;AAC5G,cAAc,gFAAgF,CAAC;AAC/F,cAAc,sEAAsE,CAAC;AACrF,cAAc,uEAAuE,CAAC;AACtF,cAAc,gGAAgG,CAAC;AAC/G,cAAc,4FAA4F,CAAC;AAC3G,cAAc,uGAAuG,CAAC;AAWtH,cAAc,2DAA2D,CAAC;AAC1E,cAAc,iDAAiD,CAAC;AAQhE,cAAc,sDAAsD,CAAC;AAMrE,cAAc,wDAAwD,CAAC;AACvE,cAAc,mDAAmD,CAAC;AAMlE,cAAc,oEAAoE,CAAC;AACnF,cAAc,wEAAwE,CAAC;AACvF,cAAc,+EAA+E,CAAC;AAC9F,cAAc,4DAA4D,CAAC;AAC3E,cAAc,yDAAyD,CAAC;AACxE,cAAc,2DAA2D,CAAC;AAC1E,cAAc,4DAA4D,CAAC;AAC3E,cAAc,8DAA8D,CAAC;AAC7E,cAAc,wEAAwE,CAAC;AACvF,cAAc,6EAA6E,CAAC;AAC5F,cAAc,8DAA8D,CAAC;AAC7E,cAAc,kEAAkE,CAAC;AACjF,cAAc,6DAA6D,CAAC;AAC5E,cAAc,+DAA+D,CAAC;AAC9E,cAAc,2FAA2F,CAAC;AAK1G,cAAc,gCAAgC,CAAC;AAC/C,cAAc,iCAAiC,CAAC;AAahD,cAAc,sDAAsD,CAAC;AACrE,cAAc,kCAAkC,CAAC;AACjD,cAAc,sCAAsC,CAAC;AACrD,cAAc,yCAAyC,CAAC;AACxD,cAAc,sCAAsC,CAAC;AACrD,cAAc,yCAAyC,CAAC;AAcxD,cAAc,4CAA4C,CAAC;AAC3D,cAAc,mCAAmC,CAAC;AAClD,cAAc,kDAAkD,CAAC;AACjE,cAAc,kEAAkE,CAAC;AACjF,cAAc,6EAA6E,CAAC;AAC5F,cAAc,qEAAqE,CAAC;AACpF,cAAc,0CAA0C,CAAC;AACzD,cAAc,+DAA+D,CAAC;AAC9E,cAAc,uDAAuD,CAAC;AACtE,cAAc,mDAAmD,CAAC;AAClE,cAAc,oDAAoD,CAAC;AACnE,cAAc,qEAAqE,CAAC;AACpF,cAAc,6DAA6D,CAAC;AAC5E,cAAc,0DAA0D,CAAC;AACzE,cAAc,wEAAwE,CAAC;AACvF,cAAc,gEAAgE,CAAC;AAC/E,cAAc,6DAA6D,CAAC;AAC5E,cAAc,uCAAuC,CAAC;AACtD,cAAc,wCAAwC,CAAC;AACvD,cAAc,mCAAmC,CAAC;AAClD,cAAc,wCAAwC,CAAC;AACvD,cAAc,2CAA2C,CAAC;AAC1D,cAAc,8CAA8C,CAAC;AAC7D,cAAc,uCAAuC,CAAC;AACtD,cAAc,oCAAoC,CAAC;AACnD,cAAc,mCAAmC,CAAC;AAClD,cAAc,gDAAgD,CAAC;AAC/D,cAAc,yCAAyC,CAAC;AACxD,cAAc,oCAAoC,CAAC;AACnD,cAAc,uCAAuC,CAAC;AACtD,cAAc,2CAA2C,CAAC;AAC1D,cAAc,0CAA0C,CAAC;AACzD,cAAc,qCAAqC,CAAC;AACpD,cAAc,mDAAmD,CAAC;AAClE,cAAc,wCAAwC,CAAC;AAOvD,cAAc,+BAA+B,CAAC;AAC9C,cAAc,2CAA2C,CAAC;AAC1D,cAAc,6CAA6C,CAAC;AAC5D,cAAc,uCAAuC,CAAC;AACtD,cAAc,kDAAkD,CAAC;AACjE,cAAc,6DAA6D,CAAC;AAC5E,cAAc,qDAAqD,CAAC;AACpE,cAAc,+DAA+D,CAAC;AAC9E,cAAc,kEAAkE,CAAC;AACjF,cAAc,2CAA2C,CAAC;AAC1D,cAAc,sDAAsD,CAAC;AACrE,cAAc,8CAA8C,CAAC;AAC7D,cAAc,iDAAiD,CAAC;AAChE,cAAc,4DAA4D,CAAC;AAC3E,cAAc,oDAAoD,CAAC;AACnE,cAAc,mDAAmD,CAAC;AAClE,cAAc,8DAA8D,CAAC;AAC7E,cAAc,sDAAsD,CAAC;AACrE,cAAc,2DAA2D,CAAC;AAC1E,cAAc,8DAA8D,CAAC;AAC7E,cAAc,+CAA+C,CAAC;AAC9D,cAAc,0DAA0D,CAAC;AACzE,cAAc,kDAAkD,CAAC;AACjE,cAAc,qDAAqD,CAAC;AACpE,cAAc,yDAAyD,CAAC;AACxE,cAAc,+DAA+D,CAAC;AAC9E,cAAc,oDAAoD,CAAC;AACnE,cAAc,uDAAuD,CAAC;AACtE,cAAc,uCAAuC,CAAC;AACtD,cAAc,qDAAqD,CAAC;AACpE,cAAc,0CAA0C,CAAC;AACzD,cAAc,6CAA6C,CAAC;AAC5D,cAAc,iDAAiD,CAAC;AAChE,cAAc,0CAA0C,CAAC;AACzD,cAAc,oCAAoC,CAAC;AACnD,cAAc,uCAAuC,CAAC;AACtD,cAAc,uCAAuC,CAAC;AACtD,cAAc,iDAAiD,CAAC;AAChE,cAAc,mDAAmD,CAAC;AAClE,cAAc,wCAAwC,CAAC;AACvD,cAAc,2CAA2C,CAAC;AAC1D,cAAc,iFAAiF,CAAC"}
|
|
1
|
+
{"version":3,"file":"application-creation.exports.d.ts","sourceRoot":"","sources":["../../../src/application-creation.exports.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqDG;AACH,cAAc,6FAA6F,CAAC;AAC5G,cAAc,gFAAgF,CAAC;AAC/F,cAAc,sEAAsE,CAAC;AACrF,cAAc,uEAAuE,CAAC;AACtF,cAAc,gGAAgG,CAAC;AAC/G,cAAc,4FAA4F,CAAC;AAC3G,cAAc,uGAAuG,CAAC;AAWtH,cAAc,2DAA2D,CAAC;AAC1E,cAAc,iDAAiD,CAAC;AAQhE,cAAc,sDAAsD,CAAC;AAMrE,cAAc,wDAAwD,CAAC;AACvE,cAAc,mDAAmD,CAAC;AAMlE,cAAc,oEAAoE,CAAC;AACnF,cAAc,wEAAwE,CAAC;AACvF,cAAc,+EAA+E,CAAC;AAC9F,cAAc,4DAA4D,CAAC;AAC3E,cAAc,yDAAyD,CAAC;AACxE,cAAc,2DAA2D,CAAC;AAC1E,cAAc,4DAA4D,CAAC;AAC3E,cAAc,8DAA8D,CAAC;AAC7E,cAAc,wEAAwE,CAAC;AACvF,cAAc,6EAA6E,CAAC;AAC5F,cAAc,8DAA8D,CAAC;AAC7E,cAAc,kEAAkE,CAAC;AACjF,cAAc,sDAAsD,CAAC;AACrE,cAAc,6DAA6D,CAAC;AAC5E,cAAc,+DAA+D,CAAC;AAC9E,cAAc,2FAA2F,CAAC;AAK1G,cAAc,gCAAgC,CAAC;AAC/C,cAAc,iCAAiC,CAAC;AAahD,cAAc,sDAAsD,CAAC;AACrE,cAAc,kCAAkC,CAAC;AACjD,cAAc,sCAAsC,CAAC;AACrD,cAAc,yCAAyC,CAAC;AACxD,cAAc,sCAAsC,CAAC;AACrD,cAAc,yCAAyC,CAAC;AACxD,cAAc,4CAA4C,CAAC;AAC3D,cAAc,uDAAuD,CAAC;AACtE,cAAc,+CAA+C,CAAC;AAC9D,cAAc,iCAAiC,CAAC;AAChD,cAAc,yCAAyC,CAAC;AAcxD,cAAc,4CAA4C,CAAC;AAC3D,cAAc,mCAAmC,CAAC;AAClD,cAAc,kDAAkD,CAAC;AACjE,cAAc,kEAAkE,CAAC;AACjF,cAAc,6EAA6E,CAAC;AAC5F,cAAc,qEAAqE,CAAC;AACpF,cAAc,0CAA0C,CAAC;AACzD,cAAc,+DAA+D,CAAC;AAC9E,cAAc,uDAAuD,CAAC;AACtE,cAAc,mDAAmD,CAAC;AAClE,cAAc,oDAAoD,CAAC;AACnE,cAAc,qEAAqE,CAAC;AACpF,cAAc,6DAA6D,CAAC;AAC5E,cAAc,0DAA0D,CAAC;AACzE,cAAc,wEAAwE,CAAC;AACvF,cAAc,gEAAgE,CAAC;AAC/E,cAAc,6DAA6D,CAAC;AAC5E,cAAc,uCAAuC,CAAC;AACtD,cAAc,wCAAwC,CAAC;AACvD,cAAc,mCAAmC,CAAC;AAClD,cAAc,yCAAyC,CAAC;AACxD,cAAc,wCAAwC,CAAC;AACvD,cAAc,2CAA2C,CAAC;AAC1D,cAAc,8CAA8C,CAAC;AAC7D,cAAc,uCAAuC,CAAC;AACtD,cAAc,oCAAoC,CAAC;AACnD,cAAc,mCAAmC,CAAC;AAClD,cAAc,gDAAgD,CAAC;AAC/D,cAAc,yCAAyC,CAAC;AACxD,cAAc,oCAAoC,CAAC;AACnD,cAAc,uCAAuC,CAAC;AACtD,cAAc,2CAA2C,CAAC;AAC1D,cAAc,0CAA0C,CAAC;AACzD,cAAc,qCAAqC,CAAC;AACpD,cAAc,mDAAmD,CAAC;AAClE,cAAc,wCAAwC,CAAC;AAOvD,cAAc,+BAA+B,CAAC;AAC9C,cAAc,2CAA2C,CAAC;AAC1D,cAAc,6CAA6C,CAAC;AAC5D,cAAc,uCAAuC,CAAC;AACtD,cAAc,kDAAkD,CAAC;AACjE,cAAc,6DAA6D,CAAC;AAC5E,cAAc,qDAAqD,CAAC;AACpE,cAAc,+DAA+D,CAAC;AAC9E,cAAc,kEAAkE,CAAC;AACjF,cAAc,2CAA2C,CAAC;AAC1D,cAAc,sDAAsD,CAAC;AACrE,cAAc,8CAA8C,CAAC;AAC7D,cAAc,iDAAiD,CAAC;AAChE,cAAc,4DAA4D,CAAC;AAC3E,cAAc,oDAAoD,CAAC;AACnE,cAAc,mDAAmD,CAAC;AAClE,cAAc,8DAA8D,CAAC;AAC7E,cAAc,sDAAsD,CAAC;AACrE,cAAc,2DAA2D,CAAC;AAC1E,cAAc,8DAA8D,CAAC;AAC7E,cAAc,+CAA+C,CAAC;AAC9D,cAAc,0DAA0D,CAAC;AACzE,cAAc,kDAAkD,CAAC;AACjE,cAAc,qDAAqD,CAAC;AACpE,cAAc,yDAAyD,CAAC;AACxE,cAAc,+DAA+D,CAAC;AAC9E,cAAc,oDAAoD,CAAC;AACnE,cAAc,uDAAuD,CAAC;AACtE,cAAc,uCAAuC,CAAC;AACtD,cAAc,qDAAqD,CAAC;AACpE,cAAc,0CAA0C,CAAC;AACzD,cAAc,6CAA6C,CAAC;AAC5D,cAAc,iDAAiD,CAAC;AAChE,cAAc,0CAA0C,CAAC;AACzD,cAAc,oCAAoC,CAAC;AACnD,cAAc,uCAAuC,CAAC;AACtD,cAAc,uCAAuC,CAAC;AACtD,cAAc,iDAAiD,CAAC;AAChE,cAAc,mDAAmD,CAAC;AAClE,cAAc,wCAAwC,CAAC;AACvD,cAAc,2CAA2C,CAAC;AAC1D,cAAc,iFAAiF,CAAC"}
|
|
@@ -103,6 +103,7 @@ export * from "./_core/compliance-documents/compliance-completeness-statement.sc
|
|
|
103
103
|
export * from "./_core/compliance-documents/document-fact-specification-generation.schemas.js";
|
|
104
104
|
export * from "./_core/compliance-documents/computed-document-facts.schemas.js";
|
|
105
105
|
export * from "./_core/compliance-documents/retention-enforcement-facts.schemas.js";
|
|
106
|
+
export * from "./_core/compliance-documents/launch-blockers.schemas.js";
|
|
106
107
|
export * from "./application-creation/journey.application-creation.schemas.js";
|
|
107
108
|
export * from "./application-creation/playbooks.application-creation.schemas.js";
|
|
108
109
|
export * from "./application-creation/domain-plan-evaluation-identities.application-creation.definitions.js";
|
|
@@ -129,6 +130,11 @@ export * from "./_core/brand/brand-snapshot.schemas.js";
|
|
|
129
130
|
export * from "./_core/brand/brand-visual-tone.schemas.js";
|
|
130
131
|
export * from "./_core/brand/brand-audience.schemas.js";
|
|
131
132
|
export * from "./_core/brand/brand-snapshot-validation.js";
|
|
133
|
+
export * from "./_core/brand/brand-name-screening.schemas.js";
|
|
134
|
+
export * from "./_core/brand/brand-name-screening-generation.schemas.js";
|
|
135
|
+
export * from "./_core/brand/brand-name-screening-validation.js";
|
|
136
|
+
export * from "./_core/brand/brand-name-choice.js";
|
|
137
|
+
export * from "./_core/brand/brand-name-screening-view.js";
|
|
132
138
|
/*
|
|
133
139
|
* The brand and pricing VOCABULARIES the two snapshots above are built from.
|
|
134
140
|
*
|
|
@@ -162,6 +168,7 @@ export * from "./_core/feature-drafts/feature-specification-drafts.schemas.js";
|
|
|
162
168
|
export * from "./_core/feature-specification.schemas.js";
|
|
163
169
|
export * from "./_core/market/market-category.schemas.js";
|
|
164
170
|
export * from "./_core/market/market-icp.schemas.js";
|
|
171
|
+
export * from "./_core/market/market-language-coverage.js";
|
|
165
172
|
export * from "./_core/market/feature-benefit.schemas.js";
|
|
166
173
|
export * from "./_core/market/market-alternative.schemas.js";
|
|
167
174
|
export * from "./_core/market/market-buying-journey.schemas.js";
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"application-creation.exports.js","sourceRoot":"","sources":["../../../src/application-creation.exports.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqDG;AACH,cAAc,6FAA6F,CAAC;AAC5G,cAAc,gFAAgF,CAAC;AAC/F,cAAc,sEAAsE,CAAC;AACrF,cAAc,uEAAuE,CAAC;AACtF,cAAc,gGAAgG,CAAC;AAC/G,cAAc,4FAA4F,CAAC;AAC3G,cAAc,uGAAuG,CAAC;AACtH,2GAA2G;AAC3G;;;;;;;;GAQG;AACH,cAAc,2DAA2D,CAAC;AAC1E,cAAc,iDAAiD,CAAC;AAChE;;;;;;GAMG;AACH,cAAc,sDAAsD,CAAC;AACrE;;;;GAIG;AACH,cAAc,wDAAwD,CAAC;AACvE,cAAc,mDAAmD,CAAC;AAClE;;;;GAIG;AACH,cAAc,oEAAoE,CAAC;AACnF,cAAc,wEAAwE,CAAC;AACvF,cAAc,+EAA+E,CAAC;AAC9F,cAAc,4DAA4D,CAAC;AAC3E,cAAc,yDAAyD,CAAC;AACxE,cAAc,2DAA2D,CAAC;AAC1E,cAAc,4DAA4D,CAAC;AAC3E,cAAc,8DAA8D,CAAC;AAC7E,cAAc,wEAAwE,CAAC;AACvF,cAAc,6EAA6E,CAAC;AAC5F,cAAc,8DAA8D,CAAC;AAC7E,cAAc,kEAAkE,CAAC;AACjF,cAAc,6DAA6D,CAAC;AAC5E,cAAc,+DAA+D,CAAC;AAC9E,cAAc,2FAA2F,CAAC;AAE1G,yEAAyE;AACzE,6EAA6E;AAC7E,6EAA6E;AAC7E,cAAc,gCAAgC,CAAC;AAC/C,cAAc,iCAAiC,CAAC;AAChD;;;;;;;;;;;GAWG;AACH,cAAc,sDAAsD,CAAC;AACrE,cAAc,kCAAkC,CAAC;AACjD,cAAc,sCAAsC,CAAC;AACrD,cAAc,yCAAyC,CAAC;AACxD,cAAc,sCAAsC,CAAC;AACrD,cAAc,yCAAyC,CAAC;AACxD;;;;;;;;;;;;GAYG;AACH,cAAc,4CAA4C,CAAC;AAC3D,cAAc,mCAAmC,CAAC;AAClD,cAAc,kDAAkD,CAAC;AACjE,cAAc,kEAAkE,CAAC;AACjF,cAAc,6EAA6E,CAAC;AAC5F,cAAc,qEAAqE,CAAC;AACpF,cAAc,0CAA0C,CAAC;AACzD,cAAc,+DAA+D,CAAC;AAC9E,cAAc,uDAAuD,CAAC;AACtE,cAAc,mDAAmD,CAAC;AAClE,cAAc,oDAAoD,CAAC;AACnE,cAAc,qEAAqE,CAAC;AACpF,cAAc,6DAA6D,CAAC;AAC5E,cAAc,0DAA0D,CAAC;AACzE,cAAc,wEAAwE,CAAC;AACvF,cAAc,gEAAgE,CAAC;AAC/E,cAAc,6DAA6D,CAAC;AAC5E,cAAc,uCAAuC,CAAC;AACtD,cAAc,wCAAwC,CAAC;AACvD,cAAc,mCAAmC,CAAC;AAClD,cAAc,wCAAwC,CAAC;AACvD,cAAc,2CAA2C,CAAC;AAC1D,cAAc,8CAA8C,CAAC;AAC7D,cAAc,uCAAuC,CAAC;AACtD,cAAc,oCAAoC,CAAC;AACnD,cAAc,mCAAmC,CAAC;AAClD,cAAc,gDAAgD,CAAC;AAC/D,cAAc,yCAAyC,CAAC;AACxD,cAAc,oCAAoC,CAAC;AACnD,cAAc,uCAAuC,CAAC;AACtD,cAAc,2CAA2C,CAAC;AAC1D,cAAc,0CAA0C,CAAC;AACzD,cAAc,qCAAqC,CAAC;AACpD,cAAc,mDAAmD,CAAC;AAClE,cAAc,wCAAwC,CAAC;AACvD;;;;;GAKG;AACH,cAAc,+BAA+B,CAAC;AAC9C,cAAc,2CAA2C,CAAC;AAC1D,cAAc,6CAA6C,CAAC;AAC5D,cAAc,uCAAuC,CAAC;AACtD,cAAc,kDAAkD,CAAC;AACjE,cAAc,6DAA6D,CAAC;AAC5E,cAAc,qDAAqD,CAAC;AACpE,cAAc,+DAA+D,CAAC;AAC9E,cAAc,kEAAkE,CAAC;AACjF,cAAc,2CAA2C,CAAC;AAC1D,cAAc,sDAAsD,CAAC;AACrE,cAAc,8CAA8C,CAAC;AAC7D,cAAc,iDAAiD,CAAC;AAChE,cAAc,4DAA4D,CAAC;AAC3E,cAAc,oDAAoD,CAAC;AACnE,cAAc,mDAAmD,CAAC;AAClE,cAAc,8DAA8D,CAAC;AAC7E,cAAc,sDAAsD,CAAC;AACrE,cAAc,2DAA2D,CAAC;AAC1E,cAAc,8DAA8D,CAAC;AAC7E,cAAc,+CAA+C,CAAC;AAC9D,cAAc,0DAA0D,CAAC;AACzE,cAAc,kDAAkD,CAAC;AACjE,cAAc,qDAAqD,CAAC;AACpE,cAAc,yDAAyD,CAAC;AACxE,cAAc,+DAA+D,CAAC;AAC9E,cAAc,oDAAoD,CAAC;AACnE,cAAc,uDAAuD,CAAC;AACtE,cAAc,uCAAuC,CAAC;AACtD,cAAc,qDAAqD,CAAC;AACpE,cAAc,0CAA0C,CAAC;AACzD,cAAc,6CAA6C,CAAC;AAC5D,cAAc,iDAAiD,CAAC;AAChE,cAAc,0CAA0C,CAAC;AACzD,cAAc,oCAAoC,CAAC;AACnD,cAAc,uCAAuC,CAAC;AACtD,cAAc,uCAAuC,CAAC;AACtD,cAAc,iDAAiD,CAAC;AAChE,cAAc,mDAAmD,CAAC;AAClE,cAAc,wCAAwC,CAAC;AACvD,cAAc,2CAA2C,CAAC;AAC1D,cAAc,iFAAiF,CAAC","sourcesContent":["/**\n * Public application-creation specification surface.\n *\n * This entrypoint is intentionally broader than any individual schema family and narrower than the\n * complete specifications package. Consumers involved in application creation depend on this stable\n * semantic boundary rather than on source-file-shaped package subpaths.\n *\n * ## Most of what this door publishes is re-exported from `_core`, and that is DELIBERATE\n *\n * Measured 2026-09-20: 78 of its 85 re-exports are `_core` content-family modules the package root\n * also publishes (through `./_core`), and only 7 are this domain's own. Counted alone that reads as\n * `root-barrel-overlap` — rule 1, \"a second door onto the same room\" — and #1352 proposed shrinking\n * this door to the 7. **Do not.** Three independent measurements say this door is load-bearing, and\n * each was paid for once already:\n *\n * 1. **It is a CLOSURE FIREWALL.** Fifteen files under `src/` import `@wildo-ai/saas-backend-lib`,\n * and every one of them is reachable from the ROOT and from no path on this door — the whole of\n * `engine/**`, plus `_core/resource-specification.schemas` and `_core/data-seed-specification.schemas`.\n * A consumer whose runner resolves engine packages with `conditions: [\"source\"]` therefore drags\n * that package's INTERNAL `~wildo-backend-lib/*` aliases into a program that cannot resolve them,\n * and every suite importing such a file fails to COLLECT — which reads as zero tests rather than as\n * a bad import. That is recorded at the site where it was measured,\n * `application-creation-workbench/src/artifact-presentation/families/processor-register.presentation.tsx`.\n * This is criterion (c) of `package-public-entrypoints.md` — *\"consumers should not load or become\n * coupled to the package's broader graph\"* — satisfied for a concrete reason, not a stylistic one.\n *\n * 2. **It preserves MODULE IDENTITY.** A symbol reached through two different specifiers is two module\n * instances. The authored-metadata note below records that exact failure: the structured-artifact\n * renderer resolved a different instance of an enum and could not recognise it as the one its own\n * schema referenced. Splitting any consumer's imports between this door and the root — which is what\n * shrinking this door would force on 100 files, 29 of them taking BOTH content and mechanism — would\n * reintroduce it wholesale.\n *\n * 3. **It keeps the Node-only creation runtime off the frontend graph**, which the section further down\n * states at its own call site.\n *\n * ## The alternative was measured too, and it is worse\n *\n * Moving the content families OUT of `_core` and behind this door (so the root stops publishing them and\n * the duplication disappears at the source) is refused by `_core/family-aspects.registry.ts`: it is\n * ROOT-reachable and aggregates families from all three domains — `_core`, `application-creation` AND\n * `assurance`. It already reaches across two of those boundaries; moving the families would take it from\n * 2 crossings to 15, trading a duplication no checker can see for a rule-7 violation that is real.\n *\n * ## Why no checker reports any of this\n *\n * `check:package-entrypoints` rule 1 compares the ONE-LEVEL `export *` target sets of the root barrel and\n * the subpath barrel. The root's targets are `./application-creation.exports`, `./_core`, `./_catalogs`\n * and `./engine`; this door's are `./_core/market/…`-shaped. The sets do not intersect, so the overlap is\n * structurally invisible to it and there is NO baseline row for this specifier — both #1352 and this\n * package's own root barrel asserted there was one. Widening rule 1 to resolve barrels transitively would\n * make it fire HERE, on a door that is correct, so the blind spot is not a defect to fix by widening: a\n * transitive rule 1 would first need to compare CLOSURES rather than path sets.\n */\nexport * from \"./application-creation/application-document-fact-specification.application-creation.schemas\";\nexport * from \"./application-creation/application-creator-inputs.application-creation.schemas\";\nexport * from \"./application-creation/application-line.application-creation.schemas\";\nexport * from \"./application-creation/playbook-instance.application-creation.schemas\";\nexport * from \"./application-creation/application-specification-family-decisions.application-creation.schemas\";\nexport * from \"./application-creation/specification-content-validation-state.application-creation.schemas\";\nexport * from \"./application-creation/application-document-release-policy-specification.application-creation.schemas\";\n// Reviewer custody and private authority lifecycle contracts intentionally share this semantic entrypoint.\n/*\n * The authored-metadata vocabularies (`AuthoredConfidence`, `ReviewCadence`).\n *\n * Every `_core` content family carries an optional `authored` block typed by these two enums, so any\n * consumer that reasons about a family's closed vocabularies needs them from the SAME entrypoint it gets\n * the schemas from. They were reachable only through the package root, which meant the structured-artifact\n * renderer — importing schemas here — resolved a different module instance of the enum and could not\n * recognise it as the one its own schema referenced.\n */\nexport * from \"./_core/application-specification-family-identity.schemas\";\nexport * from \"./_core/market/market-authored-metadata.schemas\";\n/*\n * The EXPERT ROLE vocabulary — the shaping-input kinds a seat declares, and the family/aspect each one\n * names. Exported through this door rather than only through the package root for the reason recorded\n * above the family-identity line: a runtime that composes a seat's context resolves its FAMILIES here,\n * so the binding table that joins a shaping kind to a family has to arrive from the same entrypoint or\n * the two sides compare values from different module instances.\n */\nexport * from \"./_core/expert-personas/expert-role-template.schemas\";\n/*\n * The charter CONTENT and its set validator, beside the role templates for the same reason: the semantic\n * authority binds the `expert-personas` family (#572) through THIS entrypoint, and the application-creation\n * runtime may not import the package root (`check:application-creation-boundaries`).\n */\nexport * from \"./_core/expert-personas/expert-persona-charter.schemas\";\nexport * from \"./_core/expert-personas/expert-persona-validation\";\n/*\n * The governed-document CANDIDATE content family. Exported here because the structured-artifact renderer and\n * the semantic authority both resolve schemas through this entrypoint, and identity across them requires one\n * module instance — the same reason the authored-metadata enums above are published from here.\n */\nexport * from \"./_core/compliance-documents/compliance-document-candidate.schemas\";\nexport * from \"./_core/compliance-documents/compliance-document-candidate-set.schemas\";\nexport * from \"./_core/compliance-documents/compliance-document-candidate-generation.schemas\";\nexport * from \"./_core/compliance-documents/required-document-set.schemas\";\nexport * from \"./_core/compliance-documents/processor-register.schemas\";\nexport * from \"./_core/compliance-documents/recipient-population.schemas\";\nexport * from \"./_core/compliance-documents/recipient-disclosures.schemas\";\nexport * from \"./_core/compliance-documents/subject-data-recipients.schemas\";\nexport * from \"./_core/compliance-documents/compliance-completeness-statement.schemas\";\nexport * from \"./_core/compliance-documents/document-fact-specification-generation.schemas\";\nexport * from \"./_core/compliance-documents/computed-document-facts.schemas\";\nexport * from \"./_core/compliance-documents/retention-enforcement-facts.schemas\";\nexport * from \"./application-creation/journey.application-creation.schemas\";\nexport * from \"./application-creation/playbooks.application-creation.schemas\";\nexport * from \"./application-creation/domain-plan-evaluation-identities.application-creation.definitions\";\n\n// Executable semantic authorities consumed by the Node-only application-\n// creation runtime. Keeping them on this deliberate entrypoint prevents that\n// runtime from loading the broad specifications root and its frontend graph.\nexport * from \"./_core/family-aspects.schemas\";\nexport * from \"./_core/family-aspects.registry\";\n/*\n * The expert-shaping input vocabulary and its family bindings.\n *\n * `application-specification-context-prose` reads `EXPERT_SHAPING_INPUT_FAMILY_BINDINGS` to turn a\n * shaping input KIND into the specification family that answers it, which is exactly the\n * \"executable semantic authority consumed by the runtime\" this section exists for.\n *\n * Only this module of `_core/expert-personas/` is published, deliberately. Its three siblings\n * (`expert-persona-charter`, `expert-persona-authored-metadata`, `expert-persona-validation`) have\n * no import site outside this package — measured, not assumed — so publishing them would widen the\n * entrypoint for nobody.\n */\nexport * from \"./_core/expert-personas/expert-role-template.schemas\";\nexport * from \"./_core/brand/brand-name.schemas\";\nexport * from \"./_core/brand/brand-snapshot.schemas\";\nexport * from \"./_core/brand/brand-visual-tone.schemas\";\nexport * from \"./_core/brand/brand-audience.schemas\";\nexport * from \"./_core/brand/brand-snapshot-validation\";\n/*\n * The brand and pricing VOCABULARIES the two snapshots above are built from.\n *\n * Same reason as the authored-metadata enums at the top of this file, and the same defect one layer\n * further out: `BrandLogoMarkType`, `BrandLogoBackgroundTreatment`, `BrandAsset*` and `PricingModelAxis`\n * were reachable only through the package ROOT, so the structured-artifact renderer — which resolves\n * schemas through THIS entrypoint — could not name the enum objects hanging off the very schemas it had\n * just imported. Measured 2026-08-29: `BrandSnapshot` and `BusinessModelLiteSnapshot` could not derive\n * their enum bindings at all, so neither family could ever land a produced artifact.\n *\n * A schema and the vocabularies it is made of must be published from the same entrypoint. Splitting them\n * is not a smaller surface, it is a surface that cannot be used.\n */\nexport * from \"./_core/brand/brand-logo-direction.schemas\";\nexport * from \"./_core/brand/brand-asset.schemas\";\nexport * from \"./_core/business-model-lite/pricing-plan.schemas\";\nexport * from \"./_core/business-model-lite/business-model-lite-snapshot.schemas\";\nexport * from \"./_core/business-model-lite/business-model-lite-snapshot-generation.schemas\";\nexport * from \"./_core/business-model-lite/business-model-lite-snapshot-validation\";\nexport * from \"./_core/definition-specification.schemas\";\nexport * from \"./_core/domain-plan/domain-plan-output-set-generation.schemas\";\nexport * from \"./_core/domain-plan/domain-plan-output-set-validation\";\nexport * from \"./_core/business-semantics.specifications.schemas\";\nexport * from \"./_core/domain-plan/domain-plan-output-set.schemas\";\nexport * from \"./_core/feature-drafts/capability-map-output-set-generation.schemas\";\nexport * from \"./_core/feature-drafts/capability-map-output-set-validation\";\nexport * from \"./_core/feature-drafts/capability-map-output-set.schemas\";\nexport * from \"./_core/feature-drafts/feature-specification-drafts-generation.schemas\";\nexport * from \"./_core/feature-drafts/feature-specification-drafts-validation\";\nexport * from \"./_core/feature-drafts/feature-specification-drafts.schemas\";\nexport * from \"./_core/feature-specification.schemas\";\nexport * from \"./_core/market/market-category.schemas\";\nexport * from \"./_core/market/market-icp.schemas\";\nexport * from \"./_core/market/feature-benefit.schemas\";\nexport * from \"./_core/market/market-alternative.schemas\";\nexport * from \"./_core/market/market-buying-journey.schemas\";\nexport * from \"./_core/market/market-channel.schemas\";\nexport * from \"./_core/market/market-gain.schemas\";\nexport * from \"./_core/market/market-job.schemas\";\nexport * from \"./_core/market/market-message-template.schemas\";\nexport * from \"./_core/market/market-objection.schemas\";\nexport * from \"./_core/market/market-pain.schemas\";\nexport * from \"./_core/market/market-persona.schemas\";\nexport * from \"./_core/market/market-positioning.schemas\";\nexport * from \"./_core/market/market-references.schemas\";\nexport * from \"./_core/market/market-proof.schemas\";\nexport * from \"./_core/market/market-snapshot-generation.schemas\";\nexport * from \"./_core/market/market-snapshot.schemas\";\n/*\n * The deterministic FIT scorer. Exported through this door because the creation runtime COMPUTES the\n * per-ICP FIT matrix into a playbook brief (#1435): three methods tell their model to \"feed the\n * scorer and read back the scores\", and a structured generation has no tools, so the arithmetic has\n * to be done for it — the same trade `COHERENCE_REPORT` makes.\n */\nexport * from \"./_core/market/market-scoring\";\nexport * from \"./_core/market/market-snapshot-validation\";\nexport * from \"./_core/market/market-tone-of-voice.schemas\";\nexport * from \"./_core/market/market-trigger.schemas\";\nexport * from \"./_core/build-plan/build-plan-task-graph.schemas\";\nexport * from \"./_core/build-plan/build-plan-task-graph-generation.schemas\";\nexport * from \"./_core/build-plan/build-plan-task-graph-validation\";\nexport * from \"./_core/capability-composition/capability-composition.schemas\";\nexport * from \"./_core/capability-composition/capability-composition-validation\";\nexport * from \"./_core/website-plan/website-plan.schemas\";\nexport * from \"./_core/website-plan/website-plan-generation.schemas\";\nexport * from \"./_core/website-plan/website-plan-validation\";\nexport * from \"./_core/experience-plan/experience-plan.schemas\";\nexport * from \"./_core/experience-plan/experience-plan-generation.schemas\";\nexport * from \"./_core/experience-plan/experience-plan-validation\";\nexport * from \"./_core/integration-plan/integration-plan.schemas\";\nexport * from \"./_core/integration-plan/integration-plan-generation.schemas\";\nexport * from \"./_core/integration-plan/integration-plan-validation\";\nexport * from \"./_core/application-maturity/application-maturity.schemas\";\nexport * from \"./_core/application-maturity/application-maturity-validation\";\nexport * from \"./_core/placement-plan/placement-plan.schemas\";\nexport * from \"./_core/placement-plan/placement-plan-generation.schemas\";\nexport * from \"./_core/placement-plan/placement-plan-validation\";\nexport * from \"./_core/requirements/functional-requirement.schemas\";\nexport * from \"./_core/requirements/non-functional-requirement.schemas\";\nexport * from \"./_core/requirements/requirements-snapshot-generation.schemas\";\nexport * from \"./_core/requirements/requirements-snapshot.schemas\";\nexport * from \"./_core/requirements/requirements-snapshot-validation\";\nexport * from \"./_core/roadmap/roadmap-phase.schemas\";\nexport * from \"./_core/roadmap/roadmap-snapshot-generation.schemas\";\nexport * from \"./_core/roadmap/roadmap-snapshot.schemas\";\nexport * from \"./_core/roadmap/roadmap-snapshot-validation\";\nexport * from \"./_core/vision/vision-authored-metadata.schemas\";\nexport * from \"./_core/vision/vision-constraint.schemas\";\nexport * from \"./_core/vision/vision-idea.schemas\";\nexport * from \"./_core/vision/vision-mission.schemas\";\nexport * from \"./_core/vision/vision-problem.schemas\";\nexport * from \"./_core/vision/vision-success-criterion.schemas\";\nexport * from \"./_core/vision/vision-snapshot-generation.schemas\";\nexport * from \"./_core/vision/vision-snapshot.schemas\";\nexport * from \"./_core/vision/vision-snapshot-validation\";\nexport * from \"./application-creation/structured-artifact-landing.application-creation.schemas\";\n"]}
|
|
1
|
+
{"version":3,"file":"application-creation.exports.js","sourceRoot":"","sources":["../../../src/application-creation.exports.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqDG;AACH,cAAc,6FAA6F,CAAC;AAC5G,cAAc,gFAAgF,CAAC;AAC/F,cAAc,sEAAsE,CAAC;AACrF,cAAc,uEAAuE,CAAC;AACtF,cAAc,gGAAgG,CAAC;AAC/G,cAAc,4FAA4F,CAAC;AAC3G,cAAc,uGAAuG,CAAC;AACtH,2GAA2G;AAC3G;;;;;;;;GAQG;AACH,cAAc,2DAA2D,CAAC;AAC1E,cAAc,iDAAiD,CAAC;AAChE;;;;;;GAMG;AACH,cAAc,sDAAsD,CAAC;AACrE;;;;GAIG;AACH,cAAc,wDAAwD,CAAC;AACvE,cAAc,mDAAmD,CAAC;AAClE;;;;GAIG;AACH,cAAc,oEAAoE,CAAC;AACnF,cAAc,wEAAwE,CAAC;AACvF,cAAc,+EAA+E,CAAC;AAC9F,cAAc,4DAA4D,CAAC;AAC3E,cAAc,yDAAyD,CAAC;AACxE,cAAc,2DAA2D,CAAC;AAC1E,cAAc,4DAA4D,CAAC;AAC3E,cAAc,8DAA8D,CAAC;AAC7E,cAAc,wEAAwE,CAAC;AACvF,cAAc,6EAA6E,CAAC;AAC5F,cAAc,8DAA8D,CAAC;AAC7E,cAAc,kEAAkE,CAAC;AACjF,cAAc,sDAAsD,CAAC;AACrE,cAAc,6DAA6D,CAAC;AAC5E,cAAc,+DAA+D,CAAC;AAC9E,cAAc,2FAA2F,CAAC;AAE1G,yEAAyE;AACzE,6EAA6E;AAC7E,6EAA6E;AAC7E,cAAc,gCAAgC,CAAC;AAC/C,cAAc,iCAAiC,CAAC;AAChD;;;;;;;;;;;GAWG;AACH,cAAc,sDAAsD,CAAC;AACrE,cAAc,kCAAkC,CAAC;AACjD,cAAc,sCAAsC,CAAC;AACrD,cAAc,yCAAyC,CAAC;AACxD,cAAc,sCAAsC,CAAC;AACrD,cAAc,yCAAyC,CAAC;AACxD,cAAc,4CAA4C,CAAC;AAC3D,cAAc,uDAAuD,CAAC;AACtE,cAAc,+CAA+C,CAAC;AAC9D,cAAc,iCAAiC,CAAC;AAChD,cAAc,yCAAyC,CAAC;AACxD;;;;;;;;;;;;GAYG;AACH,cAAc,4CAA4C,CAAC;AAC3D,cAAc,mCAAmC,CAAC;AAClD,cAAc,kDAAkD,CAAC;AACjE,cAAc,kEAAkE,CAAC;AACjF,cAAc,6EAA6E,CAAC;AAC5F,cAAc,qEAAqE,CAAC;AACpF,cAAc,0CAA0C,CAAC;AACzD,cAAc,+DAA+D,CAAC;AAC9E,cAAc,uDAAuD,CAAC;AACtE,cAAc,mDAAmD,CAAC;AAClE,cAAc,oDAAoD,CAAC;AACnE,cAAc,qEAAqE,CAAC;AACpF,cAAc,6DAA6D,CAAC;AAC5E,cAAc,0DAA0D,CAAC;AACzE,cAAc,wEAAwE,CAAC;AACvF,cAAc,gEAAgE,CAAC;AAC/E,cAAc,6DAA6D,CAAC;AAC5E,cAAc,uCAAuC,CAAC;AACtD,cAAc,wCAAwC,CAAC;AACvD,cAAc,mCAAmC,CAAC;AAClD,cAAc,yCAAyC,CAAC;AACxD,cAAc,wCAAwC,CAAC;AACvD,cAAc,2CAA2C,CAAC;AAC1D,cAAc,8CAA8C,CAAC;AAC7D,cAAc,uCAAuC,CAAC;AACtD,cAAc,oCAAoC,CAAC;AACnD,cAAc,mCAAmC,CAAC;AAClD,cAAc,gDAAgD,CAAC;AAC/D,cAAc,yCAAyC,CAAC;AACxD,cAAc,oCAAoC,CAAC;AACnD,cAAc,uCAAuC,CAAC;AACtD,cAAc,2CAA2C,CAAC;AAC1D,cAAc,0CAA0C,CAAC;AACzD,cAAc,qCAAqC,CAAC;AACpD,cAAc,mDAAmD,CAAC;AAClE,cAAc,wCAAwC,CAAC;AACvD;;;;;GAKG;AACH,cAAc,+BAA+B,CAAC;AAC9C,cAAc,2CAA2C,CAAC;AAC1D,cAAc,6CAA6C,CAAC;AAC5D,cAAc,uCAAuC,CAAC;AACtD,cAAc,kDAAkD,CAAC;AACjE,cAAc,6DAA6D,CAAC;AAC5E,cAAc,qDAAqD,CAAC;AACpE,cAAc,+DAA+D,CAAC;AAC9E,cAAc,kEAAkE,CAAC;AACjF,cAAc,2CAA2C,CAAC;AAC1D,cAAc,sDAAsD,CAAC;AACrE,cAAc,8CAA8C,CAAC;AAC7D,cAAc,iDAAiD,CAAC;AAChE,cAAc,4DAA4D,CAAC;AAC3E,cAAc,oDAAoD,CAAC;AACnE,cAAc,mDAAmD,CAAC;AAClE,cAAc,8DAA8D,CAAC;AAC7E,cAAc,sDAAsD,CAAC;AACrE,cAAc,2DAA2D,CAAC;AAC1E,cAAc,8DAA8D,CAAC;AAC7E,cAAc,+CAA+C,CAAC;AAC9D,cAAc,0DAA0D,CAAC;AACzE,cAAc,kDAAkD,CAAC;AACjE,cAAc,qDAAqD,CAAC;AACpE,cAAc,yDAAyD,CAAC;AACxE,cAAc,+DAA+D,CAAC;AAC9E,cAAc,oDAAoD,CAAC;AACnE,cAAc,uDAAuD,CAAC;AACtE,cAAc,uCAAuC,CAAC;AACtD,cAAc,qDAAqD,CAAC;AACpE,cAAc,0CAA0C,CAAC;AACzD,cAAc,6CAA6C,CAAC;AAC5D,cAAc,iDAAiD,CAAC;AAChE,cAAc,0CAA0C,CAAC;AACzD,cAAc,oCAAoC,CAAC;AACnD,cAAc,uCAAuC,CAAC;AACtD,cAAc,uCAAuC,CAAC;AACtD,cAAc,iDAAiD,CAAC;AAChE,cAAc,mDAAmD,CAAC;AAClE,cAAc,wCAAwC,CAAC;AACvD,cAAc,2CAA2C,CAAC;AAC1D,cAAc,iFAAiF,CAAC","sourcesContent":["/**\n * Public application-creation specification surface.\n *\n * This entrypoint is intentionally broader than any individual schema family and narrower than the\n * complete specifications package. Consumers involved in application creation depend on this stable\n * semantic boundary rather than on source-file-shaped package subpaths.\n *\n * ## Most of what this door publishes is re-exported from `_core`, and that is DELIBERATE\n *\n * Measured 2026-09-20: 78 of its 85 re-exports are `_core` content-family modules the package root\n * also publishes (through `./_core`), and only 7 are this domain's own. Counted alone that reads as\n * `root-barrel-overlap` — rule 1, \"a second door onto the same room\" — and #1352 proposed shrinking\n * this door to the 7. **Do not.** Three independent measurements say this door is load-bearing, and\n * each was paid for once already:\n *\n * 1. **It is a CLOSURE FIREWALL.** Fifteen files under `src/` import `@wildo-ai/saas-backend-lib`,\n * and every one of them is reachable from the ROOT and from no path on this door — the whole of\n * `engine/**`, plus `_core/resource-specification.schemas` and `_core/data-seed-specification.schemas`.\n * A consumer whose runner resolves engine packages with `conditions: [\"source\"]` therefore drags\n * that package's INTERNAL `~wildo-backend-lib/*` aliases into a program that cannot resolve them,\n * and every suite importing such a file fails to COLLECT — which reads as zero tests rather than as\n * a bad import. That is recorded at the site where it was measured,\n * `application-creation-workbench/src/artifact-presentation/families/processor-register.presentation.tsx`.\n * This is criterion (c) of `package-public-entrypoints.md` — *\"consumers should not load or become\n * coupled to the package's broader graph\"* — satisfied for a concrete reason, not a stylistic one.\n *\n * 2. **It preserves MODULE IDENTITY.** A symbol reached through two different specifiers is two module\n * instances. The authored-metadata note below records that exact failure: the structured-artifact\n * renderer resolved a different instance of an enum and could not recognise it as the one its own\n * schema referenced. Splitting any consumer's imports between this door and the root — which is what\n * shrinking this door would force on 100 files, 29 of them taking BOTH content and mechanism — would\n * reintroduce it wholesale.\n *\n * 3. **It keeps the Node-only creation runtime off the frontend graph**, which the section further down\n * states at its own call site.\n *\n * ## The alternative was measured too, and it is worse\n *\n * Moving the content families OUT of `_core` and behind this door (so the root stops publishing them and\n * the duplication disappears at the source) is refused by `_core/family-aspects.registry.ts`: it is\n * ROOT-reachable and aggregates families from all three domains — `_core`, `application-creation` AND\n * `assurance`. It already reaches across two of those boundaries; moving the families would take it from\n * 2 crossings to 15, trading a duplication no checker can see for a rule-7 violation that is real.\n *\n * ## Why no checker reports any of this\n *\n * `check:package-entrypoints` rule 1 compares the ONE-LEVEL `export *` target sets of the root barrel and\n * the subpath barrel. The root's targets are `./application-creation.exports`, `./_core`, `./_catalogs`\n * and `./engine`; this door's are `./_core/market/…`-shaped. The sets do not intersect, so the overlap is\n * structurally invisible to it and there is NO baseline row for this specifier — both #1352 and this\n * package's own root barrel asserted there was one. Widening rule 1 to resolve barrels transitively would\n * make it fire HERE, on a door that is correct, so the blind spot is not a defect to fix by widening: a\n * transitive rule 1 would first need to compare CLOSURES rather than path sets.\n */\nexport * from \"./application-creation/application-document-fact-specification.application-creation.schemas\";\nexport * from \"./application-creation/application-creator-inputs.application-creation.schemas\";\nexport * from \"./application-creation/application-line.application-creation.schemas\";\nexport * from \"./application-creation/playbook-instance.application-creation.schemas\";\nexport * from \"./application-creation/application-specification-family-decisions.application-creation.schemas\";\nexport * from \"./application-creation/specification-content-validation-state.application-creation.schemas\";\nexport * from \"./application-creation/application-document-release-policy-specification.application-creation.schemas\";\n// Reviewer custody and private authority lifecycle contracts intentionally share this semantic entrypoint.\n/*\n * The authored-metadata vocabularies (`AuthoredConfidence`, `ReviewCadence`).\n *\n * Every `_core` content family carries an optional `authored` block typed by these two enums, so any\n * consumer that reasons about a family's closed vocabularies needs them from the SAME entrypoint it gets\n * the schemas from. They were reachable only through the package root, which meant the structured-artifact\n * renderer — importing schemas here — resolved a different module instance of the enum and could not\n * recognise it as the one its own schema referenced.\n */\nexport * from \"./_core/application-specification-family-identity.schemas\";\nexport * from \"./_core/market/market-authored-metadata.schemas\";\n/*\n * The EXPERT ROLE vocabulary — the shaping-input kinds a seat declares, and the family/aspect each one\n * names. Exported through this door rather than only through the package root for the reason recorded\n * above the family-identity line: a runtime that composes a seat's context resolves its FAMILIES here,\n * so the binding table that joins a shaping kind to a family has to arrive from the same entrypoint or\n * the two sides compare values from different module instances.\n */\nexport * from \"./_core/expert-personas/expert-role-template.schemas\";\n/*\n * The charter CONTENT and its set validator, beside the role templates for the same reason: the semantic\n * authority binds the `expert-personas` family (#572) through THIS entrypoint, and the application-creation\n * runtime may not import the package root (`check:application-creation-boundaries`).\n */\nexport * from \"./_core/expert-personas/expert-persona-charter.schemas\";\nexport * from \"./_core/expert-personas/expert-persona-validation\";\n/*\n * The governed-document CANDIDATE content family. Exported here because the structured-artifact renderer and\n * the semantic authority both resolve schemas through this entrypoint, and identity across them requires one\n * module instance — the same reason the authored-metadata enums above are published from here.\n */\nexport * from \"./_core/compliance-documents/compliance-document-candidate.schemas\";\nexport * from \"./_core/compliance-documents/compliance-document-candidate-set.schemas\";\nexport * from \"./_core/compliance-documents/compliance-document-candidate-generation.schemas\";\nexport * from \"./_core/compliance-documents/required-document-set.schemas\";\nexport * from \"./_core/compliance-documents/processor-register.schemas\";\nexport * from \"./_core/compliance-documents/recipient-population.schemas\";\nexport * from \"./_core/compliance-documents/recipient-disclosures.schemas\";\nexport * from \"./_core/compliance-documents/subject-data-recipients.schemas\";\nexport * from \"./_core/compliance-documents/compliance-completeness-statement.schemas\";\nexport * from \"./_core/compliance-documents/document-fact-specification-generation.schemas\";\nexport * from \"./_core/compliance-documents/computed-document-facts.schemas\";\nexport * from \"./_core/compliance-documents/retention-enforcement-facts.schemas\";\nexport * from \"./_core/compliance-documents/launch-blockers.schemas\";\nexport * from \"./application-creation/journey.application-creation.schemas\";\nexport * from \"./application-creation/playbooks.application-creation.schemas\";\nexport * from \"./application-creation/domain-plan-evaluation-identities.application-creation.definitions\";\n\n// Executable semantic authorities consumed by the Node-only application-\n// creation runtime. Keeping them on this deliberate entrypoint prevents that\n// runtime from loading the broad specifications root and its frontend graph.\nexport * from \"./_core/family-aspects.schemas\";\nexport * from \"./_core/family-aspects.registry\";\n/*\n * The expert-shaping input vocabulary and its family bindings.\n *\n * `application-specification-context-prose` reads `EXPERT_SHAPING_INPUT_FAMILY_BINDINGS` to turn a\n * shaping input KIND into the specification family that answers it, which is exactly the\n * \"executable semantic authority consumed by the runtime\" this section exists for.\n *\n * Only this module of `_core/expert-personas/` is published, deliberately. Its three siblings\n * (`expert-persona-charter`, `expert-persona-authored-metadata`, `expert-persona-validation`) have\n * no import site outside this package — measured, not assumed — so publishing them would widen the\n * entrypoint for nobody.\n */\nexport * from \"./_core/expert-personas/expert-role-template.schemas\";\nexport * from \"./_core/brand/brand-name.schemas\";\nexport * from \"./_core/brand/brand-snapshot.schemas\";\nexport * from \"./_core/brand/brand-visual-tone.schemas\";\nexport * from \"./_core/brand/brand-audience.schemas\";\nexport * from \"./_core/brand/brand-snapshot-validation\";\nexport * from \"./_core/brand/brand-name-screening.schemas\";\nexport * from \"./_core/brand/brand-name-screening-generation.schemas\";\nexport * from \"./_core/brand/brand-name-screening-validation\";\nexport * from \"./_core/brand/brand-name-choice\";\nexport * from \"./_core/brand/brand-name-screening-view\";\n/*\n * The brand and pricing VOCABULARIES the two snapshots above are built from.\n *\n * Same reason as the authored-metadata enums at the top of this file, and the same defect one layer\n * further out: `BrandLogoMarkType`, `BrandLogoBackgroundTreatment`, `BrandAsset*` and `PricingModelAxis`\n * were reachable only through the package ROOT, so the structured-artifact renderer — which resolves\n * schemas through THIS entrypoint — could not name the enum objects hanging off the very schemas it had\n * just imported. Measured 2026-08-29: `BrandSnapshot` and `BusinessModelLiteSnapshot` could not derive\n * their enum bindings at all, so neither family could ever land a produced artifact.\n *\n * A schema and the vocabularies it is made of must be published from the same entrypoint. Splitting them\n * is not a smaller surface, it is a surface that cannot be used.\n */\nexport * from \"./_core/brand/brand-logo-direction.schemas\";\nexport * from \"./_core/brand/brand-asset.schemas\";\nexport * from \"./_core/business-model-lite/pricing-plan.schemas\";\nexport * from \"./_core/business-model-lite/business-model-lite-snapshot.schemas\";\nexport * from \"./_core/business-model-lite/business-model-lite-snapshot-generation.schemas\";\nexport * from \"./_core/business-model-lite/business-model-lite-snapshot-validation\";\nexport * from \"./_core/definition-specification.schemas\";\nexport * from \"./_core/domain-plan/domain-plan-output-set-generation.schemas\";\nexport * from \"./_core/domain-plan/domain-plan-output-set-validation\";\nexport * from \"./_core/business-semantics.specifications.schemas\";\nexport * from \"./_core/domain-plan/domain-plan-output-set.schemas\";\nexport * from \"./_core/feature-drafts/capability-map-output-set-generation.schemas\";\nexport * from \"./_core/feature-drafts/capability-map-output-set-validation\";\nexport * from \"./_core/feature-drafts/capability-map-output-set.schemas\";\nexport * from \"./_core/feature-drafts/feature-specification-drafts-generation.schemas\";\nexport * from \"./_core/feature-drafts/feature-specification-drafts-validation\";\nexport * from \"./_core/feature-drafts/feature-specification-drafts.schemas\";\nexport * from \"./_core/feature-specification.schemas\";\nexport * from \"./_core/market/market-category.schemas\";\nexport * from \"./_core/market/market-icp.schemas\";\nexport * from \"./_core/market/market-language-coverage\";\nexport * from \"./_core/market/feature-benefit.schemas\";\nexport * from \"./_core/market/market-alternative.schemas\";\nexport * from \"./_core/market/market-buying-journey.schemas\";\nexport * from \"./_core/market/market-channel.schemas\";\nexport * from \"./_core/market/market-gain.schemas\";\nexport * from \"./_core/market/market-job.schemas\";\nexport * from \"./_core/market/market-message-template.schemas\";\nexport * from \"./_core/market/market-objection.schemas\";\nexport * from \"./_core/market/market-pain.schemas\";\nexport * from \"./_core/market/market-persona.schemas\";\nexport * from \"./_core/market/market-positioning.schemas\";\nexport * from \"./_core/market/market-references.schemas\";\nexport * from \"./_core/market/market-proof.schemas\";\nexport * from \"./_core/market/market-snapshot-generation.schemas\";\nexport * from \"./_core/market/market-snapshot.schemas\";\n/*\n * The deterministic FIT scorer. Exported through this door because the creation runtime COMPUTES the\n * per-ICP FIT matrix into a playbook brief (#1435): three methods tell their model to \"feed the\n * scorer and read back the scores\", and a structured generation has no tools, so the arithmetic has\n * to be done for it — the same trade `COHERENCE_REPORT` makes.\n */\nexport * from \"./_core/market/market-scoring\";\nexport * from \"./_core/market/market-snapshot-validation\";\nexport * from \"./_core/market/market-tone-of-voice.schemas\";\nexport * from \"./_core/market/market-trigger.schemas\";\nexport * from \"./_core/build-plan/build-plan-task-graph.schemas\";\nexport * from \"./_core/build-plan/build-plan-task-graph-generation.schemas\";\nexport * from \"./_core/build-plan/build-plan-task-graph-validation\";\nexport * from \"./_core/capability-composition/capability-composition.schemas\";\nexport * from \"./_core/capability-composition/capability-composition-validation\";\nexport * from \"./_core/website-plan/website-plan.schemas\";\nexport * from \"./_core/website-plan/website-plan-generation.schemas\";\nexport * from \"./_core/website-plan/website-plan-validation\";\nexport * from \"./_core/experience-plan/experience-plan.schemas\";\nexport * from \"./_core/experience-plan/experience-plan-generation.schemas\";\nexport * from \"./_core/experience-plan/experience-plan-validation\";\nexport * from \"./_core/integration-plan/integration-plan.schemas\";\nexport * from \"./_core/integration-plan/integration-plan-generation.schemas\";\nexport * from \"./_core/integration-plan/integration-plan-validation\";\nexport * from \"./_core/application-maturity/application-maturity.schemas\";\nexport * from \"./_core/application-maturity/application-maturity-validation\";\nexport * from \"./_core/placement-plan/placement-plan.schemas\";\nexport * from \"./_core/placement-plan/placement-plan-generation.schemas\";\nexport * from \"./_core/placement-plan/placement-plan-validation\";\nexport * from \"./_core/requirements/functional-requirement.schemas\";\nexport * from \"./_core/requirements/non-functional-requirement.schemas\";\nexport * from \"./_core/requirements/requirements-snapshot-generation.schemas\";\nexport * from \"./_core/requirements/requirements-snapshot.schemas\";\nexport * from \"./_core/requirements/requirements-snapshot-validation\";\nexport * from \"./_core/roadmap/roadmap-phase.schemas\";\nexport * from \"./_core/roadmap/roadmap-snapshot-generation.schemas\";\nexport * from \"./_core/roadmap/roadmap-snapshot.schemas\";\nexport * from \"./_core/roadmap/roadmap-snapshot-validation\";\nexport * from \"./_core/vision/vision-authored-metadata.schemas\";\nexport * from \"./_core/vision/vision-constraint.schemas\";\nexport * from \"./_core/vision/vision-idea.schemas\";\nexport * from \"./_core/vision/vision-mission.schemas\";\nexport * from \"./_core/vision/vision-problem.schemas\";\nexport * from \"./_core/vision/vision-success-criterion.schemas\";\nexport * from \"./_core/vision/vision-snapshot-generation.schemas\";\nexport * from \"./_core/vision/vision-snapshot.schemas\";\nexport * from \"./_core/vision/vision-snapshot-validation\";\nexport * from \"./application-creation/structured-artifact-landing.application-creation.schemas\";\n"]}
|
|
@@ -174,4 +174,24 @@ export declare function deriveMcpExposureSignal(input: {
|
|
|
174
174
|
ownOperations: number;
|
|
175
175
|
inheritedExposed: number;
|
|
176
176
|
}): DerivedRiskSignal;
|
|
177
|
+
/**
|
|
178
|
+
* Where the brand's chosen NAME stands against its minimal trademark screening.
|
|
179
|
+
*
|
|
180
|
+
* Takes the RAW landed values (brand, screening, market, dossier) and parses them itself, so the companion
|
|
181
|
+
* and the assurance report — the two homes that read this — cannot compute it differently. Standing comes
|
|
182
|
+
* from `deriveBrandNameChoiceStanding`, the same function the coherence report and the brand-name choice use.
|
|
183
|
+
*
|
|
184
|
+
* - The line carries no brand (an internal tool): a COMPUTED absence.
|
|
185
|
+
* - No brand name yet: nothing to be exposed by, and not an absence either — the name is still to come.
|
|
186
|
+
* - Cleared: screened in every declared jurisdiction and class with no conflict found. Still a screening, not
|
|
187
|
+
* a clearance, which the observation says.
|
|
188
|
+
* - Screening incomplete, kept despite a conflict, or never screened: the exposure is PRESENT, with the
|
|
189
|
+
* conflicting marks or the uncovered jurisdictions in `detail`.
|
|
190
|
+
*/
|
|
191
|
+
export declare function deriveBrandNameTrademarkSignal(input: {
|
|
192
|
+
readonly brand: unknown;
|
|
193
|
+
readonly screening: unknown;
|
|
194
|
+
readonly market: unknown;
|
|
195
|
+
readonly creatorInputs: unknown;
|
|
196
|
+
}): DerivedRiskSignal;
|
|
177
197
|
//# sourceMappingURL=application-risk-signals.derivations.d.ts.map
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"application-risk-signals.derivations.d.ts","sourceRoot":"","sources":["../../../../src/assurance/application-risk-signals.derivations.ts"],"names":[],"mappings":"AAAA,OAAO,EAA4B,KAAK,8BAA8B,EAAE,MAAM,uBAAuB,CAAC;
|
|
1
|
+
{"version":3,"file":"application-risk-signals.derivations.d.ts","sourceRoot":"","sources":["../../../../src/assurance/application-risk-signals.derivations.ts"],"names":[],"mappings":"AAAA,OAAO,EAA4B,KAAK,8BAA8B,EAAE,MAAM,uBAAuB,CAAC;AAatG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAoCG;AAEH;;;;GAIG;AACH,oBAAY,cAAc;IACxB,oBAAoB,yBAAyB;IAC7C,2BAA2B,gCAAgC;CAC5D;AAED,wGAAwG;AACxG,MAAM,WAAW,iBAAiB;IAChC,QAAQ,CAAC,OAAO,EAAE,OAAO,CAAC;IAC1B,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;CACvB;AAED;;;;;GAKG;AACH,MAAM,WAAW,iBAAiB;IAChC,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;IAC3B,QAAQ,CAAC,IAAI,EAAE,cAAc,CAAC;IAC9B,QAAQ,CAAC,WAAW,EAAE,MAAM,CAAC;IAC7B,QAAQ,CAAC,UAAU,EAAE;QAAE,QAAQ,CAAC,MAAM,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;QAAC,QAAQ,CAAC,UAAU,CAAC,EAAE,MAAM,CAAA;KAAE,CAAC;IAC3F,kGAAkG;IAClG,QAAQ,CAAC,MAAM,EAAE,OAAO,CAAC;IACzB,QAAQ,CAAC,MAAM,EAAE,OAAO,CAAC;IACzB;;;;;;;OAOG;IACH,QAAQ,CAAC,iBAAiB,EAAE,iBAAiB,GAAG,IAAI,CAAC;CACtD;AAwBD;;;;;;;GAOG;AACH,wBAAgB,sBAAsB,CAAC,KAAK,EAAE;IAAE,WAAW,EAAE,WAAW,CAAC,MAAM,CAAC,CAAC;IAAC,OAAO,EAAE,SAAS,MAAM,EAAE,CAAA;CAAE,GAAG,iBAAiB,CAUjI;AAED;;;;;GAKG;AACH,wBAAgB,qBAAqB,CAAC,KAAK,EAAE;IAAE,eAAe,EAAE,SAAS,MAAM,EAAE,CAAC;IAAC,UAAU,EAAE,SAAS,MAAM,EAAE,CAAA;CAAE,GAAG,iBAAiB,CAYrI;AAED;;;;;;;;;;;;;;;;;;;GAmBG;AACH,wBAAgB,2BAA2B,CAAC,KAAK,EAAE;IACjD,YAAY,EAAE,SAAS,MAAM,EAAE,CAAC;IAChC,UAAU,EAAE,SAAS,MAAM,EAAE,CAAC;IAC9B,UAAU,EAAE,SAAS,MAAM,EAAE,CAAC;CAC/B,GAAG,iBAAiB,CA4BpB;AAED;;;;;;;;;;;;;;;;GAgBG;AACH,wBAAgB,yBAAyB,CAAC,KAAK,EAAE;IAC/C,kBAAkB,EAAE,SAAS,MAAM,EAAE,CAAC;IACtC,aAAa,EAAE,SAAS,MAAM,EAAE,CAAC;IACjC,iBAAiB,EAAE,SAAS,MAAM,EAAE,CAAC;IACrC;;;;OAIG;IACH,UAAU,EAAE,SAAS,8BAA8B,EAAE,CAAC;IACtD,wBAAwB,EAAE,MAAM,CAAC;CAClC,GAAG,SAAS,iBAAiB,EAAE,CA6B/B;AAED;;;;;;;;;;;;;;;GAeG;AACH,wBAAgB,uBAAuB,CAAC,KAAK,EAAE;IAC7C,UAAU,EAAE,MAAM,CAAC;IACnB,aAAa,EAAE,MAAM,CAAC;IACtB,gBAAgB,EAAE,MAAM,CAAC;CAC1B,GAAG,iBAAiB,CAiBpB;AAED;;;;;;;;;;;;;GAaG;AACH,wBAAgB,8BAA8B,CAAC,KAAK,EAAE;IACpD,QAAQ,CAAC,KAAK,EAAE,OAAO,CAAC;IACxB,QAAQ,CAAC,SAAS,EAAE,OAAO,CAAC;IAC5B,QAAQ,CAAC,MAAM,EAAE,OAAO,CAAC;IACzB,QAAQ,CAAC,aAAa,EAAE,OAAO,CAAC;CACjC,GAAG,iBAAiB,CA4DpB"}
|