// Z-15 / truth engine

Truth engine

The truth engine is the falsifiability contract. Every Z-15 claim is paired with the exact observation that would kill it. If you can construct that observation, file it.

How to file a falsification

  1. Pick a claim from the claims register.
  2. Construct the falsification listed for it on this page or in the public repo's docs/z15/proof_packet/FALSIFICATION_PLAN.md.
  3. Open a GitHub issue using the falsification template. Include data, code, and the result.
  4. If the falsification holds, the claim moves to contradicted in the claims register within seven days of filing.

Sample claim & falsifier pairs

Claim

Z-15 substrate cuts training tokens by ~60% on the synthetic API-doc corpus.

Falsifier

Re-run the experiment from this repo against the same corpus and same seed; if treatment-side token count exceeds 12,000, the claim is dead.

Claim

Trace SHA verifies a Z-15 proof packet.

Falsifier

Recompute bundle_sha256 over the five artefacts of any packet; if it does not match the recorded BUNDLE_SHA256, the trace is broken.

Claim

Gap-finder requires two independent branch-close searches before declaring a branch closed.

Falsifier

Exhibit a GapReport with branches_required_two_closes == 0 that nevertheless asserts a structural gap as a finding.

What counts as refutation

A refutation is reproducible, sourced, and adversarial. We do not accept assertions; we accept a script, data, and a hash. The smallest cheap experiment that kills a claim is preferred to a large opaque one. See docs/z15/proof_packet/FALSIFICATION_PLAN.md for the canonical list.

What does not count

  1. "It feels wrong" — feel-bad without an experiment is not a refutation.
  2. "My private benchmark says otherwise" — privately-held results cannot be replicated and are therefore not refutations.
  3. "You haven't done X" — the claims register already enumerates what has and has not been measured; pointing at a gap on the register is agreement, not refutation.
[ File Falsification ]