Bridge Assumption Annotation Protocol¶
Procedure — instantiates Appearance vs. Reality Distinction Audit
Requires analysts to annotate the assumptions used when converting appearances or observations into stronger causal or object-level claims.
Bridge Assumption Annotation Protocol intercepts every place a document moves from an appearance to a stronger reality claim and forces the analyst to write down the bridge — the assumption that would have to hold for the leap to be valid. Its defining move is annotating leaps already taken: it works on inferences that have already been made in prose, dashboards, or reports, dragging their implicit connective tissue into the open. "Sales fell after the rebrand, therefore the rebrand hurt the brand" hides a bridge; the protocol makes the analyst state it, name the entities it assumes exist, and record what warrant that leaves. It travels upward along an existing inference — from the observation to the conclusion someone drew — rather than tabulating claims or building tests from scratch.
Example¶
A brand team's quarterly review contains the line: "revenue dropped 12% after the rebrand, so the new identity is damaging the brand." Run through the protocol, that single sentence sprouts annotations. The bridge assumption is written out: "the rebrand — not some other factor — caused the drop, and 'brand damage' is what a revenue drop indicates." The ontology commitment is named: the claim presupposes that "brand equity" is a real, persisting state that revenue tracks. And the protocol demands the competing bridges be listed too: a price increase shipped the same month, a seasonal dip, and a competitor's promotion could each carry the same "after, therefore because" weight.
With the bridges exposed, the warrant boundary lands honestly: "revenue fell in the quarter after the rebrand (observed); the rebrand as cause is one of several unexcluded explanations (not established)." The review no longer asserts a causal verdict it hasn't earned — and it now has a to-do list, because each named bridge is a hypothesis someone can go test.
How it works¶
- Scan for appearance-to-reality moves. Find each spot where the text steps from something observed or reported to something claimed about causes, objects, or hidden states — usually marked by "so," "therefore," "which shows," "proving."
- Write the bridge. State the assumption that licenses the step, in a sentence, as an assumption rather than a fact.
- List rival bridges. Name the other assumptions that would carry the same observation to a different conclusion.
- Name the ontology it needs. Record the entities or states the claim assumes exist for it to be true as worded.
- Re-state the boundary. Rewrite what the evidence supports once the bridge is visible and un-discharged.
Tuning parameters¶
- Annotation density — every inferential step versus only the load-bearing ones; annotating everything is thorough but exhausting and can bury the decisive bridge.
- Rival-bridge depth — how many competing explanations must be listed; more rivals harden the analysis but risk analysis paralysis.
- Discharge standard — how much evidence lets a bridge be marked "supported" and the claim promoted; a strict standard resists overreach but can stall action.
- Scope of application — applied to a whole report or only to its conclusions; conclusion-only is fast but misses bridges buried in the setup.
- Owner — self-annotation by the author versus an independent reviewer; independence catches motivated bridges the author can't see.
When it helps, and when it misleads¶
Its strength is that it makes the invisible inferential step the object of scrutiny — the exact place where "appears" becomes "is" — and converts a buried assumption into a testable hypothesis. It is the mechanism most directly aimed at the archetype's core slip: the silent upgrade from observation to reality claim.
Its failure mode is that naming bridges can curdle into endless hedging, where every claim is buried under caveats and nothing can be concluded. Its classic misuse is the fallacy it is built to catch — post hoc ergo propter hoc,[n1] the assumption that because a reality claim followed an appearance the appearance established it — left un-annotated so a causal verdict rides in unexamined; the mirror misuse is weaponizing "you never proved causation" to veto any action at all. The guarding discipline is to pair every named bridge with what would discharge it, so the annotation drives inquiry toward a test rather than freezing the decision.
How it implements the components¶
Bridge Assumption Annotation Protocol realizes the audit's inference-exposure machinery — the components that make an implicit leap explicit and bound what it earns:
bridge_assumption_register— its whole output: the written record of each appearance-to-reality assumption and its rivals.ontology_commitment_map— each annotation names the entities or states the upgraded claim presupposes exist.warrant_boundary_statement— once a bridge is exposed and left un-discharged, the protocol re-states what the evidence actually supports.
It works upward from an existing inference; it does not run the opposite direction and turn a claim into the experience_condition_set of tests that would give it content — that's Sense-Condition Rewrite Template — and it neither maintains a general claim_inventory (that's Claim Tagging Matrix) nor holds a phenomenological_report_channel against a measurement_corroboration_plan (that's Symptom–Biomarker Crosswalk).
Related¶
- Instantiates: Appearance vs. Reality Distinction Audit — the protocol targets the audit's central move, the appearance-to-reality bridge.
- Sibling mechanisms: Claim Tagging Matrix · Appearance/Reality Audit Checklist · Observation Warrant Ladder · Symptom–Biomarker Crosswalk · Perceived-vs-Measured Performance Dashboard · Sense-Condition Rewrite Template
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: The mechanism repeatedly scans appearance-to-reality moves, writes the licensing assumption, lists rival bridges, and records required ontology, so its operative form is an annotation procedure.
Nearest alternative: Rule, Policy & Commitment — Analysts may be required to annotate, but the mechanism specifies the ordered work needed to expose each inferential bridge.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Philosophy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Epistemology and philosophy of science distinguish observation from the bridging assumptions that license causal, ontological, or reality-level conclusions.
Related originating lineages:
- Rhetoric — Rhetoric contributes argument, framing, audience, or false-dilemma analysis used here.
Review resolution: Philosophy is the agreed primary lineage because the protocol makes hidden premises, inferential warrants, and scope conditions explicit at a conceptual bridge. Rhetoric supplies argument annotation, while empirical-method traditions help mark evidentiary status; the reusable protocol is a cross-disciplinary Encyclopedia synthesis with universal reach.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Post hoc ergo propter hoc — "after this, therefore because of this" — the fallacy of inferring causation from mere temporal succession. It is the canonical unexamined bridge: the observation that B followed A is real, but the claim that A caused B is a separate assumption that must be stated and tested, not smuggled in by the word "so." ↩