Holds the cluster frame and routes the main branches.
Topical Mapping · Cartographer · Guided
Build a hierarchy where each child owns one narrower branch of a clear parent.
A parent topic gives the cluster its center. A child topic takes one narrower branch and earns a page only when it has a distinct job, enough depth, a clear boundary, and a route back into the parent system.
Hierarchy designProcessed map inputEvidence and owner requiredBrief follows approval
Learning levelGuidedDecision complexity, not content value
Primary jobHierarchy designOne owned decision
MIRENA outputThe MIRENA hierarchy recordEvidence, owner, route, and state
Commercial route€20 per 30 daysVAT added where applicable
Protected centerpiece
A clean hierarchy has three levels, not a flat list.
MIRENA separates parent, child, and section decisions before the page inventory is approved.
Handles one intent with enough depth for its own page.
Explains a small part of the parent or child without creating a new URL.
Records how each child differs from the pages beside it.
Connects the hierarchy through useful internal paths.
How MIRENA handles the decision
The workflow keeps source context, ownership, evidence, and handoff connected.
Define the parent in one line
MIRENA states the broad topic, user job, boundaries, and branches the parent can hold.
List child candidates
The system groups narrower subtopics by intent, role, depth, and evidence.
Make page or section calls
Each candidate becomes a child page, section, merge, hold, or reject.
Test sibling difference
MIRENA compares the one line purpose, entities, answer shape, and next route of each child.
Lock the hierarchy and links
The output declares parents, children, siblings, parent links, cross links, and downstream routes.
Decision checks
MIRENA tests the signals that can change the structural outcome.
Can the topic hold several distinct branches without becoming vague?
Can the narrower job be stated in one sentence?
Does the point fit inside the owner without a new page?
Do child pages have different purposes and depths?
Can every child return to the parent and continue usefully?
Does the hierarchy stay inside the approved topic lane?
Worked example
Parent and child topics inside Topical Mapping
Close pages can stay separate when each owns a different structural question.
Topical Mapping frames governed page ownership and routes the category.
Hub Page Design owns the cluster center.
Spoke Page Design owns narrow child page design.
Query Deserves Granularity owns page versus section routing.
A small note about singular and plural wording belongs inside granularity rather than a new URL.
Common failure modes
The wrong upstream decision can create clean looking content inside a weak architecture.
Every candidate appears at the same level.
The cluster has no readable center or boundary.
A short support point becomes a weak page.
Two child pages cannot explain their difference in one line.
MIRENA handoff
The MIRENA hierarchy record
Broad owner and boundary
Narrow job and page decision
Support points that stay on an owner
The one line difference between close children
Parent, child, sibling, proof, and next routes
Pass, revise, merge, split, hold, or block
Connected Topical Mapping routes
Continue with the asset that owns the next decision.
Questions
Parent and Child Topics questions.
What is a parent topic?
It is the broader topic that gives a cluster its center and holds several distinct branches.
What is a child topic?
It is a narrower branch with enough distinct intent, depth, and route to earn a page.
Should every subtopic become a child page?
No. Small support points should remain sections, questions, examples, or blocks inside an owner.
How does MIRENA test sibling overlap?
It compares purpose, intent, depth, entities, structure, boundary, and next route.
Next route
Give MIRENA the source context and working evidence. MIRENA returns the governed map decision.
Founder access provides one seat and one active MIRENA instance for 30 days at €20 excluding VAT. OpenAI account rules and usage limits remain separate.