Answers
Who should approve a line in the team's CLAUDE.md?
According to the Claude Code documentation, the project CLAUDE.md reaches the team through source control, and Claude treats what is in it as context, not as enforced configuration. So the file records who changed a line and when. It does not record who answers for the line, whether it still holds, or whether a person decided it or someone added it in a pull request that got a quick read. The person who should approve a line is whoever answers for what it governs: the tech lead for a coding convention, the product owner for a business rule, the security lead for a limit. In Arroway that approval is part of how a rule exists: assistants write proposals, a person approves what becomes a rule, each rule carries the condition that ends it, and a replacement names the rule it retires. Every connected tool — Claude, ChatGPT, Codex, Cursor or anything over MCP — reads the current version before acting, and the file is left with nothing worth keeping. The install page is the first step.
Last updated October 8, 2026
Who answers for a line
In the Claude Code documentation I read, the project CLAUDE.md is shared through source control, so a line changes like any other file: someone edits it, a pull request goes up, a reviewer approves. That reviewer is usually approving a diff, not the decision behind it, and two questions get mixed: whether the edit is well written, and whether the team stands behind the rule. The second needs a person with authority over what the line governs, and the approval has to be written down next to the rule, not only in the list of reviewers.
Where a line outlives its approval
A file shows who changed a line and when. It does not show who decided it, whether it still holds or what it replaced, so last spring's rule reads like today's. The documentation says that when two instructions contradict each other Claude may pick one arbitrarily, and that the files should be reviewed from time to time to remove what is outdated; it does not say who does that review. Claude Code also keeps auto memory, notes Claude writes itself from your corrections, which nobody approved. These limits follow from the rule living in a file.
When to use Arroway
Use Arroway when every rule should have an approver, a date and an end condition, and should reach every assistant on the team, including the ones that never open the repository. An assistant that notices something writes a proposal; a person with authority over the subject approves it, so the approval is a recorded act and not a click on a diff. A replacement names the rule it retires, the old rule leaves the next read and stays in the history, and a rule whose condition came true is up for retirement. What holds goes there, and the file is left with nothing worth keeping. The first step is the install page.
What it looks like in practice
A seven-person product team keeps a CLAUDE.md in its main repository. In June the tech lead adds a line: always use the v2 billing client. In September billing moves to a new provider, and a developer adds a line for the new client without removing the old one. The reviewer approves the diff, which is clean. A month later Claude follows the June line in one session and the September line in another, and nobody can say which one the team meant or who had the authority to decide. In Arroway the September rule is recorded as replacing the June rule, with the tech lead's name and the condition that ends it: until the old provider is switched off. Claude, ChatGPT and Cursor open their next session with the current rule, and the history shows the old one, when it changed and who changed it. The team in this example is illustrative.
Questions people ask about this
- Can a pull request review be the approval?
- It shows that someone read the change. It does not record who has authority over the rule or when the rule stops holding. In Arroway the approver and the end condition are part of the rule, and the next read of any connected tool shows them.
- Who should be allowed to approve?
- The person who answers for what the line governs: the tech lead for a coding convention, the product owner for a business rule, the security lead for a limit. The assistant that noticed the thing writes a proposal and does not approve it.
- How do I try Arroway?
- Install it in the tool you already use — the install page has one route for Claude, ChatGPT, Codex, Cursor or any MCP tool — and sign in when the tool asks. From then on, sessions open by reading the project and close by recording what was decided.
Where this is verifiable
Claude Code memory documentation (code.claude.com/docs/en/memory), read on 8 October 2026 — Claude Code is described only as that documentation describes it on that date, and it can change in any release. Product documentation on this site (How it works, Install), the answers on alternatives to CLAUDE.md for a team and on stale memory, and the sanction, supersession and expiry-condition rules in the sanctioned product spec. Everything described here about Arroway is behaviour the tools apply today, not roadmap. The team in the example is illustrative.
https://www.arroway.app/en/answers/who-approves-a-line-in-the-teams-claude-md