Concordance Engine

The problem

You've sat in this meeting. The motion is moved. Someone asks "what's our budget for this?" and the answer is "it should be in last quarter's report." Someone asks "who's signing this off legally?" and the answer is "we'll figure that out after." The motion passes. Three months later, nobody remembers who was responsible for what, and the board minutes can't tell you.

Structural failure in governance is almost never a single big mistake. It's a thousand small omissions that compound. The Concordance Engine catches the omissions at packet construction, not at the postmortem.

What gets checked

Every decision packet passes four gates before the engine calls it ready:

RED
Hard · REJECT
Forbidden categories: coercion, deception, exploitation, idolatry. Named explicitly so the rejection is auditable.
FLOOR
Hard · REJECT
Required structural pieces: title, scope, red_items, floor_items, way_path, execution_steps, witnesses.
BROTHERS
Soft · QUARANTINE
Witness count meets the board's threshold. Configurable per scope. Disabled by default.
GOD
Soft · QUARANTINE
Wait window: 1 hour for adapter scope, 24 hours for mesh, 7 days for canon. Buys time for an objection to surface.

Per-domain profiles

A board decision is not a household decision. The engine has separate required-field profiles:

DomainRequired fields (added to base)Recommended
business officers, fiduciary_basis dollar_amount, risk_assessment
household budget_category, affected_dependents time_horizon, alternatives_considered
education affected_cohort, learning_objective accommodation_plan, policy_reference
church elder_signoff, scripture_anchor congregation_impact, prayer_record

A worked example

The chair is about to call a vote on a vendor contract. Before the vote, the secretary runs:

verify_governance_decision_packet({
  "title": "Approve Q3 vendor contract",
  "scope": "mesh",
  "red_items": ["no exploitation", "no deception"],
  "floor_items": ["budget within tolerance"],
  "way_path": "Award to Vendor A on 12-month terms with 90-day cancellation.",
  "execution_steps": ["Sign contract", "File with finance", "90-day review"],
  "witnesses": ["CEO", "CFO"]
}, witness_count=2, domain="business")

→ {"shape": {"status": "CONFIRMED"},
   "witness_consistency": {"status": "CONFIRMED"},
   "domain_profile": {"status": "MISMATCH",
                       "detail": "business packet missing required:
                                  ['officers', 'fiduciary_basis']"}}

Two pieces are missing. The chair knows before the motion is moved. The secretary asks for the officers signing off and the fiduciary basis. Three minutes of work, and the minutes will be defensible if anyone asks later.

What it does not do

The engine doesn't tell you whether the decision is wise. It doesn't decide whether Vendor A or Vendor B is the better choice. It doesn't read the contract for hidden terms. It catches the structural gaps that make accountability possible — names attached to roles, dollar amounts attached to authorizations, witnesses attached to attestations. The judgment about whether to vote yes is still yours.

Install → How the gates work