Skip to content
BiTi
 All docs

Go-Live Readiness

The operator §18 packet reads the truth in one screen — can we trade now, why not, and the single next safe action.

Going live never guarantees profit. Crypto trading is high risk. See the Risk Disclosure.

The operator packet

The go-live decision reads /api/monitor/live-readiness-decision-packet and /api/monitor/go-live-readiness-snapshot. The packet composes the existing single-authorities into one read-only screen:

  • can trade now — a refusal-derived verdict — it is never asserted true on its own.
  • why not — the dominant blocker, classified as a correct economic refusal or a genuine defect.
  • dominant blocker — the single reason nearest to gating a live trade right now.
  • closest book → §18 — the book nearest to promotion, with its gap-to-20 attributed positive-net closes.
  • capital + safety posture — capital adequacy vs the min-notional floor and the runtime safety invariants.
  • anti-manipulation posture — a read-only warning input — it never approves a trade on its own.
  • execution-throttle posture — a read-only warning input — rate-limit / retry / idempotency health.
  • next safe action — the single next step the operator should take.

The §18 verdict is delegated, never recomputed. Anti-manipulation and execution-throttle are read-only warning inputs that never approve a trade.

The unblock is never code

force-live=false is never a user action. The live unblock is capital + genuine attributed positive-net closes + an operator first activation inside a bounded futures policy — never code, never a template, never a digest line.

Spot stays live-disabled.

See the evidence rules for the §18 corpus and the risk controls that gate every candidate.

Back to all docs