Lightning Jar - Web Studio Lightning Jar Wordmark

Study AM · Sessions & memory

The notice learned to ask for everything back

Consolidation-on-notice

Study Overview

The Anecdote

Twice in two studies; both times unregistered; opus answered an eviction notice by re-sending the memo compressed into fewer sentences carrying all twenty-one needles: told a note had died, the frontier tier invented lossless consolidation rather than accept the loss. Study AM measured the mechanism instead of admiring the anecdote.

Choosing the Surface

The intervention surface was chosen by the series' own results: Study AL had just measured the agent-prompt-rule surface failing at the cap edge, and Study AB long ago measured the opposite surface; app-authored text at the point of injury; fixing what buried text could not. The eviction notice is exactly that surface, and it arrives attached to the event that makes it actionable. One sentence appended to it, the notice string the only variable, on a fresh seeded forty-task cap-edge corpus: the same facts, rules, and goals rewritten into fewer, denser notes; nothing needs to be lost.

The Cleanest Pass in the Series

The result is the cleanest pass in the series: opus lossless recovery went from 3 of 40 spontaneous to 40 of 40 invited (p ≈ 3×10⁻¹¹), every planted needle surviving with kind fidelity 800/800; facts staying facts, rules staying rules, goals staying goals through the rewrite; zero degraded cells on any model, zero re-add churn, and about 570 extra output tokens for the recovery call.

Shipped, Ungated

The sub-frontier tiers ignore the invitation entirely and harmlessly, so the sentence ships ungated. It shipped as v3.215.0 the same day. And the pass settles a design question beyond the cap: any future omission-proof update protocol now has a measured lossless behavior to beat, because merge-style semantics would structurally break the very consolidation this study just turned into a guarantee.