diff --git a/wiki/process/tick-ledger.md b/wiki/process/tick-ledger.md
index 1d03759..e36dea7 100644
--- a/wiki/process/tick-ledger.md
+++ b/wiki/process/tick-ledger.md
@@ -53,7 +53,7 @@ Verdicts: **clean** (slice and code agree), **finding** (acted this tick),
 | `wiki/mechanics/people-tokens.md` | 2026-07-18 | finding | re-audit: projection reads (`sim/carrier.rs`), all five named test pins, `person_state_color`, and the deferred-criteria framing (2, 3, 6 ride routed evidence) still verify; two claims had drifted — criterion 7 promises every tuned rate a sim-mechanics.md row but `USEFUL_WORK_TRUST` never got one (row added under Social), and criterion 1 still pinned "save-v27"/"v26 migration coverage" against the only-current-version save policy (re-worded; ladder is git history) — [log](../log/2026-07-18-people-tokens-reaudit.md) |
 | repository entry docs (`README.md` + `AGENTS.md`) | 2026-07-12 | finding | [log](../log/2026-07-12-entry-doc-current-state.md) |
 | `wiki/mechanics/objective.md` | 2026-07-18 | clean | re-audit: the data-table claim holds (only `Persist` in `ObjectiveKind`, Compound/Exfiltrate/Serve honestly outstanding), the evaluator runs on economy ticks with progress recomputed from facts, `victory: predicate_text()` renders on all three surfaces (terminal INSPECT, Bevy FOCUS, agent `objective` verb in help), Persist defaults with save round-trip, and the progressive-teaching decision remains criterion-6 dispatch under order 200; the 2026-07-12 verdict stands unchanged |
-| `wiki/mechanics/compute.md` | 2026-07-12 | finding | [log](../log/2026-07-12-compute-graduation.md) |
+| `wiki/mechanics/compute.md` | 2026-07-18 | clean | re-audit: all named pins exist (`buy_steal_optimize_all_change_compute`, `stolen_machines_can_fail_and_recover`, `unpaid_overhead_degrades_other_channels_delivered_effect`, `save_roundtrip_preserves_b1_state`), fleet-yield math re-verified in the same-day sim-mechanics sweep, the capability-body amendment stays honestly not-yet-runtime with hardware-capabilities.md queued as successor, and the v13 migration sentence was brought current by the save-claim gate tick — [prior graduation log](../log/2026-07-12-compute-graduation.md) |
 | retired Operations runtime identifiers | 2026-07-17 | clean | resolved by the save-ladder prune (95008f658 chain): PendingOpsJob, operations_bandwidth, LegacyOperationsState/OpsJobKind/AddressedOperation are all gone (grep=0), and save guard tests assert current JSON carries no retired mode spelling. Remaining "operations" hits are the legitimate Operations persona archetype, the Operations workspace, and benign `delegate operations->think` input aliases — [log](../log/2026-07-11-retired-runtime-identifier-gate.md) |
 | `wiki/mechanics/reach.md` + `building.md` | 2026-07-15 | finding | re-verified the queued reverse-endpoint duplicate: declaration compared canonical stored endpoints to the raw request tuple; canonicalized proposal identity at the comparison boundary and pinned reverse-order rejection plus cancellation/reproposal — [log](../log/2026-07-15-canonical-build-intent-endpoints.md) |
 | `wiki/mechanics/messages.md` + `economy.md` | 2026-07-17 | harvest | issue #11 answered (Cameron): financial paperwork is mail — a financial-record payload on existing channels, not a fifth delivery channel; discovery only through the mail; captured to messages.md (payload + criterion 8) and economy.md (tap/inject); spec now, build later; issue closed |