@joe-broadhead/opencode-mem 0.12.6 → 0.13.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +47 -2
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,51 @@
|
|
|
3
3
|
The format follows Keep a Changelog 1.1.0: one `## [x.y.z] - date` section per
|
|
4
4
|
release.
|
|
5
5
|
|
|
6
|
+
## [0.13.0] - 2026-11-18
|
|
7
|
+
|
|
8
|
+
### Changed
|
|
9
|
+
|
|
10
|
+
- The daily routine and the jobs check what they file before they file it:
|
|
11
|
+
- **Sensitive traits are never stored.** A trait gate reads every claim and every line the journal prints from a
|
|
12
|
+
source, thread titles and Sources included. Its categories are health and disability, religion, political
|
|
13
|
+
opinion, sexual orientation and gender identity, ethnic origin, union membership, criminal record, immigration
|
|
14
|
+
status, pregnancy, biometric and genetic data, age, and family status. A word list always runs; a classifier reads
|
|
15
|
+
what the word list passes, up to 40 lines a call. When a re-run merges an earlier journal, a line that cites an
|
|
16
|
+
event whose title the gate now withholds is dropped, with every other line that cites that event.
|
|
17
|
+
- **A claim the classifier cannot judge is held, never filed and never dropped.** It is retried with a back-off of 1
|
|
18
|
+
to 24 hours until the classifier answers. Health shows the number of holds and the oldest one's age. A held claim
|
|
19
|
+
from a session turn is dropped only when the core, read for that turn's own user and agent, no longer holds the
|
|
20
|
+
turn: a core that fails to answer keeps the claim waiting.
|
|
21
|
+
- **The classifier has one breaker for the whole service,** behind the shared cell breaker, in the daily and in both
|
|
22
|
+
jobs, and its tokens are charged like any other call.
|
|
23
|
+
- **Candidate judgements are never stored:** a ranking, a hire or no-hire, or a score.
|
|
24
|
+
- **Meeting material is proposed, never applied as the person's own words:** notes, summaries, transcripts, minutes
|
|
25
|
+
and recordings that the person organised.
|
|
26
|
+
- **Who the person is, Memory decides,** per binding scheme. A plugin's `self: true` is no longer stored (0.12.6
|
|
27
|
+
stored it, and never trusted it).
|
|
28
|
+
- **No model call mixes sources.** On the labelled days, the daily takes 33 calls and about 60,000 tokens.
|
|
29
|
+
- A forget of a single event leaves a keyed-hash tombstone, and no text.
|
|
30
|
+
|
|
31
|
+
### Added
|
|
32
|
+
|
|
33
|
+
- **The claims log, off by default** (`RECORDS_CLAIMS`). Claims carry counts and up to 20 citations, knowledge keys,
|
|
34
|
+
precedence and pins, projections, a proposed state and rejections. A forget cascades through them, in slices that
|
|
35
|
+
yield, and the maintenance pass finishes one that a crash left pending. An item forget blocks its content from every
|
|
36
|
+
source; a person's erasure blocks only that person's statements. While the flag is off nothing is filed, but an
|
|
37
|
+
erasure still writes keyed-hash marks, with no text, so that turning the flag on later cannot bring erased content
|
|
38
|
+
back.
|
|
39
|
+
|
|
40
|
+
### Fixed
|
|
41
|
+
|
|
42
|
+
- An event whose thread is empty keys its read mark as an event with no thread, so a forget removes that mark too.
|
|
43
|
+
|
|
44
|
+
### Deploy
|
|
45
|
+
|
|
46
|
+
Records only: the plugin is unchanged from 0.12.6. The records service needs a deploy, after 0.12.6's. Additive: the
|
|
47
|
+
`trait_holds` table, the claims tables (`claims`, `claim_marks`, `claim_pins`, `claim_lines`, `claim_refs`,
|
|
48
|
+
`claim_line_cites`, `claim_forget_pending` and `claim_page_writes`), and two columns on `meeting_proposals`, with no
|
|
49
|
+
schema version change.
|
|
50
|
+
|
|
6
51
|
## [0.12.6] - 2026-11-18
|
|
7
52
|
|
|
8
53
|
### Fixed
|
|
@@ -19,8 +64,8 @@ release.
|
|
|
19
64
|
reads at least one unit, and a day that cannot progress is reported, not left to block the others.
|
|
20
65
|
- A model call is charged only the tokens the provider billed. A 429 is honoured with its `Retry-After` and ends the
|
|
21
66
|
run's remaining batches; a provider or network outage trips one breaker for the whole service, not every space's.
|
|
22
|
-
- A read mark goes with the events it is about. A forget, an erasure,
|
|
23
|
-
|
|
67
|
+
- A read mark goes with the events it is about. A forget, an erasure, an unbind and retention delete the marks of the
|
|
68
|
+
units their events were in, so the same ids collected again are read, not skipped as already read.
|
|
24
69
|
- A bind request that names an account probes that account; only a request for `default` adopts the signed-in one.
|
|
25
70
|
- A commitment control needs its `revision` again, and a stale one is refused, naming the current one.
|
|
26
71
|
|