What the model calculates
- Operating and revenue assumptions
- CAPEX, OPEX and escalation
- Senior debt and sponsor funding
- Tax, depreciation and reserves
- Cash waterfalls and financial statements
- Distributions, returns and coverage metrics
FINCO Protocol / Documentation
Start with the task you are trying to complete. FINCO keeps model outputs, company fundamentals, market observations, execution-aware analytics and evidence lineage separate so each number keeps a clear meaning.
Start here
Product map
You do not need to understand every internal boundary before using FINCO. The important rule is that a project calculation, a company financial metric, a market reference and an executable quote are not interchangeable facts.
| Surface | Primary question | Current scope |
|---|---|---|
| Model | What are the economics of the asset? | Solar and Wind: mature production workflows. Data Center (A3.1) and EV Charging (A3.2): implemented and supported modelling workflows. Storage: reference view only; working-copy runtime not released. |
| Radar | What is the market, company or macro context showing? | Stocks, Crypto, Economy and R-LIVE read-only intelligence surfaces. R-LIVE provides on-chain reference observations for a source-proven approved identity universe; observations are not executable prices. Execution simulation is analytics only; no order submitted. |
| Run Integrity | Is the committed run internally consistent? | Read-only checks over committed Last Run evidence (Sources & Uses, balance sheet, debt rollforward, debt-service consistency, CFADS/DSCR integrity, DSCR feasibility, unfunded cash, sponsor-flow consistency). Shipped; not economic truth. |
| Signed Run | Did FINCO sign these exact committed bytes? | Ed25519 FINCO_RUN_CERTIFICATE_V1 issued from a committed Last Run only; config-gated, fails closed. Off-chain. Not FINCO Verify; not economic truth. |
| Verified Assets | How does a model run connect to market identity? | Composed FINCO_VERIFIED_ASSET_V1 records: model economics + run certificate + Radar evidence + $FINCO protocol metadata. |
| $FINCO | How do I access protocol capabilities? | Protocol access and service-entitlement infrastructure is implemented. The $FINCO token is not yet launched. Token access is not a calculation authority and does not change model outputs or evidence truth. |
| API | How can software read or run FINCO capabilities? | Beta Model reference/read/preview/run and Radar read/simulation endpoints. |
| Evidence | What produced this value and how should I interpret its state? | Source, snapshot, period, lineage, freshness and deterministic verification concepts. |
FINCO Model
Model is a financial calculation workspace. The most important distinction is Working versus Last Run: an editable value can be saved and still differ from the assumptions used in the last committed calculation.
Open a reference model or an existing working project. Solar, Wind, Data Center and EV Charging are the current supported modelling verticals.
Edit project assumptions in Revenue, CAPEX, OPEX, Financing, Tax and related sections.
Commit one deterministic calculation. The resulting snapshot becomes the Last Run authority for outputs tied to that run.
Review decision KPIs, cash flow, debt, coverage, statements, distributions and returns.
Compare changed assumptions without treating an un-run working edit as a committed result.
Use run-bound export paths when an artifact needs an explicit calculation authority and lineage.
For a full formula-level description of every calculation, see the Model Methodology page — it traces every formula to its exact production source file and includes a worked example for the Generic Solar Reference model.
Canonical Solar, Wind, Data Center and EV Charging reference models are synthetic product references. They are useful for onboarding, scaling previews and stateless API runs; they are not market benchmarks or a representation of a specific real project.
Reading the outputs
| Output | How to read it | Avoid |
|---|---|---|
| Project / Equity / Sponsor IRR | Return calculated from the corresponding canonical cash-flow series. | Treating different IRR definitions as interchangeable. |
| NPV | Present value under the configured cash-flow and discount convention. | Comparing NPVs without matching basis and discount assumptions. |
| DSCR | CFADS relative to senior debt service for the applicable period. | Reading it as a market sentiment indicator. |
| LLCR | Discounted CFADS over remaining loan life relative to senior debt outstanding. | Ignoring eligibility, maturity or discount convention. |
| Statements | P&L, balance sheet and cash-flow/waterfall outputs produced by the model. | Inferring distributable cash directly from EBITDA or net income. |
| Distributions | Cash available to sponsors after operating, financing, tax and reserve requirements. | Treating reserves and unrestricted operating cash as the same account. |
FINCO Radar
Company fundamentals, financial history, corporate actions, tokenized-market context and amount-specific execution simulation.
Global market state plus focused market-structure views.
Rates, inflation, inflation expectations, labour and funding conditions with explicit period/freshness handling.
On-chain reference observations for Stock Tokens — a first-class Radar domain, not a sub-feature.
FINCO Trust Stack
The layers below are separate authorities, not automatically cumulative certification levels: a green result at one layer never implies anything about the next.
| Layer | Question answered | Shipped |
|---|---|---|
| Model | What did FINCO calculate? | Yes — deterministic engine; the committed Last Run is the output authority. |
| Run Integrity | Is the committed run internally consistent under implemented checks? | Yes — read-only checks over evidence recorded at run commit. |
| Reference Regression Check | Does the canonical reference still reproduce pinned expected outputs? | Yes — regression protection for the reference library. |
| Signed Run | Did FINCO cryptographically sign these exact committed bytes/evidence? | Yes — Ed25519, config-gated. Public trust-key distribution and a public verifier are still in development (M-2). |
| FINCO Verify | Is there sufficient source-attested evidence to bind the model/asset to the claimed external identity? | Architecture shipped; production Verified assets: 0. Records currently render MODEL_ONLY. |
Reference Regression Check ≠ Run IntegrityRun Integrity ≠ FINCO VerifySigned Run ≠ FINCO VerifySigned Run ≠ economic truthReference price ≠ executable priceWorking Copy ≠ Last Run
In the workbook, the Model Trust Pack presents these layers per project:
Last Run identity, core KPIs with lineage, the Reference Regression Check
(on-demand), Run Integrity, the Signed Run certificate and FINCO Verify state.
Machine compatibility may still use the internal authority key
MODEL_VALIDATION for the Reference Regression Check API.
FINCO Verified Assets
Verified Assets compose existing FINCO authorities into a single
FINCO_VERIFIED_ASSET_V1 record. The composition
principle is: NUMBER → LINEAGE → EVIDENCE → MARKET OBSERVATION.
FINCO_RUN_CERTIFICATE_V1)A Signed Run certificate inside the record does not make the asset VERIFIED — signing and verification are separate authorities.
V1 reference assets render as MODEL_ONLY — a canonical model↔market identity mapping is not yet established. A discovered market binding alone is never sufficient for VERIFIED status; full identity reconciliation, Radar reference evidence and tokenization premium observation are all required.
Use Verified Assets → to view the current asset composition and certificate state.
Evidence & verification
FINCO uses source, period, snapshot and lineage information to keep calculations and observations auditable. Supported verification checks deterministic identity and configured internal relationships. It does not replace an external publisher, filing or legal source with a second FINCO truth.
The validation corpus remains an advanced, non-discoverable product surface rather than a primary navigation item.
FINCO API Beta
Base path: /api/v1. The public beta exposes Model reference capabilities
and Radar data/analytics. Availability in a particular environment still depends on
deployment and source configuration.
| Method | Capability | Purpose |
|---|---|---|
GET | /model/references | List canonical Solar, Wind, Data Center and EV Charging references. |
GET | /model/references/{reference_key} | Read grouped reference assumptions. |
POST | .../{reference_key}/preview | Capacity-scaled stateless preview; no project and no model run. |
POST | .../{reference_key}/run | One stateless canonical financial run; no project/workspace persistence. |
GET | /radar/assets and sub-resources | Identity, fundamentals, financial history, corporate actions and evidence. |
POST | /radar/assets/{uid}/execution-simulation | Read-only amount/direction execution analytics; no order submitted. |
The API contract is still Beta. A stable SDK, webhooks and formal GA support/deprecation policy are later work.
Shared concepts
Status
Capability exists in the reviewed repository. This does not imply every environment has deployed or configured it.
A user-facing capability exists, while its public operating or compatibility contract is still evolving.
Direction only. Planned work is not described in the present tense and has no implied launch date.
Required evidence or runtime authority is absent. FINCO prefers this to a synthetic fallback.
Status labels appear at point of use — on individual surfaces and in capability output — rather than in a centralized limitations catalog. See the Product map for per-surface scope.
Generic debt-schedule functionality does not imply these structures are modelled.