Dinis Cruz
Founding providerBuilder of sgit; security leader (CISO and CTO); founder of The Cyber Boardroom
ruv.sgit · for providers
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.
"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."
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.
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.
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.
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.
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).
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).
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 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
Builder of sgit; security leader (CISO and CTO); founder of The Cyber Boardroom
Enterprise AI leader and agentic systems builder; co-founder, Agentics Foundation London
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.
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.
Everything a provider needs to deliver is published, under the same licences as the rest of the site.
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.
No backend and no payment: the form opens an email in your own email app, with a copy-as-JSON button.