Results and Artifacts

A result has three separate questions: did language execution complete, what device evidence was recorded, and what material state was registered? Start with the saved run outcome and inspect its underlying evidence when needed.

One Shot Files

The first-transfer example writes to run-artifacts/quickstart/:

File	Use
result.json	Summary, execution counts, OS status and registered material.
run.json	Runtime events, diagnostics and full language state.
output.json	Protocol return values and report.
plan.json	Compiled plan used for execution.
ast.json, ir.json	Parsed and lowered program representations.
validate.json, typecheck.json	Language validation and type/unit diagnostics.
os.sqlite3	Durable run, attempt, evidence and registration records.
driver/	Plugin artifacts and simulator configuration where produced.

Station state is also saved under the configured station root. Preserve it together with the run database when investigating ownership, consumable usage or uncertain placement.

Read the Outcome

A successful first-transfer result.json includes these fields, among others:

{
  "execution": {
    "completed_steps": 6,
    "diagnostic_count": 0,
    "failed_steps": 0,
    "ok": true,
    "skipped_steps": 0,
    "total_steps": 6
  },
  "os": {
    "body_outcome": "succeeded",
    "mode": "simulation",
    "status": "completed",
    "unresolved_material_effects": []
  }
}

os.run_id identifies the saved run. Container quantities are available in run.json at state.artifacts.material_state.containers. The first-transfer inspection command prints source and destination quantities.

Simulator command evidence records accepted execution in simulation. The recorded quantities are model state, not sensor measurements or measured reaction yields.

Resident Runs

Use runs and status RUN_ID --socket ... for resident results and device-status for recorded station facts. Resident execution is persisted in the host database; do not assume it creates the same per-run JSON directory as foreground run.

device-status is read-only and reports recorded state. Unknown values remain unknown. A successful status query or submission is not a successful experimental run.