The capstone of the Eskimo Brothers stack: the completed validation core that holds HACI (the human side) and MACI (the machine side) to one identical three-artifact standard — a reference validator, a deterministic torture suite, and a tiered brutal auditor. Its job is singular: guarantee that anything claiming to be HACI or MACI is checked the same brutal way on both sides of the human/machine boundary. And above the two halves sits a third, converged layer — one auditor testing shared invariants against both at once, mapping where they agree and where they diverge — plus a system audit that breaks the assembled engine on purpose, to prove it isn't a rubber stamp. Two brothers, one bond between them: the duality made ternary.
python run_duality_engine.py and python system_brutal_audit.py on this exact source — both torture hashes reproduced bit-for-bit, the converged loop returned 12/12 · 12/12 · 1 asymmetry, and the system audit scored 14/14 with all five injected breaks surfacing. The MACI suite is additionally mutation-tested: nine deliberate validator breaks → nine catches. (An earlier snapshot scored 13/14 — its converged layer passed a zero-test vacuously; the system audit caught it, and this is the patched build.)| HACI · human | MACI · machine | |
|---|---|---|
| form | document dialect, line-oriented | message protocol, JSON Lines |
| extension | .haci | .maci |
| authority | ownership by case (human / ai / shared) | explicit field (sovereign / delegated / advisory / observer) |
| operators | ! ? > prefix / suffix duality | roles: COMMAND / PROPOSAL / QUESTION / EVIDENCE / DECISION / DELEGATE / CODE |
| core guarantee | committed human declarations are immutable | authority cannot be forged or exceeded |
| decision tracking | adjacency + commit-gating | explicit refs forming a verifiable DAG |
The split is principled: a human reading a document carries authority by typography (case); a machine parsing a message carries it in a field. Each half uses the affordance that fits its reader — but both are held to the same gauntlet below.
3 | [2.1, 2.9] | 3 scaffold that attacks the validator from both directions — below.3 | [2.1, 2.9] | 3Each half has its own FSS/BSS feeding its own foundation. The converged layer (shared/converged_audit.py) unifies them: seven shared invariants, each given a HACI realization and a MACI realization, asserted to hold on both. Convergence is at the property level, not the input level — the halves speak different surface languages, so no single literal input feeds both. FSS 12/12 · BSS 12/12.
The converged loop's unique product isn't a pass/fail — it's cross-half asymmetry detection: the map of where the two sides enforce a shared invariant with different strength. Recorded, not failed — the most valuable signal the convergence produces. Exactly one stands today:
FORWARD_REF error — machines need strict ordering for replayable streams. HACI enforces only reference resolvability: an out-of-order but resolvable reference is accepted with an OPEN_CONVERSATION warning — a human document tolerates a forward reference the reader can follow. Both guard the reference axis; MACI's constraint ⊃ HACI's. The split is principled, not a bug — so it is logged as the asymmetry, not raised as a failure.A component can be sound and the assembly still rotten — adapters mistranslate, a suite rubber-stamps, a crash gets swallowed. system_brutal_audit.py aims the same 3 | [2.1, 2.9] | 3 discipline at the whole engine, and proves anti-vacuity: it injects five breaks and demands each one surface as a failure.
All five surface. With Tier 1 (5/5 integration) + system-FSS (4/4) the assembled engine scores 14/14 — sound AND proven to fail when broken. The auditor is not a rubber stamp, and now neither is the thing that checks the auditor.
A faithful slice of the machine-side auditor, in your browser: FSS probes that should pass and BSS probes that should be caught, run through the ported MACI validator (same named checks: DECISION_WITHOUT_REFS, REF_NOT_FOUND, FORWARD_REF, CHAIN_CYCLE, DELEGATE_NO_SCOPE…). Now inject a regression — disable a rule and watch the BSS tier catch the hole it opens. That is what "the suite has teeth" means.
run_duality_engine.py, shared/converged_audit.py, system_brutal_audit.py, and for each half a *_validator.py, a *_torture.py, and a *_brutal_audit.py (run python run_duality_engine.py → exits 0, writes duality_engine_status.json). It deliberately does not include the editor extension, the defensive publications, or the converters — those build on top of this stable core.