MIRENA Approval Flow | MIRENA

Cross workflow governance

MIRENA keeps approval state visible from source evidence to production handoff.

Maps, briefs, audits, drafts, rewrites, link plans, and schema cues do not share the same approval owner, but they need one consistent state model. MIRENA records version, owner, evidence, blockers, decision, conditions, and next workflow.

StatesSix controlsDraft, review, revise, hold, approve, or supersede
RecordVersion and ownerEvery decision attaches to a specific output
GateEvidence and scopeThe asset cannot outrun the approved source context
HandoffNext workflowOnly approved material moves forward

Central distinction

MIRENA Approval Flow

Maps, briefs, audits, drafts, rewrites, link plans, and schema cues do not share the same approval owner, but they need one consistent state model. MIRENA records version, owner, evidence, blockers, decision, conditions, and next workflow.

A completed output is not the same as an approved output.

MIRENA process

The internal workflow turns evidence into an approved handoff.

Register the output

MIRENA records the workflow, version, owner, target asset, and current state.

Check source and scope

The output must fit the approved site, audience, offer, page role, and evidence boundary.

Run the workflow gate

The map, brief, draft, link plan, or schema cue receives its own quality checks.

Record failed checks

Every failure receives a reason, severity, owner, and required change.

Approve, revise, or hold

The decision and any conditions are attached to the exact version.

Create the handoff

Approved items move forward while superseded, held, and unresolved items remain visible.

Operating model

Shared approval states

The state model stays consistent even when the checks and reviewers change.

Working materialDraft

The output can change and must not enter production.

Gate runningIn review

Reviewers inspect scope, evidence, quality, risk, and route.

Owned repairRevise

The output can pass after named changes.

BlockedHold

A required input, decision, or approval is missing.

Controlled versionApproved

The output can move to the named downstream workflow.

Historical recordSuperseded

A newer approved version replaces the old one.

Illustrative record

Approval differs by workflow

The same state label can carry different checks.

Example output

  • Topical mapPage ownership, overlap, routes, priority, and protected pages.
  • Content briefPurpose, intent, entities, structure, proof, links, and exclusions.
  • Draft or rewriteAnswers, facts, structure, evidence, links, claims, and editorial quality.
  • Internal link planSource, target, route job, anchor direction, and placement.
  • Schema cueVisible approval, type fit, properties, identity, validation, and timing.

Related routes

Move the approved finding into the smallest useful next workflow.

Brief governance

Brief Approval Flow

Review and approve content briefs.

Review the route
Release gate

Publish Readiness Checks

Check the final asset before publication.

Review the route
Product process

How MIRENA Works

See how the approval layer fits the system.

Review the route
Output library

MIRENA Outputs

Review the shape of each workflow handoff.

Review the route

Questions

MIRENA Approval Flow questions.

What is MIRENA approval flow?

It is the shared state model that records draft, review, revision, hold, approval, supersession, and downstream handoff.

Does every workflow use the same checks?

No. The states are shared, while maps, briefs, drafts, links, and schema cues use different gates.

Can an approved output change?

Yes, but the new version must enter review. The earlier approved version remains the controlled record until replaced.

What is a conditional approval?

It is approval tied to explicit conditions that cannot change the core structure, claims, or safety of the output.

What does MIRENA return?

MIRENA returns the state, version, failed checks, owner, condition, supersession note, and next workflow route.

Next route

Give MIRENA the source context and evidence. Receive the controlled output or handoff.

Founder access is €20 per 30 days excluding VAT for one seat and one active MIRENA instance. OpenAI account rules and usage limits remain separate.

MIRENA output requires factual, editorial, legal, technical, and business review before publication or client delivery.