MIRENA · Product documentation
MIRENA routes the current SEO problem through a sequence of owned decisions.
The system begins with source context, identifies the starting asset, chooses the smallest valid workflow, runs specialist checks, creates a governed output, and stops at human and implementation gates.
Verified facts and boundaries.
These fields identify the entity, product, document, or operational boundary without turning related parties into the same entity.
1. Source context sets the boundary.
The project identifies the site, audience, offer, allowed topic lanes, blocked claims, protected pages, internal-link rules, evidence sources, and desired output.
Without this boundary, a technically polished page can still be off-topic, commercially wrong, legally unsafe, or destructive to existing page ownership.
2. Intake identifies the real starting unit.
The starting point may be a topic, URL, draft, sitemap, cluster problem, evidence pack, or current MIRENA output. The system records what exists, what is missing, and which decision is actually open.
The same topic can enter different workflows depending on whether the user needs a site plan, page brief, draft, rewrite, link repair, or review.
3. Routing selects the smallest owning workflow.
| Starting problem | Owning route | First accepted output |
|---|---|---|
| New site or cluster | Source context → topical mapping | Processed map and page inventory |
| New page | Approved page role → content brief | Writer-ready page contract |
| Existing page | Audit → bounded rewrite | Repair plan and revised asset |
| Weak internal route | Link audit and route planning | Source-target-action record |
| Answer-format problem | SERP and visible-format review | Approved paragraph, list, table, FAQ, or comparison block |
4. Specialist controls share one project state.
Entity, intent, information gain, evidence, passage roles, vocabulary, internal links, visual semantics, accessibility, and review modules do not operate as unrelated prompts.
An accepted upstream change can invalidate downstream work. Failed or stale state cannot be handed to the next stage as though it passed.
5. Every stage returns a named handoff.
A stage should end with a map, brief, audit, draft, rewrite, link plan, answer block, hold decision, or review record—not an unbounded conversation.
The handoff names the owner, evidence, state, open issues, and next route so a contributor can act without recreating the earlier decisions.
6. Hard gates stop unsafe progression.
- Context gate: audience, offer, scope, or protected pages are unclear
- Planning gate: ownership, overlap, role, or routes are unresolved
- Production gate: facts, proof, rights, or page structure cannot support the draft
- Approval gate: final written content has not been approved
- Publish gate: claims, links, accessibility, technical checks, or implementation remain open
7. External actions remain truthful.
MIRENA can produce a publishing package or implementation plan, but it cannot claim that a CMS, analytics platform, Search Console, crawler, rank tracker, or deployment system ran unless an available tool actually performed that action.
Live rendering, publication, measurement, and post-publish optimisation require permissions and evidence from the target environment.
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 and gates.
MIRENA product overview
Current first-party routing and operating model.
MIRENA inputs
Current first-party input preparation and safety guidance.
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
MIRENA Workflow
The complete seven-stage sequence and handoff contract.
Open route →
Owned route
Inputs
Input preparation and safety boundaries.
Open route →
Owned route
Outputs
Output families and required handoff fields.
Open route →
Owned route
Agents and modules
Specialist responsibilities and orchestration.
Open route →
Owned route
Human review
Approval ownership and release states.
Open route →
Owned route
Open MIRENA
Start a supported workflow in ChatGPT.
Open route →