Aureliusstatic documentation
Repository
⌘ K

architecture · observed

Example: publishing architecture

A compact overview of how versioned sources become editorial output and agent-readable contracts.

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.

ARCHITECTURE

100%
Aurelius publishing architectureThree zones show how versioned Markdown, diagrams, and metadata pass through renderers and indexes to become a site, accessible SVG, and structured agent interfaces.VERSIONED SOURCEBUILD AND PROJECTIONPUBLISHED READINGRENDERPUBLISHCOMPOSEEMBEDINDEXEXPOSEINCLUDEDESCRIBEINCLUDEDESCRIBEMarkdownCONTENTMarkdownpages and decisionsSemantic JSONDIAGRAMSSemantic JSONzones and relationshipsRelations and sourcesMETADATARelations and sourcesIDs and traceabilityEditorial rendererHTMLEditorial rendereraccessible structureDiagram rendererSVGDiagram rendererorthogonal layoutIndex and graphINDEXIndex and graphsearch and relationsHuman readingSITEHuman readingstatic HTMLAccessible diagramSVGAccessible diagramcopy and printAPI and corpusAGENTSAPI and corpusJSON and llms.txtLEGENDINPUTCORESERVICESTOREOPTIONAL
Semantic source: diagrams/documentation-map.jsonView full diagram

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 spans five phases and 24 steps. It demonstrates the navigation surface intended for flows comparable to a complete business process.