Tribe, shared team memory
One attested, governed memory store your whole team writes to, per seat.
A Tribe is one shared memory store that many seats write to. Instead of every teammate and agent keeping a private silo, the whole team reads and writes one attested canon, under the same governed write path as everything else in Hunta Gather.
How it works
-
One shared tenant. Creating a Tribe mints a fresh shared store. Your personal store stays yours; your console switches to the team store while you hold a seat.
-
Seats with roles. Every member gets a seat with a role that maps to real backend scopes, enforced server-side:
Role Can Owner full control: invite, manage seats, curate, write Member contribute through the governed capture path, and read Viewer read only -
Every write is governed. No seat writes canon by fiat. Member contributions pass the same screen and judge gate as any capture, and land as attributable sealed facts.
-
One attestation covers every seat. The shared store carries the same signed isolation proof as a personal store, visible to every member. Any seat can verify it offline.
Create and invite
Self-serve, in the console:
- Open Tribe and create your Tribe (you become the owner).
- Invite teammates by email and pick their role. They get a join link; a seat is added when they accept.
- Manage the roster from the same page: suspend, reactivate, or remove seats. Suspending or removing a seat revokes its access.
Pricing
Hunta Tribe is $25 per seat per month, with token overage metered pay-as-you-go. Solo stays free for one seat. Estate (self-host, SSO, SLA) is custom. See hunta.ai pricing for the full tiers.