ledger
46b6282296
A scan of wizard-work/spark for every remaining reference to the 25 paths retired ina979e63turns up six files, and each exists only to exercise or describe one of them. They are retired here rather than repointed, because a repointed cell would be a new test of the survivor wearing an old tool's name: check.py imported count_words from word_counter.py through a sys.path.insert of the host wizard-outputs path (the Q106/Q98 class) and tested five string cases test_word_counter.py the same five cases against word_counter.py test_wordcount.py ran wordcount.py and compared to `wc -w` verify_snippets.py the lane's "snippet verification", whose one check was word_counter.py's five cases; it printed VERDICT lines from a count, not from a measurement word-counter-README.md documented word-counter.py's interface and a 7-word example, i.e. prose for a file that is gone scratch_word_counter.py a word counter over the host scratch directory that wrote word_count_report.json to a fixed host path What replaces them: wizard-work/spark/test_line_counter.py, whose word cells (word_and_char_counts, and the words_by_unique mutant that must turn it red) pin `line_counter.py --words` on a fixture that is in the tree. check.py's and test_word_counter.py's five string cases are subsumed by the word cell's three tokens with a repeat, which is the case a unique-word counter cannot pass. Not retired, and deliberately: word_count_report.json and the fixtures test_words.txt / test-input.txt / test-empty.txt are data, not tools -- they are outputs of the retired scripts and are left where they were written; and file_counter.py, file-counter.py, count_functions.py, json_key_counter.py, count_verified_skills.py, verify_count.py, passwd_lines.py and generate_stats.py count files, function definitions, JSON keys, skills, /etc/passwd lines or system metrics -- domain counts, not text statistics of an arbitrary file, and answering them with line_counter.py would be a different tool. The boundary is stated in the Q125 record. Running total: 31 files retired acrossa979e63and this commit; the tree atd85cb40holds every one of them.
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
- Zeph pushes a check-in every morning:
checkins/YYYY-MM-DD-zephyrus.md. - Timmy replies in the repo:
replies/YYYY-MM-DD-to-zephyrus.md, normally the same day. - 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).