@wildo-ai/framework-knowledge 1.1.7 → 1.1.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/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
|
@@ -1,11 +1,11 @@
|
|
|
1
1
|
{
|
|
2
2
|
"artifactVersion": "3",
|
|
3
|
-
"frameworkVersion": "1.1.
|
|
4
|
-
"generatorVersion": "1.1.
|
|
5
|
-
"generatedAt": "2026-
|
|
3
|
+
"frameworkVersion": "1.1.9",
|
|
4
|
+
"generatorVersion": "1.1.9",
|
|
5
|
+
"generatedAt": "2026-10-03T03:06:36.431Z",
|
|
6
6
|
"packageName": "@wildo-ai/framework-knowledge",
|
|
7
|
-
"topicCount":
|
|
8
|
-
"referenceFileCount":
|
|
7
|
+
"topicCount": 773,
|
|
8
|
+
"referenceFileCount": 654,
|
|
9
9
|
"payload": {
|
|
10
10
|
"topicIndexPath": "topic-index.json",
|
|
11
11
|
"registriesDirectory": "registries",
|
|
@@ -21,19 +21,19 @@
|
|
|
21
21
|
"registryName": "source-tags",
|
|
22
22
|
"filePath": "registries/source-tags.json",
|
|
23
23
|
"description": "Source-derived tag registry for extracted framework references.",
|
|
24
|
-
"entryCount":
|
|
24
|
+
"entryCount": 654
|
|
25
25
|
},
|
|
26
26
|
{
|
|
27
27
|
"registryName": "framework-topics",
|
|
28
28
|
"filePath": "registries/framework-topics.json",
|
|
29
29
|
"description": "Topic registry derived from extracted framework-knowledge tags.",
|
|
30
|
-
"entryCount":
|
|
30
|
+
"entryCount": 773
|
|
31
31
|
},
|
|
32
32
|
{
|
|
33
33
|
"registryName": "playbooks",
|
|
34
34
|
"filePath": "registries/playbooks.json",
|
|
35
35
|
"description": "Compiled meta-workflow playbooks (app-creation methodology definitions).",
|
|
36
|
-
"entryCount":
|
|
36
|
+
"entryCount": 47
|
|
37
37
|
},
|
|
38
38
|
{
|
|
39
39
|
"registryName": "assurance-authority-bases",
|
|
@@ -14,8 +14,11 @@ by editing this file.
|
|
|
14
14
|
|
|
15
15
|
## What it verifies today, and what it does not
|
|
16
16
|
|
|
17
|
-
**It verifies** that the application typechecks as a whole —
|
|
18
|
-
`backend-api` and `frontend
|
|
17
|
+
**It verifies** that the application typechecks as a whole — every workspace package it has:
|
|
18
|
+
`specifications`, `shared-lib`, `backend-api` and `frontend`, and the `website`, the technical
|
|
19
|
+
documentation site and each worker and minion package where the application composed one. The set is
|
|
20
|
+
derived from the application's packages, so a package added to it is checked without anyone listing
|
|
21
|
+
it; one the application does not have answers "nothing to typecheck". That is the question no earlier step answers: the dispatch lane
|
|
19
22
|
typechecks the one package a task mutated, so a build can consist entirely of green tasks and still
|
|
20
23
|
not compile as a program. Cross-package breakage is the characteristic failure of a build assembled
|
|
21
24
|
from independent tasks, and this is where it surfaces.
|
|
@@ -23,7 +26,7 @@ from independent tasks, and this is where it surfaces.
|
|
|
23
26
|
**It also verifies that the database schema plan is in sync** — that every resource the application
|
|
24
27
|
models has a migration behind it. This is a different question from compilation, and no typecheck
|
|
25
28
|
can answer it: on a PostgreSQL-backed application a table is built by a MIGRATION and by nothing
|
|
26
|
-
else, so a resource whose migration was never generated compiles perfectly in
|
|
29
|
+
else, so a resource whose migration was never generated compiles perfectly in every package and
|
|
27
30
|
then refuses to boot with `postgresql_table_schema_mismatch`. There is no type in the program that
|
|
28
31
|
knows whether a table exists.
|
|
29
32
|
|
|
@@ -44,8 +47,17 @@ A failure here means a migration is owed. Generate it with `wildo db generate --
|
|
|
44
47
|
which writes the migration **and** advances the lockfile in one invocation; the
|
|
45
48
|
`application-database-migrations` skill carries the full procedure and every refusal.
|
|
46
49
|
|
|
47
|
-
**It
|
|
48
|
-
|
|
50
|
+
**It also verifies that the sites BUILD and that the configuration VALIDATES** (#2228) — questions
|
|
51
|
+
a typecheck cannot answer. The `website` runs its own `astro build`, which refuses a page with no
|
|
52
|
+
sections and renders every route; the documentation portal runs `docusaurus build`, which refuses
|
|
53
|
+
until the documentation is published and resolves every link. An application without one of them
|
|
54
|
+
answers "nothing to build". `wildo config validate` runs the checks the backend runs at startup:
|
|
55
|
+
an error fails the check, because a backend with configuration errors does not boot; a warning
|
|
56
|
+
does not. A missing `wildo` CLI is "we could not ask", never a failing configuration. These run
|
|
57
|
+
here and at the end of the build plan, never per task: a site build takes minutes, and every task
|
|
58
|
+
already owes its package's typecheck.
|
|
59
|
+
|
|
60
|
+
**It does not** boot the application, run its test suite, or regenerate OpenAPI and documentation. Each needs a running stack or a companion affordance that does not exist
|
|
49
61
|
yet. They are absent rather than declared-and-skipped on purpose: the previous version of this
|
|
50
62
|
playbook declared all of them, ran none, and carried a long disclaimer saying so — a check that is
|
|
51
63
|
announced and not executed is worse than one that is missing, because a reader counts it.
|
|
@@ -55,8 +67,11 @@ announced and not executed is worse than one that is missing, because a reader c
|
|
|
55
67
|
Three outcomes, and they mean different things:
|
|
56
68
|
|
|
57
69
|
- **every check passed** — the application assembles. This is the signal the phase gate wants.
|
|
58
|
-
- **a check failed** — the application does not assemble. The failure names the package
|
|
59
|
-
is
|
|
70
|
+
- **a check failed** — the application does not assemble. The failure names the package. Repairing it
|
|
71
|
+
is not this playbook's job: the build's next dispatch answers with a repair run for the first failing
|
|
72
|
+
check, scoped and verified from that check. A check gets at most two repairs per round, and none when
|
|
73
|
+
the last one was given the same failure. Once those are spent, the build's refusal names the check, and
|
|
74
|
+
it needs a person or a new build task.
|
|
60
75
|
- **an infrastructure error** — the check could not be RUN. This is reported separately and must not
|
|
61
76
|
be read as a failure: "the application does not typecheck" and "we could not run the typecheck"
|
|
62
77
|
lead you to entirely different places, and only the first is the application's fault.
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "bottom_up.assemble-verify",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.4.0",
|
|
4
4
|
"phase": "bottom_up",
|
|
5
|
-
"intent": "Bottom-up assemble & verify — the FINAL bottom-up step and the capstone of the build: the pivot from having BUILT the application (the decompose / dispatch / scale loop authored its modules, resources, config and integrations) to answering ONE mechanical question — does the built application ASSEMBLE? It runs the deterministic verification set over the application
|
|
5
|
+
"intent": "Bottom-up assemble & verify — the FINAL bottom-up step and the capstone of the build: the pivot from having BUILT the application (the decompose / dispatch / scale loop authored its modules, resources, config and integrations) to answering ONE mechanical question — does the built application ASSEMBLE? It runs the deterministic verification set over EVERY workspace package the application has (specifications, shared-lib, backend-api, frontend, and the website, technical documentation site, workers and minions it composed), derived from those packages rather than listed, OUTSIDE any coding agent, and reports a per-check outcome. It fixes NOTHING: a failure is surfaced for a refinement re-dispatch, which is a different playbook's job, and it authors no schemas and writes no code. Deliberately DISTINCT from the refinement phase's coverage audit, which also binds topic 7 but asks a SEMANTIC question (does the built app match the intent — specs diffed against introspected reality). This playbook never diffs intent against reality; if you are judging coverage you are in the refinement lane. Scope honesty: the check set is the whole-application TYPECHECK across every package — the question 'does it compile as one program', which no per-task check can answer because the dispatch lane typechecks only the package a task mutated — PLUS the schema-plan drift gate (`check:schema-plan-in-sync`), which asks whether the modelled resources have migrations behind them. The second is not a variant of the first: on a PostgreSQL-backed application a table exists only because a migration built it, so a resource whose migration was never generated compiles green in every package and then refuses to boot on `postgresql_table_schema_mismatch` — invisible to a typecheck, because no type in the program knows whether a table exists. It is safe on MongoDB applications and on unbuilt trees because it resolves three outcomes (not adopted / could-not-ask / decided) rather than reading an exit code. Since #2228 it also asks the two questions a typecheck cannot: does each optional site BUILD (the website's `astro build`, the documentation portal's `docusaurus build`; an absent package answers 'nothing to build'), and does the configuration pass `wildo config validate` (errors fail, warnings do not, a missing CLI is 'we could not ask'). A boot probe, the whole test suite and OpenAPI/docs regeneration are NOT in this set: each needs a running stack or a companion affordance that does not exist, and declaring them here without running them is exactly what made the deleted version of this playbook inert.",
|
|
6
6
|
"preconditions": [
|
|
7
7
|
{
|
|
8
8
|
"kind": "artifact_exists",
|
|
@@ -19,7 +19,7 @@
|
|
|
19
19
|
"outputs": [],
|
|
20
20
|
"stepOutputs": [],
|
|
21
21
|
"method": {
|
|
22
|
-
"guidance": "# Assemble & verify — does the built application hold together?\n\nThis is the last bottom-up step. Everything before it AUTHORED the application; this one asks\nwhether what was authored is one working program.\n\n## What this playbook does\n\nIt runs a fixed set of deterministic checks against the application's workspace packages, outside\nany coding agent, and reports one outcome per check. It changes nothing.\n\nThe check set is host-owned, not authored here. A playbook names semantic check references; turning\none into an executable command is reviewed host work, which is why a new check cannot be introduced\nby editing this file.\n\n## What it verifies today, and what it does not\n\n**It verifies** that the application typechecks as a whole — `specifications`, `shared-lib
|
|
22
|
+
"guidance": "# Assemble & verify — does the built application hold together?\n\nThis is the last bottom-up step. Everything before it AUTHORED the application; this one asks\nwhether what was authored is one working program.\n\n## What this playbook does\n\nIt runs a fixed set of deterministic checks against the application's workspace packages, outside\nany coding agent, and reports one outcome per check. It changes nothing.\n\nThe check set is host-owned, not authored here. A playbook names semantic check references; turning\none into an executable command is reviewed host work, which is why a new check cannot be introduced\nby editing this file.\n\n## What it verifies today, and what it does not\n\n**It verifies** that the application typechecks as a whole — every workspace package it has:\n`specifications`, `shared-lib`, `backend-api` and `frontend`, and the `website`, the technical\ndocumentation site and each worker and minion package where the application composed one. The set is\nderived from the application's packages, so a package added to it is checked without anyone listing\nit; one the application does not have answers \"nothing to typecheck\". That is the question no earlier step answers: the dispatch lane\ntypechecks the one package a task mutated, so a build can consist entirely of green tasks and still\nnot compile as a program. Cross-package breakage is the characteristic failure of a build assembled\nfrom independent tasks, and this is where it surfaces.\n\n**It also verifies that the database schema plan is in sync** — that every resource the application\nmodels has a migration behind it. This is a different question from compilation, and no typecheck\ncan answer it: on a PostgreSQL-backed application a table is built by a MIGRATION and by nothing\nelse, so a resource whose migration was never generated compiles perfectly in every package and\nthen refuses to boot with `postgresql_table_schema_mismatch`. There is no type in the program that\nknows whether a table exists.\n\nThe check is safe on every application because it resolves three outcomes rather than two:\n\n- **no committed schema-plan lockfile** — read against the application's DECLARED store, because the\n absence means opposite things (#1144). A MongoDB application is permanently in this state and the\n check passes saying it verified nothing: a collection exists on first write. A PostgreSQL one has\n had no migration create its tables and cannot boot, so the check FAILS and names the initial\n `wildo db generate`. A store the check cannot read is \"we could not ask\", like the case below.\n- **no compiled `backend-api/dist`** — the plan is computed by importing the compiled registry, and\n a build that only ran `tsc --noEmit` never emitted one. Reported as an INFRASTRUCTURE error, never\n as drift: \"we could not ask\" is not \"the application has drifted\".\n- **both present** — `wildo db diff --check` decides, and its own message names the drifted tables\n and the command that fixes them.\n\nA failure here means a migration is owed. Generate it with `wildo db generate --name <what-changed>`,\nwhich writes the migration **and** advances the lockfile in one invocation; the\n`application-database-migrations` skill carries the full procedure and every refusal.\n\n**It also verifies that the sites BUILD and that the configuration VALIDATES** (#2228) — questions\na typecheck cannot answer. The `website` runs its own `astro build`, which refuses a page with no\nsections and renders every route; the documentation portal runs `docusaurus build`, which refuses\nuntil the documentation is published and resolves every link. An application without one of them\nanswers \"nothing to build\". `wildo config validate` runs the checks the backend runs at startup:\nan error fails the check, because a backend with configuration errors does not boot; a warning\ndoes not. A missing `wildo` CLI is \"we could not ask\", never a failing configuration. These run\nhere and at the end of the build plan, never per task: a site build takes minutes, and every task\nalready owes its package's typecheck.\n\n**It does not** boot the application, run its test suite, or regenerate OpenAPI and documentation. Each needs a running stack or a companion affordance that does not exist\nyet. They are absent rather than declared-and-skipped on purpose: the previous version of this\nplaybook declared all of them, ran none, and carried a long disclaimer saying so — a check that is\nannounced and not executed is worse than one that is missing, because a reader counts it.\n\n## Reading the result\n\nThree outcomes, and they mean different things:\n\n- **every check passed** — the application assembles. This is the signal the phase gate wants.\n- **a check failed** — the application does not assemble. The failure names the package. Repairing it\n is not this playbook's job: the build's next dispatch answers with a repair run for the first failing\n check, scoped and verified from that check. A check gets at most two repairs per round, and none when\n the last one was given the same failure. Once those are spent, the build's refusal names the check, and\n it needs a person or a new build task.\n- **an infrastructure error** — the check could not be RUN. This is reported separately and must not\n be read as a failure: \"the application does not typecheck\" and \"we could not run the typecheck\"\n lead you to entirely different places, and only the first is the application's fault.\n\nA dry run resolves the check set and executes nothing, so it tells you what would be verified\nwithout paying for it.\n\n## Quality gate\n\nThe gate is the check set itself, run by the host. There is no declared gate restating it — a second\ndescription of a live check is exactly what the retired `qualityGates` field was.\n\n## Acceptance\n\nThe creator reviews the reported outcomes. As everywhere in this lane, the run accepts nothing:\nacceptance is a later commit, and who makes it is the host's autonomy posture.\n",
|
|
23
23
|
"skillRefs": [
|
|
24
24
|
"application-database-migrations"
|
|
25
25
|
],
|
|
@@ -23,15 +23,16 @@ never a "done".
|
|
|
23
23
|
domain plan, the placement plan, the roadmap and the requirements, each task bound to
|
|
24
24
|
an application skill and to what it produces. Its own gate makes it ineligible once
|
|
25
25
|
the plan is fully landed and nothing upstream has moved.
|
|
26
|
-
- **`bottom_up.build-dispatch`** —
|
|
27
|
-
|
|
28
|
-
|
|
26
|
+
- **`bottom_up.build-dispatch`** — one WAVE per run: up to the application's build
|
|
27
|
+
parallelism of ready tasks at once (`wildo workbench parallelism`, 5 by default), each
|
|
28
|
+
routed by its target — a coding run in the workspace, or a companion-owned generation
|
|
29
|
+
step (labels, logo, emails, seeds). The runs share the worktree; the wave repairs what
|
|
30
|
+
they overwrote in each other when they have settled, then reports every run's outcome.
|
|
31
|
+
With a build parallelism of `1` it is one task per run. Lands no family, so it is
|
|
29
32
|
offered again every round — that is the loop.
|
|
30
|
-
- **`bottom_up.build-scale`** — the same act as dispatch
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
the wave exists, and its report lists the ready tasks it left behind rather than
|
|
34
|
-
running them.
|
|
33
|
+
- **`bottom_up.build-scale`** — the same act as dispatch: it declares the same executor
|
|
34
|
+
and starts the same wave. Prefer `bottom_up.build-dispatch`; selecting scale instead
|
|
35
|
+
gains nothing, and selecting both in one round would start two waves side by side.
|
|
35
36
|
- **`bottom_up.assemble-verify`** — does the built application assemble? The
|
|
36
37
|
deterministic verification set over the application's packages and the migration
|
|
37
38
|
drift probe.
|
|
@@ -51,19 +52,20 @@ between rounds unblocks its dependents without re-planning.
|
|
|
51
52
|
decomposer is offered again after its own judge found the plan does not cover the domain
|
|
52
53
|
plan (marked RE-OPENED in the round history) — then in refine mode, keeping the refs of
|
|
53
54
|
what has landed, and aimed at the criterion that faulted.
|
|
54
|
-
- **Dispatch while tasks remain.** Each round's objective names the
|
|
55
|
-
round dispatched and
|
|
56
|
-
read
|
|
55
|
+
- **Dispatch while tasks remain.** Each round's objective names the tasks the previous
|
|
56
|
+
round's wave dispatched and how each came out — the dispatch child returns those
|
|
57
|
+
outcomes, so read them rather than assuming. Once every task has landed, dispatch is no longer
|
|
57
58
|
offered at all and the remaining child is assemble-verify.
|
|
58
|
-
- **One child per round.**
|
|
59
|
-
|
|
59
|
+
- **One child per round.** The parallelism is INSIDE the dispatch child: its wave already
|
|
60
|
+
runs as many tasks at once as the build parallelism allows. A second child in the same
|
|
61
|
+
round would start a second wave beside it and double the width the person chose.
|
|
60
62
|
- **A parked question waits for the creator.** A coding run that parked on a question
|
|
61
63
|
is answered on the creation surface; the task is re-dispatched when it is.
|
|
62
64
|
|
|
63
65
|
## Composing an objective for a child
|
|
64
66
|
|
|
65
|
-
For dispatch: the
|
|
66
|
-
|
|
67
|
+
For dispatch: the tasks the previous round's wave dispatched, their outcomes, and what
|
|
68
|
+
the tasks ready now are expected to produce. For a refine decomposition: the task that could
|
|
67
69
|
not land and why. For assembly: nothing to compose — it runs the declared checks.
|
|
68
70
|
|
|
69
71
|
## When to stop
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
"ref": "bottom_up.build",
|
|
3
3
|
"version": "0.1.0",
|
|
4
4
|
"phase": "bottom_up",
|
|
5
|
-
"intent": "Drive the BUILD of the application as one lane: decompose the accepted conception into a build plan, dispatch the plan's ready tasks one at a time
|
|
5
|
+
"intent": "Drive the BUILD of the application as one lane: decompose the accepted conception into a build plan, dispatch the plan's ready tasks in parallel waves — up to the application's build parallelism at once (5 by default; 1 means one at a time), coding runs and the companion's own generation steps alike — until every task has landed, then assemble and verify the built application, and read its maturity against the requirements it was asked to satisfy. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round. The build plan is decomposed ONCE unless its inputs have moved since it landed (the decomposer's own gate says so). Dispatch is one wave per run (the parallelism is inside it, so select ONE child per round) and lands no family, so it is offered every round: keep selecting it while the plan has tasks left, with each round's objective naming what the previous round's wave dispatched and how each run came out. Prefer build-dispatch to build-scale: both start the same wave. When dispatch reports the plan exhausted, select assemble-verify, and then the maturity reading. STOP on the reading: it is what this lane ends on, and it names a STAGE rather than a completion. Stop early only when dispatch reports a task that cannot land twice, or a parked question waits on the creator — say which. A parked coding question waits for the creator; run everything else.",
|
|
6
6
|
"preconditions": [
|
|
7
7
|
{
|
|
8
8
|
"kind": "artifact_valid",
|
|
@@ -39,7 +39,7 @@
|
|
|
39
39
|
}
|
|
40
40
|
],
|
|
41
41
|
"method": {
|
|
42
|
-
"guidance": "# The Build Lane — the umbrella\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\nThis playbook produces nothing itself. It drives the steps that BUILD the application\nfrom its accepted conception — the build plan, the dispatch of its tasks, the assembly\ncheck — and it will end on the maturity reading: a stage against the requirements,\nnever a \"done\".\n\n## The children, and why the order is not written here\n\n- **`bottom_up.build-decompose`** — the build plan: an ordered task graph over the\n domain plan, the placement plan, the roadmap and the requirements, each task bound to\n an application skill and to what it produces. Its own gate makes it ineligible once\n the plan is fully landed and nothing upstream has moved.\n- **`bottom_up.build-dispatch`** —
|
|
42
|
+
"guidance": "# The Build Lane — the umbrella\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\nThis playbook produces nothing itself. It drives the steps that BUILD the application\nfrom its accepted conception — the build plan, the dispatch of its tasks, the assembly\ncheck — and it will end on the maturity reading: a stage against the requirements,\nnever a \"done\".\n\n## The children, and why the order is not written here\n\n- **`bottom_up.build-decompose`** — the build plan: an ordered task graph over the\n domain plan, the placement plan, the roadmap and the requirements, each task bound to\n an application skill and to what it produces. Its own gate makes it ineligible once\n the plan is fully landed and nothing upstream has moved.\n- **`bottom_up.build-dispatch`** — one WAVE per run: up to the application's build\n parallelism of ready tasks at once (`wildo workbench parallelism`, 5 by default), each\n routed by its target — a coding run in the workspace, or a companion-owned generation\n step (labels, logo, emails, seeds). The runs share the worktree; the wave repairs what\n they overwrote in each other when they have settled, then reports every run's outcome.\n With a build parallelism of `1` it is one task per run. Lands no family, so it is\n offered again every round — that is the loop.\n- **`bottom_up.build-scale`** — the same act as dispatch: it declares the same executor\n and starts the same wave. Prefer `bottom_up.build-dispatch`; selecting scale instead\n gains nothing, and selecting both in one round would start two waves side by side.\n- **`bottom_up.assemble-verify`** — does the built application assemble? The\n deterministic verification set over the application's packages and the migration\n drift probe.\n- **`bottom_up.maturity-reading`** — what the built application is WORTH against the\n requirements it was asked to satisfy: which are addressed, by what evidence, and the\n stage that puts it at. This is what the lane ends on. Assembly says the code compiles;\n the reading says what the application has become.\n\nNothing above is a sequence. The plan needs the conception; dispatch needs the plan;\nassembly needs the plan. Readiness is re-derived from git each round, so a task accepted\nbetween rounds unblocks its dependents without re-planning.\n\n## Selecting the next child\n\n- **Decompose once.** Re-decompose only when the decomposer's gate says an input has\n moved since the plan landed, when dispatch reports a task that cannot land, or when the\n decomposer is offered again after its own judge found the plan does not cover the domain\n plan (marked RE-OPENED in the round history) — then in refine mode, keeping the refs of\n what has landed, and aimed at the criterion that faulted.\n- **Dispatch while tasks remain.** Each round's objective names the tasks the previous\n round's wave dispatched and how each came out — the dispatch child returns those\n outcomes, so read them rather than assuming. Once every task has landed, dispatch is no longer\n offered at all and the remaining child is assemble-verify.\n- **One child per round.** The parallelism is INSIDE the dispatch child: its wave already\n runs as many tasks at once as the build parallelism allows. A second child in the same\n round would start a second wave beside it and double the width the person chose.\n- **A parked question waits for the creator.** A coding run that parked on a question\n is answered on the creation surface; the task is re-dispatched when it is.\n\n## Composing an objective for a child\n\nFor dispatch: the tasks the previous round's wave dispatched, their outcomes, and what\nthe tasks ready now are expected to produce. For a refine decomposition: the task that could\nnot land and why. For assembly: nothing to compose — it runs the declared checks.\n\n## When to stop\n\nStop on the maturity reading. It is the decision this lane ends on, and it names a\nSTAGE rather than a completion — there is no \"done\" for an application, only a\nmeasurement against its requirements that moves every time a later run lands something. Stop when dispatch has reported a task\nthat cannot land twice, or a parked question waits on the creator, and say which. A\nfull build takes several runs of this lane; each resumes where readiness now stands.\n\n## What the creator reviews\n\nEach dispatched task's work in the application workspace, through `git status`, and\nthe assembly verdict. A task lands only when its product is committed — acceptance is\nthe commit, here as everywhere in the lane.\n",
|
|
43
43
|
"skillRefs": [],
|
|
44
44
|
"skillBodyRefs": [],
|
|
45
45
|
"contextSources": [],
|
|
@@ -77,7 +77,8 @@
|
|
|
77
77
|
"bottom_up.build-decompose"
|
|
78
78
|
]
|
|
79
79
|
}
|
|
80
|
-
]
|
|
80
|
+
],
|
|
81
|
+
"closingMove": "bottom_up.assemble-verify"
|
|
81
82
|
},
|
|
82
83
|
"suspendsForClarification": false,
|
|
83
84
|
"briefAdequacyGate": false,
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"aggregationPolicyRef":"application-creation:aggregation/worst-build-plan-coherent-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/build-plan-companion-generation-interleave","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-companion-generation-interleave","requirementVersion":1}],"instruction":"Determine whether the executable companion-owned generation steps are present and placed after the surfaces whose output they consume: i18n-labels after the resources it labels; email-templates after the surfaces it serves; database-migrations after the schema stages whose drift it migrates, and only for a PostgreSQL-backed application; logo present whenever the application has a brand brief, and unordered with respect to resource work because it consumes the brand and no code surface. Do NOT flag the absence of a seeds step: seed generation has no companion pipeline and must not be authored.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A labels or email step is ordered before some surface it consumes, a migration step is missing on a PostgreSQL-backed application, or the logo step is missing on an application with a brand brief.","GAP":"A generation step the pipeline cannot execute is authored (an unknown generationStepRef, or seeds), or a generation step declares products.","INDETERMINATE":"Whether the application has a brand brief or which store it uses is not in evidence, so the required step set cannot be decided.","PASS":"Every executable generation step the application needs is present and placed after the surfaces it consumes; logo is present when a brand exists."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-decomposition-boundary","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-decomposition-boundary","requirementVersion":1}],"instruction":"Determine whether the plan stays at DECOMPOSITION depth: tasks name what they build, their topic, their skills, their target, their products and their ordering intent, and do not specify how a task is dispatched (single-flight locking, change-set capture, git baseline, verify mechanics), do not solve multi-agent scale or interleaving concurrency, and do not author a schema, resolve a cardinality into a concrete foreign key, or generate code.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A task brief drifts toward execution detail or names a concrete field type or foreign key the coding agent should decide.","GAP":"A task that specifies dispatch mechanics, concurrency, or authors schema or code in the plan itself.","INDETERMINATE":"Task briefs are not in evidence.","PASS":"Every task describes WHAT it builds and none describes how it executes."}},{"assessesAspects":["build-plan.task","domain-plan.module","domain-plan.resource"],"criterionRef":"application-creation:criterion/build-plan-module-and-resource-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-module-and-resource-coverage","requirementVersion":1}],"instruction":"Determine whether every resource in every module's inventory (mainResources and supportingResources) of the domain plan has build tasks, and whether every task's moduleRef names a module the domain plan declares. A module whose resources have tasks but which carries no redundant scaffold task is NOT a finding: module slices are scaffolded by the foundation step. A module added after foundation with neither a foundation slice nor an ensure-module task IS a gap. The billing catalogue is covered the same way: every pricing plan the business model declares must be an APPLICATION_BILLING_PRODUCT of a BILLING_CATALOG task whose servesRefs name the plan; a declared plan with no billing product is a gap (the backend would have nothing to sell and the website would re-type its price).","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete, but a task's objective CREATES a resource the domain plan shows as already existing instead of enriching it (a no-op dispatch), or a supporting resource's coverage is thin.","GAP":"A resource with no task (the build would not produce it), or a task naming a module the domain plan does not declare (the dispatcher cannot route it).","INDETERMINATE":"The domain plan or the build plan is absent, truncated or unreadable, so coverage cannot be established.","PASS":"Every domain-plan resource has build tasks and every moduleRef resolves to a declared module."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-per-resource-stage-order","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-per-resource-stage-order","requirementVersion":1}],"instruction":"For each resource, determine whether its tasks respect the inner order schema -> config -> ui-behavior -> spec through their declared prerequisiteTaskRefs. A supporting resource may legitimately omit stages it does not need (a junction with schema and config and no ui-behavior is fine); only an out-of-order stage, or a main resource missing schema or config, is a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Stages are ordered but a prerequisite edge is carried by prose rather than by prerequisiteTaskRefs, or an omitted stage on a supporting resource is unexplained.","GAP":"A config task ordered before its resource's schema task, a spec task before its ui-behavior task, or a main resource with no schema or config stage.","INDETERMINATE":"Tasks do not carry enough target and prerequisite detail to reconstruct per-resource order.","PASS":"Every resource's stages are ordered schema -> config -> ui-behavior -> spec through declared prerequisites, and every main resource has schema and config."}},{"assessesAspects":["build-plan.task","domain-plan.relationship"],"criterionRef":"application-creation:criterion/build-plan-relationship-coverage","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-relationship-coverage","requirementVersion":1}],"instruction":"Determine whether every relationship draft in the domain plan has a wiring task bound to the module-relationships skill, ordered after BOTH endpoint resources' schema tasks, and whether the wiring task is the single home of the relationship's foreign-key product. A relationship whose source or target resource is declared by no module of the domain plan is NOT this criterion's finding: no task can wire it, so it is the conception's fault and `conception-buildable` judges it. Judge the relationships whose endpoints both exist.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Every relationship is wired, but a wiring task's ordering relies on prose rather than declared prerequisites, or its cardinality intent is restated loosely.","GAP":"A relationship draft whose endpoints both exist with no wiring task, a wiring task ordered before an endpoint's schema task, or a relationship whose foreign key is also claimed by a schema task.","INDETERMINATE":"The domain plan's relationship drafts are not in evidence.","PASS":"Every relationship draft has one wiring task, ordered after both endpoints' schema tasks."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-task-well-formedness-and-products","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-task-well-formedness-and-products","requirementVersion":1}],"instruction":"Determine whether every task names exactly one real functional topic and at least one skill from the app-knowledge skill catalog, and whether every task except a COMPANION_GENERATION_STEP declares at least one product that names something composition does not already write (the fields a schema gains, the verbs a config gains, both endpoints of a relationship, the declarations a config file gains, the jobs a worker gains — not a scaffolded file or a composed package). Every product must be of the kind that names its surface: a view is a RESOURCE_COMPOSITE_VIEW / RESOURCE_CUSTOM_VIEW / RESOURCE_CHART_VIEW / APPLICATION_VIEW, a page a WEBSITE_PAGE, a worker an APPLICATION_WORKER, a provider a PROVIDER_BINDING — a non-resource surface declared under a MODULE target with a resource-shaped product, or with no product at all, is a gap. No two tasks may claim the same artifact; two tasks enriching one resource with DIFFERENT fields is correct. A cross-resource foreign key declared on a schema task's products is a gap: the relationship task is its single home.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A task's products are meaningful but thinly described, or a generation step's landed condition is stated loosely.","GAP":"An invented topic or dangling skill; a coding task with empty products; a product naming only a scaffolded artifact or a composed package; a non-resource surface (a view, a page, a worker, a provider, a config file) declared under a resource-shaped kind; two tasks claiming one artifact; or a foreign key attributed to a schema task.","INDETERMINATE":"The skill catalog or the task list is not in evidence, so bindings cannot be checked.","PASS":"Every task is bound to a real topic and skill, declares products composition does not already write, and no artifact is claimed twice."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-topic-dependency-order","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-topic-dependency-order","requirementVersion":1}],"instruction":"Determine whether tasks respect the topic dependency edges: model_domain_graph before define_interaction_semantics; an app-level shape_user_experience task (views or navigation composing several 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; and a resource's spec task after the stages it documents. A resource's OWN ui-behavior depends only on its own schema and config and MAY precede cross-resource operations — that is not a violation.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The order is right but relies on band position rather than a declared prerequisite, or an MVP-first tie-break contradicts the roadmap's phasing.","GAP":"An app-level view composing resources or operations placed before they exist, an integration task before the resources it connects, a user-experience task before that resource's schema task, or a spec task before its ui-behavior stage.","INDETERMINATE":"Topics or prerequisites are missing from the evidence, so ordering cannot be reconstructed.","PASS":"Every cross-topic dependency is honoured by declared prerequisites, and the per-resource ui-behavior exception is applied correctly."}},{"assessesAspects":["build-plan.task","domain-plan.module","domain-plan.resource","domain-plan.relationship"],"criterionRef":"application-creation:criterion/conception-buildable","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/conception-buildable","requirementVersion":1}],"instruction":"Determine whether the CONCEPTION this plan rests on can be built as declared. This criterion faults the domain plan, the capability composition or the surface plans — never the build plan. It is a GAP when (a) the domain plan declares a module, resource or relationship that no build task target can express, however it is decomposed, or (b) the computed coherence report shows a dangling reference or an 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. A domain-plan element declared in an expressible shape that the build plan simply omits is NOT this criterion: that is module-and-resource coverage, the decomposer's own fault. Name the conception element in the rationale.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A conception element is expressible only awkwardly, or the coherence report shows an unrealised item that reads as a deliberate deferral.","GAP":"The domain plan declares something no build target can express, or the coherence report shows a dangling reference or unrealised decision in the conception that the build cannot proceed past without inventing it.","INDETERMINATE":"The domain plan or the coherence report is not in evidence, so the conception cannot be read against the plan.","PASS":"Everything the conception declares has a build target, and the coherence report shows nothing in it the build would have to invent."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/build-plan-coherent","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:bottom_up.build-decompose"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
|
|
1
|
+
{"aggregationPolicyRef":"application-creation:aggregation/worst-build-plan-coherent-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/build-plan-companion-generation-interleave","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-companion-generation-interleave","requirementVersion":1}],"instruction":"Determine whether the executable companion-owned generation steps are present and placed after the surfaces whose output they consume: i18n-labels after the resources it labels; email-templates after the surfaces it serves; database-migrations after the schema stages whose drift it migrates, and only for a PostgreSQL-backed application; logo present whenever the application has a brand brief, and unordered with respect to resource work because it consumes the brand and no code surface. 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, and seeding is an APPLICATION_DATA_SEED coding task judged under module-and-resource coverage.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A labels or email step is ordered before some surface it consumes, a migration step is missing on a PostgreSQL-backed application, or the logo step is missing on an application with a brand brief.","GAP":"A generation step the pipeline cannot execute is authored (an unknown generationStepRef, or a seeds generation step), or a generation step declares products.","INDETERMINATE":"Whether the application has a brand brief or which store it uses is not in evidence, so the required step set cannot be decided.","PASS":"Every executable generation step the application needs is present and placed after the surfaces it consumes; logo is present when a brand exists."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-decomposition-boundary","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-decomposition-boundary","requirementVersion":1}],"instruction":"Determine whether the plan stays at DECOMPOSITION depth: tasks name what they build, their topic, their skills, their target, their products and their ordering intent, and do not specify how a task is dispatched (dispatch locking and concurrency, change-set capture, git baseline, verify mechanics), do not solve multi-agent scale or interleaving concurrency, and do not author a schema, resolve a cardinality into a concrete foreign key, or generate code.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A task brief drifts toward execution detail or names a concrete field type or foreign key the coding agent should decide.","GAP":"A task that specifies dispatch mechanics, concurrency, or authors schema or code in the plan itself.","INDETERMINATE":"Task briefs are not in evidence.","PASS":"Every task describes WHAT it builds and none describes how it executes."}},{"assessesAspects":["build-plan.task","experience-plan.view","experience-plan.configuration","experience-plan.milestone","experience-plan.guidance"],"criterionRef":"application-creation:criterion/build-plan-experience-coverage","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-experience-coverage","requirementVersion":1}],"instruction":"Determine whether every surface the experience plan decides has its build task: one task per VIEW (target MODULE_FRONTEND on the view's module, a product of the view's kind carrying the plan's viewRef verbatim), one APPLICATION_FRONTEND_CONFIG task per CONFIGURATION, one APPLICATION_MILESTONE task per planned MILESTONE, and one APPLICATION_GUIDANCE task per planned piece of GUIDANCE (an onboarding document's objective naming the hostViewRef that embeds it). A view, configuration, milestone or guidance entry with no task is a gap: the application would ship without it while the plan reads complete. Never conclude the plan is absent because this criterion's own slice does not show it: the accepted application truth either renders the experience plan or says it has none. When the accepted application truth STATES that `experience-plan` has no accepted content, the decomposer has rightly emitted none of these tasks and cannot repair the absence by revising: record PASS, and begin the rationale with the words 'NO EXPERIENCE PLAN:' followed by what the application will therefore lack (its app-level views, its shell and navigation configuration, its milestones and its onboarding), so the absence is on the record instead of silent.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Every entry has a task, but a task's objective drops what the plan decided for it: a view's reusesComponentRefs, a milestone's moment, a guidance entry's gate, or an onboarding document's hostViewRef.","GAP":"A view, configuration, milestone or guidance entry the experience plan declares has no task, or a view task carries a viewRef the plan does not declare.","INDETERMINATE":"The build plan is not in evidence, or the accepted application truth neither renders the experience plan nor states that it has none. (A STATED absence is not indeterminate: it is the PASS case above, marked.)","PASS":"Every view, configuration, milestone and guidance entry of the experience plan has its task — or no experience plan is in evidence, and the rationale begins 'NO EXPERIENCE PLAN:' and names what the application will lack."}},{"assessesAspects":["build-plan.task","domain-plan.module","domain-plan.resource"],"criterionRef":"application-creation:criterion/build-plan-module-and-resource-coverage","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-module-and-resource-coverage","requirementVersion":1}],"instruction":"Determine whether every resource in every module's inventory (mainResources and supportingResources) of the domain plan has build tasks, and whether every task's moduleRef names a module the domain plan declares. A module whose resources have tasks but which carries no redundant scaffold task is NOT a finding: module slices are scaffolded by the foundation step. A module added after foundation with neither a foundation slice nor an ensure-module task IS a gap. The billing catalogue is covered the same way: every pricing plan the business model declares must be an APPLICATION_BILLING_PRODUCT of a BILLING_CATALOG task whose servesRefs name the plan; a declared plan with no billing product is a gap (the backend would have nothing to sell and the website would re-type its price). Seeding is covered the same way: a plan whose domain has main resources and no APPLICATION_DATA_SEED task of content DEMONSTRATION is a concern — the application would open empty, with nothing a creator can judge or show (#2234).","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete, but a task's objective CREATES a resource the domain plan shows as already existing instead of enriching it (a no-op dispatch), a supporting resource's coverage is thin, or no DEMONSTRATION data seed gives the main resources sample rows.","GAP":"A resource with no task (the build would not produce it), or a task naming a module the domain plan does not declare (the dispatcher cannot route it).","INDETERMINATE":"The domain plan or the build plan is absent, truncated or unreadable, so coverage cannot be established.","PASS":"Every domain-plan resource has build tasks and every moduleRef resolves to a declared module."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-per-resource-stage-order","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-per-resource-stage-order","requirementVersion":1}],"instruction":"For each resource, determine whether its tasks respect the inner order schema -> config -> ui-behavior -> spec through their declared prerequisiteTaskRefs. A supporting resource may legitimately omit stages it does not need (a junction with schema and config and no ui-behavior is fine); only an out-of-order stage, or a main resource missing schema or config, is a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Stages are ordered but a prerequisite edge is carried by prose rather than by prerequisiteTaskRefs, or an omitted stage on a supporting resource is unexplained.","GAP":"A config task ordered before its resource's schema task, a spec task before its ui-behavior task, or a main resource with no schema or config stage.","INDETERMINATE":"Tasks do not carry enough target and prerequisite detail to reconstruct per-resource order.","PASS":"Every resource's stages are ordered schema -> config -> ui-behavior -> spec through declared prerequisites, and every main resource has schema and config."}},{"assessesAspects":["build-plan.task","domain-plan.relationship"],"criterionRef":"application-creation:criterion/build-plan-relationship-coverage","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-relationship-coverage","requirementVersion":1}],"instruction":"Determine whether every relationship draft in the domain plan has a wiring task bound to the module-relationships skill, ordered after BOTH endpoint resources' schema tasks, and whether the wiring task is the single home of the relationship's foreign-key product. A relationship whose source or target resource is declared by no module of the domain plan is NOT this criterion's finding: no task can wire it, so it is the conception's fault and `conception-buildable` judges it. Judge the relationships whose endpoints both exist.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Every relationship is wired, but a wiring task's ordering relies on prose rather than declared prerequisites, or its cardinality intent is restated loosely.","GAP":"A relationship draft whose endpoints both exist with no wiring task, a wiring task ordered before an endpoint's schema task, or a relationship whose foreign key is also claimed by a schema task.","INDETERMINATE":"The domain plan's relationship drafts are not in evidence.","PASS":"Every relationship draft has one wiring task, ordered after both endpoints' schema tasks."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-task-well-formedness-and-products","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-task-well-formedness-and-products","requirementVersion":1}],"instruction":"Determine whether every task names exactly one real functional topic and at least one skill from the app-knowledge skill catalog, and whether every task except a COMPANION_GENERATION_STEP declares at least one product that names something composition does not already write (the fields a schema gains, the verbs a config gains, both endpoints of a relationship, the declarations a config file gains, the jobs a worker gains — not a scaffolded file or a composed package). Every product must be of the kind that names its surface: a view is a RESOURCE_COMPOSITE_VIEW / RESOURCE_CUSTOM_VIEW / RESOURCE_CHART_VIEW / APPLICATION_VIEW, a page a WEBSITE_PAGE, a worker an APPLICATION_WORKER, a provider a PROVIDER_BINDING — a non-resource surface declared under a MODULE target with a resource-shaped product, or with no product at all, is a gap. No two tasks may claim the same artifact; two tasks enriching one resource with DIFFERENT fields is correct. A cross-resource foreign key declared on a schema task's products is a gap: the relationship task is its single home.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A task's products are meaningful but thinly described, or a generation step's landed condition is stated loosely.","GAP":"An invented topic or dangling skill; a coding task with empty products; a product naming only a scaffolded artifact or a composed package; a non-resource surface (a view, a page, a worker, a provider, a config file) declared under a resource-shaped kind; two tasks claiming one artifact; or a foreign key attributed to a schema task.","INDETERMINATE":"The skill catalog or the task list is not in evidence, so bindings cannot be checked.","PASS":"Every task is bound to a real topic and skill, declares products composition does not already write, and no artifact is claimed twice."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-topic-dependency-order","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-topic-dependency-order","requirementVersion":1}],"instruction":"Determine whether tasks respect the topic dependency edges: model_domain_graph before define_interaction_semantics; an app-level shape_user_experience task (views or navigation composing several 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; and a resource's spec task after the stages it documents. A resource's OWN ui-behavior depends only on its own schema and config and MAY precede cross-resource operations — that is not a violation.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The order is right but relies on band position rather than a declared prerequisite, or an MVP-first tie-break contradicts the roadmap's phasing.","GAP":"An app-level view composing resources or operations placed before they exist, an integration task before the resources it connects, a user-experience task before that resource's schema task, or a spec task before its ui-behavior stage.","INDETERMINATE":"Topics or prerequisites are missing from the evidence, so ordering cannot be reconstructed.","PASS":"Every cross-topic dependency is honoured by declared prerequisites, and the per-resource ui-behavior exception is applied correctly."}},{"assessesAspects":["build-plan.task","domain-plan.module","domain-plan.resource","domain-plan.relationship"],"criterionRef":"application-creation:criterion/conception-buildable","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/conception-buildable","requirementVersion":1}],"instruction":"Determine whether the CONCEPTION this plan rests on can be built as declared. This criterion faults the domain plan, the capability composition or the surface plans — never the build plan. It is a GAP when (a) the domain plan declares a module, resource or relationship that no build task target can express, however it is decomposed, or (b) the computed coherence report shows a dangling reference or an 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. A domain-plan element declared in an expressible shape that the build plan simply omits is NOT this criterion: that is module-and-resource coverage, the decomposer's own fault. Name the conception element in the rationale.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A conception element is expressible only awkwardly, or the coherence report shows an unrealised item that reads as a deliberate deferral.","GAP":"The domain plan declares something no build target can express, or the coherence report shows a dangling reference or unrealised decision in the conception that the build cannot proceed past without inventing it.","INDETERMINATE":"The domain plan or the coherence report is not in evidence, so the conception cannot be read against the plan.","PASS":"Everything the conception declares has a build target, and the coherence report shows nothing in it the build would have to invent."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/build-plan-coherent","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:bottom_up.build-decompose"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-build-plan-task-graph","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/build-plan-module-and-resource-coverage"],"requirementRef":"application-creation:authority-requirement/build-plan-coherent-result","requirementVersion":1,"riskClassRef":"application-creation:risk/build-plan-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/build-plan-coherent","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/build-plan-coherent-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/build-plan-coherent","policyVersion":1},"decisionPointRef":"application-creation:decision-point/build-plan-coherent-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/build-plan-coherent-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/build-plan-coherent","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-companion-generation-interleave","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-decomposition-boundary","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-module-and-resource-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-per-resource-stage-order","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-relationship-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-task-well-formedness-and-products","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-topic-dependency-order","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/conception-buildable","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/build-plan-task-graph-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/build-plan-change","triggerRefs":["application-creation:trigger/build-plan-task-graph-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-build-plan-coherent-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/build-plan-task-well-formedness-and-products"],"hardFloorRef":"application-creation:hard-floor/build-plan-task-graph-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/build-plan-coherent-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/build-plan-coherent","definitionVersion":3,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-build-plan-coherent-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/build-plan-companion-generation-interleave","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-companion-generation-interleave","requirementVersion":1}],"instruction":"Determine whether the executable companion-owned generation steps are present and placed after the surfaces whose output they consume: i18n-labels after the resources it labels; email-templates after the surfaces it serves; database-migrations after the schema stages whose drift it migrates, and only for a PostgreSQL-backed application; logo present whenever the application has a brand brief, and unordered with respect to resource work because it consumes the brand and no code surface. Do NOT flag the absence of a seeds step: seed generation has no companion pipeline and must not be authored.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A labels or email step is ordered before some surface it consumes, a migration step is missing on a PostgreSQL-backed application, or the logo step is missing on an application with a brand brief.","GAP":"A generation step the pipeline cannot execute is authored (an unknown generationStepRef, or seeds), or a generation step declares products.","INDETERMINATE":"Whether the application has a brand brief or which store it uses is not in evidence, so the required step set cannot be decided.","PASS":"Every executable generation step the application needs is present and placed after the surfaces it consumes; logo is present when a brand exists."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-decomposition-boundary","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-decomposition-boundary","requirementVersion":1}],"instruction":"Determine whether the plan stays at DECOMPOSITION depth: tasks name what they build, their topic, their skills, their target, their products and their ordering intent, and do not specify how a task is dispatched (single-flight locking, change-set capture, git baseline, verify mechanics), do not solve multi-agent scale or interleaving concurrency, and do not author a schema, resolve a cardinality into a concrete foreign key, or generate code.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A task brief drifts toward execution detail or names a concrete field type or foreign key the coding agent should decide.","GAP":"A task that specifies dispatch mechanics, concurrency, or authors schema or code in the plan itself.","INDETERMINATE":"Task briefs are not in evidence.","PASS":"Every task describes WHAT it builds and none describes how it executes."}},{"assessesAspects":["build-plan.task","domain-plan.module","domain-plan.resource"],"criterionRef":"application-creation:criterion/build-plan-module-and-resource-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-module-and-resource-coverage","requirementVersion":1}],"instruction":"Determine whether every resource in every module's inventory (mainResources and supportingResources) of the domain plan has build tasks, and whether every task's moduleRef names a module the domain plan declares. A module whose resources have tasks but which carries no redundant scaffold task is NOT a finding: module slices are scaffolded by the foundation step. A module added after foundation with neither a foundation slice nor an ensure-module task IS a gap. The billing catalogue is covered the same way: every pricing plan the business model declares must be an APPLICATION_BILLING_PRODUCT of a BILLING_CATALOG task whose servesRefs name the plan; a declared plan with no billing product is a gap (the backend would have nothing to sell and the website would re-type its price).","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete, but a task's objective CREATES a resource the domain plan shows as already existing instead of enriching it (a no-op dispatch), or a supporting resource's coverage is thin.","GAP":"A resource with no task (the build would not produce it), or a task naming a module the domain plan does not declare (the dispatcher cannot route it).","INDETERMINATE":"The domain plan or the build plan is absent, truncated or unreadable, so coverage cannot be established.","PASS":"Every domain-plan resource has build tasks and every moduleRef resolves to a declared module."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-per-resource-stage-order","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-per-resource-stage-order","requirementVersion":1}],"instruction":"For each resource, determine whether its tasks respect the inner order schema -> config -> ui-behavior -> spec through their declared prerequisiteTaskRefs. A supporting resource may legitimately omit stages it does not need (a junction with schema and config and no ui-behavior is fine); only an out-of-order stage, or a main resource missing schema or config, is a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Stages are ordered but a prerequisite edge is carried by prose rather than by prerequisiteTaskRefs, or an omitted stage on a supporting resource is unexplained.","GAP":"A config task ordered before its resource's schema task, a spec task before its ui-behavior task, or a main resource with no schema or config stage.","INDETERMINATE":"Tasks do not carry enough target and prerequisite detail to reconstruct per-resource order.","PASS":"Every resource's stages are ordered schema -> config -> ui-behavior -> spec through declared prerequisites, and every main resource has schema and config."}},{"assessesAspects":["build-plan.task","domain-plan.relationship"],"criterionRef":"application-creation:criterion/build-plan-relationship-coverage","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-relationship-coverage","requirementVersion":1}],"instruction":"Determine whether every relationship draft in the domain plan has a wiring task bound to the module-relationships skill, ordered after BOTH endpoint resources' schema tasks, and whether the wiring task is the single home of the relationship's foreign-key product. A relationship whose source or target resource is declared by no module of the domain plan is NOT this criterion's finding: no task can wire it, so it is the conception's fault and `conception-buildable` judges it. Judge the relationships whose endpoints both exist.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Every relationship is wired, but a wiring task's ordering relies on prose rather than declared prerequisites, or its cardinality intent is restated loosely.","GAP":"A relationship draft whose endpoints both exist with no wiring task, a wiring task ordered before an endpoint's schema task, or a relationship whose foreign key is also claimed by a schema task.","INDETERMINATE":"The domain plan's relationship drafts are not in evidence.","PASS":"Every relationship draft has one wiring task, ordered after both endpoints' schema tasks."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-task-well-formedness-and-products","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-task-well-formedness-and-products","requirementVersion":1}],"instruction":"Determine whether every task names exactly one real functional topic and at least one skill from the app-knowledge skill catalog, and whether every task except a COMPANION_GENERATION_STEP declares at least one product that names something composition does not already write (the fields a schema gains, the verbs a config gains, both endpoints of a relationship, the declarations a config file gains, the jobs a worker gains — not a scaffolded file or a composed package). Every product must be of the kind that names its surface: a view is a RESOURCE_COMPOSITE_VIEW / RESOURCE_CUSTOM_VIEW / RESOURCE_CHART_VIEW / APPLICATION_VIEW, a page a WEBSITE_PAGE, a worker an APPLICATION_WORKER, a provider a PROVIDER_BINDING — a non-resource surface declared under a MODULE target with a resource-shaped product, or with no product at all, is a gap. No two tasks may claim the same artifact; two tasks enriching one resource with DIFFERENT fields is correct. A cross-resource foreign key declared on a schema task's products is a gap: the relationship task is its single home.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A task's products are meaningful but thinly described, or a generation step's landed condition is stated loosely.","GAP":"An invented topic or dangling skill; a coding task with empty products; a product naming only a scaffolded artifact or a composed package; a non-resource surface (a view, a page, a worker, a provider, a config file) declared under a resource-shaped kind; two tasks claiming one artifact; or a foreign key attributed to a schema task.","INDETERMINATE":"The skill catalog or the task list is not in evidence, so bindings cannot be checked.","PASS":"Every task is bound to a real topic and skill, declares products composition does not already write, and no artifact is claimed twice."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-topic-dependency-order","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-topic-dependency-order","requirementVersion":1}],"instruction":"Determine whether tasks respect the topic dependency edges: model_domain_graph before define_interaction_semantics; an app-level shape_user_experience task (views or navigation composing several 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; and a resource's spec task after the stages it documents. A resource's OWN ui-behavior depends only on its own schema and config and MAY precede cross-resource operations — that is not a violation.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The order is right but relies on band position rather than a declared prerequisite, or an MVP-first tie-break contradicts the roadmap's phasing.","GAP":"An app-level view composing resources or operations placed before they exist, an integration task before the resources it connects, a user-experience task before that resource's schema task, or a spec task before its ui-behavior stage.","INDETERMINATE":"Topics or prerequisites are missing from the evidence, so ordering cannot be reconstructed.","PASS":"Every cross-topic dependency is honoured by declared prerequisites, and the per-resource ui-behavior exception is applied correctly."}},{"assessesAspects":["build-plan.task","domain-plan.module","domain-plan.resource","domain-plan.relationship"],"criterionRef":"application-creation:criterion/conception-buildable","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/conception-buildable","requirementVersion":1}],"instruction":"Determine whether the CONCEPTION this plan rests on can be built as declared. This criterion faults the domain plan, the capability composition or the surface plans — never the build plan. It is a GAP when (a) the domain plan declares a module, resource or relationship that no build task target can express, however it is decomposed, or (b) the computed coherence report shows a dangling reference or an 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. A domain-plan element declared in an expressible shape that the build plan simply omits is NOT this criterion: that is module-and-resource coverage, the decomposer's own fault. Name the conception element in the rationale.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A conception element is expressible only awkwardly, or the coherence report shows an unrealised item that reads as a deliberate deferral.","GAP":"The domain plan declares something no build target can express, or the coherence report shows a dangling reference or unrealised decision in the conception that the build cannot proceed past without inventing it.","INDETERMINATE":"The domain plan or the coherence report is not in evidence, so the conception cannot be read against the plan.","PASS":"Everything the conception declares has a build target, and the coherence report shows nothing in it the build would have to invent."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/build-plan-coherent","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:bottom_up.build-decompose"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/build-plan-coherent","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-companion-generation-interleave","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-companion-generation-interleave","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-decomposition-boundary","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-decomposition-boundary","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-module-and-resource-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-module-and-resource-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-per-resource-stage-order","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-per-resource-stage-order","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-relationship-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-relationship-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-task-well-formedness-and-products","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-task-well-formedness-and-products","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-topic-dependency-order","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-topic-dependency-order","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/conception-buildable","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/conception-buildable","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"}],"schemaVersion":1}
|
|
1
|
+
{"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-build-plan-task-graph","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/build-plan-module-and-resource-coverage"],"requirementRef":"application-creation:authority-requirement/build-plan-coherent-result","requirementVersion":1,"riskClassRef":"application-creation:risk/build-plan-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/build-plan-coherent","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/build-plan-coherent-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/build-plan-coherent","policyVersion":1},"decisionPointRef":"application-creation:decision-point/build-plan-coherent-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/build-plan-coherent-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/build-plan-coherent","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-companion-generation-interleave","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-decomposition-boundary","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-experience-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-module-and-resource-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-per-resource-stage-order","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-relationship-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-task-well-formedness-and-products","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-topic-dependency-order","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/conception-buildable","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/build-plan-task-graph-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/build-plan-change","triggerRefs":["application-creation:trigger/build-plan-task-graph-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-build-plan-coherent-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/build-plan-task-well-formedness-and-products"],"hardFloorRef":"application-creation:hard-floor/build-plan-task-graph-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/build-plan-coherent-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/build-plan-coherent","definitionVersion":6,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-build-plan-coherent-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/build-plan-companion-generation-interleave","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-companion-generation-interleave","requirementVersion":1}],"instruction":"Determine whether the executable companion-owned generation steps are present and placed after the surfaces whose output they consume: i18n-labels after the resources it labels; email-templates after the surfaces it serves; database-migrations after the schema stages whose drift it migrates, and only for a PostgreSQL-backed application; logo present whenever the application has a brand brief, and unordered with respect to resource work because it consumes the brand and no code surface. 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, and seeding is an APPLICATION_DATA_SEED coding task judged under module-and-resource coverage.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A labels or email step is ordered before some surface it consumes, a migration step is missing on a PostgreSQL-backed application, or the logo step is missing on an application with a brand brief.","GAP":"A generation step the pipeline cannot execute is authored (an unknown generationStepRef, or a seeds generation step), or a generation step declares products.","INDETERMINATE":"Whether the application has a brand brief or which store it uses is not in evidence, so the required step set cannot be decided.","PASS":"Every executable generation step the application needs is present and placed after the surfaces it consumes; logo is present when a brand exists."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-decomposition-boundary","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-decomposition-boundary","requirementVersion":1}],"instruction":"Determine whether the plan stays at DECOMPOSITION depth: tasks name what they build, their topic, their skills, their target, their products and their ordering intent, and do not specify how a task is dispatched (dispatch locking and concurrency, change-set capture, git baseline, verify mechanics), do not solve multi-agent scale or interleaving concurrency, and do not author a schema, resolve a cardinality into a concrete foreign key, or generate code.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A task brief drifts toward execution detail or names a concrete field type or foreign key the coding agent should decide.","GAP":"A task that specifies dispatch mechanics, concurrency, or authors schema or code in the plan itself.","INDETERMINATE":"Task briefs are not in evidence.","PASS":"Every task describes WHAT it builds and none describes how it executes."}},{"assessesAspects":["build-plan.task","experience-plan.view","experience-plan.configuration","experience-plan.milestone","experience-plan.guidance"],"criterionRef":"application-creation:criterion/build-plan-experience-coverage","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-experience-coverage","requirementVersion":1}],"instruction":"Determine whether every surface the experience plan decides has its build task: one task per VIEW (target MODULE_FRONTEND on the view's module, a product of the view's kind carrying the plan's viewRef verbatim), one APPLICATION_FRONTEND_CONFIG task per CONFIGURATION, one APPLICATION_MILESTONE task per planned MILESTONE, and one APPLICATION_GUIDANCE task per planned piece of GUIDANCE (an onboarding document's objective naming the hostViewRef that embeds it). A view, configuration, milestone or guidance entry with no task is a gap: the application would ship without it while the plan reads complete. Never conclude the plan is absent because this criterion's own slice does not show it: the accepted application truth either renders the experience plan or says it has none. When the accepted application truth STATES that `experience-plan` has no accepted content, the decomposer has rightly emitted none of these tasks and cannot repair the absence by revising: record PASS, and begin the rationale with the words 'NO EXPERIENCE PLAN:' followed by what the application will therefore lack (its app-level views, its shell and navigation configuration, its milestones and its onboarding), so the absence is on the record instead of silent.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Every entry has a task, but a task's objective drops what the plan decided for it: a view's reusesComponentRefs, a milestone's moment, a guidance entry's gate, or an onboarding document's hostViewRef.","GAP":"A view, configuration, milestone or guidance entry the experience plan declares has no task, or a view task carries a viewRef the plan does not declare.","INDETERMINATE":"The build plan is not in evidence, or the accepted application truth neither renders the experience plan nor states that it has none. (A STATED absence is not indeterminate: it is the PASS case above, marked.)","PASS":"Every view, configuration, milestone and guidance entry of the experience plan has its task — or no experience plan is in evidence, and the rationale begins 'NO EXPERIENCE PLAN:' and names what the application will lack."}},{"assessesAspects":["build-plan.task","domain-plan.module","domain-plan.resource"],"criterionRef":"application-creation:criterion/build-plan-module-and-resource-coverage","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-module-and-resource-coverage","requirementVersion":1}],"instruction":"Determine whether every resource in every module's inventory (mainResources and supportingResources) of the domain plan has build tasks, and whether every task's moduleRef names a module the domain plan declares. A module whose resources have tasks but which carries no redundant scaffold task is NOT a finding: module slices are scaffolded by the foundation step. A module added after foundation with neither a foundation slice nor an ensure-module task IS a gap. The billing catalogue is covered the same way: every pricing plan the business model declares must be an APPLICATION_BILLING_PRODUCT of a BILLING_CATALOG task whose servesRefs name the plan; a declared plan with no billing product is a gap (the backend would have nothing to sell and the website would re-type its price). Seeding is covered the same way: a plan whose domain has main resources and no APPLICATION_DATA_SEED task of content DEMONSTRATION is a concern — the application would open empty, with nothing a creator can judge or show (#2234).","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete, but a task's objective CREATES a resource the domain plan shows as already existing instead of enriching it (a no-op dispatch), a supporting resource's coverage is thin, or no DEMONSTRATION data seed gives the main resources sample rows.","GAP":"A resource with no task (the build would not produce it), or a task naming a module the domain plan does not declare (the dispatcher cannot route it).","INDETERMINATE":"The domain plan or the build plan is absent, truncated or unreadable, so coverage cannot be established.","PASS":"Every domain-plan resource has build tasks and every moduleRef resolves to a declared module."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-per-resource-stage-order","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-per-resource-stage-order","requirementVersion":1}],"instruction":"For each resource, determine whether its tasks respect the inner order schema -> config -> ui-behavior -> spec through their declared prerequisiteTaskRefs. A supporting resource may legitimately omit stages it does not need (a junction with schema and config and no ui-behavior is fine); only an out-of-order stage, or a main resource missing schema or config, is a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Stages are ordered but a prerequisite edge is carried by prose rather than by prerequisiteTaskRefs, or an omitted stage on a supporting resource is unexplained.","GAP":"A config task ordered before its resource's schema task, a spec task before its ui-behavior task, or a main resource with no schema or config stage.","INDETERMINATE":"Tasks do not carry enough target and prerequisite detail to reconstruct per-resource order.","PASS":"Every resource's stages are ordered schema -> config -> ui-behavior -> spec through declared prerequisites, and every main resource has schema and config."}},{"assessesAspects":["build-plan.task","domain-plan.relationship"],"criterionRef":"application-creation:criterion/build-plan-relationship-coverage","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-relationship-coverage","requirementVersion":1}],"instruction":"Determine whether every relationship draft in the domain plan has a wiring task bound to the module-relationships skill, ordered after BOTH endpoint resources' schema tasks, and whether the wiring task is the single home of the relationship's foreign-key product. A relationship whose source or target resource is declared by no module of the domain plan is NOT this criterion's finding: no task can wire it, so it is the conception's fault and `conception-buildable` judges it. Judge the relationships whose endpoints both exist.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Every relationship is wired, but a wiring task's ordering relies on prose rather than declared prerequisites, or its cardinality intent is restated loosely.","GAP":"A relationship draft whose endpoints both exist with no wiring task, a wiring task ordered before an endpoint's schema task, or a relationship whose foreign key is also claimed by a schema task.","INDETERMINATE":"The domain plan's relationship drafts are not in evidence.","PASS":"Every relationship draft has one wiring task, ordered after both endpoints' schema tasks."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-task-well-formedness-and-products","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-task-well-formedness-and-products","requirementVersion":1}],"instruction":"Determine whether every task names exactly one real functional topic and at least one skill from the app-knowledge skill catalog, and whether every task except a COMPANION_GENERATION_STEP declares at least one product that names something composition does not already write (the fields a schema gains, the verbs a config gains, both endpoints of a relationship, the declarations a config file gains, the jobs a worker gains — not a scaffolded file or a composed package). Every product must be of the kind that names its surface: a view is a RESOURCE_COMPOSITE_VIEW / RESOURCE_CUSTOM_VIEW / RESOURCE_CHART_VIEW / APPLICATION_VIEW, a page a WEBSITE_PAGE, a worker an APPLICATION_WORKER, a provider a PROVIDER_BINDING — a non-resource surface declared under a MODULE target with a resource-shaped product, or with no product at all, is a gap. No two tasks may claim the same artifact; two tasks enriching one resource with DIFFERENT fields is correct. A cross-resource foreign key declared on a schema task's products is a gap: the relationship task is its single home.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A task's products are meaningful but thinly described, or a generation step's landed condition is stated loosely.","GAP":"An invented topic or dangling skill; a coding task with empty products; a product naming only a scaffolded artifact or a composed package; a non-resource surface (a view, a page, a worker, a provider, a config file) declared under a resource-shaped kind; two tasks claiming one artifact; or a foreign key attributed to a schema task.","INDETERMINATE":"The skill catalog or the task list is not in evidence, so bindings cannot be checked.","PASS":"Every task is bound to a real topic and skill, declares products composition does not already write, and no artifact is claimed twice."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-topic-dependency-order","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-topic-dependency-order","requirementVersion":1}],"instruction":"Determine whether tasks respect the topic dependency edges: model_domain_graph before define_interaction_semantics; an app-level shape_user_experience task (views or navigation composing several 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; and a resource's spec task after the stages it documents. A resource's OWN ui-behavior depends only on its own schema and config and MAY precede cross-resource operations — that is not a violation.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The order is right but relies on band position rather than a declared prerequisite, or an MVP-first tie-break contradicts the roadmap's phasing.","GAP":"An app-level view composing resources or operations placed before they exist, an integration task before the resources it connects, a user-experience task before that resource's schema task, or a spec task before its ui-behavior stage.","INDETERMINATE":"Topics or prerequisites are missing from the evidence, so ordering cannot be reconstructed.","PASS":"Every cross-topic dependency is honoured by declared prerequisites, and the per-resource ui-behavior exception is applied correctly."}},{"assessesAspects":["build-plan.task","domain-plan.module","domain-plan.resource","domain-plan.relationship"],"criterionRef":"application-creation:criterion/conception-buildable","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/conception-buildable","requirementVersion":1}],"instruction":"Determine whether the CONCEPTION this plan rests on can be built as declared. This criterion faults the domain plan, the capability composition or the surface plans — never the build plan. It is a GAP when (a) the domain plan declares a module, resource or relationship that no build task target can express, however it is decomposed, or (b) the computed coherence report shows a dangling reference or an 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. A domain-plan element declared in an expressible shape that the build plan simply omits is NOT this criterion: that is module-and-resource coverage, the decomposer's own fault. Name the conception element in the rationale.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A conception element is expressible only awkwardly, or the coherence report shows an unrealised item that reads as a deliberate deferral.","GAP":"The domain plan declares something no build target can express, or the coherence report shows a dangling reference or unrealised decision in the conception that the build cannot proceed past without inventing it.","INDETERMINATE":"The domain plan or the coherence report is not in evidence, so the conception cannot be read against the plan.","PASS":"Everything the conception declares has a build target, and the coherence report shows nothing in it the build would have to invent."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/build-plan-coherent","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:bottom_up.build-decompose"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/build-plan-coherent","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-companion-generation-interleave","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-companion-generation-interleave","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-decomposition-boundary","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-decomposition-boundary","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-experience-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":1,"requirementRef":"application-creation:evidence-requirement/build-plan-experience-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-module-and-resource-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-module-and-resource-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-per-resource-stage-order","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-per-resource-stage-order","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-relationship-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-relationship-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-task-well-formedness-and-products","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-task-well-formedness-and-products","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-topic-dependency-order","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-topic-dependency-order","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/conception-buildable","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/conception-buildable","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"}],"schemaVersion":1}
|