@wildo-ai/framework-knowledge 1.1.9 → 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 (376) 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/expert-personas-and-deliberations.md +26 -7
  5. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +4 -2
  6. package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +4 -2
  7. package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +9 -3
  8. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  9. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  10. package/dist/esm/framework-knowledge.definitions.js +84 -4
  11. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  12. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  13. package/dist/esm/index.d.ts.map +1 -1
  14. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
  15. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  16. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
  17. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  18. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  19. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +39 -1
  20. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  21. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +132 -20
  22. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  23. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +8 -4
  25. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +13 -6
  27. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +2 -1
  29. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +85 -8
  31. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  32. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +4 -3
  33. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +4 -3
  35. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  36. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +12 -3
  37. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +8 -4
  39. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +4 -1
  41. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +2 -1
  43. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  44. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
  45. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
  47. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
  48. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  49. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
  50. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  51. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -1
  52. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  53. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
  54. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
  55. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +2 -2
  56. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  57. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +10 -4
  58. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  59. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +2 -1
  60. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -1
  61. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +5 -3
  62. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
  63. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +2 -1
  64. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
  65. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +11 -9
  66. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
  67. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +17 -3
  68. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
  69. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +19 -2
  70. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
  71. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  72. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  73. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  74. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  75. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  76. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  77. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  78. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  79. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +27 -6
  80. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
  81. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +32 -12
  82. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  83. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
  84. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  85. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  86. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  87. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -1
  88. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  89. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +13 -5
  90. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  91. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  92. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +38 -3
  93. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  94. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -1
  95. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  96. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +23 -8
  97. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  98. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
  99. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  100. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  101. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  102. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +11 -0
  103. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  104. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  105. package/dist/knowledge/manifest.json +7 -7
  106. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +1 -1
  107. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  108. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  109. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +149 -11
  110. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +40 -2
  111. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +55 -0
  112. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +1 -1
  113. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +10 -2
  114. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
  115. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
  116. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +107 -11
  117. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +4 -2
  118. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +28 -6
  119. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +5 -4
  120. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +50 -0
  121. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +16 -4
  122. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +19 -0
  123. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +5 -2
  124. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +2 -1
  125. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  126. package/dist/knowledge/playbooks/refinement.document-facts/method.md +8 -0
  127. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +3 -2
  128. package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +5 -2
  129. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +1 -1
  130. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  131. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  132. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +7 -3
  133. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +3 -3
  134. package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +56 -16
  135. package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +6 -4
  136. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -1
  137. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -1
  138. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +30 -9
  139. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +5 -3
  140. package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +12 -1
  141. package/dist/knowledge/playbooks/top_down.capability-map/method.md +10 -9
  142. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -1
  143. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +16 -2
  144. package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +5 -2
  145. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -1
  146. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-protocol.json +1 -1
  147. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-treatment.json +1 -1
  148. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +26 -0
  149. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +4 -2
  150. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  151. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  152. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +1 -1
  153. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-protocol.json +1 -1
  154. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-treatment.json +1 -1
  155. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +84 -9
  156. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +6 -3
  157. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +19 -0
  158. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +19 -1
  159. package/dist/knowledge/references/brand.name-choice.config.md +20 -3
  160. package/dist/knowledge/references/brand.name-screening.config.md +58 -3
  161. package/dist/knowledge/references/build-plan.task-graph.config.md +55 -0
  162. package/dist/knowledge/references/companion.market.prompt-renderer.md +11 -6
  163. package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +44 -0
  164. package/dist/knowledge/references/example.backend.custom-operation.audit-event.md +81 -0
  165. package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +258 -0
  166. package/dist/knowledge/references/example.backend.custom-operation.computed-total.md +153 -0
  167. package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +107 -0
  168. package/dist/knowledge/references/example.data-seeding.minimal.md +10 -9
  169. package/dist/knowledge/references/example.data-seeding.row-reference.md +80 -0
  170. package/dist/knowledge/references/example.email.template.minimal.md +1 -1
  171. package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +74 -0
  172. package/dist/knowledge/references/example.resource.personal-data.free-text-field.md +19 -0
  173. package/dist/knowledge/references/example.resource.personal-data.person-without-account.md +27 -0
  174. package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +152 -0
  175. package/dist/knowledge/references/example.resource.ui-behavior.filter-presets.md +15 -0
  176. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +8 -0
  177. package/dist/knowledge/references/example.views.app-level.home-definition.md +13 -0
  178. package/dist/knowledge/references/example.views.chart-definition.shared.md +83 -0
  179. package/dist/knowledge/references/experience-plan.config.md +60 -7
  180. package/dist/knowledge/references/market.context-block.builder.md +1 -1
  181. package/dist/knowledge/references/placement-plan.config.md +43 -0
  182. package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -2
  183. package/dist/knowledge/references/requirements.non-functional-requirement.config.md +2 -0
  184. package/dist/knowledge/references/requirements.references.conventions.md +1 -1
  185. package/dist/knowledge/references/requirements.snapshot.config.md +57 -1
  186. package/dist/knowledge/references/requirements.snapshot.validation.md +35 -1
  187. package/dist/knowledge/references/saas.backend.audit-logs.log-event.md +63 -0
  188. package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +60 -0
  189. package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +156 -0
  190. package/dist/knowledge/references/saas.backend.email.send.md +77 -0
  191. package/dist/knowledge/references/saas.backend.notifications.operation-email-template-ref.md +60 -0
  192. package/dist/knowledge/references/saas.data-seeding.computed-entry.md +43 -0
  193. package/dist/knowledge/references/saas.data-seeding.definition-input.md +8 -2
  194. package/dist/knowledge/references/saas.data-seeding.row-reference.md +93 -0
  195. package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +124 -0
  196. package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +316 -0
  197. package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +106 -0
  198. package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +60 -0
  199. package/dist/knowledge/references/saas.frontend.resource-label-params.md +52 -0
  200. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +47 -18
  201. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -1
  202. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destination-roles.md +25 -0
  203. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +2 -2
  204. package/dist/knowledge/references/saas.models.audit.trail-config.md +45 -0
  205. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +5 -3
  206. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +26 -0
  207. package/dist/knowledge/references/saas.models.roles.definition.md +61 -0
  208. package/dist/knowledge/references/saas.models.roles.organization-defaults.md +97 -0
  209. package/dist/knowledge/references/saas.public-runtime.contract.md +26 -0
  210. package/dist/knowledge/references/saas.website.astro.bridge.md +10 -0
  211. package/dist/knowledge/references/saas.website.astro.label-loader.md +3 -0
  212. package/dist/knowledge/references/saas.website.astro.llms-txt-server.md +14 -1
  213. package/dist/knowledge/references/saas.website.astro.site-context.md +13 -0
  214. package/dist/knowledge/references/saas.website.blog.bridge.md +4 -0
  215. package/dist/knowledge/references/saas.website.config.site-context-loader.md +3 -0
  216. package/dist/knowledge/references/saas.website.legal.public-document-links.md +76 -0
  217. package/dist/knowledge/references/saas.website.root-config.seo.md +2 -1
  218. package/dist/knowledge/references/saas.website.runtime.context.md +7 -0
  219. package/dist/knowledge/references/saas.website.seo.llms-txt-config.md +2 -0
  220. package/dist/knowledge/references/website-plan.config.md +26 -0
  221. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +13 -0
  222. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +7 -0
  223. package/dist/knowledge/references/zod.decorators.document-sequence.md +65 -0
  224. package/dist/knowledge/references/zod.decorators.schema-metadata.md +1 -0
  225. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +21 -0
  226. package/dist/knowledge/references/zod.factories.bigdecimal.md +1 -0
  227. package/dist/knowledge/references/zod.factories.code.md +1 -0
  228. package/dist/knowledge/references/zod.factories.duration.md +1 -0
  229. package/dist/knowledge/references/zod.factories.money.md +1 -0
  230. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  231. package/dist/knowledge/registries/framework-topics.json +337 -1
  232. package/dist/knowledge/registries/playbooks.json +18 -18
  233. package/dist/knowledge/registries/source-tags.json +1435 -873
  234. package/dist/knowledge/rules/live-context-door.md +1 -1
  235. package/dist/knowledge/skills/INDEX.md +3 -1
  236. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +16 -3
  237. package/dist/knowledge/skills/application-database-migrations/SKILL.md +14 -3
  238. package/dist/knowledge/skills/application-roles-authoring/SKILL.md +158 -0
  239. package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +169 -0
  240. package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +63 -0
  241. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +6 -1
  242. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +256 -9
  243. package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +42 -0
  244. package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +220 -0
  245. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +5 -0
  246. package/dist/knowledge/skills/brand-name-screening/SKILL.md +33 -9
  247. package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +78 -6
  248. package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +30 -8
  249. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +2 -1
  250. package/dist/knowledge/skills/config-app-shell/SKILL.md +58 -5
  251. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +461 -0
  252. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +80 -0
  253. package/dist/knowledge/skills/config-design-system/SKILL.md +28 -6
  254. package/dist/knowledge/skills/config-navigation/SKILL.md +14 -3
  255. package/dist/knowledge/skills/config-saas/SKILL.md +25 -11
  256. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +51 -1
  257. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +62 -2
  258. package/dist/knowledge/skills/config-saas-backend/SKILL.md +6 -1
  259. package/dist/knowledge/skills/configure-billing/SKILL.md +18 -4
  260. package/dist/knowledge/skills/email-add-template/SKILL.md +27 -5
  261. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +1 -1
  262. package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +128 -0
  263. package/dist/knowledge/skills/email-add-template/references/framework-operation-email-template-ref-api.md +99 -0
  264. package/dist/knowledge/skills/engine-component-registration/SKILL.md +6 -1
  265. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +21 -8
  266. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -2
  267. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +18 -4
  268. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +11 -3
  269. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +2 -1
  270. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +8 -0
  271. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +18 -4
  272. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +10 -2
  273. package/dist/knowledge/skills/infra-environment-config/SKILL.md +6 -1
  274. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +6 -1
  275. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +10 -2
  276. package/dist/knowledge/skills/market-alternatives/SKILL.md +10 -2
  277. package/dist/knowledge/skills/market-authoring-overview/SKILL.md +10 -2
  278. package/dist/knowledge/skills/market-category/SKILL.md +21 -7
  279. package/dist/knowledge/skills/market-channels/SKILL.md +6 -1
  280. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +11 -3
  281. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +1 -1
  282. package/dist/knowledge/skills/market-generation-cli/SKILL.md +21 -11
  283. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +11 -6
  284. package/dist/knowledge/skills/market-icp/SKILL.md +10 -2
  285. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +6 -1
  286. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +6 -1
  287. package/dist/knowledge/skills/market-persona/SKILL.md +14 -3
  288. package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +6 -1
  289. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +10 -2
  290. package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +6 -1
  291. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +14 -3
  292. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +6 -1
  293. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +26 -0
  294. package/dist/knowledge/skills/module-companion-exports/SKILL.md +7 -1
  295. package/dist/knowledge/skills/module-relationships/SKILL.md +31 -4
  296. package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +4 -2
  297. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +14 -3
  298. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +6 -1
  299. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +14 -3
  300. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +10 -2
  301. package/dist/knowledge/skills/resource-add-field/SKILL.md +10 -2
  302. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +46 -17
  303. package/dist/knowledge/skills/resource-add-resource/SKILL.md +14 -2
  304. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +26 -0
  305. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +29 -3
  306. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +19 -4
  307. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +5 -2
  308. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +103 -0
  309. package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +135 -0
  310. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +26 -0
  311. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +26 -7
  312. package/dist/knowledge/skills/resource-custom-view/SKILL.md +10 -2
  313. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +46 -17
  314. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +2 -2
  315. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +5 -1
  316. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +15 -1
  317. package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +569 -0
  318. package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +358 -0
  319. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +8 -0
  320. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +21 -0
  321. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +7 -2
  322. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +13 -0
  323. package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +153 -0
  324. package/dist/knowledge/skills/resource-status-lifecycle/references/commercial-documents.md +46 -0
  325. package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +198 -0
  326. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +30 -4
  327. package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +157 -0
  328. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +101 -19
  329. package/dist/knowledge/skills/seeding-authoring/SKILL.md +155 -40
  330. package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +67 -0
  331. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +148 -4
  332. package/dist/knowledge/skills/seeding-authoring/references/seed-row-overlay.md +22 -0
  333. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +43 -0
  334. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +2 -2
  335. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +6 -1
  336. package/dist/knowledge/skills/spec-component-update/SKILL.md +10 -2
  337. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +2 -2
  338. package/dist/knowledge/skills/spec-family-update/SKILL.md +71 -66
  339. package/dist/knowledge/skills/spec-family-update/references/family-spec-routing.md +1 -1
  340. package/dist/knowledge/skills/spec-resource-update/SKILL.md +30 -10
  341. package/dist/knowledge/skills/spec-resource-update/references/resource-spec-field-routing.md +28 -0
  342. package/dist/knowledge/skills/spec-update-after-change/SKILL.md +22 -5
  343. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +6 -1
  344. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +10 -2
  345. package/dist/knowledge/skills/views-app-level/SKILL.md +13 -3
  346. package/dist/knowledge/skills/views-app-level/references/application-home.md +56 -0
  347. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +221 -37
  348. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +22 -5
  349. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +1 -1
  350. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +32 -2
  351. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +16 -3
  352. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +4 -0
  353. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +7 -1
  354. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +13 -1
  355. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +10 -2
  356. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +13 -1
  357. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +6 -1
  358. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +19 -1
  359. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +55 -18
  360. package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +98 -0
  361. package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +8 -11
  362. package/dist/knowledge/skills/website-page-authoring/SKILL.md +16 -5
  363. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +3 -0
  364. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +6 -1
  365. package/dist/knowledge/skills/website-section-faq/SKILL.md +6 -1
  366. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +6 -1
  367. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +10 -2
  368. package/dist/knowledge/skills/website-section-hero/SKILL.md +6 -1
  369. package/dist/knowledge/skills/website-section-pricing/SKILL.md +6 -1
  370. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +12 -2
  371. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +15 -3
  372. package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +16 -1
  373. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +2 -1
  374. package/dist/knowledge/topic-index.json +1441 -269
  375. package/dist/tsconfig.build.tsbuildinfo +1 -1
  376. package/package.json +4 -4
@@ -1 +1 @@
1
- {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-brand-brief","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision"],"requirementRef":"application-creation:authority-requirement/brand-identity-result","requirementVersion":1,"riskClassRef":"application-creation:risk/brand-brief-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/brand-identity","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/brand-identity-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/brand-identity","policyVersion":1},"decisionPointRef":"application-creation:decision-point/brand-identity-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/brand-identity-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/brand-identity","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/brand-brief-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-brand-brief-change","triggerRefs":["application-creation:trigger/brand-brief-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-brand-identity-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision"],"hardFloorRef":"application-creation:hard-floor/brand-brief-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/brand-identity-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/brand-identity","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-brand-identity-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.audience","brand.asset","market.icp"],"criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1}],"instruction":"Determine whether the brief hands off correctly: every targetIcpRef in the audience names an ICP the market snapshot holds and none is an anti-target; the audience rationale follows from the brief's own tone and mission; and resolvedAssets is EMPTY, because assets are the companion logo step's output and a hand-authored asset reference would be overwritten or flagged.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The audience is absent although the market snapshot names ICPs the tone was chosen for, or the rationale is generic.","GAP":"An audience ref naming an ICP the market does not hold or an anti-target, or a resolvedAssets entry authored by hand.","INDETERMINATE":"The market snapshot's ICPs are not in evidence, so the audience cannot be checked.","PASS":"Every audience ref resolves to a market ICP that is not an anti-target, and resolvedAssets is empty."}},{"assessesAspects":["brand.name","brand.logo-direction","brand.visual-tone","vision.idea","vision.mission"],"criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1}],"instruction":"Determine whether the brand brief is GROUNDED: the brand name is exactly the name the creator chose in the interview (an option may carry a bracketed qualifier such as [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 screening-incomplete or kept despite a conflict, and the brief says so plainly.","GAP":"The name is not among the screened candidates, an unchecked or conflicting name is presented as clear, or the brief asserts availability or legal clearance.","INDETERMINATE":"The brand-name screening is not in evidence, so the name's standing cannot be checked.","PASS":"The name is a screened candidate covered in every declared jurisdiction and class, and the brief claims no availability or clearance."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-identity","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-identity"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/brand-identity","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-market-and-brand-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-market-and-brand-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-name-screened-and-unclaimed","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/brand-name-screening-and-brand-candidate"}],"schemaVersion":1}
1
+ {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-brand-brief","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision"],"requirementRef":"application-creation:authority-requirement/brand-identity-result","requirementVersion":1,"riskClassRef":"application-creation:risk/brand-brief-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/brand-identity","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/brand-identity-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/brand-identity","policyVersion":1},"decisionPointRef":"application-creation:decision-point/brand-identity-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/brand-identity-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/brand-identity","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/brand-brief-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-brand-brief-change","triggerRefs":["application-creation:trigger/brand-brief-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-brand-identity-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision"],"hardFloorRef":"application-creation:hard-floor/brand-brief-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/brand-identity-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/brand-identity","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-brand-identity-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.audience","brand.asset","market.icp"],"criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1}],"instruction":"Determine whether the brief hands off correctly: every targetIcpRef in the audience names an ICP the market snapshot holds and none is an anti-target; the audience rationale follows from the brief's own tone and mission; and resolvedAssets is EMPTY, because assets are the companion logo step's output and a hand-authored asset reference would be overwritten or flagged.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The audience is absent although the market snapshot names ICPs the tone was chosen for, or the rationale is generic.","GAP":"An audience ref naming an ICP the market does not hold or an anti-target, or a resolvedAssets entry authored by hand.","INDETERMINATE":"The market snapshot's ICPs are not in evidence, so the audience cannot be checked.","PASS":"Every audience ref resolves to a market ICP that is not an anti-target, and resolvedAssets is empty."}},{"assessesAspects":["brand.name","brand.logo-direction","brand.visual-tone","vision.idea","vision.mission"],"criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","criterionVersion":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}
@@ -88,13 +88,17 @@ and you say where it came from.
88
88
  proposed names and ran a minimal trademark screening of each; the creator CHOSE
89
89
  one in this playbook's `brand-name` question, from options computed from that
90
90
  screening. The `brandName` is exactly the chosen option's name. An option may end
91
- with a bracketed qualifier — `[screening-incomplete]` or `[keep-despite-conflict]`
92
- — which records how the creator chose; it is NEVER part of the name, so drop it.
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.
93
96
 
94
97
  The brand-name screening is in your brief. Never describe the name as
95
98
  "available", "registered", "protected" or "cleared": a screening is not a legal
96
99
  clearance opinion. Where the creator kept a name despite a conflict, or chose one
97
- whose screening is incomplete, do not hide or soften that anywhere in the brief.
100
+ whose screening is incomplete or read no register at all, do not hide or soften that
101
+ anywhere in the brief.
98
102
  - **Logo direction** (optional, WARNed when absent). The creative brief the
99
103
  image model turns into the master logo:
100
104
  - `markType` — the creator's `logo-mark-type` answer. The question suggests
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "top_down.brand-identity",
3
- "version": "0.3.0",
3
+ "version": "0.4.0",
4
4
  "phase": "top_down",
5
5
  "intent": "Brand-identity elicitation: draw the product's VISUAL identity out of the creator — the brand name (CHOSEN by the creator from the screened candidates `top_down.brand-naming` landed), the logo creative direction (mark type, motifs, symbolism, imagery don'ts, background), and the visual tone (style keywords, mood, color story) — and capture it as a single validated BrandSnapshot (the `brand-brief` artifact family). The visual counterpart to the vision (intent) and market (verbal voice) briefs: it derives symbolism from the VisionSnapshot's idea/mission and, when a MarketSnapshot exists, translates its verbal `tonesOfVoice` into a visual register. The emitted brand-brief is the INPUT the companion logo step generates the master logo + derived assets from, and via `BrandSnapshot.resolvedAssets` the single source of truth every logo/favicon/brand-image consumer resolves against. Progressive: may persist a partially-directed brand (logoDirection/visualTone optional) and resume. v1 scaffold methodology — iterate the interview.",
6
6
  "preconditions": [
@@ -46,7 +46,7 @@
46
46
  ],
47
47
  "stepOutputs": [],
48
48
  "method": {
49
- "guidance": "# Brand Identity — Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **brand-identity author**. Your job is to capture the product's VISUAL\nidentity, from the creator's few decisions plus what the vision and the market already\nsay, as a single typed\n**`BrandSnapshot`** — the `brand-brief` artifact. This is the visual\ncounterpart to the vision brief (which captured *intent*) and the market brief\n(which captured the *verbal* voice): here you capture what the product should\n**look like** and, specifically, the brief a logo is generated from.\n\nThe brand-brief you emit is not the logo itself — it is the *direction*. The\ncompanion logo step reads it to generate the master logo and every derived\nasset (favicon, apple-touch, maskable, OG, email, monochrome, dark/light), and\nthose become the single source of truth every surface resolves against. So an\nhonest, well-framed brief is the whole task. You do **not** generate pixels,\nset design-system color tokens, or restate the verbal brand voice — each is a\ndistinct concern with its own home.\n\n## Where the brief comes from\n\nYou do not invent a brand from nothing. Ground it in what the journey already\nknows:\n\n- **The vision brief is your source of meaning.** Read the `VisionSnapshot` and\n derive the mark's **symbolism** from the product's idea and mission — the\n mark should evoke what the product is *for*, not a decorative motif you liked.\n- **The market brief sharpens the register, when present.** If a\n `MarketSnapshot` exists, translate its verbal `tonesOfVoice` (the Nielsen\n Norman 4-axis voice) into a **visual** tone: a serious / formal voice reads as\n restrained geometry and a muted palette; a funny / casual voice reads as\n rounder forms and a warmer accent. The market brief is an *input*, not a\n precondition — if there is no market snapshot yet, derive the visual tone from\n the vision alone and note it as provisional.\n\n## What the creator decided, and what you derive\n\nThe interview asks only what the creator alone can decide. Everything else you derive,\nand you say where it came from.\n\n| Decided by the creator (interview answer) | Derived by you |\n|---|---|\n| `brand-name`: chosen from the screened names | `symbolism`, from the vision's idea and mission |\n| `brand-tagline`, or \"none\" | `motifs`: concrete elements that carry that symbolism |\n| `logo-mark-type` | `avoid`: the guardrails that keep the mark usable (no gradients, no literal clip-art, no text inside a symbol meant to stand alone) |\n| `logo-background` | `visualTone` (style keywords, mood, colour story), translated from the market's verbal voice |\n| `visual-color-seeds`, or \"none\" | |\n| `visual-direction`, or \"none\" | |\n\n- **`visual-direction` outranks the derivation.** When it is not \"none\", whatever it asks\n the mark to evoke, include or avoid is honoured, and the derived parts are shaped around it.\n- **Derived is not invented.** Every symbol, motif and tone keyword must trace to the\n vision or the market voice. A decorative choice of your own is the one thing to avoid.\n- **Progressive is fine.** A `BrandSnapshot` requires only the **name**. If the vision or\n the market is too thin to derive a direction honestly, leave `logoDirection` or\n `visualTone` out and say what is missing. The snapshot persists partially directed, and\n this playbook can resume.\n- **One product, one brand.** The snapshot is a single aggregate: one name, one logo\n direction, one visual tone.\n\n## What the brief holds — one aggregate\n\n- **Name** (REQUIRED). The anchor lexical identity: the exact, case-sensitive\n `brandName` the logo renders and every surface prints, plus an optional\n `tagline` to lock up with combination marks / OG imagery. Nothing visual\n here — the mark and the palette come next.\n\n **You do not invent the name, and you do not choose it.** `top_down.brand-naming`\n proposed names and ran a minimal trademark screening of each; the creator CHOSE\n one in this playbook's `brand-name` question, from options computed from that\n screening. The `brandName` is exactly the chosen option's name. An option may end\n with a bracketed qualifier — `[screening-incomplete]` or `[keep-despite-conflict]`\n — which records how the creator chose; it is NEVER part of the name, so drop it.\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, do not hide or soften that anywhere in the brief.\n- **Logo direction** (optional, WARNed when absent). The creative brief the\n image model turns into the master logo:\n - `markType` — the creator's `logo-mark-type` answer. The question suggests\n `COMBINATION_MARK` (symbol + wordmark) because it is the only archetype that\n natively yields BOTH a header lockup and a square symbol for favicons and app\n icons. When the creator chose `WORDMARK` (text only), note in the brief that a\n wordmark cannot produce a clean square app icon.\n - `motifs` — concrete visual elements to include (short noun phrases), DERIVED\n from the symbolism and the creator's `visual-direction`.\n - `symbolism` — the meaning the mark should evoke, **derived from the vision\n mission/idea** (and the creator's `visual-direction`, when they gave one).\n - `avoid` — imagery don'ts (the negative-prompt guardrails that keep output\n usable), DERIVED, plus anything the creator's `visual-direction` rules out.\n - `backgroundTreatment` — the creator's `logo-background` answer.\n `TRANSPARENT_ISOLATED` is the default and the only treatment that rasterizes\n losslessly into every derived asset. A\n solid field or contextual scene is an explicit opt-in the pipeline must\n compensate for — the validator WARNs on it.\n- **Visual tone** (optional, WARNed when absent). The aesthetic register — the\n VISUAL counterpart to the market voice, DERIVED from it (and shaped by the\n creator's `visual-direction`): 3–7 concrete `styleKeywords`\n (\"geometric\", \"minimal\", \"warm\"), a one-line `mood`, a prose `colorIntent`\n (the color STORY, not hex values), and the hex `colorSeeds` the creator gave in\n `visual-color-seeds`, only when they named any.\n- **Audience** (optional). WHO the brand is for: `targetIcpRefs`, the refs of\n the market ICPs its name and tone are chosen to speak to, copied exactly from\n the market's `icps`, plus a one-line `rationale`. Derive it from what the brief\n already says: the ICP whose preferred voice the visual tone translates, the\n segment the mission and tagline address. Never name a segment the market does\n not hold, and never list an anti-target. Downstream agents are given the\n brand's ICPs, and through them their personas and positionings, from this one\n declaration.\n\n## Answers the creator did not give\n\nIn a quick interview the creator is asked only for `brand-name`. Every other answer may\nreach your brief marked ASSUMED: the companion proposed it from the vision and the market,\nand it was kept without the creator deciding it — on their review, or by an unattended round. Use an assumed answer as a working\ndefault, not as the creator's choice. Where the brief explains a choice that rests on one\n(a tagline, a mark type, a background, a colour seed), say it was proposed rather than\nchosen, and never let an assumed answer outrank what the vision and the market voice imply\nthe way the creator's own answer would. `brand-name` is never assumed: the creator chooses it.\n\n## What you emit\n\nA single `BrandSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told otherwise).\n- `name` — the required anchor (`brandName`, optional `tagline`).\n- `logoDirection` / `visualTone` / `audience` — the optional singletons, present when they could be decided or honestly derived.\n- `resolvedAssets` — **leave empty.** This is the companion logo step's output,\n not something you author. Hand-authoring it fabricates asset references the\n pipeline will overwrite or the validator will flag.\n\nAuthor every entity in English. Follow the `brand-logo-authoring` skill for the\nexact field contracts and the mark-type / background / visual-tone decision\naids — its full text is in your brief, under \"The skills this method tells you\nto FOLLOW\". Read it there; you cannot open files.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `brand-snapshot-valid`\ngate (`validateBrandSnapshot`) before it commits. A directed-but-ungenerated\nbrand (a `logoDirection` present, `resolvedAssets` still empty) is expected and\nonly WARNs — it is exactly the state you hand off to the companion logo step. A\nmissing logo direction and a missing visual tone are also warnings, reflecting a\nnot-yet-complete brief. Emit a clean brief and let the warnings stand honestly\nwhen the brand genuinely is not fully directed yet, rather than inventing a\nmark to silence them.\n\nAfter landing, the advisory judge reads the brief against two criteria — grounding in\nthe interview and the vision, and the audience-and-assets hand-off — and its verdicts\nreach the creator's review as notes. A verdict never refuses a landing.\n\n## Approval\n\nThe drafted `BrandSnapshot` is presented to the creator for approval before it\nbecomes the committed `brand-brief`. Show the brief back in plain prose — the\nname, the mark direction, the visual tone — and let the creator confirm or\ncorrect it. The brand-brief is what the logo is generated from and what\npropagates everywhere; it is worth one explicit human sign-off before the mark\nis made.\n\n## Runtime context\n\nBefore you start, read the current journey state, the vision brief that grounds\nthe brand's meaning, and any brand brief that already exists so you refine it\nrather than re-deriving it from scratch.\n\n(The vision and any previously landed brand brief arrive in your brief as the `vision-brief` and\n`brand-brief` input sections.)\n\n## References\n\nThese are skill FOLDERS installed in the application, and this step has no tools,\nso it does not open them. What reaches you is stated per skill below.\n\n- `brand-logo-authoring` — the field contracts for the `BrandSnapshot` (name /\n logoDirection / visualTone), the mark-type selection table, background\n derivation-safety, and deriving the visual tone from the market voice. Its\n FULL TEXT is in your brief; follow it exactly.\n",
49
+ "guidance": "# Brand Identity — Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **brand-identity author**. Your job is to capture the product's VISUAL\nidentity, from the creator's few decisions plus what the vision and the market already\nsay, as a single typed\n**`BrandSnapshot`** — the `brand-brief` artifact. This is the visual\ncounterpart to the vision brief (which captured *intent*) and the market brief\n(which captured the *verbal* voice): here you capture what the product should\n**look like** and, specifically, the brief a logo is generated from.\n\nThe brand-brief you emit is not the logo itself — it is the *direction*. The\ncompanion logo step reads it to generate the master logo and every derived\nasset (favicon, apple-touch, maskable, OG, email, monochrome, dark/light), and\nthose become the single source of truth every surface resolves against. So an\nhonest, well-framed brief is the whole task. You do **not** generate pixels,\nset design-system color tokens, or restate the verbal brand voice — each is a\ndistinct concern with its own home.\n\n## Where the brief comes from\n\nYou do not invent a brand from nothing. Ground it in what the journey already\nknows:\n\n- **The vision brief is your source of meaning.** Read the `VisionSnapshot` and\n derive the mark's **symbolism** from the product's idea and mission — the\n mark should evoke what the product is *for*, not a decorative motif you liked.\n- **The market brief sharpens the register, when present.** If a\n `MarketSnapshot` exists, translate its verbal `tonesOfVoice` (the Nielsen\n Norman 4-axis voice) into a **visual** tone: a serious / formal voice reads as\n restrained geometry and a muted palette; a funny / casual voice reads as\n rounder forms and a warmer accent. The market brief is an *input*, not a\n precondition — if there is no market snapshot yet, derive the visual tone from\n the vision alone and note it as provisional.\n\n## What the creator decided, and what you derive\n\nThe interview asks only what the creator alone can decide. Everything else you derive,\nand you say where it came from.\n\n| Decided by the creator (interview answer) | Derived by you |\n|---|---|\n| `brand-name`: chosen from the screened names | `symbolism`, from the vision's idea and mission |\n| `brand-tagline`, or \"none\" | `motifs`: concrete elements that carry that symbolism |\n| `logo-mark-type` | `avoid`: the guardrails that keep the mark usable (no gradients, no literal clip-art, no text inside a symbol meant to stand alone) |\n| `logo-background` | `visualTone` (style keywords, mood, colour story), translated from the market's verbal voice |\n| `visual-color-seeds`, or \"none\" | |\n| `visual-direction`, or \"none\" | |\n\n- **`visual-direction` outranks the derivation.** When it is not \"none\", whatever it asks\n the mark to evoke, include or avoid is honoured, and the derived parts are shaped around it.\n- **Derived is not invented.** Every symbol, motif and tone keyword must trace to the\n vision or the market voice. A decorative choice of your own is the one thing to avoid.\n- **Progressive is fine.** A `BrandSnapshot` requires only the **name**. If the vision or\n the market is too thin to derive a direction honestly, leave `logoDirection` or\n `visualTone` out and say what is missing. The snapshot persists partially directed, and\n this playbook can resume.\n- **One product, one brand.** The snapshot is a single aggregate: one name, one logo\n direction, one visual tone.\n\n## What the brief holds — one aggregate\n\n- **Name** (REQUIRED). The anchor lexical identity: the exact, case-sensitive\n `brandName` the logo renders and every surface prints, plus an optional\n `tagline` to lock up with combination marks / OG imagery. Nothing visual\n here — the mark and the palette come next.\n\n **You do not invent the name, and you do not choose it.** `top_down.brand-naming`\n proposed names and ran a minimal trademark screening of each; the creator CHOSE\n one in this playbook's `brand-name` question, from options computed from that\n screening. The `brandName` is exactly the chosen option's name. An option may end\n with a bracketed qualifier — `[not-screened]`, `[screening-incomplete]` or\n `[keep-despite-conflict]` — which records how the creator chose; it is NEVER part of\n the name, so drop it. The interview answer also records the line the creator was\n shown beside that option (the product already using the name, the registers nobody\n could read): carry its substance into the brief rather than paraphrasing it away.\n\n The brand-name screening is in your brief. Never describe the name as\n \"available\", \"registered\", \"protected\" or \"cleared\": a screening is not a legal\n clearance opinion. Where the creator kept a name despite a conflict, or chose one\n whose screening is incomplete or read no register at all, do not hide or soften that\n anywhere in the brief.\n- **Logo direction** (optional, WARNed when absent). The creative brief the\n image model turns into the master logo:\n - `markType` — the creator's `logo-mark-type` answer. The question suggests\n `COMBINATION_MARK` (symbol + wordmark) because it is the only archetype that\n natively yields BOTH a header lockup and a square symbol for favicons and app\n icons. When the creator chose `WORDMARK` (text only), note in the brief that a\n wordmark cannot produce a clean square app icon.\n - `motifs` — concrete visual elements to include (short noun phrases), DERIVED\n from the symbolism and the creator's `visual-direction`.\n - `symbolism` — the meaning the mark should evoke, **derived from the vision\n mission/idea** (and the creator's `visual-direction`, when they gave one).\n - `avoid` — imagery don'ts (the negative-prompt guardrails that keep output\n usable), DERIVED, plus anything the creator's `visual-direction` rules out.\n - `backgroundTreatment` — the creator's `logo-background` answer.\n `TRANSPARENT_ISOLATED` is the default and the only treatment that rasterizes\n losslessly into every derived asset. A\n solid field or contextual scene is an explicit opt-in the pipeline must\n compensate for — the validator WARNs on it.\n- **Visual tone** (optional, WARNed when absent). The aesthetic register — the\n VISUAL counterpart to the market voice, DERIVED from it (and shaped by the\n creator's `visual-direction`): 3–7 concrete `styleKeywords`\n (\"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",
50
50
  "skillRefs": [
51
51
  "brand-logo-authoring"
52
52
  ],
@@ -57,7 +57,7 @@
57
57
  "questions": [
58
58
  {
59
59
  "ref": "brand-name",
60
- "question": "Which screened name should the brand carry? This exact string is what the logo renders and every surface prints. A name marked [screening-incomplete] could not be checked in every register; [keep-despite-conflict] keeps your own name although the screening found a conflicting mark or competitor. This is a minimal trademark screening, not a legal clearance — consult an IP professional before filing or launching.",
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
61
  "kind": "choice",
62
62
  "optionsFrom": "brand_name_screening_candidates",
63
63
  "depth": "essential",
@@ -43,16 +43,30 @@ Screen each proposal, **and every name the creator listed in the interview**
43
43
 
44
44
  ### Jurisdictions — derive, never assume the EU
45
45
 
46
- From the market snapshot's ICP geographies, the vision's compliance detail, and the
47
- operating jurisdictions the application declares. A region tag ("EMEA") is not a
48
- jurisdiction: name the countries it implies for this product. If any EU member state is
49
- targeted, the **EU trade mark** (`EU`) applies too, because an EUTM has effect in every
50
- member state. International registrations (`WO`) are always in scope.
51
-
52
- ### Registers
53
-
54
- - **EUIPO eSearch plus** (https://euipo.europa.eu/eSearch/) — EU trade marks, and
55
- international registrations designating the EU.
46
+ The UNION of four sources, never one of them alone:
47
+
48
+ - the market snapshot's ICP geographies;
49
+ - the vision's compliance detail;
50
+ - the jurisdictions the application DECLARES it operates in — the declared `operating_jurisdictions` context section of your brief,
51
+ read from its configuration: each declared place is a target;
52
+ - **the creator's own answer about where the product's users are** — the `target-jurisdictions`
53
+ answer in your objective (the same decision as the compliance interview's `jurisdictions`
54
+ question, asked once). When the creator names countries there ("market focus on Germany,
55
+ France, Italy and Spain"), every one of them is a target, whether or not the market snapshot
56
+ evidences it.
57
+
58
+ A region tag ("EMEA") is not a jurisdiction: name the countries it implies for this product. If
59
+ any EU member state is targeted, the **EU trade mark** (`EU`) applies too, because an EUTM has
60
+ effect in every member state. International registrations (`WO`) are always in scope. Where the
61
+ data is HOSTED is not a trademark jurisdiction: a mark is protected where it is used in trade.
62
+
63
+ **Every targeted country gets its own coverage**: a search of its national office (IT → UIBM,
64
+ ES → OEPM, DE → DPMA, FR → INPI, …), or a TMview search that includes that office, recorded with
65
+ that country among the jurisdictions it covers. Say which, per country.
66
+
67
+ ### Registers, and HOW you reach each one
68
+
69
+ - **EUIPO** — EU trade marks, and international registrations designating the EU.
56
70
  - **TMview** (https://www.tmdn.org/tmview/) — the EU office and participating national
57
71
  offices in one search.
58
72
  - **WIPO Global Brand Database** (https://branddb.wipo.int/) — international (Madrid)
@@ -60,6 +74,24 @@ member state. International registrations (`WO`) are always in scope.
60
74
  - **The national office of each targeted country** that TMview or WIPO does not already
61
75
  cover for you (for example the USPTO for the United States, UKIPO for the United Kingdom).
62
76
 
77
+ **Use a register's machine interface, not its web page, wherever one is reachable.** A register's
78
+ web page is built for a person in a browser: on a real run every one of them returned nothing a
79
+ fetch could read (results rendered in the browser, an empty page, a CAPTCHA, an HTTP 403, a search
80
+ form that never ran). A machine interface returns structured records. Today:
81
+
82
+ - **EUIPO** publishes a Trademark Search API, but it needs OAuth credentials from a registered
83
+ developer account. Use it only when the application's providers give you access to it; without
84
+ that, you cannot reach it.
85
+ - **TMview and the WIPO Global Brand Database** publish no machine interface.
86
+ - **A national office** may publish one: use it when its own documentation offers open access.
87
+
88
+ So on most runs the web page is all you have. Try each register ONCE; when it returns nothing
89
+ readable, report it as not checked and move on. Do not spend the run retrying a page that renders
90
+ in the browser.
91
+
92
+ **Report, for every query, how you reached the register**: through its machine interface, or by
93
+ fetching its web page. The landed screening records it, so a reader can tell the two apart.
94
+
63
95
  ### Classes
64
96
 
65
97
  The Nice classes the product lives in: **9** (software) and **42** (software as a service)
@@ -81,17 +113,25 @@ URL), the search URL, and today's date.
81
113
 
82
114
  ## 3. A failure is not an answer
83
115
 
84
- Some registers will not answer you: TMview renders in the browser, and WIPO's database is
85
- behind a CAPTCHA. **When you cannot run a search, or cannot read its result, report that
86
- register as NOT CHECKED, and say why.** Never infer "no conflict" from a search engine,
87
- from silence, or from your own memory of which marks exist. A candidate with a register
88
- not checked is "screening incomplete" — still offered to the creator, never as clear.
116
+ Some registers will not answer you. **When you cannot run a search, or cannot read its result,
117
+ report that register as NOT CHECKED, and say why.** Never infer "no conflict" from a search
118
+ engine, from silence, or from your own memory of which marks exist. A candidate with a register
119
+ not checked is "screening incomplete", and one with NO register read is "not screened" — still
120
+ offered to the creator, never as clear. Each unread search becomes a check the creator can run by
121
+ hand, from a link the companion builds; you do not need to write that link.
89
122
 
90
123
  ## 4. Signals beside the registers (recorded, never blocking)
91
124
 
92
125
  - the exact-match `.com` and the main country-code domains of the target countries,
93
126
  registered or available;
94
- - any company or product already trading under the name in this category, with its URL.
127
+ - any company or product already trading under the name, with its URL, and **how it relates
128
+ to this product's category**: the SAME JOB (the same work for the same kind of customer, or
129
+ the same Nice class of goods and services), an ADJACENT category, or UNRELATED.
130
+
131
+ **A product doing the same job under an identical or near-identical name is a COLLISION, not
132
+ merely a same-category use.** Report it as a collision, beside the competitor collisions, with
133
+ its URL. "Groundwork — Estimating & Job Suite", a quote-to-invoice tool for tradespeople, is a
134
+ collision for a builders' CRM called "Groundwork", although no market snapshot listed it.
95
135
 
96
136
  ## What you must never say
97
137
 
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "top_down.brand-name-research",
3
- "version": "0.1.0",
3
+ "version": "0.2.0",
4
4
  "phase": "top_down",
5
5
  "intent": "Propose candidate names for the product, grounded in the vision and the market snapshot, and run a minimal trademark screening of every candidate — proposed or supplied by the creator — against the public registers of the jurisdictions the product targets, in the Nice classes it lives in, for identical and near-identical live marks, with domain and same-category signals beside them. Returns a condensed, source-attributed brief and authors nothing. Never a legal clearance opinion: a register it could not query is reported as not checked, never as clear.",
6
6
  "preconditions": [
@@ -32,17 +32,19 @@
32
32
  "stepOutputs": [
33
33
  {
34
34
  "ref": "brand-name-evidence",
35
- "condensation": "A brief of at most ~2500 words. First the jurisdictions (each with what declared it) and the Nice classes searched (each with why). Then, per candidate: the exact name, who put it on the list (the companion or the creator), one line on why it fits (proposals only), and for EVERY register query — the register, the jurisdictions it covers, the classes searched, the match types searched (identical, near-identical), the result (no conflict found / conflict / not checked), each live conflicting mark with its owner, number, classes, status and record URL, the search URL and the date. Then any competitor or alternative the market snapshot names that the candidate is identical or close to, the domains checked with their status, and any company already trading under the name in this category. End with what could NOT be checked, and why. Every claim carries the URL it came from; raw page text is never returned.",
35
+ "condensation": "A brief of at most ~2500 words. First the jurisdictions (each with what declared it — the market, the vision, the application's declared operating jurisdictions, or the creator's own target-jurisdictions answer — and, for each targeted country, whether its national office or a TMview search covers it) and the Nice classes searched (each with why). Then, per candidate: the exact name, who put it on the list (the companion or the creator), one line on why it fits (proposals only), and for EVERY register query — the register, how it was reached (its machine interface, or its web page), the jurisdictions it covers, the classes searched, the match types searched (identical, near-identical), the result (no conflict found / conflict / not checked), each live conflicting mark with its owner, number, classes, status and record URL, the search URL and the date. Then any competitor or alternative the market snapshot names that the candidate is identical or close to, every product doing the SAME JOB under an identical or near-identical name (a collision too), the domains checked with their status, and every other company trading under the name with how its category relates (same job, adjacent, unrelated). End with what could NOT be checked, and why. Every claim carries the URL it came from; raw page text is never returned.",
36
36
  "description": "Screened brand-name candidates with per-register results and sources, condensed for the produce sibling."
37
37
  }
38
38
  ],
39
39
  "method": {
40
- "guidance": "# Brand Name Research — propose, then screen\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nYou are the **naming researcher**. You do two things: propose names for this product,\nand run a **minimal trademark screening** of every candidate. You do not choose the name\n— the creator does, from what you bring back — and you author no file.\n\n## 1. Propose (at least five)\n\nGround every proposal in what the application already decided:\n\n- the vision's **idea and mission** — what the product is FOR;\n- the market snapshot's **category language** (the words buyers and competitors use) and\n its **tones of voice** (a serious, formal voice wants a different name from a casual one);\n- the **target geographies and languages** — a name must be pronounceable and inoffensive\n in the target countries' main languages. Check that it carries no unfortunate meaning.\n\nPrefer distinctive names (invented or arbitrary) over descriptive ones. A purely\ndescriptive name (\"Building CRM\") is weak as a mark and usually refused registration.\n\n**A proposal must not be identical or close to any competitor or alternative the market\nsnapshot names**, nor to any name you find trading in the same category. Drop such a name\nbefore screening it; if one slips through, report the collision so it is never offered.\n\nPropose at least five, so at least three survive screening. One line per proposal on\nwhy it fits. That line is what the creator reads first.\n\n## 2. Screen every candidate\n\nScreen each proposal, **and every name the creator listed in the interview**\n(`names-to-screen`, unless it says \"none\"), the same way. Mark the creator's names as theirs.\n\n### Jurisdictions — derive, never assume the EU\n\nFrom the market snapshot's ICP geographies, the vision's compliance detail, and the\noperating jurisdictions the application declares. A region tag (\"EMEA\") is not a\njurisdiction: name the countries it implies for this product. If any EU member state is\ntargeted, the **EU trade mark** (`EU`) applies too, because an EUTM has effect in every\nmember state. International registrations (`WO`) are always in scope.\n\n### Registers\n\n- **EUIPO eSearch plus** (https://euipo.europa.eu/eSearch/) — EU trade marks, and\n international registrations designating the EU.\n- **TMview** (https://www.tmdn.org/tmview/) — the EU office and participating national\n offices in one search.\n- **WIPO Global Brand Database** (https://branddb.wipo.int/) — international (Madrid)\n registrations and many national collections.\n- **The national office of each targeted country** that TMview or WIPO does not already\n cover for you (for example the USPTO for the United States, UKIPO for the United Kingdom).\n\n### Classes\n\nThe Nice classes the product lives in: **9** (software) and **42** (software as a service)\nfor every software product, **35** where it is a business-management or CRM tool, and any\nother class the product category implies, each with a one-line reason.\n\n### Match types and status\n\nSearch **identical** marks (ignoring case and spacing) and **near-identical** ones\n(plurals, hyphenation, transposed or substituted letters, common phonetic variants).\nRecord only **live** marks: registered, or filed and pending (including under opposition).\nAn expired, withdrawn or refused mark is not a conflict.\n\n### What to report per query\n\nThe register, the jurisdictions it covers, the classes and match types searched, the\nresult, every live conflicting mark (mark, owner, number, classes, status, the record's\nURL), the search URL, and today's date.\n\n## 3. A failure is not an answer\n\nSome registers will not answer you: TMview renders in the browser, and WIPO's database is\nbehind a CAPTCHA. **When you cannot run a search, or cannot read its result, report that\nregister as NOT CHECKED, and say why.** Never infer \"no conflict\" from a search engine,\nfrom silence, or from your own memory of which marks exist. A candidate with a register\nnot checked is \"screening incomplete\" — still offered to the creator, never as clear.\n\n## 4. Signals beside the registers (recorded, never blocking)\n\n- the exact-match `.com` and the main country-code domains of the target countries,\n registered or available;\n- any company or product already trading under the name in this category, with its URL.\n\n## What you must never say\n\nNever write that a name is \"available\", \"free to use\", \"safe\" or \"cleared\". This is a\n**minimal trademark screening, not a legal clearance opinion**. The creator should consult an\nIP professional before filing or launching. You report what each register said, with its source.\n\n## Condensation\n\nReturn a brief, not a transcript: candidates, per-register results with URLs and dates,\ncollisions, signals, and an explicit list of what could not be checked.\n",
40
+ "guidance": "# Brand Name Research — propose, then screen\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nYou are the **naming researcher**. You do two things: propose names for this product,\nand run a **minimal trademark screening** of every candidate. You do not choose the name\n— the creator does, from what you bring back — and you author no file.\n\n## 1. Propose (at least five)\n\nGround every proposal in what the application already decided:\n\n- the vision's **idea and mission** — what the product is FOR;\n- the market snapshot's **category language** (the words buyers and competitors use) and\n its **tones of voice** (a serious, formal voice wants a different name from a casual one);\n- the **target geographies and languages** — a name must be pronounceable and inoffensive\n in the target countries' main languages. Check that it carries no unfortunate meaning.\n\nPrefer distinctive names (invented or arbitrary) over descriptive ones. A purely\ndescriptive name (\"Building CRM\") is weak as a mark and usually refused registration.\n\n**A proposal must not be identical or close to any competitor or alternative the market\nsnapshot names**, nor to any name you find trading in the same category. Drop such a name\nbefore screening it; if one slips through, report the collision so it is never offered.\n\nPropose at least five, so at least three survive screening. One line per proposal on\nwhy it fits. That line is what the creator reads first.\n\n## 2. Screen every candidate\n\nScreen each proposal, **and every name the creator listed in the interview**\n(`names-to-screen`, unless it says \"none\"), the same way. Mark the creator's names as theirs.\n\n### Jurisdictions — derive, never assume the EU\n\nThe UNION of four sources, never one of them alone:\n\n- the market snapshot's ICP geographies;\n- the vision's compliance detail;\n- the jurisdictions the application DECLARES it operates in — the declared `operating_jurisdictions` context section of your brief,\n read from its configuration: each declared place is a target;\n- **the creator's own answer about where the product's users are** — the `target-jurisdictions`\n answer in your objective (the same decision as the compliance interview's `jurisdictions`\n question, asked once). When the creator names countries there (\"market focus on Germany,\n France, Italy and Spain\"), every one of them is a target, whether or not the market snapshot\n evidences it.\n\nA region tag (\"EMEA\") is not a jurisdiction: name the countries it implies for this product. If\nany EU member state is targeted, the **EU trade mark** (`EU`) applies too, because an EUTM has\neffect in every member state. International registrations (`WO`) are always in scope. Where the\ndata is HOSTED is not a trademark jurisdiction: a mark is protected where it is used in trade.\n\n**Every targeted country gets its own coverage**: a search of its national office (IT → UIBM,\nES → OEPM, DE → DPMA, FR → INPI, …), or a TMview search that includes that office, recorded with\nthat country among the jurisdictions it covers. Say which, per country.\n\n### Registers, and HOW you reach each one\n\n- **EUIPO** — EU trade marks, and international registrations designating the EU.\n- **TMview** (https://www.tmdn.org/tmview/) — the EU office and participating national\n offices in one search.\n- **WIPO Global Brand Database** (https://branddb.wipo.int/) — international (Madrid)\n registrations and many national collections.\n- **The national office of each targeted country** that TMview or WIPO does not already\n cover for you (for example the USPTO for the United States, UKIPO for the United Kingdom).\n\n**Use a register's machine interface, not its web page, wherever one is reachable.** A register's\nweb page is built for a person in a browser: on a real run every one of them returned nothing a\nfetch could read (results rendered in the browser, an empty page, a CAPTCHA, an HTTP 403, a search\nform that never ran). A machine interface returns structured records. Today:\n\n- **EUIPO** publishes a Trademark Search API, but it needs OAuth credentials from a registered\n developer account. Use it only when the application's providers give you access to it; without\n that, you cannot reach it.\n- **TMview and the WIPO Global Brand Database** publish no machine interface.\n- **A national office** may publish one: use it when its own documentation offers open access.\n\nSo on most runs the web page is all you have. Try each register ONCE; when it returns nothing\nreadable, report it as not checked and move on. Do not spend the run retrying a page that renders\nin the browser.\n\n**Report, for every query, how you reached the register**: through its machine interface, or by\nfetching its web page. The landed screening records it, so a reader can tell the two apart.\n\n### Classes\n\nThe Nice classes the product lives in: **9** (software) and **42** (software as a service)\nfor every software product, **35** where it is a business-management or CRM tool, and any\nother class the product category implies, each with a one-line reason.\n\n### Match types and status\n\nSearch **identical** marks (ignoring case and spacing) and **near-identical** ones\n(plurals, hyphenation, transposed or substituted letters, common phonetic variants).\nRecord only **live** marks: registered, or filed and pending (including under opposition).\nAn expired, withdrawn or refused mark is not a conflict.\n\n### What to report per query\n\nThe register, the jurisdictions it covers, the classes and match types searched, the\nresult, every live conflicting mark (mark, owner, number, classes, status, the record's\nURL), the search URL, and today's date.\n\n## 3. A failure is not an answer\n\nSome registers will not answer you. **When you cannot run a search, or cannot read its result,\nreport that register as NOT CHECKED, and say why.** Never infer \"no conflict\" from a search\nengine, from silence, or from your own memory of which marks exist. A candidate with a register\nnot checked is \"screening incomplete\", and one with NO register read is \"not screened\" — still\noffered to the creator, never as clear. Each unread search becomes a check the creator can run by\nhand, from a link the companion builds; you do not need to write that link.\n\n## 4. Signals beside the registers (recorded, never blocking)\n\n- the exact-match `.com` and the main country-code domains of the target countries,\n registered or available;\n- any company or product already trading under the name, with its URL, and **how it relates\n to this product's category**: the SAME JOB (the same work for the same kind of customer, or\n the same Nice class of goods and services), an ADJACENT category, or UNRELATED.\n\n**A product doing the same job under an identical or near-identical name is a COLLISION, not\nmerely a same-category use.** Report it as a collision, beside the competitor collisions, with\nits URL. \"Groundwork — Estimating & Job Suite\", a quote-to-invoice tool for tradespeople, is a\ncollision for a builders' CRM called \"Groundwork\", although no market snapshot listed it.\n\n## What you must never say\n\nNever write that a name is \"available\", \"free to use\", \"safe\" or \"cleared\". This is a\n**minimal trademark screening, not a legal clearance opinion**. The creator should consult an\nIP professional before filing or launching. You report what each register said, with its source.\n\n## Condensation\n\nReturn a brief, not a transcript: candidates, per-register results with URLs and dates,\ncollisions, signals, and an explicit list of what could not be checked.\n",
41
41
  "skillRefs": [
42
42
  "brand-name-screening"
43
43
  ],
44
44
  "skillBodyRefs": [],
45
- "contextSources": [],
45
+ "contextSources": [
46
+ "operating_jurisdictions"
47
+ ],
46
48
  "draftableDocumentDefinitionRefs": [],
47
49
  "suspendsForClarification": false,
48
50
  "briefAdequacyGate": false,
@@ -1 +1 @@
1
- {"aggregationPolicyRef":"application-creation:aggregation/worst-brand-name-screening-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand-name-screening.candidate","vision.idea","vision.mission","market.category","market.alternative","market.tone-of-voice"],"criterionRef":"application-creation:criterion/brand-name-proposals-grounded-and-distinct","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-proposals-grounded-and-distinct","requirementVersion":1}],"instruction":"Determine whether the PROPOSALS are worth choosing from: each companion-proposed name carries a rationale traceable to the vision's idea or mission and to the market's category language or tone of voice; no proposal is identical or close to a competitor or alternative the market snapshot names, or to a company the evidence found trading in the same category (a creator-supplied name may collide — it is offered only as an explicit keep-despite-conflict, so it is not a finding here); and every name the creator listed in the interview is on the list, marked as theirs. Nothing in the screening may assert that a name is available, free to use or legally cleared.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a generic rationale, a weakly distinctive or purely descriptive proposal, or fewer than three proposals surviving the screening.","GAP":"A proposal collides with a named competitor, a creator-listed name is missing, or the screening claims a name is available or legally cleared.","INDETERMINATE":"The vision, the market snapshot or the creator's interview answer is not in evidence.","PASS":"Every proposal is grounded and distinct from the named competitors, the creator's names are all present, and nothing claims availability or clearance."}},{"assessesAspects":["brand-name-screening.candidate","brand-name-screening.jurisdiction","brand-name-screening.nice-class","market.icp"],"criterionRef":"application-creation:criterion/brand-name-screening-coverage-and-honesty","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty","requirementVersion":1}],"instruction":"Determine whether the screening COVERS what it declares and reports it HONESTLY: the declared jurisdictions follow from the market's ICP geographies and the vision (an EU member state target brings the EU trade mark with it; a region tag is resolved to countries), the Nice classes include 9 and 42 and any class the product category implies, every candidate has a query reaching each declared jurisdiction in those classes for identical and near-identical marks, every query cites a source URL and a date, and no register the evidence reports as unreachable or unread appears with a clear result. A register that could not be checked and is recorded as not checked is a legitimate, honest state, not a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is honest but thin: a class the category implies is missing, or several registers could not be checked and are correctly recorded as such.","GAP":"A query the evidence reports as unreachable or unread is recorded as clear, a declared jurisdiction is never queried while the candidate reads as cleared, or a query has no source.","INDETERMINATE":"The research evidence or the market snapshot is not in evidence, so coverage and honesty cannot be established.","PASS":"Jurisdictions and classes follow from the product, every candidate is queried across them with sources and dates, and nothing unchecked is shown as clear."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-name-screening","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-name-screening-produce"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
1
+ {"aggregationPolicyRef":"application-creation:aggregation/worst-brand-name-screening-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand-name-screening.candidate","vision.idea","vision.mission","market.category","market.alternative","market.tone-of-voice"],"criterionRef":"application-creation:criterion/brand-name-proposals-grounded-and-distinct","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-proposals-grounded-and-distinct","requirementVersion":1}],"instruction":"Determine whether the PROPOSALS are worth choosing from: each companion-proposed name carries a rationale traceable to the vision's idea or mission and to the market's category language or tone of voice; no proposal is identical or close to a competitor or alternative the market snapshot names, or to a company the evidence found doing the same job under that name — and every such same-job product is recorded as a competitor collision, with a SAME_JOB category relation, never only as a same-category use (a creator-supplied name may collide — it is offered only as an explicit keep-despite-conflict, so it is not a finding here); and every name the creator listed in the interview is on the list, marked as theirs. Nothing in the screening may assert that a name is available, free to use or legally cleared.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a generic rationale, a weakly distinctive or purely descriptive proposal, or fewer than three proposals surviving the screening.","GAP":"A proposal collides with a named competitor or a same-job product, a same-job product with a candidate's name is recorded only as a same-category use, a creator-listed name is missing, or the screening claims a name is available or legally cleared.","INDETERMINATE":"The vision, the market snapshot or the creator's interview answer is not in evidence.","PASS":"Every proposal is grounded and distinct from the named competitors, the creator's names are all present, and nothing claims availability or clearance."}},{"assessesAspects":["brand-name-screening.candidate","brand-name-screening.jurisdiction","brand-name-screening.nice-class","market.icp"],"criterionRef":"application-creation:criterion/brand-name-screening-coverage-and-honesty","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty","requirementVersion":1}],"instruction":"Determine whether the screening COVERS what it declares and reports it HONESTLY: the declared jurisdictions are the union of the market's ICP geographies, the vision, the operating jurisdictions the application declares in its configuration (operatingJurisdictions) and the creator's own target-jurisdictions answer (an EU member state target brings the EU trade mark with it; a region tag is resolved to countries; every country the creator names or the configuration declares is declared and reached by its national office or a TMview search listing it), the Nice classes include 9 and 42 and any class the product category implies, every candidate has a query reaching each declared jurisdiction in those classes for identical and near-identical marks, every query cites a source URL and a date, and no register the evidence reports as unreachable or unread appears with a clear result. A register that could not be checked and is recorded as not checked is a legitimate, honest state, not a finding — UNLESS no register returned a result for any candidate: then the screening screened nothing, however honestly it says so, and that is the worst verdict.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is honest but thin: a class the category implies is missing, or several registers could not be checked and are correctly recorded as such while at least one register returned a result.","GAP":"No register returned a result for ANY candidate (0% coverage: nothing was screened), a country the creator named or the configuration declares (operatingJurisdictions) is not a declared jurisdiction, a query the evidence reports as unreachable or unread is recorded as clear, a declared jurisdiction is never queried while the candidate reads as cleared, or a query has no source.","INDETERMINATE":"The research evidence or the market snapshot is not in evidence, so coverage and honesty cannot be established.","PASS":"Jurisdictions and classes follow from the product, every candidate is queried across them with sources and dates, and nothing unchecked is shown as clear."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-name-screening","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-name-screening-produce"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
@@ -1 +1 @@
1
- {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-brand-name-screening","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty"],"requirementRef":"application-creation:authority-requirement/brand-name-screening-result","requirementVersion":1,"riskClassRef":"application-creation:risk/brand-name-screening-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/brand-name-screening","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/brand-name-screening-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/brand-name-screening","policyVersion":1},"decisionPointRef":"application-creation:decision-point/brand-name-screening-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/brand-name-screening-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/brand-name-screening","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-proposals-grounded-and-distinct","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/brand-name-screening-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-brand-name-screening-change","triggerRefs":["application-creation:trigger/brand-name-screening-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-brand-name-screening-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty"],"hardFloorRef":"application-creation:hard-floor/brand-name-screening-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/brand-name-screening-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/brand-name-screening","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-brand-name-screening-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand-name-screening.candidate","vision.idea","vision.mission","market.category","market.alternative","market.tone-of-voice"],"criterionRef":"application-creation:criterion/brand-name-proposals-grounded-and-distinct","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-proposals-grounded-and-distinct","requirementVersion":1}],"instruction":"Determine whether the PROPOSALS are worth choosing from: each companion-proposed name carries a rationale traceable to the vision's idea or mission and to the market's category language or tone of voice; no proposal is identical or close to a competitor or alternative the market snapshot names, or to a company the evidence found trading in the same category (a creator-supplied name may collide — it is offered only as an explicit keep-despite-conflict, so it is not a finding here); and every name the creator listed in the interview is on the list, marked as theirs. Nothing in the screening may assert that a name is available, free to use or legally cleared.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a generic rationale, a weakly distinctive or purely descriptive proposal, or fewer than three proposals surviving the screening.","GAP":"A proposal collides with a named competitor, a creator-listed name is missing, or the screening claims a name is available or legally cleared.","INDETERMINATE":"The vision, the market snapshot or the creator's interview answer is not in evidence.","PASS":"Every proposal is grounded and distinct from the named competitors, the creator's names are all present, and nothing claims availability or clearance."}},{"assessesAspects":["brand-name-screening.candidate","brand-name-screening.jurisdiction","brand-name-screening.nice-class","market.icp"],"criterionRef":"application-creation:criterion/brand-name-screening-coverage-and-honesty","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty","requirementVersion":1}],"instruction":"Determine whether the screening COVERS what it declares and reports it HONESTLY: the declared jurisdictions follow from the market's ICP geographies and the vision (an EU member state target brings the EU trade mark with it; a region tag is resolved to countries), the Nice classes include 9 and 42 and any class the product category implies, every candidate has a query reaching each declared jurisdiction in those classes for identical and near-identical marks, every query cites a source URL and a date, and no register the evidence reports as unreachable or unread appears with a clear result. A register that could not be checked and is recorded as not checked is a legitimate, honest state, not a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is honest but thin: a class the category implies is missing, or several registers could not be checked and are correctly recorded as such.","GAP":"A query the evidence reports as unreachable or unread is recorded as clear, a declared jurisdiction is never queried while the candidate reads as cleared, or a query has no source.","INDETERMINATE":"The research evidence or the market snapshot is not in evidence, so coverage and honesty cannot be established.","PASS":"Jurisdictions and classes follow from the product, every candidate is queried across them with sources and dates, and nothing unchecked is shown as clear."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-name-screening","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-name-screening-produce"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/brand-name-screening","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-name-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-name-proposals-grounded-and-distinct","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-name-proposals-grounded-and-distinct","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-research-and-brand-name-screening-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-name-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-name-screening-coverage-and-honesty","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-research-and-brand-name-screening-candidate"}],"schemaVersion":1}
1
+ {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-brand-name-screening","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty"],"requirementRef":"application-creation:authority-requirement/brand-name-screening-result","requirementVersion":1,"riskClassRef":"application-creation:risk/brand-name-screening-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/brand-name-screening","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/brand-name-screening-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/brand-name-screening","policyVersion":1},"decisionPointRef":"application-creation:decision-point/brand-name-screening-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/brand-name-screening-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/brand-name-screening","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-proposals-grounded-and-distinct","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/brand-name-screening-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-brand-name-screening-change","triggerRefs":["application-creation:trigger/brand-name-screening-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-brand-name-screening-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty"],"hardFloorRef":"application-creation:hard-floor/brand-name-screening-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/brand-name-screening-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/brand-name-screening","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-brand-name-screening-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand-name-screening.candidate","vision.idea","vision.mission","market.category","market.alternative","market.tone-of-voice"],"criterionRef":"application-creation:criterion/brand-name-proposals-grounded-and-distinct","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-proposals-grounded-and-distinct","requirementVersion":1}],"instruction":"Determine whether the PROPOSALS are worth choosing from: each companion-proposed name carries a rationale traceable to the vision's idea or mission and to the market's category language or tone of voice; no proposal is identical or close to a competitor or alternative the market snapshot names, or to a company the evidence found doing the same job under that name — and every such same-job product is recorded as a competitor collision, with a SAME_JOB category relation, never only as a same-category use (a creator-supplied name may collide — it is offered only as an explicit keep-despite-conflict, so it is not a finding here); and every name the creator listed in the interview is on the list, marked as theirs. Nothing in the screening may assert that a name is available, free to use or legally cleared.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a generic rationale, a weakly distinctive or purely descriptive proposal, or fewer than three proposals surviving the screening.","GAP":"A proposal collides with a named competitor or a same-job product, a same-job product with a candidate's name is recorded only as a same-category use, a creator-listed name is missing, or the screening claims a name is available or legally cleared.","INDETERMINATE":"The vision, the market snapshot or the creator's interview answer is not in evidence.","PASS":"Every proposal is grounded and distinct from the named competitors, the creator's names are all present, and nothing claims availability or clearance."}},{"assessesAspects":["brand-name-screening.candidate","brand-name-screening.jurisdiction","brand-name-screening.nice-class","market.icp"],"criterionRef":"application-creation:criterion/brand-name-screening-coverage-and-honesty","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty","requirementVersion":1}],"instruction":"Determine whether the screening COVERS what it declares and reports it HONESTLY: the declared jurisdictions are the union of the market's ICP geographies, the vision, the operating jurisdictions the application declares in its configuration (operatingJurisdictions) and the creator's own target-jurisdictions answer (an EU member state target brings the EU trade mark with it; a region tag is resolved to countries; every country the creator names or the configuration declares is declared and reached by its national office or a TMview search listing it), the Nice classes include 9 and 42 and any class the product category implies, every candidate has a query reaching each declared jurisdiction in those classes for identical and near-identical marks, every query cites a source URL and a date, and no register the evidence reports as unreachable or unread appears with a clear result. A register that could not be checked and is recorded as not checked is a legitimate, honest state, not a finding — UNLESS no register returned a result for any candidate: then the screening screened nothing, however honestly it says so, and that is the worst verdict.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is honest but thin: a class the category implies is missing, or several registers could not be checked and are correctly recorded as such while at least one register returned a result.","GAP":"No register returned a result for ANY candidate (0% coverage: nothing was screened), a country the creator named or the configuration declares (operatingJurisdictions) is not a declared jurisdiction, a query the evidence reports as unreachable or unread is recorded as clear, a declared jurisdiction is never queried while the candidate reads as cleared, or a query has no source.","INDETERMINATE":"The research evidence or the market snapshot is not in evidence, so coverage and honesty cannot be established.","PASS":"Jurisdictions and classes follow from the product, every candidate is queried across them with sources and dates, and nothing unchecked is shown as clear."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-name-screening","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-name-screening-produce"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/brand-name-screening","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-name-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-name-proposals-grounded-and-distinct","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-name-proposals-grounded-and-distinct","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-research-and-brand-name-screening-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-name-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-name-screening-coverage-and-honesty","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-research-and-brand-name-screening-candidate"}],"schemaVersion":1}
@@ -34,17 +34,28 @@ every query faithfully.
34
34
  ## What you emit
35
35
 
36
36
  - `screenedOn` — today's date.
37
- - `jurisdictions` — each code the research searched (`EU` for the EU trade mark, `WO` for
38
- international registrations, ISO country codes otherwise), with what declared it.
37
+ - `jurisdictions` — the UNION of what the vision, the market snapshot, the application's declared
38
+ operating jurisdictions (the declared `operating_jurisdictions` context section of your brief) and the creator's own
39
+ `target-jurisdictions` answer (in the interview answers of `top_down.brand-naming`) target:
40
+ `EU` for the EU trade mark, `WO` for international registrations, ISO country codes otherwise,
41
+ each with what declared it. Every country the creator names is a jurisdiction even when the
42
+ research did not search it: an unsearched target is recorded, and reads as not cleared, rather
43
+ than silently dropped. Where data is hosted is not a trademark jurisdiction.
39
44
  - `niceClasses` — each class searched, with why this product lives in it.
40
45
  - `candidates` — one per name, with a kebab-case `slug`, the exact `name`, its `origin`,
41
46
  a one-line `rationale` for proposals, and:
42
47
  - `trademarkQueries` — one per register search the evidence reports: register,
43
- jurisdictions covered, classes and match types searched, outcome, conflicting marks,
44
- source URL, date, and a note for anything a reader needs.
48
+ `accessPath` (`MACHINE_INTERFACE` when the register's published interface answered,
49
+ `WEB_PAGE` when its web page was fetched), jurisdictions covered, classes and match types
50
+ searched, outcome, conflicting marks, source URL, date, and a note for anything a reader needs.
51
+ A TMview search covers every office it included: list each of those countries.
45
52
  - `competitorCollisions` — any market competitor or alternative the name is identical
46
- or close to.
47
- - `domainSignals` and `sameCategoryUses` — as the evidence reports them.
53
+ or close to, AND any product the evidence found doing the same job under an identical or
54
+ near-identical name.
55
+ - `sameCategoryUses` — every company or product trading under the name, each with its
56
+ `categoryRelation`: `SAME_JOB` (the same work for the same kind of customer, or the same Nice
57
+ class), `ADJACENT`, or `UNRELATED`.
58
+ - `domainSignals` — as the evidence reports them.
48
59
 
49
60
  ## The rules that keep it true
50
61
 
@@ -56,6 +67,14 @@ every query faithfully.
56
67
  mark beside a `CLEAR`, is refused at landing.
57
68
  - **Only what the evidence says.** No mark, URL, date or result from memory. A claim
58
69
  without a source in the evidence is left out and named in a query note.
70
+ - **A same-job product with an identical or near-identical name is a collision.** Record it in
71
+ `competitorCollisions` and also, with `categoryRelation: SAME_JOB`, in `sameCategoryUses`.
72
+ Filing it only as a same-category use with no relation is how a creator once chose a name
73
+ without being told a quote-to-invoice suite for tradespeople already traded under it. The
74
+ choice computation treats a `SAME_JOB` use of a colliding name as a collision anyway, but the
75
+ relation is what lets it decide: state it for every use.
76
+ - **Unread registers need no link from you.** Each `UNKNOWN` query becomes a check the creator
77
+ can run by hand, with a search link the companion builds from the query; never invent a URL.
59
78
  - **Keep conflicting proposals on record.** A proposal that conflicts is never offered
60
79
  to the creator, and the record of why it was dropped is still worth keeping.
61
80
  - **Never write "available", "free to use" or "cleared".** This is a minimal trademark
@@ -69,10 +88,12 @@ open files.
69
88
 
70
89
  The deterministic `validateBrandNameScreening` runs before anything lands. It refuses a
71
90
  contradictory record and REPORTS the rest for the creator's review: an incomplete
72
- screening, a conflicting proposal kept for the record, fewer than three offerable
73
- proposals, a missing EU trade mark for an EU target, or a missing class 9 or 42. Let
91
+ screening, a screening that read no register at all, a conflicting proposal kept for the
92
+ record, fewer than three offerable proposals, a missing EU trade mark for an EU target, or a
93
+ missing class 9 or 42. Let
74
94
  those findings stand honestly rather than inventing results to silence them.
75
95
 
76
96
  After landing, an advisory judge reads the screening for coverage and honesty, and checks
77
- that the proposals are grounded and distinct from the competitors. Its verdict is a note
97
+ that the proposals are grounded and distinct from the competitors. A screening that read no
98
+ register for any candidate is its worst verdict: honest, and still a screening of nothing. Its verdict is a note
78
99
  for the creator's review.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "top_down.brand-name-screening-produce",
3
- "version": "0.1.0",
3
+ "version": "0.2.0",
4
4
  "phase": "top_down",
5
5
  "intent": "Derive the validated brand-name screening from the vision, the market snapshot and the evidence a sibling research step gathered: the jurisdictions and Nice classes searched, and per candidate its origin, why it fits, every register query with its result, conflicting marks, source and date, the competitor collisions, and the domain and same-category signals. Transcribes, never concludes: a candidate's standing is derived from its queries. A minimal trademark screening, never a legal clearance opinion.",
6
6
  "preconditions": [
@@ -41,14 +41,16 @@
41
41
  ],
42
42
  "stepOutputs": [],
43
43
  "method": {
44
- "guidance": "# Brand Name Screening — land what the research found\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nYou turn the evidence a sibling research step gathered into the validated\n**`BrandNameScreening`** — the `brand-name-screening` family. The creator chooses the\nbrand name from what you land, so the record must say exactly what was checked and\nwhat each register returned, and nothing more.\n\nYou are a **transcriber, not a judge.** There is no field for \"this name is clear\":\na candidate's standing is computed from its register queries. Your job is to record\nevery query faithfully.\n\n## Where your inputs are\n\n- The research brief is in your brief under \"Evidence gathered for this run\".\n- The vision and the market snapshot are in your brief as input sections.\n- A screening already on record, if any, is in your brief too. Keep its candidates and\n their slugs, and re-record them with the new evidence. A re-run adds to the list; it\n does not forget it.\n- The creator's own names are in the interview answers of `top_down.brand-naming`\n (`names-to-screen`). Every one of them is a candidate with origin `CREATOR_SUPPLIED`.\n\n## What you emit\n\n- `screenedOn` — today's date.\n- `jurisdictions` — each code the research searched (`EU` for the EU trade mark, `WO` for\n international registrations, ISO country codes otherwise), with what declared it.\n- `niceClasses` — each class searched, with why this product lives in it.\n- `candidates` — one per name, with a kebab-case `slug`, the exact `name`, its `origin`,\n a one-line `rationale` for proposals, and:\n - `trademarkQueries` — one per register search the evidence reports: register,\n jurisdictions covered, classes and match types searched, outcome, conflicting marks,\n source URL, date, and a note for anything a reader needs.\n - `competitorCollisions` — any market competitor or alternative the name is identical\n or close to.\n - `domainSignals` and `sameCategoryUses` — as the evidence reports them.\n\n## The rules that keep it true\n\n- **A register the evidence could not query or read is `UNKNOWN`, with a note saying\n why.** Never `CLEAR`. Never omit it either: an unrecorded register is an uncovered\n jurisdiction, and the candidate reads as not cleared anyway.\n- **`CONFLICT` exactly when the query found a live identical or near-identical mark**,\n and then every such mark is listed with its source. A conflict with no mark, or a\n mark beside a `CLEAR`, is refused at landing.\n- **Only what the evidence says.** No mark, URL, date or result from memory. A claim\n without a source in the evidence is left out and named in a query note.\n- **Keep conflicting proposals on record.** A proposal that conflicts is never offered\n to the creator, and the record of why it was dropped is still worth keeping.\n- **Never write \"available\", \"free to use\" or \"cleared\".** This is a minimal trademark\n screening, not a legal clearance opinion.\n\nFollow the `brand-name-screening` skill for the field contracts. Its full text is in\nyour brief under \"The skills this method tells you to FOLLOW\". Read it there; you cannot\nopen files.\n\n## Quality gate\n\nThe deterministic `validateBrandNameScreening` runs before anything lands. It refuses a\ncontradictory record and REPORTS the rest for the creator's review: an incomplete\nscreening, a conflicting proposal kept for the record, fewer than three offerable\nproposals, a missing EU trade mark for an EU target, or a missing class 9 or 42. Let\nthose findings stand honestly rather than inventing results to silence them.\n\nAfter landing, an advisory judge reads the screening for coverage and honesty, and checks\nthat the proposals are grounded and distinct from the competitors. Its verdict is a note\nfor the creator's review.\n",
44
+ "guidance": "# Brand Name Screening — land what the research found\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nYou turn the evidence a sibling research step gathered into the validated\n**`BrandNameScreening`** — the `brand-name-screening` family. The creator chooses the\nbrand name from what you land, so the record must say exactly what was checked and\nwhat each register returned, and nothing more.\n\nYou are a **transcriber, not a judge.** There is no field for \"this name is clear\":\na candidate's standing is computed from its register queries. Your job is to record\nevery query faithfully.\n\n## Where your inputs are\n\n- The research brief is in your brief under \"Evidence gathered for this run\".\n- The vision and the market snapshot are in your brief as input sections.\n- A screening already on record, if any, is in your brief too. Keep its candidates and\n their slugs, and re-record them with the new evidence. A re-run adds to the list; it\n does not forget it.\n- The creator's own names are in the interview answers of `top_down.brand-naming`\n (`names-to-screen`). Every one of them is a candidate with origin `CREATOR_SUPPLIED`.\n\n## What you emit\n\n- `screenedOn` — today's date.\n- `jurisdictions` — the UNION of what the vision, the market snapshot, the application's declared\n operating jurisdictions (the declared `operating_jurisdictions` context section of your brief) and the creator's own\n `target-jurisdictions` answer (in the interview answers of `top_down.brand-naming`) target:\n `EU` for the EU trade mark, `WO` for international registrations, ISO country codes otherwise,\n each with what declared it. Every country the creator names is a jurisdiction even when the\n research did not search it: an unsearched target is recorded, and reads as not cleared, rather\n than silently dropped. Where data is hosted is not a trademark jurisdiction.\n- `niceClasses` — each class searched, with why this product lives in it.\n- `candidates` — one per name, with a kebab-case `slug`, the exact `name`, its `origin`,\n a one-line `rationale` for proposals, and:\n - `trademarkQueries` — one per register search the evidence reports: register,\n `accessPath` (`MACHINE_INTERFACE` when the register's published interface answered,\n `WEB_PAGE` when its web page was fetched), jurisdictions covered, classes and match types\n searched, outcome, conflicting marks, source URL, date, and a note for anything a reader needs.\n A TMview search covers every office it included: list each of those countries.\n - `competitorCollisions` — any market competitor or alternative the name is identical\n or close to, AND any product the evidence found doing the same job under an identical or\n near-identical name.\n - `sameCategoryUses` — every company or product trading under the name, each with its\n `categoryRelation`: `SAME_JOB` (the same work for the same kind of customer, or the same Nice\n class), `ADJACENT`, or `UNRELATED`.\n - `domainSignals` — as the evidence reports them.\n\n## The rules that keep it true\n\n- **A register the evidence could not query or read is `UNKNOWN`, with a note saying\n why.** Never `CLEAR`. Never omit it either: an unrecorded register is an uncovered\n jurisdiction, and the candidate reads as not cleared anyway.\n- **`CONFLICT` exactly when the query found a live identical or near-identical mark**,\n and then every such mark is listed with its source. A conflict with no mark, or a\n mark beside a `CLEAR`, is refused at landing.\n- **Only what the evidence says.** No mark, URL, date or result from memory. A claim\n without a source in the evidence is left out and named in a query note.\n- **A same-job product with an identical or near-identical name is a collision.** Record it in\n `competitorCollisions` and also, with `categoryRelation: SAME_JOB`, in `sameCategoryUses`.\n Filing it only as a same-category use with no relation is how a creator once chose a name\n without being told a quote-to-invoice suite for tradespeople already traded under it. The\n choice computation treats a `SAME_JOB` use of a colliding name as a collision anyway, but the\n relation is what lets it decide: state it for every use.\n- **Unread registers need no link from you.** Each `UNKNOWN` query becomes a check the creator\n can run by hand, with a search link the companion builds from the query; never invent a URL.\n- **Keep conflicting proposals on record.** A proposal that conflicts is never offered\n to the creator, and the record of why it was dropped is still worth keeping.\n- **Never write \"available\", \"free to use\" or \"cleared\".** This is a minimal trademark\n screening, not a legal clearance opinion.\n\nFollow the `brand-name-screening` skill for the field contracts. Its full text is in\nyour brief under \"The skills this method tells you to FOLLOW\". Read it there; you cannot\nopen files.\n\n## Quality gate\n\nThe deterministic `validateBrandNameScreening` runs before anything lands. It refuses a\ncontradictory record and REPORTS the rest for the creator's review: an incomplete\nscreening, a screening that read no register at all, a conflicting proposal kept for the\nrecord, fewer than three offerable proposals, a missing EU trade mark for an EU target, or a\nmissing class 9 or 42. Let\nthose findings stand honestly rather than inventing results to silence them.\n\nAfter landing, an advisory judge reads the screening for coverage and honesty, and checks\nthat the proposals are grounded and distinct from the competitors. A screening that read no\nregister for any candidate is its worst verdict: honest, and still a screening of nothing. Its verdict is a note\nfor the creator's review.\n",
45
45
  "skillRefs": [
46
46
  "brand-name-screening"
47
47
  ],
48
48
  "skillBodyRefs": [
49
49
  "brand-name-screening"
50
50
  ],
51
- "contextSources": [],
51
+ "contextSources": [
52
+ "operating_jurisdictions"
53
+ ],
52
54
  "draftableDocumentDefinitionRefs": [],
53
55
  "suspendsForClarification": false,
54
56
  "briefAdequacyGate": false,
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "top_down.brand-naming",
3
- "version": "0.1.0",
3
+ "version": "0.2.0",
4
4
  "phase": "top_down",
5
5
  "intent": "Propose names for the product and screen each against the public trademark registers of the jurisdictions it targets, landing the brand-name screening the brand-identity interview offers the creator a choice from. An umbrella: it authors nothing itself — research proposes and screens with web access, a sibling lands the validated screening. The companion proposes; the creator chooses. A minimal trademark screening, never a legal clearance opinion.",
6
6
  "preconditions": [
@@ -40,6 +40,17 @@
40
40
  "question": "Do you already have names you want screened alongside the ones the companion will propose? List each exactly as you would spell it, separated by commas, or answer \"none\".",
41
41
  "kind": "free_text",
42
42
  "whenUnknown": "ask"
43
+ },
44
+ {
45
+ "ref": "target-jurisdictions",
46
+ "question": "In which jurisdictions do your users live and your data reside or transit (e.g. EU/EEA, UK, US, California, Canada, specific countries)? This is what drives which privacy regimes apply.",
47
+ "kind": "free_text",
48
+ "sameDecisionAs": {
49
+ "playbookRef": "top_down.compliance-analysis",
50
+ "questionRef": "jurisdictions"
51
+ },
52
+ "depth": "essential",
53
+ "regulatedDomain": true
43
54
  }
44
55
  ]
45
56
  },