FINCO Protocol / Documentation

Build, read and verify financial intelligence.

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

Choose the path that matches your job.

A first 10-minute walkthrough
  1. Open Model. Start with a Solar or Wind reference and create an editable working copy.
  2. Change one or two assumptions. Capacity, pricing or a financing input is enough for a first run.
  3. Run the model. The run creates the authoritative Last Run output set.
  4. Read Radar separately. Market and company context does not silently rewrite project assumptions.
  5. Inspect evidence when it matters. Use lineage, snapshot and freshness information before treating a number as current or comparable.

Product map

Different questions, different authorities.

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.

SurfacePrimary questionCurrent scope
ModelWhat 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.
RadarWhat 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 IntegrityIs 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 RunDid 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 AssetsHow does a model run connect to market identity?Composed FINCO_VERIFIED_ASSET_V1 records: model economics + run certificate + Radar evidence + $FINCO protocol metadata.
$FINCOHow 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.
APIHow can software read or run FINCO capabilities?Beta Model reference/read/preview/run and Radar read/simulation endpoints.
EvidenceWhat produced this value and how should I interpret its state?Source, snapshot, period, lineage, freshness and deterministic verification concepts.

FINCO Model

From working assumptions to a Last Run.

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.

1
Project Library

Open a reference model or an existing working project. Solar, Wind, Data Center and EV Charging are the current supported modelling verticals.

2
Inputs

Edit project assumptions in Revenue, CAPEX, OPEX, Financing, Tax and related sections.

3
Run

Commit one deterministic calculation. The resulting snapshot becomes the Last Run authority for outputs tied to that run.

4
Results

Review decision KPIs, cash flow, debt, coverage, statements, distributions and returns.

5
Scenarios & sensitivities

Compare changed assumptions without treating an un-run working edit as a committed result.

6
Export

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.

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

Reference models

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

Use defined financial quantities, not generic health scores.

OutputHow to read itAvoid
Project / Equity / Sponsor IRRReturn calculated from the corresponding canonical cash-flow series.Treating different IRR definitions as interchangeable.
NPVPresent value under the configured cash-flow and discount convention.Comparing NPVs without matching basis and discount assumptions.
DSCRCFADS relative to senior debt service for the applicable period.Reading it as a market sentiment indicator.
LLCRDiscounted CFADS over remaining loan life relative to senior debt outstanding.Ignoring eligibility, maturity or discount convention.
StatementsP&L, balance sheet and cash-flow/waterfall outputs produced by the model.Inferring distributable cash directly from EBITDA or net income.
DistributionsCash available to sponsors after operating, financing, tax and reserve requirements.Treating reserves and unrestricted operating cash as the same account.

FINCO Radar

Stocks, Crypto and Economy keep their own data semantics.

Stocks

Company fundamentals, financial history, corporate actions, tokenized-market context and amount-specific execution simulation.

  • Featured Equities for discovery
  • Company Terminal for canonical asset identity
  • Underlying company context kept separate from token market state
  • Execution Simulation is analytics only; no order is submitted
  • No custody, wallet signing or order submission

Crypto

Global market state plus focused market-structure views.

  • Crypto Overview
  • Stablecoin liquidity and supply
  • Perpetual funding, leverage and liquidity context
  • Tokenized RWA market universe and leaders

Economy

Rates, inflation, inflation expectations, labour and funding conditions with explicit period/freshness handling.

  • Unavailable evidence is not silently substituted
  • Series are interpreted with their own observation periods
  • Macro context does not automatically rewrite Model assumptions

R-LIVE

On-chain reference observations for Stock Tokens — a first-class Radar domain, not a sub-feature.

  • Exact-identity authority: each approved identity is a specific canonical AssetKey / economic_asset_uid / pool reviewed from the official registry — no ticker-based or fuzzy lookup, no LLM fallback
  • 300-second on-chain TWAP with oracle conversion; the stablecoin is never assumed to equal USD 1
  • Explicit AVAILABLE / STALE / UNAVAILABLE states — STALE suppresses current numeric output
  • 1h / 24h historical ranges with collection-time semantics
  • Reference observations — not tradeable or executable prices; no order routing
  • Public read-only API; R-LIVE data never flows into the financial engine
Reference priceObserved market/reference value; not automatically executable.
Executable priceQuote bound to direction, size, route, settlement context and time.
Directional GAPDefined difference between executable quote authority and the relevant Radar reference authority.

FINCO Trust Stack

Five separate authorities. Each answers one question.

The layers below are separate authorities, not automatically cumulative certification levels: a green result at one layer never implies anything about the next.

LayerQuestion answeredShipped
ModelWhat did FINCO calculate?Yes — deterministic engine; the committed Last Run is the output authority.
Run IntegrityIs the committed run internally consistent under implemented checks?Yes — read-only checks over evidence recorded at run commit.
Reference Regression CheckDoes the canonical reference still reproduce pinned expected outputs?Yes — regression protection for the reference library.
Signed RunDid 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 VerifyIs 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.

What each layer means

  • Run Integrity — Sources & Uses, balance-sheet reconciliation, debt rollforward, debt-service/interest consistency, CFADS/DSCR integrity, DSCR sculpting feasibility, unfunded-cash conditions and sponsor-return input consistency, recomputed from evidence recorded at commit. It does not re-run the model and does not validate external assumptions.
  • Reference Regression Check — re-runs canonical reference models against pinned expected outputs and tolerances. Regression protection only: it does not validate a user's Last Run and is not a model-soundness guarantee.
  • Signed Run — proves FINCO signed the exact committed run evidence. It does not prove economic truth, verify an underlying asset, or constitute blockchain anchoring (none is implemented).
  • FINCO Verify — a separate source-attested binding authority. A MODEL_ONLY record is not VERIFIED.

Explicit separations

  • Reference Regression Check ≠ Run Integrity
  • Run Integrity ≠ FINCO Verify
  • Signed Run ≠ FINCO Verify
  • Signed Run ≠ economic truth
  • Reference price ≠ executable price
  • Working 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

Connect model economics to market identity.

Verified Assets compose existing FINCO authorities into a single FINCO_VERIFIED_ASSET_V1 record. The composition principle is: NUMBER → LINEAGE → EVIDENCE → MARKET OBSERVATION.

What a Verified Asset record contains

  • model — persisted canonical Last Run economics
  • Signed Run evidence — Ed25519 certificate over the committed run (FINCO_RUN_CERTIFICATE_V1)
  • FINCO Verify binding state — separate source-attested authority; absent means MODEL_ONLY
  • market — Radar model/market bridge evidence (when available)
  • protocol — $FINCO utility registry metadata

A Signed Run certificate inside the record does not make the asset VERIFIED — signing and verification are separate authorities.

V1 status

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

A digest identifies evidence; it does not make an external fact true.

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.

NUMBER→LINEAGE→EVIDENCE→MARKET OBSERVATION

Verification can

  • Check deterministic identity of supported evidence.
  • Validate configured relationships and invariants.
  • Preserve run, snapshot, period and source context.

Verification cannot

  • Prove that an external publisher or filing is factually or legally correct.
  • Turn stale or unavailable evidence into a plausible current value.
  • Claim on-chain anchoring while verification remains off-chain.

The validation corpus remains an advanced, non-discoverable product surface rather than a primary navigation item.

FINCO API Beta

Programmatic access to Model references and Radar intelligence.

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.

MethodCapabilityPurpose
GET/model/referencesList canonical Solar, Wind, Data Center and EV Charging references.
GET/model/references/{reference_key}Read grouped reference assumptions.
POST.../{reference_key}/previewCapacity-scaled stateless preview; no project and no model run.
POST.../{reference_key}/runOne stateless canonical financial run; no project/workspace persistence.
GET/radar/assets and sub-resourcesIdentity, fundamentals, financial history, corporate actions and evidence.
POST/radar/assets/{uid}/execution-simulationRead-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

Terms used across FINCO.

Working
The current editable workspace state. It may differ from the assumptions used for the Last Run.
Last Run
The last committed deterministic calculation authority and its bound input/scenario state.
Runtime snapshot
An immutable record of an acquired model or market runtime state used for evidence and replay.
Canonical authority
The designated source of truth for a particular calculation, identity or state within a defined scope.
Lineage
The sources, versions, periods, snapshots and transformations that produced an output.
Freshness
Whether observed evidence remains inside its configured time or period validity window.
Unavailable / Partial / Stale
Explicit states preferred over guessed or silently substituted values when required evidence is missing or old.

Status

Code capability and deployed availability are not the same thing.

Implemented

Capability exists in the reviewed repository. This does not imply every environment has deployed or configured it.

Beta

A user-facing capability exists, while its public operating or compatibility contract is still evolving.

Planned

Direction only. Planned work is not described in the present tense and has no implied launch date.

Unavailable

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.

Known limitations — debt repayment semantics
  • Mandatory cash sweep (SHL and senior post-sculpt) — SUPPORTED: the modelling convention sweeps available post-senior cash per period.
  • Terminal balloon at senior maturity — PARTIAL: the sculpting policy can permit or reject a terminal balance per configuration; there is no standalone balloon-repayment structure.
  • Voluntary early repayment — NOT_SUPPORTED.
  • Refinancing — NOT_SUPPORTED.
  • Prepayment penalty — NOT_SUPPORTED.
  • Debt acceleration — NOT_SUPPORTED.

Generic debt-schedule functionality does not imply these structures are modelled.