Skip to main content

RiftPoint 🌌

CI Python 3.11+ Core: Tachyon-RS

High-performance multiversal checkpointer and speculative state engine for LangGraph, powered by Janus-Tachyon-RS.


🌟 Overview

In standard LLM agent workflows, exploring alternative reasoning paths, evaluating multiple tool-use strategies, or testing speculative futures requires expensive state copying or complex DAG orchestration.

RiftPoint bridges LangGraph with the Rust-backed janus-tachyon-rs engine to provide:

  • Multiversal Branching: Instant state forks into candidate realities with near-zero memory duplication penalty.
  • Speculative Tool Calling: Concurrent execution of divergent tool-use strategies across distinct timeline branches.
  • Multiverse Collapse: Automatic scoring of candidate timelines (via LLM-as-a-judge, heuristics, or consensus) to commit winning trajectories to main while pruning discarded paths.
  • Full State Travel & Tracing: Interactive time travel, undo/redo, and timeline visualization via Mermaid.js and Matplotlib.

📚 Planning & Architecture Documentation

Detailed architectural blueprints and implementation phases are documented in docs/planning:


🚀 Quickstart

Installation

pip install riftpoint

Or install with uv:

uv add riftpoint

Basic Example

from langgraph.graph import StateGraph
from riftpoint import RiftCheckpointSaver

# Initialize the Janus-backed checkpointer
checkpointer = RiftCheckpointSaver()

# Build your LangGraph workflow
builder = StateGraph(...)
# ... define nodes and edges ...
graph = builder.compile(checkpointer=checkpointer)

# Run workflow with multiversal checkpointing
config = {"configurable": {"thread_id": "session-1"}}
result = graph.invoke({"messages": [...]}, config=config)

# Render the timeline DAG as a Mermaid diagram
print(checkpointer.visualize("session-1"))

🛠️ Developer Commands

Development workflows use uv:

# Sync dependencies
uv sync --all-groups

# Run tests with coverage requirement (>= 70%)
uv run pytest

# Lint and format
uv run ruff check --fix
uv run ruff format

# Type check
uv run mypy src tests

# Code complexity check (Radon Grade B or better)
uv run python scripts/check_radon.py src

📚 Documentation & Roadmap


📄 License

This project is dual-licensed under:

Metadata

Release files for riftpoint 1.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for riftpoint 1.0.0
File Size Uploaded
riftpoint-1.0.0.tar.gz 27.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for riftpoint 1.0.0
File Interpreter ABI Platform
riftpoint-1.0.0-py3-none-any.whl Python 3 none any Details

Total release size: 63.5 kB

Release files / riftpoint-1.0.0.tar.gz

Download URL riftpoint-1.0.0.tar.gz
Size 27.2 kB
Tags Source
SHA-256 checksum
How to use checksums
82ee299ed8ed0f769fbc7330e4d7ba9e40c5d4c1f14ac9c7a289b2af38e18a69
BLAKE2b-256 checksum
How to use checksums
68b5004af204127432ed357acb4f9f3efe9a1ab162558263fedc3ea8dbe5c004
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.

Transparency log

Release files / riftpoint-1.0.0-py3-none-any.whl

Download URL riftpoint-1.0.0-py3-none-any.whl
Size 36.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c50333ab48db40f5ed6c1796856877c2ab07b00b448aee2b972b8cdc0fb67f29
BLAKE2b-256 checksum
How to use checksums
490090e60d2b3cd0a52775687190c0ee39d0253d7d85148ce0636794b474654f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.0.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page