Files
ClaudeDo/docs/explore-notes
Mika Kuns 08d1797ead chore(claude-do): Mission Control: allgemeiner Session-Handoff an eine frische
## Ziel

Jede Mission-Control-Session (Ad-hoc UND Task-Session) soll ihre Arbeit an eine frische Session
uebergeben koennen: "gib das ab an eine neue Session". Die alte Kachel wird geschlossen, an
derselben Position oeffnet eine frische Session im selben cwd, die mit einem Brief startet, den
die abgebende Session selbst geschrieben hat.

Motivation: eine lange Session mit vollem/verrottetem Kontex

ClaudeDo-Task: 8b846deb-ad10-4243-9272-9aea2a01ec93
2026-09-28 11:57:37 +02:00
..

Explore-notes

Distilled, reusable maps of complex subsystems, produced by deep code exploration. The goal: stop re-exploring the same subsystem from scratch in every new session.

These sit between the CLAUDE.md files and the code:

  • CLAUDE.md — high-level orientation, hand-maintained, always-loaded.
  • explore-notes — deeper subsystem detail (flows, who-calls-whom, invariants) that is too fine-grained for a CLAUDE.md but stable enough to be worth caching. Read on demand.
  • code — the only source of truth.

Index

Note Covers
worker-task-pipeline TaskRunner end-to-end: config resolution, worktree, CLI invocation, streaming, commit
usage-monitoring OAuth usage endpoint, gate, throttle, per-run token accounting, usage pill/modal
external-mcp The claudedo MCP tool surface + its two test-enforced conventions
review-merge Approve=merge-unit, verify gate, MergeCommit/revert, diff stack, conflict resolver
conpty-sessions Interactive/planning/list-handler launch specs + the arg-flattening gotcha
installer-preflight CLI version/login/auto-mode research, the ExecutableResolver/shim root cause, and the Installer's Checks/+SystemCheckPage implementation status
list-virtualization-spike Phase 2a gate spike: virtualized ListBox + the existing ghost-drag InputHitTest model, verified headless

Rules

  • Only stable structure. Flows, responsibilities, entry points, invariants, relative file paths. No line numbers, no exhaustive symbol dumps — those rot fastest.
  • Verify before trusting. A note is a starting map, not authority. Always confirm against current code before acting on it. Each note records the commit it was verified against so you can diff for drift.
  • Not a substitute for CLAUDE.md. If a fact belongs in orientation, put it there.

Header every note must carry

> **Explore-note — verify before trusting.** Distilled map of a subsystem, not authoritative.
> Last verified against commit `<short-hash>` (<date>).
> Drift check: `git log --oneline <short-hash>..HEAD -- <paths this note covers>`
> Stable structure only (no line numbers). See docs/explore-notes/README.md.

Workflow

  1. Before deep-exploring a subsystem, check for a matching note here and read it first; explore only to fill gaps or confirm.
  2. After a deep explore, distill the durable findings into a new/updated note and bump its "verified against" commit line.
  3. If the drift check shows the covered paths changed a lot since the verified commit, treat the note as suspect and re-verify the parts you rely on.