agentleFS
NVIDIAKnown publisherNVIDIA/IsaacCapture/src/python/isaaccapture/cts/common/AGENTS.md

IsaacCapture / common

AGENTS.md438 starsChanged 31 days agoApache-2.0View on GitHub

CRITICAL: complete the mandatory AGENTS.md preflight in ../../../../../AGENTS.md before editing here. A change here reaches every schema's checker, so also read the AGENTS.md of each checker under ../*/checker/. cts_common is what the per-schema checkers share: file-order MCAP reading by schema name, the accumulator model, the envelope and payload checks, verdict aggregation, Mark, the label sidecar, and the viewer's Sample, Track, Skeleton, status-list HTML and submission archive. - Schema-agnostic. No record type, joint table, profile or check group lives here; tests/test_boundaries.py…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

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

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Schema-agnostic: No record type, joint table, profile or check group lives here.

    line 17
  2. Distinctive:

    Changing a shared check changes every schema's verdict: Run each checker's suite.

    line 24

≈ “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
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. SPDX-License-Identifier: Apache-2.0 -->

Agent notes — cts/common/

CRITICAL: complete the mandatory AGENTS.md preflight in ../../../../../AGENTS.md before editing here. A change here reaches every schema's checker, so also read the AGENTS.md of each checker under ../*/checker/.

cts_common is what the per-schema checkers share: file-order MCAP reading by schema name, the accumulator model, the envelope and payload checks, verdict aggregation, Mark, the label sidecar, and the viewer's Sample, Track, Skeleton, status-list HTML and submission archive.

  • Schema-agnostic. No record type, joint table, profile or check group lives here; tests/test_boundaries.py rejects the names. A shared check carries no group — each schema package subclasses it to set one.
  • Same dependency floor as the checkers: mcap and flatbuffers, no isaaccapture. viser only in panel/skeleton.py.
  • The oracles import nothing from here. Their quaternion arithmetic is duplicated on purpose; each schema's test_boundaries.py asserts it.
  • Changing a shared check changes every schema's verdict. Run each checker's suite.
  • The submission archive (panel/bundle.py) takes the schema's parts as arguments: each schema's panel/bundle.py passes the result groups, the frame series and its own package for tool. The archive carries the inputs that cannot be regenerated, above all the labels sidecar. Keep inputs (file hashes, labels, tool.commit) apart from outputs; the packed report is a cache and the recording wins. A missing companion goes in inputs.missing, not an error. It is a zip so report.json reads without decompressing the recording.
  • After moving code in or out of here, run pre-commit, not only the tests. Under from __future__ import annotations a name used only in a type hint is never evaluated, so a dropped import passes every test and fails ruff (F821).

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.