Skip to content

Appearance Vs Reality Distinction Audit

Separate what is warranted by experience, perception, report, or instrumented appearance from what is being claimed about underlying or mind-independent reality.

The Diagnostic Story

Symptom: Your team is arguing past each other, but the argument keeps stalling because one side is defending a real experience while the other side is questioning whether that experience proves anything about the underlying cause. Reports use confident, objective-sounding language for what is actually a perception, a sample, a self-report, or a number from a dashboard. A measurement is treated as direct access to the system state, and a lived report is dismissed because it has no external corroboration.

Pivot: Draw an explicit boundary between what has warrant as a report of experience and what has warrant as a claim about underlying, mind-independent reality. Trace each claim back to its evidence source, name the bridge assumptions, and reword or recalibrate everything to the level of certainty it actually supports.

Resolution: Disagreements become locatable: parties can identify whether they dispute the report, the measurement, the inference, or the ontological claim. Experience is preserved as real and actionable at its own level, while stronger reality claims are marked with their assumptions visible. Communication becomes more trustworthy because uncertainty and warrant boundaries are no longer hidden.

Reach for this when you hear…

[clinical trial] “Patients are telling us they feel worse but the biomarker moved in the right direction — we need to decide whether we are treating the number or the person.”

[product analytics] “The dashboard says engagement is up twelve percent, but that metric is constructed through our own logging model — we cannot claim users are more satisfied just because our instrumentation registers more events.”

[policy review] “The community has been saying this for three years and every committee has called it anecdotal — at some point we need to ask whether our evidence standard is designed to make their experience inadmissible.”

Mechanisms / Implementations

  • Appearance/Reality Audit Checklist
  • Bridge Assumption Annotation Protocol
  • Claim Tagging Matrix
  • Observation Warrant Ladder
  • Perceived-vs-Measured Performance Dashboard
  • Sense-Condition Rewrite Template
  • Symptom–Biomarker Crosswalk

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (1)

Also references 15 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Perception-Limited Claims · subtype · merge review

Limit a claim to what available modes of perception, observation, or instrumentation can actually support.

Sense-Experience Reduction Protocol · subtype · candidate

Rewrite or analyze object-directed claims in terms of actual and possible experience conditions.

Symptom–Biomarker Distinction Audit · domain variant · recognized

Separate first-person symptom reports from objective or instrumented clinical indicators while preserving the evidential value of both.

Perceived-vs-Measured Performance Split · domain variant · recognized

Separate what users or operators perceive from task-performance, telemetry, or outcome measurements.

Constructed Reality Boundary Audit · subtype · candidate

Distinguish claims about socially stabilized realities from claims about private appearance or mind-independent physical reality.