The top-level architecture diagram presents the platform's major tiers and runtime call direction. Its source artifacts are:

• docs/diagrams/architecture.svg — SVG embedded in the project root README.md and viewable standalone.
• docs/diagrams/architecture.html — standalone HTML page containing the same inline SVG plus summary cards and a footer.

The HTML/SVG masters are hand-authored rather than generated from manifests. Edit both with the architecture-diagram agent skill (it is not shipped in this repository) and keep their SVG elements byte-equivalent. Render the committed PNGs (docs/diagrams/img/) before you build and check the generated surfaces:

uv run --project bootstrapper python -m scripts.docs.render_diagrams
make docs-build
make docs-check

The PNG renderer exports at 3600 pixels wide and preserves each SVG's aspect ratio. The documentation gate rejects master drift and stale derived assets.

Each services/<name>/architecture.{svg,html} is auto-generated from that service's manifest (service.yml::data_flow.calls) by bootstrapper/docs/regen.py:

PYTHONPATH=bootstrapper uv run --project bootstrapper python -m bootstrapper.docs.regen <service>   # one service
PYTHONPATH=bootstrapper uv run --project bootstrapper python -m bootstrapper.docs.regen --all       # all services

The drift gate (bootstrapper/tests/test_docs_drift.py) enforces that the committed per-service SVG / HTML / README-deps-section match what the generator would emit.

A changed service diagram also needs its PNG, docs/diagrams/img/service-<name>.png, re-rendered. render_diagrams re-renders every missing or stale PNG. Run it (or make docs-build) before make docs-check, which fails on a stale PNG:

uv run --project bootstrapper python -m scripts.docs.render_diagrams

Per-service diagrams are rendered by bootstrapper/docs/diagram_renderer.py. Edit that file to change the rendered shape; manifest field changes alone regenerate the content without a renderer edit.