GitRoster
A repository-native people-operations control plane for engineering organizations that proposes roster, role, compensation-band, leave-policy, onboarding, and offboarding changes through validated pull requests, then writes approved changes to the authoritative HR system while keeping proposal, review, employment authority, provider acknowledgment, destination readback, payroll effect, employee notice, dispute, and correction separate.
Engineering organizations already review infrastructure and application changes through versioned diffs, named owners, automated checks, and merge controls, while people operations often lives behind forms, spreadsheets, tickets, and opaque HR interfaces. GitRoster applies familiar review mechanics to a limited declarative representation, but a repository entry is not an employment contract, payroll instruction, benefits enrollment, privacy consent, manager authority, or proof that an HR platform accepted the change. Git history can evidence bounded repository events; it does not make sensitive data appropriate for Git or turn a merge into legal effect. The design minimizes stored personal data and requires destination acknowledgment plus readback.
A people-operations leader, engineering operations owner, technical founder, HR systems administrator, or security-conscious engineering company that wants reviewable changes without replacing its payroll, benefits, or HR system of record.
A live internal build pattern and current developer discussion show that engineering organizations are reconsidering people-system ownership.
People operations and engineering leadership have a named workflow and a familiar review surface.
One cross-reference, two inbound connections, and two direct connections show a coherent but not broad graph.
The source identifies a specific engineering-company buyer, a live internal build that validates the pattern, current developer discussion, available HR connectivity, and no direct commercial repository-native people-operations product in the supplied scan.
No structural incumbent copying cost is proven, HR systems remain authoritative, privacy and labor obligations vary, connector write behavior is uneven, repository workflows can expose sensitive data, and setup across countries and policies is services-heavy.
Discussion
No comments yet — be the first to weigh in.