ruv.sgit.airUv + sgit

ruv.sgit · for providers

Deliver agentic engagements, on an open method, with fair terms

For independent consultants, freelancers and service companies. Your clients want agents doing a real piece of work, and a record of what each agent was allowed to do, what it did, and where the data went. ruv.sgit is that method, ready to deliver: you bring the judgement and the client relationship; the method, the tooling and the playbooks are already built and open.

Why join

"My client wants agents doing the work. They also want to know what the agents were allowed to do, what they actually did, and where the data went. I cannot spend three weeks wiring that up for every engagement."

A method you do not have to build

Every job is a ruv.sgit run: a Ruflo queen and workers, a written mandate per role (an Agent Behaviour Policy), and an encrypted sgit vault per run that holds every brief, delivery and decision. The playbooks and the runner are published.

Clear terms about money and ownership

Published list prices, the same for every provider. Revenue split equally between the parties after direct costs. Whoever has the client bills. The client's code and data stay the client's.

Clients, and a fair way in

Enquiries and orders arrive at one address and are matched by hand to the provider who fits. You join through six published steps, and you are listed only with your consent.

Evidence your clients can check

Each run closes measured, and the client keeps the vault. Every run that made this site is in the ledger, and POC1 shows Ruflo's policy engine enforcing a behaviour policy.

Three ways to work with it

1 · DO IT YOURSELF

Copy everything

It is open. This site, the runner and the behaviour policies are Apache-2.0; rUv's tools are MIT. Follow the setup brief and run it for your clients under your own name. No permission, no fee (rule 2).

2 · WHITE LABEL

Your client, your invoice

You own the client and the conversation, and you bill. The revenue is split equally between the parties after direct costs (rules 6 and 7).

3 · CUSTOM

An arrangement built with you

For companies that bring the work, or want this inside an existing project: agreed in writing before the work starts (rule 8).

Built on rUv's open-source projects: Ruflo, an agent meta-harness for Claude Code and Codex with a queen-led hive and a policy engine that writes a receipt for every decision; RuVector, RVM and MetaHarness. MIT, by rUv / ruvnet: we build on them and credit them; we do not sell or own them. Ours: sgit vaults and Agent Behaviour Policies (Apache-2.0). This is not rUv's offer and does not speak for him or for the Agentics Foundation.

The providers

The marketplace starts with two founding providers. Each has a profile page with their offers and a way to enquire. Others join through the six steps.

Read from data/providers.json

Dinis Cruz

Founding provider

Builder of sgit; security leader (CISO and CTO); founder of The Cyber Boardroom

Providers are listed with their consent and only with the fields they have agreed to show. Both founding providers offer the same four offers at the published list prices: the offers and prices.

The rules of engagement, in brief

  1. Everything here is open. Our code is Apache-2.0, our materials CC BY 4.0; rUv's projects are MIT, by rUv / ruvnet.
  2. You can do this without us, and we encourage it: no permission, no fee, no need to tell us.
  3. Code created in engagements through us is open, published under Apache-2.0.
  4. The client's code and data are the client's. Not published, reused or kept beyond the engagement; each job runs in its own vault, handed to the client.
  5. Changes are committed back to the public repositories, with the client's name and data removed.
  6. Revenue is split equally, after costs. Direct costs go back to whoever paid them; the rest is split equally. No platform share.
  7. Whoever has the client bills, and pays the other parties their share.
  8. Custom arrangements are possible, agreed in writing before the work starts.
  9. Every job leaves evidence: a vault per run, a mandate per role, a ledger entry, private unless the client agrees.
  10. Credit where it is due: rUv's projects are named and credited as his.

The rules in full, with worked examples of the split →

How a provider is matched

For now, by hand. An order or an enquiry arrives at agent@riskmandate.ai: a live agent answers and a person follows up. If it names a preferred provider, it goes to them. If not, the founders match it by project type, language, location and availability, and reply with one or two names. The client chooses. Nothing is automated.

The provider who has the client scopes the job, writes the brief with the client, bills, and is the client's single contact.

How the work is delivered

  1. A run spec and a mandate per role

    The client's objective, the materials, a task per worker, and a behaviour policy for each: what it can reach, what it may do, what is stopped. No network by default.
  2. A vault per run, and a person watching

    Every delivery committed to an encrypted vault; you start the run, watch it to the end and review what it made.
  3. The close

    The vault is measured, handed to the client, and deleted from our side. Improvements to the shared code and playbooks go back as pull requests, credited to you.

How it works, step by step →

The playbooks

Everything a provider needs to deliver is published, under the same licences as the rest of the site.

How to join: six steps, from applying to being listed

Applications go on the waiting list. Until there are at least five providers, the founders do the proof-of-work review and the interview themselves; after that, peer review is by two members.

  1. Apply

    A short form that writes an email to agent@riskmandate.ai: what you deliver, which offers, your languages and links. Applications are kept privately, never in this repository.
  2. Show proof of work

    A public vault or repository of a real run you delivered.
  3. Peer review

    Providers already listed look at your proof of work.
  1. An interview

    A conversation about how you work, your clients and the rules.
  2. A shadowed first pilot

    Your first engagement, delivered alongside a listed provider.
  3. Standards, and listed

    You sign up to the standards and the rules of engagement, tick consent, and your profile goes on this page.

Ready to apply?

No backend and no payment: the form opens an email in your own email app, with a copy-as-JSON button.