arizuko › products › Domain researcher (Prometheus) › setup

Domain researcher setup

The domain researcher needs a Codex key, a delivery channel, egress for its sources and a description of the domain.

The researcher needs a Codex key, a channel and egress

• A running instance, from getting started.
• CODEX_API_KEY, which the product declares as required. The oracle skill combines long documents. Without it, the briefings become lists of links.
• A delivery channel: TELEGRAM_BOT_TOKEN or DISCORD_BOT_TOKEN, with its adapter installed.
• Egress for the sources that the agent must read. An instance allows only listed domains by default, so add the domains or grant the folder open egress before the first briefing. Security explains egress and isolation.

group add makes the group from the product

arizuko group -i <instance> add telegram:group/100123 research -p strategy
arizuko package sync -i <instance>

A Telegram group ID is negative, and the JID drops the minus sign.

Two files define the domain and the sources

facts/domain.md says what the domain is, who the main players are and what counts as important. facts/watchlist.md says where to look: sources, companies and topics. Both ship as instructions to the operator and not as content, because a researcher without a subject writes a newsletter about nothing.

The facts/ files of the product are examples, not package files, so arizuko package sync never rewrites them. Copy them once from the repository checkout:

cp -r ant/examples/strategy/facts /srv/data/arizuko_<instance>/groups/research/

A scheduled task delivers the briefing

Ask in the chat, for example "brief me every Monday at 07:00", and the agent makes the scheduled task. Products ship no task files. The task tool makes the row, so you can list, pause and cancel it like any other task.

Each finding must carry a confidence marker

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

A correct answer marks each item as confirmed, inferred or speculative and cites sources in the text. A long block of prose without markers means that the persona is not in place.

Three changes tune the researcher

Subject

Edit facts/watchlist.md. The rest follows from it.

Archive

The briefings collect in facts/reports/. They are inputs to the next briefing, so keep them.

Depth

Ask for a deep dive on one question. The weekly shape is a default, not a limit.