@wildo-ai/framework-knowledge 1.1.8 → 1.1.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/claude-marketplace/.claude-plugin/marketplace.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +11 -0
- package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +9 -2
- package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +21 -0
- package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +121 -0
- package/dist/claude-marketplace/plugins/wildo/references/expert-personas-and-deliberations.md +26 -7
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +31 -5
- package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +4 -2
- package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +29 -2
- package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +69 -24
- package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +10 -0
- package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +21 -5
- package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +31 -5
- package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +2 -0
- package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +20 -4
- package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +95 -5
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/index.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +2 -2
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +11 -11
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +29 -22
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +41 -3
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +175 -14
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +3 -3
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +8 -4
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +13 -6
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +4 -2
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +90 -13
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +4 -3
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +4 -3
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +8 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +12 -4
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +12 -3
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +8 -4
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +4 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +2 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +25 -27
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +91 -43
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +41 -0
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +43 -0
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +200 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +203 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +81 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +93 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +3 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +27 -18
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +11 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +11 -11
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +2 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +3 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +2 -0
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +3 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +5 -2
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -4
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +27 -6
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +32 -12
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +13 -5
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +7 -3
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +71 -2
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +23 -8
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +7 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +4 -2
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +9 -3
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +3 -3
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +35 -2
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +41 -17
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
- package/dist/knowledge/manifest.json +8 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +22 -7
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
- package/dist/knowledge/playbooks/bottom_up.build/method.md +17 -15
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +4 -3
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +261 -34
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +42 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +188 -59
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +169 -276
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -2
- package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +8 -1
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.conception/method.md +3 -2
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +11 -3
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +129 -17
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +7 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +28 -6
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +5 -4
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +13 -5
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +50 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +16 -4
- package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +19 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +5 -2
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +7 -3
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +8 -0
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +3 -2
- package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +5 -2
- package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +75 -37
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +35 -38
- package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +145 -0
- package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +57 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +99 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +65 -0
- package/dist/knowledge/playbooks/top_down.brand-naming/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +76 -0
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/method.md +60 -6
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +15 -10
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +10 -9
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +30 -10
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +3 -1
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +4 -1
- package/dist/knowledge/playbooks/top_down.definition/method.md +8 -3
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +6 -4
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +16 -2
- package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +5 -2
- package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +26 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +4 -2
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +11 -1
- package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +84 -9
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +6 -3
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +21 -0
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +8 -2
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +4 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +29 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +58 -17
- package/dist/knowledge/references/brand.name-choice.config.md +144 -0
- package/dist/knowledge/references/brand.name-screening.config.md +308 -0
- package/dist/knowledge/references/build-plan.task-graph.config.md +119 -11
- package/dist/knowledge/references/business-model.pricing-plan.config.md +16 -0
- package/dist/knowledge/references/business-model.snapshot.config.md +64 -0
- package/dist/knowledge/references/business-model.snapshot.validation.md +68 -4
- package/dist/knowledge/references/capability-composition.config.md +67 -4
- package/dist/knowledge/references/companion.market.prompt-renderer.md +11 -6
- package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +44 -0
- package/dist/knowledge/references/example.backend.custom-operation.audit-event.md +81 -0
- package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +258 -0
- package/dist/knowledge/references/example.backend.custom-operation.computed-total.md +153 -0
- package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +107 -0
- package/dist/knowledge/references/example.data-seeding.minimal.md +39 -10
- package/dist/knowledge/references/example.data-seeding.row-reference.md +80 -0
- package/dist/knowledge/references/example.email.template.minimal.md +1 -1
- package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +74 -0
- package/dist/knowledge/references/example.resource.personal-data.free-text-field.md +19 -0
- package/dist/knowledge/references/example.resource.personal-data.person-without-account.md +27 -0
- package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +152 -0
- package/dist/knowledge/references/example.resource.ui-behavior.filter-presets.md +15 -0
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +8 -0
- package/dist/knowledge/references/example.views.app-level.home-definition.md +13 -0
- package/dist/knowledge/references/example.views.chart-definition.shared.md +83 -0
- package/dist/knowledge/references/experience-plan.config.md +60 -7
- package/dist/knowledge/references/market.context-block.builder.md +1 -1
- package/dist/knowledge/references/market.snapshot.validation.md +1 -1
- package/dist/knowledge/references/placement-plan.config.md +43 -0
- package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -2
- package/dist/knowledge/references/requirements.non-functional-requirement.config.md +2 -0
- package/dist/knowledge/references/requirements.references.conventions.md +1 -1
- package/dist/knowledge/references/requirements.snapshot.config.md +57 -1
- package/dist/knowledge/references/requirements.snapshot.validation.md +35 -1
- package/dist/knowledge/references/saas.backend.audit-logs.log-event.md +63 -0
- package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +60 -0
- package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +156 -0
- package/dist/knowledge/references/saas.backend.email.send.md +77 -0
- package/dist/knowledge/references/saas.backend.notifications.operation-email-template-ref.md +60 -0
- package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +7 -1
- package/dist/knowledge/references/saas.data-seeding.computed-entry.md +43 -0
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +14 -2
- package/dist/knowledge/references/saas.data-seeding.row-reference.md +93 -0
- package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +124 -0
- package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +316 -0
- package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +106 -0
- package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +60 -0
- package/dist/knowledge/references/saas.frontend.resource-label-params.md +52 -0
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +47 -18
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -1
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destination-roles.md +25 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +2 -2
- package/dist/knowledge/references/saas.models.audit.trail-config.md +45 -0
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +5 -3
- package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +81 -2
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +26 -0
- package/dist/knowledge/references/saas.models.roles.definition.md +61 -0
- package/dist/knowledge/references/saas.models.roles.organization-defaults.md +97 -0
- package/dist/knowledge/references/saas.public-runtime.contract.md +26 -0
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +10 -0
- package/dist/knowledge/references/saas.website.astro.bridge.md +10 -0
- package/dist/knowledge/references/saas.website.astro.label-loader.md +12 -0
- package/dist/knowledge/references/saas.website.astro.llms-txt-server.md +14 -1
- package/dist/knowledge/references/saas.website.astro.site-context.md +13 -0
- package/dist/knowledge/references/saas.website.blog.bridge.md +4 -0
- package/dist/knowledge/references/saas.website.config.site-context-loader.md +3 -0
- package/dist/knowledge/references/saas.website.factories.define-section.md +4 -0
- package/dist/knowledge/references/saas.website.legal.public-document-links.md +76 -0
- package/dist/knowledge/references/saas.website.page-manifest.schema.md +12 -3
- package/dist/knowledge/references/saas.website.page-sections.component.md +72 -0
- package/dist/knowledge/references/saas.website.root-config.seo.md +2 -1
- package/dist/knowledge/references/saas.website.runtime.context.md +7 -0
- package/dist/knowledge/references/saas.website.sections.definition-schema.md +11 -0
- package/dist/knowledge/references/saas.website.seo.llms-txt-config.md +2 -0
- package/dist/knowledge/references/website-plan.config.md +26 -0
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +13 -0
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +7 -0
- package/dist/knowledge/references/zod.decorators.document-sequence.md +65 -0
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +1 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +21 -0
- package/dist/knowledge/references/zod.factories.bigdecimal.md +1 -0
- package/dist/knowledge/references/zod.factories.code.md +1 -0
- package/dist/knowledge/references/zod.factories.duration.md +1 -0
- package/dist/knowledge/references/zod.factories.money.md +1 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +374 -1
- package/dist/knowledge/registries/playbooks.json +76 -28
- package/dist/knowledge/registries/source-tags.json +1513 -898
- package/dist/knowledge/rules/live-context-door.md +5 -2
- package/dist/knowledge/skills/INDEX.md +5 -2
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +16 -3
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +14 -3
- package/dist/knowledge/skills/application-roles-authoring/SKILL.md +158 -0
- package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +169 -0
- package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +63 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +6 -1
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +256 -9
- package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +42 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +220 -0
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +5 -0
- package/dist/knowledge/skills/brand-name-screening/SKILL.md +178 -0
- package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +466 -0
- package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +87 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +7 -3
- package/dist/knowledge/skills/config-app-shell/SKILL.md +58 -5
- package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +461 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +80 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +28 -6
- package/dist/knowledge/skills/config-navigation/SKILL.md +14 -3
- package/dist/knowledge/skills/config-saas/SKILL.md +56 -15
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +65 -2
- package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +62 -2
- package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +81 -2
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +6 -1
- package/dist/knowledge/skills/configure-billing/SKILL.md +18 -4
- package/dist/knowledge/skills/email-add-template/SKILL.md +28 -6
- package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +1 -1
- package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +128 -0
- package/dist/knowledge/skills/email-add-template/references/framework-operation-email-template-ref-api.md +99 -0
- package/dist/knowledge/skills/engine-component-registration/SKILL.md +6 -1
- package/dist/knowledge/skills/engine-product-definitions/SKILL.md +21 -8
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -2
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +18 -4
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +11 -3
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +2 -1
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +8 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +19 -5
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +10 -2
- package/dist/knowledge/skills/inbound-channels/SKILL.md +2 -2
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +6 -1
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +17 -2
- package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +122 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +11 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +9 -2
- package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +10 -2
- package/dist/knowledge/skills/market-alternatives/SKILL.md +10 -2
- package/dist/knowledge/skills/market-authoring-overview/SKILL.md +10 -2
- package/dist/knowledge/skills/market-category/SKILL.md +21 -7
- package/dist/knowledge/skills/market-channels/SKILL.md +6 -1
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +22 -4
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +12 -2
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +21 -11
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +11 -6
- package/dist/knowledge/skills/market-icp/SKILL.md +10 -2
- package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +6 -1
- package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +6 -1
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
- package/dist/knowledge/skills/market-persona/SKILL.md +14 -3
- package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +6 -1
- package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +10 -2
- package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +6 -1
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -4
- package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +1 -1
- package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +6 -1
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +26 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +7 -1
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +10 -0
- package/dist/knowledge/skills/module-relationships/SKILL.md +37 -8
- package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +4 -2
- package/dist/knowledge/skills/provider-address-lookup/SKILL.md +14 -3
- package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +6 -1
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +14 -3
- package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +10 -2
- package/dist/knowledge/skills/resource-add-field/SKILL.md +10 -2
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +46 -17
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +14 -2
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +26 -0
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +29 -3
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +19 -4
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +5 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +103 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +135 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +26 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +26 -7
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +10 -2
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +46 -17
- package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +2 -2
- package/dist/knowledge/skills/resource-retention-binding/SKILL.md +5 -1
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +15 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +569 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +358 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +8 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +21 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +7 -2
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +13 -0
- package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +153 -0
- package/dist/knowledge/skills/resource-status-lifecycle/references/commercial-documents.md +46 -0
- package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +198 -0
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +30 -4
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +157 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +101 -19
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +202 -39
- package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +67 -0
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +154 -4
- package/dist/knowledge/skills/seeding-authoring/references/seed-row-overlay.md +22 -0
- package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +7 -1
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +43 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +2 -2
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +6 -1
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +10 -0
- package/dist/knowledge/skills/spec-component-update/SKILL.md +10 -2
- package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +2 -2
- package/dist/knowledge/skills/spec-family-update/SKILL.md +71 -66
- package/dist/knowledge/skills/spec-family-update/references/family-spec-routing.md +1 -1
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +30 -10
- package/dist/knowledge/skills/spec-resource-update/references/resource-spec-field-routing.md +28 -0
- package/dist/knowledge/skills/spec-update-after-change/SKILL.md +22 -5
- package/dist/knowledge/skills/views-add-composite-view/SKILL.md +6 -1
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +10 -2
- package/dist/knowledge/skills/views-app-level/SKILL.md +13 -3
- package/dist/knowledge/skills/views-app-level/references/application-home.md +56 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +221 -37
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +22 -5
- package/dist/knowledge/skills/views-execution-authoring/SKILL.md +1 -1
- package/dist/knowledge/skills/website-anonymous-session/SKILL.md +32 -2
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +16 -3
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +4 -0
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +7 -1
- package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +13 -1
- package/dist/knowledge/skills/website-factory-advanced/SKILL.md +14 -2
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +13 -1
- package/dist/knowledge/skills/website-layout-overrides/SKILL.md +6 -1
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +19 -1
- package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +55 -18
- package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +98 -0
- package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +8 -11
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +100 -8
- package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +3 -0
- package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +6 -1
- package/dist/knowledge/skills/website-section-contact/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-cta/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-faq/SKILL.md +21 -1
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +21 -1
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +25 -2
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-hero/SKILL.md +33 -10
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +21 -1
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +27 -2
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +16 -4
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +11 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +16 -1
- package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +2 -1
- package/dist/knowledge/topic-index.json +1590 -292
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
|
@@ -0,0 +1,145 @@
|
|
|
1
|
+
# Brand Name Research — propose, then screen
|
|
2
|
+
|
|
3
|
+
### Target Application Framing
|
|
4
|
+
|
|
5
|
+
This knowledge is for configuring behavior in the target application.
|
|
6
|
+
Wildo is the framework surface being used, not the product being built.
|
|
7
|
+
|
|
8
|
+
Read and apply these patterns from the application-developer point of view:
|
|
9
|
+
|
|
10
|
+
- how the application should configure the relevant app-level file
|
|
11
|
+
- how the application should use framework-provided factories, enums, and helpers
|
|
12
|
+
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
13
|
+
|
|
14
|
+
|
|
15
|
+
You are the **naming researcher**. You do two things: propose names for this product,
|
|
16
|
+
and run a **minimal trademark screening** of every candidate. You do not choose the name
|
|
17
|
+
— the creator does, from what you bring back — and you author no file.
|
|
18
|
+
|
|
19
|
+
## 1. Propose (at least five)
|
|
20
|
+
|
|
21
|
+
Ground every proposal in what the application already decided:
|
|
22
|
+
|
|
23
|
+
- the vision's **idea and mission** — what the product is FOR;
|
|
24
|
+
- the market snapshot's **category language** (the words buyers and competitors use) and
|
|
25
|
+
its **tones of voice** (a serious, formal voice wants a different name from a casual one);
|
|
26
|
+
- the **target geographies and languages** — a name must be pronounceable and inoffensive
|
|
27
|
+
in the target countries' main languages. Check that it carries no unfortunate meaning.
|
|
28
|
+
|
|
29
|
+
Prefer distinctive names (invented or arbitrary) over descriptive ones. A purely
|
|
30
|
+
descriptive name ("Building CRM") is weak as a mark and usually refused registration.
|
|
31
|
+
|
|
32
|
+
**A proposal must not be identical or close to any competitor or alternative the market
|
|
33
|
+
snapshot names**, nor to any name you find trading in the same category. Drop such a name
|
|
34
|
+
before screening it; if one slips through, report the collision so it is never offered.
|
|
35
|
+
|
|
36
|
+
Propose at least five, so at least three survive screening. One line per proposal on
|
|
37
|
+
why it fits. That line is what the creator reads first.
|
|
38
|
+
|
|
39
|
+
## 2. Screen every candidate
|
|
40
|
+
|
|
41
|
+
Screen each proposal, **and every name the creator listed in the interview**
|
|
42
|
+
(`names-to-screen`, unless it says "none"), the same way. Mark the creator's names as theirs.
|
|
43
|
+
|
|
44
|
+
### Jurisdictions — derive, never assume the EU
|
|
45
|
+
|
|
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.
|
|
70
|
+
- **TMview** (https://www.tmdn.org/tmview/) — the EU office and participating national
|
|
71
|
+
offices in one search.
|
|
72
|
+
- **WIPO Global Brand Database** (https://branddb.wipo.int/) — international (Madrid)
|
|
73
|
+
registrations and many national collections.
|
|
74
|
+
- **The national office of each targeted country** that TMview or WIPO does not already
|
|
75
|
+
cover for you (for example the USPTO for the United States, UKIPO for the United Kingdom).
|
|
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
|
+
|
|
95
|
+
### Classes
|
|
96
|
+
|
|
97
|
+
The Nice classes the product lives in: **9** (software) and **42** (software as a service)
|
|
98
|
+
for every software product, **35** where it is a business-management or CRM tool, and any
|
|
99
|
+
other class the product category implies, each with a one-line reason.
|
|
100
|
+
|
|
101
|
+
### Match types and status
|
|
102
|
+
|
|
103
|
+
Search **identical** marks (ignoring case and spacing) and **near-identical** ones
|
|
104
|
+
(plurals, hyphenation, transposed or substituted letters, common phonetic variants).
|
|
105
|
+
Record only **live** marks: registered, or filed and pending (including under opposition).
|
|
106
|
+
An expired, withdrawn or refused mark is not a conflict.
|
|
107
|
+
|
|
108
|
+
### What to report per query
|
|
109
|
+
|
|
110
|
+
The register, the jurisdictions it covers, the classes and match types searched, the
|
|
111
|
+
result, every live conflicting mark (mark, owner, number, classes, status, the record's
|
|
112
|
+
URL), the search URL, and today's date.
|
|
113
|
+
|
|
114
|
+
## 3. A failure is not an answer
|
|
115
|
+
|
|
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.
|
|
122
|
+
|
|
123
|
+
## 4. Signals beside the registers (recorded, never blocking)
|
|
124
|
+
|
|
125
|
+
- the exact-match `.com` and the main country-code domains of the target countries,
|
|
126
|
+
registered or available;
|
|
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.
|
|
135
|
+
|
|
136
|
+
## What you must never say
|
|
137
|
+
|
|
138
|
+
Never write that a name is "available", "free to use", "safe" or "cleared". This is a
|
|
139
|
+
**minimal trademark screening, not a legal clearance opinion**. The creator should consult an
|
|
140
|
+
IP professional before filing or launching. You report what each register said, with its source.
|
|
141
|
+
|
|
142
|
+
## Condensation
|
|
143
|
+
|
|
144
|
+
Return a brief, not a transcript: candidates, per-register results with URLs and dates,
|
|
145
|
+
collisions, signals, and an explicit list of what could not be checked.
|
|
@@ -0,0 +1,57 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ref": "top_down.brand-name-research",
|
|
3
|
+
"version": "0.2.0",
|
|
4
|
+
"phase": "top_down",
|
|
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
|
+
"preconditions": [
|
|
7
|
+
{
|
|
8
|
+
"kind": "artifact_valid",
|
|
9
|
+
"selector": {
|
|
10
|
+
"family": "vision-brief"
|
|
11
|
+
}
|
|
12
|
+
},
|
|
13
|
+
{
|
|
14
|
+
"kind": "artifact_valid",
|
|
15
|
+
"selector": {
|
|
16
|
+
"family": "market-snapshot"
|
|
17
|
+
}
|
|
18
|
+
}
|
|
19
|
+
],
|
|
20
|
+
"inputs": [
|
|
21
|
+
{
|
|
22
|
+
"family": "vision-brief"
|
|
23
|
+
},
|
|
24
|
+
{
|
|
25
|
+
"family": "market-snapshot"
|
|
26
|
+
},
|
|
27
|
+
{
|
|
28
|
+
"family": "brand-name-screening"
|
|
29
|
+
}
|
|
30
|
+
],
|
|
31
|
+
"outputs": [],
|
|
32
|
+
"stepOutputs": [
|
|
33
|
+
{
|
|
34
|
+
"ref": "brand-name-evidence",
|
|
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
|
+
"description": "Screened brand-name candidates with per-register results and sources, condensed for the produce sibling."
|
|
37
|
+
}
|
|
38
|
+
],
|
|
39
|
+
"method": {
|
|
40
|
+
"guidance": "# Brand Name Research — propose, then screen\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nYou are the **naming researcher**. You do two things: propose names for this product,\nand run a **minimal trademark screening** of every candidate. You do not choose the name\n— the creator does, from what you bring back — and you author no file.\n\n## 1. Propose (at least five)\n\nGround every proposal in what the application already decided:\n\n- the vision's **idea and mission** — what the product is FOR;\n- the market snapshot's **category language** (the words buyers and competitors use) and\n its **tones of voice** (a serious, formal voice wants a different name from a casual one);\n- the **target geographies and languages** — a name must be pronounceable and inoffensive\n in the target countries' main languages. Check that it carries no unfortunate meaning.\n\nPrefer distinctive names (invented or arbitrary) over descriptive ones. A purely\ndescriptive name (\"Building CRM\") is weak as a mark and usually refused registration.\n\n**A proposal must not be identical or close to any competitor or alternative the market\nsnapshot names**, nor to any name you find trading in the same category. Drop such a name\nbefore screening it; if one slips through, report the collision so it is never offered.\n\nPropose at least five, so at least three survive screening. One line per proposal on\nwhy it fits. That line is what the creator reads first.\n\n## 2. Screen every candidate\n\nScreen each proposal, **and every name the creator listed in the interview**\n(`names-to-screen`, unless it says \"none\"), the same way. Mark the creator's names as theirs.\n\n### Jurisdictions — derive, never assume the EU\n\nThe UNION of four sources, never one of them alone:\n\n- the market snapshot's ICP geographies;\n- the vision's compliance detail;\n- the jurisdictions the application DECLARES it operates in — the declared `operating_jurisdictions` context section of your brief,\n read from its configuration: each declared place is a target;\n- **the creator's own answer about where the product's users are** — the `target-jurisdictions`\n answer in your objective (the same decision as the compliance interview's `jurisdictions`\n question, asked once). When the creator names countries there (\"market focus on Germany,\n France, Italy and Spain\"), every one of them is a target, whether or not the market snapshot\n evidences it.\n\nA region tag (\"EMEA\") is not a jurisdiction: name the countries it implies for this product. If\nany EU member state is targeted, the **EU trade mark** (`EU`) applies too, because an EUTM has\neffect in every member state. International registrations (`WO`) are always in scope. Where the\ndata is HOSTED is not a trademark jurisdiction: a mark is protected where it is used in trade.\n\n**Every targeted country gets its own coverage**: a search of its national office (IT → UIBM,\nES → OEPM, DE → DPMA, FR → INPI, …), or a TMview search that includes that office, recorded with\nthat country among the jurisdictions it covers. Say which, per country.\n\n### Registers, and HOW you reach each one\n\n- **EUIPO** — EU trade marks, and international registrations designating the EU.\n- **TMview** (https://www.tmdn.org/tmview/) — the EU office and participating national\n offices in one search.\n- **WIPO Global Brand Database** (https://branddb.wipo.int/) — international (Madrid)\n registrations and many national collections.\n- **The national office of each targeted country** that TMview or WIPO does not already\n cover for you (for example the USPTO for the United States, UKIPO for the United Kingdom).\n\n**Use a register's machine interface, not its web page, wherever one is reachable.** A register's\nweb page is built for a person in a browser: on a real run every one of them returned nothing a\nfetch could read (results rendered in the browser, an empty page, a CAPTCHA, an HTTP 403, a search\nform that never ran). A machine interface returns structured records. Today:\n\n- **EUIPO** publishes a Trademark Search API, but it needs OAuth credentials from a registered\n developer account. Use it only when the application's providers give you access to it; without\n that, you cannot reach it.\n- **TMview and the WIPO Global Brand Database** publish no machine interface.\n- **A national office** may publish one: use it when its own documentation offers open access.\n\nSo on most runs the web page is all you have. Try each register ONCE; when it returns nothing\nreadable, report it as not checked and move on. Do not spend the run retrying a page that renders\nin the browser.\n\n**Report, for every query, how you reached the register**: through its machine interface, or by\nfetching its web page. The landed screening records it, so a reader can tell the two apart.\n\n### Classes\n\nThe Nice classes the product lives in: **9** (software) and **42** (software as a service)\nfor every software product, **35** where it is a business-management or CRM tool, and any\nother class the product category implies, each with a one-line reason.\n\n### Match types and status\n\nSearch **identical** marks (ignoring case and spacing) and **near-identical** ones\n(plurals, hyphenation, transposed or substituted letters, common phonetic variants).\nRecord only **live** marks: registered, or filed and pending (including under opposition).\nAn expired, withdrawn or refused mark is not a conflict.\n\n### What to report per query\n\nThe register, the jurisdictions it covers, the classes and match types searched, the\nresult, every live conflicting mark (mark, owner, number, classes, status, the record's\nURL), the search URL, and today's date.\n\n## 3. A failure is not an answer\n\nSome registers will not answer you. **When you cannot run a search, or cannot read its result,\nreport that register as NOT CHECKED, and say why.** Never infer \"no conflict\" from a search\nengine, from silence, or from your own memory of which marks exist. A candidate with a register\nnot checked is \"screening incomplete\", and one with NO register read is \"not screened\" — still\noffered to the creator, never as clear. Each unread search becomes a check the creator can run by\nhand, from a link the companion builds; you do not need to write that link.\n\n## 4. Signals beside the registers (recorded, never blocking)\n\n- the exact-match `.com` and the main country-code domains of the target countries,\n registered or available;\n- any company or product already trading under the name, with its URL, and **how it relates\n to this product's category**: the SAME JOB (the same work for the same kind of customer, or\n the same Nice class of goods and services), an ADJACENT category, or UNRELATED.\n\n**A product doing the same job under an identical or near-identical name is a COLLISION, not\nmerely a same-category use.** Report it as a collision, beside the competitor collisions, with\nits URL. \"Groundwork — Estimating & Job Suite\", a quote-to-invoice tool for tradespeople, is a\ncollision for a builders' CRM called \"Groundwork\", although no market snapshot listed it.\n\n## What you must never say\n\nNever write that a name is \"available\", \"free to use\", \"safe\" or \"cleared\". This is a\n**minimal trademark screening, not a legal clearance opinion**. The creator should consult an\nIP professional before filing or launching. You report what each register said, with its source.\n\n## Condensation\n\nReturn a brief, not a transcript: candidates, per-register results with URLs and dates,\ncollisions, signals, and an explicit list of what could not be checked.\n",
|
|
41
|
+
"skillRefs": [
|
|
42
|
+
"brand-name-screening"
|
|
43
|
+
],
|
|
44
|
+
"skillBodyRefs": [],
|
|
45
|
+
"contextSources": [
|
|
46
|
+
"operating_jurisdictions"
|
|
47
|
+
],
|
|
48
|
+
"draftableDocumentDefinitionRefs": [],
|
|
49
|
+
"suspendsForClarification": false,
|
|
50
|
+
"briefAdequacyGate": false,
|
|
51
|
+
"briefAdequacyExcludedSources": []
|
|
52
|
+
},
|
|
53
|
+
"executor": "research_agent",
|
|
54
|
+
"approval": "auto",
|
|
55
|
+
"budget": {},
|
|
56
|
+
"onFailure": "keep_and_flag"
|
|
57
|
+
}
|
package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json
ADDED
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"aggregationPolicyRef":"application-creation:aggregation/worst-brand-name-screening-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand-name-screening.candidate","vision.idea","vision.mission","market.category","market.alternative","market.tone-of-voice"],"criterionRef":"application-creation:criterion/brand-name-proposals-grounded-and-distinct","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-proposals-grounded-and-distinct","requirementVersion":1}],"instruction":"Determine whether the PROPOSALS are worth choosing from: each companion-proposed name carries a rationale traceable to the vision's idea or mission and to the market's category language or tone of voice; no proposal is identical or close to a competitor or alternative the market snapshot names, or to a company the evidence found doing the same job under that name — and every such same-job product is recorded as a competitor collision, with a SAME_JOB category relation, never only as a same-category use (a creator-supplied name may collide — it is offered only as an explicit keep-despite-conflict, so it is not a finding here); and every name the creator listed in the interview is on the list, marked as theirs. Nothing in the screening may assert that a name is available, free to use or legally cleared.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a generic rationale, a weakly distinctive or purely descriptive proposal, or fewer than three proposals surviving the screening.","GAP":"A proposal collides with a named competitor or a same-job product, a same-job product with a candidate's name is recorded only as a same-category use, a creator-listed name is missing, or the screening claims a name is available or legally cleared.","INDETERMINATE":"The vision, the market snapshot or the creator's interview answer is not in evidence.","PASS":"Every proposal is grounded and distinct from the named competitors, the creator's names are all present, and nothing claims availability or clearance."}},{"assessesAspects":["brand-name-screening.candidate","brand-name-screening.jurisdiction","brand-name-screening.nice-class","market.icp"],"criterionRef":"application-creation:criterion/brand-name-screening-coverage-and-honesty","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-coverage-and-honesty","requirementVersion":1}],"instruction":"Determine whether the screening COVERS what it declares and reports it HONESTLY: the declared jurisdictions are the union of the market's ICP geographies, the vision, the operating jurisdictions the application declares in its configuration (operatingJurisdictions) and the creator's own target-jurisdictions answer (an EU member state target brings the EU trade mark with it; a region tag is resolved to countries; every country the creator names or the configuration declares is declared and reached by its national office or a TMview search listing it), the Nice classes include 9 and 42 and any class the product category implies, every candidate has a query reaching each declared jurisdiction in those classes for identical and near-identical marks, every query cites a source URL and a date, and no register the evidence reports as unreachable or unread appears with a clear result. A register that could not be checked and is recorded as not checked is a legitimate, honest state, not a finding — UNLESS no register returned a result for any candidate: then the screening screened nothing, however honestly it says so, and that is the worst verdict.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is honest but thin: a class the category implies is missing, or several registers could not be checked and are correctly recorded as such while at least one register returned a result.","GAP":"No register returned a result for ANY candidate (0% coverage: nothing was screened), a country the creator named or the configuration declares (operatingJurisdictions) is not a declared jurisdiction, a query the evidence reports as unreachable or unread is recorded as clear, a declared jurisdiction is never queried while the candidate reads as cleared, or a query has no source.","INDETERMINATE":"The research evidence or the market snapshot is not in evidence, so coverage and honesty cannot be established.","PASS":"Jurisdictions and classes follow from the product, every candidate is queried across them with sources and dates, and nothing unchecked is shown as clear."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-name-screening","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-name-screening-produce"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
|
package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json
ADDED
|
@@ -0,0 +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}
|
|
@@ -0,0 +1,99 @@
|
|
|
1
|
+
# Brand Name Screening — land what the research found
|
|
2
|
+
|
|
3
|
+
### Target Application Framing
|
|
4
|
+
|
|
5
|
+
This knowledge is for configuring behavior in the target application.
|
|
6
|
+
Wildo is the framework surface being used, not the product being built.
|
|
7
|
+
|
|
8
|
+
Read and apply these patterns from the application-developer point of view:
|
|
9
|
+
|
|
10
|
+
- how the application should configure the relevant app-level file
|
|
11
|
+
- how the application should use framework-provided factories, enums, and helpers
|
|
12
|
+
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
13
|
+
|
|
14
|
+
|
|
15
|
+
You turn the evidence a sibling research step gathered into the validated
|
|
16
|
+
**`BrandNameScreening`** — the `brand-name-screening` family. The creator chooses the
|
|
17
|
+
brand name from what you land, so the record must say exactly what was checked and
|
|
18
|
+
what each register returned, and nothing more.
|
|
19
|
+
|
|
20
|
+
You are a **transcriber, not a judge.** There is no field for "this name is clear":
|
|
21
|
+
a candidate's standing is computed from its register queries. Your job is to record
|
|
22
|
+
every query faithfully.
|
|
23
|
+
|
|
24
|
+
## Where your inputs are
|
|
25
|
+
|
|
26
|
+
- The research brief is in your brief under "Evidence gathered for this run".
|
|
27
|
+
- The vision and the market snapshot are in your brief as input sections.
|
|
28
|
+
- A screening already on record, if any, is in your brief too. Keep its candidates and
|
|
29
|
+
their slugs, and re-record them with the new evidence. A re-run adds to the list; it
|
|
30
|
+
does not forget it.
|
|
31
|
+
- The creator's own names are in the interview answers of `top_down.brand-naming`
|
|
32
|
+
(`names-to-screen`). Every one of them is a candidate with origin `CREATOR_SUPPLIED`.
|
|
33
|
+
|
|
34
|
+
## What you emit
|
|
35
|
+
|
|
36
|
+
- `screenedOn` — today's date.
|
|
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.
|
|
44
|
+
- `niceClasses` — each class searched, with why this product lives in it.
|
|
45
|
+
- `candidates` — one per name, with a kebab-case `slug`, the exact `name`, its `origin`,
|
|
46
|
+
a one-line `rationale` for proposals, and:
|
|
47
|
+
- `trademarkQueries` — one per register search the evidence reports: register,
|
|
48
|
+
`accessPath` (`MACHINE_INTERFACE` when the register's published interface answered,
|
|
49
|
+
`WEB_PAGE` when its web page was fetched), jurisdictions covered, classes and match types
|
|
50
|
+
searched, outcome, conflicting marks, source URL, date, and a note for anything a reader needs.
|
|
51
|
+
A TMview search covers every office it included: list each of those countries.
|
|
52
|
+
- `competitorCollisions` — any market competitor or alternative the name is identical
|
|
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.
|
|
59
|
+
|
|
60
|
+
## The rules that keep it true
|
|
61
|
+
|
|
62
|
+
- **A register the evidence could not query or read is `UNKNOWN`, with a note saying
|
|
63
|
+
why.** Never `CLEAR`. Never omit it either: an unrecorded register is an uncovered
|
|
64
|
+
jurisdiction, and the candidate reads as not cleared anyway.
|
|
65
|
+
- **`CONFLICT` exactly when the query found a live identical or near-identical mark**,
|
|
66
|
+
and then every such mark is listed with its source. A conflict with no mark, or a
|
|
67
|
+
mark beside a `CLEAR`, is refused at landing.
|
|
68
|
+
- **Only what the evidence says.** No mark, URL, date or result from memory. A claim
|
|
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.
|
|
78
|
+
- **Keep conflicting proposals on record.** A proposal that conflicts is never offered
|
|
79
|
+
to the creator, and the record of why it was dropped is still worth keeping.
|
|
80
|
+
- **Never write "available", "free to use" or "cleared".** This is a minimal trademark
|
|
81
|
+
screening, not a legal clearance opinion.
|
|
82
|
+
|
|
83
|
+
Follow the `brand-name-screening` skill for the field contracts. Its full text is in
|
|
84
|
+
your brief under "The skills this method tells you to FOLLOW". Read it there; you cannot
|
|
85
|
+
open files.
|
|
86
|
+
|
|
87
|
+
## Quality gate
|
|
88
|
+
|
|
89
|
+
The deterministic `validateBrandNameScreening` runs before anything lands. It refuses a
|
|
90
|
+
contradictory record and REPORTS the rest for the creator's review: an incomplete
|
|
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
|
|
94
|
+
those findings stand honestly rather than inventing results to silence them.
|
|
95
|
+
|
|
96
|
+
After landing, an advisory judge reads the screening for coverage and honesty, and checks
|
|
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
|
|
99
|
+
for the creator's review.
|
|
@@ -0,0 +1,65 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ref": "top_down.brand-name-screening-produce",
|
|
3
|
+
"version": "0.2.0",
|
|
4
|
+
"phase": "top_down",
|
|
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
|
+
"preconditions": [
|
|
7
|
+
{
|
|
8
|
+
"kind": "artifact_valid",
|
|
9
|
+
"selector": {
|
|
10
|
+
"family": "vision-brief"
|
|
11
|
+
}
|
|
12
|
+
},
|
|
13
|
+
{
|
|
14
|
+
"kind": "artifact_valid",
|
|
15
|
+
"selector": {
|
|
16
|
+
"family": "market-snapshot"
|
|
17
|
+
}
|
|
18
|
+
},
|
|
19
|
+
{
|
|
20
|
+
"kind": "step_available",
|
|
21
|
+
"ref": "brand-name-evidence"
|
|
22
|
+
}
|
|
23
|
+
],
|
|
24
|
+
"inputs": [
|
|
25
|
+
{
|
|
26
|
+
"family": "vision-brief"
|
|
27
|
+
},
|
|
28
|
+
{
|
|
29
|
+
"family": "market-snapshot"
|
|
30
|
+
},
|
|
31
|
+
{
|
|
32
|
+
"family": "brand-name-screening"
|
|
33
|
+
}
|
|
34
|
+
],
|
|
35
|
+
"outputs": [
|
|
36
|
+
{
|
|
37
|
+
"family": "brand-name-screening",
|
|
38
|
+
"schemaRef": "saas-specifications:BrandNameScreening",
|
|
39
|
+
"description": "The screened brand-name candidates — jurisdictions and classes searched, per-register results with sources and dates, competitor collisions and domain signals — validated by validateBrandNameScreening. The brand-identity interview offers its `brand-name` CHOICE from it."
|
|
40
|
+
}
|
|
41
|
+
],
|
|
42
|
+
"stepOutputs": [],
|
|
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` — 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
|
+
"skillRefs": [
|
|
46
|
+
"brand-name-screening"
|
|
47
|
+
],
|
|
48
|
+
"skillBodyRefs": [
|
|
49
|
+
"brand-name-screening"
|
|
50
|
+
],
|
|
51
|
+
"contextSources": [
|
|
52
|
+
"operating_jurisdictions"
|
|
53
|
+
],
|
|
54
|
+
"draftableDocumentDefinitionRefs": [],
|
|
55
|
+
"suspendsForClarification": false,
|
|
56
|
+
"briefAdequacyGate": false,
|
|
57
|
+
"briefAdequacyExcludedSources": []
|
|
58
|
+
},
|
|
59
|
+
"executor": "companion_agent",
|
|
60
|
+
"approval": "approve_result",
|
|
61
|
+
"budget": {
|
|
62
|
+
"maxRuns": 3
|
|
63
|
+
},
|
|
64
|
+
"onFailure": "keep_and_flag"
|
|
65
|
+
}
|
|
@@ -0,0 +1,56 @@
|
|
|
1
|
+
# Brand Naming — the umbrella
|
|
2
|
+
|
|
3
|
+
### Target Application Framing
|
|
4
|
+
|
|
5
|
+
This knowledge is for configuring behavior in the target application.
|
|
6
|
+
Wildo is the framework surface being used, not the product being built.
|
|
7
|
+
|
|
8
|
+
Read and apply these patterns from the application-developer point of view:
|
|
9
|
+
|
|
10
|
+
- how the application should configure the relevant app-level file
|
|
11
|
+
- how the application should use framework-provided factories, enums, and helpers
|
|
12
|
+
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
13
|
+
|
|
14
|
+
|
|
15
|
+
This playbook produces nothing itself. It coordinates two children, and the
|
|
16
|
+
`brand-name-screening` is landed by one of them. What lands is the list the creator
|
|
17
|
+
CHOOSES the brand name from, in the `brand-name` question of `top_down.brand-identity`.
|
|
18
|
+
|
|
19
|
+
**The companion proposes; the creator chooses.** Nothing here picks the name.
|
|
20
|
+
|
|
21
|
+
## The children, and why the order is not written here
|
|
22
|
+
|
|
23
|
+
- **`top_down.brand-name-research`** proposes candidate names and screens every
|
|
24
|
+
candidate — proposed or the creator's own — against the public trademark registers,
|
|
25
|
+
with web access. Read-only: it returns a condensed, source-attributed brief.
|
|
26
|
+
- **`top_down.brand-name-screening-produce`** turns that brief into the validated
|
|
27
|
+
`brand-name-screening` family. It becomes eligible once research has returned.
|
|
28
|
+
|
|
29
|
+
Nothing above is a sequence: produce needs research's evidence (`step_available`),
|
|
30
|
+
and that precondition is the whole order.
|
|
31
|
+
|
|
32
|
+
## Composing an objective for research
|
|
33
|
+
|
|
34
|
+
- The **first** round proposes and screens. Name the vision's idea and mission, the
|
|
35
|
+
market's category language and tones of voice, the competitors and alternatives the
|
|
36
|
+
market snapshot names (no candidate may collide with one), and the jurisdictions
|
|
37
|
+
the application targets (from the market's ICP geographies and the vision's
|
|
38
|
+
compliance detail). Ask for at least five proposals, so three survive screening.
|
|
39
|
+
- Include **every name the creator listed** in this playbook's interview (`names-to-screen`,
|
|
40
|
+
unless it says "none"). They are screened exactly like proposals, and marked as theirs.
|
|
41
|
+
- A **second** round is warranted only when the first could not reach a register
|
|
42
|
+
(a CAPTCHA, an outage) or fewer than three proposals survived. Name precisely which
|
|
43
|
+
register, jurisdiction or class was not reached, or ask for new proposals — never
|
|
44
|
+
repeat the first objective.
|
|
45
|
+
|
|
46
|
+
## When to stop
|
|
47
|
+
|
|
48
|
+
Once the screening has landed with at least three offerable proposals, or once a second
|
|
49
|
+
research round could not improve on the first. An UNKNOWN register result is an honest
|
|
50
|
+
answer: it is offered to the creator as "screening incomplete", never as clear.
|
|
51
|
+
|
|
52
|
+
## What this is not
|
|
53
|
+
|
|
54
|
+
A **minimal trademark screening — not a legal clearance opinion.** Nothing in this lane
|
|
55
|
+
may say a name is "available", "free to use" or "cleared". The creator is told to
|
|
56
|
+
consult an IP professional before filing or launching under any name.
|
|
@@ -0,0 +1,76 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ref": "top_down.brand-naming",
|
|
3
|
+
"version": "0.2.0",
|
|
4
|
+
"phase": "top_down",
|
|
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
|
+
"preconditions": [
|
|
7
|
+
{
|
|
8
|
+
"kind": "artifact_valid",
|
|
9
|
+
"selector": {
|
|
10
|
+
"family": "vision-brief"
|
|
11
|
+
}
|
|
12
|
+
},
|
|
13
|
+
{
|
|
14
|
+
"kind": "artifact_valid",
|
|
15
|
+
"selector": {
|
|
16
|
+
"family": "market-snapshot"
|
|
17
|
+
}
|
|
18
|
+
}
|
|
19
|
+
],
|
|
20
|
+
"inputs": [
|
|
21
|
+
{
|
|
22
|
+
"family": "vision-brief"
|
|
23
|
+
},
|
|
24
|
+
{
|
|
25
|
+
"family": "market-snapshot"
|
|
26
|
+
}
|
|
27
|
+
],
|
|
28
|
+
"outputs": [],
|
|
29
|
+
"stepOutputs": [],
|
|
30
|
+
"method": {
|
|
31
|
+
"guidance": "# Brand Naming — the umbrella\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis playbook produces nothing itself. It coordinates two children, and the\n`brand-name-screening` is landed by one of them. What lands is the list the creator\nCHOOSES the brand name from, in the `brand-name` question of `top_down.brand-identity`.\n\n**The companion proposes; the creator chooses.** Nothing here picks the name.\n\n## The children, and why the order is not written here\n\n- **`top_down.brand-name-research`** proposes candidate names and screens every\n candidate — proposed or the creator's own — against the public trademark registers,\n with web access. Read-only: it returns a condensed, source-attributed brief.\n- **`top_down.brand-name-screening-produce`** turns that brief into the validated\n `brand-name-screening` family. It becomes eligible once research has returned.\n\nNothing above is a sequence: produce needs research's evidence (`step_available`),\nand that precondition is the whole order.\n\n## Composing an objective for research\n\n- The **first** round proposes and screens. Name the vision's idea and mission, the\n market's category language and tones of voice, the competitors and alternatives the\n market snapshot names (no candidate may collide with one), and the jurisdictions\n the application targets (from the market's ICP geographies and the vision's\n compliance detail). Ask for at least five proposals, so three survive screening.\n- Include **every name the creator listed** in this playbook's interview (`names-to-screen`,\n unless it says \"none\"). They are screened exactly like proposals, and marked as theirs.\n- A **second** round is warranted only when the first could not reach a register\n (a CAPTCHA, an outage) or fewer than three proposals survived. Name precisely which\n register, jurisdiction or class was not reached, or ask for new proposals — never\n repeat the first objective.\n\n## When to stop\n\nOnce the screening has landed with at least three offerable proposals, or once a second\nresearch round could not improve on the first. An UNKNOWN register result is an honest\nanswer: it is offered to the creator as \"screening incomplete\", never as clear.\n\n## What this is not\n\nA **minimal trademark screening — not a legal clearance opinion.** Nothing in this lane\nmay say a name is \"available\", \"free to use\" or \"cleared\". The creator is told to\nconsult an IP professional before filing or launching under any name.\n",
|
|
32
|
+
"skillRefs": [
|
|
33
|
+
"brand-name-screening"
|
|
34
|
+
],
|
|
35
|
+
"skillBodyRefs": [],
|
|
36
|
+
"elicitation": {
|
|
37
|
+
"questions": [
|
|
38
|
+
{
|
|
39
|
+
"ref": "names-to-screen",
|
|
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
|
+
"kind": "free_text",
|
|
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
|
|
54
|
+
}
|
|
55
|
+
]
|
|
56
|
+
},
|
|
57
|
+
"contextSources": [],
|
|
58
|
+
"draftableDocumentDefinitionRefs": [],
|
|
59
|
+
"choreography": {
|
|
60
|
+
"admits": [
|
|
61
|
+
"top_down.brand-name-screening-produce",
|
|
62
|
+
"top_down.brand-name-research"
|
|
63
|
+
],
|
|
64
|
+
"maximumIterations": 6,
|
|
65
|
+
"maximumLanesPerIteration": 2,
|
|
66
|
+
"maximumDepth": 1,
|
|
67
|
+
"maximumDurationMs": 1800000
|
|
68
|
+
},
|
|
69
|
+
"suspendsForClarification": false,
|
|
70
|
+
"briefAdequacyGate": false,
|
|
71
|
+
"briefAdequacyExcludedSources": []
|
|
72
|
+
},
|
|
73
|
+
"approval": "approve_result",
|
|
74
|
+
"budget": {},
|
|
75
|
+
"onFailure": "keep_and_flag"
|
|
76
|
+
}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"aggregationPolicyRef":"application-creation:aggregation/worst-business-model-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/business-model-grounding-and-plan-coherence","criterionVersion":
|
|
1
|
+
{"aggregationPolicyRef":"application-creation:aggregation/worst-business-model-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/business-model-grounding-and-plan-coherence","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/business-model-grounding-and-plan-coherence","requirementVersion":1}],"instruction":"Assess whether the business model is GROUNDED in what the creator actually stated and coherent with the accepted market and requirements truth. First check that `pricingTiers` matches the pricing-tiers answer: \"creator_stated\" when the creator named tiers, \"proposed\" when the creator asked for tiers to be proposed, \"undecided\" when the creator said the tiers are not decided and asked for no proposal. Then, per status: a \"creator_stated\" plan must trace to a tier the creator named; a \"proposed\" plan is legitimate BECAUSE the creator asked for it, and must carry a `proposalBasis` that names an ICP present in the market snapshot and requirements present in the requirements snapshot; an \"undecided\" sketch has no plans, and that is a complete, honest artifact. Across every status: every targeted ICP and unlocked requirement must exist, the revenue model must be consistent with the plans (an empty undecided sketch is consistent with any revenue model), and no plan may carry a price or scaling axis the creator did not state — not even a proposed one. Treat as a GAP: an invented price or scaling axis; a creator-stated plan the creator never named; a status that contradicts the interview (for example \"undecided\" when the creator named tiers, or plans present when the creator neither named nor asked for them); a proposal with no basis. This family exists to carry the creator's commercial intent, not the evaluator's.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The model is faithful to the interview but a cross-link or a proposal basis is weaker than the accepted truth supports. An undecided answer the creator chose is NOT a concern — it is the honest artifact.","GAP":"A price, scaling axis or stated tier appears that the creator did not give; the tiers status contradicts the interview; a proposal has no basis; or a cross-link names an ICP or requirement that does not exist.","INDETERMINATE":"The interview answers or the accepted market/requirements evidence are absent, stale or insufficient.","PASS":"The tiers status matches the interview; every stated plan traces to what the creator named, every proposed plan carries a basis in the accepted market and requirements truth, an undecided sketch carries no plans, no price or scaling axis is invented, and every cross-link resolves."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/business-model","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.business-model"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
|