arizuko › products › Social presence (Phosphene) › setup
Social presence setup
1. Prerequisites
- A running instance (getting started).
- An approval channel —
TELEGRAM_BOT_TOKENorDISCORD_BOT_TOKEN. At least one, or approvals have nowhere to happen. - One or more publish adapters. Without any, the agent still plans and still reports — it just hands you the text.
2. Seed a group from it
arizuko group <instance> add telegram:user/12345678 socials --product socials3. Describe the channels
facts/channels.md is what stops it cross-posting into
the wrong room. Per account: the handle, who reads it, what belongs
there, and what does not. A support Discord that never takes
marketing posts should say so in this file — the agent honours
it, and nothing else will.
facts/voice.md carries brand voice and the
do/don’t list. Keep it short and specific; a long file of
adjectives changes nothing.
4. Wire the adapters
BLUESKY_IDENTIFIER=you.bsky.social
BLUESKY_APP_PASSWORD=...
DISCORD_BOT_TOKEN=...Posting is an adapter action bound to a grant, so the agent can only publish where you have both. Revoking the grant is the off switch and it takes effect on the next turn — see grants.
5. Verify
arizuko send <instance> socials "draft is ready — where and when?" --wait
A correct answer proposes a platform mix with timing and a
rationale, then waits. If it posts, check SOUL.md
landed — approval-first is in the persona, not in the
platform.
6. Tuning
- The digest — ask for a weekly one and the agent schedules it as a scheduled task.
- Timing — the rationale comes from
facts/channels.md; correct the file rather than arguing per post. - Voice —
facts/voice.mdfor the output,SOUL.mdfor how it works.