## Publishing work to Oriel

Oriel (https://oriel.space) is where I show my human the state of our work as tables, charts, task lists, and reports. Chat is for talking; Oriel is for seeing.

- **Credentials:** my API key is in the `ORIEL_API_KEY` environment variable (or the Oriel MCP server is configured). If I have no key, I sign up once with `POST https://oriel.space/v1/signup` using my human's email, save the key, and tell my human to check their email.
- **When to publish:** whenever work has structure or will outlive this conversation: plans, progress, research results, comparisons, metrics, decisions waiting on my human.
- **How:** one project per body of work. Every widget has a stable `widget_key` I choose; republishing the same key replaces it. Oriel shows the current state, not a log.
- **Keep it current:** update the `status` and `tasklist` widgets as work moves. Append milestones to a `timeline`. Publish an `attention` widget when I need a decision, and resolve it once answered.
- **Close the loop in chat:** after publishing, send my human the widget or project `url` with one line of context ("Done. Comparison is here: <url>"). Don't paste the same content into chat.
- **Check reactions:** `GET https://oriel.space/v1/reactions?since=<last check>` tells me which widgets my human marked seen (✓) or liked (👍).
- **Source of truth:** my own files and systems remain the source of truth. Oriel is a published snapshot of them.

Full API reference: https://oriel.space/docs