Skip to main content

  1. MIRENA
  2. MIRENA
  3. MIRENA Human Review and Approval

MIRENA · Product documentation

MIRENA output is working material until an accountable person accepts it.

Human review checks facts, evidence, rights, page ownership, copy, links, code, privacy, accessibility, commercial terms, implementation, and release authority before the work is treated as final.

Public record

Verified facts and boundaries.

These fields identify the entity, product, document, or operational boundary without turning related parties into the same entity.

Working outputNot final by default
Written-draft gateRequired
Final schemaBlocked before written-draft approval
PublicationRequires authorised release owner
Specialist reviewRequired where the subject demands it
Post-publishRequires real live evidence
01

Review is part of the product method.

A structured workflow can reduce ambiguity, but it cannot replace the person or organisation responsible for the final statement and action.

The reviewer must understand the page, source, audience, risk, and downstream implementation—not merely approve fluent wording.

02

Review responsibilities by subject.

Review ownership
Area Typical owner Required decision
Factual and source accuracy Editor or subject owner Claims match current evidence and scope
Product and price Product or commercial owner Offer, version, VAT, seat, and access are current
Legal and consumer terms Accountable legal reviewer Operative clauses and mandatory rights are suitable
Privacy and security Privacy or security owner Data flows, controls, providers, and incidents are accurate
Accessibility Accessibility and front-end reviewer Content and interactions are usable in target environments
Technical and CMS Developer or site operator Links, metadata, rendering, code, and rollback are valid
Client or business approval Authorised business owner Scope, claims, brand, and release are approved
03

The final written-draft gate.

The complete visible draft must receive explicit approval before final publishable structured data or final publishing authorization.

Before approval, MIRENA may provide schema candidates, type recommendations, property notes, and placeholders. Those notes do not become final JSON-LD until the visible page and entity facts are accepted.

04

Approval must identify the object and scope.

  • Exact page, file, package, or version
  • Approval owner and authority
  • Claims, sections, assets, and links included
  • Known exclusions or unresolved items
  • Environment or channel covered
  • Date and condition that would require reapproval
05

A reviewer can accept, return, hold, or reject.

Approval is not binary when the evidence is mixed. A reviewer may accept the page except for one held claim, return a section for repair, block release, or reject the page role.

A downstream owner may not consume failed, blocked, or stale work as though it passed.

06

Material changes reopen affected review.

A new price, policy, product version, provider, entity name, evidence source, internal route, or implementation can invalidate a prior approval.

Only the affected decisions and downstream checks need to reopen, but the change must be recorded.

07

Publication and monitoring remain external actions.

MIRENA can prepare a release package. An authorised site operator must still deploy, verify the live page, confirm the rollback route, and collect post-publish evidence.

Sources

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.

Semantec SEO
MIRENA workflow

Current first-party production and publish gates.

Open source →

Semantec SEO
MIRENA outputs

Current first-party output and human-review boundary.

Open source →

Google Search Central
Google generative AI guidance

Official guidance to focus on accuracy, quality, and relevance.

Open source →