Carfax for buildings.

What gets recorded

Every module entered into Keystone carries:

• Provenance — manufacturer, factory, build batch, materials lot
• QA — weld inspection, third-party inspection, defect log
• Resilience — seismic class, wildfire resistance, hurricane rating
• Value attributes — net-zero status, embodied carbon, energy posture
• State — raw → certified → completed → in-structure
• Auto-generated — module code (sequential, starting 18472), hash, KeyScore

The KeyScore — 0 to 99

A single number every downstream engine reads. Computed by a Postgres function + trigger at insert / state change. Base 40, with weighted adjustments for weld inspection (+), third-party inspection (+), net-zero (+), seismic class (+), embodied carbon penalty (–), and value state (advancing +).

KeyScore ≥65 = eligible for Capital Rail pools.
KeyScore ≥72 = eligible for gain-on-sale tranching.
KeyScore ≥80 = investment-grade for the Modular Index.

Lifecycle events

Every change to a module's state emits an immutable lifecycle event. Inspections, ownership transfers, transport, set, certificate of occupancy — all hashed, all auditable, all available to the downstream engines.

How data flows in

• Manual form — for the first 10–100 modules; click through the registration screen
• CSV bulk import — for factory backlogs; template + chunked insert
• Ingest API — for live factory MES integration
• IoT / MES nodes — for cyber-physical-system integration (roadmap)

Who pays for it

The Registry itself is the cold-start engine. Toll events are auto-metered at every insert: $100 per module, $10 per lifecycle event, $5 per pool inclusion, $5 per disbursement, $5 per insurance policy. Toll revenue is the predictable per-event SaaS base; the other four engines layer on as the registry grows.

The module gets recorded once. Everything else compounds.