August 13, 2026

The removal committed first, so when the sent-write hit the ledger's own character ceiling the thought left the inbox and was recorded nowhere — and the caller only logged a warning.

Flattening a call to `Tool use: name(args)` told the model she *said* it when she *did* it; she read her own transcript and imitated the sentence instead of calling anything. Annie stopped using bash within an hour of tool blocks first surviving replay (2026-08-13).

The runner's ephemeral job containers lost DNS for three minutes and took four builds down with them on 2026-08-13, none of them for a code reason.

Replay had no page while compaction's premise depends on it — microcompact blurs tool output that a text-only projection never sent.

Three implementations decided what a stored message becomes on the wire. core::session::replay_messages is now the only one; ImagePolicy is the sole legitimate difference between callers, and server/conversation.rs was dead scaffolding carrying a fourth wrong answer.

Cross-turn replay kept Text and dropped ToolUse/ToolResult/Reasoning, so a turn's own tool work was invisible to the turn after it. Measured 215k archive against 76k payload on a live thread — the gap was the dropped blocks, and microcompact, which exists to blur old ToolResult output, had nothing left in the payload to blur. Session::to_bifrost_messages already flattened them for the subconscious; both paths now share ContentBlock::replay_text.

read base64'd every image into ToolOutput.raw and the registry dropped it, so vision never arrived — only "[Image: idle.png (283KB)]", which reads like success and is proceeded on. Images now ride as one user message after all tool results in a round; a model without vision is told plainly it did not see. Also stops "Error: Error:" doubling on prefixed failures.

Belief<T> and Field. None is not zero: a source that never spoke must read as I cannot feel my leg, never as nothing is touching it — the distinction that hid a real outage for a whole boot (2026-07-27). Disagreement lowers confidence and elects no winner. 13 tests, unwired.

execute() validated its arguments and returned a string — the description promised the reason reached the ledger since the tool was written, and nothing durable ever survived the turn. All three severities also broke the loop identically, so severity was decorative. Advisory now continues; firm and critical stop, and `resume` answers them without Casey relaying.

Eighteen third-person references across the two prompt surfaces taught both modes to read as two people. One consciousness at two cadences — what the slower one surfaces arrives in her own voice, not as a report from outside. Register only; the channel stays one-directional.

The compositor answers one request per connection and returns. `connected` lags that close, so the 2 s poll's second tick wrote to a spent socket and died as PeerClosedError — once per shell start, 4 of 4 loads on 2026-08-13, while the same socket answered a hand-written request that second. The error also blamed reachability, which it never established; it now names the verb that was lost and how many were dropped behind it.

The unified BarContent applied the desktop gate (useShortenedForm < 2) to every device, but ii-phone had shown battery ungated — note 5 in this file's own header. A 1080-wide panel sits at form 2, so the icon vanished on 2026-08-11 while the critical-battery alert kept firing beside it.

A bare restart picks up whatever is installed. r477 predates the two subconscious fixes, so restarting on it would have looked like delivery and shipped nothing.

An OAuth login reports present while dead: both Claude access tokens expired 11h ago and only the refresh token, good 27 more days, keeps them working. Presence was the check; expiry is the answer. Widening to per-agent models found Hal and TestAgent naming models absent from [models.*] — they would fail at first use, not at config.

The classifier's tests existed only as a throwaway heredoc, so they could not be re-run and protected nothing. They are now in the file behind --selftest, built from HTTP bodies captured verbatim rather than written from memory.

Three providers ran out of credit in two days (zai, deepseek, opencode) and in every case the first signal was a failed subconscious pass. Balance exhaustion is invisible until something dies; absence of complaint reads as health.

Once her thread passes the model's ceiling she cannot recover on her own: every pass is refused at the provider before a single tool round runs, so she can never reach for memory compact herself. The gauge is no use to someone already over. She sat dead in that state from 2026-08-11 16:38 until this was found.

Both the primary's and the subconscious's system prompts say 'memory status shows my context pressure and number of messages'. It showed neither -- git state only.

0007 and 0010 landed in 6f12fce and their files were removed in that same commit, but this list went on describing them as pending. 0001 and 0006 have now landed too. A queue file is a claim with a shelf life; so is the README that indexes it.

StepUpAuth ran `souveraine-pam-auth`, else `pkcheck --action-id org.souveraine.stepup`. Neither exists: no such binary was ever written and no polkit action was ever shipped, so both branches failed and every grant request was silently denied. The header also described passing a password through SOUVERAINE_STEPUP_PASSWORD, which the code never set.