Validate scope and completeness
MIRENA checks that required clusters exist and blocked lanes remain out.
Topical Mapping · Operator
A topical map is complete only when the downstream handoff can trust it.
MIRENA treats map approval as a production gate. The draft map must pass scope, role, intent, cluster, overlap, page vs section, rollout, link, and handoff checks before briefing or drafting can begin.
Operator level
Internal MIRENA workflow
Static explanation
Human review required
InputA draft map, page inventory, roles, query ownership, cluster relationships, priority order, and handoff fields.Evidence enters before the decision.
DecisionApprove, revise, hold, or block the map.The state remains visible.
OutputAn approval record with passed gates, blockers, owners, required fixes, rollout order, and the approved next workflow.The handoff carries the reasoning.
Next routeContent Briefs or revisionDownstream work starts only after approval.
Internal MIRENA method
The decision moves through six controlled stages.
The sequence keeps the source, role, evidence, ownership, risk, and next route connected.
Review page roles and intent
Every asset needs a clear job and a distinct user or query need.
Review cluster structure
Parent, child, sibling, section, question, and commercial routes are explicit.
Run overlap and granularity checks
Near match pages are merged, narrowed, rerouted, or held.
Confirm rollout and handoff fields
Priority, entity targets, information gain notes, links, and owners are complete.
Set the approval state
The map is approved, returned for revision, held for evidence, or blocked.
Decision model
Approval uses four states, not a simple yes or no.
The state explains what can happen next and who owns the unresolved work.
Approve
All required gates pass and the handoff can start without strategic guesswork.
Revise
The map is directionally correct but specific roles, overlap, order, or fields need repair.
Hold
Required evidence, ownership, source context, or stakeholder input is missing.
Block
Duplicate intent, prohibited scope, unsafe assumptions, or unresolved structural conflict prevents movement.
Illustrative MIRENA output
Illustrative approval record
The record makes the release state and ownership visible.
Map scopeTopical Mapping cluster
Pages reviewed63 assets
Page rolesComplete
Overlap reviewTwo merge candidates resolved
Page vs section reviewComplete
Rollout orderApproved
Handoff stateReady for briefs
ApprovalApprove
Guardrails
The method protects the map from predictable failure.
Do not approve a long page list
Length is not evidence of structure.
Do not hide duplicate intent
Near match pages must be resolved before handoff.
Do not skip rollout order
An unprioritized map creates a weak production queue.
Do not make editors finish strategy
Missing handoff fields mean the map is early.
Connected routes
Move only into the workflow that owns the next decision.
Page vs Section Decisions
Continue only when the current decision and evidence are ready.
Open Page vs Section DecisionsTopic Governance Rules
Continue only when the current decision and evidence are ready.
Open Topic Governance RulesUser Journey Topical Mapping
Continue only when the current decision and evidence are ready.
Open User Journey Topical MappingTopical Mapping Hub
Continue only when the current decision and evidence are ready.
Open Topical Mapping HubQuestions
Map Approval Workflow questions.
What does map approval confirm?
It confirms scope, page roles, intent ownership, cluster relationships, overlap, granularity, rollout order, and handoff readiness.
What should block approval?
Duplicate intent, unclear roles, missing parents, unresolved overlap, weak page vs section calls, missing priorities, or incomplete handoff fields.
Is map approval the same as map creation?
No. Creation builds the first structure. Approval validates whether that structure can drive production.
What does an approved handoff include?
Page purpose, role, cluster home, entity targets, information gain notes, priority, link routes, blockers, and owner.
What happens after approval?
MIRENA routes approved map rows into content briefs. Failed rows return to the smallest repair workflow.
Next route
Give MIRENA the evidence. Receive the governed decision and handoff.
Founder access costs €20 for each 30 day period, excluding VAT, for one seat and one active MIRENA instance.
OpenAI account rules, model access, plan charges, and usage limits remain separate. MIRENA output requires factual, editorial, technical, legal, and business review.