@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
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "framework-topics",
3
3
  "metadata": {
4
- "generatedAt": "2026-08-30T22:14:50.331Z",
4
+ "generatedAt": "2026-08-29T22:33:33.791Z",
5
5
  "description": "Topic registry derived from extracted framework-knowledge tags."
6
6
  },
7
7
  "entries": {
@@ -1560,15 +1560,6 @@
1560
1560
  "referenceFilePath": "references/market.trigger.kind.md",
1561
1561
  "sourceReferenceCount": 1
1562
1562
  },
1563
- "placement-plan.config": {
1564
- "topicId": "placement-plan.config",
1565
- "title": "Placement Plan Config",
1566
- "categories": [
1567
- "placement-plan"
1568
- ],
1569
- "referenceFilePath": "references/placement-plan.config.md",
1570
- "sourceReferenceCount": 1
1571
- },
1572
1563
  "platform.config.application-database": {
1573
1564
  "topicId": "platform.config.application-database",
1574
1565
  "title": "Platform Config Application Database",
@@ -2091,6 +2082,16 @@
2091
2082
  "referenceFilePath": "references/saas.data-seeding.scope-iteration-strategy.md",
2092
2083
  "sourceReferenceCount": 1
2093
2084
  },
2085
+ "saas.external-data.admin-endpoints": {
2086
+ "topicId": "saas.external-data.admin-endpoints",
2087
+ "title": "Saas External Data Admin Endpoints",
2088
+ "categories": [
2089
+ "saas",
2090
+ "saas.external-data"
2091
+ ],
2092
+ "referenceFilePath": "references/saas.external-data.admin-endpoints.md",
2093
+ "sourceReferenceCount": 1
2094
+ },
2094
2095
  "saas.external-providers.backend-provider-registry.runtime-filter": {
2095
2096
  "topicId": "saas.external-providers.backend-provider-registry.runtime-filter",
2096
2097
  "title": "Saas External Providers Backend Provider Registry Runtime Filter",
@@ -2580,28 +2581,6 @@
2580
2581
  "referenceFilePath": "references/saas.frontend.resource-ui-behavior-preset-map.md",
2581
2582
  "sourceReferenceCount": 1
2582
2583
  },
2583
- "saas.frontend.settings-hub.engine-destinations": {
2584
- "topicId": "saas.frontend.settings-hub.engine-destinations",
2585
- "title": "Saas Frontend Settings Hub Engine Destinations",
2586
- "categories": [
2587
- "saas",
2588
- "saas.frontend",
2589
- "saas.frontend.settings-hub"
2590
- ],
2591
- "referenceFilePath": "references/saas.frontend.settings-hub.engine-destinations.md",
2592
- "sourceReferenceCount": 1
2593
- },
2594
- "saas.frontend.settings-hub.placement": {
2595
- "topicId": "saas.frontend.settings-hub.placement",
2596
- "title": "Saas Frontend Settings Hub Placement",
2597
- "categories": [
2598
- "saas",
2599
- "saas.frontend",
2600
- "saas.frontend.settings-hub"
2601
- ],
2602
- "referenceFilePath": "references/saas.frontend.settings-hub.placement.md",
2603
- "sourceReferenceCount": 2
2604
- },
2605
2584
  "saas.frontend.view-definition-scope": {
2606
2585
  "topicId": "saas.frontend.view-definition-scope",
2607
2586
  "title": "Saas Frontend View Definition Scope",
@@ -4345,16 +4324,6 @@
4345
4324
  "referenceFilePath": "references/zod.decorators.conditional-visibility.md",
4346
4325
  "sourceReferenceCount": 1
4347
4326
  },
4348
- "zod.decorators.data-categories": {
4349
- "topicId": "zod.decorators.data-categories",
4350
- "title": "Zod Decorators Data Categories",
4351
- "categories": [
4352
- "zod",
4353
- "zod.decorators"
4354
- ],
4355
- "referenceFilePath": "references/zod.decorators.data-categories.md",
4356
- "sourceReferenceCount": 4
4357
- },
4358
4327
  "zod.decorators.decorator-vocabulary": {
4359
4328
  "topicId": "zod.decorators.decorator-vocabulary",
4360
4329
  "title": "Zod Decorators Decorator Vocabulary",
@@ -4980,12 +4949,6 @@
4980
4949
  "categories": [],
4981
4950
  "sourceReferenceCount": 0
4982
4951
  },
4983
- "settings-placement-authoring": {
4984
- "topicId": "settings-placement-authoring",
4985
- "title": "Settings Placement Authoring",
4986
- "categories": [],
4987
- "sourceReferenceCount": 0
4988
- },
4989
4952
  "spec-catalog-authoring": {
4990
4953
  "topicId": "spec-catalog-authoring",
4991
4954
  "title": "Spec Catalog Authoring",
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "playbooks",
3
3
  "metadata": {
4
- "generatedAt": "2026-08-30T22:14:50.331Z",
4
+ "generatedAt": "2026-08-29T22:33:33.791Z",
5
5
  "description": "Compiled meta-workflow playbooks (app-creation methodology definitions)."
6
6
  },
7
7
  "entries": {
@@ -10,7 +10,7 @@
10
10
  "version": "0.1.0",
11
11
  "phase": "bottom_up",
12
12
  "executor": "companion_agent",
13
- "intent": "Bottom-up build decomposition — the FIRST build-execution playbook, the pivot from planning the domain (the domain-plan) to decomposing the BUILD. Reads the approved domain-plan (the ModuleBusinessSemantics module drafts + per-module resource inventory), the relationship drafts inside it (the inter-resource relationship intents), and the definition set (roadmap for phasing, requirements + feature-drafts for task-brief context), and the PLACEMENT PLAN (where each settings destination, resource operation and view sits in the shell, decided upstream), and DECOMPOSES the build work into an ordered set of coding-agent tasks. Each task is bound onto (a) the 7-topic functional taxonomy (configure_application_foundation -> model_domain_graph -> define_interaction_semantics -> shape_user_experience -> extend_application -> connect_runtime_and_external_capabilities -> assemble_verify_and_iterate) and (b) the app-knowledge skill catalog (each task names the skill(s) that carry its technical HOW). The tasks follow the per-resource inner order (schema -> config -> ui-behavior -> spec, then operations / interaction semantics, then UX, then extensions, then integrations), with companion-owned generation steps (labels / i18n, email templates, seeds) interleaved at the points their inputs exist. This playbook PRODUCES the ordered task graph (a build-plan artifact); it does NOT dispatch tasks to coding agents (that is the dispatch-orchestration playbook downstream), does NOT capture change-sets / single-flight-lock / verify, and does NOT solve multi-agent scale or interleaving. It authors no schemas and generates no code. v1 scaffold methodology — a typed build-task-graph contract, a dependency-DAG solver, and a collection validator are a later depth phase, not here.",
13
+ "intent": "Bottom-up build decomposition — the FIRST build-execution playbook, the pivot from planning the domain (the domain-plan) to decomposing the BUILD. Reads the approved domain-plan (the ModuleBusinessSemantics module drafts + per-module resource inventory), the relationship drafts inside it (the inter-resource relationship intents), and the definition set (roadmap for phasing, requirements + feature-drafts for task-brief context), and DECOMPOSES the build work into an ordered set of coding-agent tasks. Each task is bound onto (a) the 7-topic functional taxonomy (configure_application_foundation -> model_domain_graph -> define_interaction_semantics -> shape_user_experience -> extend_application -> connect_runtime_and_external_capabilities -> assemble_verify_and_iterate) and (b) the app-knowledge skill catalog (each task names the skill(s) that carry its technical HOW). The tasks follow the per-resource inner order (schema -> config -> ui-behavior -> spec, then operations / interaction semantics, then UX, then extensions, then integrations), with companion-owned generation steps (labels / i18n, email templates, seeds) interleaved at the points their inputs exist. This playbook PRODUCES the ordered task graph (a build-plan artifact); it does NOT dispatch tasks to coding agents (that is the dispatch-orchestration playbook downstream), does NOT capture change-sets / single-flight-lock / verify, and does NOT solve multi-agent scale or interleaving. It authors no schemas and generates no code. v1 scaffold methodology — a typed build-task-graph contract, a dependency-DAG solver, and a collection validator are a later depth phase, not here.",
14
14
  "functionalTopics": [],
15
15
  "skillRefs": [
16
16
  "journey-status",
@@ -31,7 +31,7 @@
31
31
  "ref": "bottom_up.build-dispatch",
32
32
  "version": "0.1.0",
33
33
  "phase": "bottom_up",
34
- "executor": "coding_agent",
34
+ "executor": "composite",
35
35
  "intent": "Bottom-up build dispatch — the SECOND build-execution playbook, the pivot from DECOMPOSING the build (the build-plan task graph) to DISPATCHING it: turning one ordered task into an actually-run, verified coding-agent run under the D4 dispatch contract. Reads the approved TYPED build-plan (`BuildPlanTaskGraph` — each task carries a closed target kind, ONE MetaWorkflow_FunctionalTopic, its skill refs, and DECLARED prerequisite task refs) and the current journey state, selects the NEXT READY task (`selectReadyBuildPlanTasks`: every declared prerequisite has landed — resolved by the host, never inferred from prose; SINGLE-FLIGHT — exactly ONE workspace-mutating run at a time), and dispatches exactly that typed task: (1) the runner builds the context pack (task brief + the task's skill pointers + the relevant journey/definition artifacts + introspected app reality + repo paths); (2) it runs ONE prompt turn against the coding agent over the Agent Client Protocol, in a session rooted at the app workspace (cwd = app root, so CLAUDE.md / .claude skills load naturally), answering the agent's permission requests within the execution profile's declared ceiling and refusing anything above it or outside the task's mutation scope; (3) it captures the change-set around the run (git baseline/post-run worktree snapshots → per-file attribution → a structured GitChangeSetCapture recorded on the task row); (4) it runs the VERIFY gate OUTSIDE the coding agent (a deterministic typecheck the runner maps onto the dispatch verification hook — pnpm exec tsc --noEmit — the trust-but-verify floor); (5) it records the result + applies the onFailure disposition (keep_and_flag: a failed/timed-out run keeps its captured change-set flagged for human triage, never a silent half-applied state). Then loop to the next ready task. This playbook PRODUCES the per-task dispatch contract + execution semantics; it authors no schemas and generates no code (the coding agent does that at dispatch time). It does NOT decompose the plan (that is the build-decompose playbook, upstream — it owns the task graph) and does NOT solve multi-agent SCALE — parallelism across several coding agents, the concurrency schedule, and interleaving the companion generation steps at scale are the downstream scale playbook. v1 scaffold: the single-flight dispatch contract; multi-agent parallelism, a run-completion serializer, and a revert_changeset failure path are later phases (revert is a MUTATING git op outside the read-only change-set carve-out, deliberately deferred).",
36
36
  "functionalTopics": [],
37
37
  "skillRefs": [
@@ -58,7 +58,7 @@
58
58
  "ref": "bottom_up.build-scale",
59
59
  "version": "0.1.0",
60
60
  "phase": "bottom_up",
61
- "executor": "coding_agent",
61
+ "executor": "composite",
62
62
  "intent": "Bottom-up build scale — the THIRD and final build-execution playbook, the pivot from dispatching ONE task safely (the single-flight dispatch contract) to running the build at SCALE: parallelism across several coding agents, the concurrency schedule, and interleaving the companion-owned generation steps concurrently with coding runs. Reads the approved build-plan (the ordered coding-agent task graph, each task carrying a target, ONE MetaWorkflow_FunctionalTopic, its skill(s), and prose prerequisite ordering) and the current journey state, and answers the SCALE questions the single-flight dispatch playbook deliberately left open: (1) derive the ready-SET (a wave / frontier of tasks whose prose prerequisites have ALL SUCCEEDED — not merely been attempted); (2) decide the parallelism degree (how many coding agents run at once) and the worktree-isolation model that keeps each concurrent run's change-set cleanly attributable; (3) schedule the waves respecting the DEPENDS_ON ordering the build-plan encodes; (4) interleave the deterministic companion-owned generation steps (labels / i18n, email templates, seeds) concurrently with coding runs at the points their inputs exist — those steps run through their deterministic companion endpoints, NOT the coding-agent single-flight lock, so they genuinely overlap coding runs; (5) reconcile wave completion across the concurrent runs (all tasks in the frontier SUCCEEDED before the next wave opens) and apply onFailure across siblings + downstream. Then advance to the next wave and loop. Each parallel slot INVOKES the single-flight dispatch contract (the build-dispatch playbook, upstream — select-next / context-pack / one ACP prompt turn / change-set capture / verify-outside / record + onFailure); this playbook does NOT re-specify those per-task mechanics and does NOT re-decompose the plan (the build-decompose playbook owns the task graph) and authors no schemas / no code. IMPORTANT HONESTY: the companion runner HARD-ENFORCES single-flight today (a run plan carries at most ONE coding-agent task; a concurrent dispatch is refused; the workspace-mutation lock + the lock-free cursor + the missing run-outcome observation loop all assume one dispatch at a time). So this v1 scale METHOD is the DECLARATIVE TARGET a runner-serializer slice will realize — on the current runner the waves DEGRADE to sequential single-flight dispatch. And even the deterministic companion-generation steps, though they do not take the coding single-flight lock, cannot SAFELY overlap an active coding run today: the coding run's change-set is captured as a whole-worktree time-window diff, so a generation step writing files inside that window is misattributed to the coding run (the same whole-worktree pollution that forbids two concurrent coding agents) — so the generation steps also serialize outside an active coding-capture window today, and genuine concurrency (coding-parallel OR generation-overlap) both arrive only with the git worktree-per-agent isolation runner task. v1 scaffold: a multi-CODING_AGENT run-completion serializer, git worktree-per-agent isolation, a run-outcome reconciler, and a cursor lock are companion-runner mechanism filed as runner tasks, NOT built here; a priority/work-stealing scheduler and cost-optimal packing are a later depth phase.",
63
63
  "functionalTopics": [],
64
64
  "skillRefs": [
@@ -109,6 +109,7 @@
109
109
  "ref": "bottom_up.foundation",
110
110
  "version": "0.2.0",
111
111
  "phase": "bottom_up",
112
+ "executor": "composite",
112
113
  "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.",
113
114
  "functionalTopics": [
114
115
  "configure_application_foundation"
@@ -124,25 +125,6 @@
124
125
  "methodFilePath": "playbooks/bottom_up.foundation/method.md",
125
126
  "sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1"
126
127
  },
127
- "bottom_up.placement-plan": {
128
- "ref": "bottom_up.placement-plan",
129
- "version": "0.1.0",
130
- "phase": "bottom_up",
131
- "executor": "companion_agent",
132
- "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.",
133
- "functionalTopics": [
134
- "shape_user_experience"
135
- ],
136
- "skillRefs": [
137
- "settings-placement-authoring",
138
- "config-app-shell",
139
- "config-navigation",
140
- "journey-status"
141
- ],
142
- "playbookFilePath": "playbooks/bottom_up.placement-plan/playbook.json",
143
- "methodFilePath": "playbooks/bottom_up.placement-plan/method.md",
144
- "sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1"
145
- },
146
128
  "refinement.compliance-document-candidate": {
147
129
  "ref": "refinement.compliance-document-candidate",
148
130
  "version": "0.1.0",
@@ -264,55 +246,10 @@
264
246
  },
265
247
  "top_down.market-analysis": {
266
248
  "ref": "top_down.market-analysis",
267
- "version": "0.2.0",
268
- "phase": "top_down",
269
- "intent": "Produce the market snapshot by gathering EVIDENCE, judging whether it is enough, and deriving the snapshot only once it is. An umbrella: it authors nothing itself — its deliverable is what its children land, and the order between them is decided by their own preconditions rather than declared here.",
270
- "functionalTopics": [],
271
- "skillRefs": [
272
- "journey-status",
273
- "market-authoring-overview"
274
- ],
275
- "playbookFilePath": "playbooks/top_down.market-analysis/playbook.json",
276
- "methodFilePath": "playbooks/top_down.market-analysis/method.md",
277
- "sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1"
278
- },
279
- "top_down.market-evidence-adequacy": {
280
- "ref": "top_down.market-evidence-adequacy",
281
249
  "version": "0.1.0",
282
250
  "phase": "top_down",
283
251
  "executor": "companion_agent",
284
- "intent": "Judge whether the evidence gathered so far is ENOUGH to derive a market snapshot from, and when it is not, name precisely what is missing so the next research round is aimed rather than repeated. Returns a verdict a sibling's precondition READS; it authors nothing and lands nothing.",
285
- "functionalTopics": [],
286
- "skillRefs": [
287
- "journey-status",
288
- "market-snapshot-validation"
289
- ],
290
- "playbookFilePath": "playbooks/top_down.market-evidence-adequacy/playbook.json",
291
- "methodFilePath": "playbooks/top_down.market-evidence-adequacy/method.md",
292
- "sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1"
293
- },
294
- "top_down.market-research": {
295
- "ref": "top_down.market-research",
296
- "version": "0.1.0",
297
- "phase": "top_down",
298
- "executor": "research_agent",
299
- "intent": "Gather EVIDENCE about the product's market from the public web — the category as it is actually named, who sells into it, what they charge, and what buyers say — and return a condensed, source-attributed brief. Produces no specification family: its whole deliverable is evidence a sibling derives from. Runs READ-ONLY: it can fetch and search, and it cannot write, execute or touch the workspace.",
300
- "functionalTopics": [],
301
- "skillRefs": [
302
- "journey-status",
303
- "market-category",
304
- "market-alternatives"
305
- ],
306
- "playbookFilePath": "playbooks/top_down.market-research/playbook.json",
307
- "methodFilePath": "playbooks/top_down.market-research/method.md",
308
- "sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1"
309
- },
310
- "top_down.market-snapshot-produce": {
311
- "ref": "top_down.market-snapshot-produce",
312
- "version": "0.1.0",
313
- "phase": "top_down",
314
- "executor": "companion_agent",
315
- "intent": "Derive a validated market snapshot from the vision and from the EVIDENCE a sibling research step gathered — the artifact-producing child of the `top_down.market-analysis` composite. The provider proposes the market graph; the trusted runtime stamps entity refs/version and keeps provenance, authority and accepted-family mutation outside model output. Its intent used to claim derivation from \"sealed research evidence\" while nothing supplied any; it now runs only once an adequacy gate has read the evidence and returned ADEQUATE.",
252
+ "intent": "Derive a validated market snapshot from accepted vision truth and sealed research evidence. The provider proposes the market graph; the trusted runtime stamps entity refs/version and keeps provenance, authority and accepted-family mutation outside model output.",
316
253
  "functionalTopics": [],
317
254
  "skillRefs": [
318
255
  "journey-status",
@@ -332,23 +269,23 @@
332
269
  "market-scoring-interpretation",
333
270
  "market-snapshot-validation"
334
271
  ],
335
- "playbookFilePath": "playbooks/top_down.market-snapshot-produce/playbook.json",
336
- "methodFilePath": "playbooks/top_down.market-snapshot-produce/method.md",
272
+ "playbookFilePath": "playbooks/top_down.market-analysis/playbook.json",
273
+ "methodFilePath": "playbooks/top_down.market-analysis/method.md",
337
274
  "sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1",
338
275
  "evaluationProtocol": {
339
276
  "protocolRef": "application-creation:evaluation-protocol/market-analysis",
340
277
  "protocolVersion": 1,
341
- "filePath": "playbooks/top_down.market-snapshot-produce/evaluation-protocol.json"
278
+ "filePath": "playbooks/top_down.market-analysis/evaluation-protocol.json"
342
279
  },
343
280
  "evaluationTreatment": {
344
281
  "definitionRef": "application-creation:evaluation-treatment/market-analysis",
345
282
  "definitionVersion": 1,
346
- "filePath": "playbooks/top_down.market-snapshot-produce/evaluation-treatment.json"
283
+ "filePath": "playbooks/top_down.market-analysis/evaluation-treatment.json"
347
284
  },
348
285
  "structuredArtifactAction": {
349
286
  "definitionRef": "application-creation:structured-artifact-action/market-analysis",
350
287
  "definitionVersion": 1,
351
- "filePath": "playbooks/top_down.market-snapshot-produce/structured-artifact-action.json"
288
+ "filePath": "playbooks/top_down.market-analysis/structured-artifact-action.json"
352
289
  }
353
290
  },
354
291
  "top_down.phase-gate": {