How every number is built.
Ten documents, canonical for both product and design. They are the markdown files in docs/, rendered here rather than rewritten — so the page and the repository cannot drift apart. They include the parts that are uncertain and the parts that may never ship.
Product
What basis measures, the two formulas and why there are two, the flag thresholds, and what it refuses to claim.
Use cases
What it is for, with the figures that make each case: what the wrong pool costs, the weekend gap, corporate actions, and what a protocol would read.
Data sources
Both upstreams, measured. The ERC-8056 multiplier, the CORS wall, the dust floor, and the corporate-action trap.
$BASIS
The three engines, their published switch-on conditions, and the mandate each one runs under.
The desk
The personal instrument panel, and the interpreter — what grounds it and what it will not do.
API
Every endpoint, its shape, and its build status stated honestly. Read-only JSON, no key.
Architecture
How a reading is assembled, why this is a server-rendered app, and how it degrades.
Design system
The colours that carry meaning, the three type roles, and the rules the interface holds to.
Brand and compliance
The naming rules, the standing copy rules, and the unresolved question, quoted from the source.
Roadmap
What is next, what it is gated on, and — the part most roadmaps omit — what might never ship.
Call it now
These endpoints are live in this build. They read the same assembler the landing page uses, so the page and the API cannot disagree about a number.
curl /api/v1/basis curl /api/v1/basis/NVDA curl /api/v1/pools/NVDA curl "/api/v1/board?min_spread_bps=400" curl /api/v1/sessions curl /api/v1/status