Outcome Verification Logic

Verify Your Trust With Sealed Proof

Billions move through construction draws on documents that are checked against other documents. GBaxOS checks them against a bank record the claimant could not have written, and seals the answer.

The party relying on the claim holds the verification.
The claimant never does.

Request Diagnostic Replay View Engine Specifications

$0 Custody
No funds touched or held.

Recomputable Re-derived from raw records
No access to our systems.

Deterministic Same inputs, same result
On any machine.

Scroll to explore

The Structural Vulnerability

Workflow Software Seals Its Own Records. Capital Carries the Result.

Draw software checks that submitted documents agree with each other. When the invoice matches the waiver, the file goes green. That confirms paperwork matches paperwork — not that money reached the trade the paperwork names. In the federal cases below, the paper was complete and the money went somewhere else, and nobody found out until liens, tips, or investigators surfaced it years later.

Federal Case · S.D. Tex.

False Invoices Against Draws

The Detamore Case

A Houston custom home builder submitted false invoices to the banks holding construction loans on single-family homes he was contracted to build, causing them to send funds to accounts he controlled. He obtained at least $1.5 million. Sentenced May 2025 to 51 months, with $2.3 million in restitution to more than ten victims. Each invoice was paid against the document itself. Nothing tied the draw to independent evidence that the money reached the parties named on it.

Federal Case · W.D. Wash.

Forged Subcontractor Invoices

The Bergevin Case

A Kirkland, Washington contractor presented homeowners with hundreds of forged subcontractor invoices between 2016 and 2019, using the real subcontractors' names and logos, for work not done as claimed. The forged invoices totaled $3,554,054 across 24 customers; restitution was approximately $4 million. It came apart when victims tracked down the named subcontractors and showed them the invoices. The subcontractors had never seen them. That comparison is the check — run by hand, by the victims, years after the money moved.

Federal Case · E.D.N.C.

The Claimant Was Also the Approver

The Garven Case

A branch vice president generated invoices in the name of a co-conspirator's company for subcontracting work never performed, from 2015 to 2020, and used his own authority to obligate his employer to pay them. Three defendants were ordered to pay $1,850,442 in restitution in May 2022; Garven received 48 months. Five years of invoices cleared every internal control, because every internal control reported to the person submitting them.

Peer-Reviewed Evidence

Verification Already Gates Capital

Heitz, Martin & Ufier · Journal of Finance, 2026

Using transaction-level data on roughly 30,000 non-syndicated construction loans, the authors found that negative inspection reports led to more draw requests being denied, and that both the occurrence and the threat of increased inspection corresponded to reduced defaults. Outside verification already changes what lenders do. That check covers physical progress. The payment leg — confirming funds reached the named trade — has no equivalent.

The Primitive

Reconciliation Without Touching the Money

The Outcome Reconciliation Anchor (ORA) is a stateless verification sidecar. It runs a four-step loop and produces a sealed verdict that recomputes from the raw records. It sits beside the ERP, the title platform, and the disbursement rail. It does not replace any of them.

Ingest

The declared obligation already in the file — an ERP export, a draw request, or a signed lien waiver.

Source

An outcome record the claimant cannot author — a cancelled check, a payee bank confirmation, or an ACH settlement record. Getting that artifact without taking custody of anything is the hardest constraint in the design, and it is what the Diagnostic Replays are built to test against real closed-project files.

Reconcile

The two records are compared on each declared dimension — amount, counterparty, and time window — producing one of three verdicts: GREEN, satisfied. AMBER, deficient. RED, divergent. A divergence is a measurement, not an accusation.

Seal

The verdict is sealed under a temporal anchor, with the reconciliation rule committed inside the sealed record. Any third party can re-derive the whole thing from the original files and the public keys. Later changes to the record become detectable.

The Proving Ground

Construction Draws Are the First Proving Ground

GBaxOS is built for funds-control operators, construction lenders, sureties, and direct owners — the parties that carry settlement risk. It is not a builder-facing product. Rather than asking for access to a contractor's accounting system, it tests submitted payment claims against bank settlement artifacts the claimant did not produce. Construction draws come first because the paper is dense, the money is real, and the gap is documented.

$0 Custody

No project funds are touched, escrowed, or held. We check the records. We never handle the cash.

Fully Deterministic

The same inputs yield the same sealed result on any machine, run by anyone. There is no model in the hash path and no judgment call in the verdict.

Recomputable Outside the Rail

The check runs outside the operator's workflow system, so a third party can re-derive the verdict without auditing the operator. Full independence means a second party holding its own key. That is the design goal and the next milestone, not something we claim today.

Current Milestones

Where This Actually Stands

A verification company that overstates its own state has already failed its own test. Here is the whole picture.

Live Now

What Is True Now

The ORA engine is a working Go prototype built against a written spec. It has replayed 14 draw pairs and every sealed verdict was recomputed independently from the raw records. That corpus is synthetic — built for the test, not supplied by a customer — so a passing check confirms the engine reconciled correctly against its inputs, not that any real claim is true. The venture is founder-run and self-funded.

Not Yet Done

What Is Not True Yet

No customers. No pilots. No revenue. No replay has been run on real closed-project files. The false-GREEN rate against adversarial documents has not been measured, and measuring it is the first use of the raise. A provisional patent draft exists and is unfiled.

Active Search

Pilot Search Open

Looking for 3–5 regional fiduciaries — lenders, sureties, or funds-control operators — to run a confidential Diagnostic Draw Replay under NDA on historical, completed projects. Closed files only. No live draws, no in-flight capital, nothing touching an active job.

[ CTO SEARCH ]

Technical Co-Founder Open

Looking for a systems engineer who cares about cryptographic primitives, stateless architecture, and non-custodial verification. Production hardening, key management, and closing the independent settlement source are the scope. Get in touch.

STATUS: PROTOTYPE