memory-operating-system

To maintain persistent context across debugging sessions, use deterministic sessionId stability and mandatory th0th_recall to ground iterative work in prior decisions. This ensures context compounds over time by routing execution through session-scoped th0th_optimized_context calls.

Memory-driven development uses a decision-engine importance rubric to persist architecture decisions, patterns, and ruled-out hypotheses via th0th_remember. It prevents context loss by enforcing recall-based context setup before starting feature development, refactoring, or TDD workflows.

Set up session management by applying projectId resolution to create stable sessionIds for Feature, Review, and ADR workflows. The system orchestrates memory-first context by performing mandatory recall, then routing execution through session-scoped context calls.

Yes, the memory system supports graceful degradation to maintain progress when memory or search is unavailable. It continuously learns by persisting decisions, patterns, trade-offs, and ruled-out hypotheses once availability is restored using th0th_remember.

Yes, you can reuse the same session for debugging the same entity by ensuring deterministic sessionId stability across all th0th context calls. This enforces persistent session management and compounds prior knowledge across Debug, Refactor, and Exploration workflows.