Skip to content

opentraces v0.4.9

Choose a tag to compare

@JayFarei JayFarei released this 05 Jul 07:59
· 63 commits to main since this release

Install

pipx install opentraces==0.4.9
# or
brew install JayFarei/opentraces/opentraces

Highlights — the Seal Family

Workflow, dataset, and capsule now sit on one projection contract (ADR-0008): a projection is a pure function of content-addressed inputs f(scope_ref, transform@digest, bucket_state@digest, answers).

  • Two seals, exactly. A dataset is a growing, reviewed seal (workflow-projected rows with per-row contract-triple provenance). A capsule is an immutable, URL-addressed seal (a redacted mini-bucket of one scope with a deterministic capsule_id).
  • Capsule surface: capsule create / get (read-only, stateless) / import (explicit opt-in write), plus preview, share, issue, replay, test, verdict, watch. A Cloudflare Worker renders published capsules at a URL.
  • Replay honesty: every capsule replay reports four derived properties — reproducible / gradable / scoped / sandboxed — with verdict_trust (floor|low|medium|high) as the weakest-link summary. A crafted capsule cannot over-claim.
  • One clearance predicate on every egress (bucket sync push, dataset publish, capsule publish), off by default, fail-closed — a refusal moves zero bytes.
  • One workflow engine (execute_workflow), the rc=10 judgment handshake (judgment is a recorded input, re-runs are byte-identical), an isolation primitive, and companion sanitization.
  • dataset verify — reproduces / bucket-advanced / integrity-failure.

Schema — opentraces-schema 0.9.0 (additive)

  • 0.8.0: PinRecord, Interpreter, and five optional Environment fields (resolved_dependencies, interpreter, arch, platform, abi_tag) — a home for pins, not a resolver (env tier unchanged).
  • 0.9.0: dataset-run metadata scope facets — DatasetCandidateQuery.facets and DatasetRunRecord.facet_resolution.

Both are additive MINOR bumps; existing records validate unchanged, no migration required.