Anomaly Triage Board¶
Workflow — instantiates Correspondence Violation Detection and Theory Refinement
Maintains a decision queue where every apparent correspondence violation is kept visible until it is classified as noise, error, boundary condition, or genuine theory failure.
An Anomaly Triage Board is the standing workflow that holds every apparent correspondence violation in a visible queue and refuses to let any of them close until someone has assigned it a type. Its single defining move is enforced classification: a discrepancy cannot be silently shrugged off as "probably nothing" or silently promoted to "the theory is broken" — it must travel across the board from detected into one labelled bucket (noise, measurement or translation error, boundary condition, or genuine theoretical failure) before it is allowed to leave the queue. The board is not where an anomaly is interpreted in depth; it is where anomalies are prevented from disappearing and are routed to whoever handles that type. Everything downstream — auditing assumptions, extracting a boundary, convening experts — is triggered by the label the board hangs on the card.
Example¶
A public-health team builds a new agent-based model of influenza spread and expects it to reproduce the classic SIR compartmental curve in a well-mixed population. Validation throws off dozens of discrepancies at once: the peak arrives three days early, the attack rate runs high in one age band, a seeding run oscillates. Argued in a chat channel, these would be relitigated and forgotten. Instead each becomes a card on an Anomaly Triage Board with columns Detected → Triaged → Under refinement → Resolved. The rule: no card leaves Triaged without a label. Working the board collapses forty raw discrepancies into six — two labelled genuine boundary conditions (the well-mixed assumption fails in the sparse rural sub-network), one genuine theory gap, and the rest closed as seeding noise or a unit mismatch in the reporting window. The board's product is not an answer but a sorted, still-visible list that says what deserves a modeler's time and what does not.
How it works¶
- Intake as logging. Any detected divergence — from a test run, a benchmark, a field report — is entered as a card carrying its source, the expected-vs-observed values, and who filed it. Nothing is discussed until it is on the board.
- Mandatory classification. Each card must be moved into exactly one type bucket; "unclassified" is not a resting state. Cards labelled boundary or genuine are flagged for escalation rather than resolved on the board.
- Aging and work-in-progress limits. Cards that sit too long or queues that grow too deep are surfaced, so the failure mode of a silent backlog becomes visible.
- Definition of done. A card closes only with a label and a disposition (dropped-as-noise with evidence, corrected, or handed off) — never by going quiet.
Tuning parameters¶
- Triage taxonomy granularity — how many type buckets. Finer buckets route more precisely but slow every hand-off; coarse buckets are fast but blur real distinctions.
- Escalation threshold — how severe or how ambiguous a card must be before it leaves the board for a panel. Set low and the panel drowns; set high and hard cases get closed by whoever is on shift.
- Intake sensitivity — how small a divergence earns a card. Sensitive intake catches subtle failures but risks a flooded board; coarse intake keeps the board readable but can miss a thin boundary.
- Closing authority — who may label a card noise. Restricting it guards against clearing the queue by mislabeling.
When it helps, and when it misleads¶
Its strength is that it makes the two opposite errors of the archetype — explaining away a real anomaly and over-reacting to noise — both visible as choices someone signed. It converts a scatter of complaints into a governed queue where each item has an owner and a type, and it keeps genuine boundary failures from being lost in the churn.
Its failure mode is that a board under load becomes a graveyard: cards accumulate faster than they are worked, and the fastest way to clear the queue is to stamp everything noise. This is the correspondence analogue of alert fatigue[n1] — when signals are too many to service, the rational-feeling response is to stop attending, and real violations are dismissed alongside the false ones. The classic misuse is turning label counts into a throughput metric, which quietly rewards mislabeling. The guarding discipline is to periodically re-audit a sample of noise-closed cards, require evidence on that label specifically, and hold the escalation criteria narrow so the board routes rather than adjudicates.
How it implements the components¶
The board fills the detect-and-sort front of the archetype, not the interpretive back:
violation_detection_protocol— the intake discipline: a defined way each divergence is logged as a card with its source and expected-vs-observed evidence, so detection is a recorded event rather than a hallway remark.violation_triage_filter— the mandatory-label step: each card is forced into one type bucket before it can move, which is the triage filter operating as a workflow gate.
It does not implement adjudication_panel_or_review_role — ruling on the contested, high-stakes subset is the job of Expert Adjudication Panel. The board is the standing queue that sorts every anomaly by type; the panel is the convened authority that decides the few the board escalates.
Related¶
- Instantiates: Correspondence Violation Detection and Theory Refinement — the board is the routing layer that keeps the whole refinement loop from losing its inputs.
- Consumes: Limiting-Case Test Suite and Residual Divergence Map — the detectors whose flagged divergences become cards.
- Sibling mechanisms: Assumption Audit Worksheet · Boundary Condition Memo · Expert Adjudication Panel · Failure Mode Annotation Card · Limiting-Case Test Suite · Overlap-Regime Benchmark Table · Parameter Sweep Matrix · Regression Correspondence Harness · Residual Divergence Map
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Maintains a decision queue where every apparent correspondence violation is kept visible until it is classified as noise, error, boundary condition, or genuine theory failure, making its operative form a bounded selection, routing, admission, or allocation among eligible alternatives.
Independent corroboration: The frozen evidence defines Anomaly Triage Board as 'Maintains a decision queue where every apparent correspondence violation is kept visible until it is classified as noise, error, boundary condition, or genuine theory failure', so its operative form is Decision, Gate & Allocation.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Philosophy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Philosophy of science supplies the classification of anomalies as error, boundary condition, or theory failure rather than automatic refutation.
Related originating lineages:
- Computer Science & Software Engineering — Issue-tracking and model-validation pipelines provide the operational artifact.
- Organizational & Management Science — Visual work queues, aging rules, and definitions of done come from workflow management.
- Statistics & Experimental Design — Error and variability analysis distinguish noise from systematic discrepancy.
- Systems Thinking & Cybernetics — Feedback-based model refinement supplies the routing from discrepancy to revision.
Review resolution: Both reviewers locate the classification logic in philosophy. Software issue queues, organizational triage, statistical model checking, and systems feedback materially supply the persistent board, so the full artifact remains a cross-disciplinary synthesis.
Attribution caveat: The board is an Encyclopedia synthesis combining philosophy-of-science anomaly classification with operational triage and queue management.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
The board is a router, not a judge: its value collapses the moment it starts trying to resolve hard cards instead of labelling and escalating them. Keeping it shallow — classify, route, keep visible — is what lets the specialist mechanisms downstream do their work on a curated, not raw, stream.
[n1] Alert fatigue — the well-documented desensitization that sets in when people face more alerts than they can act on, so they begin ignoring or reflexively dismissing them, including the valid ones. First named in clinical-alarm and security-monitoring settings; the same dynamic degrades any triage queue that is allowed to overflow. ↩