01 · DECISION ORACLE

Decision Oracle

Every conjunction-management decision, captured and signed before a command executes.

● SPECIFICATION

  • —Two-body propagation · Vallado §2.5 · RK4 with J2 perturbation
  • —Collision probability · NASA-TM-105066 (Foster) / JGCD 24:4 (Patera)
  • —Decision record signing · Ed25519 via Web Crypto API
  • —Local persistence · IndexedDB with canonical JSON serialization
  • —Record schema · four-tuple: situation, rationale, action, attestation
  • —Audit trail · append-only, cryptographically linked chain

● HOW IT OPERATES

The Decision Oracle intercepts the moment between observation and command. When an operator receives a conjunction warning, the Oracle captures the full context: TCA, Pc value, covariance quality, proposed maneuver delta-V, and the operator's stated rationale. Nothing executes without a record.

Each record is signed with an Ed25519 key tied to the operator's identity. The schema enforces four fields: situation (the objective state), rationale (the operator's stated reason), action (the command issued or declined), and attestation (timestamp + signature). The resulting record is immutable, queryable, and transmissible to any downstream consumer — insurer, regulator, fleet manager.

The Decision Oracle does not decide. It records. The operator retains authority. What the Oracle provides is an infrastructure for that authority to be verified, audited, and learned from at fleet scale.

● ENGAGEMENT

REQUEST BRIEFING →