Technical / trader

Why firms deploy DojiPad: the technical and trader read.

CTO, platform engineers, and the traders on the desk.

Single tenant, in the firm's own Azure subscription, under the firm's identity provider (Microsoft Entra ID) and the firm's keys. Data egress: none. No external calls, no telemetry, no vendor endpoint. The vendor cannot see the firm's trades; that is a property of the architecture, not a contractual promise.

Is the conversation private? Structurally. The dialogue on the trader plane is never summarised, scored, or forwarded; committed plans cross one boundary, to the officer register, and nothing else does.

The decision timeline: plan stated, mandate evaluation, order entry, execution, review. Existing controls fire at order entry and review; the mandate evaluation sits before both. THE DECISION TIMELINE Plan stated Mandate evaluation Order entry Execution Review controls fire here before both Evaluated while it is still a plan, before the order exists.

Mandate, before capital moves

Every stated plan is evaluated against the firm's mandate while it is still a plan, before the order exists. Not at order entry, not after the fact.

See it in the product →
FIRM TENANT · MICROSOFT AZUREPRIVATE NETWORK · FIRM KEYS · ENTRA ID
TRADER PLANETHE COACHING DIALOGUE
COACH
Third session this week with a planned re-entry inside 15 minutes of a red trade. Your loss rate on those is documented.
REMAINS ON TRADER PLANE
TRADER
Fair. Cutting size and waiting for the level this time.
REMAINS ON TRADER PLANE
TRADER
Committing the plan. AAPL long, thesis attached.
PLAN → FIRM PLANE
COACH
As committed this projects 20% single name against a 15% mandate limit. Worth resizing while it is still a plan.
REMAINS ON TRADER PLANE
TRADER
Resizing to 12%. Recommitting.
PLAN → FIRM PLANE
FIRM PLANEOBSERVATION REGISTER · RISK & COMPLIANCE
10:02:41Plan committed · AAPL longCOMMITTED
10:02:42Observation · projected single name exposure 20.0% of NAV against a 15.0% limitLIMIT EXCEEDED
10:03:15Plan amended · re-evaluation at 12.0%WITHIN MANDATE
10:03:15Evidence chain sealed · plan, evaluation, observation, amendmentRECORDED
EVERYTHING ABOVE RUNS INSIDE THIS BOUNDARY. MODELS, DATA, RECORDS. ALL OF IT.
The dialogue on the left is never summarized, scored, or forwarded. Committed plans, mandate evaluations, and observations cross to the officer register. Nothing else does, and nothing at all crosses the tenant boundary.

Your path.

  1. 1 Why The technical and trader read, and the path from here. →
  2. 2 Architecture What sits inside the boundary, and the evidence the deployment produces. →
  3. 3 Deployment: Azure tenant, zero egress The deployment boundary, the evidence it produces, identity and roles, and retention. →
  4. 4 How it works The decision timeline, the two planes, and a session run live. →
  5. 5 The trader plane What crosses to the firm, and what it never sees. →
  6. 6 Forecast scoring A plan-horizon forecast, scored against what the trader does next. →
  7. 7 Papers Four short papers on the thinking behind the system, and the subscription form. →
  8. 8 Walkthrough Fifteen minutes on the live product, on a simulated firm. →
  9. → Request a briefing The system running live on a simulated firm, viewed from the officer register and the trader plane in turn. →
Next: Architecture →