irrevon
Roadmap

Phases and gates, not dates

This page is a projection of the execution plan, parsed from the canonical document at build time.

No dates are promised

Nothing on this page is a schedule or a commitment; order is load-bearing — the design freeze (Stage A) precedes every live-sandbox observation and the operational freeze (Stage B) precedes confirmatory execution. Synthetic reference-destination development pilots (S-REF) already occurred and are disclosed as non-confirmatory engineering exposure; the roadmap does not call the design freeze pristine.

Evidence: Verified evidenceTechnical provenance

The phases

R1 – R4, in order

  1. R1

    source launch (complete)

    ROADMAP

    The repository-local gates are complete, outside contributions are accepted, and claims remain aligned with synthetic evidence. This milestone did not generate scientific results.

  2. R2

    provider qualification

    ROADMAP

    After owner authorization, run bounded sandbox spikes, record sanitized provider fixtures, ratify ADR-0010/ADR-0012, and update declarations only from observed evidence. Draft adapters remain drafts until this closes.

  3. R3

    benchmark freeze and execution

    ROADMAP

    Independent reviewers assess the Stage-A package; the owner freezes and timestamps registrations before any confirmatory observation. Stage B then pins provider artifacts and holdout commitments. Results are published whether they favor Irrevon or falsify it.

  4. R4

    distribution (complete for v0.1.0)

    ROADMAP

    The owner registered the PyPI trusted-publisher binding and protected GitHub release environment, pushed the version-matching annotated tag, reviewed the artifacts, and authorized publication. The workflow produced checksums, an SPDX SBOM, GitHub attestations, immutable GitHub assets, and PyPI artifacts without a long-lived publishing token.

Status chips appear only where the plan records them. Scientific freezes, live-destination qualification, and confirmatory benchmark execution remain separately human-gated. A software Alpha release does not imply any of them.

Two independent tracks

Software availability is not scientific validation

The `v0.1.0` Alpha is published while the preregistration remains an unfrozen draft. No package, tag, demo, or website claim substitutes for a Stage A or Stage B freeze, confirmatory execution, independent reproduction, or destination qualification.

Read the canonical text: execution plan (rendered) · repository copy