What is enforced, and what is not yet answered
This is the page to forward to your IT function. It states what the build enforces, it claims no certification, and it does not guess at the answers it does not have.
Properties of the build
Access is enforced at the database
Every table carries row level security. Permission is checked where the data lives, not in the screen that displays it, so a bug in the interface cannot show somebody a work paper their session should not see.
Assessments are append only
A correction is a new record, not an overwrite. The earlier record stays readable, so the history of a judgement is part of the file.
Work paper events are hash chained
Each event carries an actor, a timestamp and a digest that covers the event before it. The chain can be verified on screen, and a verification states how many events it checked.
Jurisdiction packs are marked provisional
The product says on screen which pack is in force and that its content is provisional pending counsel review.
What this page does not claim
No certification is claimed on this page. If a certificate is not shown to you, treat it as one that does not exist.
No uptime figure is published, because publishing a number that nothing measures is the same as making it up.
No client is named, because naming one without written permission is not ours to do.
Answered on the call, not here
These are the questions your IT function will ask. They get a straight answer from somebody who knows, rather than a paragraph written to sound reassuring.
- Where data is hosted, and what the self hosting option on your own infrastructure involves.
- How tenants are isolated from one another.
- Who at Uhuru AI can access client data, and under what conditions.
- The backup and recovery position.
- The incident contact and what happens when you use it.
- What is not yet in place.