Trust · Audit logs

Tamper-evident by construction.

Every STAXIS decision is recorded in a hash-chained Postgres audit log.

The log is cryptographically tamper-evident — any modification breaks the chain and is detected.

ENTRY n − 1decision datatimestamphash(prev) ↩ENTRY ndecision datatimestamphash(prev) ↩ENTRY n + 1decision datatimestamphash(prev) ↩externalanchor

What's logged

Every decision, on the record.

  • Every trade decision (with the full reasoning chain from LLM agent outputs).

  • Every breaker state change.

  • Every API call (in and out, anonymized where customer-private).

  • Every governance stage transition.

  • Every customer account event.

  • Every operational incident.

Hash-chaining

Each entry carries the hash of the one before it.

To modify any historical entry would require rewriting the entire chain forward — detectable by comparing chain endpoints to periodic external hash anchors.

ENTRY n − 1decision datatimestamphash(prev) ↩ENTRY ndecision datatimestamphash(prev) ↩ENTRY n + 1decision datatimestamphash(prev) ↩externalanchor
  1. 01

    Append-only

    Each new entry hashes the entry before it, sealing the prior record into the chain.

  2. 02

    Tamper breaks the chain

    Altering any historical entry changes its hash, breaking every link that follows.

  3. 03

    Anchored externally

    Chain endpoints are compared to periodic external hash anchors, so a rewrite is detected.

Retention

Retention by tier.

TierRetention
Retail tier3 years standard
Qualified Client7 years standard
Enterprise7 years standard; extended on contract request

Access

Your log is yours to export.

  • Customers can export their own audit log in CSV or JSON format any time.

  • Audit log access events themselves are logged.

  • Aggregated (anonymized) chain-validation metrics are published in the Calibration Report.