Cruxible Core

What is Cruxible Core?

Cruxible Core is a deterministic, typed state layer for AI agents and human teams to operate on verifiable, governed domain state. It models entity and relationship types, write rules, and recurring workflows in a Terraform-like config, and the runtime enforces them. The core contains no LLM or hidden API calls—it works with any agent harness and pins exports from real systems as artifacts.

How to use Cruxible Core?

Install with pip install cruxible, then start a local daemon with CRUXIBLE_SERVER_STATE_DIR="$HOME/.cruxible/sandbox" cruxible server start. Initialize a domain with cruxible init --kit <name>, connect an agent session with cruxible context connect, run deterministic workflows with cruxible run and cruxible apply, propose governed claims with cruxible propose, and resolve them with cruxible group resolve. Queries return receipted results via cruxible query run.

Key features of Cruxible Core

• Deterministic ingest: state enters row by row from pinned artifacts.
• Governed writes: proposal flow with declared evidence and human review.
• Executable model: declared workflows are previewable, replayable, and versioned.
• Reproducible reads: same query, same state, same result with a receipt.
• No LLM inside: core is a pure deterministic layer, works with any agent.

Use cases of Cruxible Core

• Supply-chain blast radius: from an incident, traverse impacted suppliers to exposed components.
• Incident impact analysis: judge and record which incidents materially impact suppliers.
• Governed domain modeling: define entity types, relationships, and approval routing in a single config kit.

FAQ from Cruxible Core

What is the difference between Cruxible Core and RAG/vector memory?

Cruxible Core models the domain as typed, governed state instead of retrieving similar chunks of text. Claims carry provenance and review state, multi-hop traversal follows exact relationships, and results are exact and repeatable across reads. Markdown and retrieval remain appropriate for drafts and exploration, but Cruxible Core certifies durable truth outside the model.

What dependencies and runtime are required?

Cruxible Core runs on Python 3.11+. It is installed via pip install cruxible and launched as a local HTTP server. No LLM, external API, or database is required—state is local to a state directory (CRUXIBLE_SERVER_STATE_DIR), and sandbox mode uses a built-in operator identity.

How is authentication and data transport handled?

When CRUXIBLE_SERVER_AUTH=true is set, identity is enabled: a bootstrap credential is claimed, and each agent receives its own token attributing every write. The server listens by default on http://127.0.0.1:8100. Token-based permission tiers and hardening are documented in the Runtime Auth And Agent Roles guide.