zonggong and multica-agent
78b6267d3a
HEL-885 rework: per-row progress matches what was really sent, cross-day and unknown-outcome accounting stay conservative, positive caps require the ledger authority, and the release dependency-fill command actually exists - every Memory.add now carries an anchor for exactly its own row (the HEL-882 whole-batch anchor let the first stored vector mark unsent rows complete; the manager's real-SDK partial reproduction showed the user's original words never leaving the process), a row finishing with a legitimately EMPTY extraction gets a durable sem_row_done record (r4.sql additive table) written inside the worker thread the moment its add completes, resume skips = vector-store anchors ∪ sem_row_done so no row is lost, none falsely complete, and finished work is never re-sent across budget-refusal/crash/restart/lease/concurrency, entry_ids merge across partial attempts, and the swallowed-failure detection is per-row; PersistentBudget.settle/release book on hold.day (the old write to state.day manufactured -80 used on the new day and re-opened headroom the reservation day had already spent; token_usage/request_usage refund the paying day, budget_total stays global) and the empty-budget_total TypeError crash in total_requests_used/total_tokens_used is fixed - the old one-shot-total test passed only because that crash surfaced as chat.error, it now books the total honestly; _atomic_reserve no longer purges aged reserve: rows (a crashed worker's hold is an UNKNOWN outcome - an hour-old timeout is not proof the call never happened; unknown consumption stays billed across restarts, only a provably-unsent release() ever removes a hold, embed_ops and llm_ops share the fix); Mem0Backend refuses construction before importing mem0 when any cap>0 lacks a (non-empty dict) authority block - ledger_authority_required - or when the prefix check fails, closing the fresh-empty-ledger bypass the manager reproduced live, config/semantic.example.yaml ships the authority block as REQUIRED with the explicit cumulative formula (embed_cap=500+approved-increment e.g. 680, embed_reserve=2 frozen untouched, min_used=498; never write 180 as the cumulative cap of a 498-used account) mirrored into docs/budget-plan-hel874.md §2 with the HEL-885 accounting rules; deploy/hel874-release.md §4 replaces the nonexistent uv pip download (rc=2, re-verified) with python3 -m pip download --only-binary :all: --platform manylinux2014_x86_64 --python-version 3.11 --implementation cp --abi cp311 + sha256 manifest + uv pip install --no-index --find-links offline merge + same-process co-import verdict, honest missing-materials list unchanged (no 3.11 wheels cached, zero downloads this card, no version swaps), and tools/check_release_offline_hel882.py gains R7 probing both command surfaces offline; verification: 281 python tests pass on 3.11.16 venv + requirements.lock offline (9 new tests/test_rework_hel885.py cases: partial batch claims only the sent row / empty-extraction row completes and is never resent / process restart sends only the missing row / concurrent ticks never double-send / cross-day settle and release book on the reservation day / aged unknown llm+embed reservations never refunded / missing-empty-malformed-wrong authority all fail closed; test_resume_never_loses_or_duplicates_rows rewritten to drive the REAL product path instead of hand-planting single-row anchors the product never wrote), ruff clean (src/tests/tools), web tsc + 42 vitest + build via npm ci --offline, pinned mem0 2.2.1 install on the deterministic boundary: contract re-run 12/12 (harness now hands a synthetic authority prefix - production defaults not relaxed), new tools/verify_semantic_recovery_hel885.py 7/7 (S0 authority fail-closed, S1 per-row partial with exactly 1 HTTP, S2 restart sends only the missing row proven by HTTP count since mem0 prompts legitimately carry old rows in rolling history, S3 lease recovery + concurrent ticks single-send, S4a/S4b unknown reservations kept), both manager review scripts re-run VERBATIM against this head (partial: completed=[2] only, resume done with 2 entries, HTTP=2, user words actually sent; extra: new-day used=0, over-cap request refused, aged reservation second_allowed=false, uv probe still rc=2), release offline check R1-R7 green, dual-target requirement checks 4/4 with handoff-HEL-885.json; zero real LLM, zero real embeddings, zero non-loopback outbound, authoritative ledgers and freezes untouched, not deployed, PR not merged, no visual changes
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-27 00:01:44 +08:00
zonggong and multica-agent
59fb06304f
HEL-882 evidence: manager review scripts re-run verbatim against e291058 (api repro blocked - 0 provider calls, used unchanged, honest chat.error; sdk repro 1 - exactly 1 loopback HTTP, llm_ops=1, max_retries=0; sdk repro 2 - mid-add swallow now requeues without burning attempts and resumes done with real entry ids after the cap is raised; sdk repro 3 - stub coverage no longer blocks the real rebuild, enqueue 1→tick→done→search hit→no resend proven live by the add-on), deterministic-boundary pinned-install contract re-run 12/12 with final ledger rows persisted before temp cleanup, and the release offline check green across checkout/import/health/fail-closed caps/approved-caps run/data preservation plus the honest mem0 3.11 co-import gap; zero real LLM, zero real embeddings, zero non-loopback outbound, authoritative ledgers untouched
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-26 23:30:36 +08:00
zonggong and multica-agent
e291058754
HEL-882 rework: execution-table caps become real hard gates at the wire, SDK hidden retries and mid-add failures recover without loss, the 8360 release package runs offline, and the HEL-874 embedding evidence is corrected - every real provider exit (create/dialogue/life/gist/judgment/growth/proactive phrasing + mem0's internal extraction LLM) now persistently pre-allocates request count (per-category daily + one-shot totals in request_usage/budget_total, BEGIN IMMEDIATE) and a conservative token estimate before sending, refuses at the tightest cap (BudgetStop, no more downgrade-and-keep-calling) and survives restarts; known usage settles to actual, unknown/disconnect/failure keeps the full reservation; ledger guards gain per-day tops (embed_daily/llm_daily) and verify_ledger_authority rejects a fresh file bypassing the frozen 498/500 prefix; the mem0 SDK client's hidden OpenAI retries are disabled (max_retries=0) so every actual send is gated and answered failures (even 5xx) settle as used with only httpx.ConnectError-grade unsent requests released; embed refusals the SDK swallows into empty adds are re-raised as budget errors so the batch re-queues without burning an attempt and resumes when the cap returns, add_group resumes at vector-store level (src_group anchors: only missing rows resent, crash/restart/concurrency never duplicate), sem coverage is per-backend (stub batches no longer block a real rebuild, real done batches never resend) with backend-scoped batch keys; the release package is offline-executable: fresh-dir git clone, cybergril service account, PYTHONPATH in the unit so the lock-only venv imports the product, shipped caps explicitly 0 (=refuse by design until approved), deploy/mem0-stack.lock + accurate 3.11 wheel gap with a no-download path (hel857-venv is 3.10; never present stub/FTS as the real memory experience), and tools/check_release_offline_hel882.py verifies checkout/import/health/fail-closed/approved-run/data-preservation on loopback with echo stand-ins; evidence corrected per manager review: docs/rework/hel874/erratum-hel882.json + README appendix record that e978e87's verification did real local embeddings from cache (provable lower bound 12, exact total unrecoverable, temp sandbox gone) while zero-real-LLM/zero-download/zero-outbound stand, old JSONs and authoritative ledgers untouched, and tools/verify_mem0_real_hel874.py now installs the deterministic 512-dim stand-in before TextEmbedding construction plus non-loopback socket rejection (zero model loads) with final_embed_rows persisted before temp cleanup; verification: 272 python tests pass on 3.11.16 venv + requirements.lock offline (16 new: manager api repro blocked with 0 provider calls, sdk repro 1-HTTP/max_retries=0/llm_ops=1, mid-add swallow requeued-then-resumed, resume-no-duplicate, stub-to-mem0 rebuild, daily embed cap, unified mem0-LLM gate, authority refusal, restart-persistent counters, tightest-constraint settle/release), ruff clean (src/tests/tools), web tsc + 42 vitest + build via npm ci --offline, pinned-install deterministic re-run 12/12, manager review scripts re-run evidence attached in delivery, dual-target requirement checks 4/4 with handoff-HEL-882.json; zero real calls, zero real embeddings, zero non-loopback outbound, authoritative ledgers and freezes untouched, not deployed, PR not merged, no visual changes
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-26 23:20:18 +08:00
zonggong and multica-agent
e978e878df
HEL-874 rework: bounded verbatim readback reaches the real provider input, real pinned Mem0 2.2.1 SDK contract verified live and the adapter's five wiring defects fixed, budget gates made provable (atomic reserve/settle embed ledger + independent llm_ops cap), definite-cap real-check execution table, 8360 isolated release package prepared (not deployed), 2026-10-26 user originals recorded source-only - semantic.context now quotes chain-verified archive rows (original words + role + when, <=200-char window with visible trim marker, summary demoted to a one-line pointer, same min(600,budget) cap) and episodic.context flips from gist-first-120-chars to verbatim-first (<=240) + role + date, both proven by tests/test_readback_hel874.py capturing the actual messages handed to the provider through the real API path: a detail absent from the gist yet quoted verbatim from a turn pushed outside the recent-20 window, the same for a semantic chain hit, and an unshared companion row never leaking through FTS, semantic or any anchor (AM-001); tools/verify_mem0_real_hel874.py runs the FIXED install itself (mem0ai 2.2.1 2c81af3, real embedded qdrant, real fastembed from the existing cache, deterministic 127.0.0.1 fake gateway, temp ledgers only): before=31970c4 dies at construction (second QdrantClient on the same path rejected by the SDK - recorded), and source-level findings confirmed live and fixed - unscoped search raises ValueError in 2.2.1 (add now carries user_id scope, search passes filters+top_k since limit is silently ignored), payload reads ride the SDK's own vector_store.client, the old outer search debit double-counted (wrapper is now the single accounting point), the SDK's internal extraction LLM was ungated (LlmLedgerGuard with its own llm_ops table, cap default 0) and check-then-debit could overshoot under concurrency (EmbedLedgerGuard now reserves atomically in BEGIN IMMEDIATE, releases on failure/cancel, purges stale holds); after fixes all 12 checks pass (construction/anchor payload/user scope/1 LLM + 2-3 embeds per add measured/extraction input set provably only prior gated batches incl. old memories and rolling history/unshared canary zero outbound/search single debit/concurrency never over cap/close-reopen intact/both zero caps refuse with ZERO outbound LLM requests), evidence in docs/rework/hel874/; mood sensitivity returns to the original repo's continuous rule 1.35-0.70*strength (bazi.sensitivity_from_strength, foundation commit 1012d8b) replacing HEL-870's invented 1.25/0.8 step and is labeled an engineering heuristic, never user-approved bazi science (external agent formulas remain not adopted); docs/budget-plan-hel874.md gives definite caps for the one-time team check (55 requests/0 embeds), first-week semantic activation (<=60 extract LLM / <=180 embeds) and user daily use with code-level hard-gate facts and authorization sources (old 20-30/100-200 were estimates, not approved quota; frozen 39/60 and 498/500 untouched and never挪用); deploy/hel874-release.md + cybergril-hel874-8360.service.example prepare the isolated fresh-empty-data-dir release with health capability matrix and data-preserving rollback (NOT executed, PR#11 not merged, no user-facing loop, no experience address); sources/comment-evidence-full-experience-20261026.json adds the two 2026-10-26 user originals (01a17806, 01a1780e full-experience-then-iterate) with authorship verified and manifest appended only - baseline/current/coverage/changes untouched; verification: 256 python tests pass on 3.11.16 venv + requirements.lock offline (3 new real-provider-input readback cases incl. AM-001 negative, mem0 fake rebuilt to mirror the real 2.2.1 surfaces, 9 cases), ruff clean, web tsc + 42 vitest + build pass, local 8360 stub smoke (loopback, isolated temp DB) health R4-assembly all green then stopped, real-SDK script re-run 12/12 after final edits, dual-target requirement checks 4/4 pass with handoff-HEL-874.json; zero real model calls, zero real embeddings, zero outbound (fake gateway on loopback + existing local model cache only), authoritative ledgers and freezes untouched, no existing services or profiles touched
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-26 22:13:45 +08:00
zonggong and multica-agent
31970c4dd3
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/semantic.py productizes the audited Mem0 path per plan-next-HEL-869: input-side pre-grouping sends only public rows outbound (user rows always; companion rows only judged+acked with all-told candidates), every batch anchor turn_ids/turn_roles/input_sha256 equals that exact input set, and the read-time gate independently recomputes the fingerprint against the live archive and re-checks every companion row's share state, fail-closed rejecting no_payload/unknown_source/archive_missing/source_mismatch/hit_text_mismatch/anchor_turn_mismatch/role_text_conflict/companion_unshared with honest row_verbatim/row_anchor/batch provenance; main archive chat_message remains the ONLY permanent quote layer; sem_batch/sem_covered carry a lease-recovered idempotent job loop; EmbedLedgerGuard continues the single authoritative embed ledger and with embed_cap=0 (no approved budget) refuses every real embedding so the frozen 498/500 and 39/60 accounts and the HEL-835 gate stay untouched; fixed Mem0 2c81af3 is lazily imported with zero upstream fork, a deterministic stub backend exists for engineering verification and is never claimed semantic; MoodRuntime makes core.mood live (event impulses scaled by bazi strength sensitivity, heartbeat decay, state_snapshot persistence, restart recovery, model sees one word only); DyadRuntime makes the relationship ledger live (completed exchanges are rituals, daily regression, behavior hints stay instructions); life_activity adds start/continue/interrupt/resume/finish continuity across slots and restarts with chat-completion interrupts; reach_out implements the approved R4 scope from character.yaml (>=6h interval, hours 8-23, salience>=0.6, arousal>=0.5, intimacy>=0.4) with traceable already-public bases only, UNIQUE(basis) so restarts and duplicate tasks can never multiply messages, night suppression, absence-rule fail-closed, phi projection, and messages persisted as companion rows (proactive=1) fully synced on reopen; API health reports R4-assembly with per-capability honesty (voice/vision/weather/materials/backup stay false, semantic_memory names its backend); config/semantic.example.yaml sanitized config and docs/runbook-hel870.md (startup, locked deps, health, independent data dir, disable/rollback, experience chain list, budget request, R1-R7 seams); verification: 250 python tests pass on 3.11 venv + requirements.lock (61 new deterministic/fake-provider cases covering every gate negative, restart recovery, dedupe, red line and the full entry chain incl. reopen epoch sync), ruff clean, web typecheck + 42 vitest + build pass with the original author frontend untouched except the one-line proactive passthrough; dual-target requirement checks 4/4 pass vs origin/main and origin/agent/agent/de8874a3803b with handoff-HEL-870.json; zero real model calls, zero embeddings, zero outbound network this card; local unified-instance smoke on port 8360 (stub semantic) serves the built web and reports the life loop waiting; read-only server check recorded in the runbook (existing 8300-8350 services and voice ports observed, end-to-end voice availability NOT verified); not merged, not deployed, no production or shared services touched
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-26 21:03:42 +08:00
zonggong and multica-agent
5671946267
HEL-869: read-only remediation evidence per manager independent review of 81d50f2 - 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), every e06dcaf result 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
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-26 04:09:58 +08:00
zonggong and multica-agent
81d50f28af
HEL-868: fixed 13-call real A/B retest executed in one bounded round per rework860 _retest_plan under the original '同意测试' authorization after manager HEL-867 review lifted the stop gate - criteria/fixtures/orchestration untouched at e06dcaf (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
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-26 03:49:33 +08:00
zonggong and multica-agent
e06dcaf889
HEL-867 handoff: deliverable/acceptance/deferred/verification JSON; audit867_prefix reproduced at 5e90136 worktree (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 commit 454e54c (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
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-26 03:35:21 +08:00
zonggong and multica-agent
5e90136f90
HEL-866 handoff: deliverable/acceptance/deferred/verification JSON; audit866_prefix reproduced at 5ebe407 worktree (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 commit cf3423d (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
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-26 03:15:06 +08:00
zonggong and multica-agent
5ebe407d3f
HEL-865 handoff: deliverable/acceptance/deferred/verification JSON; audit865_prefix reproduced at 070f4fd worktree (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 commit c0cb540 (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
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-26 02:56:16 +08:00
zonggong and multica-agent
070f4fd89b
HEL-864 handoff: deliverable/acceptance/deferred/verification JSON; audit864_prefix reproduced at 7aa9280 worktree (manager seven wrong-answer groups plus seven unresolved-side mirrors all pass=true) + audit864_postfix at code commit c65de00 (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
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-26 02:30:54 +08:00
zonggong and multica-agent
7aa928025b
HEL-863 handoff: deliverable/acceptance/deferred/verification JSON; audit863_prefix reproduced at 6859696 worktree (manager three new wrong-answer groups all pass=true) + audit863_postfix at code commit fcda71e (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
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-26 02:08:47 +08:00
zonggong and multica-agent
6859696075
HEL-862 handoff: deliverable/acceptance/deferred/verification JSON; audit862_prefix reproduced at a5ef23f worktree (manager four wrong-answer groups all pass=true) + audit862_postfix at code commit 60cd7fd (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)
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-26 01:40:57 +08:00
zonggong and multica-agent
a5ef23f5b5
HEL-861 handoff: deliverable/acceptance/deferred/verification JSON; audit861_prefix reproduced at 22472e4 worktree + audit861_postfix regenerated at final code commit efaa3c2 (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)
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-26 01:21:39 +08:00
zonggong and multica-agent
22472e4b92
HEL-860 handoff: deliverable/acceptance/deferred/verification JSON; audit860_postfix regenerated at final commit 6595153 (zero-embed); dual-target requirement checks pass vs origin/main and origin/agent/agent/de8874a3803b with handoff (4/4)
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-26 00:50:04 +08:00
zonggong and multica-agent
9f3e6a33c7
HEL-859 evidence: pre/post negative audit (prefix reproduces all manager-audit bypasses on 892d0d2, 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
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-26 00:19:27 +08:00
zonggong and multica-agent
892d0d2e30
HEL-858: rework per manager independent review - fixture (turn,role) integrity gate, spoken-text share bridge with partial/missing negatives + full restored P1-P5/F1-F8, known-id S4/S6 orchestration with readback and post-update re-retrieval, S7 anchor chain (input fingerprint) with wrong/unknown-source rejection, card-level persistent embed ledger (history rebuilt <=100), _flat/exit-code fixes; zero real model calls, run1/run2 evidence and 26/60 ledger untouched
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-25 23:53:10 +08:00
zonggong and multica-agent
e31ae2d946
HEL-857: approved Mem0 isolation spike - zero-model gates all pass, A/B synthetic scenarios within 26/60 real-call budget
...
- Fixed mem0 source commit 2c81af3 (2.2.1) in isolated venv, qdrant embedded + fastembed local zh embeddings (95.3MB, within 500MB cap)
- Gate0 transport-level persistent debit ledger: 61st call blocked pre-send, failures count, cross-process persistence, retries disabled+counted (fake transport, zero network)
- Gate1 qdrant embedded checks: keyword_search functional (Chinese segmentation gap recorded honestly), restart subprocess, clean-copy restore, no telemetry collections
- Gate2 privacy with stub LLM: P1-P5 zero leak, first-share timing F1-F6 (failed/cancel/unconfirmed no migration, ack+judged migrates told content with anchors, duplicate receipt idempotent), full backup incl. unshared internal memories restores clean
- A/B same-material same-criteria: Mem0 paraphrase recall strictly better than current lexical path (S3, model answers in Chinese), S1-S9 all pass, no regression
- Headline findings: Chinese input extracted as English memories (default upstream prompt), BM25 lexical channel inert for Chinese, ADD-only infer confirmed with our update orchestration, custom metadata needs direct payload read
- 26/60 real outbound via persistent ledger (incl. one parse-failure retry), usage/latency per row; embeddings 28/500; HEL-835 quota untouched
- Experiment branch only: no merge to main/product, no deploy, no real-profile access; handoff JSON + dual-base requirement checks pass
Co-authored-by: multica-agent <github@multica.ai >
2026-10-25 23:19:26 +08:00
zonggong and multica-agent
bb9cbe915e
HEL-847 v4: Mem0 capability corrections per manager review - additive-only infer, backend filter/BM25 facts, pre-isolation privacy design, concrete spike spec
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-25 22:23:53 +08:00
zonggong and multica-agent
800d3b75b6
HEL-847 v3: GOV-006 reweighing - Mem0 embedded SDK as primary candidate, 8-mechanism adaptation matrix
...
- Bounded source review of mem0ai/mem0 @2c81af3 (embedded lib, Apache-2.0,
upstream-maintained extract/consolidate/hybrid-search; SQLite history)
- Zep CE screened out (4-container stack, legacy/docker-compose.ce.yaml:5-71)
- 8-mechanism matrix from discussion takeaways: requirement/current/candidate/
thin-adapter/to-verify per mechanism
- Recommendation shifts from v2 Option C (self-maintained port) to Route E
(direct SDK adoption + thin product adapters); Option C kept as verified
fallback; spike-first with acceptance gates, no claim of final selection
- v2 report carried in verbatim as evidence base
Co-authored-by: multica-agent <github@multica.ai >
2026-10-25 22:06:31 +08:00
zonggong and multica-agent
575f2acfc5
HEL-847: apply v1.11 governance patch (GOV-006 mature-reuse principle, 60 items)
...
Audited manager handoff against af28ffd (v1.10):
- 59 original items byte-identical, open_items unchanged
- source hashes verified incl. other-agent-discussion sha256
- user quote 01a1734c verified against platform comment
- check_requirements passes vs main / hel-835-unified-review / product target
Co-authored-by: multica-agent <github@multica.ai >
2026-10-25 21:56:31 +08:00
zonggong and multica-agent
af28ffdcb5
HEL-835: evidence corrections per third review - 23 calls, day2 conclusion downgraded, old probe downgraded, null-fingerprint withdrawn, probe start deviation disclosed; 15/15 paired-window correction proof; real follow-up plan
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-25 09:17:34 +08:00
zonggong and multica-agent
c5167ca7c5
HEL-835: day2 handoff, dual-target requirement checks with handoff
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-25 09:06:59 +08:00
zonggong and multica-agent
65df25271e
HEL-835: guard v3 - done-delta streams settle ok on early close; 36/36
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-25 09:03:09 +08:00
zonggong and multica-agent
b98ab6ab50
HEL-835: deploy record updated for guard v2, restored service, prepared probe
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 14:53:01 +08:00
zonggong and multica-agent
96cdf07d73
HEL-835: probe seed backfills message_id provenance
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 14:52:15 +08:00
zonggong and multica-agent
468f0bbb6c
HEL-835: probe seed upsert memory_search flag
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 14:50:39 +08:00
zonggong and multica-agent
87afc34cd3
HEL-835: fix probe seed insert columns
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 14:50:26 +08:00
zonggong and multica-agent
e27274448d
HEL-835: fix probe seed companion identity_json shape
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 14:49:47 +08:00
zonggong and multica-agent
0b24fefc5d
HEL-835: synthetic retrieval probe seed script and runbook (approved plan, zero model calls)
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 14:49:06 +08:00
zonggong and multica-agent
9039311e29
HEL-835: guard v2 - unique call_id settlement, scene-bound categories, ledger validation, upstream close on cancel; 34/34 isolation proof
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 14:46:14 +08:00
zonggong and multica-agent
1fdca48153
HEL-835: guarded deploy record, audited call ledger, synthetic-retrieval plan (pending approval)
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 14:36:36 +08:00
zonggong and multica-agent
d7e5c00e80
HEL-835: deploy-layer durable call guard (caps 8 gist/6 turns/1 persona) + isolation proof 17/17 and assembly smoke
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 14:31:41 +08:00
zonggong and multica-agent
2ec9392aad
HEL-835: deploy record and rollback plan for isolated R3 instance on 8350
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 14:16:17 +08:00
zonggong and multica-agent
fc5e29469c
HEL-835: independent review evidence - rerun 225 pytest, web build/lint/42 vitest, 23/23 browser checks (chromium CDP), 30/30 e2e ControlledLLM isolated DB
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 13:58:13 +08:00
zonggong and multica-agent
2288471445
HEL-834: apply visual director memories page source package (6 modified + 9 new, verified against MANIFEST)
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 13:35:48 +08:00
白栖知 and multica-agent
89d53b6c53
HEL-833: restore runtime factory and verify R3 memory contracts
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 13:07:43 +08:00
白栖知 and multica-agent
78cab0456c
HEL-833: preserve R3 draft and regression stop evidence
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 12:55:58 +08:00
Chief Engineer and multica-agent
ee4459433c
HEL-832: R3 real-memory integration verification report, FTS probe evidence, handoff and follow-up construction cards (docs only)
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 12:46:53 +08:00
白栖知 and multica-agent
c285a0fd07
fix(r2): keep her self-narration and life within the approved room
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 12:03:08 +08:00
Chief Engineer and multica-agent
58d65aea05
HEL-828: wire life/persona/receipt confirmation onto 4575b275 (original author delivery, 12 files per MANIFEST in HEL-828-source-4575b275.zip)
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 11:08:53 +08:00
白栖知 and multica-agent
4575b27515
HEL-827: implement durable life, receipt-gated disclosure and persona layers
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 09:04:40 +08:00
Chief Engineer and multica-agent
2d97050c7e
HEL-825: review handoff (verified build/tests/browser checks/requirements; deploying 8320)
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 08:27:33 +08:00
Chief Engineer and multica-agent
e32a1ac0d2
HEL-825 review: link-card accessible-name selector fix (browser_check), evidence scripts, regenerated screenshots/recordings
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 08:27:06 +08:00
Chief Engineer and multica-agent
0bc4a9e68e
HEL-823 A3: days/memories, creation wizard, settings pages on cef8ae5 (author delivery, 15 modified + 1 handoff per CHANGES-HEL-823.json)
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 08:26:54 +08:00
白栖知 and multica-agent
cef8ae5581
HEL-824: land verified fixes on 4321aeb (small-screen first-press, real-time reading clock)
...
- 6 modified + handoff JSON per CHANGES-HEL-824.json, all hashes verified against git 4321aeb and package bytes
- rework_browser_check: skip full-text sheet at micro height (<420px design hides the control); migrate stale 返回日子 selector to 结束交谈 · 回到日子
- fresh run evidence: web build 25/25 unit tests, backend 142/142 (py3.12), all four browser checks PASS incl. new compact first-press and 700ms slow-frame sections (slow_frames_new_turn_to_reply_s=2.32s), layout regression 320/390/1024/1600 both themes
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 07:39:26 +08:00
白栖知 and multica-agent
4321aebfdc
HEL-822: fix handoff read_commit format
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 06:59:18 +08:00
白栖知 and multica-agent
e5fe01bfd1
HEL-822: review handoff JSON
...
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 06:59:07 +08:00
白栖知 and multica-agent
7db6677234
HEL-822: run all four browser checks; minimal mechanical check fixes + fresh run evidence
...
- browser_check.py: 视觉观察 → 视觉观察(模拟) (author renamed the aria-label, selector not migrated)
- import_check.py: handle the dirty-settings leave confirmation before opening the record (pre-existing gap, fails at base db571ba too)
- rework_browser_check.py: long-user-line reply budget 10s→60s (approved hel-799 dwell ≈2.4s/page), conditional 继续 resume (toLatest resumes flow in the approved prototype), 600ms settle before measuring compact typing nav transition
- regenerated docs/frontend + docs/rework evidence from this Linux run
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 06:58:20 +08:00
白栖知 and multica-agent
003d8c2cae
HEL-822: land HEL-821 A1+A2 source onto PR#4 base ( db571ba)
...
- 13 modified / 8 added / 1 deleted per CHANGES.json (author package 76bc120b)
- docs/requirements v1.10 + prototypes/hel-799 + PROVENANCE from bundle, verified byte-identical to 63799f0
- AGENTS.md + scripts/check_requirements.py restored from governance commit 63799f0
Co-authored-by: multica-agent <github@multica.ai >
2026-10-24 06:10:53 +08:00