Online production and transaction output
Record consumes authorized state, events, control, and media. It does not block the physics authority thread for expensive encoding or read private backend buffers. Channels carry run, generation, tick/time, and required calibration facts.
Atomic outputs. Outputs are written to staging, validated, then published atomically. Failure, cancellation, or storage errors must not leave an apparently complete result directory. Final status reports channels that succeeded, failed, or were omitted.
Replay participation. Replay reads sealed inputs and acts through controlled state restoration or control submission. It remains subject to lifecycle, generation, target discovery, and arbitration rather than bypassing Runtime through a native backend API.
Output discovery
Core CLI offers bounded discovery, inspection, opening, and cleanup under a trusted output root. Cleanup never expands to a project root or user directory.
Offline viewers and exporters read immutable artifacts. A visualization or conversion failure does not change the original FSR, and conversions record source digests, tool versions, mappings, and reopen validation.
See CLI and outputs, Official plugins, and Examples and tutorials.
Online and offline lifecycle
Online paths obey real-time budgets, generation identity, bounded queues, and Run finalization. Offline readers operate on sealed files and may retry, parallelize, or recompute. Codecs, format conversion, and training export do not belong in a physics callback.
Record is an authorized data consumer rather than a control owner. It writes through a private staging lease, closes the exact writer, exposes a bounded readback lease to validation, confirms the receipt, and only then commits an atomic FSR. Structural and SHA-256 integrity modes both retain the lease, structure, inode, size, synchronization, and no-overwrite gates.
Stop creates a terminal semantic cut. Required channels inside that cut must be consumed and finalizers must report before the Run can claim a completed output. A crash, full disk, or failed validator cannot rename staging into a plausible final artifact.
Replay remains an online controlled participant: it maps sealed input into current identities, generations, targets, and authority. Offline viewers and exporters never mutate the source FSR; every derivative records source digest, tool/format version, mapping, and reopen validation.