@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,6 +1,6 @@
1
1
  {
2
2
  "ref": "refinement.feature-contribution",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "phase": "refinement",
5
5
  "intent": "Add ONE feature to the product model, as the feature-development line it runs for describes it: the functional requirements the feature adds, and one spec-first, ref-less feature draft per capability it needs, each tracing to those requirements. Return only what the feature adds; everything the application already holds stays as it is.",
6
6
  "preconditions": [
@@ -29,7 +29,13 @@
29
29
  },
30
30
  {
31
31
  "family": "domain-plan",
32
- "render": "map"
32
+ "render": "map",
33
+ "notReopenedBy": [
34
+ {
35
+ "playbookRef": "bottom_up.domain-plan",
36
+ "reason": "This adds ONE feature, once, on request: a domain plan that moves after it is not a reason to add the feature again, and the domain plan reads the feature back (#3450)."
37
+ }
38
+ ]
33
39
  }
34
40
  ],
35
41
  "outputs": [
@@ -51,6 +57,7 @@
51
57
  "spec-feature-update"
52
58
  ],
53
59
  "skillBodyRefs": [],
60
+ "derivedFromAnswers": [],
54
61
  "contextSources": [],
55
62
  "draftableDocumentDefinitionRefs": [],
56
63
  "suspendsForClarification": false,
@@ -239,9 +239,10 @@ table; the administrative-continuity floors (a tenant cannot be left with no usa
239
239
  application cannot be left with no super-administrator); and the platform-access-grant mechanism,
240
240
  under which a platform operator crossing the per-record tenant boundary requires a granted,
241
241
  time-bounded authorization. Application-wide directory reads retain independent approval. The
242
- application audit viewer has a distinct policy: `auditTrail.applicationReadAccess` defaults to
243
- `AuditApplicationReadAccess.ROLE_BASED` in every environment, admitting the super-administrator or the
244
- read-only audit-evidence reader role; `INDEPENDENT_APPROVAL` requires a usable application-wide grant in
242
+ application audit viewer has a distinct policy: `auditTrail.applicationReadAccess`, when undeclared,
243
+ follows the application's shape in every environment — `AuditApplicationReadAccess.INDEPENDENT_APPROVAL`
244
+ where the parties of one of its relationship kinds are independent of its operator, `ROLE_BASED` otherwise. `ROLE_BASED` admits the
245
+ super-administrator or the read-only audit-evidence reader role; `INDEPENDENT_APPROVAL` requires a usable application-wide grant in
245
246
  addition to the role, and a machine reader (such as an assurance collector) holds one only when it is bound to
246
247
  its own credential and signed by a second administrator — a grant bound to a machine never admits the
247
248
  administrator who requested it. Access admission, audit observation and retained
@@ -291,9 +292,10 @@ operator's responsibilities and the customer's lies.
291
292
  **Derives from** — the `ORGANIZATIONS` engine capability, the organization scoping applied to every
292
293
  tenant-scoped resource, and the cross-tenant admission rules. Ordinary tenant crossings must be
293
294
  declared and carry a usable access grant. The application audit viewer is a separate policy surface:
294
- it defaults to role-based access (the super-administrator or the read-only audit-evidence reader), with
295
- `auditTrail.applicationReadAccess` optionally set to `AuditApplicationReadAccess.INDEPENDENT_APPROVAL`, under
296
- which a machine reader needs a second-signed grant bound to its own credential. Both modes retain cross-tenant read observations;
295
+ it follows `auditTrail.applicationReadAccess`, which defaults by the application's shape:
296
+ `AuditApplicationReadAccess.INDEPENDENT_APPROVAL` where the parties of one of its relationship kinds are independent of its operator, role-based
297
+ access (the super-administrator or the read-only audit-evidence reader) otherwise. Under independent approval a
298
+ machine reader needs a second-signed grant bound to its own credential. Both modes retain cross-tenant read observations;
297
299
  role-based access neither implies anonymized records nor supplies an approval that never occurred.
298
300
 
299
301
  **Completeness** — `DERIVED`.
@@ -25,11 +25,12 @@
25
25
  ],
26
26
  "stepOutputs": [],
27
27
  "method": {
28
- "guidance": "# Governance document candidate method\n\nYou are drafting ONE internal governance document for this application, from what the application has\nalready declared. Follow the `compliance-document-authoring` skill for the rules — refs, clause shape,\ncompleteness, what a clause may say. This method says which document, what its concerns are, and the two\nthings a governance document meets that a public notice does not.\n\n## Choose the document, from the four this lane may draft\n\nThe candidate contract admits six `documentRef` values. Four of them are this lane's; the two public ones\n(`document:public.privacy-notice`, `document:public.service-terms`) belong to\n`refinement.compliance-document-candidate` and are not yours to draft here.\n\n| `documentRef` | what it is | its concerns |\n|---|---|---|\n| `document:governance.scope-system-description` | what the system IS, for an assurance reader | service scope, security controls, audit and accountability, access control and roles, tenancy model |\n| `document:governance.roles-responsibilities` | who is accountable for what | access control and roles, operator identity |\n| `document:governance.program-handbook` | how the governance programme runs | security controls, audit and accountability, access control and roles |\n| `document:governance.document-record-control` | how governed documents are themselves controlled | **none** — see below |\n\n**Draft a document this application does not already hold.** The brief opens with what it has already\ndrafted, listing each document this lane may produce as ALREADY DRAFTED or not yet. Drafts are keyed by\n`documentRef`, so drafting one that is already there REPLACES it — right when that draft is wrong, a\nwasted run when it is not.\n\n**A held draft marked ALREADY DRAFTED, and WRONG comes before everything below.** The brief marks a held\ndraft that cites facts this application no longer declares, and names them. Nothing else corrects it: the\nlanding checks only the document a run writes, so a draft written before the facts were regenerated keeps\nits dead citations until a run redrafts that document. Redraft it against the facts that exist, and cite\nnone of the named ones.\n\nWhere several remain, **scope and system description** comes first: it is the one an assurance reader\nopens first, the one the other three refer back to, and the only one of the four carrying facts the\nframework derives rather than a person establishes.\n\n`document:governance.document-record-control` composes **no application-fact concern**, and that is\ndeclared rather than missing: it describes how documents are identified, reviewed, released and retired —\na process the operator defines, not anything derivable from the product. Every section you write for it\ncarries `concernRef: null`, and almost every clause is marked. That is the document working, not failing.\n\n## Expect to MARK, and never invent your way past a mark\n\nMost of what a governance document asserts is established by a PERSON, not derived from the application.\nMeasured on the blueprints: `roles-responsibilities` and `document-record-control` carry no\nspecification-derived fact at all — every one of their facts needs a creator decision or a qualified\nreview — and the other two carry a handful.\n\nSo a governance draft that is largely marked incomplete is the expected outcome. Draft every section,\nstate precisely what is missing in `incompleteness.needs` and what would close it in\n`incompleteness.closedBy`, and let the marks be the document's contribution. An application that can read\nexactly which governance decisions it owes is further ahead than one holding no document at all.\n\n**Two inventions are worse than any gap, and both are specific to these documents.**\n\n- **A record of review that did not happen.** These are the documents where a reviewer, an approver, an\n approval, an independence disclosure, a qualification and a decision instant are NAMED. Write one the\n application has not declared and you have not written a weak sentence — you have fabricated the record\n of a review nobody performed. Mark it instead: the fact is owed, and saying so is the answer.\n- **A control asserted to OPERATE, with nothing behind it.** \"Access is reviewed quarterly\", \"we\n monitor\", \"the trail is checked\" are claims about operating effectiveness. In THIS lane one of them\n may be legitimate — and only when a judged run in your brief's evidence section supports it, the\n clause cites that run, and the clause says what was measured and over what period. Without all three,\n say what is CONFIGURED or DECLARED, which is what the facts give you, and mark the rest.\n\n## One section per concern, and SAY which concern\n\nEvery section carries `concernRef` from the closed compliance-concern vocabulary, or `null` for a section\nthat genuinely answers no concern — a preamble, a scope statement, and every section of\n`document-record-control`. Draft one section per concern in the order the table above gives, and produce\n**every** one: a concern nothing can answer becomes a section with a marked clause, never a missing\nheading.\n\nThe value must be the concern's exact name. A near miss (`access-control` for\n`access-control-and-roles`) is worse than a null: it reports the concern as unaddressed while the\ndocument addresses it.\n\nEach section also names what it satisfies in the catalog — `satisfiesSectionRefs` on the section,\n`satisfiesClauseRefs` on each clause, from the blueprint in your brief. Those are what attach the\ncatalog's claim guards to your clauses, so a clause that says what it satisfies is checked against what it\nmust not claim, automatically. A clause that says nothing is checked against nothing.\n\nA section that supplies no required part of the document answers **`null`**, never `[]` — an empty array\nis refused, because it would be a second spelling of the same state. On a governance document the sections\nthat answer `null` are the ones with `concernRef: null` beside them, and `document-record-control` is\nmostly made of them.\n\n## The three ref arrays on every clause\n\nEvery `…Ref` field is a **namespaced ref**: `namespace:slug`, both halves lowercase, words joined by\nhyphens. One malformed ref rejects the whole draft, and all three arrays are required on every clause —\ntwo of them may be empty, but **not the first two at once**, because a clause naming neither a fact nor a\npolicy area is sourced by nothing.\n\n- `factRefs` — the facts this clause rests on, spelled exactly as the facts file declares them. EMPTY is\n normal here: a marked clause usually establishes nothing.\n- `sourcePolicyRefs` — the application POLICY AREA the statement is sourced from, and **every entry must\n be in the `policy:` namespace**: `policy:security-controls`, `policy:access-control`,\n `policy:document-control`. Any other namespace is rejected outright — `policy-area:…` is not a policy\n ref, and neither is a fact ref repeated here. **Do NOT put a fact or its authority in this array.** A\n clause resting on declared facts already cites them through `factRefs`, which resolves them; restating\n one here duplicates the citation beside it and resolves to nothing. So this array is EMPTY for a\n fact-backed clause, and carries a policy area for a clause sourced from a policy rather than a fact.\n- `claimGuardRefs` — at least one: what this clause must NOT be read as claiming. Name the ones that\n apply; do not repeat the same guard on every clause out of habit. You do not name the CATALOG's guard\n for the material — that is added for you from the blueprint clauses this clause `satisfiesClauseRefs`.\n\n`reviewChecklistRefs` needs at least one (`review-checklist:<slug>`): what a human must confirm before\nthis draft is worth anything. On a governance document that list is long, and it is where \"who reviewed\nthis, and when\" belongs — as something a person must supply, never as a name you write into a clause.\n\n`limitationRefs` may be empty and rarely should be: it is where you say, in your own words, what this\ndocument does NOT cover.\n\n## What the blueprint gives you\n\nthe declared `document_blueprint` context section of your brief carries, for each document this lane may draft, its sections, its\nclauses and which of them are required. Read the one matching your `documentRef` and treat its required\nclauses as the floor: a required clause you cannot establish is a clause you MARK, never one you omit.\n\n## Citing this application's own measured evidence\n\nA governance document is the one place an operator may say what its controls DO, and this lane is the\nonly one that may cite the measurements behind such a statement.\n\nthe declared `assurance_evidence` context section of your brief carries the judged runs this application's own assurance cycle has\ncommitted: what was measured, under which demand, with what verdict, at which framework revision, and\nwhether the judge was calibrated. Read it before writing any sentence about what a control does.\n\n- **Cite by putting the run's `assurance-run:` ref in the clause's `evidenceRefs`**, and say in the\n clause what was measured and over what period. A citation a reader cannot scope is one they cannot\n check.\n- **Only a run whose verdict CONCLUDED may support such a statement.** The section marks each one. A\n clause resting on an `INSUFFICIENT_EVIDENCE` run asserts a measurement that did not settle the\n question, which is worse than saying nothing.\n- **Say what it is.** The operator judged its own product with its own harness. A clause may say that\n and what it found; it may not say the result was verified, certified, audited or independently\n assured, and the claim guards refuse the sentence that blurs the two.\n- **Where no run supports the statement, MARK it** — the same answer this lane gives every\n unestablished statement, and the right one.\n\nA ref that resolves to no committed run is refused before the draft becomes a file, as is any citation\nat all in a PUBLIC document. Neither is your judgement to make here: cite only what the section lists.\n\n## You do not approve, release or publish\n\nYou draft the candidate. A human accepts it by committing it; nothing else is acceptance, and landing is\nnot approval. You do not author the release — almost everything a release carries is derived from the\naccepted document definition, and a release nobody has approved is composed and marked `UNAPPROVED`\nrather than withheld.\n\n**Which is why a missing approval never changes what you do here.** Waiting for one before drafting, and\ndescribing a draft as approved to get past a gate, are the two symmetric failures; the first is a\ncompliance workflow standing in front of the mechanism that builds the application.\n\n## Where the draft goes\n\nIt lands as a FILE in the application's specifications package, as an ordinary working edit, beside any\npublic candidates the application already holds.\n\n---\n\n# The compositions\n\nEach entry below is one concern: what it asserts, what in the application it derives from, what state it\nusually reaches, and what closes it when it cannot. Use the ones your document's row names and ignore the\nrest.\n\n### Concern: service scope\n\n**Asserts** — what the service actually is: the modules it runs, the resources it manages, and the\nsurfaces it exposes.\n\n**Derives from** — the application's declared modules and their resources, and the surfaces it builds\n(application, API, public website, technical documentation).\n\n**Completeness** — `DERIVED`.\n\n**Derive it; do not describe the product from its marketing.** Scope in a governed document is the\nboundary of what the statements around it apply to, so an aspirational description silently widens\nevery other clause. The declared modules are the honest boundary, and a capability the application\ndoes not run does not belong here even if it is on the roadmap.\n\n\n### Concern: security controls\n\n**Asserts** — the security measures the application actually runs, at the level of detail a notice\nneeds and no further.\n\n**Derives from** — the application's authored authentication configuration (methods enabled, MFA,\npassword policy, lockout, step-up, session lifetimes), its access floors, its encryption of stored\nsecrets, and its antivirus posture where the `ANTIVIRUS_SCANNING` INFRA capability is provisioned\n(ClamAV, consumed by the engine's file-scanning service on upload). Note this reads the INFRA\ncapability, not an engine provider slot: the equally-named `EngineCapability.ANTIVIRUS_SCANNING` was\nwithdrawn because no provider could fill it, and a derived control statement must never rest on a\nslot that cannot be configured.\n\n**Completeness** — `DERIVED`, bounded.\n\n**Bounded is the operative word.** A public notice states that measures exist and their general\nnature. **It must not enumerate the control set**: a published list of exactly which protections are\nin place, and by implication which are not, is a map for somebody attacking the service. Detail\nbelongs in a security addendum shared under agreement, not on a public page — so this fragment reads\nvery differently in `public.privacy-notice` than in a security schedule, and that difference is\ndeliberate rather than an omission.\n\n**Never state a certification.** \"Compliant\", \"certified\", \"audited\" and \"ISO/SOC\" claims are not\nderivable from configuration and are not this document's to make.\n\n\n### Concern: audit and accountability\n\n**Asserts** — that security-relevant actions are recorded, what kinds are recorded, and where those\nrecords can be sent.\n\n**Derives from** — the application's own audit store, which every application writes; the\n`COMPLIANCE_AUDIT_TRAIL` engine capability, which additionally sends each event to external providers\n(`saas-models` → `external-providers/engine-capabilities.shared.schemas.ts`); the auditable-event\ncatalog the engine emits (authentication, authorization grants, consent decisions, token lifecycle,\nconfiguration and permission changes, cross-tenant administrative access), and per-organization SIEM\nrouting where a tenant has configured it.\n\n**Completeness** — `DERIVED`.\n\nThis is one of the fragments where the ENGINE answers for the application. Every generated\napplication inherits the event catalog and the emitters; a document may state it without the\napplication having configured anything. Where a tenant has additionally routed events to its own\nSIEM, that is the tenant's configuration and belongs in a shared-responsibility statement rather than\nin the operator's own notice.\n\n\n### Concern: access control and roles\n\n**Asserts** — who inside the operator and inside a customer tenant can reach personal data, and what\nconstrains them.\n\n**Derives from** — `CORE_APP_ROLES` and `CORE_ORG_ROLES`\n(`saas-models` → `security/authorizations/roles.shared.schemas.ts`) plus the application's own role\ntable; the administrative-continuity floors (a tenant cannot be left with no usable owner, the\napplication cannot be left with no super-administrator); and the platform-access-grant mechanism,\nunder which a platform operator crossing the per-record tenant boundary requires a granted,\ntime-bounded authorization. Application-wide directory reads retain independent approval. The\napplication audit viewer has a distinct policy: `auditTrail.applicationReadAccess` defaults to\n`AuditApplicationReadAccess.ROLE_BASED` in every environment, admitting the super-administrator or the\nread-only audit-evidence reader role; `INDEPENDENT_APPROVAL` requires a usable application-wide grant in\naddition to the role, and a machine reader (such as an assurance collector) holds one only when it is bound to\nits own credential and signed by a second administrator — a grant bound to a machine never admits the\nadministrator who requested it. Access admission, audit observation and retained\nevidence are separate claims: the access decision does not depend on a successful audit write.\n\n**Completeness** — `DERIVED`.\n\nWorth stating plainly in a B2B notice, because it is the question a customer's own reviewer asks\nfirst: **operator access is governed by the resource and its declared policy.** Ordinary tenant\ncrossings require a usable grant. The application audit viewer is role-based by default, with\nindependent approval available as an explicit policy. Its cross-tenant observations still identify\nthe operator and tenants reached; role-based access does not imply anonymized logs or fabricate an\napproval record. Actual application-wide grants always retain their independent-approval requirement.\n\n**Observation coverage** — the per-record organization gate observes access to an identifiable\ntenant's record when the caller does not already hold organization-wide entry there. Separately,\ndeclared cross-tenant READ, LIST and SEARCH operations outside the organization-scoped gate observe\nthe identifiable tenants in their returned records that the caller does not already belong to,\ngrouped into one observation per tenant reached. This collection observer excludes context-free\ninternal requests and webhook callbacks; COUNT\nreturns no records and is not covered by that observer. Do not turn these scoped mechanisms into a\nclaim that every operation or every returned record produces an audit entry.\n\n**Delivery and evidence** — these observations are best-effort and do not fail the observed request.\nAn unavailable audit service, a synchronous emission error or a rejected emission can leave an\nauthorized request without a retained crossing entry. Observer-side drops have an\n`audit_observation_dropped_total` signal and throttled error logs; failures at the primary audit-store\nwrite have the separate `audit_store_failure_total` signal. Metrics export and log retention must\nactually be configured and operating for those signals to provide evidence beyond the process.\nNeither a loss counter nor an attempted emission substitutes for the missing audit entry.\n\n**Document-authoring consequence** — derive the roles, operation declarations and usable-grant\nrequirements and the audit viewer's access policy from the application's configuration. Do not\nclaim that every audit read required independent approval when the viewer is role-based. Describe the observation mechanisms as supported\ncoverage, then substantiate any statement about recorded access with retained audit records and\nevidence that the collection pipeline and loss monitoring were operating over the period claimed.\nAn empty crossing search alone does not prove that no operator accessed tenant data. `DERIVED`\nabove identifies the source of the access-control description; it does not certify complete audit\ndelivery or the application's operational compliance.\n\n\n### Concern: tenancy model\n\n**Asserts** — that customer data is separated per organization, and where the boundary between the\noperator's responsibilities and the customer's lies.\n\n**Derives from** — the `ORGANIZATIONS` engine capability, the organization scoping applied to every\ntenant-scoped resource, and the cross-tenant admission rules. Ordinary tenant crossings must be\ndeclared and carry a usable access grant. The application audit viewer is a separate policy surface:\nit defaults to role-based access (the super-administrator or the read-only audit-evidence reader), with\n`auditTrail.applicationReadAccess` optionally set to `AuditApplicationReadAccess.INDEPENDENT_APPROVAL`, under\nwhich a machine reader needs a second-signed grant bound to its own credential. Both modes retain cross-tenant read observations;\nrole-based access neither implies anonymized records nor supplies an approval that never occurred.\n\n**Completeness** — `DERIVED`.\n\n**This fragment is where shared responsibility is described, and it must never be flattened.** In a\nB2B SaaS the operator is a PROCESSOR for the data a customer stores about its own people, and a\nCONTROLLER for the data it holds about the customer's users as account holders. Those are different\nroles with different duties over the same database. Say which is which; do not pick one and apply it\nto everything.\n\n**The attribution has a home now.** `operatorComplianceIdentity.roleAllocations` in\n`wildo.saas.config.ts` carries one role per population of data — PROCESSOR for the records a customer\nstores about its own people, CONTROLLER for the account data of the people who administer them. It is\na LIST for exactly the reason this fragment gives: those are different roles over the same database,\nand a single field would force one of them to be wrong.\n\nWhere the attribution is not established, that is a `NEEDS_DECISION` — never a guess — and the\nsurface to name is `roleAllocations`. Not `NEEDS_FRAMEWORK`: there is somewhere to write the answer,\nso the remedy is to fill it in rather than to build something. See the legal-basis fragment.\n\n\n### Concern: operator identity\n\n**Asserts** — who legally operates the service: entity name, registered address, contact route for\ndata-protection questions, and a representative where one is required.\n\n**Derives from** — `operatorComplianceIdentity` in `wildo.saas.config.ts`: the legal entity, its\nregistered address, the privacy contact route, and an Art. 27 representative where one is required.\n\nThe VALUE is never derivable — a legal entity is a fact about the world, not a property of a codebase.\nWhat the framework provides is the PLACE to record it, and until 2026-08-30 it did not: this fragment\nsaid \"no engine change would close it\", which was right about derivation and wrong about the home.\nThe consequence was concrete. A landing REPLACES the produced document on every run, so an operator\nwho answered by editing the document lost the answer at the next regeneration — the answer has to live\nin the application or it does not survive.\n\n**Completeness** — `DERIVED` when the identity is declared; `NEEDS_DECISION` when it is not.\n\n⚠️ `NEEDS_DECISION`, not `NEEDS_FRAMEWORK`, and the distinction is load-bearing now that the surface\nexists. `NEEDS_FRAMEWORK` means there is nowhere to record the answer; `NEEDS_DECISION` means there is\nand nobody has. They have different remedies — build something, versus fill something in — and a\nreader who cannot tell them apart cannot act on either. Say which surface the answer goes to.\n\n**What closes it** — the operator declaring `operatorComplianceIdentity`. It is cheap and it can be\nfilled in later without redrafting anything around it, which is the reason it is not a blocker.\n\n**Never infer it.** Not from the application name, not from a domain, not from another application,\nnot from model memory. A published legal document naming the wrong entity is worse than one that says\nthe entity is not yet recorded — the first misdirects a person exercising a right, the second tells\nthem the document is incomplete.\n\n**Every document needs this fragment**, which makes it the clearest demonstration of why producing\nwith gaps beats blocking: the whole document set would be unproducible until one form is filled in.\n",
28
+ "guidance": "# Governance document candidate method\n\nYou are drafting ONE internal governance document for this application, from what the application has\nalready declared. Follow the `compliance-document-authoring` skill for the rules — refs, clause shape,\ncompleteness, what a clause may say. This method says which document, what its concerns are, and the two\nthings a governance document meets that a public notice does not.\n\n## Choose the document, from the four this lane may draft\n\nThe candidate contract admits six `documentRef` values. Four of them are this lane's; the two public ones\n(`document:public.privacy-notice`, `document:public.service-terms`) belong to\n`refinement.compliance-document-candidate` and are not yours to draft here.\n\n| `documentRef` | what it is | its concerns |\n|---|---|---|\n| `document:governance.scope-system-description` | what the system IS, for an assurance reader | service scope, security controls, audit and accountability, access control and roles, tenancy model |\n| `document:governance.roles-responsibilities` | who is accountable for what | access control and roles, operator identity |\n| `document:governance.program-handbook` | how the governance programme runs | security controls, audit and accountability, access control and roles |\n| `document:governance.document-record-control` | how governed documents are themselves controlled | **none** — see below |\n\n**Draft a document this application does not already hold.** The brief opens with what it has already\ndrafted, listing each document this lane may produce as ALREADY DRAFTED or not yet. Drafts are keyed by\n`documentRef`, so drafting one that is already there REPLACES it — right when that draft is wrong, a\nwasted run when it is not.\n\n**A held draft marked ALREADY DRAFTED, and WRONG comes before everything below.** The brief marks a held\ndraft that cites facts this application no longer declares, and names them. Nothing else corrects it: the\nlanding checks only the document a run writes, so a draft written before the facts were regenerated keeps\nits dead citations until a run redrafts that document. Redraft it against the facts that exist, and cite\nnone of the named ones.\n\nWhere several remain, **scope and system description** comes first: it is the one an assurance reader\nopens first, the one the other three refer back to, and the only one of the four carrying facts the\nframework derives rather than a person establishes.\n\n`document:governance.document-record-control` composes **no application-fact concern**, and that is\ndeclared rather than missing: it describes how documents are identified, reviewed, released and retired —\na process the operator defines, not anything derivable from the product. Every section you write for it\ncarries `concernRef: null`, and almost every clause is marked. That is the document working, not failing.\n\n## Expect to MARK, and never invent your way past a mark\n\nMost of what a governance document asserts is established by a PERSON, not derived from the application.\nMeasured on the blueprints: `roles-responsibilities` and `document-record-control` carry no\nspecification-derived fact at all — every one of their facts needs a creator decision or a qualified\nreview — and the other two carry a handful.\n\nSo a governance draft that is largely marked incomplete is the expected outcome. Draft every section,\nstate precisely what is missing in `incompleteness.needs` and what would close it in\n`incompleteness.closedBy`, and let the marks be the document's contribution. An application that can read\nexactly which governance decisions it owes is further ahead than one holding no document at all.\n\n**Two inventions are worse than any gap, and both are specific to these documents.**\n\n- **A record of review that did not happen.** These are the documents where a reviewer, an approver, an\n approval, an independence disclosure, a qualification and a decision instant are NAMED. Write one the\n application has not declared and you have not written a weak sentence — you have fabricated the record\n of a review nobody performed. Mark it instead: the fact is owed, and saying so is the answer.\n- **A control asserted to OPERATE, with nothing behind it.** \"Access is reviewed quarterly\", \"we\n monitor\", \"the trail is checked\" are claims about operating effectiveness. In THIS lane one of them\n may be legitimate — and only when a judged run in your brief's evidence section supports it, the\n clause cites that run, and the clause says what was measured and over what period. Without all three,\n say what is CONFIGURED or DECLARED, which is what the facts give you, and mark the rest.\n\n## One section per concern, and SAY which concern\n\nEvery section carries `concernRef` from the closed compliance-concern vocabulary, or `null` for a section\nthat genuinely answers no concern — a preamble, a scope statement, and every section of\n`document-record-control`. Draft one section per concern in the order the table above gives, and produce\n**every** one: a concern nothing can answer becomes a section with a marked clause, never a missing\nheading.\n\nThe value must be the concern's exact name. A near miss (`access-control` for\n`access-control-and-roles`) is worse than a null: it reports the concern as unaddressed while the\ndocument addresses it.\n\nEach section also names what it satisfies in the catalog — `satisfiesSectionRefs` on the section,\n`satisfiesClauseRefs` on each clause, from the blueprint in your brief. Those are what attach the\ncatalog's claim guards to your clauses, so a clause that says what it satisfies is checked against what it\nmust not claim, automatically. A clause that says nothing is checked against nothing.\n\nA section that supplies no required part of the document answers **`null`**, never `[]` — an empty array\nis refused, because it would be a second spelling of the same state. On a governance document the sections\nthat answer `null` are the ones with `concernRef: null` beside them, and `document-record-control` is\nmostly made of them.\n\n## The three ref arrays on every clause\n\nEvery `…Ref` field is a **namespaced ref**: `namespace:slug`, both halves lowercase, words joined by\nhyphens. One malformed ref rejects the whole draft, and all three arrays are required on every clause —\ntwo of them may be empty, but **not the first two at once**, because a clause naming neither a fact nor a\npolicy area is sourced by nothing.\n\n- `factRefs` — the facts this clause rests on, spelled exactly as the facts file declares them. EMPTY is\n normal here: a marked clause usually establishes nothing.\n- `sourcePolicyRefs` — the application POLICY AREA the statement is sourced from, and **every entry must\n be in the `policy:` namespace**: `policy:security-controls`, `policy:access-control`,\n `policy:document-control`. Any other namespace is rejected outright — `policy-area:…` is not a policy\n ref, and neither is a fact ref repeated here. **Do NOT put a fact or its authority in this array.** A\n clause resting on declared facts already cites them through `factRefs`, which resolves them; restating\n one here duplicates the citation beside it and resolves to nothing. So this array is EMPTY for a\n fact-backed clause, and carries a policy area for a clause sourced from a policy rather than a fact.\n- `claimGuardRefs` — at least one: what this clause must NOT be read as claiming. Name the ones that\n apply; do not repeat the same guard on every clause out of habit. You do not name the CATALOG's guard\n for the material — that is added for you from the blueprint clauses this clause `satisfiesClauseRefs`.\n\n`reviewChecklistRefs` needs at least one (`review-checklist:<slug>`): what a human must confirm before\nthis draft is worth anything. On a governance document that list is long, and it is where \"who reviewed\nthis, and when\" belongs — as something a person must supply, never as a name you write into a clause.\n\n`limitationRefs` may be empty and rarely should be: it is where you say, in your own words, what this\ndocument does NOT cover.\n\n## What the blueprint gives you\n\nthe declared `document_blueprint` context section of your brief carries, for each document this lane may draft, its sections, its\nclauses and which of them are required. Read the one matching your `documentRef` and treat its required\nclauses as the floor: a required clause you cannot establish is a clause you MARK, never one you omit.\n\n## Citing this application's own measured evidence\n\nA governance document is the one place an operator may say what its controls DO, and this lane is the\nonly one that may cite the measurements behind such a statement.\n\nthe declared `assurance_evidence` context section of your brief carries the judged runs this application's own assurance cycle has\ncommitted: what was measured, under which demand, with what verdict, at which framework revision, and\nwhether the judge was calibrated. Read it before writing any sentence about what a control does.\n\n- **Cite by putting the run's `assurance-run:` ref in the clause's `evidenceRefs`**, and say in the\n clause what was measured and over what period. A citation a reader cannot scope is one they cannot\n check.\n- **Only a run whose verdict CONCLUDED may support such a statement.** The section marks each one. A\n clause resting on an `INSUFFICIENT_EVIDENCE` run asserts a measurement that did not settle the\n question, which is worse than saying nothing.\n- **Say what it is.** The operator judged its own product with its own harness. A clause may say that\n and what it found; it may not say the result was verified, certified, audited or independently\n assured, and the claim guards refuse the sentence that blurs the two.\n- **Where no run supports the statement, MARK it** — the same answer this lane gives every\n unestablished statement, and the right one.\n\nA ref that resolves to no committed run is refused before the draft becomes a file, as is any citation\nat all in a PUBLIC document. Neither is your judgement to make here: cite only what the section lists.\n\n## You do not approve, release or publish\n\nYou draft the candidate. A human accepts it by committing it; nothing else is acceptance, and landing is\nnot approval. You do not author the release — almost everything a release carries is derived from the\naccepted document definition, and a release nobody has approved is composed and marked `UNAPPROVED`\nrather than withheld.\n\n**Which is why a missing approval never changes what you do here.** Waiting for one before drafting, and\ndescribing a draft as approved to get past a gate, are the two symmetric failures; the first is a\ncompliance workflow standing in front of the mechanism that builds the application.\n\n## Where the draft goes\n\nIt lands as a FILE in the application's specifications package, as an ordinary working edit, beside any\npublic candidates the application already holds.\n\n---\n\n# The compositions\n\nEach entry below is one concern: what it asserts, what in the application it derives from, what state it\nusually reaches, and what closes it when it cannot. Use the ones your document's row names and ignore the\nrest.\n\n### Concern: service scope\n\n**Asserts** — what the service actually is: the modules it runs, the resources it manages, and the\nsurfaces it exposes.\n\n**Derives from** — the application's declared modules and their resources, and the surfaces it builds\n(application, API, public website, technical documentation).\n\n**Completeness** — `DERIVED`.\n\n**Derive it; do not describe the product from its marketing.** Scope in a governed document is the\nboundary of what the statements around it apply to, so an aspirational description silently widens\nevery other clause. The declared modules are the honest boundary, and a capability the application\ndoes not run does not belong here even if it is on the roadmap.\n\n\n### Concern: security controls\n\n**Asserts** — the security measures the application actually runs, at the level of detail a notice\nneeds and no further.\n\n**Derives from** — the application's authored authentication configuration (methods enabled, MFA,\npassword policy, lockout, step-up, session lifetimes), its access floors, its encryption of stored\nsecrets, and its antivirus posture where the `ANTIVIRUS_SCANNING` INFRA capability is provisioned\n(ClamAV, consumed by the engine's file-scanning service on upload). Note this reads the INFRA\ncapability, not an engine provider slot: the equally-named `EngineCapability.ANTIVIRUS_SCANNING` was\nwithdrawn because no provider could fill it, and a derived control statement must never rest on a\nslot that cannot be configured.\n\n**Completeness** — `DERIVED`, bounded.\n\n**Bounded is the operative word.** A public notice states that measures exist and their general\nnature. **It must not enumerate the control set**: a published list of exactly which protections are\nin place, and by implication which are not, is a map for somebody attacking the service. Detail\nbelongs in a security addendum shared under agreement, not on a public page — so this fragment reads\nvery differently in `public.privacy-notice` than in a security schedule, and that difference is\ndeliberate rather than an omission.\n\n**Never state a certification.** \"Compliant\", \"certified\", \"audited\" and \"ISO/SOC\" claims are not\nderivable from configuration and are not this document's to make.\n\n\n### Concern: audit and accountability\n\n**Asserts** — that security-relevant actions are recorded, what kinds are recorded, and where those\nrecords can be sent.\n\n**Derives from** — the application's own audit store, which every application writes; the\n`COMPLIANCE_AUDIT_TRAIL` engine capability, which additionally sends each event to external providers\n(`saas-models` → `external-providers/engine-capabilities.shared.schemas.ts`); the auditable-event\ncatalog the engine emits (authentication, authorization grants, consent decisions, token lifecycle,\nconfiguration and permission changes, cross-tenant administrative access), and per-organization SIEM\nrouting where a tenant has configured it.\n\n**Completeness** — `DERIVED`.\n\nThis is one of the fragments where the ENGINE answers for the application. Every generated\napplication inherits the event catalog and the emitters; a document may state it without the\napplication having configured anything. Where a tenant has additionally routed events to its own\nSIEM, that is the tenant's configuration and belongs in a shared-responsibility statement rather than\nin the operator's own notice.\n\n\n### Concern: access control and roles\n\n**Asserts** — who inside the operator and inside a customer tenant can reach personal data, and what\nconstrains them.\n\n**Derives from** — `CORE_APP_ROLES` and `CORE_ORG_ROLES`\n(`saas-models` → `security/authorizations/roles.shared.schemas.ts`) plus the application's own role\ntable; the administrative-continuity floors (a tenant cannot be left with no usable owner, the\napplication cannot be left with no super-administrator); and the platform-access-grant mechanism,\nunder which a platform operator crossing the per-record tenant boundary requires a granted,\ntime-bounded authorization. Application-wide directory reads retain independent approval. The\napplication audit viewer has a distinct policy: `auditTrail.applicationReadAccess`, when undeclared,\nfollows the application's shape in every environment — `AuditApplicationReadAccess.INDEPENDENT_APPROVAL`\nwhere the parties of one of its relationship kinds are independent of its operator, `ROLE_BASED` otherwise. `ROLE_BASED` admits the\nsuper-administrator or the read-only audit-evidence reader role; `INDEPENDENT_APPROVAL` requires a usable application-wide grant in\naddition to the role, and a machine reader (such as an assurance collector) holds one only when it is bound to\nits own credential and signed by a second administrator — a grant bound to a machine never admits the\nadministrator who requested it. Access admission, audit observation and retained\nevidence are separate claims: the access decision does not depend on a successful audit write.\n\n**Completeness** — `DERIVED`.\n\nWorth stating plainly in a B2B notice, because it is the question a customer's own reviewer asks\nfirst: **operator access is governed by the resource and its declared policy.** Ordinary tenant\ncrossings require a usable grant. The application audit viewer is role-based by default, with\nindependent approval available as an explicit policy. Its cross-tenant observations still identify\nthe operator and tenants reached; role-based access does not imply anonymized logs or fabricate an\napproval record. Actual application-wide grants always retain their independent-approval requirement.\n\n**Observation coverage** — the per-record organization gate observes access to an identifiable\ntenant's record when the caller does not already hold organization-wide entry there. Separately,\ndeclared cross-tenant READ, LIST and SEARCH operations outside the organization-scoped gate observe\nthe identifiable tenants in their returned records that the caller does not already belong to,\ngrouped into one observation per tenant reached. This collection observer excludes context-free\ninternal requests and webhook callbacks; COUNT\nreturns no records and is not covered by that observer. Do not turn these scoped mechanisms into a\nclaim that every operation or every returned record produces an audit entry.\n\n**Delivery and evidence** — these observations are best-effort and do not fail the observed request.\nAn unavailable audit service, a synchronous emission error or a rejected emission can leave an\nauthorized request without a retained crossing entry. Observer-side drops have an\n`audit_observation_dropped_total` signal and throttled error logs; failures at the primary audit-store\nwrite have the separate `audit_store_failure_total` signal. Metrics export and log retention must\nactually be configured and operating for those signals to provide evidence beyond the process.\nNeither a loss counter nor an attempted emission substitutes for the missing audit entry.\n\n**Document-authoring consequence** — derive the roles, operation declarations and usable-grant\nrequirements and the audit viewer's access policy from the application's configuration. Do not\nclaim that every audit read required independent approval when the viewer is role-based. Describe the observation mechanisms as supported\ncoverage, then substantiate any statement about recorded access with retained audit records and\nevidence that the collection pipeline and loss monitoring were operating over the period claimed.\nAn empty crossing search alone does not prove that no operator accessed tenant data. `DERIVED`\nabove identifies the source of the access-control description; it does not certify complete audit\ndelivery or the application's operational compliance.\n\n\n### Concern: tenancy model\n\n**Asserts** — that customer data is separated per organization, and where the boundary between the\noperator's responsibilities and the customer's lies.\n\n**Derives from** — the `ORGANIZATIONS` engine capability, the organization scoping applied to every\ntenant-scoped resource, and the cross-tenant admission rules. Ordinary tenant crossings must be\ndeclared and carry a usable access grant. The application audit viewer is a separate policy surface:\nit follows `auditTrail.applicationReadAccess`, which defaults by the application's shape:\n`AuditApplicationReadAccess.INDEPENDENT_APPROVAL` where the parties of one of its relationship kinds are independent of its operator, role-based\naccess (the super-administrator or the read-only audit-evidence reader) otherwise. Under independent approval a\nmachine reader needs a second-signed grant bound to its own credential. Both modes retain cross-tenant read observations;\nrole-based access neither implies anonymized records nor supplies an approval that never occurred.\n\n**Completeness** — `DERIVED`.\n\n**This fragment is where shared responsibility is described, and it must never be flattened.** In a\nB2B SaaS the operator is a PROCESSOR for the data a customer stores about its own people, and a\nCONTROLLER for the data it holds about the customer's users as account holders. Those are different\nroles with different duties over the same database. Say which is which; do not pick one and apply it\nto everything.\n\n**The attribution has a home now.** `operatorComplianceIdentity.roleAllocations` in\n`wildo.saas.config.ts` carries one role per population of data — PROCESSOR for the records a customer\nstores about its own people, CONTROLLER for the account data of the people who administer them. It is\na LIST for exactly the reason this fragment gives: those are different roles over the same database,\nand a single field would force one of them to be wrong.\n\nWhere the attribution is not established, that is a `NEEDS_DECISION` — never a guess — and the\nsurface to name is `roleAllocations`. Not `NEEDS_FRAMEWORK`: there is somewhere to write the answer,\nso the remedy is to fill it in rather than to build something. See the legal-basis fragment.\n\n\n### Concern: operator identity\n\n**Asserts** — who legally operates the service: entity name, registered address, contact route for\ndata-protection questions, and a representative where one is required.\n\n**Derives from** — `operatorComplianceIdentity` in `wildo.saas.config.ts`: the legal entity, its\nregistered address, the privacy contact route, and an Art. 27 representative where one is required.\n\nThe VALUE is never derivable — a legal entity is a fact about the world, not a property of a codebase.\nWhat the framework provides is the PLACE to record it, and until 2026-08-30 it did not: this fragment\nsaid \"no engine change would close it\", which was right about derivation and wrong about the home.\nThe consequence was concrete. A landing REPLACES the produced document on every run, so an operator\nwho answered by editing the document lost the answer at the next regeneration — the answer has to live\nin the application or it does not survive.\n\n**Completeness** — `DERIVED` when the identity is declared; `NEEDS_DECISION` when it is not.\n\n⚠️ `NEEDS_DECISION`, not `NEEDS_FRAMEWORK`, and the distinction is load-bearing now that the surface\nexists. `NEEDS_FRAMEWORK` means there is nowhere to record the answer; `NEEDS_DECISION` means there is\nand nobody has. They have different remedies — build something, versus fill something in — and a\nreader who cannot tell them apart cannot act on either. Say which surface the answer goes to.\n\n**What closes it** — the operator declaring `operatorComplianceIdentity`. It is cheap and it can be\nfilled in later without redrafting anything around it, which is the reason it is not a blocker.\n\n**Never infer it.** Not from the application name, not from a domain, not from another application,\nnot from model memory. A published legal document naming the wrong entity is worse than one that says\nthe entity is not yet recorded — the first misdirects a person exercising a right, the second tells\nthem the document is incomplete.\n\n**Every document needs this fragment**, which makes it the clearest demonstration of why producing\nwith gaps beats blocking: the whole document set would be unproducible until one form is filled in.\n",
29
29
  "skillRefs": [
30
30
  "compliance-document-authoring"
31
31
  ],
32
32
  "skillBodyRefs": [],
33
+ "derivedFromAnswers": [],
33
34
  "contextSources": [
34
35
  "document_blueprint",
35
36
  "assurance_evidence",
@@ -1 +1 @@
1
- {"aggregationPolicyRef":"application-creation:aggregation/worst-brand-identity-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.audience","brand.asset","market.icp"],"criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1}],"instruction":"Determine whether the brief hands off correctly: every targetIcpRef in the audience names an ICP the market snapshot holds and none is an anti-target; the audience rationale follows from the brief's own tone and mission; and resolvedAssets is EMPTY, because assets are the companion logo step's output and a hand-authored asset reference would be overwritten or flagged.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The audience is absent although the market snapshot names ICPs the tone was chosen for, or the rationale is generic.","GAP":"An audience ref naming an ICP the market does not hold or an anti-target, or a resolvedAssets entry authored by hand.","INDETERMINATE":"The market snapshot's ICPs are not in evidence, so the audience cannot be checked.","PASS":"Every audience ref resolves to a market ICP that is not an anti-target, and resolvedAssets is empty."}},{"assessesAspects":["brand.name","brand.logo-direction","brand.visual-tone","vision.idea","vision.mission"],"criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1}],"instruction":"Determine whether the brand brief is GROUNDED: the brand name is exactly the name the creator chose in the interview (an option may carry a bracketed qualifier such as [not-screened], [screening-incomplete] or [keep-despite-conflict] — the name is the text before it, and the qualifier never appears in the brand name); the mark type, background and colour seeds are the creator's answers; the symbolism, motifs and imagery to avoid DERIVE from the vision's idea and mission; the visual tone translates the market's verbal voice where a market snapshot exists and is noted as provisional where it does not; and the creator's visual-direction answer, when it is not \"none\", is honoured and outranks the derivation. Derived direction is expected — the interview no longer asks for it — but it must trace to the vision or the market voice, never be a decorative choice of the model's own. A partially-directed brief (name only, direction still open) is a legitimate state, not a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a thin symbolism rationale, a tone that only loosely follows the market voice, or a background treatment the pipeline must compensate for.","GAP":"A name or mark choice that differs from the interview, a visual direction the creator gave that the brief ignores, or symbolism and tone that trace to neither the vision nor the market voice.","INDETERMINATE":"The interview answers or the vision are not in evidence, so grounding cannot be established.","PASS":"The name and the mark choices are the creator's, the symbolism and imagery trace to the vision, the tone follows the market voice or is honestly provisional, and the creator's visual direction is honoured."}},{"assessesAspects":["brand.name","brand-name-screening.candidate","brand-name-screening.jurisdiction","brand-name-screening.nice-class"],"criterionRef":"application-creation:criterion/brand-identity-name-screened-and-unclaimed","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1}],"instruction":"Determine whether the chosen NAME stands honestly against its screening: the brand name is a candidate of the brand-name screening, whose queries cover every jurisdiction and Nice class the screening declares; where the screening could not check a register, nothing in the brief presents the name as cleared; where the creator kept a name despite a conflict, the brief does not hide or soften it; and nothing in the brief asserts that the name is available, free to use, registered by this product or legally cleared — a minimal trademark screening is never a clearance opinion.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The name was chosen as not screened, screening-incomplete or kept despite a conflict, and the brief says so plainly.","GAP":"The name is not among the screened candidates, an unchecked or conflicting name is presented as clear, or the brief asserts availability or legal clearance.","INDETERMINATE":"The brand-name screening is not in evidence, so the name's standing cannot be checked.","PASS":"The name is a screened candidate covered in every declared jurisdiction and class, and the brief claims no availability or clearance."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-identity","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-identity"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
1
+ {"aggregationPolicyRef":"application-creation:aggregation/worst-brand-identity-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.audience","brand.asset","market.icp"],"criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1}],"instruction":"Determine whether the brief hands off correctly: every targetIcpRef in the audience names an ICP the market snapshot holds and none is an anti-target; the audience rationale follows from the brief's own tone and mission; and resolvedAssets is EMPTY, because assets are the companion logo step's output and a hand-authored asset reference would be overwritten or flagged.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The audience is absent although the market snapshot names ICPs the tone was chosen for, or the rationale is generic.","GAP":"An audience ref naming an ICP the market does not hold or an anti-target, or a resolvedAssets entry authored by hand.","INDETERMINATE":"The market snapshot's ICPs are not in evidence, so the audience cannot be checked.","PASS":"Every audience ref resolves to a market ICP that is not an anti-target, and resolvedAssets is empty."}},{"assessesAspects":["brand.name","brand.logo-direction","brand.visual-tone","vision.idea","vision.mission"],"criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","criterionVersion":3,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1}],"instruction":"Determine whether the brand brief is GROUNDED: the brand name is exactly the name the creator chose in the interview — that question is always asked, so the name is never an assumption (an option may carry a bracketed qualifier such as [not-screened], [screening-incomplete] or [keep-despite-conflict] — the name is the text before it, and the qualifier never appears in the brand name); the mark type, background and colour seeds are the interview's answers, read WITH their standing — an answer marked ASSUMED was proposed for the creator and never stated by them, so following it is correct while describing it as the creator's own choice is drift, and calling a DECIDED answer an assumption is drift too; the symbolism, motifs and imagery to avoid DERIVE from the vision's idea and mission; the visual tone translates the market's verbal voice where a market snapshot exists and is noted as provisional where it does not; and the visual-direction answer, when it is not \"none\" (and whatever its standing — an assumed direction is still the one the run builds on), is honoured and outranks the derivation — in the WORDS and in the LOOK they derive: the derived context gives the theme point the drafted style keywords and mood select (shape, motion, density, elevation, letter case…), computed by the framework, and a point that contradicts the direction (a rounded direction and a sharp shape, a lively one and still motion) is not honoured, however faithful the words read. Derived direction is expected — the interview no longer asks for it — but it must trace to the vision or the market voice, never be a decorative choice of the model's own. A partially-directed brief (name only, direction still open) is a legitimate state, not a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a thin symbolism rationale, a tone that only loosely follows the market voice, or a background treatment the pipeline must compensate for.","GAP":"A name or mark choice that differs from the interview, a visual direction the creator gave that the brief ignores or whose derived look contradicts it, or symbolism and tone that trace to neither the vision nor the market voice.","INDETERMINATE":"The interview answers or the vision are not in evidence, so grounding cannot be established.","PASS":"The name and the mark choices are the creator's, the symbolism and imagery trace to the vision, the tone follows the market voice or is honestly provisional, and the creator's visual direction is honoured."}},{"assessesAspects":["brand.name","brand-name-screening.candidate","brand-name-screening.jurisdiction","brand-name-screening.nice-class"],"criterionRef":"application-creation:criterion/brand-identity-name-screened-and-unclaimed","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1}],"instruction":"Determine whether the chosen NAME stands honestly against its screening: the brand name is a candidate of the brand-name screening, whose queries cover every jurisdiction and Nice class the screening declares; where the screening could not check a register, nothing in the brief presents the name as cleared; where the creator kept a name despite a conflict, the brief does not hide or soften it; and nothing in the brief asserts that the name is available, free to use, registered by this product or legally cleared — a minimal trademark screening is never a clearance opinion.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The name was chosen as not screened, screening-incomplete or kept despite a conflict, and the brief says so plainly.","GAP":"The name is not among the screened candidates, an unchecked or conflicting name is presented as clear, or the brief asserts availability or legal clearance.","INDETERMINATE":"The brand-name screening is not in evidence, so the name's standing cannot be checked.","PASS":"The name is a screened candidate covered in every declared jurisdiction and class, and the brief claims no availability or clearance."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-identity","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-identity"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
@@ -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-brand-brief","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision"],"requirementRef":"application-creation:authority-requirement/brand-identity-result","requirementVersion":1,"riskClassRef":"application-creation:risk/brand-brief-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/brand-identity","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/brand-identity-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/brand-identity","policyVersion":1},"decisionPointRef":"application-creation:decision-point/brand-identity-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/brand-identity-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/brand-identity","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/brand-brief-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-brand-brief-change","triggerRefs":["application-creation:trigger/brand-brief-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-brand-identity-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision"],"hardFloorRef":"application-creation:hard-floor/brand-brief-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/brand-identity-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/brand-identity","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-brand-identity-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.audience","brand.asset","market.icp"],"criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1}],"instruction":"Determine whether the brief hands off correctly: every targetIcpRef in the audience names an ICP the market snapshot holds and none is an anti-target; the audience rationale follows from the brief's own tone and mission; and resolvedAssets is EMPTY, because assets are the companion logo step's output and a hand-authored asset reference would be overwritten or flagged.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The audience is absent although the market snapshot names ICPs the tone was chosen for, or the rationale is generic.","GAP":"An audience ref naming an ICP the market does not hold or an anti-target, or a resolvedAssets entry authored by hand.","INDETERMINATE":"The market snapshot's ICPs are not in evidence, so the audience cannot be checked.","PASS":"Every audience ref resolves to a market ICP that is not an anti-target, and resolvedAssets is empty."}},{"assessesAspects":["brand.name","brand.logo-direction","brand.visual-tone","vision.idea","vision.mission"],"criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1}],"instruction":"Determine whether the brand brief is GROUNDED: the brand name is exactly the name the creator chose in the interview (an option may carry a bracketed qualifier such as [not-screened], [screening-incomplete] or [keep-despite-conflict] — the name is the text before it, and the qualifier never appears in the brand name); the mark type, background and colour seeds are the creator's answers; the symbolism, motifs and imagery to avoid DERIVE from the vision's idea and mission; the visual tone translates the market's verbal voice where a market snapshot exists and is noted as provisional where it does not; and the creator's visual-direction answer, when it is not \"none\", is honoured and outranks the derivation. Derived direction is expected — the interview no longer asks for it — but it must trace to the vision or the market voice, never be a decorative choice of the model's own. A partially-directed brief (name only, direction still open) is a legitimate state, not a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a thin symbolism rationale, a tone that only loosely follows the market voice, or a background treatment the pipeline must compensate for.","GAP":"A name or mark choice that differs from the interview, a visual direction the creator gave that the brief ignores, or symbolism and tone that trace to neither the vision nor the market voice.","INDETERMINATE":"The interview answers or the vision are not in evidence, so grounding cannot be established.","PASS":"The name and the mark choices are the creator's, the symbolism and imagery trace to the vision, the tone follows the market voice or is honestly provisional, and the creator's visual direction is honoured."}},{"assessesAspects":["brand.name","brand-name-screening.candidate","brand-name-screening.jurisdiction","brand-name-screening.nice-class"],"criterionRef":"application-creation:criterion/brand-identity-name-screened-and-unclaimed","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1}],"instruction":"Determine whether the chosen NAME stands honestly against its screening: the brand name is a candidate of the brand-name screening, whose queries cover every jurisdiction and Nice class the screening declares; where the screening could not check a register, nothing in the brief presents the name as cleared; where the creator kept a name despite a conflict, the brief does not hide or soften it; and nothing in the brief asserts that the name is available, free to use, registered by this product or legally cleared — a minimal trademark screening is never a clearance opinion.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The name was chosen as not screened, screening-incomplete or kept despite a conflict, and the brief says so plainly.","GAP":"The name is not among the screened candidates, an unchecked or conflicting name is presented as clear, or the brief asserts availability or legal clearance.","INDETERMINATE":"The brand-name screening is not in evidence, so the name's standing cannot be checked.","PASS":"The name is a screened candidate covered in every declared jurisdiction and class, and the brief claims no availability or clearance."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-identity","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-identity"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/brand-identity","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-market-and-brand-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-market-and-brand-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-name-screened-and-unclaimed","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/brand-name-screening-and-brand-candidate"}],"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-brand-brief","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision"],"requirementRef":"application-creation:authority-requirement/brand-identity-result","requirementVersion":1,"riskClassRef":"application-creation:risk/brand-brief-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/brand-identity","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/brand-identity-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/brand-identity","policyVersion":1},"decisionPointRef":"application-creation:decision-point/brand-identity-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/brand-identity-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/brand-identity","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/brand-brief-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-brand-brief-change","triggerRefs":["application-creation:trigger/brand-brief-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-brand-identity-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision"],"hardFloorRef":"application-creation:hard-floor/brand-brief-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/brand-identity-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/brand-identity","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-brand-identity-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.audience","brand.asset","market.icp"],"criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1}],"instruction":"Determine whether the brief hands off correctly: every targetIcpRef in the audience names an ICP the market snapshot holds and none is an anti-target; the audience rationale follows from the brief's own tone and mission; and resolvedAssets is EMPTY, because assets are the companion logo step's output and a hand-authored asset reference would be overwritten or flagged.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The audience is absent although the market snapshot names ICPs the tone was chosen for, or the rationale is generic.","GAP":"An audience ref naming an ICP the market does not hold or an anti-target, or a resolvedAssets entry authored by hand.","INDETERMINATE":"The market snapshot's ICPs are not in evidence, so the audience cannot be checked.","PASS":"Every audience ref resolves to a market ICP that is not an anti-target, and resolvedAssets is empty."}},{"assessesAspects":["brand.name","brand.logo-direction","brand.visual-tone","vision.idea","vision.mission"],"criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","criterionVersion":3,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1}],"instruction":"Determine whether the brand brief is GROUNDED: the brand name is exactly the name the creator chose in the interview — that question is always asked, so the name is never an assumption (an option may carry a bracketed qualifier such as [not-screened], [screening-incomplete] or [keep-despite-conflict] — the name is the text before it, and the qualifier never appears in the brand name); the mark type, background and colour seeds are the interview's answers, read WITH their standing — an answer marked ASSUMED was proposed for the creator and never stated by them, so following it is correct while describing it as the creator's own choice is drift, and calling a DECIDED answer an assumption is drift too; the symbolism, motifs and imagery to avoid DERIVE from the vision's idea and mission; the visual tone translates the market's verbal voice where a market snapshot exists and is noted as provisional where it does not; and the visual-direction answer, when it is not \"none\" (and whatever its standing — an assumed direction is still the one the run builds on), is honoured and outranks the derivation — in the WORDS and in the LOOK they derive: the derived context gives the theme point the drafted style keywords and mood select (shape, motion, density, elevation, letter case…), computed by the framework, and a point that contradicts the direction (a rounded direction and a sharp shape, a lively one and still motion) is not honoured, however faithful the words read. Derived direction is expected — the interview no longer asks for it — but it must trace to the vision or the market voice, never be a decorative choice of the model's own. A partially-directed brief (name only, direction still open) is a legitimate state, not a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a thin symbolism rationale, a tone that only loosely follows the market voice, or a background treatment the pipeline must compensate for.","GAP":"A name or mark choice that differs from the interview, a visual direction the creator gave that the brief ignores or whose derived look contradicts it, or symbolism and tone that trace to neither the vision nor the market voice.","INDETERMINATE":"The interview answers or the vision are not in evidence, so grounding cannot be established.","PASS":"The name and the mark choices are the creator's, the symbolism and imagery trace to the vision, the tone follows the market voice or is honestly provisional, and the creator's visual direction is honoured."}},{"assessesAspects":["brand.name","brand-name-screening.candidate","brand-name-screening.jurisdiction","brand-name-screening.nice-class"],"criterionRef":"application-creation:criterion/brand-identity-name-screened-and-unclaimed","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1}],"instruction":"Determine whether the chosen NAME stands honestly against its screening: the brand name is a candidate of the brand-name screening, whose queries cover every jurisdiction and Nice class the screening declares; where the screening could not check a register, nothing in the brief presents the name as cleared; where the creator kept a name despite a conflict, the brief does not hide or soften it; and nothing in the brief asserts that the name is available, free to use, registered by this product or legally cleared — a minimal trademark screening is never a clearance opinion.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The name was chosen as not screened, screening-incomplete or kept despite a conflict, and the brief says so plainly.","GAP":"The name is not among the screened candidates, an unchecked or conflicting name is presented as clear, or the brief asserts availability or legal clearance.","INDETERMINATE":"The brand-name screening is not in evidence, so the name's standing cannot be checked.","PASS":"The name is a screened candidate covered in every declared jurisdiction and class, and the brief claims no availability or clearance."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-identity","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-identity"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/brand-identity","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-market-and-brand-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-market-and-brand-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-name-screened-and-unclaimed","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/brand-name-screening-and-brand-candidate"}],"schemaVersion":1}
@@ -120,9 +120,16 @@ and you say where it came from.
120
120
  - **Visual tone** (optional, WARNed when absent). The aesthetic register — the
121
121
  VISUAL counterpart to the market voice, DERIVED from it (and shaped by the
122
122
  creator's `visual-direction`): 3–7 concrete `styleKeywords`
123
- ("geometric", "minimal", "warm"), a one-line `mood`, a prose `colorIntent`
123
+ ("friendly", "fluid", "confident"), a one-line `mood`, a prose `colorIntent`
124
124
  (the color STORY, not hex values), and the hex `colorSeeds` the creator gave in
125
- `visual-color-seeds`, only when they named any.
125
+ `visual-color-seeds`, only when they named any. Keep the creator's MAIN colour
126
+ first: the build derives the application's palette from these seeds, the first
127
+ as its primary and the second as its accent.
128
+ The style words and the mood ALSO choose the theme of the application and its
129
+ website (corners, depth, spacing, motion, letter case): pick them for the look
130
+ the creator's `visual-direction` describes, not only for the logo. "Minimal"
131
+ flattens every shadow, "precise" makes corners sharp and motion still, "warm"
132
+ and "soft" add depth; the `brand-logo-authoring` skill lists every word.
126
133
  - **Audience** (optional). WHO the brand is for: `targetIcpRefs`, the refs of
127
134
  the market ICPs its name and tone are chosen to speak to, copied exactly from
128
135
  the market's `icps`, plus a one-line `rationale`. Derive it from what the brief
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "top_down.brand-identity",
3
- "version": "0.4.0",
3
+ "version": "0.5.0",
4
4
  "phase": "top_down",
5
5
  "intent": "Brand-identity elicitation: draw the product's VISUAL identity out of the creator — the brand name (CHOSEN by the creator from the screened candidates `top_down.brand-naming` landed), the logo creative direction (mark type, motifs, symbolism, imagery don'ts, background), and the visual tone (style keywords, mood, color story) — and capture it as a single validated BrandSnapshot (the `brand-brief` artifact family). The visual counterpart to the vision (intent) and market (verbal voice) briefs: it derives symbolism from the VisionSnapshot's idea/mission and, when a MarketSnapshot exists, translates its verbal `tonesOfVoice` into a visual register. The emitted brand-brief is the INPUT the companion logo step generates the master logo + derived assets from, and via `BrandSnapshot.resolvedAssets` the single source of truth every logo/favicon/brand-image consumer resolves against. Progressive: may persist a partially-directed brand (logoDirection/visualTone optional) and resume. v1 scaffold methodology — iterate the interview.",
6
6
  "preconditions": [
@@ -46,7 +46,7 @@
46
46
  ],
47
47
  "stepOutputs": [],
48
48
  "method": {
49
- "guidance": "# Brand Identity — Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **brand-identity author**. Your job is to capture the product's VISUAL\nidentity, from the creator's few decisions plus what the vision and the market already\nsay, as a single typed\n**`BrandSnapshot`** — the `brand-brief` artifact. This is the visual\ncounterpart to the vision brief (which captured *intent*) and the market brief\n(which captured the *verbal* voice): here you capture what the product should\n**look like** and, specifically, the brief a logo is generated from.\n\nThe brand-brief you emit is not the logo itself — it is the *direction*. The\ncompanion logo step reads it to generate the master logo and every derived\nasset (favicon, apple-touch, maskable, OG, email, monochrome, dark/light), and\nthose become the single source of truth every surface resolves against. So an\nhonest, well-framed brief is the whole task. You do **not** generate pixels,\nset design-system color tokens, or restate the verbal brand voice — each is a\ndistinct concern with its own home.\n\n## Where the brief comes from\n\nYou do not invent a brand from nothing. Ground it in what the journey already\nknows:\n\n- **The vision brief is your source of meaning.** Read the `VisionSnapshot` and\n derive the mark's **symbolism** from the product's idea and mission — the\n mark should evoke what the product is *for*, not a decorative motif you liked.\n- **The market brief sharpens the register, when present.** If a\n `MarketSnapshot` exists, translate its verbal `tonesOfVoice` (the Nielsen\n Norman 4-axis voice) into a **visual** tone: a serious / formal voice reads as\n restrained geometry and a muted palette; a funny / casual voice reads as\n rounder forms and a warmer accent. The market brief is an *input*, not a\n precondition — if there is no market snapshot yet, derive the visual tone from\n the vision alone and note it as provisional.\n\n## What the creator decided, and what you derive\n\nThe interview asks only what the creator alone can decide. Everything else you derive,\nand you say where it came from.\n\n| Decided by the creator (interview answer) | Derived by you |\n|---|---|\n| `brand-name`: chosen from the screened names | `symbolism`, from the vision's idea and mission |\n| `brand-tagline`, or \"none\" | `motifs`: concrete elements that carry that symbolism |\n| `logo-mark-type` | `avoid`: the guardrails that keep the mark usable (no gradients, no literal clip-art, no text inside a symbol meant to stand alone) |\n| `logo-background` | `visualTone` (style keywords, mood, colour story), translated from the market's verbal voice |\n| `visual-color-seeds`, or \"none\" | |\n| `visual-direction`, or \"none\" | |\n\n- **`visual-direction` outranks the derivation.** When it is not \"none\", whatever it asks\n the mark to evoke, include or avoid is honoured, and the derived parts are shaped around it.\n- **Derived is not invented.** Every symbol, motif and tone keyword must trace to the\n vision or the market voice. A decorative choice of your own is the one thing to avoid.\n- **Progressive is fine.** A `BrandSnapshot` requires only the **name**. If the vision or\n the market is too thin to derive a direction honestly, leave `logoDirection` or\n `visualTone` out and say what is missing. The snapshot persists partially directed, and\n this playbook can resume.\n- **One product, one brand.** The snapshot is a single aggregate: one name, one logo\n direction, one visual tone.\n\n## What the brief holds — one aggregate\n\n- **Name** (REQUIRED). The anchor lexical identity: the exact, case-sensitive\n `brandName` the logo renders and every surface prints, plus an optional\n `tagline` to lock up with combination marks / OG imagery. Nothing visual\n here — the mark and the palette come next.\n\n **You do not invent the name, and you do not choose it.** `top_down.brand-naming`\n proposed names and ran a minimal trademark screening of each; the creator CHOSE\n one in this playbook's `brand-name` question, from options computed from that\n screening. The `brandName` is exactly the chosen option's name. An option may end\n with a bracketed qualifier — `[not-screened]`, `[screening-incomplete]` or\n `[keep-despite-conflict]` — which records how the creator chose; it is NEVER part of\n the name, so drop it. The interview answer also records the line the creator was\n shown beside that option (the product already using the name, the registers nobody\n could read): carry its substance into the brief rather than paraphrasing it away.\n\n The brand-name screening is in your brief. Never describe the name as\n \"available\", \"registered\", \"protected\" or \"cleared\": a screening is not a legal\n clearance opinion. Where the creator kept a name despite a conflict, or chose one\n whose screening is incomplete or read no register at all, do not hide or soften that\n anywhere in the brief.\n- **Logo direction** (optional, WARNed when absent). The creative brief the\n image model turns into the master logo:\n - `markType` — the creator's `logo-mark-type` answer. The question suggests\n `COMBINATION_MARK` (symbol + wordmark) because it is the only archetype that\n natively yields BOTH a header lockup and a square symbol for favicons and app\n icons. When the creator chose `WORDMARK` (text only), note in the brief that a\n wordmark cannot produce a clean square app icon.\n - `motifs` — concrete visual elements to include (short noun phrases), DERIVED\n from the symbolism and the creator's `visual-direction`.\n - `symbolism` — the meaning the mark should evoke, **derived from the vision\n mission/idea** (and the creator's `visual-direction`, when they gave one).\n - `avoid` — imagery don'ts (the negative-prompt guardrails that keep output\n usable), DERIVED, plus anything the creator's `visual-direction` rules out.\n - `backgroundTreatment` — the creator's `logo-background` answer.\n `TRANSPARENT_ISOLATED` is the default and the only treatment that rasterizes\n losslessly into every derived asset. A\n solid field or contextual scene is an explicit opt-in the pipeline must\n compensate for — the validator WARNs on it.\n- **Visual tone** (optional, WARNed when absent). The aesthetic register — the\n VISUAL counterpart to the market voice, DERIVED from it (and shaped by the\n creator's `visual-direction`): 3–7 concrete `styleKeywords`\n (\"geometric\", \"minimal\", \"warm\"), a one-line `mood`, a prose `colorIntent`\n (the color STORY, not hex values), and the hex `colorSeeds` the creator gave in\n `visual-color-seeds`, only when they named any.\n- **Audience** (optional). WHO the brand is for: `targetIcpRefs`, the refs of\n the market ICPs its name and tone are chosen to speak to, copied exactly from\n the market's `icps`, plus a one-line `rationale`. Derive it from what the brief\n already says: the ICP whose preferred voice the visual tone translates, the\n segment the mission and tagline address. Never name a segment the market does\n not hold, and never list an anti-target. Downstream agents are given the\n brand's ICPs, and through them their personas and positionings, from this one\n declaration.\n\n## Answers the creator did not give\n\nIn a quick interview the creator is asked only for `brand-name`. Every other answer may\nreach your brief marked ASSUMED: the companion proposed it from the vision and the market,\nand it was kept without the creator deciding it — on their review, or by an unattended round. Use an assumed answer as a working\ndefault, not as the creator's choice. Where the brief explains a choice that rests on one\n(a tagline, a mark type, a background, a colour seed), say it was proposed rather than\nchosen, and never let an assumed answer outrank what the vision and the market voice imply\nthe way the creator's own answer would. `brand-name` is never assumed: the creator chooses it.\n\n## What you emit\n\nA single `BrandSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told otherwise).\n- `name` — the required anchor (`brandName`, optional `tagline`).\n- `logoDirection` / `visualTone` / `audience` — the optional singletons, present when they could be decided or honestly derived.\n- `resolvedAssets` — **leave empty.** This is the companion logo step's output,\n not something you author. Hand-authoring it fabricates asset references the\n pipeline will overwrite or the validator will flag.\n\nAuthor every entity in English. Follow the `brand-logo-authoring` skill for the\nexact field contracts and the mark-type / background / visual-tone decision\naids — its full text is in your brief, under \"The skills this method tells you\nto FOLLOW\". Read it there; you cannot open files.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `brand-snapshot-valid`\ngate (`validateBrandSnapshot`) before it commits. A directed-but-ungenerated\nbrand (a `logoDirection` present, `resolvedAssets` still empty) is expected and\nonly WARNs — it is exactly the state you hand off to the companion logo step. A\nmissing logo direction and a missing visual tone are also warnings, reflecting a\nnot-yet-complete brief. Emit a clean brief and let the warnings stand honestly\nwhen the brand genuinely is not fully directed yet, rather than inventing a\nmark to silence them.\n\nAfter landing, the advisory judge reads the brief against two criteria — grounding in\nthe interview and the vision, and the audience-and-assets hand-off — and its verdicts\nreach the creator's review as notes. A verdict never refuses a landing.\n\n## Approval\n\nThe drafted `BrandSnapshot` is presented to the creator for approval before it\nbecomes the committed `brand-brief`. Show the brief back in plain prose — the\nname, the mark direction, the visual tone — and let the creator confirm or\ncorrect it. The brand-brief is what the logo is generated from and what\npropagates everywhere; it is worth one explicit human sign-off before the mark\nis made.\n\n## Runtime context\n\nBefore you start, read the current journey state, the vision brief that grounds\nthe brand's meaning, and any brand brief that already exists so you refine it\nrather than re-deriving it from scratch.\n\n(The vision and any previously landed brand brief arrive in your brief as the `vision-brief` and\n`brand-brief` input sections.)\n\n## References\n\nThese are skill FOLDERS installed in the application, and this step has no tools,\nso it does not open them. What reaches you is stated per skill below.\n\n- `brand-logo-authoring` — the field contracts for the `BrandSnapshot` (name /\n logoDirection / visualTone), the mark-type selection table, background\n derivation-safety, and deriving the visual tone from the market voice. Its\n FULL TEXT is in your brief; follow it exactly.\n",
49
+ "guidance": "# Brand Identity — Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **brand-identity author**. Your job is to capture the product's VISUAL\nidentity, from the creator's few decisions plus what the vision and the market already\nsay, as a single typed\n**`BrandSnapshot`** — the `brand-brief` artifact. This is the visual\ncounterpart to the vision brief (which captured *intent*) and the market brief\n(which captured the *verbal* voice): here you capture what the product should\n**look like** and, specifically, the brief a logo is generated from.\n\nThe brand-brief you emit is not the logo itself — it is the *direction*. The\ncompanion logo step reads it to generate the master logo and every derived\nasset (favicon, apple-touch, maskable, OG, email, monochrome, dark/light), and\nthose become the single source of truth every surface resolves against. So an\nhonest, well-framed brief is the whole task. You do **not** generate pixels,\nset design-system color tokens, or restate the verbal brand voice — each is a\ndistinct concern with its own home.\n\n## Where the brief comes from\n\nYou do not invent a brand from nothing. Ground it in what the journey already\nknows:\n\n- **The vision brief is your source of meaning.** Read the `VisionSnapshot` and\n derive the mark's **symbolism** from the product's idea and mission — the\n mark should evoke what the product is *for*, not a decorative motif you liked.\n- **The market brief sharpens the register, when present.** If a\n `MarketSnapshot` exists, translate its verbal `tonesOfVoice` (the Nielsen\n Norman 4-axis voice) into a **visual** tone: a serious / formal voice reads as\n restrained geometry and a muted palette; a funny / casual voice reads as\n rounder forms and a warmer accent. The market brief is an *input*, not a\n precondition — if there is no market snapshot yet, derive the visual tone from\n the vision alone and note it as provisional.\n\n## What the creator decided, and what you derive\n\nThe interview asks only what the creator alone can decide. Everything else you derive,\nand you say where it came from.\n\n| Decided by the creator (interview answer) | Derived by you |\n|---|---|\n| `brand-name`: chosen from the screened names | `symbolism`, from the vision's idea and mission |\n| `brand-tagline`, or \"none\" | `motifs`: concrete elements that carry that symbolism |\n| `logo-mark-type` | `avoid`: the guardrails that keep the mark usable (no gradients, no literal clip-art, no text inside a symbol meant to stand alone) |\n| `logo-background` | `visualTone` (style keywords, mood, colour story), translated from the market's verbal voice |\n| `visual-color-seeds`, or \"none\" | |\n| `visual-direction`, or \"none\" | |\n\n- **`visual-direction` outranks the derivation.** When it is not \"none\", whatever it asks\n the mark to evoke, include or avoid is honoured, and the derived parts are shaped around it.\n- **Derived is not invented.** Every symbol, motif and tone keyword must trace to the\n vision or the market voice. A decorative choice of your own is the one thing to avoid.\n- **Progressive is fine.** A `BrandSnapshot` requires only the **name**. If the vision or\n the market is too thin to derive a direction honestly, leave `logoDirection` or\n `visualTone` out and say what is missing. The snapshot persists partially directed, and\n this playbook can resume.\n- **One product, one brand.** The snapshot is a single aggregate: one name, one logo\n direction, one visual tone.\n\n## What the brief holds — one aggregate\n\n- **Name** (REQUIRED). The anchor lexical identity: the exact, case-sensitive\n `brandName` the logo renders and every surface prints, plus an optional\n `tagline` to lock up with combination marks / OG imagery. Nothing visual\n here — the mark and the palette come next.\n\n **You do not invent the name, and you do not choose it.** `top_down.brand-naming`\n proposed names and ran a minimal trademark screening of each; the creator CHOSE\n one in this playbook's `brand-name` question, from options computed from that\n screening. The `brandName` is exactly the chosen option's name. An option may end\n with a bracketed qualifier — `[not-screened]`, `[screening-incomplete]` or\n `[keep-despite-conflict]` — which records how the creator chose; it is NEVER part of\n the name, so drop it. The interview answer also records the line the creator was\n shown beside that option (the product already using the name, the registers nobody\n could read): carry its substance into the brief rather than paraphrasing it away.\n\n The brand-name screening is in your brief. Never describe the name as\n \"available\", \"registered\", \"protected\" or \"cleared\": a screening is not a legal\n clearance opinion. Where the creator kept a name despite a conflict, or chose one\n whose screening is incomplete or read no register at all, do not hide or soften that\n anywhere in the brief.\n- **Logo direction** (optional, WARNed when absent). The creative brief the\n image model turns into the master logo:\n - `markType` — the creator's `logo-mark-type` answer. The question suggests\n `COMBINATION_MARK` (symbol + wordmark) because it is the only archetype that\n natively yields BOTH a header lockup and a square symbol for favicons and app\n icons. When the creator chose `WORDMARK` (text only), note in the brief that a\n wordmark cannot produce a clean square app icon.\n - `motifs` — concrete visual elements to include (short noun phrases), DERIVED\n from the symbolism and the creator's `visual-direction`.\n - `symbolism` — the meaning the mark should evoke, **derived from the vision\n mission/idea** (and the creator's `visual-direction`, when they gave one).\n - `avoid` — imagery don'ts (the negative-prompt guardrails that keep output\n usable), DERIVED, plus anything the creator's `visual-direction` rules out.\n - `backgroundTreatment` — the creator's `logo-background` answer.\n `TRANSPARENT_ISOLATED` is the default and the only treatment that rasterizes\n losslessly into every derived asset. A\n solid field or contextual scene is an explicit opt-in the pipeline must\n compensate for — the validator WARNs on it.\n- **Visual tone** (optional, WARNed when absent). The aesthetic register — the\n VISUAL counterpart to the market voice, DERIVED from it (and shaped by the\n creator's `visual-direction`): 3–7 concrete `styleKeywords`\n (\"friendly\", \"fluid\", \"confident\"), a one-line `mood`, a prose `colorIntent`\n (the color STORY, not hex values), and the hex `colorSeeds` the creator gave in\n `visual-color-seeds`, only when they named any. Keep the creator's MAIN colour\n first: the build derives the application's palette from these seeds, the first\n as its primary and the second as its accent.\n The style words and the mood ALSO choose the theme of the application and its\n website (corners, depth, spacing, motion, letter case): pick them for the look\n the creator's `visual-direction` describes, not only for the logo. \"Minimal\"\n flattens every shadow, \"precise\" makes corners sharp and motion still, \"warm\"\n and \"soft\" add depth; the `brand-logo-authoring` skill lists every word.\n- **Audience** (optional). WHO the brand is for: `targetIcpRefs`, the refs of\n the market ICPs its name and tone are chosen to speak to, copied exactly from\n the market's `icps`, plus a one-line `rationale`. Derive it from what the brief\n already says: the ICP whose preferred voice the visual tone translates, the\n segment the mission and tagline address. Never name a segment the market does\n not hold, and never list an anti-target. Downstream agents are given the\n brand's ICPs, and through them their personas and positionings, from this one\n declaration.\n\n## Answers the creator did not give\n\nIn a quick interview the creator is asked only for `brand-name`. Every other answer may\nreach your brief marked ASSUMED: the companion proposed it from the vision and the market,\nand it was kept without the creator deciding it — on their review, or by an unattended round. Use an assumed answer as a working\ndefault, not as the creator's choice. Where the brief explains a choice that rests on one\n(a tagline, a mark type, a background, a colour seed), say it was proposed rather than\nchosen, and never let an assumed answer outrank what the vision and the market voice imply\nthe way the creator's own answer would. `brand-name` is never assumed: the creator chooses it.\n\n## What you emit\n\nA single `BrandSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told otherwise).\n- `name` — the required anchor (`brandName`, optional `tagline`).\n- `logoDirection` / `visualTone` / `audience` — the optional singletons, present when they could be decided or honestly derived.\n- `resolvedAssets` — **leave empty.** This is the companion logo step's output,\n not something you author. Hand-authoring it fabricates asset references the\n pipeline will overwrite or the validator will flag.\n\nAuthor every entity in English. Follow the `brand-logo-authoring` skill for the\nexact field contracts and the mark-type / background / visual-tone decision\naids — its full text is in your brief, under \"The skills this method tells you\nto FOLLOW\". Read it there; you cannot open files.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `brand-snapshot-valid`\ngate (`validateBrandSnapshot`) before it commits. A directed-but-ungenerated\nbrand (a `logoDirection` present, `resolvedAssets` still empty) is expected and\nonly WARNs — it is exactly the state you hand off to the companion logo step. A\nmissing logo direction and a missing visual tone are also warnings, reflecting a\nnot-yet-complete brief. Emit a clean brief and let the warnings stand honestly\nwhen the brand genuinely is not fully directed yet, rather than inventing a\nmark to silence them.\n\nAfter landing, the advisory judge reads the brief against two criteria — grounding in\nthe interview and the vision, and the audience-and-assets hand-off — and its verdicts\nreach the creator's review as notes. A verdict never refuses a landing.\n\n## Approval\n\nThe drafted `BrandSnapshot` is presented to the creator for approval before it\nbecomes the committed `brand-brief`. Show the brief back in plain prose — the\nname, the mark direction, the visual tone — and let the creator confirm or\ncorrect it. The brand-brief is what the logo is generated from and what\npropagates everywhere; it is worth one explicit human sign-off before the mark\nis made.\n\n## Runtime context\n\nBefore you start, read the current journey state, the vision brief that grounds\nthe brand's meaning, and any brand brief that already exists so you refine it\nrather than re-deriving it from scratch.\n\n(The vision and any previously landed brand brief arrive in your brief as the `vision-brief` and\n`brand-brief` input sections.)\n\n## References\n\nThese are skill FOLDERS installed in the application, and this step has no tools,\nso it does not open them. What reaches you is stated per skill below.\n\n- `brand-logo-authoring` — the field contracts for the `BrandSnapshot` (name /\n logoDirection / visualTone), the mark-type selection table, background\n derivation-safety, and deriving the visual tone from the market voice. Its\n FULL TEXT is in your brief; follow it exactly.\n",
50
50
  "skillRefs": [
51
51
  "brand-logo-authoring"
52
52
  ],
@@ -67,7 +67,11 @@
67
67
  "ref": "brand-tagline",
68
68
  "question": "Is there a tagline / supporting line to lock up with the name (e.g. \"Ship the week, not the meeting.\")? Answer \"none\" if not.",
69
69
  "kind": "free_text",
70
- "depth": "detail"
70
+ "depth": "detail",
71
+ "nonAnswers": [
72
+ "not_applicable",
73
+ "deferred"
74
+ ]
71
75
  },
72
76
  {
73
77
  "ref": "logo-mark-type",
@@ -99,16 +103,24 @@
99
103
  "ref": "visual-direction",
100
104
  "question": "Is there anything the logo or the look should evoke, include or avoid that the vision and the market's voice would not suggest on their own (e.g. \"no literal buildings\", \"a nod to craftsmanship\", \"warm, not corporate\")? Answer \"none\" and the symbolism, imagery and visual tone are derived from the vision and the market voice.",
101
105
  "kind": "free_text",
102
- "depth": "detail"
106
+ "depth": "detail",
107
+ "nonAnswers": [
108
+ "not_applicable"
109
+ ]
103
110
  },
104
111
  {
105
112
  "ref": "visual-color-seeds",
106
113
  "question": "Has the brand already committed to specific hex colors that the mark must agree with? If so, list them; otherwise answer \"none\" and let the design system own the palette.",
107
114
  "kind": "free_text",
108
- "depth": "detail"
115
+ "depth": "detail",
116
+ "nonAnswers": [
117
+ "not_applicable",
118
+ "deferred"
119
+ ]
109
120
  }
110
121
  ]
111
122
  },
123
+ "derivedFromAnswers": [],
112
124
  "contextSources": [],
113
125
  "draftableDocumentDefinitionRefs": [],
114
126
  "suspendsForClarification": false,
@@ -53,7 +53,8 @@ The UNION of four sources, never one of them alone:
53
53
  answer in your objective (the same decision as the compliance interview's `jurisdictions`
54
54
  question, asked once). When the creator names countries there ("market focus on Germany,
55
55
  France, Italy and Spain"), every one of them is a target, whether or not the market snapshot
56
- evidences it.
56
+ evidences it. When the creator left it NOT DECIDED YET, take the other three sources alone and
57
+ say in the brief that the creator's targets are open; never guess where the users are.
57
58
 
58
59
  A region tag ("EMEA") is not a jurisdiction: name the countries it implies for this product. If
59
60
  any EU member state is targeted, the **EU trade mark** (`EU`) applies too, because an EUTM has
@@ -89,6 +90,12 @@ So on most runs the web page is all you have. Try each register ONCE; when it re
89
90
  readable, report it as not checked and move on. Do not spend the run retrying a page that renders
90
91
  in the browser.
91
92
 
93
+ **A search belongs to the name it was run with.** When one attempt at a register failed and you
94
+ did not try it for the other candidates, report the name you searched as NOT CHECKED, and every
95
+ other candidate as NOT SEARCHED on that register, citing the attempt you made (its name and URL).
96
+ Never report one name's search as a search of another: the landed screening records the name each
97
+ search ran with, and a search attributed to the wrong name is refused.
98
+
92
99
  **Report, for every query, how you reached the register**: through its machine interface, or by
93
100
  fetching its web page. The landed screening records it, so a reader can tell the two apart.
94
101
 
@@ -107,9 +114,9 @@ An expired, withdrawn or refused mark is not a conflict.
107
114
 
108
115
  ### What to report per query
109
116
 
110
- The register, the jurisdictions it covers, the classes and match types searched, the
111
- result, every live conflicting mark (mark, owner, number, classes, status, the record's
112
- URL), the search URL, and today's date.
117
+ The register, **the name the search ran with**, the jurisdictions it covers, the classes and
118
+ match types searched, the result, every live conflicting mark (mark, owner, number, classes,
119
+ status, the record's URL), the search URL, and today's date.
113
120
 
114
121
  ## 3. A failure is not an answer
115
122
 
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "top_down.brand-name-research",
3
- "version": "0.2.0",
3
+ "version": "0.3.0",
4
4
  "phase": "top_down",
5
5
  "intent": "Propose candidate names for the product, grounded in the vision and the market snapshot, and run a minimal trademark screening of every candidate — proposed or supplied by the creator — against the public registers of the jurisdictions the product targets, in the Nice classes it lives in, for identical and near-identical live marks, with domain and same-category signals beside them. Returns a condensed, source-attributed brief and authors nothing. Never a legal clearance opinion: a register it could not query is reported as not checked, never as clear.",
6
6
  "preconditions": [
@@ -37,11 +37,12 @@
37
37
  }
38
38
  ],
39
39
  "method": {
40
- "guidance": "# Brand Name Research — propose, then screen\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\nYou are the **naming researcher**. You do two things: propose names for this product,\nand run a **minimal trademark screening** of every candidate. You do not choose the name\n— the creator does, from what you bring back — and you author no file.\n\n## 1. Propose (at least five)\n\nGround every proposal in what the application already decided:\n\n- the vision's **idea and mission** — what the product is FOR;\n- the market snapshot's **category language** (the words buyers and competitors use) and\n its **tones of voice** (a serious, formal voice wants a different name from a casual one);\n- the **target geographies and languages** — a name must be pronounceable and inoffensive\n in the target countries' main languages. Check that it carries no unfortunate meaning.\n\nPrefer distinctive names (invented or arbitrary) over descriptive ones. A purely\ndescriptive name (\"Building CRM\") is weak as a mark and usually refused registration.\n\n**A proposal must not be identical or close to any competitor or alternative the market\nsnapshot names**, nor to any name you find trading in the same category. Drop such a name\nbefore screening it; if one slips through, report the collision so it is never offered.\n\nPropose at least five, so at least three survive screening. One line per proposal on\nwhy it fits. That line is what the creator reads first.\n\n## 2. Screen every candidate\n\nScreen each proposal, **and every name the creator listed in the interview**\n(`names-to-screen`, unless it says \"none\"), the same way. Mark the creator's names as theirs.\n\n### Jurisdictions — derive, never assume the EU\n\nThe UNION of four sources, never one of them alone:\n\n- the market snapshot's ICP geographies;\n- the vision's compliance detail;\n- the jurisdictions the application DECLARES it operates in — the declared `operating_jurisdictions` context section of your brief,\n read from its configuration: each declared place is a target;\n- **the creator's own answer about where the product's users are** — the `target-jurisdictions`\n answer in your objective (the same decision as the compliance interview's `jurisdictions`\n question, asked once). When the creator names countries there (\"market focus on Germany,\n France, Italy and Spain\"), every one of them is a target, whether or not the market snapshot\n evidences it.\n\nA region tag (\"EMEA\") is not a jurisdiction: name the countries it implies for this product. If\nany EU member state is targeted, the **EU trade mark** (`EU`) applies too, because an EUTM has\neffect in every member state. International registrations (`WO`) are always in scope. Where the\ndata is HOSTED is not a trademark jurisdiction: a mark is protected where it is used in trade.\n\n**Every targeted country gets its own coverage**: a search of its national office (IT → UIBM,\nES → OEPM, DE → DPMA, FR → INPI, …), or a TMview search that includes that office, recorded with\nthat country among the jurisdictions it covers. Say which, per country.\n\n### Registers, and HOW you reach each one\n\n- **EUIPO** — EU trade marks, and international registrations designating the EU.\n- **TMview** (https://www.tmdn.org/tmview/) — the EU office and participating national\n offices in one search.\n- **WIPO Global Brand Database** (https://branddb.wipo.int/) — international (Madrid)\n registrations and many national collections.\n- **The national office of each targeted country** that TMview or WIPO does not already\n cover for you (for example the USPTO for the United States, UKIPO for the United Kingdom).\n\n**Use a register's machine interface, not its web page, wherever one is reachable.** A register's\nweb page is built for a person in a browser: on a real run every one of them returned nothing a\nfetch could read (results rendered in the browser, an empty page, a CAPTCHA, an HTTP 403, a search\nform that never ran). A machine interface returns structured records. Today:\n\n- **EUIPO** publishes a Trademark Search API, but it needs OAuth credentials from a registered\n developer account. Use it only when the application's providers give you access to it; without\n that, you cannot reach it.\n- **TMview and the WIPO Global Brand Database** publish no machine interface.\n- **A national office** may publish one: use it when its own documentation offers open access.\n\nSo on most runs the web page is all you have. Try each register ONCE; when it returns nothing\nreadable, report it as not checked and move on. Do not spend the run retrying a page that renders\nin the browser.\n\n**Report, for every query, how you reached the register**: through its machine interface, or by\nfetching its web page. The landed screening records it, so a reader can tell the two apart.\n\n### Classes\n\nThe Nice classes the product lives in: **9** (software) and **42** (software as a service)\nfor every software product, **35** where it is a business-management or CRM tool, and any\nother class the product category implies, each with a one-line reason.\n\n### Match types and status\n\nSearch **identical** marks (ignoring case and spacing) and **near-identical** ones\n(plurals, hyphenation, transposed or substituted letters, common phonetic variants).\nRecord only **live** marks: registered, or filed and pending (including under opposition).\nAn expired, withdrawn or refused mark is not a conflict.\n\n### What to report per query\n\nThe register, the jurisdictions it covers, the classes and match types searched, the\nresult, every live conflicting mark (mark, owner, number, classes, status, the record's\nURL), the search URL, and today's date.\n\n## 3. A failure is not an answer\n\nSome registers will not answer you. **When you cannot run a search, or cannot read its result,\nreport that register as NOT CHECKED, and say why.** Never infer \"no conflict\" from a search\nengine, from silence, or from your own memory of which marks exist. A candidate with a register\nnot checked is \"screening incomplete\", and one with NO register read is \"not screened\" — still\noffered to the creator, never as clear. Each unread search becomes a check the creator can run by\nhand, from a link the companion builds; you do not need to write that link.\n\n## 4. Signals beside the registers (recorded, never blocking)\n\n- the exact-match `.com` and the main country-code domains of the target countries,\n registered or available;\n- any company or product already trading under the name, with its URL, and **how it relates\n to this product's category**: the SAME JOB (the same work for the same kind of customer, or\n the same Nice class of goods and services), an ADJACENT category, or UNRELATED.\n\n**A product doing the same job under an identical or near-identical name is a COLLISION, not\nmerely a same-category use.** Report it as a collision, beside the competitor collisions, with\nits URL. \"Groundwork — Estimating & Job Suite\", a quote-to-invoice tool for tradespeople, is a\ncollision for a builders' CRM called \"Groundwork\", although no market snapshot listed it.\n\n## What you must never say\n\nNever write that a name is \"available\", \"free to use\", \"safe\" or \"cleared\". This is a\n**minimal trademark screening, not a legal clearance opinion**. The creator should consult an\nIP professional before filing or launching. You report what each register said, with its source.\n\n## Condensation\n\nReturn a brief, not a transcript: candidates, per-register results with URLs and dates,\ncollisions, signals, and an explicit list of what could not be checked.\n",
40
+ "guidance": "# Brand Name Research — propose, then screen\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\nYou are the **naming researcher**. You do two things: propose names for this product,\nand run a **minimal trademark screening** of every candidate. You do not choose the name\n— the creator does, from what you bring back — and you author no file.\n\n## 1. Propose (at least five)\n\nGround every proposal in what the application already decided:\n\n- the vision's **idea and mission** — what the product is FOR;\n- the market snapshot's **category language** (the words buyers and competitors use) and\n its **tones of voice** (a serious, formal voice wants a different name from a casual one);\n- the **target geographies and languages** — a name must be pronounceable and inoffensive\n in the target countries' main languages. Check that it carries no unfortunate meaning.\n\nPrefer distinctive names (invented or arbitrary) over descriptive ones. A purely\ndescriptive name (\"Building CRM\") is weak as a mark and usually refused registration.\n\n**A proposal must not be identical or close to any competitor or alternative the market\nsnapshot names**, nor to any name you find trading in the same category. Drop such a name\nbefore screening it; if one slips through, report the collision so it is never offered.\n\nPropose at least five, so at least three survive screening. One line per proposal on\nwhy it fits. That line is what the creator reads first.\n\n## 2. Screen every candidate\n\nScreen each proposal, **and every name the creator listed in the interview**\n(`names-to-screen`, unless it says \"none\"), the same way. Mark the creator's names as theirs.\n\n### Jurisdictions — derive, never assume the EU\n\nThe UNION of four sources, never one of them alone:\n\n- the market snapshot's ICP geographies;\n- the vision's compliance detail;\n- the jurisdictions the application DECLARES it operates in — the declared `operating_jurisdictions` context section of your brief,\n read from its configuration: each declared place is a target;\n- **the creator's own answer about where the product's users are** — the `target-jurisdictions`\n answer in your objective (the same decision as the compliance interview's `jurisdictions`\n question, asked once). When the creator names countries there (\"market focus on Germany,\n France, Italy and Spain\"), every one of them is a target, whether or not the market snapshot\n evidences it. When the creator left it NOT DECIDED YET, take the other three sources alone and\n say in the brief that the creator's targets are open; never guess where the users are.\n\nA region tag (\"EMEA\") is not a jurisdiction: name the countries it implies for this product. If\nany EU member state is targeted, the **EU trade mark** (`EU`) applies too, because an EUTM has\neffect in every member state. International registrations (`WO`) are always in scope. Where the\ndata is HOSTED is not a trademark jurisdiction: a mark is protected where it is used in trade.\n\n**Every targeted country gets its own coverage**: a search of its national office (IT → UIBM,\nES → OEPM, DE → DPMA, FR → INPI, …), or a TMview search that includes that office, recorded with\nthat country among the jurisdictions it covers. Say which, per country.\n\n### Registers, and HOW you reach each one\n\n- **EUIPO** — EU trade marks, and international registrations designating the EU.\n- **TMview** (https://www.tmdn.org/tmview/) — the EU office and participating national\n offices in one search.\n- **WIPO Global Brand Database** (https://branddb.wipo.int/) — international (Madrid)\n registrations and many national collections.\n- **The national office of each targeted country** that TMview or WIPO does not already\n cover for you (for example the USPTO for the United States, UKIPO for the United Kingdom).\n\n**Use a register's machine interface, not its web page, wherever one is reachable.** A register's\nweb page is built for a person in a browser: on a real run every one of them returned nothing a\nfetch could read (results rendered in the browser, an empty page, a CAPTCHA, an HTTP 403, a search\nform that never ran). A machine interface returns structured records. Today:\n\n- **EUIPO** publishes a Trademark Search API, but it needs OAuth credentials from a registered\n developer account. Use it only when the application's providers give you access to it; without\n that, you cannot reach it.\n- **TMview and the WIPO Global Brand Database** publish no machine interface.\n- **A national office** may publish one: use it when its own documentation offers open access.\n\nSo on most runs the web page is all you have. Try each register ONCE; when it returns nothing\nreadable, report it as not checked and move on. Do not spend the run retrying a page that renders\nin the browser.\n\n**A search belongs to the name it was run with.** When one attempt at a register failed and you\ndid not try it for the other candidates, report the name you searched as NOT CHECKED, and every\nother candidate as NOT SEARCHED on that register, citing the attempt you made (its name and URL).\nNever report one name's search as a search of another: the landed screening records the name each\nsearch ran with, and a search attributed to the wrong name is refused.\n\n**Report, for every query, how you reached the register**: through its machine interface, or by\nfetching its web page. The landed screening records it, so a reader can tell the two apart.\n\n### Classes\n\nThe Nice classes the product lives in: **9** (software) and **42** (software as a service)\nfor every software product, **35** where it is a business-management or CRM tool, and any\nother class the product category implies, each with a one-line reason.\n\n### Match types and status\n\nSearch **identical** marks (ignoring case and spacing) and **near-identical** ones\n(plurals, hyphenation, transposed or substituted letters, common phonetic variants).\nRecord only **live** marks: registered, or filed and pending (including under opposition).\nAn expired, withdrawn or refused mark is not a conflict.\n\n### What to report per query\n\nThe register, **the name the search ran with**, the jurisdictions it covers, the classes and\nmatch types searched, the result, every live conflicting mark (mark, owner, number, classes,\nstatus, the record's URL), the search URL, and today's date.\n\n## 3. A failure is not an answer\n\nSome registers will not answer you. **When you cannot run a search, or cannot read its result,\nreport that register as NOT CHECKED, and say why.** Never infer \"no conflict\" from a search\nengine, from silence, or from your own memory of which marks exist. A candidate with a register\nnot checked is \"screening incomplete\", and one with NO register read is \"not screened\" — still\noffered to the creator, never as clear. Each unread search becomes a check the creator can run by\nhand, from a link the companion builds; you do not need to write that link.\n\n## 4. Signals beside the registers (recorded, never blocking)\n\n- the exact-match `.com` and the main country-code domains of the target countries,\n registered or available;\n- any company or product already trading under the name, with its URL, and **how it relates\n to this product's category**: the SAME JOB (the same work for the same kind of customer, or\n the same Nice class of goods and services), an ADJACENT category, or UNRELATED.\n\n**A product doing the same job under an identical or near-identical name is a COLLISION, not\nmerely a same-category use.** Report it as a collision, beside the competitor collisions, with\nits URL. \"Groundwork — Estimating & Job Suite\", a quote-to-invoice tool for tradespeople, is a\ncollision for a builders' CRM called \"Groundwork\", although no market snapshot listed it.\n\n## What you must never say\n\nNever write that a name is \"available\", \"free to use\", \"safe\" or \"cleared\". This is a\n**minimal trademark screening, not a legal clearance opinion**. The creator should consult an\nIP professional before filing or launching. You report what each register said, with its source.\n\n## Condensation\n\nReturn a brief, not a transcript: candidates, per-register results with URLs and dates,\ncollisions, signals, and an explicit list of what could not be checked.\n",
41
41
  "skillRefs": [
42
42
  "brand-name-screening"
43
43
  ],
44
44
  "skillBodyRefs": [],
45
+ "derivedFromAnswers": [],
45
46
  "contextSources": [
46
47
  "operating_jurisdictions"
47
48
  ],
@@ -1 +1 @@
1
- {"aggregationPolicyRef":"application-creation:aggregation/worst-brand-name-screening-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand-name-screening.candidate","vision.idea","vision.mission","market.category","market.alternative","market.tone-of-voice"],"criterionRef":"application-creation:criterion/brand-name-proposals-grounded-and-distinct","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-proposals-grounded-and-distinct","requirementVersion":1}],"instruction":"Determine whether the PROPOSALS are worth choosing from: each companion-proposed name carries a rationale traceable to the vision's idea or mission and to the market's category language or tone of voice; no proposal is identical or close to a competitor or alternative the market snapshot names, or to a company the evidence found doing the same job under that name — and every such same-job product is recorded as a competitor collision, with a SAME_JOB category relation, never only as a same-category use (a creator-supplied name may collide — it is offered only as an explicit keep-despite-conflict, so it is not a finding here); and every name the creator listed in the interview is on the list, marked as theirs. Nothing in the screening may assert that a name is available, free to use or legally cleared.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a generic rationale, a weakly distinctive or purely descriptive proposal, or fewer than three proposals surviving the screening.","GAP":"A proposal collides with a named competitor or a same-job product, a same-job product with a candidate's name is recorded only as a same-category use, a creator-listed name is missing, or the screening claims a name is available or legally cleared.","INDETERMINATE":"The vision, the market snapshot or the creator's interview answer is not in evidence.","PASS":"Every proposal is grounded and distinct from the named competitors, the creator's names are all present, and nothing claims availability or clearance."}},{"assessesAspects":["brand-name-screening.candidate","brand-name-screening.jurisdiction","brand-name-screening.nice-class","market.icp"],"criterionRef":"application-creation:criterion/brand-name-screening-coverage-and-honesty","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty","requirementVersion":1}],"instruction":"Determine whether the screening COVERS what it declares and reports it HONESTLY: the declared jurisdictions are the union of the market's ICP geographies, the vision, the operating jurisdictions the application declares in its configuration (operatingJurisdictions) and the creator's own target-jurisdictions answer (an EU member state target brings the EU trade mark with it; a region tag is resolved to countries; every country the creator names or the configuration declares is declared and reached by its national office or a TMview search listing it), the Nice classes include 9 and 42 and any class the product category implies, every candidate has a query reaching each declared jurisdiction in those classes for identical and near-identical marks, every query cites a source URL and a date, and no register the evidence reports as unreachable or unread appears with a clear result. A register that could not be checked and is recorded as not checked is a legitimate, honest state, not a finding — UNLESS no register returned a result for any candidate: then the screening screened nothing, however honestly it says so, and that is the worst verdict.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is honest but thin: a class the category implies is missing, or several registers could not be checked and are correctly recorded as such while at least one register returned a result.","GAP":"No register returned a result for ANY candidate (0% coverage: nothing was screened), a country the creator named or the configuration declares (operatingJurisdictions) is not a declared jurisdiction, a query the evidence reports as unreachable or unread is recorded as clear, a declared jurisdiction is never queried while the candidate reads as cleared, or a query has no source.","INDETERMINATE":"The research evidence or the market snapshot is not in evidence, so coverage and honesty cannot be established.","PASS":"Jurisdictions and classes follow from the product, every candidate is queried across them with sources and dates, and nothing unchecked is shown as clear."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-name-screening","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-name-screening-produce"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
1
+ {"aggregationPolicyRef":"application-creation:aggregation/worst-brand-name-screening-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand-name-screening.candidate","vision.idea","vision.mission","market.category","market.alternative","market.tone-of-voice"],"criterionRef":"application-creation:criterion/brand-name-proposals-grounded-and-distinct","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-proposals-grounded-and-distinct","requirementVersion":1}],"instruction":"Determine whether the PROPOSALS are worth choosing from: each companion-proposed name carries a rationale traceable to the vision's idea or mission and to the market's category language or tone of voice; no proposal is identical or close to a competitor or alternative the market snapshot names, or to a company the evidence found doing the same job under that name — and every such same-job product is recorded as a competitor collision, with a SAME_JOB category relation, never only as a same-category use (a creator-supplied name may collide — it is offered only as an explicit keep-despite-conflict, so it is not a finding here); and every name the creator listed in the interview is on the list, marked as theirs. Nothing in the screening may assert that a name is available, free to use or legally cleared.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a generic rationale, a weakly distinctive or purely descriptive proposal, or fewer than three proposals surviving the screening.","GAP":"A proposal collides with a named competitor or a same-job product, a same-job product with a candidate's name is recorded only as a same-category use, a creator-listed name is missing, or the screening claims a name is available or legally cleared.","INDETERMINATE":"The vision, the market snapshot or the creator's interview answer is not in evidence.","PASS":"Every proposal is grounded and distinct from the named competitors, the creator's names are all present, and nothing claims availability or clearance."}},{"assessesAspects":["brand-name-screening.candidate","brand-name-screening.jurisdiction","brand-name-screening.nice-class","market.icp"],"criterionRef":"application-creation:criterion/brand-name-screening-coverage-and-honesty","criterionVersion":4,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty","requirementVersion":1}],"instruction":"Determine whether the screening COVERS what it declares and reports it HONESTLY: the declared jurisdictions are the union of the market's ICP geographies, the vision, the operating jurisdictions the application declares in its configuration (operatingJurisdictions) and the creator's own target-jurisdictions answer (an EU member state target brings the EU trade mark with it; a region tag is resolved to countries; every country the creator names or the configuration declares is declared and reached by its national office or a TMview search listing it), the Nice classes include 9 and 42 and any class the product category implies, every candidate has a query reaching each declared jurisdiction in those classes for identical and near-identical marks, every query cites a source URL and a date, every query records the name it searched and that name is its own candidate's (a register tried once, for another name, is recorded NOT_SEARCHED for the others, citing that attempt), and no register the evidence reports as unreachable or unread appears with a clear result. When the creator left the target-jurisdictions answer NOT DECIDED YET and no other source names a place, an empty jurisdiction list is the honest declaration, never a finding; an invented target is a GAP. A register that could not be checked and is recorded as not checked is a legitimate, honest state, not a finding — UNLESS no register returned a result for any candidate: then the screening screened nothing, however honestly it says so, and that is the worst verdict.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is honest but thin: a class the category implies is missing, or several registers could not be checked and are correctly recorded as such while at least one register returned a result.","GAP":"No register returned a result for ANY candidate (0% coverage: nothing was screened), a country the creator named or the configuration declares (operatingJurisdictions) is not a declared jurisdiction, a query the evidence reports as unreachable or unread is recorded as clear, a declared jurisdiction is never queried while the candidate reads as cleared, a query has no source, or a candidate carries another name's search as its own (its searched name or its search URL is another candidate's).","INDETERMINATE":"The research evidence or the market snapshot is not in evidence, so coverage and honesty cannot be established.","PASS":"Jurisdictions and classes follow from the product, every candidate is queried across them with sources and dates, and nothing unchecked is shown as clear."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-name-screening","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-name-screening-produce"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}