arizuko › products › Content pipeline (Inari)
Content pipeline (Inari)
Pitch, draft, revise, publish — in your voice, and never without your approval. The approval step is the product.
The persona tells Inari to draft in your voice and wait for approval
The persona file tells Inari to monitor the sources that you configure, propose angles, draft in the voice that facts/style.md records and revise on feedback. It tells Inari to ask for a brief before it drafts and to confirm the target platform before it finishes, because a Bluesky post and a newsletter section are different drafts. The product ships no scheduled task, so the operator adds the task that checks the sources.
The persona tells Inari to publish only after you approve. The platform does not enforce that step. Publishing is an adapter call, so the agent can post wherever the operator installed an adapter and granted the action.
Research drafts cite their sources. The persona tells Inari to remove the citations from final drafts unless your style file asks for them.
A sample exchange
user anything worth writing about this week?
agent Three angles. (1) the SQLite WAL post everyone is reacting to —
contrarian take available. (2) your own migration story, no one
has covered the rollback half. (3) a link roundup, cheap.
Which, and for which platform?
user 2, bluesky thread
agent Brief first: how technical, and do you want the outage named?The product ships three files
| File | What it is |
|---|---|
arizuko.yml | the manifest: name, brand, tagline and env hints |
group/SOUL.md | who the agent is: drafts in your voice and waits for approval; runed renames it to PERSONA.md at the first turn |
facts/style.md | the voice, the tone, the topics in scope and the platform rules |
The product also ships its tests in eval/.
For platform mix and timing, see the social presence manager. A group takes one persona. When two products in one group ship the same group/ file, the package added later wins.