Witness Ingestion Pipeline

Witness Ingestion

Before a proof can be generated, raw execution history must be normalized into a witness the circuit can bind. The ingestion layer handles that transformation entirely on the architect's side.

Ingestion principles:

• Pull closed-trade history from sovereign sources the quant already controls—local journals, exchange APIs, prop-firm portals—not from third-party surveillance
• Normalize disparate fill formats into a single return series suitable for attestation
• Bind the witness to a time-bounded window so allocators know exactly what period the scorecard covers
• Discard trade-level fields before they reach the prover; only the statistical summary enters the circuit

The pipeline is designed so that even if an allocator trusts the proof, they still cannot reconstruct the book. Ingestion is a one-way funnel: history in, scorecard out.