quorum

# Quorum — Multi-Agent Validation

> **⚠️ BOUNDARY DOCUMENT:** Before modifying, publishing, or releasing any Quorum code, config, or documentation, read and follow `portfolio/research-infrastructure/VALIDATOR-QUORUM-BOUNDARY.md`. This file defines the Validator (internal) / Quorum (public) boundary, what graduates and what stays proprietary, and CKMS naming conventions. No exceptions.

Quorum validates AI agent outputs by spawning multiple independent critics that evaluate artifacts against rubrics. Every criticism must cite evidence. You get a structured verdict.

## Quick Start

Clone the repository and install:

```bash
git clone https://github.com/SharedIntellect/quorum.git
cd quorum/reference-implementation
pip install -r requirements.txt
```

Run a quorum check on any file:

```bash
python -m quorum.cli run --target <path-to-artifact> --rubric <rubric-name>
```

### Built-in Rubrics

- `research-synthesis` — Research reports, literature reviews, technical analyses
- `agent-config` — Agent configurations, YAML specs, system prompts

### Depth Profiles

- `quick` — 2 critics (correctness, completeness) + pre-screen, ~5-10 min
- `standard` — 4 critics (+ security, code_hygiene) + pre-screen, ~15-30 min (default)
- `thorough` — all 4 shipped critics + pre-screen, ~30-60 min

All depth profiles include the deterministic pre-screen (10 checks: credentials, PII, syntax errors, broken links, TODOs, and more) before any LLM critic runs.

### Examples

```bash
# Validate a research report
quorum run --target my-report.md --rubric research-synthesis

# Quick check (faster, fewer critics)
quorum run --target my-report.md --rubric research-synthesis --depth quick

# Batch: validate all markdown files in a directory
quorum run --target ./docs/ --pattern "*.md" --rubric research-synthesis

# Cross-artifact consistency check
quorum run --target ./src/ --relationships quorum-relationships.yaml --depth standard

# Use a custom rubric
quorum run --target my-spec.md --rubric ./m...