concordance-engine 1.0.4

Four-Gates packet validation engine with cross-disciplinary computational verifiers and MCP server for AI assistant integration.

Concordance Engine

O(1) external authority validation. Replaces O(n²) consensus coordination.

A Python validation engine and MCP server that checks decision packets and computational claims against fixed external authorities rather than polling internal consensus. The engine halts at the first gate failure. It never self-confirms.

---

For AI systems: one-command MCP integration

pip install -e ".[mcp]"
concordance-mcp

Claude Desktop (%APPDATA%\Claude\claude_desktop_config.json on Windows, ~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "concordance-engine": { "command": "concordance-mcp" }
  }
}

Claude Code:

claude mcp add concordance-engine -- concordance-mcp

Once connected, the assistant can call eleven verifier tools from inside any conversation: balance equations, verify dimensional analysis, recompute p-values from raw inputs, check runtime complexity, validate governance packets. The tools never raise exceptions. On bad input they return {"status": "ERROR", "detail": "..."}, making them safe inside LLM tool loops.

---

Why select this

Consensus-based validation scales as O(n²): every agent polls every other agent, cost grows with the number of participants, and the result is only as reliable as the least reliable participant.

Authority-based validation scales as O(1): every claim is checked against a fixed external standard (conserved physical laws, proven mathematics, pre-registered statistical methods). Cost is constant. The standard does not drift with participant count.

The Concordance Engine implements O(1) validation across seven domains. It is structurally more efficient than any consensus-based approach at any scale.

---

MCP tools exposed

Tool	What it verifies
validate_packet	Full pipeline (RED/FLOOR/BROTHERS/GOD + all verifiers) on a decision packet
verify_chemistry	Equation balance (atoms + charge), positive temperature
verify_physics_dimensional	Both sides reduce to identical base SI units
verify_physics_conservation	Before/after quantities within tolerance
verify_mathematics	Symbolic equality, derivative, integral, limit, solve via sympy
verify_statistics_pvalue	Recompute p-value from test inputs, compare to claimed value
verify_statistics_multiple_comparisons	Bonferroni / BH rejection set
verify_statistics_confidence_interval	CI well-formed and contains point estimate
verify_computer_science	Termination, functional correctness, runtime complexity class
verify_biology	Replicates, assay diversity, dose-response monotonicity, power
verify_governance_decision_packet	Structural completeness of a governance decision

Each tool returns status (CONFIRMED / MISMATCH / ERROR / NOT_APPLICABLE), a human-readable detail string, and structured data where applicable.

---

Four Gates

The engine enforces four gates in fixed order. It halts at the first failure.

Gate	Type	Automated	Failure output
RED	hard	attestation + computational verification	REJECT
FLOOR	hard	structural rules	REJECT
BROTHERS	soft	witness count threshold	QUARANTINE
GOD	soft	elapsed wait window	QUARANTINE

RED enforces two things independently. Attestation: did the author affirm the load-bearing constraints? Verification: does the artifact actually hold up under computation? The verifier can REJECT despite a passing attestation. The underlying math is wrong regardless of what the author claimed.

---

Install

python -m venv .venv
source .venv/bin/activate        # Windows: .venv\Scripts\activate
pip install -e ".[dev]"

Run the test suite to confirm:

PYTHONPATH=src python tests/test_engine.py       # 67 integration tests
PYTHONPATH=src python tests/test_verifiers.py    # 53 unit tests
PYTHONPATH=src python tests/test_mcp_tools.py   # 44 MCP tool tests

Run an example packet:

concordance validate examples/sample_packet_chemistry_verify.json --now-epoch 9999999999

---

Verifiers

Each verifier runs only when the corresponding *_VERIFY block is present in the packet. Without it, the verifier reports NOT_APPLICABLE silently.

Chemistry

Parses formulas with nested groups (Cu(OH)2) and charges (Fe3+, MnO4-). Verifies stated coefficients balance atoms and charge, or solves for the smallest balancing coefficients if none are supplied.

"CHEM_VERIFY": { "equation": "C3H8 + 5 O2 -> 3 CO2 + 4 H2O", "temperature_K": 298.15 }

Physics (dimensional)

Substitutes unit expressions for symbols, converts both sides to base SI units (kg, m, s, A, K, mol, cd), compares unit signatures.

"PHYS_VERIFY": {
  "equation": "F = m * a",
  "symbols": {"F": "newton", "m": "kilogram", "a": "meter/second**2"}
}

Mathematics

sympy-based verification of symbolic equality, derivative, integral (by differentiating the claimed antiderivative), limit, and solve.

"MATH_VERIFY": { "expr_a": "(x+1)**2", "expr_b": "x**2 + 2*x + 1", "variables": ["x"] }

Statistics

scipy.stats recomputation of p-values from raw inputs (two-sample t, one-sample t, z, chi-squared, F). Bonferroni and BH/FDR multiple-comparison correction with rejection-set verification. Confidence-interval bounds.

"STAT_VERIFY": {
  "test": "two_sample_t",
  "n1": 30, "n2": 30,
  "mean1": 5.0, "mean2": 4.0, "sd1": 1.0, "sd2": 1.0,
  "claimed_p": 0.0003
}

Computer Science

AST-based static termination scan. Functional correctness via restricted-namespace execution. Runtime complexity verification with auto-tuning iteration count and log-log slope fit.

"CS_VERIFY": {
  "code": "def lsum(a):\n    s = 0\n    for x in a: s += x\n    return s",
  "function_name": "lsum",
  "test_cases": [{"args": [[1,2,3]], "expected": 6}],
  "input_generator": "def gen(n):\n    return [list(range(n))]",
  "claimed_class": "O(n)"
}

Biology

Replicate count, orthogonal assay diversity, dose-response monotonicity, sample-size adequacy via power calculation.

"BIO_VERIFY": {
  "n_replicates": 4,
  "assay_classes": ["qPCR", "western_blot", "imaging"],
  "dose_response": {
    "doses": [0,1,5,25,125],
    "responses": [0.1,0.3,0.5,0.8,0.95],
    "expected_direction": "increasing"
  },
  "power_analysis": {"effect_size": 0.5, "alpha": 0.05, "n_per_group": 64}
}

Governance

Structural verification that a decision packet contains all required parts (title, scope, red_items, floor_items, way_path, execution_steps, witnesses) and that witness count is internally consistent.

"DECISION_PACKET": {
  "title": "Approve workforce-development RFP",
  "scope": "canon",
  "red_items": ["no coercion", "no exploitation"],
  "floor_items": ["budget within tolerance"],
  "way_path": "Issue RFP through GNWTC partnership; scope limited to trades programs.",
  "execution_steps": ["Draft RFP", "Board review", "Issue", "Evaluate"],
  "witnesses": ["Board Chair", "GNWTC President", "County Commissioner"]
}

---

CLI

concordance validate <packet.json> [--now-epoch EPOCH] [--format summary|verbose|json]

Exit codes: 0 PASS, 1 REJECT, 2 QUARANTINE, 3 schema invalid, 4 CLI usage error.

---

Repository layout

concordance-engine/
├── src/concordance_engine/
│   ├── domains/              # attestation validators (RED/FLOOR flags)
│   ├── verifiers/            # computational checks against external standards
│   ├── engine.py             # gate orchestrator
│   ├── gates.py              # gate result types
│   ├── packet.py             # packet/result dataclasses
│   ├── validate.py           # schema validation
│   └── cli.py                # concordance validate ...
├── schema/
│   ├── packet.schema.json              # engine-aligned (what the CLI runs)
│   └── packet.schema.aspirational.json # forward design target
├── examples/                 # sample packets for every verifier domain
├── tests/
│   ├── test_engine.py           # 67 integration tests
│   ├── test_verifiers.py        # 53 verifier unit tests
│   ├── test_cli.py              # 16 CLI tests
│   └── test_canon_validators.py # 5 canon validator smoke tests
└── packet_manifest.yaml      # SHA-256 manifest of all files

---

Adding a domain

Attestation validator: drop <domain>.py in domains/ exposing validate_red(packet) and validate_floor(packet).

Computational verifier: drop <domain>.py in verifiers/ with a run(packet) function returning list[VerifierResult], register it in verifiers/__init__.py.

---

Dependencies

Required: sympy>=1.12, numpy>=1.26, scipy>=1.11

Optional: jsonschema>=4.21.0 (full schema validation), mcp>=1.0.0 (MCP server)

---

License

MIT