# Operator Communications Onboarding

Status: practical operator onboarding for #166
Related:
- #173 comms unification epic
- #174 Nostur operator edge
- #175 communication authority map

## Why this exists

Alexander wants to get off Telegram and start using the system through channels we own.
This document gives the current real operator path and the near-term target path.

It is intentionally grounded in live world state, not aspiration.

## Current live reality

Today:
- Gitea is the execution truth
- Nostur/Nostr is the only sovereign operator-edge surface actually standing
- Telegram is still the legacy human command surface
- Matrix/Conduit is not yet deployed

Verified live relay path:
- relay backend host: `167.99.126.228:2929`
- operator relay URL: `wss://alexanderwhitestone.com/relay/`
- websocket probe result: `wss://alexanderwhitestone.com/relay/` CONNECTED
- backend HTTP probe on `http://167.99.126.228:2929/` returns `Timmy Foundation NIP-29 Relay. Use a Nostr client to connect.`

Non-target relays:
- `167.99.126.228:7777` is not the current operator onboarding target
- `167.99.126.228:3334` is not the live relay to use for Nostur onboarding right now
- raw `ws://167.99.126.228:2929` is backend truth, not the preferred operator-facing URL when `wss://alexanderwhitestone.com/relay/` is working

## What to use right now

### 1. Nostur = sovereign mobile/operator edge

Use Nostur for:
- quick operator commands
- status reads
- lightweight acknowledgements
- sovereign mobile access

Add this relay in Nostur:
- `wss://alexanderwhitestone.com/relay/`

Working rule:
- Nostur gets you into the system
- Gitea still holds execution truth
- Telegram remains a bridge until Matrix is deployed

### 2. Gitea = task and review truth

Use Gitea for:
- actual tasks
- issues
- PRs
- review state
- visible decisions

If a command from Nostur matters, it must be reflected in Gitea.

### 3. Telegram = legacy bridge

Still usable for now.
Not the future.
Do not treat it as the destination architecture.

## What to do in Nostur now

1. Open Nostur
2. Add relay:
   - `wss://alexanderwhitestone.com/relay/`
3. Confirm the relay connects successfully
4. Verify your logged-in key matches your operator npub
5. Use Nostur as your sovereign mobile edge for operator ingress
6. When work is actionable, make sure it is mirrored into Gitea

## Channel authority, simplified

- Nostur: operator edge / ingress
- Gitea: work truth
- Telegram: temporary bridge
- Matrix: target private operator surface once deployed
- NATS: internal agent bus only

## Near-term target state

### Phase 1 — now
- Nostur working
- Telegram still active as bridge
- Gitea remains truth

### Phase 2 — next
- deploy Matrix/Conduit for private operator-to-fleet conversation
- keep Nostur as sovereign mobile ingress
- route meaningful commands from both surfaces into Gitea

### Phase 3 — cutover
- Telegram demoted fully to legacy or removed
- Matrix becomes the primary private command room
- Nostur remains the sovereign operator edge

## Acceptance for #166

We should consider #166 truly complete only when:
- [ ] Matrix/Conduit is deployed
- [ ] Alexander can message the fleet privately outside Telegram
- [ ] Nostur remains usable as a sovereign ingress layer
- [ ] both Matrix and Nostur feed into one execution truth: Gitea
- [ ] Telegram is no longer the only human command surface

## Operator rule

No matter which surface you use, the work must not scatter.

A command may arrive through Nostur.
A private conversation may continue in Matrix.
But the task itself must live in Gitea.