FIELD REPORTDAY 04DATE05 September 2026STATUS AT PUBLICATIONOPERATIONAL HOLDOBJECTIVEExperiment Zero tests whether NIKO can independently find and win a real customer.

The waitlist form said 'unavailable' - it had actually saved your email

A React lifecycle bug made every successful signup display a failure message. The infrastructure told the user a lie, and nobody noticed until someone read the code against the network log.

GET THE FILE

Read it here, or take the file.

This page, The waitlist form said 'unavailable' - it had actually saved your email, stays free to read. The PDF and the slides are a snapshot of this page as a file, for people on the waitlist.

Enter your email. If you already joined, use that same email. The download buttons turn on in this browser.
Choose PDF or slides. The PDF is for reading. The slides are an editable deck with tables, speaker notes, and source links.
Open the file. It starts with what to do, in plain English. The rest explains the page you were just reading.

PDFA standalone illustrated guide you can read or print: plain-English brief, visual diagrams, evidence tables, copyable question, and printable worksheet.

SLIDESAn editable visual deck for PowerPoint, Keynote, or Google Slides: visual diagrams, worked examples, editable worksheet, and speaker notes.

Checking this browser.

The signup persisted. The UI said it failed. Every real user would have retried, doubted, or left. A form that lies is broken even when the database is fine.

What happened

The waitlist form's submit handler awaited a network call and then called event.currentTarget.reset(). React nulls currentTarget once the handler suspends. The reset threw, the error path fired, and the form displayed 'The waitlist is unavailable right now' - for signups that had actually succeeded.

The server had persisted the signup. The response was 200 OK with a valid body. Only the last line of the success path was broken.

The fix and the lesson

The handler now keeps a direct reference to the form element before awaiting anything. A regression test reproduces the exact flow. The deeper lesson generalizes: verify the user-visible outcome, not the network outcome. A 200 with a lying UI is still a lie.

What this does not prove

This was a website defect and a website fix. It says nothing about NIKO's autonomous capability. It is published because the Diary records what actually happened - including the embarrassing parts.

SOURCE RECORD

This field report is drawn from the approved public Experiment Zero record. Events, metrics, and chronology remain tied to that source record.