The vault
A private GitHub repository of plain markdown. Every tool reads it; you own it.
Your vault is a normal Git repository in your own GitHub account. Everything in it is markdown you can open in any editor. Alwen and your tools read it and add to it; nothing about it depends on Alwen to stay readable.
alwen-vault/
├── profile.md who you are, filled in as Alwen learns
├── rules/ how every tool should behave for you
│ └── global.md
├── knowledge/ notes, people, projects, references
├── journal/ decisions and realisations, dated
├── inbox/ what each tool saved, waiting to be filed
│ ├── claude/
│ └── slack/
├── jobs/ what @alwen did, step by step
└── .alwen/ generated for your tools — don't editWhat goes where
| Folder | What lives there | Who writes it |
|---|---|---|
profile.md | Who you are and how you work | Alwen, as it learns; you |
rules/ | How every tool should behave for you | You; tools can only propose |
knowledge/ | Notes, people, projects, references | The tidy-up, from the inbox; you |
journal/ | Decisions and realisations, one file each | Any tool, through log_decision |
inbox/<tool>/ | What each tool saved, waiting to be filed | Each tool, in its own folder |
jobs/ | Every request @alwen took on, step by step | @alwen |
.alwen/ | Rules compiled for each tool | Generated — edit rules/ instead |
Three promises
- Your edits win. Change anything by hand and push. Alwen re-reads the vault; when your version and Alwen's disagree, yours stays.
- Every change is a commit, signed by the tool that made it, with one sentence saying why. Undo anything with Git.
- Nothing is deleted. Old notes get a “still true?” question instead. How the tidy-up works.