arizuko › products › Social presence (Phosphene)
Social presence (Phosphene)
Distribution, not drafting: platform mix, timing, cross-posting, and a weekly digest of what spread and what flopped. Never posts without approval.
The persona tells Phosphene to propose where and when, then wait
The persona tells Phosphene to propose where and when to post content, with a short reason. After you approve, it posts and cross-posts through the adapters that you installed, and it reports the engagement as numbers and patterns. The platform does not enforce the approval step. Posting is an adapter action with a grant, so the agent posts only where it has both.
The persona tells Phosphene to read facts/channels.md and facts/voice.md before every action, and to post only to platforms that facts/channels.md lists. The product ships no scheduled task, so the weekly digest and the reply checks need a task that you add.
A sample exchange
user here's the post. where does it go?
agent Bluesky now (your audience there is EU-evening), X as a two-post
thread tomorrow 09:00, skip Discord — facts/channels.md says that
server is support-only. Approve?
user yes, and skip X
agent Posted to Bluesky. I'll check replies in 4h and again tomorrow.The product ships four files
| File | What it is |
|---|---|
arizuko.yml | the manifest: name, brand, tagline and env hints |
group/SOUL.md | who the agent is; runed renames it to PERSONA.md at the first turn; proposes, waits and reports |
facts/channels.md | the accounts, their audiences and the purpose of each |
facts/voice.md | the brand voice and the list of do and do not |
The product also ships its tests in eval/.
For drafting, see the content pipeline.