Telesis Init Review

• Commands listed actually exist and work
• User journeys match real workflows
• Scope boundaries are accurate
• Requirements reflect what the software actually does

MILESTONES.md

• Milestone history aligns with actual release history
• Current milestone is accurate
• Acceptance criteria are verifiable

VISION.md

• Problem statement matches the actual problem
• Design principles reflect real architectural choices

Recovering Lost CLAUDE.md Content

As of v0.27.3, telesis init automatically preserves existing CLAUDE.md sections as notes:

telesis note list -t preserved-claude-md    # Check preserved content

If that didn't capture everything, recover manually:

git show HEAD~1:CLAUDE.md                   # View the old content
git diff HEAD~1:CLAUDE.md CLAUDE.md         # See what changed

Create notes for operational content not captured in generated docs:

telesis note add -t rules "Always use snake_case for database columns"
telesis context                              # Regenerate CLAUDE.md with notes

Common Hallucination Patterns

1. Fabricated directory structure — especially internal/ packages that don't exist
2. False statelessness claims — project may have SQLite, Redis, or file-based state
3. Inferred naming conventions — generated names that don't match reality
4. Over-scoped architecture — describing microservices when it's a monolith
5. Missing dependencies — especially transitive or build-time deps

Workflow After Validation

# 1. Fix docs to match reality
# 2. Create notes for operational content
telesis note add -t rules "..."
# 3. Regenerate context
telesis context
# 4. Verify drift
telesis drift