arizuko › products › Domain researcher (Prometheus) › setup

Domain researcher setup

1. Prerequisites

• A running instance (getting started).
• CODEX_API_KEY — declared required. Synthesis across long documents is the oracle skill’s job; without it the briefings degrade to link lists.
• A delivery channel — TELEGRAM_BOT_TOKEN or DISCORD_BOT_TOKEN.
• Egress for the sources it must read. A default instance is allowlisted, so add the domains or grant the folder open egress before the first briefing (egress and isolation).

2. Seed a group from it

arizuko group <instance> add telegram:group/-100123 research --product strategy

3. Define the domain and the watchlist

facts/domain.md says what the domain is, who the key players are, and what counts as material. facts/watchlist.md says where to look: sources, companies, topics. Both ship as operator instructions rather than content — a researcher with no beat produces a newsletter about nothing.

4. Schedule the briefing

Ask for it in chat — “brief me every Monday at 07:00” — and the agent creates the scheduled task. Products do not ship task files; the row is created through the task tool, so you can list, pause and cancel it like any other.

5. Verify

arizuko send <instance> research "what changed in the domain this week?" --wait

A correct answer marks each item confirmed, inferred or speculative and cites sources inline. An unmarked wall of prose means SOUL.md did not land.

6. Tuning

• Beat — edit facts/watchlist.md. Everything else follows from it.
• Archive — briefings accumulate in facts/reports/. They are inputs to the next one, so keep them.
• Depth — ask for a deep dive on one question; the weekly shape is a default, not a limit.