Habitat

In plain words: Reach: Discord server boundary

Designed 2 min read 4 glossary terms 9 connected pages
The short version written for the Snayu team

Defines the first public social place: one private Discord server, one channel, and a minimal-permission bot, and how Discord identity is kept separate from local authority.

Why read it: Read this to understand who may ask Reach what in Discord, and why Discord roles grant no local power.
  1. 1The bot gets only View Channel and Send Messages; non-mention messages are discarded before storage.
  2. 2Unlinked members get guest conversation only; the Security Desk maps enrolled users to real grants.
  3. 3On the VPS-edge setup, relayed identities could be faked, so home treats them as guest only.

Designed Public contract; not deployed.

Words on this page, decoded click one for its card

The original text Underlined words open their plain-English card.

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 VesselEngine Room.

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.

To decide what a member may ask of Reach, distinguish the identity observed by Discord from authority granted locally. A platform subject establishes identity only to the assurance admitted for its adapter/profile. WardSecurity Desk may map an enrolled subject to a Principal and current object grants. An unlinked member instead receives guest conversation, without private records, tools, or effects. Discord roles may narrow visibility, but they cannot create 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 WardSecurity Desk. Neither fluent account use nor tunnel possession repairs that gap.

A place the Lich may return to

Returning to this place involves several kinds of continuity. MirrorPersona Keeper preserves Persona lineage, while Discord and its adapter preserve the place, member, event, session, and delivery state. Each Reach turn keeps only material allowed for its purpose. Avatar may later relate the presentation here to Blockworld or a Spectre Habitat; that relationship does not share ContextBriefing Pack or authority, or create an 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.