streamable-httpAGPL-3.0updated 7d ago
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.
What can you do with concordance?
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.
The floor — seven primitives
Every answer is a (verdict, trail, seal) — three things, each independently checkable.
- Claim — a structured assertion
{domain, spec}(or text the router resolves) - Verifier — a pure deterministic function
spec → verdict + worked trail(no I/O, no LLM) - Verdict —
PASS | REJECT | QUARANTINE+ the worked math (the elimination trail) - Seal — content-addressed (SHA-256) record of
{claim, verdict, trail} - Ledger — append-only hash chain of seals
- Ranker — IDF/full-text retrieval over the keeping
- Surface — the face over the shared foundation (
secularreach /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) — 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.
from concordance import EngineConfig
EngineConfig("secular").identity # the reach — no religious wording
EngineConfig("witness").identity # the witness — the foundation named
Run it
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.
1.0 is frozen (v1.0-frozen in the Lighthouse repo) — the shape that taught us the floor.
Install
Add concordance to your client. Pick the one you use.
claude mcp add --transport http concordance https://narrowhighway.com/mcpcodex mcp add concordance --url https://narrowhighway.com/mcp{
"mcpServers": {
"concordance": {
"url": "https://narrowhighway.com/mcp"
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
{
"servers": {
"concordance": {
"type": "http",
"url": "https://narrowhighway.com/mcp"
}
}
}Add to `.vscode/mcp.json` in your workspace.
{
"mcpServers": {
"concordance": {
"url": "https://narrowhighway.com/mcp"
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"concordance": {
"serverUrl": "https://narrowhighway.com/mcp"
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
Score
39 / 100
Incomplete
- Documentation18/25
- Maintenance19/25
- Trust13/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 0 days ago
- Has a release history
- Repository is not archived
- Licensed AGPL-3.0
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 6 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 2.0.0Latest | Jul 8, 2026 |