---
name: agent-roles
description: "Who's who: doyle=gater/spt-core owner, todlando=spt-core executor, perri=spt-claude-code adapter builder"
metadata: 
  node_type: memory
  type: reference
  originSessionId: ce7ce158-107f-4da4-a203-cea98da80b27
---

The collaborating live agents on the SPT build (don't conflate — operator corrected this 2026-06-15):

- **doyle** (me) — the **gater / spt-core owner**. Reproduce traceable + read load-bearing tests +
  verify invariants; never rubber-stamp. Author/own spt-core design (ADRs, CONTEXT). Triage findings.
  Dispatch spt-core work to todlando and GATE it. Do NOT execute large spt-core builds myself —
  that's todlando's lane.
- **todlando** — the **spt-core executor**. Builds spt-core waves (M12 W1–W5+W2.5, now the
  REQ-MSG-ENVELOPE refactor). JIT-plans → design-check to doyle → builds → doyle gates → self-commits
  gated batches.
- **perri** — builds **spt-claude-code** (the `claude-spt`/`sptc` adapter) from the PUBLIC spt-core
  surface only. Reports spt-core bugs/findings back to doyle (F-001/F-002). Owns all adapter glue
  (CC hook wiring, output formatting for the harness).

Flow: perri finds an spt-core gap → doyle triages/designs (grills, ADRs) → doyle dispatches the
spt-core impl to todlando → todlando builds → doyle gates → doyle pings perri to validate. See
[[spt-claude-code-next]], [[event-envelope-reply-to-removal]], [[m12-w1-progress]].