Reviewed 2026-09-05 against 379064ea2af77a0deed738296da36337448bde94 on main. This is a source review and a proposed delivery plan. A specification describes intended behavior; it does not establish that the behavior already exists. Recorded historical results are not new measurements.
- Repository instructions at the root, then Intent.
- Current code and context, including the verification limits.
- Roadmap to select a dependency-ready work packet.
- Technical specification and the selected work packet.
Existing product goals, ADRs, schemas and task evidence remain authoritative for their domains. These documents make the next work explicit; they do not silently retire an existing decision. Recheck the target branch and open PRs before executing an old packet.
The coordinator hands both roles the same packet ID, base commit, acceptance criteria, permitted files and fixture contract. One implementer owns the code branch. The verifier independently derives failure cases from the specification and records its own observations. When two agents are unavailable, perform separate implementation and verification passes and disclose that independence was unavailable.
The implementer reads the named sources, reproduces the current behavior, changes only the assigned scope and hands over a commit plus commands. The verifier reads the contract before the implementation explanation, tests success and refusal/error paths, inspects the diff and returns pass, changes_requested or blocked against that exact commit. A test that never ran is not_run, never a pass. Do not mark an existing unmet gate complete merely because a packet's preparation is complete.
Use distinct branches/worktrees when executing concurrently. Packets with overlapping owned files run serially unless the coordinator explicitly partitions the edits. The coordinator integrates one reviewed change at a time, reruns the affected integration gate and reconciles status. Tests may add fixtures under their assigned test paths; shared configuration and schema edits have one owner.
packet_id: selected ID
base_commit: exact SHA
implementation_commit: exact SHA
acceptance_results: # one entry for every numbered criterion
- criterion: AC1
outcome: pass | fail | not_run
command: exact command and working directory
evidence: result or repository artifact path
changed_files: []
remaining_risks: []
verifier: independent reviewer identity or independence unavailable
verdict: pass | changes_requested | blockedKeep test data synthetic and generated evidence free of credentials. Work packets authorize their stated code/document scope, not external sends, purchases, model training, production deployment or data migration. Respect the repository's existing authorization boundaries.
Repository-scoped skills are in .agents/skills/swapos-deliver/ and .agents/skills/swapos-verify/. Invoke the applicable skill with a packet ID. If the client does not discover repository skills, open its SKILL.md explicitly; no personal skill installation is required.
ModelSwapper packets retain the original G-goal IDs. Use the branch conventions in AGENTS.md and an ADR for architectural changes. Benchmark tasks, graders and baseline runners remain outside implementation ownership. This documentation prepares quality, latency and hardware measurements; it does not claim a numerical improvement.