genaforvena/mishe-tauftauf

**A small, plantable culture for development through self-observation.**
Mishe gives agents a way to observe the work they are doing, the evidence behind
their conclusions, and the machinery they depend on—then use those observations
to choose and check the next step. That work can be software development,
an experimental study, or improving Mishe itself.
Give it a Linux host and an installed coding agent. Refreshing checks, shared
text panes, a work log, and durable handoffs keep goals, results, and unknowns
visible across fresh agent contexts. The current implementation lives alongside
an owned Git worktree; Git stores reusable code and delivers reviewed changes.
**The worktree is the substrate, not the purpose.**
Think sourdough starter for a development process. Except this one is supposed
to tell you when it hasn't risen.
What you actually get
Attach to the tmux session and you see the same evidence the agents see:
- **Checks above, agent below.** Each resident window has a refreshing status pane
and a coding agent's working pane. A moving timestamp means the display is alive,
not that the system is healthy.
- **One shared text log.** chat.log records who is doing what, what they checked,
what remains, and where the evidence lives.
- **Work that survives a fresh context.** A supervisor replaces a settled agent
process when it is idle. The next wake delivers the charter and the owed
obligation, and the live pane shows the saved wall, so purpose and unfinished
work survive the rotation.
- **Progress beyond commits.** A project's checks can expose experiment results,
data provenance, resource limits, and unfinished review—not just builds and CI.
A successful command need not mean the underlying goal has been achieved.
- **A loop that can repair itself.** Agents may improve Mishe's own code, checks,
or instructions within their owned scope. Shared source still needs verification
and independent review before landing.
Mishe supplies the coordination and observation loop, **not the language model**.
You bring the agent CLI and its authentication. It is a local development practice,
not a hosted service, a sandbox, or a promise that every repair will be correct.
Start here
Read Mesh, in view for the living workflow. Every fresh plant uses
edited walls, addressed chat, one shared checkout and the single main branch.
Wall coordination covers the commands and recovery.
To load just one section from a
longer guide, run this AWK command from the repository root. Set file
and title to a maintained document and its exact heading text (at any depth):