Route Relationship
`/finance` is the chooser. `/capital-os` runs capital control. `/financial-platform` runs finance analysis.
Context Source
standalone
Live Project
No project attached yet
Finance | Product Entry Surface
Finance is now the compatibility entry route that points you to the right standalone product.
Use this route when a user says “take me to finance” but has not yet chosen between the capital-control surface and the finance-analysis surface. `/finance` is intentionally not a third overlapping product.
Launch Behavior
Context from optimizer, handoff, parcel, or project can still arrive here first. This route simply helps the user pick the correct standalone product next.
Choose Surface
Two real standalone products now sit behind the finance entry route.
This route should remove confusion, not add it. The cards below make the product split explicit so users know where to go for each task.
Capital control and release operations
Capital OS
Use this when the job is about governed draw workflows, release readiness, evidence-backed payment control, and lender execution.
Finance analysis, underwriting, and scenario comparison
Financial Platform
Use this when the job is about budget basis, pro forma, underwriting, pricing analysis, and financial packeting.
Context
Optimizer, handoff, and project context still land here cleanly.
Project
No project attached yet
Scenario / Optimizer
No scenario context attached
Handoff
No handoff attached
Capital OS
Use `/capital-os` when the job is operational, release-governed, and tied to evidence-backed execution.
Financial Platform
Use `/financial-platform` when the job is modeling, underwriting, pricing analysis, or financial packeting.
Project Finance
Use `/project/[id]/finance` for the deeper project control room when the job needs full permissions and execution depth.