@wildo-ai/framework-knowledge 1.1.8 → 1.1.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +9 -2
- package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +21 -0
- package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +121 -0
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +29 -5
- package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +29 -2
- package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +69 -24
- package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +10 -0
- package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +21 -5
- package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +31 -5
- package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +2 -0
- package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +11 -1
- 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 +11 -1
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +2 -2
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +11 -11
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +29 -22
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +3 -3
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +59 -10
- 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 +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +3 -3
- 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 +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +2 -1
- 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 +5 -5
- 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 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +12 -4
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +25 -27
- 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 +85 -43
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +40 -0
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +41 -0
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +199 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +201 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +67 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +76 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +3 -1
- 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 +27 -18
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +11 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +11 -11
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +2 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +3 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +2 -0
- 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 +3 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +5 -2
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -4
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +7 -3
- 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 +36 -2
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +7 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +4 -2
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +9 -3
- 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 +3 -3
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +35 -2
- 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 +30 -17
- 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 -1
- package/dist/knowledge/manifest.json +8 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +22 -7
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
- package/dist/knowledge/playbooks/bottom_up.build/method.md +17 -15
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +4 -3
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +117 -28
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +4 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +133 -59
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +169 -276
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -2
- package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +8 -1
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.conception/method.md +3 -2
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +2 -2
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +22 -6
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +4 -3
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +13 -5
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +5 -2
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +71 -37
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +35 -38
- package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +105 -0
- package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +55 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +78 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +63 -0
- package/dist/knowledge/playbooks/top_down.brand-naming/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +65 -0
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/method.md +60 -6
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +15 -10
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +30 -10
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +3 -1
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +4 -1
- package/dist/knowledge/playbooks/top_down.definition/method.md +8 -3
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +6 -4
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +11 -1
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +21 -0
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +8 -2
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +4 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +10 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +40 -17
- package/dist/knowledge/references/brand.name-choice.config.md +127 -0
- package/dist/knowledge/references/brand.name-screening.config.md +253 -0
- package/dist/knowledge/references/build-plan.task-graph.config.md +64 -11
- package/dist/knowledge/references/business-model.pricing-plan.config.md +16 -0
- package/dist/knowledge/references/business-model.snapshot.config.md +64 -0
- package/dist/knowledge/references/business-model.snapshot.validation.md +68 -4
- package/dist/knowledge/references/capability-composition.config.md +67 -4
- package/dist/knowledge/references/example.data-seeding.minimal.md +29 -1
- package/dist/knowledge/references/market.snapshot.validation.md +1 -1
- package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +7 -1
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +6 -0
- package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +81 -2
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +10 -0
- package/dist/knowledge/references/saas.website.astro.label-loader.md +9 -0
- package/dist/knowledge/references/saas.website.factories.define-section.md +4 -0
- package/dist/knowledge/references/saas.website.page-manifest.schema.md +12 -3
- package/dist/knowledge/references/saas.website.page-sections.component.md +72 -0
- package/dist/knowledge/references/saas.website.sections.definition-schema.md +11 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +38 -1
- package/dist/knowledge/registries/playbooks.json +68 -20
- package/dist/knowledge/registries/source-tags.json +748 -695
- package/dist/knowledge/rules/live-context-door.md +5 -2
- package/dist/knowledge/skills/INDEX.md +2 -1
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +1 -1
- package/dist/knowledge/skills/brand-name-screening/SKILL.md +154 -0
- package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +394 -0
- package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +65 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +5 -2
- package/dist/knowledge/skills/config-saas/SKILL.md +31 -4
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +14 -1
- package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +81 -2
- package/dist/knowledge/skills/email-add-template/SKILL.md +1 -1
- package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +1 -1
- package/dist/knowledge/skills/inbound-channels/SKILL.md +2 -2
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +11 -1
- package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +122 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +11 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +9 -2
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +11 -1
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +11 -1
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +1 -1
- package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +1 -1
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +10 -0
- package/dist/knowledge/skills/module-relationships/SKILL.md +6 -4
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +51 -3
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +6 -0
- package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +7 -1
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +10 -0
- package/dist/knowledge/skills/website-factory-advanced/SKILL.md +4 -0
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +84 -3
- package/dist/knowledge/skills/website-section-contact/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-cta/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-faq/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-hero/SKILL.md +27 -9
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +1 -1
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +11 -0
- package/dist/knowledge/topic-index.json +169 -43
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
|
@@ -27,9 +27,10 @@ domain-plan`). You are not re-opening domain questions here — you are turning
|
|
|
27
27
|
*approved* domain plan into the *ordered work that builds it*.
|
|
28
28
|
|
|
29
29
|
Downstream of this playbook, two further playbooks consume your output: the
|
|
30
|
-
**dispatch-orchestration** playbook
|
|
31
|
-
|
|
32
|
-
|
|
30
|
+
**dispatch-orchestration** playbook dispatches the tasks through the coding-agent
|
|
31
|
+
contract in parallel waves (up to the application's build parallelism at once), and the
|
|
32
|
+
**scale** playbook describes how those waves are scheduled, interleaved with the
|
|
33
|
+
companion generation steps, and reconciled. **You author neither of those concerns** — see the
|
|
33
34
|
boundary section below.
|
|
34
35
|
|
|
35
36
|
## What this playbook does
|
|
@@ -146,6 +147,7 @@ product, and `TASK_DECLARES_NO_PRODUCT` is the honest answer rather than a place
|
|
|
146
147
|
| `WEBSITE_SECTION` | `pageRef` + `sectionRef` | one section of one page, declared in `<pageRef>.sections.tsx` |
|
|
147
148
|
| `DOCUMENTATION_CHAPTER` | `chapterRef` | the chapter's authored body, keyed by its `chapterRef` in `specifications/src/technical-documentation/index.ts`, which `wildo docs publish` joins to the documentation plan and publishes under `/guides/<slug>` |
|
|
148
149
|
| `APPLICATION_BILLING_PRODUCT` | `productKey` | one product of the application's billing catalogue, named by its catalogue `key` (a slug, e.g. `team`) — declared in `shared-lib/src/engine/product.ts` under the `BILLING_CATALOG` target. The KEY, never the file: `wildo init` writes the file with an empty catalogue |
|
|
150
|
+
| `APPLICATION_DATA_SEED` | `seedKey` + `resourceRef` + `content` (`REFERENCE` or `DEMONSTRATION`) | one data seed a module declares, named by its key (`<moduleRef>:<purpose>`, e.g. `crm:demo-customers`) — the file `backend-api/src/modules/<moduleRef>/seeds/<seedKey with : as .>.seed.ts`, registered by the module. A `DEMONSTRATION` seed lands only once it declares the environments it runs in, without production |
|
|
149
151
|
| `INBOUND_CHANNEL_HANDLER` | `channel` + the handler's `handlerRef` (`<moduleRef>.<purpose>`, e.g. `matters.mail-intake`) | the handler that decides what a message arriving on a channel the integration plan declared causes. Its file is `backend-api/src/modules/<moduleRef>/inbound/<handlerRef>.inbound-channel-handler.ts`, and it lands when the module's backend `index.ts` imports that file — which is how it is registered on `inboundHandlers` |
|
|
150
152
|
|
|
151
153
|
**A GOVERNED DOCUMENT is chosen from a closed list, never invented.** There are six,
|
|
@@ -565,6 +567,16 @@ export enum BuildPlanTaskProductKind {
|
|
|
565
567
|
* money and the pricing-surface facts (recommended, price disclosure, availability) the plan implies.
|
|
566
568
|
*/
|
|
567
569
|
APPLICATION_BILLING_PRODUCT = 'APPLICATION_BILLING_PRODUCT',
|
|
570
|
+
/**
|
|
571
|
+
* One data seed a module declares — rows the application creates for itself, named by the seed's
|
|
572
|
+
* `seedKey` (`crm:demo-customers`).
|
|
573
|
+
*
|
|
574
|
+
* The seed is its own file, `backend-api/src/modules/<module>/seeds/<seedKey with ':' as '.'>.seed.ts`,
|
|
575
|
+
* and it lands only once the module registers it — a seed file nothing imports never runs. Its
|
|
576
|
+
* {@link BuildPlanDataSeedContent} says whether it is REFERENCE data the application needs everywhere
|
|
577
|
+
* or DEMONSTRATION data that must never reach production.
|
|
578
|
+
*/
|
|
579
|
+
APPLICATION_DATA_SEED = 'APPLICATION_DATA_SEED',
|
|
568
580
|
/** One website page, registered in the website root config by its manifest. */
|
|
569
581
|
WEBSITE_PAGE = 'WEBSITE_PAGE',
|
|
570
582
|
/** One section of one website page, declared in that page's sections file. */
|
|
@@ -583,6 +595,27 @@ export enum BuildPlanTaskProductKind {
|
|
|
583
595
|
INBOUND_CHANNEL_HANDLER = 'INBOUND_CHANNEL_HANDLER',
|
|
584
596
|
}
|
|
585
597
|
|
|
598
|
+
|
|
599
|
+
/**
|
|
600
|
+
* What a data seed's rows ARE, which decides where they may exist.
|
|
601
|
+
*
|
|
602
|
+
* - `REFERENCE` — rows the application needs to work wherever it runs: a closed list, a default
|
|
603
|
+
* record, a system template. Every environment, production included.
|
|
604
|
+
* - `DEMONSTRATION` — sample rows that make a freshly created application look lived-in (customers,
|
|
605
|
+
* projects, a few records per list). They must never sit beside real rows, so the seed declares
|
|
606
|
+
* `allowedApplicationEnvironments` without `production`, and the task lands only once it does.
|
|
607
|
+
*/
|
|
608
|
+
export enum BuildPlanDataSeedContent {
|
|
609
|
+
REFERENCE = 'REFERENCE',
|
|
610
|
+
DEMONSTRATION = 'DEMONSTRATION',
|
|
611
|
+
}
|
|
612
|
+
|
|
613
|
+
/**
|
|
614
|
+
* A data seed's key: kebab-case segments joined by `:` (`crm:demo-customers`), the convention a
|
|
615
|
+
* `DataSeedDefinition` documents. Constrained here because the seed's FILE is derived from it.
|
|
616
|
+
*/
|
|
617
|
+
export const DATA_SEED_KEY_PATTERN: RegExp = /^[a-z0-9]+(?:-[a-z0-9]+)*(?::[a-z0-9]+(?:-[a-z0-9]+)*)*$/;
|
|
618
|
+
|
|
586
619
|
/**
|
|
587
620
|
* One artifact a task is accountable for. Closed by construction: a product the
|
|
588
621
|
* host cannot ask a question about is a product that can never be shown to have
|
|
@@ -652,6 +685,13 @@ export const BuildPlanTaskProductSchema = z.discriminatedUnion('kind', [
|
|
|
652
685
|
scope: z.enum(ProviderBindingScope).systemEnum('ProviderBindingScope'),
|
|
653
686
|
}),
|
|
654
687
|
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_BILLING_PRODUCT).systemEnum('BuildPlanTaskProductKind'), productKey: SlugSchema }),
|
|
688
|
+
z.strictObject({
|
|
689
|
+
kind: z.literal(BuildPlanTaskProductKind.APPLICATION_DATA_SEED).systemEnum('BuildPlanTaskProductKind'),
|
|
690
|
+
seedKey: z.string().regex(DATA_SEED_KEY_PATTERN),
|
|
691
|
+
/** The resource whose rows the seed writes — the `resourceType` it declares. */
|
|
692
|
+
resourceRef: SlugSchema,
|
|
693
|
+
content: z.enum(BuildPlanDataSeedContent).systemEnum('BuildPlanDataSeedContent'),
|
|
694
|
+
}),
|
|
655
695
|
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_PAGE).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema }),
|
|
656
696
|
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_SECTION).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema, sectionRef: SlugSchema }),
|
|
657
697
|
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.DOCUMENTATION_CHAPTER).systemEnum('BuildPlanTaskProductKind'), chapterRef: SlugSchema }),
|
|
@@ -734,6 +774,9 @@ export function buildPlanTaskProductIdentities(product: BuildPlanTaskProduct): r
|
|
|
734
774
|
return [`${product.kind}:${product.scope}:${product.providerRef}`];
|
|
735
775
|
case BuildPlanTaskProductKind.APPLICATION_BILLING_PRODUCT:
|
|
736
776
|
return [`${product.kind}:${product.productKey}`];
|
|
777
|
+
// The key alone: two seeds may write one resource, and the key is what the seed run ledger tracks.
|
|
778
|
+
case BuildPlanTaskProductKind.APPLICATION_DATA_SEED:
|
|
779
|
+
return [`${product.kind}:${product.seedKey}`];
|
|
737
780
|
case BuildPlanTaskProductKind.WEBSITE_PAGE:
|
|
738
781
|
return [`${product.kind}:${product.pageRef}`];
|
|
739
782
|
case BuildPlanTaskProductKind.WEBSITE_SECTION:
|
|
@@ -757,6 +800,13 @@ export function buildPlanTaskProductIdentities(product: BuildPlanTaskProduct): r
|
|
|
757
800
|
*/
|
|
758
801
|
export const BILLING_CATALOG_SKILL_REF = 'configure-billing';
|
|
759
802
|
|
|
803
|
+
/**
|
|
804
|
+
* The skill every data-seed task is authored with (#2234): levels, modes, business keys, and the
|
|
805
|
+
* environment restriction that keeps demonstration rows out of production. The dispatch derives it from
|
|
806
|
+
* an `APPLICATION_DATA_SEED` product whatever the decomposer wrote.
|
|
807
|
+
*/
|
|
808
|
+
export const DATA_SEED_SKILL_REF = 'seeding-authoring';
|
|
809
|
+
|
|
760
810
|
export const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [
|
|
761
811
|
z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE), moduleRef: ModuleRefSchema }),
|
|
762
812
|
z.strictObject({
|
|
@@ -884,15 +934,18 @@ export const BuildPlanTaskSchema = z.strictObject({
|
|
|
884
934
|
/**
|
|
885
935
|
* What this task is accountable to — traceability only, NEVER scope authority.
|
|
886
936
|
*
|
|
887
|
-
* The vocabulary is the
|
|
888
|
-
* and non-functional requirements, roadmap phases,
|
|
889
|
-
* constraints
|
|
890
|
-
*
|
|
891
|
-
*
|
|
937
|
+
* The vocabulary is the target aspects `BUILD_PLAN_FAMILY_ASPECTS` declares for this edge:
|
|
938
|
+
* functional and non-functional requirements, roadmap phases, the vision's success criteria and
|
|
939
|
+
* constraints, drafted features, pricing plans, and the brand's name, logo direction and visual
|
|
940
|
+
* tone. Each target after the first three was added because a producer had already been writing
|
|
941
|
+
* it (#629, #1433, #1835, #2221). A companion generation step serves what it consumes: the `logo`
|
|
942
|
+
* step serves the brand's logo direction and name.
|
|
892
943
|
*
|
|
893
|
-
*
|
|
894
|
-
*
|
|
895
|
-
*
|
|
944
|
+
* This schema accepts any non-empty string. Generation does not: the edge is DECLARED, so a key
|
|
945
|
+
* that resolves to no element of a target family (when that family has landed) is a dangling
|
|
946
|
+
* reference. The model is told so on retry, and the landing refuses it. That is why widening the
|
|
947
|
+
* vocabulary to what producers genuinely mean matters: a true link the vocabulary does not name
|
|
948
|
+
* fails generation. The workbench renders a key outside the vocabulary as visibly unresolved.
|
|
896
949
|
*/
|
|
897
950
|
servesRefs: z.array(NonEmptyStringSchema).default([]),
|
|
898
951
|
/**
|
|
@@ -916,9 +969,11 @@ export type BuildPlanTask = z.infer<typeof BuildPlanTaskSchema>;
|
|
|
916
969
|
* journey artifact selected by `MetaWorkflow_ArtifactSelector.family ===
|
|
917
970
|
* 'build-plan'` (the `family` vocabulary stays an open string owned by the
|
|
918
971
|
* selector surface; this note is the single place tying the SHAPE to the
|
|
919
|
-
* NAME). Produced by the build-decompose playbook, consumed
|
|
920
|
-
*
|
|
921
|
-
*
|
|
972
|
+
* NAME). Produced by the build-decompose playbook, consumed by
|
|
973
|
+
* build-dispatch (and build-scale, which runs the same branch): ready tasks
|
|
974
|
+
* are dispatched in parallel waves of up to the application's build
|
|
975
|
+
* parallelism (`wildo workbench parallelism`, 5 by default; 1 = one at a
|
|
976
|
+
* time).
|
|
922
977
|
*
|
|
923
978
|
* Invariants enforced here: unique task refs; every prerequisite names a task
|
|
924
979
|
* in this graph; no self-prerequisite. Cycle detection and ordering
|
|
@@ -1185,7 +1240,11 @@ Rules:
|
|
|
1185
1240
|
judge's `conception-buildable` verdict sends the application back to it. A plan that
|
|
1186
1241
|
invents the resource to wire it hides the fault the conception needs to see.
|
|
1187
1242
|
- **Carry the intent, not the resolution.** The task states the two ends, the
|
|
1188
|
-
cardinality intent, and the ownership direction from the relationship-draft.
|
|
1243
|
+
cardinality intent, and the ownership direction from the relationship-draft. Write
|
|
1244
|
+
the cardinality WITH its direction — "many-to-one from `customer` to
|
|
1245
|
+
`country-context`, customer holds the reference" — because the draft's label is
|
|
1246
|
+
read source → target and a bare "one-to-many" cannot be wired without knowing
|
|
1247
|
+
which end it was read from. The
|
|
1189
1248
|
cardinality-to-FK-holder resolution (discriminator / conditional relationships, the
|
|
1190
1249
|
physical FK placement) is the `module-relationships` skill's job **at dispatch
|
|
1191
1250
|
time**, not decided here.
|
|
@@ -1250,7 +1309,9 @@ replaced — the judge reports it as a gap.
|
|
|
1250
1309
|
task declares. Declare the skill the product's kind names anyway (the view skill for a view,
|
|
1251
1310
|
`config-<surface>` for a configuration), so the plan reads right; add a second only when the
|
|
1252
1311
|
task genuinely needs one no map would give it. With no experience plan,
|
|
1253
|
-
emit nothing here — an improvised surface is the state this family replaced.
|
|
1312
|
+
emit nothing here — an improvised surface is the state this family replaced. That
|
|
1313
|
+
absence is not silent: the reviewer's experience-coverage invariant records it, naming
|
|
1314
|
+
what the application will lack, so a build that goes ahead without the plan says so.
|
|
1254
1315
|
(A placement DECIDED by the placement plan is Step 1b's `SHELL_PLACEMENT`, not this.)
|
|
1255
1316
|
- **`extend_application`** — the controlled extension points where the declarative model
|
|
1256
1317
|
is not enough:
|
|
@@ -1305,6 +1366,23 @@ replaced — the judge reports it as a gap.
|
|
|
1305
1366
|
tasks whose features the plans grant. The website's PRICING section task depends on it: the
|
|
1306
1367
|
section reads this catalogue, so it must exist first. No business model, or one with no plans,
|
|
1307
1368
|
emits nothing.
|
|
1369
|
+
- **Data seeds** — target `MODULE_BACKEND` on the seed's module, product `APPLICATION_DATA_SEED`,
|
|
1370
|
+
skill `seeding-authoring` (the dispatch adds it whatever you write). A built application must not
|
|
1371
|
+
open EMPTY: an empty list is not something a creator can judge, try or show. Emit two kinds, and
|
|
1372
|
+
never mix them in one seed:
|
|
1373
|
+
- **`REFERENCE`** — rows the application needs wherever it runs, in production too: a closed list
|
|
1374
|
+
the domain plan stores as rows rather than as an enum, a default record each organization
|
|
1375
|
+
starts with. Emit one only where the domain plan implies such rows; most applications need few
|
|
1376
|
+
or none.
|
|
1377
|
+
- **`DEMONSTRATION`** — sample rows that make a freshly created application look lived-in: a few
|
|
1378
|
+
plausible records (three to eight) for each main resource a person meets first, in the market's
|
|
1379
|
+
own language and examples, consistent with each other (an enquiry names a customer that exists).
|
|
1380
|
+
One seed per resource. The seed declares `allowedApplicationEnvironments` without production,
|
|
1381
|
+
and the task lands only once it does, so these rows can never sit beside real ones.
|
|
1382
|
+
Order a seed after its resource's schema and config tasks, after the relationship tasks for the
|
|
1383
|
+
links its rows carry, and after any seed whose rows it references. Name each `seedKey`
|
|
1384
|
+
`<moduleRef>:<purpose>` (`crm:demo-customers`): the namespace keeps one module's seeds apart from
|
|
1385
|
+
another's. Never a seed for a resource the engine owns (users, organizations, memberships).
|
|
1308
1386
|
- **The website** — target `WEBSITE`, and you do NOT decide its content here. The
|
|
1309
1387
|
**website plan** (`bottom_up.website-plan`) already decided it: which pages, what each
|
|
1310
1388
|
is for, and the sections that carry each page's argument in reading order. Read it and
|
|
@@ -1371,9 +1449,13 @@ work. Emit these as tasks too — `target.kind: COMPANION_GENERATION_STEP` with
|
|
|
1371
1449
|
closed vocabulary; any other slug refuses at dispatch) — and **order them after the
|
|
1372
1450
|
surfaces whose output they consume**:
|
|
1373
1451
|
|
|
1374
|
-
- **`i18n-labels`** — label generation
|
|
1452
|
+
- **`i18n-labels`** — label generation in the application's PRIMARY locale. Order it
|
|
1375
1453
|
after the resources / ui-behavior / views / milestones / guidance whose labels it
|
|
1376
1454
|
generates — a milestone's title and a flow's words are generated from their declarations.
|
|
1455
|
+
Translation into the other enabled locales is a separate step, `i18n-translations`, which
|
|
1456
|
+
the dispatch host derives after this one for an application that enables more than one
|
|
1457
|
+
locale. Do not author it, and never make another task wait for translation: a step that
|
|
1458
|
+
needs labels (documentation publication, for one) needs only the primary locale.
|
|
1377
1459
|
- **`email-templates`** — email template + label generation and label translation.
|
|
1378
1460
|
Order it after the notification/email surfaces it renders.
|
|
1379
1461
|
- **`logo`** — the brand mark: an expert panel derives creative directions, marks are
|
|
@@ -1383,7 +1465,9 @@ surfaces whose output they consume**:
|
|
|
1383
1465
|
it after that brief exists; it depends on no
|
|
1384
1466
|
code surface, so it may run early and in parallel with resource work. Author it at
|
|
1385
1467
|
most once — an application has one accepted mark, and the step skips itself without
|
|
1386
|
-
calling a model when one is already accepted.
|
|
1468
|
+
calling a model when one is already accepted. Its `servesRefs` name the brand
|
|
1469
|
+
elements it realises — the brief's logo direction and the brand name, by the refs the
|
|
1470
|
+
brand brief shows (`brand.logo-direction`, `brand.name`). Name only refs the brief holds.
|
|
1387
1471
|
|
|
1388
1472
|
- **`database-migrations`** — `wildo db generate`: turns the drift the schema stages created into a
|
|
1389
1473
|
committed migration, and advances the accepted plan with it. **PostgreSQL-backed applications
|
|
@@ -1400,9 +1484,9 @@ surfaces whose output they consume**:
|
|
|
1400
1484
|
migration. It needs a BUILT `backend-api`, because the plan is computed by importing the compiled
|
|
1401
1485
|
registry; it refuses on an unbuilt tree instead of authoring a migration for a model nobody has.
|
|
1402
1486
|
|
|
1403
|
-
|
|
1404
|
-
|
|
1405
|
-
|
|
1487
|
+
There is no seeds GENERATION step: do **not** author one — an unknown `generationStepRef`
|
|
1488
|
+
refuses at dispatch instead of parking the build. Seeding is a CODING task: an
|
|
1489
|
+
`APPLICATION_DATA_SEED` product under the module's backend (Step 3, "Data seeds").
|
|
1406
1490
|
|
|
1407
1491
|
You **place** these steps in the order; you do **not** design how they run
|
|
1408
1492
|
concurrently with coding-agent tasks (that interleaving-at-scale concern is the scale
|
|
@@ -1410,10 +1494,15 @@ playbook's job — see the boundary below).
|
|
|
1410
1494
|
|
|
1411
1495
|
## Refine, don't re-author
|
|
1412
1496
|
|
|
1413
|
-
- **
|
|
1414
|
-
|
|
1415
|
-
|
|
1416
|
-
changed
|
|
1497
|
+
- **Your answer is the WHOLE plan, never a delta.** What you return replaces the
|
|
1498
|
+
plan on record, so a task you leave out is deleted. On a re-run, copy every task
|
|
1499
|
+
that still holds into your answer unchanged, under its existing ref, and change
|
|
1500
|
+
only what the domain plan or a prerequisite genuinely changed: add a task, re-order
|
|
1501
|
+
one, or add or correct a relationship-wiring task. Every resource and relationship
|
|
1502
|
+
the domain plan declares must still have its tasks when you are done — a plan that
|
|
1503
|
+
leaves one out is refused.
|
|
1504
|
+
- **Keep what still holds.** Do not re-decompose modules or resources whose tasks are
|
|
1505
|
+
already correct; carry them over as they are.
|
|
1417
1506
|
- **Reuse existing task refs.** A task that already exists keeps its ref — never mint a
|
|
1418
1507
|
second ref for the same unit of work.
|
|
1419
1508
|
- **Never orphan an ordering reference.** A task's prerequisite reference must name a
|
|
@@ -1443,7 +1532,7 @@ Keep this playbook at decomposition depth. Explicitly **out of scope here**:
|
|
|
1443
1532
|
- **Dispatch execution.** You do NOT dispatch any task, spawn any coding agent, build a
|
|
1444
1533
|
context pack, or run the coding-agent contract. That is the **dispatch-orchestration**
|
|
1445
1534
|
playbook, downstream of this decomposition.
|
|
1446
|
-
- **Workspace-mutation safety.**
|
|
1535
|
+
- **Workspace-mutation safety.** Dispatch locking and concurrency, clean-worktree preconditions,
|
|
1447
1536
|
change-set capture (git baseline / diff), and the failure-policy revert/flag mechanics
|
|
1448
1537
|
are the dispatch playbook's concern — NOT modelled here. A task that describes *how* it
|
|
1449
1538
|
is captured or locked is out of this playbook's depth.
|
|
@@ -1516,6 +1605,6 @@ what reaches you is this method, your declared inputs, and the brief's own secti
|
|
|
1516
1605
|
|
|
1517
1606
|
## Reviewer checklist — `build-plan-coherent`
|
|
1518
1607
|
|
|
1519
|
-
These
|
|
1608
|
+
These ten invariants are the criteria of this playbook's compiled evaluation treatment (`application-creation:evaluation-treatment/build-plan-coherent`, one criterion per invariant, invariants 2 and 2b sharing one), which the advisory judge runs after every landing. They are kept here as creator-facing review guidance too, so a reviewer and the judge read the same words:
|
|
1520
1609
|
|
|
1521
|
-
Judge whether the drafted build plan is a coherent, complete, correctly-ordered decomposition of the approved domain plan into coding-agent tasks — WITHOUT straying into how those tasks execute. Assess
|
|
1610
|
+
Judge whether the drafted build plan is a coherent, complete, correctly-ordered decomposition of the approved domain plan into coding-agent tasks — WITHOUT straying into how those tasks execute. Assess ten invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) MODULE + RESOURCE COVERAGE — every resource in every module's inventory (mainResources + supportingResources) has build tasks; a resource with no task is a GAP (the build would not produce it). Task `moduleRef` values must be module ids the workspace section lists (an invented module id is a GAP — the dispatcher cannot route it), and a task whose objective CREATES a resource the workspace section shows already exists — instead of enriching it — is a CONCERN (it dispatches a no-op). Module slices are scaffolded by the foundation step (a sibling playbook), so a module needs a dedicated ensure-module task ONLY where foundation did not establish it — a module whose resources have tasks but which carries no redundant scaffold task is NOT a GAP (do not flag the absence of a module-scaffold task foundation already owns); a module added to the plan after foundation with neither a foundation slice nor an ensure-module task IS a GAP. Every pricing plan the business model declares must be an `APPLICATION_BILLING_PRODUCT` of a `BILLING_CATALOG` task whose `servesRefs` name it; a declared plan with no billing product is a GAP. A plan with main resources and no `DEMONSTRATION` `APPLICATION_DATA_SEED` task is a CONCERN: the application would open empty. (2) TASK WELL-FORMEDNESS — every task names exactly ONE functional topic that is a real MetaWorkflow_FunctionalTopic value (configure_application_foundation / model_domain_graph / define_interaction_semantics / shape_user_experience / extend_application / connect_runtime_and_external_capabilities / assemble_verify_and_iterate) and at least one skill that is a real folder in the app-knowledge skill catalog; a task with an invented topic or a dangling skill is a GAP. (2b) PRODUCT DECLARATION — every task except a COMPANION_GENERATION_STEP declares at least one product in `produces`, and a generation step declares none; a coding task with an empty `produces` is a GAP, because it has no declared output to probe. The host can advance after a COMPLETED durable run, but carries the task in `unverifiableLandedTaskRefs`; that means ran, not proven. Repair the product declaration rather than treating this fallback as evidence of correct output. A product must name something COMPOSITION DOES NOT ALREADY WRITE — the fields a schema gains rather than its file, the verbs a config gains rather than its file, both endpoints of a relationship rather than one — so a product naming only a scaffolded artifact is a GAP wearing a declaration. Two tasks claiming the SAME artifact is a GAP as well (landing becomes undecidable); two tasks enriching one resource with DIFFERENT fields is correct and not a finding. A cross-resource FOREIGN KEY declared on a schema task's `produces` is a GAP — the relationship task is its single home (Step 2), and declaring it twice attributes one artifact to two tasks; a schema task's products are the resource's OWN domain fields. (3) PER-RESOURCE STAGE ORDER — for each resource, its tasks respect the inner order schema -> config -> ui-behavior -> spec; a config task ordered before that resource's schema task, or a spec task before its ui-behavior task, is a GAP (the build stage would run against a missing prerequisite). A supportingResource (e.g. a pure junction / lookup entity) may legitimately OMIT stages it does not need — a junction with schema + config and no ui-behavior is fine; only an out-of-ORDER stage (or a mainResource missing schema/config) is a GAP, not an intentionally-omitted stage on a supporting resource. (4) TOPIC DEPENDENCY ORDER — tasks respect the topic dependency edges (model_domain_graph before define_interaction_semantics; app-level shape_user_experience [views / navigation composing multiple resources or operations] after the interaction semantics and resources it composes; extend_application after the UX it extends; connect_runtime_and_external_capabilities after the resources it connects). Note the deliberate exception: a resource's OWN ui-behavior (its field displays / forms, a shape_user_experience task) depends only on that resource's own schema + config and MAY precede cross-resource operations — that is NOT a violation. What IS a GAP: an app-level view composing resources/operations placed before they exist, an integration task before the resources it connects, or any user-experience task before that resource's schema task. The per-resource spec task is a documentation capstone (topic model_domain_graph) and must be ordered after the schema / config / ui-behavior stages it documents; a spec task before its ui-behavior stage is a GAP. (5) RELATIONSHIP COVERAGE — every relationship-draft whose two endpoints are resources the domain plan declares has a wiring task (bound to the module-relationships skill) ordered AFTER both endpoint resources' schema tasks; a relationship with no wiring task, or one ordered before its endpoints exist, is a GAP. A relationship to a resource no module declares is NOT this invariant: no task can wire it, so it is invariant (8)'s. (6) COMPANION-GENERATION INTERLEAVE — the executable companion-owned generation steps (`i18n-labels`, `email-templates`, `logo`, plus `database-migrations` for a PostgreSQL-backed application) are present and placed AFTER the resources / modules whose output they consume; a labels-generation task ordered before the resources it labels, or a missing executable generation step for authored surfaces, is a CONCERN. `logo` is the exception to the ordering half — it consumes the brand brief rather than any code surface, so it is unordered with respect to resource work and only its ABSENCE (on an application with a brand brief) is a CONCERN. The migration step follows the schema stages whose drift it migrates and is not authored for MongoDB. Do NOT flag the absence of an `i18n-translations` step — the dispatch host derives it after `i18n-labels`. Do NOT flag the absence of a seeds GENERATION step — none exists; seeding is an `APPLICATION_DATA_SEED` coding task, judged under invariant (1). (7) BOUNDARY DISCIPLINE — the plan stays at DECOMPOSITION depth: it names tasks, their topic, their skill(s), their target, and their ordering intent; it does NOT specify how a task is DISPATCHED (dispatch locking and concurrency, change-set capture, git baseline, verify/quality-gate mechanics = the dispatch-orchestration playbook) and does NOT solve multi-agent SCALE or interleaving concurrency (= the scale playbook). Any task that describes how a task EXECUTES rather than WHAT it builds, or that authors a schema / resolves a cardinality into a concrete FK / generates code, is a CONCERN (scope creep out of the decomposition phase). (8) CONCEPTION BUILDABLE — this one faults the CONCEPTION, never the plan: a GAP when the domain plan declares a module, resource or relationship no build target can express however it is decomposed, or when the computed coherence report shows a dangling reference or unrealised decision in the conception (a domain-plan resource another family names that does not exist, a composition surface no plan realises) that the build would have to invent to proceed. An element the plan merely FORGOT is invariant (1), not this one — only a conception GAP sends the application back to its conception lane, which is the most expensive way to fix an omission. Name the conception element. (9) EXPERIENCE COVERAGE — every view, configuration, milestone and piece of guidance the experience plan declares has its task (a view task carrying the plan's viewRef verbatim, an onboarding document's objective naming its hostViewRef); an entry with no task is a GAP, and an objective that drops what the plan decided for its entry (reused components, the moment, the gate) is a CONCERN. With NO experience plan the plan rightly carries none of these tasks: mark PASS and begin the note with 'NO EXPERIENCE PLAN:' naming what the application will lack — never a CONCERN or GAP, because the decomposer cannot produce an upstream family by revising. (The deterministic gates and the creator's approval remain the floors; the judge's verdicts are advisory notes beside them.)
|