Reproduce it yourself

We do not ask you to trust the claim. We ask you to reproduce it.

The figures below come from Daynought's own execution audits. The live session that follows lets you check the central claim yourself, on a brief of your own.

110Execution auditsWith 104 written records.
53Business domainsGrouped by industry further down this page.
179Automated gatesAll passing on the current engine, confirmed 22 September 2026.
9.7Best score out of 10Marina operations, 24 August 2026.
8.8Latest score, provisionalPharmaceutical quality management, 28 September 2026.

Figures as of 28 September 2026. These are Daynought's own audits: every application is executed, never scored by reading.

01

The live reproduction session

Run on the production system, in front of your team, on a brief of your choosing.

  1. Bring a brief

    Under NDA, you bring a brief of your own, or choose one.

  2. Get access

    Access to the invite-only platform is granted in advance.

  3. Generate

    The brief is pasted in and Generate pressed. Six stages show as they happen, typically 45 to 75 seconds.

  4. Read the run page

    The run page shows the brief, what was read, what was ruled out, and what the engine completed.

  5. Download twice and compare

    The application is downloaded twice, each copy built fresh, and the two files are compared with any standard tool. They match exactly.

  6. Run the check

    A check included in every export confirms the application matches what it was built from. Change one character and it fails.

  7. Run it

    Optionally, you run the application's own pipeline and start it with one command.

02

The failure record

The corpus keeps its failures. Every low score is published with its cause, the fix, and the re-run.

  1. Field service management

    Re-run9.4

    Cause and fixA record whose name clashed with a system name was dropped without warning. Clashes are now renamed, never removed.

  2. Automotive dealer network

    Re-run9.4, then 9.6

    Cause and fixAn apostrophe in the application title broke the build. Fixed.

  3. Marina operations

    Re-run9.6, later 9.7

    Cause and fixOne page layout variant failed to build. Fixed.

  4. Crane hire

    Re-runProven on the next new domain at 9.6

    Cause and fixA record declared with no fields broke the build. Fixed the same day.

  5. Social housing repairs

    Re-run9.6 the same day

    Cause and fixA business record named "User" clashed with the system's own user table. Fixed.

  6. Banking scam claims

    Re-runBuilds, 8.6, then 9.1

    Cause and fixA missing required value stopped the build. Fixed.

  7. Third-party risk management

    Re-run8.8, then 9.4

    Cause and fixWords in an "out of scope" sentence switched on excluded features. Fixed.

  8. Materials testing laboratory

    Re-run9.4

    Cause and fixReserved names produced duplicate records. Fixed.

  9. Pharma cold chain

    Re-run9.6

    Cause and fixPayment tables appeared in an app with no payments. Fixed.