Methodology
Separate the claim from the evidence state.
The publication gate asks four questions: What exactly is claimed? What evidence supports it? Under what conditions was it checked? What remains unknown?
Release gate
Four checks before a public claim.
- 01 · Scope
Write the narrow claim
Name the object, version, condition, and decision the claim supports.
- 02 · Source
Map provenance
Use primary or official sources where possible; label internal, synthetic, and inferred material.
- 03 · Replay
Record the check
Preserve inputs, steps, expected output, date, and environment for repeatable checks.
- 04 · Boundary
Publish the limit
State what the check does not establish, plus correction and review routes.
Decision rule
What may be published
| Condition | Decision | Public wording |
|---|---|---|
| Source exists, no functional run | Publish as E1 | Source-mapped; not functionally checked |
| Local deterministic run recorded | Publish as E2 | Locally checked under stated conditions |
| Public replay package complete | Publish as E3 | Reproducible package available |
| External replay evidence received | Review for E4 | Name party, date, scope, and deviations |
| Unscoped performance or compliance claim | Hold | Do not publish until scope and evidence are supplied |
Corrections
Errors are versioned, not hidden.
- Material corrections are dated and linked from the affected page.
- A fixed build does not retroactively validate an earlier release.
- Legal, regulatory, safety, and operational determinations remain with the responsible authority and operator.