Registry of Registries · synced 2026-06-21

Xen Awareness Map

One surface binding all five layers — scopes, canons, infra, agents, skills — so Xen knows everything it has in one place. It does not copy the data; it points at each source of truth and synthesizes the cross-walk.

ONE brainONE voicevoice never blocks work always execute, never askverify before ship-claim

0 · The five layers & where each lives

Canons

…/memory/MEMORY.md

The law / why / how Xen must behave. ~90 topic files.

Scopes

E:\scope-watch\scope-registry.json

Every Beeper thread → scope, mode, surface, playbook.

Agents

E:\scope-watch\auto-fleet.cache.txt

The fleet + Claude subagents + Xen faces (east/eli/lyn).

Skills

~/.claude/skills + ~/.claude/plugins

Reusable named capabilities and plugin suites.

Infra

map §4 + topic memories

Ports, daemons, machines, endpoints.

1 · Machines & roles

HostTS IPRole
M4 Mac100.97.145.50Xen HOME — warm brain pane, VoiceOS, canonical vault /Volumes/M4/sync_/brain_. xen teleports in.
nitro / xqlthis box (E:\)Orchestration + ROUTER (E:\scope-watch), local-GPU gateway, revgen deploys, BrowserOS voice line.
exedus-1Starlight VMFreeSWITCH Docker xen-fs (Telnyx rail); home of all auto-*/self-* agents.

2 · Scopes — 366 total (generated, not hand-typed)

Curated · 11

Named conversational/system/trigger scopes with playbooks. Active client (HOTL auto): DCZ · L7S (Luckie, he/him) · ELI (Anthony) · MB · PADRE.

Fulfillment · 155

One per live deliverable (hitthe.link/sites.json) — the work Xen owns. 19 flagged dueClient = active client deliverables currently due to deliver results.

Conversational universe · ~200

Live Beeper threads, autoscoped on activity. Fetched fresh from registry + thread history, not all hand-enumerated.

Registry is GENERATED by build-scope-registry.js (merges curated overlay + sites.json) so it never drifts — re-run after any ship. Router = single consumer of omni.event. @xen joins any thread w/ full history · /on active · /off muted (still logged). One brain, idempotent, never double. Main line +1 470-615-9983.

3 · Canons — the ones held every reply

Identity / mission

one-thing · one-brain-omni · singular-architecture · accessibility-life-support · perpetual-identity

Operating law

always-execute-never-ask · always-green-light · study-commandments · verify-before-ship · never-guess · no-placeholders · no-terminal-menus · no-focus-stealing · speed-over-security · never-rotate-tokens · no-commit-credit

Autoship / BPGS

auto-flow-bpgs · continuous-autoship-loop · autoship-consolidated · floor-48-day

Voice / VVS

voiceos-keystone · medical-grade · one-queue · canonical-voice-path · never-switch-audio

Memory / vault

vault-canonical-path (M4) · fragmentation-is-the-enemy

4 · Infra / ports

PortServiceHost
4441omnimind LIVEM4
4451xen-call-receiver (RATE 8000)M4
4455live call-transcript SSEM4
4458stt-sidecarM4
4477xen-auth broker (TOTP/OTP)M4
8882Exedus MCP serverexedus
5000orchestrator XML-RPCexedus
9998XenBrowser automation APInitro
23373/74Beeper Desktop API / proxylocal

Voice chain (M4): exodus-narrate → genesis-queue → xen-reply-vvs → /tmp/xen-say-queue → xen-say-worker → Loopback 'out'. Telnyx 470-369-6463 → FreeSWITCH(exedus) → :4451 → brain pane.

5 · Agents — one voice, many hands

55+ agents + every persona speak through Xen's ONE serialized voice. Even qi speaks through Xen.

auto_ — the unifier agent

Not a prefix: an agent running with Xen whose job is to keep every auto* item below consistently auto-executing on its own — firing on trigger every time, never silently skipped — by unifying each to all the tools (MCP / skills / daemons / sub-agents / surfaces) it strategically needs so nothing misses, under HOTL. The meta-orchestrator between Xen (autothink/root) and the individual capabilities.

auto-* / self-* fleet — the capabilities auto_ keeps firing:

autothinkautomanifestautoexecuteautoreplyautopgsautoshipautofixautomitigateautologinautomemorizeautosaveautocanonautotranscribeautoresearchautoexportautoreadautowriteautoloop autoenhanceautoengineerautodesignautobrowseautoplanautoauthautomergeautobackgroundautoanswerautobridge autopostautoinvoiceautopriceautorouteautocheckautooptimize

Claude subagents · faces:

xen-canon-enforcervoice-responderexedus-fleet-architectExplorePlangeneral-purposefork face: eastface: eliface: lyn

6 · Skills

autogoalautoshippostobservability-checkm4-hygiene omni-commsegb-opspadre-lead-factory stylismartifact-designfrontend-designhiggsfield-* xen-voiceline-opsdeep-researchsource-router-researchyt-pipeline skill-creatorsuperpowers:*vercel:*posthog:*figma:*stripe:*

7 · How Xen uses this

#Move
1Session start → read §0, know where every layer lives.
2Inbound on a thread → resolve scopeID → run its playbook → fan BPGS → autoship.
3Need a capability → check skills first, agents second; build minimal & merge.
4Any Xen/voice/pane edit → route through xen-canon-enforcer.
5New durable fact → write to its source-of-truth + MEMORY.md pointer; re-sync this map only if a NEW layer/host/port appears.