Working research · October 2026

What did the check actually prove?

I study what happens when agents make work look finished: the sources they checked, the decisions they remembered, and the results that survive a second look. This is the live map of the questions, evidence, and public work.

01 Current theses02 Research03 Benchmarks04 Writing
01 / CURRENT THESES

Questions in play

Working questions, not conclusions. Each one points to a source or a next test.

01

Can a verification step catch the wrong approval?

Six documented cases show unsupported verdicts. The follow-up experiment—having a reviewer inspect the real object—has not run.

02

Can a fresh agent recover the current decision?

Stored files and a correct index are different from successful recall. A small search audit missed two of six ordinary questions; a controlled decision-recall test is still needed.

03

When output is cheap, what counts as progress?

Current work separates accepted work, elapsed time, and human review from token totals. The long-run comparison is a research direction, not a measured result.

02 / RESEARCH

Sources, studies, papers

The status here describes each work item. Acceptance, a public manuscript, and a proposed study are different events.

Accepted posterAIWILD workshop
2026

Who Verifies the Agents?

Six case accounts of unsupported verification verdicts. Accepted as a poster at the NeurIPS 2026 AIWILD workshop; the corrected manuscript is public on Zenodo. The source-inspection follow-up remains unrun.

Read the public manuscript ↗
Published preprintZenodo
11 October 2026

Where a typed decision model judges well

A case study of Jev on six decisions from one builder's tools. This is a public preprint, not a claim of peer-reviewed acceptance.

Read on Zenodo ↗
Source auditResearch in progress

What the bottleneck data can actually say

The frozen set has 663 queue events, but only 145 have direct evidence of human UI entry. Authorship is being separated before any claim about review behavior.

Read the related field note ↗
Protocol in preparationNo result yet

Can agents recall the right decision later?

The observed search miss was two of six ordinary questions in a small audit. The next study will test current-decision recovery across fresh sessions; its controlled result does not exist yet.

Measurement designNo result yet

Long runs: speed, tokens, and accepted work

The comparison is being framed around elapsed time, accepted work, and human review. No long-run effect estimate is published.

03 / BENCHMARKS

Measured runs

Competition scores belong here. They are account submission results, not paper results or an unpublished local proxy.

Submitted · public scoreARC KAGGLE / ARC-AGI-3
26.86

Latest completed account submission · 24 October

Official Kaggle account submission 57588648. This is a competition public score; the private 25 October notebook was not submitted at the last source check.

Competition destination ↗
Submitted · best public scoreARC KAGGLE / ARC-AGI-2
26.94

Best completed account submission · 10 October

Official Kaggle account submission 57052478. A later completed run scored 17.08; best and latest are distinct.

Competition destination ↗

Source: Kaggle account submission rows read 25 October 2026. Personal submission details may require account access; competition links open the public destination.

04 / WRITING

Where the work is told

Published writing has a direct destination. X drafts under review are not listed as published work.

PublishedSubstack

Where the tokens go: the end of maxxing

An accounting of token use across an agent fleet and what the output measure misses.

Read on Substack ↗
PublishedSubstack

Stress and agents: Garmin data

Heart rate and sleep beside agent use, with the one-person limit stated.

Read on Substack ↗
PublishedSubstack

Jev in the wild

Where a decision model helped on real choices and where agreement was too easy.

Read on Substack ↗
PublishedSubstack

The final way of writing

A note on writing from observed work, with the source object in view.

Read on Substack ↗
Browse 12 local experiments and other site writing

Reading

Finished enough to argue with. Each one rests on a number out of my own work that you can go and check.

where did the tokens go
I asked my agents to spend half my weekly allowance in one hour. The logs counted 284 million tokens, and 96.66% of them were cache reads. Across all my retained logs, $33,807 of use at list price, and about a third of it could not be tied to a product.
experiment · 2,802 words · 21 October 2026
my watch thinks i was resting
I put my Garmin heart rate and sleep over every coding agent session I have on record: 168 million tokens. With agents writing my average heart rate was 64.6, without them 66.2. Sleep after the heaviest days was 11 minutes shorter, which is noise. One person, 81 days, and three numbers I got wrong first.
experiment · 1,397 words · 7 October 2026
a decision model on my own work
Jev said yes to 62 of 63 events. I also tried it on contradictory notes, corrections and my own decisions. Seven graphs, some useful answers, and a much shorter list of jobs I would give it.
experiment · 2,214 words · 8 October 2026
the writing-down
Almost everything I write now is a prompt, typed to an agent, and none of it is meant for a person. So I graded six weeks of it, which is all the deletion timer left me. Prompts where I wrote down what done meant left something on disk 65% of the time against 39%. Then I checked whether knowing that had made me better, and it had made me worse. Then I found 193 days of my own record had already been deleted by a default I had never opened.
series page · 2,355 words · 4 September 2026
row four was always there
One night of coding agents left ten surfaces carrying a sentence their own cited source contradicts, across nine repositories, and not one was caught by the agent that wrote it. In the clearest case a merchant tool announced that no published figure priced an obstacle; the figure was row four of the same table it was already quoting two rows from. Then the piece itself said nine instances over a list of ten, and only a reader who had not written it counted the bullets.
essay · 4,550 words · 31 August 2026
open the page, not your memory of it
The practice without the story: one pass whose only job is to open every cited source, and which is not allowed to do anything else. Four steps, the four shapes that keep recurring, the one-line grep, and the three things that do not work: tests, rendering it and looking, and being careful.
method · 1,550 words · 31 August 2026
nobody edits their prompts
Prompts are the least edited words I produce, and they steer everything. So I graded six weeks of mine. The ones that said what done looks like left something durable behind 65% of the time, 64 of 99. The ones with no stated intent, 39%, 392 of 1,001. On a rerun six days later, counting only real commits instead, it is 30% against 17%. The same command runs on your logs.
essay · 2,579 words · 31 August 2026
my own readme
I gave six agent skills away and spent a week worrying I had sold my edge. Wrong worry. My whole working context lives in markdown I wrote, every model I ask reads those same files, and then they all agree with me.
essay · 1,802 words · 31 August 2026
did i just sell my skills
I put six of my agent skills in a public repo under an MIT licence and handed them to strangers. Then I stopped and asked the obvious thing: what did I think was mine in the first place.
essay · 763 words · 14 August 2026
source of truth for the agent era
Twenty done-claims, each re-derived from the artifact it was a claim about. Eighteen grounded, zero contradicted, two unverifiable. The two it refused to score are the reason the zero means anything.
essay · 1,020 words · 28 August 2026
I gave it away four days before I tried to protect it
Tomorrow I was going to file a provisional patent. This morning I checked where the specification's own reduction to practice lives, and found I had shipped it to a public repo four days earlier. The open-source instinct and the patent instinct were both mine, in the same week, in the same directory, and they never met.
essay · 995 words · 28 August 2026
the wrong object
The guard was right. The number it validated was true, of an object the real system had never seen. A live position ran at 5x cross-margin while the audit log honestly reported leverage 1. Nothing failed, nothing lit red.
essay · 1,264 words · 11 August 2026

Held back

Written, not posted, and the reason is a fact about the world rather than about the writing.

the demo and the number
Two kinds of contest, two ways to lose. A hackathon rewards a demo and a story. A leaderboard rewards a number and does not care who you are. They are not the same game, and the difference is the most useful thing either taught me.
essay · 855 words · 28 August 2026 · not posted
Four of its numbers went stale while it sat. It cites a score ladder topping at 58.05, a leader at 138.25 and a gap of 2.4x. Checked against the live public leaderboard on 28 Aug: the real figures are 68.535, 147.530 and 2.15x. Anyone can falsify it in ten seconds, and the piece argues for not trusting a number that went up. It goes back when it is regenerated from a run rather than hand-edited.
was the competition faulty
I lost a leaderboard competition and went looking for whether the competition itself was broken. It was not, and finding that out was the useful part.
essay · 1,729 words · 28 August 2026 · not posted
Its central number is a leaderboard score. The two submissions this hold originally named have since completed at 7.570 and 61.695, neither near the 68.535 the piece cites, so the reason it was written for expired without anyone noticing. Re-pointed on 28 Aug rather than lifted: three newer submissions are still pending and this hold had never heard of them. A hold whose reason has quietly expired is the one nobody re-reads.
Oscar Labs is a public research and writing space. Dates and statuses are checked against the linked destinations and the source records named above.