The RuV Stack gets a change feed you can check the provenance of

What this is

The ruvnet repository is the front door to the stack. It carries the marketplace plugin, the skills installer and the published evidence files that record what was measured and when.

The problem it now addresses is ordinary and annoying: a repository being pushed tells you nothing about whether anything meaningful changed. A change feed that distinguishes a reviewed change from a routine push is far more useful than a firehose.

What changed

Commit 7caac54 on September 12 adds a provenance-aware change feed for the stack: entries carry where the claim came from, not only that something moved.

Two September 14 commits extend the same idea to freshness. Commit 3d86358 exposes upstream snapshot freshness, and commit d5f7171e refreshes MCP resource freshness at read time, so a client asking through MCP sees how old the data is instead of assuming it is current. A separate September 13 commit routes ChatGPT to the review-scoped federation MCP profile, which lines up with the Ruflo federation work published the day before.

Get started

Claude Code installs the stack through the marketplace, exactly as the README states:

/plugin marketplace add ruvnet/ruvnet
/plugin install ruvnet@ruvnet

The reviewed change feed runs from a checkout. The install guide requires Node.js 22 or newer for the local companion:

git clone https://github.com/ruvnet/ruvnet.git
cd ruvnet
node plugins/ruvnet/bin/ruvnet.mjs changes

Expected result: a list of reviewed changes across the stack, each with its provenance, rather than a raw push log.

Skills and marketplace installation are documented in docs/entrypoint/INSTALL.md; the local CLI and MCP companion is documented in plugins/ruvnet/docs/INSTALL.md. Read those before wiring the feed into an automation — the commands there are the supported surface.

Use it today

Practical case: a weekly review of what actually changed across a large public stack. Input is nothing more than a checkout. Workflow is run the changes command, read the provenance on each entry, then open the ones that matter. Output is a short reviewed list instead of two hundred push timestamps.

Acceptance test: run the command twice in the same minute. The output should be stable, and any freshness field should describe the snapshot age rather than the moment you ran it.

Push it further

Experimental commentary. A provenance-carrying feed is the right input for an agent that writes release notes, because the agent can be held to citing the entry it used rather than inventing a summary.

Limitation: the feed reports reviewed changes from a snapshot, so it is only as current as the snapshot behind it — which is precisely why the freshness commits matter. Falsifiable test: compare an entry's provenance link against the repository it names. If the link does not open the change it claims, the entry is wrong and should be reported.