MIRENA product record
Follow releases that change how MIRENA plans sites, briefs pages, audits drafts, builds internal link routes, and checks output quality. Each record names the date, affected areas, user impact, and any plan note.
Release history
Use the category controls to isolate workflow changes, output improvements, fixes, or plan notes. Release records stay in reverse date order.
A new behavior layer connects semantic SEO decisions with user state, journey stage, friction, trust, effort, satisfaction, feedback, testing, compliance, readiness, synchronization, and observability.
Founder access opens with the full 20 agent workflow. Current commercial terms provide one seat, one active MIRENA instance, and 30 days of access for €20 excluding VAT.
28 April 2026 · Workflow, output, and fix update
The Behavioral Topical Map Overlay, known as BTMO, extends MIRENA beyond topic coverage and entity structure. It adds controls for how users understand, trust, decide, act, and continue.
Queries, pages, blocks, links, and topical map edges receive user state, journey stage, friction, trust, effort, and next path data.
Passages can explain, compare, prove, reassure, route, convert, support, warn, summarize, demonstrate, qualify, or distinguish.
Schema, SERP targets, links, calls to action, proof claims, and tests can be held when the user value or supporting evidence is weak.
| Decision area | Earlier emphasis | Added behavior layer |
|---|---|---|
| Topical map | Entities, queries, clusters, page roles, and semantic links | User states, journey stages, friction, trust, effort, satisfaction, and feedback |
| Internal links | Entity relationship and topical proximity | Next useful path, readiness, proof need, support need, and effort reduction |
| Content blocks | Coverage, structure, entity support, and SERP format | Behavioral role, user gain, trust support, and safe action timing |
| Schema and SERP work | Eligibility and machine readable structure | Visible support, risk checks, user value, and evidence matching |
| Release decision | Semantic fit and output quality | Publish, hold, revise, test, suppress, synchronize, or escalate |
Core patch modules
Adds shared fields for nodes, edges, blocks, links, query clusters, trust, effort, satisfaction, and feedback.
Classifies states such as beginner, comparing, skeptical, ready to act, urgent, returning, or expert.
Maps queries, pages, blocks, and edges to awareness, education, comparison, trust, action, support, or retention.
Scores topical map edges by semantic fit, user state, journey fit, trust support, effort reduction, and friction reduction.
Selects the most useful next page, block, proof route, support route, or action.
Matches anchors and destinations to readiness, journey value, proof need, support need, and user usefulness.
Finds confusion, missing proof, weak links, effort barriers, and other blockers across queries and content.
Turns skepticism, price uncertainty, authority needs, and process concerns into proof requirements.
Scores the work required to understand, compare, trust, choose, act, troubleshoot, or continue.
Separates machine facing information gain from human facing user gain, then records a combined score.
Assigns a practical job to each passage, including explain, compare, prove, reassure, route, convert, support, or warn.
Recommends summaries, tables, proof cards, calculators, questions, actions, support steps, videos, diagrams, and fallback routes.
Checks snippets, questions, lists, tables, review blocks, local blocks, and other search formats for real user value.
Recommends, revises, blocks, or suppresses schema when visible support, evidence, safety, or user value is missing.
Collects approved signals from search, engagement, links, actions, support outcomes, SERP results, schema, feedback, CRM, and review.
Turns signals into reinforcement, demotion, revision, suppression, testing, or escalation decisions.
Creates controlled tests for passages, anchors, actions, proof blocks, internal links, components, schema candidates, and layouts.
Checks safety and support before publishing, schema work, search targeting, tests, link changes, actions, claims, and feedback updates.
Combines the behavior stack into a release decision with owners, blockers, rollback state, and monitoring needs.
Shares behavior state across BTMO modules through the MIRENA knowledge sharing layer.
Runs regression, schema, sync, scoring, safety, SERP, link, path, experiment, satisfaction, and rollback checks.
Provides monitoring for blockers, risk, synchronization, satisfaction, schema, SERP status, link health, owners, and retest queues.
New output records
The added records connect planning decisions with user value, release controls, and later performance review.
Adds user state, journey, friction, trust, effort, satisfaction, and feedback fields to nodes and edges.
Shows who an asset serves and where it sits in the path from entry to support or retention.
Lists blockers and records the proof, source, author, process, pricing, or reassurance needed.
Shows user effort and balances original retrieval value with practical user value.
Recommends the next useful route plus summaries, tables, proof cards, questions, actions, or visual support.
Checks search blocks and structured data against visible content, support, risk, trust, and user value.
Collects approved post publication signals and converts them into revision, testing, or escalation decisions.
Defines variants, measures, guardrails, rollback rules, and review windows.
Records release state, owners, blockers, risk, rollback needs, health checks, and retest queues.
19 February 2026 · Plan update
The first public access milestone positions MIRENA as a structured SEO operating system for site planning, page briefing, audits, drafting, rewriting, information gain, SERP formats, and internal link direction.
Current pricing language now states the access period, seat limit, VAT treatment, platform boundary, cancellation route, and Founder rate condition more precisely than the original release note.
Release categories
Category labels make it easier to distinguish structural changes from output changes, corrections, and commercial notes.
Changes to planning, entity modeling, intent, structure, sequencing, internal links, checks, or handoffs.
Changes to topical maps, briefs, audits, drafts, rewrite records, SERP formats, schema cues, or link plans.
Corrections to process behavior, output quality, data handling, wording, validation, or release logic.
Changes to price, VAT, access periods, seats, active instances, cancellation, Founder conditions, or rollout.
Questions
MIRENA is actively developed. Public records are added when an approved product, workflow, output, fix, or plan change is ready to be communicated.
Active Founder users receive core system updates under the current published terms. Future advanced modules or plans may be packaged separately.
Important plan notes can cover price, VAT treatment, access periods, seat limits, cancellation, Founder rate conditions, and product rollout. The pricing and legal records control current commercial terms.
No. Each release names the affected area. A workflow update can change planning or validation without changing pricing, while a plan note can change access terms without changing product logic.
Send product, account, or billing questions to support@semantecseo.com. Include the release name and the workflow or output affected.
Choose the next route
Use pricing for current access terms. Use contact support for product, account, billing, cancellation, privacy, or business questions.