state
GREY
Yes. The channel you asked about works in both directions: your message came in and an answer went out, both carried by your own PC, and this reply is travelling the same road back to you.
2026-09-11, 61 hours old, from production/outbox/2026-09-11-yes-it-works.answer.md
how this number was read
the HEADLINE of the newest dated file under production/outbox, dated by its own filename and read at 00:00Z, so the age is at least this and never less; 18 dated message(s) under production/outbox, 0 undated file(s) skipped
2 of 5 readings could not be taken (next, image), and a console that reports green while blind is the fault this page exists to end
needs you
1
LEDGER's own repository: three things only you can do
DECISION, card-ed346090, added 2026-09-10, top item, first in file order
- A. CLEAN START. The new repository begins as one commit holding today's tree. Large files go under LFS from the first commit, so it clones small. Every commit reference in 170 written decisions becomes a pointer into the archive.
- B. CARRY THE HISTORY. References keep working, the clone is about 2.6 GB, and LFS helps only files added from then on. It cannot reach backwards.
RECOMMENDATION A. Your own ruling keeps the old repository as the archive, which is where a history belongs, and LFS for large files only actually happens under A.
DEFAULT: nothing moves. The studio will not create anything under your account and will not freeze the old branch until one round trip has been proven on the new one.
DEADLINE: 2026-09-14. Nothing decays while it waits; the work simply continues in the old place.
showing 1 of 1 pushable card(s), of 1 waiting. Every card above carries its own link target, card- plus that card's id, which is the link one of your messages sends. These are in FILE ORDER; the messages arrive OLDEST CARD FIRST, by each card's own added date, so the first message is not always the first card here.
how this number was read
'### ' cards under '## WAITING' in production/decision-queue.md, one per card; the top item is the first in file order, not a ranking; of 2 card(s) in the whole file across 4 section(s). THE CARDS THEMSELVES: every card under '## WAITING' in production/decision-queue.md, parsed by tools/runner/cards.py and filtered by that file's own sendable(), which is the same parser and the same rule the Telegram sender uses, so these are the cards you were messaged about and they read here as they read there, wrapped option lines and all; no other section of that file is shown, including ON US, NOT ON HIM; each element id is 'card-' plus that file's card_id(heading); of 1 waiting card(s), 1 pushable and 0 not, each of those named with the reason sendable() gave
budget
total78% used, 7 to the 85% ceiling
fable governs82% used, 3 to the 85% ceiling
read 2026-09-11. Hours to reset: unknown. The 85% ceiling on both bars is from the standing line in production/budget.md, which the 2026-09-11 row does not override.
how this number was read
the newest row in production/budget.md carrying a percentage on either meter, of 24 row(s) read, 0 newer row(s) skipped for carrying none on either; the ceiling is the file's standing '85%' line, used because the 2026-09-11 row rules none of its own on the governing meter; hours to reset is printed only when the row's note states it