Objective
Establish a reproducible, falsifiable evidence path for p05-glyphcas. This contract authorizes no result by itself. A public result requires a versioned run, exact configuration, raw artifacts, environment identity, limitations, and a receipt.
Required suites
- Exact blob and canonical subset
- Paraphrase semantic alias fixtures
- Project and authority isolation
- Dependency invalidation
- Receipt-chain verification
- Representation recipe verification
- Early-exit and full-inference fallback
- Adversarial false-reuse cases
Invalid-run conditions
A run is invalid, rather than merely low-scoring, when any of the following occurs:
- semantic candidate promoted to exact identity
- cross-project reuse without contract
- stale dependency accepted
- receipt chain break
- approximation unlabeled
Metrics
Report each metric separately. Do not hide a regression inside one composite score.
exact_hit_rate
semantic_reuse_precision
false_reuse_rate
compiler_ms
lookup_ms
full_inference_avoided
invalidation_accuracy
proof_recovery
Baseline discipline
Use the strongest sensible baseline for the exact task and information budget. Pin versions, prompts, corpora, models, hardware, runtime flags, and warm/cold state. If the research system receives additional context, dependencies, precomputation, or a model, charge or disclose them under the contract.
Run receipt
Every run emits:
run_id
suite_id
suite_version
commit
configuration_digest
corpus_or_task_digest
model_and_runtime
environment_digest
started_at
finished_at
raw_artifact_refs[]
metric_records[]
invalid_conditions_checked[]
known_limitations[]
result_state
receipt_digest
Allowed result states:
REPRODUCED
VERIFIED_MECHANISM
IMPLEMENTED
SOURCE_REVIEWED
SPECIFIED
HYPOTHESIS
INCONCLUSIVE
FAILED
AWAITING_LOCAL_RUN
INVALID
Data splits and leakage
Freeze task sets before viewing final results. Keep development, selection, and held-out evaluation separate where the suite supports them. Record any human-authored fixture that appeared during implementation. Do not tune a threshold on the final set and present it as held out.
Statistical and qualitative reporting
For repeated measurements, report sample count, central tendency, dispersion, and uncertainty appropriate to the design. Preserve row-level results. For human ratings, blind condition labels where possible, record the rubric, and retain disagreement rather than averaging away failure modes.
Negative evidence
Failed and inconclusive runs remain in the experiment ledger with code, configuration, and reason. A later successful run does not delete them.
Publication requirements
A public result page must show:
- exact evidence state;
- date and commit;
- environment and task/corpus identity;
- metric table;
- baseline table;
- raw artifact links;
- failure gallery;
- limitations and non-claims;
- reproduction command;
- receipt digest.
No marketing page may round a measured result into a broader claim than the contract supports.