MIRENA is actively developed. This page tracks product updates, workflow changes, output improvements, fixes, and important plan notes. It exists so users can see what changed, why it changed, and what it affects.
MIRENA is built as a structured, multi agent SEO workflow. It is positioned around entity relationships, information gain, SERP structure, internal linking architecture, and schema ready output rather than loose prompt-response writing. That is the lens for every update logged here.
Latest updates
The Szymon Update – 28th April 2026
Behavioural Modules Patch Update Details
The new behavioural patch is the BTMO layer: Behavioral Topical Map Overlay. It upgrades MIRENA from a mainly semantic SEO stack into a semantic + user-journey + satisfaction validation system. The core patch adds user-state, journey-stage, friction, trust, effort, satisfaction, feedback, testing, compliance, readiness, sync, validation, and observability logic across the stack.
Core Patch Modules
| # | Module | Patch Detail |
|---|---|---|
| 001 | BehavioralTopicalMapSchema | Adds the shared behavioural schema for topical nodes, edges, content blocks, links, query clusters, schema directives, friction, trust, effort, satisfaction, and feedback fields. |
| 002 | UserStateClassifier | Classifies user state behind a query, node, page, content block, or path, such as beginner, comparing, skeptical, ready to act, high urgency, returning, or expert. |
| 003 | JourneyStageMapper | Maps each query, node, page, block, and edge to journey stages such as awareness, education, comparison, trust check, conversion, support, or retention. |
| 004 | FrictionPointExtractor | Detects user friction from queries, SERP gaps, competitor gaps, content gaps, link weakness, trust gaps, effort barriers, and behavioural signals. |
| 005 | TrustRequirementMapper | Converts skepticism, proof gaps, pricing uncertainty, local relevance, authority needs, and process concerns into trust requirements for content, links, schema, SERP blocks, and CTAs. |
| 006 | EffortScoreEngine | Scores how hard a user must work to understand, compare, trust, choose, convert, troubleshoot, or continue. It flags reading load, weak structure, missing proof, unclear CTAs, price opacity, and poor paths. |
| 007 | BehavioralEdgeWeightingEngine | Reweights topical-map edges and internal-link paths by user usefulness, not only semantic closeness. It blends semantic weight with user state, journey fit, effort reduction, trust support, and friction reduction. |
| 008 | PassageRoleClassifier | Assigns each passage a behavioural role, such as explain, compare, prove, reassure, route, convert, support, warn, summarize, demonstrate, qualify, or differentiate. |
| 009 | NextBestPathRecommender | Selects the most useful next path from a node, block, CTA, FAQ, proof need, comparison need, support need, or conversion opportunity. |
| 010 | BehavioralInternalLinkOptimizer | Upgrades internal linking from entity matching to behavioural path matching, using anchor fit, target readiness, link priority, journey value, and proof or support path logic. |
| 011 | InformationGainUserGainScorer | Separates machine-facing information gain from human-facing user gain, then combines both into a balanced score for content, links, schema, UX blocks, SERP targets, and page priorities. |
| 012 | UXContentComponentRecommender | Recommends the right content or UX component for each user need: summaries, tables, proof cards, calculators, FAQs, CTAs, support steps, warning notes, videos, diagrams, and fallback routes. |
| 013 | BehavioralSERPValidationModule | Validates that snippets, PAA, FAQ blocks, HowTo blocks, review blocks, local blocks, tables, lists, and schema-facing SERP targets serve users, not only search features. |
| 014 | BehavioralSchemaAdapter | Adapts behavioural signals into schema recommendations and blocks schema that is unsupported, misleading, thin, risky, or disconnected from visible user value. |
| 015 | SatisfactionSignalIngestor | Ingests post-publish signals from search, engagement, internal links, CTAs, support outcomes, SERP performance, schema performance, feedback prompts, CRM, and editorial review. |
| 016 | BehavioralFeedbackLoopEngine | Converts satisfaction signals into reinforcement, demotion, revision, suppression, testing, or escalation decisions across the behavioural topical map. |
| 017 | ExperimentationVariantManager | Creates and manages controlled tests for passages, anchors, CTAs, proof blocks, internal links, UX components, schema candidates, SERP blocks, and page structures. |
| 018 | BehavioralComplianceAuditGate | Adds the safety gate before publish, schema deployment, SERP targeting, experiments, link changes, CTA changes, proof claims, and feedback-loop updates. |
| 019 | BehavioralPublishReadinessOrchestrator | Aggregates the full behavioural stack into an operational readiness decision for publish, hold, revise, test, rollback, suppress, sync, or escalate. |
| 020 | CrossAgentBehaviorSyncAdapter | Synchronizes behavioural topical-map state across all BTMO modules through the Multi-Agent Knowledge Sharing layer. |
| 021 | BehavioralValidationTestSuite | Runs regression, schema, sync, scoring, safety, compliance, SERP, link, path, experiment, satisfaction, and rollback tests across the full behavioural stack. |
| 022 | BehavioralObservabilityAuditDashboardLayer | Adds dashboard-ready monitoring for validation results, blockers, risks, sync events, satisfaction signals, feedback decisions, schema status, SERP status, internal-link health, and owner queues. |
What Changed Operationally
MIRENA now treats every page and content cluster as both a semantic asset and a user journey asset. The patch lets the stack ask: “Does this page help search engines understand the topic?” and also: “Does this page help the user understand, trust, decide, act, or continue?”
The biggest change is that ranking signals are no longer enough. SERP wins, schema eligibility, internal links, and content additions can now be blocked or sent to testing when they create user friction, unsupported claims, trust gaps, high effort, privacy risk, schema mismatch, or weak satisfaction outcomes.
New Output Types Added
| Output Type | Purpose |
|---|---|
| Behavioural topical map | Adds user-state, journey, friction, trust, effort, and satisfaction fields to nodes and edges. |
| User-state classification export | Shows who the page or query is likely serving. |
| Journey-stage mapping export | Shows where the asset sits in the user path. |
| Friction log | Lists blockers such as price uncertainty, confusion, proof gaps, local mismatch, or support friction. |
| Trust requirement map | Defines what proof, source, review, guarantee, author, local, or process support is needed. |
| Effort score | Shows how hard the content, CTA, link path, or support path is for the user. |
| Behavioural edge weights | Ranks links and paths by usefulness, not just topical similarity. |
| Passage role map | Shows what job each passage performs. |
| Next-best-path plan | Recommends the next useful page, block, CTA, proof route, support route, or fallback path. |
| Information gain + user gain score | Balances originality for retrieval with real usefulness for users. |
| UX component queue | Recommends tables, proof cards, FAQs, calculators, support blocks, CTAs, and visual aids. |
| SERP validation export | Checks SERP blocks for user value, risk, answer quality, trust, effort, and schema support. |
| Behavioural schema adaptation export | Converts behavioural evidence into schema add, revise, block, suppress, or review actions. |
| Satisfaction rollup | Aggregates post-publish satisfaction and dissatisfaction signals. |
| Feedback loop decision | Reinforce, demote, revise, test, suppress, or escalate. |
| Experiment package | Defines variants, metrics, guardrails, rollback rules, and measurement windows. |
| Compliance gate report | Blocks unsafe or unsupported behavioural recommendations. |
| Publish readiness report | Final release decision with owners, blockers, rollback state, and monitoring needs. |
| Observability dashboard | Stack health, blockers, validation status, satisfaction, risk, owner queues, and retest queues. |
Practical Effect
The behavioural patch makes MIRENA stricter. A page can now fail even when it is entity rich, schema ready, and SERP formatted if it does not reduce friction, build trust, lower effort, support the right journey stage, or satisfy users after publishing.
19 February 2026 – MIRENA Founders Edition opens
MIRENA opens with full 20 agent system access at Founder pricing of €20/month. Founder pricing stays active while the subscription stays active. Users can cancel anytime, but if they cancel, the €20 Founder rate cannot be restored later. Founders receive core upgrades as the system grows.
This means because MIRENA is not being positioned as a generic AI writer. It is being positioned as an SEO operating system that runs a structured pipeline across entity modeling, SERP gap detection, information gain, structural reinforcement, and internal linking architecture. The Founder release sets that product position from day one.
This update affects new Founder users, current subscribers, agencies, in-house marketers, and operators who want a more structured way to plan pages, build briefs, audit drafts, and improve internal linking.
Release categories
Updates on this page are logged under a few simple categories.
Workflow updates cover changes to how MIRENA handles planning, entity modeling, structure, and sequencing. That matches the core product story: entities, intent, gaps, structure, SERP features, internal linking, and schema ready output.
Output improvements cover changes to what MIRENA produces, including topical maps, structured briefs, draft audits, SERP ready formatting, and internal linking recommendations.
Fixes cover corrections to workflow behavior, output quality, or process clarity.
Plan notes cover pricing, access, Founder terms, and other changes that affect subscriptions or rollout. Current Founder pricing is €20/month, with cancellation allowed at any time, and Founder pricing preserved only while the subscription remains active.
Major milestones
Founders Edition launch
This is the first public milestone for MIRENA in its current expansion phase. The launch message is clear: MIRENA is expanding, public pricing is expected to increase later, tiered plans may follow, advanced modules may move higher, and Founder users keep core upgrades as the system grows.
Changelog goes live
This page is the running record of product momentum for MIRENA.
What this means for users
If you are using MIRENA, the point of these updates is not noise. The point is clearer structure, stronger planning, better brief generation, more usable draft and rewrite outputs, and tighter internal link logic. The system is designed to reduce randomness and guesswork by pushing work through a defined SEO workflow instead of one off prompting.
FAQ
How often is MIRENA updated?
MIRENA is described in the founder materials as actively expanding. This page is where those changes are logged as they are published.
Do Founder users get upgrades?
Yes. Founder users receive core upgrades as the system grows.
Does this page include pricing changes?
Yes. Important plan and pricing notes belong here when they affect access, Founder terms, or product rollout. The current Founder plan is €20/month.
What happens to Founder pricing if I cancel?
You can cancel anytime. But Founder pricing is preserved only while the subscription remains active. If you cancel, the €20 Founder rate cannot be restored later.
Is MIRENA just another AI writing tool?
No. The founder materials position it as a structured, multi agent SEO workflow that models entity relationships, information gain, SERP structure, internal linking architecture, and schema alignment before content is generated.
Keep moving
Want the full product breakdown? See Mirena.
Need current access and Founder plan details? See Pricing.