arizuko › products
products
Products provide instructions, skills and setup for a group. The shapes page describes additional layouts you can assemble.
Each product uses the same six-step pipeline. Its package can supply instructions, skills and tools for the job.
A group can select more than one package with arizuko package add -g. Run arizuko package sync to install the selected packages. The packages reference explains how their files combine.
Each product has an eval/*.toml suite. A suite sends an agent one prompt per case and checks the reply. Run anteval only against a throwaway instance. Ship tests with it explains the cases.
Helpdesk (reference)
Triages inbound support, answers what it can from seeded knowledge, and escalates billing and account questions instead of guessing. It is also the product to read first: the only one shipping one of every file kind a product can have, so the whole shape is visible at once.
intro · setup · build your own
Ships as a template: ant/examples/helpdesk
Supermarket price agent
One folder, one catch-all route, no per-user state. Answers “where’s X cheapest?” for any number of users without changing structure. The minimal end of the spectrum: same code serves 10 or 10,000 users — the limit is concurrent guest slots, not registered users.
No template ships for this one yet — the page describes the shape; you assemble it from the primitives.
Trip planner (May)
State the brief once — May researches, synthesises via oracle, and delivers a day-by-day itinerary. Preferences persist across trips. Mid-point on the spectrum: single-user depth without an org hierarchy.
Ships as a template: arizuko create -i <name> --product trip
Slack team agent
One agent per Slack channel: channel-scoped persona and thread context, per-teammate memory and grants, personal cloud storage, web interface, and usage dashboard. OAuth sign-in links a teammate’s identities across chat and web.
Ships as a template: arizuko create -i <name> --product slack-team
Discord team agent
One agent per Discord guild: channel-scoped persona, per-member memory and grants, personal cloud storage, web interface, and usage dashboard. Use cases include support agents (KB-backed Q&A with citations) and collaborative research (news ingestion, observation tracking, synthesis).
No template ships for this one yet — the page describes the shape; you assemble it from the primitives.
Repo worker (Atlas)
A solo developer’s agent for their own repositories. Reads the diff rather than the description, cites path:line, and acts through its GitHub tools — but merge, force-push and closing someone else’s work are held for you. gitd delivers repo, org and App webhook events to the group. Within one repository, each PR or issue has its own topic. Outbound comments use the token's user identity.
Ships as a template: arizuko create -i <name> --product github
Reality agent (Rhias)
Long-running personal agent. Holds named threads for ongoing situations across weeks; structured reflection on demand; monthly scheduled sweep over diary + threads to surface what changed.
Ships as a template: arizuko create -i <name> --product reality
Company brain
A network of per-team agents with their own inboxes, knowledge bases, and scheduled briefs. Folder tree mirrors the org chart. Intake from Slack, email, and webhooks. The complex end of the spectrum: all six primitives at full depth.
No template ships for this one yet — the page describes the shape; you assemble it from the primitives.
Taxonomy chat (Marble)
A read-only chat over a fixed dataset that ships inside the folder. The agent answers by running jq over bundled JSON — no web-search egress, no per-user state. Runs on a cheap model with trimmed skills. Swap the dataset and the same bot answers over your data.
No template ships for this one yet — the page describes the shape; you assemble it from the primitives.
Support desk (Atlas)
Answers from your facts/ tree and cites the path it answered from. Says “I don’t have that recorded” instead of guessing, and logs the gap. Helpdesk is the reference shape; this is the version for teams whose answers already live in documents.
Ships as a template: arizuko create -i <name> --product support
Personal assistant (Fiu)
Knows you across sessions: writes what is durable into facts/ after each one, reads the diary before answering the next. Never invents details about your life — if it is not recorded, it asks.
Ships as a template: arizuko create -i <name> --product personal
PM agent (Sloth)
The task board is a Markdown file in the group. Updates it on instruction, confirms owner and deadline before writing, flags what is blocked or overdue, and logs decisions with the context that produced them. Executes nothing.
Ships as a template: arizuko create -i <name> --product pm
Content pipeline (Inari)
Pitch, draft, revise, publish — in the voice recorded in facts/style.md, and never without approval. Asks for a brief before drafting and confirms the target platform before finishing.
Ships as a template: arizuko create -i <name> --product creator
Social presence (Phosphene)
Distribution rather than drafting: proposes platform mix and timing with a rationale, cross-posts on approval, watches replies, and reports weekly on what spread and what flopped. Composes with the content pipeline.
Ships as a template: arizuko create -i <name> --product socials
Domain researcher (Prometheus)
Tracks one domain and delivers the same four-section briefing every week, plus deep dives on demand. Every finding is marked confirmed, inferred or speculative and cited inline; the archive is a directory you can grep.
Ships as a template: arizuko create -i <name> --product strategy
CUZK cadastral lookup
Inspect one Czech cadastral property with a controlled browser and a persistent quota ledger.
Install the platform with getting started before you pick a product.