Twenty questions, four readers.

The register's record of a committed plan's evaluation against a mandate clause. It is exceeded when the committed plan sits past the clause's limit. Drafts are coaching records on the trader plane and never reach the register.

Reviewed, on the record. Every acknowledgement is an append-only entry with the officer's name and time, and the observations it covers. Acknowledging is not deleting.

No. Observations, acknowledgements, and attestations are append-only records in the firm's own storage. There is no route to edit or remove an entry.

The as-of time, the generating officer, the scope the view was filtered to (desk, name filter, status), and the monitoring line naming any unmonitored clauses.

The settlement pass still runs: every active clause, every trader, attested measured within, exceeded, or declared unmeasured. A quiet day leaves a record of its quiet.

Inside the firm's own Azure subscription, single tenant: the application, the data VM holding the records on its own persistent disk, the gateway, and the firm's Entra directory. Nothing is hosted by the vendor.

Nothing. Outbound traffic from the sealed network is denied by default; the only application egress the policy allows is the tenant's own model endpoint and Entra for token verification. The egress manifest and the flow-log verification are the evidence.

An Azure OpenAI resource in the firm's own subscription serves the model. The deployment references it and never creates or holds it; which model deployment it points to is configuration the firm can read.

Entra ID groups map to trader, desk manager, risk, compliance, auditor, and strategy. Officer surfaces are gated by capability; a denied caller receives a 404, never a 403. Administration is not oversight.

The firm, in its own storage, under its own retention policy. Every oversight surface prints an audit-stamped PDF on demand.

Committed plans, mandate evaluations, observations, and briefs you send. Nothing else crosses.

Evaluates your plan against the mandate while it is still a plan, and coaches from your own record. Reshape or commit; the choice stays yours.

No. The dialogue is never summarised, scored, or forwarded, and firm-plane routes have no path to trader-plane records. The deployment's plane-denial report demonstrates it.

A note to the desk. You author it, or send DJ's draft unedited. Sending it is your act; nothing goes without it.

Your own number and its trend. Nothing about anyone else.

Forty thousand a year for the sealed deployment in your own tenant, ten thousand per trader seat, oversight seats unlimited. A ninety-day pilot on one desk is twenty-five, credited on conversion.

90 days, one desk, up to 6 seats, in your tenant, mandate encoding included: $25,000, credited in full against year one on conversion.

Yes. Annual after the pilot, with a 90-day termination right in year one.

ARQNXS deploys, encodes the mandate, and supports the platform. Updates and support are covered by the platform fee.

Nothing. The deployment is sealed inside your tenant with no vendor endpoint. The vendor cannot see your trades, your records, or your dialogue; that is a property of the architecture, not a contractual promise.