ruvnet / ruvnet/RuVector

[PIR][WP30] RVM semantic-authority layer above OpenShell-class runtimes (ADR-333, cross-repo, ADR-only here)

Open
#899 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

adr cross-repo phase-w4-4 pir wave-4
Dominant language
Rust
Stars
4.5k
Forks
603
Avg merge
23h 32m
Merged PRs (30d)
59

Description

Part of PIR Wave 4 — epic #837.

ADR-only in this repo: position RVM one layer above OpenShell-class secure runtimes (signed agent identity, signed memory, mutation rights, transferable capabilities, provenance chains, revocation, rollback, portable execution receipts) with an OpenShell interop adapter (policy projection down to YAML, downgrade-only; audit-trail ingestion into the ADR-134/ADR-312 witness chain). NVIDIA items verified: developer.nvidia.com security-stack essay (2026-08-21) + github.com/NVIDIA/OpenShell (Apache-2.0, Landlock+seccomp, 8.3k stars). RVM-side implementation requires maintainer review — merge there is USER ACTION.

  • Evidence grade & artifact availability: docs/research/perpetual-intelligence-runtime/10-wave4-evidence-review.md (PR #892)
  • WP/ADR mapping, phases, and security gates: docs/research/perpetual-intelligence-runtime/11-wave4-program-plan.md (PR #892)
  • ADR: docs/adr/ADR-333-rvm-semantic-authority-above-openshell.md

Depends on: none in-repo.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with docs/research/perpetual-intelligence-runtime/10-wave4-evidence-review.md and 11-wave4-program-plan.md, then read docs/adr/ADR-333-rvm-semantic-authority-above-openshell.md. Confirm that the ADR records RVM's position above OpenShell-class runtimes, the downgrade-only interop adapter, and witness-chain audit ingestion; completion requires maintainer review.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, infrastructure, security
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.