Abstract

A method is disclosed for recording each merge into a shared code line as data and attributing it to a scheduled automated merger or to a human when both merge under one account identity, so that the recorded actor cannot distinguish them. A scheduled observer, fired at the merger's period shifted by a phase offset, reads merged change requests from the version-control service. It upserts one record per change keyed on the change number, re-reads an overlap behind the newest stored merge, and splits any search window whose match count approaches the service's result cap in half recursively, failing beyond a depth limit. Each merge receives one of three lanes from evidence ordered most-certain first: a foreign merging identity, or an approval count below the merger's own bar, yields human; the offset of the merge instant from the merger's most recent tick yields an automated candidate, human, or an explicitly declared unknown band; and a same-identity chain of closely spaced merges containing any member inconsistent with the merger is classified human. Approvals are also counted at the merged head commit. A response guard raises a typed error on a non-success status or a non-JSON content type, the search step raises the same error on an error-bearing payload or a missing result list, and on any error the observer prints one fixed-prefix line and exits non-zero so that its job is marked failed, not complete.

Creative Commons License

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 License.

Share

COinS