Skip to content
Conduit

mcp server

Quorum-falkordb

Git revert for AI agent beliefs: shared memory for AI agents and teammates on FalkorDB. One correction quarantines a wrong fact and everything built on it, blocks and compensates actions. Set up from

HamzaShaikh-source/Quorum-falkordbcommunitylistedunreviewed

Set up

Runs on your computer. Pick your agent and operating system.

This project does not publish an install method we can turn into a config. Follow the README instead.

README

synced Oct 21, 2026

🛡️ Quorum: Git-Revert for AI Agent Beliefs on FalkorDB

Track 02 Track 03 Graph MCP tools Live Demo YouTube

When an AI agent acts on a hallucination, poisoned webhook, or outdated policy, vector databases leave you stranded. Quorum brings Git-like rollback, epistemic causal tracking, and automated compensation to multi-agent systems using FalkorDB.


⚡ Quick Links for Evaluators


🗺️ 1. Epistemic Graph Schema & Architecture

FalkorDB is not a passive cache in Quorum—it is the epistemic causal ground truth. Agents cannot execute stateful actions without citing valid graph facts, and invalidating a root node initiates sub-millisecond topological graph cascades.

graph TD
    S[Source: Ingestion Webhook / Document] -->|PROV_SOURCE| E[Event: Policy Change]
    E -->|EXTRACTED_FROM| F1[Fact: Return Window = 90d]
    F0[Fact: Baseline Return = 30d] -.->|SUPERSEDES| F1
    F1 -->|SUPPORTS| B[Belief: High-Risk Policy Active]
    B -->|LEADS_TO| D[Decision: Issue Refund #4092]
    D -->|PRODUCES| A[Action: Helpdesk Call]
    A -->|EMITS| O[OutboxSaga: Refund Clawback]

    classDef invalid fill:#ff4d4f,stroke:#a8071a,stroke-width:2px,color:#fff;
    classDef valid fill:#52c41a,stroke:#237804,stroke-width:2px,color:#fff;
    classDef source fill:#1890ff,stroke:#0050b3,stroke-width:2px,color:#fff;
    class F1,B,D,A invalid;
    class F0 valid;
    class S,E,O source;

Graph Primitives

Node LabelPurposeKey Properties
(:Source)Ingestion origin & audit anchorsource_id, uri, tenant_id, verified_at
(:Event)Temporal context or policy updateevent_id, type, occurred_at
(:Fact)Discrete atomic belief unitfact_id, claim, validity_state (valid, quarantined, invalid), confidence
(:Belief)Synthesized agent contextbelief_id, tenant_id, strength, stale
(:Decision)Agent reasoning trace citing factsdecision_id, agent_id, cited_fact_ids, rationale
(:Action)Stateful external side-effectaction_id, target_system, status, idempotency_key
(:OutboxSaga)Deterministic compensation hooksaga_id, action_id, compensation_endpoint, state

⚙️ 2. How the Graph Does the Work (Cypher Deep-Dive)

Quorum uses pure FalkorDB Cypher traversals to execute epistemic governance in real time:

A. Pre-Execution Epistemic Gating (Quorum Gate)

Before an agent can call an external tool (e.g. process refund, send email), the Quorum Gate inspects the causal chain of all cited facts. If any fact is quarantined or invalid, the action is blocked before execution:

MATCH (d:Decision {id: $decision_id})-[:CITES]->(f:Fact)
WHERE f.validity_state IN ['quarantined', 'invalid'] OR f.stale = true
RETURN count(f) AS violations, collect(f.claim) AS tainted_claims

B. Cascading Red-Wave Invalidation (Topological Rollback)

When an auditor quarantines a rogue fact (or when an event is superseded), Quorum traverses causal edges up to 10 hops deep in < 5ms, marking all downstream beliefs, decisions, and pending actions as invalidated:

MATCH (f:Fact {id: $tainted_fact_id})-[:LEADS_TO|SUPPORTS*1..10]->(downstream)
SET downstream.validity_state = 'invalid',
    downstream.invalidated_at = timestamp(),
    downstream.invalidation_reason = $reason
RETURN labels(downstream) AS type, downstream.id AS id

C. Outbox Saga Compensation & Retraction

For actions already executed externally, Quorum queries the downstream saga graph to trigger automated API compensations and compose Damage Control retraction notices:

MATCH (d:Decision {validity_state: 'invalid'})-[:PRODUCES]->(a:Action)-[:EMITS]->(s:OutboxSaga)
WHERE s.state = 'pending'
RETURN s.saga_id, a.target_system, s.compensation_payload, a.idempotency_key

🛡️ 3. The 4-Layer Defense Engine

  • Quorum Gate: Synchronous pre-flight epistemic policy check for every agent tool invocation.
  • Execute Guard: Verifies execution permissions against tenant RBAC (admin, auditor, agent).
  • Outbox Sagas: Guaranteed at-least-once compensation for external side-effects when underlying facts collapse.
  • Damage Control Room: Human-in-the-loop review interface providing one-click customer retraction emails, audit trails, and graph time-travel.

What your AI gets

When an AI agent connects to Quorum via MCP, it receives access to the full epistemic governance toolset across 28 MCP tools:

ToolDescription
announce_workBroadcasts active task intent to peer agents to prevent conflicting actions.
claim_handoffCoordinates multi-agent handoffs with shared epistemic state across agents.
deltaComputes graph mutations and invalidated nodes between two timestamps.
deriveDerives a conclusion or belief supported by active facts.
execute_actionExecutes a previously approved action with idempotency and saga registration.
explain_blast_radiusCalculates downstream impact and affected decisions for a belief.
find_pathFinds causal provenance paths between facts and actions.
get_mapRetrieves the local causal subgraph map for a given entity or root.
get_nodeInspects detailed graph properties, timestamps, and validity states of any node.
observeRecords an external system state or sensor observation.
peer_retrieveSecurely queries shared memory from an authorized peer Quorum instance.
quarantineQuarantines a fact or belief and triggers a cascading red-wave invalidation.
quorum_connectEstablishes authorized peering connection with an external Quorum instance.
quorum_connectionsLists currently active and authorized peer hub connections.
quorum_discoverDiscovers peer Quorum instances available across the local network.
quorum_guideInteractive guide and client agreement reference for agent coordination.
quorum_helpReturns capability manifest and usage guidelines for connected agents.
quorum_inboxChecks pending inter-hub connection requests and permission handoffs.
quorum_manageManages team member tokens, permission roles, and workspace seats.
quorum_respondApproves or declines incoming inter-hub connection requests.
quorum_startInitializes team workspace settings and onboarding configurations.
quorum_statusReports active graph statistics, quarantine counts, and connection health.
recall_as_ofPerforms time-travel belief retrieval as of a historical timestamp.
remember_factSaves an atomic fact with causal source provenance into FalkorDB.
restoreRestores a quarantined fact and reactivates healthy downstream descendants.
retrieve_contextRetrieves active, non-quarantined context subgraphs for safe prompt construction.
review_handoffInspects pending handoffs and verifies approval preconditions.
stage_actionProposes a stateful action to the Quorum Gate along with cited fact IDs.

🏆 4. Empirical Evaluation & Benchmark Results

Tested across a paired synthetic & real-agent benchmark against standard vector/RAG memory architectures (see docs/PROOF.md):

  • Preventing Unsafe Actions After Correction: 28/28 (100%) prevented in Quorum vs. 0/28 (0%) in standard vector memory.
  • Topological Invalidation Speed: < 4.2ms median cascade latency across 10-hop subgraphs on FalkorDB.
  • Concurrent Writer Durability: Group-commit shared sync ensures zero lost updates under high concurrency.
  • Test Suite: 669 backend unit & integration tests, 218 frontend tests passing (100% green).

🚀 5. Local Setup & Reproduction

Prerequisites

  • Docker & Docker Compose
  • Python 3.11+
  • Node.js 18+

1-Command Docker Launch

git clone https://github.com/HamzaShaikh-source/Quorum-falkordb.git
cd Quorum-falkordb
docker compose up -d
  • Open console: http://localhost:5173/
  • Backend API docs: http://localhost:8000/docs

👥 6. Team & Hackathon Disclosures

  • Hamza Shaikh (@HamzaShaikh-source) — Frontend & Cytoscape Console Lead
  • Aaditya Arunpal (@AsteroidHH) — Backend, Epistemic Engine & MCP Lead
  • Janani — FalkorDB & Cypher Graph Architecture Lead

AI Usage Disclosure: In compliance with Hackathon Rule 11, LLM assistance was utilized for test-case expansion, UI styling scaffolding, and drafting documentation. Core Cypher schemas, causal graph algorithms, group-commit logic, and defense gate architectures were developed by the team.

↑↓ navigate openesc close