fears-and-doubts

Fears & Doubts — 2026-02-26

Captured so I keep building and don’t stop.

1. Overwhelmed by options

• So many directions to go, where do I even start?
• How do I keep everything structured and not lose anything?

2. Loss of overview

• The repo and vault are growing — not everything fits in my head anymore
• Afraid of forgetting things because I can’t see the full picture

3. Control / trust issues with Claude Code

• I want to know every change Claude Code makes
• I want to read through everything first: understand it, ask questions, add things
• Afraid Claude Code hallucinates (makes things up, writes incorrect info)

4. Fear of stopping

• If I lose momentum now, I might not pick it back up
• Need to keep the barrier to continue low

5. Fear of getting lost

• Sometimes I don’t know how to continue — what’s the next step?
• The system has grown beyond what fits in my head
• I need to trust that things won’t get lost and will surface when needed

6. Wanting everything to surface at the right moment

• Not just capture — I want the system to proactively remind me of things
• If something is relevant to what I’m doing, it should come up automatically
• Don’t want to manually check every file to know what’s going on

---

Practical answers (for future me)

“Where do I start?”

• Start with /status — it shows you exactly where everything stands
• Pick ONE thing. Don’t plan five. Just one.
• The inbox (vault/90_inbox/) is your capture net — nothing gets lost if you dump it there

”How do I keep overview?”

• vault/40_overview/feature-overview.md — your single source of truth for features
• vault/30_daily/changes/ — every change gets logged here
• git log + git diff — you can always see exactly what changed and when

”How do I trust Claude Code?”

• Read the diffs. Before committing, always review git diff
• Use /changelog — forces a written record of what was done
• Git is your safety net — nothing is lost, everything is reversible
• Ask questions. If something looks off, ask “why did you do X?”
• Start small. Let Claude do small tasks first. Build trust incrementally.

”What if Claude hallucinates?”

• Claude can and will occasionally get things wrong — that’s normal
• Verify claims against actual files (read the code, check the vault)
• The vault is YOUR source of truth, not Claude’s memory
• When in doubt: ask Claude to show you the file, not describe it from memory

”How do I not stop?”

• Keep sessions short and focused
• End each session with a clear next step (write it in thoughts or inbox)
• The system is designed to pick up where you left off — that’s the whole point

”I’m lost — what do I do next?”

• Run /status — it tells you exactly where everything stands
• Check vault/90_inbox/ — your future self left notes there
• Ask Claude: “what should I work on next?” — it reads the vault and suggests one thing
• You don’t need to hold everything in your head. That’s what the system is for.

”How do I trust nothing gets lost?”

• Everything you dump in vault/90_inbox/ is captured
• /inbox-review exists to process and sort those notes
• Features are tracked in the overview dashboard
• Git tracks every change ever made — nothing disappears
• The goal is: capture fast, organize later. You only need to trust the capture step.