Google ADK 2.6.0 → Memanto → portable OKF

Your agent forgot the correction. Ours didn’t.

A real eight-session release copilot escapes Google ADK SQLite with every current fact intact, every superseded value auditable, and zero old truth leaking back into recall.

01Google ADKreal SQLite run
02Typed OKFowned markdown
03Memantosemantic recall
04OKF againleave whenever
8ADK sessions
17persisted events
13state updates
10/10memories mapped
9semantic types
100%recall parity
151-second execution + evidence cut

Watch the full freedom loop.

The first 56 seconds replay the timestamped output of a fresh, successful execution: official Google ADK SQLite, correction-safe OKF, live Moorcheh import and recall, then a second portable OKF export. The narrated evidence walkthrough follows.

Secret scan: 0 matches · capture SHA-256 9359e62853f0ece9745241e31370c14c5abf10e8cfd5066947cb17563b164961

Golden recall lab

Ask both sides. Get the same truth.

Each question is answered independently from the current ADK state and the mapped OKF preview. Select a question to inspect the result.

RECALL COMPARISON PARITY 1.00

Source · Google ADK

match 100%
Portable · OKF

match 100%
Same current truth. Zero amnesia.
The dangerous edge case

History preserved. Old truth quarantined.

Most migrations flatten an event log and accidentally reactivate obsolete values. This adapter separates current memory from the audit archive before Memanto sees it.

Human-readable by design

No proprietary blob. Just your memory.

The active value is ordinary Markdown with explicit provenance. Git can diff it, a human can review it, and another OKF-compatible tool can ingest it.

memories/decision/adk-app-decision-feature-flag-cache-ttl.md
READ-ONLY SOURCE

The adapter cannot mutate ADK.

SQLite opens in read-only mode and the expected schema is validated before capture.

FAIL-CLOSED ARTIFACTS

Every byte is accounted for.

SHA-256 inventory, replay checks, path containment, and duplicate-entry rejection.

HONEST MEASUREMENT

No synthetic savings claims.

ADK stores no billing baseline, so the report says exactly that instead of inventing one.

One command · under 15 minutes

Don’t trust the page. Reproduce it.

uv run --group dev --with-requirements examples/migrations/google-adk/requirements.txt python examples/migrations/google-adk/run_demo.py --force

Full evidence is complete: real ADK run, 8/8 source recall, 8/8 mapped recall, 10/10 live cloud imports with 0 failures, 8/8 cloud recall, and a 10-memory Memanto-to-OKF reexport.