Skip to content

FLOW-003 QM-15: measure q per service class (docs / attested-fork / full) — Prop 12/18 inputs (was QM-08 in v1.1 numbering) #4519

Closed as not planned

Description

@noahgift

FLOW-003 v1.1 §5.1 (aprender#4518) defines three service classes: docs, attested-fork and full. Prop 12 says a class may skip the full quorum iff q_c < ΔQ/((κ_x−κ_c)D), which is 0.25 at inputs [A].

Task: measure the per-class failure rate q_c over 7 days, receipted, with the same inputs pipeline as QM-01 (#4513). Emit one row per class: n, q_c, CI, T̄_c.

Acceptance:

  • A receipt file under evidence/ that the pv contract checks.
  • The Prop 12 inequality is evaluated per class and printed PASS or FAIL.
  • A planted class with q_c = 0.5 must print FAIL.

Out of scope: any gate or ruleset change. §7 stays "no change" until these receipts exist and the operator gives a go.

Refs #4513, #4518.

Activity

  1. added this to the 0.71.0 milestone on Sep 27, 2026
  2. changed the title [-]FLOW-003 QM-08: measure q per service class (docs / attested-fork / full) — Prop 12 inputs[/-] [+]FLOW-003 QM-15: measure q per service class (docs / attested-fork / full) — Prop 12/18 inputs (was QM-08 in v1.1 numbering)[/+] on Sep 27, 2026
  3. noahgift commented on Sep 27, 2026

    @noahgift
    ContributorAuthor

    Renumbered to QM-15 to match FLOW-003 v2.0/v2.1, where QM-08 means the fleet inputs. Scope is unchanged. With v2.1, the count must include problems the full quorum caught (R2-12).

  4. modified the milestones: 0.71.0, backlog on Oct 8, 2026
  5. noahgift commented on Oct 14, 2026

    @noahgift
    ContributorAuthor

    Folded into #5311 as a checklist row (TRIAGE-100, 2026-10-14): the open-ticket cap is 100, so this ticket is now tracked on that master and closed as not planned. Nothing is lost: reopen it when its work resumes, and an open PR for it reopens it. Pushed branch: 2e/4519-qm08-review-inputs, 41/4519-qm15-receipt-contract.

    Agent: aprender-clerk

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

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions