Concordance
@matharrismma
Language models generate; Concordance verifies. The verify tool checks a claim deterministically (no model in the loop) and returns HOLDS / BROKEN / INCOMPLETE with the worked reasoning and a sealed receipt (content_hash + cite_url) that re-fetches byte-identical or not at all. A
概要
What is Concordance?
Concordance is a deterministic verification engine that 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 is built on a foundation of the Bible and offers two configurable surfaces: a secular reach and an explicit witness.
How to use Concordance?
Run with PYTHONPATH=src python -m concordance serve for the secular surface, or add --surface witness for the witness face. Then open http://127.0.0.1:8000/ to bring a claim and get a receipt. Data is generated by migration tools, but the engine runs without it (with less retrieval).
Key features of Concordance
- Seven primitives: Claim, Verifier, Verdict, Seal, Ledger, Ranker, Surface.
- Deterministic verification with a guarantee of zero false-positives.
- Tamper-evident ledger through an append-only hash chain of seals.
- Configurable secular or witness surface from one foundation.
- Purely functional verifiers with no I/O and no LLM involvement.
- Content-addressed SHA-256 seals for independent re-verification.
Use cases of Concordance
- Verify structured assertions and obtain a reproducible receipt.
- Build a tamper-evident audit trail of claims and verdicts.
- Deploy a verification API on either a secular or faith-based surface.
FAQ from Concordance
What does the seal contain?
The seal is a content-addressed (SHA-256) record of the claim, verdict, and trail.
Can I run the engine without the Bible data?
Yes, the engine runs without the generated data (keeping, WEB Bible, Strong's), though retrieval will be limited.
Does Concordance use any AI or LLM?
No, verifiers are pure deterministic functions with no I/O and no LLM.
What are the runtime dependencies?
The engine is stdlib‑first; heavy dependencies (sympy, scipy, numpy) are optional and lazy‑loaded.
How do I switch between secular and witness surfaces?
Set the surface via configuration: EngineConfig("secular") or EngineConfig("witness"). The server also accepts --surface witness.
