Skip to content
WATCHBILL from Blue Jacket
How it works

A watch is a bounded assignment

One agent, one station, one supervising human, one window. Watchbill™ is the discipline around that unit: how it is assigned, how it is gated, how it is turned over, and what it leaves behind.

Where the instrument comes from

Five properties, and each one maps onto the product

In the Navy, the watch bill is the instrument by which a ship’s company is assigned to duty. It is not a metaphor we chose for its atmosphere. It is a hundred‑year‑old answer to the problem of who is responsible for what, right now.

01

No unmanned station

The watchbill exists so that every station that matters has a name against it. If a station is unmanned, the bill shows it before the sea does.

02

Qualification precedes assignment

A sailor stands only the watch they are qualified for. Assignment is not trust. It is a recorded qualification against a defined station.

03

Authority is delegated. Accountability is not.

The captain sleeps while the officer of the deck holds the watch, because the watchbill makes the delegation explicit, bounded, and revocable.

04

Relief is a procedure, not a moment

A watch is turned over. The oncoming watch reads the log, states the status, and formally accepts. Nothing is silently dropped between watches.

05

The log survives the watch

What happened on watch is written, signed, and kept. The record is the ship’s memory, and it is the thing an inquiry reads.

The product sentence

Software agents are watchstanders now. Watchbill assigns every agent a named watch under a named human, gates every irreversible act behind that human, turns work over between sessions instead of dropping it, and keeps the append‑only record that proves all of the above to whoever asks.

The lifecycle

Six steps, at principle level

  1. 01

    Assignment

    The watchbill names which agent stands which watch, under whom, and where its authority ends. Before work begins there is a muster: the check that every watch that matters is manned.

  2. 02

    The watch

    The agent works inside its station for a defined window. The station is not a suggestion. It is the boundary the rest of the model is built on.

  3. 03

    The gate

    Nothing irreversible passes without the watch officer. Agents propose. Humans commit. A refusal is an outcome, not an error, and it is written down like any other.

  4. 04

    Turnover

    The handoff between sessions is explicit. The oncoming watch reads the log, states the status, and formally accepts. Work is not left to be inferred by whoever arrives next.

  5. 05

    The close

    A watch ends the way it began, on purpose and on the record. Relieved, with the state of the station stated rather than assumed.

  6. 06

    The record

    Every assignment, proposal, commit, and refusal lands on an append‑only log. Entries are added, never edited or removed, and edits would be evident.

A worked example

Invented for illustration, and abstracted on purpose

The shape below is what a watch looks like from outside. It is a constructed example, not a customer and not a transcript.

One watch, from assignment to close

An agent is assigned to a single station with a single window. A named engineer is the watch officer, and holds the authority to stop it.

Assigned

The agent prepares a change and proposes it. The proposal states what it would do and what could not be undone afterward.

Awaiting commit

The watch officer reads the proposal and commits it. The commit carries their name, not the agent’s.

Committed

A later proposal would reach past the edge of the station. The gate refuses it, and the refusal is written down with the reason.

Refused, on the record

The window ends. The watch is relieved: status stated, log read, acceptance recorded. What the next watch inherits is written, not remembered.

Relieved

Amber means a human has not yet committed. Green means measured and passed. Neither is ever used for decoration, which is why most of the states above are neither.

What stays dark

Principle is publishable. Mechanism is not.

This page describes what the system does and why. It does not describe how it is built, and no amount of asking will change that. The reason is the same reason the model works at all: a supervision discipline that can be read off a marketing page is a supervision discipline someone can route around.

What you can expect in a briefing. The model at the level written here, the properties of the record, and the questions a reviewer should be asking you. Not architecture, not tooling, not the text of anything operational.

What a reviewer receives