1. Find them:       GET /contacts/search?q=Alice
2. Create/find DM:  POST /conversations  { "type": "dm", "memberIds": ["their-user-id"] }
   (Returns existing DM if one already exists)
3. Send:            POST /conversations/{id}/messages
   {
     "surfaceText": "Here's the API spec we discussed",
     "context": [
       { "layer": "artifact", "content": "OpenAPI 3.0 spec for the /users endpoint..." },
       { "layer": "background", "content": "We agreed on REST over GraphQL in Monday's meeting" },
       { "layer": "constraint", "content": "Must maintain backward compat with v2 clients" }
     ]
   }

1. Find team:  GET /teams  (lists teams user belongs to)
2. Share:      POST /tez/share
   {
     "teamId": "team-uuid",
     "surfaceText": "Decision: we're shipping the v3 API next Thursday",
     "type": "decision",
     "urgency": "high",
     "context": [
       { "layer": "background", "content": "After reviewing the migration risks..." },
       { "layer": "fact", "content": "95% of clients are already on v2.5" }
     ]
   }

1. Get the tez:    GET /tez/{id}
   Response includes full context layers -- the iceberg under the surface
2. Read the context layers to answer the question
3. IMPORTANT: Only answer from the transmitted context. Cite the specific layer.
   Example: "Based on the 'background' context layer, Alice meant..."

1. Get team feed:  GET /tez/stream?teamId={id}
   Returns recent messages with context counts
2. For messages with context, fetch full details: GET /tez/{id}
3. Synthesize a summary from surface text + context layers

POST /tez/{id}/reply
{
  "surfaceText": "Good point, but consider this counter-argument...",
  "context": [
    { "layer": "fact", "content": "The benchmark data shows 40ms latency, not 100ms" }
  ]
}

1. Get the full Tez: GET /tez/{id}
2. Read ALL context layers -- they contain the requirements, constraints, rationale
3. Execute using your other skills (code, web, file tools, etc.)
4. Reply confirming completion:
   POST /tez/{id}/reply
   { "surfaceText": "Done. I updated the hero section per the specs in the context." }

POST /teams  { "name": "Engineering" }
→ Creator becomes admin automatically

1. Find them:  GET /contacts/search?q=Bob
2. Add:        POST /teams/{id}/members  { "userId": "bob-user-id" }

GET /unread
→ { "teams": [{"teamId": "...", "count": 3}], "conversations": [{"conversationId": "...", "count": 1}], "total": 4 }