Getting started

Still missingThe build is distributed as an ad-hoc signed arm64 disk image. It is not notarised, and there is no public download link on this site yet. This guide describes the steps; it is not a substitute for a download that does not exist publicly.

#What you need first

• An Apple-silicon Mac. The current build ships arm64 only.
• At least one vendor CLI you already pay for, installed and signed in.
• Nothing else. No Node, no Python, no office suite — the workbook engine is native and needs none of them.

#Connect a CLI

Finexia detects the CLIs present on the machine and drives them headless. Your subscription and your credentials stay where they are: the application never stores a vendor key, and a key never appears in a file, a database or a log. The details — which binary, which sign-in command, what each state means — are on the provider pages.

LimitThose three are what the core registry lists today. This page is generated against that registry and will not name a fourth until the core does.

#A first mission

1. Open a desk and ask one concrete question — a company, a metric, a period.
2. Watch the host route it. Cards appear for the roles the question needs.
3. Read the trace on a card. Each line is an event from the process, with its phase and its tool.
4. Open the raw output underneath the trace if you want the exact command line and the unedited stream.
5. Open whatever the card deposited: a chart module on the canvas, a workbook, or a blocked result with its reason.
6. Stop the desk from the application itself, not with a signal — the quit path is what stops the processes it started.

#What this build will not do

• AVAILABLEProduce a deck or a memo without an engineBoth formats gained a native engine in 0.0.23, alongside the workbook. What preflight still refuses, before any process starts, is a format the build does not carry — which is why a missing engine costs nothing.
• PLANNEDPlace an orderThere is no write path to a broker, and the market feed exposes no write method. That is verifiable by compilation, not by policy — and it is a deliberate boundary, not a gap waiting to be closed.
• AVAILABLEShow you a monetary costThe header shows the usage the CLI itself publishes, or says that usage is unavailable. It never invents a figure in dollars.
• PREVIEWDelegate to a sub-agentThe boundary is written and covered by tests in the core — opaque identity, six states, an idempotency key — and nothing calls it yet, so no delegation tree can be shown.