Finexia / Demonstrations
Demonstrations
Nine chapters, and how far each one was actually watched.
From the first launch to the workbook that leaves the desk. Every screen below is a recording of the product, never a mock-up — and where nothing was recorded, the chapter says so instead of showing something else.
01
Start a desk
REPLAYThree steps before anything financial happens: a face, a model, a budget.
The first launch asks what tells this desk from another, which model subscription it runs on, and what it may spend. Nothing is sent anywhere — the face stays on the machine.
02
Finexia at a glance
CAPABILITY PREVIEWWhere the desk goes when its window is somewhere else.
A bar at the top of the screen, in its own window. At rest it shows Kam and up to three agents at work, and nothing else. One event widens it to a single line that passes on its own. A click opens the panel: ask Kam a question, reach the workspace, bring the desk back, or stop it. When a piloting session runs, the same panel gains one block — the host, the next action, the count — and Stop does not move and does not grey out.
No screen recordedNo screenshot exists. The bench holds none, no sealed build carries the bar, and the branch that does has not been pushed. The home page draws an interactive reconstruction and says so; this chapter shows nothing rather than showing something else.
03
Providers
REPLAYA data source you have not tested is a data source you do not have.
The CLIs are read from PATH, not declared: what can be launched is what is installed. Each one says whether it answered, and the only proof offered is a real request in an empty workspace. Three answer today; the others refuse cleanly and name the key they need.
04
Agent collaboration
REPLAYFourteen named mandates, and a host that routes between them.
Each role carries a written remit held by the application itself — the page does not invent one. Kam picks from these, watches their states, and stitches the desk back together as each card lands, with what it delivered and what it spent in context.
05
Wanis · Quant
REPLAYA backtest that shows its baseline, or it shows nothing.
Models, backtests and exposures of a deposit. An equity curve is never drawn without its buy-and-hold baseline after costs, in the same frame; point-in-time is mandatory, and BLOCKED is a first-class result rather than a failure.
06
Sources
REPLAYWhere did this number come from, and can I check it without trusting you.
Every figure carries its source, its retrieval date and its digest. 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.
07
Deliverables
CLIENT-VERIFIEDWhat leaves the desk is a workbook someone will pull on, not a screen.
One sealed dossier composes a workbook with live formulas, a deck with editable shapes and a memo with selectable text, plus a manifest carrying the revision, the sources and the digests. Publication is atomic: the three appear together or not at all.
08
Bouna · computer assistance
REPLAYThe only mandate that touches the machine, and the only one that never sees your data.
A session, never a mode: you start it, you watch its goal and its target while it runs, and you stop it. What may be opened is declared before anything runs, a target off the list is refused, and the refusal is written down. Driving is an exit channel, so no role holds it together with reading your journal.
09
MCP
CLIENT-VERIFIEDDrive the desk from the client you already have open.
The local MCP server exposes the desk over standard input and output. Claude Code 2.1.265 connected to it on 2026-09-10, listed seven tools, called one, and received the fourteen roles the running application holds. An outside server has to be declared and granted to a role before anything reaches it.
