Product · Overview
A trader states a plan in conversation with DJ. Before capital moves, the plan is evaluated against the firm's mandate.
If a committed plan sits past a limit, the officer's register shows it, with the figure. The conversation stays with the trader. The record stays with the firm.
From plan to ledger.
- A plan is stated.
The trader describes the trade in conversation with DJ, on the trader plane. Drafts are coaching records and never reach the register.
- The plan is evaluated at intent.
Against the firm's mandate, while the position is still a plan. A clause that cannot be measured is said so, not guessed.
- The plan is committed.
The committed plan crosses the one boundary in the system, from the trader plane to the firm plane.
- Observations land on the register.
A committed plan sitting past a mandate limit becomes an exceeded observation, grouped by trader and clause on the Observations screen.
- Acknowledgement enters the ledger.
The officer acknowledges into an append-only ledger, with name and time, listed in Audit.
One card per screen.
OBSERVATIONS
The register: exceeded observations grouped by trader and clause, repeat offenders first.
Read the page →FORECAST
Will this trader's next committed plan produce an exceeded observation? Scored, per trader.
Read the page →ATTESTATIONS
The daily settlement pass: measured within, exceeded, or declared unmeasured.
Read the page →ANALYTICS
Read-only roll-up over the register, briefs, and forecasts. Every card names its window.
Read the page →DEVIATION
Realised against plan-followed. States that it cannot attribute until the execution feed is connected.
Read the page →MANDATES
Ingestion, encoding, refusal, activation, versions. The system refuses to guess.
Read the page →What the product does not do.
In the product's own words, from its own screens.