Research records and design sources
Historical evidence is useful when its date, subject and authority are visible.
Document status
The repository's document index separates the single normative design, current module specifications, decision homes, active plans, records and superseded documents. A dated record is evidence about the run it describes; it is not a current API guarantee.
The user-facing guides here explain current intended use. Internal decisions stay at their established home. Follow source links for audit detail rather than treating every old table as a live roadmap.
Research examples
| Topic | What the records can establish |
|---|---|
| Campbell sky | Measured reference-reweighting and cumulant experiments; small-case recovery and high-dimensional weight-collapse limits. |
| TRIS / Haslam / RSB | Analysis scripts and their tests. The campaign's run reports and outputs are not part of the repository. |
| Backend surveys | Probe scripts that measure a backend under recorded versions, budgets and oracles; not permanent upstream properties. |
| Mutation tables | Which deliberate defects a particular test/fixture revision detects. |
Find examples in examples/inference and probe scripts in docs/probes. Long-running scientific examples are not prerequisite tutorials.
Project history
- Changelog: released and unreleased changes.
- Implementation ownership: semantic and numerical responsibilities.
- Normative design: architecture, roadmap and acceptance requirements.
External links target the repository's main branch, which can move independently of an installed release. Use a commit permalink for reproducible research citations.