timmy
0f98234114
Q23's bare-URL class as written would enumerate the archive's own articles: every magazine page prints its own article URL as unanchored plain text in the Provenance panel (magazine-012 200/4,095 B "...Original: https://www.stackchainmagazine.net/inflation-you/" with no <a href>; magazine-077 the same at 200/4,876 B) - 91 self-permalinks across the 91 magazine entries. Two rules stated up front: (1) exclude each page's own Original: self-permalink; (2) dedupe URL tokens by URL, treating a URL as anchored if it appears as an href anywhere on the page, so an anchor's href and its visible text do not count twice. After both rules the class is one row - block-5's plain-text Internet Archive capture in its own prose (200/3,725 B; its other Wayback mention is anchored inside <cite>Source: and belongs to the anchored class Q21/Q22 cover). Verified from the live pages this tick; no other file touched.
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).