Common-Cause and Copying Audit¶
Checklist — instantiates Independent Convergence Evidence Appraisal
Runs a fixed checklist of shared sources, incentives, regulations, vendors, and social proof to see whether any of them explains the repeated solution better than independent fit.
Common-Cause and Copying Audit is a standing checklist of the ways a repeated solution can be manufactured rather than discovered independently: a shared vendor or default, a common consultant or training program, a regulatory mandate, a dominant reference implementation, a citation everyone traces back to, a fashion cascade, a procurement incentive. Its defining move is categorical, not genealogical: it does not reconstruct any particular case's history — it takes each known common-cause mechanism in turn and asks "could this one, by itself, explain the pattern I see?" Every item that fires downgrades the convergence and gets logged in a dependency register. The audit's product is a list of alternative explanations that have been actively considered and either ruled in or ruled out, so the remaining convergence is what survives after the obvious shortcuts to agreement have been subtracted.
Example¶
A fintech analyst notices that a dozen consumer banking apps have all shipped a "round-up your purchase and save the change" feature within a couple of years, and a product deck cites this as proof the feature is a natural fit for how people save. Before believing it, she runs the audit. Shared vendor? Several of the apps are built on the same core-banking and personal-finance-management SDK, which ships round-up as a configurable module — one box ticked. Dominant template? An early, widely-covered incumbent feature is the obvious reference everyone benchmarked against. Social proof / fashion? Investor decks in the period treated the feature as table stakes, so shipping it signaled legitimacy regardless of fit. Regulation? No mandate — that box stays clear.
The register now reads: three plausible common causes fire, one does not. The convergence that looked like twelve independent discoveries is, after the audit, mostly one SDK default plus benchmarking plus fashion — with only a residue of possibly-independent adoption left to weigh. The audit did not disprove fit; it named the cheaper explanations that must be excluded before fit can be credited.
How it works¶
- Walk the fixed category list. Vendors and defaults, consultants and shared training, regulation and standards mandates, reference implementations, citation bottlenecks, procurement incentives, herding and social proof — each is a checklist item, applied uniformly to every claimed lineage.
- Ask the counterfactual per item. For each firing category: would the pattern still look this uniform if this common cause were removed? If not, the category explains part of the convergence.
- Log to a dependency register. Every firing item is recorded with what it explains, building an auditable list of alternative explanations considered.
- Subtract, don't conclude. The audit reports what remains unexplained by common causes; it does not itself decide the final warrant.
Tuning parameters¶
- Checklist breadth — how many common-cause categories are included. A longer list catches more artifacts but risks explaining away genuine convergence with speculative mechanisms.
- Firing threshold — how much a category must plausibly explain before it counts as "firing." A low bar makes the audit nihilistic; a high bar lets cheap explanations slip through.
- Evidence requirement per item — whether firing needs documented proof or reasonable suspicion. Suspicion is fast and conservative; proof is slower but fairer to the convergence.
- Scope of the register — whether it logs only firing items or the full cleared list too. Logging clears makes the "we considered and rejected this" defensible.
When it helps, and when it misleads¶
Its strength is completeness under time pressure: a fixed checklist guarantees the boring, decisive explanations — a shared vendor default, a mandated standard — are considered every time, rather than being skipped because the convergence felt compelling. It is the appraisal's guard against mistaking an information cascade for independent judgment.[n1]
Its failure mode is over-subtraction: a maximally suspicious auditor can find a plausible common cause for any pattern and explain real fit-driven convergence out of existence — treating the checklist as a debunking machine rather than a fair test. The classic misuse is firing a category on speculation alone ("they probably all copied someone") with nothing in the register to support it. The guarding discipline is to require at least suspicion-level evidence to fire an item, to log cleared categories as well as firing ones, and to hand any specific copying claim to a traceback for genuine confirmation rather than asserting it from the checklist.
How it implements the components¶
copying_and_cascade_exclusion_check— the audit is this check made systematic: each category is a candidate copying-or-cascade explanation tested and excluded or retained.common_source_dependency_register— the running log of firing categories, with what each explains, is the dependency register the appraisal carries forward.
It does NOT reconstruct any lineage's actual origin-and-transmission genealogy or its lineage_timing_sequence (lineage_independence_map) — that is its nearest twin, Lineage Traceback Protocol; the audit checks fixed categories of common cause, while the traceback traces the specific who-learned-from-whom history that would confirm one.
Related¶
- Instantiates: Independent Convergence Evidence Appraisal — the audit supplies the ruled-out alternative explanations that let residual convergence count.
- Consumes: Lineage Traceback Protocol — a firing "copying" item is confirmed by a traceback rather than by the checklist alone.
- Sibling mechanisms: Convergence Evidence Matrix · Lineage Traceback Protocol · Pressure–Solution Fit Rubric · Negative-Case Scan · Blind Pattern Comparison Round · Convergence Warrant Memo
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Runs a fixed checklist of shared sources, incentives, regulations, vendors, and social proof to see whether any of them explains the repeated solution better than independent fit, making its operative form a bounded evaluation of existing evidence or work that produces a finding or disposition.
Independent corroboration: The frozen evidence defines Common-Cause and Copying Audit as 'Runs a fixed checklist of shared sources, incentives, regulations, vendors, and social proof to see whether any of them explains the repeated solution better than independent fit', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Sociology & Anthropology
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Organizational sociology established coercive, mimetic, and normative isomorphism as explanations for similar organizational forms arising from regulation, dependency, imitation, professionalization, and shared models rather than independent fit.
Related originating lineages:
- Behavioral Economics — Information-cascade and social-learning models formalize how observing predecessors can rationally suppress independent private evidence.
- History & Historiography — Genealogical source criticism supplies the test for repeated forms descending from one transmitted source rather than independent invention.
Review resolution: DiMaggio and Powell's primary article identifies coercive, mimetic, and normative processes driven by dependency, uncertainty, and professionalization. Bikhchandani, Hirshleifer, and Welch formalize an informational cascade in which actors follow predecessors regardless of their own signal. Together these cover the audit's institutional and behavioral copying hypotheses; historical source tracing supplies its independent-lineage test.
Attribution caveat: Behavioral economics supplies the sequential-copying micro-model, while sociology provides the broader vendor, standard, professional, procurement, and imitation causes enumerated by the audit.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- DiMaggio and Powell: The Iron Cage Revisited
- Bikhchandani, Hirshleifer, and Welch: A Theory of Fads, Fashion, Custom, and Cultural Change as Informational Cascades
Notes¶
[n1] An information cascade occurs when individuals rationally copy the choices of those before them and stop consulting their own information, so a long line of "agreement" can rest on very few independent judgments — precisely the artifact the copying items on this checklist exist to catch. ↩