mirror of https://github.com/ruvnet/RuView synced 2026-06-09 10:13:17 +00:00

Files

T

ruv 4557f6f614 docs+plugins: rvAgent + RVF agentic-flow integration exploration

Land the rvAgent (vendor/ruvector/crates/rvAgent/) integration research
dossier and update both the Claude Code and Codex plugins so future
operators have a discoverable entry point for prototyping agentic flows
on top of RuView's existing sensing pipeline + RVF cognitive containers.

Added:
- docs/research/rvagent-rvf-integration/README.md
  Full integration thesis: rvAgent's 8 crates + 14 middlewares share
  RVF as their state-persistence format with RuView's existing
  v2/crates/wifi-densepose-sensing-server/src/rvf_container.rs. Three
  shippable touchpoints (each independent):
    1. Two new RVF segment types (SEG_AGENT_STATE = 0x08,
       SEG_DECISION = 0x09) so rvAgent sessions and RuView sensing
       sessions interleave in one witness-bundle-attestable blob
    2. BfldEvent → ToolOutput shim — agent reads BFLD events as
       tool context with no new IPC
    3. cog-* subagent registration under a queen-agent router
  Open questions: workspace inclusion path, sync/async adapter
  placement, privacy-class composition with rvagent-middleware
  sanitizer, Soul Signature ↔ SoulMatchOracle bridge, MCP surface.
  Proposed next: ADR-124 before scaffolding wifi-densepose-agent.

- plugins/ruview/skills/ruview-rvagent/SKILL.md
  New Claude Code skill exposing the integration surface, links to
  the research doc, and lists the three shippable touchpoints. Skill
  description tuned so Claude auto-discovers it for queries like
  "wire rvAgent into RuView" or "operator agent reacting to BFLD."

- plugins/ruview/codex/prompts/ruview-rvagent.md
  Codex counterpart prompt with trigger phrasing, reading order,
  same three touchpoints + open questions, and the ADR-124 next step.

Modified:
- plugins/ruview/.claude-plugin/plugin.json
  Version 0.1.0 → 0.2.0; description extended to mention "BFLD
  privacy layer" and "rvAgent + RVF agentic flows".

- plugins/ruview/codex/AGENTS.md
  Prompt table grows one row: `ruview-rvagent` for the new prompt.

No code changes; no test impact.

Co-Authored-By: claude-flow <ruv@ruv.net>

2026-05-24 17:33:12 -04:00

2.9 KiB

Raw Blame History

name, description

name	description
ruview-rvagent	Explore and prototype rvAgent + RVF integration for RuView agentic flows. Use when working on cross-cog coordination, operator-facing agents reading BFLD / pose / vitals events live, or persisting agent state alongside sensing data in the same RVF container.

RuView rvAgent + RVF integration

Surface area for wiring vendor/ruvector/crates/rvAgent/ into RuView so the existing sensing pipeline becomes the substrate an agentic flow can read, reason about, and respond to.

When to use this skill

"I want an agent that reacts to BFLD presence in the kitchen and pages the carer."
"I need cog-pose-estimation and cog-bfld to negotiate before publishing a synthesized event."
"Can the witness chain attest both the sensing event AND the agent decision in one RVF blob?"
"How do we keep rvAgent's tool outputs class-3 compliant when the source BFLD event is Restricted?"

Key surfaces

Surface	File	Notes
rvAgent core	`vendor/ruvector/crates/rvAgent/rvagent-core/src/agi_container.rs` (627 LOC)	RVF-compatible state container
rvAgent middleware	`vendor/ruvector/crates/rvAgent/rvagent-middleware/`	Witness, sanitizer, SONA, HNSW
Agent personas	`vendor/ruvector/crates/rvAgent/.ruv/agents/rvagent-{queen,coder,tester,security}.md`	Reference patterns
RVF container	`v2/crates/wifi-densepose-sensing-server/src/rvf_container.rs`	Add `SEG_AGENT_STATE`, `SEG_DECISION`
BFLD event	`v2/crates/wifi-densepose-bfld/src/event.rs`	`BfldEvent::to_json()` → `ToolOutput`
BFLD pipeline handle	`v2/crates/wifi-densepose-bfld/src/pipeline_handle.rs`	`BfldPipelineHandle::send`

Research dossier

Full integration analysis lives at docs/research/rvagent-rvf-integration/README.md.

Three shippable touchpoints, each independent:

RVF wire: two new segment types (SEG_AGENT_STATE = 0x08, SEG_DECISION = 0x09) let rvAgent sessions interleave with RuView sensing sessions in the same blob.
Tool surface: BfldEvent → ToolOutput shim turns BFLD events into agent context with no new IPC.
Cog subagents: cog-pose-estimation / cog-person-count / cog-ha-matter / cog-bfld register as rvAgent subagents under a queen-agent router.

Open questions

Workspace inclusion of vendor/ruvector/crates/rvAgent/ (path dep vs published crate)
Sync ↔ async adapter (BFLD Publish is sync, rvAgent backends are tokio)
Privacy-class composition (does rvAgent's sanitizer consume PrivacyClass?)
Soul Signature ↔ SoulMatchOracle bridge
Whether BfldPipelineHandle::send lands as a public MCP tool via rvagent-mcp

Next decision

ADR-124 (proposed) — "rvAgent + RVF integration for RuView agentic flows" — would capture segment assignments, cog-subagent contract, and the privacy-class composition rule. Land before scaffolding v2/crates/wifi-densepose-agent.

2.9 KiB Raw Blame History