THE HEART AI FOUNDATION

HEART makes governance requirements verifiable.

Public-interest infrastructure for turning laws, standards, policies, and institutional governance into evidence-backed, bounded determinations—without replacing the authorities that created those requirements.

Why HEART HEART Standard v2.0 Profiles
HEART is a common operational grammar for plural governance. It translates an applicable requirement into a verifiable condition, identifies sufficient evidence, defines a verification rule, and records a bounded determination under seven constitutional protections.
How HEART works
ApplicabilityIdentify the subject, governing source, context, scope, time, and exclusions.
RequirementPreserve what the governing authority actually requires and its normative force.
Verifiable conditionState what must be true in operational reality without adding a hidden implementation mandate.
EvidenceUse existing sufficient evidence first; preserve provenance, scope, currency, integrity, and uncertainty.
Verification ruleDefine how the evidence will be evaluated, including competence and failure conditions.
DeterminationReport a scoped result that never claims more than the source, evidence, method, and authority support.
Small normative core
The Seven Axioms, HEART Standard v2.0, Profile architecture, and a bounded conformity Scheme—not a mandatory method stack.
Context through Profiles
Source, Domain, and Deployment Profiles preserve legal, regional, scientific, technical, and operational context.
Assurance only where needed
Ordinary verification comes first. Specialists, Guardians, formal Scheme decisions, HVCs, and Registry status are separately governed.
Plural methods
Existing evidence and external methods remain first-class. Foundation methods are conditional tools with explicit claim ceilings.
Federated legitimacy
Regional Federated Entities can localize authority and operations without forking the constitutional and interoperability core.
Public-interest stewardship
The Foundation stewards common infrastructure under Charter v3.0, anti-capture rules, scientific integrity, and public/commercial separation.
Current constitutional and standards roots

Seven Axioms v3.0

Seven co-equal, non-compensatory protections governing every HEART claim and institutional act.

Constitutional layer

HEART Standard v2.0

The universal grammar for applicability, operationalization, evidence, verification, and determination.

Read the explainer

Profile Specification v1.0

The versioned extensibility architecture for changing sources, domains, deployments, and modalities.

Understand Profiles

Conformity Scheme v1.0

The separate rules for official HEART-branded conformity decisions, credentials, status, complaints, and appeals.

Understand the Scheme
Current operating boundary

The specifications are active. Public certification intake, production HVC issuance, and a production HEART Registry are not represented as live merely because their governing documents exist. Current public status must be verified through an authorized Registry once its production gate is satisfied.

Methods and research

RCTA/BGF, GTE, MAP-States, Behavioral Oracle, the AI Behavioral Evidence Review Toolkit, Agentic Workflow Forensics, SCOPA, ABTF, and TRACE remain available when they fit the evidence problem. None is universal simply because the Foundation created it.

Browse methods by purpose, applicability, validation state, and claim ceiling.

Public / commercial boundary

HeartCore Ventures, Dwell, EMPI House, and related commercial implementations are structurally separate. They receive no preferential standards authority, Profile, assessment, decision, credential, Registry treatment, or access.