Here are the data structures with brief descriptions:

Cdes_key_schedule_t
Csafecomm_adapter_config_t	Adapter connection endpoint configuration
Csafecomm_adapter_t	Adapter handle representation
Csafecomm_ale_peer_t	One routed peer: external bearer <-> the A/B endpoint pair
Csafecomm_ale_t	An ALE instance. Caller-allocated, opaque
Csafecomm_cfm_t	A CFM instance. Caller-allocated, opaque
Csafecomm_config_entry_t	One parsed key/value pair
Csafecomm_config_t	A loaded configuration file. Caller-allocated, opaque in use
Csafecomm_er_config_t	Subset-037 profile parameters
Csafecomm_mac_ctx_t	Immutable session-key material for one SaF connection
Csafecomm_protocol_ops_t	SAPI-compatible operations vtable for safe communication channels
Csafecomm_rr_config_t	Subset-098 profile parameters
Csafecomm_saf_config_t	Static configuration for one SaF connection
Csafecomm_saf_conn_t	SaF connection object. Caller-allocated, zero-initialised, opaque in practice — fields are not part of the API contract
Csafecomm_sai_config_t	Static configuration for one SAI connection
Csafecomm_sai_conn_t	SAI connection object, layered over an already-initialised safecomm_saf_conn_t. Caller-allocated, zero-initialised; fields are not part of the API contract
Csafecomm_session_vital_state_t	Vital session state for 2oo2 hot redundancy and active/warm-standby failover
Csafecomm_transport_channel_ctx_t	Caller-owned storage for safecomm_transport_from_channel_service. No dynamic memory (MISRA): the caller allocates this, typically embedded in its own per-link state, the same way it allocates an `rte_channel_service_t`
Csafecomm_transport_t	A consumer-supplied bearer the SaF layer runs over