Public Track Record

Every signal the AI-ALPHA engine publishes is written to an append-only, hash-chained ledger — so the record is provable, not claimed. Wins and losses are shown alike. Forward outcomes fill in as time passes; the published thesis and gate are never edited.

chain unverifiable — not readnot externally anchoredrecord not loaded · store: supabase

The durable ledger could not be read, so nothing below is a record of anything.

LEDGER_TABLE_ABSENT — the published record’s durable store is not yet provisioned on this deployment.

This is stated rather than hidden: an unreadable chain shown as an empty, verified one would be exactly the kind of claim this ledger exists to make impossible.

External anchor: the chain is empty, so there is no head to anchor yet

Reproduce this — no account, no API key

Track-record chain head — chain is empty (genesis)

Source: SherpaQuant — own published record

1 — fetch the public bytes
  1. Fetch every published ledger entry and the chain verdict (no auth)
    curl -sS 'https://sherpaquant.ai/api/track-record/verify?entries=true'
2 — apply exactly this transform

For each entry in seq order, take the nine immutable fields (seq, prevHash, publishedAt, instrument, signalFamily, state, composite, gate, thesis), serialize them as canonical JSON — object keys sorted recursively, no whitespace — and SHA-256 the UTF-8 bytes. That hex digest must equal the entry's entryHash, and entry n's prevHash must equal entry n-1's entryHash (entry 0 links to 64 zeros). The last entryHash is the head.

3 — or run the one-liner
node scripts/ops/ledger-anchor.mjs --verify

Caveat: The recompute re-implements canonical JSON independently of the server code, so agreement is evidence rather than a tautology.

Verify it yourself, logged out: GET /api/track-record/verify?entries=true returns every immutable field, the hash algorithm and the field order; node scripts/ops/ledger-anchor.mjs --verify recomputes the chain with an implementation that does not import ours.