Bishop
One operator, one coordinator, a directed team.
Bishop is the system that runs the work — Jeremiah’s own, designed and built by him, his senior partner. Here is its shape and exactly how it is governed, shown plainly. The discipline is the point, and there is no smoke to hide.
Structure
The specialists are described by what they do, not by name — the roster changes; the structure holds. One operator sets the bounds, one coordinator directs the team, the team does the work.
How it is governed
The principle
Always pause, never delete.
When the system is unsure, it stops and asks. It does not act past its bounds, and it does not destroy. Data is preserved by default — nothing is removed without an explicit, logged decision. The safe default is the only default.
Approval tiers
A decision, in the open
It ran autonomously on its own development for 3+ weeks, then was deliberately disabled — Jeremiah and Bishop had converged on the same projects closely enough to collide. A coordination decision between two operators working the same ground: temporary, deliberate, to be re-enabled once their lanes separate. The system operates even on its own engineering — and the operator knows when to pull it back.
This site is maintained by Bishop.
Jeremiah designed and hand-built it; Bishop and his specialist team maintain it. The build is the operator’s, the operation is the system’s — the same system deployed for clients runs this site. The whole argument, shown instead of claimed.