Receive the change request
MIRENA records the topic, source, audience, business reason, and proposed asset.
Topical Mapping · Operator
Keep every topic in the right home as the site grows.
MIRENA uses topic governance to control how topics are added, split, merged, approved, linked, logged, and refreshed. No topic enters the map without one primary home, one role, one parent, and one reason to exist.
Operator level
Internal MIRENA workflow
Static explanation
Human review required
InputA change request, source evidence, current map, proposed role, parent, overlap notes, and business reason.Evidence enters before the decision.
DecisionAdd, split, merge, keep as a section, reroute, hold, or reject.The state remains visible.
OutputA governance record with ownership, approval, affected pages, link effects, redirects, priority, and change log.The handoff carries the reasoning.
Next routeMap Approval or controlled refreshDownstream 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.
Classify the request
The request receives a cluster, likely role, intent, parent, and nearby overlap set.
Run the governance review
MIRENA checks page vs section, primary home, split, merge, link, and scope rules.
Approve, revise, hold, or reject
The state explains whether the topic can enter the map and what must happen first.
Update routes and ownership
Parents, siblings, internal links, redirects, rollout order, and downstream fields are revised.
Log and monitor the change
The decision, owner, reason, affected pages, and refresh trigger remain visible.
Decision model
The governance charter protects four recurring decision groups.
A small set of hard rules prevents slow structural decline.
Primary home
Every topic belongs to one approved page or section.
Role and parent
Every page has one job and one stable cluster home.
Split and merge
A split or merge must improve intent clarity, depth, and routes.
Links and changes
Internal paths, redirects, approvals, logs, and refresh rules follow the map.
Illustrative MIRENA output
Illustrative governance record
The record preserves the reasoning after the change is made.
RequestCreate a separate comparison page
ClusterTopical Mapping
Proposed roleComparison
ParentTopical Mapping hub
Overlap reviewNo duplicate intent
DecisionApprove
Affected routesHub, sibling method page, product path
Change logOwner and review date recorded
Guardrails
The method protects the map from predictable failure.
No unowned topics
A request without a parent and role cannot enter the queue.
No split from keyword size alone
A split needs distinct intent, depth, and a cleaner route.
No permanent legacy decision
Thin or overlapping pages can be merged when the map improves.
No refresh outside governance
A refresh must recheck role, parent, overlap, and links.
Connected routes
Move only into the workflow that owns the next decision.
Map Approval Workflow
Continue only when the current decision and evidence are ready.
Open Map Approval WorkflowPage vs Section Decisions
Continue only when the current decision and evidence are ready.
Open Page vs Section DecisionsFeedback Loops for Refreshes
Continue only when the current decision and evidence are ready.
Open Feedback Loops for RefreshesTopical Mapping Hub
Continue only when the current decision and evidence are ready.
Open Topical Mapping HubQuestions
Topic Governance Rules questions.
What are topic governance rules?
They control how topics are added, split, merged, assigned, approved, linked, logged, and refreshed.
What is the primary governance rule?
Every topic needs one primary home, one page role, one parent cluster, and one reason to exist.
When should a topic split?
When distinct intent, stable depth, a clear child route, and improved user movement justify a separate asset.
When should pages merge?
When they share one intent, compete for the same links, or a stronger parent can absorb the thinner page.
Why keep a change log?
The log preserves the reason, owner, affected pages, links, redirects, and future review trigger.
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.