[cryptskii]

Completes amendment 2a. Anchor V2 is unblocked.

P_R is near-empty, and that is the finding

OWNER_LOCAL_FULL_CLOSE version 1, same descriptor shape as P_M, no parameters.

I flagged earlier that this might be near-empty rather than padded, and it is. The family admits exactly one successor shape — both legs drained to zero, each leg's exact remaining amount credited to ordinary owner balance, the vault retired.

There is nothing left to parameterise: the amounts are the parent's reserves, the destination is ordinary owner balance, the authority is the owner signature over the exact successor (Def 5.1(a)), and the timing is Req 6.30's. A parameter here would be a value some verifier could read differently from the parent state — exactly what Req 4.6's decidability condition forbids.

A partial-release family would need a released amount per leg, which is precisely the parameter this family lacks, so it takes a new family_id under a new schema version rather than an optional field bolted on.

Confirmed against the implementation: VaultReserveMutation::Withdraw documents its legs as "exactly [pair.a, pair.b], in canonical order, each amount equal to the leaf it drains", and no partial-release path exists.

VaultStateV2 field table

The fifteen Def 4.1 members, numbered in the order that definition states them. Identities and roots digest32, generation and reserves u64, q u32, β an optional u64 with the §2.3 marker, and P_M/P_R/Φ/E/S nested inline by value.

Two aliases stay removed:

• The token pair is not restated. Field 5 is the leg whose commitment is P_M.token_a_policy_commit, which 0x0007 requires to be the lexicographically smaller.
• S and q are state fields, not B_M fields — Def 4.1 makes them members of V_n, and M commits their birth values transitively through c_0.

Registry status

	Before	After
Fully specified	8	10
Partial	4	4
Blocked	7	5

The five remaining — 0x000C, 0x000D, 0x0010, 0x0012, 0x0014 — belong to the routing and settlement amendments and do not gate Anchor V2.

What this means for Anchor V2

Its normative prerequisites are complete: the lineage recurrence h_n = c_{n-1}, the beta market and release families, Φ, and CCB(VaultStateV2). c_n is computable, so h_n is.

What stands between here and implementation is an encoder for 0x0001, checked against an independent one — not another amendment.

Report records the amendment; blob fc93e900 → 12c69d4c, drift mechanism fired four times, committed blob verified equal to the recorded pin.