Pick a job type to see how the operating system routes work. The point is not maximum complexity. The point is clean ownership, fewer collisions, and a clear verification path.
Entry
ColtStarts the request, gives the target, and sets the outcome.
CLEOHandles the front door, decides whether the work stays local or gets pushed to the VPS lane.
Routing
AtlasCoordinates the VPS side, makes sure the right profile owns the job, and keeps shared admin tasks from bleeding into project lanes.
DevImplementation, test runs, engineering fixes, and deployment support.
Lil BeaverHandy Beaver operations, customer-facing support, and always-on VPS tasks.
BigfootKBC discovery, workflows, drafts, and approval-style automation.
LanceFreelance proposals, account ops, scopes, and client-ready language.
Execution and proof
GitHub + repo docsNon-secret instructions, branch history, workflow runs, and the durable audit trail.
R2 / Worker / site surfaceExecution lands on the actual platform surface when the task touches publishing or production output.
VerificationSmoke checks, tests, health checks, and a final brief back to the human.