docs/architecture/messaging-and-work-intake.md:107 requires the canonical session and message implementation to supply durable SQLite round trips. The current store is NellDB-backed.
Scope is the SETTLED parts of the messaging architecture only:
SQLite persistence (modernc.org/sqlite; FTS5 verified available at 3.53.3, no CGo)
application-generated canonical MessageID, platform IDs as correlation only (doc 88-90)
immutable message records (doc 112-114)
append-only linear sequence per conversation (doc 128)
real transactions for ReplaceMessages and Delete
Explicitly OUT of scope: the rich typed-content / tool-call / tool-result model and delivery-attempt semantics. docs/architecture/messaging-and-work-intake.md:273-284 lists the canonical inbound message model, source-correlation model, and outbound delivery/retry/dedup semantics as DECISIONS STILL REQUIRED, so they are not specified enough to implement. That work belongs to archie-core-abg.16.
Decision by Sam 2026-08-03 after the third review surfaced that the NellDB-vs-SQLite question was already settled by the architecture docs.
Imported from beads archie-core-1786637491855-79-803fa759 · GitHub #100 · type task · priority P2 · created 2026-08-08 · closed 2026-08-09
docs/architecture/messaging-and-work-intake.md:107 requires the canonical session and message implementation to supply durable SQLite round trips. The current store is NellDB-backed.
Scope is the SETTLED parts of the messaging architecture only:
- SQLite persistence (modernc.org/sqlite; FTS5 verified available at 3.53.3, no CGo)
- application-generated canonical MessageID, platform IDs as correlation only (doc 88-90)
- immutable message records (doc 112-114)
- append-only linear sequence per conversation (doc 128)
- real transactions for ReplaceMessages and Delete
Explicitly OUT of scope: the rich typed-content / tool-call / tool-result model and delivery-attempt semantics. docs/architecture/messaging-and-work-intake.md:273-284 lists the canonical inbound message model, source-correlation model, and outbound delivery/retry/dedup semantics as DECISIONS STILL REQUIRED, so they are not specified enough to implement. That work belongs to archie-core-abg.16.
Decision by Sam 2026-08-03 after the third review surfaced that the NellDB-vs-SQLite question was already settled by the architecture docs.
---
_Imported from beads `archie-core-1786637491855-79-803fa759` · GitHub #100 · type task · priority P2 · created 2026-08-08 · closed 2026-08-09_
sam
added the mediumtask labels 2026-10-27 13:37:00 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
docs/architecture/messaging-and-work-intake.md:107 requires the canonical session and message implementation to supply durable SQLite round trips. The current store is NellDB-backed.
Scope is the SETTLED parts of the messaging architecture only:
Explicitly OUT of scope: the rich typed-content / tool-call / tool-result model and delivery-attempt semantics. docs/architecture/messaging-and-work-intake.md:273-284 lists the canonical inbound message model, source-correlation model, and outbound delivery/retry/dedup semantics as DECISIONS STILL REQUIRED, so they are not specified enough to implement. That work belongs to archie-core-abg.16.
Decision by Sam 2026-08-03 after the third review surfaced that the NellDB-vs-SQLite question was already settled by the architecture docs.
Imported from beads
archie-core-1786637491855-79-803fa759· GitHub #100 · type task · priority P2 · created 2026-08-08 · closed 2026-08-09