A governed record of what an AI governance architecture calls itself, who claims it, what it claims to govern, when the declaration was made, which evidence supports it, and how the record changes over time.
Registration is not certification.The Registry preserves identity, declarations, evidence, provenance, version history, and disputes. It does not determine legal validity, regulatory approval, technical efficacy, ownership priority, or fitness for use.
Persistent identityVersion lineageEvidence traceabilityClaims and non-claimsDispute preservation
THE REGISTRY PRESERVES THE DECLARATION. IT DOES NOT ENDORSE THE DECLARATION.
THE CORE REGISTRY RECORD
A record designed to remain understandable under scrutiny.
Each registration must preserve enough identity, context, limitation, evidence, and history for another person to determine exactly what was declared and what the Registry did—and did not—verify.
01
Identity
Governance name, registry identifier, version, category, steward, and contact route.
02
Scope
What the architecture claims to govern, where it applies, and which actors or systems it covers.
03
Claims
Precisely stated governance, evidence, review, runtime, and execution claims.
04
Non-claims
What the submission does not establish, certify, guarantee, or authorize.
05
Evidence
Supporting publications, repositories, demonstrations, standards mappings, filings, and records.
06
Provenance
Who submitted the record, when it was submitted, what changed, and which source produced each assertion.
07
Lifecycle
Current status, effective dates, previous versions, superseding versions, disputes, withdrawals, and archival state.
08
Rights
Ownership, licensing, attribution, permitted use, confidentiality, and disclosure declarations.
REGISTRY LEGITIMACY CONTROLS
Legitimacy comes from controls, not appearance.
A serious registry must preserve stable identity, provenance, version history, correction routes, transparent status, and clear boundaries between recording a claim and validating it.
01
Persistent identity
Every accepted record receives a stable TA-14 registry identifier that does not change when descriptive metadata is updated.
REQUIRED
02
Immutable event history
Submission, review, amendment, dispute, supersession, withdrawal, and archival events remain visible as a dated chain.
REQUIRED
03
Attributable provenance
Records distinguish the claimant, submitter, steward, reviewer, evidence source, and system-generated events.
REQUIRED
04
Version integrity
Material changes create a new version connected to the prior version rather than silently rewriting history.
REQUIRED
05
Claims and non-claims
Every record separates affirmative claims from limitations so registration cannot be mistaken for certification.
REQUIRED
06
Evidence traceability
Evidence is identified by source, date, relationship, access state, and integrity information where available.
REQUIRED
07
Dispute and correction route
Affected parties can challenge attribution, ownership, scope, evidence, or material accuracy without erasing the original record.
REQUIRED
08
Explicit governance boundary
The Registry preserves declarations and evidence; it does not grant regulatory approval, legal priority, or technical validity.
REQUIRED
PUBLIC STATUS MODEL
No record is forced into a false binary.
The Registry shows where a record is in its lifecycle and preserves adverse events instead of quietly deleting inconvenient history.
SELECTED REGISTRY STATE
Registered
The record has passed registry intake controls and has been assigned a stable public or controlled identifier.
THE REGISTRY CHAIN
Every published record must remain connected to its origin and history.
The chain is designed to make silent substitution, orphaned evidence, unattributed claims, and invisible corrections harder to conceal.
Declaration→
Identity→
Evidence→
Review→
Registration→
Version→
Dispute→
Archive
REFERENCE-INFORMED METHOD
Built from established practices, without pretending to be a government register.
The operating model draws from authoritative documentation, provenance, metadata, lifecycle, and registration concepts. TA-14 remains responsible for its own registry rules, controls, and public representations.
NIST AI RMF
Systematic documentation, defined responsibilities, lifecycle governance, transparency, and accountability.
W3C PROV
Provenance relationships among entities, activities, agents, derivations, and responsibility.
DataCite practice
Consistent metadata, persistent identification, related resources, contributors, dates, and version relationships.
EU AI Act
Registration and transparency concepts for regulated AI systems, while keeping this Registry independent and non-governmental.
THE REGISTRY MAY VERIFY
That required fields were submitted.
That a submitter completed an identity or authority check defined by registry policy.
That cited evidence was accessible at the recorded time.
That the published record matches the accepted registry version.
That status and history events were recorded by the Registry.
THE REGISTRY DOES NOT, BY REGISTRATION ALONE, VERIFY
That the governance architecture works as claimed.
That the claimant owns every underlying idea or right.
That the architecture complies with any law or standard.
That a regulator, standards body, or independent reviewer endorses it.
That a registration creates legal priority, exclusivity, certification, or admissibility.
TA-14 GOVERNANCE PROFILES
The Registry establishes the record. Governance Profiles help the world understand what entered it.
A Governance Profile is a separate TA-14 Authority publication layer built on top of a registered entity's attributable Registry baseline. It may introduce the steward, explain the architecture in plain language, identify why the work is institutionally significant, and connect later demonstrations, reviews, or public records without altering the underlying Registry declaration.
01
REGISTRY RECORD
What the registrant formally declared.
Identity, version, category, steward, scope, claims, non-claims, evidence, provenance, rights, visibility, lifecycle state, and the permanent Registry identifier remain the authoritative registration baseline.
→
02
TA-14 AUTHORITY PROFILE
Why the registered architecture matters.
TA-14 may publish institutional commentary describing the architecture, its steward, its declared contribution, and the governed work that may follow. The profile does not rewrite the Registry record or convert registration into endorsement.
CURATED PUBLICATION LAYER
Independent identity remains intact.
A governance architecture does not need to become TA-14 to be profiled by TA-14. The point of the profile is to preserve the entity's own identity while making serious registered work easier for the public, institutions, researchers, potential partners, and future reviewers to understand.
Harmonic Constitutional Runtime entered the TA-14 AI Governance Registry as TA-14-AIGR-000008 under the stewardship of Timothy E. Zlomke. Its Governance Profile provides the public-facing institutional layer for understanding what Harmonic declares, why TA-14 is paying attention, and how later governed work remains distinct from the original registration baseline.
Governance Profiles are curated institutional publications.Selection for a profile does not certify effectiveness, establish legal priority, validate ownership, prove technical performance, or imply that TA-14 adopts the profiled architecture as its own.
FOUNDATIONAL RELEASE
The front door is now established.
The Registry is moving from institutional design into operation. Governance architectures can enter governed intake, preserve identity and authority declarations, submit evidence, proceed through review, receive a permanent Registry identifier, and appear in the public directory when public visibility is authorized.