avz://manual — what is averizos
A chatbot answers questions. An operating system runs your day. Here is what that difference means in practice.
001 / crew
Most assistants are one generalist doing everything averagely. Averiz runs a crew — a scheduler, a researcher, a writer, a builder — each tuned for its lane. You set the goal; they split the work and hand off between themselves.
002 / memory
The crew shares one memory store that survives across conversations, reboots, and weeks away. It is inspectable and editable — open it up, correct it, or clear it. Your context compounds instead of evaporating.
003 / voice
Push-to-talk when your hands are busy, keyboard when you need precision. Both routes hit the same crew and the same memory, so nothing gets lost switching between them.
004 / yours
Name your agents, pick their voices, set their standing instructions. Give the researcher a skeptical streak and the writer your style guide. The OS adapts to you, not the other way around.
005 / connected
Calendar, mail, files, code, music — the crew works across the tools you already use rather than asking you to move into a new one. The integration catalog grows every release.
006 / private
Memory lives in a local-first store. Export it or delete it any time, and nothing you do trains anyone else's model. An operating system should answer to its owner.