Architecture
Every subagent*.com site, and the real dependencies between them: which sites fetch which primitive's API at request time, and which primitives reference each other by id. This is not a diagram drawn separately from the code — every edge below corresponds to an actual fetch() call or foreign-key-style reference verified in this repository's source.
Drag nodes to rearrange — positions save to this browser automatically.
Reading the graph
Legacy sites (jobs/data/workers/db/etl) and the two docs mirrors (cowork/coworkers) sit outside the primitive cluster because they consume it but do not extend its schema. The nine D1-backed primitives sit in the middle; tasks-to-contracts, outcomes-to-rubrics, evaluations-to-rubrics, and evaluations-to-outcomes are real foreign-key-style id references, not just navigation links. api.com and cli.com fan out to all nine because that is literally what a catalog and a CLI do — query every primitive's API.