Module app_data 

The AppData dictionary: component IDs, the component registry, typed component values, validation, and creation-time synthesis.

fields is the developer-facing view: typed metadata fields and user data read from one committed dictionary snapshot. typed_facade gives protocol code single typed component reads.

Modules

component_id

component_permissions

component_registry

component_source

Single source-of-truth for the per-ComponentId read/encode/apply logic.

components

Concrete Component impls for every well-known XMTP component id. One submodule per family of identically-shaped components (Bytes/String metadata attributes share a module; the heterogeneous Set/Map components each get their own).

creation

App-data dictionary values that are synthesized when a conversation is created.

dm_registry_profile

DM registry profiles (DMS section 2). A profile lists the registry entries outside the application range that a DM holds from its creation. A DM keeps them for life and new installations keep joining it, so a profile is never changed or removed: a change to what a DM creator writes is a new profile, appended to PROFILES. The rows are literal so that a change to the creator path cannot change a profile.

fields

Typed metadata fields: the developer-facing view of a group’s AppData dictionary.

group_root

The group root in a group context’s GROUP_ROOT_KEY component.

migration

Shared types, errors, and encoding helpers for the app-data migration synthesis path.

policy_set

Project the public policy view from the component registry.

protocol_floor

The committed MIN_SUPPORTED_PROTOCOL_VERSION floor check.

registry_table

Static dispatch table for well-known [Component] impls.

typed

Typed dispatch for AppData components.

typed_facade

Typed read facade over an OpenMLS group’s AppData dictionary.

validation