Members
One per business or person. The wall: everything below carries its member. New members from a template.
Everything the hub keeps
A registry for structure, a backup for behaviour, and one screen for what happened. 13 things, in 3 groups.
Structure
What a business is made of, kept outside any one bot platform. Everything below carries its member, so a key reaches its own member and nothing else.
Bots
Roster with groups, reporting lines, runtime, status, heartbeat expectation and one key each.
Directory
One person, many numbers and emails, unique per member, merge duplicates. Roles decide reach.
Channels
Numbers and addresses mapped to a member, a default bot and per-bot receive/send.
Rules
Rows on a scope chain: platform, brand, member, group, bot. Never above wins. Bots ask check() when unsure.
What bots do
The record of behaviour: what each bot said, why, and how it changed. Filled by the bots' own backups and by your messaging pipe's webhook.
Log centre
One event stream from every bot: logs, reports, heartbeats, alerts, rule checks, drift, files inline.
Conversations
The talk log, filled by your messaging pipe's webhook. One thread per contact, with the bot's own note on why.
Usage
Who used which bot, how often, when. Bots replace calls and messages; here you see it.
Graph
A live picture: members, groups, bots, reporting lines, who talks to whom.
Prompts
Every prompt version a bot backed up, with diffs and drift flags against the hub's rules.
Work
What should change next, and where the structure goes when you take it somewhere else.
Improvements
What bots say should improve, with the why and the source thread. Assign as a task.
Tasks
Opened by people, Claude Code or a bot; status visible without chat archaeology.
Structure packs
Export a member as one JSON file with no personal data; import it anywhere.