← back to AbramsEgo

build-queue/done/53-a2a-protocol-scope.md

24 lines

# AbramsEgo task 53 — SCOPE the real Agent2Agent (A2A) protocol — TK-10132

Steve wants agents to "consult with A2A for best methods." Task 51 used the INTERNAL cabinet
panel. This task SCOPES ONLY the real, external A2A protocol — do NOT install deps, do NOT
open network endpoints, do NOT wire it live. Produce a decision-ready memo.

Research (read-only, prefer local reasoning; ≤$0.25 metered if needed, log to cost-tracker):
- What Google's Agent2Agent (A2A) protocol is: Agent Cards, task/message model, transport,
  discovery, auth. Cite the spec/source URLs you actually read.
- How AbramsEgo could act as an A2A CLIENT so its agents query external A2A-compliant agents
  for "best method" on a decision (e.g. which affiliate/monetization approach) — the minimal
  endpoint + client shape, where it'd hook into the existing /api/chat or a new /api/a2a route.
- Security/gating: A2A means talking to EXTERNAL agents — treat every inbound response as
  untrusted (it can carry prompt-injection). Spell out the sandbox: no auto-execution of
  returned instructions, human/officer gate before acting, no secret exposure. Reference the
  egress-sentinel + the 2026-07-29 stealer lesson.

OUTPUT: write memo to memos/a2a-protocol-scope.md AND a gated go-build copy to
~/.claude/yolo-queue/pending-approval/a2a-protocol-build-TK-10132.md with:
- recommended approach + effort estimate (as future build tasks)
- explicit dependency list (nothing installed yet)
- a vp-abramsego APPROVE/REVISE/BLOCK block
Commit `docs(a2a): scope real Agent2Agent protocol integration (gated, TK-10132)`. Print the memo path.