Capital OS | Standalone Workspace

Capital OS is the operating-system level capital workspace for governed release, lender readiness, and evidence-backed funding control.

Use Capital OS when the work is operational and release-critical: draw command, cost readiness, compliance, packet governance, evidence, and payment control. This route stands on its own and still bridges cleanly into project finance when live execution context exists.

Start Capital OS Create Project Finance Workspace Open Financial Platform

Workspace Map Launch Readiness Live Workspace Route Relationship

Launch Readiness

Standalone exploration mode

/capital-os stands on its own even without project context. It should still teach the product clearly and provide a path into a live finance lane.

Project workspace linked

No project linked yet. Open from a project or attach ?project_id=...

Scenario basis attached

No optimizer/pro-forma context yet. Attach scenario_id, optimizer_run_id, or parcel_label for launch readiness.

Handoff packet attached

No handoff packet linked yet. Attach handoff_id when the package is ready for execution.

Workspace Identity

/capital-os is a real top-level studio route with a distinct job to do.

Context Source

standalone

Live Project

No project attached yet

Capital Command Center

Capital OS organizes the funding chain around control, readiness, and governed release.

This is the operating-system layer for capital decisions. It is where budgeting, release readiness, draw operations, lender packets, and evidence-backed execution converge.

Governed draw and release operations

Draw Command

Pulls draw readiness, payment authority, inspections, conditions, and blockers into one operator lane.

Owner, builder, and lender teams can work the same governed draw chain from one surface.

Open Lane

Pay apps, waivers, and compliance gating

ClearChain

Keeps pay apps, waiver proof, retainage, and no-compliant-docs-no-pay controls attached to capital release.

This is the Flashtract/Textura displacement lane, not a side spreadsheet.

Open Lane

Cost, scope, and schedule-of-values basis

Budget Studio

Turns horizontal and vertical scope into a funding-ready budget basis with measured vs inferred quantity signals.

This is where Labs5/Labs4 quantities become lender-defensible cost basis.

Open Lane

Economics and release-aware capital math

Pro Forma Engine

Runs capital stack, revenue, IRR, NPV, profit, and release-gate-aware scenario outputs inside the same control plane.

Capital math stays connected to actual release logic instead of drifting away in a workbook.

Open Lane

Packets, conditions, and readiness

Lender Room

Makes lender packet readiness, approvals, comments, and audit history a first-class operating surface.

Capital providers should not need a different portal to see the truth.

Open Lane

5D scope-to-cost linkage

Assembly Map

Binds BIM and plan objects to cost assemblies so scope, trade rollups, and funding basis stay connected.

The 5D cost layer keeps lender conversations tied to actual scope instead of broad categories.

Open Lane

Evidence-backed release readiness

AEGIS Proof

Connects inspection outcomes, evidence, and compliance state directly to draw and payment release behavior.

Money moves against verified reality, not just uploaded documents.

Open Lane

Deterministic finance operator

Bob CFO

Surfaces action plans, blockers, lender summaries, and governed recommendations with assumptions and traceability.

Bob is the operator layer over finance controls, not a generic chatbot.

Open Lane

Release Readiness

Optimizer and handoff context should converge into a release decision path here.

Capital OS should tell the operator what is already attached, what is blocking release, and when the route is ready to hand off into live draw or payment operations.

Optimizer Context

No optimizer context attached

Handoff Context

No handoff packet attached

Standalone Behavior

Graceful even with no project attached.

This surface is designed to become the command layer once `project_id` exists. Until then, it still explains the product clearly and provides a real entry into the governed funding stack.

Start Capital OS Sign in and come back here with `project_id`, `scenario_id`, or `handoff_id` for live launch readiness.

Live Workspace

Summary, cost, pro forma, lender pack, and payment operations become live when project context is attached.

With project context attached, Capital OS renders the same core finance surfaces used in the project control room, with release operations visible from the standalone route.

What becomes live first

Summary, cost, pro forma, lender pack, and payment operations become live when project context is attached.

This surface is designed to become the command layer once `project_id` exists. Until then, it still explains the product clearly and provides a real entry into the governed funding stack.

Project Bridge

Project-embedded finance access still stays intact.

Use `/project/[id]/finance` for deeper permissioned execution, uploads, and full operator workflows when the job is already live inside a project.

Open Project Bridge

Capital OS Role

Use `/capital-os` for the operating-system level capital workspace: command center, release readiness, draw control, and lender execution.

Project Route

Use `/project/[id]/finance` for deeper permissioned execution, uploads, and full operator workflows when the job is already live inside a project.

Finance Entry

Use `/finance` only as the compatibility entry surface that points people into Capital OS or Financial Platform based on the job they are trying to do.