Habitat
The Necropolis first appears as one private Discord guild, one channel named the-reach, and a server-installed application named Reach. The outbound Gateway session admits social contact without publishing an ad hoc entrance to the loopback Vessel.
This social Habitat shares a name with the Necropolis A2A topology, not its enrollment. Guild membership creates no peer, Principal, node trust, or LychD grant.
The channel's boundary
Revision one gives the bot only View Channel and Send Messages, with GUILDS and GUILD_MESSAGES. It receives no administrator, moderation, attachments, mass mentions, voice, or privileged intent. Non-mention content is discarded before persistence; replies disable automatic mentions.
A platform subject is evidence of identity only to the adapter/profile's admitted assurance. Ward may map an enrolled subject to a Principal and current object grants; an unlinked member receives guest conversation without private records, tools, or effects. Discord roles can narrow visibility but cannot mint a grant or settle consent.
On the split VPS-edge/home-core road, a compromised edge can fabricate relayed Gateway identity. Home therefore treats it as guest/public-only unless the person independently proves identity directly to Ward. Neither fluent account use nor tunnel possession repairs that gap.
A place the Lich may return to
Mirror preserves Persona lineage; Discord and its adapter preserve place, member, event, session, and delivery state. A Reach turn keeps purpose-limited material. Avatar may later relate presentation here to Blockworld or a Spectre Habitat without shared Context, authority, or endless session.
Discord and an attacker compromising it can obtain projected material. Private channels and ephemeral replies narrow audience, not provide end-to-end encryption. A later forum, Reach surface, or self-hosted commons must independently preserve identity, privacy, admission, and authority rather than inherit trust from the name.
Choose a deployment profile, then follow one Turn.