@wildo-ai/framework-knowledge 1.1.11 → 1.1.13

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 (812) 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 +3 -3
  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 +180 -32
  13. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  14. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  15. package/dist/esm/framework-knowledge.loader.js.map +1 -1
  16. package/dist/esm/framework-knowledge.research-provenance.d.ts +6 -4
  17. package/dist/esm/framework-knowledge.research-provenance.d.ts.map +1 -1
  18. package/dist/esm/framework-knowledge.research-provenance.js.map +1 -1
  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.map +1 -1
  22. package/dist/esm/index.js.map +1 -1
  23. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -3
  24. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  25. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +4 -12
  26. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  27. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +12 -1
  29. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +7 -4
  31. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  32. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +76 -14
  33. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +0 -4
  35. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  36. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +3 -15
  37. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  39. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -1
  41. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  43. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  44. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +1 -1
  45. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +1 -1
  47. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  49. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +35 -14
  50. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  51. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +16 -8
  52. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  53. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +19 -8
  54. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  55. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +30 -3
  56. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  57. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +87 -16
  58. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  59. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
  60. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
  61. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +2 -2
  62. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -1
  63. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +2 -2
  64. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -1
  65. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +5 -1
  66. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  67. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +3 -2
  68. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  69. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  71. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +45 -10
  72. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
  73. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +61 -21
  74. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -1
  75. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +4 -3
  76. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
  77. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +8 -5
  78. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -1
  79. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
  80. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -1
  81. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +2 -2
  82. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
  83. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +3 -5
  84. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -1
  85. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +1 -1
  86. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  87. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +3 -3
  88. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  89. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  90. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +8 -6
  91. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  92. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +5 -0
  93. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
  94. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +8 -1
  95. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -1
  96. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
  97. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -1
  98. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +4 -1
  99. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  100. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +11 -3
  101. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  102. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -1
  103. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +1 -1
  104. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
  105. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
  106. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +6 -4
  107. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
  108. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +3 -1
  109. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
  110. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +4 -1
  111. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
  112. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +10 -1
  113. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  114. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +36 -13
  115. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  116. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +8 -2
  117. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  118. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +7 -1
  119. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  120. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +4 -1
  121. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  122. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +34 -6
  123. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  124. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +5 -2
  125. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  126. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +4 -3
  127. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  128. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  129. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +2 -2
  130. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  131. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +22 -10
  132. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  133. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +39 -29
  134. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  135. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  136. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  137. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +8 -3
  138. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  139. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -7
  140. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  141. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
  142. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  143. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
  144. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -1
  145. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  146. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  147. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  148. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +2 -2
  149. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  150. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  151. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  152. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  153. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +1 -1
  154. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  155. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  156. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +13 -5
  157. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  158. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +3 -7
  159. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  160. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +12 -14
  161. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  162. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +3 -0
  163. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
  164. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +2 -1
  165. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
  166. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +3 -1
  167. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  168. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +2 -1
  169. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  170. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts +4 -1
  171. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts.map +1 -1
  172. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js +14 -1
  173. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js.map +1 -1
  174. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +3 -1
  175. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  176. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +4 -2
  177. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  178. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +34 -1
  179. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  180. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +35 -17
  181. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  182. package/dist/esm/source-anchor-grammar.d.ts.map +1 -1
  183. package/dist/esm/source-anchor-grammar.js.map +1 -1
  184. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  185. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  186. package/dist/knowledge/manifest.json +7 -7
  187. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +6 -0
  188. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +4 -4
  189. package/dist/knowledge/playbooks/bottom_up.build/method.md +12 -2
  190. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +5 -3
  191. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  192. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  193. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +439 -27
  194. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +15 -4
  195. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +203 -7
  196. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -5
  197. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +1 -0
  198. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -0
  199. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +1 -0
  200. package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +2 -2
  201. package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +2 -1
  202. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
  203. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
  204. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +104 -2
  205. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -4
  206. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +59 -4
  207. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +18 -6
  208. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +121 -24
  209. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +55 -8
  210. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +15 -8
  211. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +2 -1
  212. package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +19 -2
  213. package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +4 -3
  214. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +34 -0
  215. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +9 -2
  216. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +1 -0
  217. package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +27 -12
  218. package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +11 -5
  219. package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +4 -4
  220. package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +7 -2
  221. package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +1 -0
  222. package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +6 -6
  223. package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +3 -4
  224. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -1
  225. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -1
  226. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +56 -5
  227. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +3 -2
  228. package/dist/knowledge/playbooks/refinement.document-facts/method.md +6 -4
  229. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +5 -1
  230. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +8 -1
  231. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -0
  232. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  233. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  234. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -3
  235. package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +11 -4
  236. package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +3 -2
  237. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -1
  238. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -1
  239. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +16 -6
  240. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +3 -2
  241. package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +5 -1
  242. package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
  243. package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
  244. package/dist/knowledge/playbooks/top_down.business-model/method.md +43 -11
  245. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +24 -8
  246. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +6 -2
  247. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +1 -1
  248. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +49 -14
  249. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +3 -3
  250. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +6 -2
  251. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +20 -0
  252. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +4 -3
  253. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -1
  254. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -1
  255. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +69 -65
  256. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +11 -7
  257. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +1 -0
  258. package/dist/knowledge/playbooks/top_down.definition/method.md +3 -1
  259. package/dist/knowledge/playbooks/top_down.definition/playbook.json +11 -3
  260. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +1 -0
  261. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -0
  262. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +1 -0
  263. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +4 -2
  264. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +4 -3
  265. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +1 -0
  266. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +3 -0
  267. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +3 -2
  268. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  269. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  270. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +1 -0
  271. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +14 -0
  272. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +11 -7
  273. package/dist/knowledge/playbooks/top_down.risk-register/method.md +7 -0
  274. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +5 -1
  275. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +6 -1
  276. package/dist/knowledge/playbooks/top_down.service-method/method.md +19 -1
  277. package/dist/knowledge/playbooks/top_down.service-method/playbook.json +16 -4
  278. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +5 -2
  279. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +9 -3
  280. package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-protocol.json +1 -1
  281. package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-treatment.json +1 -1
  282. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +17 -2
  283. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +59 -15
  284. package/dist/knowledge/references/application-documentation-chapters.config.md +45 -10
  285. package/dist/knowledge/references/application-documentation-plan.config.md +2 -2
  286. package/dist/knowledge/references/application-maturity.config.md +70 -1
  287. package/dist/knowledge/references/backend.inbound-channels.attachment-adoption.md +4 -2
  288. package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +52 -11
  289. package/dist/knowledge/references/backend.inbound-handlers.definition.md +38 -1
  290. package/dist/knowledge/references/brand.name-screening.config.md +30 -3
  291. package/dist/knowledge/references/build-plan.task-graph.config.md +200 -4
  292. package/dist/knowledge/references/business-model.pricing-plan.config.md +12 -9
  293. package/dist/knowledge/references/business-model.snapshot.config.md +29 -2
  294. package/dist/knowledge/references/business-model.snapshot.validation.md +11 -8
  295. package/dist/knowledge/references/companion.introspection.behaviors.market.md +3 -0
  296. package/dist/knowledge/references/companion.market.generation-service.md +46 -5
  297. package/dist/knowledge/references/companion.market.prompt-renderer.md +1 -1
  298. package/dist/knowledge/references/companion.technical-doc.service.md +195 -63
  299. package/dist/knowledge/references/domain-plan.record-partition.md +105 -0
  300. package/dist/knowledge/references/engine.client-bundle.allow-list.md +3 -1
  301. package/dist/knowledge/references/engine.saas-technical-doc.config.md +69 -15
  302. package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +10 -0
  303. package/dist/knowledge/references/example.backend.addon-wiring.module.md +6 -0
  304. package/dist/knowledge/references/example.backend.custom-operation.declared-refusal-code.md +41 -0
  305. package/dist/knowledge/references/example.backend.custom-operation.external-effect-reservation.md +107 -0
  306. package/dist/knowledge/references/example.blueprint.definition.internal-tool.md +4 -2
  307. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +8 -5
  308. package/dist/knowledge/references/example.infra.environment-config.local.md +13 -66
  309. package/dist/knowledge/references/example.module.companion-exports.full.md +1 -0
  310. package/dist/knowledge/references/example.module.relationships.actor-edge-back-to-scope-owner.md +35 -35
  311. package/dist/knowledge/references/example.navigation.one-entry-per-concept.md +47 -0
  312. package/dist/knowledge/references/example.organization-identity.system-of-record-partitions.md +18 -0
  313. package/dist/knowledge/references/example.provider.backend-module-shape.md +28 -4
  314. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +0 -4
  315. package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +21 -0
  316. package/dist/knowledge/references/example.resource.custom-view.backend-refusal.md +75 -0
  317. package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +8 -7
  318. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +37 -2
  319. package/dist/knowledge/references/example.resource.ui-behavior.record-template.md +0 -1
  320. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +1 -1
  321. package/dist/knowledge/references/example.resource.ui-behavior.workflow-record-page.md +212 -0
  322. package/dist/knowledge/references/example.subject-export.portability-archive.md +42 -0
  323. package/dist/knowledge/references/example.views.app-level.workflow-home.md +238 -0
  324. package/dist/knowledge/references/example.website.demo.complete-items.md +3 -3
  325. package/dist/knowledge/references/example.website.pricing.audit-payloads.md +38 -0
  326. package/dist/knowledge/references/example.website.pricing.catalog-load.md +77 -0
  327. package/dist/knowledge/references/example.website.pricing.offers.md +43 -0
  328. package/dist/knowledge/references/example.website.pricing.plans-section.md +20 -0
  329. package/dist/knowledge/references/example.website.pricing.plans.md +88 -0
  330. package/dist/knowledge/references/example.website.section.stats.md +1 -1
  331. package/dist/knowledge/references/experience-plan.config.md +111 -1
  332. package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +2 -0
  333. package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +8 -1
  334. package/dist/knowledge/references/external-connectors.models.hook-signature-algorithms.md +104 -0
  335. package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +11 -6
  336. package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +165 -0
  337. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +1035 -19
  338. package/dist/knowledge/references/external-connectors.private.provider-compliance-state-collector.md +36 -0
  339. package/dist/knowledge/references/external-connectors.private.provider-configuration-check.md +69 -0
  340. package/dist/knowledge/references/integration-plan.config.md +7 -7
  341. package/dist/knowledge/references/placement-plan.config.md +19 -0
  342. package/dist/knowledge/references/platform.config.backing-services.md +9 -11
  343. package/dist/knowledge/references/platform.config.environment.deployment.md +133 -8
  344. package/dist/knowledge/references/platform.config.infra-provider-resolution.md +3 -3
  345. package/dist/knowledge/references/platform.config.infrastructure-host.md +1 -1
  346. package/dist/knowledge/references/platform.config.platform-key-management.md +89 -10
  347. package/dist/knowledge/references/platform.config.saas.md +20 -18
  348. package/dist/knowledge/references/presets.3d.frame-style-resolution.md +65 -0
  349. package/dist/knowledge/references/presets.layouts-2d.authoring.md +1 -1
  350. package/dist/knowledge/references/presets.models.field-form-control-variant.md +32 -0
  351. package/dist/knowledge/references/presets.models.labelling.sections.md +39 -0
  352. package/dist/knowledge/references/presets.models.surface-policy.defaults.md +3 -3
  353. package/dist/knowledge/references/presets.models.surface-variant.md +5 -4
  354. package/dist/knowledge/references/presets.themes.compose-theme.md +2 -1
  355. package/dist/knowledge/references/requirements.engine-substance.md +38 -0
  356. package/dist/knowledge/references/requirements.functional-requirement.config.md +11 -0
  357. package/dist/knowledge/references/requirements.non-functional-requirement.config.md +15 -4
  358. package/dist/knowledge/references/requirements.snapshot.config.md +2 -3
  359. package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +49 -2
  360. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +11 -4
  361. package/dist/knowledge/references/saas.backend.actor-execution-continuation.md +21 -0
  362. package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +5 -1
  363. package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +1 -1
  364. package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +13 -1
  365. package/dist/knowledge/references/saas.backend.custom-operation.authoritative-fields.md +4 -1
  366. package/dist/knowledge/references/saas.backend.custom-operation.core-write-precondition.md +38 -0
  367. package/dist/knowledge/references/saas.backend.custom-operation.external-effect-reservation.md +109 -0
  368. package/dist/knowledge/references/saas.backend.custom-operation.hook-transaction-posture.md +43 -0
  369. package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +1 -1
  370. package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +62 -13
  371. package/dist/knowledge/references/saas.backend.domain-module.md +30 -1
  372. package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +26 -3
  373. package/dist/knowledge/references/saas.backend.flows-actors.chat-reply-handler.md +13 -1
  374. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +435 -2
  375. package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +5 -3
  376. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +1 -1
  377. package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +9 -4
  378. package/dist/knowledge/references/saas.backend.flows.start-flow-method.md +2 -1
  379. package/dist/knowledge/references/saas.backend.privacy.subject-export-archive.md +26 -0
  380. package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +21 -19
  381. package/dist/knowledge/references/saas.backend.system-access-service.md +159 -4
  382. package/dist/knowledge/references/saas.config.content-security-policy.md +26 -9
  383. package/dist/knowledge/references/saas.data-seeding.definition-input.md +1 -1
  384. package/dist/knowledge/references/saas.data-seeding.modes.md +4 -1
  385. package/dist/knowledge/references/saas.data-seeding.row-reference.md +2 -4
  386. package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +6 -0
  387. package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +2 -0
  388. package/dist/knowledge/references/saas.frontend.chart-dashboard-view.md +43 -0
  389. package/dist/knowledge/references/saas.frontend.chart-dashboard.md +133 -0
  390. package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +8 -4
  391. package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +76 -9
  392. package/dist/knowledge/references/saas.frontend.command-menu.search-resource.md +3 -3
  393. package/dist/knowledge/references/saas.frontend.errors.backend-refusal.md +96 -0
  394. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +40 -0
  395. package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +4 -0
  396. package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +3 -5
  397. package/dist/knowledge/references/saas.frontend.record-page-parts.md +117 -0
  398. package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +46 -16
  399. package/dist/knowledge/references/saas.frontend.related-resource-sections.md +6 -0
  400. package/dist/knowledge/references/saas.frontend.resource-header-title.md +1 -1
  401. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +43 -9
  402. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +259 -15
  403. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -2
  404. package/dist/knowledge/references/saas.frontend.section-stages.md +63 -0
  405. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +42 -0
  406. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +6 -9
  407. package/dist/knowledge/references/saas.frontend.viewer-may-perform-operation.md +52 -0
  408. package/dist/knowledge/references/saas.models.agent-suspension.md +8 -8
  409. package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +21 -0
  410. package/dist/knowledge/references/saas.models.auth.relationship-grantor-authentication.md +2 -2
  411. package/dist/knowledge/references/saas.models.chart-dashboard-tile-sizes.md +40 -0
  412. package/dist/knowledge/references/saas.models.config.declared-type-renames.md +246 -0
  413. package/dist/knowledge/references/saas.models.config.organization-types.md +20 -0
  414. package/dist/knowledge/references/saas.models.conversation-threads.md +39 -3
  415. package/dist/knowledge/references/saas.models.crypto-keys.floors.md +10 -0
  416. package/dist/knowledge/references/saas.models.crypto-keys.local-provider.md +2 -0
  417. package/dist/knowledge/references/saas.models.crypto-keys.purpose-descriptor.md +39 -0
  418. package/dist/knowledge/references/saas.models.crypto-keys.purposes.md +7 -0
  419. package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -78
  420. package/dist/knowledge/references/saas.models.engine-capabilities.md +11 -2
  421. package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +3 -0
  422. package/dist/knowledge/references/saas.models.external-data-pipeline.md +15 -8
  423. package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report.md +13 -9
  424. package/dist/knowledge/references/saas.models.flows-actors.agent-configuration.md +29 -0
  425. package/dist/knowledge/references/saas.models.flows-actors.agent-content-guardrails-environment.md +52 -0
  426. package/dist/knowledge/references/saas.models.flows-actors.agent-operation-record.md +7 -0
  427. package/dist/knowledge/references/saas.models.flows-actors.human-decision-decider.md +8 -0
  428. package/dist/knowledge/references/saas.models.flows-actors.human-input-form.md +47 -12
  429. package/dist/knowledge/references/saas.models.flows-actors.operation-approval-requirement.md +31 -0
  430. package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +3 -3
  431. package/dist/knowledge/references/saas.models.flows.runnable-model.md +21 -2
  432. package/dist/knowledge/references/saas.models.guidance-flow.md +1 -1
  433. package/dist/knowledge/references/saas.models.http-api-binding.md +19 -8
  434. package/dist/knowledge/references/saas.models.human-decision-review-marker.md +1 -1
  435. package/dist/knowledge/references/saas.models.inbound-channels.md +71 -2
  436. package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +1 -1
  437. package/dist/knowledge/references/saas.models.notifications.targets.md +3 -1
  438. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +201 -15
  439. package/dist/knowledge/references/saas.models.organization-assigned-rows-declaration.md +2 -1
  440. package/dist/knowledge/references/saas.models.organization-dashboard-layout.md +61 -0
  441. package/dist/knowledge/references/saas.models.organization-own-rows-declaration.md +5 -2
  442. package/dist/knowledge/references/saas.models.organizations.identity-declaration.md +201 -0
  443. package/dist/knowledge/references/saas.models.organizations.organization-relationships.md +25 -3
  444. package/dist/knowledge/references/saas.models.organizations.relationship-invitations.md +6 -2
  445. package/dist/knowledge/references/saas.models.organizations.relationship-kinds.md +14 -0
  446. package/dist/knowledge/references/saas.models.organizations.relationship-record-separation.md +1 -0
  447. package/dist/knowledge/references/saas.models.privacy.data-residency.md +676 -0
  448. package/dist/knowledge/references/saas.models.privacy.legal-holds.md +46 -2
  449. package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +6 -0
  450. package/dist/knowledge/references/saas.models.privacy.retention-binding.md +84 -1
  451. package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +10 -0
  452. package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +5 -3
  453. package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +2 -0
  454. package/dist/knowledge/references/saas.models.privacy.subject-export.md +134 -0
  455. package/dist/knowledge/references/saas.models.provider-capabilities.md +5 -0
  456. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +12 -6
  457. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +15 -0
  458. package/dist/knowledge/references/saas.models.providers.processing-region-reach.md +132 -0
  459. package/dist/knowledge/references/saas.models.providers.processing-region-selection.md +139 -0
  460. package/dist/knowledge/references/saas.models.representative-activity.md +4 -0
  461. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +107 -42
  462. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +35 -0
  463. package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +4 -2
  464. package/dist/knowledge/references/saas.models.resource-config.operation-condition-parameters.md +56 -0
  465. package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +16 -6
  466. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +38 -0
  467. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +14 -16
  468. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +2 -2
  469. package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +21 -0
  470. package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +32 -15
  471. package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +5 -4
  472. package/dist/knowledge/references/saas.models.roles.definition.md +12 -1
  473. package/dist/knowledge/references/saas.models.roles.organization-defaults.md +6 -0
  474. package/dist/knowledge/references/saas.models.schema-family-builder.md +17 -2
  475. package/dist/knowledge/references/saas.models.system-of-record-actions.md +65 -1
  476. package/dist/knowledge/references/saas.models.system-of-record-capabilities.md +3 -1
  477. package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +16 -0
  478. package/dist/knowledge/references/saas.models.systems-of-record.md +75 -14
  479. package/dist/knowledge/references/saas.public-runtime.contract.md +41 -23
  480. package/dist/knowledge/references/saas.rag.retrieval-refusals.md +3 -2
  481. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +12 -4
  482. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +21 -2
  483. package/dist/knowledge/references/saas.specifications.engine-resource-sub-domain.md +105 -0
  484. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +6 -2
  485. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +20 -3
  486. package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +100 -71
  487. package/dist/knowledge/references/saas.specifications.translation-glossary.md +80 -0
  488. package/dist/knowledge/references/saas.website.astro.label-loader.md +44 -10
  489. package/dist/knowledge/references/saas.website.astro.runtime-helper.md +3 -2
  490. package/dist/knowledge/references/saas.website.blog.collection-config.md +36 -32
  491. package/dist/knowledge/references/saas.website.blog.cover-resolver.md +1 -1
  492. package/dist/knowledge/references/saas.website.blog.frontmatter.md +2 -2
  493. package/dist/knowledge/references/saas.website.blog.post-renderer.md +2 -2
  494. package/dist/knowledge/references/saas.website.blog.react-mdx-integration.md +26 -19
  495. package/dist/knowledge/references/saas.website.blog.react-mdx-query.md +1 -1
  496. package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +3 -1
  497. package/dist/knowledge/references/saas.website.config.site-context-loader.md +6 -3
  498. package/dist/knowledge/references/saas.website.label-keys.format.md +3 -2
  499. package/dist/knowledge/references/saas.website.label-pack.validator.md +3 -1
  500. package/dist/knowledge/references/service-method.config.md +35 -2
  501. package/dist/knowledge/references/vision.constraint.config.md +4 -2
  502. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +60 -0
  503. package/dist/knowledge/references/zod.decorators.data-categories.md +46 -46
  504. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +24 -0
  505. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +11 -0
  506. package/dist/knowledge/references/zod.decorators.file-schema.md +4 -3
  507. package/dist/knowledge/references/zod.decorators.rag-source.md +20 -20
  508. package/dist/knowledge/references/zod.decorators.schema-metadata.md +2 -0
  509. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +30 -24
  510. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +63 -0
  511. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +63 -0
  512. package/dist/knowledge/references/zod.factories.bigdecimal.md +4 -4
  513. package/dist/knowledge/references/zod.factories.code.md +4 -4
  514. package/dist/knowledge/references/zod.factories.duration.md +4 -4
  515. package/dist/knowledge/references/zod.factories.money.md +4 -4
  516. package/dist/knowledge/references/zod.factories.phone.md +4 -4
  517. package/dist/knowledge/references/zod.factories.year-month.md +79 -0
  518. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  519. package/dist/knowledge/registries/framework-topics.json +455 -2
  520. package/dist/knowledge/registries/playbooks.json +51 -39
  521. package/dist/knowledge/registries/source-tags.json +2505 -1627
  522. package/dist/knowledge/rules/database-migration-obligation.md +6 -7
  523. package/dist/knowledge/rules/live-context-door.md +1 -1
  524. package/dist/knowledge/skills/INDEX.md +3 -1
  525. package/dist/knowledge/skills/agent-work-review/references/framework-actor-execution-continuation-api.md +24 -0
  526. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +1 -1
  527. package/dist/knowledge/skills/agent-work-review/references/framework-human-input-form-api.md +47 -12
  528. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +30 -19
  529. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +48 -13
  530. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +2 -2
  531. package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -11
  532. package/dist/knowledge/skills/application-database-migrations/references/postgresql-supported-surfaces.md +64 -0
  533. package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +13 -11
  534. package/dist/knowledge/skills/application-roles-authoring/SKILL.md +28 -3
  535. package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +18 -1
  536. package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +22 -1
  537. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +46 -2
  538. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-assigned-rows-declaration-api.md +5 -3
  539. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-organization-identity-declaration-api.md +247 -0
  540. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-own-rows-declaration-api.md +12 -5
  541. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +6 -0
  542. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +31 -2
  543. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +51 -14
  544. package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +4 -1
  545. package/dist/knowledge/skills/backend-custom-operation/references/declared-refusal-codes.md +95 -0
  546. package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +2 -2
  547. package/dist/knowledge/skills/backend-custom-operation/references/framework-core-write-precondition-api.md +73 -0
  548. package/dist/knowledge/skills/backend-custom-operation/references/framework-error-handling-api.md +5 -0
  549. package/dist/knowledge/skills/backend-custom-operation/references/framework-external-effect-reservation-api.md +276 -0
  550. package/dist/knowledge/skills/backend-custom-operation/references/framework-hook-transaction-posture-api.md +90 -0
  551. package/dist/knowledge/skills/blueprint-authoring/SKILL.md +4 -2
  552. package/dist/knowledge/skills/brand-name-screening/SKILL.md +13 -2
  553. package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +30 -3
  554. package/dist/knowledge/skills/chat-agent-conversations/SKILL.md +3 -0
  555. package/dist/knowledge/skills/chat-agent-conversations/references/framework-chat-conversations-api.md +13 -1
  556. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +45 -4
  557. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +17 -7
  558. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +859 -0
  559. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +6 -0
  560. package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +2 -0
  561. package/dist/knowledge/skills/config-app-shell/SKILL.md +5 -1
  562. package/dist/knowledge/skills/config-app-shell/references/framework-command-menu-omnibox-api.md +3 -3
  563. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +4 -0
  564. package/dist/knowledge/skills/config-design-system/SKILL.md +1 -1
  565. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +8 -7
  566. package/dist/knowledge/skills/config-design-system/references/framework-theme-composition-api.md +44 -1
  567. package/dist/knowledge/skills/config-navigation/SKILL.md +2 -0
  568. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +5 -0
  569. package/dist/knowledge/skills/config-navigation/references/one-entry-per-concept.md +101 -0
  570. package/dist/knowledge/skills/config-saas/SKILL.md +2 -2
  571. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +40 -3
  572. package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +20 -1
  573. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +75 -11
  574. package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +21 -19
  575. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +26 -9
  576. package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +240 -9
  577. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +16 -2
  578. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +116 -16
  579. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +20 -18
  580. package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +1 -1
  581. package/dist/knowledge/skills/config-saas-backend/SKILL.md +11 -1
  582. package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +5 -1
  583. package/dist/knowledge/skills/config-saas-backend/references/framework-declared-type-renames-api.md +261 -0
  584. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +20 -0
  585. package/dist/knowledge/skills/config-saas-backend/references/renaming-organization-and-user-types.md +69 -0
  586. package/dist/knowledge/skills/configure-billing/SKILL.md +6 -0
  587. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +28 -4
  588. package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +2 -0
  589. package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +4 -1
  590. package/dist/knowledge/skills/electronic-signature-deliverables/SKILL.md +131 -0
  591. package/dist/knowledge/skills/electronic-signature-deliverables/references/what-makes-a-request-signed.md +78 -0
  592. package/dist/knowledge/skills/email-add-template/SKILL.md +1 -1
  593. package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +11 -8
  594. package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +3 -2
  595. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +31 -9
  596. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +11 -4
  597. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +26 -3
  598. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +13 -3
  599. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +27 -0
  600. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +34 -11
  601. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +8 -5
  602. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-behavior-reports-api.md +13 -9
  603. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +188 -10
  604. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-operation-record-api.md +7 -0
  605. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-suspension-api.md +11 -9
  606. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +21 -0
  607. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +3 -3
  608. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-realtime-catalog.md +7 -1
  609. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +447 -8
  610. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +30 -1
  611. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-model-spend-limits-api.md +36 -15
  612. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +8 -0
  613. package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +13 -3
  614. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-flow-model-api.md +21 -2
  615. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +2 -1
  616. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +13 -3
  617. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +33 -1
  618. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +5 -3
  619. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +1 -1
  620. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +6 -5
  621. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +50 -14
  622. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +1 -1
  623. package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +39 -0
  624. package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +39 -0
  625. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +31 -2
  626. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +39 -0
  627. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-translation-glossary-api.md +87 -0
  628. package/dist/knowledge/skills/inbound-channels/SKILL.md +31 -9
  629. package/dist/knowledge/skills/inbound-channels/references/email-channel.md +16 -4
  630. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +169 -23
  631. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +38 -1
  632. package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +43 -4
  633. package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +15 -3
  634. package/dist/knowledge/skills/inbound-channels/references/sms-channel.md +93 -0
  635. package/dist/knowledge/skills/infra-environment-config/SKILL.md +149 -77
  636. package/dist/knowledge/skills/infra-environment-config/references/framework-agent-content-guardrails-environment-api.md +67 -0
  637. package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +12 -14
  638. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +133 -8
  639. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +1 -1
  640. package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +89 -10
  641. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-authoring-api.md +1 -1
  642. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-focal-plane-settings-api.md +16 -0
  643. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +72 -0
  644. package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +2 -2
  645. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +12 -9
  646. package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +3 -3
  647. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +2 -2
  648. package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +18 -10
  649. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +7 -7
  650. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +24 -2
  651. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +33 -2
  652. package/dist/knowledge/skills/market-generation-cli/SKILL.md +47 -6
  653. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +61 -8
  654. package/dist/knowledge/skills/model-cost-attribution/SKILL.md +3 -1
  655. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +1 -1
  656. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +107 -42
  657. package/dist/knowledge/skills/module-companion-exports/SKILL.md +1 -0
  658. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +21 -2
  659. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +30 -1
  660. package/dist/knowledge/skills/module-relationships/SKILL.md +92 -91
  661. package/dist/knowledge/skills/organization-relationships/references/framework-organization-relationships-api.md +31 -5
  662. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-grantor-authentication-api.md +2 -2
  663. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-kinds-api.md +34 -0
  664. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-record-separation-api.md +1 -0
  665. package/dist/knowledge/skills/organization-relationships/references/framework-representative-activity-api.md +4 -0
  666. package/dist/knowledge/skills/professional-qualifications/references/framework-operation-approval-requirement-api.md +31 -0
  667. package/dist/knowledge/skills/provider-backend-package/SKILL.md +272 -15
  668. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +4 -5
  669. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-compliance-state-collector-api.md +96 -0
  670. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-configuration-check-api.md +130 -0
  671. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +8 -1
  672. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-inbound-endpoint-api.md +124 -3
  673. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +165 -0
  674. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +6 -0
  675. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-processing-region-api.md +340 -0
  676. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +11 -6
  677. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +2 -0
  678. package/dist/knowledge/skills/provider-frontend-module/SKILL.md +5 -2
  679. package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +1 -1
  680. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +17 -3
  681. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +1035 -19
  682. package/dist/knowledge/skills/resource-add-field/SKILL.md +7 -0
  683. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +322 -15
  684. package/dist/knowledge/skills/resource-add-resource/SKILL.md +9 -5
  685. package/dist/knowledge/skills/resource-add-resource/references/framework-engine-api-reference-categories-api.md +119 -0
  686. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +107 -42
  687. package/dist/knowledge/skills/resource-chat-commands/SKILL.md +2 -1
  688. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +71 -5
  689. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +2 -2
  690. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-approval-api.md +48 -0
  691. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +34 -7
  692. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-bulk-api.md +15 -11
  693. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +66 -27
  694. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +140 -58
  695. package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +28 -2
  696. package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +34 -10
  697. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +5 -4
  698. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +158 -138
  699. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +52 -0
  700. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +205 -19
  701. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +253 -25
  702. package/dist/knowledge/skills/resource-custom-view/SKILL.md +126 -1
  703. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +259 -15
  704. package/dist/knowledge/skills/resource-custom-view/references/framework-backend-refusal-api.md +110 -0
  705. package/dist/knowledge/skills/resource-external-data/SKILL.md +46 -12
  706. package/dist/knowledge/skills/resource-external-data/references/bidirectional-pipelines.md +1 -1
  707. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +15 -8
  708. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +19 -8
  709. package/dist/knowledge/skills/resource-external-data/references/framework-system-of-record-capabilities-api.md +3 -1
  710. package/dist/knowledge/skills/resource-external-data/references/local-test-doubles.md +121 -0
  711. package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +1 -1
  712. package/dist/knowledge/skills/resource-external-data/references/partition-from-the-domain-plan.md +230 -0
  713. package/dist/knowledge/skills/resource-external-data/references/presenting-a-copy-and-a-read-through.md +73 -0
  714. package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +26 -5
  715. package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +76 -6
  716. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +8 -0
  717. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +12 -9
  718. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +11 -2
  719. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +29 -2
  720. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +20 -20
  721. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +18 -2
  722. package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +46 -2
  723. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +84 -1
  724. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +10 -0
  725. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +5 -3
  726. package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +21 -0
  727. package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +14 -2
  728. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +1 -1
  729. package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +4 -1
  730. package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +78 -17
  731. package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +2 -0
  732. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +26 -0
  733. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +46 -46
  734. package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +17 -2
  735. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +36 -24
  736. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +63 -0
  737. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +104 -23
  738. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +123 -0
  739. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -0
  740. package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +72 -0
  741. package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +42 -2
  742. package/dist/knowledge/skills/resource-status-lifecycle/references/framework-operation-condition-parameters-api.md +67 -0
  743. package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +16 -12
  744. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +66 -3
  745. package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +89 -10
  746. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +11 -0
  747. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +263 -17
  748. package/dist/knowledge/skills/resource-ui-behavior/references/framework-record-page-parts-api.md +155 -0
  749. package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +83 -16
  750. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +44 -10
  751. package/dist/knowledge/skills/resource-ui-behavior/references/framework-section-stages-api.md +102 -0
  752. package/dist/knowledge/skills/resource-ui-behavior/references/record-page-anatomy.md +9 -2
  753. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +33 -2
  754. package/dist/knowledge/skills/resource-ui-behavior/references/visual-quality-rubric.md +19 -2
  755. package/dist/knowledge/skills/resource-ui-behavior/references/workflow-record-page.md +264 -0
  756. package/dist/knowledge/skills/seeding-authoring/SKILL.md +24 -4
  757. package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +12 -0
  758. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +7 -6
  759. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +6 -0
  760. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +42 -0
  761. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +6 -9
  762. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +1 -0
  763. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +21 -2
  764. package/dist/knowledge/skills/spec-resource-update/SKILL.md +26 -0
  765. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +121 -75
  766. package/dist/knowledge/skills/spec-resource-update/references/workflow-record-page-specification.md +237 -0
  767. package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +100 -71
  768. package/dist/knowledge/skills/subject-data-export/SKILL.md +176 -0
  769. package/dist/knowledge/skills/subject-data-export/references/file-content-exclusions.md +15 -0
  770. package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-api.md +142 -0
  771. package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-archive-api.md +33 -0
  772. package/dist/knowledge/skills/views-app-level/SKILL.md +3 -1
  773. package/dist/knowledge/skills/views-app-level/references/workflow-home.md +373 -0
  774. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +36 -5
  775. package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +9 -5
  776. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +4 -0
  777. package/dist/knowledge/skills/views-composite-authoring/references/framework-chart-dashboard-api.md +371 -0
  778. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +40 -0
  779. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +8 -6
  780. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +70 -59
  781. package/dist/knowledge/skills/website-building-blocks/SKILL.md +1 -1
  782. package/dist/knowledge/skills/website-building-blocks/references/framework-website-demo-examples.md +3 -3
  783. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +4 -2
  784. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +3 -1
  785. package/dist/knowledge/skills/website-label-pack/SKILL.md +20 -5
  786. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +6 -3
  787. package/dist/knowledge/skills/website-section-comparison/SKILL.md +2 -2
  788. package/dist/knowledge/skills/website-section-contact/SKILL.md +1 -1
  789. package/dist/knowledge/skills/website-section-cta/SKILL.md +1 -1
  790. package/dist/knowledge/skills/website-section-faq/SKILL.md +1 -1
  791. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +1 -1
  792. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +1 -1
  793. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +1 -1
  794. package/dist/knowledge/skills/website-section-hero/SKILL.md +1 -1
  795. package/dist/knowledge/skills/website-section-how-it-works/SKILL.md +1 -1
  796. package/dist/knowledge/skills/website-section-integrations/SKILL.md +3 -3
  797. package/dist/knowledge/skills/website-section-latest-posts/SKILL.md +1 -1
  798. package/dist/knowledge/skills/website-section-pricing/SKILL.md +142 -98
  799. package/dist/knowledge/skills/website-section-pricing/examples/pricing-offers.example.md +178 -66
  800. package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +3 -1
  801. package/dist/knowledge/skills/website-section-problem/SKILL.md +3 -3
  802. package/dist/knowledge/skills/website-section-product-showcase/SKILL.md +1 -1
  803. package/dist/knowledge/skills/website-section-roadmap/SKILL.md +4 -4
  804. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +1 -1
  805. package/dist/knowledge/skills/website-section-solution-paths/SKILL.md +2 -2
  806. package/dist/knowledge/skills/website-section-stats/SKILL.md +3 -3
  807. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +3 -2
  808. package/dist/knowledge/skills/worker-authoring/SKILL.md +4 -2
  809. package/dist/knowledge/topic-index.json +2422 -723
  810. package/dist/tsconfig.build.tsbuildinfo +1 -1
  811. package/package.json +6 -6
  812. package/dist/tsconfig.tsbuildinfo +0 -1
@@ -21,6 +21,9 @@
21
21
  {
22
22
  "family": "vision-brief"
23
23
  },
24
+ {
25
+ "family": "compliance-posture"
26
+ },
24
27
  {
25
28
  "family": "domain-plan"
26
29
  },
@@ -37,9 +40,10 @@
37
40
  ],
38
41
  "stepOutputs": [],
39
42
  "method": {
40
- "guidance": "# Governed-document facts — derivation method\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What you produce\n\nOne `document-facts` file for the application: a list of **facts**, each a plain statement about how\nthis application actually behaves. Not prose for a notice — the raw material a notice is later drafted\nfrom, and the thing a drafted clause is checked against.\n\nA fact is the answer to a question a reader of a legal document would want settled:\n\n- what categories of personal data does the application hold, and where do they come from;\n- what does it do with them, and for how long does it keep them;\n- who else sees them — providers, processors, other tenants;\n- what rights does it actually honour, and through which mechanism;\n- who operates the service, and how is it contacted.\n\n## The rule that governs everything here\n\n**Every fact you write must be supported by something the application has already accepted** — and the\nstrongest support is not prose about the application, it is **the application's own code**.\n\nRead in this order:\n\n1. **The resource declarations**, which are already in this brief, under *\"The application's\n compliance-relevant resource declarations (read from its CODE)\"*. Per resource:\n `retentionPolicy.mode` (what erasure does to a row), `dataSubjectPolicy.kind` (whose login session\n an erasure ends), `systemAccessPolicy.exportSubject` (whether an Art. 15 / Art. 20 export can answer\n for them) and `seeRetained` (the audited path to retained data). These are DECLARATIONS, already\n written down and enforced at runtime. They are the best evidence a governed document can rest on,\n and they need no interpretation — only phrasing.\n\n **Use them.** A fact about a mechanism — what is kept, what is scrubbed, what can be exported — that\n does not correspond to a declaration in that section is not derived, it is recalled, and this\n playbook's whole reason for existing is the difference.\n2. **The compliance constraints on the vision**, which tell you which facts a reader will need.\n3. **The domain plan and requirements**, for what the product is FOR — purpose, not mechanism.\n\nThe split between 1 and 3 is the point. A specification says what the application is meant to do; a\nresource configuration says what it will actually do to a row tomorrow morning. Where they disagree,\nthe configuration is the fact.\n\nThat section reports engine-declared and application-declared coverage **separately**, and you should\nkeep them apart in your facts too: the two have different owners, so they have different remedies. An\napplication's authors cannot close an engine gap, and the engine's maintainers cannot close theirs.\n\nDo not assume the engine half is the settled half. Read the counts. On the first real application to\nbe measured, the engine declared an erasure treatment on **two of eighty-five** resources — the user\naccount and its self-view — and nothing on credentials, profiles, audit logs, files or membership.\nWhatever the numbers say in your own brief, they are the fact; a sentence crediting the framework with\ndeclarations it has not made is exactly as false as one crediting the application.\n\n## COVER THE WHOLE SET — this is the half a first attempt gets wrong\n\nThe facts you declare here are the only thing a later document can state as established. A concern you\nsay nothing about does not become a cautious sentence in the notice; it becomes a clause reading *\"this\nhas not yet been established\"*, in a document about somebody's personal data, when the application had\nalready established it.\n\nMeasured on the first real application (wonder-crm, 2026-08-29): this pass produced **three** facts, and\nthe notice drafted from them marked **ten of thirteen** concerns incomplete — including subject rights,\nwhich every one of that application's resources declares, and analytics, which it does not enable. Both\nwere answerable from the brief in front of it. That is the failure mode to avoid, and it is not caution:\na notice that understates what an application does is as wrong as one that overstates it.\n\nWork through this list and declare a fact for each one you can answer:\n\n| what a document will need | where the answer is |\n|---|---|\n| what personal data is held, and in which records | the resource declarations + the domain plan |\n| what erasure does to each record | `retentionPolicy.mode` per resource |\n| how long records are kept | the RETENTION SCHEDULE in your brief — four classes, each declared or UNDECIDED |\n| whether a subject-access or portability export can answer for a record | `systemAccessPolicy.exportSubject` per resource |\n| whether retained data stays reachable, and audited | `systemAccessPolicy.seeRetained` per resource |\n| who else can see the data inside the application | the domain model — roles, membership, sharing |\n| which third parties receive data, WHO they are and WHERE they process | the PROCESSOR REGISTER section — declared entries, plus the providers it lists UNDECLARED |\n| whether the application makes automated decisions or uses AI | the `## Automated decisions and AI` section — per AI capability of the contracted service, then `Agents declaring their use`, `OUTSTANDING agents` (or `Agents: NOT READ`) and the regulatory reading: the declared use, its domain and class, its human review (derived from approval gates where every write is gated) |\n| what each agent's model provider receives, and what is screened or moderated | the same section's `Content guardrails each agent DECLARES` list — the personal-data treatment, prompt-injection screening and output moderation each agent declares |\n| what analytics or tracking runs, and what is stored in a browser | the declared capabilities + the CLIENT STORAGE section (framework entries, then per surface) |\n| what consent the application asks for | the declared capabilities + the domain plan |\n| how organizations are separated from each other | the domain model and the tenancy declarations |\n\n## RECORD THE GAPS AS FACTS TOO — nothing downstream can see this brief\n\nThe sections above are yours alone. The pass that drafts the document reads the `document-facts` FILE\nand nothing else — it never sees the resource declarations, the retention schedule, the processor\nregister, the AI uses and agents or the client-storage inventory. **A gap you notice and do not write down is a\ngap that disappears**, and the document then states the half that was answered as though it were the\nwhole.\n\nSo when a section names something as `UNDECIDED`, `UNDECLARED`, `OUTSTANDING` or `UNINVENTORIED`,\ndeclare a fact recording it, naming what is missing:\n\n- *\"No retention period is declared for any of the four data classes; all four require an operator\n decision.\"*\n- *\"The `app` frontend surface's own client storage has not been catalogued.\"*\n\nThis is the failure mode to avoid, measured on a real run: the facts stated that no consent-gated\nbrowser storage is configured — true — and said nothing about the frontend surface nobody had\ninventoried. A reader of the notice would take the first as the whole answer.\n\nA gap recorded as a fact is `KNOWN`: the thing that is known IS the gap. Do not use `NOT_APPLICABLE`\nfor it — that says the question does not arise, and it does.\n\n**An UNDECIDED retention period is an OPERATOR's decision, not a framework gap.** The application can\ndeclare a period for each of the four data classes and has not for some of them. State which classes\nare declared, with their periods and the reasons given, and state plainly which are still undecided —\nthe remedy is an operator deciding, not the framework growing a mechanism. Never write a period the\napplication has not declared, and never soften an absent one into \"as long as necessary\": that is a\ncommitment nobody made and nothing enforces.\n\n**Agents are AI uses one by one.** Declare a fact per agent of the contracted service — or one fact listing\nthem, each by ref — stating its declared use, whether it decides anything about a person and who reviews it,\nand what its model is sent in place of personal data. An agent listed OUTSTANDING, a guardrail \"not declared\"\nand a field NOT READ are gaps: record each as such, never as \"the agent decides nothing\" or \"nothing is\nsent\". State a guardrail as what the agent DECLARES: an organization can tighten it at run time, and a fact\nmust not claim the tightening happened.\n\n**An absent capability is a fact, not a silence.** If no analytics provider is configured, that is\n`KNOWN`: *\"no external analytics provider is configured\"*. If no AI capability is declared, say so. These\nare the answers that let a notice state something true instead of confessing ignorance about a decision\nthe application already made — and the composition section in your brief lists them exactly.\n\n**Not built yet is not \"none\".** When your brief says NOT BUILT YET, the build has not yet produced the\napplication's own resources, and their absence is a stage of the build, not a decision. Write that the\napplication's own data is not yet established. Never write \"zero resources\", \"holds no personal data\" or\n\"declares nothing\" for data that does not exist yet. These facts are dated by the code they were read\nfrom: once the build commits its resources, configuration or roles, they go stale and are derived again.\nAn earlier run wrote \"zero personal-data resources\" and \"no billing\" an hour before the build declared\nboth, and those sentences stayed in the file.\n\n**Declare mechanism facts per RESOURCE where the resources differ.** \"All eight application resources\ndeclare a subject-export mode\" is a usable fact; \"the application supports exports\" is not, because a\nreader cannot tell which records it covers.\n\nYou are **not** deciding anything. A legal basis, a controller-versus-processor role, a governing law,\na liability position and a retention *duration the product has not chosen* are all decisions, and none\nof them is yours. If a fact needs a human to decide it, **leave it out**. Do not write a plausible\nplaceholder, and do not soften a decision into a fact by hedging the wording.\n\nLeaving it out is not a failure — it is the designed behaviour, and it does **not** block anything\ndownstream. A document clause that would have rested on a fact you did not declare is still written:\nit is marked as not yet established, names what it needs and who can supply it, and the document is\nproduced. So an absence costs the reader a precise statement of a gap, which is useful. A guessed fact\ncosts them a published false statement about somebody's data, which is not.\n\n## The shape of a declaration — get this right or the whole file is rejected\n\nEach declaration carries three slugs, all lowercase kebab-case (`retention-treatment-per-resource`),\nand **every one of them must be UNIQUE across the file**:\n\n- `slug` — names THIS declaration. Two declarations sharing a `slug` are rejected, and this is the\n single most common way a good fact set fails: a drafter answering several facts about retention\n gives them all `slug: \"retention\"`. Make each one describe its own fact.\n- `factSlug` — names the FACT being answered. One governance scope carries one answer per fact, so two\n declarations may not share a `factSlug` either. If you want to say two things about retention, they\n are two facts (`retention-treatment-per-resource`, `retention-duration`), not one fact twice.\n- `sensitivitySlug` — how sensitive the fact itself is (`public`, `internal-governance`). This one MAY\n repeat; it is a classification, not an identity.\n\nA rejection naming `declarations.N.slug` is almost always a COLLISION rather than a bad character:\nre-read your list for two entries sharing a name.\n\n## KNOWN and NOT_APPLICABLE are different answers — and both are different from absence\n\nThree states, and confusing them is the most common way this pass goes wrong.\n\n| state | means | how you write it |\n|---|---|---|\n| `KNOWN` | the application does this, and here is what it does | `resolution: KNOWN` with `value` |\n| `NOT_APPLICABLE` | this was considered and it genuinely does not apply | `resolution: NOT_APPLICABLE` with `reason` |\n| absent | nobody has established this yet | omit the declaration entirely |\n\n`NOT_APPLICABLE` is a real, useful answer — \"this application performs no international transfers\"\ntells a reviewer something. It is **not** a way to dispose of a fact you could not find. If you do not\nknow, the honest output is absence.\n\nA `KNOWN` fact must carry an actual value. An empty string, a blank one or an empty object is rejected\nby the validator: a fact that exists and says nothing is worse than a missing one, because a document\ncan cite it and learn nothing.\n\n## Read the compliance constraints first\n\n`top_down.compliance-posture` records each applicable regime as a `compliance`-kind constraint on the\nvision. Those constraints tell you which facts matter. A GDPR constraint means a reader will need data\ncategories, purposes, retention, recipients, transfers and rights mechanisms. A data-residency\nconstraint means where data lives is a fact worth stating.\n\nDerive the fact SET from the regimes, then answer each one from the application's own truth — the\nconfigurations first. Where the regime implies a fact the application has not settled, that is an\nabsence: record nothing, and let the document state the gap in place.\n\n## Who the privacy notice addresses\n\nThe facts brief says so when it matters. On an application one organization owns (an internal tool),\nthe privacy notice is addressed to that organization's STAFF, not to the public, and the brief carries\na paragraph saying so. Word the facts you declare for that reader: processing purposes and data\ncategories in terms of what the application records about staff as they work in it. The lawful bases\nand the recipients stay computed from the operator's declarations, as below; the audience never makes\nthem yours to declare. Where the brief says nothing about the audience, the notice is the public one.\n\n## Scope: one operator, deliberately\n\nEvery fact you write is attributed to one application-operator governance scope. The family can carry\nfacts for a tenant organization or a shared-responsibility boundary too, but choosing a different\nsubject per fact is deciding **shared-responsibility attribution**, which is exactly the thing that\nmust never be guessed or flattened. One operator scope is the honest output of a derivation; a second\nsubject is a human's edit.\n\nThe `operatorSlug` you supply is an operator identity, **not** a legal-entity assertion. It names who\nruns the service, not which company is on the contract — that is a decision, and it is absent until a\nhuman makes it.\n\n## What you never write\n\n- A legal basis, a lawful-processing justification, or a controller/processor role.\n- A retention period the product has not chosen, or one you inferred from a default.\n- A named human, a reviewer, a qualification or an independence statement. Every fact you produce\n carries `APPLICATION_SPECIFICATION` authority — the accepted specification is the authority, and it\n is the only one a derivation can honestly claim, and since 2026-09-03 the only one the family's TYPE\n accepts. A declaration carrying any other authority is refused before it reaches a file.\n- A decision instant. You have no clock, and the honest instant for a human decision is the commit that\n records it.\n- A security claim beyond what the application's configuration actually shows.\n- A fact about a provider, region or capability the application has not configured.\n\n## The file you write is REGENERATED WHOLE, and a second family holds what you must not touch\n\nYour output replaces `document-facts` entirely on every run. That is why the facts only a human may\nestablish — a creator decision, a qualified review — live in a SEPARATE family,\n`document-facts-authored`, which you neither read nor write. Before the two were split they shared one\nfile, and a producer run silently deleted the human half.\n\nSo an absent fact is never something for you to fill in \"because nobody else will\". The brief already\nnames which facts are yours; anything it withholds has a home you cannot reach, and leaving it absent\nis the correct outcome rather than a gap you are working around.\n\n## Some facts are COMPUTED, and you do not declare them\n\nA few facts are not written by anyone. The runtime computes them from the application's own typed\ndeclarations every time the facts are read:\n\n- `controller-and-contact` is computed from `operatorComplianceIdentity`;\n- `recipients-and-processors` is computed from the processor register and the providers' deployment\n choices;\n- `lawful-bases` is computed from `operatorComplianceIdentity.lawfulBases`;\n- `retention-rules` is computed from the `dataRetention` schedule and each resource's erasure treatment;\n- `international-transfers` is computed from each register entry's `transferDetermination`;\n- `rights-and-complaint-route` is computed from the operating jurisdictions, the lawful bases, the\n privacy contact, the identity-verification procedure and the role allocations;\n- `retention-enforcement` is computed from the retention-enforcement records the evidence plane\n collected;\n- `system-of-record-sources` is computed from the resources bound to, or copied from, a declared\n system of record, and the purposes their bindings link;\n- `ai-use-inventory` is computed from the AI-use declarations — each capability's `aiUsePosture` and\n each agent's own `aiUse` — scoped to the contracted service and joined to the providers serving each\n use and the processor register;\n- `ai-content-guardrails` is computed from the agent-operation records and guardrail audit events the\n evidence plane collected: per agent, the guardrails it declares, the recorded calls each was active\n on and what each judged.\n\nThe AI facts replace the AI half of the service terms' AI question. What is left of\n`ai-features-and-content-use` (whether customer content trains or improves a model) is a decision a\nperson records, so it is not yours to declare either.\n\nThis list is a convenience. The brief's \"do not declare\" heading is the authority.\n\nThe brief lists them under a separate \"do not declare\" heading. Declaring one is refused at\ngeneration, and a copy in the file is refused by the family's validator.\n\nThe reason is drift. Your answer would be a paraphrase of a declaration that already exists, and it\nwould go stale the day that declaration changes. If the declaration a computed fact reads is missing,\nthe fact stays absent, and the documents mark it as owed. Leave that gap alone. Do not state a\ncontroller, a recipient, a basis, a period, a transfer or a right in prose to fill it: say what is missing in a fact you do own, or leave it to\nthe document's gap marking.\n\n## A judge reads your facts against what you were given\n\nAfter the file lands, an advisory judge reads every declaration beside the same evidence you had: the\ninput families, the application's compliance-relevant declarations and the computed facts. It reports\ntwo kinds of finding. A **gap** is a claim a governed document would publish as true that nothing\nestablishes: a recipient, a transfer, a retention period, a lawful basis or an AI use that no\ndeclaration names, or an undeclared matter stated as settled. A **concern** is wording drift a reader\nwould not act on differently.\n\nThe judge refuses nothing, and a finding does not undo your file. It is written so that an unsupported\nclaim is named before a document cites it. Write each fact so that its source is obvious from the\nwords.\n\n## Refs are stamped for you\n\nSupply slugs. The runtime turns each into its namespaced ref, attaches the governance scope and\nauthority, assigns versions and sorts the declarations. Do not author a ref, a version or an ordering;\na contract that asked you to would be asking you to fail on form rather than on substance.\n\n(This paragraph listed `retention-rules`, `data-categories-and-sources` and\n`recipients-and-processors` as examples. All three are required fact names, and naming three of eight\nas \"examples\" invited a drafter to treat them as a style to imitate rather than a set to use. The\nauthoritative list now arrives in the brief.)\n\n**For a concern a governed document requires, the slug is NOT yours to choose.** The brief you were\ngiven lists the exact `factSlug` for each one, taken from the engine catalog. Use it verbatim.\n\nThis is not a style preference. A clause cites a fact BY REF, the ref is stamped from your slug, and a\nfact answering the right question under a different name is a fact the document cannot cite — it reads\nas missing while your answer sits in the file. Measured on a real run: twenty facts declared, zero of\nthe eight a privacy notice requires, because the names were semantically adjacent and lexically\ndisjoint (`retention-period-schedule-status` for `retention-rules`).\n\nFor anything the catalog does NOT name, the slug is yours: use a stable, descriptive one that reads as\nthe question it answers. An application legitimately declares facts no document requires.\n\n## Verification\n\nBefore you finish, check each declaration against these:\n\n- [ ] every `KNOWN` value states something a reader could act on, and is traceable to accepted truth;\n- [ ] no declaration encodes a decision (legal basis, role, governing law, liability, chosen retention);\n- [ ] every `NOT_APPLICABLE` reason says why it does not apply, not that it could not be found;\n- [ ] a fact you could not establish is ABSENT, not guessed and not marked not-applicable;\n- [ ] the fact set is derived from the vision's compliance constraints, not from a generic SaaS template;\n- [ ] no `factSlug` is declared twice.\n\n## Approval\n\nThe derived fact set is presented to the creator before it becomes the committed `document-facts`\nfamily. Show it back as plain statements grouped by the question each answers, and name what you left\nout and why — the absences are the part a human most needs to see, because each one is a decision\nsomebody still owes.\n\n## Runtime context\n\nEverything above is already in your brief: `vision-brief` / `domain-plan` / `requirements` render as\ninput sections under \"# Accepted application truth\", and the application's live resource\nDECLARATIONS (retention mode, data-subject kind, subject export, retained see-through) arrive as\nthe declared `compliance_primary_facts` context section of your brief. Derive facts from those sections; there is no command to\nrun in this mode.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n\n## External sign-in assurance\n\nDerive `document-fact:external-sign-in-assurance` from the brief's declared authentication policy, including organization restrictions. Do not infer an active enterprise connection from an enabled method. Describe enterprise OAuth2/OIDC responsibility delegation separately from observed MFA. For social login, name the configured warning/strict treatment and provider evidence limitations. An unreadable configuration remains unresolved, never “no external login”. Feed this fact into the service-terms account-duties clause; liability conclusions still require qualified review.\n",
43
+ "guidance": "# Governed-document facts — derivation method\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What you produce\n\nOne `document-facts` file for the application: a list of **facts**, each a plain statement about how\nthis application actually behaves. Not prose for a notice — the raw material a notice is later drafted\nfrom, and the thing a drafted clause is checked against.\n\nA fact is the answer to a question a reader of a legal document would want settled:\n\n- what categories of personal data does the application hold, and where do they come from;\n- what does it do with them, and for how long does it keep them;\n- who else sees them — providers, processors, other tenants;\n- what rights does it actually honour, and through which mechanism;\n- who operates the service, and how is it contacted.\n\n## The rule that governs everything here\n\n**Every fact you write must be supported by something the application has already accepted** — and the\nstrongest support is not prose about the application, it is **the application's own code**.\n\nRead in this order:\n\n1. **The resource declarations**, which are already in this brief, under *\"The application's\n compliance-relevant resource declarations (read from its CODE)\"*. Per resource:\n `retentionPolicy.mode` (what erasure does to a row), `dataSubjectPolicy.kind` (whose login session\n an erasure ends), `systemAccessPolicy.exportSubject` (whether an Art. 15 / Art. 20 export can answer\n for them) and `seeRetained` (the audited path to retained data). These are DECLARATIONS, already\n written down and enforced at runtime. They are the best evidence a governed document can rest on,\n and they need no interpretation — only phrasing.\n\n **Use them.** A fact about a mechanism — what is kept, what is scrubbed, what can be exported — that\n does not correspond to a declaration in that section is not derived, it is recalled, and this\n playbook's whole reason for existing is the difference.\n2. **The compliance posture**, and the creator's compliance constraints on the vision, which tell you\n which facts a reader will need.\n3. **The domain plan and requirements**, for what the product is FOR — purpose, not mechanism.\n\nThe split between 1 and 3 is the point. A specification says what the application is meant to do; a\nresource configuration says what it will actually do to a row tomorrow morning. Where they disagree,\nthe configuration is the fact.\n\nThat section reports engine-declared and application-declared coverage **separately**, and you should\nkeep them apart in your facts too: the two have different owners, so they have different remedies. An\napplication's authors cannot close an engine gap, and the engine's maintainers cannot close theirs.\n\nDo not assume the engine half is the settled half. Read the counts. On the first real application to\nbe measured, the engine declared an erasure treatment on **two of eighty-five** resources — the user\naccount and its self-view — and nothing on credentials, profiles, audit logs, files or membership.\nWhatever the numbers say in your own brief, they are the fact; a sentence crediting the framework with\ndeclarations it has not made is exactly as false as one crediting the application.\n\n## COVER THE WHOLE SET — this is the half a first attempt gets wrong\n\nThe facts you declare here are the only thing a later document can state as established. A concern you\nsay nothing about does not become a cautious sentence in the notice; it becomes a clause reading *\"this\nhas not yet been established\"*, in a document about somebody's personal data, when the application had\nalready established it.\n\nMeasured on the first real application (wonder-crm, 2026-08-29): this pass produced **three** facts, and\nthe notice drafted from them marked **ten of thirteen** concerns incomplete — including subject rights,\nwhich every one of that application's resources declares, and analytics, which it does not enable. Both\nwere answerable from the brief in front of it. That is the failure mode to avoid, and it is not caution:\na notice that understates what an application does is as wrong as one that overstates it.\n\nWork through this list and declare a fact for each one you can answer:\n\n| what a document will need | where the answer is |\n|---|---|\n| what personal data is held, and in which records | the resource declarations + the domain plan |\n| what erasure does to each record | `retentionPolicy.mode` per resource |\n| how long records are kept | the RETENTION SCHEDULE in your brief — four classes, each declared or UNDECIDED |\n| whether a subject-access or portability export can answer for a record | `systemAccessPolicy.exportSubject` per resource |\n| whether retained data stays reachable, and audited | `systemAccessPolicy.seeRetained` per resource |\n| who else can see the data inside the application | the domain model — roles, membership, sharing |\n| which third parties receive data, WHO they are and WHERE they process | the PROCESSOR REGISTER section — declared entries, plus the providers it lists UNDECLARED |\n| whether the application makes automated decisions or uses AI | the `## Automated decisions and AI` section — per AI capability of the contracted service, then `Agents declaring their use`, `OUTSTANDING agents` (or `Agents: NOT READ`) and the regulatory reading: the declared use, its domain and class, its human review (derived from approval gates where every write is gated) |\n| what each agent's model provider receives, and what is screened or moderated | the same section's `Content guardrails each agent DECLARES` list — the personal-data treatment, prompt-injection screening and output moderation each agent declares |\n| what analytics or tracking runs, and what is stored in a browser | the declared capabilities + the CLIENT STORAGE section (framework entries, then per surface) |\n| what consent the application asks for | the declared capabilities + the domain plan |\n| how organizations are separated from each other | the domain model and the tenancy declarations |\n\n## RECORD THE GAPS AS FACTS TOO — nothing downstream can see this brief\n\nThe sections above are yours alone. The pass that drafts the document reads the `document-facts` FILE\nand nothing else — it never sees the resource declarations, the retention schedule, the processor\nregister, the AI uses and agents or the client-storage inventory. **A gap you notice and do not write down is a\ngap that disappears**, and the document then states the half that was answered as though it were the\nwhole.\n\nSo when a section names something as `UNDECIDED`, `UNDECLARED`, `OUTSTANDING` or `UNINVENTORIED`,\ndeclare a fact recording it, naming what is missing:\n\n- *\"No retention period is declared for any of the four data classes; all four require an operator\n decision.\"*\n- *\"The `app` frontend surface's own client storage has not been catalogued.\"*\n\nThis is the failure mode to avoid, measured on a real run: the facts stated that no consent-gated\nbrowser storage is configured — true — and said nothing about the frontend surface nobody had\ninventoried. A reader of the notice would take the first as the whole answer.\n\nA gap recorded as a fact is `KNOWN`: the thing that is known IS the gap. Do not use `NOT_APPLICABLE`\nfor it — that says the question does not arise, and it does.\n\n**An UNDECIDED retention period is an OPERATOR's decision, not a framework gap.** The application can\ndeclare a period for each of the four data classes and has not for some of them. State which classes\nare declared, with their periods and the reasons given, and state plainly which are still undecided —\nthe remedy is an operator deciding, not the framework growing a mechanism. Never write a period the\napplication has not declared, and never soften an absent one into \"as long as necessary\": that is a\ncommitment nobody made and nothing enforces.\n\n**Agents are AI uses one by one.** Declare a fact per agent of the contracted service — or one fact listing\nthem, each by ref — stating its declared use, whether it decides anything about a person and who reviews it,\nand what its model is sent in place of personal data. An agent listed OUTSTANDING, a guardrail \"not declared\"\nand a field NOT READ are gaps: record each as such, never as \"the agent decides nothing\" or \"nothing is\nsent\". State a guardrail as what the agent DECLARES: an organization can tighten it at run time, and a fact\nmust not claim the tightening happened.\n\n**An absent capability is a fact, not a silence.** If no analytics provider is configured, that is\n`KNOWN`: *\"no external analytics provider is configured\"*. If no AI capability is declared, say so. These\nare the answers that let a notice state something true instead of confessing ignorance about a decision\nthe application already made — and the composition section in your brief lists them exactly.\n\n**Not built yet is not \"none\".** When your brief says NOT BUILT YET, the build has not yet produced the\napplication's own resources, and their absence is a stage of the build, not a decision. Write that the\napplication's own data is not yet established. Never write \"zero resources\", \"holds no personal data\" or\n\"declares nothing\" for data that does not exist yet. These facts are dated by the code they were read\nfrom: once the build commits its resources, configuration or roles, they go stale and are derived again.\nAn earlier run wrote \"zero personal-data resources\" and \"no billing\" an hour before the build declared\nboth, and those sentences stayed in the file.\n\n**Declare mechanism facts per RESOURCE where the resources differ.** \"All eight application resources\ndeclare a subject-export mode\" is a usable fact; \"the application supports exports\" is not, because a\nreader cannot tell which records it covers.\n\nYou are **not** deciding anything. A legal basis, a controller-versus-processor role, a governing law,\na liability position and a retention *duration the product has not chosen* are all decisions, and none\nof them is yours. If a fact needs a human to decide it, **leave it out**. Do not write a plausible\nplaceholder, and do not soften a decision into a fact by hedging the wording.\n\nLeaving it out is not a failure — it is the designed behaviour, and it does **not** block anything\ndownstream. A document clause that would have rested on a fact you did not declare is still written:\nit is marked as not yet established, names what it needs and who can supply it, and the document is\nproduced. So an absence costs the reader a precise statement of a gap, which is useful. A guessed fact\ncosts them a published false statement about somebody's data, which is not.\n\n## The shape of a declaration — get this right or the whole file is rejected\n\nEach declaration carries three slugs, all lowercase kebab-case (`retention-treatment-per-resource`),\nand **every one of them must be UNIQUE across the file**:\n\n- `slug` — names THIS declaration. Two declarations sharing a `slug` are rejected, and this is the\n single most common way a good fact set fails: a drafter answering several facts about retention\n gives them all `slug: \"retention\"`. Make each one describe its own fact.\n- `factSlug` — names the FACT being answered. One governance scope carries one answer per fact, so two\n declarations may not share a `factSlug` either. If you want to say two things about retention, they\n are two facts (`retention-treatment-per-resource`, `retention-duration`), not one fact twice.\n- `sensitivitySlug` — how sensitive the fact itself is (`public`, `internal-governance`). This one MAY\n repeat; it is a classification, not an identity.\n\nA rejection naming `declarations.N.slug` is almost always a COLLISION rather than a bad character:\nre-read your list for two entries sharing a name.\n\n## KNOWN and NOT_APPLICABLE are different answers — and both are different from absence\n\nThree states, and confusing them is the most common way this pass goes wrong.\n\n| state | means | how you write it |\n|---|---|---|\n| `KNOWN` | the application does this, and here is what it does | `resolution: KNOWN` with `value` |\n| `NOT_APPLICABLE` | this was considered and it genuinely does not apply | `resolution: NOT_APPLICABLE` with `reason` |\n| absent | nobody has established this yet | omit the declaration entirely |\n\n`NOT_APPLICABLE` is a real, useful answer — \"this application performs no international transfers\"\ntells a reviewer something. It is **not** a way to dispose of a fact you could not find. If you do not\nknow, the honest output is absence.\n\nA `KNOWN` fact must carry an actual value. An empty string, a blank one or an empty object is rejected\nby the validator: a fact that exists and says nothing is worse than a missing one, because a document\ncan cite it and learn nothing.\n\n## Read the compliance constraints first\n\n`top_down.compliance-posture` records each applicable regime as a constraint in the `compliance-posture`\nfamily; the vision may also carry `kind: compliance` constraints the creator stated. Those constraints\ntell you which facts matter. A GDPR constraint means a reader will need data\ncategories, purposes, retention, recipients, transfers and rights mechanisms. A data-residency\nconstraint means where data lives is a fact worth stating.\n\nDerive the fact SET from the regimes, then answer each one from the application's own truth — the\nconfigurations first. Where the regime implies a fact the application has not settled, that is an\nabsence: record nothing, and let the document state the gap in place.\n\n## Who the privacy notice addresses\n\nThe facts brief says so when it matters. On an application one organization owns (an internal tool),\nthe privacy notice is addressed to that organization's STAFF, not to the public, and the brief carries\na paragraph saying so. Word the facts you declare for that reader: processing purposes and data\ncategories in terms of what the application records about staff as they work in it. The lawful bases\nand the recipients stay computed from the operator's declarations, as below; the audience never makes\nthem yours to declare. Where the brief says nothing about the audience, the notice is the public one.\n\n## Scope: one operator, deliberately\n\nEvery fact you write is attributed to one application-operator governance scope. The family can carry\nfacts for a tenant organization or a shared-responsibility boundary too, but choosing a different\nsubject per fact is deciding **shared-responsibility attribution**, which is exactly the thing that\nmust never be guessed or flattened. One operator scope is the honest output of a derivation; a second\nsubject is a human's edit.\n\nThe `operatorSlug` you supply is an operator identity, **not** a legal-entity assertion. It names who\nruns the service, not which company is on the contract — that is a decision, and it is absent until a\nhuman makes it.\n\n## What you never write\n\n- A legal basis, a lawful-processing justification, or a controller/processor role.\n- A retention period the product has not chosen, or one you inferred from a default.\n- A named human, a reviewer, a qualification or an independence statement. Every fact you produce\n carries `APPLICATION_SPECIFICATION` authority — the accepted specification is the authority, and it\n is the only one a derivation can honestly claim, and since 2026-09-03 the only one the family's TYPE\n accepts. A declaration carrying any other authority is refused before it reaches a file.\n- A decision instant. You have no clock, and the honest instant for a human decision is the commit that\n records it.\n- A security claim beyond what the application's configuration actually shows.\n- A fact about a provider, region or capability the application has not configured.\n\n## The file you write is REGENERATED WHOLE, and a second family holds what you must not touch\n\nYour output replaces `document-facts` entirely on every run. That is why the facts only a human may\nestablish — a creator decision, a qualified review — live in a SEPARATE family,\n`document-facts-authored`, which you neither read nor write. Before the two were split they shared one\nfile, and a producer run silently deleted the human half.\n\nSo an absent fact is never something for you to fill in \"because nobody else will\". The brief already\nnames which facts are yours; anything it withholds has a home you cannot reach, and leaving it absent\nis the correct outcome rather than a gap you are working around.\n\n## Some facts are COMPUTED, and you do not declare them\n\nA few facts are not written by anyone. The runtime computes them from the application's own typed\ndeclarations every time the facts are read:\n\n- `controller-and-contact` is computed from `operatorComplianceIdentity`;\n- `recipients-and-processors` is computed from the processor register and the providers' deployment\n choices;\n- `lawful-bases` is computed from `operatorComplianceIdentity.lawfulBases`;\n- `retention-rules` is computed from the `dataRetention` schedule and each resource's erasure treatment;\n- `international-transfers` is computed from each register entry's `transferDetermination`;\n- `rights-and-complaint-route` is computed from the operating jurisdictions, the lawful bases, the\n privacy contact, the identity-verification procedure and the role allocations;\n- `retention-enforcement` is computed from the retention-enforcement records the evidence plane\n collected;\n- `system-of-record-sources` is computed from the resources bound to, or copied from, a declared\n system of record, and the purposes their bindings link;\n- `ai-use-inventory` is computed from the AI-use declarations — each capability's `aiUsePosture` and\n each agent's own `aiUse` — scoped to the contracted service and joined to the providers serving each\n use and the processor register;\n- `ai-content-guardrails` is computed from the agent-operation records and guardrail audit events the\n evidence plane collected: per agent, the guardrails it declares, the recorded calls each was active\n on and what each judged.\n\nThe AI facts replace the AI half of the service terms' AI question. What is left of\n`ai-features-and-content-use` (whether customer content trains or improves a model) is a decision a\nperson records, so it is not yours to declare either.\n\nThis list is a convenience. The brief's \"do not declare\" heading is the authority.\n\nThe brief lists them under a separate \"do not declare\" heading. Declaring one is refused at\ngeneration, and a copy in the file is refused by the family's validator.\n\nThe reason is drift. Your answer would be a paraphrase of a declaration that already exists, and it\nwould go stale the day that declaration changes. If the declaration a computed fact reads is missing,\nthe fact stays absent, and the documents mark it as owed. Leave that gap alone. Do not state a\ncontroller, a recipient, a basis, a period, a transfer or a right in prose to fill it: say what is missing in a fact you do own, or leave it to\nthe document's gap marking.\n\n## A judge reads your facts against what you were given\n\nAfter the file lands, an advisory judge reads every declaration beside the same evidence you had: the\ninput families, the application's compliance-relevant declarations and the computed facts. It reports\ntwo kinds of finding. A **gap** is a claim a governed document would publish as true that nothing\nestablishes: a recipient, a transfer, a retention period, a lawful basis or an AI use that no\ndeclaration names, or an undeclared matter stated as settled. A **concern** is wording drift a reader\nwould not act on differently.\n\nThe judge refuses nothing, and a finding does not undo your file. It is written so that an unsupported\nclaim is named before a document cites it. Write each fact so that its source is obvious from the\nwords.\n\n## Refs are stamped for you\n\nSupply slugs. The runtime turns each into its namespaced ref, attaches the governance scope and\nauthority, assigns versions and sorts the declarations. Do not author a ref, a version or an ordering;\na contract that asked you to would be asking you to fail on form rather than on substance.\n\n(This paragraph listed `retention-rules`, `data-categories-and-sources` and\n`recipients-and-processors` as examples. All three are required fact names, and naming three of eight\nas \"examples\" invited a drafter to treat them as a style to imitate rather than a set to use. The\nauthoritative list now arrives in the brief.)\n\n**For a concern a governed document requires, the slug is NOT yours to choose.** The brief you were\ngiven lists the exact `factSlug` for each one, taken from the engine catalog. Use it verbatim.\n\nThis is not a style preference. A clause cites a fact BY REF, the ref is stamped from your slug, and a\nfact answering the right question under a different name is a fact the document cannot cite — it reads\nas missing while your answer sits in the file. Measured on a real run: twenty facts declared, zero of\nthe eight a privacy notice requires, because the names were semantically adjacent and lexically\ndisjoint (`retention-period-schedule-status` for `retention-rules`).\n\nFor anything the catalog does NOT name, the slug is yours: use a stable, descriptive one that reads as\nthe question it answers. An application legitimately declares facts no document requires.\n\n## Verification\n\nBefore you finish, check each declaration against these:\n\n- [ ] every `KNOWN` value states something a reader could act on, and is traceable to accepted truth;\n- [ ] no declaration encodes a decision (legal basis, role, governing law, liability, chosen retention);\n- [ ] every `NOT_APPLICABLE` reason says why it does not apply, not that it could not be found;\n- [ ] a fact you could not establish is ABSENT, not guessed and not marked not-applicable;\n- [ ] the fact set is derived from the compliance posture and the vision's compliance constraints, not from a generic SaaS template;\n- [ ] no `factSlug` is declared twice.\n\n## Approval\n\nThe derived fact set is presented to the creator before it becomes the committed `document-facts`\nfamily. Show it back as plain statements grouped by the question each answers, and name what you left\nout and why — the absences are the part a human most needs to see, because each one is a decision\nsomebody still owes.\n\n## Runtime context\n\nEverything above is already in your brief: `vision-brief` / `domain-plan` / `requirements` render as\ninput sections under \"# Accepted application truth\", and the application's live resource\nDECLARATIONS (retention mode, data-subject kind, subject export, retained see-through) arrive as\nthe declared `compliance_primary_facts` context section of your brief. Derive facts from those sections; there is no command to\nrun in this mode.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n\n## External sign-in assurance\n\nDerive `document-fact:external-sign-in-assurance` from the brief's declared authentication policy, including organization restrictions. Do not infer an active enterprise connection from an enabled method. Describe enterprise OAuth2/OIDC responsibility delegation separately from observed MFA. For social login, name the configured warning/strict treatment and provider evidence limitations. An unreadable configuration remains unresolved, never “no external login”. Feed this fact into the service-terms account-duties clause; liability conclusions still require qualified review.\n",
41
44
  "skillRefs": [],
42
45
  "skillBodyRefs": [],
46
+ "derivedFromAnswers": [],
43
47
  "contextSources": [
44
48
  "compliance_primary_facts",
45
49
  "document_fact_obligations",
@@ -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,
@@ -30,6 +30,7 @@
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":2,"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 — 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
+ {"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":2,"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 — 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}
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}
@@ -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"]}
@@ -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-name-screening","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-name-screening-coverage-and-honesty"],"requirementRef":"application-creation:authority-requirement/brand-name-screening-result","requirementVersion":1,"riskClassRef":"application-creation:risk/brand-name-screening-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-name-screening","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/brand-name-screening-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/brand-name-screening","policyVersion":1},"decisionPointRef":"application-creation:decision-point/brand-name-screening-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/brand-name-screening-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/brand-name-screening","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-proposals-grounded-and-distinct","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/brand-name-screening-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-brand-name-screening-change","triggerRefs":["application-creation:trigger/brand-name-screening-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-brand-name-screening-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty"],"hardFloorRef":"application-creation:hard-floor/brand-name-screening-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-name-screening-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/brand-name-screening","definitionVersion":1,"evaluationProtocol":{"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"]},"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-name-screening","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-name-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-name-proposals-grounded-and-distinct","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-name-proposals-grounded-and-distinct","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-research-and-brand-name-screening-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-name-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-name-screening-coverage-and-honesty","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-research-and-brand-name-screening-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-name-screening","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-name-screening-coverage-and-honesty"],"requirementRef":"application-creation:authority-requirement/brand-name-screening-result","requirementVersion":1,"riskClassRef":"application-creation:risk/brand-name-screening-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-name-screening","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/brand-name-screening-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/brand-name-screening","policyVersion":1},"decisionPointRef":"application-creation:decision-point/brand-name-screening-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/brand-name-screening-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/brand-name-screening","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-proposals-grounded-and-distinct","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/brand-name-screening-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-brand-name-screening-change","triggerRefs":["application-creation:trigger/brand-name-screening-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-brand-name-screening-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty"],"hardFloorRef":"application-creation:hard-floor/brand-name-screening-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-name-screening-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/brand-name-screening","definitionVersion":1,"evaluationProtocol":{"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"]},"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-name-screening","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-name-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-name-proposals-grounded-and-distinct","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-name-proposals-grounded-and-distinct","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-research-and-brand-name-screening-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-name-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-name-screening-coverage-and-honesty","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-research-and-brand-name-screening-candidate"}],"schemaVersion":1}
@@ -40,15 +40,19 @@ every query faithfully.
40
40
  `EU` for the EU trade mark, `WO` for international registrations, ISO country codes otherwise,
41
41
  each with what declared it. Every country the creator names is a jurisdiction even when the
42
42
  research did not search it: an unsearched target is recorded, and reads as not cleared, rather
43
- than silently dropped. Where data is hosted is not a trademark jurisdiction.
43
+ than silently dropped. Where data is hosted is not a trademark jurisdiction. When the creator left
44
+ `target-jurisdictions` NOT DECIDED YET and no other source names a place, emit `jurisdictions: []`:
45
+ never invent a target. The screening still records every search the evidence reports (`WO` is always
46
+ searched), is marked as having no target, and clears no name until one is declared.
44
47
  - `niceClasses` — each class searched, with why this product lives in it.
45
48
  - `candidates` — one per name, with a kebab-case `slug`, the exact `name`, its `origin`,
46
49
  a one-line `rationale` for proposals, and:
47
- - `trademarkQueries` — one per register search the evidence reports: register,
48
- `accessPath` (`MACHINE_INTERFACE` when the register's published interface answered,
49
- `WEB_PAGE` when its web page was fetched), jurisdictions covered, classes and match types
50
- searched, outcome, conflicting marks, source URL, date, and a note for anything a reader needs.
51
- A TMview search covers every office it included: list each of those countries.
50
+ - `trademarkQueries` — one per register search the evidence reports FOR THIS NAME: register,
51
+ `searchedName` (the term the search actually ran with), `accessPath` (`MACHINE_INTERFACE` when
52
+ the register's published interface answered, `WEB_PAGE` when its web page was fetched),
53
+ jurisdictions covered, classes and match types searched, outcome, conflicting marks, source URL,
54
+ date, and a note for anything a reader needs. A TMview search covers every office it included:
55
+ list each of those countries.
52
56
  - `competitorCollisions` — any market competitor or alternative the name is identical
53
57
  or close to, AND any product the evidence found doing the same job under an identical or
54
58
  near-identical name.
@@ -62,6 +66,12 @@ every query faithfully.
62
66
  - **A register the evidence could not query or read is `UNKNOWN`, with a note saying
63
67
  why.** Never `CLEAR`. Never omit it either: an unrecorded register is an uncovered
64
68
  jurisdiction, and the candidate reads as not cleared anyway.
69
+ - **A search is recorded only for the name it was run with.** When the research tried a register
70
+ once, for one name, and stopped because the register failed, the other candidates were NOT
71
+ searched there: record each of them as `NOT_SEARCHED`, with `searchedName` and `sourceUrl`
72
+ citing the attempt that was made and a note saying so. Never copy one name's search onto
73
+ another as if it had been run: a query whose `searchedName` or source URL is another
74
+ candidate's is refused at landing.
65
75
  - **`CONFLICT` exactly when the query found a live identical or near-identical mark**,
66
76
  and then every such mark is listed with its source. A conflict with no mark, or a
67
77
  mark beside a `CLEAR`, is refused at landing.