Skip to content

GraphForge Roadmap

Last Updated: 2026-08-07 Current release line: v0.5.2 (see installation)


This roadmap describes product surfaces and versions, not internal delivery milestones. Where a GitHub milestone name appears elsewhere in operator docs (for example release-certification for the coordinated v0.5.x publication), it is paired with plain-language purpose there; this page stays version- and outcome-oriented.


GraphForge v0.5.2 is the current coordinated release across Rust crates, PyPI, npm bindings/CLI/skills, and public docs. Install from the published packages (see installation).

Capability surface matches the shipped v0.5 engine: openCypher, seven analyst-intent verbs, Parquet projects, and thin Python/Node bindings.

Mobile bindings (Swift/Kotlin/UniFFI) are not part of the current core package set.

See Publishing for artifact destinations and release process for operator sequence.

v0.5.1 was the first complete coordinated registry publication after the incomplete v0.5.0 surface. Prefer v0.5.2 for new installs.


GraphForge v0.5.0 is an embedded openCypher engine with a Rust core, Apache Arrow results, and Parquet-backed projects. The public surface is Cypher plus seven analyst-intent verbs:

forge.execute(cypher) # openCypher → Arrow Table
forge.rank(label, by=...) # centrality, structural scoring → Arrow Table + score
forge.cluster(label, by=...) # community detection, components → Arrow Table + community_id
forge.paths(source, target, by=) # shortest paths, flow, reachability → Arrow Table
forge.analyze(label, by=) # spanning trees, DAG, coloring, matching, embeddings → Arrow Table
forge.similar(label, by=) # pairwise node similarity → Arrow Table
forge.find(query,) # text/vector/hybrid search → Arrow Table + score + matched_on

Full algorithm catalog: Algorithm Verbs

Architecture reference: Architecture Overview, Refactor notes

Architecture decisions: ADR 0001, ADR 0002

Status vocabulary (same as architecture docs): Shipped = implemented and tested on main; Partially built = some paths real, others stubbed; Designed = specified, not yet a complete public capability; Deferred = intentionally after the current release line.

Shipped capabilities (present tense — this is the product):

Capability Status What it is
Compiler + ontology + Graph IR + relational lowering Shipped openCypher path into DataFusion
Execution + adjacency index Shipped Parquet-backed execution; derived CSR adjacency under indexes/adjacency/ (ADR 0004)
Python + Node bindings Shipped Thin bindings over graphforge-api; Arrow / IPC results
Conformance hardening Shipped openCypher TCK, fuzzing, and semantic gates
Analyst verbs Shipped rank / cluster / similar / paths / analyze → Arrow
Find / index Shipped find + index — text, vector, hybrid
Knowledge layer Shipped Immutable assertions, confidence, evidence, provenance, neutral algorithm runs
Epistemic model Shipped Append-only status, reasoning, supersession, hypotheses, optional valid time, resolved algorithm dispatch

Layer boundary notes: refactor-v0.5 §8.

Merge gates (required before merging to main)

Section titled “Merge gates (required before merging to main)”
  • Parser parity — RD+Pratt corpus + syntax goldens pass
  • openCypher TCK subset — agreed compliance threshold met
  • Ontology round-trips — load/validate/migrate stable
  • Arrow/IPC round-trips — data contract stable across shipped Rust, Python, and Node surfaces
  • Parquet provider — core semantics verified
  • Python + Node bindings — packaging and smoke tests pass
  • Observability — explain, query IDs, provenance IDs, structured errors
  • All seven analyst verbs — Arrow Tables, write-back, via/directed filters
  • forge.find() / forge.index() — lazy indexing, text + vector + hybrid

Language Mechanism Result Status
Python PyO3 + maturin pyarrow.Table Shipped (v0.5)
Node / TypeScript napi-rs Arrow IPC Buffer Shipped (v0.5)
Rust Native crate ExecutionResult Shipped (semantic owner)
Swift UniFFI Arrow IPC DataGraphForgeResult Planned (after v0.5.1 core publication)
Kotlin / JVM UniFFI Arrow IPC ByteArrayGraphForgeResult Planned (after v0.5.1 core publication)

GraphForge follows Semantic Versioning and is pre-v1.0. The 0.x series signals that the API is still maturing.

  • Patch (0.5.y): Bug fixes, small improvements, no intentional API breaks
  • Minor (0.x.0): New features; backwards-compatible where practical

v0.5.1 is the current coordinated release. A v1.0 release will happen when the API is stable enough to commit to long-term compatibility.