Learn · Sister
Dev Tools

Dev Tools is where the family's software is made. Overseer Kit keeps the building honest, so assistants can help make this future and the work is finished only when it is truly done.
An assistant can draft, search, and build. It cannot decide that the work is finished. The kit is the method that makes that sentence true in a repository, not only in a conversation.
You use Overseer Kit when assistants help build, and you need the plan frozen first and the finished work checked against that plan.
Overseer Kit keeps the building honest. Honest means a stranger can open the repository and see what was supposed to be built, what phase is current, and why someone claims it is done.
A plan is frozen before the build, and a separate review checks the finished work against that plan. Freezing is the moment the plan stops being a draft. The review before the build is independent. It challenges the plan. The review after the build is a different pass. It compares what was made to what was frozen.
The work is finished only when that review passes. Finished means the finished work was checked against the frozen plan and the check passed. Until then the phase stays open, and the handover says so.
Ordinary git still works, and MuseHub can keep a richer history when you want it. The roadmap and the handover live in the repository. Git already versions them. MuseHub is there when the work also needs the cross-domain thread: code beside music, learning, and the rest of a shared origin. The kit can use that thread.
The command is ok, bound to the repository you are in. It reads the roadmap and the handover. A session starts from those documents. One next step is named. When the step is done, both documents are updated together, so the next person, or the next assistant, inherits the same record.
Practise the loop in a repository you own: freeze a small plan, let a separate pass challenge it, build only that plan, then check the result against the freeze before you call it done. When that loop is clear, read Overseer Kit.
Dev Tools is the name of this part of the family. Overseer Kit is one tool in it. Agentception is the other. Agentception coordinates several agents on one build. A person still decides when the work is finished. Read Agentception beside Overseer Kit.
How it is built
ok is a command-line kit installed against a checkout. The two durable documents are the roadmap and the handover. The roadmap holds the phases, the model of work for each phase, and the definition of done. The handover holds the next session: what is true now, and the prompt that starts the next pass.
The freeze is an artifact with the plan locked. The first review challenges that artifact before implementation. The later review compares the diff, the tests, and the claims to the freeze. A pass, not a test suite alone, is what allows the phase to be marked done. A failure cites what to fix.
Git is the history of the documents and the code. MuseHub is an optional richer history when versions must stay tied across domains. Assistants read the kit's rules from the repository.
Dev Tools is how the family is built. Overseer Kit keeps the plan honest. Agentception coordinates the agents. A person still decides when the work is finished.