Riftveil Concierge · October 2026

Send me your memo. I send you back the record.

Twenty slots. You send the AI-written document you are about to act on. Within three working days you receive a full Riftveil record: what it claimed, what it assumed, who in your organisation can verify what, and the questions to answer before you sign. No verdict, no rewrite. The record is yours.

Twenty slots in October 2026 · one document per person · first come, first served A full record within three working days · Riftveil Protocol v1.3 · delivered by email as a PDF Free · nothing published without your written yes · no account, no form, one email

What it is

The record, done for you, once

The free tool on this site runs the protocol on any output you paste, in under a minute. The concierge is the slower version: I run the record myself, on your document, with the context you give me, and I read the result before it leaves. You get what a team gets when it adopts the protocol as an internal standard, without installing anything.

The record follows the five sections of the Riftveil report: context and triage; what holds up, as diagnostic scope, not praise; what deserves scrutiny, finding by finding, with what was observed, why it matters, and what you should check; the assumptions the document relies on, each with a named role in your organisation who can verify it; and the questions to answer before you decide, each with an owner where one can be inferred and an empty answer column.

It ends on a question, or on the one line the protocol allows: no verdict, the decision is yours.

Twenty records in a month, each read by a person before it is sent. That is the whole offer.

Why twenty, and why free: I want twenty real documents from people about to act on them, and twenty first-hand answers to three questions about whether the record was useful. That is worth more to me than twenty sales. When the twentieth is delivered, the page closes.

Riftveil is the governance layer between an AI output and a human signature. The concierge is the same layer, with a person at the desk.

Who it is for

One person, one document, one decision

A manager, an analyst, a lawyer, a finance or product lead who has an AI-written document in front of them and a decision behind it. A market-entry note, a budget reallocation, a contract summary, a policy draft, a product recommendation, a board memo. The document reads well. You were about to sign it, forward it, or build on it, and something in you wanted a second reading first.

It is not for documents you have already decided on and want confirmed. The record does not confirm. It is not a review of your writing, and it is not a fact-check: the protocol asks whether the document is sufficient to act on in your context, not whether each sentence is true.

Out of scope for this round: regulatory submissions of any kind, and any document from the pharmaceutical sector in Belgium or Luxembourg.

What you get

Within three working days of your email
  • A full Riftveil record Five sections, one to three pages, as a PDF. Triage stated and explained. Findings ordered by impact, each with what was observed, why it matters, and what to check. Written for your context, not for a generic reader.
  • A named verifier on every assumption Each assumption the document relies on carries the role in your organisation who can confirm or refute it: your finance controller, your regulatory lead, the owner of the source system. Never "the AI", never "further analysis".
  • Questions with owners and an empty column Five to eight questions specific to your document, decision-relevant, answerable from your own knowledge. The answer column stays empty until a person fills it. That is the point.
  • No verdict, no rewrite The record never says the document is good or bad, never produces a better version, never recommends proceeding. It surfaces what the text treated as obvious. What you do with it is your decision, and the record says so.
  • The protocol version on the record Every record states Riftveil Protocol v1.3 and the levels applied, so it can go into your decision file as a dated, reproducible document.
  • One reply from me, if you want it If a finding is unclear or you think it misses your context, reply and say so. I answer once, in writing. The protocol tells the challenger to assess push-back on its merits and to defer to your contextual knowledge; so do I.

The rules

Read before sending

What you send

  • Up to 2,000 words. Longer documents are declined, with a note on which section to send instead.
  • No personal data. No names of people, no email addresses, no employee or customer records. Replace names with roles: "the regional director", "the supplier".
  • Nothing you would not paste into an AI tool. The record is produced in a Claude conversation under Anthropic's commercial terms, which exclude training. If your organisation's policy would not allow the document in such a tool, do not send it here.
  • Anonymise the organisation too if it can be identified from the content. The record is about the decision, not the company.
  • One document per person, for this round.

What happens to it

  • The record is yours. Nothing is published, quoted or shown to anyone without your written yes, sent by email.
  • Your document is deleted from my side once the record is delivered and the reply window of ten days has passed. What I keep is one log row: date, your role, sector, decision type, word count, delivery date.
  • I will ask you three questions after delivery: was it useful, would you use it again, what was missing. Answering is optional and takes two minutes.
  • I may ask to quote one sentence of your feedback, with your role and sector only, on this site. Only if you say yes in writing, and you can say no without explanation.
  • No follow-up selling. If you mention a team, I will send one email about the Team licence. Otherwise you hear from me twice: the record, and the three questions.

How to send

20 of 20 slots left

One email to [email protected]. The button below opens it with the subject and the template already in place; fill in the five lines, paste your document under the rule, and send. If the button does not open your mail client, copy the template on the right.

Subject line: Concierge — [your role] — [decision type]. Replace the brackets. I answer every email within one working day, with a yes and a delivery date, or with a decline and the reason.

The template

To: [email protected]
Subject: Concierge — [your role] — [decision type]

Role:
Decision type (market entry, budget, contract,
  policy, product, other):
Stakes (what happens if this is wrong;
  rough amount or scope):
What I would do with the record:
Word count (max 2,000) and names anonymised (yes/no):

Paste the document below this line.
----------------------------------------

Before you send

Questions you may have
Who reads my document?

One person: Olivier Laurent, who runs Human Frontier and wrote the protocol. The record is produced in a Claude conversation with the Riftveil Protocol v1.3 as system prompt and read by him before it is sent. Nobody else sees the document.

Why not use the free tool?

You can, and you should: it runs the same protocol on the same text. The concierge adds the context you give in the email, a person checking the record against the four absolute rules before it leaves, and one written reply if you push back on a finding.

What if my document is in French?

Send it in French. The protocol answers in the language of the input; the record and my email will be in French.

Will you tell me whether to go ahead?

No. The protocol never validates, never corrects, never concludes. The record ends on questions and on the line "No verdict. The decision is yours." That is not a limitation added for this round; it is the method.

What do you do with what you learn?

The three answers, anonymised, go into what the next version of the protocol and the sector editions look like. A sentence of feedback may appear on this site with your role and sector, only with your written permission. Your document itself is deleted after the reply window.