[SLICE 27][CORE-H] Symbolic Memory v1 north-star integration: heterogeneous corpus → durable semantics → bounded zero-model reasoning → learned-history replay #4
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/symbolic-memory#4
Loading…
Add table
Add a link
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?
Parent epic: #19
Umbrella: #11
Depends on: #20-#44 and existing #4-#10 as applicable
Goal
Prove the library as one coherent system rather than a collection of independently green subsystems.
End-to-end fixture:
Required corpus includes at least procedures, technical/system facts, historical events, policy/default+exception, quantitative constraints, attributed conflicting claims, and cross-memory identity references.
Acceptance
With original prose absent from active model context and providers disabled where semantics are already compiled:
model_calls = 0.This issue closes Symbolic Memory v1 implementation, not the broader Machine Spirit milestone. Machine Spirit remains gated by prolog-rlm#405 executable synthesis.
Machine Spirit #405A integration mapping
prolog-rlm#405Anow defines COVENANT-MS as the baseline end-to-end typed contract spine. This #45 fixture is the natural durable-library integration component, but it must not be renamed/reported as Machine Spirit acceptance by itself.For alignment, #45 should emit/retain enough structured identity to populate the synthesis
ms_run_envelope/ conformance capsule: exact source/projection versions, world/frontier cut, semantic/epistemic profile, identity/dependence generations, bounded-projection receipt, procedure/expert/verifier refs when invoked, experience/candidate/promotion lineage, provider/resource usage and replay class.The final known-symbolic route must have original prose absent from active model context and providers disabled with
model_calls=0. Any live model/remote requery during historical replay is a new observation lineage, not exact replay.Current
IMPLEMENTATION-STATUS.mdcorrectly warns that the first remember/get vertical is authored but not yet executable-green; retain that evidence discipline. #405D remains the broader acceptance gate.Refs #11 #19 #43 and prolog-rlm#397/#405/#387/#395.