Skip to main content
BEN STONE

Vertical Operations

ProofRail

Construction & real-estate finance OS

No proof → no completion. Cognition and physics stay separated: AI reasons; ProofRail enforces gates; payments stay human-in-ledger.

Status
Production System
Role
Sole architect and builder
System Type
Construction finance OS (architecture-only public view)

Capabilities

  • AP intake with proof gates
  • Nightly audit gates
  • Draw build/send workflows (architecture)
  • Fee engine and reconciliation patterns
  • Human-in-ledger payments
  • Consumes InvoiceProof / AuditProof / VerifyAPI

Problem

Construction finance workflows move real money across entities and draw cycles. Autocomplete without proof is how bad completions become irreversible.

What I Built

ProofRail is a construction and real-estate finance OS with fail-closed SwarmSync proof at material actions. Law of the system: Cowork = cognition · ProofRail = physics · no proof → no completion.

This portfolio page is architecture-only. Client financial PDFs, draw sheets, and lien releases are excluded.

How It Works

Material workflows (AP, audit gates, draws, fees) require proof before completion. Payments remain human-controlled in the ledger system of record.

Why It Matters

Vertical finance OSes need stronger gates than generic chat automation. ProofRail is the construction instance of that rule.

Technical Depth

SPEC frozen for build; production use is operator-facing. Sibling pattern to FinanceOS; distinct from BookScout (AP email product).

Status

Production system with active development. No public product website. Architecture-only on this portfolio.

Evidence

Public third-party domains using the ProofRail name are not claimed here. No Visit Site button.