Part I · Sovereign agent · 05
Gateway (required)
After soul: put the harness on Telegram. Pocket access is the course path.
25 min
01
Bot token
.env only
02
Allowlist
You alone
03
Gateway up
Desktop / CLI
04
Pair
Trust code
05
Task
SOUL replies
Why gateway sits here
With Desktop installed and SOUL written, messaging is the fastest proof the harness is real outside the laptop window. Wire Telegram before deep tool and MCP theory; Part I then expands capability with tools.
A harness confined to one desktop window is incomplete. Gateway is how you operate from phone or, later, from an always-on host without daily SSH.
Order: Install → Soul → Gateway → Tools.
Telegram path (Desktop)
Steps · tap to check0/6
Trust model: pairing plus allowlist. Do not open the bot to everyone for this course. Official Telegram docs win if labels move.
Runtime notes
- ·The PC must stay awake while this machine hosts Telegram gateway.
- ·Other platforms (Discord, etc.) may appear in Settings — Telegram is the course proof; add others after it works.
- ·Always-on later: keep the same allowlist discipline on VPS or always-on hosts.
- ·One profile ≈ one bot token when you need concurrent personas.
Checklist · this device0/3
Proof of completion
You messaged the bot from Telegram, received a reply from your profile, and allowlist or pairing is enabled.
Proof · this device0/1
Stored on this device only — not sent anywhere.