Skip to content

docs: drop per-version README paragraphs, reorder for engineer-first reading#95

Merged
vaaraio merged 1 commit into
mainfrom
docs/readme-keep-important-sections
May 18, 2026
Merged

docs: drop per-version README paragraphs, reorder for engineer-first reading#95
vaaraio merged 1 commit into
mainfrom
docs/readme-keep-important-sections

Conversation

@vaaraio
Copy link
Copy Markdown
Owner

@vaaraio vaaraio commented May 18, 2026

Summary

  • Drops the v0.12 through v0.18 per-version paragraphs from README. CHANGELOG and Releases already carry the same history.
  • Keeps HTTP API, TypeScript client (now a ### TypeScript client subsection), and OVERT 1.0 attestation as first-class sections with their install + code blocks. No capabilities lost in compression.
  • Reorders to engineer-first: Install → Quick start → What evidence looks like → Numbers → Framework integrations → HTTP API → OVERT → Where things live.
  • "Where things live" promoted to a table. Adds CHANGELOG, SECURITY, CONTRIBUTING, and signing-keys pointers.

Test plan

  • Render README on GitHub and visually skim for layout regressions in the table, code blocks, and section nesting.
  • Verify all linked files still exist (COMPLIANCE.md, docs/openapi.yaml, CHANGELOG.md, docs/signing-keys.md, SECURITY.md, CONTRIBUTING.md, bench/vaara-bench-v1.md).

Summary by CodeRabbit

  • Documentation
    • Reorganized README content with reflowed examples and updated dependency references
    • Enhanced HTTP API and registry documentation with TypeScript client details and operator endpoint specifications
    • Extended attestation documentation with comprehensive architectural information and verifier behavior guidance
    • Refreshed directory references, updated subsection titles, and added supplementary resource links

Review Change Stack

…reading

Per-version prose (v0.12 through v0.18) duplicated content already in CHANGELOG
and the Releases page. The capabilities themselves stay as first-class README
sections (HTTP API with curl example, TypeScript client with npm install and
code block, OVERT 1.0 attestation with emit_base_envelope and verifier CLIs)
so cold readers can still copy-paste from each. Install and Quick start now
land before the evidence specimen. Where things live promoted to a table with
CHANGELOG / SECURITY / CONTRIBUTING / signing-keys pointers added. 213 to 188
lines, no capabilities dropped.
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 18, 2026

📝 Walkthrough

Walkthrough

README.md documentation is reorganized to improve clarity and completeness: the evidence section is reflowed for compactness with updated install instructions, HTTP API documentation is rewritten to emphasize OpenAPI contracts and introduces a TypeScript client, and OVERT 1.0 attestation details are substantially expanded with operational and technical specifics.

Changes

README documentation reorganization

Layer / File(s) Summary
Evidence section reorganization
README.md
The "What evidence looks like" section was relocated from the top and replaced with a condensed JSON example and updated descriptions of PDF/HTML/Sigstore output variants, with new references to required install extras.
API documentation and version cleanup
README.md
HTTP API documentation is rewritten to reference docs/openapi.yaml as the wire contract, lists operator endpoints (policy reload, injection/PII detectors), and introduces a new TypeScript client section with install command. Version suffix removed from "Cloud guardrails as upstream signals" heading.
OVERT 1.0 attestation documentation expansion
README.md
OVERT 1.0 section is expanded with new details on Arbiter role, Phase 3 IAP/log anchoring with Rekor, S3P emitter confidence intervals and protocol-profile extension, overt verify scope, experimental TEE binding, and refreshed "Where things live" directory table with Article 14 link.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~4 minutes

Possibly related PRs

  • vaaraio/vaara#89: Adds the evidence JSON specimen that this PR reorganizes and updates in the README.
  • vaaraio/vaara#80: Modifies the same OVERT 1.0 attestation/protocol section being expanded in this PR.
  • vaaraio/vaara#47: Previous README reflow with similar documentation reorganization and "Where things live" table updates.

Poem

🐰 A README reborn, clearer and bright,
Evidence shines in compact delight,
APIs speak OpenAPI's language true,
OVERT grows rich with operational dew,
Docs now guide readers through every view! 📚✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main changes: removing per-version README paragraphs and reordering content for better engineer-focused flow, which aligns with the PR objectives.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/readme-keep-important-sections

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
README.md (1)

125-126: ⚡ Quick win

Add a direct npm link for the TypeScript client package.

Line 125 says it ships as @vaara/client; linking the package page (npm) here makes verification and onboarding faster than relying on name lookup.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 125 - 126, Update the README sentence that references
clients/ts and the package name `@vaara/client` to include a direct npm package
link (https://www.npmjs.com/package/@vaara/client) so readers can click through
to the package page; edit the line that currently reads "ships on npm as
`@vaara/client`" to embed that npm URL next to the package name.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 140: Replace the loose "overt.is" reference in the sentence beginning
"Vaara implements the OVERT 1.0 (overt.is) Protocol Profile 1.0 Base
Envelope..." with a direct canonical spec URL (the official OVERT 1.0
specification document/URI) and append a brief citation (e.g., spec title and
publication date) so the claim is verifiable; update the README sentence to
include the full spec link and citation in parentheses immediately after "OVERT
1.0" and keep the rest of the technical summary unchanged.

---

Nitpick comments:
In `@README.md`:
- Around line 125-126: Update the README sentence that references clients/ts and
the package name `@vaara/client` to include a direct npm package link
(https://www.npmjs.com/package/@vaara/client) so readers can click through to
the package page; edit the line that currently reads "ships on npm as
`@vaara/client`" to embed that npm URL next to the package name.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ede97c47-17c4-4cad-8942-d61903271472

📥 Commits

Reviewing files that changed from the base of the PR and between cada37b and ebe41f9.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md
## OVERT 1.0 attestation

Vaara implements the OVERT 1.0 ([overt.is](https://overt.is/)) Protocol Profile 1.0 Base Envelope. OVERT 1.0 is an open standard for runtime trust in AI systems, authored by Glacis Technologies and published 25 March 2026. Closed-schema 9-field structure at AAL-3 Phase 2 (Provisional Receipt), canonical CBOR (RFC 8949), Ed25519 signatures, HMAC-SHA256 keyed commitments, IEEE-754 float rejection. v0.13.0 adds a reference Phase 3 IAP (`vaara.attestation.iap`) that notary-signs the Provisional Receipt and anchors it in a transparency log; production deployments can swap in sigstore Rekor or an equivalent independently-operated log at the same call sites.
Vaara implements the OVERT 1.0 ([overt.is](https://overt.is/)) Protocol Profile 1.0 Base Envelope. OVERT 1.0 is an open standard for runtime trust in AI systems, authored by Glacis Technologies and published 25 March 2026. Closed-schema 9-field structure at AAL-3 Phase 2 (Provisional Receipt), canonical CBOR (RFC 8949), Ed25519 signatures, HMAC-SHA256 keyed commitments, IEEE-754 float rejection.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Anchor the OVERT publication/date claim to a canonical spec URL.

Line 140 includes precise historical and technical claims; add a direct spec/document link (not only overt.is) so readers can verify details and avoid drift ambiguity.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` at line 140, Replace the loose "overt.is" reference in the
sentence beginning "Vaara implements the OVERT 1.0 (overt.is) Protocol Profile
1.0 Base Envelope..." with a direct canonical spec URL (the official OVERT 1.0
specification document/URI) and append a brief citation (e.g., spec title and
publication date) so the claim is verifiable; update the README sentence to
include the full spec link and citation in parentheses immediately after "OVERT
1.0" and keep the rest of the technical summary unchanged.

@vaaraio vaaraio merged commit 47812c5 into main May 18, 2026
10 checks passed
@vaaraio vaaraio deleted the docs/readme-keep-important-sections branch May 18, 2026 08:44
vaaraio added a commit that referenced this pull request May 18, 2026
… Rebuff)

* feat: v0.20.0 OSS guardrail adapters (NeMo, Guardrails AI, LLM Guard, Rebuff)

Four adapters mirror the v0.19.0 cloud pattern. 41 new mapping rows in _content_safety_articles.py across the four OSS providers (7 NeMo, 10 Guardrails AI, 20 LLM Guard, 4 Rebuff), tagged with EU AI Act articles and OWASP LLM Top 10 codes. 29 new tests, 712 total passing. Optional extras: nemo-guardrails, guardrails-ai, llm-guard, rebuff. HuggingFace Space added as Demo URL in pyproject and as a badge on README. TS client bumped lockstep to 0.20.0.

* docs: drop version label from OSS guardrails section to align with #95

---------

Co-authored-by: vaaraio <267591518+vaaraio@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant