Public: anyone can read this; nobody can change it.
docs: architecture diagrams as code (reference + Azure); wiki built around them #303
Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.
Two diagrams for clients, the wiki and the site, generated from `docs/architecture/` on one engine (`lib.ts`) with a collision check: no line crosses a box or label, no label overlaps another, no text outgrows its box.
shipped merged
Sign in to join this conversation.
Two diagrams for clients, the wiki and the site, generated from
docs/architecture/on one engine (lib.ts) with a collision check: no line crosses a box or label, no label overlaps another, no text outgrows its box.diagram.ts→wiki/open-platform-architecture*.svg): the platform on any Kubernetes; traffic, contribution, identity and integration flows; the model provider as a role; apps marked portable (repo + image + chart run on any cluster).azure.ts→wiki/open-platform-azure*.svg): whatdeploy/azure/main.bicepprovisions in aks mode, the federated identities, the operator's steps in order, pilot hardening, and the vms mode strip.Light and dark SVGs live in
wiki/so they publish with the pages and ship in the seed; PNG (2×) and vector PDF indocs/architecture/for email and review packs.The wiki is rebuilt around the reference picture:
Architectureopens with it and follows its zones and numbered flows; Home, Security Model, Platform Internals, CI and Builds, Preview Environments and Grow Your Own Platform point at the diagrams in their vocabulary;deploy/azure/README.mdembeds the Azure view; the README embeds the reference.Every string on both diagrams was checked against the wiki, the app template, the production edge manifests and the Bicep;
docs/architecture/README.mdmaps each claim to its source and lists what the diagrams deliberately do not claim.🤖 Generated with Claude Code