# Aletheia Synantisi Online Handover

**Filename:** `aletheia-synantisi-online-handover.md`  
**Version:** 0.2.0-draft  
**System class:** Aletheia handoff layer  
**Purpose:** Safe public-context handoff between Synantisi Online Rooms,
GoWalkabout, optional Thalia, and optional Aletheia CoWork/knowledge capture.

---

## 1. System intent

This file defines a **bridge**, not a dependency chain.

Synantisi remains responsible for:
- timed presence;
- private profile handling;
- matching;
- consent;
- invitations;
- block/report;
- Introduction and Contact Card gates.

Optional Aletheia-family tools may help with:
- public room/event research;
- activity ideas;
- shared-interest exploration;
- icebreaker drafting;
- developer knowledge capture.

A Synantisi room must continue to work when GoWalkabout, Thalia or ACS are not
available.

---

## 2. Hard boundary

Synantisi is:

- **18+ only**;
- **strictly non-sexual and platonic**;
- for friendship, activities, conversation, shared interests, language exchange,
  community and professional networking;
- **not a dating or sexual-contact service**.

The handoff must never weaken those rules.

`STOP`, `DECLINE`, `BLOCK` and `REPORT` override every optional handoff.

---

## 3. Privacy rule: only public-safe seeds cross the bridge

Never hand off the full private Synantisi profile.

Never hand off:
- telephone number;
- email;
- full legal name;
- exact date of birth;
- exact address or live location;
- employer/school;
- external contact handles;
- hidden acceptance/rejection criteria;
- block/report history;
- private match failures;
- another participant's inferred personality;
- protected/sensitive attributes.

Allowed examples:
- approved shared interests;
- public room title/theme;
- public activity concept;
- public event time;
- user-approved broad personality bands;
- non-sensitive room constraints.

A post-match handoff may use only information that both participants are already
allowed to know.

---

## 4. Components

| Component | Role | Required? |
| --- | --- | --- |
| Synantisi App | Profile, matching, consent, Introduction/Contact Cards | Yes |
| Synantisi Online Room | Timed public/event presence and room matching | Planned |
| GoWalkabout | Bounded creative/research exploration | Optional |
| Thalia | Human-reviewed nonsexual icebreaker after consent | Optional |
| ACS / CoWork knowledge capture | Developer/research retention of public-safe design knowledge | Optional |

No component may silently activate another one.

---

## 4A. Nearby Connections native bridge

For physical Walkabout/nearby mode, Google Nearby Connections is the preferred
first native transport candidate.

It is a **transport adapter**, not an Aletheia prompt feature.

Rules:

- Android/iOS native integration;
- private profile remains local;
- advertise opaque/session information, not readable private profile fields;
- use Nearby's connection acceptance/verification;
- exchange only the minimum Match Card needed by Synantisi;
- let the Nearby SDK choose among Bluetooth/BLE/Wi-Fi transports rather than
  hard-coding "BLE then Wi-Fi Direct";
- preserve Synantisi STOP/DECLINE/BLOCK/REPORT above the transport.

See:

`/apps/synantisi/synantisi-nearby-connections-draft.md`

## 5. Handoff triggers

A handoff may be requested for:

### Room/event design
Examples:
- Saturday House Room mechanics;
- walking-room ideas;
- volunteer/social-room ideas;
- accessible activity ideas;
- moderation research.

### Mutual-match shared-interest exploration
Only after a mutual match and the relevant consent state.

Example:
- approved shared interests: `tuxedo cats`, `house music`;
- request: suggest three safe conversation/activity ideas.

Do **not** research the other participant.

### Developer research
Examples:
- Jitsi capabilities;
- music-streaming/legal questions;
- ephemeral-room design;
- moderation patterns.

Developer capture must remain detached from individual participant data.

---

## 6. Personality signals

Synantisi may eventually use public-domain IPIP/Big-Five-style trait bands as
**soft matching/context signals**.

Allowed handoff form:

```yaml
optional_personality:
  openness: high
  extraversion: moderate
```

Rules:
- broad bands only;
- optional;
- never diagnosis;
- never a sole rejection gate;
- never infer another person's personality from chat/video;
- MBTI/16-type may be stored as an optional self-entered conversational tag,
  not as scientific ground truth.

---

## 7. Handoff bundle

```yaml
aletheia_handoff:
  protocol: synantisi-online-handover
  version: 0.2.0
  origin: synantisi-online-room
  mode: creative | research | mixed | problem-solving

  room_context:
    room_theme: "Saturday House at Home"
    event_public: true

  seeds:
    - "house music"
    - "tuxedo cats"

  constraints:
    adult_only: true
    nonsexual: true
    no_private_identifiers: true
    no_other_person_research: true
    consent_state: none | mutual_match | invitation_accepted

  optional_personality:
    openness: high

  requested_output:
    - concepts
    - researched_facts
    - activity_ideas
    - icebreaker_material
    - uncertainties
```

Do not include durable participant IDs in this portable handoff.

---

## 8. GoWalkabout

Allowed modes:
- `creative`
- `research`
- `mixed`
- `problem-solving`

GoWalkabout remains bounded and must not create an endless autonomous loop.

Its output should preserve provenance:

```yaml
gowalkabout_bundle:
  seeds_supplied: [...]
  associations_generated: [...]
  research_sources: [...]
  useful_discoveries: [...]
  researched_facts: [...]
  uncertainties: [...]
  suggested_receiver: synantisi | thalia | ACS
```

---

## 9. Thalia

Thalia is available only after a mutual match and the required invitation
acceptance.

Input:
- approved shared interests;
- public room theme;
- optional public-safe GoWalkabout ideas.

Example:

```yaml
thalia_icebreaker:
  opener: "Tuxedo-cat summit? Mine has already appointed itself DJ."
  owner_review_required: true
```

Thalia:
- drafts only;
- never sends automatically;
- never sexualises;
- never jokes about age assurance, consent, rejection, stalking, blocking,
  reporting or safety controls;
- never receives hidden match criteria.

---

## 10. ACS / CoWork capture

ACS capture is optional developer/research functionality.

It must never become a diary of who matched whom.

Allowed:

```yaml
acs_capture_request:
  origin: synantisi-online-handover
  epistemic_type: research | design | concept | uncertainty
  retention_rules:
    - public-safe information only
    - no participant identifiers
    - no individual matching outcomes
    - provenance preserved
```

---

## 11. Example: Dance Room

Public room context:

```yaml
room:
  title: "Saturday House at Home"
  duration: "20:00-22:00"
  camera: optional
  microphone: muted_by_default
  general_chat: text_and_reactions
  music: external_public_stream_link
```

Synantisi handles matching.

A video-room provider may handle optional camera/video.

The music service remains external. Synantisi links to the broadcaster/player;
it does not rebroadcast the music.

---

## 12. Example: GoWalkabout

```yaml
room:
  title: "Coate Water Walkabout"
  mode: nearby_or_event
  session_minutes: 60
```

Possible handoff:
- public walking-route ideas;
- coffee-stop ideas;
- accessible-route research;
- conversation prompts around shared interests.

Do not export live participant location.

---

## 13. Guiding principle

**Synantisi handles consent and matching.**  
**GoWalkabout handles bounded exploration.**  
**Thalia handles optional human-reviewed icebreakers.**  
**ACS handles optional public-safe knowledge capture.**  
**Aletheia keeps the handoff and provenance clean.**