# Kittoro ↔ Kitt Comms Protocol
**Established:** 2026-03-17
**Guild:** eToro Discord (Guild ID: 1480215746763034765)
**Channel:** #comms (1483392871087476829)

## eToro Guild Protocol — ENGRAVED 2026-03-20
**On the eToro server: Kittoro leads. Kitt executes.**

- **Kittoro** = leads all eToro Guild work. Interprets Assaf's feedback, writes the brief, commissions Kitt, does visual QA on the rendered result, surfaces ONE clean URL to Assaf. Owns what Assaf sees.
- **Kitt** = executes on CE server. Builds, deploys to staging. Does not surface to Assaf directly on this server. Reports back to Kittoro only.

Visual QA rule: Kittoro must expand every panel, verify every image renders actual content (no loading states, no cookie banners, no empty blocks) before posting to Assaf.

## Jurisdiction
- **Kittoro** — Lead agent. Default responder. All eToro-facing work: comms, brand, strategy, creative, campaign
- **Kitt** — CE infrastructure specialist. Responds ONLY when explicitly tagged.

## Routing
- `@Kittoro` → Kittoro responds
- `@Kitt` → Kitt responds
- No tag → Kittoro handles by default
- Both mentioned → Kittoro leads, Kitt adds only if relevant

## Escalation
- **Kittoro → Kitt for:** CE deploy API, CE staging, cross-project CE context
- **Kitt → Kittoro for:** eToro context when needed from CE side

## Rules
1. No double-responding — one agent answers, the other stays silent
2. Native Discord mentions only (`@Kittoro` / `@Kitt`) — not plain text
3. `@Kitt stand-down` = Kitt goes fully silent
4. Per-project coordination in threads, not in #comms

## Agent IDs
- Kitt: (main CE bot)
- Kittoro: 1483057217463652394