MIRENA · Product documentation
The MIRENA workflow moves from source context to a reviewed publish pack.
Seven stages keep site scope, page ownership, briefing, production, internal routes, approval, and handoff in sequence.
Verified facts and boundaries.
These fields identify the entity, product, document, or operational boundary without turning related parties into the same entity.
Stage 1 — Source context.
Set the site, organisation, product or service, audience, region, allowed topics, blocked topics, protected pages, evidence rules, tone, claims, internal-link policy, and desired output.
The accepted context becomes a project boundary. A material change can reopen later stages.
Stage 2 — Topic or page intake.
Identify the unit entering the system and its current state. The unit may be a topic, URL, draft, sitemap, cluster, data file, query set, or previous deliverable.
The intake records what exists, what is missing, what must be protected, and which workflow owns the first unresolved decision.
Stage 3 — Topical mapping.
Resolve entities, intent layers, page roles, hierarchy, cluster homes, gaps, overlap, cannibalisation, internal routes, build order, and pages that should not be created.
The accepted map row becomes the input to briefing.
Stage 4 — Content brief.
Turn one approved page role into a writer-ready contract: user task, opening answer, entities, attributes, evidence, section jobs, answer formats, internal links, CTA boundary, exclusions, and QA.
A brief is accepted only when the page job and evidence requirements are clear enough for production.
Stage 5 — Draft or rewrite.
Build new copy from the approved brief or repair the smallest evidenced failure in an existing asset. Preserve strong material and expose unsupported claims or unresolved proof.
The result includes the content, change record, open issues, and review state.
Stage 6 — Internal-link pass.
Connect the page to parent, child, sibling, bridge, proof, support, and action routes. Each link must have a destination owner and a reason to exist.
Broken, stale, ambiguous, or premature routes remain open issues rather than being inserted automatically.
Stage 7 — Publish pack.
Package the final visible draft, metadata, links, CTA, asset requirements, unresolved items, approvals, implementation instructions, and later schema candidates.
Final schema and public release remain blocked until the written draft and specialist reviews are approved.
Re-entry and change control.
A source, product, policy, price, identity, page-role, or technical change can invalidate downstream work. Only affected stages should reopen.
The workflow records the prior accepted state, the material change, the repair, and the downstream validations that must run again.
Check the controlling first-party and official sources.
These routes support the current public statement. External platform and legal sources remain subject to their own updates.
MIRENA workflow
Current first-party seven-stage workflow.
MIRENA inputs
Current first-party input and safety requirements.
MIRENA outputs
Current first-party output and handoff requirements.
Move to the page that owns the next question.
Each route has a separate job so company, product, trust, legal, and compliance information does not collapse into one promotional page.
Owned route
How MIRENA works
Routing and the product operating model.
Open route →
Owned route
Inputs
Minimum source and evidence requirements.
Open route →
Owned route
Outputs
Deliverables and handoff fields.
Open route →
Owned route
Agents and modules
Specialist responsibilities at each stage.
Open route →
Owned route
Human review
Approval gates and accountable owners.
Open route →
Owned route
Compliance Hub
Claims, sources, review, approval, corrections, and records.
Open route →