@wildo-ai/framework-knowledge 1.1.4 → 1.1.5

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 (848) 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 +227 -6
  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 +47 -1
  8. package/dist/esm/framework-knowledge.loader.js.map +1 -1
  9. package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
  10. package/dist/esm/framework-knowledge.schemas.js.map +1 -1
  11. package/dist/esm/index.d.ts.map +1 -1
  12. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
  13. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  14. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
  15. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  16. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +125 -0
  17. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -0
  18. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +177 -0
  19. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -0
  20. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +213 -7
  21. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +326 -8
  23. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +5 -3
  25. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +21 -14
  27. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  29. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +57 -0
  31. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -0
  32. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +63 -0
  33. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -0
  34. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +132 -0
  35. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -0
  36. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +179 -0
  37. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -0
  38. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +67 -0
  39. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -0
  40. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +76 -0
  41. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -0
  42. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +5 -4
  43. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  44. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +10 -5
  45. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +67 -0
  47. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -0
  48. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +82 -0
  49. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -0
  50. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +25 -9
  51. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  52. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +124 -7
  53. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  54. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +67 -0
  55. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -0
  56. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +83 -0
  57. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -0
  58. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +69 -0
  59. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -0
  60. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +71 -0
  61. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -0
  62. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -1
  63. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  64. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -1
  65. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  66. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +71 -0
  67. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -0
  68. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +88 -0
  69. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -0
  70. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +97 -0
  71. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -0
  72. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +156 -0
  73. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -0
  74. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +115 -0
  75. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -0
  76. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +152 -0
  77. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -0
  78. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +188 -8
  79. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  80. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +167 -9
  81. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  82. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +171 -1
  83. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  84. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +146 -1
  85. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  86. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts +248 -0
  87. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -0
  88. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js +248 -0
  89. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -0
  90. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +157 -4
  91. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  92. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +172 -4
  93. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  94. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +5 -4
  95. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  96. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +8 -7
  97. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  98. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +3 -2
  99. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  100. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +22 -3
  101. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  102. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +5 -3
  103. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  104. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +21 -12
  105. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  106. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +192 -27
  107. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  108. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +172 -33
  109. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  110. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +2 -1
  111. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  112. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +6 -2
  113. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  114. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +182 -5
  115. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  116. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +191 -5
  117. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  118. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +2 -1
  119. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  120. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +3 -2
  121. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  122. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +154 -0
  123. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -0
  124. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +214 -0
  125. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -0
  126. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +44 -0
  127. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -0
  128. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +51 -0
  129. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -0
  130. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -1
  131. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  132. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +2 -1
  133. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  134. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +2 -1
  135. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  136. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +6 -2
  137. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  138. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +2 -1
  139. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  140. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +2 -1
  141. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  142. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -2
  143. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  144. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +7 -3
  145. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  146. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +32 -4
  147. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  148. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +27 -3
  149. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  150. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -2
  151. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  152. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +4 -2
  153. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  154. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +199 -0
  155. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -0
  156. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +227 -0
  157. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -0
  158. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +5 -3
  159. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  160. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +18 -4
  161. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  162. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +155 -4
  163. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  164. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +187 -4
  165. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  166. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +6 -5
  167. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  168. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +18 -17
  169. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  170. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  171. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
  172. package/dist/knowledge/manifest.json +9 -8
  173. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +75 -0
  174. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
  175. package/dist/knowledge/playbooks/bottom_up.build/method.md +79 -0
  176. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +65 -0
  177. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -0
  178. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -0
  179. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +1122 -76
  180. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +49 -13
  181. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-protocol.json +1 -1
  182. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-treatment.json +1 -1
  183. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +671 -47
  184. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +10 -16
  185. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +31 -35
  186. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -16
  187. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +95 -0
  188. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +62 -0
  189. package/dist/knowledge/playbooks/bottom_up.conception/method.md +80 -0
  190. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +90 -0
  191. package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +107 -0
  192. package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +70 -0
  193. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +8 -8
  194. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +14 -13
  195. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +165 -0
  196. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +74 -0
  197. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +219 -140
  198. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +55 -22
  199. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +138 -0
  200. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +70 -0
  201. package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +87 -0
  202. package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +69 -0
  203. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +236 -0
  204. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +63 -0
  205. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +116 -0
  206. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +79 -0
  207. package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +71 -0
  208. package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +70 -0
  209. package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +83 -0
  210. package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +68 -0
  211. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -0
  212. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -0
  213. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +873 -15
  214. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +19 -12
  215. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-protocol.json +1 -0
  216. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-treatment.json +1 -0
  217. package/dist/knowledge/playbooks/refinement.document-facts/method.md +186 -21
  218. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +12 -16
  219. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-protocol.json +1 -0
  220. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-treatment.json +1 -0
  221. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +343 -0
  222. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +54 -0
  223. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -0
  224. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -0
  225. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +28 -11
  226. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -17
  227. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +8 -15
  228. package/dist/knowledge/playbooks/top_down.capability-map/method.md +25 -49
  229. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +14 -17
  230. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
  231. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +101 -0
  232. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-protocol.json +1 -0
  233. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-treatment.json +1 -0
  234. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +209 -0
  235. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +68 -0
  236. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
  237. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +42 -0
  238. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -0
  239. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -0
  240. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +39 -12
  241. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +18 -66
  242. package/dist/knowledge/playbooks/top_down.compliance-research/method.md +78 -0
  243. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +43 -0
  244. package/dist/knowledge/playbooks/top_down.definition/method.md +103 -0
  245. package/dist/knowledge/playbooks/top_down.definition/playbook.json +75 -0
  246. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +56 -0
  247. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +48 -0
  248. package/dist/knowledge/playbooks/top_down.market-analysis/method.md +51 -165
  249. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +25 -44
  250. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
  251. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +43 -0
  252. package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
  253. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +45 -0
  254. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-protocol.json +1 -1
  255. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-treatment.json +1 -1
  256. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +247 -0
  257. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +71 -0
  258. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  259. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  260. package/dist/knowledge/playbooks/top_down.phase-gate/method.md +36 -69
  261. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +12 -9
  262. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +11 -7
  263. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +12 -16
  264. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-protocol.json +1 -0
  265. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-treatment.json +1 -0
  266. package/dist/knowledge/playbooks/top_down.risk-register/method.md +46 -0
  267. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +59 -0
  268. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +12 -5
  269. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +15 -17
  270. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-protocol.json +1 -0
  271. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-treatment.json +1 -0
  272. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +23 -14
  273. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +12 -17
  274. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
  275. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +13 -17
  276. package/dist/knowledge/references/acp.execution-profile.md +266 -0
  277. package/dist/knowledge/references/acp.host-configuration-inheritance.md +29 -0
  278. package/dist/knowledge/references/acp.permission-ceiling.md +105 -0
  279. package/dist/knowledge/references/acp.permission-escalation.md +37 -0
  280. package/dist/knowledge/references/application-documentation-chapters.config.md +152 -0
  281. package/dist/knowledge/references/application-documentation-plan.config.md +136 -0
  282. package/dist/knowledge/references/application-maturity.config.md +319 -0
  283. package/dist/knowledge/references/assertions.authored-metadata.config.md +1 -1
  284. package/dist/knowledge/references/assertions.specification.config.md +1 -1
  285. package/dist/knowledge/references/brand.asset.config.md +8 -16
  286. package/dist/knowledge/references/brand.authored-metadata.config.md +2 -2
  287. package/dist/knowledge/references/brand.logo-direction.config.md +9 -7
  288. package/dist/knowledge/references/brand.snapshot.config.md +16 -2
  289. package/dist/knowledge/references/brand.snapshot.validation.md +0 -7
  290. package/dist/knowledge/references/build-plan.task-graph.config.md +581 -7
  291. package/dist/knowledge/references/business-model.authored-metadata.config.md +2 -2
  292. package/dist/knowledge/references/business-model.pricing-plan.config.md +1 -1
  293. package/dist/knowledge/references/business-model.snapshot.validation.md +15 -0
  294. package/dist/knowledge/references/capability-composition.config.md +155 -0
  295. package/dist/knowledge/references/cli.market.utils.md +1 -0
  296. package/dist/knowledge/references/companion.technical-doc.service.md +453 -98
  297. package/dist/knowledge/references/engine.client-bundle.allow-list.md +21 -0
  298. package/dist/knowledge/references/engine.client-bundle.external-connectors-public.discipline.md +20 -1
  299. package/dist/knowledge/references/engine.saas-technical-doc.config.md +8 -4
  300. package/dist/knowledge/references/engine.saas-website.config.md +22 -10
  301. package/dist/knowledge/references/example.backend.addon-wiring.module.md +8 -12
  302. package/dist/knowledge/references/example.config.app-shell.full.md +42 -7
  303. package/dist/knowledge/references/example.config.backend.required-floors.md +4 -0
  304. package/dist/knowledge/references/example.config.design-system.full.md +3 -0
  305. package/dist/knowledge/references/example.engine.product-definitions.feature-and-profiles.md +19 -7
  306. package/dist/knowledge/references/example.features.connected-feature.declaration.md +66 -0
  307. package/dist/knowledge/references/example.features.connected-feature.surface.md +42 -0
  308. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +4 -3
  309. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +6 -10
  310. package/dist/knowledge/references/example.guidance.bound-survey-flow.md +82 -0
  311. package/dist/knowledge/references/example.infra.environment-config.local.md +88 -11
  312. package/dist/knowledge/references/example.milestones.module-definitions.md +73 -0
  313. package/dist/knowledge/references/example.minion.contained-tick.md +79 -0
  314. package/dist/knowledge/references/example.module.companion-exports.full.md +38 -3
  315. package/dist/knowledge/references/example.provider.backend-module-shape.md +31 -13
  316. package/dist/knowledge/references/example.provider.frontend-app.module.md +103 -0
  317. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +20 -0
  318. package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +7 -3
  319. package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +30 -0
  320. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +11 -0
  321. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +3 -0
  322. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +94 -10
  323. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +79 -0
  324. package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +18 -0
  325. package/dist/knowledge/references/example.worker.node-route.md +94 -0
  326. package/dist/knowledge/references/experience-plan.config.md +311 -0
  327. package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +132 -9
  328. package/dist/knowledge/references/external-connectors.backend.provider-package-convention.md +36 -0
  329. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +269 -0
  330. package/dist/knowledge/references/integration-plan.config.md +185 -0
  331. package/dist/knowledge/references/market.alternative.config.md +1 -1
  332. package/dist/knowledge/references/market.authored-metadata.config.md +12 -9
  333. package/dist/knowledge/references/market.channel.config.md +3 -3
  334. package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
  335. package/dist/knowledge/references/market.gain.config.md +1 -1
  336. package/dist/knowledge/references/market.icp.config.md +2 -2
  337. package/dist/knowledge/references/market.job.config.md +1 -1
  338. package/dist/knowledge/references/market.message-template.config.md +2 -2
  339. package/dist/knowledge/references/market.objection.config.md +1 -1
  340. package/dist/knowledge/references/market.pain.config.md +1 -1
  341. package/dist/knowledge/references/market.persona.config.md +2 -2
  342. package/dist/knowledge/references/market.proof.config.md +1 -1
  343. package/dist/knowledge/references/market.snapshot.validation.md +15 -0
  344. package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
  345. package/dist/knowledge/references/market.trigger.config.md +1 -1
  346. package/dist/knowledge/references/minions.tick-contract.md +83 -0
  347. package/dist/knowledge/references/placement-plan.config.md +369 -0
  348. package/dist/knowledge/references/platform.config.application-database.md +5 -2
  349. package/dist/knowledge/references/platform.config.backing-services.md +0 -21
  350. package/dist/knowledge/references/platform.config.environment.deployment.md +206 -14
  351. package/dist/knowledge/references/platform.config.infra-provider-resolution.md +170 -0
  352. package/dist/knowledge/references/platform.config.infrastructure-host.md +87 -0
  353. package/dist/knowledge/references/platform.config.saas.md +261 -9
  354. package/dist/knowledge/references/presets.models.labelling.sections.md +14 -0
  355. package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
  356. package/dist/knowledge/references/requirements.authored-metadata.config.md +2 -2
  357. package/dist/knowledge/references/requirements.snapshot.validation.md +15 -0
  358. package/dist/knowledge/references/roadmap.authored-metadata.config.md +2 -2
  359. package/dist/knowledge/references/roadmap.snapshot.validation.md +15 -7
  360. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +71 -0
  361. package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +1 -2
  362. package/dist/knowledge/references/saas.backend.auth.federated-identity-provider-private-networks.md +62 -0
  363. package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +86 -0
  364. package/dist/knowledge/references/saas.backend.billing.catalog-sync-result.md +37 -0
  365. package/dist/knowledge/references/saas.backend.billing.resolution-failure-reasons.md +24 -5
  366. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +187 -0
  367. package/dist/knowledge/references/saas.backend.domain-module.md +25 -1
  368. package/dist/knowledge/references/saas.backend.error-builder.user-guidance.md +82 -0
  369. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +6 -0
  370. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +22 -4
  371. package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +17 -4
  372. package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +84 -0
  373. package/dist/knowledge/references/saas.backend.health-readiness-contributor.md +73 -0
  374. package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +200 -0
  375. package/dist/knowledge/references/saas.backend.providers.operation-executor.md +51 -0
  376. package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +71 -0
  377. package/dist/knowledge/references/saas.backend.queue.worker-topology.md +39 -0
  378. package/dist/knowledge/references/saas.backend.system-access-service.md +51 -42
  379. package/dist/knowledge/references/saas.composition.scenario-apply.md +51 -0
  380. package/dist/knowledge/references/saas.config.content-security-policy.md +97 -0
  381. package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +91 -21
  382. package/dist/knowledge/references/saas.data-seeding.definition-input.md +4 -0
  383. package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +38 -0
  384. package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +27 -27
  385. package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +65 -16
  386. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +41 -11
  387. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +44 -8
  388. package/dist/knowledge/references/saas.frontend.billing-context.md +108 -0
  389. package/dist/knowledge/references/saas.frontend.brand-identity.md +38 -0
  390. package/dist/knowledge/references/saas.frontend.celebration-overlay-contract.md +41 -0
  391. package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +64 -0
  392. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
  393. package/dist/knowledge/references/saas.frontend.errors.user-facing-error-message.md +47 -0
  394. package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.per-action-retry-loop.md +7 -1
  395. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +3 -3
  396. package/dist/knowledge/references/saas.frontend.flows-actors-view.md +7 -4
  397. package/dist/knowledge/references/saas.frontend.form-fields.file-provider-constraints.md +30 -48
  398. package/dist/knowledge/references/saas.frontend.full-custom-view.definition.md +24 -0
  399. package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
  400. package/dist/knowledge/references/saas.frontend.onboarding-view.md +84 -0
  401. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +65 -0
  402. package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
  403. package/dist/knowledge/references/saas.frontend.resource-header-title.md +28 -4
  404. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +127 -1
  405. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +327 -11
  406. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +198 -0
  407. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +220 -0
  408. package/dist/knowledge/references/saas.market.generation-agent.md +26 -9
  409. package/dist/knowledge/references/saas.models.analytics.value-moments.md +132 -0
  410. package/dist/knowledge/references/saas.models.audit.trail-config.md +155 -0
  411. package/dist/knowledge/references/saas.models.auth.methods.md +513 -0
  412. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +82 -0
  413. package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +77 -0
  414. package/dist/knowledge/references/saas.models.config.organization-types.md +192 -0
  415. package/dist/knowledge/references/saas.models.config.registration.md +188 -0
  416. package/dist/knowledge/references/saas.models.config.tenant-teardown.md +81 -0
  417. package/dist/knowledge/references/saas.models.data-mode-read-list.md +173 -3
  418. package/dist/knowledge/references/saas.models.email.template-type.md +40 -0
  419. package/dist/knowledge/references/saas.models.engine-capabilities.md +85 -7
  420. package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +61 -0
  421. package/dist/knowledge/references/saas.models.external-data-pipeline.md +43 -4
  422. package/dist/knowledge/references/saas.models.features.definition-builders.md +162 -0
  423. package/dist/knowledge/references/saas.models.file-upload-grant.md +222 -0
  424. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +54 -5
  425. package/dist/knowledge/references/saas.models.governed-document-acceptance-mode.md +116 -0
  426. package/dist/knowledge/references/saas.models.guidance-flow.md +160 -0
  427. package/dist/knowledge/references/saas.models.http-api-binding.md +76 -110
  428. package/dist/knowledge/references/saas.models.milestone-celebration.md +69 -0
  429. package/dist/knowledge/references/saas.models.milestone-definition.md +209 -0
  430. package/dist/knowledge/references/saas.models.navigation.layout.md +2 -2
  431. package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
  432. package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
  433. package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +150 -0
  434. package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +70 -0
  435. package/dist/knowledge/references/saas.models.notifications.targets.md +138 -0
  436. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +256 -0
  437. package/dist/knowledge/references/saas.models.onboarding-elements.md +375 -0
  438. package/dist/knowledge/references/saas.models.onboarding-trigger.md +52 -0
  439. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +50 -0
  440. package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +129 -0
  441. package/dist/knowledge/references/saas.models.privacy.client-instance-id-scope.md +49 -0
  442. package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +106 -0
  443. package/dist/knowledge/references/saas.models.progression-tracker-variant.md +76 -0
  444. package/dist/knowledge/references/saas.models.provider-capabilities.md +8 -5
  445. package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +72 -0
  446. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +50 -0
  447. package/dist/knowledge/references/saas.models.providers.capability-surface.md +58 -0
  448. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +111 -0
  449. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +156 -0
  450. package/dist/knowledge/references/saas.models.rate-limit-configuration.md +11 -1
  451. package/dist/knowledge/references/saas.models.relationship-handling-settings.md +23 -1
  452. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -4
  453. package/dist/knowledge/references/saas.models.resource-config.forwarded-label.md +5 -4
  454. package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +69 -0
  455. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +15 -2
  456. package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +66 -0
  457. package/dist/knowledge/references/saas.models.resource-config.operation-base.md +24 -1
  458. package/dist/knowledge/references/saas.models.resource-config.operation-cron-job.md +59 -0
  459. package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +55 -0
  460. package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +5 -4
  461. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +158 -0
  462. package/dist/knowledge/references/saas.models.resource-config.operation-step-up.md +77 -0
  463. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
  464. package/dist/knowledge/references/saas.models.resource-config.operation-variant-for-key.md +6 -1
  465. package/dist/knowledge/references/saas.models.resource-config.queue-policy.md +49 -0
  466. package/dist/knowledge/references/saas.models.resource-config.required-features.md +84 -0
  467. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +10 -0
  468. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +14 -0
  469. package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +111 -4
  470. package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +39 -0
  471. package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +48 -0
  472. package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +38 -0
  473. package/dist/knowledge/references/saas.models.resource-primary-scope.md +11 -2
  474. package/dist/knowledge/references/saas.models.scope-membership.md +3 -4
  475. package/dist/knowledge/references/saas.models.shared-saas-module.md +25 -0
  476. package/dist/knowledge/references/saas.models.systems-of-record.md +635 -0
  477. package/dist/knowledge/references/saas.public-runtime.contract.md +198 -1
  478. package/dist/knowledge/references/saas.rag.retrieval-result.md +19 -8
  479. package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
  480. package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +15 -36
  481. package/dist/knowledge/references/saas.specifications.application-document-publication.contract.md +9 -5
  482. package/dist/knowledge/references/saas.specifications.application-document-publication.generation.md +63 -0
  483. package/dist/knowledge/references/saas.specifications.application-document-release-set.contract.md +74 -0
  484. package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +123 -0
  485. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +88 -7
  486. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +774 -53
  487. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +211 -14
  488. package/dist/knowledge/references/saas.specifications.composite-view-specification.md +10 -0
  489. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +364 -0
  490. package/dist/knowledge/references/saas.specifications.playbook-approval-and-failure-policies.md +96 -0
  491. package/dist/knowledge/references/saas.specifications.processor-register.md +333 -0
  492. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +8 -0
  493. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
  494. package/dist/knowledge/references/saas.website.astro.bridge.md +64 -2
  495. package/dist/knowledge/references/saas.website.astro.head-renderer.md +32 -12
  496. package/dist/knowledge/references/saas.website.astro.label-loader.md +3 -0
  497. package/dist/knowledge/references/saas.website.astro.robots-renderer.md +14 -1
  498. package/dist/knowledge/references/saas.website.blog.bridge.md +21 -1
  499. package/dist/knowledge/references/saas.website.consent.banner.md +218 -0
  500. package/dist/knowledge/references/saas.website.consent.context.md +162 -0
  501. package/dist/knowledge/references/saas.website.consent.gate.md +38 -0
  502. package/dist/knowledge/references/saas.website.page-layout.component.md +67 -1
  503. package/dist/knowledge/references/saas.website.page.context.md +4 -3
  504. package/dist/knowledge/references/saas.website.runtime.context.md +43 -7
  505. package/dist/knowledge/references/saas.website.section.context.md +3 -2
  506. package/dist/knowledge/references/saas.website.sections.category-enum.md +19 -20
  507. package/dist/knowledge/references/vision.authored-metadata.config.md +2 -2
  508. package/dist/knowledge/references/website-plan.config.md +205 -0
  509. package/dist/knowledge/references/workers.node.worker-init-contract.md +57 -0
  510. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +43 -2
  511. package/dist/knowledge/references/zod.decorators.data-categories.md +197 -0
  512. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +51 -4
  513. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +54 -1
  514. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +35 -0
  515. package/dist/knowledge/references/zod.decorators.field-spec-params.md +32 -5
  516. package/dist/knowledge/references/zod.decorators.file-nature-constraints.md +86 -0
  517. package/dist/knowledge/references/zod.decorators.file-readiness-metadata.md +67 -0
  518. package/dist/knowledge/references/zod.decorators.file-schema.md +90 -14
  519. package/dist/knowledge/references/zod.decorators.file-vocabularies.md +84 -0
  520. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +140 -4
  521. package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
  522. package/dist/knowledge/references/zod.decorators.rag-source.md +6 -2
  523. package/dist/knowledge/references/zod.decorators.schema-metadata.md +24 -0
  524. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +35 -0
  525. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +46 -12
  526. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +31 -12
  527. package/dist/knowledge/references/zod.factories.address.md +118 -0
  528. package/dist/knowledge/references/zod.factories.code.md +2 -0
  529. package/dist/knowledge/references/zod.factories.duration.md +2 -0
  530. package/dist/knowledge/references/zod.factories.money.md +2 -0
  531. package/dist/knowledge/references/zod.factories.phone.md +14 -1
  532. package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
  533. package/dist/knowledge/registries/framework-topics.json +1215 -11
  534. package/dist/knowledge/registries/playbooks.json +454 -50
  535. package/dist/knowledge/registries/source-tags.json +3153 -1043
  536. package/dist/knowledge/rules/database-migration-obligation.md +110 -0
  537. package/dist/knowledge/rules/live-context-door.md +108 -0
  538. package/dist/knowledge/rules/resource-schema-awareness.md +75 -0
  539. package/dist/knowledge/skills/INDEX.md +46 -11
  540. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +80 -37
  541. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +167 -0
  542. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +6 -3
  543. package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -3
  544. package/dist/knowledge/skills/application-database-migrations/references/framework-application-database-api.md +5 -2
  545. package/dist/knowledge/skills/application-database-migrations/references/migration-refusals.md +32 -0
  546. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +94 -3
  547. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +50 -0
  548. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +26 -19
  549. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +25 -1
  550. package/dist/knowledge/skills/backend-addon-wiring/references/framework-readiness-contributor-api.md +135 -0
  551. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +75 -12
  552. package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +137 -0
  553. package/dist/knowledge/skills/backend-custom-operation/references/framework-error-user-guidance-api.md +112 -0
  554. package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +72 -1
  555. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +207 -0
  556. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +31 -1
  557. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-asset-api.md +8 -16
  558. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +25 -9
  559. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +135 -5
  560. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +80 -17
  561. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +369 -111
  562. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +32 -10
  563. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +103 -58
  564. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-publication-contract.md +19 -13
  565. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +142 -26
  566. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +722 -23
  567. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +348 -0
  568. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +123 -0
  569. package/dist/knowledge/skills/config-app-shell/SKILL.md +74 -11
  570. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +85 -19
  571. package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +70 -0
  572. package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
  573. package/dist/knowledge/skills/config-design-system/SKILL.md +43 -3
  574. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
  575. package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
  576. package/dist/knowledge/skills/config-design-system/references/surface-policy-authoring.md +19 -10
  577. package/dist/knowledge/skills/config-navigation/SKILL.md +85 -2
  578. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
  579. package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +2 -2
  580. package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
  581. package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
  582. package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +172 -0
  583. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +146 -0
  584. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +141 -0
  585. package/dist/knowledge/skills/config-saas/SKILL.md +86 -9
  586. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +199 -0
  587. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +179 -0
  588. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +493 -0
  589. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +153 -0
  590. package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +242 -0
  591. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +161 -0
  592. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +93 -12
  593. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +785 -0
  594. package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +172 -0
  595. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +261 -9
  596. package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +9 -0
  597. package/dist/knowledge/skills/config-saas-backend/SKILL.md +58 -3
  598. package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +151 -0
  599. package/dist/knowledge/skills/config-saas-backend/references/framework-auth-methods-api.md +579 -0
  600. package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +8 -2
  601. package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +96 -0
  602. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +316 -0
  603. package/dist/knowledge/skills/config-saas-backend/references/framework-registration-config-api.md +221 -0
  604. package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +121 -0
  605. package/dist/knowledge/skills/config-saas-backend/references/managed-startup-configuration.md +46 -0
  606. package/dist/knowledge/skills/configure-billing/SKILL.md +27 -22
  607. package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +27 -15
  608. package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +41 -0
  609. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +36 -17
  610. package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +30 -28
  611. package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +169 -0
  612. package/dist/knowledge/skills/configure-billing/references/framework-billing-resolution-failure-api.md +44 -11
  613. package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +187 -0
  614. package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +76 -0
  615. package/dist/knowledge/skills/configure-coding-agent/SKILL.md +280 -0
  616. package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +168 -0
  617. package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +504 -0
  618. package/dist/knowledge/skills/email-add-template/SKILL.md +41 -69
  619. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +15 -7
  620. package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +120 -0
  621. package/dist/knowledge/skills/engine-component-registration/SKILL.md +19 -12
  622. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +54 -31
  623. package/dist/knowledge/skills/engine-product-definitions/references/connected-feature-workflow.md +130 -0
  624. package/dist/knowledge/skills/engine-product-definitions/references/framework-engine-product-definitions-api.md +25 -0
  625. package/dist/knowledge/skills/engine-product-definitions/references/framework-feature-builders-api.md +215 -0
  626. package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +78 -0
  627. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +33 -24
  628. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +121 -0
  629. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
  630. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -8
  631. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +5 -4
  632. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +46 -9
  633. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +34 -7
  634. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +151 -0
  635. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +6 -10
  636. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +54 -5
  637. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +75 -21
  638. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +258 -0
  639. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +480 -0
  640. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +3983 -0
  641. package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +211 -0
  642. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +165 -0
  643. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-elements-api.md +381 -0
  644. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-trigger-api.md +57 -0
  645. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-view-api.md +89 -0
  646. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +13 -1
  647. package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +14 -0
  648. package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +14 -0
  649. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +3 -1
  650. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +14 -0
  651. package/dist/knowledge/skills/infra-environment-config/SKILL.md +237 -37
  652. package/dist/knowledge/skills/infra-environment-config/references/framework-application-database-api.md +5 -2
  653. package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +174 -21
  654. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +206 -14
  655. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +95 -0
  656. package/dist/knowledge/skills/journey-approve/SKILL.md +28 -8
  657. package/dist/knowledge/skills/journey-approve/references/specification-family-map.md +88 -0
  658. package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +37 -2
  659. package/dist/knowledge/skills/journey-next/SKILL.md +41 -1
  660. package/dist/knowledge/skills/journey-report/SKILL.md +16 -3
  661. package/dist/knowledge/skills/journey-run/SKILL.md +92 -7
  662. package/dist/knowledge/skills/journey-run/references/expert-personas-and-deliberations.md +46 -0
  663. package/dist/knowledge/skills/journey-run/references/framework-playbook-approval-policy.md +108 -0
  664. package/dist/knowledge/skills/journey-status/SKILL.md +14 -4
  665. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +153 -46
  666. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +119 -0
  667. package/dist/knowledge/skills/local-environment-bootstrap/references/initialization-recovery-recipe.md +7 -4
  668. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +253 -33
  669. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +1 -1
  670. package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
  671. package/dist/knowledge/skills/market-alternatives/SKILL.md +1 -1
  672. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +12 -9
  673. package/dist/knowledge/skills/market-channels/SKILL.md +3 -3
  674. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +226 -14
  675. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +226 -14
  676. package/dist/knowledge/skills/market-generation-cli/SKILL.md +56 -9
  677. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +32 -9
  678. package/dist/knowledge/skills/market-icp/SKILL.md +2 -2
  679. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +3 -3
  680. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -2
  681. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +17 -2
  682. package/dist/knowledge/skills/market-persona/SKILL.md +2 -2
  683. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +2 -2
  684. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -0
  685. package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +15 -0
  686. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +1 -1
  687. package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +1 -1
  688. package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +198 -0
  689. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-celebration-overlay-contract.md +51 -0
  690. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-celebration-api.md +79 -0
  691. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-definition-api.md +220 -0
  692. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-progression-tracker-api.md +86 -0
  693. package/dist/knowledge/skills/minion-authoring/SKILL.md +140 -0
  694. package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +84 -0
  695. package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +91 -0
  696. package/dist/knowledge/skills/module-companion-exports/SKILL.md +38 -3
  697. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +211 -14
  698. package/dist/knowledge/skills/module-registration/SKILL.md +50 -33
  699. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +50 -1
  700. package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +142 -0
  701. package/dist/knowledge/skills/module-registration/references/registry-files.md +14 -5
  702. package/dist/knowledge/skills/module-relationships/SKILL.md +62 -0
  703. package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +26 -5
  704. package/dist/knowledge/skills/provider-backend-package/SKILL.md +279 -0
  705. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +80 -0
  706. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +55 -0
  707. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-convention-api.md +48 -0
  708. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +33 -6
  709. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-file-provider-constraints-api.md +99 -47
  710. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +241 -9
  711. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +196 -0
  712. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +50 -0
  713. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +80 -0
  714. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +71 -0
  715. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +58 -0
  716. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +275 -0
  717. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +64 -11
  718. package/dist/knowledge/skills/rate-limit-authoring/references/fixed-window-and-environment-multiplier.md +27 -0
  719. package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +19 -6
  720. package/dist/knowledge/skills/resource-add-field/SKILL.md +12 -5
  721. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +373 -23
  722. package/dist/knowledge/skills/resource-add-module/SKILL.md +116 -265
  723. package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +133 -0
  724. package/dist/knowledge/skills/resource-add-module/references/framework-new-module-wiring-api.md +25 -0
  725. package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +12 -12
  726. package/dist/knowledge/skills/resource-add-resource/SKILL.md +26 -3
  727. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +122 -4
  728. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +25 -0
  729. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +93 -0
  730. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +136 -0
  731. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +85 -0
  732. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +133 -0
  733. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +141 -0
  734. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-step-up-api.md +126 -0
  735. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +859 -0
  736. package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +122 -0
  737. package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +124 -0
  738. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +97 -2
  739. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +457 -15
  740. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +197 -0
  741. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +162 -46
  742. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +452 -0
  743. package/dist/knowledge/skills/resource-custom-view/SKILL.md +5 -0
  744. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +327 -11
  745. package/dist/knowledge/skills/resource-custom-view/references/framework-user-facing-error-message-api.md +50 -0
  746. package/dist/knowledge/skills/resource-external-data/SKILL.md +228 -15
  747. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +54 -7
  748. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +87 -113
  749. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +13 -8
  750. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +69 -26
  751. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +246 -0
  752. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +7 -6
  753. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +5 -3
  754. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +43 -48
  755. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +96 -14
  756. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +47 -15
  757. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +6 -2
  758. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +32 -2
  759. package/dist/knowledge/skills/resource-schema-authoring/examples/basic-resource-schema.example.md +2 -1
  760. package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +17 -0
  761. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +75 -4
  762. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +182 -0
  763. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +245 -0
  764. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +35 -0
  765. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +46 -12
  766. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +480 -15
  767. package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +67 -0
  768. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +74 -14
  769. package/dist/knowledge/skills/resource-schema-authoring/references/polymorphic-per-scope-resources.md +28 -5
  770. package/dist/knowledge/skills/resource-schema-authoring/references/schema-variants-and-discriminators.md +25 -0
  771. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -1
  772. package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +34 -0
  773. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +236 -18
  774. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +54 -1
  775. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +35 -0
  776. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +327 -11
  777. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +140 -4
  778. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
  779. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +155 -5
  780. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +165 -0
  781. package/dist/knowledge/skills/seeding-authoring/SKILL.md +9 -1
  782. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +4 -0
  783. package/dist/knowledge/skills/seeding-operations/SKILL.md +33 -29
  784. package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +13 -5
  785. package/dist/knowledge/skills/seeding-operations/references/data-seeding-cron-scheduler.md +67 -74
  786. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +97 -24
  787. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +205 -0
  788. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +205 -0
  789. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +229 -0
  790. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +38 -3
  791. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +211 -14
  792. package/dist/knowledge/skills/spec-component-update/SKILL.md +30 -11
  793. package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +10 -0
  794. package/dist/knowledge/skills/spec-feature-update/SKILL.md +47 -9
  795. package/dist/knowledge/skills/spec-resource-update/SKILL.md +3 -0
  796. package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +32 -5
  797. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +30 -0
  798. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +1 -0
  799. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +13 -2
  800. package/dist/knowledge/skills/views-add-custom-view/references/framework-view-scope-and-full-custom-api.md +24 -0
  801. package/dist/knowledge/skills/views-app-level/SKILL.md +1 -0
  802. package/dist/knowledge/skills/views-app-level/references/framework-view-scope-and-full-custom-api.md +24 -0
  803. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +1 -0
  804. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +1 -0
  805. package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +64 -0
  806. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +3 -0
  807. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +3 -3
  808. package/dist/knowledge/skills/views-execution-authoring/references/framework-user-facing-error-message-api.md +50 -0
  809. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +43 -7
  810. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +21 -1
  811. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +21 -0
  812. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +41 -1
  813. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +735 -211
  814. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +54 -7
  815. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +67 -1
  816. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -0
  817. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +19 -5
  818. package/dist/knowledge/skills/website-page-authoring/SKILL.md +94 -7
  819. package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +126 -0
  820. package/dist/knowledge/skills/website-section-contact/SKILL.md +96 -146
  821. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -20
  822. package/dist/knowledge/skills/website-section-cta/SKILL.md +19 -20
  823. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -20
  824. package/dist/knowledge/skills/website-section-faq/SKILL.md +19 -20
  825. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -20
  826. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +19 -20
  827. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -20
  828. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +19 -20
  829. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -20
  830. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +19 -20
  831. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -20
  832. package/dist/knowledge/skills/website-section-hero/SKILL.md +37 -26
  833. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -20
  834. package/dist/knowledge/skills/website-section-pricing/SKILL.md +19 -20
  835. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -20
  836. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +19 -20
  837. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -20
  838. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +14 -1
  839. package/dist/knowledge/skills/worker-authoring/SKILL.md +164 -0
  840. package/dist/knowledge/skills/worker-authoring/examples/worker-route.example.md +98 -0
  841. package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +65 -0
  842. package/dist/knowledge/topic-index.json +5335 -1010
  843. package/dist/tsconfig.build.tsbuildinfo +1 -1
  844. package/dist/tsconfig.tsbuildinfo +1 -1
  845. package/package.json +4 -4
  846. package/dist/knowledge/references/example.provider.contribution.backend-billing.md +0 -12
  847. package/dist/knowledge/skills/configure-billing/references/example-provider-contribution-and-backend-config.md +0 -48
  848. /package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/structured-artifact-action.json +0 -0
@@ -1,26 +1,31 @@
1
1
  {
2
2
  "ref": "bottom_up.foundation",
3
- "version": "0.2.0",
3
+ "version": "0.2.4",
4
4
  "phase": "bottom_up",
5
- "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.",
6
- "functionalTopics": [
7
- "configure_application_foundation"
8
- ],
5
+ "intent": "Bottom-up foundation — turn the approved domain plan and top-down definitions into a configured, bootable application skeleton. For a fresh application, use wildo init in an empty destination before refining its generated configuration; preserve existing projects and use their repair/composition paths. Author capabilities, modules and providers from the approved plan, verify application knowledge delivery (wildo assets sync refreshes installed assets), then run wildo setup --non-interactive and wildo local init with their prerequisites. These tools exist; their successful invocation and postconditions must be observed in the current run. The registered foundation executor composes module/resource shells and tenancy configuration; it does not run this full init/assets/setup sequence. This methodology states the prerequisites and postconditions to fulfil around that execution. It emits no artifact: the deliverable is the application source, configured module registrations and verified initialization. Record the reasons for configuration choices beside those choices. Runs after the domain plan is approved in the bottom_up phase; business resource implementation belongs to the later build work.",
9
6
  "preconditions": [
10
7
  {
11
- "kind": "phase_is",
12
- "phase": "bottom_up"
8
+ "kind": "artifact_exists",
9
+ "selector": {
10
+ "family": "domain-plan"
11
+ }
12
+ },
13
+ {
14
+ "kind": "artifact_expected",
15
+ "selector": {
16
+ "family": "vision-brief"
17
+ }
13
18
  },
14
19
  {
15
20
  "kind": "artifact_exists",
16
21
  "selector": {
17
- "family": "domain-plan"
22
+ "family": "integration-plan"
18
23
  }
19
24
  },
20
25
  {
21
26
  "kind": "artifact_exists",
22
27
  "selector": {
23
- "family": "vision-brief"
28
+ "family": "capability-composition"
24
29
  }
25
30
  }
26
31
  ],
@@ -28,32 +33,29 @@
28
33
  {
29
34
  "family": "domain-plan"
30
35
  },
31
- {
32
- "family": "vision-brief"
33
- },
34
- {
35
- "family": "market-snapshot"
36
- },
37
36
  {
38
37
  "family": "business-model"
39
38
  },
40
39
  {
41
- "family": "requirements"
40
+ "family": "capability-composition"
42
41
  },
43
42
  {
44
- "family": "roadmap"
43
+ "family": "integration-plan"
45
44
  }
46
45
  ],
47
46
  "outputs": [],
47
+ "stepOutputs": [],
48
48
  "method": {
49
- "guidance": "# Foundation — Domain Plan → Configured, Bootable App Skeleton (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology, and part of the greenfield tooling it\n> sequences does not exist yet.** The foundation *sequence* below is a working first cut —\n> the capability-derivation heuristic, the module-registration convention, and\n> the provider-selection rubric are deliberately explicit so they can be tuned\n> against real runs. The deterministic steps that *materialize the skeleton* and\n> *install app-knowledge* are a later greenfield-enablement phase and are **not\n> built**. Those two steps are authored as `// TODO CLI COMMAND:` placeholders;\n> headless setup and verified local initialization are registered commands. **This playbook is the\n> METHOD — the description of the foundation sequence — not a runnable\n> foundation.** If you find yourself building or wiring the greenfield CLI\n> tooling, stop: that is out of this playbook's scope.\n\n## Where you are in the journey\n\nThis is the **foundation** playbook — the point in the **bottom-up** phase where\nthe *plan* becomes a *bootable app*. It runs **after** the `bottom_up.domain-plan`\nplaybook produced (and the creator approved) the **domain plan**: the module\ndecomposition, the per-module resource inventory, and the inter-resource\nrelationship intents. Its preconditions — `phase_is bottom_up` and\n`artifact_exists domain-plan` and `artifact_exists vision-brief` — mean the journey\nhas entered the build-shaping phase and the two load-bearing artifacts are present:\nthe **domain plan** (whose modules you register) and the **vision brief** (whose\ncompliance and vision constraints drive which engine capabilities you enable). The\nroute-bound `transition_committed` fact that authorized and applied crossing from top-down into\nbottom-up was the domain-plan playbook's duty (it is the first bottom-up playbook);\nyou do not re-cross that boundary — the domain plan's existence already sits behind\nit.\n\nYou are not re-opening the domain plan here — you are turning an *approved* plan\ninto the *configured application skeleton the build loop then fills in*.\n\n## What this playbook does\n\nYou are the **foundation engineer**. This playbook reads the approved domain plan\nand the vision brief, then configures and brings up the application skeleton so the\nbuild loop has a real workspace to author into. You perform a **mixed sequence**\n(hence the `composite` executor — the runner sequences the tiers per this guidance):\na config/skeleton **authoring** pass, then a **deterministic bring-up** pass. The\nwork, in order:\n\n1. **Derive the engine capabilities** from the compliance/vision constraints (and\n the market/business-model facts) and enable them in `./wildo.saas.config.ts`.\n2. **Declare the domain-plan's modules** at the SaaS root (they are registered across\n the runtimes after Step 4 materializes the skeleton, so it boots with them).\n3. **Select the providers** the enabled capabilities need.\n4. **Run the deterministic bring-up** — materialize the skeleton, install\n app-knowledge, `wildo setup --non-interactive`, then `wildo local init`.\n\nYou emit **no artifact**. The deliverable is the app itself: `./wildo.saas.config.ts`,\nthe materialized skeleton, and a verified local initialization. Record *why* each\ncapability, module and provider was chosen in the config's own comments, where the\nnext reader of that file will find it.\n\n(A `foundation-manifest` artifact was declared here until 2026-08-25 and is now\nretired with the app-creation verification/digest aspect. It was a bookkeeping record\nof decisions the config already carries — deleting it costs no fact about the app.)\n\nThis is a **foundation pass**. You enable capabilities, declare modules as shells,\nselect providers, and bring the skeleton up. You do **not** author resource schemas,\nfields, ui-behavior, views, or navigation — that is the **build loop's** job,\ndownstream of this foundation.\n\n## Read state first — the artifacts you read, the files you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*. Before configuring\nanything:\n\n1. Read the current journey state and scope through the `journey-status` skill (it\n owns the read; do not re-derive it here). Confirm the domain plan is present and\n approved, and check whether a `./wildo.saas.config.ts` already exists from an\n earlier run (refine it, do not re-author — see below).\n2. Read the **domain plan** (`domain-plan` family — the modules to register + their\n resource inventory) and the **vision brief** (`vision-brief` — the compliance and\n vision constraints that are the **primary** driver of capability selection).\n **Contextual** reads that sharpen the choices (they are *not* preconditions — read\n them if present, and note that the `business-model` may be absent, per the top-down\n phase-gate's optional posture):\n - the **market-snapshot** (`market-snapshot`) — its ICPs sharpen capability\n selection (a B2B / organization-scoped ICP → the `organizations` capability);\n - the **business-model** (`business-model`) — a paid plan → the billing capability\n (absent business model = no billing capability derived from it);\n - the **relationship drafts** inside the domain plan (the inter-resource relationships the build loop will\n wire — they can hint at which capabilities a module needs);\n - the **requirements** (functional/non-functional needs a capability may satisfy);\n - the **roadmap** (which modules are MVP-critical, so you enable what the first\n release needs and defer the rest).\n\n// TODO CLI COMMAND: wildo context journey-status\n// (read current journey scope + approved artifacts + any existing foundation config)\n// TODO CLI COMMAND: wildo context domain-plan\n// (read the modules to register + their per-module resource inventory)\n\nYou **read** `domain-plan` + `vision-brief` + `market-snapshot` + `business-model`\n+ `requirements` + `roadmap` (the domain plan carries its relationship drafts); you **write**\n`./wildo.saas.config.ts` and the materialized skeleton — app files, committed to git,\nwhich is where the record of what was decided lives.\n\n## Step 1 — Derive and enable the engine capabilities\n\nEngine capabilities are the framework surfaces the app turns on (organizations,\nbilling, notifications, audit trails, data residency, and so on). **Derive them from\nthe definition set — do not guess:**\n\n1. **Compliance/vision constraints → capabilities (the primary driver).** Walk the\n vision brief's constraints. A compliance constraint implies a capability (a privacy-law /\n data-residency constraint → the residency/audit capability; an external-assurance constraint →\n audit trails). A vision fact implies a capability (an organization-scoped product →\n `organizations`).\n2. **Market / business-model facts → capabilities (contextual sharpener).** A B2B or\n organization-scoped ICP in the `market-snapshot` → the `organizations` capability; a\n paid plan in the `business-model` → billing. Treat these as sharpeners over the\n primary compliance/vision derivation — and remember the `business-model` may be\n absent (then derive no billing capability from it).\n3. **Domain-plan needs → capabilities.** A module whose capability clearly needs a\n framework surface (a module that sends transactional email → notifications) turns\n on that capability.\n4. **Enable only what the definition set justifies.** Every enabled capability must\n trace to a compliance/vision constraint, a market/business-model fact, or a\n domain-plan module need. Do **not** enable a capability nothing asks for — that is\n speculative surface area (a coherence CONCERN — see the quality gate). Conversely,\n a compliance constraint that requires a capability you did **not** enable is a\n coverage GAP.\n\nThe `config-saas` skill carries the vocabulary for the `engineCapabilities` block of\n`./wildo.saas.config.ts`; read it to enable capabilities idiomatically. Record each\nenabled capability **and its justification** as a comment beside it in the config.\n\n## Step 2 — Declare the domain-plan's modules (register across runtimes after materialization)\n\n**Mind the ordering.** At *config-authoring* time (this step, before the skeleton\nexists) you can only **declare** the modules at the SaaS root. The shared / frontend /\nbackend module registry files do not exist until Step 4 materializes the skeleton, so\nthe cross-runtime **registration** happens *after* materialization — do not edit\nregistry files the skeleton has not yet created.\n\n1. **Declare each module at the SaaS root (now).** Add each domain-plan module to the\n `modules` composition in `./wildo.saas.config.ts` (the `config-saas` skill owns this\n surface). This declares the module's *existence* and is exactly what the skeleton\n materialization (Step 4) builds the per-module workspaces and registries from.\n2. **Register across the runtimes (after Step 4 materializes the skeleton).** Once the\n skeleton exists, each declared module is registered across the shared / frontend /\n backend registries so every runtime loads it — regenerated by `config sync` from the\n declared modules where the tooling supports it, or wired with the `module-registration`\n skill (distinct from `config-saas`, which only declares existence at the root). At\n foundation depth you register the module **shells** (the module exists and boots); the\n resources *inside* each module are authored by the build loop.\n3. **Declare every domain-plan module — and no more.** A module the domain plan named\n that is missing from the config is a GAP; a module in the config the domain plan did\n not name is an unjustified-module CONCERN. Record the declared modules (each traced\n to its domain-plan module) as a comment beside it in the config.\n\n**Do not author the resources here.** The domain plan's per-module resource inventory\ntells you *what* resources each module will own, but authoring their schemas, fields,\nand config is the **build loop's** job. If you catch yourself writing a resource\nschema, stop: that is out of this playbook's depth.\n\n## Step 3 — Select the providers\n\nEnabled capabilities that reach an external service need a **provider** (billing → a\npayment provider; notifications/email → an email provider; file storage → an object\nstore). For each such capability, select and wire the provider scope +\n`providerConfigurations` in `./wildo.saas.config.ts` (the `config-saas` skill covers\nthe provider surfaces):\n\n- **Every provider matches a declared capability.** A provider wired for no enabled\n capability is a CONCERN; an enabled capability that needs a provider with none\n selected is a GAP.\n- **Do not seed secrets here.** Provider *selection* (which provider, which scope) is\n foundation; the per-environment secret material is seeded by the deterministic\n bring-up / environment step, not authored inline. Record the selected providers\n (each matched to its capability) as a comment beside it in the config.\n\n## Step 4 — The deterministic bring-up sequence (partially deferred)\n\nWith the config authored, run the **deterministic bring-up** in prerequisite order.\nThe skeleton template and app-knowledge installer remain deferred; do not invent\nthem. Headless `wildo setup` and `wildo local init` are registered and should be\nexecuted after the app structure exists.\n\n1. **Materialize the app skeleton** — create the `./frontend/`, `./shared-lib/`,\n `./backend-api/`, `./specifications/`, and `./infrastructure/` workspaces + the\n module registries from the empty-app template, so the declared modules have a real\n workspace.\n\n // TODO CLI COMMAND: wildo materialize skeleton\n // (scaffold app/ shared-lib/ backend-api/ specifications/ + module registries — greenfield tooling, deferred)\n\n2. **Install app-knowledge** — drop the compiled skills / rules / agents into the\n project's agent-config folders so the build loop's coding agent reads them\n naturally with cwd at the app root.\n\n // TODO CLI COMMAND: wildo install app-knowledge\n // (install compiled skills/rules/agents into the app's .claude/ — greenfield tooling, deferred)\n\n3. **Run setup** — configure the app from the authored `./wildo.saas.config.ts` and\n the `./infrastructure/` env configs (the `infra-environment-config` skill owns the\n typed infra env files; the `local-environment-bootstrap` skill owns the `wildo`\n lifecycle). Headless setup is registered and fail-closed on the administrator seed\n environment variables; it mints the environment generation without placeholders.\n\n ```bash\n wildo setup --non-interactive\n ```\n\n4. **Initialize and verify the project** — run the registered convergence journey.\n It regenerates artifacts, starts and readiness-gates backing services, reconciles\n platform Mongo state and credentials, starts native platform services, registers the\n app once, emits all runtime projections, and executes a signed managed-config read.\n\n ```bash\n wildo local init\n ```\n\nReport the status of each bring-up step to the creator in your result. Skeleton\nmaterialization and app-knowledge installation remain deferred; setup and local\ninitialization are executable once those app files exist and must be recorded from their\nreal exit/postcondition result rather than marked complete from intent.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not disable a capability, drop a module,\n or re-select a provider that is already correct. Only enable a newly-justified\n capability, register a newly-added domain-plan module, or correct a provider where\n the definition set genuinely changed.\n- **Reuse existing module ids and provider scopes.** A module already registered keeps\n its id; a provider already selected keeps its scope — never mint a second one for the\n same module/capability.\n- **Follow the definition set.** If the domain plan added a module or the vision brief\n added a compliance constraint since the last run, reflect it (register the module,\n enable the capability) — do not re-derive the whole configuration from scratch. The\n delta is visible in `git diff` on the config, which is the record.\n\n## Quality gate — `foundation-configured-coherently` (declarative at scaffold depth)\n\nThe foundation is checked against the `foundation-configured-coherently` **reviewer\nchecklist** (see the end of this method): five invariants (capability derivation, module registration, provider coverage,\nsequence order, and foundation-depth boundary discipline), each marked PASS / CONCERN /\nGAP.\n\nThis checklist is **declarative**: no runtime executes it (rubric-only judge gates were retired at the flexible-intelligence hard cut — judgment runs only through a compiled Evaluation Treatment, and this playbook has none yet), so it ships as the **creator's review checklist** — nothing runs it automatically. The **trust floor** for accepting the foundation today is the\ncreator's `approve_result` review of the produced config and the bring-up result. There is\nintentionally **no deterministic gate**: config validation is a `wildo` CLI concern\n(`config sync` / validate), not a validator in the journey-artifact schemaRef\nvocabulary. When the greenfield tooling lands, the non-bypassable floor still\nhard-gates the real destructive / off-machine infra bring-up regardless of this gate.\n\n## Scaffold-depth and tooling-deferral boundary\n\nKeep this playbook at scaffold depth **and** honour the tooling deferral. Explicitly\n**out of scope here**:\n\n- **The remaining greenfield CLI tooling itself.** The skeleton-materialization\n template and app-knowledge installer do **not** exist yet and are a later\n greenfield-enablement phase. Their two `// TODO CLI COMMAND:` placeholders must not\n be invented. `wildo setup --non-interactive` and `wildo local init` do exist and are\n the registered lifecycle once the app structure is present.\n- **Resource / field / schema authoring.** The config declares modules as shells and\n enables capabilities; it does **not** author resource schemas, fields, enums,\n decorators, ui-behavior, views, or navigation. That is the build loop. If you catch\n yourself writing a resource, stop.\n- **Re-introducing a foundation artifact.** The `foundation-manifest` family was\n retired on 2026-08-25 with the app-creation verification/digest aspect. Do **NOT**\n reshape `_core` to bring it back: the config file and its git history already carry\n every decision it recorded.\n- **Deep capability / provider modelling.** A defended capability-selection model\n (per-compliance-regime obligation → capability mapping, provider cost/feature\n matrices, multi-provider fallback) is a later depth pass. You derive capabilities\n from the definition set with the v1 heuristic above — not a solved obligation graph.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at scaffold\ndepth — depth (and the greenfield tooling) are dedicated later passes done once,\nholistically.\n\n## What you emit\n\n- The authored **`./wildo.saas.config.ts`** (an app file) — the enabled engine\n capabilities, the registered modules, and the selected providers — plus the\n registered module shells across the runtimes and (when the tooling lands) the\n brought-up skeleton.\n- The **bring-up result** reported to the creator: the status of each step, taken from\n its real exit/postcondition rather than from intent. This is a report, not a stored\n artifact — nothing reads it back.\n\nThe creator reviews the result (approval posture `approve_result`) before it is\naccepted as the journey's foundation, which the bottom-up build loop then fills in\nwith authored resources, operations, UX, and integrations.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state and scope,\n and confirm the approved domain plan + vision brief are in place to configure from.\n- `.claude/skills/config-saas/SKILL.md` — the `./wildo.saas.config.ts` authoring\n surface: `engineCapabilities`, `modules`, provider scopes, and `providerConfigurations`.\n- `.claude/skills/module-registration/SKILL.md` — register each domain-plan module\n across the shared / frontend / backend registries so the skeleton boots with it\n (distinct from `config-saas`, which only declares module existence at the root).\n- `.claude/skills/infra-environment-config/SKILL.md` — the typed `./infrastructure/`\n environment configs (backing services, public domain, service auth) the bring-up needs.\n- `.claude/skills/local-environment-bootstrap/SKILL.md` — the `wildo` lifecycle\n (`setup`, `local init`, `local reinit`, `local dev`) for deterministic initialization,\n repair, clean-room recovery, and runtime start.\n\n## Reviewer checklist — `foundation-configured-coherently`\n\nFormerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is kept here, verbatim, minus the retired runner's closing sentence:\n\nJudge whether the authored foundation (the ./wildo.saas.config.ts composition + the materialized skeleton) is a coherent realisation of the approved domain plan and the top-down definition set. Assess five invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) CAPABILITY DERIVATION — every enabled engine capability traces to a compliance/vision, business-model, market, or domain-plan need; unjustified capabilities are a CONCERN and missing required capabilities are a GAP. (2) MODULE REGISTRATION — every approved domain-plan module is declared and registered across runtimes; missing modules are a GAP and extra modules are a CONCERN. (3) PROVIDER COVERAGE — every provider serves a declared capability and every provider-backed capability has a provider. (4) SEQUENCE ORDER AND PROOF — author config → materialize skeleton → install app-knowledge → wildo setup --non-interactive → wildo local init. Treat setup intent, container health, or an initialization marker as insufficient: local init must reach its signed managed-config-read postcondition. (5) BOUNDARY DISCIPLINE — stay at foundation depth and do not author resources, fields, ui-behavior, views, or navigation. Do not invent the still-deferred skeleton/app-knowledge installer commands; headless setup and local init are registered and should be executed once the structure exists. This reviewer checklist is declarative; creator approval is the trust floor.\n",
49
+ "guidance": "# Foundation — Domain Plan → Configured, Bootable App Skeleton (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis method composes existing tooling: `wildo init` creates the SaaS skeleton and\nattempts knowledge delivery, `wildo assets sync` refreshes that knowledge, and\n`wildo setup --non-interactive` followed by `wildo local init` configures and verifies\nthe local environment. It is guidance consumed by the application-creation lane,\nnot an automatically executed CLI script. The registered foundation executor composes\nmodule and resource shells and tenancy configuration from the domain plan; it does\nnot execute this full init/assets/setup sequence. Fulfil those prerequisites and\npostconditions separately and record actual command outcomes. Tool availability\nalone does not prove that a foundation run succeeded.\n\n## Where you are in the journey\n\nThis is the **foundation** playbook — the point in the **bottom-up** phase where\nthe *plan* becomes a *bootable app*. It runs **after** the `bottom_up.domain-plan`\nplaybook produced (and the creator approved) the **domain plan**: the module\ndecomposition, the per-module resource inventory, and the inter-resource\nrelationship intents. Its preconditions — `phase_is bottom_up` and\n`artifact_exists domain-plan` and `artifact_expected vision-brief` — mean the journey\nhas entered the build-shaping phase and the load-bearing artifact is present: the\n**domain plan**, whose modules are registered and whose tenancy decides two of the three\nderived capabilities. The vision is SEQUENCING here rather than readiness (#1434): nothing\nin this playbook reads its content, and it is enforced harder upstream — the market\nsnapshot and the requirements both gate on it, and the domain plan gates on those. The\nroute-bound `transition_committed` fact that authorized and applied crossing from top-down into\nbottom-up was the domain-plan playbook's duty (it is the first bottom-up playbook);\nyou do not re-cross that boundary — the domain plan's existence already sits behind\nit.\n\nYou are not re-opening the domain plan here — you are turning an *approved* plan\ninto the *configured application skeleton the build loop then fills in*.\n\n## What this playbook does\n\nYou are the **foundation engineer**. This playbook reads the approved domain plan\nand the vision brief, then configures and brings up the application skeleton so the\nbuild loop has a real workspace to author into. First inspect the destination: create\na fresh skeleton with `wildo init` in an empty directory, or preserve the existing\napplication. Then perform the configuration-authoring and bring-up steps below.\nThe method describes their order; it does not itself execute the commands.\n\n1. **The engine capabilities are DERIVED for you**, from the approved domain plan's tenancy and the\n business model's revenue model. You do not choose them — see \"Engine capabilities\" below.\n2. **Declare the domain-plan's modules** at the SaaS root (they are registered across\n the runtimes after the skeleton is present, so it boots with them).\n3. **Select the providers** the enabled capabilities need.\n4. **Record the compliance declarations you were given** — the operating entity and\n the jurisdictions, from the elicitation answers, into `./wildo.saas.config.ts`.\n See `config-saas` and its `references/compliance-declarations.md`.\n5. **Verify and bring up the configured project** — check the existing skeleton\n and knowledge delivery, run `wildo setup --non-interactive`, then `wildo local init`.\n\nYou emit **no artifact**. The deliverable is the app itself: `./wildo.saas.config.ts`,\nthe materialized skeleton, and a verified local initialization. Record *why* each\ncapability, module and provider was chosen in the config's own comments, where the\nnext reader of that file will find it.\n\nThis is a **foundation pass**. You enable capabilities, declare modules as shells,\nselect providers, and bring the skeleton up. Deterministic composition may create\nresource shells from the domain plan. Business-specific fields, processing, UI behavior,\nviews and navigation are the downstream build work; a generated shell does not\ncomplete that work.\n\n## Read state first — the artifacts you read, the files you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*. Before configuring\nanything, inspect the target directory. For a new application, run `wildo init`\nin an empty destination first, then refine its generated configuration from the\napproved plan. Do not write the planned config into an empty destination and then\nexpect initial scaffolding to merge around it. For an existing application, keep\nits source and use the documented repair/composition paths; never scaffold over it.\nThen:\n\n1. Read the current journey state and scope through the `journey-status` skill (it\n owns the read; do not re-derive it here). Confirm the domain plan is present and\n approved, and check whether a `./wildo.saas.config.ts` already exists from an\n earlier run (refine it, do not re-author — see below).\n2. Read the **domain plan** (`domain-plan` family — the modules to register + their\n resource inventory). The executor also reads the landed **business model** if there is\n one, for the billing capability alone; it may legitimately be absent, per the top-down\n phase-gate's optional posture.\n\n **Nothing else is read.** This list used to continue with the market snapshot (\"its ICPs sharpen\n capability selection\"), the requirements and the roadmap (\"which modules are MVP-critical, so you\n enable what the first release needs\"). None of the three reaches the executor, and none ever did\n (#1434). They are no longer declared as inputs either, so the declaration and the prose now say\n the same thing.\n\n// Operator affordances (the executor itself is handed the domain-plan VALUE directly):\n// `wildo context journey` — the eligibility board, runs in flight\n// `wildo context info specification-artifacts` — per-family landed state and rendered content\n\nThe executor **reads** `domain-plan` (handed to it, relationship drafts included) and the landed\n`business-model`; it **writes** `./wildo.saas.config.ts` and the materialized skeleton — app files,\ncommitted to git, which is where the record of what was decided lives.\n\nThis line used to name six families (#1434). Four of them reached nothing.\n\n## Step 1 — Derive and enable the engine capabilities\n\nEngine capabilities are the framework surfaces the app turns on (organizations, billing,\nnotifications, audit trails, and so on). **THE EXECUTOR DERIVES THEM. Nothing here chooses one.**\n\nExactly three are derivable today, and each from one declared value:\n\n| capability | derived from |\n|---|---|\n| `ORGANIZATIONS` | the domain plan's `tenancy` is `organizations` |\n| `EMAIL_TRANSACTIONAL` | the same — tenant invitations send mail |\n| `BILLING` | the business model's revenue model charges users |\n\n**Compliance constraints do NOT select a capability, and this method said for months that they were\n\"the primary driver\".** They are not, and the reason is recorded where the derivation lives\n(`FOUNDATION_CAPABILITY_BASIS`, which is TOTAL over the capability vocabulary and names why each\nremaining one is underivable). The clearest case is the one this method used to point at: where an\naudit trail must LIVE — a ledger, a SIEM — is an operator decision about retention and independence\nrather than a product fact, and leaving that capability out removes no control objective, because\nassurance reads the application's own audit store.\n\nA capability nothing derives is not enabled by guessing. It is enabled deliberately, later, by\nwhoever decides it — which is why the basis map records a reason per capability instead of a\nquestion.\n\nHistorical note, kept because it is the defect rather than a detail (#1434): this section described a\nderivation the runtime cannot perform — four steps of \"walk the constraints\", \"treat these as\nsharpeners\", \"every enabled capability must trace to a compliance constraint\" — and a reader believed\ncompliance constraints shaped the foundation. Nothing walked anything. The market snapshot, the\nrequirements and the roadmap were declared inputs of this playbook for the same reason and reached\nthe same nobody; they are no longer declared.\n\nThe `config-saas` skill carries the vocabulary for the `engineCapabilities` block of\n`./wildo.saas.config.ts`. The executor writes that block; read the skill when you need to understand\nwhat an enabled capability means, not to decide one.\n\n## Step 1b — Apply the capability composition's optional packages\n\nWhen a `capability-composition` has landed (`bottom_up.capability-composition`), the executor\napplies every scenario it marks NEEDED after the domain scenarios below — the marketing website\n(`add-website`) and the documentation portal (`add-technical-doc`) today — with the application's\nown host facts: its slug and display name from `wildo.saas.config.ts`, the public domain from its\ninfrastructure environments (a remote one first, `localhost` when none declares one), and its port\nblock (website = app port + 1, docs = app port + 2, the convention the dogfood applications use).\nA package whose workspace already exists is left alone and reported as already composed. The run\nrecord names **every scenario applied and every scenario declined with the declaration each came\nfrom** (`compositionScenarios`), so a reader sees why the application has a website — or why not —\nwithout re-deriving it.\n\n## Step 2 — Declare the domain-plan's modules (register across runtimes after materialization)\n\nThe skeleton supplies the root workspaces and registry structure; declaring a\nmodule in configuration alone does not implement its package or contributions.\n\n1. **Declare each approved module at the SaaS root.** Use `config-saas` for the\n module's application configuration and preserve existing module identifiers.\n2. **Materialize and register module shells.** Use the delivered module-composition\n scenario and `module-registration` guidance to create the corresponding shared,\n backend and frontend contributions. Inspect the resulting registry exports;\n `config sync` is not a substitute for authored module implementation. At foundation\n depth the shells must load; business-specific resource behavior remains the build\n loop's work.\n3. **Declare every domain-plan module — and no more.** A module the domain plan named\n that is missing from the config is a GAP; a module in the config the domain plan did\n not name is an unjustified-module CONCERN. Record the declared modules (each traced\n to its domain-plan module) as a comment beside it in the config.\n\n**Do not author the resources here.** The domain plan's per-module resource inventory\ntells you *what* resources each module will own, but authoring their schemas, fields,\nand config is the **build loop's** job. If you catch yourself writing a resource\nschema, stop: that is out of this playbook's depth.\n\n## Step 3 — Select the providers\n\nEnabled capabilities that reach an external service need a **provider** (billing → a\npayment provider; notifications/email → an email provider; file storage → an object\nstore). For each such capability, select and wire the provider scope +\n`providerConfigurations` in `./wildo.saas.config.ts` (the `config-saas` skill covers\nthe provider surfaces). A value the vendor issues per deployment — an OAuth client ID, a\nfrontend SDK DSN — is authored in each environment's\n`./infrastructure/<env>/wildo.infra.<env>.config.ts > providerConfigurations` instead (the\n`infra-environment-config` skill):\n\n- **Every provider matches a declared capability.** A provider wired for no enabled\n capability is a CONCERN; an enabled capability that needs a provider with none\n selected is a GAP.\n- **Do not seed secrets here.** Provider *selection* (which provider, which scope) is\n foundation; the per-environment secret material is seeded by the deterministic\n bring-up / environment step, not authored inline. Record the selected providers\n (each matched to its capability) as a comment beside it in the config.\n\n**The choice itself is the creator's, and the interview carries it.** Billing and SMS are\nthe two capabilities whose every provider needs an account, so the executor cannot pick one:\nit reads the `billing-provider` and `sms-provider` answers from the dossier, declares the chosen\nprovider in the backend scope, selects it as primary and enables the capability. The provider's\nrequired credentials are recorded on the run result as OWED — the application boots, and the\nprovider answers once an operator sets them. Answering `none` — the interview requires an answer to\nevery question, so \"decide later\" is an option — leaves the capability owed exactly as before. The\noptions are the engine providers serving the capability plus `none`; the interview validator refuses\nanything else before the run starts. Email is the exception the executor decides itself: it has a\ncredential-free development substitute (`email-preview`) and needs no choice.\n\n## Step 4 — Record the compliance declarations (only what you were told)\n\nThe creator answered `operating-entity` and `operating-jurisdictions`. Write those answers\ninto `operatorComplianceIdentity` and `operatingJurisdictions`, and **nothing else**.\n\n- **Record the PART you were given.** Every part of `operatorComplianceIdentity` is\n independently declarable, so a creator who named the company and not its lawful bases\n gets `legalEntityName` and `registeredAddress` written and the rest left absent. A\n missing part is reported downstream as outstanding; it does not block anything here.\n- **NEVER invent one.** Not a company name, not an address, not a privacy contact, and\n above all not a lawful basis — that is a legal determination, and `CONSENT` in\n particular would tell a person their data rests on an agreement they could withdraw.\n A produced privacy notice quotes these as fact. An absent declaration is reported as an\n open gap a reader can see; an invented one is published.\n- **Omit the key entirely when you were told nothing.** Absence means \"nobody answered\",\n which is the honest state and the one every consumer already renders correctly. An\n empty object is refused by the schema precisely because it would satisfy the field while\n disclosing nothing.\n- **A jurisdiction needs its `basis`.** \"eu\" alone does not say whether you are established\n there, sell there, or hold data about people there, and those imply different obligations.\n If the creator gave a place without a reason, record neither — ask, or leave it out.\n\nThis step CANNOT fail the run. If the creator answered nothing, write nothing and continue:\nthe application boots, and the gap is visible where it matters rather than here.\n\n(A `foundation-manifest` artifact was declared here until 2026-08-25 and is now\nretired with the app-creation verification/digest aspect. It was a bookkeeping record\nof decisions the config already carries — deleting it costs no fact about the app.)\n\n## Step 5 — Verify materialization and bring up the environment\n\nRun the existing commands from the intended application root with their documented\nprerequisites. Keep application structure, delivered knowledge and running services\nas separately verified results.\n\n1. **Verify the skeleton.** A fresh project starts with `wildo init` in an empty\n destination before the configuration-authoring steps above. Check `frontend/`,\n `shared-lib/`, `backend-api/`, `specifications/` and the generated configuration.\n On a repeat run, preserve existing source; use init's repair path or the relevant\n composition scenario instead of regenerating the project as a new application.\n\n2. **Verify application knowledge delivery.** Init attempts delivery from the\n installed packages and reports delivered or skipped assets. If dependency\n installation was skipped or a package is unavailable, install the required\n packages, then refresh the supported skills/rules and framework assets:\n\n ```bash\n wildo assets sync\n ```\n\n <!-- fwk-provenance-waiver: the command below is named in order to be REFUSED — `wildo fwk` needs a framework workspace and errors inside a generated application, which is exactly why an agent that might reach for it has to recognise the name; translating it away would leave the prohibition with nothing to prohibit. -->\n Read the result and inspect the delivered application guidance. Do not assume\n arbitrary agents/hooks are installed, and do not substitute a framework-developer\n delivery flow for this one — this command is how an application receives them.\n\n3. **Run setup** — configure the app from the authored `./wildo.saas.config.ts` and\n the `./infrastructure/` env configs (the `infra-environment-config` skill owns the\n typed infra env files; the `local-environment-bootstrap` skill owns the `wildo`\n lifecycle). Headless setup is registered and fail-closed on the administrator seed\n environment variables; it mints the environment generation without placeholders.\n\n ```bash\n wildo setup --non-interactive\n ```\n\n4. **Initialize and verify the project** — run the registered convergence journey.\n It regenerates artifacts, starts and readiness-gates backing services, reconciles\n platform Mongo state and credentials, starts native platform services, registers the\n app once, emits all runtime projections, and executes a signed managed-config read.\n\n ```bash\n wildo local init\n ```\n\n5. **Know what a PostgreSQL store owes — and that you do not write its baseline here.** Read the\n store selection you authored in the infra env config:\n\n ```bash\n rg -n \"applicationDatabase\" infrastructure/*/wildo.infra.*.config.ts\n ```\n\n Absent, or MongoDB: there is nothing to do — a collection exists on first write, there is no\n plan, and no migration is ever owed.\n\n `engine: DatabaseEngine.POSTGRESQL`: nothing creates a table implicitly, so until the INITIAL\n migration exists the backend refuses to boot on every table it declares. Do NOT accept a baseline\n with `wildo db diff --update-lockfile`: that writes the lockfile and NO migration, so it records a\n plan whose tables were never created and the boot gate still refuses.\n\n The build loop owns that migration. For an application that declares PostgreSQL and has no\n `backend-api/migrations/schema-plan.lock.json`, the dispatch host derives a `database-migrations`\n step; it runs `wildo db generate`, which, with no lockfile, renders the whole model as the initial\n migration and writes the baseline in the same invocation. The two are one change and are committed\n together. It needs a built `backend-api` (the plan is computed by importing the compiled backend\n registry), so report the store you found and leave the migration to that step.\n\nReport the status of each bring-up step to the creator from its real exit and\npostcondition results. A skipped knowledge delivery or unsuccessful initialization\nis not completion, even when source files exist.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not disable a capability, drop a module,\n or re-select a provider that is already correct. Only enable a newly-justified\n capability, register a newly-added domain-plan module, or correct a provider where\n the definition set genuinely changed.\n- **Reuse existing module ids and provider scopes.** A module already registered keeps\n its id; a provider already selected keeps its scope — never mint a second one for the\n same module/capability.\n- **Follow the definition set.** If the domain plan added a module since the last run,\n reflect it (register the module) — do not re-derive the whole configuration from\n scratch. The delta is visible in `git diff` on the config, which is the record. A new\n compliance constraint does NOT enable a capability here; see Step 1 for why.\n\n## Quality gate — `foundation-configured-coherently` (declarative at scaffold depth)\n\nThe foundation is checked against the `foundation-configured-coherently` **reviewer\nchecklist** (see the end of this method): five invariants (capability derivation, module registration, provider coverage,\nsequence order, and foundation-depth boundary discipline), each marked PASS / CONCERN /\nGAP.\n\nThis checklist is **declarative**: no runtime executes it (rubric-only judge gates were retired at the flexible-intelligence hard cut — judgment runs only through a compiled Evaluation Treatment, and this playbook has none yet), so it ships as the **creator's review checklist** — nothing runs it automatically. The **trust floor** for accepting the foundation today is the\ncreator's `approve_result` review of the produced config and the bring-up result. There is\nintentionally **no deterministic gate**: config validation is a `wildo` CLI concern\n(`config sync` / validate), not a validator in the journey-artifact schemaRef\nvocabulary. Existing command permission and effect boundaries apply independently\nof this reviewer checklist.\n\n## Scaffold-depth boundary\n\nKeep this playbook at foundation depth. Explicitly **out of scope here**:\n\n- **Implementing replacement CLI tooling.** Use the existing init, asset delivery,\n setup and local initialization owners. If a command fails, retain its diagnostic\n evidence and resolve the prerequisite or concrete defect rather than inventing\n another materializer inside the application.\n- **Resource / field / schema authoring.** The config declares modules as shells and\n enables capabilities. The foundation executor can materialize resource shells\n and scope them to the chosen tenancy. Filling those shells with business-specific\n fields, rules, UI behavior, views and navigation belongs to the later build work.\n- **Re-introducing a foundation artifact.** The `foundation-manifest` family was\n retired on 2026-08-25 with the app-creation verification/digest aspect. Do **NOT**\n reshape `_core` to bring it back: the config file and its git history already carry\n every decision it recorded.\n- **Deep capability / provider modelling.** A defended capability-selection model\n (per-compliance-regime obligation → capability mapping, provider cost/feature\n matrices, multi-provider fallback) is a later depth pass. You derive capabilities\n from the definition set with the v1 heuristic above — not a solved obligation graph.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at scaffold\ndepth — deeper capability modelling belongs to a dedicated later pass,\nholistically.\n\n## What you emit\n\n- The authored **`./wildo.saas.config.ts`** (an app file) — the enabled engine\n capabilities, the registered modules, and the selected providers — plus the\n registered module shells across the runtimes and the\n brought-up skeleton.\n- The **bring-up result** reported to the creator: the status of each step, taken from\n its real exit/postcondition rather than from intent. This is a report, not a stored\n artifact — nothing reads it back.\n\nThe creator reviews the result (approval posture `approve_result`) before it is\naccepted as the journey's foundation, which the bottom-up build loop then fills in\nwith authored resources, operations, UX, and integrations.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state and scope,\n and confirm the approved domain plan + vision brief are in place to configure from.\n- `.claude/skills/config-saas/SKILL.md` — the `./wildo.saas.config.ts` authoring\n surface: `engineCapabilities`, `modules`, provider scopes, and `providerConfigurations`.\n- `.claude/skills/module-registration/SKILL.md` — register each domain-plan module\n across the shared / frontend / backend registries so the skeleton boots with it\n (distinct from `config-saas`, which only declares module existence at the root).\n- `.claude/skills/infra-environment-config/SKILL.md` — the typed `./infrastructure/`\n environment configs (backing services, public domain, service auth) the bring-up needs.\n- `.claude/skills/local-environment-bootstrap/SKILL.md` — the `wildo` lifecycle\n (`setup`, `local init`, `local reinit`, `local dev`) for deterministic initialization,\n repair, clean-room recovery, and runtime start.\n\n## Reviewer checklist — `foundation-configured-coherently`\n\nFormerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is maintained here as guidance against the current tooling:\n\nJudge whether the authored foundation (the ./wildo.saas.config.ts composition + the materialized skeleton) is a coherent realisation of the approved domain plan and the top-down definition set. Assess five invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) CAPABILITY DERIVATION — every enabled engine capability traces to a compliance/vision, business-model, market, or domain-plan need; unjustified capabilities are a CONCERN and missing required capabilities are a GAP. (2) MODULE REGISTRATION — every approved domain-plan module is declared and registered across runtimes; missing modules are a GAP and extra modules are a CONCERN. (3) PROVIDER COVERAGE — every provider serves a declared capability and every provider-backed capability has a provider. (4) SEQUENCE ORDER AND PROOF — materialize a fresh skeleton in an empty destination (or preserve an existing project) → refine config and module registrations → verify knowledge delivery → wildo setup --non-interactive → wildo local init. Treat setup intent, container health, or an initialization marker as insufficient: local init must reach its signed managed-config-read postcondition. (5) BOUNDARY DISCIPLINE — stay at foundation depth: deterministic resource shells are allowed, but business-specific fields, processing, UI behavior, views and navigation belong to later build work. Use the existing init/assets owners; do not replace them. Headless setup and local init run once their prerequisites are satisfied. This reviewer checklist is declarative; creator approval is the trust floor.\n",
50
50
  "skillRefs": [
51
51
  "journey-status",
52
52
  "config-saas",
53
53
  "module-registration",
54
54
  "infra-environment-config",
55
- "local-environment-bootstrap"
55
+ "local-environment-bootstrap",
56
+ "application-database-migrations"
56
57
  ],
58
+ "skillBodyRefs": [],
57
59
  "elicitation": {
58
60
  "questions": [
59
61
  {
@@ -64,12 +66,43 @@
64
66
  "organizations",
65
67
  "users"
66
68
  ]
69
+ },
70
+ {
71
+ "ref": "operating-entity",
72
+ "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.",
73
+ "kind": "free_text"
74
+ },
75
+ {
76
+ "ref": "operating-jurisdictions",
77
+ "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\".",
78
+ "kind": "free_text"
79
+ },
80
+ {
81
+ "ref": "billing-provider",
82
+ "question": "Which billing provider should this application charge its users through? Answer `none` to decide later; the capability stays off until a provider is chosen.",
83
+ "kind": "choice",
84
+ "options": [
85
+ "stripe",
86
+ "none"
87
+ ]
88
+ },
89
+ {
90
+ "ref": "sms-provider",
91
+ "question": "Which SMS provider should this application send text messages through (phone verification, SMS second factor)? Answer `none` if the product sends no SMS, or to decide later.",
92
+ "kind": "choice",
93
+ "options": [
94
+ "twilio",
95
+ "none"
96
+ ]
67
97
  }
68
98
  ]
69
- }
99
+ },
100
+ "contextSources": [],
101
+ "draftableDocumentDefinitionRefs": [],
102
+ "suspendsForClarification": false,
103
+ "briefAdequacyGate": false,
104
+ "briefAdequacyExcludedSources": []
70
105
  },
71
- "executor": "composite",
72
- "qualityGates": [],
73
106
  "approval": "approve_result",
74
107
  "budget": {
75
108
  "maxRuns": 3
@@ -0,0 +1,138 @@
1
+ # Integration Plan — What Runs Beside the Backend
2
+
3
+ ### Target Application Framing
4
+
5
+ This knowledge is for configuring behavior in the target application.
6
+ Wildo is the framework surface being used, not the product being built.
7
+
8
+ Read and apply these patterns from the application-developer point of view:
9
+
10
+ - how the application should configure the relevant app-level file
11
+ - how the application should use framework-provided factories, enums, and helpers
12
+ - how the application should avoid mixing frontend, backend, and infrastructure concerns
13
+
14
+
15
+ ## Where you are in the journey
16
+
17
+ The domain plan is approved and the requirements are written. You decide **what this application
18
+ runs that is not a request** — its workers and its cron minions — and **what it reaches out to** —
19
+ the providers it binds, and where.
20
+
21
+ You do not write any of it. The foundation composes each package, and
22
+ `bottom_up.build-decompose` turns each entry here into a build task bound to the skill that authors
23
+ it.
24
+
25
+ ## Most applications declare nothing here, and that is an answer
26
+
27
+ There is no minimum. An application with no worker, no minion and no extra provider binding is the
28
+ ordinary case, and a plan that says so — with a rationale saying why — is complete. Inventing a
29
+ worker to fill a collection composes a package nobody maintains.
30
+
31
+ ## Step 1 — Worker or minion? One question settles it
32
+
33
+ This is the distinction the whole plan turns on, and planning one as the other produces either a
34
+ package that never runs or one that runs with nothing to contain it.
35
+
36
+ | | **worker** | **minion** |
37
+ |---|---|---|
38
+ | what starts it | the backend calls it | the clock |
39
+ | how it is reached | HTTP routes it registers | nothing reaches it |
40
+ | its authority | the caller's | a containment whitelist of its own |
41
+ | plan it when | work cannot finish inside a request | something must happen because time passed |
42
+
43
+ A nightly sweep is a minion. A slow import the user triggers is a worker. A nightly sweep that the
44
+ backend also triggers on demand is **both**, and they are two entries.
45
+
46
+ ## The refs carry a prefix, and the schema refuses one that does not
47
+
48
+ A worker is `worker-<slug>` and a minion is `minion-<slug>`. You supply the SLUG; the runtime stamps
49
+ the prefix. Keep the slug kebab-case and starting with a LETTER: a ref beginning with a digit parses
50
+ here and is then refused when the foundation derives the package's identifiers from it.
51
+
52
+ ## Step 2 — Plan each worker
53
+
54
+ - **`runtime`** — `NODE` unless the work is CPU-bound enough that the choice is the reason the
55
+ worker exists. Rust is a cargo crate: no shared-lib, no pnpm workspace member, a different
56
+ bootstrap. Choose it deliberately or choose Node.
57
+ - **`purpose`** — what the backend delegates, and **why that cannot happen inside a request**. The
58
+ second half is what a reader checks the decision against.
59
+ - **`jobRefs`** — the routes the entry registers, which is what the backend calls. At least one, and
60
+ **not the worker's own name**: `worker-imports` exposing only `imports` says nothing about what is
61
+ delegated, and the plan reports it.
62
+
63
+ ## Step 3 — Plan each minion, and name its containment
64
+
65
+ - **`purpose`** — what happens because time passed.
66
+ - **`behaviorRefs`** — the named behaviours the tick performs.
67
+ - **`readsResourceRefs` / `writesResourceRefs`** — **the containment decision, and this is why a
68
+ minion is planned rather than left to the coding agent.** A minion's `resourceAccess` whitelist
69
+ starts DENY-ALL, each named resource must separately opt in, and an empty whitelist logs a soft
70
+ warning and **keeps running** — so a minion whose access nobody decided looks healthy and touches
71
+ nothing. Name the decided resources its tick reads and the ones it writes.
72
+
73
+ **No schedule here.** The plan says what happens because time passed, never how often: a cadence is
74
+ an operational decision, and the minion's own build task sets it beside the whitelist it must widen
75
+ anyway.
76
+
77
+ ## Step 4 — Bind the providers
78
+
79
+ One entry per provider per **scope** — the runtime owner whose declaration it lands in:
80
+
81
+ | scope | the owner | what the binding is |
82
+ |---|---|---|
83
+ | `BACKEND` | the backend service | a package installed in the backend and scoped to it |
84
+ | `COMPANION` | the dev companion | the same act, in the companion's scope |
85
+ | `FRONTEND_APP` | the application frontend | a browser-bound provider module |
86
+ | `WEBSITE` | the marketing site | the same, on the website's frontend service |
87
+
88
+ The same provider on two scopes is legitimate and common; the same provider twice on ONE scope is
89
+ one declaration written twice, and the plan refuses it.
90
+
91
+ **A minion's or a worker's own providers are not here.** Those are declared on that surface's own
92
+ `providers` block and belong to the task that builds it.
93
+
94
+ ## Step 5 — Make every surface accountable
95
+
96
+ Each worker and minion carries `servesRefs`: the requirement, feature draft, roadmap phase or
97
+ success criterion that asked for it. A background process accountable to nothing is one nobody
98
+ asked for, and the plan reports it.
99
+
100
+ ## Refine, don't re-author
101
+
102
+ Your own prior plan is an input. Keep every worker and minion ref that still has a reason to exist —
103
+ build tasks name them, and a moved ref orphans the task that produced its package.
104
+
105
+ ## What you emit
106
+
107
+ - The **integration plan** at `specifications/src/integration-plan/index.ts` — the workers, the
108
+ minions and the provider bindings this application carries, with the rationale for the shape as a
109
+ whole.
110
+
111
+ ## Verification
112
+
113
+ - Every `readsResourceRefs` / `writesResourceRefs` entry names a resource the domain plan declares.
114
+ - No worker's only `jobRefs` entry repeats its own name.
115
+ - `rg -n "workerRef|minionRef" specifications/src/integration-plan/index.ts | wc -l` — the number of
116
+ packages the foundation will compose.
117
+
118
+ ## References — named by REF, because this step cannot open a file
119
+
120
+ A structured generation has no filesystem, so a path here would be an instruction answered from
121
+ recollection (#1435). Each skill is named by its REF, and two reach this step as BODIES
122
+ (`method.skillBodyRefs`): **`worker-authoring`** and **`minion-authoring`**. That is not a
123
+ convenience — step 1's question is a runtime contract, and step 3's containment chain has three
124
+ parts of which two live outside the minion's own package, so neither is answerable from memory.
125
+
126
+ The rest are the contracts the CODING AGENT opens when it builds each task:
127
+
128
+ - `provider-backend-package` — installing and scoping a provider on a backend-side owner, bound to
129
+ the emitted task by `INTEGRATION_PROVIDER_BINDING_SKILL_REF` for the `BACKEND` and `COMPANION`
130
+ scopes.
131
+ - `provider-frontend-file-picker` — the frontend provider-module mechanism, bound for the
132
+ `FRONTEND_APP` and `WEBSITE` scopes.
133
+ - `provider-operation-calls` — how a bound provider's operations are actually called, which is what
134
+ makes a binding worth having.
135
+ - `resource-external-data` — the other way to reach another system: read-through or pipeline, when
136
+ what you want is DATA rather than a provider call.
137
+ - `configure-billing` — the worked five-surface chain for the provider binding most applications
138
+ need first.
@@ -0,0 +1,70 @@
1
+ {
2
+ "ref": "bottom_up.integration-plan",
3
+ "version": "0.1.0",
4
+ "phase": "bottom_up",
5
+ "intent": "Background execution and external reach — decide WHAT RUNS BESIDE THE BACKEND and WHAT THIS APPLICATION REACHES OUT TO: which workers exist and on which runtime, which cron minions wake on their own and exactly which resources each one may read and write, and which providers are bound into which runtime owner's scope. Reads the requirements and feature drafts (what somebody asked for, including the work that cannot happen inside a request), the domain plan (the resources a minion's containment whitelist names) and the roadmap (what is owed when). Every surface names what it is accountable to, because a process nobody asked for is a process nobody maintains. Produces the plan; the foundation composes each package and the decomposer emits the work, each task bound to the skill its runtime or scope names.",
6
+ "preconditions": [
7
+ {
8
+ "kind": "artifact_exists",
9
+ "selector": {
10
+ "family": "domain-plan"
11
+ }
12
+ }
13
+ ],
14
+ "inputs": [
15
+ {
16
+ "family": "requirements"
17
+ },
18
+ {
19
+ "family": "feature-drafts"
20
+ },
21
+ {
22
+ "family": "domain-plan"
23
+ },
24
+ {
25
+ "family": "roadmap",
26
+ "render": "map"
27
+ },
28
+ {
29
+ "family": "integration-plan"
30
+ }
31
+ ],
32
+ "outputs": [
33
+ {
34
+ "family": "integration-plan",
35
+ "schemaRef": "saas-specifications:IntegrationPlan",
36
+ "description": "What this application runs beside its backend and what it reaches out to: its workers (each with its runtime, what the backend delegates to it, the routes it registers and what it is accountable to), its cron minions (each with what happens because time passed, its named behaviours, and exactly which resources its tick reads and writes), and the providers it binds into each runtime owner's scope. Every collection may be empty, and saying so is an answer."
37
+ }
38
+ ],
39
+ "stepOutputs": [],
40
+ "method": {
41
+ "guidance": "# Integration Plan — What Runs Beside the Backend\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## Where you are in the journey\n\nThe domain plan is approved and the requirements are written. You decide **what this application\nruns that is not a request** — its workers and its cron minions — and **what it reaches out to** —\nthe providers it binds, and where.\n\nYou do not write any of it. The foundation composes each package, and\n`bottom_up.build-decompose` turns each entry here into a build task bound to the skill that authors\nit.\n\n## Most applications declare nothing here, and that is an answer\n\nThere is no minimum. An application with no worker, no minion and no extra provider binding is the\nordinary case, and a plan that says so — with a rationale saying why — is complete. Inventing a\nworker to fill a collection composes a package nobody maintains.\n\n## Step 1 — Worker or minion? One question settles it\n\nThis is the distinction the whole plan turns on, and planning one as the other produces either a\npackage that never runs or one that runs with nothing to contain it.\n\n| | **worker** | **minion** |\n|---|---|---|\n| what starts it | the backend calls it | the clock |\n| how it is reached | HTTP routes it registers | nothing reaches it |\n| its authority | the caller's | a containment whitelist of its own |\n| plan it when | work cannot finish inside a request | something must happen because time passed |\n\nA nightly sweep is a minion. A slow import the user triggers is a worker. A nightly sweep that the\nbackend also triggers on demand is **both**, and they are two entries.\n\n## The refs carry a prefix, and the schema refuses one that does not\n\nA worker is `worker-<slug>` and a minion is `minion-<slug>`. You supply the SLUG; the runtime stamps\nthe prefix. Keep the slug kebab-case and starting with a LETTER: a ref beginning with a digit parses\nhere and is then refused when the foundation derives the package's identifiers from it.\n\n## Step 2 — Plan each worker\n\n- **`runtime`** — `NODE` unless the work is CPU-bound enough that the choice is the reason the\n worker exists. Rust is a cargo crate: no shared-lib, no pnpm workspace member, a different\n bootstrap. Choose it deliberately or choose Node.\n- **`purpose`** — what the backend delegates, and **why that cannot happen inside a request**. The\n second half is what a reader checks the decision against.\n- **`jobRefs`** — the routes the entry registers, which is what the backend calls. At least one, and\n **not the worker's own name**: `worker-imports` exposing only `imports` says nothing about what is\n delegated, and the plan reports it.\n\n## Step 3 — Plan each minion, and name its containment\n\n- **`purpose`** — what happens because time passed.\n- **`behaviorRefs`** — the named behaviours the tick performs.\n- **`readsResourceRefs` / `writesResourceRefs`** — **the containment decision, and this is why a\n minion is planned rather than left to the coding agent.** A minion's `resourceAccess` whitelist\n starts DENY-ALL, each named resource must separately opt in, and an empty whitelist logs a soft\n warning and **keeps running** — so a minion whose access nobody decided looks healthy and touches\n nothing. Name the decided resources its tick reads and the ones it writes.\n\n**No schedule here.** The plan says what happens because time passed, never how often: a cadence is\nan operational decision, and the minion's own build task sets it beside the whitelist it must widen\nanyway.\n\n## Step 4 — Bind the providers\n\nOne entry per provider per **scope** — the runtime owner whose declaration it lands in:\n\n| scope | the owner | what the binding is |\n|---|---|---|\n| `BACKEND` | the backend service | a package installed in the backend and scoped to it |\n| `COMPANION` | the dev companion | the same act, in the companion's scope |\n| `FRONTEND_APP` | the application frontend | a browser-bound provider module |\n| `WEBSITE` | the marketing site | the same, on the website's frontend service |\n\nThe same provider on two scopes is legitimate and common; the same provider twice on ONE scope is\none declaration written twice, and the plan refuses it.\n\n**A minion's or a worker's own providers are not here.** Those are declared on that surface's own\n`providers` block and belong to the task that builds it.\n\n## Step 5 — Make every surface accountable\n\nEach worker and minion carries `servesRefs`: the requirement, feature draft, roadmap phase or\nsuccess criterion that asked for it. A background process accountable to nothing is one nobody\nasked for, and the plan reports it.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every worker and minion ref that still has a reason to exist —\nbuild tasks name them, and a moved ref orphans the task that produced its package.\n\n## What you emit\n\n- The **integration plan** at `specifications/src/integration-plan/index.ts` — the workers, the\n minions and the provider bindings this application carries, with the rationale for the shape as a\n whole.\n\n## Verification\n\n- Every `readsResourceRefs` / `writesResourceRefs` entry names a resource the domain plan declares.\n- No worker's only `jobRefs` entry repeats its own name.\n- `rg -n \"workerRef|minionRef\" specifications/src/integration-plan/index.ts | wc -l` — the number of\n packages the foundation will compose.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem, so a path here would be an instruction answered from\nrecollection (#1435). Each skill is named by its REF, and two reach this step as BODIES\n(`method.skillBodyRefs`): **`worker-authoring`** and **`minion-authoring`**. That is not a\nconvenience — step 1's question is a runtime contract, and step 3's containment chain has three\nparts of which two live outside the minion's own package, so neither is answerable from memory.\n\nThe rest are the contracts the CODING AGENT opens when it builds each task:\n\n- `provider-backend-package` — installing and scoping a provider on a backend-side owner, bound to\n the emitted task by `INTEGRATION_PROVIDER_BINDING_SKILL_REF` for the `BACKEND` and `COMPANION`\n scopes.\n- `provider-frontend-file-picker` — the frontend provider-module mechanism, bound for the\n `FRONTEND_APP` and `WEBSITE` scopes.\n- `provider-operation-calls` — how a bound provider's operations are actually called, which is what\n makes a binding worth having.\n- `resource-external-data` — the other way to reach another system: read-through or pipeline, when\n what you want is DATA rather than a provider call.\n- `configure-billing` — the worked five-surface chain for the provider binding most applications\n need first.\n",
42
+ "skillRefs": [
43
+ "journey-status",
44
+ "worker-authoring",
45
+ "minion-authoring",
46
+ "provider-backend-package",
47
+ "provider-frontend-file-picker",
48
+ "provider-operation-calls",
49
+ "resource-external-data",
50
+ "configure-billing"
51
+ ],
52
+ "skillBodyRefs": [
53
+ "worker-authoring",
54
+ "minion-authoring"
55
+ ],
56
+ "contextSources": [
57
+ "workspace_truth"
58
+ ],
59
+ "draftableDocumentDefinitionRefs": [],
60
+ "suspendsForClarification": false,
61
+ "briefAdequacyGate": false,
62
+ "briefAdequacyExcludedSources": []
63
+ },
64
+ "executor": "companion_agent",
65
+ "approval": "approve_result",
66
+ "budget": {
67
+ "maxRuns": 3
68
+ },
69
+ "onFailure": "keep_and_flag"
70
+ }
@@ -0,0 +1,87 @@
1
+ # Maturity Reading — Where This Application Stands
2
+
3
+ ### Target Application Framing
4
+
5
+ This knowledge is for configuring behavior in the target application.
6
+ Wildo is the framework surface being used, not the product being built.
7
+
8
+ Read and apply these patterns from the application-developer point of view:
9
+
10
+ - how the application should configure the relevant app-level file
11
+ - how the application should use framework-provided factories, enums, and helpers
12
+ - how the application should avoid mixing frontend, backend, and infrastructure concerns
13
+
14
+
15
+ ## What this step does
16
+
17
+ The build lane ends on four typechecks and a migration-drift probe, and its own method says it "does
18
+ not boot the application, run its test suite". Nothing related what was BUILT to what the
19
+ application's requirements ASKED FOR.
20
+
21
+ This step records that relation as the `application-maturity` family: **one row per requirement the
22
+ application declares**, the evidence that exists for it, and the stage that follows.
23
+
24
+ ## There is no "done", and that is the design
25
+
26
+ The highest stage does not mean finished. It means that today, every requirement has the strongest
27
+ evidence this framework can produce for it — and the next requirement somebody writes lowers the
28
+ reading again, with no code change anywhere. That is what the measurement is FOR.
29
+
30
+ So nothing in the lane may gate on this family, and no other step may read a stage as permission.
31
+
32
+ ## It is derived, never judged
33
+
34
+ Nothing here is an opinion, and no model produces it. Each row's level is reached by a measurement:
35
+
36
+ | level | reached when | measured from |
37
+ |---|---|---|
38
+ | `UNADDRESSED` | nothing the application decided points at the requirement | the decided-element graph |
39
+ | `DECIDED` | a decided element links to it — a feature draft, an experience surface, a worker, a build task | inbound links on the same graph |
40
+ | `BUILT` | a build task addressing it has LANDED | the landing probe, over committed bytes |
41
+ | `VERIFIED` | that landed task's declared product was PROVEN | the same probe, minus what it could not verify |
42
+ | `OBSERVED` | something watched the running application do it | runtime observations |
43
+
44
+ The ladder is ordered, and the stage is the highest one whose threshold the population meets. The
45
+ default threshold is **every requirement at that level** — one number, and not a guess: a share
46
+ below 1 would be an invented tolerance, and this family measures rather than flatters.
47
+
48
+ ## The denominator is the requirements family, and nothing else
49
+
50
+ Every row comes from `requirements`, functional and non-functional, in its own order. Not the
51
+ requirements that happen to be referenced somewhere, not a count of build tasks, not a share of
52
+ files. A requirement nothing addresses is a ROW at `UNADDRESSED` — visible, counted, and lowering
53
+ the reading.
54
+
55
+ That is the difference between a measurement and a file count: a denominator you choose yourself is
56
+ not a measurement at all.
57
+
58
+ ## A family that addresses requirements joins on its own
59
+
60
+ "Which elements address this requirement" is read from the decided-element graph's inbound links, so
61
+ every family that declares an edge to `requirements.functional` or `requirements.non-functional`
62
+ already contributes — and one that declares such an edge tomorrow contributes without this method,
63
+ or the derivation, knowing it exists.
64
+
65
+ ## What the reading says that a number cannot
66
+
67
+ Three findings, and each names the application rather than the artifact:
68
+
69
+ - a requirement **nothing addresses** — the reading's whole point;
70
+ - a requirement whose build work **landed and could not be proven**, so its evidence stops at
71
+ `BUILT`. A task that declares no product cannot be probed, and that is a known, deliberate state
72
+ rather than a failure;
73
+ - **no runtime observation exists at all**, which today is true of every application. The finding
74
+ names what would fill it — an engine-behaviour e2e scenario that names the requirement it
75
+ exercises — rather than leaving the top of the ladder quietly empty.
76
+
77
+ ## What you emit
78
+
79
+ - The **maturity reading** at `specifications/src/application-maturity/index.ts`. It is landed by
80
+ the runner, not written by hand.
81
+
82
+ ## Verification
83
+
84
+ - The row count equals the number of requirements the application declares.
85
+ - Every `requirementRef` names a requirement in the `requirements` family.
86
+ - `rg -c "UNADDRESSED" specifications/src/application-maturity/index.ts` — how many requirements
87
+ nothing has picked up yet.
@@ -0,0 +1,69 @@
1
+ {
2
+ "ref": "bottom_up.maturity-reading",
3
+ "version": "0.1.0",
4
+ "phase": "bottom_up",
5
+ "intent": "Maturity reading — measure WHERE THIS APPLICATION STANDS against its own requirements, and record it as the `application-maturity` family: one row per requirement the application declares, the evidence that exists for it, and the stage that follows. DERIVED, never judged. Each row's level is reached by a measurement — a decided element that points at the requirement (a feature draft, an experience surface, a worker, a build task), a build task addressing it that has LANDED in committed bytes, a landed task whose declared product was PROVEN, or a runtime observation of the running application. The denominator is the requirements family itself, total and in its own order, so a requirement nothing addresses is a row rather than an omission and adding one lowers the reading with no code change. This is a MEASUREMENT and never a gate: there is no 'done' for an application, and the stage moves in both directions as the application and its requirements change.",
6
+ "preconditions": [
7
+ {
8
+ "kind": "artifact_exists",
9
+ "selector": {
10
+ "family": "requirements"
11
+ }
12
+ }
13
+ ],
14
+ "inputs": [
15
+ {
16
+ "family": "requirements",
17
+ "render": "map"
18
+ },
19
+ {
20
+ "family": "feature-drafts",
21
+ "render": "map"
22
+ },
23
+ {
24
+ "family": "build-plan",
25
+ "render": "map"
26
+ },
27
+ {
28
+ "family": "experience-plan",
29
+ "render": "map"
30
+ },
31
+ {
32
+ "family": "integration-plan",
33
+ "render": "map"
34
+ },
35
+ {
36
+ "family": "roadmap",
37
+ "render": "map"
38
+ },
39
+ {
40
+ "family": "application-maturity",
41
+ "render": "map"
42
+ }
43
+ ],
44
+ "outputs": [
45
+ {
46
+ "family": "application-maturity",
47
+ "schemaRef": "saas-specifications:ApplicationMaturity",
48
+ "description": "Where the application stands against its own requirements: one row per requirement with the evidence level it has reached and the elements, landed tasks, proven tasks and runtime observations that carry it, the thresholds the reading was scored against, and the stage that follows. A reading, never a verdict."
49
+ }
50
+ ],
51
+ "stepOutputs": [],
52
+ "method": {
53
+ "guidance": "# Maturity Reading — Where This Application Stands\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What this step does\n\nThe build lane ends on four typechecks and a migration-drift probe, and its own method says it \"does\nnot boot the application, run its test suite\". Nothing related what was BUILT to what the\napplication's requirements ASKED FOR.\n\nThis step records that relation as the `application-maturity` family: **one row per requirement the\napplication declares**, the evidence that exists for it, and the stage that follows.\n\n## There is no \"done\", and that is the design\n\nThe highest stage does not mean finished. It means that today, every requirement has the strongest\nevidence this framework can produce for it — and the next requirement somebody writes lowers the\nreading again, with no code change anywhere. That is what the measurement is FOR.\n\nSo nothing in the lane may gate on this family, and no other step may read a stage as permission.\n\n## It is derived, never judged\n\nNothing here is an opinion, and no model produces it. Each row's level is reached by a measurement:\n\n| level | reached when | measured from |\n|---|---|---|\n| `UNADDRESSED` | nothing the application decided points at the requirement | the decided-element graph |\n| `DECIDED` | a decided element links to it — a feature draft, an experience surface, a worker, a build task | inbound links on the same graph |\n| `BUILT` | a build task addressing it has LANDED | the landing probe, over committed bytes |\n| `VERIFIED` | that landed task's declared product was PROVEN | the same probe, minus what it could not verify |\n| `OBSERVED` | something watched the running application do it | runtime observations |\n\nThe ladder is ordered, and the stage is the highest one whose threshold the population meets. The\ndefault threshold is **every requirement at that level** — one number, and not a guess: a share\nbelow 1 would be an invented tolerance, and this family measures rather than flatters.\n\n## The denominator is the requirements family, and nothing else\n\nEvery row comes from `requirements`, functional and non-functional, in its own order. Not the\nrequirements that happen to be referenced somewhere, not a count of build tasks, not a share of\nfiles. A requirement nothing addresses is a ROW at `UNADDRESSED` — visible, counted, and lowering\nthe reading.\n\nThat is the difference between a measurement and a file count: a denominator you choose yourself is\nnot a measurement at all.\n\n## A family that addresses requirements joins on its own\n\n\"Which elements address this requirement\" is read from the decided-element graph's inbound links, so\nevery family that declares an edge to `requirements.functional` or `requirements.non-functional`\nalready contributes — and one that declares such an edge tomorrow contributes without this method,\nor the derivation, knowing it exists.\n\n## What the reading says that a number cannot\n\nThree findings, and each names the application rather than the artifact:\n\n- a requirement **nothing addresses** — the reading's whole point;\n- a requirement whose build work **landed and could not be proven**, so its evidence stops at\n `BUILT`. A task that declares no product cannot be probed, and that is a known, deliberate state\n rather than a failure;\n- **no runtime observation exists at all**, which today is true of every application. The finding\n names what would fill it — an engine-behaviour e2e scenario that names the requirement it\n exercises — rather than leaving the top of the ladder quietly empty.\n\n## What you emit\n\n- The **maturity reading** at `specifications/src/application-maturity/index.ts`. It is landed by\n the runner, not written by hand.\n\n## Verification\n\n- The row count equals the number of requirements the application declares.\n- Every `requirementRef` names a requirement in the `requirements` family.\n- `rg -c \"UNADDRESSED\" specifications/src/application-maturity/index.ts` — how many requirements\n nothing has picked up yet.\n",
54
+ "skillRefs": [
55
+ "journey-status"
56
+ ],
57
+ "skillBodyRefs": [],
58
+ "contextSources": [],
59
+ "draftableDocumentDefinitionRefs": [],
60
+ "suspendsForClarification": false,
61
+ "briefAdequacyGate": false,
62
+ "briefAdequacyExcludedSources": []
63
+ },
64
+ "approval": "approve_result",
65
+ "budget": {
66
+ "maxRuns": 5
67
+ },
68
+ "onFailure": "keep_and_flag"
69
+ }