Skip to content

Add the iteration request shape and release 4.4.0 - #108

Merged
mzored merged 4 commits into
mainfrom
release/440-iteration-shape
Sep 6, 2026
Merged

Add the iteration request shape and release 4.4.0#108
mzored merged 4 commits into
mainfrom
release/440-iteration-shape

Conversation

@mzored

@mzored mzored commented Sep 6, 2026

Copy link
Copy Markdown
Owner

Summary

  • The kernel gains one request shape, the iteration: a change to something the owner will look at before deciding what comes next. Its verified completion is the shown result; the wider tests, tracking, commits, push, and integration follow the owner's acceptance. The rule lives in the grant section beside the sentence that carries every other change through to the authorized destination.
  • One Codex review round returned two qualifying findings, both confirmed and fixed: the shown result is reviewed like any other final state, and a request that names a destination or asks to ship is delivery whatever the owner looks at afterwards.
  • Guide, README, decision history, evidence ledger, security policy, and changelog describe the 4.4.0 shape and what was not adopted (a separate skill, an owner-side instruction, an edit to the stop sentence, a duplicate in the verification playbook, a hook).
  • Version 4.4.0; host-smoke ledger reset for the new candidate with the Claude Code clean install and uninstall receipts on the exact package. Codex clean install is UNVERIFIED on this machine (managed source policy).

Verification

  • python scripts/check.py, git diff --check, python scripts/check_hosts.py --smoke on the exact candidate.
  • Model behavior on the new wording is UNVERIFIED; the fixture that would show it is listed in docs/evidence.md.

🤖 Generated with Claude Code

mzored and others added 4 commits September 6, 2026 23:00
Reset the host-smoke ledger to UNVERIFIED for the new candidate and point its
historical source at the 4.3.0 ledger.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
A change the owner will look at before deciding what comes next is complete
when it is shown, not when it is integrated. Delivery starts on the owner's
acceptance. This closes the gap that sent a screen edit through merge when
the owner only wanted to see it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The iteration's shown result is reviewed like any other final state; only the
wider tests, tracking, commits, push, and integration wait for acceptance. A
request that names a destination or asks to ship is delivery whatever the
owner looks at afterwards. Guide, README, decision history, evidence ledger,
security policy, and changelog describe the 4.4.0 shape.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@mzored
mzored merged commit dca3b67 into main Sep 6, 2026
1 check passed
@mzored
mzored deleted the release/440-iteration-shape branch September 6, 2026 19:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant