Skip to content

TR-09: one trace schema (= APR-OBS OBS-17) (TRACE-001) #4564

Closed as not planned

Description

@noahgift

Spec TRACE-001 v1.2 (docs/specifications/TRACE-001-tracing-consumers.md, operator 2026-09-27), row TR-09. Minted by the cop (aprender-77) under the single-minter rule. Epic #3598 (0.71.0; milestone rules in §4.1).

EV Row Work Contract Done when (all must hold) deps K̂
6 TR-09 one trace schema apr run --trace-level layer|chrome becomes a renderer over apr-trace-v1 emitted by InferenceTracer; chrome output is a format of the same data. Filed on APR-OBS as OBS-17 apr-trace-v1 same request through apr run and serve yields byte-identical apr-trace-v1 modulo timestamps APR-OBS OBS-09 120

Hard rules §5 (R-1..R-7) and STOP conditions §7 (S-1..S-9) apply. A row that misses its cut moves on with slipped_from:; if it serves an exit criterion (V1/V2/V6/V7), the move needs an operator ruling.

Activity

  1. added this to the 0.71.0 milestone on Sep 27, 2026
  2. modified the milestones: 0.71.0, 0.72.0 on Oct 8, 2026
  3. noahgift commented on Oct 14, 2026

    @noahgift
    MemberAuthor

    merged into #5314 (master ticket for epic #4000; triage rule 7b, 2026-10-14). It is a checklist row there; reopen this issue when work on it starts or its PR opens.

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

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions