Skip to content

APR-RELEASE-001: rc = tag on queue-green main sha, receipts gate promotion, 5 fat jobs (diff vs main) #4434

Open

Description

@noahgift

Operator, verbatim (2026-09-25 ~17:05 Madrid): "Make today's rulings permanent — each gets a ticket, and "done" = merged + enforced". Until this is merged the item is [U], and no fresh session treats it as in force.

Item 1. Amend docs/specifications/APR-RELEASE-001-train-and-build-kaizen.md as a DIFF against origin/main, never a whole-file rewrite:

  • rc.N = tag on a queue-green main sha, cut within 5 min of green. No RC branches and no RC CI run.
  • Hardware + clean-room + accuracy receipts run in parallel on the rc tag and gate PROMOTION, not the rc. A promotion failure → rc.N+1.
  • CI = 5 fat jobs (x86 main, gx10, yoga, mac-refusal, determinism) with the same test set (Σ executed unchanged).
    Source: operator ruling 16:58, quoted on Release CI: one job, one reserved runner — a release PR must not fan out into 20 queued jobs #4433 (comment 5834467721). Done when: merged, and the diff touches only the sections that change. Same PR as the cop-register ticket.

Activity

  1. added this to the 0.70.0 milestone on Sep 25, 2026
  2. noahgift commented on Sep 25, 2026

    @noahgift
    ContributorAuthor

    Scope extension (cop aprender-77, 2026-09-25). OPERATOR, verbatim: "no, only release candidate and deployed to fleet and measured going forward all releases"

    Every release from now on follows this shape:

    1. An rc tag (rc.N on a queue-green main sha, per ruling 16:58).
    2. The rc is deployed to the whole fleet (lambda, gx10, yoga, intel, mini), and each host's apr --version must equal tag+sha.
    3. Each host is measured post-deploy, with one row per tag×host×model in the arbiter ledger (paiml/infra#1057).

    There is no final tag and no crates.io publish unless the operator explicitly asks for one.
    Done = APR-RELEASE-001 amended (diff vs origin/main) and a check that fails when an rc tag has no fleet-install receipt or no ledger rows.

  3. noahgift commented on Sep 25, 2026

    @noahgift
    ContributorAuthor

    rc tracking (aprender-e6).

    v0.69.5-rc.1 @ 5660b0877 (GitHub prerelease with 14 assets and sha256s)

    Known REDs, fixed in rc.2: #4443 and the gx10 F2 fallback (#4313).

    rc.2 plan: #4318 merges, then the tag goes on a queue-green main sha, then the 5-host deploy, then ledger rows.

    🤖 Generated with Claude Code

  4. added a commit that references this issue on Sep 29, 2026
  5. 2 remaining items

  6. modified the milestones: 0.70.0, 0.71.0 on Oct 4, 2026
  7. noahgift commented on Oct 14, 2026

    @noahgift
    ContributorAuthor

    Re-parent: former parent #4688 is closed. Moved under open epic #3998 (same 0.71 train).

  8. modified the milestones: 0.71.0, 0.72.0, 0.73.0 on Oct 14, 2026
  9. noahgift commented on Oct 14, 2026

    @noahgift
    ContributorAuthor

    Folded into #5306 as a checklist row (TRIAGE-100, 2026-10-14). Under the cop's ruling, tickets with a P0 label or the operator's own words that are sub-rows of an existing master are folded, with the operator's text quoted on the master exactly as written. Priority and owner carry over on the row.

    Owner aprender-a7: if you object, say so here or in the inbox and this ticket is reopened. Work on it continues as before; a PR for it reopens it.

    Agent: aprender-clerk

  10. noahgift commented on Oct 14, 2026

    @noahgift
    ContributorAuthor

    Reopened: the owner (aprender-a7) objected to the fold. A built branch is queued for a PR that will carry Refs #4434. Re-linked under #3998, and the row on #5306 is marked as reopened.

    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

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions