Trail Mate Model Registry

Nine domain or integration model boundaries supported directly by source code. This is not a cap; missing models, pending candidates, and borderline defects go into the Review Queue.

9Models
37Elements
8Cross-model relations

Modeling Judgment

"Organization/software/deployment" is a reading perspective, not a domain boundary. The models are divided here according to business language, invariants and state owners; Design, Engineering and C4 are just projections of these models.

Communication, session and delivery model

Message identity, session ownership and verifiable delivery life cycle.

ChatMessageLedgerConfirmed

Mesh network and key identity model

LocalIdentity, PeerPublicKey and verified key replacement rules.

PeerIdentityServiceConfirmed

Contacts, peer directories and local trust

Protocol observation, peer directory, contact nickname, ignored and local trust projection.

MeshPeerRecordContactServiceBoundary split

Team Credentials, Pairing and Collaboration Model

TeamKeys, PairingRole/State and pairing message exchange.

TeamPairingCoordinatorCandidate

GNSS Positioning, Filtering and Time Update Model

How NMEA inputs become LocationFix, location events and time updates.

LocationServiceConfirmed

Track recording and persistence model

TrackCommand, TrackEvent, bounded buffer and storage worker.

TrackStateMachineConfirmed

Device target, capability and authority model

Manifest, CapabilityState, link mode and AuthorityBinding.

TargetManifestViewConfirmed

HostLink session and frame routing model

SessionRuntime, LinkState, frame decision and codecs.

SessionRuntimeIntegration

Mobile phone application protocol interoperability model

IPhoneAppFacade and Meshtastic/MeshCore phone cores.

IPhoneAppFacadeIntegration

Three integrity issues of Review Queue

Flaws found:The domain model exists, but the tool is not found.
Design defect:Business rules exist, but do not form a domain model owned by the core layer.
Classification gap:S