For Regulators and Public Authorities

Common verification without common government

HEART can translate an applicable public requirement into a Verifiable Condition, Evidence set, Verification Rule, and bounded Determination without replacing the authority that created the requirement. It does not decide legal applicability, compliance, authorization, accreditation, or enforcement unless a competent public source expressly gives it that role.

Source-faithful operationalization

Identify the exact enactment, regulation, guidance, standard, decision, jurisdiction, effective date, and responsible authority.
Preserve the source’s terms, definitions, exceptions, thresholds, roles, and legal effect in a versioned Source Profile.
Compose domain and deployment context without weakening or silently expanding the source.
Specify the requirement-level evidence and rule, including uncertainty and conflicts.
Select competent existing tests, assessors, specialists, or methods.
Produce a determination whose scope and claim ceiling remain visible.
Preserve correction, contest, remedy, source change, and decision lineage.

What HEART does not imply

endorsement by a regulator, standards body, notified body, accreditation body, or government;
legal compliance merely because a HEART requirement is satisfied;
that HEART is a harmonized standard, common specification, or mandated assessment path;
that a Guardian supplies statutory human oversight;
that MAP-States, BGF, GTE, or Behavioral Oracle satisfies a named legal article; or
that an HVC is a license or regulatory authorization.

Current Source Profiles must be individually adopted and listed. The EU Artificial Intelligence Act Source Profile v1.0 is the first current individual Source Profile. It is deliberately bounded: the official source controls, qualified legal review remains necessary, and HEART makes no EU conformity or notified-body claim.

See Source Profiles, Federation, and Contact.