Controlled documents, signed by the right people, with a history an auditor can follow.
A named reviewer and a named approver on every document. Nobody signs off their own work. Every version keeps a record, and if anyone changes it later, it shows.
In early use with a regulated software company.
The auditor asks who approved this version, and the answer is a search.
- The quality system lives in a wiki and an inbox.
- The approver is the author.
- Version history is a filename.
- Nobody can show that the approved version is the one still in the folder.
- The evidence exists, but assembling it takes a week of somebody senior.
A signature is only worth what it was signed against. This binds the two together.
In. Build. Leave. Prove.
One job, four weeks, in production. Then it keeps proving itself.
In
Your documents, your roles, and who may review and who may approve.
Build
We ingest the set and wire the review flow to where your team already writes.
Leave
Your team reviews and approves in it. Approval is blocked unless verification passes.
Prove
Every version keeps who reviewed, who approved, when, and what they signed.
What you get.
- Your document set under review and approval, with named people on both sides.
- Roles enforced: the reviewer is never the approver, and nobody approves their own work.
- A signed history per version, showing name, time and what was signed.
- Verification that re-checks the approved content, so a later change shows.
- An export an auditor can read.
Who approved this version, on what evidence, and has it changed since?
What the AI is allowed to do is written down first.
Every decision is checked against those rules before it happens.
A named person signs it off. The check produces the evidence; a person judges.
You can replay the whole history any day and get the same answer.
If anyone changes it later, it shows. Patent pending, UK application GB2620101.2.
That is what a deployment leaves running for your job. In the accessibility product today, a person on your team accepts every finding before it reaches your record.
Who this is for.
- Medtech and other regulated software teams with a quality system to keep.
- Teams whose notified body, auditor or customer asks for approval history.
- Quality managers who assemble evidence by hand today.
Not for
General document storage. This is the sign-off, not the filing cabinet.
Two people, on every call and in your standup.
Simon Milner, Founding Architect
He designed the record: what the AI is allowed to do, checked before it acts, and replayable afterwards. Twenty-five years in Silicon Valley before that.
Jason Crispin, Founder
He owns the customer side of every deployment: what the job is, what it is worth, and that it lands. He is on the first call and every one after.
Patent pending, UK application GB2620101.2. Meet the team
What people ask.
Is this a quality management system?
Is this a quality management system?
It is the sign-off and record layer of one. It holds who reviewed a document, who approved it, when, and what exactly they signed. It does not try to be your whole quality system.
Does it replace our wiki?
Does it replace our wiki?
No. You keep writing where you write. What changes is that a version is reviewed and approved by named people, and that the approved version is bound to its content.
Can our auditor or notified body see it?
Can our auditor or notified body see it?
You can show them the history for any version: who reviewed it, who approved it, when, and whether the content still matches what was signed. There is no separate external login today, so today that means showing it with them in the room.
Who can approve?
Who can approve?
Only the people you name. The reviewer is never the approver, and nobody approves their own work. Approval is refused unless the latest verification passes.
What does it cost?
What does it cost?
Scoped on the call. It is in early use, so we set it up with you.
Want to see it on your own documents?
Thirty minutes with Simon and Jason. Bring the document set and the question your auditor asks, and we will tell you what it would take.