SUMMARY: A default-route audit reveals what a system does when choice, evidence, ownership, timing, or integration fails, and tests whether that route remains justified. Run it on a consequential workflow before changing the interface or policy.
1. Define the Consequence
Name the state, delay, restriction, charge, disclosure, or enforcement action the route can produce. Identify who bears the effect and how quickly it becomes difficult to reverse.
2. Enumerate Every Trigger
List missing choices, timeouts, invalid fields, unavailable services, identity conflicts, capacity thresholds, failed transfers, unsupported evidence, and absent owners that invoke the default.
3. Trace the Actual Route
Follow synthetic cases across interfaces, queues, vendors, rules, operators, and recipients. Use the unobserved-path method when telemetry ends before the consequence.
4. Test Whether Choice Was Meaningful
Check visibility, language, accessibility, device support, delivery time, cognitive load, and whether declining the default creates disproportionate delay or documentation burden.
5. Inventory the Alternatives
For each branch, record whether it is visible, reachable, staffed, funded, and authorized to change the outcome. An option that cannot execute is not an alternative.
6. Compare Outcomes
Measure time, error, abandonment, escalation, reversal, downstream propagation, and burden by trigger and participant context. Look for groups overrepresented in the default without assuming preference.
7. Expose the Route in the Record
Record the trigger, rule version, alternatives presented, recognized choice, owner, timestamps, recipients, current state, and reversal route in the participant status ledger.
8. Test the Least-Harmful Default
Compare automatic action with pause, clarification, temporary protection, data minimization, and human escalation. Prefer the route that limits irreversible harm while preserving later choice.
9. Assign Ownership and Expiration
Give every default a named owner, justification, approval date, review interval, kill condition, and dependency inventory. A default without an expiration test becomes inherited policy.
10. Revalidate After Change
Repeat the audit after policy, interface, model, vendor, staffing, or topology changes. Add the route to the control revalidation cycle.
Operator rule: no consequential default should remain active unless its trigger, burden, alternatives, owner, and reversal path can be independently demonstrated.
Continue the discussion in the Clandestinia forum.