Concepts
The vocabulary Suvi uses, and what each term actually means.
Suvi's docs use these terms precisely. Where two terms sound interchangeable and are not, that is called out.
Deployment
Instance. One customer's dedicated deployment: its own box, database, memory and WhatsApp seat.
Business. A company inside an instance. An instance can hold several. Each has its own catalogue, tax defaults and invoice identity.
Branch and warehouse. Locations under a business. Stock lives in a warehouse.
People and access
Actor. The resolved person behind a turn. Tool access, row visibility and cost visibility all hang off it.
Identity binding. Connecting a WhatsApp number or Google email to a Suvi user. Until bound, a number is a stranger.
Role. Owner, admin, member or web-only. Coarse.
Action. A granular capability an admin toggles per person, such as reading mail or seeing inventory cost. This is the control you actually use.
Capability versus permission. A capability is whether the instance can do a thing, decided by whether credentials exist. A permission is whether you may. An unavailable capability hides its tools entirely, so Suvi never offers what it cannot do.
Seat. The plan's user cap. Admins cannot raise it in-product.
Memory
Memory item. The row-level system of record.
Compiled view. The prompt-visible files rendered from memory items. Build artefacts, not editable sources. Editing one is overwritten on the next render.
Entity, relationship, community. The knowledge graph vocabulary. Communities are clusters found in the graph; bridges are entities connecting clusters that otherwise do not touch.
Validity window versus supersession. When a fact was true in the world, versus when Suvi stopped believing it. Different questions, stored separately.
Reflection. The scheduled pass that reviews recent activity and files what mattered, during quiet hours.
Doing things
Session. One long-lived agent per channel. Not the same as a conversation; sessions are reaped when idle.
Tool. A callable action, gated by capability first and permission second.
Workflow versus automation. A workflow is a compiled definition of trigger plus steps. No model runs in its execution loop, so it repeats exactly.
Trigger. Manual, once, cron or event.
Approval gate. The human-in-the-loop step. The broader rule: Suvi drafts, you approve, and it never sends first to a new recipient.
Brief. The twice-daily digest.
Group mode. Active, mention, silent or mining. Controls replying, not listening. Every message is stored regardless.