Skip to content
AAOE
Draft2 min read

Context Engineering

Purpose

This Standard defines Context Engineering as the engineering discipline responsible for designing and governing the information required for effective collaboration between humans and AI systems.

Context shall be treated as a first-class engineering artifact.


Standard

Engineering teams shall intentionally engineer context.

Context shall be:

  • explicit
  • structured
  • traceable
  • reusable
  • maintainable
  • governed

Context should not rely upon implicit human knowledge.


Principles

Context Engineering shall:

  • minimize ambiguity
  • improve engineering consistency
  • improve AI effectiveness
  • improve human collaboration
  • preserve engineering knowledge
  • support traceability
  • enable reproducibility

Context Sources

Context may include:

  • Specifications
  • Standards
  • ADRs
  • Discoveries
  • Architecture documentation
  • Domain terminology
  • Reference Architectures
  • Case Studies
  • Engineering policies

All context sources should remain versioned.


Context Lifecycle

Context should:

Be Created

Be Validated

Be Used

Be Updated

Be Versioned

Be Archived

Context should evolve under governance.


Traceability

Context should remain traceable to:

  • originating Specifications
  • Discoveries
  • ADRs
  • Case Studies
  • Standards

Changes to context should preserve historical relationships.


Exceptions

Temporary context created during exploratory work may be informal.

Production engineering should rely upon governed context.


Relationship to Discoveries

This Standard operationalizes DISC-0005 — Context Engineering.

The Discovery explains why Context Engineering emerged. This Standard defines how engineering teams apply it.


Relationship to the Operating Model

The Operating Model applies this Standard through:

  • Shared Context
  • Work Orders
  • Architecture Reviews
  • Implementation Reports
  • AI Agent Collaboration

Compliance

Engineering work conforms to this Standard when:

  • Context is intentionally engineered.
  • Context is governed.
  • Context remains traceable.
  • Context evolves through controlled change.

Future Evolution

Future Standards may define:

  • Context Packaging
  • Context Quality Metrics
  • Context Exchange Formats
  • Agent Context Contracts
  • Organizational Context Models