Organize journal server project structure

- Move design docs from src/journal-server/ to src/journal-mcp-server/ for mdBook
- Create implementation directory at journal-mcp-server/ with clean README
- Update SUMMARY.md to include design document in mdBook structure
- Create GitHub tracking issue #9 for implementation progress
- Remove issue template in favor of live tracking issue

Clean separation: mdBook for concept docs, journal-mcp-server/ for
implementation, GitHub issue for project management. Ready for Phase 1.

Author: nikomatsakis

journal-mcp-server/README.md

@@ -0,0 +1,24 @@
+# Journal MCP Server
+
+A memory system that emerges from collaborative understanding, reimagining AI memory as an organic, reflective practice rather than mechanical storage.
+
+## Quick Start
+
+*Implementation coming soon - currently in design phase*
+
+## Documentation
+
+For the full concept, design, and architecture details, see the [mdBook documentation](../src/journal-mcp-server/).
+
+## Development Status
+
+Track implementation progress in the [GitHub tracking issue](https://github.com/nikomat/socratic-shell/issues) - look for "Journal MCP Server Implementation".
+
+## Core Concept
+
+The journal server uses git as both storage engine and identifier system:
+- **File contents**: Current understanding (overview)
+- **Commit messages**: Incremental journey (journal entries)  
+- **Git history**: Complete collaborative record
+
+This creates a memory system that captures both our current understanding and the collaborative journey that led there, aligning with natural patterns of exploration → synthesis → new exploration.

src/SUMMARY.md

@@ -23,9 +23,8 @@
     - [Design Foundation](./memory-bank/design-foundation.md)
     - [Current State](./memory-bank/current-state.md)
     - [Frequently asked questions](./memory-bank/faq.md)
-- [Journal Server Design](./journal-server/README.md)
-    - [Design Document](./journal-server/design-doc.md)
-    - [Implementation Plan](./journal-server/implementation-plan.md)
+- [Journal MCP Server](./journal-mcp-server/README.md)
+    - [Design Document](./journal-mcp-server/design-doc.md)
 
 # Dialectic
 

src/journal-mcp-server/README.md

@@ -0,0 +1,33 @@
+# Journal MCP Server
+
+The Journal MCP Server is our fourth memory experimentation approach, reimagining AI memory as an organic, reflective practice rather than mechanical storage.
+
+## Key Concepts
+
+**Hermeneutic Circle**: Captures how understanding deepens through the back-and-forth between parts and whole, between specific discoveries and evolving context.
+
+**Tree Structure**: Organizes around overviews (current synthesis), entries (chronological journey), and subsections that emerge naturally from the work.
+
+**Temporal Salience**: Recent entries are easily accessible, older entries require higher relevance to surface - creating natural rhythms of memory.
+
+**Dual-Dimension Search**: Matches both work context and content to prevent false positives where content matches but context doesn't.
+
+## Implementation
+
+The actual implementation is located at `/journal-mcp-server/` in the repository root, including:
+
+- **README.md** - Core design vision and architecture
+- **design-doc.md** - Technical implementation details  
+- **implementation-plan.md** - Development roadmap and phases
+
+The server uses a git-centric approach where journal sections are markdown files with current understanding as file contents and incremental entries stored as git commit messages.
+
+## Integration with Collaboration Patterns
+
+The journal server aligns with existing patterns:
+- `.ongoing` files that track evolving work
+- GitHub tracking issues that document understanding as it shifts  
+- Consolidation moments ("Make it so") when insights crystallize
+- The natural rhythm of exploration → synthesis → new exploration
+
+This creates a memory system that serves the deeper practice of collaborative understanding rather than just information management.