Slice 2 — persistent facts in HydraMem #28
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
Depends on
#29 Slice 3 — rules before models
Ting/CurryComb
#42 Build: implementation Slices 2→7
Ting/CurryComb
#1 Lower Forgejo issues into OKF evidence with provenance
Ting/CurryComb
Reference
Ting/CurryComb#28
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?
Change package: wiki OpenSpec-28-hydramem-facts — authoritative engineering contract for this Session.
Lower Forgejo structures into authoritative OKF evidence, run the persistent Mnestic projection behind HydraMem's projection interface with atomic generation publish, query bounded fact packs with provenance and watermarks, and prove rebuild equivalence. Design:
docs/handoff.md§HydraMem and Mnestic; authority boundary fixed by ADR-0001.Tasks
Exit (handoff)
Deleting the Mnestic projection and rebuilding changes neither facts nor decisions. #4 is the exit test.
Gates
OD-1 (#34) decides the projection engine; OD-7 (#40) the watermark/deferral policy. #3 and #2 carry specification-completion clauses naming exactly what waits.
Slice 2 — persistent facts in HydraMem
State:
open· Labels: Kind/Feature, Meta/Session · Comments: 0Rendered by CurryComb slice 1 projection v1. The body will be replaced by rule-derived content in Slice 3.
The Session must carry a conformant record: one-line outcome, an explicit child acceptance/exit scenario, and named gate edges. It must state that contract rather than delegating it to wiki or handoff pointers. Audit G42, grooming audit 2026-09-19/20.