Skip to content

Trajectory ingestion adapters (OpenTelemetry spans, framework tool logs) #3

Description

@SurefireStudios

Problem

StateProof verifies against a gap-free, seq-ordered trajectory in its own JSONL format. Real agents emit OpenTelemetry spans, framework-native tool logs, or vendor trace exports. Hand-converting them is the adoption barrier.

Proposal

A small set of adapters that map a source trace into the trajectory schema in packages/core/src/schema/, assigning seq from causal order rather than timestamps, and failing loudly when ordering cannot be established. A trajectory that cannot be ordered cannot support an event_order assertion, and the verifier should say so rather than guess.

Open questions

  • How human approval events are represented in each source.
  • Whether state snapshots can be reconstructed from a trace, or must be supplied separately.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-designNeeds a written design or ADR before coderoadmapOn the roadmap in docs/roadmap.md

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions