Processed topical map
A site planning package with boundaries, inventory, page roles, gaps, links, sequence, and overlap decisions.
- planning stage
- cluster output
- brief input
What the system returns
MIRENA returns structure, content, links, and a governed handoff.
The output changes with the job. A topic can return a processed map. An approved page decision can return a brief or draft. An existing URL can return an audit and rewrite pack.
StructureMaps and briefsPage ownership, roles, entities, intent, and order
ContentDrafts and rewritesSupported copy, change records, and open issues
LinksInternal routesSource, target, relationship, anchor purpose, and placement
Later cuesSERP and schemaVisible formats and approved structured data notes
Eight output families
Choose the deliverable that matches the current job.
MIRENA does not need to return an article when the correct result is a map, brief, audit, link plan, or hold decision.
Entity led content brief
A page operating plan covering the entity model, intent, user state, passages, proof, format, links, and CTA.
- page stage
- writer handoff
- review gate
New draft
A draft built from an approved page plan rather than a loose prompt.
- approved brief
- source support
- editorial review
Rewrite pack
A revised asset plus structure, change notes, metadata, links, routes, and open issues.
- existing URL
- repair plan
- publish handoff
Audit and repair plan
A diagnosis of purpose, ownership, entity, intent, structure, proof, link, and user route failures.
- keep
- move
- combine
- remove
- expand
- rewrite
Internal link plan
Source, target, relationship, anchor purpose, passage placement, and user route recommendations.
- parent
- child
- sibling
- bridge
- proof
- action
SERP ready content blocks
Approved answer formats such as definitions, lists, questions, comparisons, processes, and evidence blocks.
- format follows task
- visible support
- no feature guarantee
Schema cues after approval
Entity, property, relationship, URL, and validation notes for later structured data work.
- approved content only
- developer handoff
- validation
Handoff package
Every output package should carry enough context for the next owner to act.
Asset identity
Project, URL, topic, query, owner, and workflow stage.
Decision record
What was approved, rejected, held, or sent for review.
Evidence record
Sources used, missing evidence, confidence, and risk.
Output body
Map, brief, draft, rewrite, audit, link plan, or content block.
Open issues
Claims, proof, links, approvals, technical needs, and later cues.
Next route
Named workflow, owner, blocker, and expected handoff.
Workflow position
The output is only useful when the next owner knows what to do.
Bring the source context
Set the site, audience, offer, constraints, and desired job.
Run the approved workflow
Plan, brief, draft, rewrite, audit, or route links.
Receive and review the package
Approve the visible output and send it to the named next stage.
Questions
MIRENA Outputs questions.
What does MIRENA return?
MIRENA can return processed topical maps, content briefs, drafts, rewrite packs, audits, internal link plans, search format blocks, and later schema cues.
Does every project receive every output?
No. The output depends on the job, source context, evidence, current stage, and approved next route.
Are outputs ready to publish automatically?
No. Facts, claims, links, accessibility, legal risk, editorial quality, and technical implementation still need review.
Why does source context affect output quality?
Source context controls the site, offer, audience, topic boundary, protected pages, proof, and desired route.
Can outputs return to an earlier stage?
Yes. Missing evidence, overlap, wrong page ownership, unsupported claims, or a changed goal can return work to intake or planning.
Next route
Use the output as the handoff into the next approved MIRENA stage.
Keep unresolved evidence, claims, links, ownership, and approval needs visible.