Results
A distributed results board — the dedup backstop for :kuilt-warp.
Backed by an ORMap<TaskId, LWWRegister<Result>>: each task ID maps to a last-writer-wins register holding the task's result. A duplicate execution of the same task (same taskId) is absorbed idempotently: the LWWRegister join picks the result tagged with the highest (timestamp, replicaId), discarding the other. The result map always converges to exactly one result per task.
Merge semantics — why LWW and not MVRegister? Results tolerates duplicate execution (the warp design expects ~5–25% duplication under partition; see docs/warp-foundation.md). The goal is a single converged result per task, not a set of concurrent values. LWW achieves this with zero extra state: both executions produce a result; the one with the higher timestamp wins; the other is silently discarded. For embarrassingly-parallel tasks the discarded result is never wrong — it is a redundant computation on identical input. Callers that cannot tolerate even silent discard should use the Coordinated path (slice B).
Clock responsibility. The timestamp passed to record must be monotonically increasing within a single replica to prevent older writes silently winning. Wall-clock milliseconds are the common case; a logical clock or HLC is safer under skewed clocks.
Immutable: record returns a new instance. merge is the causal join.
Type Parameters
the type used to identify tasks — must be a stable, unique, serializable key.
the result type produced by executing a task.