ruClip closes a nonce replay race in its credential path

What ruClip is

A control plane for an organisation whose workers are agents: identity, budgets, graph state and the operating rules that keep it from running away. The repository describes itself as ruvnet only and in active development.

What changed

The September fix closes a time of check to time of use race in actor credentials and human identity attestations, where a nonce could be replayed between validation and use. Around it: concurrent, bounded fetching of session costs in the budget check, and a fix to graph query response parsing in the cycle detection path.

Get started

There is no public install path. The repository states plainly that it is a ruvnet only control plane, so treat it as source to read rather than software to deploy.

No documented public package, CLI or MCP server. Read the ADR index if you want the design; do not expect a supported install.

Use it today

Practical case for anyone building something similar: copy the failure modes, not the code. Budget checks that fan out concurrently, nonces that cannot be replayed, and cycle detection on the relationship graph are all problems you will hit.

Acceptance test for your own system: replay a valid nonce immediately after it was accepted. The second attempt must fail.

Push it further

Experimental commentary. An agent workforce needs the boring parts of a company — identity, budget, authority — before it needs more capability. The dependency is human attestation: something must anchor authority outside the agent graph.

Falsifiable test: remove the human attestation step in a sandbox and see how far an agent can escalate. That distance is your exposure.