arizuko › products › Content pipeline (Inari) › setup

Content pipeline setup

The content pipeline needs a Codex key for research, an approval channel and a style file. A publish adapter is optional.

The pipeline needs an instance, a Codex key and a channel

A running instance, from getting started.
CODEX_API_KEY, which the product declares as required. The oracle skill combines several sources. Without it, the agent drafts from one source at a time.
An approval channel, for example Telegram with TELEGRAM_BOT_TOKEN and the Telegram adapter. For publishing, also add a publish adapter.

group add makes the group from the product

arizuko group -i <instance> add telegram:<bot-id>/user/12345678 content -p creator

The command records the product selection for the group in the installed_packages resource. Run arizuko package sync after selecting the adapters below.

The style file comes first

facts/style.md is the core of the product. It ships as an instruction to the operator and not as content, because a generic voice file gives generic drafts. Record formal or casual, first or third person, the topics in scope, the topics out of scope, length and format, and the rules for each platform, for example short Bluesky posts and the thread shape on X.

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/creator/facts /srv/data/arizuko_<instance>/groups/content/

The draft quality follows this one file. If the drafts read as if nobody wrote them, fix this file. The fix is not in the prompt and not in the model.

A publish adapter lets the agent post

For Telegram approval, select catalog:teled. For Slack publishing, also select catalog:slakd. The existing package selections stay.

arizuko package add -i <instance> catalog:teled
arizuko package add -i <instance> catalog:slakd

Add the adapter keys to /srv/data/arizuko_<instance>/.env:

TELEGRAM_BOT_TOKEN=REPLACE_ME
SLACK_BOT_TOKEN=REPLACE_ME
SLACK_SIGNING_SECRET=REPLACE_ME

Restart the running instance:

sudo systemctl restart arizuko_<instance>

Publishing is a normal adapter call, so the agent can post only where you installed an adapter and granted the action. Without an adapter, the agent does not publish, and the drafts come back in the chat.

The agent must ask for a brief

arizuko send -i <instance> content "pitch me three angles on last week's outage" --wait

A correct answer proposes angles and then asks for a brief and a platform. If the agent gives a finished draft without a request, the persona file is not in the folder.

Three changes tune the pipeline

Voice: Edit facts/style.md, not the persona file. The persona controls the work habits, and the style file controls the output.
Approval: The agent waits for approval by default. To remove that, change the persona file. Think carefully before you make this one change.
Work with other products: Blend socials into the same group for distribution. The two personas conflict, so keep one persona and take the facts and rules of the other product.