Home / bearlike / grove · src/grove/core/telemetry/CLAUDE.md · GitHub

CLAUDE.md@src/grove/core/telemetry claudeA

Name: CLAUDE.md@src/grove/core/telemetry
Author: bearlike

CLAUDE.md@src/grove/core/telemetry is agent-read markdown (claude) from bearlike/grove.

Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.

What the file says

# grove.core.telemetry — one shape on the wire, whoever produced it

> ↑ [grove.core](../CLAUDE.md) · [root](../../../../CLAUDE.md)

Grove is an OpenTelemetry **gateway**, not a passenger. Everything a workspace
emits — Grove's own transcript replay, the live context tier, and a harness's
own OTLP re-exported through the receiver — is spelled from one vocabulary so a
fleet of mixed harnesses lands as one shape. This file owns the collection,
export and ingestion decisions; the LAUNCH boundary that decides whether an
agent exports at all (`_launch_spec`, `TelemetryConfig.reserve`) stays in
[grove.core](../CLAUDE.md), because that is manager and config territory.

**The three tiers, and why each exists.** Tier 1 stamps identity into the
agent's launch environment (`otel_resource.py`) — frozen at process start, by
construction. Tier 2 is the live context span on the activity bus
(`trace_forwarder.py`), carrying everything a frozen resource attribute cannot:
the phase, the branch actually created, tickets attached later. Tier 3 is the
transcript replay (`trace.py`), the only tier that can reconstruct a session
…

Read the whole file at its exact version.

How to install

Latest version

mdr add bearlike/grove/src/grove/core/telemetry/CLAUDE.md@git:20260908.bbb0fcb

Exact content

mdr add bearlike/grove/src/grove/core/telemetry/CLAUDE.md@sha256:2895cc64cf833c2c

Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.

Badge

[![mdr](https://markdownregistry.com/badge/art_lhvrej7nu5fqblb6.svg)](https://markdownregistry.com/a/art_lhvrej7nu5fqblb6)

1 badge views in 30 days

Versions

version	committed	commit	size	audit
git:20260908.bbb0fcb latest	2026-09-08	bbb0fcb	15,355 B	A	view · diff
git:20260812.6377c5a	2026-08-12	6377c5a	10,717 B	A	view

Audit of the latest version

A 14 of 14 checks passed. Deterministic, no model, same answer every run.

pass: Size between 200 bytes and 200 KB (15355 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

bearlike/grove · 7 stars · license MIT · pushed 2026-09-23 · branch current

API

GET https://markdownregistry.com/api/v1/artifacts/art_lhvrej7nu5fqblb6
GET https://markdownregistry.com/api/v1/resolve?ref=bearlike/grove/src/grove/core/telemetry/CLAUDE.md
GET https://markdownregistry.com/api/v1/blob/2895cc64cf833c2c0ba1b1ef339b1edf3dbd0d5e5432e65930ece3c381c9ed29

Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.