TwinEthos home

Docs

TwinEthos with your compliance tools

Keep the tools you have. Compliance platforms check your management system and your cloud. AI-law trackers tell you what law exists. TwinEthos tells your coding agent what the law asks of this code, in each market, and the guard to add. The guard it adds is something your other tools can then record as evidence.

What each kind of tool answers and looks at
Compliance toolCompliance functionLooks at
A compliance platformAre our controls, policies and evidence in place for an audit?Your company's systems, people and policies
A cloud compliance toolHow are our cloud services and the services connected to them configured against a framework?Your cloud tenant's settings and signals
An AI-law trackerWhich AI laws exist, where, and when do they start?The law, one instrument at a time
TwinEthosWhat must this AI feature do in each market, and which guard closes the gap?Your code, provision by provision

With a compliance platform

These platforms collect evidence that your controls are in place: access reviews, branch protection, policies, vendor reviews. Several now offer AI frameworks, such as the EU AI Act, ISO/IEC 42001 and the NIST AI RMF, as sets of controls and policies.

TwinEthos works one level down, in the code. Your coding agent asks which provisions an AI feature triggers in your markets, including US state law, and gets the guard to add and what to look for in the code. The pull request that adds the guard, with the rule id and the provision it cites, is evidence you can attach to the matching control.

With a cloud compliance tool

Cloud compliance tools assess your cloud tenant, and the services you connect to it, against regulatory templates. Some now include AI frameworks, such as the EU AI Act, ISO/IEC 42001 and the NIST AI RMF.

TwinEthos looks at your application's code instead. It covers AI law in the markets you sell to, including US states, China and Korea, and tells the coding agent what to add. Use the cloud tool for the tenant and TwinEthos for the code your team writes on top of it. TwinEthos's findings are not a guarantee of compliance: they are evidence for your team and your counsel.

With an AI-law tracker

A tracker tells you which laws exist, their status and their dates, and some now quote the obligations. TwinEthos starts from the same official text and adds what a coding agent needs: who each duty applies to, how to tell from the code whether it is met, and the guard to add. Use the tracker to follow the law and TwinEthos to act on it in code.

How the pieces connect

  1. Plan. Before building, the agent calls build_plan for the few guards that cover the most rules in your markets, and coming_into_force for the dates ahead.
  2. Build and review. On each pull request that touches AI code, the agent calls review_checklist and reports each item with file:line evidence, the rule id and the guard to add (see the AGENTS.md block).
  3. Record. The merged guard, the rule id, the provision's citation and the date of the data (data_as_of) go into the evidence your compliance platform already keeps.
  4. Stay current. changes_since lists what changed in the law data since your last review, so you know which guards to revisit.