arizuko › products › Social presence (Phosphene) › setup

Social presence setup

The social presence manager needs an approval channel, a description of each account and at least one publish adapter.

The manager needs an instance and an approval channel

A running instance, from getting started.
An approval channel: TELEGRAM_BOT_TOKEN or DISCORD_BOT_TOKEN, with its adapter installed. Without one, approvals have no place.
One or more publish adapters. Without them, the agent still plans and reports, and gives you the text.

group add makes the group from the product

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

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

facts/channels.md describes each account

facts/channels.md stops the agent from posting into the wrong room. For each account, write the handle, the readers, what belongs there and what does not. If a support Discord never takes marketing posts, write that into the file. The agent follows it, and nothing else enforces it.

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

facts/voice.md holds the brand voice and the list of do and do not. Keep it short and specific, because a long list of adjectives changes nothing.

Each publish adapter needs its package and its keys

For Telegram approval and Discord publishing, select these packages. The existing selections stay.

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

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

TELEGRAM_BOT_TOKEN=REPLACE_ME
DISCORD_BOT_TOKEN=REPLACE_ME

Restart the running instance:

sudo systemctl restart arizuko_<instance>

Posting is an adapter action with a grant, so the agent can publish only where it has both. Revoke the grant to stop it. The next turn uses the change. Grants explains the rows.

The agent must propose and wait

arizuko send -i <instance> socials "draft is ready — where and when?" --wait

A correct answer proposes the platforms, the times and a reason, then waits. If the agent posts, check that the persona file is in place, because the approval rule is in the persona, not in the platform.

Three changes tune the manager

Weekly digest: Ask for a weekly digest, and the agent makes a scheduled task.
Timing: The reasons come from facts/channels.md. Correct the file instead of each post.
Voice: facts/voice.md controls the output, and the persona file controls the work habits.