The Governed Onboarding Sequence
Onboarding isn't a form — it's a governed sequence. Capital is the root. The lender initializes capital governance first; each actor after them enters a project already contextualized, initializing the rails the next actor depends on. No actor ever sees a blank, ungoverned screen.
Live — wired & verified
Awaiting data — rail live, no records yet
Roadmap — not yet a live surface
STEP 1 · ROOTFUNCTIONAL
Lender — Initializes Capital Governance
Capital is the root of the OS. This step creates the canonical project and activates capital + draw governance.
What BuildPaid activates
Canonical project identity (single id)LIVE
Capital twinLIVE
Draw governance / verdictLIVE
Risk genome & compliance scanLIVE
GC cross-exposure detectionLIVE
Materials + supplier ingestionLIVE
Unlocks → the GC enters a governed project with capital rules, contract value, and compliance requirements already set — not a blank OS.
STEP 2 · STRUCTURE
GC — Initializes the Physical + Contractual Structure
Once capital exists, the GC defines the shape of the job.
Provides
SOV upload (governed, validated)
Subcontractor roster
Compliance plan
Field-log cadence
CO authority
BuildPaid activates
Validates SOV linesLIVE
Maps tradesLIVE
Field railAWAITING DATA
CO railLIVE
Closeout railROADMAP
Unlocks → Subs enter with their scope, compliance, and SOV lines already defined.
STEP 3 · DATA
Subcontractors — Initialize Labor + Field + CO Rails
Subs are the heartbeat — they generate the data that drives drift, risk, and capital posture.
Provides
Crew / labor profiles
Daily work logs
Compliance docs (COI, W9, safety)
Supplier list
CO submissions
BuildPaid activates
Labor railAWAITING DATA
Field narratorLIVE
CO operational propagationLIVE
Supplier onboarding contextROADMAP
Unlocks → field logs and deliveries become governed automatically — physical vs. financial divergence surfaces as evidence.
STEP 4 · DELIVERY
Suppliers — Initialize Delivery + Material Verification
Suppliers enter after subs — their deliveries map to sub scopes.
Provides
Delivery confirmations
Material tickets
Variance reports
BuildPaid activates
Supplier ingestionLIVE
Shortage / over-delivery governanceROADMAP
Supplier narratorROADMAP
Unlocks → field logs + COs + deliveries become a single governed chain.
STEP 5 · NARRATIVE
Alexis — Binds the Rails Into One Narrative
Alexis is the governance narrator, not an actor. She activates only after the rails exist.
Provides
One kernel, one source of truth
Actor-aware narration
Deterministic — no fabrication
Narrators
Capital narratorLIVE
Field narratorLIVE
Exposure narratorLIVE
CO narratorROADMAP
Supplier narratorROADMAP
Closeout narratorROADMAP
Unlocks → every actor hears the same truth, from the same kernel, in the same language.