What each person needs, who owns the repo and how that changes, and the exact steps to get it running on a machine. Written against the vault as it stands today, not as it will be.
| Person | GitHub | Needs |
|---|---|---|
| Jake | ysacks1 | invite sent Accept it from your GitHub email. Same account you use for the personal vault |
| Davor | orbiusrs | invite sent Andy inferred this handle from the Herd media repo. If that is not your account, say so and it gets cancelled |
| D'Andrew | none yet | Create a free account at github.com and send the username. Five minutes, no card |
| Honey | optional | Only needed if she is going to load lists directly rather than emailing them |
Jake (ysacks1) and Davor (orbiusrs) have admin invites waiting in their GitHub email. Neither has been accepted yet, so the vault still cannot be opened by anyone but Andy. Honey has not been invited and does not need to be. D'Andrew cannot be invited until he creates a GitHub account.
D'Andrew has no Remy email address. He raised it on 7 August as one of three things promised and never delivered, and it is still open. Everything below works without it, but he cannot send client mail from a Remy domain until it exists.
The vault sits in Andy's Remix Systems GitHub organization. That needs explaining before anyone runs a command, because it is Remy's data.
Remy's people are admins of the repo, the same powers Andy has. Scheduled jobs work, which genuinely requires admin and is the main reason to start here. Andy pushes mechanical fixes rather than talking someone through them. Transfer to a Remy-owned account at any time, which removes Andy entirely. The cost is that he retains access until asked to leave.
Remy's from the first minute, in Remy's own org or Jake's account. Andy has no access and cannot read or push. The cost is that nothing reaches the team automatically, and every fix becomes a conversation.
What Andy does with the access, plainly. He does not read the vault for interest. He checks it occasionally and only for mechanical breakage, a command that errors, a job failing silently, and pushes a fix when he finds one. Moving from A to B later is one click, so nobody is stuck somewhere they did not choose.
Start on A. The vault is three days old and the fixes are frequent. Revisit once D'Andrew has a working week in it.
Roughly twenty minutes, most of it downloads. Do these in order.
It arrives by email once Andy sends it. Accept it before anything else or step 3 fails with a confusing error.
Claude Code is how you talk to the vault. Obsidian is how you look at it, and it is free. Obsidian is optional on day one but it is where the graph becomes visible, which is the moment the thing stops feeling like a folder.
Open Terminal and paste this. It puts the vault in a Vaults folder in your home directory.
If it asks you to log in to GitHub, it will print a code and open a browser. Paste the code, authorize, come back. It sometimes asks twice, which is normal.
Start Claude Code in the folder, then say exactly this:
It walks the setup one step at a time and remembers where you left off. It will ask who you are, set up your private config file, and confirm what you can see. Your config is yours alone and never reaches GitHub, so two people setting up at once cannot collide.
Open Obsidian, choose "Open folder as vault", pick ~/Vaults/remy-vault. That is the step people stall on, and it is three clicks.
Do not read the folder. Ask it things.
When it gets something wrong, say so in the moment and tell it the rule. It writes the correction down and stops making that mistake. That is the difference between a tool that degrades and one that improves.
None of that stops anyone from opening it today and seeing whether the shape is right. That is what this pass is for.