Where Mycelium fits
Keep three graphs separate, then pass evidence between them.
Wayfinder's decision graph records why a change is wanted and what remains unresolved. Mycelium's application graph records which runtime cells may connect and what values may cross each boundary. FirstMate's delivery state records who is changing what, in which worktree, and with what result.
They are complementary, not interchangeable. A resolved decision can become a cell-level task; a cell contract can become a worker brief; test and review evidence can update delivery state and expose a new decision. Mycelium supplies the missing middle layer between product intent and agent execution.
Read the Mycelium field guide →What Kun Chen actually adds
Let the LLM manage the fleet, not make the human imitate a manager.
FirstMate is a persistent liaison over many replaceable agent sessions. It compiles requests into backlog, brief, status, and report files; dispatches isolated workers; and surfaces only the decisions that need judgment. Around it, treehouse supplies reusable worktrees, gnhf runs small fresh-context iterations with notes, commits, and rollback, and No Mistakes turns review, tests, docs, lint, and CI into a guarded delivery pipeline.
The clever part is the boundary: deterministic scripts own repeatable mechanics and durable state. LLMs interpret goals, generate the uncertain artifacts, inspect evidence, and decide what to try next. The workflow is a sequence of versioned inputs and outputs, not one heroic conversation.
The unanswered question
Is the extra engineering really improving performance?
Treat every practice as a hypothesis. Establish a baseline on comparable tasks with the model and reasoning level held steady. Change one workflow variable, repeat enough runs to expose variance, and keep holdout tasks so the harness cannot memorize the benchmark.
- Outcome
- Completion, escaped defects, acceptance failures
- Effort
- Elapsed time, tokens, cost, human review and rework
- Code health
- Change surface, complexity, test strength, next-change cost
Keep a workflow change only when it improves quality-adjusted cycle time. The reflecting LLM proposes; held-out tests and human outcomes decide.