v2.3.7

AtMem 2.3.7 — Preserve work. Resume with evidence.

AtMem 2.3.7 brings product-owned continuity to supported LangGraph applications:
save what happened, reuse completed results after a restart, and stop uncertain
actions instead of blindly repeating them. AtFlows 0.1.3 makes those attempts
inspectable and adds grouped event charts.

What you get

Resume work from durable state

Registered tools can use AtMem's governed operation identities, attempt leases
and encrypted receipts. After a restart, the application can reuse a saved result
or query a destination that explicitly supports reconciliation. When the result
cannot safely be established, AtMem asks for confirmation rather than guessing.
Permissions, operator pause and key lock remain authoritative.

Open Decisions → Resume work to inspect saved workflows and next actions.
This is an explicit integration, not an automatic upgrade to every agent tool.
Start with the continuity guide and its installed document
example. Supported hosting is synchronous, file-backed LangGraph with registered
tools and declared destination capabilities.

See the attempts in AtFlows

AtFlows Activity → Resume work joins workflow, operation, run and attempt
identities with reported retry/recovery costs. Missing prices remain unknown.
AtFlows observes execution; only AtMem authorizes governed work.

The Timeline also adds Group by charts for tool, service, model, event type
and hour. Click a bar to see its events. Counts describe the latest 100 matching
events, not an all-history or workflow-success total. Typography now follows
AtMem across both themes.

Easier local setup and Windows reliability

This stable release includes the 2.3.7 beta onboarding and concurrency changes:
managed, checksum-verified Bun setup when needed; serialized encrypted-store
access; and bounded retries for transient Windows atomic replacement failures.
Home and control-state creation no longer call POSIX-only fchmod on Windows.
AtFlows sets its SQLite busy timeout before initializing continuity tables.

Evidence you can inspect

Test situation	Observed result
Document published, receipt saved, worker killed	Restart left one document; saved result reused
Document published, worker killed before receipt saved	Restart left one document after destination reconciliation
Public retail exchange accepted, response lost	AtMem-connected arms made no repeat exchange request; stopped for confirmation
Same retail fault without AtMem	One repeat request; the store rejected it, so no second store change

The document tests used an installed product and an external crash rig: recovery
was performed by product code, not benchmark repair code. Native Windows checks
also exercised both receipt failure windows and the actual dashboards.

Read the full continuity report and raw evidence
and Windows verification.
The report separately preserves public-workload replay, fresh conversations,
grading and estimated costs. These are bounded acceptance/development results;
repeated held-out evaluation remains open. They do not establish a general
task-success advantage, universal exactly-once execution or a new leaderboard rank.
The Memory Integrity Benchmark report retains
its original tested-version provenance; it is not relabelled as a 2.3.7 rerun.

Install or upgrade

Back up your AtMem Home and AtFlows database with writers stopped first.
In the Python environment used by your services:

python -m pip install --upgrade "atmem==2.3.7"
atmem --version
atmem init
atmem status

The coordinated packages are AtMem 2.3.7, AtBot 0.1.0, AtFlows 0.1.3
and openclaw-memory-atmem@2.3.7. Pip installs packages; atmem init performs
setup/startup and reports actual dashboard URLs. Restart existing long-running
services after upgrading. For OpenClaw:

atmem openclaw upgrade
atmem control verify --probe

For standalone AtFlows, use python -m pip install --upgrade "atflows==0.1.3"
and follow its setup guide.

Opt-in, migration and compatibility

The OpenClaw declaration matrix includes 2026.9.6's default-v1 tool context;
its optional owner/session fields remain fail-closed when absent. This is a
declaration-contract check, not proof of runtime identity population. The bridge
suite also passes against the locked 2026.8.1 SDK. Verification recognizes
OpenClaw's materialized safe requireDirectSupport: true default without treating
it as configuration drift; explicit unsafe or unrelated changes still fail.

Continuity is off until a workflow is explicitly configured and enabled. It
requires full capture. First continuity creation advances that evidence vault
to schema 3; older schema-2 readers refuse it. Preserve a pre-opt-in backup:
there is no in-place downgrade. Ordinary evidence-only use remains schema 2.

LangGraph owns its checkpoint; protect that separate database independently.
The qualified LangGraph versions are 1.1.5 and 1.2.12. A lost receipt may require
waiting for the 120-second attempt lease before another worker can proceed.
Non-queryable, non-idempotent destinations may require human confirmation.
This is a bounded local sequential profile, not a distributed workflow engine.

AtFlows observation requires an explicitly configured producer token and SDK;
it does not capture every model/tool call automatically. Observer outages do not
grant or revoke execution authority. OpenClaw and AtBot retain their existing
memory/evidence integrations; arbitrary tools are not automatically made restart-safe.

Windows SSH-session lifetime testing required a scheduled-task launcher to keep
dashboards alive after disconnect. That test workaround is documented, not an
automatic service-install capability claimed by this release.