Vocabulary

Journal

Application — the state, transaction catalog, record catalog, and stream catalog one runtime hosts.

Journal — the single ordered history of accepted transactions and records.

Position — the monotonically increasing identity of one journal entry.

Transaction — an entry that changes state and must be understood during replay.

Record — a fact that changes no state and may be skipped by a reader that does not know it.

Principal — the runtime-witnessed author of an entry. Direct guest changes use guest:<id>.

Correlation — the entry family a change belongs to.

Causation — the earlier entry that directly caused another.

Request Key — an idempotency key that makes a retried commit return the original receipt.

Receipt — the position and correlation confirming an accepted entry.

Origin — state before the first journal entry.

Horizon — the oldest position still reconstructable from retained history and snapshots.

Streams

Stream — a high-rate observation path outside the journal. A stream has a stable id, a row type, and a bounded live window.

Window — the in-memory ring of recent rows.

Gap — exact evidence that rows were overwritten or dropped; never silently treated as a complete range.

Seal — the position through which served rows are durable.

Survey — an aggregate over an axis range, optionally served from stored series data beneath the live window.

Aggregate — min, max, mean, sum, count, or percentile p0 through p100.

Work

Job — finite runtime-owned work with attempts, deadline, retry policy, and an answer.

Errand — the trait a job declares by implementing it on a struct whose fields are the job's arguments; attempt borrows &mut self, so state may survive a retry.

Service — resident work supervised until stop or deactivation.

Lane — a named admission budget for finite work.

Scope — one attempt's cancellation, clock, child-task, causation, and runtime access boundary.

Direct Artifacts

Artifact — one directly installed executable sidecar or Wasm guest.

Declaration — inert metadata embedded in an artifact and read without execution: id, artifact semver, description, dependencies, routes and capabilities, and streams.

Sidecar — a supervised native executable. It communicates through gRPC over stdio and is appropriate for native SDKs, drivers, and crash-prone libraries.

Guest — a bounded WebAssembly component. It receives only the capabilities the host offers and the operator grants.

Route — a typed method a tenant answers, whichever facility hosts it: a stable id, a payload, a reply, and the bound one call is held to.

Capability — one host-mediated guest edge such as invoking a transaction or surveying a stream.

Requirement — another artifact id plus semantic-version range. It applies to either artifact kind and never names a route.

Plan — a validated, dependency-first initialization order over inspected artifact declarations.

Activation — the first point artifact code runs. Static inspection and dependency planning happen before it.

Persistence and Evidence

Source — the storage adapter recovery reads from.

Consumer — a durable fold that receives ordered entries after recovery.

Evidence — file-shaped output written as a draft, verified, then named by a journal fact.

Vault — the adapter that stores evidence.