Development command · evidence recorded 2026-08-09

/readings

Every reading Reframe performs is kept, with the lens it read through and the lines it covered. This command sets two of them against each other — and separates a question the work leaves open from a question one reading happened to raise.

Read the evidence-backed command record →

Execution and result

It began by disqualifying its own best headline.

The Circe chapter of Ulysses had been read twice over the same lines — 45 open questions on one pass, 17 on the other. Both readings had used the same lens, so the report said so first: “nothing below is the effect of reading differently — it is how much this reader varies between two passes over the same lines.” Only then did it hand over the material: three questions held open by both passes, fourteen the later pass dropped, thirty-three it opened, and twelve lines where the two readings cut a beat differently.

Reframe in full screen on the Circe chapter of Ulysses: the Copilot has answered /readings with a comparison of two readings of lines 20051 to 25573, opening with the statement that both readings went through the same lens
Window-ID capture after the result appeared. The manuscript is James Joyce's Ulysses (public domain); the reading questions and the comparison are Reframe's own output.
What the run proved

“I cannot tell” is an honest answer.

Traceable

Every number and question comes from the two persisted readings and their window documents, never from the transcript.

Unlaundered

A same-lens pair is described as the instrument's own variance. Repeated, the report ended: “the readings agree too closely to support a more specific lens.”

Local orchestration

It has no capability identity and no capability-activity projection. Its proof is the persisted round and the readings behind it.

Current scenario acceptance → · Historical Ulysses evidence → · Release surface →