FRAMEWORKS
Frameworks organize governance activity, but they do not all carry the same authority, scope, evidence expectations, or operational depth. This library preserves those differences and shows how each framework can be translated into reviewable TA-14 governance routes.
WHAT A FRAMEWORK IS
A framework can define functions, domains, practices, outcomes, questions, controls, tests, or review steps. It may guide an organization without creating legal duties by itself. The library keeps frameworks distinct from laws, regulations, standards, principles, certifications, and independent assurance.
FRAMEWORK CATALOG
Each module preserves source identity, intended use, authority, scope, lifecycle coverage, evidence expectations, relationships, known limitations, and TA-14 implementation pathways.
NIST AI RMF
National Institute of Standards and Technology
Voluntary framework
A structured approach for identifying, measuring, managing, and governing risks associated with artificial intelligence systems.
Open framework module→AI Verify
Infocomm Media Development Authority of Singapore
Testing and governance framework
A testing-oriented governance framework that connects responsible AI principles with technical tests, process checks, and evidence.
Open framework module→RAI
Multiple organizations
Organization-defined frameworks
A family of governance approaches that organize principles, policies, controls, reviews, and accountability around responsible AI development and use.
Open framework module→AI Risk
Organizations and assurance bodies
Internal or advisory framework
Enterprise structures that connect AI inventories, ownership, risk classification, controls, monitoring, incidents, and executive oversight.
Open framework module→COMPARISON ENGINE
Two frameworks may use similar words while governing different risks, actors, evidence, or lifecycle stages. Comparison should expose both overlap and boundary rather than flattening distinct systems into a false equivalence.
Open Framework ComparisonFROM FRAMEWORK TO ROUTE
A framework becomes operational only when its expectations are connected to identity, evidence, authority, continuity, decision logic, bindings, commitments, execution boundaries, and outcome records.
BOUNDARY
A framework can organize work, but it does not automatically prove that requirements were met, evidence was admissible, authority was valid, controls operated as intended, or outcomes corresponded to the committed route. TA-14 preserves those questions separately.
Live cumulative activity recorded across the public Exchange surface.