Relationship infrastructure

Give relationships a shape before asking people to enter them.

Pactloom helps a community define how people find one another, consent, meet, pause and leave—without turning their private relationship into content for a platform.

01JoinScoped identity
02ConnectExplicit consent
03MeetShared rhythm
04Leave wellPause · end · block

The premise

Most platforms organise content.
Pactloom organises consent.

Posts, files and events can live elsewhere. The thing Pactloom keeps coherent is the agreement between people: who may connect, what both accepted, when they meet, and how either person can stop.

Starting patterns

One engine, different human arrangements.

Configure any pattern
022 people

Language exchange

Half your language, half mine.

Formation
suggested
Consent
mutual
Rhythm
recurring
Open pattern
032 people

Accountability pair

Make the next step visible to someone who will ask.

Formation
browse
Consent
mutual
Rhythm
fixed-term
Open pattern
042 people

Mentoring

Experience offered without taking away agency.

Formation
suggested
Consent
mutual
Rhythm
fixed-term
Open pattern
052 people

Random coffee

A small reason to cross an existing boundary.

Formation
random
Consent
automatic
Rhythm
one-off
Open pattern
063–6 people

Study pod

A small circle that notices whether everyone is keeping up.

Formation
assigned
Consent
mutual
Rhythm
fixed-term
Open pattern

Product constitution

The relationship belongs to its participants.

Configuration can change the shape of a programme. It cannot remove the basic dignity of the people inside it.

  1. 01Consent is state, not copy.

    The software records what was accepted and requires fresh consent when the agreement materially changes.

  2. 02Exit is always available.

    Every relationship supports unilateral pause, end, block and personal-data deletion.

  3. 03Privacy follows the relationship.

    Organisers see programme health, not the private substance of meetings.

  4. 04Risk is not a theme colour.

    Sensitive programmes receive stricter defaults; unsafe combinations are rejected rather than politely warned about.

The first thread

CoCo is now a pattern.
What else should people be able to form?

Inspect the CoCo protocol