finished-work-reaches-a-verified-release — Finished work reaches a verified release at the pace it is finished

BLOCKED 0 of 2 issues done

ready: 0
blocked: 2
active: 0
verify: 0
done: 0
cancelled: 0

Problem

Work does not end when it is written or merged. A finished change flows to master, to a release whose version the public contract decided, and to every surface that publishes it, at the pace work is finished; the flow is measured, its backlog is loud before it is large, a red trunk holds it, and nothing calls a change delivered before its publication is observed. Sources: chatgpt-majordomus:c100#0, chatgpt-majordomus:c103#5, chatgpt-majordomus:c111#6, chatgpt-majordomus:c112#0, chatgpt-majordomus:c112#3, chatgpt-majordomus:c127#1, chatgpt-majordomus:c130#4, chatgpt-majordomus:c142#0, chatgpt-majordomus:c142#1, chatgpt-majordomus:c183#0, chatgpt-majordomus:c195#2, chatgpt-majordomus:c207#6, chatgpt-majordomus:c209#0, chatgpt-majordomus:c214#5, chatgpt-majordomus:c220#0, chatgpt-majordomus:c220#2, chatgpt-majordomus:c227#2, chatgpt-majordomus:c238#2, chatgpt-majordomus:c242#0, chatgpt-majordomus:c242#5, chatgpt-majordomus:c244#3, chatgpt-majordomus:c258#2, chatgpt-majordomus:c262#12, chatgpt-majordomus:c286#21, chatgpt-majordomus:c286#23, chatgpt-majordomus:c287#0, chatgpt-majordomus:c291#0.

Outcome

Current state

Its issues extend existing milestones; see each issue's why.

Desired state

Every criterion of the intent is carried by an issue here and proven by its test.

Acceptance criteria

While the trunk's verdict is red only its named carrier may land, and the trunk's protection requires the CI model's verdict
Past the declared backlog bound every session brief says so, and duplicate candidates are named
The time from a pull request's opening to its observed publication is measured per phase with p50, p95 and sample size
A publication never replaces the site with an older commit or an older release
Whether a commit may be released is one read naming each condition, and the release path reads the same functions
A finished task names the pull request that carries it and its disposition

Validation

majordomus plan validate

Issues

Each one is an execution contract with its own acceptance criteria, validation command and required evidence. The wave column is the layer of the dependency graph it sits in.

issue	status	wave	depends on	title
I3200	BLOCKED	2	I2709	The trunk's protection is compared with the CI model, and a drift is a finding that names the change
I3212	BLOCKED	1	I3204	Two open pull requests that realise the same issue are reported as duplicates, with the survivor named

The graph

finished-work-reaches-a-verified-release dependency graphfrom .ai/repo/project

flowchart LR
    I3200["I3200<br/>The trunk's protection is compared with the CI model, and a drift is a finding that names the change"]:::blocked
    I3212["I3212<br/>Two open pull requests that realise the same issue are reported as duplicates, with the survivor named"]:::blocked
    classDef done stroke:#16a34a,fill:#dcfce7,color:#14532d,stroke-width:2px
    classDef active stroke:#2563eb,fill:#eff6ff,color:#1e3a8a,stroke-width:2px
    classDef verify stroke:#7c3aed,fill:#f5f3ff,color:#4c1d95,stroke-width:2px
    classDef ready stroke:#0891b2,fill:#ecfeff,color:#164e63,stroke-width:2px
    classDef planned stroke:#0891b2,fill:#ecfeff,color:#164e63,stroke-width:2px
    classDef blocked stroke:#b45309,fill:#fffbeb,color:#78350f,stroke-width:2px
    classDef cancelled stroke:#6b7280,fill:#f9fafb,color:#374151,stroke-width:2px
    classDef superseded stroke:#6b7280,fill:#f9fafb,color:#374151,stroke-width:2px

Linked from this diagram (2)

Canonical record: .ai/repo/project/milestones/finished-work-reaches-a-verified-release.yaml. Read it back with majordomus plan show finished-work-reaches-a-verified-release.