The user state, level, role, or decision context.
Topical Mapping · Cartographer · Guided
Give every page one primary job, one owned intent, and one next route.
Page purpose is the contract that connects the map to the brief. MIRENA defines what the page helps the reader do, what it owns, what it leaves to other pages, how the answer should appear, and where the reader goes next.
Purpose definitionProcessed map inputEvidence and owner requiredBrief follows approval
Learning levelGuidedDecision complexity, not content value
Primary jobPurpose definitionOne owned decision
MIRENA outputThe MIRENA purpose recordEvidence, owner, route, and state
Commercial route€20 per 30 daysVAT added where applicable
Protected centerpiece
The purpose statement has five parts.
MIRENA turns a vague page idea into a one line operating decision.
The one task, question, comparison, or decision the page owns.
The direct response, format, proof, and depth needed.
Topics, roles, and intents that belong on other owners.
The useful parent, child, sibling, proof, support, or action path.
How MIRENA handles the decision
The workflow keeps source context, ownership, evidence, and handoff connected.
Receive the map row
MIRENA starts with the topic, query cluster, parent, role, evidence, and page or section decision.
Define the reader job
The system states the need in plain language without relying on the keyword.
Choose the answer form
MIRENA selects the page type, opening answer, depth, proof, format, and completion event.
Lock the boundary
The page records what it owns, what it links to, and what it must not repeat.
Create the brief handoff
The purpose statement moves into the brief, outline, internal link requirements, and review gate.
Decision checks
MIRENA tests the signals that can change the structural outcome.
Can the page job be explained in one clean sentence?
Does the page own one query cluster and user need?
Does the visible shape fit the job?
What should the reader know, decide, do, or open next?
Which sibling jobs remain separate?
What links and actions complete the page?
Worked example
A purpose statement for Hub Page Design
The statement prevents the asset from becoming a generic Topical Mapping explainer.
A strategist planning the parent page of a topic cluster.
Understand the hub job and the required visible parts.
A direct definition, anatomy, route groups, overlap rules, and link contract.
Leave spoke design, cluster roles, and the full internal link method to their owners.
Return to Topical Mapping or move into a blueprint or brief.
Common failure modes
The wrong upstream decision can create clean looking content inside a weak architecture.
A phrase does not describe the reader job.
The page tries to explain, compare, teach, sell, and support equally.
Nearby pages get repeated inside the outline.
The next route should follow the page job rather than appear as a late decoration.
MIRENA handoff
The MIRENA purpose record
The primary user state
The one need the page owns
Page type, direct answer, depth, and proof
What changes for the reader
Owned and excluded topics
Parent, sibling, proof, support, and action links
Connected Topical Mapping routes
Continue with the asset that owns the next decision.
Questions
Page Purpose Framework questions.
What is a page purpose framework?
It is a method for defining what a page is meant to do before a brief or draft is created.
Can one page support several intents?
It can support related needs, but MIRENA records one primary purpose and one main owned intent.
Why does purpose come before the brief?
Purpose controls scope, page type, block order, proof, internal links, and the completion event.
What should a purpose statement include?
Audience, reader job, answer, boundary, completion event, 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.