View Documentation

Each Architecture View can become an audience-specific documentation experience. Open Documentation → Views, select a View, and open its documentation area.

Evidence Used For Generation

Generation can draw from the selected version's:

• Systems, hierarchy, and Relationships
• Data Model ownership and usage
• Workflows and Behavior Model
• Capability Map and Context Map
• Deployments
• Architecture Handbook
• Project Knowledge and accepted Decisions
• The current View and its selected supporting content

Better evidence produces better drafts. Generation does not make incomplete or contradictory model data authoritative.

Generate Content

The generation flow lets you choose a complete overview or a specific section, then configure audience, technical depth, business emphasis, visual references, and focus areas.

Review the final configuration before starting. Broad generation can consume more time and AI usage than regenerating one focused section.

Edit And Assemble

• Edit generated sections in Markdown.
• Regenerate a weak section without replacing reviewed content elsewhere.
• Add project-specific caveats, ownership, and operational detail.
• Manage supporting images.
• Select the Workflows and Deployments relevant to this View.
• Reference canonical Architecture Documents rather than copying reusable material.

Resource Sections

The reader experience can include Systems, Relationships, Data Model, Context Map, Capability Map, Behavior Model, Coupling, Complexity, Blast Radius, Workflows, Deployments, Architecture Handbook, and selected Architecture Documents.

Choose sections for the audience. A security review and an executive overview should not publish the same evidence merely because it exists.

Publish

Publishing records a selected set of sections, title, description, visibility, preset preview theme, expiration, and publication version. Private publications use separately managed guest share links.