Back to Activity Records

Not Adopted: A Mechanism That Made Sequencing Too Strict

July 2026 · Record

Not adopted

Not adopted — this change was not adopted.

Wiroh explored a workflow in which one User Story would be merged, pass its Issue completion checks, and be synchronized back to `main` before the next Story branch could be created. The aim was to avoid leaving unmerged branches and pull requests behind, and to reduce stale bases, duplicate diffs, and mismatched review targets. The proposed mechanism enforced a strict sequence: one User Story, one branch, and one draft pull request, with no next Story until the previous delivery was closed.

The candidate implementation would verify the relationship between a completed Story and pull request, their exact heads, the synchronized `main`, and a clean working tree, then carry that evidence into the gate for the next Story. Review tested and revised many boundaries: stale or unrelated records could not be accepted; concurrent attempts could not race through the gate; Story and pull-request numbers could not be confused; and a remaining unmerged branch could not be overlooked. The candidate reached Wiroh’s internal process review of its workflow and evidence.

But completing that internal process review and adopting an operating rule are different decisions. The CEO concluded that the mechanism imposed a stronger constraint than the original intent—starting from `main` and avoiding branches derived from unfinished work. By placing all work in one line, it could make independent Stories wait and narrow the conditions for starting work more than necessary.

The pull request was therefore not merged, and the Issue was closed as Not Planned. The changes did not enter the current `main` branch and are not part of the current operating rules. The lasting lesson was not that stricter gates are always better, but that controls should be proportionate to the intent they protect. Even after design, implementation, and review, Wiroh may choose not to adopt a mechanism that constrains the work too broadly.

Not adopted — the verification remains part of the record, but the mechanism is not in current use.

Not adopted