# concordance

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/matharrismma/concordance-2  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/concordance

## Description
Deterministic claim verification with receipts across ~60 domains. No model in the loop.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "concordance": {
    "command": "npx",
    "args": ["-y","concordance"]
  }
}
```

## Documentation & README

# Concordance 2.0

A deterministic verification engine. It checks what is true and hands you a **receipt you can
re-verify** — a verdict, the worked reasoning, and a permanent content-addressed seal. It
eliminates what is not the answer so that what survives stands on its own.

> Rebuilt like a watch (the Calibre 44 discipline): one bounded, counted movement; serviceable by
> any competent hand; machine-honest — the accuracy *is* the finish. See
> [`docs/V2_DEFINITION.md`](docs/V2_DEFINITION.md).

## The floor — seven primitives

Every answer is a `(verdict, trail, seal)` — three things, each independently checkable.

1. **Claim** — a structured assertion `{domain, spec}` (or text the router resolves)
2. **Verifier** — a pure deterministic function `spec → verdict + worked trail` (no I/O, no LLM)
3. **Verdict** — `PASS | REJECT | QUARANTINE` + the worked math (the elimination trail)
4. **Seal** — content-addressed (SHA-256) record of `{claim, verdict, trail}`
5. **Ledger** — append-only hash chain of seals
6. **Ranker** — IDF/full-text retrieval over the keeping
7. **Surface** — the face over the shared foundation (`secular` reach / `witness`)

The measure: **reproducibility, zero false-positives on the published benchmark (docs/BENCHMARK.md), re-checkability.**

## One foundation, two surfaces

The foundation is the Bible ([`FOUNDATION.md`](FOUNDATION.md)) — Christ at the center. From it the
engine reaches the world two ways: a secular `.com` (the reach) and an explicit-witness `.org`.
One engine, one foundation, selected by config — never a fork.

```python
from concordance import EngineConfig
EngineConfig("secular").identity   # the reach — no religious wording
EngineConfig("witness").identity   # the witness — the foundation named
```

## Run it

```bash
PYTHONPATH=src python -m concordance serve          # the .com reach (secular) — API + site, same-origin
PYTHONPATH=src python -m concordance serve --surface witness   # the .org witness face
```
Then open `http://127.0.0.1:8000/` — bring a claim, get a receipt. (Data — the keeping, the WEB
Bible, Strong's — is generated by `tools/migrate_*.py` and gitignored; the engine runs without it,
just with less to retrieve.)

## Status

The 2.0 engine is built end to end — floor 7/7, the derivation moat (0 false-positives), the
tamper-evident ledger + precedent overlay, 62 verifiers, the witness overlay (theology / witness /
scripture / canon), the shared corpus + ranker, scripture ref-resolution + original-language word
study, the axes grid, a sovereign HTTP API, and the site. 13 test suites green. Sovereign,
stdlib-first; heavy deps (`sympy`/`scipy`/`numpy`) are optional, lazy-loaded. Port progress:
[`PORT_PLAN.md`](PORT_PLAN.md).

1.0 is frozen (`v1.0-frozen` in the Lighthouse repo) — the shape that taught us the floor.