@wildo-ai/framework-knowledge 1.1.8 → 1.1.10

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 (480) 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 +11 -0
  4. package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +9 -2
  5. package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +21 -0
  6. package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +121 -0
  7. package/dist/claude-marketplace/plugins/wildo/references/expert-personas-and-deliberations.md +26 -7
  8. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +31 -5
  9. package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +4 -2
  10. package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +29 -2
  11. package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +69 -24
  12. package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +10 -0
  13. package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +21 -5
  14. package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +31 -5
  15. package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +2 -0
  16. package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +20 -4
  17. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  18. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  19. package/dist/esm/framework-knowledge.definitions.js +95 -5
  20. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  21. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  22. package/dist/esm/index.d.ts.map +1 -1
  23. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
  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 +2 -2
  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 +11 -11
  28. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  29. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +29 -22
  30. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
  31. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +41 -3
  32. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  33. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +175 -14
  34. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  35. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
  36. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  37. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +3 -3
  38. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  39. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
  40. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -1
  41. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +8 -4
  43. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  44. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +13 -6
  45. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +4 -2
  47. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +90 -13
  49. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  50. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +4 -3
  51. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  52. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +4 -3
  53. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  54. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +8 -0
  55. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  56. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +12 -4
  57. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  58. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +12 -3
  59. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  60. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +8 -4
  61. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  62. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +4 -1
  63. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  64. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +2 -1
  65. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  66. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
  67. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
  68. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
  69. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  71. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
  72. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  73. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -1
  74. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  75. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
  76. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
  77. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +25 -27
  78. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  79. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +91 -43
  80. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  81. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +41 -0
  82. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -0
  83. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +43 -0
  84. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -0
  85. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +200 -0
  86. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -0
  87. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +203 -0
  88. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -0
  89. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +81 -0
  90. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -0
  91. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +93 -0
  92. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -0
  93. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +3 -1
  94. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  95. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +27 -18
  96. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  97. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  98. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +11 -1
  99. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  100. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +11 -11
  101. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  102. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +2 -0
  103. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  104. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +3 -1
  105. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  106. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  107. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +2 -0
  108. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  109. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +3 -1
  110. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  111. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  112. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +5 -2
  113. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  114. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -4
  115. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  116. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +27 -6
  117. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
  118. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +32 -12
  119. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  120. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
  121. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  122. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  123. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  124. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -1
  125. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  126. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +13 -5
  127. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  128. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +7 -3
  129. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  130. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +71 -2
  131. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  132. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -1
  133. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  134. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +23 -8
  135. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  136. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +7 -1
  137. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
  138. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +4 -2
  139. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
  140. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +9 -3
  141. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  142. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +3 -3
  143. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  144. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  145. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +35 -2
  146. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  147. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +41 -17
  148. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  149. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  150. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  151. package/dist/knowledge/manifest.json +8 -8
  152. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +22 -7
  153. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
  154. package/dist/knowledge/playbooks/bottom_up.build/method.md +17 -15
  155. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +4 -3
  156. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  157. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  158. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +261 -34
  159. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +42 -4
  160. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +188 -59
  161. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
  162. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +169 -276
  163. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -2
  164. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +8 -1
  165. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -1
  166. package/dist/knowledge/playbooks/bottom_up.conception/method.md +3 -2
  167. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +11 -3
  168. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
  169. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
  170. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +129 -17
  171. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +7 -4
  172. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +28 -6
  173. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +5 -4
  174. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +13 -5
  175. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +50 -0
  176. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +16 -4
  177. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +19 -0
  178. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +5 -2
  179. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +7 -3
  180. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  181. package/dist/knowledge/playbooks/refinement.document-facts/method.md +8 -0
  182. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +3 -2
  183. package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +5 -2
  184. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +1 -1
  185. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  186. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  187. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +75 -37
  188. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +35 -38
  189. package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +145 -0
  190. package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +57 -0
  191. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -0
  192. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -0
  193. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +99 -0
  194. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +65 -0
  195. package/dist/knowledge/playbooks/top_down.brand-naming/method.md +56 -0
  196. package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +76 -0
  197. package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
  198. package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
  199. package/dist/knowledge/playbooks/top_down.business-model/method.md +60 -6
  200. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +15 -10
  201. package/dist/knowledge/playbooks/top_down.capability-map/method.md +10 -9
  202. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -1
  203. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +30 -10
  204. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +3 -1
  205. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +4 -1
  206. package/dist/knowledge/playbooks/top_down.definition/method.md +8 -3
  207. package/dist/knowledge/playbooks/top_down.definition/playbook.json +6 -4
  208. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +16 -2
  209. package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +5 -2
  210. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -1
  211. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-protocol.json +1 -1
  212. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-treatment.json +1 -1
  213. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +26 -0
  214. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +4 -2
  215. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  216. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  217. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +11 -1
  218. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-protocol.json +1 -1
  219. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-treatment.json +1 -1
  220. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +84 -9
  221. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +6 -3
  222. package/dist/knowledge/playbooks/top_down.risk-register/method.md +21 -0
  223. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +8 -2
  224. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +4 -2
  225. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +29 -0
  226. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +58 -17
  227. package/dist/knowledge/references/brand.name-choice.config.md +144 -0
  228. package/dist/knowledge/references/brand.name-screening.config.md +308 -0
  229. package/dist/knowledge/references/build-plan.task-graph.config.md +119 -11
  230. package/dist/knowledge/references/business-model.pricing-plan.config.md +16 -0
  231. package/dist/knowledge/references/business-model.snapshot.config.md +64 -0
  232. package/dist/knowledge/references/business-model.snapshot.validation.md +68 -4
  233. package/dist/knowledge/references/capability-composition.config.md +67 -4
  234. package/dist/knowledge/references/companion.market.prompt-renderer.md +11 -6
  235. package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +44 -0
  236. package/dist/knowledge/references/example.backend.custom-operation.audit-event.md +81 -0
  237. package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +258 -0
  238. package/dist/knowledge/references/example.backend.custom-operation.computed-total.md +153 -0
  239. package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +107 -0
  240. package/dist/knowledge/references/example.data-seeding.minimal.md +39 -10
  241. package/dist/knowledge/references/example.data-seeding.row-reference.md +80 -0
  242. package/dist/knowledge/references/example.email.template.minimal.md +1 -1
  243. package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +74 -0
  244. package/dist/knowledge/references/example.resource.personal-data.free-text-field.md +19 -0
  245. package/dist/knowledge/references/example.resource.personal-data.person-without-account.md +27 -0
  246. package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +152 -0
  247. package/dist/knowledge/references/example.resource.ui-behavior.filter-presets.md +15 -0
  248. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +8 -0
  249. package/dist/knowledge/references/example.views.app-level.home-definition.md +13 -0
  250. package/dist/knowledge/references/example.views.chart-definition.shared.md +83 -0
  251. package/dist/knowledge/references/experience-plan.config.md +60 -7
  252. package/dist/knowledge/references/market.context-block.builder.md +1 -1
  253. package/dist/knowledge/references/market.snapshot.validation.md +1 -1
  254. package/dist/knowledge/references/placement-plan.config.md +43 -0
  255. package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -2
  256. package/dist/knowledge/references/requirements.non-functional-requirement.config.md +2 -0
  257. package/dist/knowledge/references/requirements.references.conventions.md +1 -1
  258. package/dist/knowledge/references/requirements.snapshot.config.md +57 -1
  259. package/dist/knowledge/references/requirements.snapshot.validation.md +35 -1
  260. package/dist/knowledge/references/saas.backend.audit-logs.log-event.md +63 -0
  261. package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +60 -0
  262. package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +156 -0
  263. package/dist/knowledge/references/saas.backend.email.send.md +77 -0
  264. package/dist/knowledge/references/saas.backend.notifications.operation-email-template-ref.md +60 -0
  265. package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +7 -1
  266. package/dist/knowledge/references/saas.data-seeding.computed-entry.md +43 -0
  267. package/dist/knowledge/references/saas.data-seeding.definition-input.md +14 -2
  268. package/dist/knowledge/references/saas.data-seeding.row-reference.md +93 -0
  269. package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +124 -0
  270. package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +316 -0
  271. package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +106 -0
  272. package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +60 -0
  273. package/dist/knowledge/references/saas.frontend.resource-label-params.md +52 -0
  274. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +47 -18
  275. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -1
  276. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destination-roles.md +25 -0
  277. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +2 -2
  278. package/dist/knowledge/references/saas.models.audit.trail-config.md +45 -0
  279. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +5 -3
  280. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +81 -2
  281. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +26 -0
  282. package/dist/knowledge/references/saas.models.roles.definition.md +61 -0
  283. package/dist/knowledge/references/saas.models.roles.organization-defaults.md +97 -0
  284. package/dist/knowledge/references/saas.public-runtime.contract.md +26 -0
  285. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +10 -0
  286. package/dist/knowledge/references/saas.website.astro.bridge.md +10 -0
  287. package/dist/knowledge/references/saas.website.astro.label-loader.md +12 -0
  288. package/dist/knowledge/references/saas.website.astro.llms-txt-server.md +14 -1
  289. package/dist/knowledge/references/saas.website.astro.site-context.md +13 -0
  290. package/dist/knowledge/references/saas.website.blog.bridge.md +4 -0
  291. package/dist/knowledge/references/saas.website.config.site-context-loader.md +3 -0
  292. package/dist/knowledge/references/saas.website.factories.define-section.md +4 -0
  293. package/dist/knowledge/references/saas.website.legal.public-document-links.md +76 -0
  294. package/dist/knowledge/references/saas.website.page-manifest.schema.md +12 -3
  295. package/dist/knowledge/references/saas.website.page-sections.component.md +72 -0
  296. package/dist/knowledge/references/saas.website.root-config.seo.md +2 -1
  297. package/dist/knowledge/references/saas.website.runtime.context.md +7 -0
  298. package/dist/knowledge/references/saas.website.sections.definition-schema.md +11 -0
  299. package/dist/knowledge/references/saas.website.seo.llms-txt-config.md +2 -0
  300. package/dist/knowledge/references/website-plan.config.md +26 -0
  301. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +13 -0
  302. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +7 -0
  303. package/dist/knowledge/references/zod.decorators.document-sequence.md +65 -0
  304. package/dist/knowledge/references/zod.decorators.schema-metadata.md +1 -0
  305. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +21 -0
  306. package/dist/knowledge/references/zod.factories.bigdecimal.md +1 -0
  307. package/dist/knowledge/references/zod.factories.code.md +1 -0
  308. package/dist/knowledge/references/zod.factories.duration.md +1 -0
  309. package/dist/knowledge/references/zod.factories.money.md +1 -0
  310. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  311. package/dist/knowledge/registries/framework-topics.json +374 -1
  312. package/dist/knowledge/registries/playbooks.json +76 -28
  313. package/dist/knowledge/registries/source-tags.json +1513 -898
  314. package/dist/knowledge/rules/live-context-door.md +5 -2
  315. package/dist/knowledge/skills/INDEX.md +5 -2
  316. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +16 -3
  317. package/dist/knowledge/skills/application-database-migrations/SKILL.md +14 -3
  318. package/dist/knowledge/skills/application-roles-authoring/SKILL.md +158 -0
  319. package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +169 -0
  320. package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +63 -0
  321. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +6 -1
  322. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +256 -9
  323. package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +42 -0
  324. package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +220 -0
  325. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +5 -0
  326. package/dist/knowledge/skills/brand-name-screening/SKILL.md +178 -0
  327. package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +466 -0
  328. package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +87 -0
  329. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +7 -3
  330. package/dist/knowledge/skills/config-app-shell/SKILL.md +58 -5
  331. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +461 -0
  332. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +80 -0
  333. package/dist/knowledge/skills/config-design-system/SKILL.md +28 -6
  334. package/dist/knowledge/skills/config-navigation/SKILL.md +14 -3
  335. package/dist/knowledge/skills/config-saas/SKILL.md +56 -15
  336. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +65 -2
  337. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +62 -2
  338. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +81 -2
  339. package/dist/knowledge/skills/config-saas-backend/SKILL.md +6 -1
  340. package/dist/knowledge/skills/configure-billing/SKILL.md +18 -4
  341. package/dist/knowledge/skills/email-add-template/SKILL.md +28 -6
  342. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +1 -1
  343. package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +128 -0
  344. package/dist/knowledge/skills/email-add-template/references/framework-operation-email-template-ref-api.md +99 -0
  345. package/dist/knowledge/skills/engine-component-registration/SKILL.md +6 -1
  346. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +21 -8
  347. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -2
  348. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +18 -4
  349. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +11 -3
  350. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +2 -1
  351. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +8 -0
  352. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +19 -5
  353. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +10 -2
  354. package/dist/knowledge/skills/inbound-channels/SKILL.md +2 -2
  355. package/dist/knowledge/skills/infra-environment-config/SKILL.md +6 -1
  356. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +17 -2
  357. package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +122 -0
  358. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +11 -0
  359. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +9 -2
  360. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +10 -2
  361. package/dist/knowledge/skills/market-alternatives/SKILL.md +10 -2
  362. package/dist/knowledge/skills/market-authoring-overview/SKILL.md +10 -2
  363. package/dist/knowledge/skills/market-category/SKILL.md +21 -7
  364. package/dist/knowledge/skills/market-channels/SKILL.md +6 -1
  365. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +22 -4
  366. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +12 -2
  367. package/dist/knowledge/skills/market-generation-cli/SKILL.md +21 -11
  368. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +11 -6
  369. package/dist/knowledge/skills/market-icp/SKILL.md +10 -2
  370. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +6 -1
  371. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +6 -1
  372. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
  373. package/dist/knowledge/skills/market-persona/SKILL.md +14 -3
  374. package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +6 -1
  375. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +10 -2
  376. package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +6 -1
  377. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -4
  378. package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +1 -1
  379. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +6 -1
  380. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +26 -0
  381. package/dist/knowledge/skills/module-companion-exports/SKILL.md +7 -1
  382. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +10 -0
  383. package/dist/knowledge/skills/module-relationships/SKILL.md +37 -8
  384. package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +4 -2
  385. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +14 -3
  386. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +6 -1
  387. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +14 -3
  388. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +10 -2
  389. package/dist/knowledge/skills/resource-add-field/SKILL.md +10 -2
  390. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +46 -17
  391. package/dist/knowledge/skills/resource-add-resource/SKILL.md +14 -2
  392. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +26 -0
  393. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +29 -3
  394. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +19 -4
  395. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +5 -2
  396. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +103 -0
  397. package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +135 -0
  398. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +26 -0
  399. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +26 -7
  400. package/dist/knowledge/skills/resource-custom-view/SKILL.md +10 -2
  401. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +46 -17
  402. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +2 -2
  403. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +5 -1
  404. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +15 -1
  405. package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +569 -0
  406. package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +358 -0
  407. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +8 -0
  408. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +21 -0
  409. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +7 -2
  410. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +13 -0
  411. package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +153 -0
  412. package/dist/knowledge/skills/resource-status-lifecycle/references/commercial-documents.md +46 -0
  413. package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +198 -0
  414. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +30 -4
  415. package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +157 -0
  416. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +101 -19
  417. package/dist/knowledge/skills/seeding-authoring/SKILL.md +202 -39
  418. package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +67 -0
  419. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +154 -4
  420. package/dist/knowledge/skills/seeding-authoring/references/seed-row-overlay.md +22 -0
  421. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +7 -1
  422. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +43 -0
  423. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +2 -2
  424. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +6 -1
  425. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +10 -0
  426. package/dist/knowledge/skills/spec-component-update/SKILL.md +10 -2
  427. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +2 -2
  428. package/dist/knowledge/skills/spec-family-update/SKILL.md +71 -66
  429. package/dist/knowledge/skills/spec-family-update/references/family-spec-routing.md +1 -1
  430. package/dist/knowledge/skills/spec-resource-update/SKILL.md +30 -10
  431. package/dist/knowledge/skills/spec-resource-update/references/resource-spec-field-routing.md +28 -0
  432. package/dist/knowledge/skills/spec-update-after-change/SKILL.md +22 -5
  433. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +6 -1
  434. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +10 -2
  435. package/dist/knowledge/skills/views-app-level/SKILL.md +13 -3
  436. package/dist/knowledge/skills/views-app-level/references/application-home.md +56 -0
  437. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +221 -37
  438. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +22 -5
  439. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +1 -1
  440. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +32 -2
  441. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +16 -3
  442. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +4 -0
  443. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +7 -1
  444. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +13 -1
  445. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +14 -2
  446. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +13 -1
  447. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +6 -1
  448. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +19 -1
  449. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +55 -18
  450. package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +98 -0
  451. package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +8 -11
  452. package/dist/knowledge/skills/website-page-authoring/SKILL.md +100 -8
  453. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +3 -0
  454. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +6 -1
  455. package/dist/knowledge/skills/website-section-contact/SKILL.md +15 -0
  456. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +15 -0
  457. package/dist/knowledge/skills/website-section-cta/SKILL.md +15 -0
  458. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +15 -0
  459. package/dist/knowledge/skills/website-section-faq/SKILL.md +21 -1
  460. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +15 -0
  461. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +21 -1
  462. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +15 -0
  463. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +25 -2
  464. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +15 -0
  465. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +15 -0
  466. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +15 -0
  467. package/dist/knowledge/skills/website-section-hero/SKILL.md +33 -10
  468. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +15 -0
  469. package/dist/knowledge/skills/website-section-pricing/SKILL.md +21 -1
  470. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +15 -0
  471. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +27 -2
  472. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +15 -0
  473. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +16 -4
  474. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +11 -0
  475. package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +16 -1
  476. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +2 -1
  477. package/dist/knowledge/topic-index.json +1590 -292
  478. package/dist/tsconfig.build.tsbuildinfo +1 -1
  479. package/dist/tsconfig.tsbuildinfo +1 -1
  480. package/package.json +4 -4
@@ -37,12 +37,13 @@
37
37
  ],
38
38
  "stepOutputs": [],
39
39
  "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 AI POSTURE section — per enabled capability, a declared consequence or OUTSTANDING |\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 posture 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**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**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## 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\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",
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 AI POSTURE section — per enabled capability, a declared consequence or OUTSTANDING |\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 posture 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**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## 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\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",
41
41
  "skillRefs": [],
42
42
  "skillBodyRefs": [],
43
43
  "contextSources": [
44
44
  "compliance_primary_facts",
45
- "document_fact_obligations"
45
+ "document_fact_obligations",
46
+ "application_role_graph"
46
47
  ],
47
48
  "draftableDocumentDefinitionRefs": [],
48
49
  "suspendsForClarification": false,
@@ -21,8 +21,11 @@ words. That is the feature. Nothing else is in scope.
21
21
  Two outputs, and each holds **only what this feature adds**:
22
22
 
23
23
  - **Requirements.** The functional requirements the feature adds, in the `functional` list, each with a
24
- ref that does not exist yet (`functional-requirement-<slug>`). Leave `nonFunctional` empty: the
25
- application's qualities are the main line's.
24
+ ref that does not exist yet (`functional-requirement-<slug>`). Leave `nonFunctional`,
25
+ `excludedStatedFacts` and `excludedMarketPains` empty: the application's qualities, and what it decided
26
+ to leave out, are the main line's, and only your `functional` entries are added to it. Leave each
27
+ requirement's `painRefs` empty too: you do not see the market, and a pain ref that does not exist is
28
+ refused.
26
29
  - **Feature drafts.** One draft per capability the feature needs, each with a feature ref that does not
27
30
  exist yet, its purpose and business role tracing to the requirements you add.
28
31
 
@@ -46,7 +46,7 @@
46
46
  ],
47
47
  "stepOutputs": [],
48
48
  "method": {
49
- "guidance": "# Feature contribution — one feature, added to the product model\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis step runs for a **feature-development line**: work opened beside the application's main line to add\nONE feature. What the line is for is written above, under \"What this run is for\", in the creator's own\nwords. That is the feature. Nothing else is in scope.\n\n## What you return\n\nTwo outputs, and each holds **only what this feature adds**:\n\n- **Requirements.** The functional requirements the feature adds, in the `functional` list, each with a\n ref that does not exist yet (`functional-requirement-<slug>`). Leave `nonFunctional` empty: the\n application's qualities are the main line's.\n- **Feature drafts.** One draft per capability the feature needs, each with a feature ref that does not\n exist yet, its purpose and business role tracing to the requirements you add.\n\nWhat you return is ADDED beside what the application already holds, and each element is recorded as this\nline's. So:\n\n- Do not copy the application's existing requirements or drafts into your output. An element you hand back\n unchanged is ignored; an element you hand back CHANGED under an existing ref is refused, and the whole\n run with it, because a line never redrafts what someone else decided.\n- If the feature genuinely changes an existing requirement, say so in the new requirement's rationale\n (which existing ref it extends or supersedes). Changing the existing one is the main line's decision.\n- Re-running this step for the same line updates the elements this line added. It never removes one: an\n element you leave out stays as it was.\n\n## How to describe the feature\n\nRead the vision and the requirements whole, and the domain plan as a map of what the application already\nmodels. Describe the feature against them: name the resources it touches in the requirement's statement\nwhen that helps, but design nothing. The domain plan and the build are re-derived from your requirements\nafterwards, by the application, and that is where the design happens.\n\nPrefer fewer, sharper requirements. Each must be checkable: give acceptance criteria a reviewer could\ntest against the built feature.\n",
49
+ "guidance": "# Feature contribution — one feature, added to the product model\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis step runs for a **feature-development line**: work opened beside the application's main line to add\nONE feature. What the line is for is written above, under \"What this run is for\", in the creator's own\nwords. That is the feature. Nothing else is in scope.\n\n## What you return\n\nTwo outputs, and each holds **only what this feature adds**:\n\n- **Requirements.** The functional requirements the feature adds, in the `functional` list, each with a\n ref that does not exist yet (`functional-requirement-<slug>`). Leave `nonFunctional`,\n `excludedStatedFacts` and `excludedMarketPains` empty: the application's qualities, and what it decided\n to leave out, are the main line's, and only your `functional` entries are added to it. Leave each\n requirement's `painRefs` empty too: you do not see the market, and a pain ref that does not exist is\n refused.\n- **Feature drafts.** One draft per capability the feature needs, each with a feature ref that does not\n exist yet, its purpose and business role tracing to the requirements you add.\n\nWhat you return is ADDED beside what the application already holds, and each element is recorded as this\nline's. So:\n\n- Do not copy the application's existing requirements or drafts into your output. An element you hand back\n unchanged is ignored; an element you hand back CHANGED under an existing ref is refused, and the whole\n run with it, because a line never redrafts what someone else decided.\n- If the feature genuinely changes an existing requirement, say so in the new requirement's rationale\n (which existing ref it extends or supersedes). Changing the existing one is the main line's decision.\n- Re-running this step for the same line updates the elements this line added. It never removes one: an\n element you leave out stays as it was.\n\n## How to describe the feature\n\nRead the vision and the requirements whole, and the domain plan as a map of what the application already\nmodels. Describe the feature against them: name the resources it touches in the requirement's statement\nwhen that helps, but design nothing. The domain plan and the build are re-derived from your requirements\nafterwards, by the application, and that is where the design happens.\n\nPrefer fewer, sharper requirements. Each must be checkable: give acceptance criteria a reviewer could\ntest against the built feature.\n",
50
50
  "skillRefs": [
51
51
  "spec-feature-update"
52
52
  ],
@@ -1 +1 @@
1
- {"aggregationPolicyRef":"application-creation:aggregation/worst-brand-identity-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.audience","brand.asset","market.icp"],"criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1}],"instruction":"Determine whether the brief hands off correctly: every targetIcpRef in the audience names an ICP the market snapshot holds and none is an anti-target; the audience rationale follows from the brief's own tone and mission; and resolvedAssets is EMPTY, because assets are the companion logo step's output and a hand-authored asset reference would be overwritten or flagged.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The audience is absent although the market snapshot names ICPs the tone was chosen for, or the rationale is generic.","GAP":"An audience ref naming an ICP the market does not hold or an anti-target, or a resolvedAssets entry authored by hand.","INDETERMINATE":"The market snapshot's ICPs are not in evidence, so the audience cannot be checked.","PASS":"Every audience ref resolves to a market ICP that is not an anti-target, and resolvedAssets is empty."}},{"assessesAspects":["brand.name","brand.logo-direction","brand.visual-tone","vision.idea","vision.mission"],"criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1}],"instruction":"Determine whether the brand brief is GROUNDED: the brand name is the exact string the creator gave; the logo direction's symbolism derives from the vision's idea and mission rather than a decorative motif; the visual tone translates the market's verbal voice where a market snapshot exists and is noted as provisional where it does not; and no mark direction or tone appears that the creator's interview answers do not support. A partially-directed brief (name only, direction still open) is a legitimate state, not a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a thin symbolism rationale, a tone that only loosely follows the market voice, or a background treatment the pipeline must compensate for.","GAP":"A mark direction or tone the creator did not give, a name that differs from the interview, or symbolism unrelated to the vision's idea and mission.","INDETERMINATE":"The interview answers or the vision are not in evidence, so grounding cannot be established.","PASS":"The name is the creator's, the symbolism traces to the vision, the tone follows the market voice or is honestly provisional, and nothing is invented beyond the interview."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-identity","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-identity"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
1
+ {"aggregationPolicyRef":"application-creation:aggregation/worst-brand-identity-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.audience","brand.asset","market.icp"],"criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1}],"instruction":"Determine whether the brief hands off correctly: every targetIcpRef in the audience names an ICP the market snapshot holds and none is an anti-target; the audience rationale follows from the brief's own tone and mission; and resolvedAssets is EMPTY, because assets are the companion logo step's output and a hand-authored asset reference would be overwritten or flagged.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The audience is absent although the market snapshot names ICPs the tone was chosen for, or the rationale is generic.","GAP":"An audience ref naming an ICP the market does not hold or an anti-target, or a resolvedAssets entry authored by hand.","INDETERMINATE":"The market snapshot's ICPs are not in evidence, so the audience cannot be checked.","PASS":"Every audience ref resolves to a market ICP that is not an anti-target, and resolvedAssets is empty."}},{"assessesAspects":["brand.name","brand.logo-direction","brand.visual-tone","vision.idea","vision.mission"],"criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1}],"instruction":"Determine whether the brand brief is GROUNDED: the brand name is exactly the name the creator chose in the interview (an option may carry a bracketed qualifier such as [not-screened], [screening-incomplete] or [keep-despite-conflict] — the name is the text before it, and the qualifier never appears in the brand name); the mark type, background and colour seeds are the creator's answers; the symbolism, motifs and imagery to avoid DERIVE from the vision's idea and mission; the visual tone translates the market's verbal voice where a market snapshot exists and is noted as provisional where it does not; and the creator's visual-direction answer, when it is not \"none\", is honoured and outranks the derivation. Derived direction is expected — the interview no longer asks for it — but it must trace to the vision or the market voice, never be a decorative choice of the model's own. A partially-directed brief (name only, direction still open) is a legitimate state, not a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a thin symbolism rationale, a tone that only loosely follows the market voice, or a background treatment the pipeline must compensate for.","GAP":"A name or mark choice that differs from the interview, a visual direction the creator gave that the brief ignores, or symbolism and tone that trace to neither the vision nor the market voice.","INDETERMINATE":"The interview answers or the vision are not in evidence, so grounding cannot be established.","PASS":"The name and the mark choices are the creator's, the symbolism and imagery trace to the vision, the tone follows the market voice or is honestly provisional, and the creator's visual direction is honoured."}},{"assessesAspects":["brand.name","brand-name-screening.candidate","brand-name-screening.jurisdiction","brand-name-screening.nice-class"],"criterionRef":"application-creation:criterion/brand-identity-name-screened-and-unclaimed","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1}],"instruction":"Determine whether the chosen NAME stands honestly against its screening: the brand name is a candidate of the brand-name screening, whose queries cover every jurisdiction and Nice class the screening declares; where the screening could not check a register, nothing in the brief presents the name as cleared; where the creator kept a name despite a conflict, the brief does not hide or soften it; and nothing in the brief asserts that the name is available, free to use, registered by this product or legally cleared — a minimal trademark screening is never a clearance opinion.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The name was chosen as not screened, screening-incomplete or kept despite a conflict, and the brief says so plainly.","GAP":"The name is not among the screened candidates, an unchecked or conflicting name is presented as clear, or the brief asserts availability or legal clearance.","INDETERMINATE":"The brand-name screening is not in evidence, so the name's standing cannot be checked.","PASS":"The name is a screened candidate covered in every declared jurisdiction and class, and the brief claims no availability or clearance."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-identity","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-identity"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
@@ -1 +1 @@
1
- {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-brand-brief","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision"],"requirementRef":"application-creation:authority-requirement/brand-identity-result","requirementVersion":1,"riskClassRef":"application-creation:risk/brand-brief-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/brand-identity","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/brand-identity-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/brand-identity","policyVersion":1},"decisionPointRef":"application-creation:decision-point/brand-identity-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/brand-identity-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/brand-identity","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/brand-brief-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-brand-brief-change","triggerRefs":["application-creation:trigger/brand-brief-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-brand-identity-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision"],"hardFloorRef":"application-creation:hard-floor/brand-brief-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/brand-identity-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/brand-identity","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-brand-identity-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.audience","brand.asset","market.icp"],"criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1}],"instruction":"Determine whether the brief hands off correctly: every targetIcpRef in the audience names an ICP the market snapshot holds and none is an anti-target; the audience rationale follows from the brief's own tone and mission; and resolvedAssets is EMPTY, because assets are the companion logo step's output and a hand-authored asset reference would be overwritten or flagged.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The audience is absent although the market snapshot names ICPs the tone was chosen for, or the rationale is generic.","GAP":"An audience ref naming an ICP the market does not hold or an anti-target, or a resolvedAssets entry authored by hand.","INDETERMINATE":"The market snapshot's ICPs are not in evidence, so the audience cannot be checked.","PASS":"Every audience ref resolves to a market ICP that is not an anti-target, and resolvedAssets is empty."}},{"assessesAspects":["brand.name","brand.logo-direction","brand.visual-tone","vision.idea","vision.mission"],"criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1}],"instruction":"Determine whether the brand brief is GROUNDED: the brand name is the exact string the creator gave; the logo direction's symbolism derives from the vision's idea and mission rather than a decorative motif; the visual tone translates the market's verbal voice where a market snapshot exists and is noted as provisional where it does not; and no mark direction or tone appears that the creator's interview answers do not support. A partially-directed brief (name only, direction still open) is a legitimate state, not a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a thin symbolism rationale, a tone that only loosely follows the market voice, or a background treatment the pipeline must compensate for.","GAP":"A mark direction or tone the creator did not give, a name that differs from the interview, or symbolism unrelated to the vision's idea and mission.","INDETERMINATE":"The interview answers or the vision are not in evidence, so grounding cannot be established.","PASS":"The name is the creator's, the symbolism traces to the vision, the tone follows the market voice or is honestly provisional, and nothing is invented beyond the interview."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-identity","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-identity"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/brand-identity","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-market-and-brand-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-market-and-brand-candidate"}],"schemaVersion":1}
1
+ {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-brand-brief","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision"],"requirementRef":"application-creation:authority-requirement/brand-identity-result","requirementVersion":1,"riskClassRef":"application-creation:risk/brand-brief-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/brand-identity","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/brand-identity-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/brand-identity","policyVersion":1},"decisionPointRef":"application-creation:decision-point/brand-identity-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/brand-identity-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/brand-identity","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/brand-brief-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-brand-brief-change","triggerRefs":["application-creation:trigger/brand-brief-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-brand-identity-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision"],"hardFloorRef":"application-creation:hard-floor/brand-brief-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/brand-identity-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/brand-identity","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-brand-identity-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.audience","brand.asset","market.icp"],"criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1}],"instruction":"Determine whether the brief hands off correctly: every targetIcpRef in the audience names an ICP the market snapshot holds and none is an anti-target; the audience rationale follows from the brief's own tone and mission; and resolvedAssets is EMPTY, because assets are the companion logo step's output and a hand-authored asset reference would be overwritten or flagged.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The audience is absent although the market snapshot names ICPs the tone was chosen for, or the rationale is generic.","GAP":"An audience ref naming an ICP the market does not hold or an anti-target, or a resolvedAssets entry authored by hand.","INDETERMINATE":"The market snapshot's ICPs are not in evidence, so the audience cannot be checked.","PASS":"Every audience ref resolves to a market ICP that is not an anti-target, and resolvedAssets is empty."}},{"assessesAspects":["brand.name","brand.logo-direction","brand.visual-tone","vision.idea","vision.mission"],"criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1}],"instruction":"Determine whether the brand brief is GROUNDED: the brand name is exactly the name the creator chose in the interview (an option may carry a bracketed qualifier such as [not-screened], [screening-incomplete] or [keep-despite-conflict] — the name is the text before it, and the qualifier never appears in the brand name); the mark type, background and colour seeds are the creator's answers; the symbolism, motifs and imagery to avoid DERIVE from the vision's idea and mission; the visual tone translates the market's verbal voice where a market snapshot exists and is noted as provisional where it does not; and the creator's visual-direction answer, when it is not \"none\", is honoured and outranks the derivation. Derived direction is expected — the interview no longer asks for it — but it must trace to the vision or the market voice, never be a decorative choice of the model's own. A partially-directed brief (name only, direction still open) is a legitimate state, not a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a thin symbolism rationale, a tone that only loosely follows the market voice, or a background treatment the pipeline must compensate for.","GAP":"A name or mark choice that differs from the interview, a visual direction the creator gave that the brief ignores, or symbolism and tone that trace to neither the vision nor the market voice.","INDETERMINATE":"The interview answers or the vision are not in evidence, so grounding cannot be established.","PASS":"The name and the mark choices are the creator's, the symbolism and imagery trace to the vision, the tone follows the market voice or is honestly provisional, and the creator's visual direction is honoured."}},{"assessesAspects":["brand.name","brand-name-screening.candidate","brand-name-screening.jurisdiction","brand-name-screening.nice-class"],"criterionRef":"application-creation:criterion/brand-identity-name-screened-and-unclaimed","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1}],"instruction":"Determine whether the chosen NAME stands honestly against its screening: the brand name is a candidate of the brand-name screening, whose queries cover every jurisdiction and Nice class the screening declares; where the screening could not check a register, nothing in the brief presents the name as cleared; where the creator kept a name despite a conflict, the brief does not hide or soften it; and nothing in the brief asserts that the name is available, free to use, registered by this product or legally cleared — a minimal trademark screening is never a clearance opinion.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The name was chosen as not screened, screening-incomplete or kept despite a conflict, and the brief says so plainly.","GAP":"The name is not among the screened candidates, an unchecked or conflicting name is presented as clear, or the brief asserts availability or legal clearance.","INDETERMINATE":"The brand-name screening is not in evidence, so the name's standing cannot be checked.","PASS":"The name is a screened candidate covered in every declared jurisdiction and class, and the brief claims no availability or clearance."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-identity","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-identity"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/brand-identity","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-market-and-brand-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-market-and-brand-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-name-screened-and-unclaimed","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/brand-name-screening-and-brand-candidate"}],"schemaVersion":1}
@@ -1,4 +1,4 @@
1
- # Brand Identity — Interview Method (v1 scaffold)
1
+ # Brand Identity — Method (v1 scaffold)
2
2
 
3
3
  ### Target Application Framing
4
4
 
@@ -20,8 +20,9 @@ Read and apply these patterns from the application-developer point of view:
20
20
 
21
21
  ## What this playbook does
22
22
 
23
- You are the **brand-identity interviewer**. Your job is to draw the product's
24
- VISUAL identity out of the creator and capture it as a single typed
23
+ You are the **brand-identity author**. Your job is to capture the product's VISUAL
24
+ identity, from the creator's few decisions plus what the vision and the market already
25
+ say, as a single typed
25
26
  **`BrandSnapshot`** — the `brand-brief` artifact. This is the visual
26
27
  counterpart to the vision brief (which captured *intent*) and the market brief
27
28
  (which captured the *verbal* voice): here you capture what the product should
@@ -51,50 +52,77 @@ knows:
51
52
  precondition — if there is no market snapshot yet, derive the visual tone from
52
53
  the vision alone and note it as provisional.
53
54
 
54
- ## The elicitation posture
55
-
56
- - **Interview, do not fill a form.** The typed questions on this playbook
57
- (`method.elicitation`) are your backbone, not your ceiling. Ask them in a
58
- natural order, reflect each answer back in one line, and let the creator
59
- correct you before moving on.
60
- - **Progressive is fine.** A `BrandSnapshot` requires only the **name**; the
61
- logo direction and visual tone are OPTIONAL and elicited progressively. If the
62
- creator can only name the brand today, capture it, note what is still open,
63
- and stop — the snapshot persists as partially-directed and this playbook can
64
- resume. Never invent a mark direction the creator did not give you.
65
- - **One product, one brand.** The snapshot is a single aggregate — one name,
66
- one logo direction, one visual tone. If the creator describes two brands,
67
- stop and ask which one this journey is for.
68
-
69
- ## What you elicit — one aggregate
55
+ ## What the creator decided, and what you derive
56
+
57
+ The interview asks only what the creator alone can decide. Everything else you derive,
58
+ and you say where it came from.
59
+
60
+ | Decided by the creator (interview answer) | Derived by you |
61
+ |---|---|
62
+ | `brand-name`: chosen from the screened names | `symbolism`, from the vision's idea and mission |
63
+ | `brand-tagline`, or "none" | `motifs`: concrete elements that carry that symbolism |
64
+ | `logo-mark-type` | `avoid`: the guardrails that keep the mark usable (no gradients, no literal clip-art, no text inside a symbol meant to stand alone) |
65
+ | `logo-background` | `visualTone` (style keywords, mood, colour story), translated from the market's verbal voice |
66
+ | `visual-color-seeds`, or "none" | |
67
+ | `visual-direction`, or "none" | |
68
+
69
+ - **`visual-direction` outranks the derivation.** When it is not "none", whatever it asks
70
+ the mark to evoke, include or avoid is honoured, and the derived parts are shaped around it.
71
+ - **Derived is not invented.** Every symbol, motif and tone keyword must trace to the
72
+ vision or the market voice. A decorative choice of your own is the one thing to avoid.
73
+ - **Progressive is fine.** A `BrandSnapshot` requires only the **name**. If the vision or
74
+ the market is too thin to derive a direction honestly, leave `logoDirection` or
75
+ `visualTone` out and say what is missing. The snapshot persists partially directed, and
76
+ this playbook can resume.
77
+ - **One product, one brand.** The snapshot is a single aggregate: one name, one logo
78
+ direction, one visual tone.
79
+
80
+ ## What the brief holds — one aggregate
70
81
 
71
82
  - **Name** (REQUIRED). The anchor lexical identity: the exact, case-sensitive
72
83
  `brandName` the logo renders and every surface prints, plus an optional
73
84
  `tagline` to lock up with combination marks / OG imagery. Nothing visual
74
- here — the mark and the palette come next. A brand without a name has nothing
75
- for a mark to render; do not proceed until you have it.
85
+ here — the mark and the palette come next.
86
+
87
+ **You do not invent the name, and you do not choose it.** `top_down.brand-naming`
88
+ proposed names and ran a minimal trademark screening of each; the creator CHOSE
89
+ one in this playbook's `brand-name` question, from options computed from that
90
+ screening. The `brandName` is exactly the chosen option's name. An option may end
91
+ with a bracketed qualifier — `[not-screened]`, `[screening-incomplete]` or
92
+ `[keep-despite-conflict]` — which records how the creator chose; it is NEVER part of
93
+ the name, so drop it. The interview answer also records the line the creator was
94
+ shown beside that option (the product already using the name, the registers nobody
95
+ could read): carry its substance into the brief rather than paraphrasing it away.
96
+
97
+ The brand-name screening is in your brief. Never describe the name as
98
+ "available", "registered", "protected" or "cleared": a screening is not a legal
99
+ clearance opinion. Where the creator kept a name despite a conflict, or chose one
100
+ whose screening is incomplete or read no register at all, do not hide or soften that
101
+ anywhere in the brief.
76
102
  - **Logo direction** (optional, WARNed when absent). The creative brief the
77
103
  image model turns into the master logo:
78
- - `markType` — pick the archetype. **Default to `COMBINATION_MARK`** (symbol +
79
- wordmark) — it is the only archetype that natively yields BOTH a header
80
- lockup and a square symbol for favicons/app-icons. Reach for `WORDMARK`
81
- (text-only) only when the brand is genuinely wordmark-only; warn the creator
82
- that a wordmark cannot produce a clean square app icon.
83
- - `motifs` — concrete visual elements to include (short noun phrases).
104
+ - `markType` — the creator's `logo-mark-type` answer. The question suggests
105
+ `COMBINATION_MARK` (symbol + wordmark) because it is the only archetype that
106
+ natively yields BOTH a header lockup and a square symbol for favicons and app
107
+ icons. When the creator chose `WORDMARK` (text only), note in the brief that a
108
+ wordmark cannot produce a clean square app icon.
109
+ - `motifs` — concrete visual elements to include (short noun phrases), DERIVED
110
+ from the symbolism and the creator's `visual-direction`.
84
111
  - `symbolism` — the meaning the mark should evoke, **derived from the vision
85
- mission/idea**.
112
+ mission/idea** (and the creator's `visual-direction`, when they gave one).
86
113
  - `avoid` — imagery don'ts (the negative-prompt guardrails that keep output
87
- usable).
88
- - `backgroundTreatment` — keep `TRANSPARENT_ISOLATED` (the default and the
89
- only treatment that rasterizes losslessly into every derived asset). A
114
+ usable), DERIVED, plus anything the creator's `visual-direction` rules out.
115
+ - `backgroundTreatment` — the creator's `logo-background` answer.
116
+ `TRANSPARENT_ISOLATED` is the default and the only treatment that rasterizes
117
+ losslessly into every derived asset. A
90
118
  solid field or contextual scene is an explicit opt-in the pipeline must
91
119
  compensate for — the validator WARNs on it.
92
120
  - **Visual tone** (optional, WARNed when absent). The aesthetic register — the
93
- VISUAL counterpart to the market voice: 3–7 concrete `styleKeywords`
121
+ VISUAL counterpart to the market voice, DERIVED from it (and shaped by the
122
+ creator's `visual-direction`): 3–7 concrete `styleKeywords`
94
123
  ("geometric", "minimal", "warm"), a one-line `mood`, a prose `colorIntent`
95
- (the color STORY, not hex values), and optional hex `colorSeeds` pinned only
96
- when the brand has already committed to anchors that must agree with the
97
- design system.
124
+ (the color STORY, not hex values), and the hex `colorSeeds` the creator gave in
125
+ `visual-color-seeds`, only when they named any.
98
126
  - **Audience** (optional). WHO the brand is for: `targetIcpRefs`, the refs of
99
127
  the market ICPs its name and tone are chosen to speak to, copied exactly from
100
128
  the market's `icps`, plus a one-line `rationale`. Derive it from what the brief
@@ -104,13 +132,23 @@ knows:
104
132
  brand's ICPs, and through them their personas and positionings, from this one
105
133
  declaration.
106
134
 
135
+ ## Answers the creator did not give
136
+
137
+ In a quick interview the creator is asked only for `brand-name`. Every other answer may
138
+ reach your brief marked ASSUMED: the companion proposed it from the vision and the market,
139
+ and it was kept without the creator deciding it — on their review, or by an unattended round. Use an assumed answer as a working
140
+ default, not as the creator's choice. Where the brief explains a choice that rests on one
141
+ (a tagline, a mark type, a background, a colour seed), say it was proposed rather than
142
+ chosen, and never let an assumed answer outrank what the vision and the market voice imply
143
+ the way the creator's own answer would. `brand-name` is never assumed: the creator chooses it.
144
+
107
145
  ## What you emit
108
146
 
109
147
  A single `BrandSnapshot`:
110
148
 
111
149
  - `version` — the snapshot format version (leave at its default unless told otherwise).
112
150
  - `name` — the required anchor (`brandName`, optional `tagline`).
113
- - `logoDirection` / `visualTone` / `audience` — the optional singletons, present only if elicited.
151
+ - `logoDirection` / `visualTone` / `audience` — the optional singletons, present when they could be decided or honestly derived.
114
152
  - `resolvedAssets` — **leave empty.** This is the companion logo step's output,
115
153
  not something you author. Hand-authoring it fabricates asset references the
116
154
  pipeline will overwrite or the validator will flag.
@@ -148,7 +186,7 @@ is made.
148
186
 
149
187
  Before you start, read the current journey state, the vision brief that grounds
150
188
  the brand's meaning, and any brand brief that already exists so you refine it
151
- rather than re-eliciting it from scratch.
189
+ rather than re-deriving it from scratch.
152
190
 
153
191
  (The vision and any previously landed brand brief arrive in your brief as the `vision-brief` and
154
192
  `brand-brief` input sections.)
@@ -1,19 +1,30 @@
1
1
  {
2
2
  "ref": "top_down.brand-identity",
3
- "version": "0.1.2",
3
+ "version": "0.4.0",
4
4
  "phase": "top_down",
5
- "intent": "Brand-identity elicitation: draw the product's VISUAL identity out of the creator — the brand name, the logo creative direction (mark type, motifs, symbolism, imagery don'ts, background), and the visual tone (style keywords, mood, color story) — and capture it as a single validated BrandSnapshot (the `brand-brief` artifact family). The visual counterpart to the vision (intent) and market (verbal voice) briefs: it derives symbolism from the VisionSnapshot's idea/mission and, when a MarketSnapshot exists, translates its verbal `tonesOfVoice` into a visual register. The emitted brand-brief is the INPUT the companion logo step generates the master logo + derived assets from, and via `BrandSnapshot.resolvedAssets` the single source of truth every logo/favicon/brand-image consumer resolves against. Progressive: may persist a partially-directed brand (logoDirection/visualTone optional) and resume. v1 scaffold methodology — iterate the interview.",
5
+ "intent": "Brand-identity elicitation: draw the product's VISUAL identity out of the creator — the brand name (CHOSEN by the creator from the screened candidates `top_down.brand-naming` landed), the logo creative direction (mark type, motifs, symbolism, imagery don'ts, background), and the visual tone (style keywords, mood, color story) — and capture it as a single validated BrandSnapshot (the `brand-brief` artifact family). The visual counterpart to the vision (intent) and market (verbal voice) briefs: it derives symbolism from the VisionSnapshot's idea/mission and, when a MarketSnapshot exists, translates its verbal `tonesOfVoice` into a visual register. The emitted brand-brief is the INPUT the companion logo step generates the master logo + derived assets from, and via `BrandSnapshot.resolvedAssets` the single source of truth every logo/favicon/brand-image consumer resolves against. Progressive: may persist a partially-directed brand (logoDirection/visualTone optional) and resume. v1 scaffold methodology — iterate the interview.",
6
6
  "preconditions": [
7
7
  {
8
8
  "kind": "artifact_exists",
9
9
  "selector": {
10
10
  "family": "vision-brief"
11
11
  }
12
+ },
13
+ {
14
+ "kind": "artifact_valid",
15
+ "selector": {
16
+ "family": "brand-name-screening"
17
+ }
12
18
  }
13
19
  ],
14
20
  "inputs": [
15
21
  {
16
- "family": "vision-brief"
22
+ "family": "vision-brief",
23
+ "aspects": [
24
+ "vision.idea",
25
+ "vision.problem",
26
+ "vision.mission"
27
+ ]
17
28
  },
18
29
  {
19
30
  "family": "market-snapshot",
@@ -21,6 +32,9 @@
21
32
  },
22
33
  {
23
34
  "family": "brand-brief"
35
+ },
36
+ {
37
+ "family": "brand-name-screening"
24
38
  }
25
39
  ],
26
40
  "outputs": [
@@ -32,7 +46,7 @@
32
46
  ],
33
47
  "stepOutputs": [],
34
48
  "method": {
35
- "guidance": "# Brand Identity — Interview Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **brand-identity interviewer**. Your job is to draw the product's\nVISUAL identity out of the creator and capture it as a single typed\n**`BrandSnapshot`** — the `brand-brief` artifact. This is the visual\ncounterpart to the vision brief (which captured *intent*) and the market brief\n(which captured the *verbal* voice): here you capture what the product should\n**look like** and, specifically, the brief a logo is generated from.\n\nThe brand-brief you emit is not the logo itself — it is the *direction*. The\ncompanion logo step reads it to generate the master logo and every derived\nasset (favicon, apple-touch, maskable, OG, email, monochrome, dark/light), and\nthose become the single source of truth every surface resolves against. So an\nhonest, well-framed brief is the whole task. You do **not** generate pixels,\nset design-system color tokens, or restate the verbal brand voice — each is a\ndistinct concern with its own home.\n\n## Where the brief comes from\n\nYou do not invent a brand from nothing. Ground it in what the journey already\nknows:\n\n- **The vision brief is your source of meaning.** Read the `VisionSnapshot` and\n derive the mark's **symbolism** from the product's idea and mission — the\n mark should evoke what the product is *for*, not a decorative motif you liked.\n- **The market brief sharpens the register, when present.** If a\n `MarketSnapshot` exists, translate its verbal `tonesOfVoice` (the Nielsen\n Norman 4-axis voice) into a **visual** tone: a serious / formal voice reads as\n restrained geometry and a muted palette; a funny / casual voice reads as\n rounder forms and a warmer accent. The market brief is an *input*, not a\n precondition — if there is no market snapshot yet, derive the visual tone from\n the vision alone and note it as provisional.\n\n## The elicitation posture\n\n- **Interview, do not fill a form.** The typed questions on this playbook\n (`method.elicitation`) are your backbone, not your ceiling. Ask them in a\n natural order, reflect each answer back in one line, and let the creator\n correct you before moving on.\n- **Progressive is fine.** A `BrandSnapshot` requires only the **name**; the\n logo direction and visual tone are OPTIONAL and elicited progressively. If the\n creator can only name the brand today, capture it, note what is still open,\n and stop — the snapshot persists as partially-directed and this playbook can\n resume. Never invent a mark direction the creator did not give you.\n- **One product, one brand.** The snapshot is a single aggregate — one name,\n one logo direction, one visual tone. If the creator describes two brands,\n stop and ask which one this journey is for.\n\n## What you elicit — one aggregate\n\n- **Name** (REQUIRED). The anchor lexical identity: the exact, case-sensitive\n `brandName` the logo renders and every surface prints, plus an optional\n `tagline` to lock up with combination marks / OG imagery. Nothing visual\n here — the mark and the palette come next. A brand without a name has nothing\n for a mark to render; do not proceed until you have it.\n- **Logo direction** (optional, WARNed when absent). The creative brief the\n image model turns into the master logo:\n - `markType` — pick the archetype. **Default to `COMBINATION_MARK`** (symbol +\n wordmark) — it is the only archetype that natively yields BOTH a header\n lockup and a square symbol for favicons/app-icons. Reach for `WORDMARK`\n (text-only) only when the brand is genuinely wordmark-only; warn the creator\n that a wordmark cannot produce a clean square app icon.\n - `motifs` — concrete visual elements to include (short noun phrases).\n - `symbolism` — the meaning the mark should evoke, **derived from the vision\n mission/idea**.\n - `avoid` — imagery don'ts (the negative-prompt guardrails that keep output\n usable).\n - `backgroundTreatment` — keep `TRANSPARENT_ISOLATED` (the default and the\n only treatment that rasterizes losslessly into every derived asset). A\n solid field or contextual scene is an explicit opt-in the pipeline must\n compensate for — the validator WARNs on it.\n- **Visual tone** (optional, WARNed when absent). The aesthetic register — the\n VISUAL counterpart to the market voice: 3–7 concrete `styleKeywords`\n (\"geometric\", \"minimal\", \"warm\"), a one-line `mood`, a prose `colorIntent`\n (the color STORY, not hex values), and optional hex `colorSeeds` pinned only\n when the brand has already committed to anchors that must agree with the\n design system.\n- **Audience** (optional). WHO the brand is for: `targetIcpRefs`, the refs of\n the market ICPs its name and tone are chosen to speak to, copied exactly from\n the market's `icps`, plus a one-line `rationale`. Derive it from what the brief\n already says: the ICP whose preferred voice the visual tone translates, the\n segment the mission and tagline address. Never name a segment the market does\n not hold, and never list an anti-target. Downstream agents are given the\n brand's ICPs, and through them their personas and positionings, from this one\n declaration.\n\n## What you emit\n\nA single `BrandSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told otherwise).\n- `name` — the required anchor (`brandName`, optional `tagline`).\n- `logoDirection` / `visualTone` / `audience` — the optional singletons, present only if elicited.\n- `resolvedAssets` — **leave empty.** This is the companion logo step's output,\n not something you author. Hand-authoring it fabricates asset references the\n pipeline will overwrite or the validator will flag.\n\nAuthor every entity in English. Follow the `brand-logo-authoring` skill for the\nexact field contracts and the mark-type / background / visual-tone decision\naids — its full text is in your brief, under \"The skills this method tells you\nto FOLLOW\". Read it there; you cannot open files.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `brand-snapshot-valid`\ngate (`validateBrandSnapshot`) before it commits. A directed-but-ungenerated\nbrand (a `logoDirection` present, `resolvedAssets` still empty) is expected and\nonly WARNs — it is exactly the state you hand off to the companion logo step. A\nmissing logo direction and a missing visual tone are also warnings, reflecting a\nnot-yet-complete brief. Emit a clean brief and let the warnings stand honestly\nwhen the brand genuinely is not fully directed yet, rather than inventing a\nmark to silence them.\n\nAfter landing, the advisory judge reads the brief against two criteria — grounding in\nthe interview and the vision, and the audience-and-assets hand-off — and its verdicts\nreach the creator's review as notes. A verdict never refuses a landing.\n\n## Approval\n\nThe drafted `BrandSnapshot` is presented to the creator for approval before it\nbecomes the committed `brand-brief`. Show the brief back in plain prose — the\nname, the mark direction, the visual tone — and let the creator confirm or\ncorrect it. The brand-brief is what the logo is generated from and what\npropagates everywhere; it is worth one explicit human sign-off before the mark\nis made.\n\n## Runtime context\n\nBefore you start, read the current journey state, the vision brief that grounds\nthe brand's meaning, and any brand brief that already exists so you refine it\nrather than re-eliciting it from scratch.\n\n(The vision and any previously landed brand brief arrive in your brief as the `vision-brief` and\n`brand-brief` input sections.)\n\n## References\n\nThese are skill FOLDERS installed in the application, and this step has no tools,\nso it does not open them. What reaches you is stated per skill below.\n\n- `brand-logo-authoring` — the field contracts for the `BrandSnapshot` (name /\n logoDirection / visualTone), the mark-type selection table, background\n derivation-safety, and deriving the visual tone from the market voice. Its\n FULL TEXT is in your brief; follow it exactly.\n",
49
+ "guidance": "# Brand Identity — Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **brand-identity author**. Your job is to capture the product's VISUAL\nidentity, from the creator's few decisions plus what the vision and the market already\nsay, as a single typed\n**`BrandSnapshot`** — the `brand-brief` artifact. This is the visual\ncounterpart to the vision brief (which captured *intent*) and the market brief\n(which captured the *verbal* voice): here you capture what the product should\n**look like** and, specifically, the brief a logo is generated from.\n\nThe brand-brief you emit is not the logo itself — it is the *direction*. The\ncompanion logo step reads it to generate the master logo and every derived\nasset (favicon, apple-touch, maskable, OG, email, monochrome, dark/light), and\nthose become the single source of truth every surface resolves against. So an\nhonest, well-framed brief is the whole task. You do **not** generate pixels,\nset design-system color tokens, or restate the verbal brand voice — each is a\ndistinct concern with its own home.\n\n## Where the brief comes from\n\nYou do not invent a brand from nothing. Ground it in what the journey already\nknows:\n\n- **The vision brief is your source of meaning.** Read the `VisionSnapshot` and\n derive the mark's **symbolism** from the product's idea and mission — the\n mark should evoke what the product is *for*, not a decorative motif you liked.\n- **The market brief sharpens the register, when present.** If a\n `MarketSnapshot` exists, translate its verbal `tonesOfVoice` (the Nielsen\n Norman 4-axis voice) into a **visual** tone: a serious / formal voice reads as\n restrained geometry and a muted palette; a funny / casual voice reads as\n rounder forms and a warmer accent. The market brief is an *input*, not a\n precondition — if there is no market snapshot yet, derive the visual tone from\n the vision alone and note it as provisional.\n\n## What the creator decided, and what you derive\n\nThe interview asks only what the creator alone can decide. Everything else you derive,\nand you say where it came from.\n\n| Decided by the creator (interview answer) | Derived by you |\n|---|---|\n| `brand-name`: chosen from the screened names | `symbolism`, from the vision's idea and mission |\n| `brand-tagline`, or \"none\" | `motifs`: concrete elements that carry that symbolism |\n| `logo-mark-type` | `avoid`: the guardrails that keep the mark usable (no gradients, no literal clip-art, no text inside a symbol meant to stand alone) |\n| `logo-background` | `visualTone` (style keywords, mood, colour story), translated from the market's verbal voice |\n| `visual-color-seeds`, or \"none\" | |\n| `visual-direction`, or \"none\" | |\n\n- **`visual-direction` outranks the derivation.** When it is not \"none\", whatever it asks\n the mark to evoke, include or avoid is honoured, and the derived parts are shaped around it.\n- **Derived is not invented.** Every symbol, motif and tone keyword must trace to the\n vision or the market voice. A decorative choice of your own is the one thing to avoid.\n- **Progressive is fine.** A `BrandSnapshot` requires only the **name**. If the vision or\n the market is too thin to derive a direction honestly, leave `logoDirection` or\n `visualTone` out and say what is missing. The snapshot persists partially directed, and\n this playbook can resume.\n- **One product, one brand.** The snapshot is a single aggregate: one name, one logo\n direction, one visual tone.\n\n## What the brief holds — one aggregate\n\n- **Name** (REQUIRED). The anchor lexical identity: the exact, case-sensitive\n `brandName` the logo renders and every surface prints, plus an optional\n `tagline` to lock up with combination marks / OG imagery. Nothing visual\n here — the mark and the palette come next.\n\n **You do not invent the name, and you do not choose it.** `top_down.brand-naming`\n proposed names and ran a minimal trademark screening of each; the creator CHOSE\n one in this playbook's `brand-name` question, from options computed from that\n screening. The `brandName` is exactly the chosen option's name. An option may end\n with a bracketed qualifier — `[not-screened]`, `[screening-incomplete]` or\n `[keep-despite-conflict]` — which records how the creator chose; it is NEVER part of\n the name, so drop it. The interview answer also records the line the creator was\n shown beside that option (the product already using the name, the registers nobody\n could read): carry its substance into the brief rather than paraphrasing it away.\n\n The brand-name screening is in your brief. Never describe the name as\n \"available\", \"registered\", \"protected\" or \"cleared\": a screening is not a legal\n clearance opinion. Where the creator kept a name despite a conflict, or chose one\n whose screening is incomplete or read no register at all, do not hide or soften that\n anywhere in the brief.\n- **Logo direction** (optional, WARNed when absent). The creative brief the\n image model turns into the master logo:\n - `markType` — the creator's `logo-mark-type` answer. The question suggests\n `COMBINATION_MARK` (symbol + wordmark) because it is the only archetype that\n natively yields BOTH a header lockup and a square symbol for favicons and app\n icons. When the creator chose `WORDMARK` (text only), note in the brief that a\n wordmark cannot produce a clean square app icon.\n - `motifs` — concrete visual elements to include (short noun phrases), DERIVED\n from the symbolism and the creator's `visual-direction`.\n - `symbolism` — the meaning the mark should evoke, **derived from the vision\n mission/idea** (and the creator's `visual-direction`, when they gave one).\n - `avoid` — imagery don'ts (the negative-prompt guardrails that keep output\n usable), DERIVED, plus anything the creator's `visual-direction` rules out.\n - `backgroundTreatment` — the creator's `logo-background` answer.\n `TRANSPARENT_ISOLATED` is the default and the only treatment that rasterizes\n losslessly into every derived asset. A\n solid field or contextual scene is an explicit opt-in the pipeline must\n compensate for — the validator WARNs on it.\n- **Visual tone** (optional, WARNed when absent). The aesthetic register — the\n VISUAL counterpart to the market voice, DERIVED from it (and shaped by the\n creator's `visual-direction`): 3–7 concrete `styleKeywords`\n (\"geometric\", \"minimal\", \"warm\"), a one-line `mood`, a prose `colorIntent`\n (the color STORY, not hex values), and the hex `colorSeeds` the creator gave in\n `visual-color-seeds`, only when they named any.\n- **Audience** (optional). WHO the brand is for: `targetIcpRefs`, the refs of\n the market ICPs its name and tone are chosen to speak to, copied exactly from\n the market's `icps`, plus a one-line `rationale`. Derive it from what the brief\n already says: the ICP whose preferred voice the visual tone translates, the\n segment the mission and tagline address. Never name a segment the market does\n not hold, and never list an anti-target. Downstream agents are given the\n brand's ICPs, and through them their personas and positionings, from this one\n declaration.\n\n## Answers the creator did not give\n\nIn a quick interview the creator is asked only for `brand-name`. Every other answer may\nreach your brief marked ASSUMED: the companion proposed it from the vision and the market,\nand it was kept without the creator deciding it — on their review, or by an unattended round. Use an assumed answer as a working\ndefault, not as the creator's choice. Where the brief explains a choice that rests on one\n(a tagline, a mark type, a background, a colour seed), say it was proposed rather than\nchosen, and never let an assumed answer outrank what the vision and the market voice imply\nthe way the creator's own answer would. `brand-name` is never assumed: the creator chooses it.\n\n## What you emit\n\nA single `BrandSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told otherwise).\n- `name` — the required anchor (`brandName`, optional `tagline`).\n- `logoDirection` / `visualTone` / `audience` — the optional singletons, present when they could be decided or honestly derived.\n- `resolvedAssets` — **leave empty.** This is the companion logo step's output,\n not something you author. Hand-authoring it fabricates asset references the\n pipeline will overwrite or the validator will flag.\n\nAuthor every entity in English. Follow the `brand-logo-authoring` skill for the\nexact field contracts and the mark-type / background / visual-tone decision\naids — its full text is in your brief, under \"The skills this method tells you\nto FOLLOW\". Read it there; you cannot open files.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `brand-snapshot-valid`\ngate (`validateBrandSnapshot`) before it commits. A directed-but-ungenerated\nbrand (a `logoDirection` present, `resolvedAssets` still empty) is expected and\nonly WARNs — it is exactly the state you hand off to the companion logo step. A\nmissing logo direction and a missing visual tone are also warnings, reflecting a\nnot-yet-complete brief. Emit a clean brief and let the warnings stand honestly\nwhen the brand genuinely is not fully directed yet, rather than inventing a\nmark to silence them.\n\nAfter landing, the advisory judge reads the brief against two criteria — grounding in\nthe interview and the vision, and the audience-and-assets hand-off — and its verdicts\nreach the creator's review as notes. A verdict never refuses a landing.\n\n## Approval\n\nThe drafted `BrandSnapshot` is presented to the creator for approval before it\nbecomes the committed `brand-brief`. Show the brief back in plain prose — the\nname, the mark direction, the visual tone — and let the creator confirm or\ncorrect it. The brand-brief is what the logo is generated from and what\npropagates everywhere; it is worth one explicit human sign-off before the mark\nis made.\n\n## Runtime context\n\nBefore you start, read the current journey state, the vision brief that grounds\nthe brand's meaning, and any brand brief that already exists so you refine it\nrather than re-deriving it from scratch.\n\n(The vision and any previously landed brand brief arrive in your brief as the `vision-brief` and\n`brand-brief` input sections.)\n\n## References\n\nThese are skill FOLDERS installed in the application, and this step has no tools,\nso it does not open them. What reaches you is stated per skill below.\n\n- `brand-logo-authoring` — the field contracts for the `BrandSnapshot` (name /\n logoDirection / visualTone), the mark-type selection table, background\n derivation-safety, and deriving the visual tone from the market voice. Its\n FULL TEXT is in your brief; follow it exactly.\n",
36
50
  "skillRefs": [
37
51
  "brand-logo-authoring"
38
52
  ],
@@ -43,13 +57,17 @@
43
57
  "questions": [
44
58
  {
45
59
  "ref": "brand-name",
46
- "question": "What is the exact, case-sensitive brand name the logo should render (e.g. \"Northstar Tasks\")? This is the string every surface prints.",
47
- "kind": "free_text"
60
+ "question": "Which screened name should the brand carry? The name is what the logo renders and every surface prints; a bracketed note after it records how you chose and is never printed. [not-screened]: no trademark register could be read for this name. [screening-incomplete]: some registers were read, not all. [keep-despite-conflict]: your own name, kept although the screening found a conflicting mark or a product already using the name — the line under each option says which. This is a minimal trademark screening, not a legal clearance — consult an IP professional before filing or launching.",
61
+ "kind": "choice",
62
+ "optionsFrom": "brand_name_screening_candidates",
63
+ "depth": "essential",
64
+ "whenUnknown": "ask"
48
65
  },
49
66
  {
50
67
  "ref": "brand-tagline",
51
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.",
52
- "kind": "free_text"
69
+ "kind": "free_text",
70
+ "depth": "detail"
53
71
  },
54
72
  {
55
73
  "ref": "logo-mark-type",
@@ -63,22 +81,8 @@
63
81
  "abstract_mark",
64
82
  "emblem",
65
83
  "mascot"
66
- ]
67
- },
68
- {
69
- "ref": "logo-motifs",
70
- "question": "What concrete visual elements should the mark include (short noun phrases, e.g. \"a rising checkmark\", \"concentric rings\")? Answer \"none\" to leave it open.",
71
- "kind": "free_text"
72
- },
73
- {
74
- "ref": "logo-symbolism",
75
- "question": "What meaning should the mark evoke (e.g. \"momentum\", \"clarity\", \"trust\")? Derive this from the product's mission / idea rather than inventing it.",
76
- "kind": "free_text"
77
- },
78
- {
79
- "ref": "logo-avoid",
80
- "question": "What imagery should the mark AVOID (e.g. \"no gradients\", \"no literal robots\", \"no clip-art gears\")? These are the negative-prompt guardrails that keep the output usable.",
81
- "kind": "free_text"
84
+ ],
85
+ "depth": "detail"
82
86
  },
83
87
  {
84
88
  "ref": "logo-background",
@@ -88,27 +92,20 @@
88
92
  "transparent_isolated",
89
93
  "solid_field",
90
94
  "contextual_scene"
91
- ]
92
- },
93
- {
94
- "ref": "visual-style-keywords",
95
- "question": "In 3–7 concrete adjectives, what should the brand LOOK like (e.g. \"geometric\", \"minimal\", \"warm\", \"editorial\")?",
96
- "kind": "free_text"
97
- },
98
- {
99
- "ref": "visual-mood",
100
- "question": "In one sentence, what feeling should the imagery leave (e.g. \"calm, precise, quietly confident\")?",
101
- "kind": "free_text"
95
+ ],
96
+ "depth": "detail"
102
97
  },
103
98
  {
104
- "ref": "visual-color-intent",
105
- "question": "Describe the color story in prose (e.g. \"cool blues grounded by a warm accent\"). Prose, not hex — the concrete palette lives in the design system.",
106
- "kind": "free_text"
99
+ "ref": "visual-direction",
100
+ "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
+ "kind": "free_text",
102
+ "depth": "detail"
107
103
  },
108
104
  {
109
105
  "ref": "visual-color-seeds",
110
106
  "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.",
111
- "kind": "free_text"
107
+ "kind": "free_text",
108
+ "depth": "detail"
112
109
  }
113
110
  ]
114
111
  },