amberfork-model 0.4.0

Canonical Run/Step trajectory model and DiffResult schema for amberfork (the frozen contract every crate reads).
Documentation
  • Coverage
  • 67.29%
    72 out of 107 items documented0 out of 9 items with examples
  • Size
  • Source code size: 37.31 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 2.01 MB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 10s Average build duration of successful builds.
  • all releases: 10s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • Repository
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • Melvin0070

Canonical trajectory model for amberfork — the frozen contract every crate reads.

A [Run] is one agent trajectory: an ordered list of [Step]s plus optional DAG [Edge]s. This is the input seam — amberfork-ingest produces it from OTel/plain JSON, and amberfork-align consumes it. It mirrors the public wire format documented in docs/trace-format.md; once this crate exists, these types are the source of truth and that document tracks them.

[DiffResult] is the matching output seam: what amberfork-align fills in and the CLI's --json and the Leptos UI render.

Design rules baked into the types (see docs/design/design-run-diff-debugger.md):

  • outcome is a run-level verdict supplied by the user, never inferred from span status.
  • Timing (t_start/t_end) is display-only and is never an alignment signal, so it stays a raw string here rather than a parsed timestamp.
  • inputs/outputs distinguish text from structured payloads in the type itself, because the diff engine text-diffs strings but field-diffs objects.