A ticket count is not a capacity model
Split a feature into a bounded behaviour change, a bug into a reproducible failure and regression test, and maintenance into a named compatibility or operational result. An arbitrary large ticket should not count as one small item. The proposed lane has one active item and a ceiling of four scoped monthly items, not four guaranteed completions.
- List dependencies and access prerequisites before ordering work.
- Name excluded behaviours and the evidence needed for acceptance.
- Do not convert uncertain estimates into a throughput guarantee.
Preserve the meaning of checks
A test that correctly catches an application bug should remain meaningful. A CI job repair must not remove assertions, alter the trigger or ignore the failure merely to obtain a pass. Acceptance records should retain source revision, event and runner context when those affect the test.
- Require a failing-then-passing regression test for the named bug.
- Require a runnable preview or example for the agreed feature.
- Record separate review findings and how they were resolved.
Define the coordination boundary
A fixed backlog project, recurring CI responsibility, engineering lane and full engineering function are different scopes. State who prioritises, clarifies product decisions, approves sensitive actions and performs the authorised release. A wider composition should include its child outcomes explicitly rather than quietly expanding a small repair.
- Keep live deployment separate from preview acceptance.
- Resolve necessary human expertise before acceptance rather than surprising the buyer.
Evidence and commercial reality
The public sample illustrates the evidence structure, not a completed customer lane. Client throughput, accepted prices and delivery economics remain unmeasured. Start with representative backlog items and budget context; final capacity, price, taxes, billing and cancellation are settled in a written proposal.
Sources and limits
- GitHub: run identity and logs Checked 2026-10-10.
- Named jobs and run logs provide inspectable CI evidence.
- Real synthetic delivery packet Checked 2026-10-10.
- The sample connects acceptance criteria, implementation, tests, review and limitations; it is not client work.