TGMS — Agent-Native Bi-Temporal Graph Store

0.41 vs 0.18 best baseline

Pooled exact match on temporal-analytics tasks (CollegeMsg dev, Qwen2.5-14B on one 24 GB GPU). Significant over vector-RAG and static-graph RAG at 95% CI.

0.67 vs 0.00 all baselines

Correction probes — “as of transaction time T, what did we believe?” No snapshot or RAG system can even express the question.

500/500 · 0 false positives

Injected false claims caught by the trace-grounded verifier. Emitted answers carry an unsupported-claim rate of 0.000.

Why two kinds of time?

Every fact carries valid time (when it held in the world) and transaction time (when the store believed it). That separates evolution — “the edge ended” — from correction — “we were wrong.” Agents can then answer belief-state questions deterministically, no LLM required for the time travel itself:

# same entity, same operators — only as_of_tt differs
entity_history(uid="n605", as_of_tt=BEFORE_CORRECTION)  # → 1 version
entity_history(uid="n605")                              # → 3 versions

And every answer is auditable. The trace viewer renders the plan DAG, per-operator cards (args, rows, latency, result digests), and each claim badged by the verifier:

$ tgms ask "How many nodes can n9 reach in May?" \
    --store stores/collegemsg --model openai/Qwen/... \
    --html trace.html
claims: c1 count=343 → verified ✓  (evidence: s1)

verified weakly supported unsupported — see a real rendered trace

Quick use cases

1 · Verified operators, no LLM needed

Time-respecting reachability, δ-motifs, snapshot diffs, bursts, Allen interval joins — deterministic, bounded, oracle-tested (500 randomized cases per operator).

$ uv run tgms call temporal_reachability '{"src": "n9",
    "window": {"t_a": 1082040961000000, "t_b": 1088000000000000}}' \
    --store stores/collegemsg
{"rows": [...], "rows_total": 343, "result_digest": "9c4f…"}

2 · Hand the toolbox to any MCP agent

The tool server is stateless and read-only: attach Claude Desktop/Code or any MCP client and it gets the whole verified algebra against a shared temporal store.

$ tgms serve --store stores/collegemsg
# any MCP client now sees 13 typed temporal tools,
# each with schemas, cost hints, and output contracts

3 · Investigations with an evidence trail

“Among accounts reachable from X in February, how many cyclic temporal triangles closed within a day?” — reachability feeds motif counting via plan refs; arithmetic runs in a compute operator, never in the LLM.

s1 resolve_entities → s2 temporal_reachability
   → s3 count_temporal_motifs(node_filter=$s2.rows[*].uid)
answer: 14 · claim c1 verified against s3’s digest

4 · Audit under revision

Knowledge bases get corrected. Reproduce exactly what the system believed when a decision was made — results pinned to a past belief state are byte-identical forever (a tested metamorphic property, not a promise).

$ uv run tgms eval c2 --store … --suite …   # verifier acceptance
detection 500/500 · false positives 0 · accepted: true

How it works

1 · PlanThe LLM emits a small JSON DAG of operator calls. A static verifier enforces grounding (no invented identifiers), output contracts (no invented result fields), temporal sanity, and cost — with structured repair payloads.

2 · ExecuteA deterministic executor runs the DAG over the bi-temporal store; results are content-addressed; truncation taints dependents. Re-execution reproduces identical digests.

3 · VerifyA reporter writes the answer; every count, entity, ordering, and pattern claim is machine-checked against the trace. Unsupported claims never ship.

pooled EM · Qwen2.5-14B	TGMS	vector-RAG	static-RAG	text-to-Cypher
all task families	0.41	0.09	0.05	0.18
correction probes	0.67	0.00	0.00	0.00

Dev split, single seed, open-source models served locally; every number carries determinism receipts — full report.

Get started

git clone https://github.com/zxf-work/tgms && cd tgms
uv sync --extra agent
make test                        # 81 tests: property, oracle, metamorphic
make data-collegemsg suite-collegemsg
bash scripts/run_webapp.sh       # interactive guided demo → localhost:8080

Works fully offline for operators, task suites, and the verifier; point --api-base at any OpenAI-compatible endpoint (e.g. vLLM) for the agent loop. Apache-2.0.