Mnestic projection generation behind HydraMem's interface with atomic publish #3
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Meta/Campaign
Meta/Epic
Meta/Session
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Curated
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Scope/Campaign
Status/Abandoned
Status/Blocked
Status/Conflicted
Status/In Progress
Status/In Review
Status/Need Grooming
Status/Need More Info
Status/Ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#28 Slice 2 — persistent facts in HydraMem
Ting/CurryComb
Reference
Ting/CurryComb#3
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Proposal
.hydramem/projections/mnestic/<generation>/: build fresh, validate, atomically advance the generation marker; readers hold stable snapshots; no in-place mutation of a published generation (ADR-0001 §6).Design
docs/handoff.md§HydraMem and Mnestic. Projection interface owned by HydraMem; this unit adds the Mnestic generation writer.Tasks
Requirement scenario
GIVEN a reader on generation N, WHEN generation N+1 publishes, THEN the reader completes on N and the next open sees N+1; a half-written generation is never observable.
Specification-completion clause (OD-1 / #34)
The production storage engine (SQLite vs RocksDB) awaits OD-1. This unit lands the trait plus a test-only engine; the engine module is the only file the ruling touches.
Mnestic projection generation behind HydraMem's interface with atomic publish
State:
open· Labels: Kind/Feature · Comments: 0Rendered by CurryComb slice 1 projection v1. The body will be replaced by rule-derived content in Slice 3.