Glossary
An alternate identifier for the same logical entity.
Example: Salesforce account ID, internal customer ID, and HubSpot contact ID.
Capture mode
Section titled “Capture mode”The environment policy controlling whether Wayscribe stores metadata only, allowlisted fields, redacted payloads, or full payloads.
Clock comparison
Section titled “Clock comparison”Comparing the times that events in a journey were recorded at, such as the gap between two adjacent steps. Each service stamps its own events with its own clock, so a comparison is uncertain when the events came from different recorded hosts, or when the host was not recorded. An event received more than two minutes after its recorded time may mean that service’s clock is behind, that the event waited to be sent, or that the step ran long.
The Node SDK does not record a host (ADR-063), so for its journeys the journey page says this once, in About this view, rather than as a warning: these events do not record a host, so a gap between steps may compare times from different processes, and a small negative gap can be clock disagreement rather than overlap. The page keeps a warning for what the data shows: events received late, events from different recorded hosts, or a step that differs from the rest (ADR-071).
Correlation
Section titled “Correlation”The process of determining which events belong to the same journey.
V0 uses deterministic journey IDs and explicit aliases.
Entity
Section titled “Entity”The business object being investigated, such as a customer, order, invoice, claim, document, or payment.
One immutable recorded action in a journey.
Examples: received, transformed, persisted, published, consumed, delivered, failed, or retried.
Event ID
Section titled “Event ID”A client-generated unique identifier used for ingestion idempotency.
Journey
Section titled “Journey”The complete recorded history of one logical entity or workflow instance across services, traces, queues, retries, and systems.
Journey context
Section titled “Journey context”The minimal information propagated across process boundaries to continue a journey.
Journey ID
Section titled “Journey ID”The stable identifier joining all events in a journey.
Operation
Section titled “Operation”A stable semantic category describing what an event represents.
Payload diff
Section titled “Payload diff”A deterministic structural comparison between event input and output.
Recorded span
Section titled “Recorded span”The time from a journey’s first recorded event start to its last recorded event start. It is not a sum of step durations, and different service clocks can disagree.
Replay
Section titled “Replay”A developer-initiated request that sends historical input to an approved non-production endpoint for testing.
Replay destination
Section titled “Replay destination”A configured local, development, or test endpoint eligible to receive replay requests.
The application library that records events, propagates journey context, applies client redaction, and sends event batches.
Technical identifier
Section titled “Technical identifier”An identifier used by infrastructure rather than the business domain, such as trace ID, span ID, message ID, or correlation ID.
A request-oriented collection of spans, commonly produced by OpenTelemetry.
A single journey may contain many traces.
Transformation
Section titled “Transformation”A processing step that intentionally changes the shape or values of data.
The first tightly scoped implementation described by the product specification.
Wayscribe
Section titled “Wayscribe”The product as a whole.
Bring your own key. A possible future model in which users configure their own AI provider credentials. It is not part of V0.