Async Governance Glossary

The discipline of defining who knows what, who owns what, and what happened since the last person was online — without requiring anyone to ask, infer, or speculate.

Async governance is not async communication. Communication tools transfer information. Governance infrastructure transfers state and accountability. A team can have excellent async communication and still have no governance layer. The difference shows up at the handoff.

The system-level implementation of async governance. The set of protocols, tools, and structures that allow a distributed team to function with continuity — without depending on any individual's availability.

Async governance infrastructure governs three things: what is declared when someone goes offline, who holds authority when the primary owner is unavailable, and how the next person picks up work without needing to ask the previous person a question.

It is not project management. Project management tracks artifacts. Governance infrastructure tracks human context and declared intent.

A structured asynchronous check-in format in which team members post written updates on what they worked on, what they plan to work on, and what is blocking them — without a scheduled meeting.

Async standups replicate the format of a standup meeting without its only functional advantage: real-time clarification. They collect information but do not transfer state. An async standup tells you what someone did. A declared handoff tells you what you need to do next.

The structural mechanism that ensures work advances across timezone boundaries without loss of context, ownership clarity, or decision authority.

A continuity layer is not documentation. Documentation captures the past for future reference. A continuity layer propagates the present — the current state of active work — so that the next person online can act without waiting.

Teams without a continuity layer experience a predictable set of symptoms: blocked PRs waiting for a reviewer who is asleep, decisions delayed until the primary decision-maker comes online, and context that exists only in the memory of the engineer who just went offline.

A structured transfer of working state from one engineer — or one shift — to the next, made explicit before the outgoing person goes offline.

A declared handoff contains: what shipped, what is in progress, what is blocked and why, who owns the next action, and when the originating engineer will return. It is not a summary of what happened. It is an instruction set for what happens next.

The word "declared" is load-bearing. Declarations are explicit, timestamped, and attributable. They do not require the recipient to infer, ask, or guess.

The explicit, published record of an engineer's or team's current working context — available to anyone who needs it, without requiring the originator to be online.

Declared state includes: what the person is working on, what is blocked, what decisions have been made, and what the next person needs to know before touching the work. It is the difference between a team whose continuity depends on who is available and a team whose continuity is built into the system.

The opposite of declared state is ambient awareness — the informal, unstructured, often-invisible knowledge that exists only in the heads of people who happen to be online at the same time.

A predefined structure that establishes who holds decision-making authority for a given area of work when the primary owner is unavailable.

Decision authority mapping eliminates the most common form of distributed team delay: the 24- to 48-hour pause that occurs when a decision is needed but the person who normally makes it is asleep, in deep work, or offline. The map is declared in advance, not constructed reactively when a decision is needed.

A decision authority map answers: who makes this call if I am not available? It is not a delegation — it is a structural commitment built into the governance layer.

A structured end-of-shift declaration made by an engineer before going offline. The wrap declares current state, outstanding blockers, decisions made during the shift, next actions and their owners, and the engineer's expected return.

The wrap is the atomic unit of async governance infrastructure. It is not a status update. A status update describes what happened. A wrap transfers responsibility for what happens next.

A software development model in which engineering work is passed continuously across time zones — each shift picking up where the previous one left off — theoretically enabling 24-hour development cycles.

Follow-the-sun development fails in practice when teams have communication infrastructure but no governance infrastructure. Passing work across time zones requires more than a ticket in Jira and a message in Slack. It requires a declared transfer of state: current progress, open questions, blockers, and decision authority. Without that transfer, each shift loses 30 to 90 minutes reconstructing context before it can move.

The structural layer between communication and coordination in a distributed engineering organization. The governance layer defines what must be declared, when it must be declared, and who holds authority when the primary owner is unavailable.

Most distributed teams have a communication layer (Slack, email, Loom) and a project tracking layer (Jira, Linear, GitHub). Very few have a governance layer. The absence of the governance layer is the structural cause behind most distributed team coordination failures — missed handoffs, duplicated work, blocked decisions, and context that exists only in memory.

The body of information that must be transferred from one engineer or shift to the next for work to continue without interruption. Handoff context includes: current task state, open decisions, blockers, relevant reasoning, and next actions.

Handoff context is not the same as documentation. Documentation captures what was done. Handoff context captures what needs to happen next and what the next person must know before touching the work. Most distributed team failures trace back to handoff context that was lost, assumed, or never declared.

The operating principle that when a declared state does not exist, the correct response is to acknowledge the absence of information — not to infer, synthesize, or guess.

Silence over speculation is the constraint that makes async governance infrastructure trustworthy. AI systems that synthesize answers from partial signals introduce accountability risk: a team might act on an inferred answer that turns out to be wrong. A governance system that refuses to guess — and explicitly says so — forces teams to build the habit of declaration.

The constraint that looks like a limitation is the source of the trust.

The act of passing the current working state of a piece of work from one person to another — explicitly and completely — so that the recipient can act without requiring the originator.

State transfer is the technical term for what a declared handoff achieves. It is distinct from information transfer, which is what async communication achieves. Information transfer tells you what happened. State transfer tells you what to do next, who owns it, and what authority you have to act.

A temporary, explicitly declared form of delegated presence. A time-bounded representative holds decision-making authority for a defined scope during a defined period — typically while the primary owner is offline or in deep work.

Time-bounded representation differs from permanent delegation in that it has an explicit expiry. When the primary owner returns or the declared period ends, authority reverts automatically. It is not inferred from inactivity. It is not triggered by a calendar event. It is declared, scoped, and time-limited.