@wildo-ai/framework-knowledge 1.1.8 → 1.1.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +9 -2
- package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +21 -0
- package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +121 -0
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +29 -5
- package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +29 -2
- package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +69 -24
- package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +10 -0
- package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +21 -5
- package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +31 -5
- package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +2 -0
- package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +11 -1
- package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +11 -1
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +2 -2
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +11 -11
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +29 -22
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +3 -3
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +59 -10
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +3 -3
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +5 -5
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +8 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +12 -4
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +25 -27
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +85 -43
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +40 -0
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +41 -0
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +199 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +201 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +67 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +76 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +3 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +27 -18
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +11 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +11 -11
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +2 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +3 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +2 -0
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +3 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +5 -2
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -4
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +7 -3
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +36 -2
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +7 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +4 -2
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +9 -3
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +3 -3
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +35 -2
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +30 -17
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
- package/dist/knowledge/manifest.json +8 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +22 -7
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
- package/dist/knowledge/playbooks/bottom_up.build/method.md +17 -15
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +4 -3
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +117 -28
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +4 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +133 -59
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +169 -276
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -2
- package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +8 -1
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.conception/method.md +3 -2
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +2 -2
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +22 -6
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +4 -3
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +13 -5
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +5 -2
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +71 -37
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +35 -38
- package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +105 -0
- package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +55 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +78 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +63 -0
- package/dist/knowledge/playbooks/top_down.brand-naming/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +65 -0
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/method.md +60 -6
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +15 -10
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +30 -10
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +3 -1
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +4 -1
- package/dist/knowledge/playbooks/top_down.definition/method.md +8 -3
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +6 -4
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +11 -1
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +21 -0
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +8 -2
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +4 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +10 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +40 -17
- package/dist/knowledge/references/brand.name-choice.config.md +127 -0
- package/dist/knowledge/references/brand.name-screening.config.md +253 -0
- package/dist/knowledge/references/build-plan.task-graph.config.md +64 -11
- package/dist/knowledge/references/business-model.pricing-plan.config.md +16 -0
- package/dist/knowledge/references/business-model.snapshot.config.md +64 -0
- package/dist/knowledge/references/business-model.snapshot.validation.md +68 -4
- package/dist/knowledge/references/capability-composition.config.md +67 -4
- package/dist/knowledge/references/example.data-seeding.minimal.md +29 -1
- package/dist/knowledge/references/market.snapshot.validation.md +1 -1
- package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +7 -1
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +6 -0
- package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +81 -2
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +10 -0
- package/dist/knowledge/references/saas.website.astro.label-loader.md +9 -0
- package/dist/knowledge/references/saas.website.factories.define-section.md +4 -0
- package/dist/knowledge/references/saas.website.page-manifest.schema.md +12 -3
- package/dist/knowledge/references/saas.website.page-sections.component.md +72 -0
- package/dist/knowledge/references/saas.website.sections.definition-schema.md +11 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +38 -1
- package/dist/knowledge/registries/playbooks.json +68 -20
- package/dist/knowledge/registries/source-tags.json +748 -695
- package/dist/knowledge/rules/live-context-door.md +5 -2
- package/dist/knowledge/skills/INDEX.md +2 -1
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +1 -1
- package/dist/knowledge/skills/brand-name-screening/SKILL.md +154 -0
- package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +394 -0
- package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +65 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +5 -2
- package/dist/knowledge/skills/config-saas/SKILL.md +31 -4
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +14 -1
- package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +81 -2
- package/dist/knowledge/skills/email-add-template/SKILL.md +1 -1
- package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +1 -1
- package/dist/knowledge/skills/inbound-channels/SKILL.md +2 -2
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +11 -1
- package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +122 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +11 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +9 -2
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +11 -1
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +11 -1
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +1 -1
- package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +1 -1
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +10 -0
- package/dist/knowledge/skills/module-relationships/SKILL.md +6 -4
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +51 -3
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +6 -0
- package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +7 -1
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +10 -0
- package/dist/knowledge/skills/website-factory-advanced/SKILL.md +4 -0
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +84 -3
- package/dist/knowledge/skills/website-section-contact/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-cta/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-faq/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-hero/SKILL.md +27 -9
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +1 -1
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +11 -0
- package/dist/knowledge/topic-index.json +169 -43
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
|
@@ -1,16 +1,16 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "playbooks",
|
|
3
3
|
"metadata": {
|
|
4
|
-
"generatedAt": "2026-
|
|
4
|
+
"generatedAt": "2026-10-03T03:06:36.431Z",
|
|
5
5
|
"description": "Compiled meta-workflow playbooks (app-creation methodology definitions)."
|
|
6
6
|
},
|
|
7
7
|
"entries": {
|
|
8
8
|
"bottom_up.assemble-verify": {
|
|
9
9
|
"ref": "bottom_up.assemble-verify",
|
|
10
|
-
"version": "0.
|
|
10
|
+
"version": "0.4.0",
|
|
11
11
|
"phase": "bottom_up",
|
|
12
12
|
"executor": "deterministic_cli",
|
|
13
|
-
"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
|
|
13
|
+
"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.",
|
|
14
14
|
"skillRefs": [
|
|
15
15
|
"application-database-migrations"
|
|
16
16
|
],
|
|
@@ -22,7 +22,7 @@
|
|
|
22
22
|
"ref": "bottom_up.build",
|
|
23
23
|
"version": "0.1.0",
|
|
24
24
|
"phase": "bottom_up",
|
|
25
|
-
"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
|
|
25
|
+
"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.",
|
|
26
26
|
"skillRefs": [],
|
|
27
27
|
"playbookFilePath": "playbooks/bottom_up.build/playbook.json",
|
|
28
28
|
"methodFilePath": "playbooks/bottom_up.build/method.md",
|
|
@@ -30,10 +30,10 @@
|
|
|
30
30
|
},
|
|
31
31
|
"bottom_up.build-decompose": {
|
|
32
32
|
"ref": "bottom_up.build-decompose",
|
|
33
|
-
"version": "0.4.
|
|
33
|
+
"version": "0.4.1",
|
|
34
34
|
"phase": "bottom_up",
|
|
35
35
|
"executor": "companion_agent",
|
|
36
|
-
"intent": "Bottom-up build decomposition — the FIRST build-execution playbook, the pivot from planning the domain (the domain-plan) to decomposing the BUILD. Reads the approved domain-plan (the ModuleBusinessSemantics module drafts + per-module resource inventory), the relationship drafts inside it (the inter-resource relationship intents), and the definition set (roadmap for phasing, requirements + feature-drafts for task-brief context), and the PLACEMENT PLAN (where each settings destination, resource operation and view sits in the shell, decided upstream), and DECOMPOSES the build work into an ordered set of coding-agent tasks. Each task is bound onto (a) the 7-topic functional taxonomy (configure_application_foundation -> model_domain_graph -> define_interaction_semantics -> shape_user_experience -> extend_application -> connect_runtime_and_external_capabilities -> assemble_verify_and_iterate) and (b) the app-knowledge skill catalog (each task names the skill(s) that carry its technical HOW). The tasks follow the per-resource inner order (schema -> config -> ui-behavior -> spec, then operations / interaction semantics, then UX, then extensions, then integrations), with companion-owned generation steps (i18n-labels, email-templates, logo, and database-migrations for applications with an accepted PostgreSQL schema plan) interleaved at the points their inputs exist. This playbook PRODUCES the ordered task graph (a build-plan artifact); it does NOT dispatch tasks to coding agents (that is the dispatch-orchestration playbook downstream), does NOT capture change-sets /
|
|
36
|
+
"intent": "Bottom-up build decomposition — the FIRST build-execution playbook, the pivot from planning the domain (the domain-plan) to decomposing the BUILD. Reads the approved domain-plan (the ModuleBusinessSemantics module drafts + per-module resource inventory), the relationship drafts inside it (the inter-resource relationship intents), and the definition set (roadmap for phasing, requirements + feature-drafts for task-brief context), and the PLACEMENT PLAN (where each settings destination, resource operation and view sits in the shell, decided upstream), and DECOMPOSES the build work into an ordered set of coding-agent tasks. Each task is bound onto (a) the 7-topic functional taxonomy (configure_application_foundation -> model_domain_graph -> define_interaction_semantics -> shape_user_experience -> extend_application -> connect_runtime_and_external_capabilities -> assemble_verify_and_iterate) and (b) the app-knowledge skill catalog (each task names the skill(s) that carry its technical HOW). The tasks follow the per-resource inner order (schema -> config -> ui-behavior -> spec, then operations / interaction semantics, then UX, then extensions, then integrations), with companion-owned generation steps (i18n-labels, email-templates, logo, and database-migrations for applications with an accepted PostgreSQL schema plan) interleaved at the points their inputs exist. This playbook PRODUCES the ordered task graph (a build-plan artifact); it does NOT dispatch tasks to coding agents (that is the dispatch-orchestration playbook downstream), does NOT capture change-sets / lock or schedule runs / verify, and does NOT solve multi-agent scale or interleaving. It authors no schemas and generates no code. The typed BuildPlanTaskGraph contract and deterministic validator already exist. Declare prerequisiteTaskRefs explicitly: the host derives readiness from those edges; functionalTopic provides context and skill routing, not an implicit execution order.",
|
|
37
37
|
"skillRefs": [
|
|
38
38
|
"resource-add-module",
|
|
39
39
|
"resource-add-resource",
|
|
@@ -56,7 +56,7 @@
|
|
|
56
56
|
},
|
|
57
57
|
"evaluationTreatment": {
|
|
58
58
|
"definitionRef": "application-creation:evaluation-treatment/build-plan-coherent",
|
|
59
|
-
"definitionVersion":
|
|
59
|
+
"definitionVersion": 6,
|
|
60
60
|
"filePath": "playbooks/bottom_up.build-decompose/evaluation-treatment.json"
|
|
61
61
|
}
|
|
62
62
|
},
|
|
@@ -65,7 +65,7 @@
|
|
|
65
65
|
"version": "0.1.0",
|
|
66
66
|
"phase": "bottom_up",
|
|
67
67
|
"executor": "coding_agent",
|
|
68
|
-
"intent": "Bottom-up build dispatch — the SECOND build-execution playbook, the pivot from DECOMPOSING the build (the build-plan task graph) to DISPATCHING it: turning one ordered task into an actually-run, verified coding-agent run under the D4 dispatch contract. Reads the approved TYPED build-plan (`BuildPlanTaskGraph` — each task carries a closed target kind, ONE MetaWorkflow_FunctionalTopic, its skill refs, and DECLARED prerequisite task refs) and the current journey state, selects the
|
|
68
|
+
"intent": "Bottom-up build dispatch — the SECOND build-execution playbook, the pivot from DECOMPOSING the build (the build-plan task graph) to DISPATCHING it: turning one ordered task into an actually-run, verified coding-agent run under the D4 dispatch contract. Reads the approved TYPED build-plan (`BuildPlanTaskGraph` — each task carries a closed target kind, ONE MetaWorkflow_FunctionalTopic, its skill refs, and DECLARED prerequisite task refs) and the current journey state, selects the READY tasks (`selectReadyBuildPlanTasks`: every declared prerequisite has landed — resolved by the host, never inferred from prose) and dispatches them as a WAVE: up to the application's build parallelism at once (`wildo workbench parallelism`, 5 by default; 1 = one workspace-mutating run at a time), in ONE shared worktree, each slot refilled as its run settles. Each task in the wave runs the same typed contract: (1) the runner builds the context pack (task brief + the task's skill pointers + the relevant journey/definition artifacts + introspected app reality + repo paths); (2) it runs ONE prompt turn against the coding agent over the Agent Client Protocol, in a session rooted at the app workspace (cwd = app root, so CLAUDE.md / .claude skills load naturally), answering the agent's permission requests within the execution profile's declared ceiling and refusing anything above it or outside the task's mutation scope; (3) it captures the change-set around the run (git baseline/post-run worktree snapshots → per-file attribution → a structured GitChangeSetCapture recorded on the task row); (4) it runs the VERIFY gate OUTSIDE the coding agent (a deterministic typecheck the runner maps onto the dispatch verification hook — pnpm exec tsc --noEmit — the trust-but-verify floor); (5) it records the result + applies the onFailure disposition (keep_and_flag: a failed/timed-out run keeps its captured change-set flagged for human triage, never a silent half-applied state). When the wave's runs have settled, the runner commits what their own accepts left as one change naming every run it carries, and re-runs ALONE each task whose finished product a sibling overwrote; each run's record names what overlapped it (`concurrency`, `interferenceSuspected`). One run of this playbook is one bounded wave; run it again for the next. This playbook PRODUCES the per-task dispatch contract + execution semantics; it authors no schemas and generates no code (the coding agent does that at dispatch time). It does NOT decompose the plan (that is the build-decompose playbook, upstream — it owns the task graph) and does NOT choose the wave's width (the build parallelism is the person's setting). A revert_changeset failure path is a later phase (revert is a MUTATING git op outside the read-only change-set carve-out, deliberately deferred).",
|
|
69
69
|
"skillRefs": [],
|
|
70
70
|
"playbookFilePath": "playbooks/bottom_up.build-dispatch/playbook.json",
|
|
71
71
|
"methodFilePath": "playbooks/bottom_up.build-dispatch/method.md",
|
|
@@ -86,7 +86,7 @@
|
|
|
86
86
|
"version": "0.1.0",
|
|
87
87
|
"phase": "bottom_up",
|
|
88
88
|
"executor": "coding_agent",
|
|
89
|
-
"intent": "Bottom-up build scale — the THIRD
|
|
89
|
+
"intent": "Bottom-up build scale — the THIRD build-execution playbook: how the build runs at SCALE, as shipped. A run of a build-execution playbook starts a WAVE: up to the application's build parallelism of build-plan tasks at once (`wildo workbench parallelism`, 5 by default; 1 = one task at a time, the single-flight mode), in ONE shared worktree, as a rolling pool that refills each slot with whatever is ready when a run settles. This playbook declares the same CODING_AGENT executor as the build-dispatch playbook and runs through the same runtime branch, so both start the SAME wave; prefer build-dispatch to start a build, and read this one for the scale questions: (1) the ready-SET — tasks whose declared prerequisites have ALL SUCCEEDED, not merely been attempted, resolved by the host from the declared refs and git; (2) the width — the build parallelism, the person's setting, never chosen by the method; (3) the isolation model — none by decision: the runs share the worktree, only a task being built twice at once is prevented, and overlap is RECORDED on each run (`concurrency`, `interferenceSuspected`); (4) the deterministic companion-owned generation steps (labels / i18n, email templates, seeds) — run through their companion endpoints at their input-ready point, inline while live coding runs continue, at most once per wave; (5) the wave's end — bounded at four dispatches per slot per call, it drains its live runs, commits what their own accepts left as ONE change naming every run it carries, re-runs ALONE each completed task whose product a sibling overwrote, and applies keep_and_flag across siblings + dependents. Each slot runs the per-task dispatch contract of the build-dispatch playbook; this playbook does NOT re-specify it, does NOT re-decompose the plan (the build-decompose playbook owns the task graph), and authors no schemas / no code. A priority / work-stealing scheduler, cost-optimal packing and a revert_changeset failure path are later phases.",
|
|
90
90
|
"skillRefs": [],
|
|
91
91
|
"playbookFilePath": "playbooks/bottom_up.build-scale/playbook.json",
|
|
92
92
|
"methodFilePath": "playbooks/bottom_up.build-scale/method.md",
|
|
@@ -108,7 +108,7 @@
|
|
|
108
108
|
"ref": "bottom_up.conception",
|
|
109
109
|
"version": "0.1.2",
|
|
110
110
|
"phase": "bottom_up",
|
|
111
|
-
"intent": "Drive the CONCEPTION of the application as one lane: the domain plan from the requirements and the market, the expert personas that staff the panels, the capability composition the application needs, the foundation composed from the plan and that composition, the surface plans for whatever the composition says this application presents — its experience, its website, its documentation — and the placement plan the panel decides — ending on one decision: the conception is accepted, or returned to the domain plan. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round. Select what is MISSING from the accepted truth shown to you
|
|
111
|
+
"intent": "Drive the CONCEPTION of the application as one lane: the domain plan from the requirements and the market, the expert personas that staff the panels, the capability composition the application needs, the foundation composed from the plan and that composition, the surface plans for whatever the composition says this application presents — its experience, its website, its documentation — and the placement plan the panel decides — ending on one decision: the conception is accepted, or returned to the domain plan. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round. Select what is MISSING from the accepted truth shown to you. A child already on record whose inputs have not changed since it landed is not offered at all; every option is marked FIRST RUN, or REFRESH with the input that moved. The foundation and the expert personas are runner-owned steps that land no family: run each ONCE, when its inputs are on record, and do not spend a round on either again — the round history shows they ran. Run independent children in the same round. STOP when the placement plan is on record AND every surface the capability composition decided NEEDED (a website, a documentation portal) has its plan on record: the placement plan is this lane's closing decision, but it needs only the domain plan, so it can land before a surface plan — and a surface decided and never planned is one the build decomposition emits no task for. A child whose interview the creator has not answered, or whose run suspended on a clarification, is not offered; run everything else and stop when nothing eligible advances the conception.",
|
|
112
112
|
"skillRefs": [],
|
|
113
113
|
"playbookFilePath": "playbooks/bottom_up.conception/playbook.json",
|
|
114
114
|
"methodFilePath": "playbooks/bottom_up.conception/method.md",
|
|
@@ -131,7 +131,7 @@
|
|
|
131
131
|
},
|
|
132
132
|
"bottom_up.domain-plan": {
|
|
133
133
|
"ref": "bottom_up.domain-plan",
|
|
134
|
-
"version": "0.
|
|
134
|
+
"version": "0.3.0",
|
|
135
135
|
"phase": "bottom_up",
|
|
136
136
|
"executor": "companion_agent",
|
|
137
137
|
"intent": "Turn the approved definition set into one atomic, planning-depth domain output set: module decomposition with per-module resource inventory plus typed inter-resource relationship intents. The output remains staged until deterministic validation, semantic evaluation and distinct result authority complete.",
|
|
@@ -383,10 +383,10 @@
|
|
|
383
383
|
},
|
|
384
384
|
"top_down.brand-identity": {
|
|
385
385
|
"ref": "top_down.brand-identity",
|
|
386
|
-
"version": "0.
|
|
386
|
+
"version": "0.3.0",
|
|
387
387
|
"phase": "top_down",
|
|
388
388
|
"executor": "companion_agent",
|
|
389
|
-
"intent": "Brand-identity elicitation: draw the product's VISUAL identity out of the creator — the brand name, the logo creative direction (mark type, motifs, symbolism, imagery don'ts, background), and the visual tone (style keywords, mood, color story) — and capture it as a single validated BrandSnapshot (the `brand-brief` artifact family). The visual counterpart to the vision (intent) and market (verbal voice) briefs: it derives symbolism from the VisionSnapshot's idea/mission and, when a MarketSnapshot exists, translates its verbal `tonesOfVoice` into a visual register. The emitted brand-brief is the INPUT the companion logo step generates the master logo + derived assets from, and via `BrandSnapshot.resolvedAssets` the single source of truth every logo/favicon/brand-image consumer resolves against. Progressive: may persist a partially-directed brand (logoDirection/visualTone optional) and resume. v1 scaffold methodology — iterate the interview.",
|
|
389
|
+
"intent": "Brand-identity elicitation: draw the product's VISUAL identity out of the creator — the brand name (CHOSEN by the creator from the screened candidates `top_down.brand-naming` landed), the logo creative direction (mark type, motifs, symbolism, imagery don'ts, background), and the visual tone (style keywords, mood, color story) — and capture it as a single validated BrandSnapshot (the `brand-brief` artifact family). The visual counterpart to the vision (intent) and market (verbal voice) briefs: it derives symbolism from the VisionSnapshot's idea/mission and, when a MarketSnapshot exists, translates its verbal `tonesOfVoice` into a visual register. The emitted brand-brief is the INPUT the companion logo step generates the master logo + derived assets from, and via `BrandSnapshot.resolvedAssets` the single source of truth every logo/favicon/brand-image consumer resolves against. Progressive: may persist a partially-directed brand (logoDirection/visualTone optional) and resume. v1 scaffold methodology — iterate the interview.",
|
|
390
390
|
"skillRefs": [
|
|
391
391
|
"brand-logo-authoring"
|
|
392
392
|
],
|
|
@@ -404,12 +404,60 @@
|
|
|
404
404
|
"filePath": "playbooks/top_down.brand-identity/evaluation-treatment.json"
|
|
405
405
|
}
|
|
406
406
|
},
|
|
407
|
+
"top_down.brand-name-research": {
|
|
408
|
+
"ref": "top_down.brand-name-research",
|
|
409
|
+
"version": "0.1.0",
|
|
410
|
+
"phase": "top_down",
|
|
411
|
+
"executor": "research_agent",
|
|
412
|
+
"intent": "Propose candidate names for the product, grounded in the vision and the market snapshot, and run a minimal trademark screening of every candidate — proposed or supplied by the creator — against the public registers of the jurisdictions the product targets, in the Nice classes it lives in, for identical and near-identical live marks, with domain and same-category signals beside them. Returns a condensed, source-attributed brief and authors nothing. Never a legal clearance opinion: a register it could not query is reported as not checked, never as clear.",
|
|
413
|
+
"skillRefs": [
|
|
414
|
+
"brand-name-screening"
|
|
415
|
+
],
|
|
416
|
+
"playbookFilePath": "playbooks/top_down.brand-name-research/playbook.json",
|
|
417
|
+
"methodFilePath": "playbooks/top_down.brand-name-research/method.md",
|
|
418
|
+
"sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1"
|
|
419
|
+
},
|
|
420
|
+
"top_down.brand-name-screening-produce": {
|
|
421
|
+
"ref": "top_down.brand-name-screening-produce",
|
|
422
|
+
"version": "0.1.0",
|
|
423
|
+
"phase": "top_down",
|
|
424
|
+
"executor": "companion_agent",
|
|
425
|
+
"intent": "Derive the validated brand-name screening from the vision, the market snapshot and the evidence a sibling research step gathered: the jurisdictions and Nice classes searched, and per candidate its origin, why it fits, every register query with its result, conflicting marks, source and date, the competitor collisions, and the domain and same-category signals. Transcribes, never concludes: a candidate's standing is derived from its queries. A minimal trademark screening, never a legal clearance opinion.",
|
|
426
|
+
"skillRefs": [
|
|
427
|
+
"brand-name-screening"
|
|
428
|
+
],
|
|
429
|
+
"playbookFilePath": "playbooks/top_down.brand-name-screening-produce/playbook.json",
|
|
430
|
+
"methodFilePath": "playbooks/top_down.brand-name-screening-produce/method.md",
|
|
431
|
+
"sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1",
|
|
432
|
+
"evaluationProtocol": {
|
|
433
|
+
"protocolRef": "application-creation:evaluation-protocol/brand-name-screening",
|
|
434
|
+
"protocolVersion": 1,
|
|
435
|
+
"filePath": "playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json"
|
|
436
|
+
},
|
|
437
|
+
"evaluationTreatment": {
|
|
438
|
+
"definitionRef": "application-creation:evaluation-treatment/brand-name-screening",
|
|
439
|
+
"definitionVersion": 1,
|
|
440
|
+
"filePath": "playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json"
|
|
441
|
+
}
|
|
442
|
+
},
|
|
443
|
+
"top_down.brand-naming": {
|
|
444
|
+
"ref": "top_down.brand-naming",
|
|
445
|
+
"version": "0.1.0",
|
|
446
|
+
"phase": "top_down",
|
|
447
|
+
"intent": "Propose names for the product and screen each against the public trademark registers of the jurisdictions it targets, landing the brand-name screening the brand-identity interview offers the creator a choice from. An umbrella: it authors nothing itself — research proposes and screens with web access, a sibling lands the validated screening. The companion proposes; the creator chooses. A minimal trademark screening, never a legal clearance opinion.",
|
|
448
|
+
"skillRefs": [
|
|
449
|
+
"brand-name-screening"
|
|
450
|
+
],
|
|
451
|
+
"playbookFilePath": "playbooks/top_down.brand-naming/playbook.json",
|
|
452
|
+
"methodFilePath": "playbooks/top_down.brand-naming/method.md",
|
|
453
|
+
"sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1"
|
|
454
|
+
},
|
|
407
455
|
"top_down.business-model": {
|
|
408
456
|
"ref": "top_down.business-model",
|
|
409
|
-
"version": "0.
|
|
457
|
+
"version": "0.2.0",
|
|
410
458
|
"phase": "top_down",
|
|
411
459
|
"executor": "companion_agent",
|
|
412
|
-
"intent": "Turn the accepted market and requirements truth, plus the creator's own pricing intent, into a non-vacuous BusinessModelLiteSnapshot: the product-level revenue model and a sketch of pricing plans, each cross-linked to the market ICPs it is sold to and the requirements it unlocks. A PLANNING artifact carrying commercial INTENT — never the billing runtime, and never a price the creator did not state.",
|
|
460
|
+
"intent": "Turn the accepted market and requirements truth, plus the creator's own pricing intent, into a non-vacuous BusinessModelLiteSnapshot: the product-level revenue model, where its pricing tiers came from (stated by the creator, proposed at the creator's request, or not decided yet), and a sketch of pricing plans, each cross-linked to the market ICPs it is sold to and the requirements it unlocks. A PLANNING artifact carrying commercial INTENT — never the billing runtime, and never a price the creator did not state.",
|
|
413
461
|
"skillRefs": [],
|
|
414
462
|
"playbookFilePath": "playbooks/top_down.business-model/playbook.json",
|
|
415
463
|
"methodFilePath": "playbooks/top_down.business-model/method.md",
|
|
@@ -421,7 +469,7 @@
|
|
|
421
469
|
},
|
|
422
470
|
"evaluationTreatment": {
|
|
423
471
|
"definitionRef": "application-creation:evaluation-treatment/business-model",
|
|
424
|
-
"definitionVersion":
|
|
472
|
+
"definitionVersion": 2,
|
|
425
473
|
"filePath": "playbooks/top_down.business-model/evaluation-treatment.json"
|
|
426
474
|
},
|
|
427
475
|
"structuredArtifactAction": {
|
|
@@ -537,9 +585,9 @@
|
|
|
537
585
|
},
|
|
538
586
|
"top_down.definition": {
|
|
539
587
|
"ref": "top_down.definition",
|
|
540
|
-
"version": "0.1.
|
|
588
|
+
"version": "0.1.1",
|
|
541
589
|
"phase": "top_down",
|
|
542
|
-
"intent": "Drive the top-down DEFINITION of the application as one lane: from an answered vision through market evidence, the market snapshot, the value proposition, the requirements, the capability map, the business model and the roadmap, to the phase gate — with the brand identity and the risk register beside the chain. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round, so the order is the leaves' preconditions and never a list. Select what is MISSING from the accepted truth shown to you
|
|
590
|
+
"intent": "Drive the top-down DEFINITION of the application as one lane: from an answered vision through market evidence, the market snapshot, the value proposition, the requirements, the capability map, the business model and the roadmap, to the phase gate — with the brand naming (screened name proposals), the brand identity and the risk register beside the chain. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round, so the order is the leaves' preconditions and never a list. Select what is MISSING from the accepted truth shown to you. A child already on record whose inputs have not changed since it landed is not offered at all; every option is marked FIRST RUN, or REFRESH with the input that moved. Prefer first runs; take a refresh when its changed input matters to it. Run independent children in the same round (brand naming or the brand identity, and the risk register beside the chain; several research lanes with different objectives). Run the phase gate once the roadmap is on record, and STOP after it has run — its verdict is this lane's closing decision, and it is not re-run in the same run. A child whose interview the creator has not answered is not offered; run everything else and stop when nothing eligible advances the definition.",
|
|
543
591
|
"skillRefs": [],
|
|
544
592
|
"playbookFilePath": "playbooks/top_down.definition/playbook.json",
|
|
545
593
|
"methodFilePath": "playbooks/top_down.definition/method.md",
|
|
@@ -652,7 +700,7 @@
|
|
|
652
700
|
},
|
|
653
701
|
"top_down.phase-gate": {
|
|
654
702
|
"ref": "top_down.phase-gate",
|
|
655
|
-
"version": "0.2.
|
|
703
|
+
"version": "0.2.1",
|
|
656
704
|
"phase": "top_down",
|
|
657
705
|
"executor": "companion_agent",
|
|
658
706
|
"intent": "Assess whether the validated top-down definition set is cross-artifact coherent enough for the current horizon. Deterministic family validation remains a non-bypassable eligibility floor; this playbook contributes an advisory semantic evaluation and never mutates application truth.",
|
|
@@ -699,7 +747,7 @@
|
|
|
699
747
|
},
|
|
700
748
|
"top_down.risk-register": {
|
|
701
749
|
"ref": "top_down.risk-register",
|
|
702
|
-
"version": "0.1.
|
|
750
|
+
"version": "0.1.2",
|
|
703
751
|
"phase": "top_down",
|
|
704
752
|
"executor": "companion_agent",
|
|
705
753
|
"intent": "Complete this application's risk register: turn each DERIVED risk signal into a statement about what the exposure means for THIS product and these users, weight it qualitatively against what is actually implemented, and propose the business risks no derivation reaches. The signals say what is present; this says what it means. A model proposes and a human accepts — the accepted register is the committed file, so this playbook never decides anything, it drafts. Runtime evidence, control-objective binding and audit depth belong to their own mechanisms; this produces the register they read.",
|