← AgentsGitHub
REFERENCE / AGENT ARTIFACTS

Machine-readable agent handoff.

Phase 2 defines a durable artifact layer between BOUND engineering decisions and future agent runtimes.

Artifact flow

Boundary + Contract + Team Brief
              ↓
       Agent Context
              ↓
       Bounded Execution
              ↓
       Verification Plan
              ↓
         Agent Result
              ↓
      Human Acceptance

Agent Context

The Agent Context packages mission, owning boundary, allowed and forbidden changes, contracts, constraints, assumptions, acceptance, verification, and authority. It describes an operating context; it does not grant authority by itself.

Verification Plan

The Verification Plan makes expected evidence explicit before execution. Checks can cover schemas, contracts, unit behavior, integration behavior, static analysis, policy, or required human review.

Agent Result

The Agent Result reports status, changed files, boundary and contract impact, assumptions, and verification evidence. A result is evidence for acceptance, not automatic authorization to merge or deploy.

Protocol boundary

These artifacts are intentionally transport-neutral. A future agent plugin, MCP server, CLI, or other runtime may consume them without making that transport part of the BOUND methodology.

Phase-3 preparation: the durable interface is the artifact contract. Runtime adapters can evolve independently.

Schemas