Skip to content

Formal evidence program: execute E01–E30 by dependency and evidence level #5

Open

Description

@hanklin9188

Goal

Retire EdgeFlow's evidence debt in the dependency order defined by docs/18_EXECUTION_BACKLOG.md and promote results only through executable validation.

Current state

Platform engineering for M0–M5 is substantially present, but the following remain incomplete before a public performance claim:

  • E01 timer calibration;
  • E02 thermal/background policy;
  • E03 repetition calibration;
  • priority validation parity closure;
  • primary 3B E04–E09 baseline/fairness/quality;
  • E10–E12 holdout policy evidence;
  • E13–E18 matched causal interventions;
  • E19–E20 amortization evidence;
  • E21–E24 profiler-selected end-to-end kernel evidence;
  • E28–E30 grounding, usability, and clean reproduction.

Operating rules

  • Follow AGENTS.md, CONTEXT.md, and relevant ADRs.
  • Use one formal experiment issue per executable block.
  • Keep engineering completion separate from experiment completion.
  • Preserve raw request records and exact commands.
  • Only measured PASS runs may enter policy synthesis.
  • Do not publish cross-runtime, causal, or kernel headlines before their release gates close.

Dependency phases

  1. Governance and calibration
  2. Executable validation parity
  3. Primary 3B E04–E09
  4. First policy claim E10–E12
  5. Causal diagnosis E13–E18
  6. Amortization E19–E20
  7. Kernel E21–E24
  8. Optional learned components E25–E27
  9. Product validation E28–E30

Blocked by

Program completion

  • First evidence release gate passes.
  • Policy claim gate passes or a documented null result is published.
  • At least one causal hypothesis reaches E3/E4 and one negative control is rejected/inconclusive.
  • Kernel claim is either end-to-end confirmed or honestly classified as an engineering demonstration.
  • E29 and E30 pass before v1.0.

Source of detail

  • docs/17_ENGINEERING_AND_EXPERIMENT_GOVERNANCE.md
  • docs/18_EXECUTION_BACKLOG.md
  • docs/19_VALIDATION_PARITY_AND_RELEASE_GATES.md
  • specs/validation_requirements.yaml

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions