Agent write-back — let AI save its results to iri

At a glance. AI agents (Claude, Cursor, internal bots) save their results back to iri automatically.

Why. Without write-back, every AI run produces output that ends up scattered across tools. With write-back, the result lands in iri and the next run (whether it's the same agent, another agent, or a person) can use it as input.

When you'd use it. When the AI summarized a meeting, drafted a report, ran a code review, or wrote a customer reply. Send those outputs to iri and they accumulate as a real asset.

---

Developer detail

Agents that only read from iri miss the compounding loop. Write-back is how the knowledge graph improves with every task.

Two write paths

Path	Endpoint / tool	When to use
Lightweight note	POST /api/notes · create_note MCP tool	Quick notes, ad-hoc captures
Structured document	POST /api/documents · create_document MCP tool	Anything an agent produces — flows into the atoms pipeline, versioned

Prefer create_document for agent output. It enforces frontmatter that lets iri version by (agent, task) and lineage by inputs / citations.

For team/project work, pass sphere_slug or sphere_id with the document. The output will appear in that sphere and be included in sphere-scoped briefings on the next retrieval.