Confirm the parent need
MIRENA starts with the stronger existing page or proposed hub.
Topical Mapping · Guided
Give a topic its own URL only when the user and the map need it.
MIRENA does not turn every promising query into a page. It checks distinct intent, answer depth, page role, separation, link path, reader value, and overlap before deciding whether the topic becomes a page or stays inside a stronger parent.
Guided level
Internal MIRENA workflow
Static explanation
Human review required
InputAn approved query bucket, result set evidence, parent topic, current page inventory, and intended user path.Evidence enters before the decision.
DecisionDoes the topic need a page, child page, section, question, merge, or hold state?The state remains visible.
OutputA granularity record with the decision, reason, parent, role, depth, overlap risk, and next route.The handoff carries the reasoning.
Next routeMap Approval WorkflowDownstream 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.
Test intent separation
A different phrase is not enough. The required answer must change.
Test useful depth
The topic needs enough explanation, proof, examples, routes, and next steps to stand alone.
Assign a page role
Hub, child, comparison, template, example, support, or section is stated explicitly.
Check route and overlap
MIRENA reviews parent, sibling, internal link, and cannibalization effects.
Record the decision
The topic becomes a page, child, section, question, merge, reject, or hold.
Decision model
The decision is broader than page or section.
MIRENA keeps all valid treatments visible so a thin topic is not forced into a URL.
Full page
Distinct intent, enough depth, clear role, clean separation, and a dedicated route.
Child page
Distinct support need that belongs under a stable parent hub.
Section or question
Narrow support need that is more useful inside the parent answer.
Merge or hold
Duplicate intent, weak depth, unstable ownership, or missing evidence blocks publication.
Illustrative MIRENA output
Illustrative granularity decision
The record carries the decision into the map and later brief.
TopicCommon page split mistakes
ParentPage vs Section Decisions
IntentSupporting diagnostic
DepthShort explanation and checklist
DecisionSection
ReasonThe need supports the parent and lacks a separate route
Overlap riskHigh if published as a standalone page
Next routeMap Approval Workflow
Guardrails
The method protects the map from predictable failure.
A keyword is not a page plan
Search volume does not prove separate intent.
Do not pad thin pages
Depth must come from user need, not word count.
Sections still need a job
A section should not become a dumping ground.
Set the parent first
A page or section decision only works inside a clear cluster.
Connected routes
Move only into the workflow that owns the next decision.
Query Buckets
Continue only when the current decision and evidence are ready.
Open Query BucketsMap Approval Workflow
Continue only when the current decision and evidence are ready.
Open Map Approval WorkflowTopic Governance Rules
Continue only when the current decision and evidence are ready.
Open Topic Governance RulesTopical Mapping Hub
Continue only when the current decision and evidence are ready.
Open Topical Mapping HubQuestions
Page vs Section Decisions questions.
When does a topic deserve its own page?
When it has distinct intent, enough useful depth, a clear role, clean separation, and a dedicated route.
When should a topic stay as a section?
When it is close to the parent, answers a narrow support need, or would create overlap as a separate URL.
Can a topic become a child page?
Yes. A distinct support need can earn a child page when the parent relationship and internal route are clear.
What if the evidence is mixed?
MIRENA holds the decision until result patterns, ownership, depth, and overlap are clear.
What happens after the decision?
The decision enters map approval with the role, parent, priority, and handoff fields.
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.