agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/nvcf/src/compute-plane-services/request-trace-uploader/AGENTS.md

nvcf / request-trace-uploader

AGENTS.md261 starsChanged 9 days agoApache-2.0View on GitHub

Native Go sidecar scaffold for closed Dynamo request-trace segments. It does not publish or delete source segments until a supported upload adapter lands. Run bazel run //:gazelle after changing Go imports or Bazel metadata. - Target Dynamo v1.4.0. It writes one segment family, so classify records by event_type and never by filename or prefix. - Treat the highest indexed segment as active. - Do not add a release entry until an approved upload adapter exists. - Do not add a…

The file

We split this AGENTS.md into the rules it gives an agent

5 rules. About 1 is common, 3 are distinctive, and 1 is very specific to this project.

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run bazel run //:gazelle after changing Go imports or Bazel metadata.

    line 22
  2. Distinctive:

    Treat the highest indexed segment as active.

    line 28
  3. Distinctive:

    Do not add a release entry until an approved upload adapter exists.

    line 29
  4. Distinctive:

    Do not add a Prometheus scrape endpoint.

    line 30
  5. Common:

    Do not log request payloads, credentials, paths, or remote upload IDs.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

AGENTS.md - request-trace-uploader

Native Go sidecar scaffold for closed Dynamo request-trace segments. It does not publish or delete source segments until a supported upload adapter lands.

Layout

  • cmd/: process entrypoint and OCI image target
  • config/: sidecar contract and bounded policy parsing
  • segment/: closed segment discovery
  • backend/: export destination contract and the backend registry
  • service/: startup, recovery scan, and HTTP server
  • internal/health/: liveness and readiness handlers

Build and test

bazel test //src/compute-plane-services/request-trace-uploader/...
bazel build //src/compute-plane-services/request-trace-uploader/cmd:image

Run bazel run //:gazelle after changing Go imports or Bazel metadata.

Rules

  • Target Dynamo v1.4.0. It writes one segment family, so classify records by event_type and never by filename or prefix.
  • Treat the highest indexed segment as active.
  • Do not add a release entry until an approved upload adapter exists.
  • Do not add a Prometheus scrape endpoint. The later observability increment exports logs, traces, and metrics through BYOO OTLP endpoints.
  • Do not log request payloads, credentials, paths, or remote upload IDs.
  • config, segment, backend, and service are consumed by other modules that link their own backends. Treat their exported surface as a contract and keep implementation detail under internal/.
  • Backends register themselves from an init function. This binary links none, so a build reports an unlinked backend rather than failing to compile.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free