[cryptskii]

The trade's settle, from the rig: the SDK's storage client asked the five storage members one after another for every object, index and cell. Now it asks them all at once. The settle's steps are logged.

Found on the rig (APK = main 0d36d20)

• Three trades took 126–129 s, and the settle was 70–80 s of each.
• The settle resolved in its first round, so no round was wasted. Inside that one resolution, about 1–2 s of fast cell reads alternated with 6–12 s of silence, five times over.
• The silence was SetClient. Every object read and put, index read and append, and cell read and put asked the members in turn. The settle's objects carry SPHINCS+ signatures, so a phone paid five round trips per object.

Change

• Concurrent set-wide calls. Every SetClient call asks all members at once and keeps their answers in member order. Nothing a member answers changes.
• fetch_verified. It reads every member at once and keeps the first answer, in member order, whose bytes re-hash to the address.
• Step logs. The settle logs where each stage ends: registration, precommit, exercise, each leg's vault, facts, advanced. Core logs each generation a chain establishes. Nothing reads a clock (ci/no_clock_and_no_json.sh passes); logcat's timestamps time each stage.

Rig after the change (APK = this branch, same fleet)

The same kind of trade, a chain ERA → RIGT → HOP with no setup, realized at position 13 in 53 s, against 126–129 s. The quote took 20 s.

Stage	Before	After
Draft → completing	14.5 s	4 s
Completing	16 s	6.3 s
Settle	70–80 s	28.7 s

Tests (release, Postgres node fleet)

• The new test: a_set_asks_every_member_at_once. Each member sits behind a relay that holds its first connection until every member has one, so a client that asks the members in turn is never answered. An object put directly is read through the relays from all five members, and a put through them is taken by all five.
• Mutation control: object reads in turn turn it red (1 of 5 members answered); restored byte for byte.
• SDK node and handler suites: 76 passed, 0 failed (node e2e, sender and recipient admission, token create, faucet, realized records, sofi_flow, route_seats, storage_node_sdk, storage_io, sofi_reads).
• Core: dsm sofi::, 237 passed, 0 failed.
• Static checks: make lint exit 0; guard clean; conformance_evidence 805 rows.

What remains (§6.59), from the step logs

• Owner walks from activation, 11 s. Whether a walk records a frontier for the vault owner is the owner's question (DSM A8).
• The chain walk of the vault the trade consumed, about 19 s. Two passes over the sibling leg re-read the same cells about four times each.
• Establishing the facts, 2.7 s.

Pins

INTENT_PINS will be repinned once from this PR's Code map.