@wildo-ai/framework-knowledge 1.1.1 → 1.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +43 -2
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts +19 -0
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js +32 -0
- package/dist/esm/framework-knowledge.loader.js.map +1 -1
- package/dist/esm/framework-knowledge.schemas.d.ts +12 -0
- package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +46 -0
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +55 -0
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +4 -4
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +3 -3
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +0 -3
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +0 -3
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +2 -7
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +8 -3
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +22 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +0 -3
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +4 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +4 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -13
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +3 -4
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +3 -3
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +2 -7
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +2 -7
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +54 -0
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +127 -0
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +76 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +92 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +30 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +29 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +9 -44
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +4 -53
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +31 -0
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +26 -0
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -7
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +0 -8
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +2 -7
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -7
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +2 -7
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +5 -3
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +0 -3
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +4 -5
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +25 -4
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
- package/dist/knowledge/manifest.json +8 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +51 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +27 -10
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +8 -7
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +6 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +4 -6
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +5 -4
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +4 -6
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +0 -4
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +4 -6
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +49 -22
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +14 -6
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +2 -4
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +46 -1
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +7 -3
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +18 -4
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +4 -2
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +2 -3
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +8 -7
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +3 -5
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +0 -2
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +100 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +117 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +86 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +41 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +21 -4
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +14 -57
- package/dist/knowledge/playbooks/top_down.compliance-research/method.md +76 -0
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +42 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +3 -5
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +3 -1
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +3 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +3 -5
- package/dist/knowledge/playbooks/top_down.phase-gate/method.md +8 -4
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +9 -7
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +8 -7
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +0 -2
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +8 -7
- package/dist/knowledge/references/companion.technical-doc.service.md +102 -2
- package/dist/knowledge/references/example.config.app-shell.full.md +0 -1
- package/dist/knowledge/references/example.module.companion-exports.full.md +1 -0
- package/dist/knowledge/references/platform.config.saas.md +1 -0
- package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +25 -1
- package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +45 -0
- package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
- package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +89 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +31 -4
- package/dist/knowledge/references/saas.models.engine-capabilities.md +26 -6
- package/dist/knowledge/references/saas.models.file-upload-grant.md +179 -0
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +127 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +4 -3
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
- package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
- package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +11 -31
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +32 -2
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +29 -6
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +20 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +6 -0
- package/dist/knowledge/references/zod.decorators.field-spec-params.md +31 -5
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +43 -0
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +15 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
- package/dist/knowledge/registries/framework-topics.json +99 -1
- package/dist/knowledge/registries/playbooks.json +81 -8
- package/dist/knowledge/registries/source-tags.json +757 -588
- package/dist/knowledge/skills/INDEX.md +3 -3
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +5 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +66 -37
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +40 -7
- package/dist/knowledge/skills/config-app-shell/SKILL.md +25 -1
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +25 -1
- package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +23 -1
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
- package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
- package/dist/knowledge/skills/config-navigation/SKILL.md +75 -2
- package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +149 -0
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +114 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +133 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +19 -2
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +111 -0
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +30 -9
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +1 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +2 -1
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +20 -0
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +20 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +20 -0
- package/dist/knowledge/skills/resource-add-field/SKILL.md +3 -3
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +104 -0
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +13 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +71 -4
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +89 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +22 -1
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +192 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +28 -8
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +15 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +6 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +89 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +43 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +1 -1
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +20 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +31 -5
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +22 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +45 -0
- package/dist/knowledge/topic-index.json +504 -156
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/esm/.builder.pid +0 -9
|
@@ -5,10 +5,6 @@
|
|
|
5
5
|
"intent": "Bottom-up build scale — the THIRD and final build-execution playbook, the pivot from dispatching ONE task safely (the single-flight dispatch contract) to running the build at SCALE: parallelism across several coding agents, the concurrency schedule, and interleaving the companion-owned generation steps concurrently with coding runs. Reads the approved build-plan (the ordered coding-agent task graph, each task carrying a target, ONE MetaWorkflow_FunctionalTopic, its skill(s), and prose prerequisite ordering) and the current journey state, and answers the SCALE questions the single-flight dispatch playbook deliberately left open: (1) derive the ready-SET (a wave / frontier of tasks whose prose prerequisites have ALL SUCCEEDED — not merely been attempted); (2) decide the parallelism degree (how many coding agents run at once) and the worktree-isolation model that keeps each concurrent run's change-set cleanly attributable; (3) schedule the waves respecting the DEPENDS_ON ordering the build-plan encodes; (4) interleave the deterministic companion-owned generation steps (labels / i18n, email templates, seeds) concurrently with coding runs at the points their inputs exist — those steps run through their deterministic companion endpoints, NOT the coding-agent single-flight lock, so they genuinely overlap coding runs; (5) reconcile wave completion across the concurrent runs (all tasks in the frontier SUCCEEDED before the next wave opens) and apply onFailure across siblings + downstream. Then advance to the next wave and loop. Each parallel slot INVOKES the single-flight dispatch contract (the build-dispatch playbook, upstream — select-next / context-pack / one ACP prompt turn / change-set capture / verify-outside / record + onFailure); this playbook does NOT re-specify those per-task mechanics and does NOT re-decompose the plan (the build-decompose playbook owns the task graph) and authors no schemas / no code. IMPORTANT HONESTY: the companion runner HARD-ENFORCES single-flight today (a run plan carries at most ONE coding-agent task; a concurrent dispatch is refused; the workspace-mutation lock + the lock-free cursor + the missing run-outcome observation loop all assume one dispatch at a time). So this v1 scale METHOD is the DECLARATIVE TARGET a runner-serializer slice will realize — on the current runner the waves DEGRADE to sequential single-flight dispatch. And even the deterministic companion-generation steps, though they do not take the coding single-flight lock, cannot SAFELY overlap an active coding run today: the coding run's change-set is captured as a whole-worktree time-window diff, so a generation step writing files inside that window is misattributed to the coding run (the same whole-worktree pollution that forbids two concurrent coding agents) — so the generation steps also serialize outside an active coding-capture window today, and genuine concurrency (coding-parallel OR generation-overlap) both arrive only with the git worktree-per-agent isolation runner task. v1 scaffold: a multi-CODING_AGENT run-completion serializer, git worktree-per-agent isolation, a run-outcome reconciler, and a cursor lock are companion-runner mechanism filed as runner tasks, NOT built here; a priority/work-stealing scheduler and cost-optimal packing are a later depth phase.",
|
|
6
6
|
"functionalTopics": [],
|
|
7
7
|
"preconditions": [
|
|
8
|
-
{
|
|
9
|
-
"kind": "phase_is",
|
|
10
|
-
"phase": "bottom_up"
|
|
11
|
-
},
|
|
12
8
|
{
|
|
13
9
|
"kind": "artifact_exists",
|
|
14
10
|
"selector": {
|
|
@@ -24,7 +20,7 @@
|
|
|
24
20
|
"outputs": [],
|
|
25
21
|
"stepOutputs": [],
|
|
26
22
|
"method": {
|
|
27
|
-
"guidance": "# Build Scale — Run the Build at Scale: Waves, Parallelism, Interleaved Generation (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology, and a deliberately honest one.** It is a\n> working first cut of the *scale* orchestration — derive a wave of ready tasks,\n> run several coding agents in parallel under an isolation model, interleave the\n> deterministic companion-generation steps, and reconcile wave completion. But\n> the companion runner **hard-enforces single-flight today**: it refuses a run\n> plan with more than one coding-agent task, refuses a second dispatch while one\n> is active, holds one workspace-mutation lock per run, and has no run-outcome\n> reconciler. So the concurrency described below is the **declarative target** a\n> runner-serializer slice will realize. **On the current runner the waves\n> degrade to sequential single-flight dispatch** — read the \"What the runner\n> actually does today\" section before you assume anything ran in parallel. Do\n> not overclaim concurrency the runner cannot do.\n\n## Where you are in the journey\n\nThis is the **third and final build-execution playbook** — the pivot from\n**dispatching one task safely** (the build-dispatch playbook's single-flight\ncontract) to **running the build at scale**. It runs in the **bottom-up phase**,\nafter the build plan exists (`artifact_exists build-plan`) and the foundation\nstep has authored the app's config and skeleton. You\nare not re-opening the decomposition here, and you are not re-specifying how one\ntask dispatches — you are deciding **how many** tasks run **concurrently** and\n**safely**, in **what order**, with the companion-generation steps interleaved.\n\nUpstream: the **build-decompose** playbook produced the ordered task graph you\nschedule; the **build-dispatch** playbook defined how ONE task dispatches\nsafely — you **invoke that contract per parallel slot**, you do not re-author\nit. **You author neither of those concerns** — see the boundary section.\n\n## What this playbook does\n\nYou are the **scale orchestrator**. This playbook reads the approved build plan\nand the current journey state and answers, across the *whole* build: *\"which set\nof tasks is ready to run now, how many run at once and on what isolation, when\ndo the deterministic generation steps run, and when has a wave actually\nfinished?\"* You do **not** produce a new journey artifact — the observable\nresult of the build is the per-task change-sets + task statuses the runner\nrecords on the task rows (the build-dispatch playbook's mechanism), not a\nschedule artifact authored here (see \"What you emit\"). You do **not** decompose\nthe plan, re-specify the per-task dispatch mechanics, author any schema, or\nwrite any code.\n\n## The scale contract — you sequence waves, the dispatch playbook runs each slot\n\nMost of the *per-task* mechanism is **not yours**: selecting one task,\ncomposing its context pack, running one prompt turn against the coding agent over\nthe Agent Client Protocol (answering its permission requests within the declared\nceiling), capturing the change-set, running the verify hook, holding the\nsingle-flight lock, enforcing the budget floor — all of that is the **build-dispatch** contract, which each\nparallel slot invokes. Your method here is the **declarative concurrency\nrecipe** the runner (or a future runner-serializer) interprets: *which set* of\ntasks is ready, *how many* run at once, *how* they are isolated, *when* the\ndeterministic generation steps interleave, and *when* a wave is done. Do not\nhand-drive git, do not compose a dispatch prompt, do not re-implement the\nsingle-flight capture — invoke the dispatch contract per slot and let it own\nthose.\n\n## Read state first — no artifact to write\n\nThis playbook is **idempotent** and, on a re-run, *advances the schedule by one\nwave* (and, on today's single-flight runner, by one task within that wave).\nBefore scheduling anything:\n\n1. Read the current journey state and scope through the `journey-status` skill\n (it owns the read; do not re-derive it here). Confirm the **build plan** is\n present and approved and the **foundation** ran. For each build-plan task,\n read its dispatch state from its task row — **not yet dispatched**,\n **dispatched-and-succeeded** (a captured change-set + a passed verify),\n **dispatched-and-failed** (a captured change-set but a failed/timed-out run\n or a failed verify), or **in-flight**. This full state — not just \"has a\n change-set\" — is what the wave derivation keys on (under `keep_and_flag` a\n *failed* task also has a captured change-set, so presence of a change-set\n alone never means \"done\").\n2. Read the approved **build plan** (`build-plan` — the ordered task graph, with\n each task's prose prerequisite references). It is your work list.\n\n That there is an application to dispatch into is answered by the committed\n `./wildo.saas.config.ts` and skeleton, not by a journey artifact. (A\n `foundation-manifest` played that role until 2026-08-25 and was retired with the\n app-creation verification/digest aspect.) The honest limitation the foundation step\n carries still applies: on-disk skeleton materialization depends on greenfield\n bring-up tooling (deferred); the dogfood app already has a skeleton, so the scale\n contract runs against an existing workspace.\n\n// TODO CLI COMMAND: wildo journey status\n// (read journey scope + the approved build plan + every task's dispatch state)\n\nYou **read** `build-plan`; you **write** no journey\nartifact — the runner records each dispatched task's change-set + status on its\nrow.\n\n## Step 1 — Derive the ready-set (the wave / frontier)\n\nWalk the build plan and compute the **frontier**: the set of tasks that are\n**not yet dispatched** (or previously-**failed** tasks cleared for retry) and\nwhose prose prerequisites have **all SUCCEEDED**. That set is the next **wave**.\n\n- **A prerequisite must have SUCCEEDED, not merely been attempted.** A task\n enters the frontier only when every task it depends on is\n dispatched-and-succeeded (verify passed). A prerequisite that is\n dispatched-and-**failed** (its change-set flagged for triage under\n `keep_and_flag`), still **in-flight**, or un-run does **not** satisfy the\n dependency — its dependents stay **out of the frontier** until it succeeds.\n This is the U13b readiness discipline, lifted to a set: do not open a wave on\n a schema whose run has not verified.\n- **The wave respects the build-plan ordering.** The build-decompose playbook\n encoded the DEPENDS_ON edges (the per-resource stage order schema → config →\n ui-behavior → spec, the cross-topic edges, relationship-after-endpoints); the\n frontier is exactly the tasks with no unsatisfied edge remaining. You do not\n re-derive or re-order those edges — you read them and compute the ready-set.\n- **An empty frontier is a terminal state.** If no task is ready — every task\n has succeeded, or the only undispatched tasks are blocked behind an\n unresolved failure — the build is done (or blocked on a flagged failure):\n report it and stop. An empty build plan is the same.\n\n## Step 2 — Decide the parallelism degree + the worktree-isolation model\n\nFor the frontier, decide **how many** coding agents run at once and **on what\nisolation**. This is the core scale decision, and it is bounded by a hard\nsafety constraint, not just throughput:\n\n- **Change-set attribution requires isolation.** The dispatch contract captures\n each run's change-set by diffing the worktree around the run and attributing\n every file as `RUN_EXCLUSIVE`, `APPEARED_DURING_RUN`, or\n `BASELINE_DIRTY_AMBIGUOUS`. **Two coding agents mutating the SAME worktree\n concurrently make every touched file `BASELINE_DIRTY_AMBIGUOUS`** — each run\n looks like it started against a tree the other was dirtying — which\n **destroys per-run attribution**. So real parallelism needs one of:\n - **git worktree-per-agent isolation** — each concurrent coding agent runs in\n its own git worktree (a disjoint checkout of the same repo), so each run's\n change-set is captured against a tree only it mutates; the worktrees are\n reconciled/merged after the wave. This is the general answer.\n - **module / resource partitioning** — schedule concurrent agents only onto\n tasks whose targets touch **disjoint file sets** (different modules /\n resources), so even on one shared worktree no two runs collide. This is the\n cheaper answer when the frontier naturally partitions by module.\n - **or keep coding single-flight** and only parallelise the deterministic\n companion-generation steps (Step 3), which are not coding-locked.\n- **Pick the degree deliberately, not maximally.** At scaffold depth prefer a\n small degree (or a module partition) over max fan-out — cost-optimal packing,\n a priority / work-stealing scheduler, and backoff are a later depth phase, not\n this scaffold. State the isolation model you chose; a wave with degree > 1 and\n **no** isolation answer is unsafe (the reviewer rubric flags it as a GAP).\n\n## Step 3 — Interleave the deterministic companion-generation steps\n\nThe build plan carries **companion-owned generation steps** — labels / i18n,\nemail templates, seeds — as tasks. These are **deterministic companion\nendpoints**, not coding-agent dispatches: they do **not** contend for the\ncoding single-flight lock. It is tempting to conclude they can freely run\n*alongside* a coding run — but there is a subtlety that makes that unsafe on\ntoday's runner, see the caveat below.\n\n- **Run each generation step at its input-ready point.** A labels/i18n step runs\n after the resources it labels exist; an email step after its templates'\n definition surfaces exist; a seed step after the resources it seeds exist.\n Schedule each at its input-ready point in the wave sequence — do not block a\n coding wave on them and do not run them before their inputs exist. (The\n *ordering* is what matters here; the *concurrency* is deferred — see the\n caveat.)\n- **Route them to their deterministic endpoint, not the coding lane.** Do not\n dispatch a coding agent for a labels/email/seed step — it has a deterministic\n companion generator. Treating a generation step as a coding dispatch is scope\n creep the reviewer flags.\n- **CAVEAT — no attribution-safe overlap with an active coding run today.** The\n coding run's change-set is captured as a **whole-worktree time-window diff**\n (every tracked-dirty + untracked file in the window). So a generation step\n writing label / email / seed files **while a coding dispatch is capturing** is\n misattributed to that coding run — its files show up as the coding run's own\n edits. This is the *same* whole-worktree pollution that forbids two concurrent\n coding agents (Step 2), and it applies identically to coding + generation. So\n on today's runner the generation steps must **also** be serialized to run\n **outside** an active coding-capture window (i.e. between coding runs). Genuine\n overlap — generation alongside coding, and coding alongside coding — both\n arrive only with git worktree-per-agent isolation (the runner task in Step 5's\n gap note). Until then, keep the input-ready *ordering* and serialize.\n\n// TODO CLI COMMAND: wildo journey run <playbookRef>\n// (trigger the scheduled wave; each coding slot invokes the single-flight dispatch contract, each generation step runs its deterministic endpoint)\n\n## Step 4 — Authorize the fan-out (approve_before)\n\nFanning out **several** coding agents that **mutate the application workspace**\nis the highest-stakes action in the journey. This playbook's approval posture is\n`approve_before`: the scale run is authorized **before** it touches the tree.\nSettle the exact pending Authority Request through the `journey-approve` skill; never start\nthe fan-out on your own judgment.\n\n- Under the **GUIDED** autonomy preset the gate is verbatim; under\n **YOLO_LIGHT** it downgrades to a post-hoc result review; under **YOLO** it is\n auto (the non-bypassable **budget floor** — per-playbook and per-journey\n run/wall-time ceilings — is the guardrail no preset can lift).\n- **v1 gate granularity (be honest about the floor's reach).** The approval gate\n is currently **playbook-scoped for the journey**, not scoped to a single wave:\n the first authorization of this scale playbook admits its subsequent runs too\n (bounded by the run-count budget floor), rather than re-prompting per wave. So\n `approve_before` here means \"the creator authorizes the **scale loop** before\n any task mutates the workspace\" — a real pre-fan-out floor. A per-wave,\n single-use gate is a deferred runner posture; until it lands, the budget\n ceiling + the per-task change-set capture + the verify gate bound the\n authorized loop.\n\n## Step 5 — Reconcile wave completion, then advance\n\nA wave is done only when **every task in the frontier reached a terminal\nSUCCEEDED outcome** (change-set captured + verify passed) or is explicitly held\nas a blocked / flagged failure. Only then does the next frontier open (Step 1).\n\n- **Do not open the next wave on an unfinished one.** Advancing while a wave's\n tasks are still in-flight, or with an unreconciled failure, risks a downstream\n task building on an unfinished prerequisite. Reconcile first.\n- **Failure disposition across siblings + downstream** — this playbook's\n `onFailure` is **`keep_and_flag`**: a failed/timed-out task keeps its captured\n change-set flagged for human triage (never silently reverted, never an\n un-recorded half-applied state). Its already-dispatched **siblings** in the\n same wave are left to complete; its **dependents** in later waves stay\n **blocked** (Step 1) until it is triaged and re-dispatched successfully.\n Triage is a human decision: keep + fix forward, unwind the flagged change-set\n by hand, or re-dispatch once the blocker is resolved. This playbook does not\n auto-retry a failed task (automated retry / backoff is a deferred build-loop\n resilience concern).\n\n> **Why keep_and_flag, not revert_changeset (a v1 boundary).** Reverting a\n> failed run's edits is a *mutating* git op, deliberately **outside** the\n> read-only change-set carve-out the dispatch lane observes. So `keep_and_flag`\n> is both the correct F-5 workspace-safety posture and the behavior the runner\n> enforces today; a `revert_changeset` path is a deliberate later boundary.\n\nThen **loop**: on the next run, `journey-status` reflects the just-completed\nwave's outcomes, and you derive the next frontier (Step 1). Close a significant\nstretch of the build with a `journey-report` summary — which waves ran, which\nchange-sets landed, what verify said, which generation steps interleaved, and\nany failed task left flagged for triage.\n\n## What the runner actually does today (do not overclaim)\n\nBe honest with the creator about the gap between this method and the runner:\n\n- **The runner enforces single-flight.** It refuses a run plan carrying more\n than one coding-agent task, refuses a second dispatch while one is active, and\n holds one workspace-mutation lock per background run. So a wave with\n parallelism degree > 1 is **not** realizable on today's runner — the wave\n **degrades to sequential single-flight dispatch** (repeated invocation of the\n build-dispatch contract, one task at a time, in frontier order). The frontier\n math, the readiness discipline, and the reconciliation are all still correct\n and useful sequentially — you just do not get concurrency yet.\n- **No overlap is attribution-safe today — not even a companion-generation\n step.** The generation endpoints are not coding-locked, but the coding\n change-set capture is a whole-worktree time-window diff, so a generation step\n writing files while a coding dispatch is capturing is misattributed to that\n run (Step 3's caveat). So the generation steps **also** serialize outside an\n active coding-capture window: their input-ready *ordering* holds, only the\n *concurrency* is deferred. Safe overlap of generation-with-coding, and\n coding-with-coding, both require git worktree-per-agent isolation.\n- **The concurrency this method describes is the declarative target** for a\n runner-serializer slice (multi-coding-agent run-completion serialization,\n git worktree-per-agent isolation, a run-outcome reconciler, and a cursor lock)\n — filed as runner tasks, **not** built by this scaffold playbook. Until they\n land, run the waves sequentially and do not claim a parallel run (or a\n generation-alongside-coding overlap) happened when it did not.\n\n## Scaffold-depth boundary (owned by a sibling, or deferred to a later phase)\n\nKeep this playbook at **scale-orchestration depth**. Explicitly **out of scope\nhere**:\n\n- **Re-decomposition.** You do NOT split modules/resources into tasks, re-order\n the graph, or add tasks — the **build-decompose** playbook owns the task\n graph. You read it and schedule from it.\n- **The per-task dispatch contract.** You do NOT re-specify single-flight\n locking, context-pack composition, change-set capture, or the verify hook —\n the **build-dispatch** playbook owns \"how ONE task dispatches safely\", and\n each parallel slot **invokes** that contract. If you catch yourself describing\n how a single task captures its change-set, stop — that is the dispatch\n playbook.\n- **The runner-serializer mechanism.** The multi-coding-agent serializer, git\n worktree-per-agent provisioning, the run-outcome reconciler, and the cursor\n lock are **companion-runner mechanism**, filed as runner tasks — this\n declarative method does not build them.\n- **A priority / work-stealing scheduler + cost-optimal packing.** Deciding an\n optimal task ordering within a band, work-stealing across idle slots, backoff,\n and cost-optimal packing are a later depth phase — the v1 scaffold picks a\n small parallelism degree (or a module partition) and a simple frontier order.\n- **A `revert_changeset` failure path.** Deferred; `keep_and_flag` is the v1\n disposition.\n- **Auto-executed reviewer checklist.** The scale-soundness checklist ships\n **declarative** — the deterministic typecheck gate runs automatically; nothing\n executes the checklist prose (rubric-only judge gates were retired at the\n flexible-intelligence hard cut). Do not assume it auto-ran.\n- **Schema / field authoring + code generation.** The **coding agents** author\n fields, schemas, ui-behavior, and code at dispatch time — never the\n orchestrator.\n\nIf you find yourself designing how ONE task dispatches safely rather than how\nMANY tasks are scheduled + reconciled, stop — that is the build-dispatch\nplaybook.\n\n## What you emit\n\n**No journey artifact.** This is a pure-orchestration playbook: the observable\nresult of the build — each task's **change-set** (files touched, attributed,\nsummarized) and **status** — is materialized by the runner on the dispatched\ntask rows (the build-dispatch playbook's mechanism), not authored here. A\nseparate schedule / wave-log artifact family is deliberately not added: the task\nrows already *are* the dispatch record and a second home for the same record\nwould drift (a typed wave-schedule / run-ledger contract is a filed later-phase\nitem). The creator authorizes the scale run (`approve_before`) before it fans\nout, and reviews the recorded change-sets + verify outcomes after — wave by\nwave, until the build plan is fully dispatched.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state,\n scope, and budget; confirm the build plan is approved and the foundation ran,\n and read every task's dispatch state to compute the frontier.\n- `.claude/skills/journey-approve/SKILL.md` — relay the exact pre-fan-out Authority Request\n gate decision that authorizes the workspace-mutating fan-out (never\n self-approve).\n- `.claude/skills/journey-run/SKILL.md` — trigger a scheduled wave; each coding\n slot invokes the single-flight dispatch contract and each deterministic\n generation step runs its companion endpoint.\n- `.claude/skills/journey-report/SKILL.md` — summarize a stretch of the build:\n which waves ran, which change-sets landed, what verify said, and any failed\n task left flagged for triage.\n\n## Reviewer checklist — `scale-schedule-sound`\n\nFormerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is kept here, verbatim, minus the retired runner's closing sentence:\n\nJudge whether the SCALE orchestration ran the build soundly — the trust-but-verify reviewer pass over how MANY tasks were scheduled, parallelised, and reconciled, WITHOUT straying into how ONE task dispatches (that is the build-dispatch playbook's rubric) or how the plan was decomposed (the build-decompose playbook's). Assess six invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) WAVE READINESS — every task dispatched in a wave had ALL its prose prerequisites already SUCCEEDED (dispatched-and-verified), not merely attempted; a task dispatched while a prerequisite was un-run, in-flight, or dispatched-and-FAILED is a GAP (the build stage ran against a missing prerequisite). A prerequisite whose run FAILED (its change-set flagged under keep_and_flag) does NOT satisfy the dependency — its dependents must stay blocked, and dispatching them anyway is a GAP. (2) PARALLELISM SAFETY / ATTRIBUTION — the concurrent coding runs in a wave were isolated so each run's change-set is cleanly attributable (files RUN_EXCLUSIVE / APPEARED_DURING_RUN per run), via git worktree-per-agent isolation OR a module/resource partition that puts every concurrent agent on a DISJOINT file set. Two concurrent coding agents mutating the SAME worktree — which makes every touched file BASELINE_DIRTY_AMBIGUOUS and destroys per-run attribution — is a GAP (the single-flight floor was bypassed without an isolation answer). Note the honest floor: the runner enforces single-flight today, so on the current runner a 'wave' degrades to SEQUENTIAL single-flight dispatch and this invariant reads whether the METHOD declared a sound isolation model, not whether concurrency actually ran. (3) COMPANION-GENERATION INTERLEAVE — the deterministic companion-owned generation steps (labels / i18n, email templates, seeds) ran through their deterministic companion endpoints AFTER the resources / modules whose output they consume existed, at the right point in the schedule order; a generation step ordered before its inputs exist, or a missing generation step for authored surfaces, is a CONCERN; treating a deterministic generation step as a coding-agent dispatch (dispatching an agent for it) is a CONCERN. Note the honest floor: the generation steps do NOT take the coding single-flight lock, but the coding change-set capture is a whole-worktree time-window diff, so a generation step writing files WHILE a coding dispatch is capturing is misattributed to that coding run — so on today's runner the generation steps also serialize outside an active coding-capture window, and this invariant reads whether they ran at the right point in the ORDER, not whether they truly overlapped a coding run (safe overlap needs worktree isolation). (4) WAVE-COMPLETION RECONCILIATION — the next wave opened only after every task in the current frontier reached a terminal SUCCEEDED outcome (or was explicitly held as a blocked / flagged failure); advancing the schedule while a wave's tasks were still in-flight or with an unreconciled failure is a GAP (a downstream task could build on an unfinished prerequisite). (5) FAILURE DISPOSITION ACROSS SIBLINGS + DOWNSTREAM — a failed / timed-out task in a wave kept its captured change-set flagged for human triage (keep_and_flag), its already-dispatched siblings in the same wave were left to complete, and its DEPENDENTS in later waves stayed blocked until it was triaged and re-dispatched successfully; a failed task whose dependents were dispatched anyway, or a failure silently reverted / left un-recorded, is a GAP (F-5 workspace-safety violation). (6) BOUNDARY DISCIPLINE — the orchestration stays at SCALE depth: it derives ready-sets, schedules waves, sets the parallelism + isolation model, interleaves the companion-generation steps, and reconciles completion. It does NOT re-decompose the plan (the build-decompose playbook owns the task graph), does NOT re-specify the per-task dispatch mechanics (single-flight lock / context-pack / change-set capture / verify — the build-dispatch playbook owns those; the scale orchestrator INVOKES that contract per slot), and does NOT itself author schemas / fields / code (the coding agents do that at dispatch time). Evidence of re-decomposition, re-authoring the single-task dispatch contract, or the orchestrator authoring code itself is a CONCERN (scope creep out of the scale lane). (The checklist is declarative: nothing executes it; the deterministic gates and the creator's approval remain the floors.)\n",
|
|
23
|
+
"guidance": "# Build Scale — Run the Build at Scale: Waves, Parallelism, Interleaved Generation (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology, and a deliberately honest one.** It is a\n> working first cut of the *scale* orchestration — derive a wave of ready tasks,\n> run several coding agents in parallel under an isolation model, interleave the\n> deterministic companion-generation steps, and reconcile wave completion. But\n> the companion runner **hard-enforces single-flight today**: it refuses a run\n> plan with more than one coding-agent task, refuses a second dispatch while one\n> is active, holds one workspace-mutation lock per run, and has no run-outcome\n> reconciler. So the concurrency described below is the **declarative target** a\n> runner-serializer slice will realize. **On the current runner the waves\n> degrade to sequential single-flight dispatch** — read the \"What the runner\n> actually does today\" section before you assume anything ran in parallel. Do\n> not overclaim concurrency the runner cannot do.\n\n## Where you are in the journey\n\nThis is the **third and final build-execution playbook** — the pivot from\n**dispatching one task safely** (the build-dispatch playbook's single-flight\ncontract) to **running the build at scale**. It runs in the **bottom-up phase**,\nafter the build plan exists (`artifact_exists build-plan`) and the foundation\nstep has authored the app's config and skeleton. You\nare not re-opening the decomposition here, and you are not re-specifying how one\ntask dispatches — you are deciding **how many** tasks run **concurrently** and\n**safely**, in **what order**, with the companion-generation steps interleaved.\n\nUpstream: the **build-decompose** playbook produced the ordered task graph you\nschedule; the **build-dispatch** playbook defined how ONE task dispatches\nsafely — you **invoke that contract per parallel slot**, you do not re-author\nit. **You author neither of those concerns** — see the boundary section.\n\n## What this playbook does\n\nYou are the **scale orchestrator**. This playbook reads the approved build plan\nand the current journey state and answers, across the *whole* build: *\"which set\nof tasks is ready to run now, how many run at once and on what isolation, when\ndo the deterministic generation steps run, and when has a wave actually\nfinished?\"* You do **not** produce a new journey artifact — the observable\nresult of the build is the per-task change-sets + task statuses the runner\nrecords on the task rows (the build-dispatch playbook's mechanism), not a\nschedule artifact authored here (see \"What you emit\"). You do **not** decompose\nthe plan, re-specify the per-task dispatch mechanics, author any schema, or\nwrite any code.\n\n## The scale contract — you sequence waves, the dispatch playbook runs each slot\n\nMost of the *per-task* mechanism is **not yours**: selecting one task,\ncomposing its context pack, running one prompt turn against the coding agent over\nthe Agent Client Protocol (answering its permission requests within the declared\nceiling), capturing the change-set, running the verify hook, holding the\nsingle-flight lock, enforcing the budget floor — all of that is the **build-dispatch** contract, which each\nparallel slot invokes. Your method here is the **declarative concurrency\nrecipe** the runner (or a future runner-serializer) interprets: *which set* of\ntasks is ready, *how many* run at once, *how* they are isolated, *when* the\ndeterministic generation steps interleave, and *when* a wave is done. Do not\nhand-drive git, do not compose a dispatch prompt, do not re-implement the\nsingle-flight capture — invoke the dispatch contract per slot and let it own\nthose.\n\n## Read state first — no artifact to write\n\nThis playbook is **idempotent** and, on a re-run, *advances the schedule by one\nwave* (and, on today's single-flight runner, by one task within that wave).\nBefore scheduling anything:\n\n1. Read the current journey state and scope through the `journey-status` skill\n (it owns the read; do not re-derive it here). Confirm the **build plan** is\n present and approved and the **foundation** ran. For each build-plan task,\n read its dispatch state from its task row — **not yet dispatched**,\n **dispatched-and-succeeded** (a captured change-set + a passed verify),\n **dispatched-and-failed** (a captured change-set but a failed/timed-out run\n or a failed verify), or **in-flight**. This full state — not just \"has a\n change-set\" — is what the wave derivation keys on (under `keep_and_flag` a\n *failed* task also has a captured change-set, so presence of a change-set\n alone never means \"done\").\n2. Read the approved **build plan** (`build-plan` — the ordered task graph, with\n each task's prose prerequisite references). It is your work list.\n\n That there is an application to dispatch into is answered by the committed\n `./wildo.saas.config.ts` and skeleton, not by a journey artifact. (A\n `foundation-manifest` played that role until 2026-08-25 and was retired with the\n app-creation verification/digest aspect.) The honest limitation the foundation step\n carries still applies: on-disk skeleton materialization depends on greenfield\n bring-up tooling (deferred); the dogfood app already has a skeleton, so the scale\n contract runs against an existing workspace.\n\n// Operator status: `wildo context journey` (phase + board + runs in flight); per-task landed\n// state is read from git by the runner.\n\nYou **read** `build-plan`; you **write** no journey\nartifact — the runner records each dispatched task's change-set + status on its\nrow.\n\n## Step 1 — Derive the ready-set (the wave / frontier)\n\nWalk the build plan and compute the **frontier**: the set of tasks that are\n**not yet dispatched** (or previously-**failed** tasks cleared for retry) and\nwhose prose prerequisites have **all SUCCEEDED**. That set is the next **wave**.\n\n- **A prerequisite must have SUCCEEDED, not merely been attempted.** A task\n enters the frontier only when every task it depends on is\n dispatched-and-succeeded (verify passed). A prerequisite that is\n dispatched-and-**failed** (its change-set flagged for triage under\n `keep_and_flag`), still **in-flight**, or un-run does **not** satisfy the\n dependency — its dependents stay **out of the frontier** until it succeeds.\n This is the U13b readiness discipline, lifted to a set: do not open a wave on\n a schema whose run has not verified.\n- **The wave respects the build-plan ordering.** The build-decompose playbook\n encoded the DEPENDS_ON edges (the per-resource stage order schema → config →\n ui-behavior → spec, the cross-topic edges, relationship-after-endpoints); the\n frontier is exactly the tasks with no unsatisfied edge remaining. You do not\n re-derive or re-order those edges — you read them and compute the ready-set.\n- **An empty frontier is a terminal state.** If no task is ready — every task\n has succeeded, or the only undispatched tasks are blocked behind an\n unresolved failure — the build is done (or blocked on a flagged failure):\n report it and stop. An empty build plan is the same.\n\n## Step 2 — Decide the parallelism degree + the worktree-isolation model\n\nFor the frontier, decide **how many** coding agents run at once and **on what\nisolation**. This is the core scale decision, and it is bounded by a hard\nsafety constraint, not just throughput:\n\n- **Change-set attribution requires isolation.** The dispatch contract captures\n each run's change-set by diffing the worktree around the run and attributing\n every file as `RUN_EXCLUSIVE`, `APPEARED_DURING_RUN`, or\n `BASELINE_DIRTY_AMBIGUOUS`. **Two coding agents mutating the SAME worktree\n concurrently make every touched file `BASELINE_DIRTY_AMBIGUOUS`** — each run\n looks like it started against a tree the other was dirtying — which\n **destroys per-run attribution**. So real parallelism needs one of:\n - **git worktree-per-agent isolation** — each concurrent coding agent runs in\n its own git worktree (a disjoint checkout of the same repo), so each run's\n change-set is captured against a tree only it mutates; the worktrees are\n reconciled/merged after the wave. This is the general answer.\n - **module / resource partitioning** — schedule concurrent agents only onto\n tasks whose targets touch **disjoint file sets** (different modules /\n resources), so even on one shared worktree no two runs collide. This is the\n cheaper answer when the frontier naturally partitions by module.\n - **or keep coding single-flight** and only parallelise the deterministic\n companion-generation steps (Step 3), which are not coding-locked.\n- **Pick the degree deliberately, not maximally.** At scaffold depth prefer a\n small degree (or a module partition) over max fan-out — cost-optimal packing,\n a priority / work-stealing scheduler, and backoff are a later depth phase, not\n this scaffold. State the isolation model you chose; a wave with degree > 1 and\n **no** isolation answer is unsafe (the reviewer rubric flags it as a GAP).\n\n## Step 3 — Interleave the deterministic companion-generation steps\n\nThe build plan carries **companion-owned generation steps** — labels / i18n,\nemail templates, seeds — as tasks. These are **deterministic companion\nendpoints**, not coding-agent dispatches: they do **not** contend for the\ncoding single-flight lock. It is tempting to conclude they can freely run\n*alongside* a coding run — but there is a subtlety that makes that unsafe on\ntoday's runner, see the caveat below.\n\n- **Run each generation step at its input-ready point.** A labels/i18n step runs\n after the resources it labels exist; an email step after its templates'\n definition surfaces exist; a seed step after the resources it seeds exist.\n Schedule each at its input-ready point in the wave sequence — do not block a\n coding wave on them and do not run them before their inputs exist. (The\n *ordering* is what matters here; the *concurrency* is deferred — see the\n caveat.)\n- **Route them to their deterministic endpoint, not the coding lane.** Do not\n dispatch a coding agent for a labels/email/seed step — it has a deterministic\n companion generator. Treating a generation step as a coding dispatch is scope\n creep the reviewer flags.\n- **CAVEAT — no attribution-safe overlap with an active coding run today.** The\n coding run's change-set is captured as a **whole-worktree time-window diff**\n (every tracked-dirty + untracked file in the window). So a generation step\n writing label / email / seed files **while a coding dispatch is capturing** is\n misattributed to that coding run — its files show up as the coding run's own\n edits. This is the *same* whole-worktree pollution that forbids two concurrent\n coding agents (Step 2), and it applies identically to coding + generation. So\n on today's runner the generation steps must **also** be serialized to run\n **outside** an active coding-capture window (i.e. between coding runs). Genuine\n overlap — generation alongside coding, and coding alongside coding — both\n arrive only with git worktree-per-agent isolation (the runner task in Step 5's\n gap note). Until then, keep the input-ready *ordering* and serialize.\n\n// The trigger is the companion's run route (`POST /api/companion/playbooks/<ref>/run`) — no CLI\n// trigger yet. Each coding slot invokes the single-flight dispatch contract; each generation step\n// runs its deterministic endpoint.\n\n## Step 4 — Authorize the fan-out (approve_before)\n\nFanning out **several** coding agents that **mutate the application workspace**\nis the highest-stakes action in the journey. This playbook's approval posture is\n`approve_before`: the scale run is authorized **before** it touches the tree.\nSettle the exact pending Authority Request through the `journey-approve` skill; never start\nthe fan-out on your own judgment.\n\n- Under the **GUIDED** autonomy preset the gate is verbatim; under\n **YOLO_LIGHT** it downgrades to a post-hoc result review; under **YOLO** it is\n auto (the non-bypassable **budget floor** — per-playbook and per-journey\n run/wall-time ceilings — is the guardrail no preset can lift).\n- **v1 gate granularity (be honest about the floor's reach).** The approval gate\n is currently **playbook-scoped for the journey**, not scoped to a single wave:\n the first authorization of this scale playbook admits its subsequent runs too\n (bounded by the run-count budget floor), rather than re-prompting per wave. So\n `approve_before` here means \"the creator authorizes the **scale loop** before\n any task mutates the workspace\" — a real pre-fan-out floor. A per-wave,\n single-use gate is a deferred runner posture; until it lands, the budget\n ceiling + the per-task change-set capture + the verify gate bound the\n authorized loop.\n\n## Step 5 — Reconcile wave completion, then advance\n\nA wave is done only when **every task in the frontier reached a terminal\nSUCCEEDED outcome** (change-set captured + verify passed) or is explicitly held\nas a blocked / flagged failure. Only then does the next frontier open (Step 1).\n\n- **Do not open the next wave on an unfinished one.** Advancing while a wave's\n tasks are still in-flight, or with an unreconciled failure, risks a downstream\n task building on an unfinished prerequisite. Reconcile first.\n- **Failure disposition across siblings + downstream** — this playbook's\n `onFailure` is **`keep_and_flag`**: a failed/timed-out task keeps its captured\n change-set flagged for human triage (never silently reverted, never an\n un-recorded half-applied state). Its already-dispatched **siblings** in the\n same wave are left to complete; its **dependents** in later waves stay\n **blocked** (Step 1) until it is triaged and re-dispatched successfully.\n Triage is a human decision: keep + fix forward, unwind the flagged change-set\n by hand, or re-dispatch once the blocker is resolved. This playbook does not\n auto-retry a failed task (automated retry / backoff is a deferred build-loop\n resilience concern).\n\n> **Why keep_and_flag, not revert_changeset (a v1 boundary).** Reverting a\n> failed run's edits is a *mutating* git op, deliberately **outside** the\n> read-only change-set carve-out the dispatch lane observes. So `keep_and_flag`\n> is both the correct F-5 workspace-safety posture and the behavior the runner\n> enforces today; a `revert_changeset` path is a deliberate later boundary.\n\nThen **loop**: on the next run, `journey-status` reflects the just-completed\nwave's outcomes, and you derive the next frontier (Step 1). Close a significant\nstretch of the build with a `journey-report` summary — which waves ran, which\nchange-sets landed, what verify said, which generation steps interleaved, and\nany failed task left flagged for triage.\n\n## What the runner actually does today (do not overclaim)\n\nBe honest with the creator about the gap between this method and the runner:\n\n- **The runner enforces single-flight.** It refuses a run plan carrying more\n than one coding-agent task, refuses a second dispatch while one is active, and\n holds one workspace-mutation lock per background run. So a wave with\n parallelism degree > 1 is **not** realizable on today's runner — the wave\n **degrades to sequential single-flight dispatch** (repeated invocation of the\n build-dispatch contract, one task at a time, in frontier order). The frontier\n math, the readiness discipline, and the reconciliation are all still correct\n and useful sequentially — you just do not get concurrency yet.\n- **No overlap is attribution-safe today — not even a companion-generation\n step.** The generation endpoints are not coding-locked, but the coding\n change-set capture is a whole-worktree time-window diff, so a generation step\n writing files while a coding dispatch is capturing is misattributed to that\n run (Step 3's caveat). So the generation steps **also** serialize outside an\n active coding-capture window: their input-ready *ordering* holds, only the\n *concurrency* is deferred. Safe overlap of generation-with-coding, and\n coding-with-coding, both require git worktree-per-agent isolation.\n- **The concurrency this method describes is the declarative target** for a\n runner-serializer slice (multi-coding-agent run-completion serialization,\n git worktree-per-agent isolation, a run-outcome reconciler, and a cursor lock)\n — filed as runner tasks, **not** built by this scaffold playbook. Until they\n land, run the waves sequentially and do not claim a parallel run (or a\n generation-alongside-coding overlap) happened when it did not.\n\n## Scaffold-depth boundary (owned by a sibling, or deferred to a later phase)\n\nKeep this playbook at **scale-orchestration depth**. Explicitly **out of scope\nhere**:\n\n- **Re-decomposition.** You do NOT split modules/resources into tasks, re-order\n the graph, or add tasks — the **build-decompose** playbook owns the task\n graph. You read it and schedule from it.\n- **The per-task dispatch contract.** You do NOT re-specify single-flight\n locking, context-pack composition, change-set capture, or the verify hook —\n the **build-dispatch** playbook owns \"how ONE task dispatches safely\", and\n each parallel slot **invokes** that contract. If you catch yourself describing\n how a single task captures its change-set, stop — that is the dispatch\n playbook.\n- **The runner-serializer mechanism.** The multi-coding-agent serializer, git\n worktree-per-agent provisioning, the run-outcome reconciler, and the cursor\n lock are **companion-runner mechanism**, filed as runner tasks — this\n declarative method does not build them.\n- **A priority / work-stealing scheduler + cost-optimal packing.** Deciding an\n optimal task ordering within a band, work-stealing across idle slots, backoff,\n and cost-optimal packing are a later depth phase — the v1 scaffold picks a\n small parallelism degree (or a module partition) and a simple frontier order.\n- **A `revert_changeset` failure path.** Deferred; `keep_and_flag` is the v1\n disposition.\n- **Auto-executed reviewer checklist.** The scale-soundness checklist ships\n **declarative** — the deterministic typecheck gate runs automatically; nothing\n executes the checklist prose (rubric-only judge gates were retired at the\n flexible-intelligence hard cut). Do not assume it auto-ran.\n- **Schema / field authoring + code generation.** The **coding agents** author\n fields, schemas, ui-behavior, and code at dispatch time — never the\n orchestrator.\n\nIf you find yourself designing how ONE task dispatches safely rather than how\nMANY tasks are scheduled + reconciled, stop — that is the build-dispatch\nplaybook.\n\n## What you emit\n\n**No journey artifact.** This is a pure-orchestration playbook: the observable\nresult of the build — each task's **change-set** (files touched, attributed,\nsummarized) and **status** — is materialized by the runner on the dispatched\ntask rows (the build-dispatch playbook's mechanism), not authored here. A\nseparate schedule / wave-log artifact family is deliberately not added: the task\nrows already *are* the dispatch record and a second home for the same record\nwould drift (a typed wave-schedule / run-ledger contract is a filed later-phase\nitem). The creator authorizes the scale run (`approve_before`) before it fans\nout, and reviews the recorded change-sets + verify outcomes after — wave by\nwave, until the build plan is fully dispatched.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state,\n scope, and budget; confirm the build plan is approved and the foundation ran,\n and read every task's dispatch state to compute the frontier.\n- `.claude/skills/journey-approve/SKILL.md` — relay the exact pre-fan-out Authority Request\n gate decision that authorizes the workspace-mutating fan-out (never\n self-approve).\n- `.claude/skills/journey-run/SKILL.md` — trigger a scheduled wave; each coding\n slot invokes the single-flight dispatch contract and each deterministic\n generation step runs its companion endpoint.\n- `.claude/skills/journey-report/SKILL.md` — summarize a stretch of the build:\n which waves ran, which change-sets landed, what verify said, and any failed\n task left flagged for triage.\n\n## Reviewer checklist — `scale-schedule-sound`\n\nFormerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is kept here, verbatim, minus the retired runner's closing sentence:\n\nJudge whether the SCALE orchestration ran the build soundly — the trust-but-verify reviewer pass over how MANY tasks were scheduled, parallelised, and reconciled, WITHOUT straying into how ONE task dispatches (that is the build-dispatch playbook's rubric) or how the plan was decomposed (the build-decompose playbook's). Assess six invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) WAVE READINESS — every task dispatched in a wave had ALL its prose prerequisites already SUCCEEDED (dispatched-and-verified), not merely attempted; a task dispatched while a prerequisite was un-run, in-flight, or dispatched-and-FAILED is a GAP (the build stage ran against a missing prerequisite). A prerequisite whose run FAILED (its change-set flagged under keep_and_flag) does NOT satisfy the dependency — its dependents must stay blocked, and dispatching them anyway is a GAP. (2) PARALLELISM SAFETY / ATTRIBUTION — the concurrent coding runs in a wave were isolated so each run's change-set is cleanly attributable (files RUN_EXCLUSIVE / APPEARED_DURING_RUN per run), via git worktree-per-agent isolation OR a module/resource partition that puts every concurrent agent on a DISJOINT file set. Two concurrent coding agents mutating the SAME worktree — which makes every touched file BASELINE_DIRTY_AMBIGUOUS and destroys per-run attribution — is a GAP (the single-flight floor was bypassed without an isolation answer). Note the honest floor: the runner enforces single-flight today, so on the current runner a 'wave' degrades to SEQUENTIAL single-flight dispatch and this invariant reads whether the METHOD declared a sound isolation model, not whether concurrency actually ran. (3) COMPANION-GENERATION INTERLEAVE — the deterministic companion-owned generation steps (labels / i18n, email templates, seeds) ran through their deterministic companion endpoints AFTER the resources / modules whose output they consume existed, at the right point in the schedule order; a generation step ordered before its inputs exist, or a missing generation step for authored surfaces, is a CONCERN; treating a deterministic generation step as a coding-agent dispatch (dispatching an agent for it) is a CONCERN. Note the honest floor: the generation steps do NOT take the coding single-flight lock, but the coding change-set capture is a whole-worktree time-window diff, so a generation step writing files WHILE a coding dispatch is capturing is misattributed to that coding run — so on today's runner the generation steps also serialize outside an active coding-capture window, and this invariant reads whether they ran at the right point in the ORDER, not whether they truly overlapped a coding run (safe overlap needs worktree isolation). (4) WAVE-COMPLETION RECONCILIATION — the next wave opened only after every task in the current frontier reached a terminal SUCCEEDED outcome (or was explicitly held as a blocked / flagged failure); advancing the schedule while a wave's tasks were still in-flight or with an unreconciled failure is a GAP (a downstream task could build on an unfinished prerequisite). (5) FAILURE DISPOSITION ACROSS SIBLINGS + DOWNSTREAM — a failed / timed-out task in a wave kept its captured change-set flagged for human triage (keep_and_flag), its already-dispatched siblings in the same wave were left to complete, and its DEPENDENTS in later waves stayed blocked until it was triaged and re-dispatched successfully; a failed task whose dependents were dispatched anyway, or a failure silently reverted / left un-recorded, is a GAP (F-5 workspace-safety violation). (6) BOUNDARY DISCIPLINE — the orchestration stays at SCALE depth: it derives ready-sets, schedules waves, sets the parallelism + isolation model, interleaves the companion-generation steps, and reconciles completion. It does NOT re-decompose the plan (the build-decompose playbook owns the task graph), does NOT re-specify the per-task dispatch mechanics (single-flight lock / context-pack / change-set capture / verify — the build-dispatch playbook owns those; the scale orchestrator INVOKES that contract per slot), and does NOT itself author schemas / fields / code (the coding agents do that at dispatch time). Evidence of re-decomposition, re-authoring the single-task dispatch contract, or the orchestrator authoring code itself is a CONCERN (scope creep out of the scale lane). (The checklist is declarative: nothing executes it; the deterministic gates and the creator's approval remain the floors.)\n",
|
|
28
24
|
"skillRefs": [
|
|
29
25
|
"journey-status",
|
|
30
26
|
"journey-approve",
|
|
@@ -32,7 +28,9 @@
|
|
|
32
28
|
"journey-report"
|
|
33
29
|
],
|
|
34
30
|
"contextSources": [],
|
|
35
|
-
"suspendsForClarification": false
|
|
31
|
+
"suspendsForClarification": false,
|
|
32
|
+
"briefAdequacyGate": false,
|
|
33
|
+
"briefAdequacyExcludedSources": []
|
|
36
34
|
},
|
|
37
35
|
"executor": "coding_agent",
|
|
38
36
|
"approval": "approve_before",
|
|
@@ -81,10 +81,6 @@ anything:
|
|
|
81
81
|
which modules are MVP-critical vs later) and the **VisionSnapshot**
|
|
82
82
|
(`vision-brief` — the product framing and differentiation).
|
|
83
83
|
|
|
84
|
-
// TODO CLI COMMAND: wildo context journey-status
|
|
85
|
-
// (read current journey scope + approved artifacts + any existing domain plan)
|
|
86
|
-
// TODO CLI COMMAND: wildo context requirements
|
|
87
|
-
// (read the functional / non-functional requirements to decompose)
|
|
88
84
|
|
|
89
85
|
You **read** `requirements` + `market-snapshot` + `feature-drafts` + `roadmap` +
|
|
90
86
|
`vision-brief`; you **write** the `domain-plan` families.
|
|
@@ -7,10 +7,6 @@
|
|
|
7
7
|
"model_domain_graph"
|
|
8
8
|
],
|
|
9
9
|
"preconditions": [
|
|
10
|
-
{
|
|
11
|
-
"kind": "phase_is",
|
|
12
|
-
"phase": "bottom_up"
|
|
13
|
-
},
|
|
14
10
|
{
|
|
15
11
|
"kind": "artifact_exists",
|
|
16
12
|
"selector": {
|
|
@@ -51,7 +47,7 @@
|
|
|
51
47
|
],
|
|
52
48
|
"stepOutputs": [],
|
|
53
49
|
"method": {
|
|
54
|
-
"guidance": "# Domain Plan — Definition Set → Modules + Resources + Relationships (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to be\n> iterated. The decomposition heuristic, the resource-inventory convention, and\n> the relationship-intent shape below are deliberately explicit so they can be\n> tuned against real runs — treat them as a starting rubric, not a frozen\n> contract. The *analytical depth* of domain modelling (a full ERD, a\n> cardinality-to-FK solver and full domain-graph validation) is intentionally\n> shallow here and is deepened in a later phase; do\n> not perfect it in this playbook.\n\n## Where you are in the journey\n\nThis is the **first bottom-up playbook** — the pivot from **product definition**\n(top-down: vision, market, requirements, roadmap, business model) to **project\ndefinition** (bottom-up: the app's modules, resources, and how they relate). It\nruns **only after** the exact\n`top_down-to-bottom_up.bootstrap-non-regulated@0.1.0` route has produced a\ndurable `top_down → bottom_up` transition-commit fact. That fact proves the\nroute-bound readiness, semantic decision, Authority Request/Decision and phase\neffect chain; it is not an arbitrary approval flag. The separate\n`phase_is bottom_up` predicate checks the current phase projection. You are not\nre-opening product questions here — you are turning the currently accepted\nproduct definition into the *shape of the software that delivers it*.\n\n## What this playbook does\n\nYou are the **domain architect**. This playbook reads the approved definition set\nand drafts the **domain plan**: the answer to *\"what modules does this app have,\nwhat resources live in each, and how do those resources relate?\"* You produce\n**two artifacts**:\n\n1. The **domain-plan** family — the **module decomposition** with a **per-module\n resource inventory**, authored as a collection of **ModuleBusinessSemantics\n drafts** (one per proposed module). Each module draft states its purpose, its\n business capability, its primary actors, and its resource inventory\n (`mainResources` — the semantic center of the module; `supportingResources` —\n resources that support without being the center). The resource inventory lives\n **inside** each module draft because an inventory is inherently *per module*.\n2. The **relationship drafts** — carried INSIDE the same domain-plan value — the **inter-resource relationship\n intents**: for each durable association between two inventoried resources, the\n two ends, the **cardinality intent** (one-to-one / one-to-many / many-to-many),\n and the **ownership direction** (which resource holds the reference). These are\n typed conceptual drafts — a relationship is not a module, so it earns its own\n family, and the build loop consumes it when it wires FK fields.\n\nThis is a **planning pass**. You name modules, the resources inside them, and how\nthey relate. You do **not** author schemas, resolve a cardinality intent into a\nconcrete foreign-key field, or generate any code — that is the **bottom-up build\nloop's** job, downstream of this plan.\n\n## Read state first — the definition set you read, the two artifacts you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*. Before drafting\nanything:\n\n1. Read the current journey state and scope through the `journey-status` skill (it\n owns the read; do not re-derive it here). Confirm the top-down set is present\n and approved, and check whether a `domain-plan` already\n exist from an earlier run (refine them, do not re-author — see below).\n2. Read the approved definition set. **Load-bearing** (these drive the\n decomposition): the **requirements** (`requirements` family — the functional and\n non-functional requirements the domain must satisfy), the capability-mapped\n **MarketSnapshot** (`market-snapshot` — the benefits wired to their delivering\n features, so you know what capability each feature carries), and the\n **feature-drafts** (the prose capability contracts — what each delivering\n feature actually is). **Contextual** (they shape emphasis, not the core\n decomposition): the **roadmap** (`roadmap` — the release phasing, so you can see\n which modules are MVP-critical vs later) and the **VisionSnapshot**\n (`vision-brief` — the product framing and differentiation).\n\n// TODO CLI COMMAND: wildo context journey-status\n// (read current journey scope + approved artifacts + any existing domain plan)\n// TODO CLI COMMAND: wildo context requirements\n// (read the functional / non-functional requirements to decompose)\n\nYou **read** `requirements` + `market-snapshot` + `feature-drafts` + `roadmap` +\n`vision-brief`; you **write** the `domain-plan` families.\n\n## Step 1 — Derive the modules (the decomposition)\n\nA **module** is a bounded slice of the app that delivers a coherent business\ncapability. Derive modules by **clustering** the definition set, not by guessing:\n\n1. **Cluster requirements and features by capability.** Group the functional\n requirements and the feature-drafts that serve one coherent capability (e.g.\n \"everything about authoring and tracking tasks\", \"everything about billing and\n plans\"). Each tight cluster is a candidate module. A feature-draft and the\n requirements it realises usually land in the same module.\n2. **Name each module and state its semantics.** For each candidate module author a\n `ModuleBusinessSemantics` draft: a `relatedModuleId` (the id the module registry\n will use — it must be **distinct across all module drafts**; two modules sharing\n an id silently collide, since the registry addresses modules by id), a `purpose`\n (why the module exists, in plain language), a\n `businessCapability` (the capability it delivers), the `primaryActors` (the\n human/business actors that interact with it), and — optionally — a\n `businessDomain` (the larger bounded-context label) and `integrationSurfaces`\n (named surfaces the module participates in).\n3. **Keep modules justified.** Every module must earn its existence from\n requirements or features in the definition set. Do **not** invent a module the\n definition set does not call for — a speculative module is a coherence CONCERN\n (see the quality gate). Conversely, if a requirement or feature has no home\n module, you are missing a module (a coverage GAP).\n\nThe `resource-add-module` skill carries the module-scaffolding vocabulary (what a\nmodule is across the project layout); read it to keep module boundaries idiomatic.\n\n## Step 2 — Inventory the resources per module\n\nFor each module, list the **resources** (persisted entity types) it owns. The\ninventory is **two lists on the module draft**:\n\n- **`mainResources`** — the resources that form the semantic **center** of the\n module (the entities the module is *about*: a `tasks` module's `task`).\n- **`supportingResources`** — resources that **support** the module's capability\n without being its center (lookup tables, join/junction entities, per-entity\n settings). A resource that is the center of the module belongs in `mainResources`,\n not here.\n\nRules for a plausible inventory:\n\n- **Derive resources from the requirements + feature-drafts**, not from a blank\n page: a requirement that says \"users can label tasks\" implies a `task` resource\n and (probably) a `label` resource. The `resource-add-resource` skill carries the\n vocabulary for what a resource is; read it to keep the inventory idiomatic.\n- **Each resource is inventoried in exactly one module** as its `mainResource`. A\n resource that is genuinely shared across modules is a signal you either have the\n module boundary wrong or you need a relationship (Step 3), not the same main\n resource duplicated in two modules.\n- **Do not author fields or schemas here.** The inventory names the resource and\n says which module owns it. What fields the resource carries, its enums, its\n decorators — all of that is the **build loop's** job. If you catch yourself\n writing a field list, stop: that is out of this playbook's depth.\n\n## Step 3 — Draft the inter-resource relationships\n\nOnce the resources are inventoried, capture how they **relate**. For each durable\nassociation between two inventoried resources, author a **relationship draft** in\nthe relationship drafts (inside the domain-plan value) stating:\n\n- **The two ends** — the two resources that relate (both must be inventoried in\n some module's inventory from Step 2; a relationship to an un-inventoried resource\n is a coverage GAP).\n- **The cardinality intent** — one-to-one, one-to-many, or many-to-many. This is an\n *intent*, in prose; you are not resolving it into a foreign-key placement here.\n- **The ownership direction** — which resource conceptually **holds** the reference\n (e.g. \"a `task` belongs to a `project`\" → the `task` end holds the reference).\n This is the *intent* the build loop needs; it does **not** decide the physical FK\n holder (that resolution — FK holder from cardinality, discriminator relationships,\n conditional relationships — is the `module-relationships` skill's job at build\n time, **not** here).\n\nThe `module-relationships` skill carries the technical HOW of realising a\nrelationship (FK fields, cardinality-to-FK-holder resolution, conditional /\ndiscriminator relationships). Read it to keep your relationship *intents* aligned\nwith what the build loop can actually wire — but do **not** perform that wiring in\nthis planning pass.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not rename or re-decompose modules\n that are already correct. Only add a module, move a resource to a different\n module, or add/correct a relationship where the plan genuinely changed.\n- **Reuse existing module ids.** A module that already exists keeps its\n `relatedModuleId` — never mint a second id for the same module. Likewise, keep a\n resource's name stable across runs.\n- **Never orphan a relationship.** A relationship draft must name two resources\n that are actually inventoried in Step 2. If you move or rename a resource, follow\n it into every relationship draft that references it.\n\n## Executable semantic evaluation — `domain-plan-output-set-result`\n\nThe staged output set first passes deterministic structural validation: exact\nmodule/resource identities, typed relationship ends, unique ownership, and the\natomic manifest must all be valid. That is a non-bypassable eligibility floor,\nnot a semantic quality opinion.\n\nThe companion then executes the playbook's structured semantic Treatment over\nthe exact staged output-set artifact. Its six criteria remain distinct:\nrequirement coverage, feature coverage, module justification, inventory\nplausibility, relationship integrity, and planning-depth boundary discipline.\nEach criterion produces PASS / CONCERN / GAP / INDETERMINATE evidence, and the\nworst-verdict aggregation policy determines the Decision Rule consequence.\n\nA semantic PASS does **not** accept or publish the candidate. It transitions the\nresult Decision Point to `AUTHORITY_REQUIRED`; an explicit operator authority\ndecision is a separate later boundary. CONCERN or GAP requests revision,\nINDETERMINATE requests evidence, and evaluator or hard-floor failure blocks\nclosed. The evaluation path never mutates accepted specification heads.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. Explicitly **out of scope here**:\n\n- **Schema / field authoring.** The inventory names resources and their owning\n module; it does **not** author fields, enums, decorators, or Zod schemas. That is\n the build loop. If you catch yourself writing a field list, stop.\n- **Cardinality-to-FK resolution.** A relationship draft states a cardinality\n *intent* and an ownership *intent* in prose. Resolving that into a physical\n foreign-key holder, a discriminator relationship, or a conditional relationship is\n the `module-relationships` skill's job **at build time**, not here.\n- **A full ERD / domain-graph solver.** Phases-of-a-graph, transitive dependency\n ordering, normalization analysis, and diagram generation are a later-phase\n concern. You draft modules, an inventory, and relationship intents — not a solved\n entity-relationship diagram.\n- **A full domain-graph solver.** The framework now ships a typed conceptual\n relationship-draft contract and deterministic structural validation for the\n atomic output set. It deliberately does not solve physical FK placement,\n normalization, graph execution order, discriminator relationships, or\n conditional relationships; those remain build-depth concerns.\n- **Code generation / module registration.** Scaffolding the module folders,\n registering the module across runtimes, generating resource files — all of that is\n the bottom-up build loop, downstream of this plan.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nTwo artifacts for this journey:\n\n- The **domain-plan** under `specifications/src/domain-plan/` — a\n collection of `ModuleBusinessSemantics` drafts: the module decomposition, each\n module carrying its purpose, business capability, primary actors, and its\n `mainResources` / `supportingResources` inventory.\n- The **relationship drafts** inside the landed `specifications/src/domain-plan/` value\n — the inter-resource relationship intents (two ends + cardinality intent +\n ownership direction) between inventoried resources.\n\nAfter deterministic validation and semantic PASS, the runtime creates a distinct\nresult-bound Authority Request for the exact staged output-set digest. The local\noperator's explicit interface response settles that request; transition authority\ncannot substitute for it. Only then may the atomic specification-family mutation\naccept both files together for consumption by the bottom-up build loop.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state and\n scope, and confirm the approved top-down set is in place to plan the domain from.\n- `.claude/skills/resource-add-module/SKILL.md` — the module-scaffolding vocabulary\n (what a module is across the project layout); keeps module boundaries idiomatic.\n- `.claude/skills/resource-add-resource/SKILL.md` — the resource vocabulary (what a\n resource is); keeps the per-module inventory idiomatic.\n- `.claude/skills/module-relationships/SKILL.md` — the technical HOW of realising a\n relationship (FK fields, cardinality-to-FK-holder resolution, conditional /\n discriminator relationships) — consulted so relationship *intents* align with what\n the build loop can wire, NOT performed in this planning pass.\n",
|
|
50
|
+
"guidance": "# Domain Plan — Definition Set → Modules + Resources + Relationships (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to be\n> iterated. The decomposition heuristic, the resource-inventory convention, and\n> the relationship-intent shape below are deliberately explicit so they can be\n> tuned against real runs — treat them as a starting rubric, not a frozen\n> contract. The *analytical depth* of domain modelling (a full ERD, a\n> cardinality-to-FK solver and full domain-graph validation) is intentionally\n> shallow here and is deepened in a later phase; do\n> not perfect it in this playbook.\n\n## Where you are in the journey\n\nThis is the **first bottom-up playbook** — the pivot from **product definition**\n(top-down: vision, market, requirements, roadmap, business model) to **project\ndefinition** (bottom-up: the app's modules, resources, and how they relate). It\nruns **only after** the exact\n`top_down-to-bottom_up.bootstrap-non-regulated@0.1.0` route has produced a\ndurable `top_down → bottom_up` transition-commit fact. That fact proves the\nroute-bound readiness, semantic decision, Authority Request/Decision and phase\neffect chain; it is not an arbitrary approval flag. The separate\n`phase_is bottom_up` predicate checks the current phase projection. You are not\nre-opening product questions here — you are turning the currently accepted\nproduct definition into the *shape of the software that delivers it*.\n\n## What this playbook does\n\nYou are the **domain architect**. This playbook reads the approved definition set\nand drafts the **domain plan**: the answer to *\"what modules does this app have,\nwhat resources live in each, and how do those resources relate?\"* You produce\n**two artifacts**:\n\n1. The **domain-plan** family — the **module decomposition** with a **per-module\n resource inventory**, authored as a collection of **ModuleBusinessSemantics\n drafts** (one per proposed module). Each module draft states its purpose, its\n business capability, its primary actors, and its resource inventory\n (`mainResources` — the semantic center of the module; `supportingResources` —\n resources that support without being the center). The resource inventory lives\n **inside** each module draft because an inventory is inherently *per module*.\n2. The **relationship drafts** — carried INSIDE the same domain-plan value — the **inter-resource relationship\n intents**: for each durable association between two inventoried resources, the\n two ends, the **cardinality intent** (one-to-one / one-to-many / many-to-many),\n and the **ownership direction** (which resource holds the reference). These are\n typed conceptual drafts — a relationship is not a module, so it earns its own\n family, and the build loop consumes it when it wires FK fields.\n\nThis is a **planning pass**. You name modules, the resources inside them, and how\nthey relate. You do **not** author schemas, resolve a cardinality intent into a\nconcrete foreign-key field, or generate any code — that is the **bottom-up build\nloop's** job, downstream of this plan.\n\n## Read state first — the definition set you read, the two artifacts you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*. Before drafting\nanything:\n\n1. Read the current journey state and scope through the `journey-status` skill (it\n owns the read; do not re-derive it here). Confirm the top-down set is present\n and approved, and check whether a `domain-plan` already\n exist from an earlier run (refine them, do not re-author — see below).\n2. Read the approved definition set. **Load-bearing** (these drive the\n decomposition): the **requirements** (`requirements` family — the functional and\n non-functional requirements the domain must satisfy), the capability-mapped\n **MarketSnapshot** (`market-snapshot` — the benefits wired to their delivering\n features, so you know what capability each feature carries), and the\n **feature-drafts** (the prose capability contracts — what each delivering\n feature actually is). **Contextual** (they shape emphasis, not the core\n decomposition): the **roadmap** (`roadmap` — the release phasing, so you can see\n which modules are MVP-critical vs later) and the **VisionSnapshot**\n (`vision-brief` — the product framing and differentiation).\n\n\nYou **read** `requirements` + `market-snapshot` + `feature-drafts` + `roadmap` +\n`vision-brief`; you **write** the `domain-plan` families.\n\n## Step 1 — Derive the modules (the decomposition)\n\nA **module** is a bounded slice of the app that delivers a coherent business\ncapability. Derive modules by **clustering** the definition set, not by guessing:\n\n1. **Cluster requirements and features by capability.** Group the functional\n requirements and the feature-drafts that serve one coherent capability (e.g.\n \"everything about authoring and tracking tasks\", \"everything about billing and\n plans\"). Each tight cluster is a candidate module. A feature-draft and the\n requirements it realises usually land in the same module.\n2. **Name each module and state its semantics.** For each candidate module author a\n `ModuleBusinessSemantics` draft: a `relatedModuleId` (the id the module registry\n will use — it must be **distinct across all module drafts**; two modules sharing\n an id silently collide, since the registry addresses modules by id), a `purpose`\n (why the module exists, in plain language), a\n `businessCapability` (the capability it delivers), the `primaryActors` (the\n human/business actors that interact with it), and — optionally — a\n `businessDomain` (the larger bounded-context label) and `integrationSurfaces`\n (named surfaces the module participates in).\n3. **Keep modules justified.** Every module must earn its existence from\n requirements or features in the definition set. Do **not** invent a module the\n definition set does not call for — a speculative module is a coherence CONCERN\n (see the quality gate). Conversely, if a requirement or feature has no home\n module, you are missing a module (a coverage GAP).\n\nThe `resource-add-module` skill carries the module-scaffolding vocabulary (what a\nmodule is across the project layout); read it to keep module boundaries idiomatic.\n\n## Step 2 — Inventory the resources per module\n\nFor each module, list the **resources** (persisted entity types) it owns. The\ninventory is **two lists on the module draft**:\n\n- **`mainResources`** — the resources that form the semantic **center** of the\n module (the entities the module is *about*: a `tasks` module's `task`).\n- **`supportingResources`** — resources that **support** the module's capability\n without being its center (lookup tables, join/junction entities, per-entity\n settings). A resource that is the center of the module belongs in `mainResources`,\n not here.\n\nRules for a plausible inventory:\n\n- **Derive resources from the requirements + feature-drafts**, not from a blank\n page: a requirement that says \"users can label tasks\" implies a `task` resource\n and (probably) a `label` resource. The `resource-add-resource` skill carries the\n vocabulary for what a resource is; read it to keep the inventory idiomatic.\n- **Each resource is inventoried in exactly one module** as its `mainResource`. A\n resource that is genuinely shared across modules is a signal you either have the\n module boundary wrong or you need a relationship (Step 3), not the same main\n resource duplicated in two modules.\n- **Do not author fields or schemas here.** The inventory names the resource and\n says which module owns it. What fields the resource carries, its enums, its\n decorators — all of that is the **build loop's** job. If you catch yourself\n writing a field list, stop: that is out of this playbook's depth.\n\n## Step 3 — Draft the inter-resource relationships\n\nOnce the resources are inventoried, capture how they **relate**. For each durable\nassociation between two inventoried resources, author a **relationship draft** in\nthe relationship drafts (inside the domain-plan value) stating:\n\n- **The two ends** — the two resources that relate (both must be inventoried in\n some module's inventory from Step 2; a relationship to an un-inventoried resource\n is a coverage GAP).\n- **The cardinality intent** — one-to-one, one-to-many, or many-to-many. This is an\n *intent*, in prose; you are not resolving it into a foreign-key placement here.\n- **The ownership direction** — which resource conceptually **holds** the reference\n (e.g. \"a `task` belongs to a `project`\" → the `task` end holds the reference).\n This is the *intent* the build loop needs; it does **not** decide the physical FK\n holder (that resolution — FK holder from cardinality, discriminator relationships,\n conditional relationships — is the `module-relationships` skill's job at build\n time, **not** here).\n\nThe `module-relationships` skill carries the technical HOW of realising a\nrelationship (FK fields, cardinality-to-FK-holder resolution, conditional /\ndiscriminator relationships). Read it to keep your relationship *intents* aligned\nwith what the build loop can actually wire — but do **not** perform that wiring in\nthis planning pass.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not rename or re-decompose modules\n that are already correct. Only add a module, move a resource to a different\n module, or add/correct a relationship where the plan genuinely changed.\n- **Reuse existing module ids.** A module that already exists keeps its\n `relatedModuleId` — never mint a second id for the same module. Likewise, keep a\n resource's name stable across runs.\n- **Never orphan a relationship.** A relationship draft must name two resources\n that are actually inventoried in Step 2. If you move or rename a resource, follow\n it into every relationship draft that references it.\n\n## Executable semantic evaluation — `domain-plan-output-set-result`\n\nThe staged output set first passes deterministic structural validation: exact\nmodule/resource identities, typed relationship ends, unique ownership, and the\natomic manifest must all be valid. That is a non-bypassable eligibility floor,\nnot a semantic quality opinion.\n\nThe companion then executes the playbook's structured semantic Treatment over\nthe exact staged output-set artifact. Its six criteria remain distinct:\nrequirement coverage, feature coverage, module justification, inventory\nplausibility, relationship integrity, and planning-depth boundary discipline.\nEach criterion produces PASS / CONCERN / GAP / INDETERMINATE evidence, and the\nworst-verdict aggregation policy determines the Decision Rule consequence.\n\nA semantic PASS does **not** accept or publish the candidate. It transitions the\nresult Decision Point to `AUTHORITY_REQUIRED`; an explicit operator authority\ndecision is a separate later boundary. CONCERN or GAP requests revision,\nINDETERMINATE requests evidence, and evaluator or hard-floor failure blocks\nclosed. The evaluation path never mutates accepted specification heads.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. Explicitly **out of scope here**:\n\n- **Schema / field authoring.** The inventory names resources and their owning\n module; it does **not** author fields, enums, decorators, or Zod schemas. That is\n the build loop. If you catch yourself writing a field list, stop.\n- **Cardinality-to-FK resolution.** A relationship draft states a cardinality\n *intent* and an ownership *intent* in prose. Resolving that into a physical\n foreign-key holder, a discriminator relationship, or a conditional relationship is\n the `module-relationships` skill's job **at build time**, not here.\n- **A full ERD / domain-graph solver.** Phases-of-a-graph, transitive dependency\n ordering, normalization analysis, and diagram generation are a later-phase\n concern. You draft modules, an inventory, and relationship intents — not a solved\n entity-relationship diagram.\n- **A full domain-graph solver.** The framework now ships a typed conceptual\n relationship-draft contract and deterministic structural validation for the\n atomic output set. It deliberately does not solve physical FK placement,\n normalization, graph execution order, discriminator relationships, or\n conditional relationships; those remain build-depth concerns.\n- **Code generation / module registration.** Scaffolding the module folders,\n registering the module across runtimes, generating resource files — all of that is\n the bottom-up build loop, downstream of this plan.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nTwo artifacts for this journey:\n\n- The **domain-plan** under `specifications/src/domain-plan/` — a\n collection of `ModuleBusinessSemantics` drafts: the module decomposition, each\n module carrying its purpose, business capability, primary actors, and its\n `mainResources` / `supportingResources` inventory.\n- The **relationship drafts** inside the landed `specifications/src/domain-plan/` value\n — the inter-resource relationship intents (two ends + cardinality intent +\n ownership direction) between inventoried resources.\n\nAfter deterministic validation and semantic PASS, the runtime creates a distinct\nresult-bound Authority Request for the exact staged output-set digest. The local\noperator's explicit interface response settles that request; transition authority\ncannot substitute for it. Only then may the atomic specification-family mutation\naccept both files together for consumption by the bottom-up build loop.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state and\n scope, and confirm the approved top-down set is in place to plan the domain from.\n- `.claude/skills/resource-add-module/SKILL.md` — the module-scaffolding vocabulary\n (what a module is across the project layout); keeps module boundaries idiomatic.\n- `.claude/skills/resource-add-resource/SKILL.md` — the resource vocabulary (what a\n resource is); keeps the per-module inventory idiomatic.\n- `.claude/skills/module-relationships/SKILL.md` — the technical HOW of realising a\n relationship (FK fields, cardinality-to-FK-holder resolution, conditional /\n discriminator relationships) — consulted so relationship *intents* align with what\n the build loop can wire, NOT performed in this planning pass.\n",
|
|
55
51
|
"skillRefs": [
|
|
56
52
|
"journey-status",
|
|
57
53
|
"resource-add-module",
|
|
@@ -72,7 +68,9 @@
|
|
|
72
68
|
]
|
|
73
69
|
},
|
|
74
70
|
"contextSources": [],
|
|
75
|
-
"suspendsForClarification": true
|
|
71
|
+
"suspendsForClarification": true,
|
|
72
|
+
"briefAdequacyGate": false,
|
|
73
|
+
"briefAdequacyExcludedSources": []
|
|
76
74
|
},
|
|
77
75
|
"executor": "companion_agent",
|
|
78
76
|
"approval": "approve_result",
|
|
@@ -18,7 +18,7 @@ Read and apply these patterns from the application-developer point of view:
|
|
|
18
18
|
> the provider-selection rubric are deliberately explicit so they can be tuned
|
|
19
19
|
> against real runs. The deterministic steps that *materialize the skeleton* and
|
|
20
20
|
> *install app-knowledge* are a later greenfield-enablement phase and are **not
|
|
21
|
-
> built**. Those two steps are authored as
|
|
21
|
+
> built**. Those two steps are authored as explicit deferred-tooling notes;
|
|
22
22
|
> headless setup and verified local initialization are registered commands. **This playbook is the
|
|
23
23
|
> METHOD — the description of the foundation sequence — not a runnable
|
|
24
24
|
> foundation.** If you find yourself building or wiring the greenfield CLI
|
|
@@ -48,16 +48,19 @@ into the *configured application skeleton the build loop then fills in*.
|
|
|
48
48
|
You are the **foundation engineer**. This playbook reads the approved domain plan
|
|
49
49
|
and the vision brief, then configures and brings up the application skeleton so the
|
|
50
50
|
build loop has a real workspace to author into. You perform a **mixed sequence**
|
|
51
|
-
(
|
|
51
|
+
(the runner sequences the tiers per this guidance):
|
|
52
52
|
a config/skeleton **authoring** pass, then a **deterministic bring-up** pass. The
|
|
53
53
|
work, in order:
|
|
54
54
|
|
|
55
55
|
1. **Derive the engine capabilities** from the compliance/vision constraints (and
|
|
56
56
|
the market/business-model facts) and enable them in `./wildo.saas.config.ts`.
|
|
57
57
|
2. **Declare the domain-plan's modules** at the SaaS root (they are registered across
|
|
58
|
-
the runtimes after Step
|
|
58
|
+
the runtimes after Step 5 materializes the skeleton, so it boots with them).
|
|
59
59
|
3. **Select the providers** the enabled capabilities need.
|
|
60
|
-
4. **
|
|
60
|
+
4. **Record the compliance declarations you were given** — the operating entity and
|
|
61
|
+
the jurisdictions, from the elicitation answers, into `./wildo.saas.config.ts`.
|
|
62
|
+
See `config-saas` and its `references/compliance-declarations.md`.
|
|
63
|
+
5. **Run the deterministic bring-up** — materialize the skeleton, install
|
|
61
64
|
app-knowledge, `wildo setup --non-interactive`, then `wildo local init`.
|
|
62
65
|
|
|
63
66
|
You emit **no artifact**. The deliverable is the app itself: `./wildo.saas.config.ts`,
|
|
@@ -65,10 +68,6 @@ the materialized skeleton, and a verified local initialization. Record *why* eac
|
|
|
65
68
|
capability, module and provider was chosen in the config's own comments, where the
|
|
66
69
|
next reader of that file will find it.
|
|
67
70
|
|
|
68
|
-
(A `foundation-manifest` artifact was declared here until 2026-08-25 and is now
|
|
69
|
-
retired with the app-creation verification/digest aspect. It was a bookkeeping record
|
|
70
|
-
of decisions the config already carries — deleting it costs no fact about the app.)
|
|
71
|
-
|
|
72
71
|
This is a **foundation pass**. You enable capabilities, declare modules as shells,
|
|
73
72
|
select providers, and bring the skeleton up. You do **not** author resource schemas,
|
|
74
73
|
fields, ui-behavior, views, or navigation — that is the **build loop's** job,
|
|
@@ -99,10 +98,9 @@ anything:
|
|
|
99
98
|
- the **roadmap** (which modules are MVP-critical, so you enable what the first
|
|
100
99
|
release needs and defer the rest).
|
|
101
100
|
|
|
102
|
-
//
|
|
103
|
-
//
|
|
104
|
-
//
|
|
105
|
-
// (read the modules to register + their per-module resource inventory)
|
|
101
|
+
// Operator affordances (the executor itself is handed the domain-plan VALUE directly):
|
|
102
|
+
// `wildo context journey` — current phase, the eligibility board, runs in flight
|
|
103
|
+
// `wildo context info specification-artifacts` — per-family landed state and rendered content
|
|
106
104
|
|
|
107
105
|
You **read** `domain-plan` + `vision-brief` + `market-snapshot` + `business-model`
|
|
108
106
|
+ `requirements` + `roadmap` (the domain plan carries its relationship drafts); you **write**
|
|
@@ -143,15 +141,15 @@ enabled capability **and its justification** as a comment beside it in the confi
|
|
|
143
141
|
|
|
144
142
|
**Mind the ordering.** At *config-authoring* time (this step, before the skeleton
|
|
145
143
|
exists) you can only **declare** the modules at the SaaS root. The shared / frontend /
|
|
146
|
-
backend module registry files do not exist until Step
|
|
144
|
+
backend module registry files do not exist until Step 5 materializes the skeleton, so
|
|
147
145
|
the cross-runtime **registration** happens *after* materialization — do not edit
|
|
148
146
|
registry files the skeleton has not yet created.
|
|
149
147
|
|
|
150
148
|
1. **Declare each module at the SaaS root (now).** Add each domain-plan module to the
|
|
151
149
|
`modules` composition in `./wildo.saas.config.ts` (the `config-saas` skill owns this
|
|
152
150
|
surface). This declares the module's *existence* and is exactly what the skeleton
|
|
153
|
-
materialization (Step
|
|
154
|
-
2. **Register across the runtimes (after Step
|
|
151
|
+
materialization (Step 5) builds the per-module workspaces and registries from.
|
|
152
|
+
2. **Register across the runtimes (after Step 5 materializes the skeleton).** Once the
|
|
155
153
|
skeleton exists, each declared module is registered across the shared / frontend /
|
|
156
154
|
backend registries so every runtime loads it — regenerated by `config sync` from the
|
|
157
155
|
declared modules where the tooling supports it, or wired with the `module-registration`
|
|
@@ -184,7 +182,36 @@ the provider surfaces):
|
|
|
184
182
|
bring-up / environment step, not authored inline. Record the selected providers
|
|
185
183
|
(each matched to its capability) as a comment beside it in the config.
|
|
186
184
|
|
|
187
|
-
## Step 4 —
|
|
185
|
+
## Step 4 — Record the compliance declarations (only what you were told)
|
|
186
|
+
|
|
187
|
+
The creator answered `operating-entity` and `operating-jurisdictions`. Write those answers
|
|
188
|
+
into `operatorComplianceIdentity` and `operatingJurisdictions`, and **nothing else**.
|
|
189
|
+
|
|
190
|
+
- **Record the PART you were given.** Every part of `operatorComplianceIdentity` is
|
|
191
|
+
independently declarable, so a creator who named the company and not its lawful bases
|
|
192
|
+
gets `legalEntityName` and `registeredAddress` written and the rest left absent. A
|
|
193
|
+
missing part is reported downstream as outstanding; it does not block anything here.
|
|
194
|
+
- **NEVER invent one.** Not a company name, not an address, not a privacy contact, and
|
|
195
|
+
above all not a lawful basis — that is a legal determination, and `CONSENT` in
|
|
196
|
+
particular would tell a person their data rests on an agreement they could withdraw.
|
|
197
|
+
A produced privacy notice quotes these as fact. An absent declaration is reported as an
|
|
198
|
+
open gap a reader can see; an invented one is published.
|
|
199
|
+
- **Omit the key entirely when you were told nothing.** Absence means "nobody answered",
|
|
200
|
+
which is the honest state and the one every consumer already renders correctly. An
|
|
201
|
+
empty object is refused by the schema precisely because it would satisfy the field while
|
|
202
|
+
disclosing nothing.
|
|
203
|
+
- **A jurisdiction needs its `basis`.** "eu" alone does not say whether you are established
|
|
204
|
+
there, sell there, or hold data about people there, and those imply different obligations.
|
|
205
|
+
If the creator gave a place without a reason, record neither — ask, or leave it out.
|
|
206
|
+
|
|
207
|
+
This step CANNOT fail the run. If the creator answered nothing, write nothing and continue:
|
|
208
|
+
the application boots, and the gap is visible where it matters rather than here.
|
|
209
|
+
|
|
210
|
+
(A `foundation-manifest` artifact was declared here until 2026-08-25 and is now
|
|
211
|
+
retired with the app-creation verification/digest aspect. It was a bookkeeping record
|
|
212
|
+
of decisions the config already carries — deleting it costs no fact about the app.)
|
|
213
|
+
|
|
214
|
+
## Step 5 — The deterministic bring-up sequence (partially deferred)
|
|
188
215
|
|
|
189
216
|
With the config authored, run the **deterministic bring-up** in prerequisite order.
|
|
190
217
|
The skeleton template and app-knowledge installer remain deferred; do not invent
|
|
@@ -196,15 +223,15 @@ executed after the app structure exists.
|
|
|
196
223
|
module registries from the empty-app template, so the declared modules have a real
|
|
197
224
|
workspace.
|
|
198
225
|
|
|
199
|
-
//
|
|
200
|
-
//
|
|
226
|
+
// (Deferred greenfield tooling: skeleton materialization is not yet a registered command —
|
|
227
|
+
// do not invent one.)
|
|
201
228
|
|
|
202
229
|
2. **Install app-knowledge** — drop the compiled skills / rules / agents into the
|
|
203
230
|
project's agent-config folders so the build loop's coding agent reads them
|
|
204
231
|
naturally with cwd at the app root.
|
|
205
232
|
|
|
206
|
-
//
|
|
207
|
-
//
|
|
233
|
+
// (Deferred greenfield tooling: the app-knowledge installer is not yet a registered command —
|
|
234
|
+
// do not invent one. `wildo fwk dev-skills` covers the framework-development flow only.)
|
|
208
235
|
|
|
209
236
|
3. **Run setup** — configure the app from the authored `./wildo.saas.config.ts` and
|
|
210
237
|
the `./infrastructure/` env configs (the `infra-environment-config` skill owns the
|
|
@@ -265,8 +292,8 @@ Keep this playbook at scaffold depth **and** honour the tooling deferral. Explic
|
|
|
265
292
|
|
|
266
293
|
- **The remaining greenfield CLI tooling itself.** The skeleton-materialization
|
|
267
294
|
template and app-knowledge installer do **not** exist yet and are a later
|
|
268
|
-
greenfield-enablement phase. Their two
|
|
269
|
-
|
|
295
|
+
greenfield-enablement phase. Their two deferred-tooling notes must not be turned
|
|
296
|
+
into invented commands. `wildo setup --non-interactive` and `wildo local init` do exist and are
|
|
270
297
|
the registered lifecycle once the app structure is present.
|
|
271
298
|
- **Resource / field / schema authoring.** The config declares modules as shells and
|
|
272
299
|
enables capabilities; it does **not** author resource schemas, fields, enums,
|
|
@@ -7,10 +7,6 @@
|
|
|
7
7
|
"configure_application_foundation"
|
|
8
8
|
],
|
|
9
9
|
"preconditions": [
|
|
10
|
-
{
|
|
11
|
-
"kind": "phase_is",
|
|
12
|
-
"phase": "bottom_up"
|
|
13
|
-
},
|
|
14
10
|
{
|
|
15
11
|
"kind": "artifact_exists",
|
|
16
12
|
"selector": {
|
|
@@ -47,7 +43,7 @@
|
|
|
47
43
|
"outputs": [],
|
|
48
44
|
"stepOutputs": [],
|
|
49
45
|
"method": {
|
|
50
|
-
"guidance": "# Foundation — Domain Plan → Configured, Bootable App Skeleton (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology, and part of the greenfield tooling it\n> sequences does not exist yet.** The foundation *sequence* below is a working first cut —\n> the capability-derivation heuristic, the module-registration convention, and\n> the provider-selection rubric are deliberately explicit so they can be tuned\n> against real runs. The deterministic steps that *materialize the skeleton* and\n> *install app-knowledge* are a later greenfield-enablement phase and are **not\n> built**. Those two steps are authored as `// TODO CLI COMMAND:` placeholders;\n> headless setup and verified local initialization are registered commands. **This playbook is the\n> METHOD — the description of the foundation sequence — not a runnable\n> foundation.** If you find yourself building or wiring the greenfield CLI\n> tooling, stop: that is out of this playbook's scope.\n\n## Where you are in the journey\n\nThis is the **foundation** playbook — the point in the **bottom-up** phase where\nthe *plan* becomes a *bootable app*. It runs **after** the `bottom_up.domain-plan`\nplaybook produced (and the creator approved) the **domain plan**: the module\ndecomposition, the per-module resource inventory, and the inter-resource\nrelationship intents. Its preconditions — `phase_is bottom_up` and\n`artifact_exists domain-plan` and `artifact_exists vision-brief` — mean the journey\nhas entered the build-shaping phase and the two load-bearing artifacts are present:\nthe **domain plan** (whose modules you register) and the **vision brief** (whose\ncompliance and vision constraints drive which engine capabilities you enable). The\nroute-bound `transition_committed` fact that authorized and applied crossing from top-down into\nbottom-up was the domain-plan playbook's duty (it is the first bottom-up playbook);\nyou do not re-cross that boundary — the domain plan's existence already sits behind\nit.\n\nYou are not re-opening the domain plan here — you are turning an *approved* plan\ninto the *configured application skeleton the build loop then fills in*.\n\n## What this playbook does\n\nYou are the **foundation engineer**. This playbook reads the approved domain plan\nand the vision brief, then configures and brings up the application skeleton so the\nbuild loop has a real workspace to author into. You perform a **mixed sequence**\n(hence the `composite` executor — the runner sequences the tiers per this guidance):\na config/skeleton **authoring** pass, then a **deterministic bring-up** pass. The\nwork, in order:\n\n1. **Derive the engine capabilities** from the compliance/vision constraints (and\n the market/business-model facts) and enable them in `./wildo.saas.config.ts`.\n2. **Declare the domain-plan's modules** at the SaaS root (they are registered across\n the runtimes after Step 4 materializes the skeleton, so it boots with them).\n3. **Select the providers** the enabled capabilities need.\n4. **Run the deterministic bring-up** — materialize the skeleton, install\n app-knowledge, `wildo setup --non-interactive`, then `wildo local init`.\n\nYou emit **no artifact**. The deliverable is the app itself: `./wildo.saas.config.ts`,\nthe materialized skeleton, and a verified local initialization. Record *why* each\ncapability, module and provider was chosen in the config's own comments, where the\nnext reader of that file will find it.\n\n(A `foundation-manifest` artifact was declared here until 2026-08-25 and is now\nretired with the app-creation verification/digest aspect. It was a bookkeeping record\nof decisions the config already carries — deleting it costs no fact about the app.)\n\nThis is a **foundation pass**. You enable capabilities, declare modules as shells,\nselect providers, and bring the skeleton up. You do **not** author resource schemas,\nfields, ui-behavior, views, or navigation — that is the **build loop's** job,\ndownstream of this foundation.\n\n## Read state first — the artifacts you read, the files you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*. Before configuring\nanything:\n\n1. Read the current journey state and scope through the `journey-status` skill (it\n owns the read; do not re-derive it here). Confirm the domain plan is present and\n approved, and check whether a `./wildo.saas.config.ts` already exists from an\n earlier run (refine it, do not re-author — see below).\n2. Read the **domain plan** (`domain-plan` family — the modules to register + their\n resource inventory) and the **vision brief** (`vision-brief` — the compliance and\n vision constraints that are the **primary** driver of capability selection).\n **Contextual** reads that sharpen the choices (they are *not* preconditions — read\n them if present, and note that the `business-model` may be absent, per the top-down\n phase-gate's optional posture):\n - the **market-snapshot** (`market-snapshot`) — its ICPs sharpen capability\n selection (a B2B / organization-scoped ICP → the `organizations` capability);\n - the **business-model** (`business-model`) — a paid plan → the billing capability\n (absent business model = no billing capability derived from it);\n - the **relationship drafts** inside the domain plan (the inter-resource relationships the build loop will\n wire — they can hint at which capabilities a module needs);\n - the **requirements** (functional/non-functional needs a capability may satisfy);\n - the **roadmap** (which modules are MVP-critical, so you enable what the first\n release needs and defer the rest).\n\n// TODO CLI COMMAND: wildo context journey-status\n// (read current journey scope + approved artifacts + any existing foundation config)\n// TODO CLI COMMAND: wildo context domain-plan\n// (read the modules to register + their per-module resource inventory)\n\nYou **read** `domain-plan` + `vision-brief` + `market-snapshot` + `business-model`\n+ `requirements` + `roadmap` (the domain plan carries its relationship drafts); you **write**\n`./wildo.saas.config.ts` and the materialized skeleton — app files, committed to git,\nwhich is where the record of what was decided lives.\n\n## Step 1 — Derive and enable the engine capabilities\n\nEngine capabilities are the framework surfaces the app turns on (organizations,\nbilling, notifications, audit trails, data residency, and so on). **Derive them from\nthe definition set — do not guess:**\n\n1. **Compliance/vision constraints → capabilities (the primary driver).** Walk the\n vision brief's constraints. A compliance constraint implies a capability (a privacy-law /\n data-residency constraint → the residency/audit capability; an external-assurance constraint →\n audit trails). A vision fact implies a capability (an organization-scoped product →\n `organizations`).\n2. **Market / business-model facts → capabilities (contextual sharpener).** A B2B or\n organization-scoped ICP in the `market-snapshot` → the `organizations` capability; a\n paid plan in the `business-model` → billing. Treat these as sharpeners over the\n primary compliance/vision derivation — and remember the `business-model` may be\n absent (then derive no billing capability from it).\n3. **Domain-plan needs → capabilities.** A module whose capability clearly needs a\n framework surface (a module that sends transactional email → notifications) turns\n on that capability.\n4. **Enable only what the definition set justifies.** Every enabled capability must\n trace to a compliance/vision constraint, a market/business-model fact, or a\n domain-plan module need. Do **not** enable a capability nothing asks for — that is\n speculative surface area (a coherence CONCERN — see the quality gate). Conversely,\n a compliance constraint that requires a capability you did **not** enable is a\n coverage GAP.\n\nThe `config-saas` skill carries the vocabulary for the `engineCapabilities` block of\n`./wildo.saas.config.ts`; read it to enable capabilities idiomatically. Record each\nenabled capability **and its justification** as a comment beside it in the config.\n\n## Step 2 — Declare the domain-plan's modules (register across runtimes after materialization)\n\n**Mind the ordering.** At *config-authoring* time (this step, before the skeleton\nexists) you can only **declare** the modules at the SaaS root. The shared / frontend /\nbackend module registry files do not exist until Step 4 materializes the skeleton, so\nthe cross-runtime **registration** happens *after* materialization — do not edit\nregistry files the skeleton has not yet created.\n\n1. **Declare each module at the SaaS root (now).** Add each domain-plan module to the\n `modules` composition in `./wildo.saas.config.ts` (the `config-saas` skill owns this\n surface). This declares the module's *existence* and is exactly what the skeleton\n materialization (Step 4) builds the per-module workspaces and registries from.\n2. **Register across the runtimes (after Step 4 materializes the skeleton).** Once the\n skeleton exists, each declared module is registered across the shared / frontend /\n backend registries so every runtime loads it — regenerated by `config sync` from the\n declared modules where the tooling supports it, or wired with the `module-registration`\n skill (distinct from `config-saas`, which only declares existence at the root). At\n foundation depth you register the module **shells** (the module exists and boots); the\n resources *inside* each module are authored by the build loop.\n3. **Declare every domain-plan module — and no more.** A module the domain plan named\n that is missing from the config is a GAP; a module in the config the domain plan did\n not name is an unjustified-module CONCERN. Record the declared modules (each traced\n to its domain-plan module) as a comment beside it in the config.\n\n**Do not author the resources here.** The domain plan's per-module resource inventory\ntells you *what* resources each module will own, but authoring their schemas, fields,\nand config is the **build loop's** job. If you catch yourself writing a resource\nschema, stop: that is out of this playbook's depth.\n\n## Step 3 — Select the providers\n\nEnabled capabilities that reach an external service need a **provider** (billing → a\npayment provider; notifications/email → an email provider; file storage → an object\nstore). For each such capability, select and wire the provider scope +\n`providerConfigurations` in `./wildo.saas.config.ts` (the `config-saas` skill covers\nthe provider surfaces):\n\n- **Every provider matches a declared capability.** A provider wired for no enabled\n capability is a CONCERN; an enabled capability that needs a provider with none\n selected is a GAP.\n- **Do not seed secrets here.** Provider *selection* (which provider, which scope) is\n foundation; the per-environment secret material is seeded by the deterministic\n bring-up / environment step, not authored inline. Record the selected providers\n (each matched to its capability) as a comment beside it in the config.\n\n## Step 4 — The deterministic bring-up sequence (partially deferred)\n\nWith the config authored, run the **deterministic bring-up** in prerequisite order.\nThe skeleton template and app-knowledge installer remain deferred; do not invent\nthem. Headless `wildo setup` and `wildo local init` are registered and should be\nexecuted after the app structure exists.\n\n1. **Materialize the app skeleton** — create the `./frontend/`, `./shared-lib/`,\n `./backend-api/`, `./specifications/`, and `./infrastructure/` workspaces + the\n module registries from the empty-app template, so the declared modules have a real\n workspace.\n\n // TODO CLI COMMAND: wildo materialize skeleton\n // (scaffold app/ shared-lib/ backend-api/ specifications/ + module registries — greenfield tooling, deferred)\n\n2. **Install app-knowledge** — drop the compiled skills / rules / agents into the\n project's agent-config folders so the build loop's coding agent reads them\n naturally with cwd at the app root.\n\n // TODO CLI COMMAND: wildo install app-knowledge\n // (install compiled skills/rules/agents into the app's .claude/ — greenfield tooling, deferred)\n\n3. **Run setup** — configure the app from the authored `./wildo.saas.config.ts` and\n the `./infrastructure/` env configs (the `infra-environment-config` skill owns the\n typed infra env files; the `local-environment-bootstrap` skill owns the `wildo`\n lifecycle). Headless setup is registered and fail-closed on the administrator seed\n environment variables; it mints the environment generation without placeholders.\n\n ```bash\n wildo setup --non-interactive\n ```\n\n4. **Initialize and verify the project** — run the registered convergence journey.\n It regenerates artifacts, starts and readiness-gates backing services, reconciles\n platform Mongo state and credentials, starts native platform services, registers the\n app once, emits all runtime projections, and executes a signed managed-config read.\n\n ```bash\n wildo local init\n ```\n\nReport the status of each bring-up step to the creator in your result. Skeleton\nmaterialization and app-knowledge installation remain deferred; setup and local\ninitialization are executable once those app files exist and must be recorded from their\nreal exit/postcondition result rather than marked complete from intent.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not disable a capability, drop a module,\n or re-select a provider that is already correct. Only enable a newly-justified\n capability, register a newly-added domain-plan module, or correct a provider where\n the definition set genuinely changed.\n- **Reuse existing module ids and provider scopes.** A module already registered keeps\n its id; a provider already selected keeps its scope — never mint a second one for the\n same module/capability.\n- **Follow the definition set.** If the domain plan added a module or the vision brief\n added a compliance constraint since the last run, reflect it (register the module,\n enable the capability) — do not re-derive the whole configuration from scratch. The\n delta is visible in `git diff` on the config, which is the record.\n\n## Quality gate — `foundation-configured-coherently` (declarative at scaffold depth)\n\nThe foundation is checked against the `foundation-configured-coherently` **reviewer\nchecklist** (see the end of this method): five invariants (capability derivation, module registration, provider coverage,\nsequence order, and foundation-depth boundary discipline), each marked PASS / CONCERN /\nGAP.\n\nThis checklist is **declarative**: no runtime executes it (rubric-only judge gates were retired at the flexible-intelligence hard cut — judgment runs only through a compiled Evaluation Treatment, and this playbook has none yet), so it ships as the **creator's review checklist** — nothing runs it automatically. The **trust floor** for accepting the foundation today is the\ncreator's `approve_result` review of the produced config and the bring-up result. There is\nintentionally **no deterministic gate**: config validation is a `wildo` CLI concern\n(`config sync` / validate), not a validator in the journey-artifact schemaRef\nvocabulary. When the greenfield tooling lands, the non-bypassable floor still\nhard-gates the real destructive / off-machine infra bring-up regardless of this gate.\n\n## Scaffold-depth and tooling-deferral boundary\n\nKeep this playbook at scaffold depth **and** honour the tooling deferral. Explicitly\n**out of scope here**:\n\n- **The remaining greenfield CLI tooling itself.** The skeleton-materialization\n template and app-knowledge installer do **not** exist yet and are a later\n greenfield-enablement phase. Their two `// TODO CLI COMMAND:` placeholders must not\n be invented. `wildo setup --non-interactive` and `wildo local init` do exist and are\n the registered lifecycle once the app structure is present.\n- **Resource / field / schema authoring.** The config declares modules as shells and\n enables capabilities; it does **not** author resource schemas, fields, enums,\n decorators, ui-behavior, views, or navigation. That is the build loop. If you catch\n yourself writing a resource, stop.\n- **Re-introducing a foundation artifact.** The `foundation-manifest` family was\n retired on 2026-08-25 with the app-creation verification/digest aspect. Do **NOT**\n reshape `_core` to bring it back: the config file and its git history already carry\n every decision it recorded.\n- **Deep capability / provider modelling.** A defended capability-selection model\n (per-compliance-regime obligation → capability mapping, provider cost/feature\n matrices, multi-provider fallback) is a later depth pass. You derive capabilities\n from the definition set with the v1 heuristic above — not a solved obligation graph.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at scaffold\ndepth — depth (and the greenfield tooling) are dedicated later passes done once,\nholistically.\n\n## What you emit\n\n- The authored **`./wildo.saas.config.ts`** (an app file) — the enabled engine\n capabilities, the registered modules, and the selected providers — plus the\n registered module shells across the runtimes and (when the tooling lands) the\n brought-up skeleton.\n- The **bring-up result** reported to the creator: the status of each step, taken from\n its real exit/postcondition rather than from intent. This is a report, not a stored\n artifact — nothing reads it back.\n\nThe creator reviews the result (approval posture `approve_result`) before it is\naccepted as the journey's foundation, which the bottom-up build loop then fills in\nwith authored resources, operations, UX, and integrations.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state and scope,\n and confirm the approved domain plan + vision brief are in place to configure from.\n- `.claude/skills/config-saas/SKILL.md` — the `./wildo.saas.config.ts` authoring\n surface: `engineCapabilities`, `modules`, provider scopes, and `providerConfigurations`.\n- `.claude/skills/module-registration/SKILL.md` — register each domain-plan module\n across the shared / frontend / backend registries so the skeleton boots with it\n (distinct from `config-saas`, which only declares module existence at the root).\n- `.claude/skills/infra-environment-config/SKILL.md` — the typed `./infrastructure/`\n environment configs (backing services, public domain, service auth) the bring-up needs.\n- `.claude/skills/local-environment-bootstrap/SKILL.md` — the `wildo` lifecycle\n (`setup`, `local init`, `local reinit`, `local dev`) for deterministic initialization,\n repair, clean-room recovery, and runtime start.\n\n## Reviewer checklist — `foundation-configured-coherently`\n\nFormerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is kept here, verbatim, minus the retired runner's closing sentence:\n\nJudge whether the authored foundation (the ./wildo.saas.config.ts composition + the materialized skeleton) is a coherent realisation of the approved domain plan and the top-down definition set. Assess five invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) CAPABILITY DERIVATION — every enabled engine capability traces to a compliance/vision, business-model, market, or domain-plan need; unjustified capabilities are a CONCERN and missing required capabilities are a GAP. (2) MODULE REGISTRATION — every approved domain-plan module is declared and registered across runtimes; missing modules are a GAP and extra modules are a CONCERN. (3) PROVIDER COVERAGE — every provider serves a declared capability and every provider-backed capability has a provider. (4) SEQUENCE ORDER AND PROOF — author config → materialize skeleton → install app-knowledge → wildo setup --non-interactive → wildo local init. Treat setup intent, container health, or an initialization marker as insufficient: local init must reach its signed managed-config-read postcondition. (5) BOUNDARY DISCIPLINE — stay at foundation depth and do not author resources, fields, ui-behavior, views, or navigation. Do not invent the still-deferred skeleton/app-knowledge installer commands; headless setup and local init are registered and should be executed once the structure exists. This reviewer checklist is declarative; creator approval is the trust floor.\n",
|
|
46
|
+
"guidance": "# Foundation — Domain Plan → Configured, Bootable App Skeleton (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology, and part of the greenfield tooling it\n> sequences does not exist yet.** The foundation *sequence* below is a working first cut —\n> the capability-derivation heuristic, the module-registration convention, and\n> the provider-selection rubric are deliberately explicit so they can be tuned\n> against real runs. The deterministic steps that *materialize the skeleton* and\n> *install app-knowledge* are a later greenfield-enablement phase and are **not\n> built**. Those two steps are authored as explicit deferred-tooling notes;\n> headless setup and verified local initialization are registered commands. **This playbook is the\n> METHOD — the description of the foundation sequence — not a runnable\n> foundation.** If you find yourself building or wiring the greenfield CLI\n> tooling, stop: that is out of this playbook's scope.\n\n## Where you are in the journey\n\nThis is the **foundation** playbook — the point in the **bottom-up** phase where\nthe *plan* becomes a *bootable app*. It runs **after** the `bottom_up.domain-plan`\nplaybook produced (and the creator approved) the **domain plan**: the module\ndecomposition, the per-module resource inventory, and the inter-resource\nrelationship intents. Its preconditions — `phase_is bottom_up` and\n`artifact_exists domain-plan` and `artifact_exists vision-brief` — mean the journey\nhas entered the build-shaping phase and the two load-bearing artifacts are present:\nthe **domain plan** (whose modules you register) and the **vision brief** (whose\ncompliance and vision constraints drive which engine capabilities you enable). The\nroute-bound `transition_committed` fact that authorized and applied crossing from top-down into\nbottom-up was the domain-plan playbook's duty (it is the first bottom-up playbook);\nyou do not re-cross that boundary — the domain plan's existence already sits behind\nit.\n\nYou are not re-opening the domain plan here — you are turning an *approved* plan\ninto the *configured application skeleton the build loop then fills in*.\n\n## What this playbook does\n\nYou are the **foundation engineer**. This playbook reads the approved domain plan\nand the vision brief, then configures and brings up the application skeleton so the\nbuild loop has a real workspace to author into. You perform a **mixed sequence**\n(the runner sequences the tiers per this guidance):\na config/skeleton **authoring** pass, then a **deterministic bring-up** pass. The\nwork, in order:\n\n1. **Derive the engine capabilities** from the compliance/vision constraints (and\n the market/business-model facts) and enable them in `./wildo.saas.config.ts`.\n2. **Declare the domain-plan's modules** at the SaaS root (they are registered across\n the runtimes after Step 5 materializes the skeleton, so it boots with them).\n3. **Select the providers** the enabled capabilities need.\n4. **Record the compliance declarations you were given** — the operating entity and\n the jurisdictions, from the elicitation answers, into `./wildo.saas.config.ts`.\n See `config-saas` and its `references/compliance-declarations.md`.\n5. **Run the deterministic bring-up** — materialize the skeleton, install\n app-knowledge, `wildo setup --non-interactive`, then `wildo local init`.\n\nYou emit **no artifact**. The deliverable is the app itself: `./wildo.saas.config.ts`,\nthe materialized skeleton, and a verified local initialization. Record *why* each\ncapability, module and provider was chosen in the config's own comments, where the\nnext reader of that file will find it.\n\nThis is a **foundation pass**. You enable capabilities, declare modules as shells,\nselect providers, and bring the skeleton up. You do **not** author resource schemas,\nfields, ui-behavior, views, or navigation — that is the **build loop's** job,\ndownstream of this foundation.\n\n## Read state first — the artifacts you read, the files you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*. Before configuring\nanything:\n\n1. Read the current journey state and scope through the `journey-status` skill (it\n owns the read; do not re-derive it here). Confirm the domain plan is present and\n approved, and check whether a `./wildo.saas.config.ts` already exists from an\n earlier run (refine it, do not re-author — see below).\n2. Read the **domain plan** (`domain-plan` family — the modules to register + their\n resource inventory) and the **vision brief** (`vision-brief` — the compliance and\n vision constraints that are the **primary** driver of capability selection).\n **Contextual** reads that sharpen the choices (they are *not* preconditions — read\n them if present, and note that the `business-model` may be absent, per the top-down\n phase-gate's optional posture):\n - the **market-snapshot** (`market-snapshot`) — its ICPs sharpen capability\n selection (a B2B / organization-scoped ICP → the `organizations` capability);\n - the **business-model** (`business-model`) — a paid plan → the billing capability\n (absent business model = no billing capability derived from it);\n - the **relationship drafts** inside the domain plan (the inter-resource relationships the build loop will\n wire — they can hint at which capabilities a module needs);\n - the **requirements** (functional/non-functional needs a capability may satisfy);\n - the **roadmap** (which modules are MVP-critical, so you enable what the first\n release needs and defer the rest).\n\n// Operator affordances (the executor itself is handed the domain-plan VALUE directly):\n// `wildo context journey` — current phase, the eligibility board, runs in flight\n// `wildo context info specification-artifacts` — per-family landed state and rendered content\n\nYou **read** `domain-plan` + `vision-brief` + `market-snapshot` + `business-model`\n+ `requirements` + `roadmap` (the domain plan carries its relationship drafts); you **write**\n`./wildo.saas.config.ts` and the materialized skeleton — app files, committed to git,\nwhich is where the record of what was decided lives.\n\n## Step 1 — Derive and enable the engine capabilities\n\nEngine capabilities are the framework surfaces the app turns on (organizations,\nbilling, notifications, audit trails, data residency, and so on). **Derive them from\nthe definition set — do not guess:**\n\n1. **Compliance/vision constraints → capabilities (the primary driver).** Walk the\n vision brief's constraints. A compliance constraint implies a capability (a privacy-law /\n data-residency constraint → the residency/audit capability; an external-assurance constraint →\n audit trails). A vision fact implies a capability (an organization-scoped product →\n `organizations`).\n2. **Market / business-model facts → capabilities (contextual sharpener).** A B2B or\n organization-scoped ICP in the `market-snapshot` → the `organizations` capability; a\n paid plan in the `business-model` → billing. Treat these as sharpeners over the\n primary compliance/vision derivation — and remember the `business-model` may be\n absent (then derive no billing capability from it).\n3. **Domain-plan needs → capabilities.** A module whose capability clearly needs a\n framework surface (a module that sends transactional email → notifications) turns\n on that capability.\n4. **Enable only what the definition set justifies.** Every enabled capability must\n trace to a compliance/vision constraint, a market/business-model fact, or a\n domain-plan module need. Do **not** enable a capability nothing asks for — that is\n speculative surface area (a coherence CONCERN — see the quality gate). Conversely,\n a compliance constraint that requires a capability you did **not** enable is a\n coverage GAP.\n\nThe `config-saas` skill carries the vocabulary for the `engineCapabilities` block of\n`./wildo.saas.config.ts`; read it to enable capabilities idiomatically. Record each\nenabled capability **and its justification** as a comment beside it in the config.\n\n## Step 2 — Declare the domain-plan's modules (register across runtimes after materialization)\n\n**Mind the ordering.** At *config-authoring* time (this step, before the skeleton\nexists) you can only **declare** the modules at the SaaS root. The shared / frontend /\nbackend module registry files do not exist until Step 5 materializes the skeleton, so\nthe cross-runtime **registration** happens *after* materialization — do not edit\nregistry files the skeleton has not yet created.\n\n1. **Declare each module at the SaaS root (now).** Add each domain-plan module to the\n `modules` composition in `./wildo.saas.config.ts` (the `config-saas` skill owns this\n surface). This declares the module's *existence* and is exactly what the skeleton\n materialization (Step 5) builds the per-module workspaces and registries from.\n2. **Register across the runtimes (after Step 5 materializes the skeleton).** Once the\n skeleton exists, each declared module is registered across the shared / frontend /\n backend registries so every runtime loads it — regenerated by `config sync` from the\n declared modules where the tooling supports it, or wired with the `module-registration`\n skill (distinct from `config-saas`, which only declares existence at the root). At\n foundation depth you register the module **shells** (the module exists and boots); the\n resources *inside* each module are authored by the build loop.\n3. **Declare every domain-plan module — and no more.** A module the domain plan named\n that is missing from the config is a GAP; a module in the config the domain plan did\n not name is an unjustified-module CONCERN. Record the declared modules (each traced\n to its domain-plan module) as a comment beside it in the config.\n\n**Do not author the resources here.** The domain plan's per-module resource inventory\ntells you *what* resources each module will own, but authoring their schemas, fields,\nand config is the **build loop's** job. If you catch yourself writing a resource\nschema, stop: that is out of this playbook's depth.\n\n## Step 3 — Select the providers\n\nEnabled capabilities that reach an external service need a **provider** (billing → a\npayment provider; notifications/email → an email provider; file storage → an object\nstore). For each such capability, select and wire the provider scope +\n`providerConfigurations` in `./wildo.saas.config.ts` (the `config-saas` skill covers\nthe provider surfaces):\n\n- **Every provider matches a declared capability.** A provider wired for no enabled\n capability is a CONCERN; an enabled capability that needs a provider with none\n selected is a GAP.\n- **Do not seed secrets here.** Provider *selection* (which provider, which scope) is\n foundation; the per-environment secret material is seeded by the deterministic\n bring-up / environment step, not authored inline. Record the selected providers\n (each matched to its capability) as a comment beside it in the config.\n\n## Step 4 — Record the compliance declarations (only what you were told)\n\nThe creator answered `operating-entity` and `operating-jurisdictions`. Write those answers\ninto `operatorComplianceIdentity` and `operatingJurisdictions`, and **nothing else**.\n\n- **Record the PART you were given.** Every part of `operatorComplianceIdentity` is\n independently declarable, so a creator who named the company and not its lawful bases\n gets `legalEntityName` and `registeredAddress` written and the rest left absent. A\n missing part is reported downstream as outstanding; it does not block anything here.\n- **NEVER invent one.** Not a company name, not an address, not a privacy contact, and\n above all not a lawful basis — that is a legal determination, and `CONSENT` in\n particular would tell a person their data rests on an agreement they could withdraw.\n A produced privacy notice quotes these as fact. An absent declaration is reported as an\n open gap a reader can see; an invented one is published.\n- **Omit the key entirely when you were told nothing.** Absence means \"nobody answered\",\n which is the honest state and the one every consumer already renders correctly. An\n empty object is refused by the schema precisely because it would satisfy the field while\n disclosing nothing.\n- **A jurisdiction needs its `basis`.** \"eu\" alone does not say whether you are established\n there, sell there, or hold data about people there, and those imply different obligations.\n If the creator gave a place without a reason, record neither — ask, or leave it out.\n\nThis step CANNOT fail the run. If the creator answered nothing, write nothing and continue:\nthe application boots, and the gap is visible where it matters rather than here.\n\n(A `foundation-manifest` artifact was declared here until 2026-08-25 and is now\nretired with the app-creation verification/digest aspect. It was a bookkeeping record\nof decisions the config already carries — deleting it costs no fact about the app.)\n\n## Step 5 — The deterministic bring-up sequence (partially deferred)\n\nWith the config authored, run the **deterministic bring-up** in prerequisite order.\nThe skeleton template and app-knowledge installer remain deferred; do not invent\nthem. Headless `wildo setup` and `wildo local init` are registered and should be\nexecuted after the app structure exists.\n\n1. **Materialize the app skeleton** — create the `./frontend/`, `./shared-lib/`,\n `./backend-api/`, `./specifications/`, and `./infrastructure/` workspaces + the\n module registries from the empty-app template, so the declared modules have a real\n workspace.\n\n // (Deferred greenfield tooling: skeleton materialization is not yet a registered command —\n // do not invent one.)\n\n2. **Install app-knowledge** — drop the compiled skills / rules / agents into the\n project's agent-config folders so the build loop's coding agent reads them\n naturally with cwd at the app root.\n\n // (Deferred greenfield tooling: the app-knowledge installer is not yet a registered command —\n // do not invent one. `wildo fwk dev-skills` covers the framework-development flow only.)\n\n3. **Run setup** — configure the app from the authored `./wildo.saas.config.ts` and\n the `./infrastructure/` env configs (the `infra-environment-config` skill owns the\n typed infra env files; the `local-environment-bootstrap` skill owns the `wildo`\n lifecycle). Headless setup is registered and fail-closed on the administrator seed\n environment variables; it mints the environment generation without placeholders.\n\n ```bash\n wildo setup --non-interactive\n ```\n\n4. **Initialize and verify the project** — run the registered convergence journey.\n It regenerates artifacts, starts and readiness-gates backing services, reconciles\n platform Mongo state and credentials, starts native platform services, registers the\n app once, emits all runtime projections, and executes a signed managed-config read.\n\n ```bash\n wildo local init\n ```\n\nReport the status of each bring-up step to the creator in your result. Skeleton\nmaterialization and app-knowledge installation remain deferred; setup and local\ninitialization are executable once those app files exist and must be recorded from their\nreal exit/postcondition result rather than marked complete from intent.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not disable a capability, drop a module,\n or re-select a provider that is already correct. Only enable a newly-justified\n capability, register a newly-added domain-plan module, or correct a provider where\n the definition set genuinely changed.\n- **Reuse existing module ids and provider scopes.** A module already registered keeps\n its id; a provider already selected keeps its scope — never mint a second one for the\n same module/capability.\n- **Follow the definition set.** If the domain plan added a module or the vision brief\n added a compliance constraint since the last run, reflect it (register the module,\n enable the capability) — do not re-derive the whole configuration from scratch. The\n delta is visible in `git diff` on the config, which is the record.\n\n## Quality gate — `foundation-configured-coherently` (declarative at scaffold depth)\n\nThe foundation is checked against the `foundation-configured-coherently` **reviewer\nchecklist** (see the end of this method): five invariants (capability derivation, module registration, provider coverage,\nsequence order, and foundation-depth boundary discipline), each marked PASS / CONCERN /\nGAP.\n\nThis checklist is **declarative**: no runtime executes it (rubric-only judge gates were retired at the flexible-intelligence hard cut — judgment runs only through a compiled Evaluation Treatment, and this playbook has none yet), so it ships as the **creator's review checklist** — nothing runs it automatically. The **trust floor** for accepting the foundation today is the\ncreator's `approve_result` review of the produced config and the bring-up result. There is\nintentionally **no deterministic gate**: config validation is a `wildo` CLI concern\n(`config sync` / validate), not a validator in the journey-artifact schemaRef\nvocabulary. When the greenfield tooling lands, the non-bypassable floor still\nhard-gates the real destructive / off-machine infra bring-up regardless of this gate.\n\n## Scaffold-depth and tooling-deferral boundary\n\nKeep this playbook at scaffold depth **and** honour the tooling deferral. Explicitly\n**out of scope here**:\n\n- **The remaining greenfield CLI tooling itself.** The skeleton-materialization\n template and app-knowledge installer do **not** exist yet and are a later\n greenfield-enablement phase. Their two deferred-tooling notes must not be turned\n into invented commands. `wildo setup --non-interactive` and `wildo local init` do exist and are\n the registered lifecycle once the app structure is present.\n- **Resource / field / schema authoring.** The config declares modules as shells and\n enables capabilities; it does **not** author resource schemas, fields, enums,\n decorators, ui-behavior, views, or navigation. That is the build loop. If you catch\n yourself writing a resource, stop.\n- **Re-introducing a foundation artifact.** The `foundation-manifest` family was\n retired on 2026-08-25 with the app-creation verification/digest aspect. Do **NOT**\n reshape `_core` to bring it back: the config file and its git history already carry\n every decision it recorded.\n- **Deep capability / provider modelling.** A defended capability-selection model\n (per-compliance-regime obligation → capability mapping, provider cost/feature\n matrices, multi-provider fallback) is a later depth pass. You derive capabilities\n from the definition set with the v1 heuristic above — not a solved obligation graph.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at scaffold\ndepth — depth (and the greenfield tooling) are dedicated later passes done once,\nholistically.\n\n## What you emit\n\n- The authored **`./wildo.saas.config.ts`** (an app file) — the enabled engine\n capabilities, the registered modules, and the selected providers — plus the\n registered module shells across the runtimes and (when the tooling lands) the\n brought-up skeleton.\n- The **bring-up result** reported to the creator: the status of each step, taken from\n its real exit/postcondition rather than from intent. This is a report, not a stored\n artifact — nothing reads it back.\n\nThe creator reviews the result (approval posture `approve_result`) before it is\naccepted as the journey's foundation, which the bottom-up build loop then fills in\nwith authored resources, operations, UX, and integrations.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state and scope,\n and confirm the approved domain plan + vision brief are in place to configure from.\n- `.claude/skills/config-saas/SKILL.md` — the `./wildo.saas.config.ts` authoring\n surface: `engineCapabilities`, `modules`, provider scopes, and `providerConfigurations`.\n- `.claude/skills/module-registration/SKILL.md` — register each domain-plan module\n across the shared / frontend / backend registries so the skeleton boots with it\n (distinct from `config-saas`, which only declares module existence at the root).\n- `.claude/skills/infra-environment-config/SKILL.md` — the typed `./infrastructure/`\n environment configs (backing services, public domain, service auth) the bring-up needs.\n- `.claude/skills/local-environment-bootstrap/SKILL.md` — the `wildo` lifecycle\n (`setup`, `local init`, `local reinit`, `local dev`) for deterministic initialization,\n repair, clean-room recovery, and runtime start.\n\n## Reviewer checklist — `foundation-configured-coherently`\n\nFormerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is kept here, verbatim, minus the retired runner's closing sentence:\n\nJudge whether the authored foundation (the ./wildo.saas.config.ts composition + the materialized skeleton) is a coherent realisation of the approved domain plan and the top-down definition set. Assess five invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) CAPABILITY DERIVATION — every enabled engine capability traces to a compliance/vision, business-model, market, or domain-plan need; unjustified capabilities are a CONCERN and missing required capabilities are a GAP. (2) MODULE REGISTRATION — every approved domain-plan module is declared and registered across runtimes; missing modules are a GAP and extra modules are a CONCERN. (3) PROVIDER COVERAGE — every provider serves a declared capability and every provider-backed capability has a provider. (4) SEQUENCE ORDER AND PROOF — author config → materialize skeleton → install app-knowledge → wildo setup --non-interactive → wildo local init. Treat setup intent, container health, or an initialization marker as insufficient: local init must reach its signed managed-config-read postcondition. (5) BOUNDARY DISCIPLINE — stay at foundation depth and do not author resources, fields, ui-behavior, views, or navigation. Do not invent the still-deferred skeleton/app-knowledge installer commands; headless setup and local init are registered and should be executed once the structure exists. This reviewer checklist is declarative; creator approval is the trust floor.\n",
|
|
51
47
|
"skillRefs": [
|
|
52
48
|
"journey-status",
|
|
53
49
|
"config-saas",
|
|
@@ -65,11 +61,23 @@
|
|
|
65
61
|
"organizations",
|
|
66
62
|
"users"
|
|
67
63
|
]
|
|
64
|
+
},
|
|
65
|
+
{
|
|
66
|
+
"ref": "operating-entity",
|
|
67
|
+
"question": "Which legal entity operates this service? Give the registered company name, its registered address, and the route a person uses to reach you about privacy (an email, a URL or a postal address). 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.",
|
|
68
|
+
"kind": "free_text"
|
|
69
|
+
},
|
|
70
|
+
{
|
|
71
|
+
"ref": "operating-jurisdictions",
|
|
72
|
+
"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? Use country codes (`fr`, `us`), the supranational `eu`, or a subdivision (`us-ca`). Answer \"not decided\" if the market is genuinely unsettled; an absent answer is read as unanswered, never as \"nowhere\".",
|
|
73
|
+
"kind": "free_text"
|
|
68
74
|
}
|
|
69
75
|
]
|
|
70
76
|
},
|
|
71
77
|
"contextSources": [],
|
|
72
|
-
"suspendsForClarification": false
|
|
78
|
+
"suspendsForClarification": false,
|
|
79
|
+
"briefAdequacyGate": false,
|
|
80
|
+
"briefAdequacyExcludedSources": []
|
|
73
81
|
},
|
|
74
82
|
"approval": "approve_result",
|
|
75
83
|
"budget": {
|
|
@@ -7,10 +7,6 @@
|
|
|
7
7
|
"shape_user_experience"
|
|
8
8
|
],
|
|
9
9
|
"preconditions": [
|
|
10
|
-
{
|
|
11
|
-
"kind": "phase_is",
|
|
12
|
-
"phase": "bottom_up"
|
|
13
|
-
},
|
|
14
10
|
{
|
|
15
11
|
"kind": "artifact_exists",
|
|
16
12
|
"selector": {
|
|
@@ -46,6 +42,8 @@
|
|
|
46
42
|
"workspace_truth"
|
|
47
43
|
],
|
|
48
44
|
"suspendsForClarification": false,
|
|
45
|
+
"briefAdequacyGate": false,
|
|
46
|
+
"briefAdequacyExcludedSources": [],
|
|
49
47
|
"deliberation": {
|
|
50
48
|
"workDomain": "information_architecture",
|
|
51
49
|
"reviewerRoleRefs": [
|