Gather

Operational Event Stream Capture

One ordered log of everything that happened.

Ingests timestamped operational events from any instrumented source — systems, sensors, user actions, channel messages — into an append-only ordered log. Downstream consumers (real-time dashboards, postmortems, analytics, alerting) all read from the same canonical record, so nothing is lost and any point in history is replayable.

Shape

Operational dimensions

No human in loop

Runs without a person in the path.

Continuous

Always running.

Low data gravity

Light state; replaceable any time.

Read-only inbound

Consumes external data; does not write back.

Inputs

Instrumented event sources (system APIs, sensors, webhook endpoints, log agents)
Event schema per source type
Source identifier and timestamp authority config
Backpressure / replay window configuration

Outputs

Append-only ordered event log with source attribution
Subscribable event stream for downstream real-time consumers
Replayable event history (point-in-time reconstruction)
Source health and ingestion lag metrics

Mechanism

Ingests discrete timestamped operational events from instrumented sources (systems, sensors, actor actions, channels) into an append-only event log with ordering, source attribution, and replay.

Why this is a primitive

Cannot be decomposed — the receive-timestamp-attribute-append operation against a continuous event stream is one operation. Distinct from stream-monitoring (no relevance filter — events are captured as-of; filtering is downstream). Distinct from document-intake (events are structured at source, not parsed from artefacts). Distinct from notice-what-worked telemetry-feedback-loops (capture is upstream of any analysis loop — same mechanism whether the consumer is real-time ops, postmortem, or analytics). The append-only log with ordering and provenance is irreducible.

Where it shows up

SaaS platform — captures all user interaction events (clicks, API calls, feature usage) into a canonical event log feeding both real-time dashboards and usage analytics

Smart building operator — ingests sensor events from HVAC, access control, and occupancy sensors into a unified event log for facilities management and postmortem investigation

Contact centre — captures all agent-action events (status changes, call dispositions, escalations) for real-time supervisor dashboards and compliance audit trails

Logistics operator — ingests scan events from warehouse and carrier systems into a single ordered log powering track-and-trace and SLA monitoring

Related primitives

Composes with

Structured Submitter-Side Form Intake →

Alternative to

External Stream Monitoring →