Architecture Documents

Architecture Documents are canonical, reusable documents owned by a project version. Open Documentation → Documents.

Unlike older View-owned custom pages, an Architecture Document can stand on its own and be referenced from multiple Architecture Views without duplicating its content.

Document Library

Use the library to:

• Create top-level documents and nested subpages
• Search by title or content context
• Reorder documents and move them within the hierarchy
• Discuss a selected document with Archie
• Delete a document from the project version

Deleting a document removes its references from every View. It does not delete the architecture resources embedded in the document.

Block Editor

Documents are assembled from ordered blocks. Use text-oriented blocks for narrative, code, callouts, and section separation. Resource blocks can render live project evidence such as:

• Architecture Views
• Workflows and Deployments
• Systems and Relationships
• Capability Map and Behavior Model
• Data Model and Context Map
• Explorer, Complexity, Coupling, and Blast Radius evidence

Prefer a live reference when the document should track the selected version. Use a pinned snapshot when the evidence must remain tied to a specific review result.

Reference Documents From Views

Open a View's documentation area and choose which Architecture Documents belong in that published experience. The View stores references to the canonical documents; editing the document updates every live reference to it.

This works well for material reused across audiences, such as security posture, integration conventions, operational readiness, or a domain overview.

Versioning And Permissions

Documents are version-scoped and participate in version cloning, comparison, and merge. A read-only version can render documents but cannot author, reorder, move, or delete them.

Choosing The Right Surface