Orient
Learn the language, page roles, evidence rules, and first route.
Main category hub · Modular toolkit
Move through Templates from first principles to governed practice.
The Templates hub provides working records that preserve source context, page ownership, entities, briefs, rewrite actions, internal routes, review states, and handoffs across the MIRENA workflow.
The hub is the main node for 6 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.
6 complete assets
5 learning levels
5 entry states
One main category node
Beginner route
Choose the smallest template that matches the current stage.
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
Standardise fields, owners, approvals, versioning, reuse, and transfer across teams and large projects.
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 preparing the project
Recommended route
Start with the Source Context Template.
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 am planning the site
Recommended route
Use the Processed Topical Map Template.
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 am planning page meaning
Recommended route
Use the Entity Map Template.
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 am preparing a new page
Recommended route
Use the Content Brief Template.
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 am repairing an existing page
Recommended route
Use the Rewrite Brief and Internal Link Map Templates.
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 · Modular toolkit
The interface mirrors the way the category is meant to be understood.
Modular toolkit 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.
CenterTemplates
EntryChoose the smallest template that matches the current stage.
DepthStandardise fields, owners, approvals, versioning, reuse, and transfer across teams and large projects.
MetaphorModular toolkit
Asset count6
Next routeEvidence decides
Complete child asset index
All 6 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.
Internal Link Map Template
Use a reusable working record that carries approved fields, ownership, evidence, review state, and the next handoff.
Open the assetRewrite Brief Template
Use a reusable working record that carries approved fields, ownership, evidence, review state, and the next handoff.
Open the assetContent Brief Template
Use a reusable working record that carries approved fields, ownership, evidence, review state, and the next handoff.
Open the assetEntity Map Template
Use a reusable working record that carries approved fields, ownership, evidence, review state, and the next handoff.
Open the assetProcessed Topical Map Template
Use a reusable working record that carries approved fields, ownership, evidence, review state, and the next handoff.
Open the assetSource Context Template
Use a reusable working record that carries approved fields, ownership, evidence, review state, and the next handoff.
Open the assetOperator field guide
Read the modular toolkit 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.
Select the module
The modular toolkit begins with the workflow stage and the exact record that needs to survive the handoff.
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.
Prepare the inputs
Fields are included when they change ownership, evidence, scope, priority, build, review, or route decisions.
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.
Assemble the record
Templates turn repeatable work into visible contracts without replacing the judgement needed to fill them accurately.
The route should make the next action obvious to a beginner while preserving the evidence, dependencies, exclusions, and review burden an advanced operator needs.
Inspect the handoff
Versions, owners, source context, approvals, examples, and change records keep the modules useful across teams and projects.
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 Internal Link Map Template, Rewrite Brief Template, Content Brief Template. 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 Internal Link Map Template, Rewrite Brief Template, Content Brief Template. 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 Internal Link Map Template, Rewrite Brief Template, Content Brief Template. 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 Internal Link Map Template, Rewrite Brief Template, Content Brief Template. Advanced work separates symptoms from causes, keeps alternative explanations visible, ranks repair priorities, and avoids changing strong parts of the system without evidence.
Use Internal Link Map Template, Rewrite Brief Template, Content Brief Template. 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 Templates, 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 Templates.
- Complete visibility. All 6 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.
Docs
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.
Open the Docs 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 HubInternal Linking
The Internal Linking hub connects pages by meaning, page role, journey stage, proof need, support need, and next useful action rather than by loose keyword mention.
Open the Internal Linking HubQuestions
Templates Hub questions.
Can the templates be copied?
Yes. Use the visible copy action or select the template text when clipboard access is unavailable.
Do templates replace MIRENA workflows?
No. They carry approved decisions and make handoffs consistent.
Should every field be filled?
Required fields should be complete. Optional fields are used when they change a decision or route.
How are templates maintained?
Keep an owner, version, date, source context, approval state, and change record.
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.