@wildo-ai/framework-knowledge 1.1.10 → 1.1.12

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 (1349) hide show
  1. package/dist/claude-marketplace/.claude-plugin/marketplace.json +1 -1
  2. package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
  3. package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +4 -0
  4. package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +25 -3
  5. package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +40 -12
  6. package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +7 -5
  7. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +12 -0
  8. package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +19 -2
  9. package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +33 -9
  10. package/dist/esm/framework-knowledge.definitions.d.ts +2 -3
  11. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  12. package/dist/esm/framework-knowledge.definitions.js +628 -107
  13. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  14. package/dist/esm/framework-knowledge.loader.js.map +1 -1
  15. package/dist/esm/framework-knowledge.research-provenance.d.ts +90 -0
  16. package/dist/esm/framework-knowledge.research-provenance.d.ts.map +1 -0
  17. package/dist/esm/framework-knowledge.research-provenance.js +140 -0
  18. package/dist/esm/framework-knowledge.research-provenance.js.map +1 -0
  19. package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
  20. package/dist/esm/framework-knowledge.schemas.js.map +1 -1
  21. package/dist/esm/index.d.ts +2 -0
  22. package/dist/esm/index.d.ts.map +1 -1
  23. package/dist/esm/index.js +2 -0
  24. package/dist/esm/index.js.map +1 -1
  25. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -3
  26. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  27. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +4 -12
  28. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  29. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +12 -1
  31. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
  32. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +10 -4
  33. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +82 -15
  35. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  36. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -5
  37. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +4 -16
  39. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  41. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +1 -1
  43. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -1
  44. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +1 -1
  45. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +9 -5
  47. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +11 -7
  49. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  50. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +1 -1
  51. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -1
  52. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +1 -1
  53. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -1
  54. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  55. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +38 -14
  56. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  57. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +16 -8
  58. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  59. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +20 -8
  60. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  61. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +29 -3
  62. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  63. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +80 -16
  64. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  65. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +2 -2
  66. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
  67. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +7 -2
  68. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
  69. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +2 -2
  70. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -1
  71. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +2 -2
  72. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -1
  73. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +6 -2
  74. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  75. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +4 -3
  76. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  77. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +26 -7
  78. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  79. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +23 -6
  80. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  81. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +45 -10
  82. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
  83. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +61 -21
  84. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -1
  85. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +4 -3
  86. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
  87. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +8 -5
  88. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -1
  89. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -1
  90. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +2 -2
  91. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
  92. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +7 -3
  93. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -1
  94. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +1 -1
  95. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +3 -3
  96. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  97. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  98. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +9 -7
  99. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  100. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +5 -0
  101. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
  102. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +9 -2
  103. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -1
  104. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -1
  105. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +5 -2
  106. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  107. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +15 -5
  108. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  109. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +1 -1
  110. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
  111. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
  112. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +6 -4
  113. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
  114. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +3 -1
  115. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
  116. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +4 -1
  117. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
  118. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +10 -1
  119. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  120. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +36 -13
  121. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  122. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +8 -2
  123. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  124. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +7 -1
  125. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  126. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +4 -1
  127. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  128. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +34 -6
  129. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  130. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +7 -3
  131. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  132. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +6 -4
  133. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  134. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +2 -2
  135. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  136. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +22 -10
  137. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  138. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +39 -29
  139. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  140. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  141. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +8 -3
  142. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  143. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +24 -9
  144. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  145. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +8 -2
  146. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
  147. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +8 -2
  148. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  149. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js +1 -1
  150. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -1
  151. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  152. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +2 -2
  153. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  154. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  155. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +1 -1
  156. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  157. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  158. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +13 -5
  159. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  160. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +3 -7
  161. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  162. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +12 -14
  163. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  164. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +3 -0
  165. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
  166. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +2 -1
  167. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
  168. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +3 -1
  169. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  170. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +2 -1
  171. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  172. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts +98 -0
  173. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts.map +1 -0
  174. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js +124 -0
  175. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js.map +1 -0
  176. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +3 -1
  177. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  178. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +4 -2
  179. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  180. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +34 -1
  181. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  182. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +39 -20
  183. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  184. package/dist/esm/source-anchor-grammar.d.ts +70 -0
  185. package/dist/esm/source-anchor-grammar.d.ts.map +1 -0
  186. package/dist/esm/source-anchor-grammar.js +114 -0
  187. package/dist/esm/source-anchor-grammar.js.map +1 -0
  188. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  189. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  190. package/dist/knowledge/manifest.json +8 -8
  191. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +12 -0
  192. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +4 -4
  193. package/dist/knowledge/playbooks/bottom_up.build/method.md +12 -2
  194. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +5 -3
  195. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  196. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  197. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +788 -49
  198. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +18 -4
  199. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +451 -16
  200. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +3 -6
  201. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +1 -0
  202. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +2 -2
  203. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +3 -2
  204. package/dist/knowledge/playbooks/bottom_up.conception/method.md +12 -7
  205. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +4 -3
  206. package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +2 -2
  207. package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +2 -1
  208. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
  209. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
  210. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +115 -2
  211. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +11 -4
  212. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +71 -7
  213. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +19 -6
  214. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +126 -24
  215. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +51 -7
  216. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +28 -9
  217. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +5 -3
  218. package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +10 -2
  219. package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +4 -3
  220. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +67 -5
  221. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +10 -3
  222. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +176 -22
  223. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +21 -3
  224. package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +27 -12
  225. package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +11 -5
  226. package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +4 -4
  227. package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +7 -2
  228. package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +1 -0
  229. package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +6 -5
  230. package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +5 -2
  231. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -1
  232. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -1
  233. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +153 -28
  234. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +3 -2
  235. package/dist/knowledge/playbooks/refinement.document-facts/method.md +36 -7
  236. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +6 -2
  237. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +9 -2
  238. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +8 -6
  239. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +2 -1
  240. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  241. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  242. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +9 -2
  243. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +17 -5
  244. package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +11 -4
  245. package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +3 -2
  246. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -1
  247. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -1
  248. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +16 -6
  249. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +3 -2
  250. package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +5 -1
  251. package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
  252. package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
  253. package/dist/knowledge/playbooks/top_down.business-model/method.md +49 -11
  254. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +24 -8
  255. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +6 -2
  256. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +1 -1
  257. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +49 -14
  258. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +15 -5
  259. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +6 -2
  260. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +20 -0
  261. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +4 -3
  262. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -1
  263. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -1
  264. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +69 -65
  265. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +11 -7
  266. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +1 -0
  267. package/dist/knowledge/playbooks/top_down.definition/method.md +10 -3
  268. package/dist/knowledge/playbooks/top_down.definition/playbook.json +14 -5
  269. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +10 -3
  270. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +4 -3
  271. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +2 -1
  272. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +1 -0
  273. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +4 -2
  274. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +4 -3
  275. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +1 -0
  276. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +3 -0
  277. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +3 -2
  278. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  279. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  280. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +1 -0
  281. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +10 -6
  282. package/dist/knowledge/playbooks/top_down.risk-register/method.md +8 -1
  283. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +5 -1
  284. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +6 -1
  285. package/dist/knowledge/playbooks/top_down.service-method/method.md +216 -0
  286. package/dist/knowledge/playbooks/top_down.service-method/playbook.json +108 -0
  287. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +5 -2
  288. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +9 -3
  289. package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-protocol.json +1 -1
  290. package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-treatment.json +1 -1
  291. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +21 -2
  292. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +63 -18
  293. package/dist/knowledge/references/acp.execution-profile.md +9 -1
  294. package/dist/knowledge/references/application-documentation-chapters.config.md +45 -10
  295. package/dist/knowledge/references/application-documentation-plan.config.md +2 -2
  296. package/dist/knowledge/references/application-maturity.config.md +28 -2
  297. package/dist/knowledge/references/backend.inbound-channels.attachment-adoption.md +57 -0
  298. package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +65 -13
  299. package/dist/knowledge/references/backend.inbound-handlers.agents.md +10 -3
  300. package/dist/knowledge/references/backend.inbound-handlers.definition.md +463 -5
  301. package/dist/knowledge/references/backend.inbound-handlers.pipelines.md +62 -0
  302. package/dist/knowledge/references/blueprint.definition-contract.md +483 -0
  303. package/dist/knowledge/references/brand.name-screening.config.md +30 -3
  304. package/dist/knowledge/references/brand.visual-tone.config.md +26 -8
  305. package/dist/knowledge/references/build-plan.task-graph.config.md +438 -12
  306. package/dist/knowledge/references/business-model.pricing-plan.config.md +19 -9
  307. package/dist/knowledge/references/business-model.snapshot.config.md +29 -2
  308. package/dist/knowledge/references/business-model.snapshot.validation.md +29 -8
  309. package/dist/knowledge/references/capability-composition.config.md +4 -3
  310. package/dist/knowledge/references/cli.market.generate-command.md +2 -1
  311. package/dist/knowledge/references/companion.introspection.behaviors.market.md +3 -0
  312. package/dist/knowledge/references/companion.market.generation-service.md +46 -5
  313. package/dist/knowledge/references/companion.market.prompt-renderer.md +1 -1
  314. package/dist/knowledge/references/companion.technical-doc.service.md +342 -76
  315. package/dist/knowledge/references/domain-plan.record-partition.md +105 -0
  316. package/dist/knowledge/references/engine.client-bundle.allow-list.md +16 -0
  317. package/dist/knowledge/references/engine.saas-technical-doc.config.md +69 -15
  318. package/dist/knowledge/references/engine.saas-website.config.md +16 -44
  319. package/dist/knowledge/references/example.ai-use-declaration.agent.md +37 -0
  320. package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +10 -0
  321. package/dist/knowledge/references/{example.authorization.service-provider-organization-wide-access.md → example.authorization.relationship-organization-wide-access.md} +2 -2
  322. package/dist/knowledge/references/example.backend.addon-wiring.module.md +6 -0
  323. package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +4 -3
  324. package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +22 -0
  325. package/dist/knowledge/references/example.backend.custom-operation.declared-refusal-code.md +41 -0
  326. package/dist/knowledge/references/example.backend.custom-operation.external-effect-reservation.md +107 -0
  327. package/dist/knowledge/references/example.blueprint.definition.internal-tool.md +47 -0
  328. package/dist/knowledge/references/example.config.app-shell.full.md +6 -3
  329. package/dist/knowledge/references/example.config.app-shell.hosted-components.md +4 -1
  330. package/dist/knowledge/references/example.config.backend.inbound-email.md +4 -2
  331. package/dist/knowledge/references/example.config.backend.required-floors.md +4 -2
  332. package/dist/knowledge/references/example.config.design-system.full.md +40 -116
  333. package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +10 -0
  334. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +78 -19
  335. package/dist/knowledge/references/example.flows-actors.declared-flow.md +115 -0
  336. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +12 -0
  337. package/dist/knowledge/references/example.inbound.email-channel-handler.md +10 -1
  338. package/dist/knowledge/references/example.infra.environment-config.local.md +34 -63
  339. package/dist/knowledge/references/example.layout-2d.registration.md +11 -0
  340. package/dist/knowledge/references/example.minion.contained-tick.md +1 -1
  341. package/dist/knowledge/references/example.module.companion-exports.full.md +1 -0
  342. package/dist/knowledge/references/example.module.relationships.actor-edge-back-to-scope-owner.md +35 -35
  343. package/dist/knowledge/references/example.module.relationships.scope-membership-junction.md +8 -10
  344. package/dist/knowledge/references/example.navigation.one-entry-per-concept.md +47 -0
  345. package/dist/knowledge/references/example.organization-identity.system-of-record-partitions.md +18 -0
  346. package/dist/knowledge/references/example.organizations.relationship-kinds.md +26 -0
  347. package/dist/knowledge/references/example.professional-qualifications.declaration.md +10 -0
  348. package/dist/knowledge/references/example.professional-qualifications.gate.md +25 -0
  349. package/dist/knowledge/references/example.provider.backend-module-shape.md +38 -4
  350. package/dist/knowledge/references/example.provider.frontend-facet.on-demand-sdk.md +41 -0
  351. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +4 -5
  352. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +7 -5
  353. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +0 -5
  354. package/dist/knowledge/references/example.resource.custom-view.backend-refusal.md +75 -0
  355. package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +8 -7
  356. package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +23 -7
  357. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +87 -22
  358. package/dist/knowledge/references/example.resource.ui-behavior.record-template.md +80 -0
  359. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +20 -21
  360. package/dist/knowledge/references/example.resource.ui-behavior.workflow-record-page.md +212 -0
  361. package/dist/knowledge/references/example.spec.composite-view.workspace.md +10 -2
  362. package/dist/knowledge/references/example.subject-export.portability-archive.md +42 -0
  363. package/dist/knowledge/references/example.views.app-level.workflow-home.md +238 -0
  364. package/dist/knowledge/references/example.views.composite-view.workspace.md +10 -3
  365. package/dist/knowledge/references/example.website.blocks.section.md +20 -0
  366. package/dist/knowledge/references/example.website.blocks.site-choices.md +78 -0
  367. package/dist/knowledge/references/example.website.blocks.site-configs.md +155 -0
  368. package/dist/knowledge/references/example.website.demo.append.md +57 -0
  369. package/dist/knowledge/references/example.website.demo.approval.md +47 -0
  370. package/dist/knowledge/references/example.website.demo.celebrate.md +39 -0
  371. package/dist/knowledge/references/example.website.demo.complete-items.md +103 -0
  372. package/dist/knowledge/references/example.website.demo.connect.md +45 -0
  373. package/dist/knowledge/references/example.website.demo.dashboard.md +74 -0
  374. package/dist/knowledge/references/example.website.demo.query-answer.md +77 -0
  375. package/dist/knowledge/references/example.website.demo.status-lifecycle.md +71 -0
  376. package/dist/knowledge/references/example.website.demo.transform.md +43 -0
  377. package/dist/knowledge/references/example.website.page.manifest.md +2 -6
  378. package/dist/knowledge/references/example.website.pricing.audit-payloads.md +38 -0
  379. package/dist/knowledge/references/example.website.pricing.catalog-load.md +77 -0
  380. package/dist/knowledge/references/example.website.pricing.offers.md +43 -0
  381. package/dist/knowledge/references/example.website.pricing.plans-section.md +20 -0
  382. package/dist/knowledge/references/example.website.pricing.plans.md +88 -0
  383. package/dist/knowledge/references/example.website.section.bento.md +27 -0
  384. package/dist/knowledge/references/example.website.section.contact-form.md +15 -0
  385. package/dist/knowledge/references/example.website.section.factories.md +82 -0
  386. package/dist/knowledge/references/example.website.section.faq.md +17 -0
  387. package/dist/knowledge/references/example.website.section.footer-cta.md +13 -0
  388. package/dist/knowledge/references/example.website.section.hero.md +16 -0
  389. package/dist/knowledge/references/example.website.section.latest-posts.md +15 -0
  390. package/dist/knowledge/references/example.website.section.marquee.md +26 -0
  391. package/dist/knowledge/references/example.website.section.roadmap.md +25 -0
  392. package/dist/knowledge/references/example.website.section.site-block.md +43 -0
  393. package/dist/knowledge/references/example.website.section.solution-paths.md +17 -0
  394. package/dist/knowledge/references/example.website.section.stats.md +23 -0
  395. package/dist/knowledge/references/example.website.section.steps.md +15 -0
  396. package/dist/knowledge/references/example.website.showcase.tour.md +49 -0
  397. package/dist/knowledge/references/example.website.theme.composed.md +69 -0
  398. package/dist/knowledge/references/experience-plan.config.md +127 -1
  399. package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +8 -0
  400. package/dist/knowledge/references/external-connectors.frontend-provider-sdk-activation-mode.md +27 -0
  401. package/dist/knowledge/references/external-connectors.models.connection-target.md +99 -0
  402. package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +13 -0
  403. package/dist/knowledge/references/external-connectors.models.hook-inbound-endpoint.md +352 -0
  404. package/dist/knowledge/references/external-connectors.models.hook-signature-algorithms.md +168 -0
  405. package/dist/knowledge/references/external-connectors.models.hook-trigger-strategy.md +97 -0
  406. package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +72 -8
  407. package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +235 -0
  408. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +1272 -3
  409. package/dist/knowledge/references/external-connectors.models.subject-erasure-effect.md +105 -0
  410. package/dist/knowledge/references/external-connectors.private.provider-compliance-state-collector.md +36 -0
  411. package/dist/knowledge/references/external-connectors.private.provider-configuration-check.md +69 -0
  412. package/dist/knowledge/references/integration-plan.config.md +28 -8
  413. package/dist/knowledge/references/market.references.weighted-edges.md +14 -1
  414. package/dist/knowledge/references/minions.tick-contract.md +2 -2
  415. package/dist/knowledge/references/placement-plan.config.md +94 -13
  416. package/dist/knowledge/references/platform.config.backing-services.md +9 -11
  417. package/dist/knowledge/references/platform.config.environment.deployment.md +140 -7
  418. package/dist/knowledge/references/platform.config.infra-provider-resolution.md +3 -3
  419. package/dist/knowledge/references/platform.config.infrastructure-host.md +2 -1
  420. package/dist/knowledge/references/platform.config.platform-key-management.md +282 -0
  421. package/dist/knowledge/references/platform.config.saas.md +126 -32
  422. package/dist/knowledge/references/platform.key-management.vault-custody.md +78 -0
  423. package/dist/knowledge/references/presets.3d.frame-style-resolution.md +65 -0
  424. package/dist/knowledge/references/presets.3d.layout-contract.md +4 -30
  425. package/dist/knowledge/references/presets.3d.register-layout.md +14 -36
  426. package/dist/knowledge/references/presets.layouts-2d.authoring.md +157 -0
  427. package/dist/knowledge/references/presets.layouts-2d.register-layout.md +53 -0
  428. package/dist/knowledge/references/presets.layouts-2d.settings.md +53 -0
  429. package/dist/knowledge/references/presets.layouts-2d.vocabulary.md +41 -0
  430. package/dist/knowledge/references/presets.models.field-form-control-variant.md +32 -0
  431. package/dist/knowledge/references/presets.models.labelling.sections.md +39 -0
  432. package/dist/knowledge/references/presets.models.palette-contrast.md +183 -0
  433. package/dist/knowledge/references/presets.models.palette-derivation.md +93 -0
  434. package/dist/knowledge/references/presets.models.surface-policy.defaults.md +27 -0
  435. package/dist/knowledge/references/presets.models.surface-variant.md +11 -0
  436. package/dist/knowledge/references/presets.models.theme-contract.md +136 -0
  437. package/dist/knowledge/references/presets.models.theme-personality-lexicon.md +81 -0
  438. package/dist/knowledge/references/presets.models.theme-personality.md +159 -0
  439. package/dist/knowledge/references/presets.themes.compose-theme.md +47 -0
  440. package/dist/knowledge/references/requirements.non-functional-requirement.config.md +4 -4
  441. package/dist/knowledge/references/requirements.snapshot.config.md +2 -3
  442. package/dist/knowledge/references/roadmap.phase.config.md +2 -16
  443. package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +158 -0
  444. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +85 -12
  445. package/dist/knowledge/references/saas.backend.actor-execution-continuation.md +179 -0
  446. package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +5 -1
  447. package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +3 -1
  448. package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +13 -1
  449. package/dist/knowledge/references/saas.backend.crypto-keys.application-keys.md +100 -0
  450. package/dist/knowledge/references/saas.backend.custom-operation.authoritative-fields.md +4 -1
  451. package/dist/knowledge/references/saas.backend.custom-operation.commit-outcome-read-back.md +208 -0
  452. package/dist/knowledge/references/saas.backend.custom-operation.core-write-precondition.md +38 -0
  453. package/dist/knowledge/references/saas.backend.custom-operation.external-effect-reservation.md +109 -0
  454. package/dist/knowledge/references/saas.backend.custom-operation.hook-transaction-posture.md +43 -0
  455. package/dist/knowledge/references/saas.backend.custom-operation.target-authority.md +33 -0
  456. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +131 -1
  457. package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +1 -1
  458. package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +62 -13
  459. package/dist/knowledge/references/saas.backend.domain-module.md +105 -1
  460. package/dist/knowledge/references/saas.backend.email-template.definition.md +34 -0
  461. package/dist/knowledge/references/saas.backend.email-template.words.md +98 -0
  462. package/dist/knowledge/references/saas.backend.email.send.md +7 -0
  463. package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +35 -4
  464. package/dist/knowledge/references/saas.backend.flows-actors.ask-person-tool.md +79 -0
  465. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-case-selector.md +71 -0
  466. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-declaration.md +21 -10
  467. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-schedule.md +11 -5
  468. package/dist/knowledge/references/saas.backend.flows-actors.chat-agent-declaration.md +51 -0
  469. package/dist/knowledge/references/saas.backend.flows-actors.chat-reply-handler.md +219 -0
  470. package/dist/knowledge/references/saas.backend.flows-actors.decision-notice-handler.md +239 -0
  471. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +661 -3
  472. package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +15 -2
  473. package/dist/knowledge/references/saas.backend.flows-actors.operation-approval-resolvers.md +50 -0
  474. package/dist/knowledge/references/saas.backend.flows-actors.present-records-tool.md +106 -0
  475. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +14 -1
  476. package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +9 -4
  477. package/dist/knowledge/references/saas.backend.flows-actors.retrieval-tool.md +205 -0
  478. package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +21 -5
  479. package/dist/knowledge/references/saas.backend.flows.start-flow-method.md +28 -0
  480. package/dist/knowledge/references/saas.backend.flows.start-flow.md +47 -0
  481. package/dist/knowledge/references/saas.backend.pdf-template.collection-definition.md +5 -3
  482. package/dist/knowledge/references/saas.backend.privacy.subject-export-archive.md +26 -0
  483. package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +21 -19
  484. package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +15 -25
  485. package/dist/knowledge/references/saas.backend.rate-limit-service.check-policy.md +3 -2
  486. package/dist/knowledge/references/saas.backend.submission-challenge.md +4 -0
  487. package/dist/knowledge/references/saas.backend.system-access-service.md +394 -104
  488. package/dist/knowledge/references/saas.config.content-security-policy.md +26 -10
  489. package/dist/knowledge/references/saas.data-seeding.definition-input.md +1 -1
  490. package/dist/knowledge/references/saas.data-seeding.modes.md +4 -1
  491. package/dist/knowledge/references/saas.data-seeding.row-reference.md +2 -4
  492. package/dist/knowledge/references/saas.data-seeding.run-ledger.md +3 -0
  493. package/dist/knowledge/references/saas.external-data.admin-endpoints.md +70 -3
  494. package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +6 -0
  495. package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +2 -0
  496. package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +3 -0
  497. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +10 -2
  498. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +10 -16
  499. package/dist/knowledge/references/saas.frontend.app-shell.building-blocks.md +7 -3
  500. package/dist/knowledge/references/saas.frontend.app-shell.register-shell-layout.md +97 -0
  501. package/dist/knowledge/references/saas.frontend.app-shell.shell-layout-contract.md +60 -0
  502. package/dist/knowledge/references/saas.frontend.app-shell.shell-motion-contract.md +274 -0
  503. package/dist/knowledge/references/saas.frontend.app-shell.use-shell-motion.md +73 -0
  504. package/dist/knowledge/references/saas.frontend.brand-identity.md +6 -0
  505. package/dist/knowledge/references/saas.frontend.chart-dashboard-view.md +43 -0
  506. package/dist/knowledge/references/saas.frontend.chart-dashboard.md +130 -0
  507. package/dist/knowledge/references/saas.frontend.chart-view.inserted-declaration.md +13 -0
  508. package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +8 -4
  509. package/dist/knowledge/references/saas.frontend.chat-sign-in-completion.md +99 -0
  510. package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +92 -23
  511. package/dist/knowledge/references/saas.frontend.command-menu.search-resource.md +3 -3
  512. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +9 -3
  513. package/dist/knowledge/references/saas.frontend.domain-module.md +5 -0
  514. package/dist/knowledge/references/saas.frontend.embedded-resource-descent.md +2 -1
  515. package/dist/knowledge/references/saas.frontend.errors.backend-refusal.md +96 -0
  516. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +57 -3
  517. package/dist/knowledge/references/saas.frontend.field-tiles.md +76 -0
  518. package/dist/knowledge/references/saas.frontend.flows-actors-view.md +10 -2
  519. package/dist/knowledge/references/saas.frontend.focus-indicator.md +119 -0
  520. package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +14 -2
  521. package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +7 -4
  522. package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +17 -16
  523. package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +3 -5
  524. package/dist/knowledge/references/saas.frontend.operation-key-and-resource-config-like.md +68 -1
  525. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +14 -24
  526. package/dist/knowledge/references/saas.frontend.record-page-parts.md +117 -0
  527. package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +184 -5
  528. package/dist/knowledge/references/saas.frontend.related-resource-sections.md +6 -0
  529. package/dist/knowledge/references/saas.frontend.resource-header-title.md +98 -34
  530. package/dist/knowledge/references/saas.frontend.resource-label-params.md +3 -1
  531. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +59 -19
  532. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +344 -62
  533. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +13 -8
  534. package/dist/knowledge/references/saas.frontend.section-stages.md +63 -0
  535. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +183 -32
  536. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +72 -13
  537. package/dist/knowledge/references/saas.frontend.viewer-may-perform-operation.md +52 -0
  538. package/dist/knowledge/references/saas.models.agent-suspension.md +75 -0
  539. package/dist/knowledge/references/saas.models.agent-work-capture-settings.md +2 -2
  540. package/dist/knowledge/references/saas.models.agent-work-decision-contents-read.md +69 -0
  541. package/dist/knowledge/references/saas.models.agent-work-decision-surface.md +11 -2
  542. package/dist/knowledge/references/saas.models.agent-work-decision-vocabulary.md +20 -3
  543. package/dist/knowledge/references/saas.models.agent-work-output-review.md +3 -3
  544. package/dist/knowledge/references/saas.models.agent-work-override-rate.md +6 -5
  545. package/dist/knowledge/references/saas.models.agent-work-review-config.md +22 -4
  546. package/dist/knowledge/references/saas.models.analytics.value-moments.md +22 -0
  547. package/dist/knowledge/references/saas.models.application-agent-policy.md +28 -0
  548. package/dist/knowledge/references/saas.models.application-entry-points.md +45 -0
  549. package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +21 -0
  550. package/dist/knowledge/references/saas.models.audit.trail-config.md +18 -5
  551. package/dist/knowledge/references/saas.models.auth.relationship-grantor-authentication.md +175 -0
  552. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +4 -4
  553. package/dist/knowledge/references/saas.models.chat-identity-link-host.md +38 -0
  554. package/dist/knowledge/references/saas.models.compliance.ai-use-classification.md +179 -0
  555. package/dist/knowledge/references/saas.models.compliance.ai-use-posture.md +121 -0
  556. package/dist/knowledge/references/saas.models.config.declared-type-renames.md +246 -0
  557. package/dist/knowledge/references/saas.models.config.organization-types.md +54 -74
  558. package/dist/knowledge/references/saas.models.conversation-threads.md +43 -6
  559. package/dist/knowledge/references/saas.models.crypto-keys.floors.md +32 -0
  560. package/dist/knowledge/references/saas.models.crypto-keys.key-management-config.md +130 -0
  561. package/dist/knowledge/references/saas.models.crypto-keys.local-provider.md +29 -0
  562. package/dist/knowledge/references/saas.models.crypto-keys.purpose-descriptor.md +442 -0
  563. package/dist/knowledge/references/saas.models.crypto-keys.purposes.md +91 -0
  564. package/dist/knowledge/references/saas.models.data-mode-read-list.md +24 -79
  565. package/dist/knowledge/references/saas.models.engine-capabilities.md +39 -2
  566. package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +3 -0
  567. package/dist/knowledge/references/saas.models.evaluation-dataset-export.md +16 -9
  568. package/dist/knowledge/references/saas.models.evaluation-export-authorization.md +23 -6
  569. package/dist/knowledge/references/saas.models.external-data-conflict-vocabulary.md +53 -0
  570. package/dist/knowledge/references/saas.models.external-data-pipeline.md +96 -26
  571. package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report-config.md +28 -0
  572. package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report.md +321 -0
  573. package/dist/knowledge/references/saas.models.flows-actors.agent-configuration.md +29 -0
  574. package/dist/knowledge/references/saas.models.flows-actors.agent-content-guardrails.md +150 -0
  575. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +45 -0
  576. package/dist/knowledge/references/saas.models.flows-actors.agent-operation-record.md +154 -0
  577. package/dist/knowledge/references/saas.models.flows-actors.autonomous-agents-vocabulary.md +49 -7
  578. package/dist/knowledge/references/saas.models.flows-actors.chat-agents-vocabulary.md +26 -0
  579. package/dist/knowledge/references/saas.models.flows-actors.decision-card-wording.md +284 -0
  580. package/dist/knowledge/references/saas.models.flows-actors.decision-notice-recorded-cards.md +93 -0
  581. package/dist/knowledge/references/saas.models.flows-actors.human-decision-decider.md +70 -0
  582. package/dist/knowledge/references/saas.models.flows-actors.human-input-form.md +349 -0
  583. package/dist/knowledge/references/saas.models.flows-actors.operation-approval-pending.md +55 -0
  584. package/dist/knowledge/references/saas.models.flows-actors.operation-approval-requirement.md +93 -0
  585. package/dist/knowledge/references/saas.models.flows-actors.review-deadline-vocabulary.md +6 -0
  586. package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +4 -3
  587. package/dist/knowledge/references/saas.models.flows.run-state.md +49 -0
  588. package/dist/knowledge/references/saas.models.flows.runnable-model.md +274 -0
  589. package/dist/knowledge/references/saas.models.frontend-on-demand-capability-contract.md +54 -0
  590. package/dist/knowledge/references/saas.models.guidance-flow.md +1 -1
  591. package/dist/knowledge/references/saas.models.http-api-binding.md +176 -50
  592. package/dist/knowledge/references/saas.models.http-api-binding.rest-write-operations.md +3 -3
  593. package/dist/knowledge/references/saas.models.http-api-population-filter.md +51 -0
  594. package/dist/knowledge/references/saas.models.human-decision-review-marker.md +1 -1
  595. package/dist/knowledge/references/saas.models.inbound-channels.md +75 -3
  596. package/dist/knowledge/references/saas.models.inbound-email-domains.md +5 -5
  597. package/dist/knowledge/references/saas.models.inbound-email.md +2 -2
  598. package/dist/knowledge/references/saas.models.m2m-webhook-events.md +73 -0
  599. package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +1 -1
  600. package/dist/knowledge/references/saas.models.model-cost-summary.md +56 -20
  601. package/dist/knowledge/references/saas.models.notifications.targets.md +28 -3
  602. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +259 -21
  603. package/dist/knowledge/references/saas.models.on-demand-provider-capabilities.md +28 -0
  604. package/dist/knowledge/references/saas.models.organization-agent-policy.md +43 -0
  605. package/dist/knowledge/references/saas.models.organization-assigned-rows-declaration.md +74 -0
  606. package/dist/knowledge/references/saas.models.organization-own-rows-declaration.md +51 -0
  607. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +6 -6
  608. package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +9 -10
  609. package/dist/knowledge/references/saas.models.organizations.identity-declaration.md +201 -0
  610. package/dist/knowledge/references/saas.models.organizations.organization-relationships.md +933 -0
  611. package/dist/knowledge/references/saas.models.organizations.professional-qualification-kinds.md +46 -0
  612. package/dist/knowledge/references/saas.models.organizations.professional-qualifications.md +168 -0
  613. package/dist/knowledge/references/{saas.models.organizations.service-provider-capability-grants.md → saas.models.organizations.relationship-capability-grants.md} +56 -35
  614. package/dist/knowledge/references/saas.models.organizations.relationship-grantor-controls.md +62 -0
  615. package/dist/knowledge/references/saas.models.organizations.relationship-invitations.md +228 -0
  616. package/dist/knowledge/references/saas.models.organizations.relationship-kinds.md +291 -0
  617. package/dist/knowledge/references/saas.models.organizations.relationship-record-separation.md +114 -0
  618. package/dist/knowledge/references/saas.models.privacy.data-residency.md +676 -0
  619. package/dist/knowledge/references/saas.models.privacy.legal-holds.md +114 -7
  620. package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +73 -2
  621. package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +13 -14
  622. package/dist/knowledge/references/saas.models.privacy.retention-binding.md +84 -1
  623. package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +10 -0
  624. package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +5 -3
  625. package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +280 -40
  626. package/dist/knowledge/references/saas.models.privacy.subject-export.md +134 -0
  627. package/dist/knowledge/references/saas.models.provider-capabilities.md +38 -0
  628. package/dist/knowledge/references/saas.models.provider-usage-pricing-authority.md +50 -1
  629. package/dist/knowledge/references/saas.models.providers.capability-activation-policy.md +28 -0
  630. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +20 -6
  631. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +52 -0
  632. package/dist/knowledge/references/saas.models.providers.execute-operation-request.md +25 -0
  633. package/dist/knowledge/references/saas.models.providers.processing-region-reach.md +132 -0
  634. package/dist/knowledge/references/saas.models.providers.processing-region-selection.md +139 -0
  635. package/dist/knowledge/references/saas.models.providers.scope-reauthorization.md +1 -1
  636. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +13 -1
  637. package/dist/knowledge/references/saas.models.rate-limit-configuration.md +4 -4
  638. package/dist/knowledge/references/saas.models.representative-activity.md +69 -0
  639. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +165 -44
  640. package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +24 -0
  641. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +92 -11
  642. package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +4 -2
  643. package/dist/knowledge/references/saas.models.resource-config.operation-base.md +20 -3
  644. package/dist/knowledge/references/saas.models.resource-config.operation-bulk.md +37 -0
  645. package/dist/knowledge/references/saas.models.resource-config.operation-chat-command.md +39 -0
  646. package/dist/knowledge/references/saas.models.resource-config.operation-condition-parameters.md +56 -0
  647. package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +16 -6
  648. package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +1 -1
  649. package/dist/knowledge/references/saas.models.resource-config.operation-required-qualifications.md +30 -0
  650. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +137 -2
  651. package/dist/knowledge/references/saas.models.resource-config.operation-submission-challenge.md +1 -1
  652. package/dist/knowledge/references/saas.models.resource-config.operation-union.md +0 -1
  653. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +1 -1
  654. package/dist/knowledge/references/saas.models.resource-config.record-label-fields.md +23 -0
  655. package/dist/knowledge/references/saas.models.resource-config.request-field-offers.md +104 -0
  656. package/dist/knowledge/references/saas.models.resource-config.required-features.md +20 -0
  657. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +23 -16
  658. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +25 -3
  659. package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +46 -0
  660. package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +32 -15
  661. package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +2 -1
  662. package/dist/knowledge/references/saas.models.resource-config.token-generation.md +1 -1
  663. package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +5 -4
  664. package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +3 -2
  665. package/dist/knowledge/references/saas.models.resource-relationship-builder-parameters.md +6 -2
  666. package/dist/knowledge/references/saas.models.roadmap.phase-horizon.md +31 -0
  667. package/dist/knowledge/references/saas.models.roles.definition.md +12 -1
  668. package/dist/knowledge/references/saas.models.roles.organization-defaults.md +12 -6
  669. package/dist/knowledge/references/saas.models.schema-family-builder.md +32 -4
  670. package/dist/knowledge/references/saas.models.scope-membership.md +2 -2
  671. package/dist/knowledge/references/saas.models.system-of-record-actions.md +65 -1
  672. package/dist/knowledge/references/saas.models.system-of-record-capabilities.md +123 -0
  673. package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +19 -2
  674. package/dist/knowledge/references/saas.models.systems-of-record.md +110 -14
  675. package/dist/knowledge/references/saas.models.work-attribution-vocabulary.md +7 -3
  676. package/dist/knowledge/references/saas.models.work-unit-ref.md +17 -2
  677. package/dist/knowledge/references/saas.public-runtime.contract.md +75 -25
  678. package/dist/knowledge/references/saas.rag.retrieval-refusals.md +3 -2
  679. package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +3 -2
  680. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +13 -0
  681. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +287 -17
  682. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +5 -4
  683. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +30 -2
  684. package/dist/knowledge/references/saas.specifications.engine-resource-sub-domain.md +105 -0
  685. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +22 -4
  686. package/dist/knowledge/references/saas.specifications.processor-register.md +10 -1
  687. package/dist/knowledge/references/saas.specifications.recipient-disclosures.md +111 -2
  688. package/dist/knowledge/references/saas.specifications.recipient-population.md +46 -0
  689. package/dist/knowledge/references/saas.specifications.resource-frontend-configuration-aspect.md +7 -0
  690. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +44 -5
  691. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +21 -7
  692. package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +113 -70
  693. package/dist/knowledge/references/saas.specifications.subject-data-recipients.md +136 -6
  694. package/dist/knowledge/references/saas.specifications.translation-glossary.md +80 -0
  695. package/dist/knowledge/references/saas.website.astro.bridge.md +51 -14
  696. package/dist/knowledge/references/saas.website.astro.head-renderer.md +63 -27
  697. package/dist/knowledge/references/saas.website.astro.i18n-helper.md +39 -10
  698. package/dist/knowledge/references/saas.website.astro.label-key-collector.md +12 -11
  699. package/dist/knowledge/references/saas.website.astro.label-loader.md +77 -14
  700. package/dist/knowledge/references/saas.website.astro.pick-labels-for-page.md +1 -2
  701. package/dist/knowledge/references/saas.website.astro.runtime-helper.md +49 -17
  702. package/dist/knowledge/references/saas.website.astro.site-context.md +17 -8
  703. package/dist/knowledge/references/saas.website.astro.structured-data-renderer.md +29 -8
  704. package/dist/knowledge/references/saas.website.blocks.actions.md +91 -0
  705. package/dist/knowledge/references/saas.website.blocks.band.md +41 -0
  706. package/dist/knowledge/references/saas.website.blocks.bento.md +70 -0
  707. package/dist/knowledge/references/saas.website.blocks.card-grid.md +115 -0
  708. package/dist/knowledge/references/saas.website.blocks.card.md +77 -0
  709. package/dist/knowledge/references/saas.website.blocks.cta-band.md +94 -0
  710. package/dist/knowledge/references/saas.website.blocks.define-block.md +123 -0
  711. package/dist/knowledge/references/saas.website.blocks.definitions.md +132 -0
  712. package/dist/knowledge/references/saas.website.blocks.faq.md +89 -0
  713. package/dist/knowledge/references/saas.website.blocks.feature-row.md +109 -0
  714. package/dist/knowledge/references/saas.website.blocks.hero.md +140 -0
  715. package/dist/knowledge/references/saas.website.blocks.intro.md +68 -0
  716. package/dist/knowledge/references/saas.website.blocks.latest-posts.md +104 -0
  717. package/dist/knowledge/references/saas.website.blocks.marquee.md +76 -0
  718. package/dist/knowledge/references/saas.website.blocks.pricing.md +395 -0
  719. package/dist/knowledge/references/saas.website.blocks.product-tour.md +158 -0
  720. package/dist/knowledge/references/saas.website.blocks.quote-cards.md +64 -0
  721. package/dist/knowledge/references/saas.website.blocks.roadmap.md +108 -0
  722. package/dist/knowledge/references/saas.website.blocks.section-slots.md +64 -0
  723. package/dist/knowledge/references/saas.website.blocks.solution-paths.md +71 -0
  724. package/dist/knowledge/references/saas.website.blocks.stats.md +183 -0
  725. package/dist/knowledge/references/saas.website.blocks.steps.md +69 -0
  726. package/dist/knowledge/references/saas.website.blocks.stylesheet.md +68 -0
  727. package/dist/knowledge/references/saas.website.blocks.tables.md +153 -0
  728. package/dist/knowledge/references/saas.website.blocks.vocabulary.md +227 -0
  729. package/dist/knowledge/references/saas.website.blog.bridge.md +98 -53
  730. package/dist/knowledge/references/saas.website.blog.collection-config.md +105 -49
  731. package/dist/knowledge/references/saas.website.blog.cover-resolver.md +93 -0
  732. package/dist/knowledge/references/saas.website.blog.frontmatter.md +106 -9
  733. package/dist/knowledge/references/saas.website.blog.head-renderer.md +37 -19
  734. package/dist/knowledge/references/saas.website.blog.index-builder.md +63 -0
  735. package/dist/knowledge/references/saas.website.blog.index.md +43 -0
  736. package/dist/knowledge/references/saas.website.blog.post-cover.md +38 -0
  737. package/dist/knowledge/references/saas.website.blog.post-renderer.md +115 -87
  738. package/dist/knowledge/references/saas.website.blog.react-mdx-integration.md +188 -0
  739. package/dist/knowledge/references/saas.website.blog.react-mdx-query.md +26 -0
  740. package/dist/knowledge/references/saas.website.blog.vocabulary-labels.md +113 -0
  741. package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +5 -2
  742. package/dist/knowledge/references/saas.website.config.site-context-loader.md +26 -3
  743. package/dist/knowledge/references/saas.website.consent.banner.md +1 -1
  744. package/dist/knowledge/references/saas.website.consent.context.md +1 -1
  745. package/dist/knowledge/references/saas.website.design-tokens.bundle.md +28 -6
  746. package/dist/knowledge/references/saas.website.design-tokens.colors.md +7 -6
  747. package/dist/knowledge/references/saas.website.design-tokens.compose-function.md +35 -0
  748. package/dist/knowledge/references/saas.website.design-tokens.compose.md +76 -0
  749. package/dist/knowledge/references/saas.website.design-tokens.personality-derivation.md +22 -0
  750. package/dist/knowledge/references/saas.website.design-tokens.personality-lexicon.md +31 -0
  751. package/dist/knowledge/references/saas.website.design-tokens.personality.md +82 -0
  752. package/dist/knowledge/references/saas.website.design-tokens.product.md +122 -0
  753. package/dist/knowledge/references/saas.website.design-tokens.radius.md +12 -1
  754. package/dist/knowledge/references/saas.website.design-tokens.readers.md +58 -0
  755. package/dist/knowledge/references/saas.website.design-tokens.spacing.md +61 -0
  756. package/dist/knowledge/references/saas.website.design-tokens.surface-depth.md +60 -0
  757. package/dist/knowledge/references/saas.website.design-tokens.tones.md +75 -0
  758. package/dist/knowledge/references/saas.website.design-tokens.typography.md +115 -0
  759. package/dist/knowledge/references/saas.website.factories.define-page-manifest.md +23 -21
  760. package/dist/knowledge/references/saas.website.factories.define-section.md +36 -38
  761. package/dist/knowledge/references/saas.website.format.publication-date.md +26 -0
  762. package/dist/knowledge/references/saas.website.label-keys.compose-helper.md +1 -1
  763. package/dist/knowledge/references/saas.website.label-keys.format.md +4 -3
  764. package/dist/knowledge/references/saas.website.label-pack.validator.md +9 -8
  765. package/dist/knowledge/references/saas.website.labels.section-labels.md +34 -0
  766. package/dist/knowledge/references/saas.website.legal.public-document-links.md +19 -4
  767. package/dist/knowledge/references/saas.website.locale-switcher.label-keys.md +35 -0
  768. package/dist/knowledge/references/saas.website.menu.icons.md +123 -0
  769. package/dist/knowledge/references/saas.website.menu.label-keys.md +112 -0
  770. package/dist/knowledge/references/saas.website.menu.schema.md +92 -0
  771. package/dist/knowledge/references/saas.website.menu.vocabulary.md +79 -0
  772. package/dist/knowledge/references/saas.website.motion.demo-player.md +105 -0
  773. package/dist/knowledge/references/saas.website.motion.demo-scenario.md +460 -0
  774. package/dist/knowledge/references/saas.website.motion.demo.md +324 -0
  775. package/dist/knowledge/references/saas.website.motion.element-attributes.md +115 -0
  776. package/dist/knowledge/references/saas.website.motion.reveal-renditions.md +67 -0
  777. package/dist/knowledge/references/saas.website.motion.stylesheet.md +82 -0
  778. package/dist/knowledge/references/saas.website.motion.tempo-table.md +99 -0
  779. package/dist/knowledge/references/saas.website.motion.tokens.md +46 -0
  780. package/dist/knowledge/references/saas.website.motion.vocabulary.md +85 -0
  781. package/dist/knowledge/references/saas.website.page-layout.component.md +34 -8
  782. package/dist/knowledge/references/saas.website.page-manifest.meta-label-keys.md +4 -4
  783. package/dist/knowledge/references/saas.website.page-manifest.route-path.md +1 -1
  784. package/dist/knowledge/references/saas.website.page-manifest.schema.md +25 -29
  785. package/dist/knowledge/references/saas.website.page-manifest.seo.md +1 -1
  786. package/dist/knowledge/references/saas.website.page-navigation.md +44 -0
  787. package/dist/knowledge/references/saas.website.page.context.md +9 -2
  788. package/dist/knowledge/references/saas.website.primitives.button.md +6 -6
  789. package/dist/knowledge/references/saas.website.primitives.heading.md +17 -18
  790. package/dist/knowledge/references/saas.website.primitives.image.md +18 -15
  791. package/dist/knowledge/references/saas.website.primitives.internal-button.md +11 -12
  792. package/dist/knowledge/references/saas.website.primitives.internal-link.md +11 -35
  793. package/dist/knowledge/references/saas.website.primitives.link.md +22 -11
  794. package/dist/knowledge/references/saas.website.primitives.text.md +10 -8
  795. package/dist/knowledge/references/saas.website.product.atoms.md +366 -0
  796. package/dist/knowledge/references/saas.website.product.figures.md +320 -0
  797. package/dist/knowledge/references/saas.website.product.hooks.md +278 -0
  798. package/dist/knowledge/references/saas.website.product.panels.md +324 -0
  799. package/dist/knowledge/references/saas.website.product.stylesheet.md +1086 -0
  800. package/dist/knowledge/references/saas.website.refs.section.md +2 -2
  801. package/dist/knowledge/references/saas.website.root-config.schema.md +34 -17
  802. package/dist/knowledge/references/saas.website.routing.link-target.md +70 -0
  803. package/dist/knowledge/references/saas.website.routing.localized-path.md +15 -8
  804. package/dist/knowledge/references/saas.website.runtime.context.md +44 -17
  805. package/dist/knowledge/references/saas.website.section.component.md +21 -19
  806. package/dist/knowledge/references/saas.website.sections.category-enum.md +21 -2
  807. package/dist/knowledge/references/saas.website.sections.definition-schema.md +47 -39
  808. package/dist/knowledge/references/saas.website.site-footer.menu.md +47 -0
  809. package/dist/knowledge/references/saas.website.site-header.component.md +100 -0
  810. package/dist/knowledge/references/saas.website.site-header.scroll-behavior.md +26 -0
  811. package/dist/knowledge/references/saas.website.stacking.md +86 -0
  812. package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +162 -0
  813. package/dist/knowledge/references/saas.website.use-blog-index.hook.md +27 -0
  814. package/dist/knowledge/references/saas.website.use-label.hook.md +6 -4
  815. package/dist/knowledge/references/service-method.config.md +303 -0
  816. package/dist/knowledge/references/vision.constraint.config.md +4 -2
  817. package/dist/knowledge/references/website-plan.config.md +544 -32
  818. package/dist/knowledge/references/website-plan.menu-placement.md +118 -0
  819. package/dist/knowledge/references/website-plan.page-kind-essentials.md +42 -0
  820. package/dist/knowledge/references/website-plan.page-routes.md +39 -0
  821. package/dist/knowledge/references/workers.node.worker-init-contract.md +4 -2
  822. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +133 -9
  823. package/dist/knowledge/references/zod.decorators.chrome-modes.md +92 -0
  824. package/dist/knowledge/references/zod.decorators.data-categories.md +124 -34
  825. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +99 -6
  826. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +34 -1
  827. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +41 -7
  828. package/dist/knowledge/references/zod.decorators.file-schema.md +10 -8
  829. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +25 -9
  830. package/dist/knowledge/references/zod.decorators.primitive-ui.md +15 -3
  831. package/dist/knowledge/references/zod.decorators.rag-source.md +20 -20
  832. package/dist/knowledge/references/zod.decorators.schema-metadata.md +6 -0
  833. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +52 -18
  834. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +107 -5
  835. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +193 -9
  836. package/dist/knowledge/references/zod.factories.bigdecimal.md +17 -8
  837. package/dist/knowledge/references/zod.factories.code.md +18 -9
  838. package/dist/knowledge/references/zod.factories.duration.md +23 -14
  839. package/dist/knowledge/references/zod.factories.money.md +24 -15
  840. package/dist/knowledge/references/zod.factories.phone.md +23 -14
  841. package/dist/knowledge/references/zod.factories.range.md +5 -1
  842. package/dist/knowledge/references/zod.factories.year-month.md +79 -0
  843. package/dist/knowledge/registries/assurance-authority-bases.json +3 -3
  844. package/dist/knowledge/registries/framework-topics.json +5250 -2565
  845. package/dist/knowledge/registries/playbooks.json +88 -55
  846. package/dist/knowledge/registries/source-tags.json +9347 -4807
  847. package/dist/knowledge/rules/database-migration-obligation.md +10 -5
  848. package/dist/knowledge/rules/live-context-door.md +1 -1
  849. package/dist/knowledge/skills/INDEX.md +62 -33
  850. package/dist/knowledge/skills/agent-work-review/SKILL.md +86 -23
  851. package/dist/knowledge/skills/agent-work-review/references/framework-actor-execution-continuation-api.md +227 -0
  852. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-capture-settings-api.md +2 -2
  853. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-decision-contents-api.md +79 -0
  854. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-output-review-api.md +4 -4
  855. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-override-rate-api.md +6 -5
  856. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-config-api.md +22 -4
  857. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +16 -4
  858. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-vocabulary-api.md +20 -3
  859. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-dataset-export-api.md +16 -9
  860. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-export-authorization-api.md +24 -7
  861. package/dist/knowledge/skills/agent-work-review/references/framework-human-input-form-api.md +376 -0
  862. package/dist/knowledge/skills/ai-use-declaration/SKILL.md +192 -0
  863. package/dist/knowledge/skills/ai-use-declaration/references/choosing-the-domain-and-class.md +73 -0
  864. package/dist/knowledge/skills/ai-use-declaration/references/framework-ai-use-classification-api.md +194 -0
  865. package/dist/knowledge/skills/ai-use-declaration/references/framework-ai-use-posture-api.md +136 -0
  866. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +30 -19
  867. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +48 -13
  868. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +2 -2
  869. package/dist/knowledge/skills/application-database-migrations/SKILL.md +26 -9
  870. package/dist/knowledge/skills/application-database-migrations/references/postgresql-supported-surfaces.md +64 -0
  871. package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +37 -1
  872. package/dist/knowledge/skills/application-roles-authoring/SKILL.md +28 -3
  873. package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +24 -7
  874. package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +22 -1
  875. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +168 -3
  876. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-assigned-rows-declaration-api.md +92 -0
  877. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-organization-identity-declaration-api.md +247 -0
  878. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-own-rows-declaration-api.md +66 -0
  879. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +6 -6
  880. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +6 -0
  881. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +108 -2
  882. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +81 -10
  883. package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +4 -1
  884. package/dist/knowledge/skills/backend-custom-operation/references/declared-refusal-codes.md +95 -0
  885. package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +3 -2
  886. package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +5 -2
  887. package/dist/knowledge/skills/backend-custom-operation/references/framework-core-write-precondition-api.md +73 -0
  888. package/dist/knowledge/skills/backend-custom-operation/references/framework-error-handling-api.md +5 -0
  889. package/dist/knowledge/skills/backend-custom-operation/references/framework-external-effect-reservation-api.md +276 -0
  890. package/dist/knowledge/skills/backend-custom-operation/references/framework-hook-transaction-posture-api.md +79 -0
  891. package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +20 -3
  892. package/dist/knowledge/skills/backend-custom-operation/references/framework-target-authority-api.md +61 -0
  893. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +368 -1
  894. package/dist/knowledge/skills/blueprint-authoring/SKILL.md +191 -0
  895. package/dist/knowledge/skills/blueprint-authoring/references/blueprint-content-kinds.md +29 -0
  896. package/dist/knowledge/skills/blueprint-authoring/references/framework-blueprint-definition-api.md +490 -0
  897. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +127 -2
  898. package/dist/knowledge/skills/brand-logo-authoring/references/brand-authoring-decisions.md +15 -3
  899. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +26 -8
  900. package/dist/knowledge/skills/brand-logo-authoring/references/framework-style-word-lexicon-api.md +126 -0
  901. package/dist/knowledge/skills/brand-name-screening/SKILL.md +13 -2
  902. package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +30 -3
  903. package/dist/knowledge/skills/chat-agent-conversations/SKILL.md +166 -0
  904. package/dist/knowledge/skills/chat-agent-conversations/references/framework-chat-conversations-api.md +307 -0
  905. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -1
  906. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +8 -6
  907. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +179 -37
  908. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +4 -3
  909. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +13 -0
  910. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +48 -11
  911. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +10 -1
  912. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +896 -0
  913. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +184 -4
  914. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-population.md +46 -0
  915. package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +487 -61
  916. package/dist/knowledge/skills/config-app-shell/SKILL.md +62 -29
  917. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +20 -18
  918. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-building-blocks-api.md +7 -3
  919. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-hosted-components-api.md +13 -0
  920. package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +20 -0
  921. package/dist/knowledge/skills/config-app-shell/references/framework-command-menu-omnibox-api.md +3 -3
  922. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +21 -6
  923. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +24 -22
  924. package/dist/knowledge/skills/config-app-shell/references/framework-shell-layout-api.md +528 -0
  925. package/dist/knowledge/skills/config-design-system/SKILL.md +245 -162
  926. package/dist/knowledge/skills/config-design-system/references/design-system-file.md +5 -1
  927. package/dist/knowledge/skills/config-design-system/references/framework-focus-indicator-api.md +182 -0
  928. package/dist/knowledge/skills/config-design-system/references/framework-palette-contrast-api.md +195 -0
  929. package/dist/knowledge/skills/config-design-system/references/framework-palette-derivation-api.md +108 -0
  930. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +38 -0
  931. package/dist/knowledge/skills/config-design-system/references/framework-theme-composition-api.md +278 -0
  932. package/dist/knowledge/skills/config-design-system/references/theme-design-principles.md +202 -0
  933. package/dist/knowledge/skills/config-navigation/SKILL.md +2 -0
  934. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +16 -5
  935. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +1 -1
  936. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +12 -1
  937. package/dist/knowledge/skills/config-navigation/references/one-entry-per-concept.md +101 -0
  938. package/dist/knowledge/skills/config-saas/SKILL.md +4 -2
  939. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +51 -6
  940. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +18 -5
  941. package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +333 -0
  942. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +29 -1
  943. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +83 -11
  944. package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +21 -19
  945. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +26 -10
  946. package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +1370 -0
  947. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +77 -2
  948. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +171 -26
  949. package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +22 -0
  950. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +126 -32
  951. package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +1 -1
  952. package/dist/knowledge/skills/config-saas-backend/SKILL.md +16 -4
  953. package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +9 -10
  954. package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +5 -1
  955. package/dist/knowledge/skills/config-saas-backend/references/framework-declared-type-renames-api.md +261 -0
  956. package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +6 -4
  957. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +167 -84
  958. package/dist/knowledge/skills/config-saas-backend/references/renaming-organization-and-user-types.md +69 -0
  959. package/dist/knowledge/skills/configure-billing/SKILL.md +20 -0
  960. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +38 -4
  961. package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +2 -0
  962. package/dist/knowledge/skills/configure-billing/references/framework-metered-usage-recording-api.md +109 -0
  963. package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +4 -1
  964. package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +18 -2
  965. package/dist/knowledge/skills/electronic-signature-deliverables/SKILL.md +131 -0
  966. package/dist/knowledge/skills/electronic-signature-deliverables/references/what-makes-a-request-signed.md +61 -0
  967. package/dist/knowledge/skills/email-add-template/SKILL.md +47 -6
  968. package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +11 -8
  969. package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +10 -2
  970. package/dist/knowledge/skills/email-add-template/references/framework-email-template-api.md +134 -0
  971. package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +28 -0
  972. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +102 -23
  973. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +103 -14
  974. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +35 -4
  975. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +98 -9
  976. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +71 -16
  977. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-autonomous-agent-api.md +160 -23
  978. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-inbound-agents-api.md +10 -3
  979. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/tool-posture.md +14 -2
  980. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +298 -26
  981. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +78 -19
  982. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-behavior-reports-api.md +455 -0
  983. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +446 -0
  984. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-operation-record-api.md +208 -0
  985. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-suspension-api.md +174 -0
  986. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-ask-person-tool-api.md +121 -0
  987. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +21 -0
  988. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +10 -3
  989. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-realtime-catalog.md +69 -0
  990. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +695 -11
  991. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +124 -6
  992. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-model-spend-limits-api.md +276 -0
  993. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-present-records-tool-api.md +150 -0
  994. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-retrieval-tool-api.md +251 -0
  995. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +120 -16
  996. package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +339 -0
  997. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-flow-model-api.md +283 -0
  998. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +134 -0
  999. package/dist/knowledge/skills/flows-actors-declared-flow/references/step-kinds.md +16 -0
  1000. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +91 -5
  1001. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +78 -1
  1002. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +16 -3
  1003. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +13 -6
  1004. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +5 -4
  1005. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +29 -19
  1006. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +166 -21
  1007. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +1 -1
  1008. package/dist/knowledge/skills/human-decision-notices/SKILL.md +150 -0
  1009. package/dist/knowledge/skills/human-decision-notices/references/framework-decision-card-wording-api.md +292 -0
  1010. package/dist/knowledge/skills/human-decision-notices/references/framework-decision-notice-handler-api.md +340 -0
  1011. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +17 -1
  1012. package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +39 -0
  1013. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +1 -1
  1014. package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +39 -0
  1015. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +35 -3
  1016. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +39 -0
  1017. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-translation-glossary-api.md +87 -0
  1018. package/dist/knowledge/skills/inbound-channels/SKILL.md +93 -13
  1019. package/dist/knowledge/skills/inbound-channels/references/email-channel.md +49 -4
  1020. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +245 -27
  1021. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-email-api.md +8 -8
  1022. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +471 -6
  1023. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-pipelines-api.md +73 -0
  1024. package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +44 -5
  1025. package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +39 -16
  1026. package/dist/knowledge/skills/inbound-channels/references/sms-channel.md +93 -0
  1027. package/dist/knowledge/skills/infra-environment-config/SKILL.md +226 -73
  1028. package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +12 -14
  1029. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +140 -7
  1030. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +2 -1
  1031. package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +370 -0
  1032. package/dist/knowledge/skills/layout-2d-adoption/SKILL.md +158 -0
  1033. package/dist/knowledge/skills/layout-2d-adoption/references/choosing-a-layout.md +43 -0
  1034. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-authoring-api.md +167 -0
  1035. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-registration-api.md +101 -0
  1036. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-settings-api.md +59 -0
  1037. package/dist/knowledge/skills/layout-2d-adoption/references/framework-shell-motion-api.md +415 -0
  1038. package/dist/knowledge/skills/layout-3d-adoption/SKILL.md +1 -0
  1039. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-focal-plane-settings-api.md +16 -0
  1040. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +72 -0
  1041. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-contract-api.md +65 -32
  1042. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-registration-api.md +14 -36
  1043. package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-building-blocks-api.md +7 -3
  1044. package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +2 -2
  1045. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +12 -9
  1046. package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +7 -5
  1047. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +2 -2
  1048. package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +18 -10
  1049. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +7 -7
  1050. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +14 -1
  1051. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +33 -2
  1052. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +42 -2
  1053. package/dist/knowledge/skills/market-generation-cli/SKILL.md +49 -7
  1054. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +63 -9
  1055. package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +1 -1
  1056. package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +2 -2
  1057. package/dist/knowledge/skills/model-cost-attribution/SKILL.md +43 -11
  1058. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +58 -3
  1059. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-summary-api.md +57 -21
  1060. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-attribution-api.md +7 -3
  1061. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +257 -46
  1062. package/dist/knowledge/skills/module-companion-exports/SKILL.md +1 -0
  1063. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +30 -2
  1064. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +110 -1
  1065. package/dist/knowledge/skills/module-relationships/SKILL.md +143 -119
  1066. package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +8 -4
  1067. package/dist/knowledge/skills/organization-relationships/SKILL.md +668 -0
  1068. package/dist/knowledge/skills/organization-relationships/references/framework-organization-relationships-api.md +1259 -0
  1069. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-capability-grants-api.md +243 -0
  1070. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-grantor-authentication-api.md +284 -0
  1071. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-kinds-api.md +555 -0
  1072. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-record-separation-api.md +163 -0
  1073. package/dist/knowledge/skills/organization-relationships/references/framework-representative-activity-api.md +149 -0
  1074. package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-collection-template-api.md +5 -3
  1075. package/dist/knowledge/skills/professional-qualifications/SKILL.md +173 -0
  1076. package/dist/knowledge/skills/professional-qualifications/references/choosing-who-may-decide.md +53 -0
  1077. package/dist/knowledge/skills/professional-qualifications/references/framework-operation-approval-requirement-api.md +98 -0
  1078. package/dist/knowledge/skills/professional-qualifications/references/framework-operation-required-qualifications-api.md +39 -0
  1079. package/dist/knowledge/skills/professional-qualifications/references/framework-professional-qualifications-api.md +223 -0
  1080. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +1 -1
  1081. package/dist/knowledge/skills/provider-address-lookup/references/framework-browser-operation-policy-api.md +3 -3
  1082. package/dist/knowledge/skills/provider-backend-package/SKILL.md +388 -11
  1083. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +31 -28
  1084. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-augmentation-api.md +16 -0
  1085. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-compliance-state-collector-api.md +96 -0
  1086. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-configuration-check-api.md +130 -0
  1087. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +13 -0
  1088. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-inbound-endpoint-api.md +755 -0
  1089. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +235 -0
  1090. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +6 -0
  1091. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-processing-region-api.md +340 -0
  1092. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +72 -8
  1093. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-subject-erasure-effect-api.md +222 -0
  1094. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +9 -5
  1095. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +11 -2
  1096. package/dist/knowledge/skills/provider-frontend-module/SKILL.md +50 -5
  1097. package/dist/knowledge/skills/provider-frontend-module/references/framework-on-demand-capabilities-api.md +306 -0
  1098. package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +11 -3
  1099. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +41 -15
  1100. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +56 -18
  1101. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +1 -1
  1102. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +143 -25
  1103. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +6 -0
  1104. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-scope-reauthorization-api.md +9 -6
  1105. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +1275 -4
  1106. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +71 -35
  1107. package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +27 -13
  1108. package/dist/knowledge/skills/resource-add-field/SKILL.md +7 -0
  1109. package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +32 -12
  1110. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +451 -67
  1111. package/dist/knowledge/skills/resource-add-resource/SKILL.md +57 -8
  1112. package/dist/knowledge/skills/resource-add-resource/references/framework-engine-api-reference-categories-api.md +119 -0
  1113. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +165 -44
  1114. package/dist/knowledge/skills/resource-chat-commands/SKILL.md +138 -0
  1115. package/dist/knowledge/skills/resource-chat-commands/references/framework-resource-chat-command-contract.md +72 -0
  1116. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +171 -7
  1117. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +4 -4
  1118. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +17 -8
  1119. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +8 -2
  1120. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-approval-api.md +371 -0
  1121. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +51 -7
  1122. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-bulk-api.md +163 -0
  1123. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +66 -27
  1124. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +200 -61
  1125. package/dist/knowledge/skills/resource-config-wiring/references/framework-request-field-offers-api.md +168 -0
  1126. package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +20 -0
  1127. package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +8 -3
  1128. package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +34 -10
  1129. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +8 -6
  1130. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +351 -159
  1131. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +160 -2
  1132. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +440 -119
  1133. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +426 -32
  1134. package/dist/knowledge/skills/resource-config-wiring/references/framework-webhook-events-api.md +116 -0
  1135. package/dist/knowledge/skills/resource-custom-view/SKILL.md +126 -1
  1136. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +344 -62
  1137. package/dist/knowledge/skills/resource-custom-view/references/framework-backend-refusal-api.md +110 -0
  1138. package/dist/knowledge/skills/resource-external-data/SKILL.md +326 -76
  1139. package/dist/knowledge/skills/resource-external-data/references/bidirectional-pipelines.md +335 -0
  1140. package/dist/knowledge/skills/resource-external-data/references/declared-expressions.md +18 -6
  1141. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +71 -12
  1142. package/dist/knowledge/skills/resource-external-data/references/facet-augmentations.md +6 -0
  1143. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +96 -26
  1144. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +257 -57
  1145. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +111 -11
  1146. package/dist/knowledge/skills/resource-external-data/references/framework-system-of-record-capabilities-api.md +147 -0
  1147. package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +30 -4
  1148. package/dist/knowledge/skills/resource-external-data/references/local-test-doubles.md +121 -0
  1149. package/dist/knowledge/skills/resource-external-data/references/odata-v2-sources.md +21 -9
  1150. package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +62 -15
  1151. package/dist/knowledge/skills/resource-external-data/references/partition-from-the-domain-plan.md +230 -0
  1152. package/dist/knowledge/skills/resource-external-data/references/presenting-a-copy-and-a-read-through.md +73 -0
  1153. package/dist/knowledge/skills/resource-external-data/references/provenance-cue.md +18 -2
  1154. package/dist/knowledge/skills/resource-external-data/references/rate-budgets-and-pacing.md +3 -1
  1155. package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +65 -18
  1156. package/dist/knowledge/skills/resource-external-data/references/remote-references.md +17 -7
  1157. package/dist/knowledge/skills/resource-external-data/references/requested-keys.md +104 -0
  1158. package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +77 -7
  1159. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +25 -4
  1160. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +2 -2
  1161. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +1 -1
  1162. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +18 -9
  1163. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +42 -3
  1164. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +29 -2
  1165. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +20 -20
  1166. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +21 -3
  1167. package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +114 -7
  1168. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +84 -1
  1169. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +10 -0
  1170. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +5 -3
  1171. package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +46 -0
  1172. package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +14 -2
  1173. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +27 -11
  1174. package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +23 -7
  1175. package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +13 -8
  1176. package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +78 -17
  1177. package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +4 -0
  1178. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +105 -6
  1179. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +19 -22
  1180. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +150 -35
  1181. package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +32 -4
  1182. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +58 -18
  1183. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +107 -5
  1184. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +200 -69
  1185. package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +2 -1
  1186. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +326 -18
  1187. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +7 -0
  1188. package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +72 -0
  1189. package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +42 -2
  1190. package/dist/knowledge/skills/resource-status-lifecycle/references/framework-operation-condition-parameters-api.md +67 -0
  1191. package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +16 -12
  1192. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +219 -77
  1193. package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +105 -24
  1194. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +131 -1
  1195. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +41 -7
  1196. package/dist/knowledge/skills/resource-ui-behavior/references/framework-field-tiles-api.md +114 -0
  1197. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +428 -72
  1198. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +25 -9
  1199. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +15 -3
  1200. package/dist/knowledge/skills/resource-ui-behavior/references/framework-record-page-parts-api.md +155 -0
  1201. package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +223 -6
  1202. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +186 -65
  1203. package/dist/knowledge/skills/resource-ui-behavior/references/framework-section-stages-api.md +102 -0
  1204. package/dist/knowledge/skills/resource-ui-behavior/references/record-page-anatomy.md +138 -0
  1205. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +89 -32
  1206. package/dist/knowledge/skills/resource-ui-behavior/references/visual-quality-rubric.md +73 -0
  1207. package/dist/knowledge/skills/resource-ui-behavior/references/workflow-record-page.md +264 -0
  1208. package/dist/knowledge/skills/seeding-authoring/SKILL.md +24 -4
  1209. package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +12 -0
  1210. package/dist/knowledge/skills/seeding-authoring/references/data-seeding-mode-picker.md +16 -1
  1211. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +7 -6
  1212. package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +15 -8
  1213. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +3 -0
  1214. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +48 -11
  1215. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +183 -32
  1216. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +72 -13
  1217. package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +5 -4
  1218. package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +5 -4
  1219. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +1 -0
  1220. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +30 -2
  1221. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +15 -7
  1222. package/dist/knowledge/skills/spec-resource-update/SKILL.md +26 -0
  1223. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +186 -83
  1224. package/dist/knowledge/skills/spec-resource-update/references/workflow-record-page-specification.md +237 -0
  1225. package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +113 -70
  1226. package/dist/knowledge/skills/subject-data-export/SKILL.md +176 -0
  1227. package/dist/knowledge/skills/subject-data-export/references/file-content-exclusions.md +15 -0
  1228. package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-api.md +142 -0
  1229. package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-archive-api.md +33 -0
  1230. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +14 -5
  1231. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +10 -1
  1232. package/dist/knowledge/skills/views-add-custom-view/references/framework-focus-indicator-api.md +145 -0
  1233. package/dist/knowledge/skills/views-app-level/SKILL.md +3 -1
  1234. package/dist/knowledge/skills/views-app-level/references/workflow-home.md +373 -0
  1235. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +41 -5
  1236. package/dist/knowledge/skills/views-chart-authoring/references/framework-chart-view-contracts-api.md +13 -0
  1237. package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +9 -5
  1238. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +15 -4
  1239. package/dist/knowledge/skills/views-composite-authoring/references/framework-chart-dashboard-api.md +244 -0
  1240. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +11 -2
  1241. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +57 -3
  1242. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +61 -25
  1243. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +253 -78
  1244. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +1105 -222
  1245. package/dist/knowledge/skills/website-building-blocks/SKILL.md +337 -0
  1246. package/dist/knowledge/skills/website-building-blocks/references/framework-website-blocks-api.md +3050 -0
  1247. package/dist/knowledge/skills/website-building-blocks/references/framework-website-demo-examples.md +627 -0
  1248. package/dist/knowledge/skills/website-building-blocks/references/framework-website-product-kit-api.md +3309 -0
  1249. package/dist/knowledge/skills/website-building-blocks/references/website-visual-quality-rubric.md +75 -0
  1250. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +42 -19
  1251. package/dist/knowledge/skills/website-bundle-discipline/references/example-website-button-override.md +8 -12
  1252. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +20 -5
  1253. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +84 -28
  1254. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +67 -64
  1255. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +58 -23
  1256. package/dist/knowledge/skills/website-inbound-contact-forms/references/framework-submission-challenge-api.md +5 -1
  1257. package/dist/knowledge/skills/website-label-pack/SKILL.md +43 -21
  1258. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +112 -77
  1259. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +24 -13
  1260. package/dist/knowledge/skills/website-motion-design/SKILL.md +277 -0
  1261. package/dist/knowledge/skills/website-motion-design/references/framework-motion-api.md +1562 -0
  1262. package/dist/knowledge/skills/website-motion-design/references/industry-practice.md +28 -0
  1263. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +255 -397
  1264. package/dist/knowledge/skills/website-navigation-authoring/references/framework-menu-api.md +712 -0
  1265. package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +28 -6
  1266. package/dist/knowledge/skills/website-navigation-authoring/references/menu-keys-and-styling.md +151 -0
  1267. package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +131 -326
  1268. package/dist/knowledge/skills/website-page-authoring/SKILL.md +160 -67
  1269. package/dist/knowledge/skills/website-page-authoring/references/framework-page-kinds-api.md +982 -0
  1270. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +29 -5
  1271. package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +19 -0
  1272. package/dist/knowledge/skills/website-page-authoring/references/page-kinds.md +118 -0
  1273. package/dist/knowledge/skills/website-page-variants/SKILL.md +70 -69
  1274. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +48 -28
  1275. package/dist/knowledge/skills/website-section-comparison/SKILL.md +1171 -0
  1276. package/dist/knowledge/skills/website-section-comparison/references/define-website-section-api.md +679 -0
  1277. package/dist/knowledge/skills/website-section-comparison/references/framework-website-tables-api.md +487 -0
  1278. package/dist/knowledge/skills/website-section-contact/SKILL.md +409 -186
  1279. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +197 -119
  1280. package/dist/knowledge/skills/website-section-cta/SKILL.md +399 -235
  1281. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +197 -119
  1282. package/dist/knowledge/skills/website-section-faq/SKILL.md +562 -303
  1283. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +197 -119
  1284. package/dist/knowledge/skills/website-section-faq/references/framework-website-faq-api.md +489 -0
  1285. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +648 -275
  1286. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +197 -119
  1287. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +573 -265
  1288. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +197 -119
  1289. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +533 -234
  1290. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +197 -119
  1291. package/dist/knowledge/skills/website-section-hero/SKILL.md +604 -333
  1292. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +198 -120
  1293. package/dist/knowledge/skills/website-section-how-it-works/SKILL.md +1150 -0
  1294. package/dist/knowledge/skills/website-section-how-it-works/references/define-website-section-api.md +679 -0
  1295. package/dist/knowledge/skills/website-section-how-it-works/references/framework-website-steps-api.md +337 -0
  1296. package/dist/knowledge/skills/website-section-integrations/SKILL.md +974 -0
  1297. package/dist/knowledge/skills/website-section-integrations/references/define-website-section-api.md +679 -0
  1298. package/dist/knowledge/skills/website-section-integrations/references/framework-website-marquee-api.md +825 -0
  1299. package/dist/knowledge/skills/website-section-latest-posts/SKILL.md +928 -0
  1300. package/dist/knowledge/skills/website-section-latest-posts/references/define-website-section-api.md +679 -0
  1301. package/dist/knowledge/skills/website-section-latest-posts/references/framework-website-latest-posts-api.md +465 -0
  1302. package/dist/knowledge/skills/website-section-pricing/SKILL.md +594 -379
  1303. package/dist/knowledge/skills/website-section-pricing/examples/pricing-offers.example.md +189 -0
  1304. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +197 -119
  1305. package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +5 -2
  1306. package/dist/knowledge/skills/website-section-pricing/references/framework-website-pricing-api.md +670 -0
  1307. package/dist/knowledge/skills/website-section-problem/SKILL.md +1150 -0
  1308. package/dist/knowledge/skills/website-section-problem/references/define-website-section-api.md +679 -0
  1309. package/dist/knowledge/skills/website-section-problem/references/framework-website-card-grid-api.md +664 -0
  1310. package/dist/knowledge/skills/website-section-product-showcase/SKILL.md +1322 -0
  1311. package/dist/knowledge/skills/website-section-product-showcase/references/define-website-section-api.md +679 -0
  1312. package/dist/knowledge/skills/website-section-product-showcase/references/framework-website-card-grid-api.md +533 -0
  1313. package/dist/knowledge/skills/website-section-product-showcase/references/framework-website-product-tour-api.md +917 -0
  1314. package/dist/knowledge/skills/website-section-roadmap/SKILL.md +1133 -0
  1315. package/dist/knowledge/skills/website-section-roadmap/references/define-website-section-api.md +679 -0
  1316. package/dist/knowledge/skills/website-section-roadmap/references/framework-website-roadmap-api.md +475 -0
  1317. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +740 -316
  1318. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +197 -119
  1319. package/dist/knowledge/skills/website-section-social-proof/references/framework-website-quote-cards-api.md +623 -0
  1320. package/dist/knowledge/skills/website-section-solution-paths/SKILL.md +1057 -0
  1321. package/dist/knowledge/skills/website-section-solution-paths/references/define-website-section-api.md +679 -0
  1322. package/dist/knowledge/skills/website-section-solution-paths/references/framework-website-solution-paths-api.md +477 -0
  1323. package/dist/knowledge/skills/website-section-stats/SKILL.md +1086 -0
  1324. package/dist/knowledge/skills/website-section-stats/references/define-website-section-api.md +679 -0
  1325. package/dist/knowledge/skills/website-section-stats/references/framework-website-stats-api.md +517 -0
  1326. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +183 -67
  1327. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +576 -57
  1328. package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +1 -1
  1329. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +6 -94
  1330. package/dist/knowledge/skills/website-theme-authoring/SKILL.md +226 -0
  1331. package/dist/knowledge/skills/website-theme-authoring/references/framework-website-theme-api.md +893 -0
  1332. package/dist/knowledge/skills/worker-authoring/SKILL.md +4 -2
  1333. package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +4 -2
  1334. package/dist/knowledge/topic-index.json +17998 -8568
  1335. package/dist/tsconfig.build.tsbuildinfo +1 -1
  1336. package/package.json +6 -6
  1337. package/dist/knowledge/references/example.organizations.serves-as-provider.md +0 -12
  1338. package/dist/knowledge/references/saas.models.auth.service-provider-client-authentication.md +0 -169
  1339. package/dist/knowledge/references/saas.models.organizations.service-provider-activity-feed.md +0 -121
  1340. package/dist/knowledge/references/saas.models.organizations.service-provider-client-controls.md +0 -49
  1341. package/dist/knowledge/references/saas.models.organizations.service-provider-relationships.md +0 -567
  1342. package/dist/knowledge/references/saas.website.root-config.navigation.md +0 -37
  1343. package/dist/knowledge/skills/service-provider-relationships/SKILL.md +0 -455
  1344. package/dist/knowledge/skills/service-provider-relationships/references/framework-organization-types-api.md +0 -270
  1345. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-activity-feed-api.md +0 -129
  1346. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-capability-grants-api.md +0 -161
  1347. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-client-authentication-api.md +0 -224
  1348. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-relationships-api.md +0 -576
  1349. package/dist/tsconfig.tsbuildinfo +0 -1
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "ref": "bottom_up.website-plan",
3
- "version": "0.2.1",
3
+ "version": "0.5.1",
4
4
  "phase": "bottom_up",
5
- "intent": "Website plan — decide WHAT THE MARKETING WEBSITE SAYS for this application: which pages it has, what each page is for and who it is written for, and the sections that carry each page's argument in reading order, each drawing on the market entries the top-down lane authored (benefits, proofs, objections, jobs, pains, ICPs, tones of voice). Runs only once the capability composition decides the website is NEEDED (a declined website is never planned, and a plan landed before a later decline is set aside). A section's KIND (hero, benefits summary, benefit in detail, pricing, proof, objections answered, call to action, closing call to action, contact) names the shipped `website-section-*` skill that authors it, so the build lane can bind each emitted task to its skill without a model naming folders. Produces the plan; `bottom_up.build-decompose` turns it into the page and section tasks a coding agent runs, and the `add-website` composition scenario is what creates the `website/` workspace they write in.",
5
+ "intent": "Website plan — decide WHAT THE MARKETING WEBSITE SAYS for this application: which pages it has and the KIND of each (home, product overview, product area, solution by role / industry / use case / company size, pricing, contact, company, security, blog — the kind derives its route, its menu placement and its essential sections), what each page is for and who it is written for, and the sections that carry each page's argument in reading order, each drawing on the market entries the top-down lane authored (benefits, proofs, objections, jobs, pains, ICPs, tones of voice). Runs only once the capability composition decides the website is NEEDED (a declined website is never planned, and a plan landed before a later decline is set aside). A section's KIND (hero, benefits summary, benefit in detail, pricing, proof, objections answered, call to action, closing call to action, contact, the problem, how it works, the product shown, paths by audience, comparison, facts in figures, integrations, latest posts, roadmap) names the shipped `website-section-*` skill that authors it, so the build lane can bind each emitted task to its skill without a model naming folders. Every capability, figure and name the plan asks a section to state must be one the application declares (its roadmap, requirements, document facts and integration plan), never a claim the marketing material makes alone. Produces the plan; `bottom_up.build-decompose` turns it into the page and section tasks a coding agent runs, and the `add-website` composition scenario is what creates the `website/` workspace they write in.",
6
6
  "preconditions": [
7
7
  {
8
8
  "kind": "artifact_exists",
@@ -42,9 +42,25 @@
42
42
  {
43
43
  "family": "vision-brief"
44
44
  },
45
+ {
46
+ "family": "roadmap"
47
+ },
45
48
  {
46
49
  "family": "requirements"
47
50
  },
51
+ {
52
+ "family": "document-facts"
53
+ },
54
+ {
55
+ "family": "domain-plan",
56
+ "aspects": [
57
+ "domain-plan.resource",
58
+ "domain-plan.lifecycle"
59
+ ]
60
+ },
61
+ {
62
+ "family": "integration-plan"
63
+ },
48
64
  {
49
65
  "family": "website-plan"
50
66
  }
@@ -58,10 +74,11 @@
58
74
  ],
59
75
  "stepOutputs": [],
60
76
  "method": {
61
- "guidance": "# Website Plan — What the Marketing Site Says\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## Where you are in the journey\n\nThe top-down lane has produced a market snapshot — ICPs, jobs, pains, gains, benefits with their\nweighting, positioning per ICP, tones of voice, proofs and objections — and a brand. The capability\ncomposition has decided whether this application has a marketing website. You decide **what that\nsite says**: its pages, and the sections that carry each page's argument.\n\nYou do not write the site. `bottom_up.build-decompose` turns each page and each section into a\nbuild task, and a coding agent authors it against the shipped `website-*` skills. The `website/`\nworkspace itself is composed by the `add-website` scenario, which the foundation applies from the\nsame capability composition you read here.\n\n## Step 1 — Read the capability composition FIRST\n\nFind the `add-website` decision. This playbook runs only once the composition decides it is\n**NEEDED**: its eligibility is gated on that decision, so a declined website is never planned, and a\nplan landed while it was needed is set aside for every reader if the composition later declines it.\n\n- **Needed** (the normal case): `disposition: PLANNED`, and continue.\n- **Declined** in the record you are given (it changed after you were started): land a plan with\n `disposition: NOT_APPLICABLE`, no pages, and a `rationale` naming what the composition said. Do not\n plan a site the application will never compose — the pages would become tasks with nowhere to write.\n\n## Step 2 — Decide the pages, from what the product actually declares\n\nA page exists because something the application declared needs a place to be said. Derive first,\nand invent nothing:\n\n| page | exists when |\n|---|---|\n| the landing page | always — it is the origin every canonical URL derives from |\n| a pricing page | the business model declares pricing plans |\n| a features page | the market snapshot carries benefits worth arguing one at a time |\n| a contact page | the product's audience buys through a conversation (an inbound channel, a legal-entity ICP) |\n\nEach page names the ICPs it is **written for** and the tone of voice it speaks in, both by their\nmarket-snapshot refs. A page written for everybody is written for nobody: the positioning the\nmarket pass produced is per ICP, and a page that names none cannot use it.\n\n## Step 3 — Compose each page's sections, in reading order\n\nOrder is the plan's substance. A page opens on a **HERO** — the promise, before any detail — and\nargues from there. The section kinds are closed, and each one names the skill that authors it:\n\n| kind | what it does |\n|---|---|\n| `HERO` | the opening promise: headline, sub-headline, primary call to action |\n| `FEATURE_BENEFIT_SUMMARY` | the benefits in one line each, for a reader who will not read the detail |\n| `FEATURE_DETAIL` | one benefit argued: the job it advances, the pain it relieves, what the product does |\n| `PRICING` | the plans, as the business model declares them |\n| `SOCIAL_PROOF` | the proofs the market pass authored |\n| `FAQ` | the objections, answered |\n| `CTA` | a call to action inside the page's flow |\n| `FOOTER_CTA` | the closing call to action |\n| `CONTACT` | a way to reach a human |\n\n**Every section names the market entries it draws on** (`drawsOnRefs`) — the benefit, proof,\nobjection, job, pain, ICP or tone refs, exactly as the snapshot authored them. That is what makes a\nclaim checkable: a reader opens the snapshot and finds the entry. A section that draws on nothing is\na section somebody invented, and the validator reports a page where no section names anything.\n\n**A section that says what the product DOES names the requirement behind it** (`backedByRequirementRefs`).\nA market benefit says what a buyer wants; it does not say the product delivers it. An earlier site\npromised \"country workflow guidance with its limits stated\", drawn from a benefit, while the product\nshipped an empty page for an administrator to write guidance into.\n\n- Every `FEATURE_DETAIL` and `FEATURE_BENEFIT_SUMMARY` section cites the requirements (functional, or\n non-functional such as working on a phone in the field), by their refs in your `requirements` input,\n that commit the product to what it describes. The validator reports one that cites none.\n- Any other section (a hero, an FAQ, a pricing table) may cite requirements too, and should when its\n copy will say what the product does. A section that cites none describes no capability as available.\n- A citation is necessary, not sufficient. When the section is built, its author is told where each\n cited requirement stands: delivered, still being built, reported unmet by the run that built it, or\n only on a later roadmap phase. Only what is delivered is written as available; the rest is written as\n planned. So cite what the section is ABOUT, and do not drop a requirement because it is not built yet.\n- A benefit no requirement backs is not presented as a capability: leave it out, or give it a section\n whose purpose says it is planned.\n\nLead with fit. The brief carries the computed fit matrix beside each benefit's authored Kano\ncategory; a page for an ICP argues the benefits that score for THAT ICP first, rather than the ones\nthe model finds most interesting.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every page ref that still has a reason to exist — build tasks\nname them, and a ref that moves orphans the task that produced its page. Add, sharpen and reorder;\ndo not renumber.\n\n## What you emit\n\n- The **website plan** at `specifications/src/website-plan/index.ts` — a disposition with its\n rationale, and the pages in navigation order, each with its purpose, audience, tone and ordered\n sections.\n\n## Verification\n\n- Every `drawsOnRefs` entry names an entry that exists in the market snapshot.\n- Every `FEATURE_DETAIL` and `FEATURE_BENEFIT_SUMMARY` section names at least one `backedByRequirementRefs`\n entry, and each names a requirement in the requirements.\n- Every page opens on a `HERO`, and exactly one page reads as the landing page.\n- `rg -n \"sectionRef\" specifications/src/website-plan/index.ts | wc -l` — the number of website\n section tasks the build lane will emit.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem: naming a path here would be an instruction answered from\nrecollection (#1435). So each skill is named by its REF, and only `website-page-authoring` reaches\nthis step as a BODY (`method.skillBodyRefs`) — it is the one contract the plan must not contradict,\nbecause it says what a page IS in this engine: a manifest, a route adapter, a sections file and a\nlabel pack that fails the build closed on a missing key. A page planned against anything else is a\npage the build lane cannot author.\n\nThe others below are the contracts the CODING AGENT opens when it builds each task, listed so a\nreader knows the plan's decisions land somewhere:\n\n- `website-navigation-authoring` — how pages reach each other, which bounds how many top-level pages are worth planning.\n- `website-seo-aeo-geo` — what a page owes a search engine and an answer engine.\n- `website-label-pack` — every string a section renders is a label key, and the build fails closed on a missing one.\n- `website-marketing-metadata-extension` — the metadata a page carries beyond its sections.\n- `website-section-*` — one per section KIND, bound to the emitted task by `WEBSITE_SECTION_SKILL_REF`.\n- `market-positioning-authoring`, `market-tone-of-voice`, `market-proof-and-objection` — the market\n vocabularies a section draws on, which arrive here as the market snapshot itself rather than as prose.\n",
77
+ "guidance": "# Website Plan — What the Marketing Site Says\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## Where you are in the journey\n\nThe top-down lane has produced a market snapshot — ICPs, jobs, pains, gains, benefits with their\nweighting, positioning per ICP, tones of voice, proofs and objections — and a brand. The capability\ncomposition has decided whether this application has a marketing website. You decide **what that\nsite says**: its pages, and the sections that carry each page's argument.\n\nYou do not write the site. `bottom_up.build-decompose` turns each page and each section into a\nbuild task, and a coding agent authors it against the shipped `website-*` skills. The `website/`\nworkspace itself is composed by the `add-website` scenario, which the foundation applies from the\nsame capability composition you read here.\n\n## Step 1 — Read the capability composition FIRST\n\nFind the `add-website` decision. This playbook runs only once the composition decides it is\n**NEEDED**: its eligibility is gated on that decision, so a declined website is never planned, and a\nplan landed while it was needed is set aside for every reader if the composition later declines it.\n\n- **Needed** (the normal case): `disposition: PLANNED`, and continue.\n- **Declined** in the record you are given (it changed after you were started): land a plan with\n `disposition: NOT_APPLICABLE`, no pages, and a `rationale` naming what the composition said. Do not\n plan a site the application will never compose — the pages would become tasks with nowhere to write.\n\n## Step 2 — Decide the pages and their KINDS, from what the product actually declares\n\nEvery page has a **kind**, and the kind decides what you no longer have to: its route\n(`/product/<slug>`, `/solutions/<slug>`, `/pricing`, …), its place in the site menu, and the sections\nit cannot do without. You never name a route or a menu position — they are derived.\n\n| kind | exists when | route |\n|---|---|---|\n| `HOME` | always, exactly one; its slug is `landing` (the scaffold's starter page, which the home page grows) | `/` |\n| `PRODUCT` | one per product AREA the application actually ships and the snapshot argues for — a capability a visitor would look up by name | `/product/<slug>` |\n| `PRODUCT_OVERVIEW` | three or more PRODUCT pages (the validator asks for it from three on), or one page for a single-area product | `/product` |\n| `SOLUTION` | one per audience the snapshot positions separately — an ICP, a role, an industry or a use case with its own pains and proofs | `/solutions/<slug>` |\n| `PRICING` | the business model declares pricing plans | `/pricing` |\n| `CONTACT` | the audience buys through a conversation (an inbound channel, a legal-entity ICP) | `/contact` |\n| `COMPANY` | the snapshot or brand carries a story about who builds the product and why | `/about` |\n| `TRUST` | the application has controls a buyer's security review asks about — where data is stored, how people sign in, what is recorded, how long what is kept, the rights a person can exercise | `/security` |\n| `BLOG` | the application publishes posts (the blog adapter: one MDX file per post, per locale) | `/blog` |\n\n**Product page or solution page?** A product page answers *what does it do* — one area of the BUILT\nproduct: what it is, how it works, what it changes. A solution page answers *how does it solve MY\nproblem* — the product seen from one audience: their problem first, in their words, then how the\nproduct answers it, with proof from people like them. A SOLUTION page carries a `solutionAxis` —\n`ROLE`, `INDUSTRY`, `USE_CASE` or `COMPANY_SIZE` — which groups the Solutions menu; name it the way\nthe visitor names themselves. Solutions are secondary to the product: never plan solution pages\ninstead of product pages.\n\n**Ground product pages in the built product.** A PRODUCT page about a capability the application\ndoes not ship is a promise on the page buyers read most. Plan one per area the application's modules\ndeliver; if the market snapshot argues for something the product does not do yet, it is not a page.\n\nEach page names the ICPs it is **written for** and the tone of voice it speaks in, both by their\nmarket-snapshot refs. A page written for everybody is written for nobody: the positioning the\nmarket pass produced is per ICP, and a page that names none cannot use it. A SOLUTION page names\nexactly the audience it is for.\n\n## Step 3 — Compose each page's sections, in reading order\n\nOrder is the plan's substance. A page opens on a **HERO** — the promise, before any detail — and\nargues from there. The section kinds are closed, and each one names the skill that authors it:\n\n| kind | what it does |\n|---|---|\n| `HERO` | the opening promise: headline, sub-headline, primary call to action |\n| `FEATURE_BENEFIT_SUMMARY` | the benefits in one line each, for a reader who will not read the detail |\n| `FEATURE_DETAIL` | one benefit argued: the job it advances, the pain it relieves, what the product does |\n| `PRICING` | the plans, as the business model declares them |\n| `SOCIAL_PROOF` | the proofs the market pass authored |\n| `FAQ` | the objections, answered |\n| `CTA` | a call to action inside the page's flow |\n| `FOOTER_CTA` | the closing call to action |\n| `CONTACT` | a way to reach a human |\n| `PROBLEM` | the audience's pain, in their words, before the product appears — a solution page's opening argument |\n| `HOW_IT_WORKS` | three or four steps the built product performs |\n| `PRODUCT_SHOWCASE` | the real product shown: a framed screen, a bento of key screens, tabs across its views |\n| `SOLUTION_PATHS` | one card per solution page, routing each audience to the page written for it |\n| `COMPARISON` | the product against the alternatives the snapshot names, honestly |\n| `STATS` | facts about the product as figures — each one a value the application declares |\n| `INTEGRATIONS` | the systems the product connects to, each one a provider, channel or protocol it declares |\n| `LATEST_POSTS` | the blog's newest posts, read from their own frontmatter |\n| `ROADMAP` | what has shipped, what is next, what comes later — nothing unbuilt shown as available |\n\nEach kind has essentials the validator reports when missing: a product page shows how the product\nworks (HOW_IT_WORKS / FEATURE_DETAIL / PRODUCT_SHOWCASE) and offers a next step (FOOTER_CTA / CTA); a\nsolution page opens on its PROBLEM, then argues (FEATURE_DETAIL / HOW_IT_WORKS /\nFEATURE_BENEFIT_SUMMARY) and offers a next step; the home page shows the product and offers a next\nstep; pricing carries PRICING, contact CONTACT; a security page describes its controls (FEATURE_DETAIL /\nFEATURE_BENEFIT_SUMMARY / STATS); the blog page carries LATEST_POSTS. A LATEST_POSTS section anywhere else\n(the home page's \"from the blog\") needs a BLOG page in the same plan, because the posts live in the blog's\ncontent collection: a plan that lists posts and has no blog is refused.\n\n**The home page reads as modern when the product is on it, early.** Open on the HERO, show the\nproduct next (a PRODUCT_SHOWCASE, unless the hero itself carries the product visual), name the\nproblem when the audience does not yet know it has one, then how it works, the one or two benefits\nthat score highest, a SOLUTION_PATHS section once there are two or more solution pages, proof,\nobjections, and the closing call to action. Vary the section kinds — five benefit grids in a row read\nas filler — and keep it to about eight sections.\n\n**A solution page** reads: HERO (\"For <audience>\"), PROBLEM, FEATURE_DETAIL × 2–3 (each answering a\npain) or HOW_IT_WORKS, COMPARISON against what this audience uses today when the snapshot names it,\nSOCIAL_PROOF from people in this audience, FAQ, FOOTER_CTA.\n\n**A product page** reads: HERO, HOW_IT_WORKS or PRODUCT_SHOWCASE, FEATURE_DETAIL × 2–3, SOCIAL_PROOF,\nFAQ, FOOTER_CTA.\n\n**A security page** reads: HERO, FEATURE_BENEFIT_SUMMARY (the controls at a glance), FEATURE_DETAIL × 2–3 (sign-in,\ndata rights, the retention schedule as a table), STATS when the controls have figures, FAQ, FOOTER_CTA. It states\nwhat the product DOES; a certification the application does not hold is not on it, not even as \"in progress\".\n\n**Every section names the market entries it draws on** (`drawsOnRefs`) — the benefit, proof,\nobjection, job, pain, ICP or tone refs, exactly as the snapshot authored them. That is what makes a\nclaim checkable: a reader opens the snapshot and finds the entry. A section that draws on nothing is\na section somebody invented, and the validator reports a page where no section names anything.\n\n**A section that says what the product DOES names the requirement behind it** (`backedByRequirementRefs`).\nA market benefit says what a buyer wants; it does not say the product delivers it. An earlier site\npromised \"country workflow guidance with its limits stated\", drawn from a benefit, while the product\nshipped an empty page for an administrator to write guidance into.\n\n- Every section whose kind says what the product does (`FEATURE_DETAIL`, `FEATURE_BENEFIT_SUMMARY`,\n `PRODUCT_SHOWCASE`, `HOW_IT_WORKS`, `COMPARISON` and `INTEGRATIONS`) cites the requirements (functional, or\n non-functional such as working on a phone in the field), by their refs in your `requirements` input,\n that commit the product to what it describes. The validator reports one that cites none. An\n INTEGRATIONS section cites the requirement each connection serves as well as naming the provider the\n integration plan declares: the declaration says the provider is planned, the requirement's standing\n says whether the build delivered it.\n- Any other section (a hero, an FAQ, a pricing table, the solution paths) may cite requirements too, and\n should when its copy will say what the product does. A section that cites none describes no capability\n as available.\n- A citation is necessary, not sufficient. When the section is built, its author is told where each\n cited requirement stands: delivered, still being built, reported unmet by the run that built it, or\n only on a later roadmap phase. Only what is delivered is written as available; the rest is written as\n planned. So cite what the section is ABOUT, and do not drop a requirement because it is not built yet.\n- A benefit no requirement backs is not presented as a capability: leave it out, or give it a section\n whose purpose says it is planned.\n\nLead with fit. The brief carries the computed fit matrix beside each benefit's authored Kano\ncategory; a page for an ICP argues the benefits that score for THAT ICP first, rather than the ones\nthe model finds most interesting.\n\n## Step 4 — Every claim on the site is something the application already says\n\nA site generated from a product's own specifications can do what a hand-written one cannot: make every sentence\ncheckable. Hold the plan to it, because the coding agent will write exactly what the section's purpose asks for.\n\nThe brief carries what the application declares about itself, beside the market material: the roadmap (built now,\nnext, later), the requirements, the document facts (what it keeps and for how long, who receives what and where, the\nrights it honours) and the integration plan, each when it has landed. A section's purpose names which of them it\nstates. When none of them backs a claim the market snapshot makes, the claim belongs on the roadmap or nowhere; when\nthe family a section would state from has not landed yet, plan the section to state less, not to guess.\n\n- **A capability** is on a page only when the application PERFORMS it for the people the site is addressed to; a\n declared phase that is not built goes on a ROADMAP section in the horizon the roadmap gives it. Four near-misses\n read like capabilities and are not:\n - a STORED SETTING is not a behaviour: a resource that records a policy (reminder rules, an escalation policy, a\n snooze date) does nothing until something reads it, so the page may not say the product reminds, escalates or\n hides anything;\n - the OPERATOR's integration is not the customer's: a system of record the application reads its own business rows\n from is not something a customer connects;\n - an integration needs its deployment: a provider with no credential in the environment the site describes (a\n sign-in client, an app registration) is not offered there;\n - a gate belongs to one surface: an approval declared on an assistant's tool does not govern the same operation\n reached over MCP or the API. Say which surface asks, never that every surface does.\n- **A figure** (STATS, a hero note, an FAQ answer) is a value the application declares: a retention period, the\n length of an exposed list, a storage region, the number of locales.\n- **Where data lives** is the primary store's region AND every vendor-hosted service the application declares a\n compliance choice for (`providerComplianceChoices`), each with its region. \"All customer data in <region>\" is\n true only when every one of them is in it; otherwise the page names the services that are not. The same rule holds\n for a security control: state what the configuration REQUIRES (a policy for a user type, a role), never \"always\"\n for something a person may switch on. Write the section's purpose so it names the\n declaration (\"the audit trail's retention period from the retention schedule\"). A customer count, a rating, an\n uptime or \"x% faster\" is not a figure this lane can source, and is never planned.\n- **A name** (INTEGRATIONS, a COMPARISON column) is a provider, channel or protocol the application declares, or an\n alternative the market snapshot names.\n- **A quote** (SOCIAL_PROOF) comes from the snapshot's proofs with its source; a testimonial nobody gave is never\n planned, however natural the page would look with one.\n\n## Step 5 — Show the product, drawn faithfully and moving\n\nA modern site is read as a product when the product is on it. Plan PRODUCT_SHOWCASE (and FEATURE_DETAIL sections\nwith a visual) as DRAWN demos of the real interface, and say in the section's purpose which screen and which\nmoment: the screen the product is used from, and the moment it exists for (an item reaching done, a request being\napproved, a record arriving from outside). The coding agent draws them from the application's own resources (their\nreal fields, statuses and enum values) and animates them as a short state timeline in the engine's demo frame\n(`website-section-product-showcase`, `website-motion-design`). The last state is the still frame, which the server,\nreduced motion and a STILL site show; a paused demo holds the moment it is on. Plan breadth, not repetition: across\nthe site, show each product area once in motion, not the same list five times.\n\nWrite that decision into the section's `demo`: its `archetype` (what happens: items APPEND, an APPROVAL, a\nQUERY_ANSWER, a TRANSFORM, a CONNECT, COMPLETE_ITEMS, a STATUS_LIFECYCLE, a DASHBOARD filling in, a CELEBRATE), the\n`resourceRef` it is drawn from (the resource's ref in the domain plan, so the drawing is bound to that resource's real\nfields and values; for a status demo, the states its lifecycle declares), and the `moment` in one sentence. A ref the\ndomain plan does not declare is noted, and the build cannot bind the drawing to it. A demo goes only on a section whose block may hold a drawing (a hero, a feature row, a\nproduct tour, a bento, or a block of the site's own); a product showcase or feature detail drawn with one and planned without a demo is reported.\n\n**A drawing is a claim too**, and Step 4 governs it like a sentence. It draws only what the application shows: no\nfield the operation cannot change, no \"before\" value a screen does not render, no count or meter the resource does not\ncarry, no screen the application does not have (an operation reachable only through the API or an assistant is drawn\nthere, not as a screen of its own).\n\n## Step 6 — Design each section in the engine's blocks\n\nThe site's design is decided here, once, so every section task builds what the plan names instead of each choosing\nits own. Each section carries:\n\n- `component`: the block that builds it, among those its kind allows. A FAQ is a FAQ block, a hero a hero; a\n benefits summary is a card grid or a bento; a product showcase a product tour, a bento or a card grid; social proof\n quotation cards or a marquee. Leave it out to take the kind's usual block. `SITE_BLOCK`, a block of the site's own, is open only to the\n kinds whose skill teaches one (a problem stated once, area cards with moving drawings, a logo band, a contact\n layout), and its purpose says why no engine block fits.\n- `variant`, when the block has named layouts: a hero's STAGE (the product below the copy, for the home page's\n opening), SPLIT (beside it) or COMPACT (no visual); a feature row's side, alternated down the page so rows\n zig-zag; a card grid's columns; steps in a row or a stack; a FAQ's intro beside or above. A variant belongs to one\n block, and the plan refuses one given to another.\n- `tone`, the surface it stands on, where the surface carries meaning: the page's turning points and its numbers on\n INVERSE, its close on INVERSE, at most one BRAND band a page. Leave the rest out; the build alternates them.\n\nEach page names its `signatureSectionRef`: the one section a visitor remembers the page by, usually its richest\ndrawing. The build gives it the most care. It must be one of the page's own sections.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every page ref that still has a reason to exist — build tasks\nname them, and a ref that moves orphans the task that produced its page. Add, sharpen and reorder;\ndo not renumber.\n\n## What you emit\n\n- The **website plan** at `specifications/src/website-plan/index.ts` — a disposition with its\n rationale, and the pages, each with its kind (and a SOLUTION page's axis), purpose, audience, tone,\n signature section and ordered sections, each section with its design (block, layout, surface, demo). Routes and\n menu placement are derived from the kinds; do not author them.\n\n## Verification\n\n- Every `drawsOnRefs` entry names an entry that exists in the market snapshot.\n- Exactly one page is `HOME`, with the slug `landing`; every page opens on a `HERO`.\n- Every PRODUCT page names an area the application ships; every SOLUTION page names its audience and\n its `solutionAxis`, and opens its argument on a `PROBLEM`.\n- Every section that says what the product does (`FEATURE_DETAIL`, `FEATURE_BENEFIT_SUMMARY`, `PRODUCT_SHOWCASE`,\n `HOW_IT_WORKS`, `COMPARISON`, `INTEGRATIONS`) names at least one `backedByRequirementRefs` entry, and each names a\n requirement in the requirements.\n- Every STATS, INTEGRATIONS and ROADMAP section's purpose names the declaration its figures, names or stages come\n from; no section plans a customer count, a rating or a testimonial the snapshot does not carry.\n- No kind's essentials are missing (the validator reports them by page).\n- Every section's `component` is one its kind allows and every `variant` shapes that component (the plan refuses\n either otherwise); every product showcase or feature detail drawn with a picture has a `demo`; no page stands\n more than one section on BRAND; every page's `signatureSectionRef` names one of its own sections.\n- Every section ref is unique across the SITE, not only within its page: the build collects every section by\n its ref, so name each after its page (`landing-hero`, `pricing-hero`). Every page opens on a HERO, so two\n pages always need two names; the plan refuses a ref declared on two pages.\n- `rg -n \"sectionRef\" specifications/src/website-plan/index.ts | wc -l` — the number of website\n section tasks the build lane will emit.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem: naming a path here would be an instruction answered from\nrecollection (#1435). So each skill is named by its REF, and only `website-page-authoring` reaches\nthis step as a BODY (`method.skillBodyRefs`) — it is the one contract the plan must not contradict,\nbecause it says what a page IS in this engine: a manifest, a route adapter, a sections file and a\nlabel pack that fails the build closed on a missing key. A page planned against anything else is a\npage the build lane cannot author.\n\nThe others below are the contracts the CODING AGENT opens when it builds each task, listed so a\nreader knows the plan's decisions land somewhere:\n\n- `website-navigation-authoring` — the site menu each page joins (Product and Solutions panels, direct links), derived from the kinds you plan. Its top level is at most six entries, in a fixed order: product, solutions, pricing, blog, company, contact.\n- `website-motion-design` — the site's motion vocabulary; the home page's one signature entrance is the hero's.\n- `website-seo-aeo-geo` — what a page owes a search engine and an answer engine.\n- `website-label-pack` — every string a section renders is a label key, and the build fails closed on a missing one.\n- `website-marketing-metadata-extension` — the metadata a page carries beyond its sections.\n- `website-section-*` — one per section KIND, bound to the emitted task by `WEBSITE_SECTION_SKILL_REF`.\n- `market-positioning-authoring`, `market-tone-of-voice`, `market-proof-and-objection` — the market\n vocabularies a section draws on, which arrive here as the market snapshot itself rather than as prose.\n",
62
78
  "skillRefs": [
63
79
  "website-page-authoring",
64
80
  "website-navigation-authoring",
81
+ "website-motion-design",
65
82
  "website-seo-aeo-geo",
66
83
  "website-label-pack",
67
84
  "website-marketing-metadata-extension",
@@ -72,6 +89,7 @@
72
89
  "skillBodyRefs": [
73
90
  "website-page-authoring"
74
91
  ],
92
+ "derivedFromAnswers": [],
75
93
  "contextSources": [
76
94
  "market_fit_scores"
77
95
  ],
@@ -12,16 +12,21 @@ Read and apply these patterns from the application-developer point of view:
12
12
  - how the application should avoid mixing frontend, backend, and infrastructure concerns
13
13
 
14
14
 
15
- This playbook IS the creation of the application. It produces nothing itself: it drives
16
- four lanes, each of which drives its own leaves, and it ends on a reading of how mature
17
- the application is against its own requirements — a stage, never a "done".
15
+ This playbook IS the creation of the application. It produces nothing itself: it runs
16
+ the vision interview, drives four lanes, each of which drives its own leaves, and it ends
17
+ on a reading of how mature the application is against its own requirements — a stage,
18
+ never a "done".
18
19
 
19
20
  ## The lanes, and why the order is not written here
20
21
 
21
- - **`top_down.definition`** — what the application IS: the vision, the market and its
22
- evidence, the value proposition, the requirements, the capability map, the business
23
- model, the roadmap, and the phase gate that judges their coherence. Brand identity and
24
- the risk register run beside the chain. Opens on an empty application.
22
+ - **`top_down.vision-elicitation`** — not a lane but the vision interview itself, from the
23
+ creator's answers. Opens on an empty application, and on an empty application it is the
24
+ only thing that can run: both lanes that follow need the vision, so it lands in a round
25
+ of its own and they start together.
26
+ - **`top_down.definition`** — what the application IS: the market and its evidence, the
27
+ value proposition, the requirements, the capability map, the business model, the
28
+ roadmap, and the phase gate that judges their coherence. Brand identity and the risk
29
+ register run beside the chain. Opens on a valid vision.
25
30
  - **`cross_cutting.compliance`** — which regimes apply and what the application must be
26
31
  able to say: the posture from researched evidence, the assurance programme, the facts
27
32
  read from the product, and the drafted governed documents. Opens on a valid vision, so
@@ -40,11 +45,21 @@ whatever is not.
40
45
 
41
46
  ## Selecting the next lane
42
47
 
43
- - **One lane per round.** A lane is a long run of its own. The definition and compliance
44
- lanes both write the vision, so they cannot share a round; the rest are sequential.
45
- - **Furthest first.** Choose the lane that can advance the application most from what is
46
- on record, and prefer a lane waiting on nothing to one waiting on the creator.
47
- - **Do not re-select a lane that has just landed.** The round history says what ran.
48
+ - **The vision first, alone.** When the application has no vision, the interview is the
49
+ only thing on offer: run it. Once it has landed, the definition and compliance lanes are
50
+ both on offer, and they belong in the same round.
51
+ - **Up to two lanes per round.** A round waits for both of its lanes, so pick two that do
52
+ not write the same work. Compliance pairs with any other lane, and the definition with the
53
+ conception or the build. The conception lane and the build do not pair, and the vision
54
+ interview, when the creator's answers change, does not pair with the definition lane.
55
+ - **The build lane, whenever it can dispatch.** While the build plan has tasks that are
56
+ ready, or that only wait on a staffing repair, the build lane is one of the round's
57
+ two. Leaving it out leaves the build idle for the whole round.
58
+ - **Furthest first, for the other slot.** Choose the lane that can advance the
59
+ application most from what is on record, and prefer a lane waiting on nothing to one
60
+ waiting on the creator.
61
+ - **Do not re-select a lane that has just landed,** except the build lane while tasks
62
+ remain to dispatch. The round history says what ran.
48
63
  - **A lane that stopped because the creator owes it an answer is a real stop.** Say so
49
64
  in the rationale rather than re-selecting it.
50
65
 
@@ -1,13 +1,17 @@
1
1
  {
2
2
  "ref": "cross_cutting.application-creation",
3
- "version": "0.1.0",
3
+ "version": "0.3.0",
4
4
  "phase": "cross_cutting",
5
- "intent": "Create the application: drive the definition (vision, market, requirements, capabilities, business model, roadmap, phase gate), the compliance posture and its governed documents, the conception (domain plan, foundation, placement) and the build (decompose, dispatch, assemble) as four LANES, each of which drives its own leaves. An umbrella over umbrellas: it authors nothing itself, and the order between the lanes is decided by their own preconditions against the working tree rather than declared here — the definition lane opens on a fresh application, compliance opens on a valid vision and runs beside it, conception opens once requirements and the market snapshot are on record, the build once the domain and placement plans are. Select the lane that can advance the application FURTHEST from what is on record, and prefer a lane that is waiting on nothing to one waiting on the creator. A lane is a long run: expect one lane per round, and do not re-select a lane that has just landed its families. STOP when no lane can advance the application — that is a STAGE the maturity reading names, never a finished application.",
5
+ "intent": "Create the application: elicit the vision, then drive the definition (market, requirements, capabilities, business model, roadmap, phase gate), the compliance posture and its governed documents, the conception (domain plan, foundation, placement) and the build (decompose, dispatch, assemble) as four LANES, each of which drives its own leaves. An umbrella over umbrellas: it authors nothing itself, and the order between the lanes is decided by their own preconditions against the working tree rather than declared here — on a fresh application only the vision interview can run, and it runs alone; the definition and compliance lanes both open on a valid vision and run side by side, conception opens once requirements and the market snapshot are on record, the build once the domain and placement plans are. Select up to TWO lanes per round whose work does not overlap: while the build lane can dispatch a task, it is always one of them, and the other is the lane that can advance the application furthest (compliance pairs with any lane). Prefer a lane that is waiting on nothing to one waiting on the creator. Do not re-select a lane that has just landed its families, except the build lane while tasks remain to dispatch. STOP when no lane can advance the application — that is a STAGE the maturity reading names, never a finished application.",
6
6
  "preconditions": [],
7
7
  "inputs": [
8
8
  {
9
9
  "family": "vision-brief"
10
10
  },
11
+ {
12
+ "family": "compliance-posture",
13
+ "render": "map"
14
+ },
11
15
  {
12
16
  "family": "market-snapshot",
13
17
  "render": "map"
@@ -40,9 +44,10 @@
40
44
  "outputs": [],
41
45
  "stepOutputs": [],
42
46
  "method": {
43
- "guidance": "# Creating the application — the root\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis playbook IS the creation of the application. It produces nothing itself: it drives\nfour lanes, each of which drives its own leaves, and it ends on a reading of how mature\nthe application is against its own requirements — a stage, never a \"done\".\n\n## The lanes, and why the order is not written here\n\n- **`top_down.definition`** — what the application IS: the vision, the market and its\n evidence, the value proposition, the requirements, the capability map, the business\n model, the roadmap, and the phase gate that judges their coherence. Brand identity and\n the risk register run beside the chain. Opens on an empty application.\n- **`cross_cutting.compliance`** — which regimes apply and what the application must be\n able to say: the posture from researched evidence, the assurance programme, the facts\n read from the product, and the drafted governed documents. Opens on a valid vision, so\n it runs beside the definition rather than after it.\n- **`bottom_up.conception`** — the structure: the domain plan, the expert charters that\n staff the panels, the composed foundation, the placement plan. Opens once the\n requirements and the market snapshot are on record.\n- **`bottom_up.build`** — the application itself: the build plan, the dispatch of its\n tasks, the assembly check, and the maturity reading it ends on. Opens once the domain\n and placement plans are on record.\n\nNothing above is a sequence. Each lane declares what it needs and the runtime re-reads\nthe tree after every round; that is the waterfall, and it is why this playbook can be\nrun again on an application at any stage — whatever is on record satisfies the gates of\nwhatever is not.\n\n## Selecting the next lane\n\n- **One lane per round.** A lane is a long run of its own. The definition and compliance\n lanes both write the vision, so they cannot share a round; the rest are sequential.\n- **Furthest first.** Choose the lane that can advance the application most from what is\n on record, and prefer a lane waiting on nothing to one waiting on the creator.\n- **Do not re-select a lane that has just landed.** The round history says what ran.\n- **A lane that stopped because the creator owes it an answer is a real stop.** Say so\n in the rationale rather than re-selecting it.\n\n## Composing an objective for a lane\n\nName what the application already holds and what this lane should add — \"the vision and\nmarket are on record, the requirements are not; take the definition through to the phase\ngate\". A later round names what changed: \"the domain plan moved; re-open the document\nfacts that were derived from it\".\n\n## When to stop\n\nStop when no lane can advance the application from what is on record. **That is a\nSTAGE, not a finished application** — the maturity reading is what names it, measured\nagainst the application's own requirements, and it moves every time a later run lands\nsomething. Stop also when every remaining lane is waiting on the creator, and say which\nanswers are owed.\n\n## What the creator reviews\n\nOne decision at the end: the work every lane kept, to accept, to revise with a note, or\nto discard. Under the current posture it is notified rather than awaited. Each lane has\nalready ended on its own decision, and each leaf's own review guide still applies to\nwhat it landed.\n",
47
+ "guidance": "# Creating the application — the root\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis playbook IS the creation of the application. It produces nothing itself: it runs\nthe vision interview, drives four lanes, each of which drives its own leaves, and it ends\non a reading of how mature the application is against its own requirements — a stage,\nnever a \"done\".\n\n## The lanes, and why the order is not written here\n\n- **`top_down.vision-elicitation`** — not a lane but the vision interview itself, from the\n creator's answers. Opens on an empty application, and on an empty application it is the\n only thing that can run: both lanes that follow need the vision, so it lands in a round\n of its own and they start together.\n- **`top_down.definition`** — what the application IS: the market and its evidence, the\n value proposition, the requirements, the capability map, the business model, the\n roadmap, and the phase gate that judges their coherence. Brand identity and the risk\n register run beside the chain. Opens on a valid vision.\n- **`cross_cutting.compliance`** — which regimes apply and what the application must be\n able to say: the posture from researched evidence, the assurance programme, the facts\n read from the product, and the drafted governed documents. Opens on a valid vision, so\n it runs beside the definition rather than after it.\n- **`bottom_up.conception`** — the structure: the domain plan, the expert charters that\n staff the panels, the composed foundation, the placement plan. Opens once the\n requirements and the market snapshot are on record.\n- **`bottom_up.build`** — the application itself: the build plan, the dispatch of its\n tasks, the assembly check, and the maturity reading it ends on. Opens once the domain\n and placement plans are on record.\n\nNothing above is a sequence. Each lane declares what it needs and the runtime re-reads\nthe tree after every round; that is the waterfall, and it is why this playbook can be\nrun again on an application at any stage — whatever is on record satisfies the gates of\nwhatever is not.\n\n## Selecting the next lane\n\n- **The vision first, alone.** When the application has no vision, the interview is the\n only thing on offer: run it. Once it has landed, the definition and compliance lanes are\n both on offer, and they belong in the same round.\n- **Up to two lanes per round.** A round waits for both of its lanes, so pick two that do\n not write the same work. Compliance pairs with any other lane, and the definition with the\n conception or the build. The conception lane and the build do not pair, and the vision\n interview, when the creator's answers change, does not pair with the definition lane.\n- **The build lane, whenever it can dispatch.** While the build plan has tasks that are\n ready, or that only wait on a staffing repair, the build lane is one of the round's\n two. Leaving it out leaves the build idle for the whole round.\n- **Furthest first, for the other slot.** Choose the lane that can advance the\n application most from what is on record, and prefer a lane waiting on nothing to one\n waiting on the creator.\n- **Do not re-select a lane that has just landed,** except the build lane while tasks\n remain to dispatch. The round history says what ran.\n- **A lane that stopped because the creator owes it an answer is a real stop.** Say so\n in the rationale rather than re-selecting it.\n\n## Composing an objective for a lane\n\nName what the application already holds and what this lane should add — \"the vision and\nmarket are on record, the requirements are not; take the definition through to the phase\ngate\". A later round names what changed: \"the domain plan moved; re-open the document\nfacts that were derived from it\".\n\n## When to stop\n\nStop when no lane can advance the application from what is on record. **That is a\nSTAGE, not a finished application** — the maturity reading is what names it, measured\nagainst the application's own requirements, and it moves every time a later run lands\nsomething. Stop also when every remaining lane is waiting on the creator, and say which\nanswers are owed.\n\n## What the creator reviews\n\nOne decision at the end: the work every lane kept, to accept, to revise with a note, or\nto discard. Under the current posture it is notified rather than awaited. Each lane has\nalready ended on its own decision, and each leaf's own review guide still applies to\nwhat it landed.\n",
44
48
  "skillRefs": [],
45
49
  "skillBodyRefs": [],
50
+ "derivedFromAnswers": [],
46
51
  "contextSources": [],
47
52
  "draftableDocumentDefinitionRefs": [],
48
53
  "choreography": {
@@ -50,10 +55,11 @@
50
55
  "bottom_up.build",
51
56
  "bottom_up.conception",
52
57
  "cross_cutting.compliance",
53
- "top_down.definition"
58
+ "top_down.definition",
59
+ "top_down.vision-elicitation"
54
60
  ],
55
61
  "maximumIterations": 10,
56
- "maximumLanesPerIteration": 1,
62
+ "maximumLanesPerIteration": 2,
57
63
  "maximumDepth": 3,
58
64
  "maximumDurationMs": 86400000,
59
65
  "reopenOnVerdict": [
@@ -23,7 +23,7 @@ marked and notified, never composed by the mechanism.
23
23
  the product facts that decide which regimes apply (data classes, where the vendor is
24
24
  established, jurisdictions, sector, residency), gathers regime evidence from
25
25
  authoritative sources, judges whether it is enough, and records the applicable regimes
26
- on the vision as constraints only once it is. Its evidence loop and its interview are
26
+ in the `compliance-posture` family only once it is. Its evidence loop and its interview are
27
27
  its own; this lane sees only that a posture landed.
28
28
  - **`top_down.compliance-conception`** — the assurance programme, the publication
29
29
  specification and the release policy, from the posture. Asks one question.
@@ -41,8 +41,8 @@ the facts need the domain plan; the drafters expect the facts.
41
41
 
42
42
  ## Two halves, and the lane may stop between them
43
43
 
44
- The lane is eligible on a vision alone, on purpose: the definition lane's phase gate
45
- reads the posture, so the posture must be able to land before the definition ends. On
44
+ The lane is eligible on a vision alone, on purpose: the posture needs nothing else, so
45
+ it can land before conception has run. On
46
46
  an application whose domain plan is not yet on record, land the posture and the
47
47
  conception, then stop — the lane resumes once the conception lane has landed the plan,
48
48
  and the first round then offers the facts.
@@ -78,6 +78,6 @@ gap twice and a further round could not close it. Say which, in the rationale.
78
78
 
79
79
  ## What the creator reviews
80
80
 
81
- The posture on the vision, the programme, the facts, and each drafted document with its
81
+ The compliance posture, the programme, the facts, and each drafted document with its
82
82
  marked statements — and the release decision: a legally-binding statement leaving the
83
83
  system, notified under the current posture and awaited once Gate 3 arms it.
@@ -2,7 +2,7 @@
2
2
  "ref": "cross_cutting.compliance",
3
3
  "version": "0.1.0",
4
4
  "phase": "cross_cutting",
5
- "intent": "Drive the COMPLIANCE of the application as one lane: the posture (regime evidence, judged adequate, recorded on the vision as constraints), the compliance conception (the programme, the publication and release policies), the document facts read from the product, and the drafted governed documents — public and governance — ending on one decision: the document release, marked and notified. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round. Select what is MISSING from the accepted truth shown to you, in the order the chain implies: the posture before the conception, the facts before the candidates, and never a candidate re-drafted while its facts are unchanged. The posture half needs only the vision; the facts need a valid domain plan — when it is not on record, land the posture and the conception and STOP: the lane resumes when the conception lane has landed the plan. STOP when the candidates are drafted: the release is this lane's closing decision. A child whose interview the creator has not answered is not offered; run everything else and stop when nothing eligible advances the compliance.",
5
+ "intent": "Drive the COMPLIANCE of the application as one lane: the posture (regime evidence, judged adequate, recorded in the compliance-posture family), the compliance conception (the programme, the publication and release policies), the document facts read from the product, and the drafted governed documents — public and governance — ending on one decision: the document release, marked and notified. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round. Select what is MISSING from the accepted truth shown to you, in the order the chain implies: the posture before the conception, the facts before the candidates, and never a candidate re-drafted while its facts are unchanged. The posture half needs only the vision; the facts need a valid domain plan — when it is not on record, land the posture and the conception and STOP: the lane resumes when the conception lane has landed the plan. STOP when the candidates are drafted: the release is this lane's closing decision. A child whose interview the creator has not answered is not offered; run everything else and stop when nothing eligible advances the compliance.",
6
6
  "preconditions": [
7
7
  {
8
8
  "kind": "artifact_valid",
@@ -15,6 +15,10 @@
15
15
  {
16
16
  "family": "vision-brief"
17
17
  },
18
+ {
19
+ "family": "compliance-posture",
20
+ "render": "map"
21
+ },
18
22
  {
19
23
  "family": "domain-plan",
20
24
  "render": "map"
@@ -37,9 +41,10 @@
37
41
  "outputs": [],
38
42
  "stepOutputs": [],
39
43
  "method": {
40
- "guidance": "# The Compliance Lane — the umbrella\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis playbook produces nothing itself. It drives the steps that establish the\napplication's COMPLIANCE — the posture, the programme, the facts, the governed\ndocuments — and it ends on the document release, which is the lane's closing decision:\nmarked and notified, never composed by the mechanism.\n\n## The children, and why the order is not written here\n\n- **`top_down.compliance-analysis`** — a NESTED LANE, not a leaf: it asks the creator\n the product facts that decide which regimes apply (data classes, where the vendor is\n established, jurisdictions, sector, residency), gathers regime evidence from\n authoritative sources, judges whether it is enough, and records the applicable regimes\n on the vision as constraints only once it is. Its evidence loop and its interview are\n its own; this lane sees only that a posture landed.\n- **`top_down.compliance-conception`** — the assurance programme, the publication\n specification and the release policy, from the posture. Asks one question.\n- **`refinement.document-facts`** — the facts a governed document rests on, READ FROM\n THE PRODUCT (the resource configurations, the declared identity). Needs a valid\n domain plan.\n- **`refinement.compliance-document-candidate`** — the public documents (privacy\n notice, service terms), drafted from the facts.\n- **`refinement.governance-document-candidate`** — the governance documents, drafted\n from the facts and the assurance evidence.\n\nNothing above is a sequence. Each child declares what it needs and the runtime\nre-computes what may run after every round. The posture half needs only the vision;\nthe facts need the domain plan; the drafters expect the facts.\n\n## Two halves, and the lane may stop between them\n\nThe lane is eligible on a vision alone, on purpose: the definition lane's phase gate\nreads the posture, so the posture must be able to land before the definition ends. On\nan application whose domain plan is not yet on record, land the posture and the\nconception, then stop — the lane resumes once the conception lane has landed the plan,\nand the first round then offers the facts.\n\n## Selecting the next children\n\n- **The chain's order, stated as a preference the gates do not enforce.** The runner\n admits a child past a sequencing expectation inside a lane, so the drafters are\n offered before the facts land. Land the facts first. A document drafted without them\n marks what it could not establish and is re-drafted when they land — honest, and the\n weaker document.\n- **Missing beats present.** A drafted candidate is not re-drafted while its facts are\n unchanged; a landed posture is not re-recorded while the vision is unchanged.\n- **Independent children share a round.** The two drafters read the same facts and can\n run beside each other; several research lanes with different jurisdictions in their\n objectives return more than one asked everything.\n- **A child waiting on the creator is not offered** — which for this lane means the\n posture umbrella, until its product-fact questions are answered. The document half\n needs the domain plan rather than the jurisdictions, so it runs meanwhile.\n\n## Composing an objective for a child\n\nFor research, the umbrella's rule: the first round aimed at the jurisdictions and data\nclasses the creator named, a later round at the gap the gate named. For the drafters,\nname the documents the publication specification declares and the facts on record.\n\n## When to stop\n\nStop when the candidates are drafted: the release is the decision this lane ends on.\nStop when the domain plan is not on record and the posture and the conception are —\nthe second half waits on another lane. Stop when the evidence gate has named the same\ngap twice and a further round could not close it. Say which, in the rationale.\n\n## What the creator reviews\n\nThe posture on the vision, the programme, the facts, and each drafted document with its\nmarked statements — and the release decision: a legally-binding statement leaving the\nsystem, notified under the current posture and awaited once Gate 3 arms it.\n",
44
+ "guidance": "# The Compliance Lane — the umbrella\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis playbook produces nothing itself. It drives the steps that establish the\napplication's COMPLIANCE — the posture, the programme, the facts, the governed\ndocuments — and it ends on the document release, which is the lane's closing decision:\nmarked and notified, never composed by the mechanism.\n\n## The children, and why the order is not written here\n\n- **`top_down.compliance-analysis`** — a NESTED LANE, not a leaf: it asks the creator\n the product facts that decide which regimes apply (data classes, where the vendor is\n established, jurisdictions, sector, residency), gathers regime evidence from\n authoritative sources, judges whether it is enough, and records the applicable regimes\n in the `compliance-posture` family only once it is. Its evidence loop and its interview are\n its own; this lane sees only that a posture landed.\n- **`top_down.compliance-conception`** — the assurance programme, the publication\n specification and the release policy, from the posture. Asks one question.\n- **`refinement.document-facts`** — the facts a governed document rests on, READ FROM\n THE PRODUCT (the resource configurations, the declared identity). Needs a valid\n domain plan.\n- **`refinement.compliance-document-candidate`** — the public documents (privacy\n notice, service terms), drafted from the facts.\n- **`refinement.governance-document-candidate`** — the governance documents, drafted\n from the facts and the assurance evidence.\n\nNothing above is a sequence. Each child declares what it needs and the runtime\nre-computes what may run after every round. The posture half needs only the vision;\nthe facts need the domain plan; the drafters expect the facts.\n\n## Two halves, and the lane may stop between them\n\nThe lane is eligible on a vision alone, on purpose: the posture needs nothing else, so\nit can land before conception has run. On\nan application whose domain plan is not yet on record, land the posture and the\nconception, then stop — the lane resumes once the conception lane has landed the plan,\nand the first round then offers the facts.\n\n## Selecting the next children\n\n- **The chain's order, stated as a preference the gates do not enforce.** The runner\n admits a child past a sequencing expectation inside a lane, so the drafters are\n offered before the facts land. Land the facts first. A document drafted without them\n marks what it could not establish and is re-drafted when they land — honest, and the\n weaker document.\n- **Missing beats present.** A drafted candidate is not re-drafted while its facts are\n unchanged; a landed posture is not re-recorded while the vision is unchanged.\n- **Independent children share a round.** The two drafters read the same facts and can\n run beside each other; several research lanes with different jurisdictions in their\n objectives return more than one asked everything.\n- **A child waiting on the creator is not offered** — which for this lane means the\n posture umbrella, until its product-fact questions are answered. The document half\n needs the domain plan rather than the jurisdictions, so it runs meanwhile.\n\n## Composing an objective for a child\n\nFor research, the umbrella's rule: the first round aimed at the jurisdictions and data\nclasses the creator named, a later round at the gap the gate named. For the drafters,\nname the documents the publication specification declares and the facts on record.\n\n## When to stop\n\nStop when the candidates are drafted: the release is the decision this lane ends on.\nStop when the domain plan is not on record and the posture and the conception are —\nthe second half waits on another lane. Stop when the evidence gate has named the same\ngap twice and a further round could not close it. Say which, in the rationale.\n\n## What the creator reviews\n\nThe compliance posture, the programme, the facts, and each drafted document with its\nmarked statements — and the release decision: a legally-binding statement leaving the\nsystem, notified under the current posture and awaited once Gate 3 arms it.\n",
41
45
  "skillRefs": [],
42
46
  "skillBodyRefs": [],
47
+ "derivedFromAnswers": [],
43
48
  "contextSources": [],
44
49
  "draftableDocumentDefinitionRefs": [],
45
50
  "choreography": {
@@ -44,6 +44,7 @@
44
44
  "guidance": "# The feature-development line — the umbrella\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis playbook produces nothing itself. It develops ONE feature, the one the line was opened for (see \"What\nthis run is for\"), beside the application's main line, and through the product model: the feature is\nwritten down as requirements and drafts first, and everything built from those is re-derived from them.\n\n## The children\n\n- **`refinement.feature-contribution`** — adds the feature to the requirements and the feature drafts, as\n this line's own elements. Nothing it returns replaces what the application already holds.\n- **`bottom_up.domain-plan`** — the application's domain plan, re-derived from requirements that now hold\n the feature. It runs for the whole application, not for this line.\n- **`bottom_up.experience-plan`** — the screens and journeys, re-derived the same way, when the feature\n changes what a person sees.\n- **`bottom_up.build`** — the build lane: it decomposes the changed plan into tasks and dispatches them to\n the coding agent. A long lane with its own rounds.\n\n## Choosing\n\nNothing above is a sequence the runtime enforces; each child declares what it needs. Read what exists:\n\n- If the requirements do not yet hold this feature, run the feature contribution. Nothing downstream can\n reflect a feature the requirements do not name.\n- Once they do, the domain plan is out of date with respect to them: re-derive it.\n- Then the experience plan, if the feature has anything a person sees.\n- Then the build.\n\nStop when the feature is built, or when no eligible child advances it. Do not re-run the contribution to\n\"improve\" a feature that has landed: a refinement of the feature is a new run of this line, asked for by\nthe person who opened it.\n",
45
45
  "skillRefs": [],
46
46
  "skillBodyRefs": [],
47
+ "derivedFromAnswers": [],
47
48
  "contextSources": [],
48
49
  "draftableDocumentDefinitionRefs": [],
49
50
  "choreography": {
@@ -23,13 +23,14 @@ Each child re-derives one whole family for the application. They come in two kin
23
23
 
24
24
  - **What can be refined** (what the line may name), each from its own prior output: the vision, the
25
25
  requirements, the feature drafts, the value proposition and the capability map (both refine the market),
26
- the roadmap, the brand; the domain, experience, integration, website and documentation plans, and the build
27
- plan (`bottom_up.build-decompose`).
26
+ the roadmap, the brand, the business model, the risk register and the service method; the domain,
27
+ experience, integration, website and documentation plans, and the build plan (`bottom_up.build-decompose`).
28
28
  - **What can only be refreshed**, re-derived from its inputs when a refinement made it stale: the placement
29
- plan, the capability composition, the business model, the risk register, the document facts and the
30
- governed documents.
29
+ plan, the capability composition, the document facts and the governed documents.
31
30
  - **`bottom_up.build`** — the build lane: it decomposes the changed plan into tasks and dispatches them to
32
- the coding agent. A long lane with its own rounds.
31
+ the coding agent. A long lane with its own rounds. It also runs the expert staffing
32
+ (`top_down.expert-personas`) when a change made a panel's charters stale, so the staffing is not a child
33
+ of its own here.
33
34
 
34
35
  ## Choosing
35
36
 
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "cross_cutting.refinement",
3
- "version": "0.1.0",
3
+ "version": "0.1.3",
4
4
  "phase": "cross_cutting",
5
5
  "intent": "Refine what this line was opened for: re-derive each named family from what it already holds, guided by the purpose, then refresh what that made out of date and build it. An umbrella: it authors nothing itself. The first move is fixed: the producers of the named families. After that, select only children whose outputs are STALE, upstream before downstream, the build last. STOP when nothing is stale any more and the build has run, or when nothing eligible advances the refinement.",
6
6
  "preconditions": [
@@ -39,9 +39,10 @@
39
39
  "outputs": [],
40
40
  "stepOutputs": [],
41
41
  "method": {
42
- "guidance": "# The refinement line — the umbrella\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis playbook produces nothing itself. It refines what the line was opened for (see \"What this run is for\",\nwhich names the purpose and the families to refine), beside the application's main line. A refinement\nre-derives a family the application ALREADY holds, from what it already says: keep what still holds, change\nwhat the purpose asks, and do not re-author the rest.\n\n## The children\n\nEach child re-derives one whole family for the application. They come in two kinds:\n\n- **What can be refined** (what the line may name), each from its own prior output: the vision, the\n requirements, the feature drafts, the value proposition and the capability map (both refine the market),\n the roadmap, the brand; the domain, experience, integration, website and documentation plans, and the build\n plan (`bottom_up.build-decompose`).\n- **What can only be refreshed**, re-derived from its inputs when a refinement made it stale: the placement\n plan, the capability composition, the business model, the risk register, the document facts and the\n governed documents.\n- **`bottom_up.build`** — the build lane: it decomposes the changed plan into tasks and dispatches them to\n the coding agent. A long lane with its own rounds.\n\n## Choosing\n\n- **The first rounds are fixed.** While a family this line names has not been re-derived, you are offered\n only its producers, upstream ones first. Pass the purpose on in the child's objective, in the person's\n terms: it is what the refinement must change.\n- **Then refresh what the change made stale, and nothing else.** Each eligible child shows the outputs that\n are stale and the inputs they wait on. Refresh a family only when it is stale, and its own stale inputs\n first: the requirements before the domain plan, the domain plan before the experience plan, a plan before\n the build plan.\n- **Build last**, once the plans the change touched are current.\n- **Stop** when nothing is stale any more and the build has run, or when no eligible child advances the\n refinement. Do not re-run a named family's producer to \"improve\" it further: a further refinement is a new\n run of this line, asked for by the person who opened it.\n",
42
+ "guidance": "# The refinement line — the umbrella\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis playbook produces nothing itself. It refines what the line was opened for (see \"What this run is for\",\nwhich names the purpose and the families to refine), beside the application's main line. A refinement\nre-derives a family the application ALREADY holds, from what it already says: keep what still holds, change\nwhat the purpose asks, and do not re-author the rest.\n\n## The children\n\nEach child re-derives one whole family for the application. They come in two kinds:\n\n- **What can be refined** (what the line may name), each from its own prior output: the vision, the\n requirements, the feature drafts, the value proposition and the capability map (both refine the market),\n the roadmap, the brand, the business model, the risk register and the service method; the domain,\n experience, integration, website and documentation plans, and the build plan (`bottom_up.build-decompose`).\n- **What can only be refreshed**, re-derived from its inputs when a refinement made it stale: the placement\n plan, the capability composition, the document facts and the governed documents.\n- **`bottom_up.build`** — the build lane: it decomposes the changed plan into tasks and dispatches them to\n the coding agent. A long lane with its own rounds. It also runs the expert staffing\n (`top_down.expert-personas`) when a change made a panel's charters stale, so the staffing is not a child\n of its own here.\n\n## Choosing\n\n- **The first rounds are fixed.** While a family this line names has not been re-derived, you are offered\n only its producers, upstream ones first. Pass the purpose on in the child's objective, in the person's\n terms: it is what the refinement must change.\n- **Then refresh what the change made stale, and nothing else.** Each eligible child shows the outputs that\n are stale and the inputs they wait on. Refresh a family only when it is stale, and its own stale inputs\n first: the requirements before the domain plan, the domain plan before the experience plan, a plan before\n the build plan.\n- **Build last**, once the plans the change touched are current.\n- **Stop** when nothing is stale any more and the build has run, or when no eligible child advances the\n refinement. Do not re-run a named family's producer to \"improve\" it further: a further refinement is a new\n run of this line, asked for by the person who opened it.\n",
43
43
  "skillRefs": [],
44
44
  "skillBodyRefs": [],
45
+ "derivedFromAnswers": [],
45
46
  "contextSources": [],
46
47
  "draftableDocumentDefinitionRefs": [],
47
48
  "choreography": {
@@ -60,6 +61,7 @@
60
61
  "refinement.document-facts",
61
62
  "top_down.compliance-conception",
62
63
  "top_down.risk-register",
64
+ "top_down.service-method",
63
65
  "top_down.business-model",
64
66
  "top_down.brand-identity",
65
67
  "top_down.scope-roadmap",
@@ -88,6 +90,7 @@
88
90
  "refinement.document-facts",
89
91
  "top_down.compliance-conception",
90
92
  "top_down.risk-register",
93
+ "top_down.service-method",
91
94
  "top_down.business-model",
92
95
  "top_down.brand-identity",
93
96
  "top_down.scope-roadmap",
@@ -1 +1 @@
1
- {"aggregationPolicyRef":"application-creation:aggregation/worst-compliance-document-claims-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/compliance-document-claims-within-guard","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-document-claims-within-guard","requirementVersion":1}],"instruction":"The subject under judgment is each landed `compliance-document-candidate`. For EVERY clause, find the catalog claim guards it names in `claimGuardRefs` in the \"Catalog claim guards\" section of the evidence. A clause's `claimGuardRefs` mixes TWO vocabularies and only one is defined anywhere: a `document-claim-guard:` ref is the CATALOG's, added from the blueprint clauses the clause satisfies, and the evidence section carries its prohibited claims and reviewer instruction. A bare `claim-guard:` ref is the DRAFTER'S OWN statement of what its clause must not be read as claiming; no catalog defines it and none will be supplied. Read it as context about the clause's intent, and NEVER answer INDETERMINATE because its definition is absent — that is not missing evidence, it is a vocabulary that has no definitions, and read the clause's `bodyMarkdown` against each guard's prohibited claims and reviewer instruction. Look for: a claim of certification, attestation or audit without the authority to make it; a legal conclusion or legal advice (\"you are protected\", \"this is lawful\") rather than a statement of what the operator does; a NIST publication presented as legal equivalence; OPERATING EFFECTIVENESS — a sentence asserting that a control operates, works or worked (\"we monitor\", \"we detect\", \"access is always reviewed\") rather than that something is configured or declared; self-attestation presented as independent assurance; and an unscoped compliance claim (\"GDPR compliant\", \"fully secure\"). In a document whose guard names `document-claim-policy:public-safe-baseline`, ANY operating-effectiveness assertion is prohibited, whatever it cites. Do NOT re-check whether cited facts exist — landing already decided that exactly. Name every finding by its `clauseRef`, quote the words, and name the prohibited claim it falls under. Separate severities by CONSEQUENCE: a prohibited claim a reader of the published document would rely on is a GAP; wording that leans toward one without asserting it is a CONCERN.","schemaVersion":1,"verdictGuidance":{"CONCERN":"No prohibited claim is asserted, but wording leans toward one in a way a reader could take as the claim — a softened operating assertion, a scope left implicit. Name each clauseRef and quote it.","GAP":"At least one clause asserts a prohibited claim a reader would rely on. Name each clauseRef, quote the words, and name the prohibited claim.","INDETERMINATE":"The CATALOG guards of the drafted documents are absent from the evidence, or a document has no catalog guard at all, so the clauses cannot be judged against what they must not claim. Say which. A clause-level `claim-guard:` ref having no definition is NOT this: that vocabulary has none anywhere.","PASS":"No clause asserts a prohibited claim: nothing certifies, concludes the law, equates NIST with law, asserts a control operates in a public document, presents self-attestation as independence, or claims unscoped compliance."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/compliance-document-claims","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:refinement.compliance-document-candidate"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
1
+ {"aggregationPolicyRef":"application-creation:aggregation/worst-compliance-document-claims-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/compliance-document-claims-within-guard","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-document-claims-within-guard","requirementVersion":1}],"instruction":"The subject under judgment is each landed `compliance-document-candidate`. For EVERY clause, find the catalog claim guards it names in `claimGuardRefs` in the \"Catalog claim guards\" section of the evidence. A clause's `claimGuardRefs` mixes TWO vocabularies and only one is defined anywhere: a `document-claim-guard:` ref is the CATALOG's, added from the blueprint clauses the clause satisfies, and the evidence section carries its prohibited claims and reviewer instruction. A bare `claim-guard:` ref is the DRAFTER'S OWN statement of what its clause must not be read as claiming; no catalog defines it and none will be supplied. Read it as context about the clause's intent, and NEVER answer INDETERMINATE because its definition is absent — that is not missing evidence, it is a vocabulary that has no definitions, and read the clause's `bodyMarkdown` against each guard's prohibited claims and reviewer instruction. Look for: a claim of certification, attestation or audit without the authority to make it; a legal conclusion or legal advice (\"you are protected\", \"this is lawful\") rather than a statement of what the operator does; a NIST publication presented as legal equivalence; OPERATING EFFECTIVENESS — a sentence asserting that a control operates, works or worked (\"we monitor\", \"we detect\", \"access is always reviewed\") rather than that something is configured or declared; self-attestation presented as independent assurance; and an unscoped compliance claim (\"GDPR compliant\", \"fully secure\"). In a document whose guard names `document-claim-policy:public-safe-baseline`, an operating-effectiveness assertion is prohibited, with ONE exception (decided 2026-11-06, #3343): a statement of what the application's OWN RECORDS show, taken from a fact the runtime computes from records (`retention-enforcement`, `ai-content-guardrails`) and scoped to that fact's observation (\"as of <date>\", \"in the window <from>–<to>\"), is permitted, because it reports a record rather than the operator's judgement. Still prohibited in a public document: such a statement with no date or window, one that generalizes beyond it (\"runs on every call\", \"is always enforced\"), one that reads a quiet window as having run or as not having run, and any assertion resting on a judged run or an evidence citation. Do NOT re-check whether cited facts exist — landing already decided that exactly. Name every finding by its `clauseRef`, quote the words, and name the prohibited claim it falls under. Separate severities by CONSEQUENCE: a prohibited claim a reader of the published document would rely on is a GAP; wording that leans toward one without asserting it is a CONCERN.","schemaVersion":1,"verdictGuidance":{"CONCERN":"No prohibited claim is asserted, but wording leans toward one in a way a reader could take as the claim — a softened operating assertion, a scope left implicit. Name each clauseRef and quote it.","GAP":"At least one clause asserts a prohibited claim a reader would rely on. Name each clauseRef, quote the words, and name the prohibited claim.","INDETERMINATE":"The CATALOG guards of the drafted documents are absent from the evidence, or a document has no catalog guard at all, so the clauses cannot be judged against what they must not claim. Say which. A clause-level `claim-guard:` ref having no definition is NOT this: that vocabulary has none anywhere.","PASS":"No clause asserts a prohibited claim: nothing certifies, concludes the law, equates NIST with law, asserts a control operates in a public document, presents self-attestation as independence, or claims unscoped compliance."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/compliance-document-claims","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:refinement.compliance-document-candidate"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
@@ -1 +1 @@
1
- {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-compliance-document-candidate","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/compliance-document-claims-within-guard"],"requirementRef":"application-creation:authority-requirement/compliance-document-claims","requirementVersion":1,"riskClassRef":"application-creation:risk/compliance-claim-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/compliance-document-claims","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/compliance-document-claims","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/compliance-document-claims","policyVersion":1},"decisionPointRef":"application-creation:decision-point/compliance-document-claims","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/compliance-document-claims","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/compliance-document-claims","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-document-claims-within-guard","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/compliance-document-candidate-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/compliance-document-change","triggerRefs":["application-creation:trigger/compliance-document-candidate-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-compliance-document-claims-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/compliance-document-claims-within-guard"],"hardFloorRef":"application-creation:hard-floor/compliance-document-candidate-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/compliance-document-claims","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/compliance-document-claims","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-compliance-document-claims-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/compliance-document-claims-within-guard","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-document-claims-within-guard","requirementVersion":1}],"instruction":"The subject under judgment is each landed `compliance-document-candidate`. For EVERY clause, find the catalog claim guards it names in `claimGuardRefs` in the \"Catalog claim guards\" section of the evidence. A clause's `claimGuardRefs` mixes TWO vocabularies and only one is defined anywhere: a `document-claim-guard:` ref is the CATALOG's, added from the blueprint clauses the clause satisfies, and the evidence section carries its prohibited claims and reviewer instruction. A bare `claim-guard:` ref is the DRAFTER'S OWN statement of what its clause must not be read as claiming; no catalog defines it and none will be supplied. Read it as context about the clause's intent, and NEVER answer INDETERMINATE because its definition is absent — that is not missing evidence, it is a vocabulary that has no definitions, and read the clause's `bodyMarkdown` against each guard's prohibited claims and reviewer instruction. Look for: a claim of certification, attestation or audit without the authority to make it; a legal conclusion or legal advice (\"you are protected\", \"this is lawful\") rather than a statement of what the operator does; a NIST publication presented as legal equivalence; OPERATING EFFECTIVENESS — a sentence asserting that a control operates, works or worked (\"we monitor\", \"we detect\", \"access is always reviewed\") rather than that something is configured or declared; self-attestation presented as independent assurance; and an unscoped compliance claim (\"GDPR compliant\", \"fully secure\"). In a document whose guard names `document-claim-policy:public-safe-baseline`, ANY operating-effectiveness assertion is prohibited, whatever it cites. Do NOT re-check whether cited facts exist — landing already decided that exactly. Name every finding by its `clauseRef`, quote the words, and name the prohibited claim it falls under. Separate severities by CONSEQUENCE: a prohibited claim a reader of the published document would rely on is a GAP; wording that leans toward one without asserting it is a CONCERN.","schemaVersion":1,"verdictGuidance":{"CONCERN":"No prohibited claim is asserted, but wording leans toward one in a way a reader could take as the claim — a softened operating assertion, a scope left implicit. Name each clauseRef and quote it.","GAP":"At least one clause asserts a prohibited claim a reader would rely on. Name each clauseRef, quote the words, and name the prohibited claim.","INDETERMINATE":"The CATALOG guards of the drafted documents are absent from the evidence, or a document has no catalog guard at all, so the clauses cannot be judged against what they must not claim. Say which. A clause-level `claim-guard:` ref having no definition is NOT this: that vocabulary has none anywhere.","PASS":"No clause asserts a prohibited claim: nothing certifies, concludes the law, equates NIST with law, asserts a control operates in a public document, presents self-attestation as independence, or claims unscoped compliance."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/compliance-document-claims","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:refinement.compliance-document-candidate"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/compliance-document-claims","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-catalog-claim-guards-of-drafted-documents","criterionRef":"application-creation:criterion/compliance-document-claims-within-guard","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-document-claims-within-guard","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/compliance-document-candidates-and-catalog-claim-guards"}],"schemaVersion":1}
1
+ {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-compliance-document-candidate","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/compliance-document-claims-within-guard"],"requirementRef":"application-creation:authority-requirement/compliance-document-claims","requirementVersion":1,"riskClassRef":"application-creation:risk/compliance-claim-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/compliance-document-claims","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/compliance-document-claims","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/compliance-document-claims","policyVersion":1},"decisionPointRef":"application-creation:decision-point/compliance-document-claims","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/compliance-document-claims","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/compliance-document-claims","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-document-claims-within-guard","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/compliance-document-candidate-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/compliance-document-change","triggerRefs":["application-creation:trigger/compliance-document-candidate-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-compliance-document-claims-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/compliance-document-claims-within-guard"],"hardFloorRef":"application-creation:hard-floor/compliance-document-candidate-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/compliance-document-claims","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/compliance-document-claims","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-compliance-document-claims-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/compliance-document-claims-within-guard","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-document-claims-within-guard","requirementVersion":1}],"instruction":"The subject under judgment is each landed `compliance-document-candidate`. For EVERY clause, find the catalog claim guards it names in `claimGuardRefs` in the \"Catalog claim guards\" section of the evidence. A clause's `claimGuardRefs` mixes TWO vocabularies and only one is defined anywhere: a `document-claim-guard:` ref is the CATALOG's, added from the blueprint clauses the clause satisfies, and the evidence section carries its prohibited claims and reviewer instruction. A bare `claim-guard:` ref is the DRAFTER'S OWN statement of what its clause must not be read as claiming; no catalog defines it and none will be supplied. Read it as context about the clause's intent, and NEVER answer INDETERMINATE because its definition is absent — that is not missing evidence, it is a vocabulary that has no definitions, and read the clause's `bodyMarkdown` against each guard's prohibited claims and reviewer instruction. Look for: a claim of certification, attestation or audit without the authority to make it; a legal conclusion or legal advice (\"you are protected\", \"this is lawful\") rather than a statement of what the operator does; a NIST publication presented as legal equivalence; OPERATING EFFECTIVENESS — a sentence asserting that a control operates, works or worked (\"we monitor\", \"we detect\", \"access is always reviewed\") rather than that something is configured or declared; self-attestation presented as independent assurance; and an unscoped compliance claim (\"GDPR compliant\", \"fully secure\"). In a document whose guard names `document-claim-policy:public-safe-baseline`, an operating-effectiveness assertion is prohibited, with ONE exception (decided 2026-11-06, #3343): a statement of what the application's OWN RECORDS show, taken from a fact the runtime computes from records (`retention-enforcement`, `ai-content-guardrails`) and scoped to that fact's observation (\"as of <date>\", \"in the window <from>–<to>\"), is permitted, because it reports a record rather than the operator's judgement. Still prohibited in a public document: such a statement with no date or window, one that generalizes beyond it (\"runs on every call\", \"is always enforced\"), one that reads a quiet window as having run or as not having run, and any assertion resting on a judged run or an evidence citation. Do NOT re-check whether cited facts exist — landing already decided that exactly. Name every finding by its `clauseRef`, quote the words, and name the prohibited claim it falls under. Separate severities by CONSEQUENCE: a prohibited claim a reader of the published document would rely on is a GAP; wording that leans toward one without asserting it is a CONCERN.","schemaVersion":1,"verdictGuidance":{"CONCERN":"No prohibited claim is asserted, but wording leans toward one in a way a reader could take as the claim — a softened operating assertion, a scope left implicit. Name each clauseRef and quote it.","GAP":"At least one clause asserts a prohibited claim a reader would rely on. Name each clauseRef, quote the words, and name the prohibited claim.","INDETERMINATE":"The CATALOG guards of the drafted documents are absent from the evidence, or a document has no catalog guard at all, so the clauses cannot be judged against what they must not claim. Say which. A clause-level `claim-guard:` ref having no definition is NOT this: that vocabulary has none anywhere.","PASS":"No clause asserts a prohibited claim: nothing certifies, concludes the law, equates NIST with law, asserts a control operates in a public document, presents self-attestation as independence, or claims unscoped compliance."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/compliance-document-claims","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:refinement.compliance-document-candidate"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/compliance-document-claims","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-catalog-claim-guards-of-drafted-documents","criterionRef":"application-creation:criterion/compliance-document-claims-within-guard","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-document-claims-within-guard","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/compliance-document-candidates-and-catalog-claim-guards"}],"schemaVersion":1}