NL · EN
  manuals / Support

Support

The human side of SWARP: where the other services measure and give structure, this is the place where people find and support each other.

documentation in four layers · support.swarp.nl · Leiden, 12 Sept 2026

This is not a flat manual but documentation in four layers, for four readers: whoever uses it, whoever wants to grasp the idea, whoever builds it, and whoever wants to go further. Each layer carries a label saying how long it lasts.

enduringOutlives a rebuild — the idea, the model, the choices.
tracks the codeDescribes how it is built right now — routes, screens. This can age.

Layer 1 — for the user1What you do with it tracks the code

Support gives you four ways to find and carry people:

  • The forum — join discussions, per scale (national, municipality, district). Every contribution passes a moderator; after a few contributions "Socrates" asks one deepening question.
  • Network — form connections with other members through request-and-accept.
  • Messages — one-to-one conversations, private, outside the forum.
  • Meetings — a live meeting with several people.

Logging in works with a magic link by email — no password — and one account holds across the whole family (Support, Living Environment, Extended). Support also carries the parent↔child core with which SWARP began: the Blueprint, SwarpKids, career choice, family and compatibility (one-time purchase; free in the current test phase).

Layer 2 — for the thinker2The idea & the philosophy enduring

Support is the place for the people. Weather measures the outer weather, Living Environment draws the map, the MAZE carries the memory — Support is where people speak to, find and carry one another.

The family idea is that a support group can be read as a circle: its shared memory is the forum, and in time its book is the MAZE-Bank. The moderator and Socrates are not surveillance but care for the conversation — one keeps the tone safe, the other keeps the conversation open by asking rather than judging.

One thing belongs here honestly, because this is the enduring layer and it must not promise more than exists: the link between a care circle and the bank as its ledger is now a direction, not a built unit. The next layer describes what actually runs.

Layer 3 — for the builder3How it works — the shared forum & API

The shared forum enduring

The forum is the shared memory of the family: the same discussions are visible in Support, Living Environment and Extended. Other services read the forum directly, but always write through Support, because three things that guard the forum live there:

The moderator

An AI moderator reads every contribution before it is posted. In doubt it is mild (fail-open), so a conversation is not wrongly stalled.

Socrates

After a few contributions, one deepening question — at most once per hour per thread. Not an opinion, but a question.

The notifications

When something happens in your thread, an email (at most once per hour per thread).

The API tracks the code

get /api/forum/discussions
The discussions, optionally filtered by scale and area.
post /api/forum/discussions/:id/posts
Post a contribution (goes past the moderator).
post /api/forum/plaats-namens
Server-to-server: a sister service posts on behalf of a service user, with a shared secret.
ws /ws/meeting
The live connection for a meeting.

Support carries more than the forum (network, messages, payments, the family core); these are the load-bearing forum routes and the "on-behalf-of" gate the family writes through.