InquirySpec - Ontological Boundary: Reality-contact is the maintained relation among signal, situation, artifact, action, and consequence. - Not This: Not certainty, metaphysical possession, or a grand public hook. - Doctrine Dependencies: Observation, Interpretation, Application; recursive source-to-claim synthesis; Accountability Assessment; Design-Based Research.
Working Definition
Reality-contact is the maintained relation among signal, situation, artifact, action, consequence, and repair capacity.
A person or group has reality-contact when its records and decisions remain answerable to observable conditions and to the consequences that follow from action. The phrase does not mean certainty. It does not mean possession of a final view from nowhere. It means the work has not drifted so far into summaries, roles, dashboards, narratives, or model outputs that it can no longer be corrected by the situation it claims to address.
Reality-contact is therefore a discipline of maintained attachment. A signal must remain attached to the conditions under which it was sensed. An interpretation must remain attached to the evidence and uncertainty that shaped it. An action must remain attached to the consequences it produces. A repair must remain possible when those consequences reveal that the prior interpretation was incomplete.
In the Field Guide, this node is deliberately modest. Reality-contact is not a grand public slogan. It is the operational standard behind accountable knowledge work: can the artifact still answer back to the world it came from, and can the group revise its action when the world pushes back?
The Phenomenological Problem
Digital work makes portable artifacts extremely powerful. A dashboard tile, transcript, executive summary, model response, risk label, policy note, or research claim can travel farther and faster than the situation that produced it. That portability is useful. It is also dangerous when the receiving system treats the portable artifact as the whole situation.
The common failure is not theatrical deception. It is systemic gravity. Everyone is busy. The environment rewards speed, compression, and plausible handoff. A number can move through the organization faster than an explanation of how the number was produced. A model answer can move faster than a review of what context the model did or did not receive. A decision note can move faster than the unresolved questions that should have traveled with it.
As that pressure accumulates, the artifact becomes detached. The dashboard becomes a proxy for performance. The summary becomes a proxy for understanding. The record becomes a proxy for accountability. The team may still have information, but the information no longer has enough contact with the conditions, people, and consequences that make it meaningful.
Reality-contact names the discipline that resists that drift. It asks a simple but demanding question: when this artifact is used to justify action, can we still inspect what it observed, how it was interpreted, what action followed, and what consequences came back?
The Engineering Anchor
The first anchor is Observation, Interpretation, Application. Observation receives a context-bound signal. Interpretation asks what that signal can responsibly support. Application commits a move that changes the situation and sends new feedback back into the loop. Reality-contact exists when that loop remains intact.
If observation loses context, the group collects signals that cannot be interpreted well. If interpretation becomes detached from evidence, the group produces stories that cannot be challenged. If application is avoided, the group performs analysis without contact with consequence. If application is rushed, the group acts from reflex rather than situated judgment. Reality-contact requires all three phases to remain distinguishable and connected.
The second anchor is source-to-claim traceability. A claim should be walkable. A competent reviewer should be able to move backward from the claim to the source situation, then forward again through the mechanism by which the claim becomes action. This is why reality-contact is related to research synthesis, audit trails, and reviewable artifacts. The point is not to make every artifact heavy. The point is to keep enough linkage that the claim remains testable.
The third anchor is accountability assessment. Consequences, evidence, and forum must stay separated. A record can preserve evidence, but it does not by itself decide what the evidence means. A forum can interpret consequence, but it needs evidence that has not been flattened beyond repair. Reality-contact depends on both: evidence that remains reviewable and a human forum capable of contextualizing, challenging, and repairing what the evidence appears to show.
This is why Accountable Artifacts matter. An accountable artifact is not merely polished or official-looking. It carries provenance, warrant, uncertainty, responsibility, and correction routes across handoff. Reality-contact is the condition those artifacts are built to preserve.
Boundary Conditions
Reality-contact is this:
- A maintained relation between a signal and the situation that produced it.
- A method standard for keeping artifacts answerable to evidence, interpretation, consequence, and repair.
- A way to distinguish contact-bearing records from portable fragments that only look complete.
- A correction discipline for Situated Response, because situated action must remain revisable after it meets consequence.
- A research discipline for Design-Based Research, because tools and doctrine must change when use exposes a better account of the field.
It is not this:
- Certainty.
- A metaphysical possession claim.
- A branding substitute for careful evidence work.
- A permission structure for surveillance.
- A demand that every participant see every trace at every moment.
The boundary is assessability. An artifact has enough reality-contact when the relevant actors can reconstruct, at the appropriate level of detail, what was observed, how it was interpreted, what action followed, what happened next, and what remains open to repair.
That standard is intentionally phase-bound. Not every draft needs a legal record. Not every comment needs a full audit trail. But consequential work needs enough contact that later review is possible. Without that, the group has activity, but it has lost the correction loop.
Drill Path
Start with Observation, Interpretation, Application when the question is methodological: what was observed, how was it interpreted, and what application followed?
Use Situated Response when the question is practical: did the action fit the actual situation, or did it merely satisfy a role, script, metric, or platform category?
Use Accountable Artifacts when the question is material: what record survives the handoff, and does it preserve provenance, warrant, uncertainty, and correction routes?
Use Design-Based Research when the question is developmental: how should the Field Guide, tool, or doctrine change after contact with actual use?
The working test is compact:
- What signal entered the work, and what context traveled with it?
- What interpretation was made, and what uncertainty remained visible?
- What action followed, and what consequences returned?
- What repair route remains available if the contact shows the artifact was incomplete?