Repository navigation
The Maintainer's decision at the first Release on next is continue, on 2026-11-13 (#198's ruling 7) - #795
Conversation
…n 2026-11-13 Typed on his word, as the Factory Builder relayed it; record 0200 has the change merge only on his own approval, by hand, which is the act that shows a person decided. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|



This writes the Maintainer's decision at the first Release on
nextintorelease/decision-points.json:decided"continue",day"2026-11-13",by"don-petry". It changes those three fields and nothing else. He decided on 2026-11-13, through the Factory Builder, after reading the count the file shows; a session typed it on his word. Part of "The ruleset switch: main requires the machine user's approval of the most recent commit, and slice 1's event is recorded" (#198); it does not close it.This pull request merges only by the Maintainer's hand.
release/decision-points.jsonis a path only a person decides (record 0200): the Factory reviews the change and then waits for a person's approval, which a session cannot give. He approves the head by hand as the machine user (record 0198), and the Factory Builder enqueues it. That approval is the act that shows a person decided. No enqueue wait is armed on it.For him to confirm when he approves: the day. It is written 2026-11-13, the UTC day his word came; it was the evening of 2026-11-12 where he sat. No check can confirm a day:
tools/check_release.pyholds it only to being a calendar day on or after the day the counts were read.Size. 398 characters and 17 lines by
git diff; 464 characters as the Kernel counts a diff. It carries no record: no check asks for one, and records 0194, 0198 and 0200 already say what the file is and how it merges.Why it was opened only now
Both Claude readers found that the Release then on
next, factory/v0.1.10, was cut before record 0200 merged, so its Kernel would have let the Factory approve this change as any other. The branch was held unopened until factory/v0.1.11 was cut from d440e4d andnextmoved to it. That Release'sconfig/hooks.jsonholds the person-only list.Checks
make checkstools/check_release.pyfinds the decision written whole, by the Maintainerconfig/hooks.jsonnames, on or after the day the counts were readtests.test_releaserelease/decision-points.json, run alone on an exportmake verifyverifyis the answer33273293327329332732933273293327329nextpredated record 0200, so the Factory could approve this change on a model review alonenext🤖 Generated with Claude Code