M.A.I.C.Alpha Crypto Intelligence

TRACK B · FORWARD EVIDENCE

Frozen Live Forward

Generation 1 is frozen to the audited production baseline at 2026-09-30T14:35:19Z. The older 2026-09-09 causal-policy boundary remains provenance only; no pre-freeze live NAV is backfilled. Completed forward intervals are appended and missing evidence remains missing.

TRACK B · FORWARD EVIDENCE

FROZEN LIVE FORWARD

Immutable forward model record — frozen since 2026-09-30

LIVE FORWARD — APPEND ONLYVERIFICATION PENDING
MAIC Live GrossMAIC Live 10 bps StressBTC Benchmark
Period
Awaiting completed forward interval
Live Multiple
—
Live Return
—
Annualized*
—
Max Drawdown
—
Sharpe · 0% rf
—
Sortino · 0% target
—
Avg Exposure
—
Turnover
—
Elapsed
—
Completed Intervals
0
Last Verified Publication
—

No pre-freeze live return is backfilled. A verification badge is only promoted to HASH CHAIN VERIFIED when the backend verifier passes over a non-empty ledger.

Verification

Every published row contains its own SHA-256 record hash and the previous published record hash. The status above is backend-derived; this page never hard-codes a verified badge.

Freeze manifest hashCanonical API
Latest ledger hash—
Previous record hash—
Freeze code commit3a25a6644f0d3066c30f2749e2d15e21ec32399a
Runtime code commit—
Frozen model SHA-2563c35c804875d621a75c1f1356a1d5c0cd1645814b3683c7411c1f70ebe458a1d
Strategy source fingerprint5f1325e5dc0e085203e495ef7e04ae13ac65c6ffd0799aec398c17715bcb361b
Methodology versionMAIC_PUBLIC_PERFORMANCE_METHOD_V1
Last publication—
Effective corrections0
Verifier resultPENDING

Chronology limitation

If a valid forward snapshot existed before deployment of the public ledger, any migration is published with the actual later published_at timestamp and an explicit migration disclosure. It is not presented as though the ledger row had been publicly timestamped earlier.

Published history

DateGross NAV10 bps NAVBTC NAV
Awaiting canonical completed forward intervals.