OSCILLA®

THE OSCILLA LAB NOTEBOOK

Notes from a lab
that checks itself.

Research, engineering, field notes and releases from Oscilla Labs — the working record of a model that shows its steps, and of the people who check them.

S1S2S3S4S5S6EVERY STEP, CHECKED AS IT IS PRODUCEDA RUN OF SIX STEPS — FIVE CHECKS VISIBLE, ONE FLAGGED
FIG. 20 — ONE RUN, SIX STEPS, EVERY STEP CHECKED

FEATURED · RESEARCH · 06 NOV 2026 · 14 MIN

Proof-carrying inference: every step, checked as it is produced

The paper behind Oscilla-1.2, in notebook form. A run that carries its own evidence — each step stated, checked and cited before the next begins — and what that changes for the people who have to trust the answer.

READ THE NOTE →
ONE BRANCH IN ORANGE DID NOT SURVIVE
FIG. 21 — A PROOF TREE, PRUNED BY SEARCH

RESEARCH · 04 NOV 2026 · 12 MIN

Counter-example search at 1.2 million cases

We pointed the search at our own proofs and let it try to break them. What it found — and the three counter-examples that changed the roadmap.

READ THE NOTE →
#1042#1059#1076#1093#1110#1127
FIG. 22 — THE LEDGER, ENTRY BY ENTRY

ENGINEERING · 28 OCT 2026 · 8 MIN

The audit trail is an interface

Every run leaves a ledger a stranger can read: inputs, steps, checks, citations. Designing that ledger as a product, not a log file.

READ THE NOTE →
1 GLITCHBLOCK C — 04:12 TO 04:12, ONE ANOMALY
FIG. 23 — ONE NIGHT IN BLOCK C

FIELD NOTES · 21 OCT 2026 · 6 MIN

Chip verification, block C: a night in the run log

04:12 to 04:12, one anomaly, forty thousand checks. A night shift in the verification lab, told from the log itself.

READ THE NOTE →
1.2PINNED, REPLAYABLE, CITED
FIG. 24 — VERSION RINGS, 1.1 TO 1.2

RELEASES · 05 NOV 2026 · 4 MIN

Oscilla-1.2: pinned versions and run replay

Pin a model version and it stays pinned; replay any run and it replays exactly. The 1.2 release notes, in notebook form.

READ THE NOTE →
S1S2S3S4S5S6S7FAILURES PER 1,000 STEPS, BY POSITION
FIG. 25 — FAILURE RATE BY STEP

RESEARCH · 14 OCT 2026 · 10 MIN

Where proofs break: failure rate by reasoning step

Failures are not spread evenly across a proof. They gather at step four — the step where the model starts trusting itself.

READ THE NOTE →
CALLCHECKRESULT
FIG. 26 — A CALL, A CHECK, A RESULT

ENGINEERING · 30 SEP 2026 · 7 MIN

Tool calls that check themselves

A tool result is a claim, and claims get checked. How Oscilla verifies what its tools hand back before the run continues.

READ THE NOTE →
40,000 IN — ELEVEN OUT, ONE IN ORANGE CARRIED THE PAPER
FIG. 27 — THE SURVIVORS, LIT

FIELD NOTES · 22 SEP 2026 · 9 MIN

Materials screening: 40,000 candidates, eleven survivors

Six weeks of screening with a partner laboratory, and the eleven candidate alloys that earned a second look.

READ THE NOTE →
[1][2][3][4][5]EVERY CLAIM IN THE RUN VIEW CARRIES ITS SOURCE
FIG. 28 — CITATIONS IN THE RUN VIEW

RELEASES · 29 OCT 2026 · 3 MIN

Console 2.3: citations in the run view

Every claim in a run now carries its source inline. A short note on the release, and on reading a run like a paper.

READ THE NOTE →
A DISTRICT, READ AS A SET OF OBLIGATIONS
FIG. 29 — A DISTRICT AS OBLIGATIONS

RESEARCH · 15 SEP 2026 · 11 MIN

Reading a city grid as a proof obligation

Grid planning, reframed: a district is a set of claims about flow, load and light — and each claim can be checked.

READ THE NOTE →