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.
What it does
Inari monitors sources, pitches angles, drafts in the voice recorded
in facts/style.md, revises on feedback, and publishes
only when you approve. It asks for a brief before drafting rather
than starting cold, and confirms the target platform before
finishing — a Bluesky post and a newsletter section are not the
same draft.
Research cites its sources; final drafts strip them unless your style file asks for them. That split is deliberate: you need to check the claim, your reader usually does not.
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?What it ships
| File | What it is |
|---|---|
PRODUCT.md | the manifest — name, brand, tagline, env hints |
SOUL.md | who the agent is: drafts in your voice, waits for approval |
facts/style.md | the voice, tone, in-scope topics and platform rules |
Who it is for
Someone who publishes regularly and is the bottleneck on drafting rather than on ideas. If you want distribution and scheduling across several platforms instead of drafting, that is the social presence manager — the two compose: blend both into one group and Inari drafts what Phosphene posts.