Skip to content

docs: position the GitHub overview for agent workflows - #2522

Open
miyoungc wants to merge 10 commits into
developfrom
miyoungc/ngr-1020-guardrails-github-overview-update
Open

miyoungc wants to merge 10 commits into
developfrom
miyoungc/ngr-1020-guardrails-github-overview-update

Conversation

@miyoungc

@miyoungc miyoungc commented Oct 28, 2026 •

Copy link
Copy Markdown
Collaborator

Description

Update the GitHub README around agent workflows, using Monika's product proposal and a technical introduction. Add a runnable, model-free refund-policy quickstart, four integration use cases, and a linked list of NeMo Guardrails capabilities. Describe the current coverage and limitations of the SDK, API server, hooks server, and experimental proxy.

Remove the hard-coded README release notice and the release workflow step that updated it. Apply the NVIDIA documentation style guide. Keep the release announcement in release-notes tracking and focus the README on NeMo Guardrails capabilities.

Preview: https://github.com/NVIDIA-NeMo/Guardrails/blob/miyoungc/ngr-1020-guardrails-github-overview-update/README.md

Related Issue(s)

The tracking issue is in Linear; there is no linked triaged GitHub issue.

Verification

  • Audited every README section against the implementation, schemas, and existing tests. Corrected explicit tool-rail selection, error handling, LangChain framework requirements, action terminology, and telemetry/privacy guidance.
  • 805 targeted tests passed across tool rails, the checks API, hooks, LangChain, proxy contracts, telemetry, framework selection, error handling, and speculative generation. No live model/provider calls were made.
  • Executed the exact README quickstart with network connections prohibited; output matched. Seven additional policy/schema boundary cases passed. A separate supplied-LLM check confirmed RunnableRails works without changing the default framework.
  • Verified 27 local targets/anchors and 14 published NVIDIA documentation URLs, plus GitHub workflow and Discussions metadata. Every capability item links to supporting documentation.
  • uv run --locked pre-commit run --files README.md .github/workflows/release.yml and git diff --check passed.
  • make docs-fern passed with 0 errors and 567 warnings.
Source references for the factual audit

These checks establish implemented behavior; they do not establish detector effectiveness or qualify every remote service.

AI Assistance

Codex helped prepare the README and perform local verification. Human review is pending.

  • No AI tools were used.
  • AI tools were used; a human reviewed and can explain every change (tool: Codex).

Checklist

  • I've read the CONTRIBUTING guidelines.
  • This PR links to a triaged issue assigned to me.
  • My PR title follows the project commit convention.
  • I've updated the documentation if applicable.
  • I've added tests if applicable. The README example was executed and checked against policy boundaries.
  • I've noted verification and any checks I couldn't run.
  • I did not update generated changelog files manually.
  • I addressed all CodeRabbit, Greptile, and other review comments, or replied with why no change is needed.
  • @mentions of the person or team responsible for reviewing proposed changes.

Summary by CodeRabbit

  • Documentation
    • Reworked the README to explain how applications can apply programmable safeguards for AI agents, including workflow checks and verdict enforcement.
    • Added a refund-tool example, deployment options, supported checks, limitations, and telemetry information.
    • Updated installation, contribution, and license references. The release process no longer updates the README’s release link.

Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
@github-actions github-actions Bot added status: needs triage New issues that have not yet been reviewed or categorized. size: M labels Oct 28, 2026
Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
@github-actions github-actions Bot added size: L and removed size: M labels Oct 29, 2026
Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
@miyoungc
miyoungc marked this pull request as ready for review October 30, 2026 19:43
Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
@miyoungc miyoungc added status: in review status: triaged Triaged by a maintainer; eligible for automated review (CodeRabbit/Greptile). and removed status: needs triage New issues that have not yet been reviewed or categorized. labels Oct 30, 2026
@greptile-apps

greptile-apps Bot commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 5/5

[Low impact] The PR appears safe to merge, with the previous privacy issue fixed and no new actionable issues found.

Summary

Reworks the GitHub overview around agent workflows.

  • The README shows where agents can check prompts, tools, and results.
  • Developers can check a refund tool against a $500 limit without a model.
  • The README explains how agent checks fit into services, hooks, and frameworks.
  • The README maps Guardrails capabilities to checks and agent checkpoints.
  • The README summarizes usage reporting and separates it from provider data sharing.
  • Release pull requests no longer update the README version notice.
  • The README points contributors to current support and citation details.

The previous privacy-guidance finding is fully addressed. No new actionable issues were found.

Reviews (2) · Last reviewed commit: "docs: ground overview claims in implemen..." · Reviewed by Greptile

Comment thread README.md Outdated
Third-party endpoints have separate terms and privacy practices. The NVIDIA NeMo Guardrails library can use inference endpoints such as NVIDIA Build (`build.nvidia.com`). If you use NVIDIA Build or another third-party endpoint, that endpoint's terms of service and privacy practices apply independently of the library. Any telemetry opt-out in the NVIDIA NeMo Guardrails library does not extend to the endpoint you choose. NVIDIA Build is intended for evaluation and testing only and must not be used in production environments. Do not submit confidential information or personal data when using NVIDIA Build.

## Inviting the community to contribute
Refer to [telemetry and privacy](https://docs.nvidia.com/nemo/guardrails/latest/resources/telemetry) for the full schema, local audit file, opt-out options, and third-party endpoint terms.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Promised privacy guidance is missing

The linked page only covers library telemetry; it does not contain the promised third-party endpoint terms. This PR also removes the README's explanation that third-party services have separate privacy terms and that the library's opt-out does not cover them. Readers following this link cannot find that guidance. Move it into the linked page or link to a page that contains it.

Prompt To Fix With AI
This is a comment left during a code review.
Path: README.md
Line: 253

Comment:
**Promised privacy guidance is missing**

The linked page only covers library telemetry; it does not contain the promised third-party endpoint terms. This PR also removes the README's explanation that third-party services have separate privacy terms and that the library's opt-out does not cover them. Readers following this link cannot find that guidance. Move it into the linked page or link to a page that contains it.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

@coderabbitai

coderabbitai Bot commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

Review in Change Stack →

No actionable comments were generated in the recent review.

Recent review info
Run configuration
Commits

Reviewing files that changed from the base of the PR and between 731f6d0 and bec712d.

Files selected for processing: 2
  • .github/workflows/release.yml
  • README.md
Files with no reviewable changes: 1
  • .github/workflows/release.yml

Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review.

Walkthrough

The README is rewritten around programmable safeguards for AI agents, with a new quickstart and updated deployment, check, telemetry, and project information. The release workflow no longer updates README release references; version, changelog, and lockfile updates remain.

Changes: Agent safeguards documentation

Layer / File(s) Summary
Project framing and release updates
README.md, .github/workflows/release.yml
The README introduces configurable checks for agent workflows and updates project links. The release workflow stops editing the README and removes the related pull request text and path entry.
Check workflow and quickstart
README.md
The README explains check verdicts and tool execution boundaries, then adds a refund-tool example using a CEL rule, check_async(), and IORails.
Deployment and check coverage
README.md
The README describes the HTTP proxy, coding-agent hooks, framework integration, check coverage, and supported engines.
Telemetry and project policies
README.md
The README shortens its telemetry description and updates contribution, license, and citation links.

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Suggested labels: documentation

Suggested reviewers: pouyanpi

Merge Risk: Minimal · up to bec71

No actionable merge-blocking risk remains.

Pre-merge checks: Passed 5
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly describes the main change: repositioning the GitHub README around agent workflows. The release workflow update is secondary.
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Test Results For Major Changes Passed The PR makes a substantial README and release-workflow documentation change. Its description includes testing information: a network-disabled quickstart run, seven policy and schema boundary checks, t…
Full details: Test Results For Major Changes

Explanation

The PR makes a substantial README and release-workflow documentation change. Its description includes testing information: a network-disabled quickstart run, seven policy and schema boundary checks, target and URL validation, pre-commit, diff, and documentation checks. No numeric, convergence, or performance change is introduced.

Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size: L status: in review status: triaged Triaged by a maintainer; eligible for automated review (CodeRabbit/Greptile).

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant