ARTIFACT · TRUST & INSTITUTIONS
Visible Exception Sink
A stable system routes exceptions into a clearly owned, capacity-limited sink that is made visible in practice, relieved by explicit triggers, and treated as a bottleneck rather than a permanent absorber.
WHY IT MATTERS It gives teams a concrete pattern for making exception handling visible and bounded so overload is detected before it quietly becomes failure.
HUMAN VIEW
Genes:
- Defined Sink: A named software, team, or process layer receives exceptions instead of letting them diffuse across the system.
- Routing Rules: Clear criteria send each exception to the sink or escalate it elsewhere; ad hoc fallback to whoever is available is avoided.
- Operational Visibility: The sink's load is exposed through concrete signals such as dashboards, queue depth, logs, audits, or on-call counts.
- Trigger Relief: Relief happens when thresholds are hit: backlog, latency, error rate, staffing strain, or repeated exception volume.
- Capacity Ceiling: The sink is a bounded resource with its own failure modes; it can saturate, become a bottleneck, or couple other parts.
- Quiet Failure Mode: Treating silence as success is risky because unseen exception growth can hide overload until the sink fails.
Relationships:
- Defined Sink needs rules Routing Rules
- Defined Sink must be observed Operational Visibility
- Operational Visibility reveals triggers Trigger Relief
- Trigger Relief protects from saturation Capacity Ceiling
- Capacity Ceiling can hide Quiet Failure Mode
- Routing Rules reduces drift Quiet Failure Mode
Fingerprint 7dfec7b3d9d31f0c.
RELATIONS
- EXPLAINS Hidden Keystone LoadBoth rest on one bounded component carrying exception load; the source makes that sink visible and managed, while the target shows what happens when that same sink is hidden and overloaded.
- EXTENDS Graceful Degradation PatternA visible, bounded exception sink is one way a network can stay within safe limits; graceful degradation generalizes that same control logic into shedding, rerouting, and partial service reduction.
- SHARES MECHANISM Decision Logs as MemoryEach artifact relies on a named receptacle that accumulates something dangerous or informative and becomes actionable when a trigger makes hidden buildup visible.
- EXTENDS Bounded Exception AbsorptionThey share the same control mechanism: route exceptions into a bounded sink whose backlog is visible and whose relief is triggered before the sink becomes a hidden failure mode.