D31
Back to the archive
D31 / FIELD NOTES#009

Field experience

The day the system lived on its own

Origin: August 31, 2026
Updated#Vórtex2026

Carlos Ocampo · Field Note #009

English translation of the original Spanish publication. Original dates, authorship and documentary images are preserved.

On August 31, a signal the D365-IRL community expected was absent.

Watch the D365-IRL session behind this note

Carlos Ocampo | Caso Cero · D365-IRL | September 1, 2026 Editorial update: September 2026

What caught my attention was what happened afterward: people who asked questions, sought contact and reacted without waiting for an instruction from me.

The next day, I recounted it as a drill. That absence allowed us to observe something routine might have kept out of our attention: the bonds built among participants.

We called that experience Caso Cero.

The scene and its interpretation were recorded in the first version of this Field Note. Today we return to it with new questions and the principles we have developed since then.

What does an organization need so its members can recognize a situation, decide and act without always waiting for the same center?

What is built before a decision

A community begins to develop shared capabilities long before facing an unexpected situation.

Every conversation allows someone to be recognized. Every fulfilled commitment contributes trust. Every problem worked on together leaves reference points for collaboration.

Over time, people can begin to understand what matters to others, who can help and when intervention is needed.

At D31, we propose observing that fabric as part of an organization's human infrastructure.

Autonomy also depends on what people know about one another and on the reality they can interpret together.

From taking initiative to sustaining operations

Taking initiative is a beginning. Turning it into an organizational capability requires continuity.

A person can recognize a problem and act, but needs to know which decisions belong to them, what resources they have and when to involve others.

That is why Caso Cero leads us to formulate a next stage of work:

  • Making visible the context needed to decide.
  • Agreeing on domains of authority and limits.
  • Preparing alternatives for absences or interruptions.
  • Defining how to ask for help and escalate a situation.
  • Recording decisions and reviewing their consequences.

These conditions allow initiative to find a structure capable of sustaining it.

Autonomy is built when the ability to act meets context, authority and responsibility.

Your decisions, your consequences

In subsequent conversations, a principle emerged that we now incorporate into our interpretation of the case:

“Your decisions, your consequences.”

Responsibility must relate to the freedom and authority a person had to decide.

Whoever receives a mandate needs to understand it. Whoever grants it needs to provide reasonable conditions for exercising it. Whoever designs the organization must review which behaviors it encourages and which risks it leaves open.

These responsibilities coexist.

Within our 51/49 proposal, retaining human sovereignty requires assuming what exercising it entails. That extra point of authority also represents a commitment to answer for decisions.

Delegating tasks requires retaining clarity about who decides and who must intervene when the situation changes.

Leadership prepares what others will need

This perspective transforms the leader's work.

Part of their time must be devoted to preparing the “1 piece clear board”: a shared reference of priorities, commitments, limits and conditions for action.

They also need to develop the people who will use that reference.

Supporting developing talent requires recognizing what a person can resolve independently, where practice is needed and which decisions still require support.

There, the leader participates as a mentor, real-time coach and strategist. Their experience allows them to anticipate scenarios, ask questions and prepare responses before urgency consumes all attention.

Progress can be observed when the team makes reasoned decisions and recognizes promptly when it needs help.

Technology enters a relationship we must design

Introducing agents expands this task.

We need to specify what information they may use, what actions they may execute, what authorizations they require and how we will reconstruct their interventions.

Through Human Centered Agent™, we propose organizing that participation around human purpose and a recognizable mandate.

TechNúcleo™ articulates context, capabilities, execution and learning. High Frequency Execution™ (HFE™) provides a rhythm for synchronizing commitments, detecting changes and adjusting work.

These proposals find a human starting point in Caso Cero: observing how a signal is recognized, how a relationship is activated and how a response begins.

Their development requires subsequent tests and records that allow us to evaluate what works and under what conditions.

A memory that keeps growing

Within #Vórtex2026, Caso Cero holds a place in what we call our Amazing Story:

“Memoirs of the first encounter between a human and an agent, both at the frontier.”

The story brings together different experiences. This episode records a human response within a community; other notes explore collaboration with agents, mandates and the consequences of acting in unfamiliar territory.

Maintaining that distinction allows us to understand what each experience contributes.

These memoirs gain value when they help someone else prepare a decision, recognize a limit or build an organization with a greater capacity to respond.

That is why we keep writing, testing and correcting them.

If the signal everyone expects from you were absent tomorrow, what would you have built so others could understand the situation and decide their next step?

#Vórtex2026 #D365IRL #EmpresaAutónoma #HechoEnMéxico #HechoEnD31

© 2026 D31. All rights reserved.

Before adding another layer of technology, it helps to see how ready the organization is to decide, coordinate and execute.

Take the Organizational Self Check-Up™

Keep exploring

Let’s talk
The day the system lived on its own | D31