MIRENA · Product documentation
MIRENA returns a governed deliverable, not an isolated block of text.
The output changes with the job. A topic can return a processed map; an approved page can return a brief or draft; an existing URL can return an audit, rewrite, link plan, or hold decision.
Verified facts and boundaries.
These fields identify the entity, product, document, or operational boundary without turning related parties into the same entity.
Eight output families.
| Output | Primary job | Typical next owner |
|---|---|---|
| Processed topical map | Page ownership, hierarchy, boundaries, build order, routes | Content strategy or briefing |
| Entity and intent-led brief | Opening answer, section jobs, proof, formats, links, exclusions | Writer or production owner |
| New draft | Build from an approved brief and sources | Editorial review |
| Rewrite pack | Repair a current asset and show what changed | Editor and implementation |
| Audit and repair plan | Diagnose purpose, entity, intent, structure, proof, or route failures | Owning specialist |
| Internal-link plan | Source, target, relationship, anchor purpose, placement | Editor or developer |
| SERP-ready content blocks | Visible paragraph, list, table, FAQ, comparison, or process | Editor and QA |
| Schema candidates | Entity, property, relationship, and validation notes | Schema reviewer after content approval |
Every output carries the project state.
A deliverable should identify the project, page or asset, source context, workflow stage, accepted decisions, rejected options, evidence, open issues, owner, and next route.
If a required fact or permission is missing, the output should preserve that blocker rather than filling the gap with plausible copy.
Draft and rewrite outputs remain reviewable.
A new draft should be traceable to an approved brief. A rewrite should distinguish retained material, removed material, revised copy, evidence requests, internal-link changes, and reasons for the repair.
This record lets a human reviewer understand the change without diffing two long pages or trusting a model summary.
A hold decision can be the correct output.
MIRENA may return hold, merge, remove, redirect, request evidence, request approval, or use another page instead of producing a new article.
The output is judged by whether it settles the real decision safely, not by the amount of content generated.
Schema comes after visible-content approval.
Before approval, MIRENA can identify candidate entities, types, properties, URLs, and eligibility notes. Final publishable JSON-LD is a later stage that must match the approved visible page and rendered implementation.
Output limits.
MIRENA does not guarantee that a search engine will index, rank, cite, feature, or display an output. It does not prove that a client, regulator, user, CMS, or external platform will accept the work.
The recipient remains responsible for the review, implementation, publication, and monitoring appropriate to the asset.
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 outputs
Current first-party deliverable families and handoff requirements.
MIRENA workflow
Current first-party sequence and output gates.
MIRENA product overview
Current first-party output previews and product limits.
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
Inputs
Prepare the source and evidence required by the output.
Open route →
Owned route
Workflow
See where each deliverable is created and accepted.
Open route →
Owned route
Human review
Review duties and approval states.
Open route →
Owned route
Prompt system
How prompts enforce output contracts and stop rules.
Open route →
Owned route
Pricing
Current subscription scope and exclusions.
Open route →
Owned route
Open MIRENA
Run the workflow that owns the desired output.
Open route →