THE READING ROOM
THE READING ROOM
A shared dashboard can make a platform look unified long before its measurements are comparable. One service records request duration in seconds. Another records milliseconds. A third starts the timer after retrieval, while the first includes it.
A real SQLite fixture keeps failed attempts while the current operation turns successful. Identity conflicts, repeated observations and a local transaction show why a summary is not an incident history.
Six deliberately broken executor variants show whether independent effect assertions detect missing actor, scope, replay, expiry, digest and version controls.
A bounded plain-text ingestion pipeline preserves versions, cancellation and searchable representation identity, with actual SQLite checks and small-corpus measurements.
A real Blazor WASM and .NET ONNX comparison freezes tokens, model, pooling and candidate scope, then tests parity and failure across a loopback HTTP boundary.
A real SQL Server experiment traces the read benefit, update obligation and storage cost of a computed-column index over a JSON property.
A throughput experiment is incomplete until it demonstrates recovery from duplicates, retries and interrupted processing.
An executable recovery runbook rejects missing artifacts, wrong identities, stale history and conflicting replay before allowing the next step.
A migration can compile successfully, pass a demonstration and still change the behavior that made an agent useful. The new implementation may choose different tools, forget state at a different boundary or retry an operation that the old implementation treated as terminal.
A real HTTP and SQLite fixture shows why a persisted request and a confirmed reservation are different promises. Admission, worker processing and terminal outcomes are verified separately.
A reproducible C# allocation model separates source records, shared-resource policy and unresolved attribution. Synthetic units make conservation and rounding testable without claiming live cloud costs.
Two real context builders share one eligible source catalog and a scripted Microsoft IChatClient boundary, exposing version, size and update contracts without claiming a live-model quality comparison.
