Every claim on this site is meant to be checkable by somebody who does not trust us. This page is the instructions. It takes about two minutes for the first level, needs no account and no permission, and is designed to fail when the evidence changes. If a published number had been edited after the fact, the command below would say so.

There are three levels, each more hands-on than the last, and each independent of taking our word for anything. The first needs nothing but Python. The second adds one library and checks the signatures. The third clones the engine and re-runs it. You do not need to do all three: the first one alone establishes that the numbers you are reading are the numbers that were published.

Level 1: recompute every hash

Each published artifact carries a SHA-256 over its own canonical bytes. This recomputes all 164 of them from files downloaded straight off this site and confirms every one matches. You need no repository, install or private data. The Python standard library is enough.

Show the command (lists all 164 files it downloads)

mkdir canli-verify && cd canli-verify

for f in \
  accessibility_interaction_audit active_ownership_13d_item4_v3_blind \
  active_ownership_confirmatory_design active_ownership_human_gate_audit \
  active_ownership_item4_v3_blind_label_packet active_ownership_item4_v3_feasibility \
  admission_v7_promotion alpaca_broker_reconciliation \
  alphamax_upstream_clean_workspace alphatrend_upstream_clean_workspace \
  alphatrend_upstream_replay_manifest alphavintage_core_portable_reproduction \
  alphavintage_full_decision_reproduction alphavintage_rtdsm_portable_fetch \
  archival_publication_visual_inspection author_protocol_review_packets \
  backtest_overfitting_calculator_contract bond_etf_nav_reachability \
  book_drawdown_ladder borrow_execution_contract breadth_lab_contract capacity \
  cftc_release_reachability corporate_action_contract cost_coverage \
  crowding_risk_contract crypto_carry_current_replay_receipt \
  crypto_carry_first_rebalance_attribution crypto_carry_full_path_attribution \
  crypto_carry_portable_v1_admission_closure crypto_carry_portable_v1_result \
  crypto_carry_replay_correction crypto_lab_carry_crash_incident \
  crypto_position_attribution crypto_position_attribution_rollout_verification \
  crypto_position_attribution_vps_preflight_observation current_book_diversification \
  current_book_drawdown data_gate_unblocks deflated_sharpe_calculator_contract \
  deflation drawdown_control_v1 earnings_narrative_change_diversification \
  earnings_narrative_change_input_data_manifest \
  eia_petroleum_inventory_input_data_manifest energy_inventory_source_provenance \
  engineering_open_source execution_lab_contract external_publication_readiness \
  external_submission_plan external_validation_opportunities financing_contract \
  forward_drawdown_evidence forward_evidence_maturity \
  forward_full_evidence_reservation_v2_template_audit forward_sleeve_contribution \
  foundry_local_contract_verification fundamental_single_book_to_price_curve_evidence \
  fundamental_single_book_to_price_diversification \
  fundamental_single_book_to_price_input_data_manifest \
  fundamental_single_book_to_price_market_evidence \
  fundamental_single_book_to_price_replay_environment \
  fundamental_single_book_to_price_replay_failure \
  fundamental_single_earnings_yield_curve_evidence \
  fundamental_single_earnings_yield_diversification \
  fundamental_single_earnings_yield_input_data_manifest \
  fundamental_single_earnings_yield_market_evidence \
  fundamental_single_earnings_yield_replay_environment \
  fundamental_single_earnings_yield_replay_failure \
  fundamental_single_gross_profitability_curve_evidence \
  fundamental_single_gross_profitability_diversification \
  fundamental_single_gross_profitability_input_data_manifest \
  fundamental_single_gross_profitability_market_evidence \
  fundamental_single_gross_profitability_replay_environment \
  fundamental_single_gross_profitability_replay_failure \
  fundamental_single_operating_margin_curve_evidence \
  fundamental_single_operating_margin_diversification \
  fundamental_single_operating_margin_input_data_manifest \
  fundamental_single_operating_margin_market_evidence \
  fundamental_single_operating_margin_replay_environment \
  fundamental_single_operating_margin_replay_failure \
  fundamental_single_operating_margin_replay_infrastructure_failure \
  fundamental_single_operating_margin_replay_infrastructure_failure_environment \
  fundamental_single_operating_margin_replay_infrastructure_failure_lake_manifest \
  fundamental_single_operating_margin_replay_root_cause \
  fundamental_single_sales_to_price_curve_evidence \
  fundamental_single_sales_to_price_diversification \
  fundamental_single_sales_to_price_input_data_manifest \
  fundamental_single_sales_to_price_market_evidence \
  fundamental_single_sales_to_price_replay_environment \
  fundamental_single_sales_to_price_replay_failure futures_execution_contract \
  hdb_dividend_vendor_resolution identity_packet_recoverability \
  inflation_breakeven_relative_value_feasibility \
  insider_purchase_clusters_input_data_manifest kill_log legacy_research_epoch_closure \
  lint_debt_contract market_status_contract merger_announcement_confirmatory_design \
  next_sleeve_selection operating_margin_corrected_replay_authorization \
  operating_margin_corrected_reproduction \
  operating_margin_exposed_split_issuer_resolution \
  operating_margin_replay_infrastructure_failure \
  operating_margin_unresolved_split_exposure options_execution_contract \
  paper_evidence_conformance polygon_split_crosscheck pre_registration \
  prereg_investment_upstream_clean_workspace program_status prospective_epoch_register \
  publication_clean_checkout_integrity record_continuity red_team reproducibility \
  repurchase_issuance_companyfacts_audit repurchase_issuance_identity_overlap_audit \
  repurchase_issuance_semantics_audit repurchase_item703_blind_label_packet research \
  research_accessibility_audit selection_risk_lab_contract \
  sharadar_corporate_action_corrected_lake \
  sharadar_corrected_corporate_action_validation sharadar_dividend_basis_resolution \
  sharadar_dividend_price_consistency sharadar_dividend_split_basis \
  sharadar_hdb_corrected_lake sharadar_split_governance_policy \
  sharadar_split_lifecycle_scope sharadar_zero_dividend_quarantine sleeve_atlas \
  sleeve_atlas_audit sleeve_family_lineage_audit \
  sleeve_publication_isolated_replay_verification \
  sleeve_publication_replay_verification split_direction_before_after \
  split_exception_issuer_resolution split_issuer_conflict_resolution_batch_v5 \
  split_issuer_resolution_batch_v10 split_issuer_resolution_batch_v11 \
  split_issuer_resolution_batch_v2 split_issuer_resolution_batch_v3 \
  split_issuer_resolution_batch_v4 split_issuer_resolution_batch_v6 \
  split_issuer_resolution_batch_v7 split_issuer_resolution_batch_v8 \
  split_issuer_resolution_batch_v9 split_lifecycle_discontinuity_resolution \
  stanford_cs_evidence_map tender_offer_reachability track_record \
  treasury_schedule_state_machine_audit treasury_tentative_schedule_audit trial_ledger \
  trial_packet_manifest unresolved_split_event_context vate_2020_dividend_resolution \
  walkforward_input_snapshot_protocol wave1_data_rights_audit wave1_release_candidates ; do
  curl -sO https://canlicapital.com/glassbox/$f.json
done
curl -sO https://canlicapital.com/glassbox/reproduce.py

python3 reproduce.py --dir .

You should see L1 content hashes : 164 reproduced, 0 failed. If any line says FAIL, a published file no longer matches the hash it was published with, and the kit exits non-zero. That is the kit working, not the kit breaking.

Level 2: check the signatures and the chain

Two commitments are Ed25519-signed, and the whole track record is written into an append-only hash chain: each entry links to the one before it by hash, and every link is signed. Re-deriving that chain is the check that matters most, because it is the one that catches a past day being quietly rewritten rather than a present file being edited.

pip install cryptography

for f in capacity_commitment founder_commitment ; do
  curl -sO https://canlicapital.com/glassbox/$f.json
done
python3 reproduce.py --dir .

# and the append-only chain, which is the part that cannot be quietly rewritten
curl -sO https://canlicapital.com/glassbox/transparency_log.json
curl -sO https://canlicapital.com/glassbox/verify_transparency.py
python3 verify_transparency.py transparency_log.json

The chain currently holds 1399 entries, from 2026-06-27 to 2026-10-11, signed under the public key 0c6606a6b0c5b66fbf3b78521c85e72019484e0177d04a873a651179175ac095. If any earlier entry had been altered, that entry's chain hash and every later signature would fail here.

Inspect the chain in the browser. The interactive microscope verifies every predecessor link and signature, exposes the payload-disclosure boundary and lets you mutate a local copy of any entry. The Python command above remains the canonical check for disclosed payload bytes.

Level 3: re-run the engine

The last level checks that the engine which produced the numbers is deterministic and unchanged: a golden-master test replays a scripted fixture and requires the output to be byte-for-byte identical. This one needs the repository.

git clone https://github.com/arhancanli/alphac.git
cd alphac && uv sync
uv run python scripts/reproduce.py

Run inside the repo, the same reproduce.py executes all three levels at once and prints a summary of each.

What this does not prove

A verification page that only lists what it establishes is marketing, so here is the other half, stated as plainly as the commands above.

A matching hash does not make a number correct. It proves the file you are reading is the file that was published and has not been edited since. If a figure was computed wrongly, it will hash perfectly. What defends against that is a different thing entirely: the measurements, each published with its own claim boundary, and the published corrections we have had to make against our own earlier figures.

A valid chain does not make the history complete. It proves that nothing has been altered or removed since the chain began, at 2026-06-27. It cannot say anything about what was or was not recorded before that date, and it never will. That is a real limit and it does not shrink with time.

A deterministic engine is not an accurate one. The golden master proves the engine reproduces its own output exactly. It says nothing about whether the model of the market inside it is any good, which is what the research library exists to argue about and what the forward record exists to settle.

And none of it is funded performance. The published ALPHAC book trades on paper, nothing here is investment advice, and a verified record of a simulation is still a record of a simulation.

If something does not reproduce

Then we would want to know before you do, and we have deliberately made that easy to report: the failing output of reproduce.py is self-describing, name the file and the level. A published record whose only asset is that it checks out cannot ship a bundle that does not check out, so a genuine failure here is a defect on our side, not a support question.

The glass box · Every measurement · The research library