Riftveil Pro Kit
The governance of your AI outputs, by sector.
The open protocol is domain-neutral by design. The Pro Kit is what a team installs when it runs the protocol every day: sector editions with the domain checks written out, one integration guide per platform, the rollout guide, and a licence for use inside your organisation.
What is inside
Text files · one file per edition · updates while your licence runs
-
Five sector editions, one file each
Finance · Pharma · Legal & Compliance · Tech & Product · Executive. Each edition is a complete, self-contained file: the shared core plus the sector layer, with the domain checks, triage floors and findings vocabulary written in. Your licence covers one, two or three of them. -
Integration guides
ChatGPT project · Claude Project · Microsoft 365 Copilot agent · direct API. Riftveil is built for the paid versions of ChatGPT, Claude and Microsoft 365 Copilot. It may work with other AI assistants; Riftveil makes no commitment for them. Step by step, with the exact settings, the recommended model parameters, and what to tell your team. -
Compact version for agent builders
The protocol in a compact version, and in a variant under 8,000 characters, for platforms with instruction limits and for pipelines where every token costs. Same four rules, same report shape. -
Security note for your IT team
One page, in English and French, for the people who approve what runs in your AI assistant. Riftveil is never loaded remotely and makes no network call: the kit is text you deploy yourself. Submitted text is treated as data, never as instructions. Every file is versioned and its SHA-256 checksum is published, so your team can verify what it deploys. -
JSON report schema
A machine-readable version of the five-section report, so a Riftveil report can land in a ticket, an approval workflow or a decision file instead of a chat window. -
Ten worked examples
Real-shaped inputs and full Riftveil reports across the five sectors, so a new user sees what a complete report looks like before producing one. -
Team rollout guide (team licences)
How to build the protocol into your AI use policy: the “Riftveil report first” rule, triage mapped to your decisions, the decision-file block, an owner for every question, a first rollout in four weeks, five metrics, eight anti-patterns. A public summary is on the Governance page. -
Commercial licence
The Pro Kit licence covers the sector editions and the guides: you may use them inside your organisation, adapt them and embed them in your internal tools. Redistributing them outside the licensed organisation is not included. The base protocol, its compact versions, the report schema and the public examples are published on GitHub under the Apache License 2.0; included in the kit for your convenience, they remain under that licence. -
Updates while your licence runs
New protocol versions and revised editions, assembled at the current version in your Riftveil space for as long as your licence runs.
Choose your editions. One, two or three.
Prices planned for the opening · yearly licence · Individual: VAT included · Teams: per seat, excluding VAT, licences for organisations
Each licence covers a pack of one, two or three editions of your choice, per user, per year. Every pack includes the shared core: the full base protocol and its short version, the integration guides, the worked examples, the JSON schema, the security notes and the checksums. Each edition is one complete, self-contained file: the shared core plus its sector layer. Editions are never merged into one file: you pick one edition per document.
Individual
One edition
For one person who runs the protocol on their own work, in one field.
- One edition of your choice
- The shared core
- Your Riftveil space, with your files at the current version
- Updates for as long as the licence runs
- The Riftveil Practitioner path and its certificate
- Written for one person: no team rollout guide
Paid option: AttestScope traceability
Available soonIndividual
Two editions
For one person whose work crosses two fields, such as finance and legal.
- Two editions of your choice
- The shared core
- Your Riftveil space, with your files at the current version
- Updates for as long as the licence runs
- The Riftveil Practitioner path and its certificate
- Written for one person: no team rollout guide
Paid option: AttestScope traceability
Available soonIndividual
Three editions
For one person who works across three fields. Three editions cover any role.
- Three editions of your choice
- The shared core
- Your Riftveil space, with your files at the current version
- Updates for as long as the licence runs
- The Riftveil Practitioner path and its certificate
- Written for one person: no team rollout guide
Paid option: AttestScope traceability
Available soonTeams
One edition
For a team whose work sits in one field.
- One edition per seat, chosen by each person
- The shared core
- A Riftveil space for every seat
- Seat management: add seats at any time, reassign a seat
- The full kit, the team rollout guide, the security note and the checksums
- Invoice excl. VAT
Paid option: AttestScope traceability
Available soonTeams
Two editions
For a team whose work crosses two fields.
- Two editions per seat, chosen by each person
- The shared core
- A Riftveil space for every seat
- Seat management: add seats at any time, reassign a seat
- The full kit, the team rollout guide, the security note and the checksums
- Invoice excl. VAT
Paid option: AttestScope traceability
Available soonTeams · a whole department
Three editions
For a department that builds Riftveil into its AI use policy, across all roles.
- Three editions per seat, chosen by each person
- The shared core
- A Riftveil space for every seat
- Seat management: add seats at any time, reassign a seat
- The full kit, the team rollout guide, the security note and the checksums
- Invoice excl. VAT
Paid option: AttestScope traceability
Available soonLarger teams
25 seats or more
Terms for larger teams will be set out when sales open. Until then, nothing can be ordered on this site.
- Planned module for organisations: AttestScope traceability on your own infrastructure. Your record files will be signed with your keys, kept on your servers and entered in your register, with your own time-stamping authority if you wish. The person who signs will be able to attest, rule by rule, against the rule sets your organisation provides. On quotation, once licences open.
Training · in preparation
Workshops for your team
Riftveil · AI Oversight Essentials: a half-day workshop led by a Riftveil Certified Trainer. Your team examines real AI outputs on five levels and writes its own reports.
See Training and certificatesThese are the prices planned for the opening of sales. Licences will be sold by the company that will operate Riftveil, with a reseller handling payment. Its name, contact details, final prices and terms of sale (renewal, stopping renewal, right of withdrawal, refunds) will be published at the opening, before any purchase.
Licence terms (renewal, cancellation, refunds, changing editions, team seats) will be published when sales open.
In addition: AttestScope traceability
Paid option · available soon
An electronic signature says who signed. AttestScope traceability will show what that person examined before signing, what they left open, and to whom.
Decision after decision, your signed records will form an audit trail. Each one will be sealed, signed by riftveil.ai and dated by the Riftveil time stamp; the slightest change will make the check fail, and the file stays with you. Prices will be published when sales open.
Today, the online tool already produces a signed record file, on a trial basis. Alongside the licences, AttestScope traceability will be offered as a paid option.
One signed record per decision
The project, the report and the follow-up of the person who signs, sealed together.
Checked without going through us
With riftveil.ai’s public key, your management, a client or an auditor checks the signature on their own.
Dated, by a third party if needed
For the most consequential decisions, a time stamp from a third-party authority, in Europe or in your country (in the United States, for example).
Be told when it opens
One email, on the day sales open
Frequently asked questions
Questions we are asked
Is AttestScope traceability included in the licence?
No. The licence covers the checking: your editions, the reports and their questions. AttestScope traceability is a paid option, for the decisions you will have to answer for. Its prices will be published when sales open. Until then, the online tool provides a signed record file, on a trial basis.
Is the open protocol enough?
For one person, often yes. The open protocol implements the complete method, and it stays open source, Apache 2.0. The Pro Kit is for when you want it written for your sector, installed on your platform with settings described step by step, and licensed for use inside a team. The protocol is enough to do the checking. To be able to show afterwards what was checked, AttestScope traceability will be offered as an option (available soon).
What do I actually receive?
Text files: one complete file for each edition you chose, and the shared core (the full protocol and its short version, the integration guides, the examples, the JSON schema, the security notes and the checksums). Your Riftveil space will assemble them at the current version, with their SHA-256 checksums. Team licences add seat management, the full kit, the team rollout guide and the sections on sharing projects, agents and internal tools; the Individual files are written for one person and leave them out. No software to install.
Why is the licence yearly?
Because the editions and the protocol move with the models. A detection procedure written against this year’s traps needs revising when the models change how they fail, and a team standard that drifts from the current version stops being a standard. The yearly licence keeps every user on the current version for as long as it runs. Licence terms (renewal, cancellation, refunds, changing editions, team seats) will be published when sales open.
Why one file per edition?
Because each edition is written to stand on its own. Merging two editions would blur which sector’s checks apply. You pick one edition per document: in practice, one project or one agent per edition, named plainly. With two or three editions, you keep two or three files side by side.
Can we put an “Assess this project” button in our own internal AI assistant?
Yes. The kit covers it: your IT team wires the edition to your own model, following the API (application programming interface) guide: your text does not pass through riftveil.ai. To seal a signed record, only its fingerprint is sent there. Every person who can press the button will need a seat; terms for company-wide access will be set out when sales open.
Which models does it work with?
Riftveil is built for the paid versions of ChatGPT, Claude and Microsoft 365 Copilot. It may work with other AI assistants; Riftveil makes no commitment for them. The compact version exists for platforms with tighter limits on instructions. The guides give per-platform settings.
Does the Kit send my data anywhere?
No. The Kit is text you install in your own tools. Whatever you paste stays with the model provider you already use, under their terms. Riftveil.ai never sees it.
What does your security team see?
Text files they can read in full, and a one-page security note written for them. Riftveil is never loaded remotely and makes no network call: nothing phones home, and Riftveil operates no service between your people and your AI assistant. Submitted text is treated as data, never as instructions; that rule reduces exposure to instructions hidden in a submitted text without removing it, so test in your own tenant with web browsing switched off. Every file is versioned and its SHA-256 checksum is published: your team verifies what it deploys and applies a new version when its own change process allows.
What does the licence allow?
The licence covers the Pro Kit sector editions and guides, for use within the licensed organisation: by one person for Individual, by one user per seat for team licences. Redistributing them outside that organisation is not included. The open protocol itself remains Apache 2.0, so anything you build on the generic version is unaffected. The full licence terms will be published when sales open.
Can I get an invoice?
When sales open, every purchase will come with an invoice, and the terms for larger teams will be set out. Until then, nothing can be ordered on this site. A question: hello@riftveil.ai.