Outputs

What Outputs is for

Outputs inventories the exact retained files and bounded event records behind the selected Run Output. Use it to verify what was stored, inspect integrity, open an allowed artifact, or hand the result to a Notebook without losing lineage.

Paths and files are evidence containers. Their roles, schemas, checksums, and reader states define what they mean.

Read the output inventory

Each output identifies:

• user-facing role;
• retained entry or table;
• schema and compatibility state;
• checksum and size when applicable;
• Available, Not applicable, or Blocked status; and
• safe copy, reveal, export, or Notebook actions.

Unreadable or unknown historical schemas remain visible as blocked inventory. Results does not reinterpret them through the current engine or silently delete them.

Inspect execution events

The bounded execution-event reader retains the ordered information needed to explain Strategy and Portfolio decisions, including applicable:

• intent and order lifecycle;
• activation, replacement, cancellation, and rejection;
• fills and partial fills;
• position changes;
• fees, slippage, latency, and queue outcomes;
• Portfolio admission or suppression context; and
• stable sequence, checksum, and temporal-integrity evidence.

Use page controls for large outputs and preserve the Run Output id, offset, and schema with any external note.

Inspect L3 order evidence

For intended L3 order-level replay, Outputs includes bounded reconstruction and hypothetical-order detail such as:

• replay and book epoch identity;
• queue position or orders ahead at arrival;
• queue changes caused by eligible recorded events;
• partial fills and remaining quantity;
• cancel, reset, or gap outcome;
• liquidity-consumption summary; and
• blocker or limitation reason.

This material supports review of the simulated order. It does not expose licensed raw market data unnecessarily or claim exact exchange fills.

Copy, reveal, or open safely

Use the workstation actions instead of constructing a path manually. Reveal remains disabled when an output is missing, unsafe, outside its allowed storage root, or not intended for direct opening.

Copying a path does not certify the file. Verify role, status, schema, and checksum first.

Open in a Notebook

The Notebook handoff binds the exact Run Output and selected output identity. Use it for custom reconciliation, charts, comparisons, or reports while preserving immutable lineage.

Notebook calculations are separate analysis. They do not mutate the Run Output or become built-in Results evidence unless a product owner explicitly defines and validates that contract.

Recover a missing output

• Confirm the Run Output identity and expected retained-detail profile.
• Refresh after the producing job finishes.
• Open Diagnostics for the writing phase and error state.
• Open System & Jobs for the producing job and corrective action.
• Rerun only when the missing output is required and the exact inputs remain available.

A complete Run Output can legitimately omit an optional artifact. A required missing or malformed artifact remains Blocked.