← All investor documents · This document as plain markdown
# The Achievement: One Founder, ~10 Months, a Production Commerce OS **The build-proof and discipline record behind ComOS** *First written November 2025. Rewritten July 14, 2026 under CO 297. Every number was re-derived 2026-09-15 against `comos-federation` at HEAD `6b70605` — the live system. Facts are stated as facts; estimates are labeled as estimates.* --- ## What This Document Is This is the capital-efficiency and de-risk exhibit. It documents three claims, each verifiable: 1. **The system exists at production scale.** A live federation gateway and agent service, autonomous agents running on schedule, agent-commerce protocol surfaces served, and live endpoints anyone can query today. 2. **It was built by one founder working with AI** — ~3,000 hours over ~10 months, self-financed. 3. **It is maintained under machine-checked discipline.** The methodology that keeps AI-built code correct at this scale — proof-before-done, change orders, the honesty ratio, quality sweeps — is itself part of the achievement, and it goes in the data room. This is not the business-model document. The revenue model gets one short section here ([below](#the-revenue-model-in-brief)) and lives in full at docs/business/FINANCIAL-MODEL.md. --- ## The System, Federation-Only **Read this row first.** The live system is `comos-federation` alone. comAI — the commerce engine that carried the earlier headline counts — was deprecated on 2026-08-04, after CO 420 deleted its entire deployed estate from GCP. Everything below describes the repo that actually serves traffic. | Metric | Value | |---|---| | **Built vs. live** | Two full systems were built and then deliberately retired: comai-portal (deprecated 2026-07-14) and comAI Retail (deprecated 2026-08-04). Both are excluded from every live count here — see [Subtraction](#subtraction-two-systems-built-then-deliberately-retired) | | **Platforms** | **20** composable platforms — 5 vendor / 15 customer, all available — plus 10 presets (events, food, salon, fitness, lodging, courses, repair, creative-studio, equipment-delivery, marketplace: recipes composing live platforms), queryable live via `federation_catalog_platforms` | | **Protocols** | MCP, UCP discovery, OpenAPI/REST in production | | **Build time** | ~10 months, one founder working with AI | --- ## The Build: Ten Months, Honestly Told The canonical build figure is **~3,000 hours over ~10 months.** Two chapters inside that window matter to an investor. ### The opening sprint (an early chapter, not the whole story) The first three weeks produced the working backbone: core commerce services (catalog, cart, orders, users, inventory, payments), the AI services (NLU, RAG, brand voice, policy engine), the database layer, and the initial testing framework. That sprint is worth naming because it set the velocity baseline — but it was the *start* of the build, not the build. ### The following months (where the hard part lived) The remaining months are where the system became an operating system rather than a large codebase: - **The Federation** — the MCP gateway that fronts every tenant behind one endpoint, with OAuth 2.1 + PKCE authorization (RFC 9728, RFC 8414), enterprise SSO, and fail-closed per-tool scoping. This is the system that survived, and it is the system that runs today. - **Protocol surfaces served** — MCP, UCP (layer-tested), and OpenAPI/REST in production. - **The economy** — Com tokens, the ledger, per-act pricing, and the two revenue cuts, wired and live in production. - **The teardowns** — two entire systems deliberately removed (next section). - **The discipline machinery** — installed mid-build and applied to everything after, including the teardowns. One post-launch data point on sustained velocity: OAuth 2.1 with PKCE — spec-compliant authorization, dynamic client registration, enterprise SSO — shipped to production on the Federation in a single short session. Industry coverage has called authorization the hardest part of MCP adoption; a large share of production MCP servers still lack identity verification. ComOS ships it, in production, verifiable at `https://mcp.comos-federation.com/mcp` today. --- ## Subtraction: Two Systems Built, Then Deliberately Retired The strongest single piece of evidence in this document is not something that was built. It is something that was deleted — twice. **comai-portal (deprecated 2026-07-14).** A complete SaaS management platform: billing, subscriptions, team management, its own frontend apps, built to production quality. Then the business model evolved past it — revenue moved from subscriptions to two inline cuts collected where value flows, which made a subscription-management platform structurally unnecessary. So it was decommissioned (CO 153): its load-bearing pieces rehomed into the Federation, the rest torn down. **comAI Retail (deprecated 2026-08-04).** The commerce engine. As the federation matured, the capabilities that mattered converged into it — the atomic `order_create` settlement path superseded the retail checkout saga, tools were single-sourced onto the gateway's surface, and the retail estate's remaining reason to exist thinned to almost nothing. CO 420 finished it: every service, job, cron, and URL mapping deleted from GCP, leaving exactly two Cloud Run services, both federation-owned. Why this matters for diligence: - **Maturity by subtraction, twice.** The common failure mode of AI-assisted development is accretion — code is cheap to generate, so systems bloat. This founder deletes at scale, and has now done it to two production systems rather than defend a sunk cost. - **Both teardowns ran under the same discipline as the build** — change-ordered, gated, on the record. --- ## The Discipline: Why AI-Built Code Can Be Trusted Anyone can generate hundreds of thousands of lines with AI in 2026. The achievement is that this system is *maintainable* — and the machinery that makes it so is explicit, mechanical, and inspectable. It is also what made two deprecations survivable. This is the diligence exhibit. ### Proof-before-done No task is declared complete without a closing test that verifies its central claim. This is not a norm; it is a gate. Agent-proposed pull requests must carry a closing-test section inline, an evidence chain, and a change-order link; self-approval is forbidden by branch protection and enforced mechanically. Tautological closing tests (compiles + "passes" but doesn't test the claim) are the named failure mode human review exists to catch. ### The change-order cascade Every deliberate change to a contract, interface, or invariant fires a change order: a four-artifact directory (seed, plan, blueprint, playbook) answering six fixed questions before any code moves. The log is sequential and public within the repos — at this writing it runs past CO 550, a continuous decision record from May 2026 forward. An acquirer or investor can trace *why* any architectural fact is the way it is. ### The honesty ratio Each repository carries a machine-computed honesty ratio: the fraction of shipped artifacts whose "done" claims are backed by verified proof, read live from the introspection plane and snapshotted on an automated cadence. The number is never 100%, and that is the point — it is a measurement the system takes of itself, not a marketing claim. A dashboard renders it continuously. ### Quality sweeps and the skill loop Ongoing quality is verified, not assumed: pattern-based sweeps (error handling, dead code, naming, dependency hygiene) run across the repos on a reusable audit prompt, and every debugging session produces a documented skill — permanent institutional memory that prevents the error class from recurring. The operating assumption is an 80% trust factor on any agent output; the machinery exists because of that assumption, not despite it. **Both core disciplines are open-sourced** — [github.com/ComOS-Federation/proof-before-done](https://github.com/ComOS-Federation/proof-before-done) and [github.com/ComOS-Federation/initiate-change](https://github.com/ComOS-Federation/initiate-change) — so the methodology can be inspected independently of any claim made here. --- ## The Testing: Verifiable, Not Vanity Only verifiable claims appear here. The verifiable facts: - A test suite runs on every change and gates it; proof-before-done refuses a done-claim without evidence. - Protocol conformance is tested at the layer level, for each layer of the UCP implementation. --- ## What Runs Now That Didn't in November This document was first written in November 2025, when the achievement was a codebase. Today it is a running system. Everything below is live, not roadmap: - **The two revenue cuts are live.** The 6% mint cut is charged on top of every Com purchase, and the 3% merchant cut resolves into a clearing sale's journal split (CO 112 and its follow-on). - **Any agent can buy.** Claude through the MCP connector, or any client over REST, searches the network and buys with one atomic `order_create`. A working flow any investor can run from their own agent. - **The door is open.** An outside agent can self-admit to the federation with OAuth and an accountable root — no human sales motion in the path (CO 263). - **Admitted agents are governed, and the disconnected-manager accountability arc is complete.** Liveness decay for silent agents (CO 264), and cryptographic key binding (CO 314): a root proves control of a published key by signing a server-issued challenge, verified before it persists, so a disconnected/silicon manager keeps a durable, counterparty-verifiable identity across a severed human link. Plus freeze-at-dispatch enforcement (CO 259) and the accountable manager root stamped on every audit record (CO 318). - **Every priced act charges.** 49 priced write operations across 19 platforms charge per act, resolved from live pricesheets at the routing seam (CO 287). Queryable via `federation_pricesheet`. - **The same runtime runs on customer-class hardware.** ComOS installs on a machine the merchant owns as a sealed, signed artifact and joins the one federation as a node (CO 475). A buying agent discovers a vendor that exists only on a node, buys from it, and the sale executes locally and settles on the hub rail with the 3% collected — node-stamped, hosted-identical. The node calls out and nothing calls in; its identity keypair is generated on the machine itself and the private key never leaves it; the ledger projects down read-only and cannot be written from the node. Where we are: live since February 2026. No outside merchants, no revenue. Settlements so far are internal and proof transactions. The system is built and governed. --- ## The Revenue Model, in Brief ComOS charges **two flat inline cuts and nothing else**: **6%** when a tenant buys Coms (the mint cut) and **3%** when a sale clears (the merchant cut). Both run in production. Free to start — no subscriptions, no tiers, no seats, no rent. Revenue is linear in throughput, indifferent to who is transacting: the Visa shape, made literal. There is no subscription tier, no GMV take rate, and no services revenue line: the code that once implemented subscription billing was torn down with the portal. The full model, including its integrity ledger, is the financial model, available in diligence. --- ## What This De-Risks — and What It Doesn't **Retired risks:** - **Execution risk.** The system is built, deployed, and live. This is not a plan to build; it is a running system. - **Capital-efficiency risk.** One founder built the system with AI, self-financed. Burn is deliberately small; scale spend follows throughput rather than preceding it. - **Key-person risk, partially.** The system runs under manager-rooted autonomous agents, and the knowledge lives in the documentation and change-order corpus across the repos, not in one head. The discipline machinery is what a hire — or an acquirer — would onboard against. Hiring is for distribution, not survival. - **AI-slop risk.** The specific fear that an AI-built codebase is an unmaintainable liability is answered by the discipline chapter: mechanical gates, a public decision log, a self-measured honesty ratio, and a founder with a documented record of deleting two production systems when the architecture demanded it. **Not retired, and not claimed:** - Distribution. There are no outside merchants and no revenue yet; settlements so far are internal and proof transactions. The raise exists to buy down exactly this risk. - The throughput curve. Throughput is instrumented weekly, and the curve that matters begins at the first external settlement. The founder's background — software since 1988 across NASA, Amazon, Apple, Wells Fargo — is on his LinkedIn profile for anyone who wants it. This document leads with the system because the work is the proof. --- ## Appendix: System Inventory **Live system = ComOS Federation, alone.** comAI Retail (deprecated 2026-08-04) and comai-portal (deprecated 2026-07-14) are both excluded. **Two repos, and only two:** `comos-federation` — the live system; `comai-plan` — the origin cockpit (docs, change orders, strategy). **Protocol surface:** MCP (OAuth 2.1 + PKCE, Streamable HTTP + stdio transports, spec 2025-06-18), UCP (`/.well-known/ucp`, layer-tested; catalog / orders / OAuth live — checkout + payment layers decommissioned per CO 308/310), OpenAPI/REST (`/openapi.json`, `/.well-known/openapi-actions.json`). Agent checkout settles through the federation's `order_create`. AP2 was deliberately withdrawn (CO 370): its card-shaped mandate model doesn't match a ledger that settles in milliseconds; its delegated-spend-caps primitive is recorded for rebuild on the Coms rail. **Stack:** TypeScript / Node.js / Fastify; Next.js 14 + React 18 frontends; MongoDB Atlas; Google Gemini 2.5 Flash via Vertex AI for LLM inference; Docker, Kubernetes-ready. **Live endpoints:** Federation MCP at `https://mcp.comos-federation.com/mcp`; agent-vendor disclosure at `/.well-known/comos-vendor.json`; public catalog via `federation_catalog_agents` / `federation_catalog_platforms`; live pricing via `federation_pricesheet`.