Namus reads your code, infrastructure and policy in place, then returns a control-by-control compliance record for Texas TRAIGA.
say they have an AI governance framework
have implemented the controls it calls for
One control, one rule, one system, and what the code actually says about it.
Works with Bedrock, Vertex AI, Azure OpenAI, LangChain, LangGraph, Crew AI, HuggingFace and OpenAI API.
Namus reads what your system is written to do, from source, infrastructure and policy documents. A gap is not a claim that something failed in production, and it is not a failure of your team. It is a finding with a fix, and the clause it maps to.
Frameworks and statutes ask for overlapping things in different words. You answer the requirement once.
Your source, IaC and configuration, checked control by control against what each rule requires.
Findings ship with the artifacts behind them and export as OSCAL. No new system of record.
The analysis runs inside your environment, under your access controls. Namus receives aggregate gap counts and nothing else.
The evidence exists. It is spread across repositories, consoles and people's memories, and someone has to go and collect it by hand every cycle.
Run it on the release, not on the audit. Evidence produced once a year is accurate on the day it is written and drifting by the time anyone reads it.
We only cover AI. If SOC 2 is what you need, we know people who do it well.
High-risk obligations, Art. 9 to 15. Annex IV documentation.
Govern, Map, Measure and Manage at subcategory level.
AI management system controls and Annex A.
Domain-level AI control implementation.
Application-layer AI risk in production.
Six domains, 130 controls, independently audited.
HB 149. Prohibited uses and disclosure duties, since January 2026.
Frontier model transparency and safety reporting.
AI in employment, under the Human Rights Act.
Bias audits for employment decision tools.
SB 149, as amended. Generative AI disclosure.
Training data provenance disclosure for generative systems.
Safety protocols and 72-hour incident reporting.
Automated decision-making. Replaced SB 24-205.
State law moves faster than any control catalog. Take Colorado. SB 24-205 passed in 2024, was delayed twice, then repealed and replaced before it took effect. One control set means a statute change re-points a clause reference rather than restarting your program.
Request a free baseline assessment below. You pick your highest-stakes AI system, we run it against the rules that apply, and you keep the record.
Design-partner engagements are limited while we build. If your system is out of scope we will say so on the call.