This is the status view for whether the mica.wtf document families have both a freshness pipeline and content/format conventions.

Short answer: no, not all document families are fully covered yet. The core MiCA legal text and main EU supervisory document families have meaningful pipelines and conventions. National adaptations, consultations, political signals, and DORA-adjacent material are partially covered. DORA has no dedicated freshness loop.

Family	Current files	Notes
MiCA article pages	150	Legal text corpus under mica/; includes article pages and title/chapter structure.
MiCA title/chapter README pages	27	Navigation/section pages.
EU-level Q&A	35	Includes answered and pending Q&A pages.
EU-level guidelines	17	ESMA/EBA guideline and final report pages under eu-level/guidelines/.
EU-level technical standards	51	RTS/ITS/final report pages under eu-level/technical-standards/.
EU-level soft law	17	Opinions, statements, reports/advice, IOSCO, templates.
EU-level consultations	1	Current targeted MiCA review consultation page.
National adaptation content files	98	Across 30 EEA jurisdictions and 32 NCA folders.
MiCA definition pages	51	Reader/linking layer derived from MiCA and adjacent laws.
DORA article pages	64	Separate space; useful context but not yet in the MiCA freshness system.

Document family	Freshness pipeline	Convention coverage	Status	What this means
MiCA legal text	micawtf-cellar-legislation active; eurlex-mica structured checker implemented but inactive in the legislation group	_conventions/mica-legal-text.md; _conventions/maps/article-map.json	Strong, with human-review gate	Legal-text freshness is live through the Cellar lane. Article, recital, and annex pages now have structured frontmatter and source/status orientation tables; title/chapter indexes have structured frontmatter. Corrigenda, amendments, consolidated-text changes, and application-date changes require human review.
ToFR legal text	cellar-legislation legacy lane active; eurlex-tofr structured checker implemented but inactive	ToFR corpus exists; accuracy review exists	Partial	Watched for legal-text changes, but still mostly separate from the MiCA document-family overview.
ESMA Q&A	esma-mica-qas active in Hermes; ESMA RSS legacy lane still active as redundancy	_conventions/q-and-a-content.md; generator rules in scripts/update-checkers/lib/markdown.js	Strong, with migration/runtime caveats	New generated pages now target eu-level/q-and-a/, use compact official-ID slugs, include description frontmatter, and start with an orientation table. Existing Q&A pages have been migrated to description frontmatter and orientation tables; misleading legacy filenames such as EBA items under esma-qa-* still need a redirect-backed slug migration.
EBA Q&A	eba-micar-qas active in Hermes; EBA RSS legacy lane still active as redundancy	_conventions/q-and-a-content.md; generator rules in scripts/update-checkers/lib/markdown.js	Strong, with migration/runtime caveats	Same posture as ESMA Q&A. Structured EBA is now active, with legacy RSS retained as redundancy; legacy EBA filenames need redirect-backed cleanup.
ESMA/EBA guidelines	esma-mica-docs and eba-micar-docs active in Hermes through micawtf-esma/micawtf-eba; ESMA/EBA RSS legacy lanes still active as redundancy	_conventions/guidelines-content.md; _conventions/eu-level-page-anatomy.md	Strong, with human-review gate	Guideline freshness is now covered by active structured document checkers. New or changed guideline documents remain review items by default; Docling/PDF formatting rules from #36 are codified and all guideline pages have description frontmatter plus orientation tables.
ESMA/EBA other documents and reports	esma-mica-docs, eba-micar-docs, and legacy RSS lanes detect changes	_conventions/eu-level-page-anatomy.md	Partial	Detection is active, but non-guideline reports and soft-law subtypes still need family-specific conventions and lifecycle/status rules.
Technical standards RTS/ITS/final reports	esma-mica-docs and eba-micar-docs active in Hermes through micawtf-esma/micawtf-eba; micawtf-cellar-legislation watches EUR-Lex; ESMA/EBA RSS legacy lanes still active as redundancy	_conventions/technical-standards-content.md; _conventions/eu-level-page-anatomy.md	Strong, with lifecycle/review caveats	Freshness is live, but publication remains human-review by default because lifecycle moves differ: consultation/final report, Commission adoption, OJ publication, and application dates can each require different page updates. All technical-standard document pages now have description frontmatter and orientation tables.
ESMA MiCA registers	esma-mica-registers implemented	No dedicated reader-facing register convention yet	Partial	Detection exists, but the product surface/convention for register deltas is not settled.
EU consultations	eu-political implemented but inactive; active ESMA/EBA structured document lanes may detect supervisory consultations/final reports; manual review for Commission lifecycle changes	_conventions/consultations-content.md; _conventions/eu-level-page-anatomy.md	Stronger, review-gated	The MiCA review consultation is in corpus with description frontmatter, a compact stable slug, and an orientation table. Lifecycle stages are documented (open, closing_soon, closed, feedback_published, final_report_published, superseded); consultation pages are never auto-published from political signals.
EU political layer	eu-political implemented but inactive; blog-signals available but inactive	Blog queue and editorial conventions exist	Partial	Good for editorial discovery, not authoritative content freshness. Needs deliberate activation/noise tuning.
IOSCO/global standards	iosco-crypto-assets and global-standards implemented but inactive	EU-level/soft-law conventions partly apply	Partial	Detection exists, but relevance triage and page conventions are still review-heavy.
National adaptations: AMF, CBI	nca-amf, nca-cbi implemented in nca-daily but not active	_conventions/national-adaptations-anatomy.md; docs/ADDING-AN-NCA.md	Partial	Strong conventions, partial checker coverage, not active in Hermes.
National adaptations: BaFin, CSSF, DFSA, DNB/AFM	Implemented in nca-weekly but not active	_conventions/national-adaptations-anatomy.md; docs/ADDING-AN-NCA.md	Partial	Same: source modules exist, runtime inactive.
Remaining NCAs	No source-specific checkers for most jurisdictions	National adaptation convention exists	Gap	Content structure exists, but most NCA pages have no automated freshness loop.
Definitions	Derived rebuild through scripts/build-definitions.js; refreshed after legal-text source changes	_conventions/definitions-content.md; generator output in spaces/definitions/ synced to live definitions/; _conventions/maps/article-map.json	Strong, derived-content model	Definitions are generated from MiCA Article 3, ToFR Article 3, and imported legal-source definitions encoded in the generator. No standalone cron is needed; legal-text freshness alerts trigger human review and generator rebuild.
Blog/editorial	editorial-clock, review-nudge, queue/signals	_conventions/blog-content.md, prompts/article-writer.md; #19 folded into #45	Strong, but now part of the family cleanup	The publishing workflow is covered. Freshness-triggered blog-post draft creation belongs to #45, not a Beehiiv/newsletter-specific standalone issue.
X signals	Grok prompt and launcher exist, inactive	prompts/x-signals-run.md	Optional/partial	Discovery-only. Should never be treated as authoritative freshness.
DORA	No dedicated DORA freshness loop	DORA content exists; no DORA-specific convention in _conventions/	Gap	DORA is a separate content space and should not be assumed current by the MiCA freshness system.

Active Hermes jobs today are:

• micawtf-cellar-legislation
• micawtf-esma-rss
• micawtf-eba-rss
• micawtf-esma
• micawtf-eba
• micawtf-docling-sweeper
• micawtf-review-nudge
• micawtf-editorial-clock

Implemented but inactive structured checker groups include:

• nca-daily
• nca-weekly
• legislation
• eu-political
• global-standards
• blog-signals
• x-signals

The practical implication is that the repo has more source-specific checker code than the currently active box runtime uses. That is intentional for now, but it means the coverage map must distinguish implemented from scheduled.

Convention	File	Covers	Gaps
Blog/editorial	_conventions/blog-content.md	Blog drafts, approval gate, social copy, editorial scheduling	Folded into #45 for freshness-triggered draft creation after #19 closure
Q&A	_conventions/q-and-a-content.md, scripts/update-checkers/lib/markdown.js	ESMA/EBA Q&A generation, compact slugs, orientation tables, freshness quality gates	Existing misleading EBA-as-ESMA filenames need redirect-backed cleanup
Guidelines	_conventions/guidelines-content.md, _conventions/eu-level-page-anatomy.md	ESMA/EBA comply-or-explain guideline pages, Docling/PDF post-processing, review gates, source mapping	Existing long legacy slugs are stable until a redirect-backed migration is deliberately scheduled
Technical standards	_conventions/technical-standards-content.md, _conventions/eu-level-page-anatomy.md	RTS, ITS, delegated/implementing regulations, final reports, lifecycle migration, ESMA/EBA source differences	Existing long legacy slugs are stable until a redirect-backed migration is deliberately scheduled
EU-level page anatomy	_conventions/eu-level-page-anatomy.md	Guidelines, reports, soft-law style pages	Guidelines, technical standards, and consultations now have family conventions; registers still need a more explicit subtype
National adaptations	_conventions/national-adaptations-anatomy.md, docs/ADDING-AN-NCA.md	NCA/jurisdiction pages	Strong structure, but freshness activation is incomplete
MiCA legal text	_conventions/mica-legal-text.md, _conventions/maps/article-map.json	MiCA article/title/chapter/recital/annex metadata, source rules, corrigenda/amendment handling	Structured eurlex-mica checker remains implemented but inactive; Cellar lane is active
Definitions	_conventions/definitions-content.md, scripts/build-definitions.js	Generated MiCA/ToFR/imported definition pages, slugs, frontmatter, orientation tables, rebuild/sync rule	DORA definitions are not owned by this generator and remain separate until DORA gets its own freshness track
Article map	_conventions/maps/article-map.json	Article linking and map/linter support	Supports links; legal-text page rules live in mica-legal-text.md
Prompt infrastructure	prompts/	Runtime prompts, article writer, X signals, freshness triage	Historical vault prompts still need periodic extraction if they contain durable rules
Restore/runtime	docs/operations/restore-runbook.md, ops/hermes/	Clean-box runtime restore	Good after issue #11

1. Finish #46 Q&A operationalization. The generator, convention, page-shape migration, and structured ESMA/EBA runtime activation are in place; remaining work is redirect-backed filename cleanup and monitoring the first full-automation runs.
2. Monitor structured ESMA/EBA document checks for guidelines. Guideline coverage is active, but changed documents are review items; watch for duplicate RSS/structured alerts and false positives.
3. Monitor technical-standard lifecycle alerts. Technical standards are live through ESMA/EBA and Cellar checks, but review must distinguish final-report changes, Commission adoption, OJ publication, and application-date metadata.
4. Turn docs/freshness-coverage.md into the live operator dashboard. Keep this status doc as the audit snapshot; maintain coverage in one place going forward.
5. Add register conventions. The MiCA review consultation now has a dedicated convention; ESMA registers are recurring enough to deserve specific page rules.
6. Monitor MiCA legal-text Cellar alerts. Article metadata is now normalized, but legal-text changes still require human review and the structured legislation group remains inactive.
7. Expand NCA activation in tiers. Start with AMF/CBI/BaFin/CSSF/DNB/AFM/DFSA because checkers exist. Do not add the remaining NCAs until source-specific checkers exist.
8. Monitor definitions rebuilds after legal-text alerts. Definitions now have a derived-content convention and generator sync path; run node scripts/build-definitions.js after relevant source legal-text changes and review the diff.
9. Decide whether DORA belongs in this operating system. If yes, create a DORA-specific freshness strategy and convention file instead of letting it inherit MiCA assumptions.

Do all MiCA-space documents have a freshness pipeline and content/format convention?

No. The system is strong for blog/editorial workflow and now stronger for generated Q&A, but it is still partial for legal text, standards, consultations, registers, and NCAs. It has clear gaps for most NCAs and DORA. The next practical step is not more generic automation; it is finishing each document-family convention and activating the implemented high-value loops deliberately.