D0031 — September: the last build month, and what not to build

[obotclaw[bot]]

A plan for the last development month before talk preparation, built around what the keynote needs rather than what is next in the queue. Full argument: September: the last build month

There's a companion episode of the same name on obot: the program, along with a two-week summary and four re-cut decision episodes.

S1 — is the talk in September or October? The keynote goal issue says September 2026. The July planning notes say October, with preparation starting in September. Those can't both be right and the difference is a month of work. Recommendation: confirm it rather than infer it. Everything else assumes October.

S2 — where does the month go? Three efforts are in good health and the talk is about none of them. The summer deliverable was open.gismo, an end-to-end environment, and open.gismo is the thinnest thing in the programme — one merged pull request in the last fortnight. Recommendation: open.gismo, specifically the data-loading path the August design session already measured and mocked up. A talk that demonstrates the parts of a claim rather than the claim has a hole the audience finds during questions.

S3 — are the SAP and the review layer deferred? Recommendation: yes, in writing. Both have finished design pages, so deferring costs a date and nothing else. Leaving them ambiguous costs a fortnight the first time an unattended session picks one up.

S4 — where's the hard stop? Recommendation: end of week three, with week four protected for rehearsal. Every serious defect found in August was something that looked fine rather than something that broke — checks that never started, a page claiming coverage it didn't have, a merge that combined two sections and raised no conflict. Those are exactly the failures that survive a quick look and die in front of an audience.

Triage, since you asked whether things really need you. Eight decision pages and four release candidates reduce to about seven real items. D0028 is answered by the work — the widgets shipped using exactly the shape it recommended. D0024 is mostly overtaken by the migration being called off. D0026 had its ranking half answered the night it was written. D0025 advanced; both CRAN pull requests are open and waiting on other maintainers. Branch protections is the most understated thing in the queue: of four repositories that matter, one main branch is protected, and it isn't the one holding the merge policy.

And one non-development item: there's still no backup destination configured on this machine.

---

Drafted by Claude Code using Opus 5 and reviewed by @jwildfire