Residual Case Log¶
Case register — instantiates Tool-Repertoire Bias Counterbalancing
A standing register of cases that don't fit current categories, each tagged with an owner and a route, so residuals are preserved and resolved rather than dumped.
A Residual Case Log is a persistent, cross-case register of everything that did not fit the available categories, tools, or workflows — kept over time so that patterns of misfit accumulate instead of vanishing. Its defining move is durable memory with accountability: every logged residual carries an owner and a disposition — routed, escalated, scheduled for review, or explicitly declined with a reason — so recording a misfit becomes an obligation to resolve it rather than a place to bury it. Where a one-time analysis surfaces residuals for a single case, the log's whole point is longevity and aggregation: it is the institution's ledger of what its tools keep failing to grip, and it refuses to let those cases quietly become "not our problem."
Example¶
An e-commerce company's customer-operations team runs on a ticketing system with fixed categories: shipping, returns, billing, product defect. Anything that doesn't fit gets crammed into "other" and closed — which means it disappears. A team lead stands up a Residual Case Log for exactly these misfits.
A customer writes that the product arrived fine but the packaging was so wasteful they're embarrassed to reorder — no category holds "brand-damage from packaging." Another reports that the size chart is accurate but written only in inches, useless to their overseas team. Each goes in the log as a residual, not a closed "other" ticket: owner assigned, disposition set. The packaging complaint is routed to sustainability with a review date; the size-chart gap is escalated to product content. Over a quarter, the log shows eleven packaging complaints clustering — a pattern no single "other" ticket could have revealed. What the ticketing tool treated as noise the log preserved as signal, each case with a name attached so none rots into an unowned grievance.
How it works¶
- Capture what the categories exclude. Anything that would otherwise be forced into a catch-all bucket or closed as "doesn't fit" is entered verbatim, in the stakeholder's terms, before any tool reshapes it.
- Attach owner and disposition. Every entry gets a named owner and one of a fixed set of routes — referred, escalated, scheduled, or explicitly declined-with-reason. No entry is allowed to sit ownerless.
- Aggregate to find patterns. Because it persists across cases, the log surfaces recurring misfits — clusters that signal a real repertoire gap rather than a one-off oddity.
Tuning parameters¶
- Entry threshold — log every deviation versus only cases that truly resist all categories. A low threshold captures more signal but bloats the log; a high one is lean but misses slow-building patterns.
- Disposition discipline — how strictly every entry must carry an owner and route. Strict discipline prevents dumping but adds overhead; loose discipline lets the log rot into a graveyard.
- Review cadence — how often the log is read for clusters. Frequent review catches emerging gaps early; rare review lets patterns calcify into normalized workarounds.
- Decline rigor — whether "we won't act on this" requires a written rationale. Requiring one keeps non-action honest; skipping it reopens the dumping loophole.
When it helps, and when it misleads¶
Its strength is that it defeats the archetype's quiet erasure: cases a tool cannot grip normally leave no trace, and the log gives them a durable home where individual oddities become visible trends. It is the standing memory that a repertoire gap even exists.
Its failure mode is precisely the one the archetype names — residual dumping: a log that records without routing becomes a comfortable place to file a problem and forget it, and worse, its very existence can normalize the workaround, so a recurring misfit gets logged forever instead of fixed. This is normalization of deviance in artifact form: the exception, repeatedly recorded and tolerated, silently becomes the accepted state.[n1] The guarding discipline is to make ownership and disposition mandatory on every entry, to read the log for clusters on a cadence, and to route persistent patterns onward as evidence the repertoire itself must change.
How it implements the components¶
non_grippable_residual_register— the log is this register: the durable, aggregated record of cases the available tools and categories cannot hold, preserved in the stakeholder's own terms.referral_or_borrowed_tool_path— every entry's mandatory disposition routes it (refer, escalate, schedule, or decline-with-reason), so recording is coupled to a hand-off rather than a dead end.
It records and assigns residual cases but does not itself carry out the negotiated external transfer — pre-wiring and guaranteeing the borrow/refer/escalate landing is the Borrow-or-Refer Protocol, its nearest twin: the log remembers the misfit and names its owner, the protocol executes the send. It also does not diagnose why a tool failed a case after the fact (outcome_validity_check, the Tool-Mismatch Postmortem).
Related¶
- Instantiates: Tool-Repertoire Bias Counterbalancing — supplies the durable memory that keeps residuals from being erased.
- Consumes: Affordance Blind-Spot Walkthrough feeds it the residuals a per-tool probe surfaces.
- Sibling mechanisms: Borrow-or-Refer Protocol · Affordance Blind-Spot Walkthrough · Tool-Mismatch Postmortem · Problem-First Intake Template · Tool Repertoire Inventory · Alternative-Tool Red Team · Representation Fit Scorecard
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Residual Case Log operates as a persistent ledger, log, register, or case record that preserves history and traceability because it a standing register of cases that don't fit current categories, each tagged with an owner and a route, so residuals are preserved and resolved rather than dumped.
Independent corroboration: The frozen evidence defines Residual Case Log as 'A standing register of cases that don't fit current categories, each tagged with an owner and a route, so residuals are preserved and resolved rather than dumped', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Convergent development
Present-day reach: Universal
Rationale: Registering currently unclassified records with provenance until the scheme is revised is a classification and records-stewardship practice; owners and routes adapt it to operational case management.
Related originating lineages:
- Data Science & Analytics — data_science contributes operational analytics, profiling, and monitoring to the mechanism’s formative or independently convergent form; that contribution does not displace the primary library_information_science lineage.
- Organizational & Management Science — organizational_management contributes ownership, portfolio review, coordination, and operational governance to the mechanism’s formative or independently convergent form; that contribution does not displace the primary library_information_science lineage.
Review resolution: The blind reviewers disagreed on primary lineage; authoritative research supports library_information_science over the competing primary. Registering currently unclassified records with provenance until the scheme is revised is a classification and records-stewardship practice; owners and routes adapt it to operational case management. The cited Library of Congress Classification provides direct evidence for that defining form. Alternates are retained only where they contributed an independent formative tradition, while domain_reach=universal records later transfer separately from historical origin.
Review outcome: Researched adjudication after independent review; medium confidence.
Sources consulted:
Notes¶
[n1] Normalization of deviance — Diane Vaughan's term for how a repeatedly tolerated exception gradually becomes accepted as normal. A residual log guards against erasure but can itself normalize a misfit if entries are recorded and tolerated rather than routed and resolved. ↩