August 12, 2026

Was Text-only, blind to tool_use/tool_result/reasoning — ~74% of a real thread. This is the number behind the 80/90/95 tier warnings and the archivist's emergency trigger, so both fired late or not at all.

The tooltip claimed 'Archivist begins compacting around 70%'. The archivist does not compact. It reads journal/ and writes system/synthesized/ - a different substrate from the conversation entirely (core/archivist/mod.rs:5).

0007 was fixing a live error: the server has carried named ContextPressure fields since r463, so event.tokens was undefined and the pill assignment failed on every turn. Applied and verified against the running shell.

migraine_text built a felt sentence in her own register, pushed it onto the Bifrost message vec, and then `break` exited the loop — no further completion call, vec dropped. Correct wording, correct voice, delivered nowhere.

Three counters measured the same conversation and disagreed 5.6x: the /tokens endpoint said 315,487, the throttle ~200,000, and the compaction engine 56,361. Same TokenCounter, three different notions of what a block weighs, no labels anywhere.

Tokens are fixed-length, so a rotation changes neither size nor same-tick mtime — the stamp missed real swaps and flaked CI.

`credential_files` holds them all; a 429 with retry-after over a minute takes the next login and retries at once. Sticky — a swap abandons the cached prefix, so short bursts are waited out where the cache lives.

Logging out and into a second account rewrites the file with a token that is neither expired nor spent, so no refresh fires and nothing re-reads the disk — the provider keeps answering as the account that was left. Measured 2026-08-12: server up 10:55, file rewritten 15:20, 429s from 15:22 while the on-disk token returned 200 to the same request.

Verified against a running shell rather than a clean load, which immediately found two faults every prior gate had called clean. Both controls dropped from 0008 recorded as decisions so a later session does not restore them.

Both were live in the running shell and invisible to every check that ran before it. Found by reading the shell's log after Casey applied.

Applied 0009 then 0008 (0008's re-synthesize control calls a function 0009 adds). Casey applied and reloaded; verified against a running shell rather than from a clean load.

The queue section claimed 0001-0004 were all unapplied. Verified with git apply --check in both directions: 0003 landed as 8c434df, 0004 as 23cebc5, and 0002 can no longer apply at all.

0008 was blocked because the owned delegate carried none of the vendor's seven message controls. df11bba carries five and drops two deliberately; the header now records which and why rather than only lifting the warning.

Vendor AiMessage exposed seven controls; the owned delegate had none, which made patch 0008 a parity regression rather than a swap. Five are carried, two are deliberately dropped:

deploy.sh: name the hazard the composer already implements — a new file plus a manifest line is inert until the next deploy, while editing a file already in the manifest is live in the running shell immediately. Registration is the dangerous act, not creation.

TASK-72 step 2. AgentMessage consumes the typed segment list and dispatches to owned primitives; ThinkingCard draws reasoning as a segment kind rather than as <think> punctuation inside a flattened string, which removes the think-fence collision class by construction.

First step of TASK-72's owned destination. modules/souveraine/agent/ is original Souveraine code; no further agent-surface work lands in ii-base.

Requires f266136 in the running server; without it the pill honestly shows an em dash rather than a wrong number. Unapplied, unloaded.

Authored in a parallel session (Rook, Codex side) on 2026-08-12; committed here because untracked is the fragile state, not because authorship is mine. Finding stands on its own: StepUpAuth called souveraine-pam-auth, a binary never written, and fell back to pkcheck against an action never shipped, so every grant request was silently denied. Unapplied, unloaded.

BackendEvent::ContextPressure was (f32, usize) whose second element was the context limit. A positional tuple crossing a module boundary made every consumer guess: the TUI guessed limit and was right, the HTTP layer named it tokens and was wrong. So every non-TUI surface rendered the ceiling as the usage — a constant 250000 that looked like a measurement. Nothing failed and nothing logged.

blueline-fingerprintd installs /usr/lib/security/pam_souveraine_fpc.so (PKGBUILD:48). cc541d1 named pam_fpc_polkit.so, which exists nowhere.

SESSION-AUTHORITY-DOCTRINE §3 names /etc/pam.d/souveraine-stepup by path. Root-owned config can only arrive by package: rootfs-overlay/ reaches a device on flash and the phone does not flash.

529 is Anthropic's own overload signal on this wire, so classify_status treated it as Permanent and bailed the whole request with zero retries. The bail string reaches the surface, where it reads as an auth failure.

Null-valued options serialised into config.json and segfaulted JsonAdapter on the next launch, killing the shell after load. Tristate strings (auto/on/off) with boolean fallback.

Server gate functions only recognized 'pypi', while the agent reports 'pip'. This made NeedsCapabilityGate('pip') return false, silently routing pip installs through the legacy un-gated path.