@wildo-ai/framework-knowledge 1.1.3 → 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 (841) 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 +349 -17
  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/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
  10. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
  11. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  12. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +125 -0
  13. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -0
  14. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +177 -0
  15. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -0
  16. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +213 -7
  17. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  18. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +326 -8
  19. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  20. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +5 -3
  21. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +21 -14
  23. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +57 -0
  25. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -0
  26. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +63 -0
  27. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -0
  28. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +132 -0
  29. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -0
  30. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +179 -0
  31. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -0
  32. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +67 -0
  33. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -0
  34. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +76 -0
  35. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -0
  36. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +5 -4
  37. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +10 -5
  39. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +67 -0
  41. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -0
  42. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +82 -0
  43. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -0
  44. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +25 -9
  45. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +124 -7
  47. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +67 -0
  49. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -0
  50. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +83 -0
  51. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -0
  52. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +69 -0
  53. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -0
  54. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +71 -0
  55. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -0
  56. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -1
  57. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -1
  58. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  59. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +71 -0
  60. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -0
  61. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +88 -0
  62. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -0
  63. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +97 -0
  64. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -0
  65. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +156 -0
  66. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -0
  67. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +115 -0
  68. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -0
  69. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +152 -0
  70. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -0
  71. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +188 -8
  72. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  73. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +167 -9
  74. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  75. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +171 -1
  76. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  77. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +146 -1
  78. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  79. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts +248 -0
  80. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -0
  81. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js +248 -0
  82. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -0
  83. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +157 -4
  84. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  85. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +172 -4
  86. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  87. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +5 -4
  88. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  89. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +8 -7
  90. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  91. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +3 -2
  92. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  93. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +22 -3
  94. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  95. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +5 -3
  96. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  97. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +21 -12
  98. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  99. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +192 -27
  100. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  101. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +172 -33
  102. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  103. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +2 -1
  104. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  105. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +6 -2
  106. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  107. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +182 -5
  108. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  109. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +191 -5
  110. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  111. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +2 -1
  112. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  113. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +3 -2
  114. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  115. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +154 -0
  116. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -0
  117. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +214 -0
  118. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -0
  119. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +44 -0
  120. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -0
  121. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +51 -0
  122. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -0
  123. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -1
  124. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  125. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +2 -1
  126. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  127. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +2 -1
  128. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  129. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +6 -2
  130. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  131. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +2 -1
  132. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  133. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +2 -1
  134. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  135. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -2
  136. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  137. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +7 -3
  138. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  139. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +32 -4
  140. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  141. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +27 -3
  142. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  143. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -2
  144. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  145. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +4 -2
  146. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  147. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +199 -0
  148. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -0
  149. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +227 -0
  150. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -0
  151. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +5 -3
  152. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  153. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +18 -4
  154. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  155. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +155 -4
  156. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  157. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +187 -4
  158. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  159. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +6 -5
  160. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  161. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +18 -17
  162. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  163. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  164. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
  165. package/dist/knowledge/manifest.json +9 -8
  166. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +75 -0
  167. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
  168. package/dist/knowledge/playbooks/bottom_up.build/method.md +79 -0
  169. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +65 -0
  170. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -0
  171. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -0
  172. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +1122 -76
  173. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +49 -13
  174. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-protocol.json +1 -1
  175. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-treatment.json +1 -1
  176. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +671 -47
  177. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +10 -16
  178. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +31 -35
  179. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -16
  180. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +95 -0
  181. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +62 -0
  182. package/dist/knowledge/playbooks/bottom_up.conception/method.md +80 -0
  183. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +90 -0
  184. package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +107 -0
  185. package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +70 -0
  186. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +8 -8
  187. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +14 -13
  188. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +165 -0
  189. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +74 -0
  190. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +219 -140
  191. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +55 -22
  192. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +138 -0
  193. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +70 -0
  194. package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +87 -0
  195. package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +69 -0
  196. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +236 -0
  197. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +63 -0
  198. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +116 -0
  199. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +79 -0
  200. package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +71 -0
  201. package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +70 -0
  202. package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +83 -0
  203. package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +68 -0
  204. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -0
  205. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -0
  206. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +873 -15
  207. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +19 -12
  208. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-protocol.json +1 -0
  209. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-treatment.json +1 -0
  210. package/dist/knowledge/playbooks/refinement.document-facts/method.md +186 -21
  211. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +12 -16
  212. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-protocol.json +1 -0
  213. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-treatment.json +1 -0
  214. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +343 -0
  215. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +54 -0
  216. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -0
  217. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -0
  218. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +28 -11
  219. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -17
  220. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +8 -15
  221. package/dist/knowledge/playbooks/top_down.capability-map/method.md +25 -49
  222. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +14 -17
  223. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
  224. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +101 -0
  225. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-protocol.json +1 -0
  226. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-treatment.json +1 -0
  227. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +209 -0
  228. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +68 -0
  229. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
  230. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +42 -0
  231. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -0
  232. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -0
  233. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +39 -12
  234. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +18 -66
  235. package/dist/knowledge/playbooks/top_down.compliance-research/method.md +78 -0
  236. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +43 -0
  237. package/dist/knowledge/playbooks/top_down.definition/method.md +103 -0
  238. package/dist/knowledge/playbooks/top_down.definition/playbook.json +75 -0
  239. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +56 -0
  240. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +48 -0
  241. package/dist/knowledge/playbooks/top_down.market-analysis/method.md +51 -165
  242. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +25 -44
  243. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
  244. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +43 -0
  245. package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
  246. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +45 -0
  247. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-protocol.json +1 -1
  248. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-treatment.json +1 -1
  249. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +247 -0
  250. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +71 -0
  251. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  252. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  253. package/dist/knowledge/playbooks/top_down.phase-gate/method.md +36 -69
  254. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +12 -9
  255. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +11 -7
  256. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +12 -16
  257. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-protocol.json +1 -0
  258. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-treatment.json +1 -0
  259. package/dist/knowledge/playbooks/top_down.risk-register/method.md +46 -0
  260. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +59 -0
  261. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +12 -5
  262. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +15 -17
  263. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-protocol.json +1 -0
  264. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-treatment.json +1 -0
  265. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +23 -14
  266. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +12 -17
  267. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
  268. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +13 -17
  269. package/dist/knowledge/references/acp.execution-profile.md +266 -0
  270. package/dist/knowledge/references/acp.host-configuration-inheritance.md +29 -0
  271. package/dist/knowledge/references/acp.permission-ceiling.md +105 -0
  272. package/dist/knowledge/references/acp.permission-escalation.md +37 -0
  273. package/dist/knowledge/references/application-documentation-chapters.config.md +152 -0
  274. package/dist/knowledge/references/application-documentation-plan.config.md +136 -0
  275. package/dist/knowledge/references/application-maturity.config.md +319 -0
  276. package/dist/knowledge/references/assertions.authored-metadata.config.md +1 -1
  277. package/dist/knowledge/references/assertions.specification.config.md +1 -1
  278. package/dist/knowledge/references/brand.asset.config.md +8 -16
  279. package/dist/knowledge/references/brand.authored-metadata.config.md +2 -2
  280. package/dist/knowledge/references/brand.logo-direction.config.md +9 -7
  281. package/dist/knowledge/references/brand.snapshot.config.md +16 -2
  282. package/dist/knowledge/references/brand.snapshot.validation.md +0 -7
  283. package/dist/knowledge/references/build-plan.task-graph.config.md +581 -7
  284. package/dist/knowledge/references/business-model.authored-metadata.config.md +2 -2
  285. package/dist/knowledge/references/business-model.pricing-plan.config.md +1 -1
  286. package/dist/knowledge/references/business-model.snapshot.validation.md +15 -0
  287. package/dist/knowledge/references/capability-composition.config.md +155 -0
  288. package/dist/knowledge/references/cli.market.utils.md +1 -0
  289. package/dist/knowledge/references/companion.technical-doc.service.md +453 -98
  290. package/dist/knowledge/references/engine.client-bundle.allow-list.md +21 -0
  291. package/dist/knowledge/references/engine.client-bundle.external-connectors-public.discipline.md +20 -1
  292. package/dist/knowledge/references/engine.saas-technical-doc.config.md +8 -4
  293. package/dist/knowledge/references/engine.saas-website.config.md +22 -10
  294. package/dist/knowledge/references/example.backend.addon-wiring.module.md +8 -12
  295. package/dist/knowledge/references/example.config.app-shell.full.md +42 -7
  296. package/dist/knowledge/references/example.config.backend.required-floors.md +4 -0
  297. package/dist/knowledge/references/example.config.design-system.full.md +3 -0
  298. package/dist/knowledge/references/example.engine.product-definitions.feature-and-profiles.md +19 -7
  299. package/dist/knowledge/references/example.features.connected-feature.declaration.md +66 -0
  300. package/dist/knowledge/references/example.features.connected-feature.surface.md +42 -0
  301. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +4 -3
  302. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +6 -10
  303. package/dist/knowledge/references/example.guidance.bound-survey-flow.md +82 -0
  304. package/dist/knowledge/references/example.infra.environment-config.local.md +88 -11
  305. package/dist/knowledge/references/example.milestones.module-definitions.md +73 -0
  306. package/dist/knowledge/references/example.minion.contained-tick.md +79 -0
  307. package/dist/knowledge/references/example.module.companion-exports.full.md +38 -3
  308. package/dist/knowledge/references/example.provider.backend-module-shape.md +31 -13
  309. package/dist/knowledge/references/example.provider.frontend-app.module.md +103 -0
  310. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +20 -0
  311. package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +7 -3
  312. package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +30 -0
  313. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +11 -0
  314. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +3 -0
  315. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +94 -10
  316. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +79 -0
  317. package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +18 -0
  318. package/dist/knowledge/references/example.worker.node-route.md +94 -0
  319. package/dist/knowledge/references/experience-plan.config.md +311 -0
  320. package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +132 -9
  321. package/dist/knowledge/references/external-connectors.backend.provider-package-convention.md +36 -0
  322. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +269 -0
  323. package/dist/knowledge/references/integration-plan.config.md +185 -0
  324. package/dist/knowledge/references/market.alternative.config.md +1 -1
  325. package/dist/knowledge/references/market.authored-metadata.config.md +12 -9
  326. package/dist/knowledge/references/market.channel.config.md +3 -3
  327. package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
  328. package/dist/knowledge/references/market.gain.config.md +1 -1
  329. package/dist/knowledge/references/market.icp.config.md +2 -2
  330. package/dist/knowledge/references/market.job.config.md +1 -1
  331. package/dist/knowledge/references/market.message-template.config.md +2 -2
  332. package/dist/knowledge/references/market.objection.config.md +1 -1
  333. package/dist/knowledge/references/market.pain.config.md +1 -1
  334. package/dist/knowledge/references/market.persona.config.md +2 -2
  335. package/dist/knowledge/references/market.proof.config.md +1 -1
  336. package/dist/knowledge/references/market.snapshot.validation.md +15 -0
  337. package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
  338. package/dist/knowledge/references/market.trigger.config.md +1 -1
  339. package/dist/knowledge/references/minions.tick-contract.md +83 -0
  340. package/dist/knowledge/references/placement-plan.config.md +369 -0
  341. package/dist/knowledge/references/platform.config.application-database.md +5 -2
  342. package/dist/knowledge/references/platform.config.backing-services.md +0 -21
  343. package/dist/knowledge/references/platform.config.environment.deployment.md +206 -14
  344. package/dist/knowledge/references/platform.config.infra-provider-resolution.md +170 -0
  345. package/dist/knowledge/references/platform.config.infrastructure-host.md +87 -0
  346. package/dist/knowledge/references/platform.config.saas.md +261 -9
  347. package/dist/knowledge/references/presets.models.labelling.sections.md +14 -0
  348. package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
  349. package/dist/knowledge/references/requirements.authored-metadata.config.md +2 -2
  350. package/dist/knowledge/references/requirements.snapshot.validation.md +15 -0
  351. package/dist/knowledge/references/roadmap.authored-metadata.config.md +2 -2
  352. package/dist/knowledge/references/roadmap.snapshot.validation.md +15 -7
  353. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +71 -0
  354. package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +1 -2
  355. package/dist/knowledge/references/saas.backend.auth.federated-identity-provider-private-networks.md +62 -0
  356. package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +86 -0
  357. package/dist/knowledge/references/saas.backend.billing.catalog-sync-result.md +37 -0
  358. package/dist/knowledge/references/saas.backend.billing.resolution-failure-reasons.md +24 -5
  359. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +187 -0
  360. package/dist/knowledge/references/saas.backend.domain-module.md +25 -1
  361. package/dist/knowledge/references/saas.backend.error-builder.user-guidance.md +82 -0
  362. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +6 -0
  363. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +22 -4
  364. package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +17 -4
  365. package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +84 -0
  366. package/dist/knowledge/references/saas.backend.health-readiness-contributor.md +73 -0
  367. package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +200 -0
  368. package/dist/knowledge/references/saas.backend.providers.operation-executor.md +51 -0
  369. package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +71 -0
  370. package/dist/knowledge/references/saas.backend.queue.worker-topology.md +39 -0
  371. package/dist/knowledge/references/saas.backend.system-access-service.md +51 -42
  372. package/dist/knowledge/references/saas.composition.scenario-apply.md +51 -0
  373. package/dist/knowledge/references/saas.config.content-security-policy.md +97 -0
  374. package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +91 -21
  375. package/dist/knowledge/references/saas.data-seeding.definition-input.md +4 -0
  376. package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +38 -0
  377. package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +27 -27
  378. package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +65 -16
  379. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +41 -11
  380. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +44 -8
  381. package/dist/knowledge/references/saas.frontend.billing-context.md +108 -0
  382. package/dist/knowledge/references/saas.frontend.brand-identity.md +38 -0
  383. package/dist/knowledge/references/saas.frontend.celebration-overlay-contract.md +41 -0
  384. package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +64 -0
  385. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
  386. package/dist/knowledge/references/saas.frontend.errors.user-facing-error-message.md +47 -0
  387. package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.per-action-retry-loop.md +7 -1
  388. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +3 -3
  389. package/dist/knowledge/references/saas.frontend.flows-actors-view.md +7 -4
  390. package/dist/knowledge/references/saas.frontend.form-fields.file-provider-constraints.md +30 -48
  391. package/dist/knowledge/references/saas.frontend.full-custom-view.definition.md +24 -0
  392. package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
  393. package/dist/knowledge/references/saas.frontend.onboarding-view.md +84 -0
  394. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +65 -0
  395. package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
  396. package/dist/knowledge/references/saas.frontend.resource-header-title.md +28 -4
  397. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +127 -1
  398. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +327 -11
  399. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +198 -0
  400. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +220 -0
  401. package/dist/knowledge/references/saas.market.generation-agent.md +26 -9
  402. package/dist/knowledge/references/saas.models.analytics.value-moments.md +132 -0
  403. package/dist/knowledge/references/saas.models.audit.trail-config.md +155 -0
  404. package/dist/knowledge/references/saas.models.auth.methods.md +513 -0
  405. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +82 -0
  406. package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +77 -0
  407. package/dist/knowledge/references/saas.models.config.organization-types.md +192 -0
  408. package/dist/knowledge/references/saas.models.config.registration.md +188 -0
  409. package/dist/knowledge/references/saas.models.config.tenant-teardown.md +81 -0
  410. package/dist/knowledge/references/saas.models.data-mode-read-list.md +173 -3
  411. package/dist/knowledge/references/saas.models.email.template-type.md +40 -0
  412. package/dist/knowledge/references/saas.models.engine-capabilities.md +85 -7
  413. package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +61 -0
  414. package/dist/knowledge/references/saas.models.external-data-pipeline.md +43 -4
  415. package/dist/knowledge/references/saas.models.features.definition-builders.md +162 -0
  416. package/dist/knowledge/references/saas.models.file-upload-grant.md +222 -0
  417. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +54 -5
  418. package/dist/knowledge/references/saas.models.governed-document-acceptance-mode.md +116 -0
  419. package/dist/knowledge/references/saas.models.guidance-flow.md +160 -0
  420. package/dist/knowledge/references/saas.models.http-api-binding.md +76 -110
  421. package/dist/knowledge/references/saas.models.milestone-celebration.md +69 -0
  422. package/dist/knowledge/references/saas.models.milestone-definition.md +209 -0
  423. package/dist/knowledge/references/saas.models.navigation.layout.md +2 -2
  424. package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
  425. package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
  426. package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +150 -0
  427. package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +70 -0
  428. package/dist/knowledge/references/saas.models.notifications.targets.md +138 -0
  429. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +256 -0
  430. package/dist/knowledge/references/saas.models.onboarding-elements.md +375 -0
  431. package/dist/knowledge/references/saas.models.onboarding-trigger.md +52 -0
  432. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +50 -0
  433. package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +129 -0
  434. package/dist/knowledge/references/saas.models.privacy.client-instance-id-scope.md +49 -0
  435. package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +106 -0
  436. package/dist/knowledge/references/saas.models.progression-tracker-variant.md +76 -0
  437. package/dist/knowledge/references/saas.models.provider-capabilities.md +8 -5
  438. package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +72 -0
  439. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +50 -0
  440. package/dist/knowledge/references/saas.models.providers.capability-surface.md +58 -0
  441. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +111 -0
  442. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +156 -0
  443. package/dist/knowledge/references/saas.models.rate-limit-configuration.md +11 -1
  444. package/dist/knowledge/references/saas.models.relationship-handling-settings.md +23 -1
  445. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -4
  446. package/dist/knowledge/references/saas.models.resource-config.forwarded-label.md +5 -4
  447. package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +69 -0
  448. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +15 -2
  449. package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +66 -0
  450. package/dist/knowledge/references/saas.models.resource-config.operation-base.md +24 -1
  451. package/dist/knowledge/references/saas.models.resource-config.operation-cron-job.md +59 -0
  452. package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +55 -0
  453. package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +5 -4
  454. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +158 -0
  455. package/dist/knowledge/references/saas.models.resource-config.operation-step-up.md +77 -0
  456. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
  457. package/dist/knowledge/references/saas.models.resource-config.operation-variant-for-key.md +6 -1
  458. package/dist/knowledge/references/saas.models.resource-config.queue-policy.md +49 -0
  459. package/dist/knowledge/references/saas.models.resource-config.required-features.md +84 -0
  460. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +10 -0
  461. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +14 -0
  462. package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +111 -4
  463. package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +39 -0
  464. package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +48 -0
  465. package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +38 -0
  466. package/dist/knowledge/references/saas.models.resource-primary-scope.md +11 -2
  467. package/dist/knowledge/references/saas.models.scope-membership.md +3 -4
  468. package/dist/knowledge/references/saas.models.shared-saas-module.md +25 -0
  469. package/dist/knowledge/references/saas.models.systems-of-record.md +635 -0
  470. package/dist/knowledge/references/saas.public-runtime.contract.md +198 -1
  471. package/dist/knowledge/references/saas.rag.retrieval-result.md +19 -8
  472. package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
  473. package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +15 -36
  474. package/dist/knowledge/references/saas.specifications.application-document-publication.contract.md +9 -5
  475. package/dist/knowledge/references/saas.specifications.application-document-publication.generation.md +63 -0
  476. package/dist/knowledge/references/saas.specifications.application-document-release-set.contract.md +74 -0
  477. package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +123 -0
  478. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +88 -7
  479. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +774 -53
  480. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +211 -14
  481. package/dist/knowledge/references/saas.specifications.composite-view-specification.md +10 -0
  482. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +364 -0
  483. package/dist/knowledge/references/saas.specifications.playbook-approval-and-failure-policies.md +96 -0
  484. package/dist/knowledge/references/saas.specifications.processor-register.md +333 -0
  485. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +8 -0
  486. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
  487. package/dist/knowledge/references/saas.website.astro.bridge.md +64 -2
  488. package/dist/knowledge/references/saas.website.astro.head-renderer.md +32 -12
  489. package/dist/knowledge/references/saas.website.astro.label-loader.md +3 -0
  490. package/dist/knowledge/references/saas.website.astro.robots-renderer.md +14 -1
  491. package/dist/knowledge/references/saas.website.blog.bridge.md +21 -1
  492. package/dist/knowledge/references/saas.website.consent.banner.md +218 -0
  493. package/dist/knowledge/references/saas.website.consent.context.md +162 -0
  494. package/dist/knowledge/references/saas.website.consent.gate.md +38 -0
  495. package/dist/knowledge/references/saas.website.page-layout.component.md +67 -1
  496. package/dist/knowledge/references/saas.website.page.context.md +4 -3
  497. package/dist/knowledge/references/saas.website.runtime.context.md +43 -7
  498. package/dist/knowledge/references/saas.website.section.context.md +3 -2
  499. package/dist/knowledge/references/saas.website.sections.category-enum.md +19 -20
  500. package/dist/knowledge/references/vision.authored-metadata.config.md +2 -2
  501. package/dist/knowledge/references/website-plan.config.md +205 -0
  502. package/dist/knowledge/references/workers.node.worker-init-contract.md +57 -0
  503. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +43 -2
  504. package/dist/knowledge/references/zod.decorators.data-categories.md +197 -0
  505. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +51 -4
  506. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +54 -1
  507. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +35 -0
  508. package/dist/knowledge/references/zod.decorators.field-spec-params.md +32 -5
  509. package/dist/knowledge/references/zod.decorators.file-nature-constraints.md +86 -0
  510. package/dist/knowledge/references/zod.decorators.file-readiness-metadata.md +67 -0
  511. package/dist/knowledge/references/zod.decorators.file-schema.md +90 -14
  512. package/dist/knowledge/references/zod.decorators.file-vocabularies.md +84 -0
  513. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +140 -4
  514. package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
  515. package/dist/knowledge/references/zod.decorators.rag-source.md +6 -2
  516. package/dist/knowledge/references/zod.decorators.schema-metadata.md +24 -0
  517. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +35 -0
  518. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +46 -12
  519. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +31 -12
  520. package/dist/knowledge/references/zod.factories.address.md +118 -0
  521. package/dist/knowledge/references/zod.factories.code.md +2 -0
  522. package/dist/knowledge/references/zod.factories.duration.md +2 -0
  523. package/dist/knowledge/references/zod.factories.money.md +2 -0
  524. package/dist/knowledge/references/zod.factories.phone.md +14 -1
  525. package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
  526. package/dist/knowledge/registries/framework-topics.json +1215 -11
  527. package/dist/knowledge/registries/playbooks.json +454 -50
  528. package/dist/knowledge/registries/source-tags.json +3153 -1043
  529. package/dist/knowledge/rules/database-migration-obligation.md +110 -0
  530. package/dist/knowledge/rules/live-context-door.md +108 -0
  531. package/dist/knowledge/rules/resource-schema-awareness.md +75 -0
  532. package/dist/knowledge/skills/INDEX.md +46 -11
  533. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +80 -37
  534. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +167 -0
  535. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +6 -3
  536. package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -3
  537. package/dist/knowledge/skills/application-database-migrations/references/framework-application-database-api.md +5 -2
  538. package/dist/knowledge/skills/application-database-migrations/references/migration-refusals.md +32 -0
  539. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +94 -3
  540. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +50 -0
  541. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +26 -19
  542. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +25 -1
  543. package/dist/knowledge/skills/backend-addon-wiring/references/framework-readiness-contributor-api.md +135 -0
  544. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +75 -12
  545. package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +137 -0
  546. package/dist/knowledge/skills/backend-custom-operation/references/framework-error-user-guidance-api.md +112 -0
  547. package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +72 -1
  548. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +207 -0
  549. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +31 -1
  550. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-asset-api.md +8 -16
  551. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +25 -9
  552. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +135 -5
  553. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +80 -17
  554. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +369 -111
  555. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +32 -10
  556. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +103 -58
  557. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-publication-contract.md +19 -13
  558. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +142 -26
  559. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +722 -23
  560. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +348 -0
  561. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +123 -0
  562. package/dist/knowledge/skills/config-app-shell/SKILL.md +74 -11
  563. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +85 -19
  564. package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +70 -0
  565. package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
  566. package/dist/knowledge/skills/config-design-system/SKILL.md +43 -3
  567. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
  568. package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
  569. package/dist/knowledge/skills/config-design-system/references/surface-policy-authoring.md +19 -10
  570. package/dist/knowledge/skills/config-navigation/SKILL.md +85 -2
  571. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
  572. package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +2 -2
  573. package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
  574. package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
  575. package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +172 -0
  576. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +146 -0
  577. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +141 -0
  578. package/dist/knowledge/skills/config-saas/SKILL.md +86 -9
  579. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +199 -0
  580. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +179 -0
  581. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +493 -0
  582. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +153 -0
  583. package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +242 -0
  584. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +161 -0
  585. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +93 -12
  586. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +785 -0
  587. package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +172 -0
  588. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +261 -9
  589. package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +9 -0
  590. package/dist/knowledge/skills/config-saas-backend/SKILL.md +58 -3
  591. package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +151 -0
  592. package/dist/knowledge/skills/config-saas-backend/references/framework-auth-methods-api.md +579 -0
  593. package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +8 -2
  594. package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +96 -0
  595. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +316 -0
  596. package/dist/knowledge/skills/config-saas-backend/references/framework-registration-config-api.md +221 -0
  597. package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +121 -0
  598. package/dist/knowledge/skills/config-saas-backend/references/managed-startup-configuration.md +46 -0
  599. package/dist/knowledge/skills/configure-billing/SKILL.md +27 -22
  600. package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +27 -15
  601. package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +41 -0
  602. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +36 -17
  603. package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +30 -28
  604. package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +169 -0
  605. package/dist/knowledge/skills/configure-billing/references/framework-billing-resolution-failure-api.md +44 -11
  606. package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +187 -0
  607. package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +76 -0
  608. package/dist/knowledge/skills/configure-coding-agent/SKILL.md +280 -0
  609. package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +168 -0
  610. package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +504 -0
  611. package/dist/knowledge/skills/email-add-template/SKILL.md +41 -69
  612. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +15 -7
  613. package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +120 -0
  614. package/dist/knowledge/skills/engine-component-registration/SKILL.md +19 -12
  615. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +54 -31
  616. package/dist/knowledge/skills/engine-product-definitions/references/connected-feature-workflow.md +130 -0
  617. package/dist/knowledge/skills/engine-product-definitions/references/framework-engine-product-definitions-api.md +25 -0
  618. package/dist/knowledge/skills/engine-product-definitions/references/framework-feature-builders-api.md +215 -0
  619. package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +78 -0
  620. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +33 -24
  621. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +121 -0
  622. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
  623. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -8
  624. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +5 -4
  625. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +46 -9
  626. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +34 -7
  627. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +151 -0
  628. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +6 -10
  629. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +54 -5
  630. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +75 -21
  631. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +258 -0
  632. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +480 -0
  633. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +3983 -0
  634. package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +211 -0
  635. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +165 -0
  636. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-elements-api.md +381 -0
  637. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-trigger-api.md +57 -0
  638. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-view-api.md +89 -0
  639. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +13 -1
  640. package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +14 -0
  641. package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +14 -0
  642. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +3 -1
  643. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +14 -0
  644. package/dist/knowledge/skills/infra-environment-config/SKILL.md +237 -37
  645. package/dist/knowledge/skills/infra-environment-config/references/framework-application-database-api.md +5 -2
  646. package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +174 -21
  647. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +206 -14
  648. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +95 -0
  649. package/dist/knowledge/skills/journey-approve/SKILL.md +28 -8
  650. package/dist/knowledge/skills/journey-approve/references/specification-family-map.md +88 -0
  651. package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +37 -2
  652. package/dist/knowledge/skills/journey-next/SKILL.md +41 -1
  653. package/dist/knowledge/skills/journey-report/SKILL.md +16 -3
  654. package/dist/knowledge/skills/journey-run/SKILL.md +92 -7
  655. package/dist/knowledge/skills/journey-run/references/expert-personas-and-deliberations.md +46 -0
  656. package/dist/knowledge/skills/journey-run/references/framework-playbook-approval-policy.md +108 -0
  657. package/dist/knowledge/skills/journey-status/SKILL.md +14 -4
  658. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +153 -46
  659. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +119 -0
  660. package/dist/knowledge/skills/local-environment-bootstrap/references/initialization-recovery-recipe.md +7 -4
  661. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +253 -33
  662. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +1 -1
  663. package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
  664. package/dist/knowledge/skills/market-alternatives/SKILL.md +1 -1
  665. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +12 -9
  666. package/dist/knowledge/skills/market-channels/SKILL.md +3 -3
  667. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +226 -14
  668. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +226 -14
  669. package/dist/knowledge/skills/market-generation-cli/SKILL.md +56 -9
  670. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +32 -9
  671. package/dist/knowledge/skills/market-icp/SKILL.md +2 -2
  672. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +3 -3
  673. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -2
  674. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +17 -2
  675. package/dist/knowledge/skills/market-persona/SKILL.md +2 -2
  676. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +2 -2
  677. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -0
  678. package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +15 -0
  679. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +1 -1
  680. package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +1 -1
  681. package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +198 -0
  682. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-celebration-overlay-contract.md +51 -0
  683. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-celebration-api.md +79 -0
  684. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-definition-api.md +220 -0
  685. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-progression-tracker-api.md +86 -0
  686. package/dist/knowledge/skills/minion-authoring/SKILL.md +140 -0
  687. package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +84 -0
  688. package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +91 -0
  689. package/dist/knowledge/skills/module-companion-exports/SKILL.md +38 -3
  690. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +211 -14
  691. package/dist/knowledge/skills/module-registration/SKILL.md +50 -33
  692. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +50 -1
  693. package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +142 -0
  694. package/dist/knowledge/skills/module-registration/references/registry-files.md +14 -5
  695. package/dist/knowledge/skills/module-relationships/SKILL.md +62 -0
  696. package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +26 -5
  697. package/dist/knowledge/skills/provider-backend-package/SKILL.md +279 -0
  698. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +80 -0
  699. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +55 -0
  700. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-convention-api.md +48 -0
  701. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +33 -6
  702. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-file-provider-constraints-api.md +99 -47
  703. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +241 -9
  704. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +196 -0
  705. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +50 -0
  706. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +80 -0
  707. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +71 -0
  708. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +58 -0
  709. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +275 -0
  710. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +64 -11
  711. package/dist/knowledge/skills/rate-limit-authoring/references/fixed-window-and-environment-multiplier.md +27 -0
  712. package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +19 -6
  713. package/dist/knowledge/skills/resource-add-field/SKILL.md +12 -5
  714. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +373 -23
  715. package/dist/knowledge/skills/resource-add-module/SKILL.md +116 -265
  716. package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +133 -0
  717. package/dist/knowledge/skills/resource-add-module/references/framework-new-module-wiring-api.md +25 -0
  718. package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +12 -12
  719. package/dist/knowledge/skills/resource-add-resource/SKILL.md +26 -3
  720. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +122 -4
  721. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +25 -0
  722. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +93 -0
  723. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +136 -0
  724. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +85 -0
  725. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +133 -0
  726. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +141 -0
  727. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-step-up-api.md +126 -0
  728. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +859 -0
  729. package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +122 -0
  730. package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +124 -0
  731. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +97 -2
  732. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +457 -15
  733. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +197 -0
  734. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +162 -46
  735. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +452 -0
  736. package/dist/knowledge/skills/resource-custom-view/SKILL.md +5 -0
  737. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +327 -11
  738. package/dist/knowledge/skills/resource-custom-view/references/framework-user-facing-error-message-api.md +50 -0
  739. package/dist/knowledge/skills/resource-external-data/SKILL.md +228 -15
  740. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +54 -7
  741. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +87 -113
  742. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +13 -8
  743. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +69 -26
  744. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +246 -0
  745. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +7 -6
  746. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +5 -3
  747. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +43 -48
  748. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +96 -14
  749. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +47 -15
  750. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +6 -2
  751. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +32 -2
  752. package/dist/knowledge/skills/resource-schema-authoring/examples/basic-resource-schema.example.md +2 -1
  753. package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +17 -0
  754. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +75 -4
  755. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +182 -0
  756. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +245 -0
  757. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +35 -0
  758. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +46 -12
  759. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +480 -15
  760. package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +67 -0
  761. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +74 -14
  762. package/dist/knowledge/skills/resource-schema-authoring/references/polymorphic-per-scope-resources.md +28 -5
  763. package/dist/knowledge/skills/resource-schema-authoring/references/schema-variants-and-discriminators.md +25 -0
  764. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -1
  765. package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +34 -0
  766. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +236 -18
  767. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +54 -1
  768. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +35 -0
  769. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +327 -11
  770. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +140 -4
  771. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
  772. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +155 -5
  773. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +165 -0
  774. package/dist/knowledge/skills/seeding-authoring/SKILL.md +9 -1
  775. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +4 -0
  776. package/dist/knowledge/skills/seeding-operations/SKILL.md +33 -29
  777. package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +13 -5
  778. package/dist/knowledge/skills/seeding-operations/references/data-seeding-cron-scheduler.md +67 -74
  779. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +97 -24
  780. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +205 -0
  781. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +205 -0
  782. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +229 -0
  783. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +38 -3
  784. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +211 -14
  785. package/dist/knowledge/skills/spec-component-update/SKILL.md +30 -11
  786. package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +10 -0
  787. package/dist/knowledge/skills/spec-feature-update/SKILL.md +47 -9
  788. package/dist/knowledge/skills/spec-resource-update/SKILL.md +3 -0
  789. package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +32 -5
  790. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +30 -0
  791. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +1 -0
  792. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +13 -2
  793. package/dist/knowledge/skills/views-add-custom-view/references/framework-view-scope-and-full-custom-api.md +24 -0
  794. package/dist/knowledge/skills/views-app-level/SKILL.md +1 -0
  795. package/dist/knowledge/skills/views-app-level/references/framework-view-scope-and-full-custom-api.md +24 -0
  796. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +1 -0
  797. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +1 -0
  798. package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +64 -0
  799. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +3 -0
  800. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +3 -3
  801. package/dist/knowledge/skills/views-execution-authoring/references/framework-user-facing-error-message-api.md +50 -0
  802. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +43 -7
  803. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +21 -1
  804. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +21 -0
  805. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +41 -1
  806. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +735 -211
  807. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +54 -7
  808. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +67 -1
  809. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -0
  810. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +19 -5
  811. package/dist/knowledge/skills/website-page-authoring/SKILL.md +94 -7
  812. package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +126 -0
  813. package/dist/knowledge/skills/website-section-contact/SKILL.md +96 -146
  814. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -20
  815. package/dist/knowledge/skills/website-section-cta/SKILL.md +19 -20
  816. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -20
  817. package/dist/knowledge/skills/website-section-faq/SKILL.md +19 -20
  818. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -20
  819. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +19 -20
  820. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -20
  821. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +19 -20
  822. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -20
  823. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +19 -20
  824. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -20
  825. package/dist/knowledge/skills/website-section-hero/SKILL.md +37 -26
  826. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -20
  827. package/dist/knowledge/skills/website-section-pricing/SKILL.md +19 -20
  828. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -20
  829. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +19 -20
  830. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -20
  831. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +14 -1
  832. package/dist/knowledge/skills/worker-authoring/SKILL.md +164 -0
  833. package/dist/knowledge/skills/worker-authoring/examples/worker-route.example.md +98 -0
  834. package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +65 -0
  835. package/dist/knowledge/topic-index.json +5335 -1010
  836. package/dist/tsconfig.build.tsbuildinfo +1 -1
  837. package/dist/tsconfig.tsbuildinfo +1 -1
  838. package/package.json +4 -4
  839. package/dist/knowledge/references/example.provider.contribution.backend-billing.md +0 -12
  840. package/dist/knowledge/skills/configure-billing/references/example-provider-contribution-and-backend-config.md +0 -48
  841. /package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/structured-artifact-action.json +0 -0
@@ -0,0 +1 @@
1
+ {"aggregationPolicyRef":"application-creation:aggregation/worst-governance-document-claims-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/governance-document-claims-within-guard","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/governance-document-claims-within-guard","requirementVersion":1}],"instruction":"The subject under judgment is each landed `compliance-document-candidate` for an INTERNAL governance document. For EVERY clause, find the catalog claim guards it names in `claimGuardRefs` in the \"Catalog claim guards\" section of the evidence. A clause's `claimGuardRefs` mixes TWO vocabularies and only one is defined anywhere: a `document-claim-guard:` ref is the CATALOG's, added from the blueprint clauses the clause satisfies, and the evidence section carries its prohibited claims and reviewer instruction. A bare `claim-guard:` ref is the DRAFTER'S OWN statement of what its clause must not be read as claiming; no catalog defines it and none will be supplied. Read it as context about the clause's intent, and NEVER answer INDETERMINATE because its definition is absent — that is not missing evidence, it is a vocabulary that has no definitions, and read the clause's `bodyMarkdown` against each guard's prohibited claims and reviewer instruction. Two things are judged here that a public notice does not meet. FIRST, a FABRICATED RECORD OF REVIEW: a named reviewer, an approver, an approval, an independence disclosure, a qualification or a decision instant that the application has not declared is a GAP, whatever else the clause gets right — a governance document is where those are recorded, and inventing one records a review that did not happen. SECOND, an UNSUPPORTED OPERATING claim: a sentence asserting that a control operates, works or worked ('we monitor', 'access is reviewed quarterly', 'the trail is checked') rather than that something is configured or declared. In an INTERNAL governance document such a claim is legitimate when THREE things hold together: the clause cites a judged run in `evidenceRefs`, that run's verdict CONCLUDED (CONFORMANT or OBSERVATION, never INSUFFICIENT_EVIDENCE or NONCONFORMITY), and the clause states what was measured and over what period. An operating claim missing any of the three is a GAP — uncited it rests on nothing, citing an unconcluded run it rests on a question nobody settled, and without scope or period the reader it is written for cannot check it. A citation may never be laundered either: the runs are the operator judging its own product, so a clause may say what was measured and may NOT say it was verified, certified, audited or independently assured. Also look for: certification, attestation or audit claimed without the authority to make it; a legal conclusion rather than a statement of what the operator does; a NIST publication presented as legal equivalence; self-attestation presented as independent assurance; and an unscoped compliance claim (\"fully secure\", \"ISO-ready\"). Do NOT re-check whether cited facts exist — landing already decided that exactly — and do NOT treat a clause MARKED as not established as a defect: marking is what this lane is for. Name every finding by its `clauseRef`, quote the words, and name the prohibited claim it falls under. Separate severities by CONSEQUENCE: a claim an assurance reader would rely on is a GAP; wording that leans toward one without asserting it is a CONCERN.","schemaVersion":1,"verdictGuidance":{"CONCERN":"No prohibited claim is asserted, but wording leans toward one in a way an assurance reader could take as the claim — a softened operating assertion, a review implied by the passive voice, a scope left implicit. Name each clauseRef and quote it.","GAP":"At least one clause asserts a prohibited claim an assurance reader would rely on — most seriously, a record of review nobody performed, or a control asserted to operate with nothing able to support it. Name each clauseRef, quote the words, and name the prohibited claim.","INDETERMINATE":"The CATALOG guards of the drafted documents are absent from the evidence, or a document has no catalog guard at all, so the clauses cannot be judged against what they must not claim. Say which. A clause-level `claim-guard:` ref having no definition is NOT this: that vocabulary has none anywhere.","PASS":"No clause asserts a prohibited claim: none names a reviewer, approval, independence or decision instant the application has not declared; none asserts that a control operates; none certifies, concludes the law, equates NIST with law, presents self-attestation as independence, or claims unscoped compliance. Marked clauses are not findings."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/governance-document-claims","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:refinement.governance-document-candidate"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
@@ -0,0 +1 @@
1
+ {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-compliance-document-candidate","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/governance-document-claims-within-guard"],"requirementRef":"application-creation:authority-requirement/governance-document-claims","requirementVersion":1,"riskClassRef":"application-creation:risk/compliance-claim-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/governance-document-claims","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/governance-document-claims","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/governance-document-claims","policyVersion":1},"decisionPointRef":"application-creation:decision-point/governance-document-claims","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/governance-document-claims","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/governance-document-claims","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/governance-document-claims-within-guard","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/compliance-document-candidate-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/compliance-document-change","triggerRefs":["application-creation:trigger/compliance-document-candidate-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-governance-document-claims-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/governance-document-claims-within-guard"],"hardFloorRef":"application-creation:hard-floor/compliance-document-candidate-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/governance-document-claims","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/governance-document-claims","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-governance-document-claims-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/governance-document-claims-within-guard","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/governance-document-claims-within-guard","requirementVersion":1}],"instruction":"The subject under judgment is each landed `compliance-document-candidate` for an INTERNAL governance document. For EVERY clause, find the catalog claim guards it names in `claimGuardRefs` in the \"Catalog claim guards\" section of the evidence. A clause's `claimGuardRefs` mixes TWO vocabularies and only one is defined anywhere: a `document-claim-guard:` ref is the CATALOG's, added from the blueprint clauses the clause satisfies, and the evidence section carries its prohibited claims and reviewer instruction. A bare `claim-guard:` ref is the DRAFTER'S OWN statement of what its clause must not be read as claiming; no catalog defines it and none will be supplied. Read it as context about the clause's intent, and NEVER answer INDETERMINATE because its definition is absent — that is not missing evidence, it is a vocabulary that has no definitions, and read the clause's `bodyMarkdown` against each guard's prohibited claims and reviewer instruction. Two things are judged here that a public notice does not meet. FIRST, a FABRICATED RECORD OF REVIEW: a named reviewer, an approver, an approval, an independence disclosure, a qualification or a decision instant that the application has not declared is a GAP, whatever else the clause gets right — a governance document is where those are recorded, and inventing one records a review that did not happen. SECOND, an UNSUPPORTED OPERATING claim: a sentence asserting that a control operates, works or worked ('we monitor', 'access is reviewed quarterly', 'the trail is checked') rather than that something is configured or declared. In an INTERNAL governance document such a claim is legitimate when THREE things hold together: the clause cites a judged run in `evidenceRefs`, that run's verdict CONCLUDED (CONFORMANT or OBSERVATION, never INSUFFICIENT_EVIDENCE or NONCONFORMITY), and the clause states what was measured and over what period. An operating claim missing any of the three is a GAP — uncited it rests on nothing, citing an unconcluded run it rests on a question nobody settled, and without scope or period the reader it is written for cannot check it. A citation may never be laundered either: the runs are the operator judging its own product, so a clause may say what was measured and may NOT say it was verified, certified, audited or independently assured. Also look for: certification, attestation or audit claimed without the authority to make it; a legal conclusion rather than a statement of what the operator does; a NIST publication presented as legal equivalence; self-attestation presented as independent assurance; and an unscoped compliance claim (\"fully secure\", \"ISO-ready\"). Do NOT re-check whether cited facts exist — landing already decided that exactly — and do NOT treat a clause MARKED as not established as a defect: marking is what this lane is for. Name every finding by its `clauseRef`, quote the words, and name the prohibited claim it falls under. Separate severities by CONSEQUENCE: a claim an assurance reader would rely on is a GAP; wording that leans toward one without asserting it is a CONCERN.","schemaVersion":1,"verdictGuidance":{"CONCERN":"No prohibited claim is asserted, but wording leans toward one in a way an assurance reader could take as the claim — a softened operating assertion, a review implied by the passive voice, a scope left implicit. Name each clauseRef and quote it.","GAP":"At least one clause asserts a prohibited claim an assurance reader would rely on — most seriously, a record of review nobody performed, or a control asserted to operate with nothing able to support it. Name each clauseRef, quote the words, and name the prohibited claim.","INDETERMINATE":"The CATALOG guards of the drafted documents are absent from the evidence, or a document has no catalog guard at all, so the clauses cannot be judged against what they must not claim. Say which. A clause-level `claim-guard:` ref having no definition is NOT this: that vocabulary has none anywhere.","PASS":"No clause asserts a prohibited claim: none names a reviewer, approval, independence or decision instant the application has not declared; none asserts that a control operates; none certifies, concludes the law, equates NIST with law, presents self-attestation as independence, or claims unscoped compliance. Marked clauses are not findings."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/governance-document-claims","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:refinement.governance-document-candidate"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/governance-document-claims","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-catalog-claim-guards-of-drafted-documents","criterionRef":"application-creation:criterion/governance-document-claims-within-guard","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/governance-document-claims-within-guard","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/governance-document-candidates-and-catalog-claim-guards"}],"schemaVersion":1}
@@ -0,0 +1,343 @@
1
+ # Governance document candidate method
2
+
3
+ You are drafting ONE internal governance document for this application, from what the application has
4
+ already declared. Follow the `compliance-document-authoring` skill for the rules — refs, clause shape,
5
+ completeness, what a clause may say. This method says which document, what its concerns are, and the two
6
+ things a governance document meets that a public notice does not.
7
+
8
+ ## Choose the document, from the four this lane may draft
9
+
10
+ The candidate contract admits six `documentRef` values. Four of them are this lane's; the two public ones
11
+ (`document:public.privacy-notice`, `document:public.service-terms`) belong to
12
+ `refinement.compliance-document-candidate` and are not yours to draft here.
13
+
14
+ | `documentRef` | what it is | its concerns |
15
+ |---|---|---|
16
+ | `document:governance.scope-system-description` | what the system IS, for an assurance reader | service scope, security controls, audit and accountability, access control and roles, tenancy model |
17
+ | `document:governance.roles-responsibilities` | who is accountable for what | access control and roles, operator identity |
18
+ | `document:governance.program-handbook` | how the governance programme runs | security controls, audit and accountability, access control and roles |
19
+ | `document:governance.document-record-control` | how governed documents are themselves controlled | **none** — see below |
20
+
21
+ **Draft a document this application does not already hold.** The brief opens with what it has already
22
+ drafted, listing each document this lane may produce as ALREADY DRAFTED or not yet. Drafts are keyed by
23
+ `documentRef`, so drafting one that is already there REPLACES it — right when that draft is wrong, a
24
+ wasted run when it is not.
25
+
26
+ Where several remain, **scope and system description** comes first: it is the one an assurance reader
27
+ opens first, the one the other three refer back to, and the only one of the four carrying facts the
28
+ framework derives rather than a person establishes.
29
+
30
+ `document:governance.document-record-control` composes **no application-fact concern**, and that is
31
+ declared rather than missing: it describes how documents are identified, reviewed, released and retired —
32
+ a process the operator defines, not anything derivable from the product. Every section you write for it
33
+ carries `concernRef: null`, and almost every clause is marked. That is the document working, not failing.
34
+
35
+ ## Expect to MARK, and never invent your way past a mark
36
+
37
+ Most of what a governance document asserts is established by a PERSON, not derived from the application.
38
+ Measured on the blueprints: `roles-responsibilities` and `document-record-control` carry no
39
+ specification-derived fact at all — every one of their facts needs a creator decision or a qualified
40
+ review — and the other two carry a handful.
41
+
42
+ So a governance draft that is largely marked incomplete is the expected outcome. Draft every section,
43
+ state precisely what is missing in `incompleteness.needs` and what would close it in
44
+ `incompleteness.closedBy`, and let the marks be the document's contribution. An application that can read
45
+ exactly which governance decisions it owes is further ahead than one holding no document at all.
46
+
47
+ **Two inventions are worse than any gap, and both are specific to these documents.**
48
+
49
+ - **A record of review that did not happen.** These are the documents where a reviewer, an approver, an
50
+ approval, an independence disclosure, a qualification and a decision instant are NAMED. Write one the
51
+ application has not declared and you have not written a weak sentence — you have fabricated the record
52
+ of a review nobody performed. Mark it instead: the fact is owed, and saying so is the answer.
53
+ - **A control asserted to OPERATE, with nothing behind it.** "Access is reviewed quarterly", "we
54
+ monitor", "the trail is checked" are claims about operating effectiveness. In THIS lane one of them
55
+ may be legitimate — and only when a judged run in your brief's evidence section supports it, the
56
+ clause cites that run, and the clause says what was measured and over what period. Without all three,
57
+ say what is CONFIGURED or DECLARED, which is what the facts give you, and mark the rest.
58
+
59
+ ## One section per concern, and SAY which concern
60
+
61
+ Every section carries `concernRef` from the closed compliance-concern vocabulary, or `null` for a section
62
+ that genuinely answers no concern — a preamble, a scope statement, and every section of
63
+ `document-record-control`. Draft one section per concern in the order the table above gives, and produce
64
+ **every** one: a concern nothing can answer becomes a section with a marked clause, never a missing
65
+ heading.
66
+
67
+ The value must be the concern's exact name. A near miss (`access-control` for
68
+ `access-control-and-roles`) is worse than a null: it reports the concern as unaddressed while the
69
+ document addresses it.
70
+
71
+ Each section also names what it satisfies in the catalog — `satisfiesSectionRefs` on the section,
72
+ `satisfiesClauseRefs` on each clause, from the blueprint in your brief. Those are what attach the
73
+ catalog's claim guards to your clauses, so a clause that says what it satisfies is checked against what it
74
+ must not claim, automatically. A clause that says nothing is checked against nothing.
75
+
76
+ A section that supplies no required part of the document answers **`null`**, never `[]` — an empty array
77
+ is refused, because it would be a second spelling of the same state. On a governance document the sections
78
+ that answer `null` are the ones with `concernRef: null` beside them, and `document-record-control` is
79
+ mostly made of them.
80
+
81
+ ## The three ref arrays on every clause
82
+
83
+ Every `…Ref` field is a **namespaced ref**: `namespace:slug`, both halves lowercase, words joined by
84
+ hyphens. One malformed ref rejects the whole draft, and all three arrays are required on every clause —
85
+ two of them may be empty, but **not the first two at once**, because a clause naming neither a fact nor a
86
+ policy area is sourced by nothing.
87
+
88
+ - `factRefs` — the facts this clause rests on, spelled exactly as the facts file declares them. EMPTY is
89
+ normal here: a marked clause usually establishes nothing.
90
+ - `sourcePolicyRefs` — the application POLICY AREA the statement is sourced from, and **every entry must
91
+ be in the `policy:` namespace**: `policy:security-controls`, `policy:access-control`,
92
+ `policy:document-control`. Any other namespace is rejected outright — `policy-area:…` is not a policy
93
+ ref, and neither is a fact ref repeated here. **Do NOT put a fact or its authority in this array.** A
94
+ clause resting on declared facts already cites them through `factRefs`, which resolves them; restating
95
+ one here duplicates the citation beside it and resolves to nothing. So this array is EMPTY for a
96
+ fact-backed clause, and carries a policy area for a clause sourced from a policy rather than a fact.
97
+ - `claimGuardRefs` — at least one: what this clause must NOT be read as claiming. Name the ones that
98
+ apply; do not repeat the same guard on every clause out of habit. You do not name the CATALOG's guard
99
+ for the material — that is added for you from the blueprint clauses this clause `satisfiesClauseRefs`.
100
+
101
+ `reviewChecklistRefs` needs at least one (`review-checklist:<slug>`): what a human must confirm before
102
+ this draft is worth anything. On a governance document that list is long, and it is where "who reviewed
103
+ this, and when" belongs — as something a person must supply, never as a name you write into a clause.
104
+
105
+ `limitationRefs` may be empty and rarely should be: it is where you say, in your own words, what this
106
+ document does NOT cover.
107
+
108
+ ## What the blueprint gives you
109
+
110
+ the declared `document_blueprint` context section of your brief carries, for each document this lane may draft, its sections, its
111
+ clauses and which of them are required. Read the one matching your `documentRef` and treat its required
112
+ clauses as the floor: a required clause you cannot establish is a clause you MARK, never one you omit.
113
+
114
+ ## Citing this application's own measured evidence
115
+
116
+ A governance document is the one place an operator may say what its controls DO, and this lane is the
117
+ only one that may cite the measurements behind such a statement.
118
+
119
+ the declared `assurance_evidence` context section of your brief carries the judged runs this application's own assurance cycle has
120
+ committed: what was measured, under which demand, with what verdict, at which framework revision, and
121
+ whether the judge was calibrated. Read it before writing any sentence about what a control does.
122
+
123
+ - **Cite by putting the run's `assurance-run:` ref in the clause's `evidenceRefs`**, and say in the
124
+ clause what was measured and over what period. A citation a reader cannot scope is one they cannot
125
+ check.
126
+ - **Only a run whose verdict CONCLUDED may support such a statement.** The section marks each one. A
127
+ clause resting on an `INSUFFICIENT_EVIDENCE` run asserts a measurement that did not settle the
128
+ question, which is worse than saying nothing.
129
+ - **Say what it is.** The operator judged its own product with its own harness. A clause may say that
130
+ and what it found; it may not say the result was verified, certified, audited or independently
131
+ assured, and the claim guards refuse the sentence that blurs the two.
132
+ - **Where no run supports the statement, MARK it** — the same answer this lane gives every
133
+ unestablished statement, and the right one.
134
+
135
+ A ref that resolves to no committed run is refused before the draft becomes a file, as is any citation
136
+ at all in a PUBLIC document. Neither is your judgement to make here: cite only what the section lists.
137
+
138
+ ## You do not approve, release or publish
139
+
140
+ You draft the candidate. A human accepts it by committing it; nothing else is acceptance, and landing is
141
+ not approval. You do not author the release — almost everything a release carries is derived from the
142
+ accepted document definition, and a release nobody has approved is composed and marked `UNAPPROVED`
143
+ rather than withheld.
144
+
145
+ **Which is why a missing approval never changes what you do here.** Waiting for one before drafting, and
146
+ describing a draft as approved to get past a gate, are the two symmetric failures; the first is a
147
+ compliance workflow standing in front of the mechanism that builds the application.
148
+
149
+ ## Where the draft goes
150
+
151
+ It lands as a FILE in the application's specifications package, as an ordinary working edit, beside any
152
+ public candidates the application already holds.
153
+
154
+ ---
155
+
156
+ # The compositions
157
+
158
+ Each entry below is one concern: what it asserts, what in the application it derives from, what state it
159
+ usually reaches, and what closes it when it cannot. Use the ones your document's row names and ignore the
160
+ rest.
161
+
162
+ ### Concern: service scope
163
+
164
+ **Asserts** — what the service actually is: the modules it runs, the resources it manages, and the
165
+ surfaces it exposes.
166
+
167
+ **Derives from** — the application's declared modules and their resources, and the surfaces it builds
168
+ (application, API, public website, technical documentation).
169
+
170
+ **Completeness** — `DERIVED`.
171
+
172
+ **Derive it; do not describe the product from its marketing.** Scope in a governed document is the
173
+ boundary of what the statements around it apply to, so an aspirational description silently widens
174
+ every other clause. The declared modules are the honest boundary, and a capability the application
175
+ does not run does not belong here even if it is on the roadmap.
176
+
177
+
178
+ ### Concern: security controls
179
+
180
+ **Asserts** — the security measures the application actually runs, at the level of detail a notice
181
+ needs and no further.
182
+
183
+ **Derives from** — the application's authored authentication configuration (methods enabled, MFA,
184
+ password policy, lockout, step-up, session lifetimes), its access floors, its encryption of stored
185
+ secrets, and its antivirus posture where the `ANTIVIRUS_SCANNING` INFRA capability is provisioned
186
+ (ClamAV, consumed by the engine's file-scanning service on upload). Note this reads the INFRA
187
+ capability, not an engine provider slot: the equally-named `EngineCapability.ANTIVIRUS_SCANNING` was
188
+ withdrawn because no provider could fill it, and a derived control statement must never rest on a
189
+ slot that cannot be configured.
190
+
191
+ **Completeness** — `DERIVED`, bounded.
192
+
193
+ **Bounded is the operative word.** A public notice states that measures exist and their general
194
+ nature. **It must not enumerate the control set**: a published list of exactly which protections are
195
+ in place, and by implication which are not, is a map for somebody attacking the service. Detail
196
+ belongs in a security addendum shared under agreement, not on a public page — so this fragment reads
197
+ very differently in `public.privacy-notice` than in a security schedule, and that difference is
198
+ deliberate rather than an omission.
199
+
200
+ **Never state a certification.** "Compliant", "certified", "audited" and "ISO/SOC" claims are not
201
+ derivable from configuration and are not this document's to make.
202
+
203
+
204
+ ### Concern: audit and accountability
205
+
206
+ **Asserts** — that security-relevant actions are recorded, what kinds are recorded, and where those
207
+ records can be sent.
208
+
209
+ **Derives from** — the application's own audit store, which every application writes; the
210
+ `COMPLIANCE_AUDIT_TRAIL` engine capability, which additionally sends each event to external providers
211
+ (`saas-models` → `external-providers/engine-capabilities.shared.schemas.ts`); the auditable-event
212
+ catalog the engine emits (authentication, authorization grants, consent decisions, token lifecycle,
213
+ configuration and permission changes, cross-tenant administrative access), and per-organization SIEM
214
+ routing where a tenant has configured it.
215
+
216
+ **Completeness** — `DERIVED`.
217
+
218
+ This is one of the fragments where the ENGINE answers for the application. Every generated
219
+ application inherits the event catalog and the emitters; a document may state it without the
220
+ application having configured anything. Where a tenant has additionally routed events to its own
221
+ SIEM, that is the tenant's configuration and belongs in a shared-responsibility statement rather than
222
+ in the operator's own notice.
223
+
224
+
225
+ ### Concern: access control and roles
226
+
227
+ **Asserts** — who inside the operator and inside a customer tenant can reach personal data, and what
228
+ constrains them.
229
+
230
+ **Derives from** — `CORE_APP_ROLES` and `CORE_ORG_ROLES`
231
+ (`saas-models` → `security/authorizations/roles.shared.schemas.ts`) plus the application's own role
232
+ table; the administrative-continuity floors (a tenant cannot be left with no usable owner, the
233
+ application cannot be left with no super-administrator); and the platform-access-grant mechanism,
234
+ under which a platform operator crossing the per-record tenant boundary requires a granted,
235
+ time-bounded authorization. Application-wide directory reads retain independent approval. The
236
+ application audit viewer has a distinct policy: `auditTrail.applicationReadAccess` defaults to
237
+ `AuditApplicationReadAccess.ROLE_BASED` in every environment, admitting the super-administrator or the
238
+ read-only audit-evidence reader role; `INDEPENDENT_APPROVAL` requires a usable application-wide grant in
239
+ addition to the role, and a machine reader (such as an assurance collector) holds one only when it is bound to
240
+ its own credential and signed by a second administrator — a grant bound to a machine never admits the
241
+ administrator who requested it. Access admission, audit observation and retained
242
+ evidence are separate claims: the access decision does not depend on a successful audit write.
243
+
244
+ **Completeness** — `DERIVED`.
245
+
246
+ Worth stating plainly in a B2B notice, because it is the question a customer's own reviewer asks
247
+ first: **operator access is governed by the resource and its declared policy.** Ordinary tenant
248
+ crossings require a usable grant. The application audit viewer is role-based by default, with
249
+ independent approval available as an explicit policy. Its cross-tenant observations still identify
250
+ the operator and tenants reached; role-based access does not imply anonymized logs or fabricate an
251
+ approval record. Actual application-wide grants always retain their independent-approval requirement.
252
+
253
+ **Observation coverage** — the per-record organization gate observes access to an identifiable
254
+ tenant's record when the caller does not already hold organization-wide entry there. Separately,
255
+ declared cross-tenant READ, LIST and SEARCH operations outside the organization-scoped gate observe
256
+ the identifiable tenants in their returned records that the caller does not already belong to,
257
+ grouped into one observation per tenant reached. This collection observer excludes context-free
258
+ internal requests and webhook callbacks; COUNT
259
+ returns no records and is not covered by that observer. Do not turn these scoped mechanisms into a
260
+ claim that every operation or every returned record produces an audit entry.
261
+
262
+ **Delivery and evidence** — these observations are best-effort and do not fail the observed request.
263
+ An unavailable audit service, a synchronous emission error or a rejected emission can leave an
264
+ authorized request without a retained crossing entry. Observer-side drops have an
265
+ `audit_observation_dropped_total` signal and throttled error logs; failures at the primary audit-store
266
+ write have the separate `audit_store_failure_total` signal. Metrics export and log retention must
267
+ actually be configured and operating for those signals to provide evidence beyond the process.
268
+ Neither a loss counter nor an attempted emission substitutes for the missing audit entry.
269
+
270
+ **Document-authoring consequence** — derive the roles, operation declarations and usable-grant
271
+ requirements and the audit viewer's access policy from the application's configuration. Do not
272
+ claim that every audit read required independent approval when the viewer is role-based. Describe the observation mechanisms as supported
273
+ coverage, then substantiate any statement about recorded access with retained audit records and
274
+ evidence that the collection pipeline and loss monitoring were operating over the period claimed.
275
+ An empty crossing search alone does not prove that no operator accessed tenant data. `DERIVED`
276
+ above identifies the source of the access-control description; it does not certify complete audit
277
+ delivery or the application's operational compliance.
278
+
279
+
280
+ ### Concern: tenancy model
281
+
282
+ **Asserts** — that customer data is separated per organization, and where the boundary between the
283
+ operator's responsibilities and the customer's lies.
284
+
285
+ **Derives from** — the `ORGANIZATIONS` engine capability, the organization scoping applied to every
286
+ tenant-scoped resource, and the cross-tenant admission rules. Ordinary tenant crossings must be
287
+ declared and carry a usable access grant. The application audit viewer is a separate policy surface:
288
+ it defaults to role-based access (the super-administrator or the read-only audit-evidence reader), with
289
+ `auditTrail.applicationReadAccess` optionally set to `AuditApplicationReadAccess.INDEPENDENT_APPROVAL`, under
290
+ which a machine reader needs a second-signed grant bound to its own credential. Both modes retain cross-tenant read observations;
291
+ role-based access neither implies anonymized records nor supplies an approval that never occurred.
292
+
293
+ **Completeness** — `DERIVED`.
294
+
295
+ **This fragment is where shared responsibility is described, and it must never be flattened.** In a
296
+ B2B SaaS the operator is a PROCESSOR for the data a customer stores about its own people, and a
297
+ CONTROLLER for the data it holds about the customer's users as account holders. Those are different
298
+ roles with different duties over the same database. Say which is which; do not pick one and apply it
299
+ to everything.
300
+
301
+ **The attribution has a home now.** `operatorComplianceIdentity.roleAllocations` in
302
+ `wildo.saas.config.ts` carries one role per population of data — PROCESSOR for the records a customer
303
+ stores about its own people, CONTROLLER for the account data of the people who administer them. It is
304
+ a LIST for exactly the reason this fragment gives: those are different roles over the same database,
305
+ and a single field would force one of them to be wrong.
306
+
307
+ Where the attribution is not established, that is a `NEEDS_DECISION` — never a guess — and the
308
+ surface to name is `roleAllocations`. Not `NEEDS_FRAMEWORK`: there is somewhere to write the answer,
309
+ so the remedy is to fill it in rather than to build something. See the legal-basis fragment.
310
+
311
+
312
+ ### Concern: operator identity
313
+
314
+ **Asserts** — who legally operates the service: entity name, registered address, contact route for
315
+ data-protection questions, and a representative where one is required.
316
+
317
+ **Derives from** — `operatorComplianceIdentity` in `wildo.saas.config.ts`: the legal entity, its
318
+ registered address, the privacy contact route, and an Art. 27 representative where one is required.
319
+
320
+ The VALUE is never derivable — a legal entity is a fact about the world, not a property of a codebase.
321
+ What the framework provides is the PLACE to record it, and until 2026-08-30 it did not: this fragment
322
+ said "no engine change would close it", which was right about derivation and wrong about the home.
323
+ The consequence was concrete. A landing REPLACES the produced document on every run, so an operator
324
+ who answered by editing the document lost the answer at the next regeneration — the answer has to live
325
+ in the application or it does not survive.
326
+
327
+ **Completeness** — `DERIVED` when the identity is declared; `NEEDS_DECISION` when it is not.
328
+
329
+ ⚠️ `NEEDS_DECISION`, not `NEEDS_FRAMEWORK`, and the distinction is load-bearing now that the surface
330
+ exists. `NEEDS_FRAMEWORK` means there is nowhere to record the answer; `NEEDS_DECISION` means there is
331
+ and nobody has. They have different remedies — build something, versus fill something in — and a
332
+ reader who cannot tell them apart cannot act on either. Say which surface the answer goes to.
333
+
334
+ **What closes it** — the operator declaring `operatorComplianceIdentity`. It is cheap and it can be
335
+ filled in later without redrafting anything around it, which is the reason it is not a blocker.
336
+
337
+ **Never infer it.** Not from the application name, not from a domain, not from another application,
338
+ not from model memory. A published legal document naming the wrong entity is worse than one that says
339
+ the entity is not yet recorded — the first misdirects a person exercising a right, the second tells
340
+ them the document is incomplete.
341
+
342
+ **Every document needs this fragment**, which makes it the clearest demonstration of why producing
343
+ with gaps beats blocking: the whole document set would be unproducible until one form is filled in.
@@ -0,0 +1,54 @@
1
+ {
2
+ "ref": "refinement.governance-document-candidate",
3
+ "version": "0.5.0",
4
+ "phase": "refinement",
5
+ "intent": "Propose structured candidate content for ONE of the four internal governance documents — scope and system description, roles and responsibilities, the programme handbook, or document and record control — from what the application has already declared. The companion agent may draft prose but cannot invent a fact, decide a legal question, name a reviewer, record a decision instant, approve or release: every clause it writes is checked against the accepted `document-facts` family, and a clause asserting a fact the application never declared is refused before it becomes a file.",
6
+ "preconditions": [
7
+ {
8
+ "kind": "artifact_expected",
9
+ "selector": {
10
+ "family": "document-facts"
11
+ }
12
+ }
13
+ ],
14
+ "inputs": [
15
+ {
16
+ "family": "document-facts"
17
+ }
18
+ ],
19
+ "outputs": [
20
+ {
21
+ "family": "compliance-document-candidate",
22
+ "schemaRef": "saas-specifications:ComplianceDocumentCandidate",
23
+ "description": "An untrusted structured content proposal for ONE internal governance document, landing as a FILE for a human to read and commit. Its clauses are validated against the application's accepted document facts before the write; landing is never an approval, a release or a publication."
24
+ }
25
+ ],
26
+ "stepOutputs": [],
27
+ "method": {
28
+ "guidance": "# Governance document candidate method\n\nYou are drafting ONE internal governance document for this application, from what the application has\nalready declared. Follow the `compliance-document-authoring` skill for the rules — refs, clause shape,\ncompleteness, what a clause may say. This method says which document, what its concerns are, and the two\nthings a governance document meets that a public notice does not.\n\n## Choose the document, from the four this lane may draft\n\nThe candidate contract admits six `documentRef` values. Four of them are this lane's; the two public ones\n(`document:public.privacy-notice`, `document:public.service-terms`) belong to\n`refinement.compliance-document-candidate` and are not yours to draft here.\n\n| `documentRef` | what it is | its concerns |\n|---|---|---|\n| `document:governance.scope-system-description` | what the system IS, for an assurance reader | service scope, security controls, audit and accountability, access control and roles, tenancy model |\n| `document:governance.roles-responsibilities` | who is accountable for what | access control and roles, operator identity |\n| `document:governance.program-handbook` | how the governance programme runs | security controls, audit and accountability, access control and roles |\n| `document:governance.document-record-control` | how governed documents are themselves controlled | **none** — see below |\n\n**Draft a document this application does not already hold.** The brief opens with what it has already\ndrafted, listing each document this lane may produce as ALREADY DRAFTED or not yet. Drafts are keyed by\n`documentRef`, so drafting one that is already there REPLACES it — right when that draft is wrong, a\nwasted run when it is not.\n\nWhere several remain, **scope and system description** comes first: it is the one an assurance reader\nopens first, the one the other three refer back to, and the only one of the four carrying facts the\nframework derives rather than a person establishes.\n\n`document:governance.document-record-control` composes **no application-fact concern**, and that is\ndeclared rather than missing: it describes how documents are identified, reviewed, released and retired —\na process the operator defines, not anything derivable from the product. Every section you write for it\ncarries `concernRef: null`, and almost every clause is marked. That is the document working, not failing.\n\n## Expect to MARK, and never invent your way past a mark\n\nMost of what a governance document asserts is established by a PERSON, not derived from the application.\nMeasured on the blueprints: `roles-responsibilities` and `document-record-control` carry no\nspecification-derived fact at all — every one of their facts needs a creator decision or a qualified\nreview — and the other two carry a handful.\n\nSo a governance draft that is largely marked incomplete is the expected outcome. Draft every section,\nstate precisely what is missing in `incompleteness.needs` and what would close it in\n`incompleteness.closedBy`, and let the marks be the document's contribution. An application that can read\nexactly which governance decisions it owes is further ahead than one holding no document at all.\n\n**Two inventions are worse than any gap, and both are specific to these documents.**\n\n- **A record of review that did not happen.** These are the documents where a reviewer, an approver, an\n approval, an independence disclosure, a qualification and a decision instant are NAMED. Write one the\n application has not declared and you have not written a weak sentence — you have fabricated the record\n of a review nobody performed. Mark it instead: the fact is owed, and saying so is the answer.\n- **A control asserted to OPERATE, with nothing behind it.** \"Access is reviewed quarterly\", \"we\n monitor\", \"the trail is checked\" are claims about operating effectiveness. In THIS lane one of them\n may be legitimate — and only when a judged run in your brief's evidence section supports it, the\n clause cites that run, and the clause says what was measured and over what period. Without all three,\n say what is CONFIGURED or DECLARED, which is what the facts give you, and mark the rest.\n\n## One section per concern, and SAY which concern\n\nEvery section carries `concernRef` from the closed compliance-concern vocabulary, or `null` for a section\nthat genuinely answers no concern — a preamble, a scope statement, and every section of\n`document-record-control`. Draft one section per concern in the order the table above gives, and produce\n**every** one: a concern nothing can answer becomes a section with a marked clause, never a missing\nheading.\n\nThe value must be the concern's exact name. A near miss (`access-control` for\n`access-control-and-roles`) is worse than a null: it reports the concern as unaddressed while the\ndocument addresses it.\n\nEach section also names what it satisfies in the catalog — `satisfiesSectionRefs` on the section,\n`satisfiesClauseRefs` on each clause, from the blueprint in your brief. Those are what attach the\ncatalog's claim guards to your clauses, so a clause that says what it satisfies is checked against what it\nmust not claim, automatically. A clause that says nothing is checked against nothing.\n\nA section that supplies no required part of the document answers **`null`**, never `[]` — an empty array\nis refused, because it would be a second spelling of the same state. On a governance document the sections\nthat answer `null` are the ones with `concernRef: null` beside them, and `document-record-control` is\nmostly made of them.\n\n## The three ref arrays on every clause\n\nEvery `…Ref` field is a **namespaced ref**: `namespace:slug`, both halves lowercase, words joined by\nhyphens. One malformed ref rejects the whole draft, and all three arrays are required on every clause —\ntwo of them may be empty, but **not the first two at once**, because a clause naming neither a fact nor a\npolicy area is sourced by nothing.\n\n- `factRefs` — the facts this clause rests on, spelled exactly as the facts file declares them. EMPTY is\n normal here: a marked clause usually establishes nothing.\n- `sourcePolicyRefs` — the application POLICY AREA the statement is sourced from, and **every entry must\n be in the `policy:` namespace**: `policy:security-controls`, `policy:access-control`,\n `policy:document-control`. Any other namespace is rejected outright — `policy-area:…` is not a policy\n ref, and neither is a fact ref repeated here. **Do NOT put a fact or its authority in this array.** A\n clause resting on declared facts already cites them through `factRefs`, which resolves them; restating\n one here duplicates the citation beside it and resolves to nothing. So this array is EMPTY for a\n fact-backed clause, and carries a policy area for a clause sourced from a policy rather than a fact.\n- `claimGuardRefs` — at least one: what this clause must NOT be read as claiming. Name the ones that\n apply; do not repeat the same guard on every clause out of habit. You do not name the CATALOG's guard\n for the material — that is added for you from the blueprint clauses this clause `satisfiesClauseRefs`.\n\n`reviewChecklistRefs` needs at least one (`review-checklist:<slug>`): what a human must confirm before\nthis draft is worth anything. On a governance document that list is long, and it is where \"who reviewed\nthis, and when\" belongs — as something a person must supply, never as a name you write into a clause.\n\n`limitationRefs` may be empty and rarely should be: it is where you say, in your own words, what this\ndocument does NOT cover.\n\n## What the blueprint gives you\n\nthe declared `document_blueprint` context section of your brief carries, for each document this lane may draft, its sections, its\nclauses and which of them are required. Read the one matching your `documentRef` and treat its required\nclauses as the floor: a required clause you cannot establish is a clause you MARK, never one you omit.\n\n## Citing this application's own measured evidence\n\nA governance document is the one place an operator may say what its controls DO, and this lane is the\nonly one that may cite the measurements behind such a statement.\n\nthe declared `assurance_evidence` context section of your brief carries the judged runs this application's own assurance cycle has\ncommitted: what was measured, under which demand, with what verdict, at which framework revision, and\nwhether the judge was calibrated. Read it before writing any sentence about what a control does.\n\n- **Cite by putting the run's `assurance-run:` ref in the clause's `evidenceRefs`**, and say in the\n clause what was measured and over what period. A citation a reader cannot scope is one they cannot\n check.\n- **Only a run whose verdict CONCLUDED may support such a statement.** The section marks each one. A\n clause resting on an `INSUFFICIENT_EVIDENCE` run asserts a measurement that did not settle the\n question, which is worse than saying nothing.\n- **Say what it is.** The operator judged its own product with its own harness. A clause may say that\n and what it found; it may not say the result was verified, certified, audited or independently\n assured, and the claim guards refuse the sentence that blurs the two.\n- **Where no run supports the statement, MARK it** — the same answer this lane gives every\n unestablished statement, and the right one.\n\nA ref that resolves to no committed run is refused before the draft becomes a file, as is any citation\nat all in a PUBLIC document. Neither is your judgement to make here: cite only what the section lists.\n\n## You do not approve, release or publish\n\nYou draft the candidate. A human accepts it by committing it; nothing else is acceptance, and landing is\nnot approval. You do not author the release — almost everything a release carries is derived from the\naccepted document definition, and a release nobody has approved is composed and marked `UNAPPROVED`\nrather than withheld.\n\n**Which is why a missing approval never changes what you do here.** Waiting for one before drafting, and\ndescribing a draft as approved to get past a gate, are the two symmetric failures; the first is a\ncompliance workflow standing in front of the mechanism that builds the application.\n\n## Where the draft goes\n\nIt lands as a FILE in the application's specifications package, as an ordinary working edit, beside any\npublic candidates the application already holds.\n\n---\n\n# The compositions\n\nEach entry below is one concern: what it asserts, what in the application it derives from, what state it\nusually reaches, and what closes it when it cannot. Use the ones your document's row names and ignore the\nrest.\n\n### Concern: service scope\n\n**Asserts** — what the service actually is: the modules it runs, the resources it manages, and the\nsurfaces it exposes.\n\n**Derives from** — the application's declared modules and their resources, and the surfaces it builds\n(application, API, public website, technical documentation).\n\n**Completeness** — `DERIVED`.\n\n**Derive it; do not describe the product from its marketing.** Scope in a governed document is the\nboundary of what the statements around it apply to, so an aspirational description silently widens\nevery other clause. The declared modules are the honest boundary, and a capability the application\ndoes not run does not belong here even if it is on the roadmap.\n\n\n### Concern: security controls\n\n**Asserts** — the security measures the application actually runs, at the level of detail a notice\nneeds and no further.\n\n**Derives from** — the application's authored authentication configuration (methods enabled, MFA,\npassword policy, lockout, step-up, session lifetimes), its access floors, its encryption of stored\nsecrets, and its antivirus posture where the `ANTIVIRUS_SCANNING` INFRA capability is provisioned\n(ClamAV, consumed by the engine's file-scanning service on upload). Note this reads the INFRA\ncapability, not an engine provider slot: the equally-named `EngineCapability.ANTIVIRUS_SCANNING` was\nwithdrawn because no provider could fill it, and a derived control statement must never rest on a\nslot that cannot be configured.\n\n**Completeness** — `DERIVED`, bounded.\n\n**Bounded is the operative word.** A public notice states that measures exist and their general\nnature. **It must not enumerate the control set**: a published list of exactly which protections are\nin place, and by implication which are not, is a map for somebody attacking the service. Detail\nbelongs in a security addendum shared under agreement, not on a public page — so this fragment reads\nvery differently in `public.privacy-notice` than in a security schedule, and that difference is\ndeliberate rather than an omission.\n\n**Never state a certification.** \"Compliant\", \"certified\", \"audited\" and \"ISO/SOC\" claims are not\nderivable from configuration and are not this document's to make.\n\n\n### Concern: audit and accountability\n\n**Asserts** — that security-relevant actions are recorded, what kinds are recorded, and where those\nrecords can be sent.\n\n**Derives from** — the application's own audit store, which every application writes; the\n`COMPLIANCE_AUDIT_TRAIL` engine capability, which additionally sends each event to external providers\n(`saas-models` → `external-providers/engine-capabilities.shared.schemas.ts`); the auditable-event\ncatalog the engine emits (authentication, authorization grants, consent decisions, token lifecycle,\nconfiguration and permission changes, cross-tenant administrative access), and per-organization SIEM\nrouting where a tenant has configured it.\n\n**Completeness** — `DERIVED`.\n\nThis is one of the fragments where the ENGINE answers for the application. Every generated\napplication inherits the event catalog and the emitters; a document may state it without the\napplication having configured anything. Where a tenant has additionally routed events to its own\nSIEM, that is the tenant's configuration and belongs in a shared-responsibility statement rather than\nin the operator's own notice.\n\n\n### Concern: access control and roles\n\n**Asserts** — who inside the operator and inside a customer tenant can reach personal data, and what\nconstrains them.\n\n**Derives from** — `CORE_APP_ROLES` and `CORE_ORG_ROLES`\n(`saas-models` → `security/authorizations/roles.shared.schemas.ts`) plus the application's own role\ntable; the administrative-continuity floors (a tenant cannot be left with no usable owner, the\napplication cannot be left with no super-administrator); and the platform-access-grant mechanism,\nunder which a platform operator crossing the per-record tenant boundary requires a granted,\ntime-bounded authorization. Application-wide directory reads retain independent approval. The\napplication audit viewer has a distinct policy: `auditTrail.applicationReadAccess` defaults to\n`AuditApplicationReadAccess.ROLE_BASED` in every environment, admitting the super-administrator or the\nread-only audit-evidence reader role; `INDEPENDENT_APPROVAL` requires a usable application-wide grant in\naddition to the role, and a machine reader (such as an assurance collector) holds one only when it is bound to\nits own credential and signed by a second administrator — a grant bound to a machine never admits the\nadministrator who requested it. Access admission, audit observation and retained\nevidence are separate claims: the access decision does not depend on a successful audit write.\n\n**Completeness** — `DERIVED`.\n\nWorth stating plainly in a B2B notice, because it is the question a customer's own reviewer asks\nfirst: **operator access is governed by the resource and its declared policy.** Ordinary tenant\ncrossings require a usable grant. The application audit viewer is role-based by default, with\nindependent approval available as an explicit policy. Its cross-tenant observations still identify\nthe operator and tenants reached; role-based access does not imply anonymized logs or fabricate an\napproval record. Actual application-wide grants always retain their independent-approval requirement.\n\n**Observation coverage** — the per-record organization gate observes access to an identifiable\ntenant's record when the caller does not already hold organization-wide entry there. Separately,\ndeclared cross-tenant READ, LIST and SEARCH operations outside the organization-scoped gate observe\nthe identifiable tenants in their returned records that the caller does not already belong to,\ngrouped into one observation per tenant reached. This collection observer excludes context-free\ninternal requests and webhook callbacks; COUNT\nreturns no records and is not covered by that observer. Do not turn these scoped mechanisms into a\nclaim that every operation or every returned record produces an audit entry.\n\n**Delivery and evidence** — these observations are best-effort and do not fail the observed request.\nAn unavailable audit service, a synchronous emission error or a rejected emission can leave an\nauthorized request without a retained crossing entry. Observer-side drops have an\n`audit_observation_dropped_total` signal and throttled error logs; failures at the primary audit-store\nwrite have the separate `audit_store_failure_total` signal. Metrics export and log retention must\nactually be configured and operating for those signals to provide evidence beyond the process.\nNeither a loss counter nor an attempted emission substitutes for the missing audit entry.\n\n**Document-authoring consequence** — derive the roles, operation declarations and usable-grant\nrequirements and the audit viewer's access policy from the application's configuration. Do not\nclaim that every audit read required independent approval when the viewer is role-based. Describe the observation mechanisms as supported\ncoverage, then substantiate any statement about recorded access with retained audit records and\nevidence that the collection pipeline and loss monitoring were operating over the period claimed.\nAn empty crossing search alone does not prove that no operator accessed tenant data. `DERIVED`\nabove identifies the source of the access-control description; it does not certify complete audit\ndelivery or the application's operational compliance.\n\n\n### Concern: tenancy model\n\n**Asserts** — that customer data is separated per organization, and where the boundary between the\noperator's responsibilities and the customer's lies.\n\n**Derives from** — the `ORGANIZATIONS` engine capability, the organization scoping applied to every\ntenant-scoped resource, and the cross-tenant admission rules. Ordinary tenant crossings must be\ndeclared and carry a usable access grant. The application audit viewer is a separate policy surface:\nit defaults to role-based access (the super-administrator or the read-only audit-evidence reader), with\n`auditTrail.applicationReadAccess` optionally set to `AuditApplicationReadAccess.INDEPENDENT_APPROVAL`, under\nwhich a machine reader needs a second-signed grant bound to its own credential. Both modes retain cross-tenant read observations;\nrole-based access neither implies anonymized records nor supplies an approval that never occurred.\n\n**Completeness** — `DERIVED`.\n\n**This fragment is where shared responsibility is described, and it must never be flattened.** In a\nB2B SaaS the operator is a PROCESSOR for the data a customer stores about its own people, and a\nCONTROLLER for the data it holds about the customer's users as account holders. Those are different\nroles with different duties over the same database. Say which is which; do not pick one and apply it\nto everything.\n\n**The attribution has a home now.** `operatorComplianceIdentity.roleAllocations` in\n`wildo.saas.config.ts` carries one role per population of data — PROCESSOR for the records a customer\nstores about its own people, CONTROLLER for the account data of the people who administer them. It is\na LIST for exactly the reason this fragment gives: those are different roles over the same database,\nand a single field would force one of them to be wrong.\n\nWhere the attribution is not established, that is a `NEEDS_DECISION` — never a guess — and the\nsurface to name is `roleAllocations`. Not `NEEDS_FRAMEWORK`: there is somewhere to write the answer,\nso the remedy is to fill it in rather than to build something. See the legal-basis fragment.\n\n\n### Concern: operator identity\n\n**Asserts** — who legally operates the service: entity name, registered address, contact route for\ndata-protection questions, and a representative where one is required.\n\n**Derives from** — `operatorComplianceIdentity` in `wildo.saas.config.ts`: the legal entity, its\nregistered address, the privacy contact route, and an Art. 27 representative where one is required.\n\nThe VALUE is never derivable — a legal entity is a fact about the world, not a property of a codebase.\nWhat the framework provides is the PLACE to record it, and until 2026-08-30 it did not: this fragment\nsaid \"no engine change would close it\", which was right about derivation and wrong about the home.\nThe consequence was concrete. A landing REPLACES the produced document on every run, so an operator\nwho answered by editing the document lost the answer at the next regeneration — the answer has to live\nin the application or it does not survive.\n\n**Completeness** — `DERIVED` when the identity is declared; `NEEDS_DECISION` when it is not.\n\n⚠️ `NEEDS_DECISION`, not `NEEDS_FRAMEWORK`, and the distinction is load-bearing now that the surface\nexists. `NEEDS_FRAMEWORK` means there is nowhere to record the answer; `NEEDS_DECISION` means there is\nand nobody has. They have different remedies — build something, versus fill something in — and a\nreader who cannot tell them apart cannot act on either. Say which surface the answer goes to.\n\n**What closes it** — the operator declaring `operatorComplianceIdentity`. It is cheap and it can be\nfilled in later without redrafting anything around it, which is the reason it is not a blocker.\n\n**Never infer it.** Not from the application name, not from a domain, not from another application,\nnot from model memory. A published legal document naming the wrong entity is worse than one that says\nthe entity is not yet recorded — the first misdirects a person exercising a right, the second tells\nthem the document is incomplete.\n\n**Every document needs this fragment**, which makes it the clearest demonstration of why producing\nwith gaps beats blocking: the whole document set would be unproducible until one form is filled in.\n",
29
+ "skillRefs": [
30
+ "compliance-document-authoring"
31
+ ],
32
+ "skillBodyRefs": [],
33
+ "contextSources": [
34
+ "document_blueprint",
35
+ "assurance_evidence",
36
+ "authored_document_facts"
37
+ ],
38
+ "draftableDocumentDefinitionRefs": [
39
+ "document-definition:governance.scope-system-description",
40
+ "document-definition:governance.roles-responsibilities",
41
+ "document-definition:governance.program-handbook",
42
+ "document-definition:governance.document-record-control"
43
+ ],
44
+ "suspendsForClarification": false,
45
+ "briefAdequacyGate": false,
46
+ "briefAdequacyExcludedSources": []
47
+ },
48
+ "executor": "companion_agent",
49
+ "approval": "approve_result",
50
+ "budget": {
51
+ "maxRuns": 3
52
+ },
53
+ "onFailure": "keep_and_flag"
54
+ }
@@ -0,0 +1 @@
1
+ {"aggregationPolicyRef":"application-creation:aggregation/worst-brand-identity-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.audience","brand.asset","market.icp"],"criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1}],"instruction":"Determine whether the brief hands off correctly: every targetIcpRef in the audience names an ICP the market snapshot holds and none is an anti-target; the audience rationale follows from the brief's own tone and mission; and resolvedAssets is EMPTY, because assets are the companion logo step's output and a hand-authored asset reference would be overwritten or flagged.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The audience is absent although the market snapshot names ICPs the tone was chosen for, or the rationale is generic.","GAP":"An audience ref naming an ICP the market does not hold or an anti-target, or a resolvedAssets entry authored by hand.","INDETERMINATE":"The market snapshot's ICPs are not in evidence, so the audience cannot be checked.","PASS":"Every audience ref resolves to a market ICP that is not an anti-target, and resolvedAssets is empty."}},{"assessesAspects":["brand.name","brand.logo-direction","brand.visual-tone","vision.idea","vision.mission"],"criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1}],"instruction":"Determine whether the brand brief is GROUNDED: the brand name is the exact string the creator gave; the logo direction's symbolism derives from the vision's idea and mission rather than a decorative motif; the visual tone translates the market's verbal voice where a market snapshot exists and is noted as provisional where it does not; and no mark direction or tone appears that the creator's interview answers do not support. A partially-directed brief (name only, direction still open) is a legitimate state, not a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a thin symbolism rationale, a tone that only loosely follows the market voice, or a background treatment the pipeline must compensate for.","GAP":"A mark direction or tone the creator did not give, a name that differs from the interview, or symbolism unrelated to the vision's idea and mission.","INDETERMINATE":"The interview answers or the vision are not in evidence, so grounding cannot be established.","PASS":"The name is the creator's, the symbolism traces to the vision, the tone follows the market voice or is honestly provisional, and nothing is invented beyond the interview."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-identity","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-identity"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
@@ -0,0 +1 @@
1
+ {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-brand-brief","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision"],"requirementRef":"application-creation:authority-requirement/brand-identity-result","requirementVersion":1,"riskClassRef":"application-creation:risk/brand-brief-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/brand-identity","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/brand-identity-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/brand-identity","policyVersion":1},"decisionPointRef":"application-creation:decision-point/brand-identity-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/brand-identity-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/brand-identity","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/brand-brief-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-brand-brief-change","triggerRefs":["application-creation:trigger/brand-brief-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-brand-identity-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision"],"hardFloorRef":"application-creation:hard-floor/brand-brief-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/brand-identity-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/brand-identity","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-brand-identity-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.audience","brand.asset","market.icp"],"criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1}],"instruction":"Determine whether the brief hands off correctly: every targetIcpRef in the audience names an ICP the market snapshot holds and none is an anti-target; the audience rationale follows from the brief's own tone and mission; and resolvedAssets is EMPTY, because assets are the companion logo step's output and a hand-authored asset reference would be overwritten or flagged.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The audience is absent although the market snapshot names ICPs the tone was chosen for, or the rationale is generic.","GAP":"An audience ref naming an ICP the market does not hold or an anti-target, or a resolvedAssets entry authored by hand.","INDETERMINATE":"The market snapshot's ICPs are not in evidence, so the audience cannot be checked.","PASS":"Every audience ref resolves to a market ICP that is not an anti-target, and resolvedAssets is empty."}},{"assessesAspects":["brand.name","brand.logo-direction","brand.visual-tone","vision.idea","vision.mission"],"criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1}],"instruction":"Determine whether the brand brief is GROUNDED: the brand name is the exact string the creator gave; the logo direction's symbolism derives from the vision's idea and mission rather than a decorative motif; the visual tone translates the market's verbal voice where a market snapshot exists and is noted as provisional where it does not; and no mark direction or tone appears that the creator's interview answers do not support. A partially-directed brief (name only, direction still open) is a legitimate state, not a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a thin symbolism rationale, a tone that only loosely follows the market voice, or a background treatment the pipeline must compensate for.","GAP":"A mark direction or tone the creator did not give, a name that differs from the interview, or symbolism unrelated to the vision's idea and mission.","INDETERMINATE":"The interview answers or the vision are not in evidence, so grounding cannot be established.","PASS":"The name is the creator's, the symbolism traces to the vision, the tone follows the market voice or is honestly provisional, and nothing is invented beyond the interview."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-identity","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-identity"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/brand-identity","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-market-and-brand-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-market-and-brand-candidate"}],"schemaVersion":1}
@@ -95,6 +95,14 @@ knows:
95
95
  (the color STORY, not hex values), and optional hex `colorSeeds` pinned only
96
96
  when the brand has already committed to anchors that must agree with the
97
97
  design system.
98
+ - **Audience** (optional). WHO the brand is for: `targetIcpRefs`, the refs of
99
+ the market ICPs its name and tone are chosen to speak to, copied exactly from
100
+ the market's `icps`, plus a one-line `rationale`. Derive it from what the brief
101
+ already says: the ICP whose preferred voice the visual tone translates, the
102
+ segment the mission and tagline address. Never name a segment the market does
103
+ not hold, and never list an anti-target. Downstream agents are given the
104
+ brand's ICPs, and through them their personas and positionings, from this one
105
+ declaration.
98
106
 
99
107
  ## What you emit
100
108
 
@@ -102,14 +110,15 @@ A single `BrandSnapshot`:
102
110
 
103
111
  - `version` — the snapshot format version (leave at its default unless told otherwise).
104
112
  - `name` — the required anchor (`brandName`, optional `tagline`).
105
- - `logoDirection` / `visualTone` — the optional singletons, present only if elicited.
113
+ - `logoDirection` / `visualTone` / `audience` — the optional singletons, present only if elicited.
106
114
  - `resolvedAssets` — **leave empty.** This is the companion logo step's output,
107
115
  not something you author. Hand-authoring it fabricates asset references the
108
116
  pipeline will overwrite or the validator will flag.
109
117
 
110
118
  Author every entity in English. Follow the `brand-logo-authoring` skill for the
111
119
  exact field contracts and the mark-type / background / visual-tone decision
112
- aids.
120
+ aids — its full text is in your brief, under "The skills this method tells you
121
+ to FOLLOW". Read it there; you cannot open files.
113
122
 
114
123
  ## Quality gate
115
124
 
@@ -122,6 +131,10 @@ not-yet-complete brief. Emit a clean brief and let the warnings stand honestly
122
131
  when the brand genuinely is not fully directed yet, rather than inventing a
123
132
  mark to silence them.
124
133
 
134
+ After landing, the advisory judge reads the brief against two criteria — grounding in
135
+ the interview and the vision, and the audience-and-assets hand-off — and its verdicts
136
+ reach the creator's review as notes. A verdict never refuses a landing.
137
+
125
138
  ## Approval
126
139
 
127
140
  The drafted `BrandSnapshot` is presented to the creator for approval before it
@@ -137,15 +150,19 @@ Before you start, read the current journey state, the vision brief that grounds
137
150
  the brand's meaning, and any brand brief that already exists so you refine it
138
151
  rather than re-eliciting it from scratch.
139
152
 
140
- // TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)
141
- // TODO CLI COMMAND: wildo context vision-brief (read the vision to derive symbolism/tone)
142
- // TODO CLI COMMAND: wildo context brand-brief (read the existing brand brief, if any, to refine it)
153
+ (The vision and any previously landed brand brief arrive in your brief as the `vision-brief` and
154
+ `brand-brief` input sections.)
143
155
 
144
156
  ## References
145
157
 
146
- - `.claude/skills/brand-logo-authoring/SKILL.md` — the field contracts for the
147
- `BrandSnapshot` (name / logoDirection / visualTone), the mark-type selection
148
- table, background derivation-safety, and deriving the visual tone from the
149
- market voice.
150
- - `.claude/skills/journey-status/SKILL.md` — read current journey state and
151
- whether a `vision-brief` / `brand-brief` already exists.
158
+ These are skill FOLDERS installed in the application, and this step has no tools,
159
+ so it does not open them. What reaches you is stated per skill below.
160
+
161
+ - `brand-logo-authoring` — the field contracts for the `BrandSnapshot` (name /
162
+ logoDirection / visualTone), the mark-type selection table, background
163
+ derivation-safety, and deriving the visual tone from the market voice. Its
164
+ FULL TEXT is in your brief; follow it exactly.
165
+ - `journey-status` — reads the current journey state and whether a
166
+ `vision-brief` / `brand-brief` already exists. That is a READ a tool-using
167
+ agent performs; you receive its answer as your declared inputs instead, so
168
+ you never need to consult the skill itself.