Context as management

People managers move context through meetings, updates, nudges, repetition, and judgment calls. Individual operators now do a smaller, sharper version of that for agents.

They package reality so a worker can act without constant interruption. They decide what the system needs to know, what should persist, what should be forgotten, and what should be treated as uncertain.

This is why "just give the agent more context" is lazy advice. Context is not a landfill. It is a management layer.

What useful context includes

Useful context is the minimum set of facts, sources, decisions, constraints, examples, and current-state signals required to make good local decisions.

A context pack should include:

  • Goal: the outcome, not merely the activity;
  • Source paths: the authoritative documents, tickets, notes, dashboards, or transcripts;
  • Recent decisions: what has already been settled and should not be relitigated;
  • Definitions: key terms that would otherwise be interpreted generically;
  • Known traps: previous mistakes, stakeholder sensitivities, duplicate ideas, fragile assumptions;
  • Style or taste bar: examples of what excellent and unacceptable output look like;
  • Non-goals: adjacent tasks that are out of scope;
  • Dependencies: who or what this work depends on;
  • Verification method: how the output will be checked;
  • Staleness note: what may be outdated or uncertain.

The staleness note is not optional. Agents treat old context with a confidence it may not deserve.

Context rot

Context rot is one of the quietest agent-management failures.

It happens when copied briefs carry old assumptions, when trackers say "in progress" after the work has changed shape, when a prior decision survives even though the constraint disappeared, or when an agent inherits a source pack that was correct last week and misleading today.

Rot feels authoritative because it is written down. That is what makes it dangerous.

The operator has two context jobs: add what matters and evict what no longer does.

A context maintenance loop

For recurring work, run a simple loop:

  1. Before work: refresh source paths, current state, and open decisions.
  2. During work: log material assumptions and unresolved questions.
  3. At review: compare output against the brief and mark context gaps.
  4. After decision: update the tracker, memory, or source note with what changed.
  5. Before reuse: delete stale instructions instead of copying the previous brief blindly.

This is how an individual operator avoids becoming the manager of a haunted filing cabinet.

Context pack checklist

Before delegation, ask:

  • What does the worker need to know to make good local decisions?
  • What would be dangerous for the worker to assume?
  • Which source wins if two sources disagree?
  • What context is old, speculative, or politically sensitive?
  • What should persist after the task ends?
  • What should be explicitly discarded?

Agents do not remove the need for management. They move management into context design.