Guide

Static binding traces and saved source

A trace lets you step through how a program's bindings depend on each other, with the source it was built from, without running it.

Code & run Run the pipeline’s validator

For finer questions, use the Explorer guide.

Navigate the complete loaded program

Five source packages in the Explorer target

  • types.bosatsu: Record, ValidationResult
  • ingest.bosatsu: IO reads from database
  • transform.bosatsu: Pure data transforms
  • validate.bosatsu: State-dependent and constant validation paths
  • pipeline.bosatsu: Orchestrator

Static questions to run in Explorer

  • IO ingest and pipeline have real IO operations
  • pure transform is fully pure, with no IO
  • signal inspect the constant hardcoded_pass path

What the trace establishes

Binding dependencies

Static references between bindings, not an execution order.

Explicit value origins

static-literal is a compiler-known constant; not-evaluated means no value is available.

Saved source snapshots

The source the trace was built from, unchanged by later edits.

Ask your agent about anything here; it has the detail.

Where this fits

What this is about: Fact Tooling