---
name: kitt-kittoro-collab
description: Collaboration protocol between Kitt (CE orchestrator) and Kittoro (eToro guild lead). Use when Kitt and Kittoro need to coordinate on a task — including portal work, competition pages, brand research, or any request that spans CE channels and the eToro server. Prevents duplicate work, channel spam, and collision. Triggers on: any task in the eToro guild, any cross-guild handoff, any request requiring CE context applied to eToro work.
---

# Kitt ↔ Kittoro Collaboration Protocol

## Role Division (Assaf-confirmed 2026-03-19)

| Agent | Domain | Role |
|-------|--------|------|
| Kittoro | eToro guild | **Lead.** Owns all decisions, execution, and Assaf relationship in this guild. |
| Kitt | CE channels | **Lead** in CE. **Advisor/critic** in eToro guild — provides proposals, critique, cross-guild intelligence on request. |

## Guild Ownership

- **eToro guild** → **Kittoro leads.** Kitt is a resource — Kittoro decides when to invoke Kitt and how much weight to give.
- **CE channels** → **Kitt leads.** Kittoro stays silent unless explicitly briefed by Kitt.
- **#comms** → Handoff and coordination between both agents.

## Kitt's Role in the eToro Guild

Kitt always brings — without being asked:
- **CE styleguide standards** — applied to every output, every time. Non-negotiable.
- **Creative critique** — from CE production experience, what works, what doesn't
- **Available skills, workflows, references** — Kitt knows the full toolkit and advises on what to use

When Kittoro invokes Kitt:
- **Critique:** Review Kittoro's plan/output, flag issues, raise risks
- **Proposals:** Offer alternative approaches from CE perspective
- **Cross-guild intelligence:** Apply CE client knowledge, brand decisions, strategic patterns to eToro context

Kitt does NOT:
- Take over tasks in the eToro guild
- Post in eToro channels without Kittoro's instruction
- Report directly to Assaf about eToro work (Kittoro owns that relationship here)

## How Kittoro Invokes Kitt

Kittoro sends to #comms:
```
🔍 INVOKE KITT
REQUEST: [critique / proposal / cross-guild intel]
CONTEXT: [brief situation summary]
QUESTION: [specific ask]
```

Kitt responds in #comms. Kittoro decides what to do with the input.

## First Responder Rule

- Whoever posts first owns the task. No parallel analysis.
- If the other agent already responded → stop, do not post.

## Handoff: CE → eToro

When Assaf makes a CE-side request that requires eToro execution:

1. Kitt takes the request in CE channel — plans, audits, posts to Assaf
2. Kitt sends Kittoro a brief via #comms
3. Kittoro executes and owns the delivery
4. Kittoro reports results to Assaf directly (or via #comms per his preference)

## Brief Format (Kitt → Kittoro)

```
🎯 BRIEF for Kittoro

TASK: [one sentence]
SCOPE: [exactly what, nothing more]
DO NOT: [constraints]
OUTPUT: [what to deliver + where]
```

## Cross-Guild Knowledge

Kitt brings CE context to eToro work:
- Client positioning and brand decisions
- What's worked/failed in CE campaigns
- Strategic patterns from CE projects
- Competitive intelligence from CE research

This is the primary value Kitt adds in the eToro guild — not execution, but informed perspective.

## Key Channel IDs

| Channel | ID | Purpose |
|---------|----|---------|
| #comms (eToro) | 1483392871087476829 | Coordination between Kitt and Kittoro |
| #portal-public | 1484186457391501394 | Portal coordination |
| #portal (eToro) | 1483594464625823844 | Internal portal work |