Trust needs a shared reality

Carlos Ocampo · Field Notes D31 · Based on D365-IRL, Day 352 · September 2, 2026

Two people can leave a meeting convinced they reached an agreement and begin executing different things.

One understood that they had to prepare a proposal. The other expected that proposal to have already been sent. Both acted from an interpretation they never made explicit.

This example illustrates a question we revisit from the Day 352 conversation in D365-IRL: what do we need to share to coordinate with trust?

During the session, we addressed Human2Human, truth, evidence, time, synchronization and human sovereignty. At D31, we connect those topics with a practical condition of autonomy: having common reference points for deciding and acting.

Trust allows us to move forward with other people. To sustain that progress, we need to understand what is happening, what was agreed and what changed.

A shared reality is built by making those reference points visible and leaving room to compare them.

What we observed directly. What was reported to us. What we are interpreting. What remains a hypothesis. When the information was updated and who can clarify it.

Sharing information also requires sharing its context and limits.

Consider a sales opportunity marked “confirmed.” For sales, the customer expressed interest. For operations, that word means capacity can now be reserved. For administration, it means sufficient conditions exist to begin the billing process.

The record is the same; its consequences differ.

Agreeing on what each status means allows actions to be coordinated. It also makes it easier to detect an exception before it becomes a commitment someone else will have to resolve.

Time is part of that context. Availability reviewed yesterday may have changed. An authorization may correspond to an earlier version of the proposal. An agreement may remain valid while the conditions for executing it have already changed.

That is why, at D31, we propose that the information needed to act include its date, its owner and the conditions that require its review.

Synchronization consists, in part, of keeping those updates connected with the people who depend on them.

Autonomy requires every participant to be able to recognize when the situation has changed.

Here we find an everyday application of the Human2Human approach: being able to ask, point out a difference and correct an understanding without turning every clarification into a personal conflict.

Saying “this is what I understood” opens a possibility for comparison. Asking “what changed?” allows the decision to be updated. Recognizing “we do not know this yet” prevents an assumption from circulating as fact.

Collaboration with agents introduces the same requirement. An AI-generated summary needs to preserve the relevant distinctions in the material it processes. Whoever uses it must be able to return to the source, review an attribution and correct a conclusion.

The 51/49 rule finds a condition for exercising human sovereignty here: access to comprehensible information and an effective possibility of questioning it.

In TechNúcleo™, we propose connecting that context with responsibilities and execution. HFE™ offers a rhythm for reviewing what happened, what we learned and what needs adjustment before the next move.

This session contributes a question to the story we have been documenting since Caso Cero: how can distributed initiative be sustained while people retain enough context to act together?

The answer requires agreements that can be consulted, information that can be updated and relationships where clarification is part of the work.

Before asking your team to move faster, can you verify that everyone is deciding on the same version of what is happening?

Field note based on the recovered summary of Day 352. The meeting and sales opportunity examples are editorial developments; they do not describe specific cases presented in the session.

© 2026 D31. All rights reserved.