# Hubs

> Source: https://whisperer.one/llms/hubs.md · Whisperer machine-readable layer.
> Product overview: https://whisperer.one/llms/product.md · Full corpus: https://whisperer.one/llms-full.txt

A hub is the place a body of work lives — a client, a project, a hiring round, a release.
It exists so that what a meeting produces has an address.

## The problem it solves

Without hubs, a task created from a meeting suggestion has nowhere specific to go: the system
picks the first tracker project it finds, because it has nothing better to choose with. Work
turns into a pile of meetings, tasks and files with no organising principle above them.

## What a hub holds

The hub itself — its name, the kind of work, the tracker board it files work to, and its link
to an organisation in the context graph. Which meetings have been routed to it, and by which
signal, so the decision can be challenged. And the corrections a person has made, so the same
question is not asked three times.

A hub keeps links and an address; the content stays in the domains that own it — meetings
with meetings, tasks with the tracker, files with storage.

## How a meeting finds its hub

A ladder of signals, strongest first:

1. **What the person said** — final, and remembered as a rule.
2. **A calendar series** — the strongest automatic signal. A weekly rollout sync and a one-off
   partnership call are unambiguously different even with identical attendees.
3. **The meeting title** — this is what catches an internal review about a client.
4. **A live thread** — an obligation already living in a hub came up on the call.
5. **Named things** — a product, a document, a contract the hub knows.
6. **The organisation** — corporate mail domains only; public ones are excluded.
7. **Participants** — they confirm a guess but never create one.

A strong signal overrides a weak one, and several weak signals never combine into a strong
one. Routing by participants alone is wrong in three everyday cases: the same people run two
different pieces of work, an internal discussion about a client happens without the client,
and several clients on public mail domains collapse into one.

## Invariants

- **Not sure means not routed.** Indistinguishable candidates produce a question, not a best
  guess. A wrong address is worse than none: the task quietly lands in someone else's work and
  is discovered a week later.
- **A hub is never created automatically.** The system may propose one; the person names it.
- **The decision is explainable.** The signal and the confidence are stored with the address.
- **No deletion, only archiving.** A hub holds a history of negotiations and promises.
- **An empty address is a legal state.** With no board chosen, a suggestion declines honestly
  rather than filing work somewhere arbitrary.

## What a hub shows

Not "what happened" but what is missing: obligations coming due, decisions still open, work
with no owner.