REFERENCE / ARTIFACTS
Machine-readable BOUND artifacts.
These structures are the proposed foundation for future tooling and agent integration. They are not presented as an existing SDK or API.
Team Brief
mission: owner: boundary: allowed_changes: forbidden_changes: inputs: outputs: dependencies: required_interfaces: contracts: invariants: acceptance: verification: definition_of_done:
Boundary Definition
domain: responsibility: owner: owns: may_decide: exposes: consumes: forbidden_dependencies:
Contract
name: version: provider: consumers: inputs: outputs: errors: timeouts: retries: ordering: concurrency: ownership: compatibility: migration: verification:
Formal schemas
The first schema set is published as JSON Schema Draft 2020-12 documents. They are deliberately marked as proposed: the repository can validate their syntax now, while their normative status remains subject to formal specification and versioning.
Agent execution artifacts
Agent Context, Verification Plan, and Agent Result extend the core artifacts into a bounded execution handoff. They remain proposed and transport-neutral.
Read the Agent Artifact reference →
Next engineering step: formalize schemas, version them, validate them in CI, and only then expose them as stable interfaces to tooling or agents.