Coding

    Untested

    Describe software, get a generated project. Routing exists; the engine is not running anywhere.

    Coding is meant to turn a requirement into a running project. It is the most ambitious space and the one where the gap between what was documented and what we can currently verify is widest.

    The two modes

    Autonomous pipeline
    A requirements stack goes in, a complete project comes out — generated, containerised, tested. Designed around a multi-agent pipeline with convergence validation rather than a single generation pass.
    Conversational coding
    You describe what you want and watch it appear. Comparable to browser-based app builders, except not restricted to web technology — the engine is language-agnostic by design.

    The documented pipeline

    Specification, then domain slicing, then parallel generation across agents, then merge and validation, then end-to-end testing, then deployment. Coordinated over an event bus with a multi-phase convergence check, and a set of convergence modes trading thoroughness against speed.

    Generated code is meant to go to your own git. Whether the code you send to a model provider may be used for training depends on that provider and your terms with them, not on us.