Repository navigation
Architecture Authoring
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 rootREADME.mdand 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-checkThe 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 servicesThe 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_diagramsPer-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.
Atlas documentation.
- 1. Overview
- 2. Quick Start
- 3. Core Concepts
- 4. Tracks
-
5. Services
- 5.1. Service Catalog
-
5.2. Service Guides
- 5.2.1. airflow
- 5.2.2. asset-baker
- 5.2.3. asset-worker
- 5.2.4. backend
- 5.2.5. backup
- 5.2.6. blender-mcp
- 5.2.7. celery
- 5.2.8. chatterbox
- 5.2.9. cloud-providers
- 5.2.10. cloudflared
- 5.2.11. comfyui
- 5.2.12. crawl4ai
- 5.2.13. doc-processor
- 5.2.14. docling
- 5.2.15. docling-lightrag-adapter
- 5.2.16. fal
- 5.2.17. globals
- 5.2.18. grafana
- 5.2.19. hermes
- 5.2.20. iceberg-rest
- 5.2.21. jenkins
- 5.2.22. jupyterhub
- 5.2.23. kong
- 5.2.24. label-studio
- 5.2.25. langfuse
- 5.2.26. lightrag
- 5.2.27. litellm
- 5.2.28. llm-graph-builder
- 5.2.29. local-deep-researcher
- 5.2.30. loki
- 5.2.31. mcp-servers
- 5.2.32. minio
- 5.2.33. mlflow
- 5.2.34. multi2vec-clip
- 5.2.35. n8n
- 5.2.36. neo4j
- 5.2.37. ollama
- 5.2.38. open-webui
- 5.2.39. openclaw
- 5.2.40. otel-collector
- 5.2.41. parakeet
- 5.2.42. prometheus
- 5.2.43. ray
- 5.2.44. redis
- 5.2.45. redpanda
- 5.2.46. searxng
- 5.2.47. spark
- 5.2.48. speaches
- 5.2.49. stt-provider
- 5.2.50. supabase
- 5.2.51. supavisor
- 5.2.52. tei-reranker
- 5.2.53. tempo
- 5.2.54. tika
- 5.2.55. trino
- 5.2.56. trueforge
- 5.2.57. tts-provider
- 5.2.58. verba
- 5.2.59. vllm-metal
- 5.2.60. weaviate
- 5.2.61. zeppelin
- 5.3. Provider And Extension Guides
- 6. Configuration
- 7. Operations
- 8. Architecture
- 9. Development
- 10. Reference