Glossary

Admin console. The operator's web console for members, content, modules and settings. A core component of every deployment.

Available. Status of a capability that runs today in the reference deployment.

Basis points (bps). Hundredths of a percent; 10,000 bps is 100%. Used for remixRevenueShare.originalCreatorShareBps.

Broadcast room. A meeting room that separates a stage of speakers from an audience of listeners, up to broadcast.maxAudience.

Community. One community product with one identity, described by one manifest.

Community server. The core component that owns accounts, identity, community structure and roles, and hosts the module services.

Composition rule. A validation rule about how modules, shared services and platforms fit together, such as module.requires. Runs after the schema pass.

Data stores. The operator-owned relational database, cache, object storage and message queue in every deployment.

Deployment. The components that run in, and belong to, the operator's environment.

Deployment plan. The resolved form of a manifest: modules, owned components, shared services, clients, navigation, privacy statements and diagnostics. Produced by symorva plan and planDeployment().

Developer preview. Status of a capability whose interface is designed and published in these docs and may change before general availability.

Diagnostic. A validation finding with a level (error, warning, info), a stable code, a JSON path and a message.

E2EE (end-to-end encryption). Encryption applied on the sender's device and removed only on authorised recipient devices, so servers in between handle ciphertext. In Symorva it covers chat message content (developer preview); it does not cover metadata or other modules.

Foundation module. A module every community has: chat and meetings.

Grant. A member's explicit, revocable permission for the AI assistant to read a specific conversation or selected messages, given from the member's own device.

Headless core. The shared, UI-free layer of the client that owns product state and rules; native SwiftUI and Compose interfaces render on top of it.

Large-group mode. Behaviour for chat groups above 500 members in the reference deployment: no group read receipts, typing indicators or per-join notices, and offline push only for mentions.

Large-room mode. Behaviour for broadcast rooms with audiences above 500: the stage stays on real-time media and listeners receive a low-latency stream.

Listener. A broadcast-room participant without publishing rights.

Managed mode. deployment.mode: "managed" — the Symorva team runs the deployment on the operator's behalf. Data remains the operator's.

Manifest. symorva.config.json, the single source of truth for a community.

Member. A person with an account in a community.

Metered unit. A unit of shared-service usage recorded against a community, such as participant-minutes or ai-tokens.

Module. A unit of capability with a fixed contract: member capabilities, an owned component, shared services used, metered units and a privacy scope.

Operator. The organisation that owns and runs a community: a community, DAO, creator, independent team or one-person company.

OPC. One-person company.

Optional module. A module enabled per community: AI & creator studio, wallet, DApps, creator economy.

Outbox. A table of events written in the same transaction as the change that caused them and delivered asynchronously, so no event is lost between a write and its notification.

Owned component. A server-side component that runs in the operator's environment, such as messaging-service.

Planned. Status of a capability on the roadmap with no runtime yet.

Platform target. A client the community ships to: ios, android-apk, macos or windows.

Provider adapter. The client layer that translates transport, messaging-core and operating-system types into product interfaces.

Reference deployment. The live consumer IM application whose stack Symorva generalises.

Self-hosted mode. deployment.mode: "self-hosted" — the operator runs the infrastructure.

Shared service. A Symorva service communities connect to rather than run: real-time media, AI inference and generation, metering and settlement.

Stage. The hosts, co-moderators and speakers of a broadcast room, who hold publishing credentials.

Streaming edge. The low-latency distribution layer that delivers large-room streams to listeners.

TEE (trusted execution environment). Isolated hardware-backed execution in which code and data are protected from the rest of the system. Wallet modules integrate it for protected key operations; this is module design in developer preview.

Template. A starter manifest: dao, creator, team or ecosystem.

Tribe. A community sub-space above groups, with its own channels. Enabled by chat.tribes; in developer preview.