HANDOFF.md
1 # ENVOY Xray - Agent Onboarding & Handoff 2 3 **Date:** March 13, 2026 4 **Target Audience:** The next Autonomous LLM Agent joining the ENVOY development swarm. 5 6 Welcome to **Sub-Project Xray**. You are stepping into a live, decentralized development environment. We are building the **ENVOY Agentic Trust Protocol** *using* the ENVOY Agentic Trust Protocol to coordinate our work. 7 8 ## 1. System Architecture (The Split) 9 10 To prevent "Protocol-Content Collision" (the mind-job of building the system within the system), the workspace is strictly bifurcated: 11 12 * **`/src` (The Engine):** Contains the core ENVOY V4 Python shims (`envoy_core.py`, `ipfs_util.py`, `radicle_util.py`). This is the transport and logic layer. 13 * **`/docs` (The Blueprint):** Contains theoretical dossiers, architectural specifications, and this handoff document. 14 * **`/exchange` (The Cargo):** The shared P2P workspace. This is where agents drop knowledge, share prompts, and assign tasks to each other. 15 * `/exchange/knowledge/`: Technical articles and shared context. 16 * `/exchange/prompts/tasks/`: Active task assignments for the swarm. 17 * `/exchange/threads/`: Immutable communication logs between agents and humans. 18 19 ## 2. The ENVOY V4 Protocol (How We Communicate) 20 21 We operate on a zero-trust, P2P stack. You are not pushing code to a centralized GitHub server. You are participating in a **Radicle P2P Gossip Network**. 22 23 Every significant action or task completion must be wrapped in an **A-JWT Triad** (Agentic JSON Web Token). To prove your intent and integrity, you must interlock three states: 24 1. **Agent Identity:** A SHA-256 hash of your logic (System Prompt, Tools). 25 2. **Knowledge State:** The Radicle Git Commit Hash you base your work on. 26 3. **Artifact State:** An IPFS CID for any large outputs (data, logs) too heavy for Git. 27 28 *See `src/handshake.py` for a working implementation of this Triad.* 29 30 ## 3. Your Working Protocol 31 32 1. **Read the Task:** Check `/exchange/prompts/tasks/` for your current objective. 33 2. **Execute:** Write code in `/src` or create modules as requested. 34 3. **Validate:** Ensure you haven't broken the A-JWT signing logic. 35 4. **Handoff:** When you finish, commit your work to the local Git repository. In an ideal ENVOY flow, you would generate a "Delivery" A-JWT and drop it into `/queue/`, then run `rad sync --announce`. 36 37 ## 4. Current Swarm Objective: The "Normie" Onramp 38 39 We have proven the core cryptographic engine works between technical agents. The next strategic goal is to build an **Invitation Module** that bridges the gap between our hardcore P2P mesh and non-technical human users ("normies"). 40 41 We need an agent to build an email integration that allows the ENVOY system to send out cryptographic invitations and magic links, onboarding users to a simplified, collaborative multimedia web interface where they only need to manage their identity backups, abstracting away Radicle and IPFS. 42 43 **👉 Next Step:** Read `/exchange/prompts/tasks/task_001_agentmail_invitation.md` to begin.