MADADH enforces a single hard rule: when authority or integrity fails, the protected runtime halts deterministically. It stays halted. It does not resume until the correct physical authorities and cryptographic validation are present.
MADADH is not a convenience layer. It is not a permissive orchestration system. It is a portable, fail-closed enforcement capability built for environments where continued execution under broken trust is unacceptable.
Most systems fail gracefully. They degrade, retry, and assume. MADADH does none of that. When a critical trust condition fails, the response is refusal. Persistent refusal. The system halts, records that halt in a durable latch, and holds that state until the correct physical and cryptographic conditions are satisfied by a human operator with the right tokens in hand. Deploy it anywhere. Carry it with you. The authority travels with the hardware.
Prevents a system from continuing because software assumes authority is still valid. Authority is continuously verified, not assumed.
Prevents a system from resuming because a fault appears to have disappeared or a component has been reconnected. Recovery requires explicit validation.
Prevents a halted condition from being lost through reboot, restart, or process churn. The latch persists across all of these.
Removes dependence on memory, intent, or informal procedure as the basis for safe recovery. Recovery is explicit, ordered, and cryptographically bound.
Once a halt condition is entered, MADADH records and maintains a persistent latch state. That latch survives reboot, service restart, process churn, and reconnection of any device.
Return to operation requires two separate physical tokens and cryptographically signed clearance data bound to the specific machine, the specific halt event, and the current recovery window. Nothing else will do.
The master authority token alone is not sufficient. Both tokens must be present.
MADADH has been tested end-to-end under live conditions including chaos testing and extended soak runs. The following behaviors have been observed and evidenced, not assumed.
MADADH uses a local four-role architecture. State is exchanged through an atomic file-based bus. Supervisory logic is deterministic and locally self-contained. No remote orchestration. No cloud dependency. No ambiguity in decision flow.
| Role | Function |
|---|---|
| Master | Validates authority state and master control conditions on a continuous basis. Physical hardware token binding enforced throughout operation. |
| Heartbeat | Monitors runtime continuity and expected supervisory presence. Detects loss of control-plane coherence. |
| Health | Evaluates protected runtime and control-plane health conditions. Triggers halt on defined failure states. |
| Bridge | Handles local state exchange, event movement, and control communication across the local bus. |
MADADH is built for environments where the critical question is not whether a system can keep running, but who is allowed to let it run again. If that is your problem, get in touch.
contact@madadh.systems