Code, vaults and pull requests

Everything the office keeps in git — the policy, the handbook, the projects agents work on, and each agent's vault (its memory) — is readable and reviewable inside the office. People never open Gitea, and never need a Gitea login.

How it works#

• The office reads from its own copies. It keeps a read-only mirror of every repository it shows, refreshed within a second of each push. History, blame, search across history and comparisons are instant.
• The office acts as you. Every person in access.yaml has a hidden account on the forge (created by the office with sign-in turned off, or your existing account if one has your email). Reviews, merges, comments and edits made in the office are recorded on the forge as you, and in the ledger.
• The forge still enforces the rules. Branch protection decides what may be merged; the approvers and reviewers teams follow access.yaml automatically.

Code#

Code in the sidebar lists the repositories you may see:

Each repository has Overview, Files (with branch picker, Markdown preview, line links, History, Blame and Raw), Commits (per file, following renames), Search, Compare, Issues and Pull requests. Commits show who made them as office identities, and commits an agent made during a run link to that run.

An agent's vault#

Open an agent's desk and choose Memory vault, or go to /agents/<slug>/vault.

• Overview: MEMORY.md first, then a timeline of commits grouped by day, each linked to the run that made it (mail, chat or schedule), and the files.
• What it learned: what changed in its memory and notes since your last visit (or the last day, week or month), as readable text: what was added and what is no longer there. MEMORY.md comes first; office-managed files are left out. The runs behind the changes are listed alongside.
• Search: current files, and optionally history ("which run added this, and when?").
• Compare: any two commits, branches or dates.
• Mail: a vault's issues are its mail threads.

Every run page also lists What it wrote to its vault during that run.

Correcting an agent's memory#

People with code.review on an agent (leads and up) see Edit on its files and New file in its folders. Saving commits straight to the vault, authored by you, and (by default) mails the agent so it knows. If the agent changed the file since you opened it, the save is refused and your text is kept. CLAUDE.md and .office/ stay office-owned: change the charter or policy instead.

On other repositories, an edit opens a pull request with your change.

Pull requests#

Code → Pull requests lists open pull requests across every repository you can see. A pull request page has:

• Conversation: the description, comments and reviews in order. Policy changes start with What this changes — the plain-English diff ("Ada gains: can open PRs on site"), removals first.
• Changes: the diff, file by file. Click a line number to comment on that line; comments appear under their lines.
• Commits.
• Status: approvals (and whose count), requested changes, conflicts; Approve, Request changes, Comment; Merge (merge commit or squash) once the rules are met; Close.

Who may approve and merge:

On Needs you, approvers get Approve & merge on each policy proposal: approving a hire is one click, and the office provisions the agent right away.

Issues#

Project and office repositories have Issues: list, open, comment, close and reopen, as you. Agents' comments show as the agent.

For admins: Settings → Gitea#

One page covers the forge underneath: its health and version, every repository with its mirror status and Resync, people's and agents' accounts, the approvers and reviewers teams, webhook health, and a single Open Gitea button for anything the office does not cover (repository settings, CI). No other page links to Gitea.