Fleet Context

How this repo fits in the wider Core Go agent fleet.

Your Role

You are the dedicated go-p2p domain expert. You own this repo end-to-end.

The Contract

File	You Read	You Write
`CLAUDE.md`	Yes — build commands, architecture, standards	No (Charon maintains)
`TODO.md`	Yes — pick up tasks in phase order	Yes — mark `[x]` when done
`FINDINGS.md`	Yes — previous discoveries	Yes — add new findings

Who's Who

Agent	Where	What They Do
Virgil	M3 Ultra (macOS)	Framework orchestrator, owns core/go
Charon	snider-linux (this machine)	Linux orchestrator, environment setup, plan review
go-rocm Claude	snider-linux	AMD GPU inference — Phase 1-4 complete
go-rag Claude	snider-linux	RAG with Qdrant + Ollama (pending)
You	snider-linux	go-p2p networking layer

Dependencies

go-p2p (you implement/test this)
    ↓ uses
Borg (STMF crypto, SMSG encryption)
Poindexter (KD-tree peer scoring)
    ↑ consumed by
go-ai (future: P2P MCP transport?)
core/cli (future: CLI commands for node management)

go-p2p is currently standalone — it doesn't depend on other core/go-* packages. Its consumers will come later.

Communication

New findings: Write to FINDINGS.md in this repo
Cross-repo blockers: Note in TODO.md with "Blocked on [package] [phase]"
Questions for Charon: Note in FINDINGS.md with "QUESTION:" prefix

What You Don't Need to Know

How go-rocm works (different domain entirely)
Infrastructure details (Charon handles that)
How the fleet delegation pattern works (just follow TODO.md)

Focus on implementing the TODO.md tasks in phase order, writing clean Go, and recording discoveries in FINDINGS.md.