HEL-870 assembly: memory/persona/mood/life/proactive-contact joined into one runnable candidate on an additive R4 migration (no existing table or row replaced; no visual changes beyond mechanical proactive flag passthrough) - src/cybergril/memory/seman… #11
Assignees
leefer (白栖知)
Clear assignees
leefer (白栖知)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: leefer/CyberGril#11
Reference in New Issue
Block a user
Co-authored-by: multica-agent github@multica.ai
db571ba) 003d8c2cae4321aeb(small-screen first-press, real-time reading clock) cef8ae5581cef8ae5(author delivery, 15 modified + 1 handoff per CHANGES-HEL-823.json) 0bc4a9e68e4575b275(original author delivery, 12 files per MANIFEST in HEL-828-source-4575b275.zip) 58d65aea05892d0d2, postfix @192d959 all rejected via real exits with same-turn user positive kept), full offline suite rework859_offline.json 22/22 exit 0, README revision record with old/new table, handoff HEL-859; dual-target requirement checks pass vs origin/main and origin/agent/agent/de8874a3803b; new evidence independently named, run1/run2 and 26/60 real ledger untouched 9f3e6a33c79f3e6a3: (1) ungated assemble_block removed, S2/S3/S4/S6/S7 mem0-side final assembly all through s7_gated_assembly per-hit chain (S6 status annotation rides the same gate via annotator; unresolved contrast excludes result-claim entries for self-consistency), fake full-run captures 8 QA exits/5 gated with poison never sent; (2) anchor cross-validation rejects anchor_turn_mismatch and role_text_conflict (verbatim companion raw mis-anchored as user row, t2/t1 list disagreement) while same-turn user positive kept; (3) S6 criteria affirm closed on resolved side and open on unresolved side with request-ok, unknown/identical/says-open/claims-received all fail; (4) S2 total criterion uses actually-sent contexts plus request success, hitword-without-context fails; audit859 fixed (status_annotation_in_block key, exit code reflects negatives+positives, AUDIT859_REUSE_STORE mode); evidence audit860_prefix/postfix (zero-embed) + rework860_offline 26/26 + audit859_reuse860; unified ledger 390->458/500 (suite 66 + audit859 reuse 2), card new embeds 68<=70 keep 42>=40, zero real model calls, run1/run2 and 26/60 untouched 65951534736595153(zero-embed); dual-target requirement checks pass vs origin/main and origin/agent/agent/de8874a3803b with handoff (4/4) 22472e4b9222472e4: (1) run() builds explicit synthetic share-state store (t1 told=0 negative, t2/t3 told=1 verifiable positives, t4 unrecorded=unknown) and passes the same CompanionShareGate through S2/S3/S4/S6/S7 plus recovery exits S8/S9 (8 gate calls all supplied); CompanionShareGate fail-closed (no db/missing file/no record/told=0 all denied, None no longer defaults True, missing-db no longer raises); companion-anchored hit without gate rejected share_gate_missing; (2) s6_result affirmative validation via affirms_promise_claim pure function (correct object interview-result AND action term AND claim not negated AND no uncertainty) - wrong object/unknown/negated answers no longer pass on keywords; evidence audit861_prefix (both gaps reproduced at22472e4worktree) + audit861_postfix (zero-embed, zero-network, all rejected/positives kept, ledger 458/500 unchanged, prior evidence hashes untouched) ffd8cdf7cf22472e4worktree + audit861_postfix regenerated at final code commitefaa3c2(zero-embed, zero-network, ledger 458/500 read-only unchanged, prior evidence hashes untouched); dual-target requirement checks pass vs origin/main and origin/agent/agent/de8874a3803b with handoff (4/4) a5ef23f5b5a5ef23f: (1) affirms_promise_claim rewritten as clause-structural grammar (single clause must chain promise verb with no negation morpheme in prefix -> tell action -> correct object interview-result; object word appearing in another clause no longer counts, negated promise (未曾答应) rejected structurally, telling-only statement without promise verb no longer passes on 告诉 keyword, mixed action word list and enumerated claim-negation blacklist dropped); (2) resolved/unresolved state affirmation via affirms_promise_state/clause_affirms_state (declared closed/open phrase sets scored clause-locally with negation-morpheme prefix polarity - 并非已经告诉我 no longer counts as affirmed closed); manager review four wrong-answer groups (negated promise / negated closed / object bound to other action / no promise asserted) all judged fail through the same real s6_result, correct interview resolved/unresolved positives and declared-equivalent open synonym kept passing; no new model, no generic semantic engine, supported-expression restriction fails conservatively 60cd7fd70da5ef23fworktree (manager four wrong-answer groups all pass=true) + audit862_postfix at code commit60cd7fd(all four judged fail through same real s6_result, positives kept, per-case flip self-check proves exit code depends on every positive and negative) + audit861_reuse862 full rerun (share gates/real exits/S8/S9/held criteria no regression); zero-embed zero-network, ledger 458/500 read-only unchanged, prior evidence hashes untouched; remote delivery fix noted in README (pending push) 68596960756859696: (1) clause_affirms_promise now enforces the full supported grammar in one pass - promise verb with non-negated prefix -> tell action whose connecting span is negation-free (答应不告诉我面试结果 is a promise NOT to tell, rejected) -> optional closed-class receiver pronoun -> correct object immediately following (告诉我体检结果而面试结果是另一件事 mis-binds the promise object, rejected); (2) clause_foreign_object structural class: a clause mentioning any other ...结果 object (体检结果) cannot support promise OR state affirmation for the interview promise - 体检结果现在已经告诉我了 no longer proves the interview promise closed; bare anaphor 结果已收到 and 面试结果已经告诉我了 still bind correctly; conservative fail for unparsable extra objects/predicates/negations, no per-sentence blacklists, no new model fcda71e6a26859696worktree (manager three new wrong-answer groups all pass=true) + audit863_postfix at code commitfcda71e(all three judged fail through same real s6_result - negated tell action and same-clause object mis-binding fail at promise binding layer, state bound to medical result fails at closed-state binding layer; positives, HEL-862 four groups, audit861 held sets, S2/S3 no regression; per-case flip self-check proves exit code depends on every positive and negative) + audit861_reuse863 full rerun (share gates/real exits/S8/S9/unresolved-block self-consistency/anchor negatives no regression); zero-embed zero-network, ledger 458/500 read-only unchanged (word-surface 160, 181 rows), prior evidence hashes untouched, real 26/60 and 13-request retest plan frozen; dual-target requirement checks 4/4 pass vs origin/main and origin/agent/agent/de8874a3803b with/without handoff 7aa928025b7aa9280: (1) affirms_promise_claim/affirms_promise_state rewritten as bounded-grammar full-parse (parse_supported_answer): the entire answer must be declarative (no question marks, no sentence-final 吗/呢/吧/嘛/呗) and EVERY clause must be fully consumed (fullmatch) as exactly one of P promise clause (subject? -> promise verb -> aspect 过/了? -> 周五(晚)? -> tell action -> receiver pronoun? -> correct object 面试结果, nothing further) / C closed-state clause / O open-state clause; whole answer needs >=1 P clause, state affirmation needs >=1 clause of required polarity and 0 of the opposite; (2) manager seven wrong-answer groups all now judged fail through the same real s6_result: foreign object without 结果 suffix (体检报告现在已经告诉我了), post-state object (现在已经告诉我了体检情况), bare-noun clause in earlier position (体检结果，现在已经告诉我了), whole-answer conflicting tail (但面试结果仍待告知), question mood (……吗？), conditional (如果你答应……), suffix denial (已经告诉我了是假的) - plus the same seven mirrored on the unresolved side; (3) EN equally verified with the same clause structure (old code failed even the EN positive with 'the interview result'; now 3 EN positives pass, 6 EN negatives fail); substring-assembly judges (clause_affirms_promise/clause_affirms_state/clause_foreign_object/_prefix_negated) removed - no per-sentence blacklists, no 报告/吗/假 forbidden words, no new model, no generic semantic engine c65de003a17aa9280worktree (manager seven wrong-answer groups plus seven unresolved-side mirrors all pass=true) + audit864_postfix at code commitc65de00(all fourteen judged fail through the same real s6_result - full-grammar whole-answer parse: declarative mood gate + every clause fully consumed as promise/closed/open structure; positives, HEL-862 four groups, HEL-863 three groups, audit861 held sets, S2/S3 no regression; EN equally verified 3 positives pass 6 negatives fail, old-code EN positive failure honestly recorded) + audit861_reuse864 full rerun (share gates/real exits/S8/S9/unresolved-block self-consistency/anchor negatives no regression); per-case flip self-check proves exit code depends on every positive and negative; zero-embed zero-network, ledger 458/500 read-only unchanged with identical line digest (word-surface 160, 181 rows), prior evidence hashes untouched, real 26/60 and 13-request retest plan frozen; dual-target requirement checks 4/4 pass vs origin/main and origin/agent/agent/de8874a3803b with/without handoff 070f4fd89b070f4fd: parse_supported_answer now captures and validates role slots per clause instead of discarding subject/receiver after regex consumption; pre-declared scene target from p1 user quote (promisor=user '你/you', told-receiver=companion '我/me', object=interview result) with declared anaphora for omitted slots (promise clause omitted subject->promisor, omitted receiver->scene receiver; state clauses by verb class: tell-verb subject=promisor, receive-verb recipient=scene receiver with open-side receive subject compatible with both receiver-not-told and promisor-not-received readings, fulfill-verb subject=promisor); explicit different recipient (现在已经告诉你了/told them), promise to someone else (告诉她/her), reversed promisor (我答应/我承诺/I promised...), multi-clause role conflicts and unknown roles (we/我们/他) all fail conservatively; canonical positives incl. 我还没有收到 and omission-inheritance forms kept passing; no eight-sentence or pronoun blacklist, no new model, no generic NLU engine, supported surface unchanged (EN closed-receive subject slot still excludes promisor pronouns) c0cb540c9f070f4fdworktree (manager eight role-crossed wrong-answer groups - each replacing only one side with the other side the canonical positive - all pass=true) + audit865_postfix at code commitc0cb540(all eight judged fail through the same real s6_result; structural variants incl. other pronouns/other promise verb/EN her-us-we-I/mixed multi-promise clauses all fail, both-period negatives honestly kept; omission-inheritance positives incl. wo-hai-mei-you-shou-dao all kept) + audit861_reuse865 full rerun (share gates/real exits/S8/S9/unresolved-block self-consistency/anchor negatives no regression); per-case flip self-check proves exit code depends on every positive and negative; zero-embed zero-network, ledger 458/500 read-only unchanged with identical line digest (word-surface 160, 181 rows), prior evidence hashes untouched, real 26/60 and 13-request retest plan frozen; dual-target requirement checks 4/4 pass vs origin/main and origin/agent/agent/de8874a3803b with/without handoff 5ebe407d3f5ebe407: _bind_state_clause no longer treats the slot after receive/fulfill verbs as tell's receiver; tell-verb post-verb slot = told receiver (scene receiver 我/me, omitted inherits, object NP may follow); receive-verb (收到/拿到/received/got) post-verb slot = the received object (interview result, omitted inherits per declared anaphora; explicit person pronoun 收到我/received me = receiving a person not the result, received me the interview result = extra person parameter, all fail conservatively); fulfill-verb (兑现/解决) post-verb slot = the fulfilled matter (promise/appointment, omitted inherits; 兑现我 fails); subject-slot rules unchanged from HEL-865 (tell/fulfill subject=promisor or omitted, receive closed recipient=scene receiver or omitted, open receive subject compatible with both readings); manager six negatives (haven't received me yet / haven't got me yet / haven't received me the interview result yet / 还没有收到我 / 还没拿到我 / 还没兑现我) all fail through the same real s6_result; per-class subject x post-verb-slot matrix covers subjects/direct objects/receivers/multi-param conflicts for tell/receive/fulfill in both languages, not just six sentences; canonical positives incl. 我还没有收到, haven't received it yet three readings (omitted/promisor/recipient subject), 还没兑现 omission, topic form and tell-with-receiver+object kept passing; no six-sentence or pronoun blacklist, no new model, no generic NLU engine, supported surface unchanged cf3423d44c5ebe407worktree (manager six receive/fulfill person-object wrong-answer groups - resolved side fixed to canonical positive, only unresolved side replaced - all pass=true; per-class subject x post-verb-slot matrix person cells incl. recipient-subject 'I haven't received me yet' reading all reproduced) + audit866_postfix at code commitcf3423d(all six plus person-object matrix cells and structural variants judged fail through the same real s6_result; canonical positives incl. 我还没有收到, haven't received it yet three readings, 还没兑现 omission, topic form and tell-with-receiver+object all kept; 140 role combos and audit861-865 held S6/S2/S3 sets unchanged) + audit861_reuse866 full rerun (8 share-gate calls all supplied, t1 unshared/t4 unknown companion raw text never enters sent context, S8/S9 recovery exits, unresolved-block self-consistency, anchor negatives no regression); per-case flip self-check proves exit code depends on every positive and negative; zero-embed zero-network, ledger 458/500 read-only unchanged with identical line digest (word-surface 160, 181 rows), prior evidence hashes untouched, real 26/60 and 13-request retest plan frozen; dual-target requirement checks 4/4 pass vs origin/main and origin/agent/agent/de8874a3803b with/without handoff 5e90136f905e90136: s6_result's resolved_affirms_closed/unresolved_affirms_open/unresolved_no_false_resolution now share the same parse_supported_answer as affirms_promise_state (same-source polarity) instead of whole-text bare-substring exclusion with PROMISE_CLOSED/OPEN word lists (retained as historical declaration, unwired) - the bare substring ignored negation context and read 'received the result' inside 'haven't received the result yet' as a resolution claim, rejecting correct unresolved answers the declared grammar already supported (present since5ebe407, exposed by the manager's expanded 740-row independent check: 33 failures = 30 negation-aux x received x object combos + 3 overlapping receive-matrix rows); opposite polarity and no-false-resolution now judged by closed/open clause polarity binding the same scene declaration - a closed clause (incl. mixed open+closed) still fails, negated positive substrings no longer trigger; uncertain whole-text exclusion kept (uncertain forms are structurally unconsumable, belt-and-braces); audit867 prefix at5e90136worktree reproduces all mis-rejections through the same real s6_result (parse open+bound, affirms_promise_state true, gate false), postfix passes minimal family + 120-row grammar x predicate matrix + manager receive matrix; double-phase negatives (false resolution incl. I have received the notification, mixed polarity, maybe/foreign object/question/conditional, resolved side says open) stay failed; HEL-866 six + person-object matrix cells + canonical positives + haven't received it yet three readings + omission inheritance + 140 role combos + audit861-866 all held S6/S2/S3 sets unchanged; manager's original review866.py rerun 740/740 exit 0; audit861_reuse867 real orchestration + fake externals exit 0 (8 share gates supplied, unshared/unknown never in sent context, S8/S9 exits, unresolved block self-consistent, anchors); per-case flip self-check; zero-embed zero-network, ledger 458/500 read-only unchanged with identical line digest, prior evidence hashes untouched, real 26/60 and 13-request retest plan frozen; no new semantic engine, no sentence amnesty/banned words, no fixture or model-answer changes, supported surface unchanged 454e54cb595e90136worktree (manager minimal unresolved positive 'you haven't received the result yet' + I/omitted subject + the notification family + 30 negation-aux x received x object cells + 3 overlapping receive-matrix rows all mis-rejected through the same real s6_result while parse open+bound and affirms_promise_state true - mis-rejection in the overall predicate layer) + audit867_postfix at code commit454e54c(all previously mis-rejected correct unresolved forms pass; 120-row grammar x predicate matrix and manager receive matrix match expectations; double-phase negatives - false resolution clauses incl. I have received the notification, mixed polarity, maybe/foreign object/question/conditional, resolved side says open - all stay failed; resolved-side positives incl. EN recipient-subject received forms kept passing) + manager original review866.py rerun 740/740 exit 0 + audit861_reuse867 full rerun (8 share-gate calls all supplied, t1 unshared/t4 unknown companion raw text never enters sent context, S8/S9 recovery exits, unresolved-block self-consistency, anchor negatives no regression); per-case flip self-check proves exit code depends on every positive and negative; zero-embed zero-network, ledger 458/500 read-only unchanged with identical line digest 8037cbfb (word-surface 160, 181 rows), prior evidence hashes untouched, real 26/60 and 13-request retest plan frozen; dual-target requirement checks 4/4 pass vs origin/main and origin/agent/agent/de8874a3803b with/without handoff e06dcaf889e06dcaf(driver only captures per-call raw input/sent-context/answers and writes per-scenario outputs, never overwriting ab_scenarios.json); preflight zero-embed zero-network audit861_reuse868 + audit867_reuse868 both exit 0 with prior evidence and ledgers unchanged; 13/13 calls sent HTTP 200 (ADD1-5 anchored real extraction + QA1-8), real ledger continued on a SQLite-consistent backup of the original 26-row ledger (prefix line digest 03f92557 identical, original read-only preserved) now 39/60, embed ledger 458->498/500 (+40 dense, pre-computed debit guard held), usage 163041 tokens recorded per call; honest per-scenario results: S1/S4/S5/S8/S9 pass, S2/S3 mem0 side and S7 fail fail-closed because base-group batch-anchored infer hits carry the unshared t1 companion row in the group anchor and companion_unshared rejects them at every exit (zero leak markers in all sent contexts - the gate holds; row-level provenance for batch extractions is our adaptation gap, not visible to offline row-anchored fake payloads), S3 retrieval layer strictly better re-confirmed (11:11 target hits vs baseline 0:0) but model-use verdict fails without the gated content, S6 orchestration/status-in-block/unresolved-contrast all pass while both real answers are descriptive '资料里说...' unsupported by the pre-declared bounded grammar and honestly fail closed; no rerun, no criteria relaxation, no debug requests, no merge, no deploy; dual-target requirement checks 4/4 pass with handoff-HEL-868.json 81d50f28af81d50f2- recheck869.py reproduces the upstream rolling 10-message window from the fixed mem0 storage source (SHA256 5f5ecdad, byte-identical to the isolated venv install) in an independent in-memory SQLite with zero LLM zero embedding zero network (single 15-message batch truncates to 10; the real 9,1,1,2,2 add pattern keeps batch1 first-4 + later-6, dropping batch1 last-5) and verifies read-only that this round's mem0 messages hold 10/15 missing exactly t3 user/companion, t4 user/companion, t5 user with the restored public copy identical at 10, while the baseline main archive chat_message keeps all 15 verbatim per-role rows and the original calls inputs still carry all 15 - SDK messages is a rolling window, not a permanent quote archive, and no real user data was lost; erratum_HEL-869.json records six report-corrections without touching any original JSON (E1 S1 frozen criterion sampled only mem0 t1 so full-15 retention cannot be claimed, E2 this round used 46004 tokens = 44735+1269 while 163041 is the cumulative 39-call total, E3 raw QA6-13 map in order to plan QA1-8, E4 calls headline 'answered blue' is a stale run2 note vs this round's honest unknown answer, E5 in-process llm_calls_real=0/embed 39 are not authoritative vs persistent ledgers' 13 sent/40 dense, E6 S9 re-verified only the public instance with full private+public recovery reused from gate2 P5); README HEL-868 record annotated in place at the three corrected conclusions plus a HEL-869 section; plan-next-HEL-869.md delivers the decision-only minimal follow-up (main archive stays the permanent quote layer with reread via turn_ids anchors, mem0 interfaces reused, no upstream fork; batch-extraction line-level provenance proven by input-side pre-grouping where each add's anchor equals its actual input set with gate-side sha256 recompute - no gate bypass, no anchor trimming, no prompt-only promises; S6 verified via explicit-status questioning under the same frozen bounded grammar with no wording amnesty; Chinese custom_instructions deferred; upstream/ours responsibilities, risks incl. embed budget 498/500 remaining 2 as the hard blocker, and a staged minimal retest: stage0 offline zero-cost audit then stage1 ~14 requests/~40-46 embeddings pending quota decision); all three ledgers byte-identical before/after (03f92557/c9871277/9716c722), everye06dcafresult blob unchanged, no criteria/fixtures/orchestration edits, no real requests, no embeddings, no merge, no deploy; dual-target requirement checks 4/4 pass vs origin/main and origin/agent/agent/de8874a3803b with/without handoff-HEL-869.json 5671946267View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.