How to use these docs

This site documents the PatternYard platform as a system, not any single repo. It exists because the platform spans roughly twenty repositories and seven deployed projects, and no individual README captures how they connect.

How it is organized

• Architecture — how the system is built: the projects, the domains, the data and storage model, and the editor login bridge.
• Operations — how to work on it: the two deploy loops and the deployment runbook with its known gotchas.
• Reference — flat lookup tables: the repository inventory and the environment variable map.

Diagrams are code

Every diagram on this site is authored as D2 text inside the page that uses it — there are no binary image files to fall out of sync. To change a diagram, edit its fenced d2 block and rebuild; the SVG regenerates. This is deliberate: the architecture changes, and a diagram you cannot diff is a diagram that goes stale.

Keeping it current

Treat these pages like code. When you change how services connect — a new subdomain, a new cross-service call, a moved responsibility — update the relevant page in the same change set. The reference tables in particular are meant to be authoritative; if they drift, they are worse than nothing.

Note

This is documentation, not a live dashboard. It describes intended structure and the verified state at the time of writing. For live status, check the Vercel dashboard and the actual deployments.