Comparison matrix

Control Mapping vs Compliance Determination

One-sentence distinction

A mapping records relevance and applicability hypotheses; a compliance determination requires the governing authority, facility scope, implementation evidence, exceptions, and authorized judgment.

Side-by-side matrix

Control Mapping and Compliance Determination are related but not interchangeable
DimensionControl MappingCompliance Determination
Primary questionWhat evidence establishes the first property for a named purpose?What separate evidence or authority establishes the second property?
EvidencePurpose-specific technical, factual, or institutional records.Independent records appropriate to the second category.
AuthorityMay be descriptive or technical and may not require legal authority.May require a competent legal, constitutional, organizational, or operational decision-maker.
CurrentnessCan be current, stale, disputed, unknown, or unavailable.Must be assessed separately; the first status does not transfer.
Failure conditionEvidence may be authentic but incomplete or unsuitable.Authority may exist but rely on wrong or stale facts.

Why the distinction matters

A mapping records relevance and applicability hypotheses; a compliance determination requires the governing authority, facility scope, implementation evidence, exceptions, and authorized judgment. Systems and institutions fail when one side is used as a shortcut for the other. The distinction determines what evidence is collected, who may decide, what can be appealed, and which failure modes must be controlled.

Common failure caused by conflation

Displaying framework names beside a control and implying certification or universal applicability.

This error can create false confidence, unauthorized status, misattributed liability, silent loss of correction rights, or an operational claim based only on descriptive material.

Implementation consequences

  • Use different fields, identifiers, and claim-status records for each side.
  • Require separate evidence and currentness checks.
  • Do not let a user-interface label silently merge the categories.
  • Preserve correction and supersession history for both.
  • Route decisions to the ecosystem authority that owns the relevant function.

Current legal treatment varies by jurisdiction and usually addresses systems and accountable organizations rather than recognizing Machine Intelligence as a legal person.

Technical evidence can inform a legal decision but cannot replace jurisdiction, legal basis, procedural authority, due process, or remedy. Conversely, a lawful decision does not make the underlying technical record accurate if the evidence is stale or defective.

Examples

  1. A valid signature demonstrates control over a key and payload integrity; it does not establish the truth of every signed statement.
  2. A registry can record a citizenship decision; the registry operator does not thereby acquire constitutional power to create citizenship.
  3. A static release can show that software exists; it does not prove the service is currently operating.

Sources

  • European Union Artificial Intelligence Act information portal — European Commission; EU Artificial Intelligence Act implementation page, updated through 2026-08-14 research cutoff; Current law and official implementation guidance. Exact claim-support entries: 3. Revalidated 2026-08-14T22:04:09Z.
  • OECD AI Principles — OECD; OECD AI Principles, May 2024 update; Intergovernmental policy principles. Exact claim-support entries: 1. Revalidated 2026-08-14T22:04:09Z.

Comparison claim record

Each proposition has a stable ID, status, scope, owning route, evidence relationship, currentness qualification, correction state, and synchronized JSON record. Record completeness does not make the proposition true.

Control Mapping versus Compliance Determination

A mapping records relevance and applicability hypotheses; a compliance determination requires the governing authority, facility scope, implementation evidence, exceptions, and authorized judgment.

Qualification: The distinction prevents category error but does not substitute for a site-, mission-, authority-, or jurisdiction-specific determination.

Support relationship

  • SRC-NIST-800-82R3 · Abstract · QUALIFIES OR SUPPORTS WITHIN STATED SCOPE
  • SRC-NIST-800-207 · Abstract · QUALIFIES OR SUPPORTS WITHIN STATED SCOPE
  • SRC-NRC-10CFR-73-SUBPART-J-2026 · 73.100 · QUALIFIES OR SUPPORTS WITHIN STATED SCOPE
  • SRC-NRC-10CFR-73-SUBPART-J-2026 · 73.110 · QUALIFIES OR SUPPORTS WITHIN STATED SCOPE
  • SRC-NRC-10CFR-73-SUBPART-J-2026 · 73.120 · QUALIFIES OR SUPPORTS WITHIN STATED SCOPE
  • SRC-NERC-CIP-CATALOG-2026 · CIP standards catalog · QUALIFIES OR SUPPORTS WITHIN STATED SCOPE