rajamesandClaude Opus 5.5
7aed588f78
docs/CLAUDE.md Phase 2, 2026-10-14. All moves by git mv; every archived file carries a header saying what it is, why, and where to look instead. - docs/reference/ (new): roadmap and versioning policy, M7.1, word-ACL design, kernel args, hosted acceptance test, dictionary, primitives, ontology, L8 table -- previously spread over docs/, docs/lithosananke/ and docs/03-architecture/. - docs/working/archive/historical/: finished work (session plan, test-gap audit, birthing plan, fix write-ups, the January architecture draft). - docs/working/archive/superseded/: the Hermes-VM Tripod docs and July Hermes designs (-> FABRIC-3.5/3.6), the StarForth roadmap, every working doc already flagged superseded or obsolete. - docs/working/archive/dead/: the hal_* target contract (never adopted), L4Re, metrics-and-knobs. - Papers and proposals into docs/working/papers/. - References rewritten across the repo (not logs/, not docs/patent/); CLAUDE.md's documentation section rewritten. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Session Logs
Historical development session summaries preserved for context and reference.
Purpose
These are informal notes from development sessions, documenting:
- Long debugging sessions with significant findings
- Experimental iterations and design decisions
- Development context and rationale
- Dead-ends and lessons learned
When to Create Session Logs
✅ Do create session logs for:
- Multi-hour debugging sessions with important discoveries
- Experimental work with multiple failed attempts before success
- Design discussions that made important architectural decisions
- Complex refactoring with non-obvious rationale
❌ Don't create session logs for:
- Routine development (use git commit messages instead)
- Formal documentation (use appropriate numbered directory)
- Final implementation details (use architecture docs)
Important Notes
⚠️ Session logs are archival and may contain outdated information
- Always consult current documentation first
- Information here reflects the state at the time of writing
- Design decisions may have been revised
- Code examples may be superseded
Contents
- 2025-11-20-recap.md - Development recap session
- 2025-11-26-worklog.md - Work log summary
- experimental-addendum.md - Experimental work notes
- experimental-iteration-usage.md - Iteration notes
- serialized-questing-pike.md - Design exploration notes
Relationship to Formal Documentation
Session logs supplement formal documentation but don't replace it:
| Session Logs | Formal Documentation |
|---|---|
| Informal notes | Structured guides |
| Point-in-time snapshots | Maintained and current |
| Developer perspective | User/maintainer perspective |
| Context and rationale | How-to and reference |
For Current Developers
If you're looking for information:
- Check formal docs first:
../01-getting-started/,../03-architecture/, etc. - Search session logs if you need historical context
- Update formal docs if you find valuable information only in session logs
For Historical Research
Session logs provide valuable insight into:
- Development process and methodology
- Design evolution over time
- Challenges faced and solutions developed
- Team decision-making rationale