Release: the ring file, the rules that cut and move next and roll it back, and a commit's one Release (#197, PR 1)
Closed
DO
25d ago+1619+1619+0123456789012345678901234567890123456789-20-20-01234567890123456789
Part of "Release: cut an immutable tag, move next, and roll back in one action" (#197), PR 1: code and data only. Nothing here writes a tag, mints a credential or dispatches a workflow.
What it holds
release/rings.json(rings/1, a data file):next(factory/v0-next) serves combsmith/software-factory forreview-change;stable(factory/v0-stable) serves nothing; promotion fromnexttostableneeds at least one Run, every Effect read back and an eval for each changed Intent (FR-47, FR-50, L-47). Schemaschemas/rings.schema.json; example and four counter-examples.release/cut.py, pure (rulings 4, 4″, 5′):plan(step, refs, facts, channels)gives the writes or one code. Only a Channelrings.jsondeclares is moved, and only to a commit one Release names alone; every commit and ref is a full sha, or the step is refused. A cut refusesnot_newer,not_on_main,not_verified,already_released,another_majorand, read before anything is written so a closed gate burns no version,eval_gate_closed, which also refuses a pass judged for another Release. A move goes only to an existing Release of the Channel's major, through the same gate. A rollback passes no gate and only moves back (not_earlier), by default to the greatest Release below. No step writes a Release tag (release_is_immutable) orstable(promotion_not_built).release/current.py(ruling 7):resolve(commit, refs)is the one Release tag on the commit; a Channel never counts, and two Releases are none, matching the interimgit tag --points-atsemantics.release/move.py:python3 -m release.move plan STEP REFS FACTS, which prints the plan and writes nothing.adapters/tags.py: one read ofgit/matching-refs/tags/factorythrough the transport;{name: commit}, or None for an annotated tag, a name twice, another page, or any answer not a list of refs. It reads nothing at any tag (0006).tools/check_release.py, run by verify: no repo and family on two Channels, both Channels of one major, and the rules import nothing but each other.check_examplesrefuses a rings counter-example through it, as it does a trial's throughcheck_trials..claude/skills/cut-a-release/SKILL.md(10′), pointed to from the rootAGENTS.md;release/AGENTS.md.examples/invalid/task.a-channel-for-a-release.json(L-45).config/apps.json: the release App's five needs (write:release_tag,write:move_channel,write:deployment,read:release.refs,read:release.runs), eachwaits_onits registration, aswrite:write_viewwaits on the view App's; the schema and the apps counter-examples carry them.release/fixtures/refs.read.json: one read ofrefs/tags/factory/through the Maintainer's gh login on 2026-10-26, redacted (nofactory/tag exists yet);adapters/tags.pyreplays it, andcheck_releaseholds every Release fixture tocheck_trials' credential scan and header list.- Rows re-pointed: 0006 (three), 0010 (one), L-45, L-46, L-47.
- Protected files, for the Maintainer's eye:
config/hooks.json(release/added as a verify lens input;tests/test_tools.py::TheListrequires every top-level package there) andconfig/apps.json(the five needs above, no grant).
The gate is read before the tag is created, not after as 4′ words it, so a closed gate burns no version; the record should say so.
Not here
.github/workflows/release.yml(4′): PR 2, reviewed on its own. The App's entry with 4′'s grants: after the Maintainer registers it and P-39 reads it again (PR 3 or its own). Here, only its needs, each waiting on that registration.- Record 0066: written, and added once records 0064 and 0065 are on
main(records are gapless in merge order). - Ruling 8 (a Run on another Release than its pass's does nothing): L-46's second half now waits on
.github/workflows/run-jobs.yml, since #334 is rewritingharness/run.py. release/rings.jsonas a protected path inconfig/hooks.json: the Maintainer's edit (ruling 6).- For PR 2: a forward
moveinput onrelease.yml(9′ step 5 needs one; 4′ names only cut and rollback); a check thatfactory/v0.0.1is lightweight, sinceadapters/tags.pyrefuses an annotated tag and a Release tag can never be deleted; and whether GitHub paginatesmatching-refs(the port fails closed on anextlink), which no fixture records yet.
Gates
make verify(SIM_SEEDS=40, alone): 1183 tests OK (14 expected failures), every check ok, on 87e497f- Mutants: 48 new, each killed by its named test in a whole-tree copy with
MUTATING=1(50 now). The capped filtered run hit the machine-load timeout (its baseline suite takes over 600 s here, and it caps a run at 40), so CI's 8 shards stand as the mutant gate - Fresh Claude review with a security pass: no blocker; two majors (an undeclared Channel of another major; ruling 8 not here) and minors, fixed in the second commit but for ruling 8 and the PR 2 items above
- Argon (AGY): one blocker (a move or rollback onto a commit two Releases name) and majors (the rules could import the CLI; a falsy
to; non-sha commits; mutants missing), each fixed in the second commit - SonarCloud: the plan read paths from argv (S8707); it now reads standard input (87e497f), thread answered
- Muse: not run (Maintainer, 2026-10-20: Kernel/hook only)
🤖 Generated with Claude Code