ruvnet / ruvnet/midstream

SOTA: adaptive hierarchical runtime monitoring with value-of-information escalation

Open
#99 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
147
Forks
39
Avg merge
16h 39m
Merged PRs (30d)
2

Description

Goal

Add a hierarchical streaming safety monitor that spends verification compute only when expected risk justifies it while forcing inspection around privileged actions.

Architecture

stream -> tiny detector -> risk score -> local verifier -> strong investigator -> RVM stop

Low-risk tokens/events continue without expensive investigation. Medium-risk activity invokes a local verifier. High-risk activity invokes a stronger model or policy investigator. Critical events are synchronously gated by RVM.

Required hard gates

Always inspect privilege escalation, credential access, network egress, destructive filesystem operations, runtime mutation, capability grants, secret handling, and policy changes.

Routing rule

Use a value-of-information decision:

investigate iff P(violation | evidence) * expected_damage > verification_cost + latency_penalty

The risk estimator must never bypass hard gates.

Metrics

  • average monitoring compute overhead
  • p50/p95 added latency
  • recall on known policy violations
  • false positive rate
  • cost per prevented violation
  • escalation distribution by tier

Target

Aim for <5% average monitoring compute overhead on ordinary traffic while preserving 100% inspection of hard-gated privileged operations.

Integration

  • MidStream: streaming feature extraction and risk scoring
  • Ruflo: agent/tool context
  • RVM: authoritative stop/allow enforcement
  • RuVector: durable incident and pattern memory
  • MetaHarness: benchmark/adversarial evaluation

Acceptance criteria

A benchmark demonstrates lower average monitoring cost than full expensive inspection while matching its recall on hard-gated operations and producing auditable escalation receipts.

Contributor guide

Open the contributing guide

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 by mapping the MidStream streaming feature extraction and risk-scoring path to the Ruflo, RVM, RuVector, and MetaHarness integrations named in the issue. Use MetaHarness for benchmark and adversarial evaluation, then verify that hard-gated operations are always inspected, escalation receipts are auditable, and adaptive monitoring lowers average cost while matching recall on those operations.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
observability-sre, security, stream-processing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.