
Research
Vektra Research.
Before machines go where people can’t, we work out how they should behave around people when things go wrong, write it down as an open protocol, and prove each rule in code.
Why research leads
Machines will act where people can’t reach them.
Collapsed buildings, blackouts, orbit, Mars with minutes of signal delay. No shared rulebook says how a machine behaves around people when things go wrong. Most fail open.
Research stays labeled as research until it is proven.
The method
Lessons paid for in lives.
We merge what these fields learned into one protocol, then prove it.
- Aviation
The black box.
Every flight is recorded, so every failure can teach.
- NASA
Flight rules.
Hard calls are decided before the crisis, not during it.
- Nuclear
Fail safe on doubt.
When something is unclear, go to a known safe state.
- Surgery
The time-out.
Stop and confirm before anything that can’t be undone.
- Incident command
One person in command.
Everyone knows who is in charge. Handoffs are clean.
- Submarines
Degraded modes.
Backups for the backups, and a plan for running hurt.

The Vektra Protocol
Thirteen rules. Every one proven, or marked as not yet.
Aviation, spaceflight, nuclear power, surgery, incident command and submarines each learned how to keep people safe the hard way. We merge those lessons into one open rulebook for machines that act around people, then prove each rule in code.
Draft v0.1
Read the full Protocol- P1A named human holds command.
- P2Decide before the crisis.
- P3Start held, fail safe.
- P4Stop always works.
- P5A time-out before the irreversible.
- P6A black box.
- P7Honest status.
- P8Degraded modes.
- P9Lost contact.
- P10Clean handoff.
- P11A hazard register.
- P12Prove it.
- P13Undo where possible.
The proof lives in I.L.O., our kernel.
The Safety Program
Any agent. One set of Laws.
In design
AI agents and models connect to the Vektra Kernel. They start with little awareness and little authority.
A person grants more as trust is earned, and can take it back at any moment.
Vektra Kernel
The gate every agent and model passes through.
Vektra Link
How agents connect: an MCP server, Python and TypeScript SDKs, a model proxy, and later a ROS 2 bridge.
Awareness levels
A0 to A4. A person grants each step and can take it back.
Mind Contract
What the agent is told: the rules, in its own context.
Standing record
Trust earned over time, written down where people can check it.
Vektra Proof
A conformance suite: tests that show whether a system follows the Protocol.
Awareness levels
A0 to A4.
A person grants each step and can take it back.
- A0
Task
Sees only the job in front of it.
- A1
Workspace
Sees the files and tools it was given.
- A2
Your context
Knows your situation, because you allowed it.
- A3
The outside world
Can look beyond your space.
- A4
The mission
Understands the whole mission and the people in it.
Awareness levels are in design. The one-line descriptions are design intent.

Agents earn awareness. Humans grant it. The Laws never move.
Tell the mind, enforce in the kernel.
AI safety
What we commit to.
Humans stay in command. Every system Vektra builds is held to that.
Humans stay in command.
Consequential real-world actions wait for a person’s approval. A human stop is built to always work, and the system is designed to hold safe when it does.
Cognition is untrusted.
Language models are treated as untrusted. I.L.O. is designed to place a small, auditable policy kernel between any model and the world.
Every action leaves a record.
An append-only audit journal with integrity checks, so any operator can reconstruct what happened and why.
Augment, never replace.
Nothing ships that makes the operator dumber, slower, or more dependent on the machine.
Honest status.
We say “in research” when it is in research. No capability claim ships without evidence.
Open for inspection.
Safety-critical code is meant to be read. We are preparing to release it so others can test it and break it.
Safe when degraded.
When signal, power, or the model drops, the system is built to hold, hand back, and say so.
What Vektra will not build.
Surveillance.
Trust is a decision filter. Products built to oppress disqualify themselves.
Autonomy without a stop.
No system that acts in the world without a human able to halt it.
Unearned claims.
No safety claim we cannot show.
Safety and security reports go straight to the founder. Write to security@vektraindustries.com under the responsible disclosure policy.
The agenda
What we study.
- Fail-Open BenchHow often AI safety gates fail open, and why a plain rule beats a model.
- Command under delayWhat a machine may do alone at Mars distances, with minutes between question and answer.
- Approval fatigueKeeping humans sharp, not rubber-stamping.
- One person, many machinesCommand of a whole fleet, across makers, from one place.
- Rules for bodiesCarrying the Protocol into robots: force, speed and zones.
- Human-centered assistanceSupport that keeps operators clear and capable, including neurodivergent operators.
Now, next, later
The path.
- Now0–3 months
- Publish Protocol v0.1.
- Build Vektra Research around it.
- Map every rule to a test.
- Next3–12 months
- The Fail-Open Bench.
- Human Framework v0.1.
- A first Earth pilot, in disaster response or elder care.
- Later
- Robotics.
- Then orbit.

Work with us
Build the safety layer with us.
Partner on a pilot, collaborate on the research, or fund the mission.