Synthetic buildBuilding something completely new

    Hello World

    A single-page application from a one-page RFP

    The smallest possible project, run end to end, to show the method with nothing to hide behind.

    The situation

    Every method should be shown on something small enough to read in full. Hello World is the whole pipeline — specification, criteria, build, gate — run on a one-page request, so that every artifact fits on a screen and nothing is summarised.

    The specification

    The request is one page. The specification written from it is the smallest governed specification the method produces: every requirement traced to the sentence in the request that produced it, every criterion stated so that it can pass or fail, nothing added that the request did not ask for.

    What was built

    The request asked for a single HTML file with no backend, no build tools and no frameworks: at least twenty languages, each in its own script, shown one at a time with animated transitions, right-to-left scripts handled correctly, a configurable hold time, and a developer configuration object. Five enhancements were listed as optional and priced separately: an ambient background animation, a language label, pause on click or spacebar, a spoken-greeting accessibility mode, and a settings panel.

    What was built is a single file of about 32 KB with no external requests: twenty languages in native script, right-to-left handling for Arabic and Hebrew, three transition modes, and all five of the optional enhancements. Sixteen requirements, eleven core and five optional, were written from the request; every one is implemented. It is the application linked from this page.

    What the receipts say

    Two gates stood between the request and the application. The package gate, which checks the generated specification against the request before anything is built, returned GO WITH GAPS: of thirty-five stated requirements, thirty-four were covered and one, the request’s subjective aesthetic wish, could not be made checkable. The build gate returned ACCEPT: sixteen of sixteen requirements implemented, every acceptance criterion satisfied.

    The same specification was then run again, five days later, through a later vintage of the pipeline. Same two verdicts: GO WITH GAPS at the package gate, ACCEPT at the build gate, sixteen of sixteen. Two governed cycles, two acceptances, from one page of request. That is the reproducibility the method is meant to deliver, shown on the smallest thing it can be shown on.

    One honest caveat. The gate that graded both cycles sampled a subset of the criteria rather than grading every one. A third cycle, graded in full, is running now; this page will carry its result when it lands.

    The receipts

    The company is invented. The numbers are not: the estimate, the price and the measures of the software are as they stood.

    Priced the conventional way

    $3,555

    ~24 hours

    the M6 estimate: the request priced at standard AI-assisted rates, core application plus five optional enhancements

    What it is

    Not a priced project. This is the demonstration build: small enough to read in full, run the same way as everything else.

    Open the application it produced

    16

    Requirements, every one implemented

    eleven core, five optional

    20

    Languages, each in its own script

    right-to-left scripts included

    2

    Governed cycles, both accepted

    same specification, five days apart

    Behind these numbers is the run itself — its gate verdicts, scorecards, rulings and phase reports, and how long and how much it took. All of it is available for review when you want to check it. Ask, and we will walk you through it.

    A read-only snapshot: the built code, its tests, the specification and the reports. We review each request and send a download link.

    This build is evidence for one door on the homepage: Building something completely new. The method behind it is the same for every project.

    The other builds

    • Kindred TableSynthetic build

      A multi-role marketplace, regenerated from its spec eight times, because when building takes hours the spec is where you iterate.

    • Rincon PhotonicsSynthetic build

      An enterprise specification taken through the full cycle: six phases, every one gated, accepted after remediation, with the record of every no along the way.

    • VeeFor a prospective client

      Built before any contract, for a real prospective client, so the conversation could start from working software rather than a proposal.

    © 2026 Vertical Horizon AI LLC. All Rights Reserved.

    TermsPrivacy