This is the service account of vibey, a queue-based conductor for autonomous software delivery: design, build and review, driven by coding agents over a PostgreSQL queue and an append-only ledger.

It is vibey's delegated reviewer. When the operator is away and has switched the grant on, it may approve a pull request in the operator's place, and it can do so only through approve-check. That command refuses, and says why, unless every condition of the operator's written grant holds:

• the grant is switched on, in the repository's configuration and in a live variable the operator can turn off at any time;
• the pull request's author is on the operator's allowlist;
• the change touches none of the paths that decide what a gate measures, who may approve, or what an agent may do;
• every required check on the exact commit is green;
• this account wrote no part of the change.

Anything it cannot read counts as a refusal. An approval is pinned to the commit that was checked, and it is added to the gates, never used in place of one.

• It does not write, push or merge code.
• It holds write access, never admin, so it cannot bypass branch protection.
• It is not a code owner. Code ownership grants review authority, and a reviewer that is automated must not satisfy its own requirement.

The rules it follows are part of vibey's governing canon, and the reasoning behind each one is recorded in the project's architecture decisions.

• Repository: the-vibey-project/vibey
• Documentation: the-vibey-project.github.io/vibey
• Research paper: PDF

Made with ❤️ by Vibey, Developed by Adam Matthew Steinberger (@adammatthewsteinberger).