MIRENA separates specialist responsibilities but keeps one project state.

Verified facts and boundaries.

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

Agents own broad responsibilities.

The public system describes specialist responsibilities for query intent, entities, information gain, semantic expansion, content structure, drafting, vocabulary, internal linking, SERP features, schema, reasoning control, compliance, and shared state.

The names describe execution responsibilities inside one product. They do not imply separate companies, human employees, or background services running independently.

Modules own narrower checks.

The registry contains 181 module records. A module may classify intent, map entity attributes, score information gain, plan a centerpiece, select a route, inspect passage density, validate behaviour, prepare schema candidates, or manage post-publish feedback.

The registry is an orchestration index. Strict execution depends on the complete module specification from its declared source files.

One state machine controls handoffs.

Repair is local where possible.

When a module fails, the system should repair the smallest failing unit and rerun only the affected downstream work. Restarting the whole project can destroy valid accepted decisions and obscure the actual defect.

After the permitted repair cycles are exhausted, the system records the blocker and returns the furthest valid output.

Module applicability depends on the page.

A legal document, company profile, product page, topical map, rewrite, schema plan, and post-publish experiment do not use the same modules in the same way.

A module may be not applicable only with a written reason. Post-publish modules may be deferred only when live evidence genuinely does not yet exist.

Human and external boundaries.

Agent and module execution does not replace legal, security, privacy, accessibility, product, editorial, or release authority. A module cannot self-approve a failed validation.

The system also cannot claim that an external API, crawler, CMS, analytics product, or deployment ran unless an available tool performed the action.

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.

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.