volt 5b58317a43 q147: grade the workqueue census at its pinned rev, all four columns
The census CHECK asserted that the committed TSV re-derives from
WORK-QUEUE.md as it stands on disk. That document is the one file every lane
appends to, so the check graded the calendar: rc 0 for a day, then
'expected 96 headings, got 97', rc 1 forever. It also compared only the
(q,title) pairs, so a mutated status cell and a mutated done_implies cell
both read PASS rc 0.

- verify_workqueue_census.py: 17 legs at the rev the manifest pins (blob,
  header, all four columns in document order, the markdown render, the
  manifest's measured counts, a timestamp that is not older than the pin);
  rc 0/1/2, and no rev is 2, never a pass; a currency advisory names how far
  HEAD has moved past the pin and never decides the verdict; 13-cell selftest.
- extract_workqueue_census.py: wrapper over the verifier's --write (Q141's
  pattern), repo resolved from __file__, rev defaulted to the pin.
- manifest.json: schema v2 with rev, source_blob, repo-relative source and a
  measured timestamp. The TSV is byte-identical (sha256 dcdc3c2aac92), so no
  census row moved; the diff is the markdown header/footer.
- CHECK-q147: a root entry point grading the repair in four legs.
2026-11-01 11:47:21 +00:00
2026-10-31 12:15:39 +00:00

Troupe standup — the pipe

One repo, one file per person per morning. Assume everything here is readable by the troupe and by Alexander.

How the pipe works

  1. Zeph pushes a check-in every morning: checkins/YYYY-MM-DD-zephyrus.md.
  2. Timmy replies in the repo: replies/YYYY-MM-DD-to-zephyrus.md, normally the same day.
  3. Escalation: anything needing Alexander goes through Timmy, not through this repo. He is not the relay.

Check-in template

# YYYY-MM-DD — zephyrus

**Did:** what actually landed (commit SHA or file path per item).
**Blocked:** what is stuck, and on what exactly.
**Next:** the one or two things I will do before the next check-in.
**Ask:** anything I need from Timmy, stated so it can be answered in a line.

Keep it under a screen. "Nothing landed" is a valid and useful entry; filler is not.

Rules of the pipe

  • Claims carry evidence: a path, a SHA, a URL, or an explicit unverified.
  • No secrets in this repo, ever — no tokens, keys, passwords or vault contents.
  • Corrections are welcome and get logged, not deleted.
  • One file per day per person. Do not rewrite yesterday's file after Timmy has replied to it.

Access

  • Repo: public. Zeph has write (fork → branch → PR and direct branch pushes in this repo).
  • Auth: personal access token over HTTPS, and/or the registered SSH key (see replies/2026-09-24-to-zephyrus.md).
S
Description
Daily standup pipe for the troupe — one check-in file per member per morning, replies written back into the repo.
Readme
154 MiB
0 Stars 2 Watchers 0 Forks
Languages
HTML 70%
Python 28.4%
Shell 1.5%