What is a HEART Profile?

A HEART Profile is a versioned standards artifact that adds explicit source, domain, deployment, or modality context without silently changing the stable HEART core.

Is a Domain Profile a Division?

No. A Domain Profile is a versioned standards artifact. A Division is the stewardship program responsible for research, consultation, maintenance, and change proposals in that domain.

HEART Profiles

The extensibility joint of HEART

A HEART Profile is a versioned standards artifact that adds explicit context to HEART Standard v2.0. It is not a separate HEART Standard or certification stack.

Source ProfileWhat a specific law, standard, policy, contract, or other governance authority requires.

Domain ProfileWhat validated domain knowledge and domain-specific protections add within a declared scope.

Deployment ProfileHow the requirements apply to a bounded system, service, model, function, population, place, and operating context.

Modality OverlayAdditional context where voice, text, embodiment, persistence, autonomy, or another interaction mode materially changes evidence or risk.

Verification planThe composed requirements, evidence, methods, competence, and rules for the actual claim.

What every Profile must declare

authority, family, scope, and version;
what it adds, interprets, or selects;
normative source and evidence basis;
research status, uncertainty, and claim ceiling where material;
dependencies and conflicts;
adaptation and review triggers; and
a lifecycle that permits replacement or retirement.

Profiles preserve source fidelity and the Seven Axioms. They may not convert guidance into law, research into fact, or one deployment choice into a universal HEART requirement.

Current public status

The Profile Specification, eight Domain Profiles v1.0, and the EU Artificial Intelligence Act Source Profile v1.0 are current.

The architecture defines Source and Deployment Profile families. No individual Deployment Profile is currently adopted. Every Profile requires its own versioned approval and authority-index entry.

“vNext Profile” is not the durable nomenclature. Use HEART Source Profile, HEART Domain Profile, HEART Deployment Profile, or HEART Modality Overlay.

HEART Deployment Profiles — A Deployment Profile binds applicable requirements and Domain Profiles to a specific system, function, context, population, version, place, and time.

HEART Domain Profiles — Eight current Domain Profiles add research-bounded domain requirements and claim ceilings to the stable HEART core.

HEART Source Profiles — A Source Profile operationalizes one identified governance source while preserving its authority, force, qualifications, conflicts, and change state.