Visibility Is Verification

Table of Contents

A draft for the proposal shelf. Not submitted anywhere. Status: Essay, not a talk.

1. Pitch

When code is cheap to generate, the scarce thing is knowing which code is right. You find out by looking.

2. Abstract

Cheap generation moves the bottleneck from writing code to knowing which code is right. Reasoning about a diff does not scale to the volume an agent produces; seeing the program behave does. An argued essay, with a taxonomy of the instruments that make behaviour visible and the findings behind it.

3. Audience, format, venue

Audience
Readers of an essays track; engineering leads.
Format
Essay plus talk. Not a 45-minute practitioner talk.
Where
Onward! Essays at SPLASH 2027 (a guess at fit; the SPLASH notes here do not record what that track accepts).

4. Review

Both reviews say the same thing: a slogan title and a taxonomy read as "no demo" to a practitioner committee, and the material is better used as framing for The Failure That Looks Like Success. One of the three findings the note leans on carries a disputed verdict; settle it or drop "three" before using it. A talk title, if one is wanted: "You Can't Review Your Way Out".

5. Backing

Public repositories:

  • None public. Concept only.

Notes on this site: