Skip to content

Record the M3.13f delivery and the next slice - #221

Merged
kaikisegfault merged 1 commit into
mainfrom
docs/m3-13f-closeout
Aug 31, 2026
Merged

Record the M3.13f delivery and the next slice#221
kaikisegfault merged 1 commit into
mainfrom
docs/m3-13f-closeout

Conversation

@kaikisegfault

Copy link
Copy Markdown
Owner

Documentation only. docs/project/current-state.md, no source, build, workflow,
or vector change, so this is the focused metadata verification path.

What it records

  • M3.13f is delivered: the store's fault and recovery work is on main
    across 73955eb..a30a997, closing the two debts ADR 0057 carried and making
    requirement 13's own words — "through restart and recovery" — true on the
    storage side.
  • The contract that came out of it: everything before the commit rolls back
    and is an ordinary refusal that leaves the store usable; only the commit can
    leave a head the process cannot name, and there the store poisons itself and
    reads the file again; recovery may fail, and then the store refuses everything
    rather than guessing.
  • The correction that produced it, stated rather than smoothed over: the
    original code poisoned on any write failure, which was safe and wrong, and ADR
    0057's own text already said the store is poisoned "if the write itself fails".
  • What the failure contract looks like now, so a later session does not
    rediscover which fault points throw, which are invoked and ignored so a test
    can terminate the process, and why poisoning on every write failure must not be
    reintroduced as a simplification.
  • That version one's recovery suite was re-run, because the fault seams this
    slice wires are the ones it drives.

The slice letter moved

This handoff's previous entry recorded the ABCI adapter as M3.13f. The slice
actually taken next was the store's fault and recovery work, so that took M3.13f
and the adapter is now M3.13g. Nothing about the adapter's content changed,
and the handoff says so in place rather than silently renumbering.

Verification

python3 -B tools/verify_metadata.py — 5 repository skills and 265 internal
Markdown links validated. git diff --check clean. The hosted focused metadata
path is the gate for this exact commit.

The store's fault and recovery work is merged, which closes the two debts
ADR 0057 carried and makes requirement 13's own words — "through restart
and recovery" — true on the storage side.

The handoff records the contract that came out of it: everything before
the commit rolls back and is an ordinary refusal that leaves the store
usable, only the commit can leave a head the process cannot name, and
recovery is allowed to fail into a store that refuses everything rather
than guesses. It also records the correction that produced it, since the
original code poisoned on any write failure and ADR 0057's own text said
otherwise.

The recorded next action is renumbered to M3.13g, the version-seven ABCI
adapter, because the letter this entry carried was taken by the recovery
slice. Nothing about the adapter's content changed.
@kaikisegfault
kaikisegfault merged commit 1cc7b5c into main Aug 31, 2026
3 checks passed
@kaikisegfault
kaikisegfault deleted the docs/m3-13f-closeout branch August 31, 2026 23:25
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