GUTS externalizes what an organization actually is: how it coordinates,
remembers, decides, and executes. For two generations it was a
diagram. Now it has a body: an always-on Linux box, tmux sessions as
persistent worker bodies, a private Tailscale network, and a built browser
Bridge with a lock screen, in daily use from a phone.
Built
GUTS Bridge
Browser control surface over tmux: lock screen, session tabs, dashboard cards, agent-stopped detection, one-tap defaults replay. 40 tests passing; in daily use from the phone.
In the field
GIMS
The institutional ledger, deployed as a working lab system in a regulated environment, with a commercial compliance derivative in a pharma pilot.
Next
The event spine
MVP 2: every Bridge and session action leaves a GIMS sentence. Session ledger, work claims, message records. Memory before autonomy.
A private factory on one always-on machine, where tmux provides persistent
worker bodies, the Bridge gives the human a window and a lock,
GIMS writes every action into institutional memory, GONS
runs the floor and briefs the owner, GEDS prepares relevance and anomaly
handoffs for higher reasoning, and GOMS turns general goals into executable
campaigns and sprints. One layer is built, one is in the field, the rest are designed
and ordered.
In a GUTS-native world
The shifts that compound
These are not present-tense claims for every row: the stack earns them one MVP rung at a
time. The first shift is already physical. The rest are what the ledger, the foreman, and
the relevance engine are being built to compound.
From
A remote terminal trick: a phone reaching a laptop through a private tunnel
→
To
A physical runtime for organizational cognition
From
Memory decays when people leave, projects pause, or context is lost
→
To
Organizational memory compounds instead of decaying
From
Decomposition is human labor — translating intent into tickets is the bottleneck
→
To
Decomposition becomes computational
From
Continuity dies in the gap between sessions, sprints, and interruptions
→
To
Continuity of intent survives interruption and time
From
Operational exhaust — events, logs, outcomes — is discarded
→
To
Operational exhaust becomes inference substrate
From
Ambiguity stalls until a human notices and routes it
→
To
Ambiguity becomes computationally routable
From
Org structure is brittle — bound to managerial memory and tribal knowledge
→
To
Org structure becomes dynamically reconfigurable
From
Humans are stuck as continuous drivers, routers, status-relayers
→
To
Humans elevated to high-value intervention points
From
Unknown unknowns stay unknown — sensors have blind spots
→
To
Latent structure surfaces through relevance inference over events, tensions, and anomalies
The Anatomy
The organs, in dependency order
One is built, one is in the field, three are designed, three are deliberately deferred.
They are not peers in a ring: they are layers of a stack, and every one of them reads and
writes the same ledger. Deep pages carry the full argument for each.
The most common mistake when reading this stack is to imagine a linear flow: GOMS feeds
GONS feeds GEDS feeds execution. The actual design has one center of gravity, and it is
not a tool. It is the ledger.
The wrong picture — a pipeline of tools
A pipeline of tools has no memory of itself. Each stage holds its own state, a stalled
stage blocks the floor, and reconstructing what happened means archaeology across six
tools. That is coordination overhead rebuilt, not removed.
The right picture — one ledger, routed, gated
The design: every organ reads and writes one append-only ledger.
Agents never inject into each other's terminals; a question becomes a GIMS record, GONS
routes it to whoever can answer, and the reply returns the same way, attributable and
replayable. The human holds the gate on anything dangerous. tmux is the last-mile
display, not the source of truth.
Not workflow automation: a factory designed so its memory of itself is complete. One ledger every
organ will read and write, a foreman that will route every question through it, and a human at
the gate. Absence becomes computable: a heartbeat that should exist and does not is
itself a signal.
In the Field
GIMS — deployed across two domains
Architectural claims are only as good as their implementations. GIMS has been deployed in
two distinct regulated contexts, producing two different products from the same underlying
grammar. Both cases are the noun-verb-ledger abstraction applied to a specific operational
problem. MVP 2 brings the same grammar home: the factory's own actions become GIMS sentences.
The GUTS architecture did not emerge from a whiteboard. It emerged from eight years
of regulated-industry fieldwork: cleanrooms, LIMS implementations, seven regulatory
jurisdictions, and a consistent discovery: the honest answer to "what work simply must
be done?" is almost always smaller than what currently exists.
The ladder is MVP 0 through 7, and each rung must be boring, useful, and observable
before the next one starts. Two rungs are done: the runtime and the Bridge. The event
spine is next. The numbers below are the honest ones.
MVP Rungs Complete
2 / 8
MVP 0 runtime · MVP 1 the Bridge
Tests Passing on the Bridge
40
unit + real-tmux integration, isolated sockets
Organs in the Field
1
GIMS + Compliance Relay — pharma pilot
Deferred by Design
3
GEMS · GAMS · GRAMS — later layers
The full rung-by-rung ladder, with a done-when sentence for each MVP, lives on
the blueprint.