MADADH halts a protected runtime when authority or integrity fails. The halt latches persistently and survives reboot. Restart requires two physical hardware tokens and cryptographically signed clearance bound to the specific halt event. No cloud dependency. Chaos and soak tested.
No reviews yetBe the first to leave a review for MADADH
Maker
📌
I built MADADH because I kept seeing systems that claimed to fail closed but had no enforced mechanism to prove it. Every security product I looked at either relied on software assumptions, single physical keys, or cloud connectivity to enforce control. None of them could evidence their behavior under real fault conditions.
MADADH enforces a hard rule locally. When authority or integrity breaks the runtime halts. That halt is latched to a hardware token and cannot be cleared without two physical devices and cryptographic clearance bound to the specific incident. It has been chaos and soak tested. The behavior is evidenced not claimed.