@wildo-ai/framework-knowledge 1.1.1 → 1.1.3

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.
Files changed (223) hide show
  1. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  2. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  3. package/dist/esm/framework-knowledge.definitions.js +271 -8
  4. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  5. package/dist/esm/framework-knowledge.loader.d.ts +19 -0
  6. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  7. package/dist/esm/framework-knowledge.loader.js +32 -0
  8. package/dist/esm/framework-knowledge.loader.js.map +1 -1
  9. package/dist/esm/framework-knowledge.schemas.d.ts +13 -2
  10. package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
  11. package/dist/esm/framework-knowledge.schemas.js.map +1 -1
  12. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +45 -0
  13. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -0
  14. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +55 -0
  15. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -0
  16. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +6 -7
  17. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  18. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +6 -6
  19. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  20. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +0 -4
  21. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +0 -2
  23. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +0 -4
  25. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +0 -2
  27. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +3 -9
  29. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +1 -3
  31. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  32. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +10 -6
  33. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +25 -4
  35. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  36. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -5
  37. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -3
  39. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +4 -2
  41. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  42. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +4 -2
  43. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  44. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -2
  45. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -14
  47. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  48. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +3 -5
  49. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  50. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +3 -4
  51. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  52. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +2 -8
  53. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  54. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +0 -2
  55. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  56. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +2 -8
  57. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  58. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +0 -2
  59. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  60. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +52 -0
  61. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -0
  62. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +127 -0
  63. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -0
  64. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +75 -0
  65. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -0
  66. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +91 -0
  67. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -0
  68. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +29 -0
  69. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -0
  70. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +28 -0
  71. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -0
  72. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +9 -45
  73. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  74. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +4 -54
  75. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  76. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +30 -0
  77. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -0
  78. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +25 -0
  79. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -0
  80. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -9
  81. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  82. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +9 -5
  83. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  84. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +0 -1
  85. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  86. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +0 -1
  87. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  88. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +0 -1
  89. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  90. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +0 -1
  91. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  92. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +0 -9
  93. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  94. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -2
  95. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  96. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +2 -8
  97. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  98. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +0 -2
  99. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  100. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -8
  101. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  102. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +0 -2
  103. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  104. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +2 -8
  105. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  106. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +5 -4
  107. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  108. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +0 -4
  109. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  110. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -2
  111. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  112. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +4 -6
  113. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  114. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +25 -5
  115. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  116. package/dist/knowledge/manifest.json +6 -7
  117. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +7 -47
  118. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +6 -13
  119. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +1 -82
  120. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +11 -6
  121. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -5
  122. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +3 -4
  123. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +3 -4
  124. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +15 -735
  125. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +11 -7
  126. package/dist/knowledge/playbooks/refinement.document-facts/method.md +16 -123
  127. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +15 -8
  128. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +10 -4
  129. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +10 -4
  130. package/dist/knowledge/playbooks/top_down.capability-map/method.md +2 -2
  131. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +12 -5
  132. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +10 -4
  133. package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-protocol.json +1 -1
  134. package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-treatment.json +1 -1
  135. package/dist/knowledge/playbooks/top_down.market-analysis/method.md +165 -51
  136. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +39 -21
  137. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +2 -6
  138. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +10 -4
  139. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +1 -1
  140. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +11 -5
  141. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +2 -2
  142. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +11 -5
  143. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +10 -4
  144. package/dist/knowledge/references/build-plan.task-graph.config.md +1 -45
  145. package/dist/knowledge/references/example.config.app-shell.full.md +4 -0
  146. package/dist/knowledge/references/example.provider.backend-module-shape.md +0 -7
  147. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +1 -0
  148. package/dist/knowledge/references/platform.config.saas.md +0 -50
  149. package/dist/knowledge/references/saas.external-data.admin-endpoints.md +48 -0
  150. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +10 -6
  151. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +1 -0
  152. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +0 -109
  153. package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -137
  154. package/dist/knowledge/references/saas.models.http-api-binding.md +29 -3
  155. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +2 -4
  156. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +0 -2
  157. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +0 -14
  158. package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +1 -1
  159. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +0 -36
  160. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +0 -26
  161. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +0 -45
  162. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +1 -1
  163. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +1 -1
  164. package/dist/knowledge/references/zod.decorators.schema-metadata.md +0 -1
  165. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  166. package/dist/knowledge/registries/framework-topics.json +11 -48
  167. package/dist/knowledge/registries/playbooks.json +11 -74
  168. package/dist/knowledge/registries/source-tags.json +538 -622
  169. package/dist/knowledge/skills/INDEX.md +0 -1
  170. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -16
  171. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +8 -26
  172. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +74 -252
  173. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +8 -26
  174. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +21 -36
  175. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +19 -49
  176. package/dist/knowledge/skills/config-app-shell/SKILL.md +8 -6
  177. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +11 -6
  178. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +0 -50
  179. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +0 -7
  180. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +0 -36
  181. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +0 -36
  182. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +0 -36
  183. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +0 -109
  184. package/dist/knowledge/skills/resource-add-resource/SKILL.md +1 -2
  185. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +2 -4
  186. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +0 -2
  187. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +2 -157
  188. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +0 -109
  189. package/dist/knowledge/skills/resource-external-data/SKILL.md +2 -0
  190. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +29 -3
  191. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +70 -0
  192. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +0 -1
  193. package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +0 -17
  194. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +0 -46
  195. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +0 -26
  196. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +1 -1
  197. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +0 -109
  198. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +1 -1
  199. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +0 -36
  200. package/dist/knowledge/topic-index.json +128 -285
  201. package/dist/tsconfig.build.tsbuildinfo +1 -1
  202. package/dist/tsconfig.tsbuildinfo +1 -1
  203. package/package.json +4 -4
  204. package/dist/esm/.builder.pid +0 -9
  205. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +0 -185
  206. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +0 -66
  207. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +0 -56
  208. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +0 -40
  209. package/dist/knowledge/playbooks/top_down.market-research/method.md +0 -68
  210. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -42
  211. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +0 -239
  212. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +0 -69
  213. package/dist/knowledge/references/placement-plan.config.md +0 -330
  214. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +0 -58
  215. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +0 -118
  216. package/dist/knowledge/references/zod.decorators.data-categories.md +0 -197
  217. package/dist/knowledge/rules/resource-schema-awareness.md +0 -77
  218. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +0 -622
  219. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +0 -245
  220. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +0 -134
  221. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +0 -65
  222. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +0 -127
  223. /package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/structured-artifact-action.json +0 -0
@@ -9,12 +9,10 @@
9
9
  */
10
10
  export const playbookDefinition = {
11
11
  "ref": "bottom_up.foundation",
12
- "version": "0.2.0",
12
+ "version": "0.2.1",
13
13
  "phase": "bottom_up",
14
14
  "intent": "Bottom-up foundation — turn the approved domain plan + the top-down definition set into a configured, bootable application skeleton. Reads the domain-plan (the module decomposition + per-module resource inventory) and the vision-brief (whose compliance/vision constraints drive which engine capabilities to enable), then: (1) authors ./wildo.saas.config.ts for real — the engine capabilities (derived from compliance/vision), the modules (from the domain plan), and the providers (matched to the declared capabilities); (2) materializes the app skeleton (app/ shared-lib/ backend-api/ specifications/ + the module registries); (3) installs app-knowledge; (4) runs the deterministic bring-up — wildo setup --non-interactive, then wildo local init. This is a v1 SCAFFOLD METHOD describing the foundation SEQUENCE: skeleton materialization and app-knowledge installation remain deferred greenfield tooling, while headless setup and verified local initialization are registered commands once the app structure exists. It emits NO artifact: the deliverable is the app itself (the authored config + materialized skeleton + verified initialization), and the reasons behind each capability/module/provider choice are recorded as comments in the config the next reader opens. The foundation-manifest family it used to emit was retired 2026-08-25 with the app-creation verification/digest aspect. Runs after the domain plan is approved and the journey is in the bottom_up phase.",
15
- "functionalTopics": ["configure_application_foundation"],
16
15
  "preconditions": [
17
- { "kind": "phase_is", "phase": "bottom_up" },
18
16
  { "kind": "artifact_exists", "selector": { "family": "domain-plan" } },
19
17
  { "kind": "artifact_exists", "selector": { "family": "vision-brief" } }
20
18
  ],
@@ -33,7 +31,8 @@ export const playbookDefinition = {
33
31
  "config-saas",
34
32
  "module-registration",
35
33
  "infra-environment-config",
36
- "local-environment-bootstrap"
34
+ "local-environment-bootstrap",
35
+ "application-database-migrations"
37
36
  ],
38
37
  "elicitation": {
39
38
  "questions": [
@@ -52,6 +51,28 @@ export const playbookDefinition = {
52
51
  "question": "What is the application's tenancy model? Answer `organizations` when users collaborate inside shared workspaces/teams (this enables the ORGANIZATIONS engine capability), or `users` when every user's data is their own.",
53
52
  "kind": "choice",
54
53
  "options": ["organizations", "users"]
54
+ },
55
+ /*
56
+ * The operator's own legal identity (issue #235), asked HERE because this is the playbook that
57
+ * writes `wildo.saas.config.ts` and already carries the `config-saas` skill — an answer
58
+ * elicited anywhere else would have nowhere to land, since a companion-agent playbook produces
59
+ * an artifact and writes no files.
60
+ *
61
+ * Both questions are deliberately ANSWERABLE IN PART. Every part of
62
+ * `operatorComplianceIdentity` is independently declarable (#228), so a creator who knows the
63
+ * registered name and not the lawful bases records the name — and Paul's decision (#225) is
64
+ * explicit that filling the entity must never block. A question that demanded the whole thing
65
+ * would reintroduce the blocking this lane just removed, one layer up.
66
+ */
67
+ {
68
+ "ref": "operating-entity",
69
+ "question": "Which legal entity operates this service? Give the registered company name, its registered address, and the route a person uses to reach you about privacy (an email, a URL or a postal address). Answer only the parts you actually know today — anything you leave out is recorded as outstanding and nothing is blocked by it. Do NOT supply a placeholder or a plausible-looking value: a produced privacy notice quotes these as fact, and the address is what a person would use to serve a legal request on a real company.",
70
+ "kind": "free_text"
71
+ },
72
+ {
73
+ "ref": "operating-jurisdictions",
74
+ "question": "Which jurisdictions does this application operate in, and why does each one reach it — are you established there, do you sell there, or do you hold data about people there? Use country codes (`fr`, `us`), the supranational `eu`, or a subdivision (`us-ca`). Answer \"not decided\" if the market is genuinely unsettled; an absent answer is read as unanswered, never as \"nowhere\".",
75
+ "kind": "free_text"
55
76
  }
56
77
  ]
57
78
  }
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.foundation/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,sBAAsB;IAC7B,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,87CAA87C;IACx8C,kBAAkB,EAAE,CAAC,kCAAkC,CAAC;IACxD,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,UAAU,EAAE,OAAO,EAAE,WAAW,EAAE;QAC5C,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,aAAa,EAAE,EAAE;QACtE,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,cAAc,EAAE,EAAE;KACxE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,aAAa,EAAE;QAC3B,EAAE,QAAQ,EAAE,cAAc,EAAE;QAC5B,EAAE,QAAQ,EAAE,iBAAiB,EAAE;QAC/B,EAAE,QAAQ,EAAE,gBAAgB,EAAE;QAC9B,EAAE,QAAQ,EAAE,cAAc,EAAE;QAC5B,EAAE,QAAQ,EAAE,SAAS,EAAE;KACxB;IACD,SAAS,EAAE,EAAE;IACb,QAAQ,EAAE;QACR,WAAW,EAAE;YACX,gBAAgB;YAChB,aAAa;YACb,qBAAqB;YACrB,0BAA0B;YAC1B,6BAA6B;SAC9B;QACD,aAAa,EAAE;YACb,WAAW,EAAE;gBACX;;;;;;;;;mBASG;gBACH;oBACE,KAAK,EAAE,eAAe;oBACtB,UAAU,EAAE,2NAA2N;oBACvO,MAAM,EAAE,QAAQ;oBAChB,SAAS,EAAE,CAAC,eAAe,EAAE,OAAO,CAAC;iBACtC;aACF;SACF;KACF;IACC,UAAU,EAAE,gBAAgB;IAC9B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * The structured method remains intentionally rich: its intent, inputs, output\n * contracts, elicitation, deterministic verification and skill routing are the\n * application knowledge a later generic assessment loop composes. This source\n * intentionally omits the superseded per-playbook evaluation-treatment object;\n * generation records that absence rather than fabricating legacy judge behavior.\n */\nexport const playbookDefinition =\n{\n \"ref\": \"bottom_up.foundation\",\n \"version\": \"0.2.0\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Bottom-up foundation — turn the approved domain plan + the top-down definition set into a configured, bootable application skeleton. Reads the domain-plan (the module decomposition + per-module resource inventory) and the vision-brief (whose compliance/vision constraints drive which engine capabilities to enable), then: (1) authors ./wildo.saas.config.ts for real — the engine capabilities (derived from compliance/vision), the modules (from the domain plan), and the providers (matched to the declared capabilities); (2) materializes the app skeleton (app/ shared-lib/ backend-api/ specifications/ + the module registries); (3) installs app-knowledge; (4) runs the deterministic bring-up — wildo setup --non-interactive, then wildo local init. This is a v1 SCAFFOLD METHOD describing the foundation SEQUENCE: skeleton materialization and app-knowledge installation remain deferred greenfield tooling, while headless setup and verified local initialization are registered commands once the app structure exists. It emits NO artifact: the deliverable is the app itself (the authored config + materialized skeleton + verified initialization), and the reasons behind each capability/module/provider choice are recorded as comments in the config the next reader opens. The foundation-manifest family it used to emit was retired 2026-08-25 with the app-creation verification/digest aspect. Runs after the domain plan is approved and the journey is in the bottom_up phase.\",\n \"functionalTopics\": [\"configure_application_foundation\"],\n \"preconditions\": [\n { \"kind\": \"phase_is\", \"phase\": \"bottom_up\" },\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"domain-plan\" } },\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"vision-brief\" } }\n ],\n \"inputs\": [\n { \"family\": \"domain-plan\" },\n { \"family\": \"vision-brief\" },\n { \"family\": \"market-snapshot\" },\n { \"family\": \"business-model\" },\n { \"family\": \"requirements\" },\n { \"family\": \"roadmap\" }\n ],\n \"outputs\": [],\n \"method\": {\n \"skillRefs\": [\n \"journey-status\",\n \"config-saas\",\n \"module-registration\",\n \"infra-environment-config\",\n \"local-environment-bootstrap\"\n ],\n \"elicitation\": {\n \"questions\": [\n /*\n * THE FALLBACK, since 2026-08-28. `bottom_up.domain-plan` now asks this and carries the\n * answer in the committed plan (`DomainPlanOutputSet.tenancy`), because the plan MODELS\n * tenancy — wonder-crm's invented a workspace module and a membership before anyone was\n * asked — so asking after the model is shaped lets a second answer contradict it.\n *\n * The executor reads the plan first and reaches this question only for a plan authored\n * before the field existed. Keep it: those plans are real (wonder-crm, wonder-todos) and\n * must stay composable.\n */\n {\n \"ref\": \"primary-scope\",\n \"question\": \"What is the application's tenancy model? Answer `organizations` when users collaborate inside shared workspaces/teams (this enables the ORGANIZATIONS engine capability), or `users` when every user's data is their own.\",\n \"kind\": \"choice\",\n \"options\": [\"organizations\", \"users\"]\n }\n ]\n }\n },\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
1
+ {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.foundation/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,sBAAsB;IAC7B,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,87CAA87C;IACx8C,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,aAAa,EAAE,EAAE;QACtE,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,cAAc,EAAE,EAAE;KACxE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,aAAa,EAAE;QAC3B,EAAE,QAAQ,EAAE,cAAc,EAAE;QAC5B,EAAE,QAAQ,EAAE,iBAAiB,EAAE;QAC/B,EAAE,QAAQ,EAAE,gBAAgB,EAAE;QAC9B,EAAE,QAAQ,EAAE,cAAc,EAAE;QAC5B,EAAE,QAAQ,EAAE,SAAS,EAAE;KACxB;IACD,SAAS,EAAE,EAAE;IACb,QAAQ,EAAE;QACR,WAAW,EAAE;YACX,gBAAgB;YAChB,aAAa;YACb,qBAAqB;YACrB,0BAA0B;YAC1B,6BAA6B;YAC7B,iCAAiC;SAClC;QACD,aAAa,EAAE;YACb,WAAW,EAAE;gBACX;;;;;;;;;mBASG;gBACH;oBACE,KAAK,EAAE,eAAe;oBACtB,UAAU,EAAE,2NAA2N;oBACvO,MAAM,EAAE,QAAQ;oBAChB,SAAS,EAAE,CAAC,eAAe,EAAE,OAAO,CAAC;iBACtC;gBACD;;;;;;;;;;;mBAWG;gBACH;oBACE,KAAK,EAAE,kBAAkB;oBACzB,UAAU,EAAE,ogBAAogB;oBAChhB,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,yBAAyB;oBAChC,UAAU,EAAE,6XAA6X;oBACzY,MAAM,EAAE,WAAW;iBACpB;aACF;SACF;KACF;IACC,UAAU,EAAE,gBAAgB;IAC9B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * The structured method remains intentionally rich: its intent, inputs, output\n * contracts, elicitation, deterministic verification and skill routing are the\n * application knowledge a later generic assessment loop composes. This source\n * intentionally omits the superseded per-playbook evaluation-treatment object;\n * generation records that absence rather than fabricating legacy judge behavior.\n */\nexport const playbookDefinition =\n{\n \"ref\": \"bottom_up.foundation\",\n \"version\": \"0.2.1\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Bottom-up foundation — turn the approved domain plan + the top-down definition set into a configured, bootable application skeleton. Reads the domain-plan (the module decomposition + per-module resource inventory) and the vision-brief (whose compliance/vision constraints drive which engine capabilities to enable), then: (1) authors ./wildo.saas.config.ts for real — the engine capabilities (derived from compliance/vision), the modules (from the domain plan), and the providers (matched to the declared capabilities); (2) materializes the app skeleton (app/ shared-lib/ backend-api/ specifications/ + the module registries); (3) installs app-knowledge; (4) runs the deterministic bring-up — wildo setup --non-interactive, then wildo local init. This is a v1 SCAFFOLD METHOD describing the foundation SEQUENCE: skeleton materialization and app-knowledge installation remain deferred greenfield tooling, while headless setup and verified local initialization are registered commands once the app structure exists. It emits NO artifact: the deliverable is the app itself (the authored config + materialized skeleton + verified initialization), and the reasons behind each capability/module/provider choice are recorded as comments in the config the next reader opens. The foundation-manifest family it used to emit was retired 2026-08-25 with the app-creation verification/digest aspect. Runs after the domain plan is approved and the journey is in the bottom_up phase.\",\n \"preconditions\": [\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"domain-plan\" } },\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"vision-brief\" } }\n ],\n \"inputs\": [\n { \"family\": \"domain-plan\" },\n { \"family\": \"vision-brief\" },\n { \"family\": \"market-snapshot\" },\n { \"family\": \"business-model\" },\n { \"family\": \"requirements\" },\n { \"family\": \"roadmap\" }\n ],\n \"outputs\": [],\n \"method\": {\n \"skillRefs\": [\n \"journey-status\",\n \"config-saas\",\n \"module-registration\",\n \"infra-environment-config\",\n \"local-environment-bootstrap\",\n \"application-database-migrations\"\n ],\n \"elicitation\": {\n \"questions\": [\n /*\n * THE FALLBACK, since 2026-08-28. `bottom_up.domain-plan` now asks this and carries the\n * answer in the committed plan (`DomainPlanOutputSet.tenancy`), because the plan MODELS\n * tenancy — wonder-crm's invented a workspace module and a membership before anyone was\n * asked — so asking after the model is shaped lets a second answer contradict it.\n *\n * The executor reads the plan first and reaches this question only for a plan authored\n * before the field existed. Keep it: those plans are real (wonder-crm, wonder-todos) and\n * must stay composable.\n */\n {\n \"ref\": \"primary-scope\",\n \"question\": \"What is the application's tenancy model? Answer `organizations` when users collaborate inside shared workspaces/teams (this enables the ORGANIZATIONS engine capability), or `users` when every user's data is their own.\",\n \"kind\": \"choice\",\n \"options\": [\"organizations\", \"users\"]\n },\n /*\n * The operator's own legal identity (issue #235), asked HERE because this is the playbook that\n * writes `wildo.saas.config.ts` and already carries the `config-saas` skill — an answer\n * elicited anywhere else would have nowhere to land, since a companion-agent playbook produces\n * an artifact and writes no files.\n *\n * Both questions are deliberately ANSWERABLE IN PART. Every part of\n * `operatorComplianceIdentity` is independently declarable (#228), so a creator who knows the\n * registered name and not the lawful bases records the name — and Paul's decision (#225) is\n * explicit that filling the entity must never block. A question that demanded the whole thing\n * would reintroduce the blocking this lane just removed, one layer up.\n */\n {\n \"ref\": \"operating-entity\",\n \"question\": \"Which legal entity operates this service? Give the registered company name, its registered address, and the route a person uses to reach you about privacy (an email, a URL or a postal address). Answer only the parts you actually know today — anything you leave out is recorded as outstanding and nothing is blocked by it. Do NOT supply a placeholder or a plausible-looking value: a produced privacy notice quotes these as fact, and the address is what a person would use to serve a legal request on a real company.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"operating-jurisdictions\",\n \"question\": \"Which jurisdictions does this application operate in, and why does each one reach it — are you established there, do you sell there, or do you hold data about people there? Use country codes (`fr`, `us`), the supranational `eu`, or a subdivision (`us-ca`). Answer \\\"not decided\\\" if the market is genuinely unsettled; an absent answer is read as unanswered, never as \\\"nowhere\\\".\",\n \"kind\": \"free_text\"\n }\n ]\n }\n },\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
@@ -10,11 +10,7 @@ export declare const playbookDefinition: {
10
10
  readonly version: "0.1.0";
11
11
  readonly phase: "bottom_up";
12
12
  readonly intent: "Decide WHERE every settings destination, resource operation and application view sits in the application shell, and WHY. Reads the domain plan (the modules, their resources and what they mean) and the requirements (which tasks matter), and produces a PLACEMENT PLAN: for each subject, either a PLACED decision naming one surface (the settings hub rail, the sidebar, the user menu, the command palette) and its address on that surface, or an explicit DECLINED decision with a reason. Both carry a rationale. It also declares the GROUPS that should exist on the grouped surfaces (settings rail categories, sidebar sections) with the product purpose behind each, which is what grounds their generated labels in authored intent instead of filler. This playbook DECIDES placement; it does NOT author configuration — turning a decision into `frontend/src/config/settings-hub.config.ts` and `app-shell.config.ts` is a coding task the build lane dispatches through the `settings-placement-authoring` skill. It runs BEFORE build-decompose, which consumes the plan and emits those tasks — the reverse order would be a cycle, since build-decompose is what produces the build plan. It writes no TypeScript, invents no destination refs, and authors no labels. It exists because the alternative is the framework defaulting placement, which is what made an application's settings rail unauthorable: nothing is placed implicitly, so a subject nobody decided about is a visible coverage gap rather than a silent framework default.";
13
- readonly functionalTopics: readonly ["shape_user_experience"];
14
13
  readonly preconditions: readonly [{
15
- readonly kind: "phase_is";
16
- readonly phase: "bottom_up";
17
- }, {
18
14
  readonly kind: "artifact_exists";
19
15
  readonly selector: {
20
16
  readonly family: "domain-plan";
@@ -28,7 +24,7 @@ export declare const playbookDefinition: {
28
24
  readonly outputs: readonly [{
29
25
  readonly family: "placement-plan";
30
26
  readonly schemaRef: "saas-specifications:PlacementPlan";
31
- readonly description: "The placement decision — `groups[]` (the containers that should exist on the grouped surfaces, each with the product purpose behind it) plus `decisions[]` (one per subject PER SURFACE: a stable `decisionRef`, the `PlacementSubject` being placed — an engine settings destination by ref, a resource operation, or an app view — a `PlacementDisposition` of PLACED or DECLINED, the surface-discriminated `PlacementAddress` when placed, and a REQUIRED `rationale` on both arms). Each decision also carries a REQUIRED `origin` — `DELIBERATED` or `REVISED` — which the trusted runtime stamps `DELIBERATED`; it is not representable in the provider-facing generation shape, because a panel run IS the panel's judgement and a model cannot declare its own output a human revision. A later edit that changes a decision sets `origin: REVISED` and records the panel's own reasoning in `supersedes.rationale`, so the artifact stops asserting panel reasoning for a decision the panel never took. Typed by the `_core` `placement-plan` family (`PlacementPlan`); the provider answers the strict `PlacementPlanGeneration` shape and the trusted runtime stamps refs and version. `validatePlacementPlan` is the deterministic validator: one subject placed twice on the SAME surface is a hard floor (the plan contradicts itself), while an empty group and an order collision are authoring warnings. Its coverage checks run only when the caller supplies the destination catalog, so a run without one reports no coverage result rather than a clean one. The plan carries no file path, config key or label string — those belong to the coding task that authors the config.";
27
+ readonly description: "The placement decision — `groups[]` (the containers that should exist on the grouped surfaces, each with the product purpose behind it) plus `decisions[]` (one per subject PER SURFACE: a stable `decisionRef`, the `PlacementSubject` being placed — an engine settings destination by ref, a resource operation, or an app view — a `PlacementDisposition` of PLACED or DECLINED, the surface-discriminated `PlacementAddress` when placed, and a REQUIRED `rationale` on both arms). Each decision also carries a REQUIRED `origin` — `DELIBERATED` or `REVISED` — which the trusted runtime stamps `DELIBERATED`; it is not representable in the provider-facing generation shape, because a panel run IS the panel's judgement and a model cannot declare its own output a human revision. A later edit that changes a decision sets `origin: REVISED` and records the panel's own reasoning in `supersedes.rationale`, so the artifact stops asserting panel reasoning for a decision the panel never took. Typed by the `_core` `placement-plan` family (`PlacementPlan`); the provider answers the strict `PlacementPlanGeneration` shape and the trusted runtime stamps refs and version. `validatePlacementPlan` is the deterministic validator: one subject placed twice on the SAME surface is a hard floor (the plan contradicts itself), while an empty group and an order collision are authoring warnings. Its coverage checks run per SUBJECT KIND and only for the kinds a caller supplies a catalog for, so a run that supplies none — the case today — reports no coverage result rather than a clean one, and a caller holding only the engine settings catalog can never make an unknown-subject refusal fire on a resource operation or an app view it was never told about. The plan carries no file path, config key or label string — those belong to the coding task that authors the config.";
32
28
  }];
33
29
  readonly method: {
34
30
  readonly "//contextSources": "WORKSPACE_TRUTH — placement is decided against what EXISTS: the real engine settings destinations, the real resources and their operations, and the shell surfaces the application already has. A planner working from the definition artifacts alone invents destination refs that resolve to nothing, and every decision it emits is unplaceable.";
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.placement-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8CrB,CAAC"}
1
+ {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.placement-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA4CrB,CAAC"}
@@ -10,9 +10,7 @@ export const playbookDefinition = {
10
10
  "version": "0.1.0",
11
11
  "phase": "bottom_up",
12
12
  "intent": "Decide WHERE every settings destination, resource operation and application view sits in the application shell, and WHY. Reads the domain plan (the modules, their resources and what they mean) and the requirements (which tasks matter), and produces a PLACEMENT PLAN: for each subject, either a PLACED decision naming one surface (the settings hub rail, the sidebar, the user menu, the command palette) and its address on that surface, or an explicit DECLINED decision with a reason. Both carry a rationale. It also declares the GROUPS that should exist on the grouped surfaces (settings rail categories, sidebar sections) with the product purpose behind each, which is what grounds their generated labels in authored intent instead of filler. This playbook DECIDES placement; it does NOT author configuration — turning a decision into `frontend/src/config/settings-hub.config.ts` and `app-shell.config.ts` is a coding task the build lane dispatches through the `settings-placement-authoring` skill. It runs BEFORE build-decompose, which consumes the plan and emits those tasks — the reverse order would be a cycle, since build-decompose is what produces the build plan. It writes no TypeScript, invents no destination refs, and authors no labels. It exists because the alternative is the framework defaulting placement, which is what made an application's settings rail unauthorable: nothing is placed implicitly, so a subject nobody decided about is a visible coverage gap rather than a silent framework default.",
13
- "functionalTopics": ["shape_user_experience"],
14
13
  "preconditions": [
15
- { "kind": "phase_is", "phase": "bottom_up" },
16
14
  { "kind": "artifact_exists", "selector": { "family": "domain-plan" } }
17
15
  ],
18
16
  "inputs": [
@@ -23,7 +21,7 @@ export const playbookDefinition = {
23
21
  {
24
22
  "family": "placement-plan",
25
23
  "schemaRef": "saas-specifications:PlacementPlan",
26
- "description": "The placement decision — `groups[]` (the containers that should exist on the grouped surfaces, each with the product purpose behind it) plus `decisions[]` (one per subject PER SURFACE: a stable `decisionRef`, the `PlacementSubject` being placed — an engine settings destination by ref, a resource operation, or an app view — a `PlacementDisposition` of PLACED or DECLINED, the surface-discriminated `PlacementAddress` when placed, and a REQUIRED `rationale` on both arms). Each decision also carries a REQUIRED `origin` — `DELIBERATED` or `REVISED` — which the trusted runtime stamps `DELIBERATED`; it is not representable in the provider-facing generation shape, because a panel run IS the panel's judgement and a model cannot declare its own output a human revision. A later edit that changes a decision sets `origin: REVISED` and records the panel's own reasoning in `supersedes.rationale`, so the artifact stops asserting panel reasoning for a decision the panel never took. Typed by the `_core` `placement-plan` family (`PlacementPlan`); the provider answers the strict `PlacementPlanGeneration` shape and the trusted runtime stamps refs and version. `validatePlacementPlan` is the deterministic validator: one subject placed twice on the SAME surface is a hard floor (the plan contradicts itself), while an empty group and an order collision are authoring warnings. Its coverage checks run only when the caller supplies the destination catalog, so a run without one reports no coverage result rather than a clean one. The plan carries no file path, config key or label string — those belong to the coding task that authors the config."
24
+ "description": "The placement decision — `groups[]` (the containers that should exist on the grouped surfaces, each with the product purpose behind it) plus `decisions[]` (one per subject PER SURFACE: a stable `decisionRef`, the `PlacementSubject` being placed — an engine settings destination by ref, a resource operation, or an app view — a `PlacementDisposition` of PLACED or DECLINED, the surface-discriminated `PlacementAddress` when placed, and a REQUIRED `rationale` on both arms). Each decision also carries a REQUIRED `origin` — `DELIBERATED` or `REVISED` — which the trusted runtime stamps `DELIBERATED`; it is not representable in the provider-facing generation shape, because a panel run IS the panel's judgement and a model cannot declare its own output a human revision. A later edit that changes a decision sets `origin: REVISED` and records the panel's own reasoning in `supersedes.rationale`, so the artifact stops asserting panel reasoning for a decision the panel never took. Typed by the `_core` `placement-plan` family (`PlacementPlan`); the provider answers the strict `PlacementPlanGeneration` shape and the trusted runtime stamps refs and version. `validatePlacementPlan` is the deterministic validator: one subject placed twice on the SAME surface is a hard floor (the plan contradicts itself), while an empty group and an order collision are authoring warnings. Its coverage checks run per SUBJECT KIND and only for the kinds a caller supplies a catalog for, so a run that supplies none — the case today — reports no coverage result rather than a clean one, and a caller holding only the engine settings catalog can never make an unknown-subject refusal fire on a resource operation or an app view it was never told about. The plan carries no file path, config key or label string — those belong to the coding task that authors the config."
27
25
  }
28
26
  ],
29
27
  "method": {
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.placement-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,0BAA0B;IACjC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,2+CAA2+C;IACr/C,kBAAkB,EAAE,CAAC,uBAAuB,CAAC;IAC7C,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,UAAU,EAAE,OAAO,EAAE,WAAW,EAAE;QAC5C,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,aAAa,EAAE,EAAE;KACvE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,aAAa,EAAE;QAC3B,EAAE,QAAQ,EAAE,cAAc,EAAE;KAC7B;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,gBAAgB;YAC1B,WAAW,EAAE,mCAAmC;YAChD,aAAa,EAAE,0mDAA0mD;SAC1nD;KACF;IACD,QAAQ,EAAE;QACR,kBAAkB,EAAE,qVAAqV;QACzW,gBAAgB,EAAE,CAAC,iBAAiB,CAAC;QACrC,WAAW,EAAE;YACX,8BAA8B;YAC9B,kBAAkB;YAClB,mBAAmB;YACnB,gBAAgB;SACjB;QACD,gBAAgB,EAAE,4pBAA4pB;QAC9qB,cAAc,EAAE;YACd,YAAY,EAAE,0BAA0B;YACxC,kBAAkB,EAAE,CAAC,uBAAuB,EAAE,wBAAwB,CAAC;YACvE,oBAAoB,EAAE,wBAAwB;YAC9C,sBAAsB,EAAE,uBAAuB;YAC/C,gBAAgB,EAAE,CAAC;SACpB;KACF;IACD,UAAU,EAAE,iBAAiB;IAC7B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * Placement is a DECISION the creator should not have to make. This playbook\n * produces it as an artifact, with a per-decision rationale, so a later reader\n * can ask \"why is this here?\" without re-deriving the answer.\n */\nexport const playbookDefinition =\n{\n \"ref\": \"bottom_up.placement-plan\",\n \"version\": \"0.1.0\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Decide WHERE every settings destination, resource operation and application view sits in the application shell, and WHY. Reads the domain plan (the modules, their resources and what they mean) and the requirements (which tasks matter), and produces a PLACEMENT PLAN: for each subject, either a PLACED decision naming one surface (the settings hub rail, the sidebar, the user menu, the command palette) and its address on that surface, or an explicit DECLINED decision with a reason. Both carry a rationale. It also declares the GROUPS that should exist on the grouped surfaces (settings rail categories, sidebar sections) with the product purpose behind each, which is what grounds their generated labels in authored intent instead of filler. This playbook DECIDES placement; it does NOT author configuration — turning a decision into `frontend/src/config/settings-hub.config.ts` and `app-shell.config.ts` is a coding task the build lane dispatches through the `settings-placement-authoring` skill. It runs BEFORE build-decompose, which consumes the plan and emits those tasks — the reverse order would be a cycle, since build-decompose is what produces the build plan. It writes no TypeScript, invents no destination refs, and authors no labels. It exists because the alternative is the framework defaulting placement, which is what made an application's settings rail unauthorable: nothing is placed implicitly, so a subject nobody decided about is a visible coverage gap rather than a silent framework default.\",\n \"functionalTopics\": [\"shape_user_experience\"],\n \"preconditions\": [\n { \"kind\": \"phase_is\", \"phase\": \"bottom_up\" },\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"domain-plan\" } }\n ],\n \"inputs\": [\n { \"family\": \"domain-plan\" },\n { \"family\": \"requirements\" }\n ],\n \"outputs\": [\n {\n \"family\": \"placement-plan\",\n \"schemaRef\": \"saas-specifications:PlacementPlan\",\n \"description\": \"The placement decision — `groups[]` (the containers that should exist on the grouped surfaces, each with the product purpose behind it) plus `decisions[]` (one per subject PER SURFACE: a stable `decisionRef`, the `PlacementSubject` being placed — an engine settings destination by ref, a resource operation, or an app view — a `PlacementDisposition` of PLACED or DECLINED, the surface-discriminated `PlacementAddress` when placed, and a REQUIRED `rationale` on both arms). Each decision also carries a REQUIRED `origin` — `DELIBERATED` or `REVISED` — which the trusted runtime stamps `DELIBERATED`; it is not representable in the provider-facing generation shape, because a panel run IS the panel's judgement and a model cannot declare its own output a human revision. A later edit that changes a decision sets `origin: REVISED` and records the panel's own reasoning in `supersedes.rationale`, so the artifact stops asserting panel reasoning for a decision the panel never took. Typed by the `_core` `placement-plan` family (`PlacementPlan`); the provider answers the strict `PlacementPlanGeneration` shape and the trusted runtime stamps refs and version. `validatePlacementPlan` is the deterministic validator: one subject placed twice on the SAME surface is a hard floor (the plan contradicts itself), while an empty group and an order collision are authoring warnings. Its coverage checks run only when the caller supplies the destination catalog, so a run without one reports no coverage result rather than a clean one. The plan carries no file path, config key or label string — those belong to the coding task that authors the config.\"\n }\n ],\n \"method\": {\n \"//contextSources\": \"WORKSPACE_TRUTH — placement is decided against what EXISTS: the real engine settings destinations, the real resources and their operations, and the shell surfaces the application already has. A planner working from the definition artifacts alone invents destination refs that resolve to nothing, and every decision it emits is unplaceable.\",\n \"contextSources\": [\"workspace_truth\"],\n \"skillRefs\": [\n \"settings-placement-authoring\",\n \"config-app-shell\",\n \"config-navigation\",\n \"journey-status\"\n ],\n \"//deliberation\": \"Placement is DECIDED BY A PANEL, not elicited from the creator: the arrangement that is right for an application has several defensible answers, and the creator is the person least equipped to choose between them before the app exists. The information-architect OWNS the domain (so it derives the rubric); the design-system-guardian sits as the coherence memory, because where a thing goes must not fork the pattern the shipped surfaces already taught users. Three candidates, because the criteria trade off against each other — first-run discoverability, the daily-use path, and category convention pull in different directions and a single pass silently picks one.\",\n \"deliberation\": {\n \"workDomain\": \"information_architecture\",\n \"reviewerRoleRefs\": [\"information-architect\", \"design-system-guardian\"],\n \"coordinatorRoleRef\": \"design-system-guardian\",\n \"rubricDeriverRoleRef\": \"information-architect\",\n \"candidateCount\": 3\n }\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
1
+ {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.placement-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,0BAA0B;IACjC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,2+CAA2+C;IACr/C,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,aAAa,EAAE,EAAE;KACvE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,aAAa,EAAE;QAC3B,EAAE,QAAQ,EAAE,cAAc,EAAE;KAC7B;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,gBAAgB;YAC1B,WAAW,EAAE,mCAAmC;YAChD,aAAa,EAAE,2zDAA2zD;SAC30D;KACF;IACD,QAAQ,EAAE;QACR,kBAAkB,EAAE,qVAAqV;QACzW,gBAAgB,EAAE,CAAC,iBAAiB,CAAC;QACrC,WAAW,EAAE;YACX,8BAA8B;YAC9B,kBAAkB;YAClB,mBAAmB;YACnB,gBAAgB;SACjB;QACD,gBAAgB,EAAE,4pBAA4pB;QAC9qB,cAAc,EAAE;YACd,YAAY,EAAE,0BAA0B;YACxC,kBAAkB,EAAE,CAAC,uBAAuB,EAAE,wBAAwB,CAAC;YACvE,oBAAoB,EAAE,wBAAwB;YAC9C,sBAAsB,EAAE,uBAAuB;YAC/C,gBAAgB,EAAE,CAAC;SACpB;KACF;IACD,UAAU,EAAE,iBAAiB;IAC7B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * Placement is a DECISION the creator should not have to make. This playbook\n * produces it as an artifact, with a per-decision rationale, so a later reader\n * can ask \"why is this here?\" without re-deriving the answer.\n */\nexport const playbookDefinition =\n{\n \"ref\": \"bottom_up.placement-plan\",\n \"version\": \"0.1.0\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Decide WHERE every settings destination, resource operation and application view sits in the application shell, and WHY. Reads the domain plan (the modules, their resources and what they mean) and the requirements (which tasks matter), and produces a PLACEMENT PLAN: for each subject, either a PLACED decision naming one surface (the settings hub rail, the sidebar, the user menu, the command palette) and its address on that surface, or an explicit DECLINED decision with a reason. Both carry a rationale. It also declares the GROUPS that should exist on the grouped surfaces (settings rail categories, sidebar sections) with the product purpose behind each, which is what grounds their generated labels in authored intent instead of filler. This playbook DECIDES placement; it does NOT author configuration — turning a decision into `frontend/src/config/settings-hub.config.ts` and `app-shell.config.ts` is a coding task the build lane dispatches through the `settings-placement-authoring` skill. It runs BEFORE build-decompose, which consumes the plan and emits those tasks — the reverse order would be a cycle, since build-decompose is what produces the build plan. It writes no TypeScript, invents no destination refs, and authors no labels. It exists because the alternative is the framework defaulting placement, which is what made an application's settings rail unauthorable: nothing is placed implicitly, so a subject nobody decided about is a visible coverage gap rather than a silent framework default.\",\n \"preconditions\": [\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"domain-plan\" } }\n ],\n \"inputs\": [\n { \"family\": \"domain-plan\" },\n { \"family\": \"requirements\" }\n ],\n \"outputs\": [\n {\n \"family\": \"placement-plan\",\n \"schemaRef\": \"saas-specifications:PlacementPlan\",\n \"description\": \"The placement decision — `groups[]` (the containers that should exist on the grouped surfaces, each with the product purpose behind it) plus `decisions[]` (one per subject PER SURFACE: a stable `decisionRef`, the `PlacementSubject` being placed — an engine settings destination by ref, a resource operation, or an app view — a `PlacementDisposition` of PLACED or DECLINED, the surface-discriminated `PlacementAddress` when placed, and a REQUIRED `rationale` on both arms). Each decision also carries a REQUIRED `origin` — `DELIBERATED` or `REVISED` — which the trusted runtime stamps `DELIBERATED`; it is not representable in the provider-facing generation shape, because a panel run IS the panel's judgement and a model cannot declare its own output a human revision. A later edit that changes a decision sets `origin: REVISED` and records the panel's own reasoning in `supersedes.rationale`, so the artifact stops asserting panel reasoning for a decision the panel never took. Typed by the `_core` `placement-plan` family (`PlacementPlan`); the provider answers the strict `PlacementPlanGeneration` shape and the trusted runtime stamps refs and version. `validatePlacementPlan` is the deterministic validator: one subject placed twice on the SAME surface is a hard floor (the plan contradicts itself), while an empty group and an order collision are authoring warnings. Its coverage checks run per SUBJECT KIND and only for the kinds a caller supplies a catalog for, so a run that supplies none — the case today — reports no coverage result rather than a clean one, and a caller holding only the engine settings catalog can never make an unknown-subject refusal fire on a resource operation or an app view it was never told about. The plan carries no file path, config key or label string — those belong to the coding task that authors the config.\"\n }\n ],\n \"method\": {\n \"//contextSources\": \"WORKSPACE_TRUTH — placement is decided against what EXISTS: the real engine settings destinations, the real resources and their operations, and the shell surfaces the application already has. A planner working from the definition artifacts alone invents destination refs that resolve to nothing, and every decision it emits is unplaceable.\",\n \"contextSources\": [\"workspace_truth\"],\n \"skillRefs\": [\n \"settings-placement-authoring\",\n \"config-app-shell\",\n \"config-navigation\",\n \"journey-status\"\n ],\n \"//deliberation\": \"Placement is DECIDED BY A PANEL, not elicited from the creator: the arrangement that is right for an application has several defensible answers, and the creator is the person least equipped to choose between them before the app exists. The information-architect OWNS the domain (so it derives the rubric); the design-system-guardian sits as the coherence memory, because where a thing goes must not fork the pattern the shipped surfaces already taught users. Three candidates, because the criteria trade off against each other — first-run discoverability, the daily-use path, and category convention pull in different directions and a single pass silently picks one.\",\n \"deliberation\": {\n \"workDomain\": \"information_architecture\",\n \"reviewerRoleRefs\": [\"information-architect\", \"design-system-guardian\"],\n \"coordinatorRoleRef\": \"design-system-guardian\",\n \"rubricDeriverRoleRef\": \"information-architect\",\n \"candidateCount\": 3\n }\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
@@ -10,10 +10,9 @@
10
10
  */
11
11
  export declare const playbookDefinition: {
12
12
  readonly ref: "refinement.compliance-document-candidate";
13
- readonly version: "0.1.0";
13
+ readonly version: "0.2.0";
14
14
  readonly phase: "refinement";
15
15
  readonly intent: "Propose structured privacy-notice or service-terms candidate content from the application's accepted document facts. The companion agent may draft prose but cannot invent a fact, decide a legal question, approve, release or publish the document: every clause it writes is checked against the `document-facts` family, and a clause asserting a fact the application never declared is refused before it becomes a file.";
16
- readonly functionalTopics: readonly [];
17
16
  readonly preconditions: readonly [{
18
17
  readonly kind: "artifact_expected";
19
18
  readonly selector: {
@@ -31,6 +30,9 @@ export declare const playbookDefinition: {
31
30
  readonly method: {
32
31
  readonly "//contextSources": "DOCUMENT_BLUEPRINT — this playbook DRAFTS a governed document, and the catalog is the only thing that says what one must contain. Measured 2026-08-30: `document-definition:public.privacy-notice` requires eight facts; wonder-crm's generated notice declared twenty and matched NONE of them, scoring zero dangling citations throughout — internally consistent, and addressing none of what a privacy notice is obliged to address. The catalog had held the answer since it was written and had no runtime lookup of any kind, while this playbook's own skill instructed the drafter to \"Read the definition and blueprint\": a step it was told to perform and given nothing to perform it on. Deliberately NOT COMPLIANCE_PRIMARY_FACTS: that source carries raw resource declarations and belongs to `refinement.document-facts`, which declares it. A drafter given mechanism directly could write a clause resting on something the application never DECLARED, which is precisely what the fact-binding check exists to refuse — this playbook reads the declared `document-facts` family and nothing beneath it.";
33
32
  readonly contextSources: readonly ["document_blueprint"];
33
+ readonly "//briefAdequacyGate": "The #254 pilot (decision 2026-09-02, built 2026-09-04): this lane is where both recorded promise-gap defects lived, and its context needs vary per document. The gate judges the composed brief once; INSUFFICIENT adds proposed sources for this run only. The exclusion carries the //contextSources boundary above into the mechanism: the gate may never hand this drafter raw resource mechanism.";
34
+ readonly briefAdequacyGate: true;
35
+ readonly briefAdequacyExcludedSources: readonly ["compliance_primary_facts"];
34
36
  readonly skillRefs: readonly ["compliance-document-authoring"];
35
37
  };
36
38
  readonly executor: "companion_agent";
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/refinement.compliance-document-candidate/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8DrB,CAAC"}
1
+ {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/refinement.compliance-document-candidate/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgErB,CAAC"}
@@ -10,10 +10,9 @@
10
10
  */
11
11
  export const playbookDefinition = {
12
12
  "ref": "refinement.compliance-document-candidate",
13
- "version": "0.1.0",
13
+ "version": "0.2.0",
14
14
  "phase": "refinement",
15
15
  "intent": "Propose structured privacy-notice or service-terms candidate content from the application's accepted document facts. The companion agent may draft prose but cannot invent a fact, decide a legal question, approve, release or publish the document: every clause it writes is checked against the `document-facts` family, and a clause asserting a fact the application never declared is refused before it becomes a file.",
16
- "functionalTopics": [],
17
16
  "preconditions": [
18
17
  {
19
18
  /*
@@ -59,6 +58,9 @@ export const playbookDefinition = {
59
58
  "method": {
60
59
  "//contextSources": "DOCUMENT_BLUEPRINT \u2014 this playbook DRAFTS a governed document, and the catalog is the only thing that says what one must contain. Measured 2026-08-30: `document-definition:public.privacy-notice` requires eight facts; wonder-crm's generated notice declared twenty and matched NONE of them, scoring zero dangling citations throughout \u2014 internally consistent, and addressing none of what a privacy notice is obliged to address. The catalog had held the answer since it was written and had no runtime lookup of any kind, while this playbook's own skill instructed the drafter to \"Read the definition and blueprint\": a step it was told to perform and given nothing to perform it on. Deliberately NOT COMPLIANCE_PRIMARY_FACTS: that source carries raw resource declarations and belongs to `refinement.document-facts`, which declares it. A drafter given mechanism directly could write a clause resting on something the application never DECLARED, which is precisely what the fact-binding check exists to refuse \u2014 this playbook reads the declared `document-facts` family and nothing beneath it.",
61
60
  "contextSources": ["document_blueprint"],
61
+ "//briefAdequacyGate": "The #254 pilot (decision 2026-09-02, built 2026-09-04): this lane is where both recorded promise-gap defects lived, and its context needs vary per document. The gate judges the composed brief once; INSUFFICIENT adds proposed sources for this run only. The exclusion carries the //contextSources boundary above into the mechanism: the gate may never hand this drafter raw resource mechanism.",
62
+ "briefAdequacyGate": true,
63
+ "briefAdequacyExcludedSources": ["compliance_primary_facts"],
62
64
  "skillRefs": [
63
65
  "compliance-document-authoring"
64
66
  ]
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/refinement.compliance-document-candidate/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,0CAA0C;IACjD,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,YAAY;IACrB,QAAQ,EAAE,gaAAga;IAC1a,kBAAkB,EAAE,EAAE;IACtB,eAAe,EAAE;QACf;YACE;;;;;;;;;;;;;;;;;;;;;eAqBG;YACH,MAAM,EAAE,mBAAmB;YAC3B,UAAU,EAAE;gBACV,QAAQ,EAAE,gBAAgB;aAC3B;SACF;KACF;IACD,QAAQ,EAAE;QACR;YACE,QAAQ,EAAE,gBAAgB;SAC3B;KACF;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,+BAA+B;YACzC,WAAW,EAAE,iDAAiD;YAC9D,aAAa,EAAE,0TAA0T;SAC1U;KACF;IACD,QAAQ,EAAE;QACR,kBAAkB,EAAE,glCAAglC;QACpmC,gBAAgB,EAAE,CAAC,oBAAoB,CAAC;QACxC,WAAW,EAAE;YACX,+BAA+B;SAChC;KACF;IACD,UAAU,EAAE,iBAAiB;IAC7B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * Migrated from the retired JSON-v1 authoring format at the first-activation\n * hard cut (same ref@version — the companion's assurance-document candidate\n * preparation pins `refinement.compliance-document-candidate@0.1.0` in the\n * installed Framework Knowledge and fails closed without it). This source\n * intentionally omits the superseded per-playbook evaluation-treatment object;\n * generation records that absence rather than fabricating legacy judge behavior.\n */\nexport const playbookDefinition =\n{\n \"ref\": \"refinement.compliance-document-candidate\",\n \"version\": \"0.1.0\",\n \"phase\": \"refinement\",\n \"intent\": \"Propose structured privacy-notice or service-terms candidate content from the application's accepted document facts. The companion agent may draft prose but cannot invent a fact, decide a legal question, approve, release or publish the document: every clause it writes is checked against the `document-facts` family, and a clause asserting a fact the application never declared is refused before it becomes a file.\",\n \"functionalTopics\": [],\n \"preconditions\": [\n {\n /*\n * The facts this draft SHOULD rest on — expected first, never a gate.\n *\n * Three revisions, and the middle one is the instructive part:\n *\n * 1. Until 2026-08-28 this gated on `compliance-document-fact-projection`, a host-computed\n * projection sealed with a projector identity, source-head digests and per-contribution\n * authority receipts. `artifact_valid` reads LANDED families and a host-computed projection\n * never lands, so the precondition could never be satisfied: this playbook, and with it the\n * whole `refinement` phase, was permanently ineligible from the day it was authored, and\n * nothing reported it because an ineligible playbook never reaches the board. The projection\n * went with the digest demolition (`.claude/rules/one-source-of-truth.md`, Rule 0).\n * 2. It was then re-gated onto `document-facts` with `artifact_valid`, which made it reachable\n * — and blocking. That is the wrong posture for a compliance document: an application must be\n * able to produce its privacy notice today, with the statements it cannot yet establish\n * marked incomplete, and complete them later. A document nobody can produce is worth less\n * than one that states precisely what is missing.\n * 3. `artifact_expected` (SEQUENCING) says facts come first while letting a human run proceed\n * past it. What the old projection PROTECTED — a document may not assert what nobody\n * established — is unaffected: it is a cross-reference check between this draft and the\n * facts file, run before the write, and it refuses INVENTION rather than incompleteness.\n */\n \"kind\": \"artifact_expected\",\n \"selector\": {\n \"family\": \"document-facts\"\n }\n }\n ],\n \"inputs\": [\n {\n \"family\": \"document-facts\"\n }\n ],\n \"outputs\": [\n {\n \"family\": \"compliance-document-candidate\",\n \"schemaRef\": \"saas-specifications:ComplianceDocumentCandidate\",\n \"description\": \"An untrusted structured content proposal that lands as a FILE for a human to read and commit. Its clauses are validated against the application's accepted document facts before the write; landing is never an approval, a release or a publication. Nothing is sealed \\u2014 the draft is accepted by being committed.\"\n }\n ],\n \"method\": {\n \"//contextSources\": \"DOCUMENT_BLUEPRINT \\u2014 this playbook DRAFTS a governed document, and the catalog is the only thing that says what one must contain. Measured 2026-08-30: `document-definition:public.privacy-notice` requires eight facts; wonder-crm's generated notice declared twenty and matched NONE of them, scoring zero dangling citations throughout \\u2014 internally consistent, and addressing none of what a privacy notice is obliged to address. The catalog had held the answer since it was written and had no runtime lookup of any kind, while this playbook's own skill instructed the drafter to \\\"Read the definition and blueprint\\\": a step it was told to perform and given nothing to perform it on. Deliberately NOT COMPLIANCE_PRIMARY_FACTS: that source carries raw resource declarations and belongs to `refinement.document-facts`, which declares it. A drafter given mechanism directly could write a clause resting on something the application never DECLARED, which is precisely what the fact-binding check exists to refuse \\u2014 this playbook reads the declared `document-facts` family and nothing beneath it.\",\n \"contextSources\": [\"document_blueprint\"],\n \"skillRefs\": [\n \"compliance-document-authoring\"\n ]\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
1
+ {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/refinement.compliance-document-candidate/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,0CAA0C;IACjD,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,YAAY;IACrB,QAAQ,EAAE,gaAAga;IAC1a,eAAe,EAAE;QACf;YACE;;;;;;;;;;;;;;;;;;;;;eAqBG;YACH,MAAM,EAAE,mBAAmB;YAC3B,UAAU,EAAE;gBACV,QAAQ,EAAE,gBAAgB;aAC3B;SACF;KACF;IACD,QAAQ,EAAE;QACR;YACE,QAAQ,EAAE,gBAAgB;SAC3B;KACF;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,+BAA+B;YACzC,WAAW,EAAE,iDAAiD;YAC9D,aAAa,EAAE,0TAA0T;SAC1U;KACF;IACD,QAAQ,EAAE;QACR,kBAAkB,EAAE,glCAAglC;QACpmC,gBAAgB,EAAE,CAAC,oBAAoB,CAAC;QACxC,qBAAqB,EAAE,wYAAwY;QAC/Z,mBAAmB,EAAE,IAAI;QACzB,8BAA8B,EAAE,CAAC,0BAA0B,CAAC;QAC5D,WAAW,EAAE;YACX,+BAA+B;SAChC;KACF;IACD,UAAU,EAAE,iBAAiB;IAC7B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * Migrated from the retired JSON-v1 authoring format at the first-activation\n * hard cut (same ref@version — the companion's assurance-document candidate\n * preparation pins `refinement.compliance-document-candidate@0.1.0` in the\n * installed Framework Knowledge and fails closed without it). This source\n * intentionally omits the superseded per-playbook evaluation-treatment object;\n * generation records that absence rather than fabricating legacy judge behavior.\n */\nexport const playbookDefinition =\n{\n \"ref\": \"refinement.compliance-document-candidate\",\n \"version\": \"0.2.0\",\n \"phase\": \"refinement\",\n \"intent\": \"Propose structured privacy-notice or service-terms candidate content from the application's accepted document facts. The companion agent may draft prose but cannot invent a fact, decide a legal question, approve, release or publish the document: every clause it writes is checked against the `document-facts` family, and a clause asserting a fact the application never declared is refused before it becomes a file.\",\n \"preconditions\": [\n {\n /*\n * The facts this draft SHOULD rest on — expected first, never a gate.\n *\n * Three revisions, and the middle one is the instructive part:\n *\n * 1. Until 2026-08-28 this gated on `compliance-document-fact-projection`, a host-computed\n * projection sealed with a projector identity, source-head digests and per-contribution\n * authority receipts. `artifact_valid` reads LANDED families and a host-computed projection\n * never lands, so the precondition could never be satisfied: this playbook, and with it the\n * whole `refinement` phase, was permanently ineligible from the day it was authored, and\n * nothing reported it because an ineligible playbook never reaches the board. The projection\n * went with the digest demolition (`.claude/rules/one-source-of-truth.md`, Rule 0).\n * 2. It was then re-gated onto `document-facts` with `artifact_valid`, which made it reachable\n * — and blocking. That is the wrong posture for a compliance document: an application must be\n * able to produce its privacy notice today, with the statements it cannot yet establish\n * marked incomplete, and complete them later. A document nobody can produce is worth less\n * than one that states precisely what is missing.\n * 3. `artifact_expected` (SEQUENCING) says facts come first while letting a human run proceed\n * past it. What the old projection PROTECTED — a document may not assert what nobody\n * established — is unaffected: it is a cross-reference check between this draft and the\n * facts file, run before the write, and it refuses INVENTION rather than incompleteness.\n */\n \"kind\": \"artifact_expected\",\n \"selector\": {\n \"family\": \"document-facts\"\n }\n }\n ],\n \"inputs\": [\n {\n \"family\": \"document-facts\"\n }\n ],\n \"outputs\": [\n {\n \"family\": \"compliance-document-candidate\",\n \"schemaRef\": \"saas-specifications:ComplianceDocumentCandidate\",\n \"description\": \"An untrusted structured content proposal that lands as a FILE for a human to read and commit. Its clauses are validated against the application's accepted document facts before the write; landing is never an approval, a release or a publication. Nothing is sealed \\u2014 the draft is accepted by being committed.\"\n }\n ],\n \"method\": {\n \"//contextSources\": \"DOCUMENT_BLUEPRINT \\u2014 this playbook DRAFTS a governed document, and the catalog is the only thing that says what one must contain. Measured 2026-08-30: `document-definition:public.privacy-notice` requires eight facts; wonder-crm's generated notice declared twenty and matched NONE of them, scoring zero dangling citations throughout \\u2014 internally consistent, and addressing none of what a privacy notice is obliged to address. The catalog had held the answer since it was written and had no runtime lookup of any kind, while this playbook's own skill instructed the drafter to \\\"Read the definition and blueprint\\\": a step it was told to perform and given nothing to perform it on. Deliberately NOT COMPLIANCE_PRIMARY_FACTS: that source carries raw resource declarations and belongs to `refinement.document-facts`, which declares it. A drafter given mechanism directly could write a clause resting on something the application never DECLARED, which is precisely what the fact-binding check exists to refuse \\u2014 this playbook reads the declared `document-facts` family and nothing beneath it.\",\n \"contextSources\": [\"document_blueprint\"],\n \"//briefAdequacyGate\": \"The #254 pilot (decision 2026-09-02, built 2026-09-04): this lane is where both recorded promise-gap defects lived, and its context needs vary per document. The gate judges the composed brief once; INSUFFICIENT adds proposed sources for this run only. The exclusion carries the //contextSources boundary above into the mechanism: the gate may never hand this drafter raw resource mechanism.\",\n \"briefAdequacyGate\": true,\n \"briefAdequacyExcludedSources\": [\"compliance_primary_facts\"],\n \"skillRefs\": [\n \"compliance-document-authoring\"\n ]\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
@@ -11,7 +11,7 @@ import { MetaWorkflow_ApprovalPolicy, MetaWorkflow_ContextSource, MetaWorkflow_E
11
11
  * (`.claude/rules/one-source-of-truth.md`, Rule 0).
12
12
  *
13
13
  * The candidate playbook was left gating on that projection, which is why it — and with it the whole
14
- * `refinement` phase — had been permanently ineligible since it was authored: `artifact_valid` reads
14
+ * `refinement` phase — was permanently ineligible from the day it was authored until 2026-08-29: `artifact_valid` reads
15
15
  * LANDED families, and a host-computed projection never lands.
16
16
  *
17
17
  * This is the replacement, and it is deliberately ordinary: the facts become a FILE the application
@@ -24,7 +24,6 @@ export declare const playbookDefinition: {
24
24
  version: string;
25
25
  phase: MetaWorkflow_Phase.REFINEMENT;
26
26
  intent: string;
27
- functionalTopics: any[];
28
27
  preconditions: {
29
28
  kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID;
30
29
  selector: {
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/refinement.document-facts/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,0BAA0B,EAC1B,qBAAqB,EACrB,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,EAE3B,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;;GAmBG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6F+G,CAAC"}
1
+ {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/refinement.document-facts/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,0BAA0B,EAC1B,qBAAqB,EACrB,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,EAE3B,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;;GAmBG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA4F+G,CAAC"}
@@ -11,7 +11,7 @@ import { MetaWorkflow_ApprovalPolicy, MetaWorkflow_ContextSource, MetaWorkflow_E
11
11
  * (`.claude/rules/one-source-of-truth.md`, Rule 0).
12
12
  *
13
13
  * The candidate playbook was left gating on that projection, which is why it — and with it the whole
14
- * `refinement` phase — had been permanently ineligible since it was authored: `artifact_valid` reads
14
+ * `refinement` phase — was permanently ineligible from the day it was authored until 2026-08-29: `artifact_valid` reads
15
15
  * LANDED families, and a host-computed projection never lands.
16
16
  *
17
17
  * This is the replacement, and it is deliberately ordinary: the facts become a FILE the application
@@ -24,23 +24,22 @@ export const playbookDefinition = {
24
24
  version: '0.1.0',
25
25
  phase: MetaWorkflow_Phase.REFINEMENT,
26
26
  intent: "Derive the application's governed-document FACTS from truth it has already accepted — its vision (including the compliance regimes the posture pass recorded), its domain and its requirements — and land them as the `document-facts` family. A fact is a plain statement about how this application actually behaves: what data it holds, how long it keeps it, who it discloses to, what rights it honours. This produces the raw material a privacy notice or service terms is drafted FROM; it never drafts the document, never decides a legal question, and never states a fact the application's own code and accepted specifications do not support. Mechanism facts — retention treatment, data-subject kind, subject export — are read from the resource configurations, which declare what the application will actually do to a row; specifications supply purpose, not mechanism.",
27
- functionalTopics: [],
28
27
  preconditions: [
29
28
  /*
30
- * There is deliberately NO `PHASE_IS` gate, and its absence is the fix for #116.
29
+ * This playbook was where the phase gate was first found, and the last place it was patched.
31
30
  *
32
- * This playbook gated on `PHASE_IS: REFINEMENT` from the day it was authored. `deriveJourneyPhase`
33
- * returns only TOP_DOWN or BOTTOM_UP, so that precondition could never be satisfied and the
34
- * unattended loop could never select this playbook — while nothing reported it, because an
35
- * ineligible playbook never reaches the eligibility board. Audit rule 27 now catches the shape at
36
- * PR time.
31
+ * It gated on `PHASE_IS: REFINEMENT` from the day it was authored, and `deriveJourneyPhase`
32
+ * returned only TOP_DOWN or BOTTOM_UP — so the precondition could never be satisfied and the
33
+ * unattended loop could never select it, while nothing reported it, because an ineligible playbook
34
+ * never reaches the eligibility board (#116). The gate was removed here, and the reasoning offered
35
+ * for removing it applied to all nineteen: gate on the ARTIFACTS a pass actually needs, not on a
36
+ * phase — an evolving application is not in a phase, it is in a STATE, and the state is the tree.
37
37
  *
38
- * Fixed the same way its sibling `refinement.compliance-document-candidate` was on 2026-08-28:
39
- * gate on the ARTIFACTS the pass actually needs, not on a phase. That is also the direction the
40
- * design takes generally — phases are first-run scaffolding, and an evolving application is not in
41
- * a phase, it is in a state, and the state is the tree. The two `ARTIFACT_VALID` gates below are
42
- * the real readiness requirement and are unchanged; nothing about when this pass is SAFE to run
43
- * depended on the phase.
38
+ * The whole mechanism went on 2026-09-04. `PHASE_IS` no longer exists, so its absence here is no
39
+ * longer a decision this playbook makes.
40
+ *
41
+ * The two `ARTIFACT_VALID` gates below are, and always were, the real readiness requirement:
42
+ * nothing about when this pass is SAFE to run depended on the phase.
44
43
  */
45
44
  /*
46
45
  * The vision is required rather than merely declared: `top_down.compliance-posture` records each
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/refinement.document-facts/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,0BAA0B,EAC1B,qBAAqB,EACrB,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,GAE3B,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;;GAmBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,GAAG,EAAE,2BAA2B;IAChC,OAAO,EAAE,OAAO;IAChB,KAAK,EAAE,kBAAkB,CAAC,UAAU;IACpC,MAAM,EACJ,i2BAAi2B;IACn2B,gBAAgB,EAAE,EAAE;IACpB,aAAa,EAAE;QACb;;;;;;;;;;;;;;;WAeG;QACH;;;;;;WAMG;QACH,EAAE,IAAI,EAAE,0BAA0B,CAAC,cAAc,EAAE,QAAQ,EAAE,EAAE,MAAM,EAAE,cAAc,EAAE,EAAE;QACzF;;;;WAIG;QACH,EAAE,IAAI,EAAE,0BAA0B,CAAC,cAAc,EAAE,QAAQ,EAAE,EAAE,MAAM,EAAE,aAAa,EAAE,EAAE;KACzF;IACD,MAAM,EAAE,CAAC,EAAE,MAAM,EAAE,cAAc,EAAE,EAAE,EAAE,MAAM,EAAE,aAAa,EAAE,EAAE,EAAE,MAAM,EAAE,cAAc,EAAE,CAAC;IAC3F,OAAO,EAAE,CAAC;YACR,MAAM,EAAE,gBAAgB;YACxB,SAAS,EAAE,0DAA0D;YACrE,WAAW,EACT,4XAA4X;SAC/X,CAAC;IACF,MAAM,EAAE;QACN;;;;;;;;;;;;;;;;;;;WAmBG;QACH;;;;;;;;;;;;;WAaG;QACH,cAAc,EAAE,CAAC,0BAA0B,CAAC,wBAAwB,EAAE,0BAA0B,CAAC,yBAAyB,CAAC;QAC3H,SAAS,EAAE,CAAC,gBAAgB,CAAC;KAC9B;IACD,QAAQ,EAAE,qBAAqB,CAAC,eAAe;IAC/C,QAAQ,EAAE,2BAA2B,CAAC,cAAc;IACpD,MAAM,EAAE,EAAE,OAAO,EAAE,CAAC,EAAE;IACtB,SAAS,EAAE,0BAA0B,CAAC,aAAa;IACnD;;;;OAIG;CACyI,CAAC","sourcesContent":["import {\n MetaWorkflow_ApprovalPolicy,\n MetaWorkflow_ContextSource,\n MetaWorkflow_Executor,\n MetaWorkflow_FailurePolicy,\n MetaWorkflow_Phase,\n MetaWorkflow_PredicateKind,\n type MetaWorkflowPlaybookAuthoring,\n} from '@wildo-ai/saas-specifications/application-creation';\n\n/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * ## Why this playbook exists\n *\n * `refinement.compliance-document-candidate` drafts a governed document, and a governed document may\n * not assert anything about the application that nobody established. Until 2026-08-28 the fact set it\n * rested on was a HOST-COMPUTED projection sealed with a projector identity, source-head digests and\n * per-contribution authority receipts — none of it branchable on git, all of it deleted\n * (`.claude/rules/one-source-of-truth.md`, Rule 0).\n *\n * The candidate playbook was left gating on that projection, which is why it — and with it the whole\n * `refinement` phase — had been permanently ineligible since it was authored: `artifact_valid` reads\n * LANDED families, and a host-computed projection never lands.\n *\n * This is the replacement, and it is deliberately ordinary: the facts become a FILE the application\n * commits, like every other family. What used to be enforced by a seal is now enforced by a pure\n * cross-reference check at the drafting boundary — a clause citing a fact this file does not declare\n * is refused before it can be written.\n */\nexport const playbookDefinition = {\n ref: 'refinement.document-facts',\n version: '0.1.0',\n phase: MetaWorkflow_Phase.REFINEMENT,\n intent:\n \"Derive the application's governed-document FACTS from truth it has already accepted — its vision (including the compliance regimes the posture pass recorded), its domain and its requirements — and land them as the `document-facts` family. A fact is a plain statement about how this application actually behaves: what data it holds, how long it keeps it, who it discloses to, what rights it honours. This produces the raw material a privacy notice or service terms is drafted FROM; it never drafts the document, never decides a legal question, and never states a fact the application's own code and accepted specifications do not support. Mechanism facts — retention treatment, data-subject kind, subject export — are read from the resource configurations, which declare what the application will actually do to a row; specifications supply purpose, not mechanism.\",\n functionalTopics: [],\n preconditions: [\n /*\n * There is deliberately NO `PHASE_IS` gate, and its absence is the fix for #116.\n *\n * This playbook gated on `PHASE_IS: REFINEMENT` from the day it was authored. `deriveJourneyPhase`\n * returns only TOP_DOWN or BOTTOM_UP, so that precondition could never be satisfied and the\n * unattended loop could never select this playbook — while nothing reported it, because an\n * ineligible playbook never reaches the eligibility board. Audit rule 27 now catches the shape at\n * PR time.\n *\n * Fixed the same way its sibling `refinement.compliance-document-candidate` was on 2026-08-28:\n * gate on the ARTIFACTS the pass actually needs, not on a phase. That is also the direction the\n * design takes generally — phases are first-run scaffolding, and an evolving application is not in\n * a phase, it is in a state, and the state is the tree. The two `ARTIFACT_VALID` gates below are\n * the real readiness requirement and are unchanged; nothing about when this pass is SAFE to run\n * depended on the phase.\n */\n /*\n * The vision is required rather than merely declared: `top_down.compliance-posture` records each\n * applicable regime as a `compliance`-kind constraint there, and those constraints are what tell\n * this pass WHICH facts a later document will need. A derivation with no regime in view produces a\n * plausible generic fact set — the exact failure `compliance-document-system.md` forbids (\"do not\n * generate legal text from a generic SaaS category when application facts are absent\").\n */\n { kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'vision-brief' } },\n /*\n * The domain plan is where the application's resources and their data actually live. Retention,\n * data categories and disclosure facts are read from it; without it this pass would be inventing\n * what the product stores.\n */\n { kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'domain-plan' } },\n ],\n inputs: [{ family: 'vision-brief' }, { family: 'domain-plan' }, { family: 'requirements' }],\n outputs: [{\n family: 'document-facts',\n schemaRef: 'saas-specifications:ApplicationDocumentFactSpecification',\n description:\n \"The application's declared governed-document facts, one declaration per fact, each either KNOWN with its value or NOT_APPLICABLE with a reason. Authority is APPLICATION_SPECIFICATION throughout: these are facts the application's own accepted specifications establish. A fact needing a named human decision is deliberately ABSENT rather than dressed in an authority nobody holds.\",\n }],\n method: {\n /*\n * The resource declarations reach the brief through this, and nothing else does.\n *\n * This playbook's intent and its method have said since the day they were authored that mechanism\n * facts \"are read from the resource configurations\". They were not: the `compliance-primary-facts`\n * behavior existed and answered correctly, and no playbook declared it, so the derivation the\n * method describes could not happen. Its first live run (wonder-crm, 2026-08-29) landed two facts,\n * both paraphrased from vision prose, neither citing a declaration — a schema-valid artifact that\n * was wrong about where it came from, which is the one failure mode a governed document cannot\n * survive.\n *\n * NOT `WORKSPACE_TRUTH`: that section carries module ids and schema FIELD NAMES for a build\n * planner. A field's name says nothing about whether erasing its subject scrubs it.\n *\n * The run immediately after wiring it landed a fact reading \"contact records are retained and\n * impersonalized on erasure; workspace, workspace-member, company, pipeline-stage, deal, next-step\n * and interaction are declared RETAIN_ONLY\" — per resource, from the declarations. The run before\n * it, on the same application and the same method prose, had produced two paraphrases of the\n * vision. Nothing about the guidance changed; the evidence arrived.\n */\n /*\n * DOCUMENT_FACT_OBLIGATIONS supplies the second half, and it is the one this playbook had never\n * been given: the NAMES.\n *\n * COMPLIANCE_PRIMARY_FACTS made the answers true — the run after wiring it landed a per-resource\n * erasure fact instead of two paraphrases of the vision. It did nothing about what those answers\n * are CALLED, and a fact's ref is stamped from the slug this playbook chooses. Measured 2026-08-30:\n * twenty facts declared, ZERO of the eight a privacy notice requires, because the names were\n * semantically adjacent and lexically disjoint. True answers, uncitable.\n *\n * The method below already asks for stable descriptive slugs and names three of the eight as\n * examples, and has since 2026-08-28. That is prose, and the churn was measured with it in place.\n * This supplies the closed set itself, which the engine catalog has held all along.\n */\n contextSources: [MetaWorkflow_ContextSource.COMPLIANCE_PRIMARY_FACTS, MetaWorkflow_ContextSource.DOCUMENT_FACT_OBLIGATIONS],\n skillRefs: ['journey-status'],\n },\n executor: MetaWorkflow_Executor.COMPANION_AGENT,\n approval: MetaWorkflow_ApprovalPolicy.APPROVE_RESULT,\n budget: { maxRuns: 3 },\n onFailure: MetaWorkflow_FailurePolicy.KEEP_AND_FLAG,\n /*\n * `guidance` is deliberately absent: the method prose is the single source of truth in `method.md`,\n * and the generator renders it (partials + references expanded) and injects it as `method.guidance`.\n * Declaring it here would be a second copy that drifts — the folder contract rejects an inline one.\n */\n} satisfies Omit<MetaWorkflowPlaybookAuthoring, 'method'> & { method: Omit<NonNullable<MetaWorkflowPlaybookAuthoring['method']>, 'guidance'> };\n"]}
1
+ {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/refinement.document-facts/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,0BAA0B,EAC1B,qBAAqB,EACrB,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,GAE3B,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;;GAmBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,GAAG,EAAE,2BAA2B;IAChC,OAAO,EAAE,OAAO;IAChB,KAAK,EAAE,kBAAkB,CAAC,UAAU;IACpC,MAAM,EACJ,i2BAAi2B;IACn2B,aAAa,EAAE;QACb;;;;;;;;;;;;;;;WAeG;QACH;;;;;;WAMG;QACH,EAAE,IAAI,EAAE,0BAA0B,CAAC,cAAc,EAAE,QAAQ,EAAE,EAAE,MAAM,EAAE,cAAc,EAAE,EAAE;QACzF;;;;WAIG;QACH,EAAE,IAAI,EAAE,0BAA0B,CAAC,cAAc,EAAE,QAAQ,EAAE,EAAE,MAAM,EAAE,aAAa,EAAE,EAAE;KACzF;IACD,MAAM,EAAE,CAAC,EAAE,MAAM,EAAE,cAAc,EAAE,EAAE,EAAE,MAAM,EAAE,aAAa,EAAE,EAAE,EAAE,MAAM,EAAE,cAAc,EAAE,CAAC;IAC3F,OAAO,EAAE,CAAC;YACR,MAAM,EAAE,gBAAgB;YACxB,SAAS,EAAE,0DAA0D;YACrE,WAAW,EACT,4XAA4X;SAC/X,CAAC;IACF,MAAM,EAAE;QACN;;;;;;;;;;;;;;;;;;;WAmBG;QACH;;;;;;;;;;;;;WAaG;QACH,cAAc,EAAE,CAAC,0BAA0B,CAAC,wBAAwB,EAAE,0BAA0B,CAAC,yBAAyB,CAAC;QAC3H,SAAS,EAAE,CAAC,gBAAgB,CAAC;KAC9B;IACD,QAAQ,EAAE,qBAAqB,CAAC,eAAe;IAC/C,QAAQ,EAAE,2BAA2B,CAAC,cAAc;IACpD,MAAM,EAAE,EAAE,OAAO,EAAE,CAAC,EAAE;IACtB,SAAS,EAAE,0BAA0B,CAAC,aAAa;IACnD;;;;OAIG;CACyI,CAAC","sourcesContent":["import {\n MetaWorkflow_ApprovalPolicy,\n MetaWorkflow_ContextSource,\n MetaWorkflow_Executor,\n MetaWorkflow_FailurePolicy,\n MetaWorkflow_Phase,\n MetaWorkflow_PredicateKind,\n type MetaWorkflowPlaybookAuthoring,\n} from '@wildo-ai/saas-specifications/application-creation';\n\n/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * ## Why this playbook exists\n *\n * `refinement.compliance-document-candidate` drafts a governed document, and a governed document may\n * not assert anything about the application that nobody established. Until 2026-08-28 the fact set it\n * rested on was a HOST-COMPUTED projection sealed with a projector identity, source-head digests and\n * per-contribution authority receipts — none of it branchable on git, all of it deleted\n * (`.claude/rules/one-source-of-truth.md`, Rule 0).\n *\n * The candidate playbook was left gating on that projection, which is why it — and with it the whole\n * `refinement` phase — was permanently ineligible from the day it was authored until 2026-08-29: `artifact_valid` reads\n * LANDED families, and a host-computed projection never lands.\n *\n * This is the replacement, and it is deliberately ordinary: the facts become a FILE the application\n * commits, like every other family. What used to be enforced by a seal is now enforced by a pure\n * cross-reference check at the drafting boundary — a clause citing a fact this file does not declare\n * is refused before it can be written.\n */\nexport const playbookDefinition = {\n ref: 'refinement.document-facts',\n version: '0.1.0',\n phase: MetaWorkflow_Phase.REFINEMENT,\n intent:\n \"Derive the application's governed-document FACTS from truth it has already accepted — its vision (including the compliance regimes the posture pass recorded), its domain and its requirements — and land them as the `document-facts` family. A fact is a plain statement about how this application actually behaves: what data it holds, how long it keeps it, who it discloses to, what rights it honours. This produces the raw material a privacy notice or service terms is drafted FROM; it never drafts the document, never decides a legal question, and never states a fact the application's own code and accepted specifications do not support. Mechanism facts — retention treatment, data-subject kind, subject export — are read from the resource configurations, which declare what the application will actually do to a row; specifications supply purpose, not mechanism.\",\n preconditions: [\n /*\n * This playbook was where the phase gate was first found, and the last place it was patched.\n *\n * It gated on `PHASE_IS: REFINEMENT` from the day it was authored, and `deriveJourneyPhase`\n * returned only TOP_DOWN or BOTTOM_UP — so the precondition could never be satisfied and the\n * unattended loop could never select it, while nothing reported it, because an ineligible playbook\n * never reaches the eligibility board (#116). The gate was removed here, and the reasoning offered\n * for removing it applied to all nineteen: gate on the ARTIFACTS a pass actually needs, not on a\n * phase — an evolving application is not in a phase, it is in a STATE, and the state is the tree.\n *\n * The whole mechanism went on 2026-09-04. `PHASE_IS` no longer exists, so its absence here is no\n * longer a decision this playbook makes.\n *\n * The two `ARTIFACT_VALID` gates below are, and always were, the real readiness requirement:\n * nothing about when this pass is SAFE to run depended on the phase.\n */\n /*\n * The vision is required rather than merely declared: `top_down.compliance-posture` records each\n * applicable regime as a `compliance`-kind constraint there, and those constraints are what tell\n * this pass WHICH facts a later document will need. A derivation with no regime in view produces a\n * plausible generic fact set — the exact failure `compliance-document-system.md` forbids (\"do not\n * generate legal text from a generic SaaS category when application facts are absent\").\n */\n { kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'vision-brief' } },\n /*\n * The domain plan is where the application's resources and their data actually live. Retention,\n * data categories and disclosure facts are read from it; without it this pass would be inventing\n * what the product stores.\n */\n { kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'domain-plan' } },\n ],\n inputs: [{ family: 'vision-brief' }, { family: 'domain-plan' }, { family: 'requirements' }],\n outputs: [{\n family: 'document-facts',\n schemaRef: 'saas-specifications:ApplicationDocumentFactSpecification',\n description:\n \"The application's declared governed-document facts, one declaration per fact, each either KNOWN with its value or NOT_APPLICABLE with a reason. Authority is APPLICATION_SPECIFICATION throughout: these are facts the application's own accepted specifications establish. A fact needing a named human decision is deliberately ABSENT rather than dressed in an authority nobody holds.\",\n }],\n method: {\n /*\n * The resource declarations reach the brief through this, and nothing else does.\n *\n * This playbook's intent and its method have said since the day they were authored that mechanism\n * facts \"are read from the resource configurations\". They were not: the `compliance-primary-facts`\n * behavior existed and answered correctly, and no playbook declared it, so the derivation the\n * method describes could not happen. Its first live run (wonder-crm, 2026-08-29) landed two facts,\n * both paraphrased from vision prose, neither citing a declaration — a schema-valid artifact that\n * was wrong about where it came from, which is the one failure mode a governed document cannot\n * survive.\n *\n * NOT `WORKSPACE_TRUTH`: that section carries module ids and schema FIELD NAMES for a build\n * planner. A field's name says nothing about whether erasing its subject scrubs it.\n *\n * The run immediately after wiring it landed a fact reading \"contact records are retained and\n * impersonalized on erasure; workspace, workspace-member, company, pipeline-stage, deal, next-step\n * and interaction are declared RETAIN_ONLY\" — per resource, from the declarations. The run before\n * it, on the same application and the same method prose, had produced two paraphrases of the\n * vision. Nothing about the guidance changed; the evidence arrived.\n */\n /*\n * DOCUMENT_FACT_OBLIGATIONS supplies the second half, and it is the one this playbook had never\n * been given: the NAMES.\n *\n * COMPLIANCE_PRIMARY_FACTS made the answers true — the run after wiring it landed a per-resource\n * erasure fact instead of two paraphrases of the vision. It did nothing about what those answers\n * are CALLED, and a fact's ref is stamped from the slug this playbook chooses. Measured 2026-08-30:\n * twenty facts declared, ZERO of the eight a privacy notice requires, because the names were\n * semantically adjacent and lexically disjoint. True answers, uncitable.\n *\n * The method below already asks for stable descriptive slugs and names three of the eight as\n * examples, and has since 2026-08-28. That is prose, and the churn was measured with it in place.\n * This supplies the closed set itself, which the engine catalog has held all along.\n */\n contextSources: [MetaWorkflow_ContextSource.COMPLIANCE_PRIMARY_FACTS, MetaWorkflow_ContextSource.DOCUMENT_FACT_OBLIGATIONS],\n skillRefs: ['journey-status'],\n },\n executor: MetaWorkflow_Executor.COMPANION_AGENT,\n approval: MetaWorkflow_ApprovalPolicy.APPROVE_RESULT,\n budget: { maxRuns: 3 },\n onFailure: MetaWorkflow_FailurePolicy.KEEP_AND_FLAG,\n /*\n * `guidance` is deliberately absent: the method prose is the single source of truth in `method.md`,\n * and the generator renders it (partials + references expanded) and injects it as `method.guidance`.\n * Declaring it here would be a second copy that drifts — the folder contract rejects an inline one.\n */\n} satisfies Omit<MetaWorkflowPlaybookAuthoring, 'method'> & { method: Omit<NonNullable<MetaWorkflowPlaybookAuthoring['method']>, 'guidance'> };\n"]}
@@ -9,14 +9,10 @@
9
9
  */
10
10
  export declare const playbookDefinition: {
11
11
  readonly ref: "top_down.brand-identity";
12
- readonly version: "0.1.0";
12
+ readonly version: "0.1.1";
13
13
  readonly phase: "top_down";
14
14
  readonly 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.";
15
- readonly functionalTopics: readonly [];
16
15
  readonly preconditions: readonly [{
17
- readonly kind: "phase_is";
18
- readonly phase: "top_down";
19
- }, {
20
16
  readonly kind: "artifact_exists";
21
17
  readonly selector: {
22
18
  readonly family: "vision-brief";
@@ -27,6 +23,8 @@ export declare const playbookDefinition: {
27
23
  }, {
28
24
  readonly family: "market-snapshot";
29
25
  readonly intent: "voice";
26
+ }, {
27
+ readonly family: "brand-brief";
30
28
  }];
31
29
  readonly outputs: readonly [{
32
30
  readonly family: "brand-brief";
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.brand-identity/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA4FrB,CAAC"}
1
+ {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.brand-identity/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA2FrB,CAAC"}
@@ -9,17 +9,16 @@
9
9
  */
10
10
  export const playbookDefinition = {
11
11
  "ref": "top_down.brand-identity",
12
- "version": "0.1.0",
12
+ "version": "0.1.1",
13
13
  "phase": "top_down",
14
14
  "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.",
15
- "functionalTopics": [],
16
15
  "preconditions": [
17
- { "kind": "phase_is", "phase": "top_down" },
18
16
  { "kind": "artifact_exists", "selector": { "family": "vision-brief" } }
19
17
  ],
20
18
  "inputs": [
21
19
  { "family": "vision-brief" },
22
- { "family": "market-snapshot", "intent": "voice" }
20
+ { "family": "market-snapshot", "intent": "voice" },
21
+ { "family": "brand-brief" }
23
22
  ],
24
23
  "outputs": [
25
24
  {
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.brand-identity/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,yBAAyB;IAChC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,UAAU;IACnB,QAAQ,EAAE,07BAA07B;IACp8B,kBAAkB,EAAE,EAAE;IACtB,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,UAAU,EAAE,OAAO,EAAE,UAAU,EAAE;QAC3C,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,cAAc,EAAE,EAAE;KACxE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,cAAc,EAAE;QAC5B,EAAE,QAAQ,EAAE,iBAAiB,EAAE,QAAQ,EAAE,OAAO,EAAE;KACnD;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,aAAa;YACvB,WAAW,EAAE,mCAAmC;YAChD,aAAa,EAAE,oXAAoX;SACpY;KACF;IACD,QAAQ,EAAE;QACR,WAAW,EAAE,CAAC,gBAAgB,EAAE,sBAAsB,CAAC;QACvD,aAAa,EAAE;YACb,WAAW,EAAE;gBACX;oBACE,KAAK,EAAE,YAAY;oBACnB,UAAU,EAAE,0IAA0I;oBACtJ,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,eAAe;oBACtB,UAAU,EAAE,mIAAmI;oBAC/I,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,gBAAgB;oBACvB,UAAU,EAAE,yJAAyJ;oBACrK,MAAM,EAAE,QAAQ;oBAChB,SAAS,EAAE,CAAC,kBAAkB,EAAE,UAAU,EAAE,YAAY,EAAE,gBAAgB,EAAE,eAAe,EAAE,QAAQ,EAAE,QAAQ,CAAC;iBACjH;gBACD;oBACE,KAAK,EAAE,aAAa;oBACpB,UAAU,EAAE,kKAAkK;oBAC9K,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,gBAAgB;oBACvB,UAAU,EAAE,yJAAyJ;oBACrK,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,YAAY;oBACnB,UAAU,EAAE,iLAAiL;oBAC7L,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,iBAAiB;oBACxB,UAAU,EAAE,oNAAoN;oBAChO,MAAM,EAAE,QAAQ;oBAChB,SAAS,EAAE,CAAC,sBAAsB,EAAE,aAAa,EAAE,kBAAkB,CAAC;iBACvE;gBACD;oBACE,KAAK,EAAE,uBAAuB;oBAC9B,UAAU,EAAE,yHAAyH;oBACrI,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,aAAa;oBACpB,UAAU,EAAE,qGAAqG;oBACjH,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,qBAAqB;oBAC5B,UAAU,EAAE,sJAAsJ;oBAClK,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,oBAAoB;oBAC3B,UAAU,EAAE,8KAA8K;oBAC1L,MAAM,EAAE,WAAW;iBACpB;aACF;SACF;KACF;IACD,UAAU,EAAE,iBAAiB;IAC7B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * The structured method remains intentionally rich: its intent, inputs, output\n * contracts, elicitation, deterministic verification and skill routing are the\n * application knowledge a later generic assessment loop composes. This source\n * intentionally omits the superseded per-playbook evaluation-treatment object;\n * generation records that absence rather than fabricating legacy judge behavior.\n */\nexport const playbookDefinition = \n{\n \"ref\": \"top_down.brand-identity\",\n \"version\": \"0.1.0\",\n \"phase\": \"top_down\",\n \"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.\",\n \"functionalTopics\": [],\n \"preconditions\": [\n { \"kind\": \"phase_is\", \"phase\": \"top_down\" },\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"vision-brief\" } }\n ],\n \"inputs\": [\n { \"family\": \"vision-brief\" },\n { \"family\": \"market-snapshot\", \"intent\": \"voice\" }\n ],\n \"outputs\": [\n {\n \"family\": \"brand-brief\",\n \"schemaRef\": \"saas-specifications:BrandSnapshot\",\n \"description\": \"The visual-identity artifact — one BrandSnapshot per product (name + logo direction + visual tone; resolvedAssets left empty for the companion logo step to populate). Read by the companion logo generation step (which produces the master + derived assets) and, via resolvedAssets, by every downstream logo/favicon/brand-image consumer. Validated by validateBrandSnapshot.\"\n }\n ],\n \"method\": {\n \"skillRefs\": [\"journey-status\", \"brand-logo-authoring\"],\n \"elicitation\": {\n \"questions\": [\n {\n \"ref\": \"brand-name\",\n \"question\": \"What is the exact, case-sensitive brand name the logo should render (e.g. \\\"Northstar Tasks\\\")? This is the string every surface prints.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"brand-tagline\",\n \"question\": \"Is there a tagline / supporting line to lock up with the name (e.g. \\\"Ship the week, not the meeting.\\\")? Answer \\\"none\\\" if not.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"logo-mark-type\",\n \"question\": \"Which logo archetype fits the brand? A combination mark (symbol + wordmark) is the safe default — it yields both a header lockup and a square app icon.\",\n \"kind\": \"choice\",\n \"options\": [\"combination_mark\", \"wordmark\", \"lettermark\", \"pictorial_mark\", \"abstract_mark\", \"emblem\", \"mascot\"]\n },\n {\n \"ref\": \"logo-motifs\",\n \"question\": \"What concrete visual elements should the mark include (short noun phrases, e.g. \\\"a rising checkmark\\\", \\\"concentric rings\\\")? Answer \\\"none\\\" to leave it open.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"logo-symbolism\",\n \"question\": \"What meaning should the mark evoke (e.g. \\\"momentum\\\", \\\"clarity\\\", \\\"trust\\\")? Derive this from the product's mission / idea rather than inventing it.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"logo-avoid\",\n \"question\": \"What imagery should the mark AVOID (e.g. \\\"no gradients\\\", \\\"no literal robots\\\", \\\"no clip-art gears\\\")? These are the negative-prompt guardrails that keep the output usable.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"logo-background\",\n \"question\": \"How should the master logo be composed? A transparent, isolated mark is the default — it rasterizes cleanly into favicons and monochrome / dark-light variants. Choose otherwise only if the brand truly needs it.\",\n \"kind\": \"choice\",\n \"options\": [\"transparent_isolated\", \"solid_field\", \"contextual_scene\"]\n },\n {\n \"ref\": \"visual-style-keywords\",\n \"question\": \"In 3–7 concrete adjectives, what should the brand LOOK like (e.g. \\\"geometric\\\", \\\"minimal\\\", \\\"warm\\\", \\\"editorial\\\")?\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"visual-mood\",\n \"question\": \"In one sentence, what feeling should the imagery leave (e.g. \\\"calm, precise, quietly confident\\\")?\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"visual-color-intent\",\n \"question\": \"Describe the color story in prose (e.g. \\\"cool blues grounded by a warm accent\\\"). Prose, not hex — the concrete palette lives in the design system.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"visual-color-seeds\",\n \"question\": \"Has the brand already committed to specific hex colors that the mark must agree with? If so, list them; otherwise answer \\\"none\\\" and let the design system own the palette.\",\n \"kind\": \"free_text\"\n }\n ]\n }\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
1
+ {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.brand-identity/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,yBAAyB;IAChC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,UAAU;IACnB,QAAQ,EAAE,07BAA07B;IACp8B,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,cAAc,EAAE,EAAE;KACxE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,cAAc,EAAE;QAC5B,EAAE,QAAQ,EAAE,iBAAiB,EAAE,QAAQ,EAAE,OAAO,EAAE;QAClD,EAAE,QAAQ,EAAE,aAAa,EAAE;KAC5B;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,aAAa;YACvB,WAAW,EAAE,mCAAmC;YAChD,aAAa,EAAE,oXAAoX;SACpY;KACF;IACD,QAAQ,EAAE;QACR,WAAW,EAAE,CAAC,gBAAgB,EAAE,sBAAsB,CAAC;QACvD,aAAa,EAAE;YACb,WAAW,EAAE;gBACX;oBACE,KAAK,EAAE,YAAY;oBACnB,UAAU,EAAE,0IAA0I;oBACtJ,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,eAAe;oBACtB,UAAU,EAAE,mIAAmI;oBAC/I,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,gBAAgB;oBACvB,UAAU,EAAE,yJAAyJ;oBACrK,MAAM,EAAE,QAAQ;oBAChB,SAAS,EAAE,CAAC,kBAAkB,EAAE,UAAU,EAAE,YAAY,EAAE,gBAAgB,EAAE,eAAe,EAAE,QAAQ,EAAE,QAAQ,CAAC;iBACjH;gBACD;oBACE,KAAK,EAAE,aAAa;oBACpB,UAAU,EAAE,kKAAkK;oBAC9K,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,gBAAgB;oBACvB,UAAU,EAAE,yJAAyJ;oBACrK,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,YAAY;oBACnB,UAAU,EAAE,iLAAiL;oBAC7L,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,iBAAiB;oBACxB,UAAU,EAAE,oNAAoN;oBAChO,MAAM,EAAE,QAAQ;oBAChB,SAAS,EAAE,CAAC,sBAAsB,EAAE,aAAa,EAAE,kBAAkB,CAAC;iBACvE;gBACD;oBACE,KAAK,EAAE,uBAAuB;oBAC9B,UAAU,EAAE,yHAAyH;oBACrI,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,aAAa;oBACpB,UAAU,EAAE,qGAAqG;oBACjH,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,qBAAqB;oBAC5B,UAAU,EAAE,sJAAsJ;oBAClK,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,oBAAoB;oBAC3B,UAAU,EAAE,8KAA8K;oBAC1L,MAAM,EAAE,WAAW;iBACpB;aACF;SACF;KACF;IACD,UAAU,EAAE,iBAAiB;IAC7B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * The structured method remains intentionally rich: its intent, inputs, output\n * contracts, elicitation, deterministic verification and skill routing are the\n * application knowledge a later generic assessment loop composes. This source\n * intentionally omits the superseded per-playbook evaluation-treatment object;\n * generation records that absence rather than fabricating legacy judge behavior.\n */\nexport const playbookDefinition = \n{\n \"ref\": \"top_down.brand-identity\",\n \"version\": \"0.1.1\",\n \"phase\": \"top_down\",\n \"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.\",\n \"preconditions\": [\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"vision-brief\" } }\n ],\n \"inputs\": [\n { \"family\": \"vision-brief\" },\n { \"family\": \"market-snapshot\", \"intent\": \"voice\" },\n { \"family\": \"brand-brief\" }\n ],\n \"outputs\": [\n {\n \"family\": \"brand-brief\",\n \"schemaRef\": \"saas-specifications:BrandSnapshot\",\n \"description\": \"The visual-identity artifact — one BrandSnapshot per product (name + logo direction + visual tone; resolvedAssets left empty for the companion logo step to populate). Read by the companion logo generation step (which produces the master + derived assets) and, via resolvedAssets, by every downstream logo/favicon/brand-image consumer. Validated by validateBrandSnapshot.\"\n }\n ],\n \"method\": {\n \"skillRefs\": [\"journey-status\", \"brand-logo-authoring\"],\n \"elicitation\": {\n \"questions\": [\n {\n \"ref\": \"brand-name\",\n \"question\": \"What is the exact, case-sensitive brand name the logo should render (e.g. \\\"Northstar Tasks\\\")? This is the string every surface prints.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"brand-tagline\",\n \"question\": \"Is there a tagline / supporting line to lock up with the name (e.g. \\\"Ship the week, not the meeting.\\\")? Answer \\\"none\\\" if not.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"logo-mark-type\",\n \"question\": \"Which logo archetype fits the brand? A combination mark (symbol + wordmark) is the safe default — it yields both a header lockup and a square app icon.\",\n \"kind\": \"choice\",\n \"options\": [\"combination_mark\", \"wordmark\", \"lettermark\", \"pictorial_mark\", \"abstract_mark\", \"emblem\", \"mascot\"]\n },\n {\n \"ref\": \"logo-motifs\",\n \"question\": \"What concrete visual elements should the mark include (short noun phrases, e.g. \\\"a rising checkmark\\\", \\\"concentric rings\\\")? Answer \\\"none\\\" to leave it open.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"logo-symbolism\",\n \"question\": \"What meaning should the mark evoke (e.g. \\\"momentum\\\", \\\"clarity\\\", \\\"trust\\\")? Derive this from the product's mission / idea rather than inventing it.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"logo-avoid\",\n \"question\": \"What imagery should the mark AVOID (e.g. \\\"no gradients\\\", \\\"no literal robots\\\", \\\"no clip-art gears\\\")? These are the negative-prompt guardrails that keep the output usable.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"logo-background\",\n \"question\": \"How should the master logo be composed? A transparent, isolated mark is the default — it rasterizes cleanly into favicons and monochrome / dark-light variants. Choose otherwise only if the brand truly needs it.\",\n \"kind\": \"choice\",\n \"options\": [\"transparent_isolated\", \"solid_field\", \"contextual_scene\"]\n },\n {\n \"ref\": \"visual-style-keywords\",\n \"question\": \"In 3–7 concrete adjectives, what should the brand LOOK like (e.g. \\\"geometric\\\", \\\"minimal\\\", \\\"warm\\\", \\\"editorial\\\")?\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"visual-mood\",\n \"question\": \"In one sentence, what feeling should the imagery leave (e.g. \\\"calm, precise, quietly confident\\\")?\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"visual-color-intent\",\n \"question\": \"Describe the color story in prose (e.g. \\\"cool blues grounded by a warm accent\\\"). Prose, not hex — the concrete palette lives in the design system.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"visual-color-seeds\",\n \"question\": \"Has the brand already committed to specific hex colors that the mark must agree with? If so, list them; otherwise answer \\\"none\\\" and let the design system own the palette.\",\n \"kind\": \"free_text\"\n }\n ]\n }\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
@@ -5,18 +5,12 @@ export declare const playbookDefinition: {
5
5
  version: string;
6
6
  phase: MetaWorkflow_Phase.TOP_DOWN;
7
7
  intent: string;
8
- functionalTopics: any[];
9
- preconditions: ({
10
- kind: MetaWorkflow_PredicateKind.PHASE_IS;
11
- phase: MetaWorkflow_Phase.TOP_DOWN;
12
- selector?: undefined;
13
- } | {
8
+ preconditions: {
14
9
  kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID;
15
10
  selector: {
16
11
  family: string;
17
12
  };
18
- phase?: undefined;
19
- })[];
13
+ }[];
20
14
  inputs: ({
21
15
  family: string;
22
16
  intent: MetaWorkflow_ArtifactIntent.AUDIENCE;
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.business-model/playbook.definition.ts"],"names":[],"mappings":"AAIA,OAAO,EACL,oCAAoC,EACpC,kCAAkC,EAClC,wCAAwC,EACxC,+BAA+B,EAC/B,gCAAgC,EAChC,sCAAsC,EACtC,0CAA0C,EAC1C,6CAA6C,EAC7C,8BAA8B,EAC9B,oCAAoC,EACpC,+BAA+B,EAC/B,6BAA6B,EAC7B,+BAA+B,EAC/B,sCAAsC,EACtC,kDAAkD,EACnD,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EACL,2BAA2B,EAC3B,oCAAoC,EACpC,2BAA2B,EAC3B,qBAAqB,EACrB,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,EAE3B,MAAM,oDAAoD,CAAC;AAE5D,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6E+G,CAAC;AAE/I,eAAO,MAAM,8BAA8B;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgDW,CAAC;AAEvD,eAAO,MAAM,yBAAyB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAoHW,CAAC"}
1
+ {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.business-model/playbook.definition.ts"],"names":[],"mappings":"AAIA,OAAO,EACL,oCAAoC,EACpC,kCAAkC,EAClC,wCAAwC,EACxC,+BAA+B,EAC/B,gCAAgC,EAChC,sCAAsC,EACtC,0CAA0C,EAC1C,6CAA6C,EAC7C,8BAA8B,EAC9B,oCAAoC,EACpC,+BAA+B,EAC/B,6BAA6B,EAC7B,+BAA+B,EAC/B,sCAAsC,EACtC,kDAAkD,EACnD,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EACL,2BAA2B,EAC3B,oCAAoC,EACpC,2BAA2B,EAC3B,qBAAqB,EACrB,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,EAE3B,MAAM,oDAAoD,CAAC;AAE5D,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA2E+G,CAAC;AAE/I,eAAO,MAAM,8BAA8B;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgDW,CAAC;AAEvD,eAAO,MAAM,yBAAyB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAoHW,CAAC"}
@@ -5,9 +5,7 @@ export const playbookDefinition = {
5
5
  version: '0.1.0',
6
6
  phase: MetaWorkflow_Phase.TOP_DOWN,
7
7
  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.",
8
- functionalTopics: [],
9
8
  preconditions: [
10
- { kind: MetaWorkflow_PredicateKind.PHASE_IS, phase: MetaWorkflow_Phase.TOP_DOWN },
11
9
  // The two families whose refs this artifact cross-links. `requirements` is required rather than
12
10
  // merely declared because `includesRequirementRefs` is the traceability the foundation reads to
13
11
  // derive the billing capability — a plan that unlocks nothing nameable teaches it nothing.