Orient
Learn the language, page roles, evidence rules, and first route.
Main category hub · Command deck
Move through Docs from first principles to governed practice.
The Docs hub is the operating manual for preparing inputs, selecting workflows, understanding outputs, reviewing approvals, and moving through MIRENA without losing the source context.
The hub is the main node for 19 complete assets. It gives beginners a clear first route, gives practitioners a production path, and gives advanced operators the controls needed to govern ownership, evidence, approval, maintenance, and scale.
19 complete assets
5 learning levels
4 entry states
One main category node
Beginner route
Learn what MIRENA needs and how the workflow is organised.
Start with language, ownership, and the first useful decision.
Practitioner route
Turn approved decisions into a working output
Build only after the input, scope, and owner are clear.
Advanced route
Govern evidence, prompt execution, approval states, output quality, and handoff controls.
Govern evidence, dependencies, and long term quality.
Hub rule
Every asset earns a clear role and route
No child asset sits as an unowned archive item.
Start from the current state
Choose the route that matches the decision already in front of you.
The route selector moves a beginner, practitioner, or advanced operator into the smallest asset that can own the next decision. Every route remains visible without relying on fragile tabs.
I am opening MIRENA for the first time
Recommended route
Start with Getting Started, Inputs, Workflow, and Outputs.
Begin with the asset that owns the first decision, then move through the hub only as the evidence and user state require.
Open the starting assetI have files but do not know which workflow fits
Recommended route
Use Source Context, Evidence Intake, and Workflow Routing.
Begin with the asset that owns the first decision, then move through the hub only as the evidence and user state require.
Open the starting assetI need a production prompt
Recommended route
Choose the prompt library for the exact planning or page job.
Begin with the asset that owns the first decision, then move through the hub only as the evidence and user state require.
Open the starting assetI need approval and release controls
Recommended route
Use Approval Flow and Publish Readiness.
Begin with the asset that owns the first decision, then move through the hub only as the evidence and user state require.
Open the starting assetBeginner through advanced
The journey grows from orientation into system governance.
The levels are not credentials. They describe the complexity of the decision, the amount of evidence required, and the number of connected assets that must be controlled.
Frame
Choose ownership, intent, scope, inputs, and the correct workflow.
Build
Create the map, brief, draft, format, link route, or implementation.
Refine
Audit overlap, gaps, weak answers, structure, proof, and performance.
Govern
Control approvals, ownership, maintenance, refresh, policy, and scale.
Visual semantics · Command deck
The interface mirrors the way the category is meant to be understood.
Command deck is more than decoration.
The visual system gives the category one stable mental model. The hero shows the category center, the route selector shows the current state, the journey rail shows progression, the complete index shows every owned asset, and the connected hub section shows where the work moves next.
Color carries stage and category meaning. Repeated card geometry signals comparable choices. Larger nodes indicate parent ownership. Lines, rings, grids, or layers express relationships, sequence, evidence, and handoff without asking the reader to decode a decorative illustration.
The copy follows the same grammar. Every block names the job, the input, the decision, the output, and the route. The result is a page that can orient a beginner without flattening the system for an experienced operator.
CenterDocs
EntryLearn what MIRENA needs and how the workflow is organised.
DepthGovern evidence, prompt execution, approval states, output quality, and handoff controls.
MetaphorCommand deck
Asset count19
Next routeEvidence decides
Complete child asset index
All 19 assets remain visible from the main node.
Search by title, task, stage, or concept. Filter by learning level without hiding the full category architecture from users or search systems.
MIRENA Page Types in Semantic SEO
Strengthen meaning, topical support, passage clarity, retrieval, and the relationships that help the asset read as one coherent answer.
Open the assetMIRENA Publish Readiness Checks
Control the release gate with visible evidence, blockers, owners, review needs, and a clear pass, revise, hold, or block state.
Open the assetMIRENA Approval Flow
Control the release gate with visible evidence, blockers, owners, review needs, and a clear pass, revise, hold, or block state.
Open the assetDrafting and Rewriting Workflow Prompts
Use this Docs asset to make a clearer decision, create the right output, and preserve evidence, ownership, and the next route.
Open the assetContent Brief Workflow Prompts
Turn approved site and page decisions into precise production instructions with evidence, formats, links, exclusions, and review.
Open the assetBehavioral Mapping and User Path Prompts
Shape page ownership, parent and child relationships, overlap controls, routes, dependencies, and build order.
Open the assetTopical Mapping and Site Architecture Prompts
Shape page ownership, parent and child relationships, overlap controls, routes, dependencies, and build order.
Open the assetWorkflow Routing and Module Selection Prompts
Use this Docs asset to make a clearer decision, create the right output, and preserve evidence, ownership, and the next route.
Open the assetEvidence Intake and Data Readiness Prompts
Control the release gate with visible evidence, blockers, owners, review needs, and a clear pass, revise, hold, or block state.
Open the assetSource Context, Project Control, and Guardrail Prompts
Use this Docs asset to make a clearer decision, create the right output, and preserve evidence, ownership, and the next route.
Open the assetInformation Gain Prompts
Use current search evidence to choose or review the visible answer form without promising a search presentation.
Open the assetRaw Semantic Discovery Prompts
Strengthen meaning, topical support, passage clarity, retrieval, and the relationships that help the asset read as one coherent answer.
Open the assetEntity SEO and Salience Prompts
Clarify identity, hierarchy, attributes, relationships, placement, support, ownership, and cross page consistency.
Open the assetGetting Started with MIRENA
Use the guided entry route to prepare the inputs, choose the first workflow, and avoid broad unstructured prompting.
Open the assetRewrite Outputs
Rebuild or update existing content through structure, intent, entities, proof, answer form, links, and controlled review.
Open the assetTopical Map Outputs
Shape page ownership, parent and child relationships, overlap controls, routes, dependencies, and build order.
Open the assetMIRENA Workflow
Use this Docs asset to make a clearer decision, create the right output, and preserve evidence, ownership, and the next route.
Open the assetMIRENA Outputs
Use this Docs asset to make a clearer decision, create the right output, and preserve evidence, ownership, and the next route.
Open the assetMIRENA Inputs
Use this Docs asset to make a clearer decision, create the right output, and preserve evidence, ownership, and the next route.
Open the assetOperator field guide
Read the command deck as a working system.
The visual metaphor creates a memory structure for the category. Each part of the model represents a decision the operator must make, not a decorative label.
Read the instruments
The command deck begins with the runbook, the incoming evidence, and the status of the current decision.
A beginner should be able to state the current job in one sentence before opening a deeper asset. That sentence becomes the reference point for scope, evidence, page ownership, and the next route.
Choose the runbook
Each control belongs to one workflow stage. Inputs, prompts, outputs, approvals, and handoffs should never share one ambiguous panel.
The edge marks the point where a related topic stops supporting the current job and needs another page, block, workflow, policy, or hold state. This boundary prevents the hub from becoming a catch all archive.
Execute the controlled step
A strong operator follows the instrument sequence rather than opening every control at once.
The route should make the next action obvious to a beginner while preserving the evidence, dependencies, exclusions, and review burden an advanced operator needs.
Record the handoff
The deck remains useful when failed gates, unresolved assumptions, release notes, and ownership changes return to the visible record.
A completed handoff records what was accepted, what remains uncertain, who owns the next action, which trigger reopens the decision, and when the system should be reviewed again.
Worked progression
The same hub supports five levels of decision maturity.
The route becomes more connected as the operator gains context. The advanced path does not replace the beginner path; it adds evidence, dependencies, ownership, review, and maintenance.
Start with MIRENA Page Types in Semantic SEO, MIRENA Publish Readiness Checks, MIRENA Approval Flow. The aim is to learn the category language, recognise the main asset roles, and avoid solving a structural problem with an unstructured content request.
Move into MIRENA Page Types in Semantic SEO, MIRENA Publish Readiness Checks, MIRENA Approval Flow. At this level the operator defines what belongs in the current asset, what belongs elsewhere, which inputs are approved, and which decision must be completed before production begins.
Use MIRENA Page Types in Semantic SEO, MIRENA Publish Readiness Checks, MIRENA Approval Flow. The practitioner produces a map, brief, block, rewrite, link route, answer form, schema graph, comparison, template, or policy action while keeping the approved boundary visible.
Review MIRENA Page Types in Semantic SEO, MIRENA Publish Readiness Checks, MIRENA Approval Flow. Advanced work separates symptoms from causes, keeps alternative explanations visible, ranks repair priorities, and avoids changing strong parts of the system without evidence.
Use MIRENA Page Types in Semantic SEO, MIRENA Publish Readiness Checks, MIRENA Approval Flow. Governance adds owners, approvals, versions, refresh triggers, exception rules, change records, measurement, and a safe route when the evidence no longer supports the existing model.
Why the main node exists
The hub holds the broad journey while child assets own focused depth.
The hub is a semantic and behavioral contract.
The parent node defines Docs, shows the complete branch system, and explains how the parts connect. It does not absorb every child lesson. The child assets earn their own URLs by owning a narrower reader task, decision, process, comparison, audit, template, policy, or production stage.
That split creates a cleaner journey. A beginner can understand the category without reading every guide. A practitioner can jump to the owned task without losing the parent context. An advanced operator can inspect dependencies, overlap, evidence, and governance without turning the hub into an unstructured knowledge dump.
The internal links follow the same model. The hub links down to every core child. Children link back to the hub. Close siblings link across when the reader has reached the point where the relationship becomes useful. Connected category hubs receive the work when the next job changes discipline.
Six rules protect the hub and ring.
- One parent topic. The H1, opening, route selector, journey, and index stay centered on Docs.
- Complete visibility. All 19 child assets remain accessible from the main node and are not hidden behind a shortened archive.
- Distinct ownership. Every child earns a focused job that the hub should not carry in full.
- Progressive depth. Beginner, guided, practitioner, advanced, and operator routes use the same system at different levels of decision complexity.
- Evidence before expansion. New pages, blocks, routes, claims, and policies require enough approved material and a clear owner.
- Maintenance after release. Live signals, product changes, platform changes, legal updates, and user feedback can reopen the model through a recorded review route.
Advanced operating controls
A complete hub is maintained as a system, not published as a one time archive.
Advanced use adds ownership, evidence, change records, review triggers, and route quality. These controls keep the category useful as the site, product, search environment, and user needs change.
Ownership
Every query, entity, page, block, link, policy, and output has one accountable home.
Evidence
Claims, examples, product facts, links, and search observations retain their source and confidence.
Boundary
Related work stays outside the asset when it changes the page job or exceeds the approved scope.
Approval
Pass, revise, hold, and block states remain visible through the production handoff.
Maintenance
Owners, dates, triggers, versions, and refresh actions keep the hub and child assets current.
Measurement
Live signals can support or challenge the plan, but one metric does not prove the cause.
Connected category hubs
Move across the operating system when the current category exposes the next job.
The connection is based on workflow dependency and user progression rather than topical similarity alone.
Use Cases
The Use Cases hub starts from the person, team, business model, asset, or problem and routes the work into the MIRENA lane that can produce the right site or page decision.
Open the Use Cases HubTopical Mapping
The Topical Mapping hub turns topics, URLs, queries, business goals, user states, and existing pages into a governed architecture with page roles, cluster homes, overlap controls, publishing order, and useful next routes.
Open the Topical Mapping HubContent Briefs
The Content Briefs hub turns approved site and page decisions into a writer ready operating plan with page job, intent, entities, section roles, evidence, answer formats, internal links, exclusions, and approval controls.
Open the Content Briefs HubDrafting and Rewriting
The Drafting and Rewriting hub diagnoses why an asset fails, protects the approved page job, selects the smallest repair boundary, rewrites only what needs to change, and returns reviewed copy with evidence and next routes.
Open the Drafting and Rewriting HubQuestions
Docs Hub questions.
Where should a beginner start?
Start with Getting Started, Inputs, Workflow, Outputs, and Page Types.
Does every job need the full prompt library?
No. The Docs hub routes the current task into the smallest useful workflow.
What happens before a prompt is run?
Source context and evidence readiness come first.
What happens after output is generated?
Review the output, unresolved assumptions, approval state, and next handoff before implementation.
Next route
Start with the current state, choose the owned asset, and move only when the evidence supports the next stage.
MIRENA connects the category decision to source context, planning, production, review, internal routes, and the final handoff. The hub remains the main node as the category grows.
Founder access is €20 for each 30 day subscription period excluding VAT, with one seat and one active MIRENA instance. OpenAI account rules, plan charges, model access, availability, and usage limits remain separate.