agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/nvcf/src/control-plane-services/notary/AGENTS.md

nvcf / notary

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

Notary is an OSS/self-hosted Java service in the root nvcf Bazel module. It does not own a nested module, lockfile, Bazel configuration, or third-party dependency hub. The monorepo copy is Bazel-only and contains no project POMs. Bazel consumes nv-boot through direct source labels and produces the executable application jar. Keep any Maven build support in the independent source repository. Do not restore project POMs or add Maven build instructions here. Run commands from the monorepo root: The tests use in-process…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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. Distinctive:

    Run commands from the monorepo root:

    line 14
  2. Distinctive:

    Use direct labels for nv-boot source targets:

    line 37
  3. Very specific:

    Do not restore the source repository's Maven NOTICE generator or copy its standalone LICENSE or NOTICE files into this subtree.

    line 59

≈ “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 - Notary

Notary is an OSS/self-hosted Java service in the root nvcf Bazel module. It does not own a nested module, lockfile, Bazel configuration, or third-party dependency hub.

The monorepo copy is Bazel-only and contains no project POMs. Bazel consumes nv-boot through direct source labels and produces the executable application jar. Keep any Maven build support in the independent source repository. Do not restore project POMs or add Maven build instructions here.

Build and test

Run commands from the monorepo root:

export BAZEL_OUTPUT_USER_ROOT="${TMPDIR:-/tmp}/nvcf-bazel-cache"

bazel --output_user_root="${BAZEL_OUTPUT_USER_ROOT}" \
  build //src/control-plane-services/notary/...

bazel --output_user_root="${BAZEL_OUTPUT_USER_ROOT}" \
  test //src/control-plane-services/notary/... \
  --cache_test_results=no \
  --test_output=errors

The tests use in-process Spring Boot and WireMock servers. They do not require Docker. CI therefore routes this component to the build-container lane.

Dependencies

The root MODULE.bazel and maven_install.json own the shared @nv_third_party_deps hub. BUILD targets declare direct compile and runtime edges. A coordinate in the hub is not automatically on Notary's classpath.

Use direct labels for nv-boot source targets:

//src/libraries/java/nv-boot-parent/nv-boot-starter-core:nv_boot_starter_core

The source Maven build pins commons-collections4 4.4. The monorepo shared dependency graph selects the compatible 4.5.0 version. Keep that intentional parity difference documented instead of adding a lower root pin.

NOTICE

The component NOTICE is derived from jars under the Bazel-built notary-service:app. Generate and check it through the root-owned rules:

bazel run //src/control-plane-services/notary:generate_notice -- \
  --update-metadata --write
bazel test //src/control-plane-services/notary:notice_check_test
bazel build //src/control-plane-services/notary:osrb_dependency_delta

Do not restore the source repository's Maven NOTICE generator or copy its standalone LICENSE or NOTICE files into this subtree.

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