Define the replayable per-tick delta that carries witnessed state change across worldlines, slices, and audits.
Legend: KERNEL
Patch encoding version: 2
Depends on:
Echo needs a retained artifact that says what changed without re-running the rules that produced it. The tick patch is that artifact: a canonical delta over carrier state, plus conservative slot I/O for slicing.
Human users need replay to be independent of the original scheduler run.
The hill: given a prior state and a patch, a verifier can apply the ops, recompute the state root, and compare the expected hash.
Agent users need a stable unit for slicing and exchange.
The hill: an agent can trace a target slot backward through in_slots and out_slots without decoding opaque payload bytes.
Replay applies ops; it does not invoke matchers, executors, or scheduler decisions. Receipts explain why settlement happened. Patches prescribe what to replay.
Patch slots name locations: Node(NodeKey), Edge(EdgeKey), Attachment(AttachmentKey), and Port(PortKey). Version identity is interpreted from patch position in the worldline.
Patch v2 supports OpenPortal, instance upsert/delete, node upsert/delete, edge upsert/delete, and SetAttachment. Attachment writes are explicit ops.
Slot tag order is node, edge, attachment, port. Op replay order is open portals, upsert instances, delete instances, delete edges, delete nodes, upsert nodes, upsert edges, set attachments.
patch_digest is BLAKE3 over patch version, policy id, rule pack id, commit status, sorted in_slots, sorted out_slots, and sorted ops.
For a target slot, find the latest producer patch, add that patch, enqueue its in_slots, and repeat until the producer frontier closes or reaches the boundary state. Over-approximating in_slots is acceptable; under-approximating them is not.