Capability / Engineering · requirements, build, review, proof
Built.Then proven.
Every delivery follows the same line: you approve what will be built, engineering agents build it, an independent reviewer can refuse it, and a verifier proves the package before it reaches you.
Fig. 07 — The line
Choose a button to read its note, or press Send one through.
From approved to proven.
Our build line turns an approved specification into tested, packaged software with a receipt. AI engineering agents do the planning, building and reviewing. People decide what gets built and accept the result.
Nothing ships on say-so.
Custom software is usually slow, and "done" usually means "it worked once on the developer's machine". Code written by AI raises the stakes: it is fast and it is confident, whether or not it is right. The answer to both is the same: nothing ships on anyone's say-so, human or AI. It ships when an independent check has proven it.
78 deliveries, each with a receipt.
78 packaged deliveries across 55 projects, counted from the delivery records, every one with a passing acceptance receipt bound to the fingerprint of its archive.
- Deliveries
- These are our own products and internal projects: 39 web applications, 16 services and APIs, 12 command-line tools, 8 iPhone builds and 3 bots.
- MayaClerk for iPhone
- MayaClerk for iPhone went down this line. The reviewer refused it four times before it passed; the final build passed 155 of 155 tests in the iPhone simulator.
- This website
- This website came off the same line. Its first ten accepted deliveries each passed 23 of 23 acceptance checks, and the independent reviewer refused six candidates along the way.
- Sixteen kits
- A library of sixteen reusable kits: interface components, knowledge and search, memory, voice, model gateway, companion, identity and sign-in, billing and metering, avatar, three.js scenes, an Unreal Engine bridge, web research, real-time events, source explorer, workflow, and a reference companion stack.
- Reports
- Reports that keep three things apart: built, tested in the simulator, and used on a real device.
Your stack, your gates.
The technology and the hosting. The acceptance checks: your own requirements become checks the verifier runs. The review gates: add your security or compliance review to the line. The parts: which kits a project starts from.
Delivered with its proof.
A source package with its receipt, deployed and run by us or handed over to your team. You approve the requirements before anything is built and you accept the result at the end.
The record.
The figure above. The MayaClerk for iPhone record (four refusals, then 155 of 155). This site's own record (its first ten accepted deliveries, 23 of 23 each, six refusals along the way).
The same pattern, separate agents with a check between them, also runs inside a product: see MayaClerk's Dossiers.
Have something to build?
What "independent" means here.
The reviewer is a separate run with its own copy of the code and a veto; the verifier is not an AI at all. Agreement between a builder and a reviewer is never taken as proof. The checks are.