| name | record-experience |
| description | Persist outcomes to Pluribus after meaningful work. Use after landing a fix, resolving a non-obvious failure, confirming a design decision, or discovering a durable pattern or mistake to avoid. |
Record experience (Pluribus)
After outcomes that should survive the chat:
- Call
record_experience (same ingestion path as legacy mcp_episode_ingest if exposed).
- Summarize what happened, why it mattered, and outcome (success, failure, tradeoff) with concrete detail—not generic filler.
- Include tags and rich situation text so retrieval can find it later.
Do not skip recording because recall_context returned little or nothing—empty recall ≠ skip record.
Qualification and promotion are server-side; your job is honest, signal-rich text—not inventing authority or ranking locally.