Merlin adfff7a39a Q30 DONE: the renderer's entry point runs, and it refuses production by default
- reproduced the defect first: python3 helm-render.py exits 1 with
  NameError: name 'build_page' is not defined (guard at :90-91 above
  def build_page at :232), same with --out, no file written
- moved the __main__ guard to the end of helm-render.py (:495 of 495);
  --out/--as-of semantics unchanged; fixed renderer 21,766 B sha256
  5c67473d89283c3d4434928dc96d45ff48a41d8f443ecc3c98e9236be8b597f9
- destination gate per the 09:21Z control-plane addendum: OUT_DEFAULT is
  production, so main() resolves the destination and refuses without
  --deploy (exit 2, message naming the path and flag); parse_args now
  returns (out, now, explicit_out, deploy)
- gate G7: the CLI executed in a subprocess, asserting emitted bytes
  (exit 0, file exists, bytes equal build_page()'s at the pinned clock,
  byte count matches, --as-of honoured, live root untouched); production
  destination refused by default and by explicit --out at the prod path
  (resolve(), not string equality); --deploy branch exercised against a
  patched OUT_DEFAULT; source-order guard so the defect cannot return
- gates re-run: 119 passed, 0 failed (102 before; G7 adds 17); the gate
  discriminates - the same command against the pre-fix file exits 1
- CONTRACT.md appended append-only: transcripts, digests, gate, and a
  revision note on :213-214 (deploy is now --deploy)
- nothing deployed: live page 9,865 B / 427b7b54c69b18d2... and snapshot
  aa842b0fd88037f8... unchanged before and after every run; --deploy
  alone never executed
2026-10-11 11:16:20 +00:00
2026-10-08 13:09:29 +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
155 MiB
0 Stars 2 Watchers 0 Forks
Languages
HTML 69.9%
Python 28.5%
Shell 1.5%