ciris-persist

What it is and what it does

CIRISPersist is a Rust-backed storage layer for CIRIS federation nodes, exposing a unified Python API that abstracts away the choice between Postgres and SQLite backends. It manages multiple stateful substrates—signed reasoning traces, hash-chained audit logs, memory graphs, time-series telemetry, encrypted secrets, federation consensus state, fountain-coded content, and holonomic forever-memory tiers—all through one versioned interface. The package is designed as an in-process library (not a daemon), allowing a CIRIS agent or lens node to link it directly and avoid hand-rolling ~11 separate storage services.

The implementation enforces post-quantum cryptography (hybrid Ed25519 + ML-DSA-65) at federation tier, routes all signing and verification through ciris-verify to avoid crypto re-rolls, and aligns with the CIRIS Constitution 0.1.5 substrate clauses. Secrets are encrypted at rest using AES-256-GCM with hardware-backed master keys where available. The audit log uses RFC 6962 Merkle trees; the forever-memory substrate implements CEG §19 / §19.7 with signed manifests and authenticated partial reads. Both backends achieve 100% parity on every method, including observability queries and lens-derived schemas.

Use it for:

• Store signed reasoning traces and LLM-call logs for a CIRIS agent with cryptographic proof of event ordering.
• Maintain a hash-chained, per-tenant audit log compliant with RFC 6962 Merkle tree standards.
• Manage federated secrets with AES-256-GCM encryption and TPM/Keystore-backed master keys in a single API.
• Run a sovereign CIRIS node on resource-constrained hardware (Pi, iOS) using SQLite without second-class performance.
• Implement post-quantum-signed federation consensus state and holonomic memory tiers per CEG §19.
• Ingest and route divergence detection through quorum-merge logic without embedding a separate graph database.

Worth the install?

AI-flagged interpretation of the facts on this page — verify before relying

CIRISPersist provides unified, versioned storage for CIRIS federation nodes—handling signed event logs, audit trails, memory graphs, secrets, and telemetry—via a single Python API backed by Postgres or SQLite.

Yes, with conditions. Install if you are building a CIRIS federation node and need unified, constitution-aligned storage for signed events, audit logs, secrets, and telemetry. The active maintenance, zero known vulnerabilities, and Postgres/SQLite parity make it solid for federation use. Avoid if you require proprietary licensing (AGPLv3+ is restrictive) or horizontal sharding (library-only, not a service). The medium install friction (compiled Rust wheel) is typical for performance-critical storage layers.

Install

ciris-persist on PyPI

pip install ciris-persist

uv add ciris-persist

poetry add ciris-persist

Installing ciris-persist

Before you install

Medium install friction due to compiled Rust extension (PyO3 wheel); actively maintained with recent release (15 days ago). Requires Python 3.10+. Single runtime dependency on ciris-verify.

License in practice

AGPLv3+ license requires derivative works and network-accessible modifications to be open-sourced; suitable for open federation infrastructure but restrictive for proprietary deployments.

Quickstart

import ciris_persist as cp

engine = cp.Engine(dsn="sqlite://./agent.db", signing_key_id="agent-ed25519")
engine.register_consumer("my-adapter", ["cirisgraph"])
summary = engine.receive_and_persist(request_body_bytes)

Requires Python 3.10+; ciris-verify v5.10.0 must be installed; Postgres or SQLite backend required.

Verify before relying

• Whether the PyO3 wheel covers all target platforms beyond macOS ARM64 (Linux, Windows availability unclear).
• Performance characteristics under high-concurrency workloads beyond the published benchmark suite.
• Compatibility guarantees between ciris-persist v22.0.1 and ciris-verify v5.10.0 across future releases.

Package facts

Evidence: ciris_persist-22.0.1-cp310-abi3-macosx_11_0_arm64.whl

Tags

More Database packages