Merge gated, deterministic work without a human
State: open/proposed
Statement
Section titled “Statement”A bounded class of tasks — generated-doc refreshes, dependency bumps, and system duties whose checks are complete — merges on green gates with no human in the loop. The class is declared per task kind and starts empty.
Who/what it affects
Section titled “Who/what it affects”The person who today merges every PR by hand, including the ones where the checks already prove the change safe. It also affects the gate design: a task kind can only join the class once its checks are trusted to be complete.
Evidence
Section titled “Evidence”- N-41AZ-vision, “Non-goals and settled tensions”, the “Humans merge” row: “The loop shepherds and a person merges. The exception is a bounded class of work that is deterministic and fully gated: generated-doc refreshes, dependency bumps, and system duties whose checks are complete. That class is declared per task kind, starts empty, and grows only as gates prove out.”
Toward resolution
Section titled “Toward resolution”Not yet a milestone. The plan’s “Not yet a milestone” list names it directly: declare the auto-merge class per task kind once the gates exist.