THE ZERO-PERSON IT DEPARTMENT?Build a town.
Build a town.
Not a pile of robots.
Explore one opinionated architecture, compare every steering wheel, price the stack—and see exactly where humans are still constitutionally required.
Our answerAutomate the work. Keep human accountability. Minimize control planes.
♙People, identity & devicesKeys and school desks⇆Edge, access & networkRoads and gates⚙Source & software factoryWorkshop and loading dock▦Platform & deliveryStandard roads and buildings≈Data & contextReservoir, library and receipts⌁Observe, support & repairNerves, hospital and fire station↺Security, recovery & auditLocks, spare keys and court records⚖CONTROL GRAPHone authority per field
01
THE OPINIONATED ANSWER
AWS underneath. EKS as the paved road. PostgreSQL by default—not for everything.
Buyworkplace, edge and vendor support
Owncontracts, templates, evidence and recovery
Opendelivery, data context and observability protocols
Refuseoverlapping writers and magical RCA
FOLLOW ONE THING
Watch the department think.
Choose an event. Every bead is a different authority; no agent silently jumps the gate.
1Request→
2Contract→
3Agent worker→
4Independent CI→
5Signed artifact→
6Canary→
7Business probe→
8Evidence
The lesson: autonomy lives in the arrows. A tool can be excellent inside one box and still fail the department.
Walk through the eight-layer department.
Open blueprint →⇄Why this tool, not that one?Switch options and compare hard trade-offs.
Open comparison lab →$What does greenfield cost?Move the employee and engineer sliders.
Open cost model →⚠What is still uncovered?See every human and commercial gap.
Open gap map →18technology organs
150+named systems and components
301evidence records
72open disconfirmation queries
32NVIDIA GitHub organizations
13completed research passes