Proof Wiring

Packets, artifacts, hashes, and claim boundaries in one path.

This page connects the public Ark Axiom sample packets to their raw evidence files, review-target artifacts, run receipts, manifests, hashes, and blocked-claim boundaries. It is an evidence map, not a signoff report.

3
Review surfaces
Public
Sample packet paths
SHA-256
Artifact manifests
false
packet_authorizes_execution
Primary Evidence Paths

Start with the packet. Drill into the proof.

Each lane exposes a human-readable packet page first, then raw machine-readable or hash-verifiable artifacts.

Evidence Matrix

What is wired now.

Lane Readable packet Raw evidence Integrity proof Blocked claims
RTL Review Agent WarpCore packet and historical replay set packet.json, review targets, evidence table, affected signals, expression excerpts hashes.sha256 / sha256_manifest.txt No correctness, formal proof, FPGA/ASIC readiness, or signoff
PCB Review Gate PCB packet index and case-level summaries review_targets.json, affected nets, affected footprints, segment/via changes, visual overlays sha256_manifest.txt No DRC/ERC, DFM, SI/PI, thermal, fab approval, or manufacturing signoff
Compiler-Hardware Assumption Gate Compiler-Hardware packet compiler_hardware_packet.json, review targets, simulator/RTL questions, memory assumptions, benchmark boundary run_receipt.json + hashes.sha256 No compiler correctness, simulator/RTL equivalence, benchmark validation, hardware readiness
Claim Boundary

The proof object does not authorize execution.

Ark Axiom packets preserve review evidence, compression rationale, hashes, and blocked claims. They do not approve tapeout, fabrication, assembly, benchmark claims, compiler equivalence, production readiness, or replacement of human engineering review.

Operator Handoff

human_operator_handoff:true

Every public lane keeps final engineering judgment outside the packet.