IncidentMesh

What it does

IncidentMesh is a concurrent incident-response system where independent Trace, Dependency, and Impact responders investigate the same incident in parallel and publish evidence into shared Mozaik state. A Safety Gate evaluates that evidence at an action boundary. In the canonical demo, conflicting evidence blocks a proposed rollback_production call, Mozaik’s real interception path rewrites it to request_corroboration, and the system moves to a canary-and-corroboration response instead.

How the agents run concurrently

Trace, Dependency, and Impact are separate Mozaik participants with independent handlers triggered by the same incident.opened event. They operate concurrently rather than waiting for fixed handoffs, and all three responder pairs overlap in the deterministic fixture. Their hypotheses enter shared typed runtime state as they arrive. IncidentMesh includes a controlled scheduling ablation holding the incident, evidence, policy, proposed action, and action boundary constant: with concurrent scheduling, all required evidence is present in time to identify the conflict and choose a targeted canary response; with serialized evidence, the same fail-closed gate must hold for missing evidence until the remaining signals arrive.