One operator, one coordinator, a directed team.
Bishop is the system that runs the work. He is Jeremiah’s own, designed and built by him, and the closest thing he has to a senior partner. What follows is the shape of the system and exactly how it is governed. Nothing here is hidden, because the discipline is the whole point and there is no smoke to clear.
The specialists are described by what they do, not by name. The roster changes over time. The structure holds. One operator sets the bounds, one coordinator directs the team, and the team does the work.
Always pause, never delete.
When the system is unsure, it stops and asks. It does not act past its bounds, and it never destroys. Data is preserved by default, nothing is removed without an explicit, logged decision, and the safe choice is the only default it has. Everything below is how that principle is held in place.
Security hardening
The pieces that must not change are made unchangeable. Critical configuration and the agents’ own operating files are locked at the filesystem level, so a stray process, a mistake, or a bad instruction cannot rewrite them. Defenses against prompt injection are built in, not bolted on: attempts to talk an agent past its instructions are caught before they reach the work.
Approval gateway
Every action an agent can take passes through one gateway. What it may do on its own is set by an explicit allowlist, deliberately broad, and anything not on it routes to a person before it runs. This is where the approval tiers are enforced: routine work inside approved bounds runs on its own, anything with a real consequence stops at a gate.
Agentic security
One agent’s only job is to watch the others. It reviews what the team is doing against what normal looks like and surfaces the outliers, the actions that do not fit the pattern, straight to the operator. A second set of eyes that never tires, sitting outside the work it checks.
Bishop did not start from scratch, and that is the honest version. He began as an OpenClaw agent, then was forked and rebuilt with a set of operator enhancements specific to how this work runs. Later he was hybridized with Hermes, which gave him self-improvement protocols and a far better memory: he holds useful context across sessions and gets sharper at the work over time, rather than starting cold each day. He is still changing. What he is today is a snapshot, not a finished thing, and showing the lineage is the point: no magic, just a system built deliberately, in the open, and still being built.
This site is maintained by Bishop.
Jeremiah designed and hand-built it, and Bishop and his specialist team keep it running. The build is the operator’s. The operation is the system’s. The same system deployed for clients is the one running this page, which makes the argument hard to overstate, because it is not being made in words. It is simply on.