AbstractMemory 0.3.1__tar.gz → 0.3.2__tar.gz

{abstractmemory-0.3.1 → abstractmemory-0.3.2}/CHANGELOG.md

@@ -9,6 +9,22 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 *No unreleased changes.*
 
+## [0.3.2] - 2026-10-20
+
+### Added
+
+- **A third closure kind, `reinterpreted`**, for an assertion whose reading was
+  superseded by a re-interpretation of its source: the writer no longer reads
+  that source this way (for example, AbstractNote understanding a note again
+  against an earlier foundation withdraws its previous reading). It is neither
+  `retract` (the fact was wrong) nor `supersede` (a later fact replaced it).
+  `ClosureRecord`, `close_assertions` and `close_record` accept it;
+  `replacement_ids` is optional (the new reading's assertions, when there are
+  any); like the other kinds, a `reinterpreted` closure takes the assertion out
+  of ranked retrieval while it stays in the store and in history. The accepted
+  kinds are listed in `abstractmemory.journal.CLOSURE_KINDS`.
+  Additive: existing callers and stored journals are unaffected.
+
 ## [0.3.1] - 2026-10-19
 
 ### Added

{abstractmemory-0.3.1 → abstractmemory-0.3.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: AbstractMemory
-Version: 0.3.1
+Version: 0.3.2
 Summary: AbstractMemory: temporal, provenance-aware semantic memory primitives for AbstractFramework.
 Project-URL: AbstractFramework (monorepo), https://github.com/lpalbou/abstractframework
 Author: Laurent-Philippe Albou
@@ -164,7 +164,7 @@ system.commit_selection(result.trace_id, [h.record_id for h in result.handles[:2
 
 ## Design principles
 
-- **Append-only, no deletion**: updates are new assertions; belief revision is closure records (retract/supersede); forgetting is decay of retrieval strength plus closures and silencing — the substrate is lossless.
+- **Append-only, no deletion**: updates are new assertions; belief revision is closure records (retract/supersede/reinterpreted); forgetting is decay of retrieval strength plus closures and silencing — the substrate is lossless.
 - **Reads are pure**: reconstruction, inspection, replay, and the entity card deposit nothing. `commit_selection` is the only strengthening path.
 - **One seq axis**: the journal assigns a monotonic `seq` to every record; any past state is reproducible by anchoring reads at `as_of`.
 - **Works-or-loud**: degraded paths are labeled `#FALLBACK` in result warnings; invalid inputs raise actionable errors instead of silently meaning something else.

{abstractmemory-0.3.1 → abstractmemory-0.3.2}/README.md

@@ -128,7 +128,7 @@ system.commit_selection(result.trace_id, [h.record_id for h in result.handles[:2
 
 ## Design principles
 
-- **Append-only, no deletion**: updates are new assertions; belief revision is closure records (retract/supersede); forgetting is decay of retrieval strength plus closures and silencing — the substrate is lossless.
+- **Append-only, no deletion**: updates are new assertions; belief revision is closure records (retract/supersede/reinterpreted); forgetting is decay of retrieval strength plus closures and silencing — the substrate is lossless.
 - **Reads are pure**: reconstruction, inspection, replay, and the entity card deposit nothing. `commit_selection` is the only strengthening path.
 - **One seq axis**: the journal assigns a monotonic `seq` to every record; any past state is reproducible by anchoring reads at `as_of`.
 - **Works-or-loud**: degraded paths are labeled `#FALLBACK` in result warnings; invalid inputs raise actionable errors instead of silently meaning something else.

{abstractmemory-0.3.1 → abstractmemory-0.3.2}/docs/api.md

@@ -135,7 +135,7 @@ Record families (all append-only, all `seq`-stamped by the journal):
 
 - `MemoryEvent` — attention events. Scoring kinds: `selected`, `co_selected` (pair trails), `pinned`, `silenced`; decay marker: `refocus`; audit-only (recorded, never scored): `listed`, `shown`, `expanded`, `cited`.
 - `ScopeBinding` — visibility: `search_state` (`indexed`/`hidden`), `prompt_state` (`active`/`inactive`), `lifecycle`, `source`, `reason`. Latest per `(record_id, scope, owner_id)` wins; `fold_bindings(bindings)` applies that fold.
-- `ClosureRecord` — belief lifecycle: `kind` (`retract`/`supersede`), mandatory `reason`, `replacement_ids` (required for supersede).
+- `ClosureRecord` — belief lifecycle: `kind` (`retract`/`supersede`/`reinterpreted`), mandatory `reason`, `replacement_ids` (required for supersede, optional otherwise). `reinterpreted` means the writer no longer reads its source this way (a note understood again): neither a correction nor a later fact; it leaves ranked retrieval like the others.
 - `ReconstructionTrace` — one recall: fingerprint, searched scopes, candidates, selected/dropped, cues, budgets, admission labels, warnings.
 - `ActiveMemorySnapshot` — see seam types.
 - `ValenceEvent` — signed appraisals and standing markers (see valence below).
@@ -186,7 +186,7 @@ Diary formation rules: `kind="diary"` requires `provenance.source` ∈ {`diary-p
 ### Bindings and closures
 
 - `bind(record_id, *, scope, owner_id, search_state, prompt_state="inactive", lifecycle="none", source="operator", reason=None, binding_id=None) -> ScopeBinding` — append a visibility event. A folded `hidden` binding removes the record from ranked retrieval in that scope pair only; re-binding `indexed` restores it. `prompt_state="active"` admits the record into the identity (self) component. Record-level bindings hide the digest and its edge assertions together. Direct `store.query` id lookups bypass folds by design.
-- `close_assertions(assertion_ids, *, kind, replacement_ids=(), reason) -> list[str]` — append one closure per assertion (`retract` | `supersede`).
+- `close_assertions(assertion_ids, *, kind, replacement_ids=(), reason) -> list[str]` — append one closure per assertion (`retract` | `supersede` | `reinterpreted`).
 - `close_record(record_id, *, reason, kind="retract", replacement_ids=()) -> list[str]` — close a whole record (digest and its edges) as one belief-revision act; closure ids are deterministic, so replays dedupe.
 
 ### Identity: spark, engram, self core, floors

{abstractmemory-0.3.1 → abstractmemory-0.3.2}/docs/architecture.md

@@ -62,7 +62,7 @@ The same discipline extends to every derived read: inspection (`activation`, `ac
 There is no delete surface anywhere in the package:
 
 - Updates are new assertions with fresh provenance.
-- Belief revision is a `ClosureRecord` (`retract` or `supersede` with replacements) — the old record leaves ranked retrieval but remains in the store and in history.
+- Belief revision is a `ClosureRecord` (`retract`, `supersede` with replacements, or `reinterpreted` when the writer reads the source differently) — the old record leaves ranked retrieval but remains in the store and in history.
 - Visibility is a `ScopeBinding` fold (latest per record/scope/owner wins): `hidden` removes a record from ranked retrieval in that scope pair only; re-binding `indexed` restores it.
 - Forgetting is decay of retrieval strength plus closures and silencing. Storage never decays; only the temporal-access signal does. The global access count (`selected_count`) never decays at all.
 

{abstractmemory-0.3.1 → abstractmemory-0.3.2}/docs/faq.md

@@ -39,7 +39,7 @@ Canonicalization (trim + lowercase) is part of the matching contract: it prevent
 There is no update or delete API, by design:
 
 - At layer 1, represent changes by adding a new assertion with fresh provenance. When the new assertion supersedes an earlier one, `close_assertion(assertion_id, valid_until)` (in-memory and SQLite stores) closes the earlier validity window in place, so `TripleQuery(active_at=...)` stops returning it from that moment; nothing else about the row changes.
-- At layer 2, belief revision is a closure record (`close_record` / `close_assertions`: retract or supersede with replacements) — the old record leaves ranked retrieval but stays in the store and in history. Visibility can also be withdrawn per scope with a `hidden` binding and restored with `indexed`.
+- At layer 2, belief revision is a closure record (`close_record` / `close_assertions`: retract, supersede with replacements, or reinterpreted when the source is read differently) — the old record leaves ranked retrieval but stays in the store and in history. Visibility can also be withdrawn per scope with a `hidden` binding and restored with `indexed`.
 - Forgetting is decay of retrieval strength plus closures and silencing. The substrate is lossless; there is no compaction.
 
 ## What do `scope` and `owner_id` mean?

{abstractmemory-0.3.1 → abstractmemory-0.3.2}/docs/troubleshooting.md

@@ -70,7 +70,7 @@ explain_recall(store, journal, record_id, trace_id=trace_id)
 recall_history(journal, record_id)
 ```
 
-`absence_diagnosis` reports structural reasons in plain sentences (never formed, retracted, hidden, out of scope, vectorless). `explain_recall` answers the same question against one specific recall. Common structural causes: the record is in a scope the ladder does not include; a closure retracted or superseded it; it is an inactive candidate; or it was formed after the `as_of` seq you anchored to.
+`absence_diagnosis` reports structural reasons in plain sentences (never formed, retracted, hidden, out of scope, vectorless). `explain_recall` answers the same question against one specific recall. Common structural causes: the record is in a scope the ladder does not include; a closure retracted, superseded or reinterpreted it; it is an inactive candidate; or it was formed after the `as_of` seq you anchored to.
 
 ### Recall results change between runs with the same input
 

{abstractmemory-0.3.1 → abstractmemory-0.3.2}/llms-full.txt

@@ -154,7 +154,7 @@ system.commit_selection(result.trace_id, [h.record_id for h in result.handles[:2
 
 ## Design principles
 
-- **Append-only, no deletion**: updates are new assertions; belief revision is closure records (retract/supersede); forgetting is decay of retrieval strength plus closures and silencing — the substrate is lossless.
+- **Append-only, no deletion**: updates are new assertions; belief revision is closure records (retract/supersede/reinterpreted); forgetting is decay of retrieval strength plus closures and silencing — the substrate is lossless.
 - **Reads are pure**: reconstruction, inspection, replay, and the entity card deposit nothing. `commit_selection` is the only strengthening path.
 - **One seq axis**: the journal assigns a monotonic `seq` to every record; any past state is reproducible by anchoring reads at `as_of`.
 - **Works-or-loud**: degraded paths are labeled `#FALLBACK` in result warnings; invalid inputs raise actionable errors instead of silently meaning something else.
@@ -389,7 +389,7 @@ The same discipline extends to every derived read: inspection (`activation`, `ac
 There is no delete surface anywhere in the package:
 
 - Updates are new assertions with fresh provenance.
-- Belief revision is a `ClosureRecord` (`retract` or `supersede` with replacements) — the old record leaves ranked retrieval but remains in the store and in history.
+- Belief revision is a `ClosureRecord` (`retract`, `supersede` with replacements, or `reinterpreted` when the writer reads the source differently) — the old record leaves ranked retrieval but remains in the store and in history.
 - Visibility is a `ScopeBinding` fold (latest per record/scope/owner wins): `hidden` removes a record from ranked retrieval in that scope pair only; re-binding `indexed` restores it.
 - Forgetting is decay of retrieval strength plus closures and silencing. Storage never decays; only the temporal-access signal does. The global access count (`selected_count`) never decays at all.
 
@@ -664,7 +664,7 @@ Record families (all append-only, all `seq`-stamped by the journal):
 
 - `MemoryEvent` — attention events. Scoring kinds: `selected`, `co_selected` (pair trails), `pinned`, `silenced`; decay marker: `refocus`; audit-only (recorded, never scored): `listed`, `shown`, `expanded`, `cited`.
 - `ScopeBinding` — visibility: `search_state` (`indexed`/`hidden`), `prompt_state` (`active`/`inactive`), `lifecycle`, `source`, `reason`. Latest per `(record_id, scope, owner_id)` wins; `fold_bindings(bindings)` applies that fold.
-- `ClosureRecord` — belief lifecycle: `kind` (`retract`/`supersede`), mandatory `reason`, `replacement_ids` (required for supersede).
+- `ClosureRecord` — belief lifecycle: `kind` (`retract`/`supersede`/`reinterpreted`), mandatory `reason`, `replacement_ids` (required for supersede, optional otherwise). `reinterpreted` means the writer no longer reads its source this way (a note understood again): neither a correction nor a later fact; it leaves ranked retrieval like the others.
 - `ReconstructionTrace` — one recall: fingerprint, searched scopes, candidates, selected/dropped, cues, budgets, admission labels, warnings.
 - `ActiveMemorySnapshot` — see seam types.
 - `ValenceEvent` — signed appraisals and standing markers (see valence below).
@@ -715,7 +715,7 @@ Diary formation rules: `kind="diary"` requires `provenance.source` ∈ {`diary-p
 ### Bindings and closures
 
 - `bind(record_id, *, scope, owner_id, search_state, prompt_state="inactive", lifecycle="none", source="operator", reason=None, binding_id=None) -> ScopeBinding` — append a visibility event. A folded `hidden` binding removes the record from ranked retrieval in that scope pair only; re-binding `indexed` restores it. `prompt_state="active"` admits the record into the identity (self) component. Record-level bindings hide the digest and its edge assertions together. Direct `store.query` id lookups bypass folds by design.
-- `close_assertions(assertion_ids, *, kind, replacement_ids=(), reason) -> list[str]` — append one closure per assertion (`retract` | `supersede`).
+- `close_assertions(assertion_ids, *, kind, replacement_ids=(), reason) -> list[str]` — append one closure per assertion (`retract` | `supersede` | `reinterpreted`).
 - `close_record(record_id, *, reason, kind="retract", replacement_ids=()) -> list[str]` — close a whole record (digest and its edges) as one belief-revision act; closure ids are deterministic, so replays dedupe.
 
 ### Identity: spark, engram, self core, floors
@@ -1280,7 +1280,7 @@ Canonicalization (trim + lowercase) is part of the matching contract: it prevent
 There is no update or delete API, by design:
 
 - At layer 1, represent changes by adding a new assertion with fresh provenance. When the new assertion supersedes an earlier one, `close_assertion(assertion_id, valid_until)` (in-memory and SQLite stores) closes the earlier validity window in place, so `TripleQuery(active_at=...)` stops returning it from that moment; nothing else about the row changes.
-- At layer 2, belief revision is a closure record (`close_record` / `close_assertions`: retract or supersede with replacements) — the old record leaves ranked retrieval but stays in the store and in history. Visibility can also be withdrawn per scope with a `hidden` binding and restored with `indexed`.
+- At layer 2, belief revision is a closure record (`close_record` / `close_assertions`: retract, supersede with replacements, or reinterpreted when the source is read differently) — the old record leaves ranked retrieval but stays in the store and in history. Visibility can also be withdrawn per scope with a `hidden` binding and restored with `indexed`.
 - Forgetting is decay of retrieval strength plus closures and silencing. The substrate is lossless; there is no compaction.
 
 ## What do `scope` and `owner_id` mean?
@@ -1413,7 +1413,7 @@ explain_recall(store, journal, record_id, trace_id=trace_id)
 recall_history(journal, record_id)
 ```
 
-`absence_diagnosis` reports structural reasons in plain sentences (never formed, retracted, hidden, out of scope, vectorless). `explain_recall` answers the same question against one specific recall. Common structural causes: the record is in a scope the ladder does not include; a closure retracted or superseded it; it is an inactive candidate; or it was formed after the `as_of` seq you anchored to.
+`absence_diagnosis` reports structural reasons in plain sentences (never formed, retracted, hidden, out of scope, vectorless). `explain_recall` answers the same question against one specific recall. Common structural causes: the record is in a scope the ladder does not include; a closure retracted, superseded or reinterpreted it; it is an inactive candidate; or it was formed after the `as_of` seq you anchored to.
 
 ### Recall results change between runs with the same input
 

{abstractmemory-0.3.1 → abstractmemory-0.3.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "AbstractMemory"
-version = "0.3.1"
+version = "0.3.2"
 description = "AbstractMemory: temporal, provenance-aware semantic memory primitives for AbstractFramework."
 readme = "README.md"
 requires-python = ">=3.10"

abstractmemory-0.3.2/release-notes.md

@@ -0,0 +1,13 @@
+### Added
+
+- **A third closure kind, `reinterpreted`**, for an assertion whose reading was
+  superseded by a re-interpretation of its source: the writer no longer reads
+  that source this way (for example, AbstractNote understanding a note again
+  against an earlier foundation withdraws its previous reading). It is neither
+  `retract` (the fact was wrong) nor `supersede` (a later fact replaced it).
+  `ClosureRecord`, `close_assertions` and `close_record` accept it;
+  `replacement_ids` is optional (the new reading's assertions, when there are
+  any); like the other kinds, a `reinterpreted` closure takes the assertion out
+  of ranked retrieval while it stays in the store and in history. The accepted
+  kinds are listed in `abstractmemory.journal.CLOSURE_KINDS`.
+  Additive: existing callers and stored journals are unaffected.

{abstractmemory-0.3.1 → abstractmemory-0.3.2}/src/abstractmemory/journal.py

@@ -221,12 +221,22 @@ class ScopeBinding:
         return _jsonify(asdict(self))
 
 
+#: The closure kinds a ClosureRecord accepts (``reinterpreted`` is additive, 0.3.2).
+CLOSURE_KINDS = frozenset({"retract", "supersede", "reinterpreted"})
+
+
 @dataclass(frozen=True)
 class ClosureRecord:
-    """Append-only belief-lifecycle record (backlog 0010): retract or supersede."""
+    """Append-only belief-lifecycle record (backlog 0010): retract, supersede or reinterpreted.
+
+    ``reinterpreted`` (additive, 0.3.2): the writer no longer reads its source this way (AbstractNote ADR 0008: a
+    note understood again against an earlier foundation withdraws its previous reading). It is neither a
+    correction of the fact (``retract``) nor a later fact replacing it (``supersede``); like both it leaves
+    ranked retrieval. ``replacement_ids`` is optional (the new reading's assertions, when there are any).
+    """
 
     assertion_id: str
-    kind: str                        # retract | supersede
+    kind: str                        # retract | supersede | reinterpreted
     reason: str
     replacement_ids: Tuple[str, ...] = ()
     observed_at: str = field(default_factory=utc_now_iso)
@@ -240,8 +250,8 @@ class ClosureRecord:
             raise ValueError("ClosureRecord requires assertion_id")
         object.__setattr__(self, "assertion_id", self.assertion_id.strip())
         kind = str(self.kind or "").strip().lower()
-        if kind not in {"retract", "supersede"}:
-            raise ValueError("ClosureRecord.kind must be 'retract' or 'supersede'")
+        if kind not in CLOSURE_KINDS:
+            raise ValueError("ClosureRecord.kind must be 'retract', 'supersede' or 'reinterpreted'")
         object.__setattr__(self, "kind", kind)
         if not (isinstance(self.reason, str) and self.reason.strip()):
             raise ValueError("ClosureRecord requires a non-empty reason")

{abstractmemory-0.3.1 → abstractmemory-0.3.2}/src/abstractmemory/system.py

@@ -853,7 +853,8 @@ class MemorySystem(ValenceOps, AccessOps):
         replacement_ids: Sequence[str] = (),
         reason: str,
     ) -> List[str]:
-        """Append one ClosureRecord per assertion (retract | supersede);
+        """Append one ClosureRecord per assertion (retract | supersede |
+        reinterpreted);
         returns closure ids. Supersede requires replacement_ids; reason is
         mandatory — validated by ClosureRecord BEFORE any append. A multi-
         assertion supersede shares one replacement set. Accepts either id

{abstractmemory-0.3.1 → abstractmemory-0.3.2}/tests/test_journal_backends.py

@@ -462,6 +462,21 @@ def test_record_validation_errors_surface() -> None:
         make_event(kind="co_selected", pair_ids=("rec-a", "rec-a"))
 
 
+def test_reinterpreted_closure_kind(journal) -> None:
+    """Additive closure kind (0.3.2): a source read again withdraws its previous reading; replacements optional."""
+    from abstractmemory.journal import CLOSURE_KINDS
+
+    assert "reinterpreted" in CLOSURE_KINDS
+    journal.append_closure(make_closure(assertion_id="as-r", kind="reinterpreted", reason="read again"))
+    journal.append_closure(make_closure(assertion_id="as-s", kind="REINTERPRETED", reason="read again",
+                                        replacement_ids=("as-t",)))
+    got = {c.assertion_id: c for c in journal.closures()}
+    assert got["as-r"].kind == "reinterpreted" and got["as-r"].replacement_ids == ()
+    assert got["as-s"].kind == "reinterpreted" and got["as-s"].replacement_ids == ("as-t",)
+    with pytest.raises(ValueError, match="kind"):
+        make_closure(kind="revised")
+
+
 # ---------------------------------------------------------------------------
 # JSON round-trip
 # ---------------------------------------------------------------------------

abstractmemory-0.3.1/release-notes.md

@@ -1,12 +0,0 @@
-### Added
-
-- **`close_assertion(assertion_id, valid_until)`** on `SQLiteTripleStore` and
-  `InMemoryTripleStore`: closes an assertion's open validity window in place
-  (only while `valid_until` is still empty; terms, provenance, attributes,
-  keyword index and vector are untouched) and returns whether a row changed
-  (`False` for an unknown id or a window that is already closed). A writer
-  that supersedes a fact can make `TripleQuery(active_at=...)` agree with its
-  own belief window, where a layer-2 closure record only reaches ranked
-  retrieval. Existing callers are unaffected; `add` stays append-only and
-  `LanceDBTripleStore` keeps the protocol surface (`add`, `query`, `close`).
-  Contributed by the AbstractNote lane.