The intent, entities, questions, proof, and decision that belong here.
Topical Mapping · Cartographer · Guided
Keep each page deep in one direction instead of broad across every adjacent topic.
Topic scope control decides what a page owns, what belongs on a child or sibling, what stays as a short block, what needs a link out, and what does not belong in the cluster.
Boundary controlProcessed map inputEvidence and owner requiredBrief follows approval
Learning levelGuidedDecision complexity, not content value
Primary jobBoundary controlOne owned decision
MIRENA outputThe MIRENA scope recordEvidence, owner, route, and state
Commercial route€20 per 30 daysVAT added where applicable
Protected centerpiece
Four scope states keep the page directional.
MIRENA records the states before the brief so the outline cannot absorb every nearby idea.
A child, sibling, parent, comparison, template, or product page owns the deeper need.
A small point helps the main answer but does not deserve a URL.
The topic drifts from the source context, duplicates an owner, or weakens the cluster.
How MIRENA handles the decision
The workflow keeps source context, ownership, evidence, and handoff connected.
Define the page purpose
MIRENA starts with the user job, page type, role, parent, and completion event.
Map nearby topics
The system lists child candidates, sibling owners, parent coverage, support points, and off scope ideas.
Assign scope states
Every nearby topic becomes own, hand off, support, or block.
Test depth and direction
MIRENA checks if the outline stays deep in the owned job instead of switching tracks.
Write the boundary into the brief
The handoff records included topics, excluded topics, links, blocked claims, and review rules.
Decision checks
MIRENA tests the signals that can change the structural outcome.
The point directly supports the primary job
The point has a narrower distinct intent and enough depth
The point belongs close but serves another job
The point improves the answer in a small block
The point drifts off context or duplicates an owner
The reader needs the point, but another page should explain it
Worked example
Scope control for a hub page
The hub stays useful without becoming the entire cluster.
Define the parent topic and expose the main branches.
Detailed spoke design and cluster entry logic move to their own pages.
A short page versus section note can support branch choice.
A full content brief tutorial does not belong inside the hub design page.
The hub routes the reader to the owned detail.
Common failure modes
The wrong upstream decision can create clean looking content inside a weak architecture.
The outline covers many adjacent jobs without completing one.
The page absorbs topics that have clear owners elsewhere.
The brief already carries the drift.
Off context ideas return during refreshes.
MIRENA handoff
The MIRENA scope record
The intent, entities, questions, and proof the page covers
Child, sibling, parent, template, proof, or product owners
Small points that stay local
Duplicate, off context, unsupported, or low value ideas
Where the reader moves for deeper or adjacent needs
What can reopen the boundary later
Connected Topical Mapping routes
Continue with the asset that owns the next decision.
Questions
Topic Scope Control questions.
What is topic scope control?
It is the decision about what a page owns, hands off, supports briefly, or blocks.
Does a narrow scope mean a short page?
No. A page can be deep and detailed while staying focused on one primary job.
How does scope control reduce overlap?
It declares the owners of adjacent topics before the brief and draft begin.
What should be recorded in the brief?
Owned topics, excluded topics, handoff owners, support blocks, required links, and blocked claims.
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.