Six stations, one river
How the mist ledger desk works with you
Every service below is a way of writing the same river more clearly. Read them in order and you have the
full method. Read only the one that matches your current fog and you still get a finished page, because
each station is designed to close on its own terms.
B Ship Note Bays
A ship note bay is where a new problem is opened and named before a tool is touched. A keeper sits with
your operators, records what the river carries today, and pins the note in the bay so scope cannot
drift unnoticed. The first note is deliberately short: it names the problem, the people affected and the
smallest change worth making. Because it is short, it is easy to challenge, and because it is written,
it survives the meeting that produced it.
Bays are kept open for the length of an engagement. When a new question appears mid project, it is
opened in a second bay rather than folded into the first. That habit keeps the original problem legible
and stops a small repair from quietly becoming a rebuild nobody agreed to. If you have ever watched a
simple fix turn into a season long project, the bay is the remedy.
D Mist Sheet Runs
Mist sheets list what nobody can yet see: missing data, loose assumptions and steps without an owner.
A run walks the sheet line by line with the people who live with the consequences, until the fog thins
and each unknown becomes a decision with a name and a date on it. Some lines close within an hour and
others take a season, but none are allowed to sit unread, because unread fog is where systems fail
quietly long after the project review is over.
A mist run is honest work, not a status report. The output is a sheet that records what remains unknown
as plainly as what has been settled. Clients often keep the sheet on the wall after the engagement
ends. It is a working map of the crossing, and it tells the next reader where the desk already looked
so that nobody repeats the same search.
T Consignment Letter Desks
A consignment letter is the written handover between the desk and your operators. It records what was
built, who owns it, how it is watched and how to recover when a step fails, all in language the floor
can read. The letter is written for the person who joins next year and has to understand the system
from paper alone. If that person cannot recover the crossing, the engagement is not finished.
Letters are drafted before the final build review, not after it, so that gaps surface while the desk can
still close them. Each letter is dated, signed by the keeper who wrote it and stored where the client
can retrieve it years later. Nothing about this is ceremonial. A handover that lives only in the memory
of the person leaving is a risk the desk refuses to accept.
C Berth Windows
Berth windows are reserved build and change slots, agreed in advance and protected from surprise work.
A live operation cannot pause while a designer experiments, so the desk plans each crossing, tests it
against the recorded river and keeps a rollback note ready. When the window closes, the operation runs on
the new route and the old route is documented rather than abandoned.
Windows are coordinated with the people who actually feel a deployment: counter staff, floor leads,
night crews and schedulers. A window that suits the desk but wrecks a shift is not a window at all. The
calendar is shared, the rollback is rehearsed, and the desk stays reachable for the hours after the
change, because the first evening after a crossing is when the real questions arrive.
H Drift Review Rounds
Every season the desk returns to the river and compares the written record with what is actually
happening. Drift review rounds catch the slow creep that no single incident report ever shows: a
shortcut that became policy, a report nobody reads, a step that moved one desk to the left. These rounds
keep a system honest as the business around it changes shape.
A round produces a short written comparison, not a scorecard. It says what changed, what the ledger
still expects, and which few adjustments would bring the two back into line. Many clients schedule two
rounds a year and treat them as maintenance rather than crisis response, which is exactly how the desk
prefers to work.
M River Sittings
A river sitting is an unhurried working session with the people who use the system daily. It is where
the ledger learns what the reports leave out, from the workaround nobody documented to the handoff that
happens in a doorway rather than a ticketing tool. Sittings are scheduled outside peak hours and run
without an agenda beyond listening well.
Notes from a sitting feed directly into the open ship note and the current mist sheet, so nothing is
gathered and forgotten. Clients sometimes ask to run a sitting before any build begins, and that is
usually the wisest request we receive. The river is the best teacher of where the fog actually gathers.