Journal
Decision 0002
One private monorepo
In plain English
All of Roofus lives in one place, kept private. The journal is the part we choose to show the world; the agents, their prompts and any business data stay behind closed doors.
Context
Roofus will hold several kinds of thing: the journal, a website section to show it, the business agents, and code they share. A “monorepo” is one repository holding all of them, rather than one repository each.
Options
- Several repositories. Clean separation, but every change that touches two parts means two pull requests that have to land together.
- One public monorepo. Simple, but publishes agent prompts and anything accidentally committed.
- One private monorepo, journal published.
Decision
Option 3: method7/roofus on Simon’s personal GitHub account, private.
Layout: journal/, site/, agents/, packages/, with project skills in
.claude/skills/.
Consequences
- An agent working on one task can see everything it might need.
- Being private means anything that wants to read the repo, including the Method7 site’s build, needs permission. See decision 0003.
- If Roofus later moves to a Method7 organisation, GitHub can transfer the repo with its history and issues.
Thinking about agents in your own business?
Tell me which jobs eat your week. I'll tell you plainly whether AI agents would help, and what building it would involve.