---
id: architecture-example
title: Example: publishing architecture
description: A compact overview of how versioned sources become editorial output and agent-readable contracts.
type: architecture
status: observed
visibility: public
tags: architecture, diagrams, example
related: home, content-model, agent-interface, large-canvas
source_refs: diagrams/documentation-map.json, ../../core/build.mjs
diagram: documentation-map
---

## A bounded architecture view

This example uses the full architecture budget: nine nodes, three zones, and ten relationships. The primary flow reads left to right; vertical connections show dependencies inside each layer.

> **Diagram: Aurelius publishing architecture**
> Three zones show how versioned Markdown, diagrams, and metadata pass through renderers and indexes to become a site, accessible SVG, and structured agent interfaces.
> Semantic source: `diagrams/documentation-map.json`

Use “View full diagram” below the figure to inspect it without article-width constraints. Use “Copy SVG” to reuse the accessible vector output. For a much larger process, use a Canvas instead of overloading the architecture view.

## When the map needs to be much larger

The [large Canvas example](doc:large-canvas) spans five phases and 24 steps. It demonstrates the navigation surface intended for flows comparable to a complete business process.