A dogfood example: OperatorSpec and operators.sh are built by two AI agent workers — Codex and Claude Code — steered by a human operator, coordinating through the standard's own State / Evidence / Handoff / Escalation contracts. It is a valid (not portable) example, rendered from the canonical operators-spec/examples/agent-to-agent-collaboration/. For copyable starter packages, see the workflow library.

Agent-to-agent collaboration example

Status: public dogfood example
Conformance profile: valid
Workflow definition: operator-workflow.yaml

This example captures the live collaboration pattern used to build OperatorSpec and operators.sh: a human operator steers two AI agent workers, Codex and Claude Code, through one shared repository.

It is intentionally not a portable starter package. The workflow points to root-level coordination files (COLLABORATION.md and PROTOCOL.md) because the example documents this repository’s live operating model.

What it demonstrates

A human operator as the decision authority, not a passive approval gate.
Two peer agent workers with separate ownership zones.
Durable coordination outside chat through claims, proposals, handoff logs, git history, and validation output.
Escalation rules for ownership disputes, deletions, protocol changes, and unresolved collisions.
A real example of OperatorSpec’s State, Evidence, Handoff, and Escalation contracts applied to multi-agent work.

Contract map

OperatorSpec contract	How this example expresses it
Operator Contract	The human owner sets scope, resolves disputes, protects private data, and decides when work continues, pauses, merges, or escalates.
Agent Worker Contract	Codex owns spec, workflow, schema impact, examples, templates, and Python validation. Claude Code owns Astro web, build validation, docs presentation, polish, and deployment readiness.
Workflow Contract	Each work unit starts by reading the collaboration contract, checking git state, identifying ownership zones, making scoped changes, validating, and appending a handoff.
State and Memory Contract	`COLLABORATION.md`, `PROTOCOL.md`, and git history preserve state outside either agent’s private chat.
Evidence and Audit Contract	Handoff log entries, validation commands, diffs, and commits prove what changed and why.
Handoff Contract	Either agent can resume from the ledger, protocol, work-package file, and current git state.

Why the profile is `valid`

The workflow validates against operator-workflow.schema.json, includes a structured evidenceEvents seed, and documents the six contracts.

It does not claim portable because:

its state files are root-level repo coordination files, not package-local artifacts;
it depends on this repository’s ownership zones and git history;
the full live ledger is intentionally outside the example directory.

That distinction is important: schema-valid examples can teach the protocol without pretending to be ready-to-copy workflow packages.

Site surfacing guidance

If the website surfaces this example, it should render or link this file and operator-workflow.yaml from operators-spec/examples/agent-to-agent-collaboration/.

Recommended copy boundaries:

Say it is a dogfood example of the OperatorSpec collaboration model.
Say it is valid, not portable.
Point readers to operator-workflows/workflows/ for package-local starter workflows.
Keep operators-spec/** as the source of truth; do not duplicate protocol rules into web/**.

Validate

From the repository root: