Read a reckoning

A reckoning is the ruling you record once a manifest has landed. It says what happened, and what should change for the seat that did the work. Where it fits in the cycle is covered in the org cycle. The Reckonings screen is where you read past rulings and record new ones.

Open the screen

Choose Reckonings in the left rail. A number on the item counts findings you have not seen yet, and opening the screen clears it. The Range control in the header sets how far back to look: 2 weeks, 1 month, 3 months or All. Every list on the screen uses the same range. Browsing only reads the record, so looking further back costs nothing.

Findings: what stopped an agent

FINDINGS lists each time an agent was stopped, newest first. That covers stalls, blocks, failed starts, terminations, cancellations, and tickets dispatched more than once. Each row shows when it happened, the ticket, the seat, what stopped it, what the agent wrote, and the ruling that followed. A row with no ruling yet carries an unruled chip.

Press a row to open it. It lists the manifest, how many times the ticket was dispatched, and the signature of the stop. Two actions follow:

• Rule… opens the reckoning form for that ticket's manifest. Nothing is recorded until you submit it.
• Ask → puts a question about the finding into the Superintendent's composer without sending it.

The timeline of rulings

TIMELINE is folded shut by default. Press it to open the list of recorded reckonings, newest first. If a field was never recorded, the screen shows a dash rather than filling it in.

At the top of the timeline, a line such as 3 landed manifests unreckoned counts the manifests that have landed but have no ruling yet. It ignores the range picker: a manifest waiting for a ruling is shown however long ago it landed. When nothing is waiting, the line does not appear.

Record a reckoning

1. Press the unreckoned line and choose a manifest, or press Rule… on a finding.
2. The Record a reckoning form opens with what the record already holds: the seat the tickets were assigned to and that seat's current mandate.
3. Write the Ruling, a one-line title, and the Feedback.
4. Pick an Improvement. The chips are exactly the improvements hm accepts.
5. Check the Seat. If two seats worked on the manifest, choose one yourself. For an improvement that changes the seat's mandate, fill in Mandate.
6. Press Record reckoning.

The form runs the same hm reckoning run command the terminal does. If hm refuses, its own message appears under the form. Nothing is written, and what you typed stays in the form. When it succeeds, the ruling appears in the timeline.

Decompress notes

If your Works has an advisor configured, a DECOMPRESS NOTES column shows one card per seat for the latest period. Each card has Well, Watch and Improve lines, and a caption naming the period and the advisor that wrote it. A period that has rulings but no note is shown as a dated chip. Recompute now asks the advisor to write the missing notes. It can be pressed at most once a minute, and the line beside it says why when it is unavailable. The Improve line can be handed to the Superintendent composer.

hm reckoning findings --since 2026-08-01    # what stopped an agent, in a range
hm reckoning list                           # recorded rulings, newest first
hm reckoning pending                        # landed manifests still owed a ruling
hm reckoning draft <manifest-id>            # what the form is filled in with
hm reckoning run <manifest-id> --title "..." --feedback "..." --improvement <kind> --seat <seat>
hm reckoning decompress show                # the notes on record
hm reckoning decompress recompute           # compute missing notes