v1.2.0: the GraphStore release.
The materialized graph projection becomes a pluggable seam. Graph
state (objects, relations, patches) has always been a projection of
the event log; v1.2.0 makes where that projection materializes a
pluggable choice, parallel to the EventStore seam for the log
itself. InMemoryGraphStore remains the default and is byte-for-byte
the previous behavior. FalkorDBGraphStore backs the projection with
a FalkorDB graph — objects as :AGNode:AGObject nodes, relations as
native AGRelation edges — so the current-state view is a real,
traversable, Cypher-queryable graph. Query hooks push type filters,
relation lookups, neighborhood walks, and whole pattern chains into
the database, so query cost scales with result size rather than
graph size. Install with pip install 'activegraph[falkordb]'
(server client) or 'activegraph[falkordb-embedded]' (embedded
engine, Python 3.12+).
Contributed by @dudizimber (issues #38, #41, #43, #45; PRs #39,
#46). The architectural decisions are locked in CONTRACT.md § v1.2
#1–#5, including the provenance note recording that the lock was
written retroactively during release preparation.
The test suite is now a CI gate (CONTRACT v1.2 #6): pytest runs on
a Python 3.11 + 3.12 matrix with the FalkorDB and Postgres
conformance suites executing rather than skipping. Every non-slow
test runs on at least one matrix leg; previously no workflow ran
the suite at all.
Also in this release: agent-discovery files at the doc-site root
(/llms.md, /robots.txt), docstring Wave 1 complete (every Ring 0
public symbol is documented and the exemption list is empty), and
the next cycle scoped in ROADMAP.md.
No migration is required. Runs that don't pass graph_store= behave
identically, and the FalkorDB projection layout change from the
pre-release relations-as-nodes shape needs no tooling — the
projection is disposable and rematerializes from the event log.
See CHANGELOG.md for full notes.
