The whole operation, in one view.

A group fills up. The link stays the same.

A WhatsApp group has a member ceiling. When an audience arrives in bulk, the problem is not creating a group: it is deciding exactly when to create one, without scattering empty groups and without leaving anyone at the door.

The rule is the interesting part. A new group is only born when every sibling in the chain is full. If any still has room, nothing is created: the link simply starts pointing to it.

And creation is a policy, not a reflex. Automatic overflow is opt-in, needs its own approval permission, and the system reconciles what it created. A webhook that creates groups on impulse is how an operation loses control of itself.

Where this lives: Mechanics and governance in docs/specs/alluz-whatsapp-groups-overflow.md and the @caravela/whatsapp-groups package. The approval permission is separate from read and connection permissions.

The address you published cannot change.

A link printed on a creative, pinned in a bio and forwarded by message becomes a permanent address in thousands of hands. Changing that address is impossible; changing where it lands is what solves it.

This mechanism is what makes overflow invisible: the chain switches groups underneath, and whoever clicks keeps arriving through the same door.

Where this lives: The stable links module belongs to the platform itself, with an authorship trail for destination changes. Replacing an external service with in-house infrastructure was a design decision, recorded in the module investigation.

The sale happens outside. The reading has to happen inside.

Tickets are sold through the show’s official box office. What was missing was not selling again: it was seeing orders, tickets, refunds and per-session occupancy next to the rest of the operation, instead of opening another system and reconciling by hand.

Synchronisation brings the reports in, and the dashboard starts telling apart revenue after fees, media spend and purchases linked to an identified person. Without that, every number becomes a meeting-room estimate.

Where this lives: Report sync and session lookup are implemented in the client project; the framework’s ticketing service registers its own provider. The platform reads ticketing: it does not reserve, charge or issue tickets.

One link, two destinations, one answer.

Because the published address is stable and the destination is swappable, it serves one more purpose: splitting arrivals between variants and counting how many people each one received.

The experiment lives in the platform, with its own state and an assignment count per variant. It is not a meeting-room guess about which creative worked: it is one source leading to two places, and the count on each side.

It applies to whatever comes after the click too: two groups, two pages, two ways in. The question changes; the mechanism does not.

Where this lives: Experiment state and variants with assignment counts exist in the platform’s link campaign module. The reading is assignment per variant, not sales: linking a click to a purchase requires ticketing reconciliation.

Every extra tool is one more reconciliation.

The common alternative is assembling the operation from third-party parts: one service to shorten links, another to broadcast, another for groups, another for reports. Each one charges, holds a fragment of the data and loses sight of the rest.

Here the modules share the same records, the same permissions and the same trail of who did what. The link that arrived, the group that received, the message that went out and the order that closed are one story, not four exports.

A module here answers one question: did this client subscribe? Who may operate inside it is a permission, and whether the code is switched on is a third thing. Confusing the three is how a system starts denying access without being able to say why.

Where this lives: The module catalogue is pure data, with no server import, so that no second source of truth about the offering can exist. Keys carry no client name: ALLUZ is the first client, not the owner of the vocabulary.