Define the trajectory schema package and validation fixtures #42

Closed
opened 2026-07-23 05:32:28 +00:00 by coilyco-ops · 0 comments
Member

Parent: #40

Implement the versioned trajectory contract v1 as a shared schema package with producer and consumer validation fixtures.

Dependencies:

  • None

Acceptance criteria:

  • Encode the event envelope, correlation fields, event taxonomy, provenance, redaction metadata, and model execution fields from docs/trajectory-contract-v1.md.
  • Provide valid, invalid, duplicate, late-event, partial-trajectory, and replay fixtures.
  • Support OpenTelemetry and GenAI attributes alongside agentproxy-specific joins.
  • Keep opt-in body capture and content references explicit.
  • Publish compatibility and schema-versioning rules for independent producers and consumers.

Historical telemetry issues may be cited as evidence only. Do not reopen or repurpose them.

Parent: #40 Implement the versioned trajectory contract v1 as a shared schema package with producer and consumer validation fixtures. Dependencies: - None Acceptance criteria: - Encode the event envelope, correlation fields, event taxonomy, provenance, redaction metadata, and model execution fields from docs/trajectory-contract-v1.md. - Provide valid, invalid, duplicate, late-event, partial-trajectory, and replay fixtures. - Support OpenTelemetry and GenAI attributes alongside agentproxy-specific joins. - Keep opt-in body capture and content references explicit. - Publish compatibility and schema-versioning rules for independent producers and consumers. Historical telemetry issues may be cited as evidence only. Do not reopen or repurpose them.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/agent-proxy#42
No description provided.