Pancake Receipt
A Pancake receipt is an immutable, shareable backtest artifact at /r/<short_id> that records the strategy spec, evidence dataset hash, full metrics, verification boundary, and a SHA-256 result hash — making the backtest independently auditable and permanently citable.
How it works
Pancake is hosting infrastructure for AI-built trading strategies. The receipt is the central artifact in that model: when the Pancake engine completes a backtest run, it emits a receipt — a write-once database row with a stable short URL (/r/<short_id>). The receipt is permanent — the underlying record is never mutated. Any link to /r/<short_id> will return the same content indefinitely. Backtest is the on-ramp; the receipt travels with the strategy as it advances toward live execution.
A receipt contains six primary sections. First, the strategy spec viewer: the full strategy spec that was run, including markets, entry/exit rules, position sizing, fee_bps, and slippage_bps. Second, the evidence reference: the EvidenceDataset id and rows_sha256 content hash, linking the result to the exact rows used. Third, the metrics table: all 10 computed metrics (total return, CAGR, Sharpe, Sortino, max drawdown, win rate, Wilson CI, Brier score, bootstrap CI, permutation test p-value). Metrics requiring N ≥ 10 trades are labeled "insufficient_data" when trade count is below threshold.
Fourth, the verification boundary 3-tuple: the verified / agent_supplied_evidence / unmodeled_risks blocks described in the verification boundary concept page. Fifth, the result_hash: the SHA-256 digest of the canonical execution output envelope. Any reader can reproduce this hash by running batter at the same engine_version with the same spec and dataset. Sixth, engine identity: engine_version (batter package version), compiler_version, and renderer_version — all pinned at run time.
Receipts are available in three formats: HTML at /r/<short_id>, Markdown at /r/<short_id>.md (agent-readable directly in a context window), and JSON at /api/v1/public/results/<short_id>. The citation API at /api/cite/<short_id> produces BibTeX, CSL-JSON, or RIS from any public or unlisted receipt. The oEmbed endpoint at /api/oembed produces a rich embed card.
Visibility is controlled per receipt: public (indexed, appears in sitemap and llms-full.txt), unlisted (accessible by URL, not indexed), or private (owner-only). The visibility default is public unless the agent or user overrides it.