There is no new interface for your codebase to learn. XRevery sits between your team and your repositories, runs the work in cloud sandboxes, and hands the result back as a pull request in GitHub.
Install the GitHub app, pick the repositories you want in scope, and group the related ones into a System so a single brief can cross service boundaries. XRevery builds a profile of each repo: stack, test command, layout, owners.
Talk it through with the Coordinator, attach whatever context you have, and it proposes a plan: which repos, which workflow, where a human should sign off, and what it is likely to cost. Nothing starts until you confirm.
Runs execute in their own sandboxes while you do something else. You get a timeline, live activity and a cost ledger if you want to watch, and a notification when a decision is yours. Each repo ends in a pull request, and follow-up runs can address review comments on it.
We would rather be clear about the boundary than oversell it.
Architecture, product judgement, code review, and the merge. Agents open pull requests; people merge them.
The harness: workflows, sandboxes, context discipline, gates, observability, spend control and the catalogue.
Knowledge. Repo profiles and the System Wiki grow from your code and from finished runs, and you can edit them.