@wildo-ai/framework-knowledge 1.1.7 → 1.1.9
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/plugins/wildo/.claude-plugin/plugin.json +1 -1
- 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/runs-judges-and-questions.md +29 -5
- 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 +11 -1
- 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 +11 -1
- package/dist/esm/framework-knowledge.definitions.js.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.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 +3 -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 +59 -10
- 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.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.js +1 -1
- 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 +2 -1
- 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 +5 -5
- package/dist/esm/playbooks/bottom_up.domain-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/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 +85 -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 +40 -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 +41 -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 +199 -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 +201 -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 +67 -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 +76 -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.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-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.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.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 +36 -2
- package/dist/esm/playbooks/top_down.phase-gate/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.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 +30 -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 +117 -28
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +4 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +133 -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 +2 -2
- 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 +22 -6
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +4 -3
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +13 -5
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +5 -2
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/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 +71 -37
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +35 -38
- package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +105 -0
- package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +55 -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 +78 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +63 -0
- package/dist/knowledge/playbooks/top_down.brand-naming/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +65 -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.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.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.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 +10 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +40 -17
- package/dist/knowledge/references/brand.name-choice.config.md +127 -0
- package/dist/knowledge/references/brand.name-screening.config.md +253 -0
- package/dist/knowledge/references/build-plan.task-graph.config.md +64 -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/example.data-seeding.minimal.md +29 -1
- package/dist/knowledge/references/market.snapshot.validation.md +1 -1
- package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +7 -1
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +6 -0
- package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +81 -2
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +10 -0
- package/dist/knowledge/references/saas.website.astro.label-loader.md +9 -0
- package/dist/knowledge/references/saas.website.factories.define-section.md +4 -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.sections.definition-schema.md +11 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +38 -1
- package/dist/knowledge/registries/playbooks.json +68 -20
- package/dist/knowledge/registries/source-tags.json +748 -695
- package/dist/knowledge/rules/live-context-door.md +5 -2
- package/dist/knowledge/skills/INDEX.md +2 -1
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +1 -1
- package/dist/knowledge/skills/brand-name-screening/SKILL.md +154 -0
- package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +394 -0
- package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +65 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +5 -2
- package/dist/knowledge/skills/config-saas/SKILL.md +31 -4
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +14 -1
- package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +81 -2
- package/dist/knowledge/skills/email-add-template/SKILL.md +1 -1
- package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +1 -1
- package/dist/knowledge/skills/inbound-channels/SKILL.md +2 -2
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +11 -1
- 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-companion-prompt-enrichment/SKILL.md +11 -1
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +11 -1
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +1 -1
- package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +1 -1
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +10 -0
- package/dist/knowledge/skills/module-relationships/SKILL.md +6 -4
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +51 -3
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +6 -0
- package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +7 -1
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +10 -0
- package/dist/knowledge/skills/website-factory-advanced/SKILL.md +4 -0
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +84 -3
- 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 +15 -0
- 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 +15 -0
- 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 +15 -0
- 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 +27 -9
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +15 -0
- 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 +15 -0
- 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 +1 -1
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +11 -0
- package/dist/knowledge/topic-index.json +169 -43
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
|
@@ -0,0 +1,65 @@
|
|
|
1
|
+
# Screening procedure: registers, classes, match rules, wording
|
|
2
|
+
|
|
3
|
+
A **minimal trademark screening, not a legal clearance opinion.** This page is the checklist a
|
|
4
|
+
screening follows. It decides what is searched and how a result is recorded. It never decides
|
|
5
|
+
whether a name may be used.
|
|
6
|
+
|
|
7
|
+
## Registers
|
|
8
|
+
|
|
9
|
+
| Register | Covers | Jurisdiction code to record |
|
|
10
|
+
|---|---|---|
|
|
11
|
+
| EUIPO eSearch plus — https://euipo.europa.eu/eSearch/ | EU trade marks; international registrations designating the EU | `EU` (plus `WO` for the designations it shows) |
|
|
12
|
+
| TMview — https://www.tmdn.org/tmview/ | The EU office and participating national offices in one search | each country whose office the search included, and `EU` |
|
|
13
|
+
| WIPO Global Brand Database — https://branddb.wipo.int/ | International (Madrid) registrations and many national collections | `WO`, plus each national collection searched |
|
|
14
|
+
| A national office (USPTO, UKIPO, DPMA, INPI, …) | That country only | the country's ISO code — never `EU` or `WO` |
|
|
15
|
+
|
|
16
|
+
Several of these render in the browser or sit behind a CAPTCHA (TMview, WIPO). When a search
|
|
17
|
+
cannot be run or its result cannot be read, the query is **`UNKNOWN` with a note saying why**.
|
|
18
|
+
|
|
19
|
+
## Jurisdictions
|
|
20
|
+
|
|
21
|
+
Derived, never assumed:
|
|
22
|
+
|
|
23
|
+
1. the market snapshot's ICP geographies (resolve `EMEA`, `NAM`, … to the countries they mean
|
|
24
|
+
for this product);
|
|
25
|
+
2. the vision's compliance detail and the application's declared operating jurisdictions;
|
|
26
|
+
3. `EU` whenever any EU member state is targeted;
|
|
27
|
+
4. `WO`, always: an international registration can designate any targeted country.
|
|
28
|
+
|
|
29
|
+
A candidate is covered in a jurisdiction only by a `CLEAR` query that searched **every declared
|
|
30
|
+
class with both match types**. Anything less leaves it uncovered, and the candidate not cleared.
|
|
31
|
+
|
|
32
|
+
## Nice classes
|
|
33
|
+
|
|
34
|
+
| Class | Covers | Searched when |
|
|
35
|
+
|---|---|---|
|
|
36
|
+
| 9 | Downloadable software, apps | always, for a software product |
|
|
37
|
+
| 42 | Software as a service, hosting, development | always, for a software product |
|
|
38
|
+
| 35 | Business management, CRM, marketing services | the product manages a business process or customers |
|
|
39
|
+
| other | e.g. 36 (financial), 41 (education), 44 (health), 45 (legal) | the product category implies it |
|
|
40
|
+
|
|
41
|
+
Record each with a one-line reason.
|
|
42
|
+
|
|
43
|
+
## Match types and status
|
|
44
|
+
|
|
45
|
+
- **Identical**: the same mark, ignoring case and spacing.
|
|
46
|
+
- **Near-identical**: plurals, hyphenation, transposed or substituted letters, and common
|
|
47
|
+
phonetic variants ("Siteline" against "SiteLine", "Sightline").
|
|
48
|
+
- Record only **live** marks: `REGISTERED`, or `PENDING` (filed, including under opposition).
|
|
49
|
+
An expired, withdrawn or refused mark is not a conflict.
|
|
50
|
+
|
|
51
|
+
## Signals beside the registers (recorded, never blocking)
|
|
52
|
+
|
|
53
|
+
- Exact-match `.com` and the main ccTLDs of the target countries: `REGISTERED`, `AVAILABLE` or `UNKNOWN`.
|
|
54
|
+
- Companies or products already trading under the name in the same category, with their URL.
|
|
55
|
+
- **Competitor collisions**: a name identical or close to a competitor or alternative the
|
|
56
|
+
market snapshot names. A collision makes a proposal unofferable, like a conflict does.
|
|
57
|
+
|
|
58
|
+
## How a result is worded
|
|
59
|
+
|
|
60
|
+
| Write | Never write |
|
|
61
|
+
|---|---|
|
|
62
|
+
| "No live identical or near-identical mark found in classes 9, 42 on EUIPO (searched 2026-10-01)." | "The name is available." |
|
|
63
|
+
| "Not checked: TMview requires a browser session the research could not run." | "TMview: clear." (when it was not read) |
|
|
64
|
+
| "Conflict: KEYSTONE, EUTM 0123456, classes 9 and 42, registered." | "Probably fine for software." |
|
|
65
|
+
| "A minimal trademark screening, not a legal clearance opinion." | "Cleared for use." |
|
|
@@ -509,8 +509,11 @@ its subprocessors; reaching the processor is the transfer the operator answers f
|
|
|
509
509
|
|
|
510
510
|
**The `international-transfers` fact is COMPUTED from those determinations** — you never declare it.
|
|
511
511
|
It carries each determined entry, the origin jurisdictions, `undeterminedRecipients` — a register entry
|
|
512
|
-
with no determination, or a configured provider the register does not establish —
|
|
513
|
-
a declared origin a TRANSFER names no safeguard for
|
|
512
|
+
with no determination, or a configured provider the register does not establish — `safeguardGaps`:
|
|
513
|
+
a declared origin a TRANSFER names no safeguard for — and `operatorHostingRegions`: where the operator's
|
|
514
|
+
OWN infrastructure holds the data (`operatorComplianceIdentity.hostingRegions`), or `null` when the
|
|
515
|
+
operator has not declared it. State a `null` as the operator's hosting location not yet being declared;
|
|
516
|
+
it never means the data is held nowhere, and it never supports "no international transfer".
|
|
514
517
|
|
|
515
518
|
**Completeness** — do not round any state up.
|
|
516
519
|
|
|
@@ -97,10 +97,31 @@ When you change `wildo.saas.config.ts` or infrastructure config files, update
|
|
|
97
97
|
task instead of silently skipping specification review.
|
|
98
98
|
|
|
99
99
|
|
|
100
|
-
### Step 4:
|
|
101
|
-
|
|
102
|
-
|
|
103
|
-
|
|
100
|
+
### Step 4: Apply the declaration, then verify
|
|
101
|
+
|
|
102
|
+
The running application does not read `wildo.saas.config.ts`. It reads the
|
|
103
|
+
copy apps-manager STORED at registration, and that copy covers
|
|
104
|
+
`engineCapabilities`, `providers`, `providerConfigurations`,
|
|
105
|
+
`frontendServices`, `minions`, `workers`, `organizationTypes`,
|
|
106
|
+
`systemsOfRecord` and the app's display identity. An edit to any of them does
|
|
107
|
+
nothing until it is applied:
|
|
108
|
+
|
|
109
|
+
- `wildo local dev` applies it on every start (registration reapplies the
|
|
110
|
+
declaration) and names each slice it applied, so restarting the stack is
|
|
111
|
+
enough. It is the step to use after adding or removing a minion or worker:
|
|
112
|
+
registration is what mints and revokes their credentials.
|
|
113
|
+
- `wildo config reapply-declaration` applies it to a stack that is already
|
|
114
|
+
running. Add `--dry-run` to see what it would change. It changes no
|
|
115
|
+
infrastructure, and no credential except one: a changed `minions` set
|
|
116
|
+
reconciles the minions' backing-service credentials, so restart the minions
|
|
117
|
+
afterwards. It does not mint a new worker's credential.
|
|
118
|
+
- `wildo config sync` also applies it, but it also regenerates env and
|
|
119
|
+
provider artifacts, so do not reach for it just to apply a declaration edit.
|
|
120
|
+
|
|
121
|
+
`wildo config validate` (or `--domain declaration`) and `wildo local doctor`
|
|
122
|
+
both report a stored config that is behind the file, naming the slices.
|
|
123
|
+
Then ensure all listed modules / minions / workers resolve from disk and the
|
|
124
|
+
requested provider scopes materialize.
|
|
104
125
|
|
|
105
126
|
## Worked Example
|
|
106
127
|
|
|
@@ -215,6 +236,8 @@ What is **not** in this block (and shouldn't be):
|
|
|
215
236
|
and each minion and worker that should be traceable
|
|
216
237
|
- [ ] `services` keys referenced by `modules[*].services` actually exist in `services`
|
|
217
238
|
- [ ] Companion sees the updated module list (re-run companion introspection)
|
|
239
|
+
- [ ] The stored config matches the file: `wildo config validate --domain declaration`
|
|
240
|
+
reports no stale slice (or the stack was restarted with `wildo local dev`)
|
|
218
241
|
- [ ] No compliance declaration carries an invented value — every one is either the operator's
|
|
219
242
|
own answer or absent (absent is reported as an open gap; invented is published as fact)
|
|
220
243
|
|
|
@@ -232,6 +255,7 @@ Run from the app root:
|
|
|
232
255
|
| **No placeholder in a compliance declaration** (must return empty) | `rg -n "TODO\|TBD\|PLACEHOLDER\|example\.com\|Acme" wildo.saas.config.ts` |
|
|
233
256
|
| Which provider is selected for telemetry | `rg -n "OBSERVABILITY_TELEMETRY\]:\s*\{" -A2 wildo.saas.config.ts` |
|
|
234
257
|
| **Which runtimes declare it** (compare against the runtimes that should be traceable) | `rg -n "^\s+<telemetryProviderRef>:\s*\{" wildo.saas.config.ts` |
|
|
258
|
+
| **Stored config matches the file** (no stale slice reported) | `wildo config validate --domain declaration` |
|
|
235
259
|
|
|
236
260
|
The third invariant (modules ↔ folders) is the high-signal one — a
|
|
237
261
|
module declared in config without a matching folder breaks `pnpm dev`
|
|
@@ -251,6 +275,7 @@ missing it does not appear until a token is provisioned.
|
|
|
251
275
|
| "Comment out a module temporarily" | Dead entries confuse tooling and the spec layer; remove the entry or gate the module through an explicit module-owned product feature. |
|
|
252
276
|
| "Inline the AI provider key here" | Provider secrets MUST stay in secrets/env. Config only declares **policy** (which providers are allowed); the credentials sit in `wildo-secrets` or env. |
|
|
253
277
|
| "Skip `dataServices.*` prefixes — defaults work" | Defaults collide across apps in shared infra; the prefix declaration is what isolates state per app/environment. |
|
|
278
|
+
| "`wildo config validate` passed, so the capability is on" | Validation checks the file. The runtime reads the declaration apps-manager stored, which only changes when it is applied (`wildo local dev`, or `wildo config reapply-declaration`). The `declaration` domain of `validate` says whether it has been. |
|
|
254
279
|
| "I'll add a new key not in the schema, the framework will pick it up" | The schema is the contract — unknown keys are dropped or error. Add the field through the framework first if a new dimension is needed. |
|
|
255
280
|
| "Put a placeholder entity name in now and fix it later" | A produced document quotes it as fact. An absent declaration is reported as an open gap a reader can see; an invented one is published. Leave it out. |
|
|
256
281
|
| "The identity needs every field, so I'll wait until I have them all" | Every part is independently declarable — record the half you know. Waiting is how the answer ends up edited into a document that a regeneration then replaces. |
|
|
@@ -264,6 +289,8 @@ missing it does not appear until a token is provisioned.
|
|
|
264
289
|
- Module name in config with no folder on disk (catch with the **modules ↔ folders agree** comm invariant — must return empty).
|
|
265
290
|
- Minion / worker entry pointing at a non-existent `path` (catch with the **Minion / worker paths exist** check — must return no `MISSING:` lines).
|
|
266
291
|
- Engine capability block lacking `enabled:` (catch with the **Each engine capability declares `enabled:`** check — counts must match).
|
|
292
|
+
- An `engineCapabilities` (or provider, minion, worker) edit that "does nothing" at runtime: the
|
|
293
|
+
stored declaration was not applied (catch with the **Stored config matches the file** check above).
|
|
267
294
|
- Frontend service with no `frontendType` (implicit defaults are framework-version-dependent; declare it explicitly).
|
|
268
295
|
- A minion or worker expected to be traceable whose scope omits the selected
|
|
269
296
|
`OBSERVABILITY_TELEMETRY` provider (catch with the **which runtimes declare it** read above —
|
|
@@ -42,10 +42,23 @@ blocked.
|
|
|
42
42
|
operatorComplianceIdentity: {
|
|
43
43
|
legalEntityName: 'Wonder Software SAS',
|
|
44
44
|
registeredAddress: '1 rue de la Paix, 75002 Paris, France',
|
|
45
|
-
// privacyContact, roleAllocations and
|
|
45
|
+
// privacyContact, roleAllocations, lawfulBases and hostingRegions may all follow later.
|
|
46
46
|
},
|
|
47
47
|
```
|
|
48
48
|
|
|
49
|
+
`hostingRegions` says where the operator's OWN infrastructure hosts the data (`['France (eu-west-3)']`).
|
|
50
|
+
It is the operator's region, not a vendor's: a provider's region is `providerComplianceChoices.<ref>.processingRegion`,
|
|
51
|
+
and a hosting company that processes on your behalf also belongs in the processor register.
|
|
52
|
+
|
|
53
|
+
To see every part still owed, with the rest of what stands between the application and launch:
|
|
54
|
+
|
|
55
|
+
```bash
|
|
56
|
+
wildo context launch-blockers # each open decision, where it is decided, what settles it
|
|
57
|
+
wildo context launch-blockers --json # the same list as a document
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
It reports and never fails: a missing part is marked, and declaring it removes it on the next read.
|
|
61
|
+
|
|
49
62
|
What the schema still refuses, and why it is not a contradiction: it refuses an **incoherent** answer,
|
|
50
63
|
never an **absent** one.
|
|
51
64
|
|
|
@@ -247,6 +247,56 @@ The report separates retained occurrence coverage from invocation success, selec
|
|
|
247
247
|
export const SCHEDULED_INITIAL_ADMISSION_MAX_AGE_MS = 5 * 60 * 1000;
|
|
248
248
|
export const SCHEDULED_INITIAL_ADMISSION_FUTURE_SKEW_MS = 30 * 1000;
|
|
249
249
|
|
|
250
|
+
/**
|
|
251
|
+
* How long after its token expired a delivery may still be RECORDED as a missed occurrence (#2212).
|
|
252
|
+
*
|
|
253
|
+
* An expired token stays cryptographically valid forever, so without a horizon anyone able to
|
|
254
|
+
* publish onto the application's queue could replay a captured token of any age and plant a
|
|
255
|
+
* "missed while absent" record. The horizon is APPROXIMATELY the job-row retention: within it, a
|
|
256
|
+
* replayed token almost always meets the occurrence's existing row and is recognised as already
|
|
257
|
+
* held; beyond it, no genuine backlog is plausible and the delivery is rejected as a trust failure.
|
|
258
|
+
* "Approximately" because a row that ran on time expires measured from its completion while the
|
|
259
|
+
* horizon is measured from the token's expiry, which leaves a window of a few minutes in which a
|
|
260
|
+
* replay is recorded as a fresh miss. It never runs anything, and archived run evidence still wins
|
|
261
|
+
* the occurrence in coverage.
|
|
262
|
+
*
|
|
263
|
+
* Equal to `JOB_EXECUTION_TTL_SECONDS` (declared further down, outside this shared block, so it
|
|
264
|
+
* cannot be referenced here without a temporal-dead-zone hazard); a test pins the two together, so
|
|
265
|
+
* changing one without the other fails.
|
|
266
|
+
*/
|
|
267
|
+
export const SCHEDULED_LATE_DELIVERY_HORIZON_MS = 30 * 24 * 60 * 60 * 1000;
|
|
268
|
+
|
|
269
|
+
/**
|
|
270
|
+
* Why an AUTHENTIC scheduled delivery reached the application too late to be admitted (#2212).
|
|
271
|
+
*
|
|
272
|
+
* Either way the occurrence was MISSED: it is recorded as such and not run, and the schedule
|
|
273
|
+
* continues with its next occurrence. The two gates differ in WHO was late, which is why they are
|
|
274
|
+
* kept apart:
|
|
275
|
+
*
|
|
276
|
+
* - `TOKEN_EXPIRED` — the delivery sat in the queue for longer than its token lives, so nothing
|
|
277
|
+
* consumed the application's scheduled queue for that long: the backend (or minion) was stopped,
|
|
278
|
+
* restarting or crash-looping. This is the common case after a restart.
|
|
279
|
+
* - `OUTSIDE_ADMISSION_WINDOW` — the token is still current, but the occurrence it names is older
|
|
280
|
+
* than the window. The scheduler may sign up to the window's length AFTER the occurrence, so the
|
|
281
|
+
* delay is shared between the scheduler's publication and the application's consumption, and
|
|
282
|
+
* cannot be attributed to the application alone.
|
|
283
|
+
*
|
|
284
|
+
* A late delivery is never an authentication failure: its signature, issuer and audience were
|
|
285
|
+
* proven before it was classified late. A token that cannot be proven authentic, that names an
|
|
286
|
+
* occurrence in the future, or that expired longer ago than `SCHEDULED_LATE_DELIVERY_HORIZON_MS`
|
|
287
|
+
* is a trust failure instead and is reported loudly.
|
|
288
|
+
*
|
|
289
|
+
* Missed occurrences are SKIPPED, never caught up: that is the established cron behaviour (a
|
|
290
|
+
* Kubernetes `CronJob` past its `startingDeadlineSeconds`, a Quartz trigger with the do-nothing
|
|
291
|
+
* misfire instruction), and it keeps the short signed window a replay bound rather than a credential.
|
|
292
|
+
*/
|
|
293
|
+
export enum ScheduledDeliveryLateness {
|
|
294
|
+
/** The signed delivery token's `exp` passed before the delivery was consumed. */
|
|
295
|
+
TOKEN_EXPIRED = 'token_expired',
|
|
296
|
+
/** The token is current, but the occurrence it names is older than `SCHEDULED_INITIAL_ADMISSION_MAX_AGE_MS`; scheduler and consumer share the delay. */
|
|
297
|
+
OUTSIDE_ADMISSION_WINDOW = 'outside_admission_window',
|
|
298
|
+
}
|
|
299
|
+
|
|
250
300
|
/** How the handler's complete effects tolerate execution after an uncertain outcome. */
|
|
251
301
|
export enum ScheduledReplaySafety {
|
|
252
302
|
/** No automatic repetition; a failed call can already have committed effects. */
|
|
@@ -320,11 +370,41 @@ export const ScheduledEvidencePolicySchema = z.object({
|
|
|
320
370
|
});
|
|
321
371
|
export type ScheduledEvidencePolicy = z.infer<typeof ScheduledEvidencePolicySchema>;
|
|
322
372
|
|
|
373
|
+
/** How a scheduled occurrence's archived evidence came to exist. */
|
|
323
374
|
export enum ScheduledEvidenceSource {
|
|
375
|
+
/** The handler ran and reported completion. */
|
|
324
376
|
EXECUTION = 'execution',
|
|
377
|
+
/** The handler's reconciler established that an interrupted run completed. */
|
|
325
378
|
RECONCILIATION = 'reconciliation',
|
|
379
|
+
/** An operator confirmed completion of an occurrence held for review. */
|
|
326
380
|
OPERATOR_CONFIRMATION = 'operator_confirmation',
|
|
381
|
+
/** An operator decided an occurrence held for review will not run. */
|
|
327
382
|
ABANDONMENT = 'abandonment',
|
|
383
|
+
/**
|
|
384
|
+
* The occurrence was never run: its authentic delivery reached the application after the
|
|
385
|
+
* admission deadline (see `ScheduledDeliveryLateness` for who was late). Coverage reads it as an
|
|
386
|
+
* EXPLAINED gap: the slot stays missing, because the occurrence did not run, and the record says
|
|
387
|
+
* why — rather than an unexplained one.
|
|
388
|
+
*/
|
|
389
|
+
LATE_DELIVERY = 'late_delivery',
|
|
390
|
+
}
|
|
391
|
+
|
|
392
|
+
/**
|
|
393
|
+
* The terminal invocation status each evidence source records — the one place that pairing is stated.
|
|
394
|
+
*
|
|
395
|
+
* A source whose occurrence never reached a successful invocation records `FAILED`; this follows the
|
|
396
|
+
* precedent `ABANDONMENT` set, and the SOURCE (never the status) is what says why it did not run.
|
|
397
|
+
*/
|
|
398
|
+
export function scheduledEvidenceInvocationStatus(source: ScheduledEvidenceSource): JobExecutionStatus {
|
|
399
|
+
switch (source) {
|
|
400
|
+
case ScheduledEvidenceSource.EXECUTION:
|
|
401
|
+
case ScheduledEvidenceSource.RECONCILIATION:
|
|
402
|
+
case ScheduledEvidenceSource.OPERATOR_CONFIRMATION:
|
|
403
|
+
return JobExecutionStatus.COMPLETED;
|
|
404
|
+
case ScheduledEvidenceSource.ABANDONMENT:
|
|
405
|
+
case ScheduledEvidenceSource.LATE_DELIVERY:
|
|
406
|
+
return JobExecutionStatus.FAILED;
|
|
407
|
+
}
|
|
328
408
|
}
|
|
329
409
|
export enum ScheduledEvidenceResultStatus {
|
|
330
410
|
CAPTURED = 'captured',
|
|
@@ -354,8 +434,7 @@ export const ScheduledRunEvidenceSchema = ScheduledRunEvidenceFieldsSchema.super
|
|
|
354
434
|
: evidence.jobType !== JobType.SCHEDULED_CRON || !(evidence.batchRef || evidence.operationPathKey))) {
|
|
355
435
|
ctx.addIssue({ code: 'custom', message: 'Evidence requires exactly one scheduled batch, operation or minion target' });
|
|
356
436
|
}
|
|
357
|
-
|
|
358
|
-
if (evidence.invocationStatus !== expectedStatus) {
|
|
437
|
+
if (evidence.invocationStatus !== scheduledEvidenceInvocationStatus(evidence.source)) {
|
|
359
438
|
ctx.addIssue({ code: 'custom', path: ['invocationStatus'], message: 'Terminal outcome must agree with evidence source' });
|
|
360
439
|
}
|
|
361
440
|
|
|
@@ -381,7 +381,7 @@ Run from the app root. Replace `<email-root>` with the actual owning scanner dir
|
|
|
381
381
|
| Definition declares `type:` | `rg -n "type:\s+EmailTemplateType\." <email-root>/<template>/template.tsx` |
|
|
382
382
|
| Subject / body read from `labels.` | `rg -n "labels\.[a-zA-Z]+" <email-root>/<template>/template.tsx` |
|
|
383
383
|
| Locale files exist for every supported locale | `ls <email-root>/<template>/labels.*.ts` |
|
|
384
|
-
| Other-locale files are the generated ones (must return empty) | `rg -
|
|
384
|
+
| Other-locale files are the generated ones (must return empty) | `rg --files-without-match "DO NOT EDIT THIS FILE MANUALLY" <email-root>/<template>/labels.<locale>.ts` (run for each non-primary locale) |
|
|
385
385
|
| Owning registry/scanner and ref mapping are present | `rg -n "scanEmailTemplateDirectory\|keyFromPath\|emailTemplateDefinitions" <registry-file>` (inspect the mapping; scanned templates need no per-template map entry) |
|
|
386
386
|
| Per-locale label files share the same key set | `comm -23 <(rg -o '\\w+:' <email-root>/<template>/labels.<primary-locale>.ts \| sort -u) <(rg -o '\\w+:' <email-root>/<template>/labels.<locale>.ts \| sort -u)` (output should be empty) |
|
|
387
387
|
| Sender resolves template by typed id | `rg -n "EmailTemplateType\.[A-Z_]+" backend-api/src/modules/<module>/` |
|
|
@@ -222,7 +222,7 @@ Run from the app root, substituting `<source>` and `<target>`:
|
|
|
222
222
|
| Lock file is up-to-date with both locales | `rg -n '"localeCode":\s*"(<source>\|<target>)"' wildo-saas.lock.json` |
|
|
223
223
|
| **No empty values** in any per-unit file (must be empty) | `rg -n '":\s*""' backend-api/src/engine/i18n -g '*.ts'` |
|
|
224
224
|
| **No hard-coded product strings** in JSX touched in this change | `rg -n ">[A-Z][a-z]+ [A-Z][a-z]" frontend/src/modules/<slug>/` |
|
|
225
|
-
| Every per-unit file preserves the auto-generated header | `rg -
|
|
225
|
+
| Every per-unit file preserves the auto-generated header | `rg --files-without-match "DO NOT EDIT THIS FILE MANUALLY" backend-api/src/engine/i18n -g '*.ts'` (output should be empty) |
|
|
226
226
|
| **No** monolithic `labels.<locale>.ts` (must be empty) | `rg --files backend-api/src/engine/i18n -g 'labels.*.ts' \| rg -v '/'` |
|
|
227
227
|
|
|
228
228
|
The high-signal invariant is **"per-unit count matches between
|
|
@@ -256,9 +256,9 @@ export const matterMailInboundHandler = defineInboundChannelHandler({
|
|
|
256
256
|
|
|
257
257
|
- `rg "inboundHandlers:" backend-api/src/modules` — every handler file is registered somewhere.
|
|
258
258
|
- `rg "APP_ADMIN_SUPER_ADMIN" backend-api/src/modules/*/inbound` — must return nothing.
|
|
259
|
-
- `rg "HMAC_SHA256_HEADER" -l backend-api/src/modules/*/inbound | xargs rg -
|
|
259
|
+
- `rg "HMAC_SHA256_HEADER" -l backend-api/src/modules/*/inbound | xargs rg --files-without-match "dedupKey"` — must return nothing.
|
|
260
260
|
- `rg -c "isDefault: true" backend-api/src/modules/*/inbound` — sums to one per channel.
|
|
261
|
-
- `rg -l "defineInboundChannelHandler" backend-api/src/modules | xargs rg -
|
|
261
|
+
- `rg -l "defineInboundChannelHandler" backend-api/src/modules | xargs rg --files-without-match "minimumSenderAssurance"` — must return nothing.
|
|
262
262
|
- `rg -n "message\.(text|strippedReply)" backend-api/src/modules/*/inbound` — every read of the body; none may
|
|
263
263
|
choose an organization, a record to write into, or a recipient.
|
|
264
264
|
|
|
@@ -97,6 +97,9 @@ deployed environment shares them).
|
|
|
97
97
|
(added a backing service, changed a port, swapped a `BackingServiceSource`)
|
|
98
98
|
- Generated artifacts are missing or stale and need regeneration
|
|
99
99
|
(`config.json`, the compose file, `.env.wildo-platform`)
|
|
100
|
+
- A process refuses a generated file, or its error says to regenerate or to
|
|
101
|
+
run `wildo config sync` (provider runtime artifacts, CSP, compliance modules,
|
|
102
|
+
the lockfile) — read `references/derived-artifact-currency.md`
|
|
100
103
|
- The user wants to rotate local credentials (rare; explicit opt-in)
|
|
101
104
|
- Platform/application state is absent, partial, or inconsistent and must be
|
|
102
105
|
repaired without deleting backing data (`wildo local init`)
|
|
@@ -143,7 +146,10 @@ the user's situation, including whether another application owns the running pla
|
|
|
143
146
|
|
|
144
147
|
If the user is describing a symptom rather than an action ("the dev
|
|
145
148
|
companion can't reach mongodb", "the stack won't start"), read
|
|
146
|
-
`references/local-environment-troubleshooting.md` first to triage.
|
|
149
|
+
`references/local-environment-troubleshooting.md` first to triage. If the
|
|
150
|
+
symptom names a generated file, or says it was "generated before" a check or
|
|
151
|
+
a contract change, read `references/derived-artifact-currency.md` instead: the
|
|
152
|
+
fix is to regenerate that file, never to edit it or the code that refused it.
|
|
147
153
|
|
|
148
154
|
A live `wildo local dev` owner blocks full initialization because convergence
|
|
149
155
|
stops tracked processes and rewrites the shared platform generation. For a
|
|
@@ -383,6 +389,10 @@ What this loop does **not** do:
|
|
|
383
389
|
(move the CLI and this application to a release, and what it owes afterwards),
|
|
384
390
|
then `wildo align-deps`: why the second install is not optional, and the
|
|
385
391
|
undeclared-peer trap that no repeated install can fix
|
|
392
|
+
- `references/derived-artifact-currency.md` — every derived artifact in the
|
|
393
|
+
application: where it lives, which command regenerates it, how to tell it is
|
|
394
|
+
current (and which ones nothing can check), and the refusal messages a stale
|
|
395
|
+
one produces
|
|
386
396
|
- `references/local-environment-troubleshooting.md` — symptom-driven
|
|
387
397
|
triage for the most common failure modes (missing manifest, missing
|
|
388
398
|
config.json, arm64 image incompatibilities, docker-credential-helper
|
package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md
ADDED
|
@@ -0,0 +1,122 @@
|
|
|
1
|
+
# Derived artifacts and their currency
|
|
2
|
+
|
|
3
|
+
Read this when:
|
|
4
|
+
|
|
5
|
+
- a dev server, the backend, a worker, a minion or the dev companion refuses to start and its error
|
|
6
|
+
names a generated file, or tells you to "regenerate" or to run `wildo config sync`;
|
|
7
|
+
- something behaves as if an earlier version of your configuration were still in force;
|
|
8
|
+
- you just ran `wildo update`, or changed `providers` / `services` in `wildo.saas.config.ts`;
|
|
9
|
+
- you need to know whether a file under `.wildo-saas/` or a `src/generated/` folder is safe to
|
|
10
|
+
delete, safe to edit (never), or must be committed.
|
|
11
|
+
|
|
12
|
+
### Derived artifacts: where they live, how to tell they are current, what regenerates them
|
|
13
|
+
|
|
14
|
+
Much of what your application runs is **derived**: written by a `wildo` command or a dev watcher from
|
|
15
|
+
something you authored. A derived file never fails at the moment it goes stale. It fails later, far
|
|
16
|
+
from its cause, when a process that reads it refuses it — and by then the error reads like a bug in
|
|
17
|
+
your code or in the framework. It almost never is.
|
|
18
|
+
|
|
19
|
+
Four facts govern every row below:
|
|
20
|
+
|
|
21
|
+
- **A derived file is never edited by hand.** Fix the authored source, then regenerate. A hand edit is
|
|
22
|
+
overwritten by the next regeneration and leaves no trace of why it reverted.
|
|
23
|
+
- **Most derived files are regenerated by a COMMAND, not by a watcher.** `wildo local dev` rebuilds
|
|
24
|
+
your packages as you edit them, and when it STARTS it regenerates the provider runtime artifacts if a
|
|
25
|
+
generated module is missing or a reader would refuse one of the JSON artifacts — but it never refreshes the CSP file, the labels or the docs,
|
|
26
|
+
and it does not watch the provider artifacts once running. A framework update can change what a
|
|
27
|
+
reader requires of those files while their inputs stay the same, so they go stale without anything
|
|
28
|
+
you did.
|
|
29
|
+
- **When a reader refuses a derived file, its message names the command that regenerates it.** That
|
|
30
|
+
is the fix. Run it; do not "repair" the reader, the provider, or the authored config to make the
|
|
31
|
+
refusal go away.
|
|
32
|
+
- **Regenerating is safe.** `wildo config sync` never rotates a secret unless you pass
|
|
33
|
+
`--rotate-secrets`; it only adds framework-managed secrets that are missing. Apart from that, the
|
|
34
|
+
one authored file it can change is a backend `package.json` (and the root `pnpm.overrides`), when
|
|
35
|
+
`systemsOfRecord` is declared and the library it needs is not: run `pnpm install` after that.
|
|
36
|
+
Regenerating a current file changes nothing.
|
|
37
|
+
|
|
38
|
+
#### When a running process refuses a generated file
|
|
39
|
+
|
|
40
|
+
1. **Read the refusal for a command.** The messages in the table below each name one.
|
|
41
|
+
2. **Date the artifact.** Provider runtime artifacts carry a `generatedAt` field; for anything else use
|
|
42
|
+
the file's modification time. Older than the last change to your `@wildo-ai/*` versions
|
|
43
|
+
(`pnpm-lock.yaml`), to `wildo.saas.config.ts`, or to `wildo.infra.<env>.config.ts`? It is stale.
|
|
44
|
+
3. **Run the command it names**, from the application root. For the provider runtime artifacts that
|
|
45
|
+
is `wildo -y config sync --local` (add `--env <env>` for one environment). `-y` keeps it from
|
|
46
|
+
stopping at the env-file prompt: it then leaves existing `.env` files alone, which is what you want
|
|
47
|
+
here, and still writes every provider runtime artifact.
|
|
48
|
+
4. **Let the refused process restart.** Under `wildo local dev` each process is supervised and
|
|
49
|
+
restarts on its own within seconds; otherwise restart that one process. Do not restart the stack.
|
|
50
|
+
5. **Confirm**: the process logs that it started, and the artifact's `generatedAt` is now.
|
|
51
|
+
|
|
52
|
+
| The refusal says (abbreviated) | Stale artifact | Regenerate with |
|
|
53
|
+
|---|---|---|
|
|
54
|
+
| `refused to serve frontend provider configuration it was handed … declares no publicConfigSchema whose keys can be read … generated before this check existed` | the frontend provider bootstrap: `.wildo-saas/generated/providers/frontend-services.runtime-providers.generated.json` when a website or docs build refuses, `backend-api/src/generated/wildo-provider-runtime.generated.ts` when the backend's `/application-config` refuses | `wildo -y config sync --local` |
|
|
55
|
+
| `generated provider runtime artifact at … does not satisfy the current contract` | a `.wildo-saas/generated/providers/*.runtime-providers.generated.json` file | `wildo -y config sync --local` |
|
|
56
|
+
| `generated before the contract changed. Regenerate it … and restart` · `The artifact is stale for this package` | `backend-api/src/generated/wildo-provider-runtime.generated.ts` | `wildo -y config sync --local` |
|
|
57
|
+
| `runtime artifact lists no facet modules` | the same module, generated before systems of record existed | `wildo -y config sync --local --domain env-files` |
|
|
58
|
+
| `Missing generated provider runtime module` (printed by your backend's own `src/index.ts`) | the same module, absent | `wildo -y config sync --local` |
|
|
59
|
+
| `Missing or invalid companion provider runtime artifact` | `.wildo-saas/generated/providers/companion.runtime-providers.generated.json` | `wildo -y config sync --local` |
|
|
60
|
+
| `detected stale provider topology` · `does not contain a scope for worker/minion` | a minion's or worker's `.wildo-providers.env` or generated module | `wildo -y config sync --local` |
|
|
61
|
+
| browser console: `bundle carries no code for it … regenerate frontend-providers.generated.ts` (a provider silently missing) | `<frontend service>/src/generated/frontend-providers.generated.ts` | `wildo -y config sync --local`, then commit it |
|
|
62
|
+
| `Lockfile drift detected` | `.wildo-saas/wildo-saas.lock.json` | `wildo -y config sync --local`, then commit it |
|
|
63
|
+
| `postgresql_table_schema_mismatch` | the database schema behind your resources | `wildo db generate --name <label>` (see the database-migrations skill) |
|
|
64
|
+
| `Run wildo dev sync-csp and commit the result` | `<frontend service>/src/generated/csp.generated.json` | `wildo dev sync-csp` |
|
|
65
|
+
| `Run wildo config <data-retention · service-consent · subject-data-recipients · document-releases> and commit` | the matching `backend-api/src/*.generated.ts` compliance module | the command it names |
|
|
66
|
+
| `No generated config … Run wildo config sync --domain config` | `.wildo-saas/infrastructure/environments/<env>/generated/config/config.json` | `wildo config sync --local --domain config` |
|
|
67
|
+
|
|
68
|
+
#### Every derived artifact, and how to check it
|
|
69
|
+
|
|
70
|
+
| Artifact | Lives at | Regenerated by | How to tell it is current | In git? |
|
|
71
|
+
|---|---|---|---|---|
|
|
72
|
+
| Provider runtime artifacts | `.wildo-saas/generated/providers/*.runtime-providers.generated.json`; `backend-api/src/generated/wildo-provider-runtime.generated.ts` and the same file in each minion and Node worker; `minions/*/.wildo-providers.env`, `workers/*/.wildo-providers.env` | `wildo -y config sync --local` (no prompt); `wildo local dev` regenerates a missing or refused one when it starts | `wildo local doctor` — the **generated provider-runtime artifact content** line checks the frontend-services, backend and companion JSON files with what their readers apply, and names every one a reader would refuse. It does not read the minion and worker JSON files, the `.ts` modules or the `.wildo-providers.env` files | No — always safe to regenerate |
|
|
73
|
+
| Frontend provider modules | `<frontend service>/src/generated/frontend-providers.generated.ts`, `frontend-provider-service.generated.json` | `wildo -y config sync --local` | Nothing. A stale one drops a provider with a browser-console warning instead of failing | Yes — commit after regenerating |
|
|
74
|
+
| Provider catalogue types | `.wildo-saas/generated/provider-catalog.types.ts` | `wildo -y config sync --local` | Nothing; stale only means stale autocomplete | Yes |
|
|
75
|
+
| Application lockfile | `.wildo-saas/wildo-saas.lock.json` | `wildo -y config sync --local` (providers, infra); module and label commands write their own sections | `wildo lock check` — checks the providers and infra sections only | Yes |
|
|
76
|
+
| Content security policy | `<frontend service>/src/generated/csp.generated.json` | `wildo dev sync-csp` (also `wildo dev start`) — **not** `wildo config sync` | `wildo dev sync-csp --check` (it refreshes the provider artifacts before comparing) | Yes |
|
|
77
|
+
| Environment config and local stack | `.wildo-saas/infrastructure/environments/<env>/generated/config/config.json`, `…/docker-compose/docker-compose.wildo-platform.yml`, `…/docker-compose/.env.wildo-platform` | `wildo -y config sync --local`. `wildo local up` only recreates a MISSING one, never a stale one | `wildo config validate --domain config` checks coherence with your secrets, not currency | No |
|
|
78
|
+
| Per-package `.env` files | `backend-api/.env`, `frontend/.env`, `website/.env`, `technical-doc/.env`, each minion and worker, `.wildo-saas/wildo-dev-companion/.env` | `wildo -y config sync --local --domain env-files` — needs the local platform running (when it is down this phase fails, but the provider artifacts are still written). It asks before overwriting; `-y` SKIPS existing files, `--force` rewrites them | Nothing | No |
|
|
79
|
+
| Application identity | `.wildo-saas/infrastructure/environments/<env>/generated/config/application-runtime-identity.json` | **Not derived** — assigned when the application registered (`wildo local init`) | — | No, and **do not delete it**: only re-registration restores it |
|
|
80
|
+
| Compliance modules | `backend-api/src/{data-retention,service-consent-requirement,subject-data-recipients,governed-document-releases}.generated.ts` | `wildo config data-retention` · `service-consent` · `subject-data-recipients` · `document-releases` | The same command with `--check`, or `wildo config validate --domain <same name>` | Yes |
|
|
81
|
+
| Database migrations | `backend-api/migrations/`, `backend-api/migrations/schema-plan.lock.json` | `wildo db generate --name <label>` | `wildo db diff --check`. It refuses to answer while `backend-api/dist` is older than its sources — let the build catch up first | Yes — **never delete** |
|
|
82
|
+
| Labels and translations | `backend-api/src/engine/i18n/**` | `wildo generate labels`, then `wildo generate translate` (the dev companion must be running) | No command reports it; the lockfile records each unit's status | Yes |
|
|
83
|
+
| Technical documentation | `technical-doc/src/generated/api-reference/**`, `technical-doc/src/generated/consumer-documentation/**` | `wildo docs publish` (the dev companion must be running) | Nothing short of republishing and reading the diff | Yes |
|
|
84
|
+
| Package builds | each package's `dist/` | the dev watchers `wildo local dev` starts | Nothing direct; `wildo db diff` refuses on a stale `backend-api/dist` | No |
|
|
85
|
+
| Config loader cache | `.wildo-saas/dist/config-loader/` | rebuilt on demand | Nothing; delete it when `wildo.saas.config.ts` edits seem ignored | No — always safe to delete |
|
|
86
|
+
| Delivered framework | `.claude/skills/` and the rules delivered beside them under `.claude/`, `.wildo-saas/templates/`, `.wildo-saas/wildo-dev-companion/` | `wildo assets sync` (`wildo update` runs it) | Nothing records which release delivered them; re-run `wildo assets sync` when in doubt | Skills and rules yes; templates and the companion build no |
|
|
87
|
+
|
|
88
|
+
Files your application-creation runs produced — brand assets, personas, charters, specifications —
|
|
89
|
+
are **committed decisions**, not caches. They are never regenerated to fix a refusal.
|
|
90
|
+
|
|
91
|
+
#### What `wildo local doctor` can and cannot tell you
|
|
92
|
+
|
|
93
|
+
- It **fails** when a generated provider runtime module is missing, and names `wildo config sync`.
|
|
94
|
+
- It **fails** when a present provider runtime artifact would be refused by the process that reads
|
|
95
|
+
it (*generated provider-runtime artifact content*), with the reason that reader gives — for the
|
|
96
|
+
frontend-services and backend files, the reader's own refusal message. It applies what the readers
|
|
97
|
+
apply rather than comparing dates, so it catches a file a framework update made stale while every
|
|
98
|
+
input stayed the same. It covers the frontend-services, backend and companion JSON files only.
|
|
99
|
+
- It does not check the other derived artifacts in the table above; use the command in their row.
|
|
100
|
+
- Its **derived-artifact currency** line reads `not probed` in an application installed from
|
|
101
|
+
published packages. That is not a pass: it compares builds against a framework source checkout,
|
|
102
|
+
which your application does not have.
|
|
103
|
+
|
|
104
|
+
#### Regenerate before you debug, after any of these
|
|
105
|
+
|
|
106
|
+
- **A framework update.** `wildo update` ends by regenerating the provider runtime artifacts and the
|
|
107
|
+
CSP files (`wildo dev sync-csp`, for the active environment), after declaring and installing the
|
|
108
|
+
systems-of-record library when `systemsOfRecord` needs it. If the release you moved to predates that
|
|
109
|
+
step, run `wildo -y config sync --local` yourself. If the step fails, its message says why:
|
|
110
|
+
- `Config file not found: …/wildo.infra.<env>.config.ts` — only the CSP half failed: the provider
|
|
111
|
+
runtime artifacts were already regenerated. The active environment has no authored infra config;
|
|
112
|
+
set it up with `wildo setup` (or select an environment that has one), then run `wildo dev sync-csp`.
|
|
113
|
+
- `Cannot produce the frontend provider configuration … its secrets … cannot be read` — nothing was
|
|
114
|
+
produced, and `config sync` stops on the same check. Restore that environment's `secrets.json`:
|
|
115
|
+
the provider configuration is screened against it and is never produced without it.
|
|
116
|
+
- **A change to `providers` or `services` in `wildo.saas.config.ts`**, or adding a frontend service:
|
|
117
|
+
`wildo -y config sync --local`, then `wildo dev sync-csp`.
|
|
118
|
+
- **A change to `wildo.infra.<env>.config.ts`**: `wildo -y config sync --local`, then
|
|
119
|
+
`wildo config sync --local --domain manifest`.
|
|
120
|
+
|
|
121
|
+
Commit the tracked files a regeneration changed in their own commit, so the next reader can tell a
|
|
122
|
+
regeneration from an authored change.
|
|
@@ -21,6 +21,17 @@ It moves the two homes of a release, in this order:
|
|
|
21
21
|
It restarts nothing. Afterwards `wildo local up` puts the platform on the release's image, and
|
|
22
22
|
restarting `wildo local dev` runs the application and its companion on the new packages.
|
|
23
23
|
|
|
24
|
+
Its last step is `wildo dev sync-csp`, which regenerates the provider runtime artifacts and the CSP
|
|
25
|
+
files built from them for the active environment. Just before it, an application whose `systemsOfRecord`
|
|
26
|
+
needs the systems-of-record library gets that dependency declared on its backend manifests and
|
|
27
|
+
installed, so the regeneration never meets an uninstalled package. A release can change what the backend, the website or the companion requires
|
|
28
|
+
of those files without any input changing, and a file the previous release wrote is then refused at
|
|
29
|
+
start-up (`…generated before this check existed — regenerate it with wildo config sync`). If the
|
|
30
|
+
release you moved to predates that step, run `wildo -y config sync --local` before restarting
|
|
31
|
+
`wildo local dev`. If the step reports a failure, read its message first: a missing infra config fails only
|
|
32
|
+
the CSP half (the provider artifacts were regenerated), while an unreadable `secrets.json` stops the
|
|
33
|
+
provider artifacts and `config sync` alike. `derived-artifact-currency.md` gives the fix for each.
|
|
34
|
+
|
|
24
35
|
## When the release asks for something this application does not declare
|
|
25
36
|
|
|
26
37
|
A release can make a declaration REQUIRED that older applications do not have. `wildo update` then
|
package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md
CHANGED
|
@@ -361,6 +361,13 @@ timestamps and exactly what to delete, and it does not act. Read it before you
|
|
|
361
361
|
debug logic: a stale artifact answers confidently about a version of the
|
|
362
362
|
application that no longer exists.
|
|
363
363
|
|
|
364
|
+
That sweep compares builds against a framework SOURCE checkout. In an
|
|
365
|
+
application installed from published packages it reports `not probed`, which
|
|
366
|
+
is not a pass. The provider runtime artifacts have their own line, in every
|
|
367
|
+
mode: *generated provider-runtime artifact content* runs their readers' checks
|
|
368
|
+
and names each file they would refuse. See `derived-artifact-currency.md` for
|
|
369
|
+
what each derived artifact can and cannot be checked by.
|
|
370
|
+
|
|
364
371
|
It reports orphaned compiler watchers and never kills them; reaping is
|
|
365
372
|
`wildo dev force-stop`.
|
|
366
373
|
|
|
@@ -478,13 +485,13 @@ their values in logs or documentation.
|
|
|
478
485
|
|---------------------------------------------------------|--------------------------------------------------------------------------------------|
|
|
479
486
|
| `./infrastructure/<env>/wildo.infra.local.config.ts` / `wildo.infra.remote.config.ts` (added/changed a backing service, runtime, `publicDomain`, …) | `wildo -y config sync --local` for config/env outputs; then run `wildo -y config sync --local --domain manifest` separately for the local workload render. An explicit domain filter replaces the defaults. Ordinary non-CI sync reconciles authored state first |
|
|
480
487
|
| `./wildo.saas.config.ts` (modules, engine capabilities, provider scopes) | `wildo -y config sync --local --domain config` then restart the affected runtime process (`wildo dev start` if the app dev script owns it) |
|
|
481
|
-
| Provider API keys (OpenAI, Anthropic, …) — typed in by hand | `wildo secrets set <ENV_VAR_NAME>` (add `--env <env>` for a remote environment): it writes `secrets.json` → `providerEnv`, regenerates the env files and restarts
|
|
488
|
+
| Provider API keys (OpenAI, Anthropic, …) — typed in by hand | `wildo secrets set <ENV_VAR_NAME>` (add `--env <env>` for a remote environment): it writes `secrets.json` → `providerEnv`, regenerates the env files, has a running dev companion load the key in place (no restart, no run interrupted) and restarts the other supervised runtimes that read it; the output says which, and names any runtime you still have to restart yourself (this is the rotation path you DO want) |
|
|
482
489
|
| The authored secrets path (`./infrastructure/<env>/secrets/`) — moved or split | `wildo -y setup` and answer the path question with the new layout |
|
|
483
490
|
| Nothing — just want to bounce the stack | `wildo -y local up --restart` |
|
|
484
491
|
| `./wildo.saas.config.ts` — a service port, a session storage mode, a capability flag, or removing a provider from a scope | `wildo config mutate` (idempotent, dry-runnable, names the segment it cannot resolve) then `wildo -y config sync --local` |
|
|
485
492
|
| Anything at all, and you want to CHECK before writing | `wildo config validate` — writes nothing |
|
|
486
493
|
| The declaration, on an application that is already running | `wildo config reapply-declaration` (leaves credentials, database, infra and the seeded administrator alone) |
|
|
487
|
-
| Nothing — but something is behaving impossibly | `wildo local doctor` FIRST
|
|
494
|
+
| Nothing — but something is behaving impossibly | `wildo local doctor` FIRST, then `derived-artifact-currency.md`: a process refusing a generated file names the command that regenerates it |
|
|
488
495
|
| Nothing — you want a newer framework release | `wildo update` (or `--to <version>`). It moves the CLI, then this application's pins, dependencies, companion, skills and deploy manifests. See `framework-upgrade-and-dependency-alignment.md` |
|
|
489
496
|
| The `@wildo-ai/*` versions in `pnpm.overrides`, by hand | `pnpm install` → `wildo align-deps --write` → `pnpm install` again, then `wildo assets sync`. Prefer `wildo update`, which does all of it and moves the CLI to match |
|
|
490
497
|
| Nothing — the application was just scaffolded and installed for the first time | `wildo align-deps --write` once, then `pnpm install`. Expected, not a defect: scaffolding pins from the framework checkout while pinning the framework to the published release |
|
|
@@ -922,6 +922,8 @@ export interface SpecificationsCompanionExports<
|
|
|
922
922
|
TIntegrationPlan = IntegrationPlan,
|
|
923
923
|
// Appended STRICTLY LAST: where the application stands against its own requirements (#1496).
|
|
924
924
|
TApplicationMaturity = ApplicationMaturity,
|
|
925
|
+
// Appended STRICTLY LAST: the screened brand-name candidates the brand-identity interview chooses from.
|
|
926
|
+
TBrandNameScreening = BrandNameScreening,
|
|
925
927
|
> {
|
|
926
928
|
resourceSpecifications: TResourceSpecifications;
|
|
927
929
|
applicationBusinessSemanticsSnapshot?: TBusinessSemanticsSnapshot;
|
|
@@ -1452,6 +1454,14 @@ export interface SpecificationsCompanionExports<
|
|
|
1452
1454
|
* never a gate. Read by the coherence report and the workbench.
|
|
1453
1455
|
*/
|
|
1454
1456
|
applicationMaturity?: TApplicationMaturity;
|
|
1457
|
+
/**
|
|
1458
|
+
* WHICH NAMES were proposed for the brand and what a minimal trademark screening of each found —
|
|
1459
|
+
* registers, classes and jurisdictions searched, per-register results with sources and dates, and the
|
|
1460
|
+
* competitor collisions beside them. Produced by `top_down.brand-naming`; the brand-identity interview's
|
|
1461
|
+
* `brand-name` CHOICE is computed from it, and the coherence report reads it to say where the chosen
|
|
1462
|
+
* brand name stands. A screening, never a legal clearance opinion.
|
|
1463
|
+
*/
|
|
1464
|
+
brandNameScreening?: TBrandNameScreening;
|
|
1455
1465
|
/**
|
|
1456
1466
|
* Accepted application-declared semantic causality between whole
|
|
1457
1467
|
* specification-family states. This is not the registry's physical
|
|
@@ -2332,7 +2342,7 @@ function detectMissingPositioningForIcp(snapshot: MarketSnapshot, issues: Market
|
|
|
2332
2342
|
const positionedIcpRefs = new Set(snapshot.positionings.map(p => p.icpRef));
|
|
2333
2343
|
|
|
2334
2344
|
for (const [iIdx, icp] of snapshot.icps.entries()) {
|
|
2335
|
-
if (
|
|
2345
|
+
if (!TARGETED_ICP_PRIORITIES.has(icp.priority)) continue;
|
|
2336
2346
|
if (positionedIcpRefs.has(icp.ref)) continue;
|
|
2337
2347
|
|
|
2338
2348
|
issues.push({
|
|
@@ -827,6 +827,8 @@ export interface SpecificationsCompanionExports<
|
|
|
827
827
|
TIntegrationPlan = IntegrationPlan,
|
|
828
828
|
// Appended STRICTLY LAST: where the application stands against its own requirements (#1496).
|
|
829
829
|
TApplicationMaturity = ApplicationMaturity,
|
|
830
|
+
// Appended STRICTLY LAST: the screened brand-name candidates the brand-identity interview chooses from.
|
|
831
|
+
TBrandNameScreening = BrandNameScreening,
|
|
830
832
|
> {
|
|
831
833
|
resourceSpecifications: TResourceSpecifications;
|
|
832
834
|
applicationBusinessSemanticsSnapshot?: TBusinessSemanticsSnapshot;
|
|
@@ -1357,6 +1359,14 @@ export interface SpecificationsCompanionExports<
|
|
|
1357
1359
|
* never a gate. Read by the coherence report and the workbench.
|
|
1358
1360
|
*/
|
|
1359
1361
|
applicationMaturity?: TApplicationMaturity;
|
|
1362
|
+
/**
|
|
1363
|
+
* WHICH NAMES were proposed for the brand and what a minimal trademark screening of each found —
|
|
1364
|
+
* registers, classes and jurisdictions searched, per-register results with sources and dates, and the
|
|
1365
|
+
* competitor collisions beside them. Produced by `top_down.brand-naming`; the brand-identity interview's
|
|
1366
|
+
* `brand-name` CHOICE is computed from it, and the coherence report reads it to say where the chosen
|
|
1367
|
+
* brand name stands. A screening, never a legal clearance opinion.
|
|
1368
|
+
*/
|
|
1369
|
+
brandNameScreening?: TBrandNameScreening;
|
|
1360
1370
|
/**
|
|
1361
1371
|
* Accepted application-declared semantic causality between whole
|
|
1362
1372
|
* specification-family states. This is not the registry's physical
|
|
@@ -2060,7 +2070,7 @@ function detectMissingPositioningForIcp(snapshot: MarketSnapshot, issues: Market
|
|
|
2060
2070
|
const positionedIcpRefs = new Set(snapshot.positionings.map(p => p.icpRef));
|
|
2061
2071
|
|
|
2062
2072
|
for (const [iIdx, icp] of snapshot.icps.entries()) {
|
|
2063
|
-
if (
|
|
2073
|
+
if (!TARGETED_ICP_PRIORITIES.has(icp.priority)) continue;
|
|
2064
2074
|
if (positionedIcpRefs.has(icp.ref)) continue;
|
|
2065
2075
|
|
|
2066
2076
|
issues.push({
|
|
@@ -789,7 +789,7 @@ function detectMissingPositioningForIcp(snapshot: MarketSnapshot, issues: Market
|
|
|
789
789
|
const positionedIcpRefs = new Set(snapshot.positionings.map(p => p.icpRef));
|
|
790
790
|
|
|
791
791
|
for (const [iIdx, icp] of snapshot.icps.entries()) {
|
|
792
|
-
if (
|
|
792
|
+
if (!TARGETED_ICP_PRIORITIES.has(icp.priority)) continue;
|
|
793
793
|
if (positionedIcpRefs.has(icp.ref)) continue;
|
|
794
794
|
|
|
795
795
|
issues.push({
|