Research / Safety
Systems that can be checked.
Every Gytev system is evaluated against the reality it will act on, with a human able to stop it.
Approach
Four rules we do not skip.
They apply before a system is allowed to make a decision that matters.
- 01
Test against the field
Evaluation uses the data and conditions of the deployment, not only a clean validation set.
- 02
Keep a human in the loop
Decisions that affect people or critical resources stay approved by a named operator.
- 03
Log the decisions
Every recommendation keeps its context, its source and the final decision.
- 04
Bound the scope
A model only acts within the scope it was validated for. Outside it, the system stops and raises a flag.
Deployment
Bounded before it is switched on.
A deployment is a defined scope with a named owner, not a model released into the organisation.
- 01
Before
What is agreed:
- The decision the system may support, and the decisions it may not.
- The data it can read, and the records it can write.
- A named operator who approves the output.
- A stop condition and a way back to the previous process.
- 02
During
What is watched:
- Decisions and overrides, with their context, in the audit log.
- Drift between the deployment's data and the evaluation data.
- Incidents and near misses, reviewed with the operator.
- A periodic review that can widen or narrow the scope.
Data & isolation
Isolation is physical.
Each deployment runs on its own database. No foreign key crosses two deployments.
- 01
One database per deployment
The platform directory holds the tenants. Operational records live in the deployment's own database.
- 02
Scoped access
Roles decide what an operator can see and change: administration, operations, field teams, legal guardian.
- 03
Short sessions, full trace
Access tokens expire after 15 minutes. Actions are written to an audit journal with their author.
- 04
Documents from the record
Official acts, reports, certificates and transcripts are generated from the record as PDFs, not retyped.
This page describes what we apply across our systems. It is not an independent audit; we recommend one for any critical deployment.