Topical Mapping · Documentation architecture
How MIRENA plans documentation as a connected cluster, not a loose folder.
Give MIRENA the product workflows, current docs, inputs, outputs, setup steps, roles, approvals, support paths, and use cases. MIRENA assigns doc families, page roles, naming, hierarchy, sibling routes, and product bridges.
MIRENA internal workflow
Static decision model
Human approval required
No ranking guarantee
Planning problem
A docs cluster organizes product understanding, setup, inputs, outputs, workflows, approvals, roles, support, and next routes under one clear documentation hub.
The job is structural. MIRENA reviews ownership, intent, role, evidence, dependencies, routes, user progression, and downstream production before a decision is accepted.
Docs become a side folder
Pages are added without a parent model, stable naming, or route logic.
Docs duplicate product and use cases
A setup or output page starts explaining the whole product or job.
Readers get the answer but lose the path
The page does not connect to the next doc, product, support, or use case.
Boundary: MIRENA keeps product understanding, workflow documentation, support, use cases, and commercial pages connected but distinct. A docs page should not absorb the full product or marketing role.
How MIRENA handles the work
The internal process moves from evidence into governed page and route decisions.
Define the docs job
Write what the docs area must help readers find, understand, complete, or verify.
Inventory doc families
Group setup, inputs, outputs, workflows, approvals, roles, fields, support, and examples.
Define the docs hub
Give the area one parent page and grouped routes.
Assign page roles and names
Use stable labels that match the task and avoid duplicate doc paths.
Set hierarchy and dependencies
Order setup, input, workflow, output, approval, and support pages.
Separate adjacent lanes
Clarify docs versus support, use case, product, and educational content.
Map internal routes
Connect parent, sibling, next step, product, use case, and support pages.
Assign maintenance ownership
Record owner, update trigger, approval state, and next review.
Decision record
MIRENA keeps the important fields visible through the handoff.
Doc family
Setup, input, output, workflow, approval, role, field, example, or support.
Page job
Find, explain, prepare, complete, verify, troubleshoot, or continue.
Parent and sibling
The docs hub and closest related pages.
Dependency
The earlier doc or approved concept needed first.
Product bridge
The use case, product, pricing, or support route.
Maintenance state
Current, revise, hold, archive, or replace.
Illustrative output
The record shows what MIRENA decided and where the work moves next.
The example shows structure only. It is not a client result, live audit, ranking claim, or automatic implementation.
- Docs familyInputs
- Page jobExplain what evidence MIRENA can accept
- ParentDocs
- Sibling routesOutputs, workflows, approvals
- Next routeMatching use case and product access
Review states
MIRENA returns an owned decision instead of an unqualified recommendation.
The doc has one job, one home, stable naming, and useful routes.
The content fits but the hierarchy or next step is weak.
The product behavior or approval state is unclear.
The proposed doc duplicates a use case, product page, or existing doc.
Connected workflow
The work moves into the next page that owns the decision.
Navigational Cluster Planning
Place docs inside the known destination system.
Open the routeUse Case Led Architecture
Connect how it works to the job it solves.
Open the routeTemplates and Examples Planning
Add reusable and illustrative support.
Open the routeSite Architecture for Semantic SEO
Place docs inside the wider site model.
Open the routeMIRENA Docs
Use the current documentation parent.
Open the routeContent Briefs
Turn doc roles into page instructions.
Open the routeQuestions
Docs Cluster Planning for SEO questions.
What is a docs cluster?
It is a structured group of documentation pages built around product understanding, setup, inputs, outputs, workflows, approvals, and support paths.
How are docs different from use case pages?
Docs explain how the system works. Use case pages explain what job the workflow solves.
How are docs different from support pages?
Docs focus on product understanding and operation. Support pages handle troubleshooting, account, billing, or service needs.
What does MIRENA return?
MIRENA returns the docs hierarchy, page roles, naming, dependencies, internal routes, product bridges, and maintenance states.
What follows docs planning?
Approved docs pages enter content briefs, examples, templates, product links, support routes, and maintenance governance.
Next route
Give MIRENA the source context and working evidence. MIRENA returns the governed handoff.
The current Founder plan includes one seat and one active MIRENA instance for 30 days at €20 excluding VAT. OpenAI account rules and usage limits remain separate.
MIRENA output requires factual, editorial, legal, technical, and business review before publication or implementation.