Event-sourced memory for agent work

Zaxy

Zaxy keeps multi-agent projects replayable: parent missions, isolated worker sessions, cited findings, purpose-conditioned checkout, conflict review, and accepted merge-back into one durable project history.

Install locally Coordinate docs Purpose roadmap

runtimeembedded Kuzu default

sourceEventloom append-only JSONL

checkoutcited, purpose-conditioned context

PyPI 1.1.1 embedded local runtime purpose-v1 passed CoordinationBench gate passed StateRecoveryBench gate passed Quarq/Hybi claims blocked external verification requested

Coordinate

Worker-local claims are not project truth.

Spawning agents is easy. The hard part is turning isolated investigations into one trustworthy state of work. Zaxy records each worker in its own Eventloom session, reviews findings with evidence, marks stale and conflicting claims, and promotes only accepted facts into the parent mission.

Parent mission

The coordinator owns accepted project history, decisions, handoff, and Memory Checkout state.

Worker sessions

Agents investigate in isolated logs, so exploration does not contaminate authoritative memory.

Approval packets

Human or coordinator-agent review accepts, rejects, defers, or promotes findings with cited provenance.

Architecture

Eventloom is truth. The graph is a rebuildable projection.

Missionobjective and parent state

Workersisolated Eventloom sessions

Findingsevidence, confidence, citations

Reviewconflicts, stale claims, approvals

Checkoutaccepted cited prompt state

Eventloom source of truth remains the append-only project record. The default local runtime is embedded Kuzu, launched and cleaned by zaxy init and zaxy doctor. Neo4j remains the sidecar control backend; pgGraph, LatticeDB, and Pathlight are advanced integration tracks for teams that need alternate deployment or observability posture.

Purpose control plane

The same evidence can mean different memory for different work.

Zaxy now carries purpose through retrieval, checkout diagnostics, feedback, compaction, and Coordinate accepted state. This is still framed as project-local agent work memory, not a broad Company Brain claim.

memory_checkout(..., purpose="coding")

Applies deterministic purpose emphasis, recall floors, scoring profile selection, and checkout guidance.

zaxy memory purpose status

Replays active profile, checkout quality, accepted Coordinate state, and feedback posture without graph mutation.

zaxy memory purpose lanes

Shows purpose-specific checkout lanes, cited source groups, and suppression candidates.

zaxy memory purpose feedback

Surfaces positive and negative outcome history so future retrieval can prioritize useful purpose-specific memory.

Interfaces

CLI, MCP, dashboard, and adapters share the same contracts.

coordination_checkout accepted parent state plus diagnostic worker-local findings coordination_approval_packet reviewable accept/reject/defer/promote payloads memory_checkout answerability, current_citation_count, required action, and memory_feedback guidance CoordinationAdapter dependency-light Python wrapper with LangGraph and CrewAI helper paths dashboard --enable-coordinate-review opt-in human review controls over replay-backed state; read-only remains the default

Benchmark evidence

Public claims stay inside the evidence boundary.

Current artifacts separate internal release gates from comparative claims. Purpose-v1 passes its deterministic contract lanes. CoordinationBench v1 passes accepted-finding precision and recall, conflict handling, stale rejection, proof-backed synthesis, and parent answerability. Semantic Reach/Hybi and Quarq rows remain disclosure only until pinned same-harness adapters produce locally scored, fingerprinted results.

Purpose Benchmark

10/10 lanes passed

Purpose recall, ontology shift, outcome feedback, evidence discipline, and neutral-substrate projection are covered by purpose-v1.

CoordinationBench

1.000 gate metrics

Accepted-state synthesis, non-authoritative leakage, citation coverage, parent answerability, and Eventloom replayability pass.

Competitors

blocked claims

Quarq and Semantic Reach/Hybi are pinned as unsupported disclosure rows until same-harness audits complete.

Current Evidence Boundary

These rows are release evidence and disclosure status, not a universal memory leaderboard.

Artifact	Status	What it supports	What it does not support
purpose-v1	passed	Purpose-conditioned retrieval, checkout, feedback, and compaction contract.	external Semantic Reach or Quarq superiority claims.
public-derived purpose holdout	diagnostic	Representative pressure cases with citation coverage and frozen fingerprint.	Release gate or outside-user validation.
CoordinationBench real-v1	passed	Accepted parent state, conflict handling, stale rejection, proof-backed synthesis.	Generic RAG, open-domain QA, or all memory workflows.
Quarq / Semantic Reach Hybi	blocked	Adapter metadata and public disclosure that same-harness work is still required.	Completed competitor scoring.
BM25 worker logs	0.666667 precision	Same-harness local baseline over rendered worker findings.	Accepted project state, conflict recall, stale rejection, or citation coverage.
Markdown notes	0.636364 precision	Same-harness local baseline without promotion or conflict semantics.	Authoritative parent checkout or proof-backed merge-back.
Flat transcript	0.272727 precision	Contamination baseline that treats all worker output as accepted state.	Reliable accepted-state precision, stale rejection, or conflict review.
Mem0 / Agent Memory / ActiveGraph	not_run	disclosure only rows until pinned same-harness runner manifests exist.	Any comparative score.

CoordinationBench reportGate status and baselines Purpose roadmapPurpose-v1 and holdout boundary Benchmark reviewContribution and claim discipline External verificationPublic request and report contract

Install

Initialize a local embedded runtime, then expose memory through MCP.

pipx install zaxy-memory
zaxy init
zaxy memory log --eventloom-path .eventloom --limit 5
zaxy memory bootstrap --eventloom-path .eventloom
zaxy doctor --eventloom-path .eventloom

zaxy coordinate start "ship auth refactor" --mission auth-main
zaxy coordinate worker create --mission auth-main --worker auth-api
zaxy coordinate assign --mission auth-main --worker auth-api "trace failures"
zaxy coordinate brief --mission auth-main
zaxy coordinate checkout --mission auth-main

What happens when you run init

Zaxy writes `.env.local`, records session genesis and heartbeat, checks graph posture, and prints the MCP command or config path.

What stays local

Session history lives in .eventloom/ as append-only JSONL. The graph is a rebuildable projection.

How to prove capture

memory log, memory bootstrap, doctor, and hook-status expose Last checkout, capture, and stale-memory posture.

Documentation

Start with Coordinate and purpose. Keep the rest as operator reference.

Coordinate roadmap Purpose analysis and roadmap Benchmarks External verification request Getting started MCP quickstart Coordinate quickstart First-run validation Zaxy Collaborate demo media Architecture MCP interface Framework integrations Why Zaxy

Operator and internals reference

Zaxy 1.0.0 release Zaxy 1.0.0 X article Zaxy 1.1.0 X article Zaxy Coordinate announcement Zaxy 0.4.0 archive v1 roadmap Configuration MCP install targets Eventloom contract Agent events Hook protocol Codebase mapping Graph schema Retrieval Embeddings Security Operations Deployment Testing Benchmark contributions Benchmark review Consolidation Python API API inventory Stability commitment Migration guide v0.9 gate audit v1.0 gate audit Release validation checklist Competitive positioning Runtime roadmap Packet analyzer Workspace genesis