Glossary
Agent ArchitectureEmerging

Context Packet

A bundled collection of specifications, architectural rules, golden samples, and domain context that agents need to execute tasks.

Definition

A Context Packet is the bundled collection of specifications, architectural rules, golden samples, and domain context that an agent needs to execute a specific task. It is the delivery mechanism that transforms raw organizational knowledge into a focused, task-ready input for agent execution.

A typical Context Packet contains:

  1. Live Spec — the specification with acceptance criteria and edge cases for the target task.
  2. Architectural Rules — the constraints and standards the implementation must follow.
  3. Golden Samples — reference implementations that demonstrate the expected patterns.
  4. Domain Context — links to relevant background information from the Context Index.

Context Packets are typically assembled during weekly Specification Engineering Blocks, where Context Architects prepare the bundles that will be consumed during daily agent execution cycles. This preparation step is critical because the quality of the Context Packet directly determines the quality of the agent's output.

The full lifecycle connects quarterly planning (which defines epics) to weekly specification engineering (which produces Context Packets) to daily execution (which consumes them).

Last updated: 3/11/2026