Questions
Common questions
Every answer has its own address — the heading is a link. A manual where an answer cannot be linked to is a manual you cannot point anyone at.
What is this, briefly?
An open-source framework that turns the traces of a working week — conversations, meetings, commits, issues — into documentation you can act on, inside a personal Obsidian vault. The skills run inside a Claude Code session on your own machine, against your own files.
Is it an app I install?
No. It is text files read into a session that is already running. A skill cannot start anything, cannot run on a schedule, and cannot be called by other software. Everything it does happens because you opened a session.
Are my files sent anywhere?
The skills read and write in the vault on your machine. What leaves it is decided by which model you point Claude Code at and which tools you have connected — nothing in the framework uploads anything on its own. Agenda generation works with no network and no credential at all, deliberately.
Do I have to use Obsidian?
No. The vault is a folder of markdown files. Obsidian is a convenient way to read it, not a requirement. The convention that machine-written folders start with a dot exists partly because Obsidian hides them.
What do you mean by "the contract"?
A file, ecosystem.yaml, declaring the parts, the paths, the shared enumerations and the working loop. Every part reads it instead of carrying its own copy. This site reads it too — everything factual you see is rendered from it rather than written here.
Why are several components not published?
They are local tools built against one operation, not products. They are described anyway, because the manual describes the whole system — and because the pattern usually transfers even when the code does not. Every such page says plainly that the part is not published.
What does it cost?
Nothing. MIT-licensed. What costs money is the model you point Claude Code at, which is a bill between you and that provider.
Can I change it?
Yes — that is the point of text files. What is worth knowing is that the contract is the interface: change what a file means without changing the contract and you have two truths, which is the single failure class the framework exists to avoid.