Mayo D. Tubbs
Operations Engineer Senior Staff · 43 years
Latterly led enterprise strategic sourcing for Lockheed Martin Aeronautics, building the process that decides which suppliers the company relies on.
About us
At the intersection of human and machine
TEKIMAX is a Fort Worth software company. We build AI systems that stay inside the limits the people running them set, because most tools built around AI quietly take the human out of the loop.
The obvious objection is that a human in the loop slows everything down. It would, if you put one on every step, so ALOS does not. Reversible work runs without waiting. Only what cannot be undone stops for a named human.
How it works
The rules are a document both sides can read.
A governance policy usually lives in a slide deck, and a machine cannot check a slide deck. So the rules a project is held to are written as something that compiles, and the same file is the thing a person reads and the thing the platform measures against.
It compiles, or it is refused
A playbook names the controls a kind of work requires and puts them in order. Eight checks run before it is allowed to exist: a control the catalogue does not carry, a requirement nothing could ever satisfy, a step waiting on a later step, a phase left empty so it reads as finished. A playbook that fails comes back with the reasons, one per cause, and nothing is saved. The same refusal a compiler gives you, for the same reason: a set of rules nobody could satisfy should not be handed to a team as though they could.
It is measured from the work, not from a questionnaire
Gates read the records the project already produced. Nobody is asked to attest to something a system can see for itself, and where a human judgement is genuinely required, it is a named person signing rather than a tick in a box.
It leaves in a format we did not invent
A playbook exports as OSCAL, the format NIST publishes for control catalogues and the tailored subsets an organisation adopts. Two documents together, the catalogue and what this playbook selects from it, in JSON or YAML. Work done here is not stuck here, and a reviewer who has never heard of us can open it.
And the boundary is stated, not blurred
The playbook measures. What refuses at the moment of action is the tool gate: role, reversibility and tenant checked on every call, with anything irreversible queued for a person rather than performed. A playbook does not block an action, and we say so on the product's own pages rather than letting somebody assume otherwise.
The team
Who we are
Christian KamanChief Executive Officer
Tony Chung, MBASenior Director of Capture and Programs
Jacob HolleDirector of Defense and Public Sector Growth
Kailey ScheinCommunications and Marketing
Advisors
Our board of advisors
People outside the company who see the work and say what they think of it.
Drew Santaniello, CPA
Global finance, SaaS and technology
A finance executive who has taken SaaS and technology companies from startup to global scale, building the remote teams and the systems that hold once a company is running in several countries at once. Previously at WHOOP.
Work with us, or come and learn
If you are weighing us up, the fastest way through is a conversation about your own work rather than a demo of ours.