Why Information Is Not Enough
A team can have the dashboard, the transcript, the score, the policy field, and the timestamp, and still not know what happened.
Guided essays
Read the Field Guide in order.
Season 1
Season 1: Signals Need Context
The opening arc: why information alone cannot carry the situation that made it meaningful.
The Transductive Boundary
Digital life is not defined by screens. It is defined by how often ordinary human situations must cross a digital "signal" to be recorded, remembered, shared, judged, or acted on.
When Context Gets Flattened
The first failure is rarely dramatic. A number appears in a dashboard. A sentence lands in a status report. A comment is lifted from a meeting and pasted into a planning document. A model produces a summary that is...
Season 2
Season 2: Boundaries, Systems, and Repair
How models, social systems, and feedback loops should be bounded before they are acted on.
Models That Know Their Limits
Season 1 ended with a problem: modern systems move artifacts faster than they preserve the conditions for interpretation. A metric travels without the work ecology that produced it. A summary travels without the...
Reading the Shape of a Social System
A social system is easier to read when it is under load.
The Trolley Problem Alibi
The trolley problem is useful because it is clean. A track. A lever. A forced choice. A small number of lives on one side, another number on the other. The person in the thought experiment is trapped inside a designed...
When the Entity Is Not a Person
When something goes wrong, the first question is usually "Who did it?" That question has value. People make choices. People carry obligations. People can explain, apologize, escalate, repair, refuse, or repeat. A Field...
Reality Feedback as a Method
An organization can say it listens. A team can say it learns. A platform can say it is accountable. A policy can say it protects people. A model can say it is aligned with a purpose. None of those statements are...
Season 3
Season 3: Memory, Authority, and Continuity
How persistent context helps records remain useful without pretending retrieval is wisdom.
From Noise to Continuity
Every organization eventually develops an archive. It may not call it that. It may call it a project drive, a dashboard, a CRM, a ticket queue, a learning platform, a transcript library, a data warehouse, a chat...
Memory Is Not Wisdom
The previous step in this season moved from noise to continuity. That matters. A group that cannot preserve context will keep paying the same coordination tax: repeated explanations, brittle handoffs, disputed...
Keeping Context Attached
A working group does not only need memory. It needs memory that can move without losing its boundaries.
Retrieval Is Not Authority
The most dangerous artifact in a knowledge system is often the one that is easiest to find.
Coordinating Action Across the Divide
Draft scaffold awaiting expansion in the Field Guide workflow.
Season 4
Season 4: Agency Without the Monolith
How work is scaffolded across people, tools, roles, and institutions.
Season 5
Season 5: Accountable Public Artifacts as Method
How public artifacts, agency, and reflexive research practice become part of the engine.
Escaping the Apparatus
Draft scaffold awaiting expansion in the Field Guide workflow.
Accountable Artifacts for Human Groups
Draft scaffold awaiting expansion in the Field Guide workflow.
Augmented Agency
Draft scaffold awaiting expansion in the Field Guide workflow.
The Engine That Builds Itself
Draft scaffold awaiting expansion in the Field Guide workflow.