Expand description
Newtype wrappers for the protocol’s identifier fields (RFC §6.1.1).
Identifiers are categorised into two flavours:
- Prefixed ULIDs for runtime-minted identifiers. The on-the-wire form
is
<prefix>_<ULID>; the prefix is asserted on parse. Mixing aSessionIdwith aMessageIdis a compile error. - Free-form opaque strings for ids whose format is determined by the
environment:
TraceIdandSpanId(per OpenTelemetry / Datadog / Honeycomb conventions, §17.1) andIdempotencyKey(client-supplied logical intent key, §6.4).
Structs§
- Artifact
Id - Identifier for an addressable artifact (RFC §16).
- Idempotency
Key - Logical idempotency key supplied by the client for a command intent (RFC §6.4).
- JobId
- Identifier for a durable job (RFC §10).
- LeaseId
- Identifier for a permission lease (RFC §15.5).
- Message
Id - Globally unique envelope identifier (RFC §6.1.1).
- Session
Id - Identifier for an ARCP session (RFC §9).
- SpanId
- Span identifier within a trace (RFC §17.1). Format is environment-defined.
- Stream
Id - Identifier for a stream (RFC §11).
- Subscription
Id - Identifier for an observer subscription (RFC §13).
- TraceId
- Distributed-trace identifier (RFC §17.1). Format is environment-defined.
Enums§
- IdParse
Error - Errors produced when parsing a typed ID from a string.