Back to browse
GitHub Repository

Deterministic decision engine with receipts for agents

6 starsPython

Cruxible Core – Deterministic decision engine with receipts for agents

by rmalone1097·Mar 5, 2026·2 points·0 comments

AI Analysis

●●●BangerBig BrainSolve My ProblemZero to One

Auditable agent decisions via DAG receipts—unlike prompt-dependent LLMs, this proves reasoning.

Strengths
  • Receipt/DAG model makes decisions reproducible and challengeable, not opaque
  • Feedback loop compounds domain knowledge across sessions, improving confidence over time
  • Real demos (DDI, OFAC, MITRE ATT&CK) show concrete high-stakes use cases beyond hype
Weaknesses
  • Tiny ecosystem—success depends entirely on adoption by AI orchestration platforms
  • Early stage (6 GitHub stars); unclear how much production traffic it handles
Target Audience

AI engineers, compliance teams, high-stakes decision systems (drug interactions, sanctions screening, threat detection)

Similar To

Langchain agents with memory · Prolog/logic programming engines · Supabase for structured queries

Post Description

Cruxible Core is an open source MCP server/runtime that lets you define a decision domain in YAML (entities, relationships, queries, constraints), then run queries deterministically via AI agents (Codex, Claude Code, Cursor).

Every query returns a DAG receipt showing exactly how the result was derived (nodes traversed, filters/constraints applied, outputs). The goal is to make agent decisions auditable and reproducible instead of prompt-dependent.

I built this because LLMs are strong at orchestration and general reasoning, but high-stakes decision logic often needs deterministic execution and explicit proof trails. Cruxible receipts are meant to be audited, replayed, and challenged.

There’s also a feedback loop: users can approve/correct/reject edges and update confidence/evidence, so domain knowledge and decision trails compound across sessions.

Demos included: - Drug interactions (DDinter + CYP450) - OFAC sanctions screening (ownership chains) - MITRE ATT&CK threat modeling

Known limitations: - Candidate edge generation is still basic (property matching, shared-neighbor analysis, AI suggestions) - No application/action layer yet (e.g., transaction blocking, clinical alerts) - --limit queries currently persist full receipts instead of pruning to returned rows (fix planned)

Repo: https://github.com/cruxible-ai/cruxible-core

Thank you for reading! Feedback I’d value most: 1. What limitation makes this less useful for your domain? 2. Any setup/usability issues you hit? 3. Structural criticism of the approach

Similar Projects

Developer Tools●●Solid

Agent Audit Kit v0.1 – deterministic replay + stress for LLM agents

Deterministic capture + replay for LLM agents is a practical, under-served problem and this repo actually ships a 'golden run' zip with cold‑run verification hashes — that’s the kind of evidence chain auditors want. The focus on portable evidence bundles and stress verification suggests useful forensics and load testing of agent logic, but the release page looks early-stage; I'd like to see integrations (tooling for popular agent frameworks), richer docs, and example pipelines before I'd evangelize it.

Niche GemSolve My ProblemShip It
helpfuldolphin
104mo ago
Developer Tools●●●Banger

FlowScript – Agent memory where contradictions are features

Five queries vector stores can't answer: why(), tensions(), blocked(), whatIf(), alternatives().

Big BrainZero to OneWizardry
phillipclapham
212mo ago