Source context
Set the site, audience, offer, allowed topic lanes, blocked claims, protected pages, internal link rules, and desired output.
From input to governed output
MIRENA moves from context to planning, briefing, production, links, and handoff.
The workflow prevents a topic, URL, sitemap, or draft from jumping directly into copy. Each stage makes one class of decision and passes an approved record to the next owner.
7 stages3 production lanesSequential gatesHuman review
InputTopic, URL, draft, sitemapThe unit entering the workflow
PlanProcessed topical mapOwnership, roles, links, and sequence
PageBrief, draft, or rewriteEntity, intent, proof, format, and route
HandoffPublish packMetadata, links, CTA, approvals, and open issues
Seven stage workflow
Each stage has one job and one handoff.
Topic or page intake
Identify the starting unit: topic, URL, draft, sitemap, cluster goal, evidence set, or rewrite target.
Topical mapping
Resolve topic boundaries, entities, intent layers, page roles, support pages, gaps, overlap, links, and build order.
Content brief
Turn an approved page decision into entity, intent, passage, proof, format, internal link, and CTA instructions.
Draft or rewrite
Build or repair the page from the approved structure rather than starting from a blank prompt.
Internal link pass
Connect the page to parent, child, sibling, bridge, proof, support, and action routes.
Publish pack
Package the final draft, metadata, links, CTA, unresolved items, approval notes, and later schema cues.
Three common routes
The same controls support different starting problems.
Plan, brief, draft
Start with source context and evidence, process the map, brief one approved page, then draft and link it.
Brief, draft, route
Use an approved page role or map row, build the brief, produce the page, then connect it to the cluster.
Audit, rewrite, route
Confirm the page still owns the right job, repair failed blocks, update links, and return the revised publish pack.
Stage gates
Work stops when the evidence or ownership is not ready.
Context gate
Hold when the audience, offer, scope, protected pages, or desired output is unclear.
Planning gate
Hold when page ownership, overlap, role, or link routes remain unresolved.
Production gate
Hold when facts, proof, entity support, or the page structure cannot support the draft.
Publish gate
Hold when claims, links, accessibility, legal review, metadata, or final approvals remain open.
Questions
MIRENA workflow questions.
Why does MIRENA start with source context?
Source context controls the site, audience, offer, topic boundaries, protected pages, claims, and next workflow. Without it, later outputs can look complete while pointing in the wrong direction.
Can MIRENA start from an existing draft?
Yes. The draft enters intake, then passes through structure, entity, intent, information gain, link, and review controls before a rewrite is accepted.
When does a content brief begin?
Only after the page role, ownership, topic boundary, and major overlap decisions are approved.
Are internal links a final cleanup step?
No. Link routes begin in planning and are refined after the page structure is approved.
When are schema cues created?
After the visible draft is approved. Cues describe approved entities and page sections; final schema follows the stable page.
Choose the current stage
Use the workflow to move the asset into the smallest approved next job.
Review inputs before planning and outputs before production handoff.