Frame the cluster and route readers into the main branches.
Topical Mapping · Cartographer · Guided
Give every page one role before the cluster moves into briefing.
Cluster roles define what each page does inside the architecture. MIRENA uses role assignment to separate broad and narrow intent, protect page ownership, plan internal routes, and stop a map from becoming a flat list of similar URLs.
Role assignmentProcessed map inputEvidence and owner requiredBrief follows approval
Learning levelGuidedDecision complexity, not content value
Primary jobRole assignmentOne owned decision
MIRENA outputThe MIRENA role recordEvidence, owner, route, and state
Commercial route€20 per 30 daysVAT added where applicable
Protected centerpiece
Six common roles give a cluster shape.
A page can support more than one route, but it receives one primary architectural role.
Answer a narrower intent with focused depth.
Explain a relationship and route between related clusters or stages.
Orient a first time visitor and show the next useful path.
Provide a reusable record, example, checklist, or implementation asset.
Connect educational coverage to a product, service, use case, or comparison path.
How MIRENA handles the decision
The workflow keeps source context, ownership, evidence, and handoff connected.
Identify the cluster home
MIRENA names the parent topic and the page that owns the center.
Define each page purpose
Every candidate receives one primary reader job and one owned intent.
Assign the primary role
The system matches purpose and depth to hub, spoke, bridge, entry, template, support, or commercial.
Test sibling boundaries
MIRENA checks if nearby pages have different jobs, depths, and next routes.
Build the route graph
The output declares parent, child, sibling, proof, support, and next action links.
Decision checks
MIRENA tests the signals that can change the structural outcome.
Broad parent intent and multiple distinct branches
One narrower intent with enough depth for a full page
A useful relationship between two owned lanes
A likely first landing that needs orientation and a handoff
The user needs a reusable asset rather than another explanation
The page supports a real decision without taking over the cluster.
Worked example
A role system for the Topical Mapping cluster
Each asset can stay close in topic while doing a different job.
Parent hub and category entry point
Spoke that owns the design of the cluster center
Spoke that owns first landing and route logic
Template role with a reusable working record
Comparison and orientation role
Commercial use case route
Common failure modes
The wrong upstream decision can create clean looking content inside a weak architecture.
The cluster has no center, bridge, template, or decision path.
A phrase does not decide the architectural job.
A page that tries to lead, compare, teach, and convert equally becomes unclear.
A role without declared routes cannot support the cluster.
MIRENA handoff
The MIRENA role record
The main architectural job
The one reader job the page owns
The declared cluster home
The nearest pages and their separate jobs
Links required by the role
Brief, blueprint, merge, split, or review
Connected Topical Mapping routes
Continue with the asset that owns the next decision.
Questions
Cluster Roles questions.
What is a cluster role?
It is the primary function a page performs inside a topic cluster.
Can a page have more than one role?
A page can support several routes, but MIRENA records one primary role to protect clarity and ownership.
What are the main cluster roles?
Common roles include hub, spoke, bridge, entry, template, support, comparison, and commercial.
Why assign roles before writing?
Roles define page scope, prevent overlap, shape links, and give the content brief a clear job.
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.