@wildo-ai/framework-knowledge 1.1.4 → 1.1.6

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 (1167) hide show
  1. package/dist/claude-marketplace/.claude-plugin/marketplace.json +14 -0
  2. package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +8 -0
  3. package/dist/claude-marketplace/plugins/wildo/agents/wildo-deriver.md +41 -0
  4. package/dist/claude-marketplace/plugins/wildo/hooks/hooks.json +18 -0
  5. package/dist/claude-marketplace/plugins/wildo/monitors/monitors.json +8 -0
  6. package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +38 -0
  7. package/dist/claude-marketplace/plugins/wildo/references/approval-and-failure-policy.md +110 -0
  8. package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +29 -0
  9. package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +61 -0
  10. package/dist/claude-marketplace/plugins/wildo/references/expert-personas-and-deliberations.md +46 -0
  11. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +67 -0
  12. package/dist/claude-marketplace/plugins/wildo/references/specification-family-map.md +88 -0
  13. package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +43 -0
  14. package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +70 -0
  15. package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +38 -0
  16. package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +23 -0
  17. package/dist/claude-marketplace/plugins/wildo/skills/next/SKILL.md +39 -0
  18. package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +39 -0
  19. package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +38 -0
  20. package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +38 -0
  21. package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +37 -0
  22. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  23. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  24. package/dist/esm/framework-knowledge.definitions.js +547 -17
  25. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  26. package/dist/esm/framework-knowledge.loader.d.ts +19 -0
  27. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  28. package/dist/esm/framework-knowledge.loader.js +47 -1
  29. package/dist/esm/framework-knowledge.loader.js.map +1 -1
  30. package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
  31. package/dist/esm/framework-knowledge.schemas.js.map +1 -1
  32. package/dist/esm/index.d.ts.map +1 -1
  33. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
  34. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  35. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -4
  36. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  37. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +135 -0
  38. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -0
  39. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +208 -0
  40. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -0
  41. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +218 -9
  42. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  43. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +374 -11
  44. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  45. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +6 -4
  46. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  47. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +22 -20
  48. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  49. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
  50. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  51. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -6
  52. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  53. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +57 -0
  54. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -0
  55. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +62 -0
  56. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -0
  57. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +132 -0
  58. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -0
  59. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +188 -0
  60. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -0
  61. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +74 -0
  62. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -0
  63. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +80 -0
  64. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -0
  65. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +5 -4
  66. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  67. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +18 -8
  68. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  69. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +67 -0
  70. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -0
  71. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +81 -0
  72. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -0
  73. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +31 -11
  74. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  75. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +132 -10
  76. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  77. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +68 -0
  78. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -0
  79. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +84 -0
  80. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -0
  81. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +69 -0
  82. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -0
  83. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +69 -0
  84. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -0
  85. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +2 -2
  86. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  87. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -2
  88. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  89. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +78 -0
  90. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -0
  91. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +93 -0
  92. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -0
  93. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +104 -0
  94. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -0
  95. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +184 -0
  96. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -0
  97. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +115 -0
  98. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -0
  99. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +152 -0
  100. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -0
  101. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts +59 -0
  102. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -0
  103. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js +72 -0
  104. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -0
  105. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +66 -0
  106. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -0
  107. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +115 -0
  108. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -0
  109. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +188 -8
  110. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  111. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +167 -9
  112. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  113. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +172 -2
  114. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  115. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +147 -2
  116. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  117. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +50 -0
  118. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -0
  119. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +54 -0
  120. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -0
  121. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts +248 -0
  122. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -0
  123. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js +248 -0
  124. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -0
  125. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +158 -5
  126. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  127. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +173 -5
  128. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  129. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +6 -5
  130. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  131. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +9 -8
  132. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  133. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +3 -2
  134. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  135. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +23 -4
  136. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  137. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +6 -4
  138. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  139. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +22 -13
  140. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  141. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +193 -28
  142. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  143. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +173 -34
  144. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  145. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +3 -2
  146. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  147. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +7 -3
  148. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  149. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +183 -6
  150. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  151. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +192 -6
  152. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  153. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +3 -2
  154. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  155. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +4 -3
  156. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  157. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +173 -0
  158. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -0
  159. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +264 -0
  160. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -0
  161. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +44 -0
  162. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -0
  163. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +51 -0
  164. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -0
  165. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts +45 -0
  166. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -0
  167. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js +46 -0
  168. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -0
  169. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -1
  170. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  171. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +3 -2
  172. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  173. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +2 -1
  174. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  175. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +7 -3
  176. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  177. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +2 -1
  178. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  179. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +3 -2
  180. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  181. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -2
  182. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  183. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +7 -4
  184. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  185. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +33 -5
  186. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  187. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +28 -4
  188. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  189. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +3 -3
  190. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  191. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +5 -3
  192. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  193. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +199 -0
  194. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -0
  195. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +227 -0
  196. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -0
  197. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +6 -4
  198. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  199. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +19 -5
  200. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  201. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +156 -5
  202. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  203. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +187 -5
  204. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  205. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +7 -6
  206. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  207. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +28 -19
  208. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  209. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  210. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
  211. package/dist/knowledge/manifest.json +9 -8
  212. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +75 -0
  213. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +40 -0
  214. package/dist/knowledge/playbooks/bottom_up.build/method.md +81 -0
  215. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +89 -0
  216. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -0
  217. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -0
  218. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +1234 -80
  219. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +53 -14
  220. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-protocol.json +1 -1
  221. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-treatment.json +1 -1
  222. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +743 -64
  223. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +10 -21
  224. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +34 -49
  225. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -21
  226. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +93 -0
  227. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +61 -0
  228. package/dist/knowledge/playbooks/bottom_up.conception/method.md +98 -0
  229. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +98 -0
  230. package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +109 -0
  231. package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +77 -0
  232. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +9 -11
  233. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +16 -16
  234. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +181 -0
  235. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +73 -0
  236. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +222 -145
  237. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +60 -24
  238. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +152 -0
  239. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +70 -0
  240. package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +87 -0
  241. package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +67 -0
  242. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +236 -0
  243. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +62 -0
  244. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +117 -0
  245. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +86 -0
  246. package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +71 -0
  247. package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +92 -0
  248. package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +83 -0
  249. package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +65 -0
  250. package/dist/knowledge/playbooks/cross_cutting.feature-development/method.md +42 -0
  251. package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +73 -0
  252. package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +46 -0
  253. package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +108 -0
  254. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -0
  255. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -0
  256. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +964 -15
  257. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +19 -12
  258. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-protocol.json +1 -0
  259. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-treatment.json +1 -0
  260. package/dist/knowledge/playbooks/refinement.document-facts/method.md +191 -21
  261. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +12 -18
  262. package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +48 -0
  263. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +66 -0
  264. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-protocol.json +1 -0
  265. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-treatment.json +1 -0
  266. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +349 -0
  267. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +54 -0
  268. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -0
  269. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -0
  270. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +24 -11
  271. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -18
  272. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +9 -18
  273. package/dist/knowledge/playbooks/top_down.capability-map/method.md +26 -52
  274. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +14 -18
  275. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
  276. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +99 -0
  277. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-protocol.json +1 -0
  278. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-treatment.json +1 -0
  279. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +211 -0
  280. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +66 -0
  281. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
  282. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +40 -0
  283. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -0
  284. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -0
  285. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +37 -14
  286. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +19 -69
  287. package/dist/knowledge/playbooks/top_down.compliance-research/method.md +78 -0
  288. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +41 -0
  289. package/dist/knowledge/playbooks/top_down.definition/method.md +106 -0
  290. package/dist/knowledge/playbooks/top_down.definition/playbook.json +120 -0
  291. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +56 -0
  292. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +46 -0
  293. package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +72 -0
  294. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +57 -0
  295. package/dist/knowledge/playbooks/top_down.market-analysis/method.md +51 -165
  296. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +25 -45
  297. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
  298. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +42 -0
  299. package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
  300. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +44 -0
  301. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-protocol.json +1 -1
  302. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-treatment.json +1 -1
  303. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +245 -0
  304. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +70 -0
  305. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  306. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  307. package/dist/knowledge/playbooks/top_down.phase-gate/method.md +36 -69
  308. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +12 -13
  309. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +28 -8
  310. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +12 -19
  311. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-protocol.json +1 -0
  312. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-treatment.json +1 -0
  313. package/dist/knowledge/playbooks/top_down.risk-register/method.md +46 -0
  314. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +57 -0
  315. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +25 -10
  316. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +16 -20
  317. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-protocol.json +1 -0
  318. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-treatment.json +1 -0
  319. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +24 -17
  320. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +12 -18
  321. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +12 -4
  322. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +23 -20
  323. package/dist/knowledge/references/acp.execution-profile.md +266 -0
  324. package/dist/knowledge/references/acp.host-configuration-inheritance.md +29 -0
  325. package/dist/knowledge/references/acp.permission-ceiling.md +105 -0
  326. package/dist/knowledge/references/acp.permission-escalation.md +37 -0
  327. package/dist/knowledge/references/application-documentation-chapters.config.md +152 -0
  328. package/dist/knowledge/references/application-documentation-plan.config.md +136 -0
  329. package/dist/knowledge/references/application-maturity.config.md +319 -0
  330. package/dist/knowledge/references/assertions.authored-metadata.config.md +1 -1
  331. package/dist/knowledge/references/assertions.specification.config.md +1 -1
  332. package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +212 -0
  333. package/dist/knowledge/references/backend.inbound-handlers.agents.md +45 -0
  334. package/dist/knowledge/references/backend.inbound-handlers.definition.md +218 -0
  335. package/dist/knowledge/references/brand.asset.config.md +8 -16
  336. package/dist/knowledge/references/brand.authored-metadata.config.md +2 -2
  337. package/dist/knowledge/references/brand.logo-direction.config.md +9 -7
  338. package/dist/knowledge/references/brand.snapshot.config.md +16 -2
  339. package/dist/knowledge/references/brand.snapshot.validation.md +0 -7
  340. package/dist/knowledge/references/build-plan.task-graph.config.md +649 -10
  341. package/dist/knowledge/references/business-model.authored-metadata.config.md +2 -2
  342. package/dist/knowledge/references/business-model.pricing-plan.config.md +1 -1
  343. package/dist/knowledge/references/business-model.snapshot.validation.md +15 -0
  344. package/dist/knowledge/references/capability-composition.config.md +174 -0
  345. package/dist/knowledge/references/cli.market.generate-command.md +18 -2
  346. package/dist/knowledge/references/cli.market.utils.md +1 -0
  347. package/dist/knowledge/references/companion.technical-doc.service.md +453 -98
  348. package/dist/knowledge/references/engine.client-bundle.allow-list.md +28 -22
  349. package/dist/knowledge/references/engine.client-bundle.external-connectors-public.discipline.md +20 -1
  350. package/dist/knowledge/references/engine.saas-technical-doc.config.md +8 -4
  351. package/dist/knowledge/references/engine.saas-technical-doc.provider-component.slot.md +83 -0
  352. package/dist/knowledge/references/engine.saas-website.config.md +22 -10
  353. package/dist/knowledge/references/example.authorization.service-provider-organization-wide-access.md +12 -0
  354. package/dist/knowledge/references/example.backend.addon-wiring.module.md +13 -12
  355. package/dist/knowledge/references/example.backend.custom-operation.create-postfix.md +7 -3
  356. package/dist/knowledge/references/example.config.app-shell.command-menu-items.md +7 -0
  357. package/dist/knowledge/references/example.config.app-shell.full.md +53 -7
  358. package/dist/knowledge/references/example.config.backend.billing-enable.md +14 -0
  359. package/dist/knowledge/references/example.config.backend.inbound-email.md +14 -0
  360. package/dist/knowledge/references/example.config.backend.required-floors.md +11 -0
  361. package/dist/knowledge/references/example.config.design-system.full.md +3 -0
  362. package/dist/knowledge/references/example.config.navigation.full.md +45 -2
  363. package/dist/knowledge/references/example.config.provider-usage-pricing.md +36 -0
  364. package/dist/knowledge/references/example.config.provider.backend-scope-billing.md +5 -3
  365. package/dist/knowledge/references/example.config.provider.backend-scope-inbound-email.md +16 -0
  366. package/dist/knowledge/references/example.engine.product-definitions.feature-and-profiles.md +19 -7
  367. package/dist/knowledge/references/example.features.connected-feature.declaration.md +66 -0
  368. package/dist/knowledge/references/example.features.connected-feature.surface.md +42 -0
  369. package/dist/knowledge/references/example.flows-actors.autonomous-agent.md +23 -0
  370. package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +36 -0
  371. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +30 -6
  372. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +7 -11
  373. package/dist/knowledge/references/example.guidance.bound-survey-flow.md +82 -0
  374. package/dist/knowledge/references/example.inbound.application-endpoint-handler.md +72 -0
  375. package/dist/knowledge/references/example.inbound.email-channel-handler.md +47 -0
  376. package/dist/knowledge/references/example.inbound.email-to-todo.md +150 -0
  377. package/dist/knowledge/references/example.infra.environment-config.local.md +104 -43
  378. package/dist/knowledge/references/example.layout-3d.own-layout.md +16 -0
  379. package/dist/knowledge/references/example.layout-3d.registration.md +15 -0
  380. package/dist/knowledge/references/example.milestones.module-definitions.md +73 -0
  381. package/dist/knowledge/references/example.minion.contained-tick.md +79 -0
  382. package/dist/knowledge/references/example.module.companion-exports.full.md +46 -16
  383. package/dist/knowledge/references/example.module.relationships.discriminator.md +2 -2
  384. package/dist/knowledge/references/example.organizations.serves-as-provider.md +12 -0
  385. package/dist/knowledge/references/example.provider.address-lookup.adapter.md +64 -0
  386. package/dist/knowledge/references/example.provider.backend-module-shape.md +34 -13
  387. package/dist/knowledge/references/example.provider.frontend-app.module.md +112 -0
  388. package/dist/knowledge/references/example.provider.frontend-facet.package-module.md +85 -0
  389. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +34 -13
  390. package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +25 -3
  391. package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +30 -0
  392. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +16 -0
  393. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +5 -0
  394. package/dist/knowledge/references/example.resource.retention-binding.closure-event.md +21 -0
  395. package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +1 -2
  396. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +112 -10
  397. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +90 -0
  398. package/dist/knowledge/references/example.resource.work-unit.declaration.md +13 -0
  399. package/dist/knowledge/references/example.spec.composite-view.workspace.md +0 -12
  400. package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +18 -0
  401. package/dist/knowledge/references/example.views.app-level.composite-views-config.md +1 -1
  402. package/dist/knowledge/references/example.views.chart-view.resource-owned.md +27 -0
  403. package/dist/knowledge/references/example.views.composite-view.workspace.md +4 -1
  404. package/dist/knowledge/references/example.website.page.manifest.md +30 -0
  405. package/dist/knowledge/references/example.worker.node-route.md +94 -0
  406. package/dist/knowledge/references/experience-plan.config.md +318 -0
  407. package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +152 -9
  408. package/dist/knowledge/references/external-connectors.backend.provider-augmentation.md +75 -0
  409. package/dist/knowledge/references/external-connectors.backend.provider-package-convention.md +36 -0
  410. package/dist/knowledge/references/external-connectors.frontend-provider-component-declaration.md +85 -0
  411. package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +52 -0
  412. package/dist/knowledge/references/external-connectors.models.connection-rate-budgets.md +113 -0
  413. package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +165 -0
  414. package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +133 -0
  415. package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +44 -0
  416. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +290 -0
  417. package/dist/knowledge/references/external-connectors.provider-component-load-state.md +45 -0
  418. package/dist/knowledge/references/external-connectors.provider-component-loader-contribution.md +32 -0
  419. package/dist/knowledge/references/external-connectors.provider-component-registry.md +190 -0
  420. package/dist/knowledge/references/external-connectors.techdoc.frontend-provider-module.md +91 -0
  421. package/dist/knowledge/references/external-connectors.website.frontend-provider-module.md +91 -0
  422. package/dist/knowledge/references/integration-plan.config.md +217 -0
  423. package/dist/knowledge/references/market.alternative.config.md +2 -2
  424. package/dist/knowledge/references/market.authored-metadata.config.md +12 -9
  425. package/dist/knowledge/references/market.buying-journey.config.md +1 -1
  426. package/dist/knowledge/references/market.category.config.md +1 -1
  427. package/dist/knowledge/references/market.channel.config.md +4 -4
  428. package/dist/knowledge/references/market.feature-benefit.config.md +2 -2
  429. package/dist/knowledge/references/market.gain.config.md +2 -2
  430. package/dist/knowledge/references/market.icp.config.md +3 -3
  431. package/dist/knowledge/references/market.job.config.md +2 -2
  432. package/dist/knowledge/references/market.message-template.config.md +3 -3
  433. package/dist/knowledge/references/market.objection.config.md +2 -2
  434. package/dist/knowledge/references/market.pain.config.md +2 -2
  435. package/dist/knowledge/references/market.persona.config.md +3 -3
  436. package/dist/knowledge/references/market.positioning.config.md +1 -1
  437. package/dist/knowledge/references/market.proof.config.md +2 -2
  438. package/dist/knowledge/references/market.references.weighted-edges.md +7 -0
  439. package/dist/knowledge/references/market.snapshot.validation.md +15 -0
  440. package/dist/knowledge/references/market.tone-of-voice.config.md +2 -2
  441. package/dist/knowledge/references/market.trigger.config.md +2 -2
  442. package/dist/knowledge/references/minions.tick-contract.md +83 -0
  443. package/dist/knowledge/references/placement-plan.config.md +375 -0
  444. package/dist/knowledge/references/platform.config.application-database.md +5 -2
  445. package/dist/knowledge/references/platform.config.backing-services.md +15 -36
  446. package/dist/knowledge/references/platform.config.environment.deployment.md +206 -14
  447. package/dist/knowledge/references/platform.config.infra-provider-resolution.md +170 -0
  448. package/dist/knowledge/references/platform.config.infrastructure-host.md +87 -0
  449. package/dist/knowledge/references/platform.config.saas.md +261 -9
  450. package/dist/knowledge/references/presets.3d.frame-style-overrides.md +134 -0
  451. package/dist/knowledge/references/presets.3d.layout-contract.md +213 -0
  452. package/dist/knowledge/references/presets.3d.register-layout.md +95 -0
  453. package/dist/knowledge/references/presets.models.labelling.sections.md +19 -0
  454. package/dist/knowledge/references/presets.models.shell-region.md +47 -0
  455. package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
  456. package/dist/knowledge/references/requirements.authored-metadata.config.md +2 -2
  457. package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -0
  458. package/dist/knowledge/references/requirements.snapshot.validation.md +15 -0
  459. package/dist/knowledge/references/roadmap.authored-metadata.config.md +2 -2
  460. package/dist/knowledge/references/roadmap.snapshot.validation.md +15 -7
  461. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +71 -0
  462. package/dist/knowledge/references/saas.backend.actor-execution-decision-record.md +41 -0
  463. package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +1 -2
  464. package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +1 -1
  465. package/dist/knowledge/references/saas.backend.auth.federated-identity-provider-private-networks.md +62 -0
  466. package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +87 -0
  467. package/dist/knowledge/references/saas.backend.billing.catalog-sync-result.md +37 -0
  468. package/dist/knowledge/references/saas.backend.billing.resolution-failure-reasons.md +24 -5
  469. package/dist/knowledge/references/saas.backend.compliance.governed-documents-pdf-template.md +370 -0
  470. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +194 -0
  471. package/dist/knowledge/references/saas.backend.domain-module.md +118 -16
  472. package/dist/knowledge/references/saas.backend.error-builder.user-guidance.md +82 -0
  473. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-declaration.md +66 -0
  474. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-schedule.md +31 -0
  475. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +206 -0
  476. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +22 -4
  477. package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +19 -4
  478. package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +84 -0
  479. package/dist/knowledge/references/saas.backend.health-readiness-contributor.md +73 -0
  480. package/dist/knowledge/references/saas.backend.pdf-template.collection-definition.md +73 -0
  481. package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +224 -0
  482. package/dist/knowledge/references/saas.backend.providers.operation-executor.md +51 -0
  483. package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +71 -0
  484. package/dist/knowledge/references/saas.backend.queue.worker-topology.md +39 -0
  485. package/dist/knowledge/references/saas.backend.submission-challenge.md +118 -0
  486. package/dist/knowledge/references/saas.backend.system-access-service.md +148 -41
  487. package/dist/knowledge/references/saas.backend.system-of-record-action-runner.md +73 -0
  488. package/dist/knowledge/references/saas.composition.scenario-apply.md +51 -0
  489. package/dist/knowledge/references/saas.config.content-security-policy.md +97 -0
  490. package/dist/knowledge/references/saas.config.providers.augmentations.md +61 -0
  491. package/dist/knowledge/references/saas.config.providers.packages.md +59 -0
  492. package/dist/knowledge/references/saas.config.providers.shared-connections.md +84 -0
  493. package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +91 -21
  494. package/dist/knowledge/references/saas.data-seeding.definition-input.md +4 -0
  495. package/dist/knowledge/references/saas.external-data.admin-endpoints.md +56 -2
  496. package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +38 -0
  497. package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +27 -27
  498. package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +65 -16
  499. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +43 -13
  500. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +44 -8
  501. package/dist/knowledge/references/saas.frontend.app-shell.building-blocks.md +250 -0
  502. package/dist/knowledge/references/saas.frontend.billing-context.md +131 -0
  503. package/dist/knowledge/references/saas.frontend.brand-identity.md +38 -0
  504. package/dist/knowledge/references/saas.frontend.celebration-overlay-contract.md +41 -0
  505. package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +92 -0
  506. package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +64 -0
  507. package/dist/knowledge/references/saas.frontend.consent-based-provider-activation.md +22 -0
  508. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
  509. package/dist/knowledge/references/saas.frontend.errors.user-facing-error-message.md +47 -0
  510. package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.per-action-retry-loop.md +7 -1
  511. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +3 -3
  512. package/dist/knowledge/references/saas.frontend.flows-actors-view.md +7 -4
  513. package/dist/knowledge/references/saas.frontend.form-field-address.lookup-slot.md +74 -0
  514. package/dist/knowledge/references/saas.frontend.form-fields.file-provider-constraints.md +30 -48
  515. package/dist/knowledge/references/saas.frontend.full-custom-view.definition.md +24 -0
  516. package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +60 -0
  517. package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +47 -0
  518. package/dist/knowledge/references/saas.frontend.notifications.publish-badge-count.md +60 -0
  519. package/dist/knowledge/references/saas.frontend.onboarding-view.md +84 -0
  520. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +80 -0
  521. package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
  522. package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +49 -0
  523. package/dist/knowledge/references/saas.frontend.related-resource-sections.md +8 -1
  524. package/dist/knowledge/references/saas.frontend.resource-header-title.md +28 -4
  525. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +136 -1
  526. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +422 -11
  527. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +25 -1
  528. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +259 -0
  529. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +220 -0
  530. package/dist/knowledge/references/saas.market.generation-agent.md +26 -10
  531. package/dist/knowledge/references/saas.models.agent-work-capture-settings.md +34 -0
  532. package/dist/knowledge/references/saas.models.agent-work-decision-surface.md +45 -0
  533. package/dist/knowledge/references/saas.models.agent-work-decision-vocabulary.md +107 -0
  534. package/dist/knowledge/references/saas.models.agent-work-output-review.md +36 -0
  535. package/dist/knowledge/references/saas.models.agent-work-override-rate.md +50 -0
  536. package/dist/knowledge/references/saas.models.agent-work-review-config.md +24 -0
  537. package/dist/knowledge/references/saas.models.analytics.value-moments.md +132 -0
  538. package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +97 -0
  539. package/dist/knowledge/references/saas.models.audit.trail-config.md +161 -0
  540. package/dist/knowledge/references/saas.models.auth.methods.md +513 -0
  541. package/dist/knowledge/references/saas.models.auth.service-provider-client-authentication.md +169 -0
  542. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +90 -0
  543. package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +130 -0
  544. package/dist/knowledge/references/saas.models.billing.referral-program.md +47 -0
  545. package/dist/knowledge/references/saas.models.config.organization-types.md +266 -0
  546. package/dist/knowledge/references/saas.models.config.registration.md +188 -0
  547. package/dist/knowledge/references/saas.models.config.tenant-teardown.md +98 -0
  548. package/dist/knowledge/references/saas.models.conversation-threads.md +242 -0
  549. package/dist/knowledge/references/saas.models.data-mode-read-list.md +173 -3
  550. package/dist/knowledge/references/saas.models.email.template-type.md +40 -0
  551. package/dist/knowledge/references/saas.models.engine-capabilities.md +97 -7
  552. package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +65 -0
  553. package/dist/knowledge/references/saas.models.evaluation-dataset-export.md +39 -0
  554. package/dist/knowledge/references/saas.models.evaluation-export-authorization.md +38 -0
  555. package/dist/knowledge/references/saas.models.external-data-pipeline.md +710 -10
  556. package/dist/knowledge/references/saas.models.features.definition-builders.md +162 -0
  557. package/dist/knowledge/references/saas.models.file-upload-grant.md +222 -0
  558. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +54 -5
  559. package/dist/knowledge/references/saas.models.flows-actors.autonomous-agents-vocabulary.md +98 -0
  560. package/dist/knowledge/references/saas.models.flows-actors.human-decision-vocabulary.md +52 -0
  561. package/dist/knowledge/references/saas.models.flows-actors.review-calendar.md +42 -0
  562. package/dist/knowledge/references/saas.models.flows-actors.review-deadline-vocabulary.md +84 -0
  563. package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +69 -0
  564. package/dist/knowledge/references/saas.models.frontend-provider-public-config-contract.md +72 -0
  565. package/dist/knowledge/references/saas.models.governed-document-acceptance-mode.md +116 -0
  566. package/dist/knowledge/references/saas.models.guidance-flow.md +160 -0
  567. package/dist/knowledge/references/saas.models.http-api-binding.md +884 -135
  568. package/dist/knowledge/references/saas.models.http-api-binding.rest-write-operations.md +81 -0
  569. package/dist/knowledge/references/saas.models.human-decision-review-marker.md +20 -0
  570. package/dist/knowledge/references/saas.models.inbound-channels.md +277 -0
  571. package/dist/knowledge/references/saas.models.inbound-email-domains.md +101 -0
  572. package/dist/knowledge/references/saas.models.inbound-email.md +111 -0
  573. package/dist/knowledge/references/saas.models.milestone-celebration.md +69 -0
  574. package/dist/knowledge/references/saas.models.milestone-definition.md +209 -0
  575. package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +28 -0
  576. package/dist/knowledge/references/saas.models.model-cost-summary.md +87 -0
  577. package/dist/knowledge/references/saas.models.navigation.layout.md +13 -9
  578. package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +133 -0
  579. package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +103 -0
  580. package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +152 -0
  581. package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +84 -0
  582. package/dist/knowledge/references/saas.models.notifications.targets.md +146 -0
  583. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +283 -0
  584. package/dist/knowledge/references/saas.models.onboarding-elements.md +375 -0
  585. package/dist/knowledge/references/saas.models.onboarding-trigger.md +52 -0
  586. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +59 -0
  587. package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +129 -0
  588. package/dist/knowledge/references/saas.models.organizations.service-provider-activity-feed.md +121 -0
  589. package/dist/knowledge/references/saas.models.organizations.service-provider-capability-grants.md +152 -0
  590. package/dist/knowledge/references/saas.models.organizations.service-provider-client-controls.md +49 -0
  591. package/dist/knowledge/references/saas.models.organizations.service-provider-relationships.md +567 -0
  592. package/dist/knowledge/references/saas.models.privacy.client-instance-id-scope.md +49 -0
  593. package/dist/knowledge/references/saas.models.privacy.legal-holds.md +172 -0
  594. package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +104 -0
  595. package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +106 -0
  596. package/dist/knowledge/references/saas.models.privacy.retention-binding.md +103 -0
  597. package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +120 -0
  598. package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +147 -0
  599. package/dist/knowledge/references/saas.models.privacy.statutory-retention-ground.md +50 -0
  600. package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +388 -0
  601. package/dist/knowledge/references/saas.models.progression-tracker-variant.md +76 -0
  602. package/dist/knowledge/references/saas.models.provider-address-lookup-contract.md +139 -0
  603. package/dist/knowledge/references/saas.models.provider-address-lookup-declaration.md +61 -0
  604. package/dist/knowledge/references/saas.models.provider-capabilities.md +42 -5
  605. package/dist/knowledge/references/saas.models.provider-credential-identity.md +67 -0
  606. package/dist/knowledge/references/saas.models.provider-usage-pricing-authority.md +139 -0
  607. package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +133 -0
  608. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +50 -0
  609. package/dist/knowledge/references/saas.models.providers.capability-surface.md +58 -0
  610. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +196 -0
  611. package/dist/knowledge/references/saas.models.providers.scope-reauthorization.md +57 -0
  612. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +156 -0
  613. package/dist/knowledge/references/saas.models.rate-limit-configuration.md +11 -1
  614. package/dist/knowledge/references/saas.models.relationship-handling-settings.md +23 -1
  615. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +244 -32
  616. package/dist/knowledge/references/saas.models.resource-config.forwarded-label.md +5 -4
  617. package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +69 -0
  618. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +15 -2
  619. package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +66 -0
  620. package/dist/knowledge/references/saas.models.resource-config.operation-base.md +24 -1
  621. package/dist/knowledge/references/saas.models.resource-config.operation-cron-job.md +59 -0
  622. package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +55 -0
  623. package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +5 -4
  624. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +158 -0
  625. package/dist/knowledge/references/saas.models.resource-config.operation-step-up.md +77 -0
  626. package/dist/knowledge/references/saas.models.resource-config.operation-submission-challenge.md +54 -0
  627. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
  628. package/dist/knowledge/references/saas.models.resource-config.operation-variant-for-key.md +6 -1
  629. package/dist/knowledge/references/saas.models.resource-config.queue-policy.md +49 -0
  630. package/dist/knowledge/references/saas.models.resource-config.required-features.md +84 -0
  631. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +16 -0
  632. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +22 -0
  633. package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +82 -0
  634. package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +111 -4
  635. package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +39 -0
  636. package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +48 -0
  637. package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +38 -0
  638. package/dist/knowledge/references/saas.models.resource-primary-scope.md +11 -2
  639. package/dist/knowledge/references/saas.models.scope-membership.md +3 -4
  640. package/dist/knowledge/references/saas.models.shared-saas-module.md +25 -0
  641. package/dist/knowledge/references/saas.models.system-of-record-actions.md +226 -0
  642. package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +461 -0
  643. package/dist/knowledge/references/saas.models.systems-of-record.facet-augmentation.md +63 -0
  644. package/dist/knowledge/references/saas.models.systems-of-record.md +870 -0
  645. package/dist/knowledge/references/saas.models.work-attribution-vocabulary.md +109 -0
  646. package/dist/knowledge/references/saas.models.work-unit-ref.md +28 -0
  647. package/dist/knowledge/references/saas.public-runtime.contract.md +268 -3
  648. package/dist/knowledge/references/saas.rag.retrieval-result.md +19 -8
  649. package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
  650. package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +15 -36
  651. package/dist/knowledge/references/saas.specifications.application-document-publication.contract.md +9 -5
  652. package/dist/knowledge/references/saas.specifications.application-document-publication.generation.md +63 -0
  653. package/dist/knowledge/references/saas.specifications.application-document-release-set.contract.md +74 -0
  654. package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +123 -0
  655. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +108 -7
  656. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +880 -66
  657. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +14 -13
  658. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.discriminated-union.md +36 -14
  659. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-aggregate-offer.md +4 -3
  660. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-product.md +4 -4
  661. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-software-application.md +71 -0
  662. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +217 -18
  663. package/dist/knowledge/references/saas.specifications.compliance.retention-enforcement-state.md +32 -0
  664. package/dist/knowledge/references/saas.specifications.composite-view-specification.md +10 -0
  665. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +376 -0
  666. package/dist/knowledge/references/saas.specifications.playbook-approval-and-failure-policies.md +96 -0
  667. package/dist/knowledge/references/saas.specifications.processor-register.md +410 -0
  668. package/dist/knowledge/references/saas.specifications.recipient-disclosures.md +71 -0
  669. package/dist/knowledge/references/saas.specifications.recipient-population.md +549 -0
  670. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +120 -45
  671. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +35 -1
  672. package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +17 -0
  673. package/dist/knowledge/references/saas.specifications.resource-spec-frontend-prose.md +16 -0
  674. package/dist/knowledge/references/saas.specifications.subject-data-recipients.md +98 -0
  675. package/dist/knowledge/references/saas.website.astro.bridge.md +92 -7
  676. package/dist/knowledge/references/saas.website.astro.head-renderer.md +33 -13
  677. package/dist/knowledge/references/saas.website.astro.label-loader.md +10 -4
  678. package/dist/knowledge/references/saas.website.astro.robots-renderer.md +29 -16
  679. package/dist/knowledge/references/saas.website.astro.site-context.md +5 -2
  680. package/dist/knowledge/references/saas.website.blog.bridge.md +34 -1
  681. package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +61 -0
  682. package/dist/knowledge/references/saas.website.config.site-context-loader.md +154 -0
  683. package/dist/knowledge/references/saas.website.consent.banner.md +218 -0
  684. package/dist/knowledge/references/saas.website.consent.context.md +162 -0
  685. package/dist/knowledge/references/saas.website.consent.gate.md +38 -0
  686. package/dist/knowledge/references/saas.website.design-tokens.colors.md +7 -4
  687. package/dist/knowledge/references/saas.website.design-tokens.radius.md +1 -1
  688. package/dist/knowledge/references/saas.website.factories.define-section.md +3 -3
  689. package/dist/knowledge/references/saas.website.page-layout.component.md +70 -1
  690. package/dist/knowledge/references/saas.website.page.context.md +4 -3
  691. package/dist/knowledge/references/saas.website.pricing-offer-structured-data.md +140 -0
  692. package/dist/knowledge/references/saas.website.provider-component.slot.md +99 -0
  693. package/dist/knowledge/references/saas.website.root-config.schema.md +6 -6
  694. package/dist/knowledge/references/saas.website.runtime.context.md +66 -11
  695. package/dist/knowledge/references/saas.website.section.context.md +3 -2
  696. package/dist/knowledge/references/saas.website.sections.category-enum.md +19 -20
  697. package/dist/knowledge/references/saas.website.sections.definition-schema.md +14 -7
  698. package/dist/knowledge/references/saas.website.seo.robots-config.md +4 -3
  699. package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +7 -5
  700. package/dist/knowledge/references/saas.website.submission-challenge.md +77 -0
  701. package/dist/knowledge/references/saas.website.use-pricing-catalog.hook.md +36 -0
  702. package/dist/knowledge/references/saas.website.use-runtime.hook.md +3 -2
  703. package/dist/knowledge/references/vision.authored-metadata.config.md +2 -2
  704. package/dist/knowledge/references/website-plan.config.md +238 -0
  705. package/dist/knowledge/references/workers.node.worker-init-contract.md +57 -0
  706. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +43 -2
  707. package/dist/knowledge/references/zod.decorators.data-categories.md +197 -0
  708. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +53 -5
  709. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +75 -1
  710. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +36 -2
  711. package/dist/knowledge/references/zod.decorators.field-spec-params.md +32 -5
  712. package/dist/knowledge/references/zod.decorators.file-nature-constraints.md +86 -0
  713. package/dist/knowledge/references/zod.decorators.file-readiness-metadata.md +67 -0
  714. package/dist/knowledge/references/zod.decorators.file-schema.md +95 -18
  715. package/dist/knowledge/references/zod.decorators.file-vocabularies.md +87 -0
  716. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +148 -6
  717. package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
  718. package/dist/knowledge/references/zod.decorators.rag-source.md +6 -2
  719. package/dist/knowledge/references/zod.decorators.schema-metadata.md +24 -0
  720. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +35 -0
  721. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +50 -12
  722. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +35 -12
  723. package/dist/knowledge/references/zod.factories.address.md +118 -0
  724. package/dist/knowledge/references/zod.factories.code.md +4 -2
  725. package/dist/knowledge/references/zod.factories.duration.md +6 -4
  726. package/dist/knowledge/references/zod.factories.money.md +5 -3
  727. package/dist/knowledge/references/zod.factories.phone.md +14 -1
  728. package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
  729. package/dist/knowledge/registries/framework-topics.json +2602 -214
  730. package/dist/knowledge/registries/playbooks.json +468 -92
  731. package/dist/knowledge/registries/source-tags.json +6171 -1996
  732. package/dist/knowledge/rules/database-migration-obligation.md +110 -0
  733. package/dist/knowledge/rules/live-context-door.md +137 -0
  734. package/dist/knowledge/rules/resource-schema-awareness.md +75 -0
  735. package/dist/knowledge/skills/INDEX.md +67 -29
  736. package/dist/knowledge/skills/agent-work-review/SKILL.md +141 -0
  737. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-capture-settings-api.md +38 -0
  738. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-output-review-api.md +40 -0
  739. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-override-rate-api.md +54 -0
  740. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-config-api.md +28 -0
  741. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +108 -0
  742. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-vocabulary-api.md +111 -0
  743. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-dataset-export-api.md +43 -0
  744. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-export-authorization-api.md +42 -0
  745. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +111 -37
  746. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +167 -0
  747. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +6 -3
  748. package/dist/knowledge/skills/application-database-migrations/SKILL.md +11 -3
  749. package/dist/knowledge/skills/application-database-migrations/references/framework-application-database-api.md +5 -2
  750. package/dist/knowledge/skills/application-database-migrations/references/migration-refusals.md +32 -0
  751. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +95 -3
  752. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +59 -0
  753. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +32 -19
  754. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +119 -17
  755. package/dist/knowledge/skills/backend-addon-wiring/references/framework-readiness-contributor-api.md +135 -0
  756. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +96 -20
  757. package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +137 -0
  758. package/dist/knowledge/skills/backend-custom-operation/references/framework-error-user-guidance-api.md +112 -0
  759. package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +72 -1
  760. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +214 -0
  761. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +39 -1
  762. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-asset-api.md +8 -16
  763. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +25 -9
  764. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +162 -8
  765. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +80 -17
  766. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +518 -132
  767. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +32 -10
  768. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +103 -58
  769. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-publication-contract.md +19 -13
  770. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +162 -26
  771. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +734 -23
  772. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +436 -0
  773. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +221 -0
  774. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +209 -0
  775. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-population.md +577 -0
  776. package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +549 -0
  777. package/dist/knowledge/skills/config-app-shell/SKILL.md +95 -11
  778. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +87 -21
  779. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-building-blocks-api.md +276 -0
  780. package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +70 -0
  781. package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
  782. package/dist/knowledge/skills/config-app-shell/references/framework-shell-region-markers-api.md +66 -0
  783. package/dist/knowledge/skills/config-design-system/SKILL.md +44 -3
  784. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
  785. package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
  786. package/dist/knowledge/skills/config-design-system/references/surface-policy-authoring.md +19 -10
  787. package/dist/knowledge/skills/config-navigation/SKILL.md +200 -19
  788. package/dist/knowledge/skills/config-navigation/references/choosing-a-navigation-shape.md +314 -0
  789. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
  790. package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +13 -9
  791. package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +78 -0
  792. package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +245 -0
  793. package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +174 -0
  794. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +253 -0
  795. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +141 -0
  796. package/dist/knowledge/skills/config-navigation/references/navigation-zones.md +1 -1
  797. package/dist/knowledge/skills/config-saas/SKILL.md +88 -9
  798. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +206 -0
  799. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +189 -0
  800. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +493 -0
  801. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +157 -0
  802. package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +292 -0
  803. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +161 -0
  804. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +139 -12
  805. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +1024 -0
  806. package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +172 -0
  807. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +261 -9
  808. package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +9 -0
  809. package/dist/knowledge/skills/config-saas-backend/SKILL.md +66 -3
  810. package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +151 -0
  811. package/dist/knowledge/skills/config-saas-backend/references/framework-auth-methods-api.md +579 -0
  812. package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +8 -2
  813. package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +96 -0
  814. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +397 -0
  815. package/dist/knowledge/skills/config-saas-backend/references/framework-registration-config-api.md +221 -0
  816. package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +143 -0
  817. package/dist/knowledge/skills/config-saas-backend/references/managed-startup-configuration.md +46 -0
  818. package/dist/knowledge/skills/configure-billing/SKILL.md +91 -46
  819. package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +62 -17
  820. package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +55 -0
  821. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +39 -17
  822. package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +30 -28
  823. package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +192 -0
  824. package/dist/knowledge/skills/configure-billing/references/framework-billing-resolution-failure-api.md +44 -11
  825. package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +259 -0
  826. package/dist/knowledge/skills/configure-billing/references/framework-referral-program.md +110 -0
  827. package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +91 -0
  828. package/dist/knowledge/skills/configure-coding-agent/SKILL.md +289 -0
  829. package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +192 -0
  830. package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +504 -0
  831. package/dist/knowledge/skills/email-add-template/SKILL.md +100 -91
  832. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +15 -7
  833. package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +123 -0
  834. package/dist/knowledge/skills/email-definition-wiring/SKILL.md +1 -0
  835. package/dist/knowledge/skills/email-labels-authoring/SKILL.md +2 -1
  836. package/dist/knowledge/skills/email-template-authoring/SKILL.md +1 -0
  837. package/dist/knowledge/skills/engine-component-registration/SKILL.md +20 -12
  838. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +60 -31
  839. package/dist/knowledge/skills/engine-product-definitions/references/connected-feature-workflow.md +130 -0
  840. package/dist/knowledge/skills/engine-product-definitions/references/framework-engine-product-definitions-api.md +25 -0
  841. package/dist/knowledge/skills/engine-product-definitions/references/framework-feature-builders-api.md +215 -0
  842. package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +78 -0
  843. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +60 -27
  844. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +121 -0
  845. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
  846. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +180 -0
  847. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +56 -0
  848. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-autonomous-agent-api.md +208 -0
  849. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-inbound-agents-api.md +51 -0
  850. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/tool-posture.md +27 -0
  851. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +41 -12
  852. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +31 -7
  853. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +148 -0
  854. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +287 -0
  855. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +248 -9
  856. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +127 -22
  857. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +236 -0
  858. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +8 -11
  859. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +54 -5
  860. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +75 -21
  861. package/dist/knowledge/skills/frontend-cdn-publish/SKILL.md +1 -0
  862. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +259 -0
  863. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +480 -0
  864. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +3988 -0
  865. package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +212 -0
  866. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +165 -0
  867. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-elements-api.md +381 -0
  868. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-trigger-api.md +57 -0
  869. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-view-api.md +89 -0
  870. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +14 -1
  871. package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +19 -0
  872. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +11 -9
  873. package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +19 -0
  874. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +11 -2
  875. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +19 -0
  876. package/dist/knowledge/skills/i18n-translation-rerun/references/translation-workflow.md +5 -0
  877. package/dist/knowledge/skills/inbound-channels/SKILL.md +301 -0
  878. package/dist/knowledge/skills/inbound-channels/references/email-channel.md +133 -0
  879. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +800 -0
  880. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-email-api.md +222 -0
  881. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +231 -0
  882. package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +135 -0
  883. package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +297 -0
  884. package/dist/knowledge/skills/infra-environment-config/SKILL.md +387 -81
  885. package/dist/knowledge/skills/infra-environment-config/references/framework-application-database-api.md +5 -2
  886. package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +198 -36
  887. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +206 -14
  888. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +95 -0
  889. package/dist/knowledge/skills/layout-3d-adoption/SKILL.md +176 -0
  890. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +141 -0
  891. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-contract-api.md +223 -0
  892. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-registration-api.md +103 -0
  893. package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-building-blocks-api.md +256 -0
  894. package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-region-marker-api.md +52 -0
  895. package/dist/knowledge/skills/layout-3d-adoption/references/layouts-and-transitions.md +29 -0
  896. package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +25 -0
  897. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +184 -46
  898. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +119 -0
  899. package/dist/knowledge/skills/local-environment-bootstrap/references/initialization-recovery-recipe.md +7 -4
  900. package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +2 -1
  901. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +289 -37
  902. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +3 -2
  903. package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +2 -2
  904. package/dist/knowledge/skills/market-alternatives/SKILL.md +4 -3
  905. package/dist/knowledge/skills/market-authoring-overview/SKILL.md +1 -0
  906. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +7 -0
  907. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +12 -9
  908. package/dist/knowledge/skills/market-category/SKILL.md +2 -1
  909. package/dist/knowledge/skills/market-channels/SKILL.md +5 -4
  910. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +233 -18
  911. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +232 -18
  912. package/dist/knowledge/skills/market-generation-cli/SKILL.md +77 -15
  913. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +50 -12
  914. package/dist/knowledge/skills/market-icp/SKILL.md +4 -3
  915. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +7 -6
  916. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +4 -3
  917. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +18 -3
  918. package/dist/knowledge/skills/market-persona/SKILL.md +4 -3
  919. package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +2 -1
  920. package/dist/knowledge/skills/market-positioning-authoring/references/framework-positioning-api.md +1 -1
  921. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +5 -4
  922. package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +1 -0
  923. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +16 -0
  924. package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +15 -0
  925. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +3 -2
  926. package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +4 -3
  927. package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +199 -0
  928. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-celebration-overlay-contract.md +51 -0
  929. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-celebration-api.md +79 -0
  930. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-definition-api.md +220 -0
  931. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-progression-tracker-api.md +86 -0
  932. package/dist/knowledge/skills/minion-authoring/SKILL.md +144 -0
  933. package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +84 -0
  934. package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +91 -0
  935. package/dist/knowledge/skills/model-cost-attribution/SKILL.md +143 -0
  936. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +211 -0
  937. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-summary-api.md +95 -0
  938. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-attribution-api.md +117 -0
  939. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +677 -0
  940. package/dist/knowledge/skills/module-companion-exports/SKILL.md +55 -19
  941. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +217 -18
  942. package/dist/knowledge/skills/module-registration/SKILL.md +50 -32
  943. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +143 -16
  944. package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +227 -0
  945. package/dist/knowledge/skills/module-registration/references/registry-files.md +14 -5
  946. package/dist/knowledge/skills/module-relationships/SKILL.md +65 -2
  947. package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +26 -5
  948. package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +34 -2
  949. package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-collection-template-api.md +447 -0
  950. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +207 -0
  951. package/dist/knowledge/skills/provider-address-lookup/references/framework-address-field-lookup-slot-api.md +82 -0
  952. package/dist/knowledge/skills/provider-address-lookup/references/framework-address-lookup-contract-api.md +214 -0
  953. package/dist/knowledge/skills/provider-address-lookup/references/framework-browser-operation-policy-api.md +143 -0
  954. package/dist/knowledge/skills/provider-address-lookup/references/google-places-setup.md +73 -0
  955. package/dist/knowledge/skills/provider-backend-package/SKILL.md +518 -0
  956. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +80 -0
  957. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-augmentation-api.md +227 -0
  958. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-credential-identity-api.md +101 -0
  959. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +245 -0
  960. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +88 -0
  961. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +55 -0
  962. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-allow-list-api.md +111 -0
  963. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-convention-api.md +48 -0
  964. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +309 -0
  965. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +165 -29
  966. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-file-provider-constraints-api.md +99 -47
  967. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +399 -0
  968. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +270 -9
  969. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-public-config-api.md +115 -0
  970. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-provider-component-registry-api.md +386 -0
  971. package/dist/knowledge/skills/provider-frontend-module/SKILL.md +258 -0
  972. package/dist/knowledge/skills/provider-frontend-module/references/framework-frontend-facet-contracts-api.md +463 -0
  973. package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +61 -0
  974. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +247 -0
  975. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +50 -0
  976. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +141 -0
  977. package/dist/knowledge/skills/provider-operation-calls/references/framework-connection-rate-budgets-api.md +176 -0
  978. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +86 -0
  979. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +73 -0
  980. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-scope-reauthorization-api.md +127 -0
  981. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +300 -0
  982. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +70 -11
  983. package/dist/knowledge/skills/rate-limit-authoring/references/fixed-window-and-environment-multiplier.md +27 -0
  984. package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +19 -6
  985. package/dist/knowledge/skills/resource-add-field/SKILL.md +13 -5
  986. package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +1 -2
  987. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +472 -23
  988. package/dist/knowledge/skills/resource-add-module/SKILL.md +117 -265
  989. package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +134 -0
  990. package/dist/knowledge/skills/resource-add-module/references/framework-new-module-wiring-api.md +25 -0
  991. package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +12 -12
  992. package/dist/knowledge/skills/resource-add-resource/SKILL.md +29 -3
  993. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +244 -32
  994. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +26 -0
  995. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +101 -0
  996. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +145 -0
  997. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +101 -0
  998. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +133 -0
  999. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +141 -0
  1000. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-step-up-api.md +126 -0
  1001. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +953 -0
  1002. package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +122 -0
  1003. package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +125 -0
  1004. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +97 -2
  1005. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +595 -45
  1006. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +197 -0
  1007. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +259 -45
  1008. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +486 -0
  1009. package/dist/knowledge/skills/resource-custom-view/SKILL.md +6 -0
  1010. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +422 -11
  1011. package/dist/knowledge/skills/resource-custom-view/references/framework-user-facing-error-message-api.md +50 -0
  1012. package/dist/knowledge/skills/resource-external-data/SKILL.md +1242 -31
  1013. package/dist/knowledge/skills/resource-external-data/references/declared-expressions.md +144 -0
  1014. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +68 -0
  1015. package/dist/knowledge/skills/resource-external-data/references/facet-augmentations.md +154 -0
  1016. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +739 -17
  1017. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +987 -140
  1018. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +175 -10
  1019. package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +152 -0
  1020. package/dist/knowledge/skills/resource-external-data/references/odata-v2-sources.md +60 -0
  1021. package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +179 -0
  1022. package/dist/knowledge/skills/resource-external-data/references/pipeline-destination-schema.md +1 -1
  1023. package/dist/knowledge/skills/resource-external-data/references/provenance-cue.md +63 -0
  1024. package/dist/knowledge/skills/resource-external-data/references/rate-budgets-and-pacing.md +122 -0
  1025. package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +745 -0
  1026. package/dist/knowledge/skills/resource-external-data/references/remote-references.md +85 -0
  1027. package/dist/knowledge/skills/resource-external-data/references/rest-keyset-sources.md +85 -0
  1028. package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +442 -0
  1029. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +70 -26
  1030. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +246 -0
  1031. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +7 -6
  1032. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +5 -3
  1033. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +44 -48
  1034. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +108 -14
  1035. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +47 -15
  1036. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +6 -2
  1037. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +186 -0
  1038. package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +200 -0
  1039. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +111 -0
  1040. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +173 -0
  1041. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +155 -0
  1042. package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +139 -0
  1043. package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +55 -0
  1044. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +34 -4
  1045. package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +1 -2
  1046. package/dist/knowledge/skills/resource-schema-authoring/examples/basic-resource-schema.example.md +2 -1
  1047. package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +17 -0
  1048. package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +3 -1
  1049. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +77 -5
  1050. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +210 -0
  1051. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +245 -0
  1052. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +35 -0
  1053. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +50 -12
  1054. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +497 -28
  1055. package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +67 -0
  1056. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +78 -14
  1057. package/dist/knowledge/skills/resource-schema-authoring/references/polymorphic-per-scope-resources.md +28 -5
  1058. package/dist/knowledge/skills/resource-schema-authoring/references/schema-variants-and-discriminators.md +25 -0
  1059. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -1
  1060. package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +34 -0
  1061. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +300 -23
  1062. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +75 -1
  1063. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +36 -2
  1064. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +447 -12
  1065. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +148 -6
  1066. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
  1067. package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +57 -1
  1068. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +216 -6
  1069. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +266 -0
  1070. package/dist/knowledge/skills/seeding-authoring/SKILL.md +10 -1
  1071. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +4 -0
  1072. package/dist/knowledge/skills/seeding-operations/SKILL.md +34 -29
  1073. package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +13 -5
  1074. package/dist/knowledge/skills/seeding-operations/references/data-seeding-cron-scheduler.md +67 -74
  1075. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +97 -24
  1076. package/dist/knowledge/skills/service-provider-relationships/SKILL.md +455 -0
  1077. package/dist/knowledge/skills/service-provider-relationships/references/framework-organization-types-api.md +270 -0
  1078. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-activity-feed-api.md +129 -0
  1079. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-capability-grants-api.md +161 -0
  1080. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-client-authentication-api.md +224 -0
  1081. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-relationships-api.md +576 -0
  1082. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +206 -0
  1083. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +266 -0
  1084. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +229 -0
  1085. package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +43 -37
  1086. package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +15 -14
  1087. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +52 -19
  1088. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +217 -18
  1089. package/dist/knowledge/skills/spec-component-update/SKILL.md +31 -11
  1090. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +20 -21
  1091. package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +10 -0
  1092. package/dist/knowledge/skills/spec-family-update/SKILL.md +1 -0
  1093. package/dist/knowledge/skills/spec-feature-update/SKILL.md +48 -9
  1094. package/dist/knowledge/skills/spec-resource-update/SKILL.md +16 -0
  1095. package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +32 -5
  1096. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +188 -46
  1097. package/dist/knowledge/skills/spec-update-after-change/SKILL.md +1 -0
  1098. package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +17 -0
  1099. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +6 -1
  1100. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +14 -2
  1101. package/dist/knowledge/skills/views-add-custom-view/references/framework-view-scope-and-full-custom-api.md +24 -0
  1102. package/dist/knowledge/skills/views-app-level/SKILL.md +3 -1
  1103. package/dist/knowledge/skills/views-app-level/references/framework-view-scope-and-full-custom-api.md +24 -0
  1104. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +44 -1
  1105. package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +102 -0
  1106. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +6 -1
  1107. package/dist/knowledge/skills/views-composite-authoring/references/composite-embedding-checklist.md +3 -2
  1108. package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +64 -0
  1109. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +4 -0
  1110. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +3 -3
  1111. package/dist/knowledge/skills/views-execution-authoring/references/framework-user-facing-error-message-api.md +50 -0
  1112. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +72 -13
  1113. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +3 -2
  1114. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +34 -1
  1115. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +44 -28
  1116. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +48 -23
  1117. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +882 -211
  1118. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +4 -3
  1119. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +117 -13
  1120. package/dist/knowledge/skills/website-inbound-contact-forms/references/framework-submission-challenge-api.md +275 -0
  1121. package/dist/knowledge/skills/website-label-pack/SKILL.md +13 -5
  1122. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +71 -1
  1123. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +22 -2
  1124. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +21 -6
  1125. package/dist/knowledge/skills/website-page-authoring/SKILL.md +206 -35
  1126. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +164 -0
  1127. package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +126 -0
  1128. package/dist/knowledge/skills/website-page-variants/SKILL.md +1 -0
  1129. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +1 -0
  1130. package/dist/knowledge/skills/website-section-contact/SKILL.md +159 -180
  1131. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +38 -31
  1132. package/dist/knowledge/skills/website-section-cta/SKILL.md +51 -42
  1133. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +38 -31
  1134. package/dist/knowledge/skills/website-section-faq/SKILL.md +118 -83
  1135. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +38 -31
  1136. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +46 -38
  1137. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +38 -31
  1138. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +52 -42
  1139. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +38 -31
  1140. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +50 -40
  1141. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +38 -31
  1142. package/dist/knowledge/skills/website-section-hero/SKILL.md +101 -69
  1143. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +38 -31
  1144. package/dist/knowledge/skills/website-section-pricing/SKILL.md +236 -220
  1145. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +38 -31
  1146. package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +248 -0
  1147. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +64 -54
  1148. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +38 -31
  1149. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +8 -3
  1150. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +64 -34
  1151. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +44 -26
  1152. package/dist/knowledge/skills/worker-authoring/SKILL.md +165 -0
  1153. package/dist/knowledge/skills/worker-authoring/examples/worker-route.example.md +98 -0
  1154. package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +65 -0
  1155. package/dist/knowledge/topic-index.json +12659 -4142
  1156. package/dist/tsconfig.build.tsbuildinfo +1 -1
  1157. package/dist/tsconfig.tsbuildinfo +1 -1
  1158. package/package.json +4 -4
  1159. package/dist/knowledge/references/example.provider.contribution.backend-billing.md +0 -12
  1160. package/dist/knowledge/skills/configure-billing/references/example-provider-contribution-and-backend-config.md +0 -48
  1161. package/dist/knowledge/skills/journey-approve/SKILL.md +0 -43
  1162. package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +0 -42
  1163. package/dist/knowledge/skills/journey-next/SKILL.md +0 -42
  1164. package/dist/knowledge/skills/journey-report/SKILL.md +0 -43
  1165. package/dist/knowledge/skills/journey-run/SKILL.md +0 -55
  1166. package/dist/knowledge/skills/journey-status/SKILL.md +0 -50
  1167. /package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/structured-artifact-action.json +0 -0
@@ -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\n**A held draft marked ALREADY DRAFTED, and WRONG comes before everything below.** The brief marks a held\ndraft that cites facts this application no longer declares, and names them. Nothing else corrects it: the\nlanding checks only the document a run writes, so a draft written before the facts were regenerated keeps\nits dead citations until a run redrafts that document. Redraft it against the facts that exist, and cite\nnone of the named ones.\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,15 @@ 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.
@@ -1,14 +1,9 @@
1
1
  {
2
2
  "ref": "top_down.brand-identity",
3
- "version": "0.1.0",
3
+ "version": "0.1.2",
4
4
  "phase": "top_down",
5
5
  "intent": "Brand-identity elicitation: draw the product's VISUAL identity out of the creator — the brand name, the logo creative direction (mark type, motifs, symbolism, imagery don'ts, background), and the visual tone (style keywords, mood, color story) — and capture it as a single validated BrandSnapshot (the `brand-brief` artifact family). The visual counterpart to the vision (intent) and market (verbal voice) briefs: it derives symbolism from the VisionSnapshot's idea/mission and, when a MarketSnapshot exists, translates its verbal `tonesOfVoice` into a visual register. The emitted brand-brief is the INPUT the companion logo step generates the master logo + derived assets from, and via `BrandSnapshot.resolvedAssets` the single source of truth every logo/favicon/brand-image consumer resolves against. Progressive: may persist a partially-directed brand (logoDirection/visualTone optional) and resume. v1 scaffold methodology — iterate the interview.",
6
- "functionalTopics": [],
7
6
  "preconditions": [
8
- {
9
- "kind": "phase_is",
10
- "phase": "top_down"
11
- },
12
7
  {
13
8
  "kind": "artifact_exists",
14
9
  "selector": {
@@ -23,20 +18,25 @@
23
18
  {
24
19
  "family": "market-snapshot",
25
20
  "intent": "voice"
21
+ },
22
+ {
23
+ "family": "brand-brief"
26
24
  }
27
25
  ],
28
26
  "outputs": [
29
27
  {
30
28
  "family": "brand-brief",
31
29
  "schemaRef": "saas-specifications:BrandSnapshot",
32
- "placement": ".wildo-saas/journey/<journeyId>/brand-brief/",
33
30
  "description": "The visual-identity artifact — one BrandSnapshot per product (name + logo direction + visual tone; resolvedAssets left empty for the companion logo step to populate). Read by the companion logo generation step (which produces the master + derived assets) and, via resolvedAssets, by every downstream logo/favicon/brand-image consumer. Validated by validateBrandSnapshot."
34
31
  }
35
32
  ],
33
+ "stepOutputs": [],
36
34
  "method": {
37
- "guidance": "# Brand Identity — Interview Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **brand-identity interviewer**. Your job is to draw the product's\nVISUAL identity out of the creator and capture it as a single typed\n**`BrandSnapshot`** — the `brand-brief` artifact. This is the visual\ncounterpart to the vision brief (which captured *intent*) and the market brief\n(which captured the *verbal* voice): here you capture what the product should\n**look like** and, specifically, the brief a logo is generated from.\n\nThe brand-brief you emit is not the logo itself — it is the *direction*. The\ncompanion logo step reads it to generate the master logo and every derived\nasset (favicon, apple-touch, maskable, OG, email, monochrome, dark/light), and\nthose become the single source of truth every surface resolves against. So an\nhonest, well-framed brief is the whole task. You do **not** generate pixels,\nset design-system color tokens, or restate the verbal brand voice — each is a\ndistinct concern with its own home.\n\n## Where the brief comes from\n\nYou do not invent a brand from nothing. Ground it in what the journey already\nknows:\n\n- **The vision brief is your source of meaning.** Read the `VisionSnapshot` and\n derive the mark's **symbolism** from the product's idea and mission — the\n mark should evoke what the product is *for*, not a decorative motif you liked.\n- **The market brief sharpens the register, when present.** If a\n `MarketSnapshot` exists, translate its verbal `tonesOfVoice` (the Nielsen\n Norman 4-axis voice) into a **visual** tone: a serious / formal voice reads as\n restrained geometry and a muted palette; a funny / casual voice reads as\n rounder forms and a warmer accent. The market brief is an *input*, not a\n precondition — if there is no market snapshot yet, derive the visual tone from\n the vision alone and note it as provisional.\n\n## The elicitation posture\n\n- **Interview, do not fill a form.** The typed questions on this playbook\n (`method.elicitation`) are your backbone, not your ceiling. Ask them in a\n natural order, reflect each answer back in one line, and let the creator\n correct you before moving on.\n- **Progressive is fine.** A `BrandSnapshot` requires only the **name**; the\n logo direction and visual tone are OPTIONAL and elicited progressively. If the\n creator can only name the brand today, capture it, note what is still open,\n and stop — the snapshot persists as partially-directed and this playbook can\n resume. Never invent a mark direction the creator did not give you.\n- **One product, one brand.** The snapshot is a single aggregate — one name,\n one logo direction, one visual tone. If the creator describes two brands,\n stop and ask which one this journey is for.\n\n## What you elicit — one aggregate\n\n- **Name** (REQUIRED). The anchor lexical identity: the exact, case-sensitive\n `brandName` the logo renders and every surface prints, plus an optional\n `tagline` to lock up with combination marks / OG imagery. Nothing visual\n here — the mark and the palette come next. A brand without a name has nothing\n for a mark to render; do not proceed until you have it.\n- **Logo direction** (optional, WARNed when absent). The creative brief the\n image model turns into the master logo:\n - `markType` — pick the archetype. **Default to `COMBINATION_MARK`** (symbol +\n wordmark) — it is the only archetype that natively yields BOTH a header\n lockup and a square symbol for favicons/app-icons. Reach for `WORDMARK`\n (text-only) only when the brand is genuinely wordmark-only; warn the creator\n that a wordmark cannot produce a clean square app icon.\n - `motifs` — concrete visual elements to include (short noun phrases).\n - `symbolism` — the meaning the mark should evoke, **derived from the vision\n mission/idea**.\n - `avoid` — imagery don'ts (the negative-prompt guardrails that keep output\n usable).\n - `backgroundTreatment` — keep `TRANSPARENT_ISOLATED` (the default and the\n only treatment that rasterizes losslessly into every derived asset). A\n solid field or contextual scene is an explicit opt-in the pipeline must\n compensate for — the validator WARNs on it.\n- **Visual tone** (optional, WARNed when absent). The aesthetic register — the\n VISUAL counterpart to the market voice: 3–7 concrete `styleKeywords`\n (\"geometric\", \"minimal\", \"warm\"), a one-line `mood`, a prose `colorIntent`\n (the color STORY, not hex values), and optional hex `colorSeeds` pinned only\n when the brand has already committed to anchors that must agree with the\n design system.\n\n## What you emit\n\nA single `BrandSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told otherwise).\n- `name` — the required anchor (`brandName`, optional `tagline`).\n- `logoDirection` / `visualTone` — the optional singletons, present only if elicited.\n- `resolvedAssets` — **leave empty.** This is the companion logo step's output,\n not something you author. Hand-authoring it fabricates asset references the\n pipeline will overwrite or the validator will flag.\n\nAuthor every entity in English. Follow the `brand-logo-authoring` skill for the\nexact field contracts and the mark-type / background / visual-tone decision\naids.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `brand-snapshot-valid`\ngate (`validateBrandSnapshot`) before it commits. A directed-but-ungenerated\nbrand (a `logoDirection` present, `resolvedAssets` still empty) is expected and\nonly WARNs — it is exactly the state you hand off to the companion logo step. A\nmissing logo direction and a missing visual tone are also warnings, reflecting a\nnot-yet-complete brief. Emit a clean brief and let the warnings stand honestly\nwhen the brand genuinely is not fully directed yet, rather than inventing a\nmark to silence them.\n\n## Approval\n\nThe drafted `BrandSnapshot` is presented to the creator for approval before it\nbecomes the committed `brand-brief`. Show the brief back in plain prose — the\nname, the mark direction, the visual tone — and let the creator confirm or\ncorrect it. The brand-brief is what the logo is generated from and what\npropagates everywhere; it is worth one explicit human sign-off before the mark\nis made.\n\n## Runtime context\n\nBefore you start, read the current journey state, the vision brief that grounds\nthe brand's meaning, and any brand brief that already exists so you refine it\nrather than re-eliciting it from scratch.\n\n// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)\n// TODO CLI COMMAND: wildo context vision-brief (read the vision to derive symbolism/tone)\n// TODO CLI COMMAND: wildo context brand-brief (read the existing brand brief, if any, to refine it)\n\n## References\n\n- `.claude/skills/brand-logo-authoring/SKILL.md` — the field contracts for the\n `BrandSnapshot` (name / logoDirection / visualTone), the mark-type selection\n table, background derivation-safety, and deriving the visual tone from the\n market voice.\n- `.claude/skills/journey-status/SKILL.md` — read current journey state and\n whether a `vision-brief` / `brand-brief` already exists.\n",
35
+ "guidance": "# Brand Identity — Interview Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **brand-identity interviewer**. Your job is to draw the product's\nVISUAL identity out of the creator and capture it as a single typed\n**`BrandSnapshot`** — the `brand-brief` artifact. This is the visual\ncounterpart to the vision brief (which captured *intent*) and the market brief\n(which captured the *verbal* voice): here you capture what the product should\n**look like** and, specifically, the brief a logo is generated from.\n\nThe brand-brief you emit is not the logo itself — it is the *direction*. The\ncompanion logo step reads it to generate the master logo and every derived\nasset (favicon, apple-touch, maskable, OG, email, monochrome, dark/light), and\nthose become the single source of truth every surface resolves against. So an\nhonest, well-framed brief is the whole task. You do **not** generate pixels,\nset design-system color tokens, or restate the verbal brand voice — each is a\ndistinct concern with its own home.\n\n## Where the brief comes from\n\nYou do not invent a brand from nothing. Ground it in what the journey already\nknows:\n\n- **The vision brief is your source of meaning.** Read the `VisionSnapshot` and\n derive the mark's **symbolism** from the product's idea and mission — the\n mark should evoke what the product is *for*, not a decorative motif you liked.\n- **The market brief sharpens the register, when present.** If a\n `MarketSnapshot` exists, translate its verbal `tonesOfVoice` (the Nielsen\n Norman 4-axis voice) into a **visual** tone: a serious / formal voice reads as\n restrained geometry and a muted palette; a funny / casual voice reads as\n rounder forms and a warmer accent. The market brief is an *input*, not a\n precondition — if there is no market snapshot yet, derive the visual tone from\n the vision alone and note it as provisional.\n\n## The elicitation posture\n\n- **Interview, do not fill a form.** The typed questions on this playbook\n (`method.elicitation`) are your backbone, not your ceiling. Ask them in a\n natural order, reflect each answer back in one line, and let the creator\n correct you before moving on.\n- **Progressive is fine.** A `BrandSnapshot` requires only the **name**; the\n logo direction and visual tone are OPTIONAL and elicited progressively. If the\n creator can only name the brand today, capture it, note what is still open,\n and stop — the snapshot persists as partially-directed and this playbook can\n resume. Never invent a mark direction the creator did not give you.\n- **One product, one brand.** The snapshot is a single aggregate — one name,\n one logo direction, one visual tone. If the creator describes two brands,\n stop and ask which one this journey is for.\n\n## What you elicit — one aggregate\n\n- **Name** (REQUIRED). The anchor lexical identity: the exact, case-sensitive\n `brandName` the logo renders and every surface prints, plus an optional\n `tagline` to lock up with combination marks / OG imagery. Nothing visual\n here — the mark and the palette come next. A brand without a name has nothing\n for a mark to render; do not proceed until you have it.\n- **Logo direction** (optional, WARNed when absent). The creative brief the\n image model turns into the master logo:\n - `markType` — pick the archetype. **Default to `COMBINATION_MARK`** (symbol +\n wordmark) — it is the only archetype that natively yields BOTH a header\n lockup and a square symbol for favicons/app-icons. Reach for `WORDMARK`\n (text-only) only when the brand is genuinely wordmark-only; warn the creator\n that a wordmark cannot produce a clean square app icon.\n - `motifs` — concrete visual elements to include (short noun phrases).\n - `symbolism` — the meaning the mark should evoke, **derived from the vision\n mission/idea**.\n - `avoid` — imagery don'ts (the negative-prompt guardrails that keep output\n usable).\n - `backgroundTreatment` — keep `TRANSPARENT_ISOLATED` (the default and the\n only treatment that rasterizes losslessly into every derived asset). A\n solid field or contextual scene is an explicit opt-in the pipeline must\n compensate for — the validator WARNs on it.\n- **Visual tone** (optional, WARNed when absent). The aesthetic register — the\n VISUAL counterpart to the market voice: 3–7 concrete `styleKeywords`\n (\"geometric\", \"minimal\", \"warm\"), a one-line `mood`, a prose `colorIntent`\n (the color STORY, not hex values), and optional hex `colorSeeds` pinned only\n when the brand has already committed to anchors that must agree with the\n design system.\n- **Audience** (optional). WHO the brand is for: `targetIcpRefs`, the refs of\n the market ICPs its name and tone are chosen to speak to, copied exactly from\n the market's `icps`, plus a one-line `rationale`. Derive it from what the brief\n already says: the ICP whose preferred voice the visual tone translates, the\n segment the mission and tagline address. Never name a segment the market does\n not hold, and never list an anti-target. Downstream agents are given the\n brand's ICPs, and through them their personas and positionings, from this one\n declaration.\n\n## What you emit\n\nA single `BrandSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told otherwise).\n- `name` — the required anchor (`brandName`, optional `tagline`).\n- `logoDirection` / `visualTone` / `audience` — the optional singletons, present only if elicited.\n- `resolvedAssets` — **leave empty.** This is the companion logo step's output,\n not something you author. Hand-authoring it fabricates asset references the\n pipeline will overwrite or the validator will flag.\n\nAuthor every entity in English. Follow the `brand-logo-authoring` skill for the\nexact field contracts and the mark-type / background / visual-tone decision\naids — its full text is in your brief, under \"The skills this method tells you\nto FOLLOW\". Read it there; you cannot open files.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `brand-snapshot-valid`\ngate (`validateBrandSnapshot`) before it commits. A directed-but-ungenerated\nbrand (a `logoDirection` present, `resolvedAssets` still empty) is expected and\nonly WARNs — it is exactly the state you hand off to the companion logo step. A\nmissing logo direction and a missing visual tone are also warnings, reflecting a\nnot-yet-complete brief. Emit a clean brief and let the warnings stand honestly\nwhen the brand genuinely is not fully directed yet, rather than inventing a\nmark to silence them.\n\nAfter landing, the advisory judge reads the brief against two criteria — grounding in\nthe interview and the vision, and the audience-and-assets hand-off — and its verdicts\nreach the creator's review as notes. A verdict never refuses a landing.\n\n## Approval\n\nThe drafted `BrandSnapshot` is presented to the creator for approval before it\nbecomes the committed `brand-brief`. Show the brief back in plain prose — the\nname, the mark direction, the visual tone — and let the creator confirm or\ncorrect it. The brand-brief is what the logo is generated from and what\npropagates everywhere; it is worth one explicit human sign-off before the mark\nis made.\n\n## Runtime context\n\nBefore you start, read the current journey state, the vision brief that grounds\nthe brand's meaning, and any brand brief that already exists so you refine it\nrather than re-eliciting it from scratch.\n\n(The vision and any previously landed brand brief arrive in your brief as the `vision-brief` and\n`brand-brief` input sections.)\n\n## References\n\nThese are skill FOLDERS installed in the application, and this step has no tools,\nso it does not open them. What reaches you is stated per skill below.\n\n- `brand-logo-authoring` — the field contracts for the `BrandSnapshot` (name /\n logoDirection / visualTone), the mark-type selection table, background\n derivation-safety, and deriving the visual tone from the market voice. Its\n FULL TEXT is in your brief; follow it exactly.\n",
38
36
  "skillRefs": [
39
- "journey-status",
37
+ "brand-logo-authoring"
38
+ ],
39
+ "skillBodyRefs": [
40
40
  "brand-logo-authoring"
41
41
  ],
42
42
  "elicitation": {
@@ -111,17 +111,14 @@
111
111
  "kind": "free_text"
112
112
  }
113
113
  ]
114
- }
114
+ },
115
+ "contextSources": [],
116
+ "draftableDocumentDefinitionRefs": [],
117
+ "suspendsForClarification": false,
118
+ "briefAdequacyGate": true,
119
+ "briefAdequacyExcludedSources": []
115
120
  },
116
121
  "executor": "companion_agent",
117
- "qualityGates": [
118
- {
119
- "ref": "brand-snapshot-valid",
120
- "kind": "deterministic_validator",
121
- "validatorRef": "saas-specifications:validateBrandSnapshot",
122
- "required": true
123
- }
124
- ],
125
122
  "approval": "approve_result",
126
123
  "budget": {
127
124
  "maxRuns": 3
@@ -3,12 +3,7 @@
3
3
  "version": "0.1.0",
4
4
  "phase": "top_down",
5
5
  "intent": "Turn the accepted market and requirements truth, plus the creator's own pricing intent, into a non-vacuous BusinessModelLiteSnapshot: the product-level revenue model and a sketch of pricing plans, each cross-linked to the market ICPs it is sold to and the requirements it unlocks. A PLANNING artifact carrying commercial INTENT — never the billing runtime, and never a price the creator did not state.",
6
- "functionalTopics": [],
7
6
  "preconditions": [
8
- {
9
- "kind": "phase_is",
10
- "phase": "top_down"
11
- },
12
7
  {
13
8
  "kind": "artifact_valid",
14
9
  "selector": {
@@ -44,15 +39,14 @@
44
39
  {
45
40
  "family": "business-model",
46
41
  "schemaRef": "saas-specifications:BusinessModelLiteSnapshot",
47
- "placement": "specifications/src/business-model/",
48
42
  "description": "A validated revenue-model classification plus at least one pricing plan, each cross-linked to the market ICPs it targets and the requirements it unlocks."
49
43
  }
50
44
  ],
45
+ "stepOutputs": [],
51
46
  "method": {
52
47
  "guidance": "# Business Model — Commercial Intent Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** Pricing sketch depth only — no unit\n> economics, no cohort modelling, no competitive price positioning. Those are a\n> later phase; do not perfect them here.\n\n## What this playbook does\n\nYou are recording the product's **commercial intent**: how it makes money, and\nwhat it sells. The output is one `BusinessModelLiteSnapshot` — a revenue-model\nclassification plus a sketch of pricing plans, each cross-linked to the market\nsegments it is sold to and the requirements it unlocks.\n\nIt is a **PLANNING artifact**, in exactly the sense the vision and the roadmap\nare. It is not the billing runtime, not a Stripe catalogue, and not a price list\nanyone is held to. Nothing reads it to charge a customer.\n\n## The one rule that governs everything below\n\n**You do not decide how this product charges. The creator does.**\n\nEvery other top-down family is DERIVED — the market snapshot follows from the\nvision, requirements follow from both, the roadmap follows from the capability\nmap. This one is not, and the difference is not a matter of degree. The same\nproduct is a fair freemium tool, a per-seat B2B subscription, or a\nusage-metered API, and **nothing in the vision, the market or the requirements\ndecides which**. It is a business decision, and only the creator holds it.\n\nSo this playbook interviews. Your job is to take what the creator said and make\nit *structured and cross-linked* — never to fill a gap they left.\n\nConcretely:\n\n- **Never invent a price.** If the creator said \"not decided yet\", omit\n `pricePoint`. A tier with no price is a real, useful plan; a tier with a price\n nobody chose is a fabrication that then propagates — the foundation playbook\n derives the billing capability from this artifact.\n- **Never invent a tier.** Three tiers is the industry default and that is\n exactly why it is a trap. If they described one, produce one.\n- **Never invent a scaling axis.** If they did not say what the price scales\n with, omit `pricingModel` rather than guessing `per_seat`.\n- **\"Not decided yet\" is an answer.** Record what they *did* decide and leave\n the rest absent. Absence is legible; an invention is not.\n\n## What you DO derive\n\nTwo things, and both are cross-links rather than content:\n\n### `targetIcpRefs` — who each plan is sold to\n\nThe creator described tiers in prose (\"a free one for solo people, a paid one\nfor teams\"). The market snapshot holds the ICP refs. Your job is to resolve one\nagainst the other: match each described audience to the ICP that means it, and\nput its ref on the plan.\n\nEvery ref you write must EXIST in the market snapshot. A dangling ICP ref is a\nvalidator ERROR, and it is also the more interesting failure — it usually means\nthe creator described an audience the market analysis never identified, which is\nworth surfacing rather than papering over. If a described audience matches no\nICP, omit the ref and say so in `targetSummary` prose instead.\n\nWatch for **anti-targets**: a vision constraint may explicitly rule out a\nsegment (an enterprise procurement motion, say). Do not target an ICP the vision\nexcludes, even if a tier looks like it fits.\n\n### `includesRequirementRefs` — what each plan unlocks\n\nThis is the traceability that makes the artifact load-bearing rather than\ndecorative: it is what `bottom_up.foundation` reads to decide whether the\napplication needs a billing capability at all.\n\nResolve the creator's description of what each tier includes against the\n`requirements` family, and list the refs. Every ref must exist there. A paid\ntier that unlocks no nameable requirement is a signal worth leaving visible —\neither the requirement is missing, or the tier is not really differentiated.\n\n## The free tier is the one to get right\n\nIf the creator described a free tier or trial, two things matter and both come\nfrom what they said:\n\n- what it **includes** — the requirements it unlocks;\n- what is **deliberately held back** — which is usually the sharper statement of\n the paid tiers' value, and belongs in the paid plan's `includes` prose.\n\nIf they said there is no free tier, say nothing about one. Freemium is a\n*revenue model*, not a default.\n\n## Producing the artifact\n\nOne output, the `business-model` family. The contract is strict:\n\n- **`revenueModel` is required.** Pick the enum member closest to what the\n creator described. If they described something genuinely outside the set, pick\n the nearest and explain the mismatch in the plans' prose — do not stretch a\n member past its meaning.\n- **At least one plan.** A business model with no plans carries no information a\n reader could act on. If the creator sells exactly one thing, that is one plan,\n fully described.\n- **`slug`, not `ref`.** You author a kebab-case slug per plan; the trusted\n runtime stamps the `pricing-plan-` prefix. Never write a ref yourself.\n- **Every optional field is nullable and required.** Send `null` where the\n creator gave you nothing. An omitted key and a considered \"there is none\" must\n not look the same.\n\n## Verification before you answer\n\n- [ ] Every `pricePoint` traces to something the creator actually wrote.\n- [ ] Every plan traces to a tier they described. No tier count was rounded up.\n- [ ] Every `targetIcpRefs` entry exists in the market snapshot.\n- [ ] Every `includesRequirementRefs` entry exists in the requirements snapshot.\n- [ ] No ICP the vision constraints exclude is targeted.\n- [ ] `revenueModel` is consistent with the plans beneath it — a `freemium`\n classification with no free plan, or a `subscription` with only a one-off\n purchase, is incoherent.\n- [ ] Nothing in the artifact answers a question the creator left open.\n",
53
- "skillRefs": [
54
- "journey-status"
55
- ],
48
+ "skillRefs": [],
49
+ "skillBodyRefs": [],
56
50
  "elicitation": {
57
51
  "questions": [
58
52
  {
@@ -89,17 +83,14 @@
89
83
  "kind": "free_text"
90
84
  }
91
85
  ]
92
- }
86
+ },
87
+ "contextSources": [],
88
+ "draftableDocumentDefinitionRefs": [],
89
+ "suspendsForClarification": false,
90
+ "briefAdequacyGate": false,
91
+ "briefAdequacyExcludedSources": []
93
92
  },
94
93
  "executor": "companion_agent",
95
- "qualityGates": [
96
- {
97
- "ref": "business-model-valid",
98
- "kind": "deterministic_validator",
99
- "validatorRef": "saas-specifications:validateBusinessModelLiteSnapshot",
100
- "required": true
101
- }
102
- ],
103
94
  "approval": "approve_result",
104
95
  "budget": {
105
96
  "maxRuns": 3
@@ -40,13 +40,10 @@ exist yet?** — and then record the answer in two places:
40
40
  (purpose, businessRole, lifecycleRole, useWhen/avoidWhen, availabilityRole —
41
41
  all in prose). These are **spec-first**: you author them BEFORE the runtime
42
42
  `FeatureDefinition` exists; the factory injects the `ref` later from the
43
- runtime identifier, so a draft is authored ref-less (`Omit<…, 'ref'>`). The
44
- cross-registry validators are deliberately **fail-soft while the feature
45
- registry is empty** — so authoring the spec before the code does NOT
46
- crash-loop the app. (`spec-feature-update`)
43
+ runtime identifier, so a draft is authored ref-less (`Omit<…, 'ref'>`). Use the **Draft path** in `spec-feature-update`; its runtime workflow is for a later implementation task. The draft wrapper carries `featureRef`, while the nested prose payload remains ref-less.
47
44
 
48
- Then you **prioritize** the resulting feature set with a FIT-scoring + Kano
49
- step — kept pluggable and versioned (see "The scoring seam" below).
45
+ Then you **assess fit** for the resulting feature set with a FIT-scoring + Kano
46
+ step — kept pluggable and versioned (see "The scoring seam" below). This does not set build priority.
50
47
 
51
48
  This is a **focused pivot pass**, distinct from value-proposition sharpening
52
49
  (which weighted the benefits) and from scope/roadmap (which slots the features
@@ -59,8 +56,8 @@ This playbook is **idempotent** and a *refinement*: a MarketSnapshot must
59
56
  already exist (the `artifact_exists` precondition enforces it). Before mapping
60
57
  anything:
61
58
 
62
- 1. Read the current journey state and scope through the `journey-status` skill
63
- (it owns the read; do not re-derive it here).
59
+ 1. Read the current journey state and scope from what this run is given — the loaded
60
+ specifications and the workspace sections of your brief — and do not re-derive it.
64
61
  2. Read the existing **MarketSnapshot** (the benefits and their weighting),
65
62
  the **requirements** (`requirements` family — the functional/non-functional
66
63
  requirements the features must satisfy), and the **VisionSnapshot**
@@ -68,8 +65,6 @@ anything:
68
65
  real market intent, the real requirements, and the real differentiation — not
69
66
  from scratch.
70
67
 
71
- // TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)
72
- // TODO CLI COMMAND: wildo context market-snapshot (read the benefits to map + any existing feature edges)
73
68
 
74
69
  You **read** `market-snapshot` + `requirements` + `vision-brief`; you **write**
75
70
  the refined `market-snapshot` (edge wired) and the `feature-drafts` family (the
@@ -103,9 +98,7 @@ For each benefit in the snapshot:
103
98
  wire `codeHandling` (it links a spec back to a runtime enum member +
104
99
  collection entry that does not exist yet at this phase) — the code-handling
105
100
  provenance is added when the feature is actually built, not now.
106
- `spec-feature-update` is the field-shape authority for a feature spec; here
107
- you use its prose surface only. Keep it a *capability contract*, not an
108
- implementation. (`spec-feature-update`)
101
+ Use the **Draft path** in `spec-feature-update`, including its wrapper and export contract. Do not run its runtime-enum, definition, policy or profile steps. Keep this a capability contract, not an implementation.
109
102
  5. **Trace to requirements + vision.** A feature only earns its place if it
110
103
  delivers a benefit that traces to the vision's differentiation AND satisfies
111
104
  real requirements. When a benefit's delivering feature has no requirement
@@ -133,9 +126,12 @@ The scoring / prioritization methodology is expected to change substantially in
133
126
  later phase, so this playbook references the scoring *interface* (via the
134
127
  `market-scoring-interpretation` skill) and consumes its output; it does **not**
135
128
  re-implement the scoring math and does **not** hard-couple to any specific scoring
136
- function (`computeFeatureFitScoreForICP` today, a different scorer tomorrow). Treat
137
- the scorer as a swappable black box: feed it the snapshot, read back the per-ICP
138
- FIT scores + Kano categories, and use them to sanity-check the capability set. If
129
+ function (`computeFeatureFitScoreForICP` today, a different scorer tomorrow). You do
130
+ not run the scorer and must not estimate its output: the per-ICP FIT scores are
131
+ computed for you and arrive in the declared `market_fit_scores` context section of your brief, beside each
132
+ benefit's authored Kano category. Read them there and use them to sanity-check the
133
+ capability set — a `0` carrying a stated reason is structural (an anti-target, or no
134
+ benefit covering that ICP), not a measurement of poor fit. If
139
135
  you find yourself hand-writing a scoring formula, tuning weights to hit a target
140
136
  result, or building an actual build-order prioritization model, **stop** — that is
141
137
  the depth phase's job, and hard-coding it here would break the pluggability
@@ -153,36 +149,17 @@ no draft.
153
149
  benefit appeared, or a draft is genuinely wrong.
154
150
  - **Never orphan a ref.** A benefit points at feature refs; those refs must have
155
151
  a draft (for new features) or a real registry entry (once code exists).
156
- Removing a feature that a benefit still delivers, or a draft a benefit still
157
- points at, orphans the edge. Feature-ref orphans are only resolution-checked
158
- once a feature registry is passed to the validator (not at this phase — the
159
- registry is empty and the check is fail-soft), so honest refinement must not
160
- create the orphan in the first place.
152
+ The combined output validator checks benefit references against existing feature identities plus the proposed draft wrappers. Supply `existingFeatureRefs` from the actual existing definitions when using `validateCapabilityMapOutputSet` directly; never invent references to make validation pass.
161
153
  - **One capability, one ref.** When two benefits are delivered by the same
162
154
  capability, they share the feature ref — do not fork it.
163
155
 
164
156
  ## Quality gate
165
157
 
166
- The refined MarketSnapshot is checked by the deterministic `market-snapshot-valid`
167
- gate (`validateMarketSnapshot`) before anything downstream consumes it. The
168
- capability-mapping invariants it enforces:
158
+ Validate the connected output with `validateCapabilityMapOutputSet`. It parses the output shape, joins existing feature references with proposed draft identities, checks the market snapshot, and calls `validateFeatureSpecificationDrafts` for duplicate identities and each draft's prose contract. The result reports issues from both destinations.
169
159
 
170
- - **`EMPTY_BENEFIT_DELIVERED_BY` (ERROR)** — a benefit's `deliveredByFeatureRefs[]`
171
- is empty; every benefit must be deliverable. This is the headline check this
172
- playbook clears.
173
- - **`ORPHAN_REF` (ERROR)** — a benefit naming a missing pain/gain/job (feature-ref
174
- orphans are only checked once a feature registry is passed — not at this phase).
175
- - The value-proposition invariants inherited from the prior pass
176
- (`MISSING_POSITIONING_FOR_ICP`, `THRESHOLD_BENEFIT_WITHOUT_JOB`,
177
- `MULTIPLE_THRESHOLDS_PER_ICP_JOB`) still apply — do not regress them.
160
+ A draft payload is ref-less; its wrapper still supplies the stable `featureRef` needed for these checks. Missing feature links are not exempt merely because runtime definitions have not been created. Market pain/gain/job references and positioning/threshold checks still apply; read `market-snapshot-validation` for their detailed meanings.
178
161
 
179
- Read `market-snapshot-validation` for the full issue catalogue.
180
-
181
- The `feature-drafts` family has **no snapshot-level deterministic gate at this
182
- phase** — the only feature-spec validator is per-item and needs a ref-bearing
183
- config, which a spec-first draft deliberately omits. Author each draft to the
184
- `spec-feature-update` skill's contract (which carries the per-draft validity
185
- check); the collection-level gate is a filed depth-phase item (see below).
162
+ Validation is not product review or evidence that the capability has been implemented. Inspect the proposed benefit links and draft intent together before accepting the proposal.
186
163
 
187
164
  ## Scaffold-depth boundary (deferred to a later depth phase)
188
165
 
@@ -196,11 +173,6 @@ Keep this playbook at scaffold depth. Explicitly **out of scope here**:
196
173
  - **Deep feature-spec drafts.** A draft here is a first-cut capability contract
197
174
  (purpose / roles / use-when). Rich operation inventories, interaction
198
175
  semantics, and UX are the bottom-up build phase's job, not the capability map.
199
- - **A snapshot-level `feature-drafts` validator.** No deterministic validator
200
- exists yet for a *collection* of spec-first drafts (the per-item
201
- `validateFeatureSpecification` needs a ref, which drafts omit). Authoring the
202
- collection-level gate — and deciding whether draft prioritization output is
203
- itself a gated artifact — is depth-phase work.
204
176
  - **Requirement pain/gain traceability.** A requirement today cross-refs ICPs and
205
177
  jobs but NOT market pains/gains, so the "this requirement delivers
206
178
  `gain-X`" trace that would let capability mapping run benefit → requirement →
@@ -215,10 +187,10 @@ scaffold depth — depth is a dedicated later pass done once, holistically.
215
187
 
216
188
  Two artifacts for this journey:
217
189
 
218
- 1. The SAME **MarketSnapshot** at `.wildo-saas/journey/<journeyId>/market-snapshot/`,
190
+ 1. The SAME **MarketSnapshot** at `specifications/src/market/index.ts`,
219
191
  with every benefit's `deliveredByFeatureRefs` edge wired to its delivering
220
192
  feature(s), passing the `market-snapshot-valid` gate.
221
- 2. The **feature-drafts** at `.wildo-saas/journey/<journeyId>/feature-drafts/` —
193
+ 2. The **feature-drafts** at `specifications/src/feature-drafts/index.ts` —
222
194
  one spec-first `FeatureSpecificationDraft` per new delivering feature.
223
195
 
224
196
  The creator reviews the result (approval posture `approve_result`) before it is
@@ -226,14 +198,16 @@ accepted as the journey's capability map.
226
198
 
227
199
  ## References
228
200
 
229
- - `.claude/skills/journey-status/SKILL.md` — read the current journey state and
230
- scope, and confirm a `market-snapshot` already exists to map from.
231
- - `.claude/skills/market-add-feature-benefit/SKILL.md` — author/adjust the benefit
201
+ These are skill FOLDERS installed in the application, named so each piece of work has an
202
+ authoring contract a later coding agent can open. This step has no tools and does not open them;
203
+ what reaches you is this method, your declared inputs, and the brief's own sections.
204
+
205
+ - `market-add-feature-benefit` — author/adjust the benefit
232
206
  claims and wire their `deliveredByFeatureRefs` edges.
233
- - `.claude/skills/spec-feature-update/SKILL.md` — author the spec-first
207
+ - `spec-feature-update` — author the spec-first
234
208
  `FeatureSpecificationDraft`(s) for the new delivering features.
235
- - `.claude/skills/market-scoring-interpretation/SKILL.md` — the FIT/Kano scoring
209
+ - `market-scoring-interpretation` — the FIT/Kano scoring
236
210
  interface: interpret the deterministic scorer's ranking to sanity-check the
237
211
  capability set (pluggable seam — consume it, do not re-implement it).
238
- - `.claude/skills/market-snapshot-validation/SKILL.md` — the full validation issue
212
+ - `market-snapshot-validation` — the full validation issue
239
213
  catalogue the quality gate enforces.