Generating View Documentation
Create and refine architecture documentation from versioned project evidence
This guide creates documentation for one Architecture View. Use Architecture Documents when the narrative should be canonical and reusable across Views.
Prepare The Evidence
Before generating:
- Confirm the active architecture version.
- Give important Systems and Relationships meaningful descriptions.
- Map at least one relevant Workflow.
- Add Data Model, Behavior, Capability, Deployment, or Context evidence when the topic depends on it.
- Record accepted goals, constraints, decisions, and risks in the Architecture Handbook.
- Approve only trustworthy Project Knowledge memories and insights.
1. Open The View
Go to Documentation → Views, choose the intended View, and open its documentation area. Confirm that the View contains the elements needed for its audience and question.
2. Select Supporting Content
Choose the Workflows and Deployments that belong in this View. Add references to existing Architecture Documents rather than copying reusable content.
3. Configure Generation
Choose Generate Documentation and complete the three stages:
- Content Type — full overview or a focused section
- Customize — audience, technical level, business metrics, visual references, and focus areas
- Generate — verify the choices and start generation
Generate a focused section when most of the document has already been reviewed.
4. Review The Draft
Check every factual statement against the model and source evidence. Pay particular attention to inferred ownership, synchronous versus asynchronous interaction, risk severity, data flow, and runtime behavior.
Edit the Markdown directly and add material that the model cannot infer, such as operational responsibility, regulatory boundaries, rollout constraints, or deliberately rejected alternatives.
5. Regenerate Selectively
When a section is weak:
- Correct the underlying model or Project Knowledge evidence.
- Regenerate only the affected section.
- Preserve reviewed hand-written material elsewhere.
Treat generation as a feedback loop for model quality, not a one-time export.
6. Preview And Publish
Preview the complete reader experience, select only relevant sections, choose public or private access, set a preset preview theme and expiration, and publish. Create a guest link separately when a private publication needs external readers.