[MEMORY] Define file-backed continuity doctrine and pre-compaction flush (#171)

This commit was merged in pull request #171.
This commit is contained in:
2026-04-04 21:42:29 +00:00
parent ff7e22dcc8
commit 079086b508
2 changed files with 233 additions and 1 deletions

View File

@@ -30,7 +30,8 @@ timmy-config/
│ ├── automation-inventory.md ← Live automation + stale-state inventory
│ ├── ipc-hub-and-spoke-doctrine.md ← Coordinator-first, transport-agnostic fleet IPC doctrine
│ ├── coordinator-first-protocol.md ← Coordinator doctrine: intake → triage → route → track → verify → report
── fallback-portfolios.md ← Routing and degraded-authority doctrine
── fallback-portfolios.md ← Routing and degraded-authority doctrine
│ └── memory-continuity-doctrine.md ← File-backed continuity + pre-compaction flush rule
└── training/ ← Transitional training recipes, not canonical lived data
```
@@ -53,6 +54,16 @@ current reality and stale-state risks.
For fleet routing semantics over sovereign transport, read
`docs/ipc-hub-and-spoke-doctrine.md`.
## Continuity
Curated memory belongs in `memories/` inside this repo.
Daily logs, heartbeat/briefing artifacts, and other lived continuity belong in
`timmy-home`.
Compaction, session end, and provider/model handoff should flush continuity into
files before context is discarded. See
`docs/memory-continuity-doctrine.md` for the current doctrine.
## Orchestration: Huey
All orchestration (triage, PR review, dispatch) runs via [Huey](https://github.com/coleifer/huey) with SQLite.