@wildo-ai/framework-knowledge 1.1.12 → 1.1.14
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/claude-marketplace/.claude-plugin/marketplace.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +12 -4
- package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +4 -0
- package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +10 -0
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +8 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
- package/dist/knowledge/manifest.json +7 -7
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +6 -0
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +6 -3
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +9 -0
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +1 -1
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +11 -2
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +14 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +1 -1
- package/dist/knowledge/references/application-maturity.config.md +43 -0
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +6 -0
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +5 -1
- package/dist/knowledge/references/example.backend.custom-operation.declared-refusal-code.md +6 -0
- package/dist/knowledge/references/example.config.navigation.full.md +14 -0
- package/dist/knowledge/references/example.infra.environment-config.local.md +2 -2
- package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +21 -0
- package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +1 -1
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +8 -2
- package/dist/knowledge/references/platform.config.environment.deployment.md +60 -4
- package/dist/knowledge/references/platform.config.infrastructure-host.md +1 -0
- package/dist/knowledge/references/platform.config.platform-key-management.md +5 -2
- package/dist/knowledge/references/requirements.engine-substance.md +38 -0
- package/dist/knowledge/references/requirements.functional-requirement.config.md +11 -0
- package/dist/knowledge/references/requirements.non-functional-requirement.config.md +11 -0
- package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +20 -0
- package/dist/knowledge/references/saas.backend.custom-operation.hook-transaction-posture.md +12 -1
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +72 -0
- package/dist/knowledge/references/saas.backend.system-access-service.md +30 -1
- package/dist/knowledge/references/saas.frontend.app-shell.shell-motion-contract.md +30 -0
- package/dist/knowledge/references/saas.frontend.chart-dashboard-view.md +3 -3
- package/dist/knowledge/references/saas.frontend.chart-dashboard.md +38 -35
- package/dist/knowledge/references/saas.models.chart-dashboard-tile-sizes.md +40 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-content-guardrails-environment.md +52 -0
- package/dist/knowledge/references/saas.models.frontend-provider-public-config-contract.md +6 -0
- package/dist/knowledge/references/saas.models.organization-dashboard-layout.md +61 -0
- package/dist/knowledge/references/saas.models.privacy.data-residency.md +188 -31
- package/dist/knowledge/references/saas.models.providers.compliance-choice.md +9 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-condition-parameters.md +8 -1
- package/dist/knowledge/references/saas.specifications.processor-register.md +10 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +41 -1
- package/dist/knowledge/registries/playbooks.json +1 -1
- package/dist/knowledge/registries/source-tags.json +1147 -1077
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +5 -1
- package/dist/knowledge/skills/backend-custom-operation/references/declared-refusal-codes.md +28 -1
- package/dist/knowledge/skills/backend-custom-operation/references/framework-hook-transaction-posture-api.md +32 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +11 -2
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +16 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +197 -31
- package/dist/knowledge/skills/config-app-shell/references/framework-shell-layout-api.md +30 -0
- package/dist/knowledge/skills/config-navigation/SKILL.md +14 -0
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +19 -0
- package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +58 -1
- package/dist/knowledge/skills/electronic-signature-deliverables/references/what-makes-a-request-signed.md +20 -3
- package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +12 -2
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +16 -4
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +144 -6
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +72 -0
- package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +12 -2
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +12 -2
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +1 -1
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +3 -2
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +13 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +36 -8
- package/dist/knowledge/skills/infra-environment-config/references/framework-agent-content-guardrails-environment-api.md +67 -0
- package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +60 -4
- package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +1 -0
- package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +5 -2
- package/dist/knowledge/skills/layout-2d-adoption/references/framework-shell-motion-api.md +30 -0
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +17 -3
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-public-config-api.md +6 -0
- package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +4 -1
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +6 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +4 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +21 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +30 -1
- package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +3 -2
- package/dist/knowledge/skills/resource-status-lifecycle/references/framework-operation-condition-parameters-api.md +8 -1
- package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +3 -3
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +8 -2
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +5 -1
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +1 -1
- package/dist/knowledge/skills/views-composite-authoring/references/framework-chart-dashboard-api.md +166 -39
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +6 -0
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +6 -0
- package/dist/knowledge/topic-index.json +292 -153
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/package.json +4 -4
|
@@ -64,7 +64,8 @@ export declare const playbookDefinition: {
|
|
|
64
64
|
};
|
|
65
65
|
}, {
|
|
66
66
|
readonly ref: "operating-entity";
|
|
67
|
-
readonly
|
|
67
|
+
readonly nonAnswers: readonly [MetaWorkflow_ElicitationNonAnswer.DEFERRED];
|
|
68
|
+
readonly question: "Which legal entity operates this service? Give the parts you know, each on its own line (or separated by `;`) and labelled: `name: <registered company name>`, `address: <registered address>`, `privacy contact: <the email, URL or postal address a person uses to reach you about privacy>`. Answer only the parts you actually know today — anything you leave out is recorded as outstanding and nothing is blocked by it. If you know none of them yet (no company exists), defer the question rather than answer it. Do NOT supply a placeholder or a plausible-looking value: a produced privacy notice quotes these as fact, and the address is what a person would use to serve a legal request on a real company.";
|
|
68
69
|
readonly kind: "free_text";
|
|
69
70
|
readonly answerFormat: MetaWorkflow_ElicitationAnswerFormat.OPERATOR_IDENTITY_PARTS;
|
|
70
71
|
readonly depth: "essential";
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.foundation/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,OAAO,EAAE,4BAA4B,EAAE,MAAM,oDAAoD,CAAC;AAClG,OAAO,EAAE,oCAAoC,EAAE,iCAAiC,EAAE,MAAM,sCAAsC,CAAC;AAE/H,eAAO,MAAM,kBAAkB
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.foundation/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,OAAO,EAAE,4BAA4B,EAAE,MAAM,oDAAoD,CAAC;AAClG,OAAO,EAAE,oCAAoC,EAAE,iCAAiC,EAAE,MAAM,sCAAsC,CAAC;AAE/H,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAmRrB,CAAC"}
|
|
@@ -173,7 +173,14 @@ export const playbookDefinition = {
|
|
|
173
173
|
*/
|
|
174
174
|
{
|
|
175
175
|
"ref": "operating-entity",
|
|
176
|
-
|
|
176
|
+
/*
|
|
177
|
+
* DEFERRED, for the creator who knows none of the three parts yet: no company is incorporated (#3204). The
|
|
178
|
+
* labelled grammar needs at least one part, so without a non-answer that creator could not answer at all and the
|
|
179
|
+
* foundation waited on them, while the question promises that nothing is blocked by a part left out. Reference run
|
|
180
|
+
* 43207965509 stopped there. A deferral writes nothing and travels as the advisory an unanswered question does.
|
|
181
|
+
*/
|
|
182
|
+
nonAnswers: [MetaWorkflow_ElicitationNonAnswer.DEFERRED],
|
|
183
|
+
"question": "Which legal entity operates this service? Give the parts you know, each on its own line (or separated by `;`) and labelled: `name: <registered company name>`, `address: <registered address>`, `privacy contact: <the email, URL or postal address a person uses to reach you about privacy>`. Answer only the parts you actually know today — anything you leave out is recorded as outstanding and nothing is blocked by it. If you know none of them yet (no company exists), defer the question rather than answer it. Do NOT supply a placeholder or a plausible-looking value: a produced privacy notice quotes these as fact, and the address is what a person would use to serve a legal request on a real company.",
|
|
177
184
|
"kind": "free_text",
|
|
178
185
|
answerFormat: MetaWorkflow_ElicitationAnswerFormat.OPERATOR_IDENTITY_PARTS,
|
|
179
186
|
"depth": "essential",
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.foundation/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,OAAO,EAAE,4BAA4B,EAAE,MAAM,oDAAoD,CAAC;AAClG,OAAO,EAAE,oCAAoC,EAAE,iCAAiC,EAAE,MAAM,sCAAsC,CAAC;AAE/H,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,sBAAsB;IAC7B,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,gsCAAgsC;IAC1sC,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,aAAa,EAAE,EAAE;QACtE;;;;;;;;;;;;WAYG;QACH,EAAE,MAAM,EAAE,mBAAmB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,cAAc,EAAE,EAAE;QACzE;;;;;;;;;;;;;;;;;;;;;;;;WAwBG;QACH,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,kBAAkB,EAAE,EAAE;QAC3E;;;;;;WAMG;QACH,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,wBAAwB,EAAE,EAAE;KAClF;IACD;;;;;;;;;;;;;;;OAeG;IACH,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,aAAa,EAAE;QAC3B,EAAE,QAAQ,EAAE,gBAAgB,EAAE;QAC9B;;;;;;WAMG;QACH,EAAE,QAAQ,EAAE,wBAAwB,EAAE;QACtC;;;;;;WAMG;QACH,EAAE,QAAQ,EAAE,kBAAkB,EAAE;KACjC;IACD,SAAS,EAAE,EAAE;IACb,QAAQ,EAAE;QACR,WAAW,EAAE;YACX,aAAa;YACb,qBAAqB;YACrB,0BAA0B;YAC1B,6BAA6B;YAC7B,iCAAiC;SAClC;QACD;;;;;;;;;;;;WAYG;QACH,oBAAoB,EAAE;YACpB,EAAE,aAAa,EAAE,6BAA6B,EAAE,aAAa,EAAE,kBAAkB,EAAE;SACpF;QACD,aAAa,EAAE;YACb,WAAW,EAAE;gBACX;;;;;;;;;mBASG;gBACH;oBACE,KAAK,EAAE,eAAe;oBACtB,UAAU,EAAE,4MAA4M;oBACxN,MAAM,EAAE,QAAQ;oBAChB,SAAS,EAAE,CAAC,eAAe,EAAE,OAAO,CAAC;oBACrC,OAAO,EAAE,WAAW;oBACpB;;;;uBAIG;oBACH,gBAAgB,EAAE,EAAE,aAAa,EAAE,uBAAuB,EAAE,aAAa,EAAE,SAAS,EAAE;iBACvF;gBACD;;;;;;;;;;;;;;;;;;;mBAmBG;gBACH;oBACE,KAAK,EAAE,kBAAkB;oBACzB,UAAU,EAAE,kmBAAkmB;oBAC9mB,MAAM,EAAE,WAAW;oBACnB,YAAY,EAAE,oCAAoC,CAAC,uBAAuB;oBAC1E,OAAO,EAAE,WAAW;oBACpB,aAAa,EAAE,KAAK;oBACpB,iBAAiB,EAAE,IAAI;iBACxB;gBACD;oBACE,KAAK,EAAE,yBAAyB;oBAChC,UAAU,EAAE,CAAC,iCAAiC,CAAC,QAAQ,CAAC;oBACxD,UAAU,EAAE,qhBAAqhB;oBACjiB,MAAM,EAAE,WAAW;oBACnB,YAAY,EAAE,oCAAoC,CAAC,uBAAuB;oBAC1E,OAAO,EAAE,WAAW;oBACpB,iBAAiB,EAAE,IAAI;iBACxB;gBACD;;;;;;;;;;;;;;;;;mBAiBG;gBACH;oBACE,KAAK,EAAE,4BAA4B;oBACnC,UAAU,EAAE,CAAC,iCAAiC,CAAC,QAAQ,CAAC;oBACxD,UAAU,EAAE,0cAA0c;oBACtd,MAAM,EAAE,WAAW;oBACnB,YAAY,EAAE,oCAAoC,CAAC,0BAA0B;oBAC7E,OAAO,EAAE,QAAQ;oBACjB,iBAAiB,EAAE,IAAI;iBACxB;gBACD;;;;;;;;;;;;;;;mBAeG;gBACH;oBACE,KAAK,EAAE,kBAAkB;oBACzB,UAAU,EAAE,CAAC,iCAAiC,CAAC,cAAc,EAAE,iCAAiC,CAAC,QAAQ,CAAC;oBAC1G,UAAU,EAAE,8JAA8J;oBAC1K,MAAM,EAAE,QAAQ;oBAChB,SAAS,EAAE,CAAC,QAAQ,EAAE,MAAM,CAAC;oBAC7B,OAAO,EAAE,QAAQ;iBAClB;gBACD;oBACE,KAAK,EAAE,cAAc;oBACrB,UAAU,EAAE,CAAC,iCAAiC,CAAC,cAAc,EAAE,iCAAiC,CAAC,QAAQ,CAAC;oBAC1G,UAAU,EAAE,+KAA+K;oBAC3L,MAAM,EAAE,QAAQ;oBAChB,SAAS,EAAE,CAAC,QAAQ,EAAE,MAAM,CAAC;oBAC7B,OAAO,EAAE,QAAQ;iBAClB;gBACD;;;;;;;;;;;mBAWG;gBACH;oBACE,KAAK,EAAE,oBAAoB;oBAC3B,UAAU,EAAE,CAAC,iCAAiC,CAAC,QAAQ,CAAC;oBACxD,UAAU,EAAE,4YAA4Y;oBACxZ,MAAM,EAAE,QAAQ;oBAChB,SAAS,EAAE,CAAC,4BAA4B,CAAC,+BAA+B,EAAE,4BAA4B,CAAC,iBAAiB,EAAE,4BAA4B,CAAC,IAAI,CAAC;oBAC5J,OAAO,EAAE,QAAQ;iBAClB;aACF;SACF;KACF;IACC,UAAU,EAAE,gBAAgB;IAC9B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * The structured method remains intentionally rich: its intent, inputs, output\n * contracts, elicitation, deterministic verification and skill routing are the\n * application knowledge a later generic assessment loop composes. This source\n * intentionally omits the superseded per-playbook evaluation-treatment object;\n * generation records that absence rather than fabricating legacy judge behavior.\n */\nimport { ApplicationCorporateIdentity } from '@wildo-ai/saas-specifications/application-creation';\nimport { MetaWorkflow_ElicitationAnswerFormat, MetaWorkflow_ElicitationNonAnswer } from '@wildo-ai/saas-models/meta-workflows';\n\nexport const playbookDefinition =\n{\n \"ref\": \"bottom_up.foundation\",\n \"version\": \"0.5.0\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Bottom-up foundation \\u2014 turn the approved domain plan and top-down definitions into a configured, bootable application skeleton. For a fresh application, use wildo init in an empty destination before refining its generated configuration; preserve existing projects and use their repair/composition paths. Author capabilities, modules and providers from the approved plan, verify application knowledge delivery (wildo assets sync refreshes installed assets), then run wildo setup --non-interactive and wildo local init with their prerequisites. These tools exist; their successful invocation and postconditions must be observed in the current run. The registered foundation executor composes module/resource shells and tenancy configuration; it does not run this full init/assets/setup sequence. This methodology states the prerequisites and postconditions to fulfil around that execution. It emits no artifact: the deliverable is the application source, configured module registrations and verified initialization. Record the reasons for configuration choices beside those choices. Runs after the domain plan is approved in the bottom_up phase; business resource implementation belongs to the later build work.\",\n \"preconditions\": [\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"domain-plan\" } },\n /*\n * SEQUENCING, not readiness (#1434). `artifact_exists` asserts this playbook needs the vision's\n * CONTENT, and it does not read a word of it: the run short-circuits into the foundation\n * executor before any brief is composed, and the executor reads the domain plan and the landed\n * business model. The audit rule that reports a readiness gate whose family is undeclared named\n * both remedies — declare it, or weaken the gate \"if the order is all that matters\" — and here\n * the order is all that matters.\n *\n * Nothing is lost by weakening it. The vision is enforced TRANSITIVELY and harder than this gate\n * ever did: `top_down.market-snapshot-produce` and `top_down.requirements-definition` both gate\n * on `vision-brief` at readiness, and `bottom_up.domain-plan` gates on both of those — so an\n * approved domain plan, which this playbook DOES require at readiness, cannot exist without one.\n */\n { \"kind\": \"artifact_expected\", \"selector\": { \"family\": \"vision-brief\" } },\n /*\n * CONTENT, not sequencing — and this gate is why (#1544).\n *\n * `appendBackgroundExecutionScenarios` composes one `add-worker-node` / `add-worker-rust` /\n * `add-minion` per surface the INTEGRATION PLAN declares, deriving every variable from that\n * declaration. It reads the plan leniently on purpose: absent or unparseable means the\n * application declares nothing to run beside its backend, which is the ordinary case. That\n * leniency is correct and stays — what it cannot do is tell \"declares nothing\" from \"has not\n * been produced yet\", and both come back as silence.\n *\n * Measured on the first end-to-end run: this playbook ran at 06:58:03 and concluded three\n * seconds later; `bottom_up.integration-plan` started at 06:58:47 — 44 seconds AFTER — and\n * declared one minion, `minion-compose-weekly-team-digest`. Nothing was composed. The build\n * decomposer then emitted `build-task-weekly-digest-minion` against a package that no step\n * would ever create, and nine hours later there was still no `minions/` directory and\n * `applicationMinions = {}`.\n *\n * `artifact_exists` rather than `artifact_expected`, by the distinction the vision gate above\n * draws: this playbook reads the plan's CONTENT, not merely its position in the order.\n *\n * Safe to gate on. The integration-plan playbook produces a plan for every application,\n * `workers: []` and `minions: []` included — an application with no background execution is a\n * plan that says so, not an absent one. So this cannot make the foundation permanently\n * ineligible; it can only hold it until the answer exists.\n */\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"integration-plan\" } },\n /*\n * The same gate for the same reason, one input over. `capability-composition` decides which\n * scenarios are NEEDED — the loop above it throws when a scenario is marked needed and the\n * foundation has no invocation for it — so composing before it lands composes from an empty\n * decision set, silently and with the same shape. Not measured failing; gated because it is the\n * same invariant at its other site (`invariant-call-site-enumeration.md`).\n */\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"capability-composition\" } }\n ],\n /*\n * TWO, measured rather than aspirational (#1434) — THREE since #1491, see the third entry.\n *\n * This playbook does not compose a brief at all: `executePlaybookRun` short-circuits it into the\n * foundation executor before any section is composed, so a declared input reaches no model. The\n * executor reads the domain plan (handed to it) and the landed business model (read itself), and\n * derives the three capabilities that are derivable from those two values.\n *\n * `vision-brief`, `market-snapshot`, `requirements` and `roadmap` were declared and reached\n * nothing — while the method told a reader that the vision's compliance constraints were \"the\n * primary driver of capability selection\". A declaration nothing reads is a promise nothing\n * keeps, and four of the six were exactly that.\n *\n * `vision-brief` stays a PRECONDITION, which is a different statement: the foundation must not run\n * before a vision exists, and that gate is real whether or not anything reads its content here.\n */\n \"inputs\": [\n { \"family\": \"domain-plan\" },\n { \"family\": \"business-model\" },\n /*\n * THIRD, since #1491: which optional packages (the website, the documentation portal) this\n * application needs, decided by `bottom_up.capability-composition` and applied here after the\n * domain scenarios. An INPUT, not a precondition, for the same reason as the business model: a\n * foundation run with no composition yet composes the domain and applies no optional package,\n * and the executor reads it through the `capabilityComposition` slot rather than a brief.\n */\n { \"family\": \"capability-composition\" },\n /*\n * FOURTH, since #1495: what runs beside the backend. The executor fans one `add-worker-node`,\n * `add-worker-rust` or `add-minion` out of this plan per surface it declares — the same shape as\n * the module and resource fan-out, and an INPUT for the same reason as the two above: a run with\n * no integration plan composes no background package, and a plan landing later re-stales this\n * step rather than gating it.\n */\n { \"family\": \"integration-plan\" }\n ],\n \"outputs\": [],\n \"method\": {\n \"skillRefs\": [\n \"config-saas\",\n \"module-registration\",\n \"infra-environment-config\",\n \"local-environment-bootstrap\",\n \"application-database-migrations\"\n ],\n /*\n * The application's LINE (#3270): the executor reads it on every run (`resolveApplicationLineDeclaration`). It decides\n * whether one organization owns the application, the line's access posture and the organization identity\n * declaration. The interview asks it in `top_down.vision-elicitation`, and the line answers none of THIS interview's\n * questions on a B2B line, so nothing dated the foundation by it: a line changed after the foundation landed left the\n * foundation CURRENT, and the configuration kept the old posture until a person ran it by hand. Declared here, the\n * line answer dates the foundation like one of its own answers, and its REFRESH says \"the application line\".\n *\n * The ACCEPTED BRAND is read too and is deliberately NOT declared: the foundation copies the brand only into a surface\n * it composes in that run, and every later accept of a mark propagates to every surface that exists\n * (`propagateAcceptedBrand`). A re-run after a new mark would copy nothing, so dating the foundation by the brand would\n * spend a run that changes no file. The corporate-identity answer is this interview's own question, dated as such.\n */\n \"derivedFromAnswers\": [\n { \"playbookRef\": \"top_down.vision-elicitation\", \"questionRef\": \"application-line\" }\n ],\n \"elicitation\": {\n \"questions\": [\n /*\n * THE FALLBACK, since 2026-08-28. `bottom_up.domain-plan` now asks this and carries the\n * answer in the committed plan (`DomainPlanOutputSet.tenancy`), because the plan MODELS\n * tenancy — wonder-crm's invented a workspace module and a membership before anyone was\n * asked — so asking after the model is shaped lets a second answer contradict it.\n *\n * The executor reads the plan first and reaches this question only for a plan authored\n * before the field existed. Keep it: those plans are real (wonder-crm, wonder-todos) and\n * must stay composable.\n */\n {\n \"ref\": \"primary-scope\",\n \"question\": \"Do people use this application together, in shared workspaces or teams, or does each person only see their own data? Choose organizations if they work together, users if each person's data is their own.\",\n \"kind\": \"choice\",\n \"options\": [\"organizations\", \"users\"],\n \"depth\": \"essential\",\n /*\n * ONE decision, asked once (#1454, gap 4): the domain plan's tenancy question owns it, and\n * this fallback reads that answer. The dossier listed the two as separate open questions,\n * worded differently, for the same choice.\n */\n \"sameDecisionAs\": { \"playbookRef\": \"bottom_up.domain-plan\", \"questionRef\": \"tenancy\" }\n },\n /*\n * The operator's own legal identity (issue #235), asked HERE because this is the playbook that\n * writes `wildo.saas.config.ts` and already carries the `config-saas` skill — an answer\n * elicited anywhere else would have nowhere to land, since a companion-agent playbook produces\n * an artifact and writes no files.\n *\n * WRITTEN by the executor since the #2294 follow-up (2026-11-10). Both answers follow a grammar the interview\n * holds them to at every door (`MetaWorkflow_ElicitationAnswerFormat.OPERATOR_IDENTITY_PARTS` and\n * `.OPERATING_JURISDICTIONS`), so the foundation executor writes them deterministically: the stated parts into\n * `operatorComplianceIdentity`, the jurisdictions into `operatingJurisdictions`. It never overwrites a value the\n * configuration already authors (a differing one is reported, not replaced), and an unanswered question writes\n * nothing and travels on the run result as an advisory. Until then the executor read neither answer and the\n * dossier was their only reader (#1454, #1434): the method described an agent writing them, and no agent ran.\n *\n * Both questions are deliberately ANSWERABLE IN PART. Every part of\n * `operatorComplianceIdentity` is independently declarable (#228), so a creator who knows the\n * registered name and not the lawful bases records the name — and Paul's decision (#225) is\n * explicit that filling the entity must never block. A question that demanded the whole thing\n * would reintroduce the blocking this lane just removed, one layer up.\n */\n {\n \"ref\": \"operating-entity\",\n \"question\": \"Which legal entity operates this service? Give the parts you know, each on its own line (or separated by `;`) and labelled: `name: <registered company name>`, `address: <registered address>`, `privacy contact: <the email, URL or postal address a person uses to reach you about privacy>`. Answer only the parts you actually know today — anything you leave out is recorded as outstanding and nothing is blocked by it. Do NOT supply a placeholder or a plausible-looking value: a produced privacy notice quotes these as fact, and the address is what a person would use to serve a legal request on a real company.\",\n \"kind\": \"free_text\",\n answerFormat: MetaWorkflow_ElicitationAnswerFormat.OPERATOR_IDENTITY_PARTS,\n \"depth\": \"essential\",\n \"whenUnknown\": \"ask\",\n \"regulatedDomain\": true\n },\n {\n \"ref\": \"operating-jurisdictions\",\n nonAnswers: [MetaWorkflow_ElicitationNonAnswer.DEFERRED],\n \"question\": \"Which jurisdictions does this application operate in, and why does each one reach it — are you established there, do you sell there, or do you hold data about people there? Give one per line (or separated by `;`), each as `<code>: <why>`, using country codes (`fr`, `us`), the supranational `eu`, or a subdivision (`us-ca`): for example `fr: established here; eu: customers resident here`. If the market is genuinely unsettled, defer the question rather than answer it; an absent answer is read as unanswered, never as \\\"nowhere\\\".\",\n \"kind\": \"free_text\",\n answerFormat: MetaWorkflow_ElicitationAnswerFormat.OPERATING_JURISDICTIONS,\n \"depth\": \"essential\",\n \"regulatedDomain\": true\n },\n /*\n * WHERE the application's data may be processed, as places the framework compares (#2294). The executor writes\n * the answer into `operatorComplianceIdentity.dataResidency`, and with it a processing region for every\n * data-serving provider the residency leaves exactly one region for; a provider with several regions inside, none,\n * or a deployment model to choose stays unplaced and is named in the run result and in `wildo context\n * launch-blockers`. The residency is written only once every data-serving provider is placed inside it, because\n * `wildo config sync` refuses a declared residency that leaves one unplaced: written early, it would stop the\n * application starting, which is the mechanism blocking on a decision rather than marking it.\n *\n * `top_down.compliance-analysis` asks the REQUIREMENT in the creator's words (`data-residency`), which is what the\n * regime research reads; this asks the same decision as places, which no prose can stand in for. Not a\n * `sameDecisionAs`: one is prose and the other a typed value, and one answer cannot satisfy both. DETAIL with the\n * default proposal policy, so a simple interview proposes it from that prose answer, and `regulatedDomain` names the\n * proposal to the person before it is kept.\n *\n * `none` declares no residency (nothing is refused, and the documents say none is declared). DEFERRED leaves it\n * open, and the run says so.\n */\n {\n \"ref\": \"data-residency-territories\",\n nonAnswers: [MetaWorkflow_ElicitationNonAnswer.DEFERRED],\n \"question\": \"Must this application's data stay inside named places? List them as jurisdiction codes separated by commas: a country (`de`, `fr`, `ch`), the supranational `eu`, or a subdivision (`us-ca`); the EEA is `eu, is, li, no`. Every provider that processes the data must then process inside them, so the framework chooses each provider's region where only one fits and names the providers where you must choose. Answer `none` if the data may be processed anywhere.\",\n \"kind\": \"free_text\",\n answerFormat: MetaWorkflow_ElicitationAnswerFormat.JURISDICTION_SLUGS_OR_NONE,\n \"depth\": \"detail\",\n \"regulatedDomain\": true\n },\n /*\n * The creator's PROVIDER choices (#1488). Which vendor an application charges or texts through is\n * a class-3 product decision — the field does not converge on one answer — so it is asked, as a\n * typed CHOICE, and the answer is kept in the dossier and read by the foundation executor, which\n * declares the provider, selects it as primary and enables the capability. The credentials the\n * provider needs are recorded as OWED on the run result: the boot floor reads declaration and\n * selection, never secrets, so the application boots and the provider answers once they are set.\n *\n * The OPTIONS are the engine providers serving the capability (ENGINE origin, backend scope), and\n * `foundation-executor.companion.service.test.ts` pins these authored lists to that derivation plus the\n * `none` member, so a vendor added to the catalogue fails the pin until it is offered here.\n *\n * `none` is an OPTION, not an absence: the elicitation contract refuses a run whose interview is not\n * fully answered, and a CHOICE accepts only its options, so \"decide later\" has to be sayable. It leaves\n * the capability owed exactly as before (#1272).\n */\n {\n \"ref\": \"billing-provider\",\n nonAnswers: [MetaWorkflow_ElicitationNonAnswer.NOT_APPLICABLE, MetaWorkflow_ElicitationNonAnswer.DEFERRED],\n \"question\": \"Which billing provider should this application charge its users through? Answer `none` to decide later; the capability stays off until a provider is chosen.\",\n \"kind\": \"choice\",\n \"options\": [\"stripe\", \"none\"],\n \"depth\": \"detail\"\n },\n {\n \"ref\": \"sms-provider\",\n nonAnswers: [MetaWorkflow_ElicitationNonAnswer.NOT_APPLICABLE, MetaWorkflow_ElicitationNonAnswer.DEFERRED],\n \"question\": \"Which SMS provider should this application send text messages through (phone verification, SMS second factor)? Answer `none` if the product sends no SMS, or to decide later.\",\n \"kind\": \"choice\",\n \"options\": [\"twilio\", \"none\"],\n \"depth\": \"detail\"\n },\n /*\n * An internal tool's CORPORATE IDENTITY (#3037), asked only on that line (`lineQuestions` in the line definition;\n * every other line, and an application with no line yet, is not asked it). Whether the company signs its people in\n * through its own identity provider, and provisions them from its directory, is a fact about the company that\n * nothing upstream decides, so it is asked once, typed. The foundation executor reads the answer and turns the doors\n * on (`applyLineAccessPosture`): the enterprise sign-in methods, SCIM provisioning on the owner organization type,\n * and the features those doors are gated on. Registration itself is the line's decision (invitation only) and is not\n * asked. DETAIL, so a simple interview proposes it from the vision, recorded as an assumption.\n *\n * The options are the `ApplicationCorporateIdentity` members, so a member added there is offered here in the same\n * change.\n */\n {\n \"ref\": \"corporate-identity\",\n nonAnswers: [MetaWorkflow_ElicitationNonAnswer.DEFERRED],\n \"question\": \"How do the company's people sign in to this tool? Through the company's identity provider (single sign-on, such as Microsoft Entra ID, Okta or Google Workspace) with accounts provisioned from the company directory; through the identity provider with each person invited by an administrator; or with no corporate identity provider, each person invited and signing in with the tool's own sign-in.\",\n \"kind\": \"choice\",\n \"options\": [ApplicationCorporateIdentity.IDENTITY_PROVIDER_AND_DIRECTORY, ApplicationCorporateIdentity.IDENTITY_PROVIDER, ApplicationCorporateIdentity.NONE],\n \"depth\": \"detail\"\n }\n ]\n }\n },\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
|
|
1
|
+
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.foundation/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,OAAO,EAAE,4BAA4B,EAAE,MAAM,oDAAoD,CAAC;AAClG,OAAO,EAAE,oCAAoC,EAAE,iCAAiC,EAAE,MAAM,sCAAsC,CAAC;AAE/H,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,sBAAsB;IAC7B,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,gsCAAgsC;IAC1sC,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,aAAa,EAAE,EAAE;QACtE;;;;;;;;;;;;WAYG;QACH,EAAE,MAAM,EAAE,mBAAmB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,cAAc,EAAE,EAAE;QACzE;;;;;;;;;;;;;;;;;;;;;;;;WAwBG;QACH,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,kBAAkB,EAAE,EAAE;QAC3E;;;;;;WAMG;QACH,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,wBAAwB,EAAE,EAAE;KAClF;IACD;;;;;;;;;;;;;;;OAeG;IACH,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,aAAa,EAAE;QAC3B,EAAE,QAAQ,EAAE,gBAAgB,EAAE;QAC9B;;;;;;WAMG;QACH,EAAE,QAAQ,EAAE,wBAAwB,EAAE;QACtC;;;;;;WAMG;QACH,EAAE,QAAQ,EAAE,kBAAkB,EAAE;KACjC;IACD,SAAS,EAAE,EAAE;IACb,QAAQ,EAAE;QACR,WAAW,EAAE;YACX,aAAa;YACb,qBAAqB;YACrB,0BAA0B;YAC1B,6BAA6B;YAC7B,iCAAiC;SAClC;QACD;;;;;;;;;;;;WAYG;QACH,oBAAoB,EAAE;YACpB,EAAE,aAAa,EAAE,6BAA6B,EAAE,aAAa,EAAE,kBAAkB,EAAE;SACpF;QACD,aAAa,EAAE;YACb,WAAW,EAAE;gBACX;;;;;;;;;mBASG;gBACH;oBACE,KAAK,EAAE,eAAe;oBACtB,UAAU,EAAE,4MAA4M;oBACxN,MAAM,EAAE,QAAQ;oBAChB,SAAS,EAAE,CAAC,eAAe,EAAE,OAAO,CAAC;oBACrC,OAAO,EAAE,WAAW;oBACpB;;;;uBAIG;oBACH,gBAAgB,EAAE,EAAE,aAAa,EAAE,uBAAuB,EAAE,aAAa,EAAE,SAAS,EAAE;iBACvF;gBACD;;;;;;;;;;;;;;;;;;;mBAmBG;gBACH;oBACE,KAAK,EAAE,kBAAkB;oBACzB;;;;;uBAKG;oBACH,UAAU,EAAE,CAAC,iCAAiC,CAAC,QAAQ,CAAC;oBACxD,UAAU,EAAE,8rBAA8rB;oBAC1sB,MAAM,EAAE,WAAW;oBACnB,YAAY,EAAE,oCAAoC,CAAC,uBAAuB;oBAC1E,OAAO,EAAE,WAAW;oBACpB,aAAa,EAAE,KAAK;oBACpB,iBAAiB,EAAE,IAAI;iBACxB;gBACD;oBACE,KAAK,EAAE,yBAAyB;oBAChC,UAAU,EAAE,CAAC,iCAAiC,CAAC,QAAQ,CAAC;oBACxD,UAAU,EAAE,qhBAAqhB;oBACjiB,MAAM,EAAE,WAAW;oBACnB,YAAY,EAAE,oCAAoC,CAAC,uBAAuB;oBAC1E,OAAO,EAAE,WAAW;oBACpB,iBAAiB,EAAE,IAAI;iBACxB;gBACD;;;;;;;;;;;;;;;;;mBAiBG;gBACH;oBACE,KAAK,EAAE,4BAA4B;oBACnC,UAAU,EAAE,CAAC,iCAAiC,CAAC,QAAQ,CAAC;oBACxD,UAAU,EAAE,0cAA0c;oBACtd,MAAM,EAAE,WAAW;oBACnB,YAAY,EAAE,oCAAoC,CAAC,0BAA0B;oBAC7E,OAAO,EAAE,QAAQ;oBACjB,iBAAiB,EAAE,IAAI;iBACxB;gBACD;;;;;;;;;;;;;;;mBAeG;gBACH;oBACE,KAAK,EAAE,kBAAkB;oBACzB,UAAU,EAAE,CAAC,iCAAiC,CAAC,cAAc,EAAE,iCAAiC,CAAC,QAAQ,CAAC;oBAC1G,UAAU,EAAE,8JAA8J;oBAC1K,MAAM,EAAE,QAAQ;oBAChB,SAAS,EAAE,CAAC,QAAQ,EAAE,MAAM,CAAC;oBAC7B,OAAO,EAAE,QAAQ;iBAClB;gBACD;oBACE,KAAK,EAAE,cAAc;oBACrB,UAAU,EAAE,CAAC,iCAAiC,CAAC,cAAc,EAAE,iCAAiC,CAAC,QAAQ,CAAC;oBAC1G,UAAU,EAAE,+KAA+K;oBAC3L,MAAM,EAAE,QAAQ;oBAChB,SAAS,EAAE,CAAC,QAAQ,EAAE,MAAM,CAAC;oBAC7B,OAAO,EAAE,QAAQ;iBAClB;gBACD;;;;;;;;;;;mBAWG;gBACH;oBACE,KAAK,EAAE,oBAAoB;oBAC3B,UAAU,EAAE,CAAC,iCAAiC,CAAC,QAAQ,CAAC;oBACxD,UAAU,EAAE,4YAA4Y;oBACxZ,MAAM,EAAE,QAAQ;oBAChB,SAAS,EAAE,CAAC,4BAA4B,CAAC,+BAA+B,EAAE,4BAA4B,CAAC,iBAAiB,EAAE,4BAA4B,CAAC,IAAI,CAAC;oBAC5J,OAAO,EAAE,QAAQ;iBAClB;aACF;SACF;KACF;IACC,UAAU,EAAE,gBAAgB;IAC9B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * The structured method remains intentionally rich: its intent, inputs, output\n * contracts, elicitation, deterministic verification and skill routing are the\n * application knowledge a later generic assessment loop composes. This source\n * intentionally omits the superseded per-playbook evaluation-treatment object;\n * generation records that absence rather than fabricating legacy judge behavior.\n */\nimport { ApplicationCorporateIdentity } from '@wildo-ai/saas-specifications/application-creation';\nimport { MetaWorkflow_ElicitationAnswerFormat, MetaWorkflow_ElicitationNonAnswer } from '@wildo-ai/saas-models/meta-workflows';\n\nexport const playbookDefinition =\n{\n \"ref\": \"bottom_up.foundation\",\n \"version\": \"0.5.0\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Bottom-up foundation \\u2014 turn the approved domain plan and top-down definitions into a configured, bootable application skeleton. For a fresh application, use wildo init in an empty destination before refining its generated configuration; preserve existing projects and use their repair/composition paths. Author capabilities, modules and providers from the approved plan, verify application knowledge delivery (wildo assets sync refreshes installed assets), then run wildo setup --non-interactive and wildo local init with their prerequisites. These tools exist; their successful invocation and postconditions must be observed in the current run. The registered foundation executor composes module/resource shells and tenancy configuration; it does not run this full init/assets/setup sequence. This methodology states the prerequisites and postconditions to fulfil around that execution. It emits no artifact: the deliverable is the application source, configured module registrations and verified initialization. Record the reasons for configuration choices beside those choices. Runs after the domain plan is approved in the bottom_up phase; business resource implementation belongs to the later build work.\",\n \"preconditions\": [\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"domain-plan\" } },\n /*\n * SEQUENCING, not readiness (#1434). `artifact_exists` asserts this playbook needs the vision's\n * CONTENT, and it does not read a word of it: the run short-circuits into the foundation\n * executor before any brief is composed, and the executor reads the domain plan and the landed\n * business model. The audit rule that reports a readiness gate whose family is undeclared named\n * both remedies — declare it, or weaken the gate \"if the order is all that matters\" — and here\n * the order is all that matters.\n *\n * Nothing is lost by weakening it. The vision is enforced TRANSITIVELY and harder than this gate\n * ever did: `top_down.market-snapshot-produce` and `top_down.requirements-definition` both gate\n * on `vision-brief` at readiness, and `bottom_up.domain-plan` gates on both of those — so an\n * approved domain plan, which this playbook DOES require at readiness, cannot exist without one.\n */\n { \"kind\": \"artifact_expected\", \"selector\": { \"family\": \"vision-brief\" } },\n /*\n * CONTENT, not sequencing — and this gate is why (#1544).\n *\n * `appendBackgroundExecutionScenarios` composes one `add-worker-node` / `add-worker-rust` /\n * `add-minion` per surface the INTEGRATION PLAN declares, deriving every variable from that\n * declaration. It reads the plan leniently on purpose: absent or unparseable means the\n * application declares nothing to run beside its backend, which is the ordinary case. That\n * leniency is correct and stays — what it cannot do is tell \"declares nothing\" from \"has not\n * been produced yet\", and both come back as silence.\n *\n * Measured on the first end-to-end run: this playbook ran at 06:58:03 and concluded three\n * seconds later; `bottom_up.integration-plan` started at 06:58:47 — 44 seconds AFTER — and\n * declared one minion, `minion-compose-weekly-team-digest`. Nothing was composed. The build\n * decomposer then emitted `build-task-weekly-digest-minion` against a package that no step\n * would ever create, and nine hours later there was still no `minions/` directory and\n * `applicationMinions = {}`.\n *\n * `artifact_exists` rather than `artifact_expected`, by the distinction the vision gate above\n * draws: this playbook reads the plan's CONTENT, not merely its position in the order.\n *\n * Safe to gate on. The integration-plan playbook produces a plan for every application,\n * `workers: []` and `minions: []` included — an application with no background execution is a\n * plan that says so, not an absent one. So this cannot make the foundation permanently\n * ineligible; it can only hold it until the answer exists.\n */\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"integration-plan\" } },\n /*\n * The same gate for the same reason, one input over. `capability-composition` decides which\n * scenarios are NEEDED — the loop above it throws when a scenario is marked needed and the\n * foundation has no invocation for it — so composing before it lands composes from an empty\n * decision set, silently and with the same shape. Not measured failing; gated because it is the\n * same invariant at its other site (`invariant-call-site-enumeration.md`).\n */\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"capability-composition\" } }\n ],\n /*\n * TWO, measured rather than aspirational (#1434) — THREE since #1491, see the third entry.\n *\n * This playbook does not compose a brief at all: `executePlaybookRun` short-circuits it into the\n * foundation executor before any section is composed, so a declared input reaches no model. The\n * executor reads the domain plan (handed to it) and the landed business model (read itself), and\n * derives the three capabilities that are derivable from those two values.\n *\n * `vision-brief`, `market-snapshot`, `requirements` and `roadmap` were declared and reached\n * nothing — while the method told a reader that the vision's compliance constraints were \"the\n * primary driver of capability selection\". A declaration nothing reads is a promise nothing\n * keeps, and four of the six were exactly that.\n *\n * `vision-brief` stays a PRECONDITION, which is a different statement: the foundation must not run\n * before a vision exists, and that gate is real whether or not anything reads its content here.\n */\n \"inputs\": [\n { \"family\": \"domain-plan\" },\n { \"family\": \"business-model\" },\n /*\n * THIRD, since #1491: which optional packages (the website, the documentation portal) this\n * application needs, decided by `bottom_up.capability-composition` and applied here after the\n * domain scenarios. An INPUT, not a precondition, for the same reason as the business model: a\n * foundation run with no composition yet composes the domain and applies no optional package,\n * and the executor reads it through the `capabilityComposition` slot rather than a brief.\n */\n { \"family\": \"capability-composition\" },\n /*\n * FOURTH, since #1495: what runs beside the backend. The executor fans one `add-worker-node`,\n * `add-worker-rust` or `add-minion` out of this plan per surface it declares — the same shape as\n * the module and resource fan-out, and an INPUT for the same reason as the two above: a run with\n * no integration plan composes no background package, and a plan landing later re-stales this\n * step rather than gating it.\n */\n { \"family\": \"integration-plan\" }\n ],\n \"outputs\": [],\n \"method\": {\n \"skillRefs\": [\n \"config-saas\",\n \"module-registration\",\n \"infra-environment-config\",\n \"local-environment-bootstrap\",\n \"application-database-migrations\"\n ],\n /*\n * The application's LINE (#3270): the executor reads it on every run (`resolveApplicationLineDeclaration`). It decides\n * whether one organization owns the application, the line's access posture and the organization identity\n * declaration. The interview asks it in `top_down.vision-elicitation`, and the line answers none of THIS interview's\n * questions on a B2B line, so nothing dated the foundation by it: a line changed after the foundation landed left the\n * foundation CURRENT, and the configuration kept the old posture until a person ran it by hand. Declared here, the\n * line answer dates the foundation like one of its own answers, and its REFRESH says \"the application line\".\n *\n * The ACCEPTED BRAND is read too and is deliberately NOT declared: the foundation copies the brand only into a surface\n * it composes in that run, and every later accept of a mark propagates to every surface that exists\n * (`propagateAcceptedBrand`). A re-run after a new mark would copy nothing, so dating the foundation by the brand would\n * spend a run that changes no file. The corporate-identity answer is this interview's own question, dated as such.\n */\n \"derivedFromAnswers\": [\n { \"playbookRef\": \"top_down.vision-elicitation\", \"questionRef\": \"application-line\" }\n ],\n \"elicitation\": {\n \"questions\": [\n /*\n * THE FALLBACK, since 2026-08-28. `bottom_up.domain-plan` now asks this and carries the\n * answer in the committed plan (`DomainPlanOutputSet.tenancy`), because the plan MODELS\n * tenancy — wonder-crm's invented a workspace module and a membership before anyone was\n * asked — so asking after the model is shaped lets a second answer contradict it.\n *\n * The executor reads the plan first and reaches this question only for a plan authored\n * before the field existed. Keep it: those plans are real (wonder-crm, wonder-todos) and\n * must stay composable.\n */\n {\n \"ref\": \"primary-scope\",\n \"question\": \"Do people use this application together, in shared workspaces or teams, or does each person only see their own data? Choose organizations if they work together, users if each person's data is their own.\",\n \"kind\": \"choice\",\n \"options\": [\"organizations\", \"users\"],\n \"depth\": \"essential\",\n /*\n * ONE decision, asked once (#1454, gap 4): the domain plan's tenancy question owns it, and\n * this fallback reads that answer. The dossier listed the two as separate open questions,\n * worded differently, for the same choice.\n */\n \"sameDecisionAs\": { \"playbookRef\": \"bottom_up.domain-plan\", \"questionRef\": \"tenancy\" }\n },\n /*\n * The operator's own legal identity (issue #235), asked HERE because this is the playbook that\n * writes `wildo.saas.config.ts` and already carries the `config-saas` skill — an answer\n * elicited anywhere else would have nowhere to land, since a companion-agent playbook produces\n * an artifact and writes no files.\n *\n * WRITTEN by the executor since the #2294 follow-up (2026-11-10). Both answers follow a grammar the interview\n * holds them to at every door (`MetaWorkflow_ElicitationAnswerFormat.OPERATOR_IDENTITY_PARTS` and\n * `.OPERATING_JURISDICTIONS`), so the foundation executor writes them deterministically: the stated parts into\n * `operatorComplianceIdentity`, the jurisdictions into `operatingJurisdictions`. It never overwrites a value the\n * configuration already authors (a differing one is reported, not replaced), and an unanswered question writes\n * nothing and travels on the run result as an advisory. Until then the executor read neither answer and the\n * dossier was their only reader (#1454, #1434): the method described an agent writing them, and no agent ran.\n *\n * Both questions are deliberately ANSWERABLE IN PART. Every part of\n * `operatorComplianceIdentity` is independently declarable (#228), so a creator who knows the\n * registered name and not the lawful bases records the name — and Paul's decision (#225) is\n * explicit that filling the entity must never block. A question that demanded the whole thing\n * would reintroduce the blocking this lane just removed, one layer up.\n */\n {\n \"ref\": \"operating-entity\",\n /*\n * DEFERRED, for the creator who knows none of the three parts yet: no company is incorporated (#3204). The\n * labelled grammar needs at least one part, so without a non-answer that creator could not answer at all and the\n * foundation waited on them, while the question promises that nothing is blocked by a part left out. Reference run\n * 43207965509 stopped there. A deferral writes nothing and travels as the advisory an unanswered question does.\n */\n nonAnswers: [MetaWorkflow_ElicitationNonAnswer.DEFERRED],\n \"question\": \"Which legal entity operates this service? Give the parts you know, each on its own line (or separated by `;`) and labelled: `name: <registered company name>`, `address: <registered address>`, `privacy contact: <the email, URL or postal address a person uses to reach you about privacy>`. Answer only the parts you actually know today — anything you leave out is recorded as outstanding and nothing is blocked by it. If you know none of them yet (no company exists), defer the question rather than answer it. Do NOT supply a placeholder or a plausible-looking value: a produced privacy notice quotes these as fact, and the address is what a person would use to serve a legal request on a real company.\",\n \"kind\": \"free_text\",\n answerFormat: MetaWorkflow_ElicitationAnswerFormat.OPERATOR_IDENTITY_PARTS,\n \"depth\": \"essential\",\n \"whenUnknown\": \"ask\",\n \"regulatedDomain\": true\n },\n {\n \"ref\": \"operating-jurisdictions\",\n nonAnswers: [MetaWorkflow_ElicitationNonAnswer.DEFERRED],\n \"question\": \"Which jurisdictions does this application operate in, and why does each one reach it — are you established there, do you sell there, or do you hold data about people there? Give one per line (or separated by `;`), each as `<code>: <why>`, using country codes (`fr`, `us`), the supranational `eu`, or a subdivision (`us-ca`): for example `fr: established here; eu: customers resident here`. If the market is genuinely unsettled, defer the question rather than answer it; an absent answer is read as unanswered, never as \\\"nowhere\\\".\",\n \"kind\": \"free_text\",\n answerFormat: MetaWorkflow_ElicitationAnswerFormat.OPERATING_JURISDICTIONS,\n \"depth\": \"essential\",\n \"regulatedDomain\": true\n },\n /*\n * WHERE the application's data may be processed, as places the framework compares (#2294). The executor writes\n * the answer into `operatorComplianceIdentity.dataResidency`, and with it a processing region for every\n * data-serving provider the residency leaves exactly one region for; a provider with several regions inside, none,\n * or a deployment model to choose stays unplaced and is named in the run result and in `wildo context\n * launch-blockers`. The residency is written only once every data-serving provider is placed inside it, because\n * `wildo config sync` refuses a declared residency that leaves one unplaced: written early, it would stop the\n * application starting, which is the mechanism blocking on a decision rather than marking it.\n *\n * `top_down.compliance-analysis` asks the REQUIREMENT in the creator's words (`data-residency`), which is what the\n * regime research reads; this asks the same decision as places, which no prose can stand in for. Not a\n * `sameDecisionAs`: one is prose and the other a typed value, and one answer cannot satisfy both. DETAIL with the\n * default proposal policy, so a simple interview proposes it from that prose answer, and `regulatedDomain` names the\n * proposal to the person before it is kept.\n *\n * `none` declares no residency (nothing is refused, and the documents say none is declared). DEFERRED leaves it\n * open, and the run says so.\n */\n {\n \"ref\": \"data-residency-territories\",\n nonAnswers: [MetaWorkflow_ElicitationNonAnswer.DEFERRED],\n \"question\": \"Must this application's data stay inside named places? List them as jurisdiction codes separated by commas: a country (`de`, `fr`, `ch`), the supranational `eu`, or a subdivision (`us-ca`); the EEA is `eu, is, li, no`. Every provider that processes the data must then process inside them, so the framework chooses each provider's region where only one fits and names the providers where you must choose. Answer `none` if the data may be processed anywhere.\",\n \"kind\": \"free_text\",\n answerFormat: MetaWorkflow_ElicitationAnswerFormat.JURISDICTION_SLUGS_OR_NONE,\n \"depth\": \"detail\",\n \"regulatedDomain\": true\n },\n /*\n * The creator's PROVIDER choices (#1488). Which vendor an application charges or texts through is\n * a class-3 product decision — the field does not converge on one answer — so it is asked, as a\n * typed CHOICE, and the answer is kept in the dossier and read by the foundation executor, which\n * declares the provider, selects it as primary and enables the capability. The credentials the\n * provider needs are recorded as OWED on the run result: the boot floor reads declaration and\n * selection, never secrets, so the application boots and the provider answers once they are set.\n *\n * The OPTIONS are the engine providers serving the capability (ENGINE origin, backend scope), and\n * `foundation-executor.companion.service.test.ts` pins these authored lists to that derivation plus the\n * `none` member, so a vendor added to the catalogue fails the pin until it is offered here.\n *\n * `none` is an OPTION, not an absence: the elicitation contract refuses a run whose interview is not\n * fully answered, and a CHOICE accepts only its options, so \"decide later\" has to be sayable. It leaves\n * the capability owed exactly as before (#1272).\n */\n {\n \"ref\": \"billing-provider\",\n nonAnswers: [MetaWorkflow_ElicitationNonAnswer.NOT_APPLICABLE, MetaWorkflow_ElicitationNonAnswer.DEFERRED],\n \"question\": \"Which billing provider should this application charge its users through? Answer `none` to decide later; the capability stays off until a provider is chosen.\",\n \"kind\": \"choice\",\n \"options\": [\"stripe\", \"none\"],\n \"depth\": \"detail\"\n },\n {\n \"ref\": \"sms-provider\",\n nonAnswers: [MetaWorkflow_ElicitationNonAnswer.NOT_APPLICABLE, MetaWorkflow_ElicitationNonAnswer.DEFERRED],\n \"question\": \"Which SMS provider should this application send text messages through (phone verification, SMS second factor)? Answer `none` if the product sends no SMS, or to decide later.\",\n \"kind\": \"choice\",\n \"options\": [\"twilio\", \"none\"],\n \"depth\": \"detail\"\n },\n /*\n * An internal tool's CORPORATE IDENTITY (#3037), asked only on that line (`lineQuestions` in the line definition;\n * every other line, and an application with no line yet, is not asked it). Whether the company signs its people in\n * through its own identity provider, and provisions them from its directory, is a fact about the company that\n * nothing upstream decides, so it is asked once, typed. The foundation executor reads the answer and turns the doors\n * on (`applyLineAccessPosture`): the enterprise sign-in methods, SCIM provisioning on the owner organization type,\n * and the features those doors are gated on. Registration itself is the line's decision (invitation only) and is not\n * asked. DETAIL, so a simple interview proposes it from the vision, recorded as an assumption.\n *\n * The options are the `ApplicationCorporateIdentity` members, so a member added there is offered here in the same\n * change.\n */\n {\n \"ref\": \"corporate-identity\",\n nonAnswers: [MetaWorkflow_ElicitationNonAnswer.DEFERRED],\n \"question\": \"How do the company's people sign in to this tool? Through the company's identity provider (single sign-on, such as Microsoft Entra ID, Okta or Google Workspace) with accounts provisioned from the company directory; through the identity provider with each person invited by an administrator; or with no corporate identity provider, each person invited and signing in with the tool's own sign-in.\",\n \"kind\": \"choice\",\n \"options\": [ApplicationCorporateIdentity.IDENTITY_PROVIDER_AND_DIRECTORY, ApplicationCorporateIdentity.IDENTITY_PROVIDER, ApplicationCorporateIdentity.NONE],\n \"depth\": \"detail\"\n }\n ]\n }\n },\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
|