Skip to content

corrections: OpenTelemetry read-back adapter for the findings buffer #7564

Description

@kyle-sexton

Parent

Refs #7555. Source: PLAN Phase 0, topic poteto-review. Thread: OpenTelemetry read-back adapter for
the buffer (deferred).

Depends on

  • none (parked: opens on the reopen trigger below, not on an edge)

Reopen trigger

A team adopts OpenTelemetry as a buffer source.

Outcome

When reopened: a findings-buffer adapter reads rows back from OpenTelemetry.

Decisions

  • Deferred: no OpenTelemetry read-back adapter until a team adopts (D61). Origin: ours.

Key interfaces

From the design's contracts, the adapter it would implement: "append.sh < rows.jsonl: stores each
line; exit 0 only when every row is durable ... read.sh [--since <UTC ISO-8601>]: JSONL to
stdout; with --since returns at least every row with ts >= since; never truncates silently."

Done when

  • The trigger has fired and is cited in a comment.
  • Slices are filed under this item.

Out of scope

  • The buffer contract itself, which the Findings buffer thread owns.

Activity

  1. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 16, 2026
  2. github-actions commented on Oct 16, 2026

    @github-actions
    Contributor

    Thanks for the report. Automated triage handed this issue to a maintainer.

    Automated triage. A maintainer reviews it.

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-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.needs-specNeeds a Brief or plan before anyone can build it.

    Fields

    Work status

    needs-spec

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions