Architecture · LikeC4
coding-agent-workflows
Renders one neutral source layer into a native practices bundle per coding agent, and installs it into consuming projects
The whole picture
System landscape
The system in context, then opened up into its containers.
coding-agent-workflows — system landscape
index
coding-agent-workflows — containers (source → build → targets → install)
cawSystemRenders one neutral source layer into a native practices bundle per coding agent, and installs it into consuming projects
Risks & open questions
risks
Planned & in-flight work
plannedInside each box
Containers & components
Each part decomposed into the components that implement it. Every box links to its source in the interactive explorer.
source/ — authored bundle (the only hand-edited layer)
sourceContainerThe single source of truth: rules, agent roles, skills, workflows, templates, and the scope manifest. Everything else is generated from here
build/ — renderer + staleness & release gates
buildContainerMechanism only (IO + template substitution, no content decisions): turns source/ into targets/ and AGENTS files, then gates the rendered output
targets/ + AGENTS — rendered per-agent output
targetsContainerPre-rendered and committed; no build step before use. The artifacts install.sh copies into a consuming project
scripts/fleet/ — machine-level conformance track
fleetContainerA separate machine-level track (install.sh fleet): passively register every repo and scan it for guardrails/testing/observability conformance
How it runs
Walkthrough flows
Dynamic views — the narrative spine of the system, step by step.
Walkthrough — render source/ into every target
buildFlowMechanism only: render reads the scope manifest, resets targets/, and emits the thin AGENTS.md index, the full AGENTS.full.md bundle, and the native Claude + Codex layouts — injecting the generated rule catalog into the Claude coding-practices skill so it can never drift.
Walkthrough — staleness + release gates
releaseFlowThe repo`s one mechanical invariant: committed output must match a fresh render of source/, and must carry no absolute paths, PII, or internal jargon. CI and the pre-commit hook both run these; a failed staleness check restores the committed snapshot so it never leaves rendered changes behind.
Walkthrough — install into a project and consume it
installFlowA plain file copy — no hooks, no daemons. The consumer picks its agent`s layout; the agent then auto-loads the thin index and reads only the section a task needs, keeping always-loaded context small.
Where it runs
Deployment
What runs where, and the process & data boundaries between the pieces.
Deployment — where each piece runs
deploymentExplore it live
The figures above are static exports. The interactive explorer lets you pan, zoom, follow relationships, and jump from any box to the source.