Finexia / Finance
Finance
Eight domains, and how far each one actually goes.
For every financial problem below: the mandate that carries it, where the figures come from, what comes out, and what stops the result being wrong. Each domain says its own level of proof — a page that presents eight equally mature domains is lying about seven of them.
Company analysis
TESTEDA filing says one number and the press says another. You need the one the company actually filed, with the period it covers and the note that explains it.
Liviafundamentalfilings, results, unit economics- What Finexia does
- Reads the accounts where the company files them, then the breakdown the consolidation erases — by product, by geography, by segment — from the filing’s own XBRL instance.
- Where the figures come from
- SEC EDGAR for a domestic or New York-listed issuer, the European mechanisms for a European listing. Each fact comes back with its accession, its full period, its unit and its precision.
- What comes out
- A margin or revenue reading on the canvas, carrying its source and the date it was retrieved.
- Tools it may call
- ohlcv · vendor_bars · options_chain · crypto_quote · symbol_search · github_repo · filing_segments · filings · offerings · vol_surface · chart_open · chart_indicators · place · annotate · dossier_contribute · dossier_status · report_blocked
What stops it being wrong
- A breakdown is never summed: at Apple, iPhone + Mac + iPad + Wearables is Product, and adding all six would count revenue almost twice.
- A quarter and a nine-month cumulative that end the same day stay distinct.
- An amendment sits beside the original, never in its place.
- A fact tagged nil is not a zero.
TESTEDOne SEC filing read end to end under a named test: 1 036 facts, five geographic members, the instance digest recorded. No agent has assembled a three-year series from it yet.
Markets and macro
AVAILABLEA price series without its venue is a different company. A rate without its regime is a number.
Sachamacrorates, FX, regime- What Finexia does
- Reads real candles and resolves the company and exchange alongside them; reads rate, FX and regime series from named providers.
- Where the figures come from
- Yahoo Finance for candles, with one named vendor as a cross-check — two vendors rarely publish the same figure for the same day, and the gap is information. Macro series from their publishers.
- What comes out
- A chart on the canvas, on the same series the agent reasoned over.
- Tools it may call
- ohlcv · vendor_bars · options_chain · crypto_quote · macro_series · vintage_series · euro_series · vol_surface · chart_open · chart_indicators · place · annotate · report_blocked
What stops it being wrong
- The resolved company and venue travel with the series, so a ticker cannot silently become another company.
- Contracts the exchange did not price are counted and dropped, not set to zero.
- Three vendors need a key and refuse cleanly without one.
AVAILABLEShipped in the current build and exercised by the recorded run. The figures on this site come from sealed captures, never from a live feed.
Portfolio and risk
PARTIALThe question is rarely “is this a good company”. It is “what does this do to what I already hold”.
Verariskdeclared limits, desk concentration, veto on adoption- What Finexia does
- Models, backtests and exposures of a deposit; declared limits, desk concentration, and a veto at adoption.
- Where the figures come from
- What the operator has deposited. Finexia holds no position and reads no broker — the exposure is of a deposit, and the wording is deliberate.
- What comes out
- A risk reading, and where relevant a refusal that names what is missing.
- Tools it may call
- report_blocked
What stops it being wrong
- A backtest is never shown without its baseline after costs, in the same frame.
- Point-in-time is mandatory: a model that sees tomorrow’s data is not a model.
- BLOCKED is a first-class result, not a failure.
- The risk mandate can refuse adoption, and its refusal names the limit it hit.
PARTIALThe mandate, the capability table and the refusal path are written and tested. No native run has produced a portfolio reading end to end.
Accounting
NATIVETwo documents disagree and nobody notices for a quarter. Reconciliation is where a dossier earns its credibility.
Nouraccountingfiled documents, reconciliation, discrepancies- What Finexia does
- Reconciles what was filed against what supports it, and names the discrepancies rather than smoothing them.
- Where the figures come from
- The documents the operator filed. The accounting mandate fetches nothing on its own — it reconciles what is there and names what is absent.
- What comes out
- A reconciliation with its gaps listed as prominently as its matches.
- Tools it may call
- dossier_contribute · dossier_status · workbook_create · report_blocked
What stops it being wrong
- A missing piece is reported as missing, never inferred.
- Two roles asserting different figures under one identifier create a named conflict, and the dossier refuses to seal until someone settles it with a reason.
NATIVEObserved: on 2026-09-10 the accounting mandate filed 25 contributions into a shared dossier that was sealed and published.
Due diligence
PLANNEDA data room looks complete until you list what should be in it. The absent documents are the ones that cost money.
Théadiligencedata room, cap table- What Finexia does
- Inventories the room as it was filed, reads the cap table against the documents that should support it, and marks what contradicts and what was never filed.
- Where the figures come from
- The data room as deposited, and nothing beyond it.
- What comes out
- A diligence board: what is filed, what contradicts, what is absent — the absent items as visible as the present ones.
- Tools it may call
- report_blocked
What stops it being wrong
- Anything fetched from outside is treated as data, never as an instruction.
- The mandate inventories; it does not conclude on the deal.
PLANNEDThe mandate and its capability table exist. No sealed capture and no native run — the page says so on the role’s own file rather than borrowing another mandate’s screen.
Execution
AVAILABLEWhere liquidity actually sits, and what an entry or an exit costs at that size.
Miloexecutionliquidity zones, entries and exits- What Finexia does
- Reads liquidity zones, entries and exits on real series.
- Where the figures come from
- Market data from the same providers as the charts, with their venue resolved.
- What comes out
- Zones marked on the open chart, each mark refused if it falls outside the series.
- Tools it may call
- ohlcv · vendor_bars · options_chain · crypto_quote · symbol_search · vol_surface · chart_open · chart_indicators · place · annotate · report_blocked
What stops it being wrong
- Finexia has no broker write access. There is no order path in the product, and the Feed trait exposes no write method — it is verifiable by compilation.
- The output is an argued thesis, never an instruction to buy or sell.
AVAILABLEShipped in the current build. The absence of any order path is a structural guarantee, not a policy.
Financial deliverables
PARTIALA reading that stays on a screen is not a deliverable. What leaves the desk is a workbook someone will pull on, a deck someone will present, a memo someone will quote.
MenzotoolsmithPython tools, proven by running them- What Finexia does
- Composes a workbook, a deck and a memo from one sealed dossier, then reopens each to check it.
- Where the figures come from
- Only what the roles filed into the shared dossier. The agent supplies no path, no filename and no figure of its own.
- What comes out
- One bundle: XLSX with live formulas, PPTX with editable shapes, PDF with selectable text, plus a manifest carrying the revision, the sources and the digests.
- Tools it may call
- python_run · report_blocked
What stops it being wrong
- Publication is atomic: the three files appear together or not at all.
- Sealing refuses while a conflict is unsettled, while the frame is missing, or if any fact has no source.
- A contribution filed after publication opens the next revision; it never edits what is already out.
PARTIALA real bundle was produced by a native run on 2026-09-10 and re-read by an independent reader — but it was sealed one revision too early and its manifest names version 0.0.0. It is shown as technical evidence on the Casefile, and offered for download nowhere.
Provenance and controls
NATIVEThe question that decides whether any of the above is usable: where did this number come from, and can I check it without trusting you.
Seliacioarbitrates between cards, allocates attention- What Finexia does
- Every figure carries its source, its retrieval date and its digest. Every claim on this site carries the release and the commit that established it.
- Where the figures come from
- The core registries, read at a pinned commit and committed alongside the site. Two builds of the same commit describe the same product.
- What comes out
- A trail you can follow: accession, URL, SHA-256, timestamp, product commit.
- Tools it may call
- dossier_contribute · dossier_status · report_blocked
What stops it being wrong
- An agent cannot cite a source it did not read: it gives back the reference a tool returned, and Finexia attaches the address, the time and the digest.
- A fact keeps the release that established it — importing a newer one adds a layer, it never relabels the old.
- No key ever leaves the macOS keychain, and the server never sees your data.
NATIVEObserved and published: the Casefile carries 37 facts across two releases, each with its own commits, and an evidence ledger that keeps them apart.