Volume VIII — Registry

Official Definition

The 360WiSE Registry is the structured public record system used to publish and maintain identity, participation, verification, relationship, provenance, continuity, resolution, and authority information for eligible individuals, businesses, creators, organizations, institutions, government bodies, media properties, platforms, and other participating entities.

The Registry provides each eligible entity with a maintained Canonical Registry Record and, where assigned, a unique 360WSE Identifier.

The Registry stores and publishes the structured record. The Resolution Infrastructure uses the assigned 360WSE Identifier to direct people and machines to the entity’s Canonical Resolution Endpoint.

Registry publication confirms that a record has been established and maintained within the 360WiSE Framework. It does not represent governmental registration, regulatory approval, external accreditation, universal certification, or guaranteed recognition by independent systems.

Purpose

The purpose of the Registry is to create a durable, organized, publicly accessible, and machine-readable reference layer for participating entities.

Identity information is often divided across websites, databases, social profiles, applications, news publications, public records, streaming platforms, directories, institutional systems, and AI interfaces.

The Registry provides one structured location within the 360WiSE Framework where those records may be connected, classified, verified, maintained, corrected, resolved, and referenced over time.

The Registry is intended to preserve more than a present-day profile. It may document current identity, historical identity, verified relationships, official properties, corrections, transitions, provenance, and relevant recognition observations.

The Registry Problem

The registry problem occurs when an entity has no stable, authoritative public reference connecting its identity, evidence, relationships, history, official sources, and current status.

Common registry gaps include:

• No unique public reference for the entity
• Duplicate profiles across unrelated platforms
• Official and unofficial information being mixed together
• Names changing without a preserved historical connection
• Brands being disconnected from their legal operators
• Applications being separated from their publishers
• Founders or leaders being disconnected from organizations
• Verification status being unclear
• Corrections being published without a maintained record
• Source evidence being disconnected from the claim it supports
• Historical information being confused with current information
• Participation status being mistaken for endorsement
• External mentions being presented as permanent recognition
• Machine-readable relationships being absent or incomplete
• Identifiers being inconsistent across systems
• Resolver endpoints being disconnected from source records

The Registry addresses these conditions by organizing authority information around one maintained entity record and one stable framework identifier.

Registry Model

The Registry operates as a structured publication and record maintenance layer within the broader 360WiSE Framework.

Registry Record

A Registry Record is the maintained public representation of an eligible participating entity within the 360WiSE Framework.

The Registry Record may combine identity information, supporting evidence, claim statuses, public relationships, historical context, participation information, official properties, corrections, technical references, and relevant recognition observations.

A Registry Record does not imply that every field has the same verification status. Each material claim or relationship may be classified independently according to the applicable review process.

A published Registry Record may be associated with a Canonical Resolution Endpoint, but the Registry Record and the Resolution Endpoint perform separate functions.

360WSE Identifier

Eligible Registry Records may be assigned a unique 360WSE Identifier, which serves as the permanent canonical reference for a participating entity throughout the 360WiSE Framework.

The 360WSE Identifier is the primary reference used across the Registry, Resolution Infrastructure, Verification services, Recognition Protocol, Broadcast Infrastructure, Developer Standards, structured data, APIs, and approved future implementations to consistently identify the same entity.

The published identifier format is:

Every published Registry Record assigned a 360WSE Identifier is intended to resolve to one Canonical Resolution Endpoint.

The identifier remains associated with the entity throughout its documented lifecycle, including updates, corrections, historical records, continuity events, status changes, and approved framework extensions.

The 360WSE Identifier is a framework identifier. It does not create legal identity, governmental registration, ownership rights, regulatory approval, accreditation, licensing authority, or certification.

A 360WSE Identifier should not be transferred, reassigned, reused, altered, or represented as belonging to another entity except through documented Registry governance, continuity procedures, and published correction records.

Relationship to the Resolver

The Registry and the Resolution Infrastructure are connected but distinct components of the 360WiSE Framework.

A Canonical Resolution Endpoint may display the entity name, assigned 360WSE Identifier, Registry status, verification status, resolver status, entity type, official relationships, Canon references, machine-readable resources, and other approved record components.

The existence of a Resolution Endpoint does not require every field within the associated Registry Record to be publicly displayed. Privacy, security, legal, contractual, licensing, and governance restrictions may limit public disclosure.

Canonical Registry Record

A Canonical Registry Record may contain structured information describing the participating entity. Components vary according to entity type, available evidence, publication permissions, verification status, technical implementation, and applicable governance policies.

Components may be added, revised, restricted, corrected, superseded, archived, or retired as the Framework evolves. Historical information remains governed by the Continuity, Provenance, Change Log, and Revision History provisions of the Official Canon.

Participation Status

A Registry Record may include a participation status describing the entity’s current relationship to the 360WiSE Framework.

Participation status is separate from claim verification, external recognition, legal standing, licensing status, regulatory status, accreditation, and commercial performance.

Participation status does not represent endorsement, approval, accreditation, governmental standing, regulatory standing, financial condition, or guaranteed recognition by an independent system.

Claim and Evidence Status

Material claims within a Canonical Registry Record may carry individual statuses that are separate from the entity’s overall participation status.

A participating or Authority Verified™ entity may still have individual claims that are pending, historical, disputed, corrected, superseded, expired, restricted, or unverified.

Unverified does not automatically mean false. It means sufficient evidence has not been confirmed under the applicable review process.

Every status should be interpreted according to the exact claim, scope, evidence, review date, source provenance, and published limitation associated with it.

Registry Publication

Registry publication makes an eligible Canonical Registry Record available as a public reference within the 360WiSE Framework.

Published records may be accessible through one or more approved methods, including:

• A Canonical Resolution Endpoint
• A Registry page
• A 360WSE Identifier lookup
• A participant authority page
• A public verification workflow
• A structured-data endpoint
• An approved website integration
• A developer API
• A JSON or JSON-LD representation
• A Broadcast Infrastructure implementation
• An approved future reference implementation

Registry publication may support:

• Public identity confirmation
• Entity distinction
• Official relationship documentation
• Claim-to-evidence connection
• Identifier-based resolution
• Historical continuity
• Correction transparency
• Source provenance
• Machine-readable representation
• Cross-reference among ecosystem properties
• Public verification inquiries
• Developer and technical integrations

Publication does not require an independent system to retrieve, cite, rank, recognize, reproduce, recommend, or rely upon the Registry Record.

Publication also does not require every internal field, source, document, verification note, or restricted record to be made public.

Record Maintenance

Canonical Registry Records should be maintained as the represented entity and its public information evolve.

Maintenance may include:

• Updating official descriptions
• Changing leadership or authorized representatives
• Adding or removing official properties
• Documenting legal or public name changes
• Recording organizational transitions
• Updating locations and service areas
• Renewing licenses or credentials
• Correcting inaccurate claims
• Changing participation status
• Updating verification status
• Updating source and evidence references
• Documenting expired or discontinued records
• Adding technical, media, or distribution properties
• Preserving historical versions
• Recording recognition observations
• Updating machine-readable representations
• Maintaining Resolver connections
• Documenting material governance changes

Participants are responsible for notifying 360WiSE of material changes affecting the accuracy, authority, currency, or lawful publication of their records.

360WiSE may update, qualify, restrict, suspend, correct, supersede, archive, or preserve a record based on reliable evidence, governance requirements, legal obligations, privacy concerns, security risks, technical requirements, or material public-interest considerations.

Corrections and Disputes

A Canonical Registry Record may be corrected when reliable evidence shows that published information is materially inaccurate, incomplete, outdated, misattributed, misleading, or connected to the wrong entity.

A correction request should identify:

• The affected Registry Record
• The applicable 360WSE Identifier
• The specific information challenged
• The requested correction
• The evidence supporting the request
• The authority of the submitting party
• Relevant dates and source records
• Any known competing claims
• Any privacy, legal, or security concern

360WiSE may classify disputed information as pending, disputed, corrected, superseded, historical, unverified, restricted, archived, or otherwise qualified while the matter is reviewed.

A correction may affect the Registry Record, Canonical Resolution Endpoint, verification status, machine-readable representation, relationship mapping, provenance record, or continuity history.

The Registry favors transparent correction and preserved continuity over silent removal when the earlier record remains material to public understanding.

360WiSE may decline to determine matters that require legal adjudication, regulatory action, private arbitration, forensic examination, or evidence beyond the reasonable authority and scope of the Framework.

Privacy and Restricted Information

The Registry is a public reference system, but not every submitted, reviewed, or internally maintained record is appropriate for full public disclosure.

Information may be withheld, limited, summarized, redacted, restricted, or excluded where publication would conflict with:

• Privacy rights
• Security requirements
• Contractual restrictions
• Confidentiality obligations
• Intellectual-property rights
• Applicable law
• Platform policies
• Child-safety requirements
• Protected personal information
• Trade-secret protections
• Internal verification procedures
• Technical security controls
• Law-enforcement restrictions
• Government-record limitations

A public verification status may be displayed without publishing every underlying private document, internal note, authorization record, or restricted source used during review.

Restricted evidence may remain available for internal governance, reverification, dispute handling, security review, legal response, authorized inspection, or continuity maintenance where appropriate.

Relationship to Identity

Identity establishes who or what the entity is. The Registry publishes and maintains the structured public record associated with that identity.

Identity provides the entity definition, distinguishing attributes, relationships, official properties, and historical context.

The Registry provides the durable public location and framework structure through which that identity may be maintained, referenced, corrected, and resolved.

Identity defines the entity. The Registry publishes the maintained identity record.

Relationship to Verification

Verification determines whether specified claims are sufficiently supported according to the applicable 360WiSE criteria.

The Registry may publish the verification status of eligible claims, identities, relationships, properties, sources, or participants.

Registry publication does not automatically mean that every element of the record is verified.

Verification scope, date, claim status, supporting evidence, and limitations should be identified separately from overall Registry participation.

Relationship to Resolution

Resolution connects information, relationships, evidence, records, sources, and properties to the correct entity.

The Registry preserves the resulting entity connections so that related information may be understood as part of one maintained public identity.

The Resolution Infrastructure uses the assigned 360WSE Identifier to direct a request to the entity’s Canonical Resolution Endpoint.

Resolution determines where the information belongs. The Registry publishes and maintains that resolved relationship.

Relationship to Continuity

Continuity preserves how an entity and its records change over time. The Registry provides the maintained public record in which those changes, corrections, transitions, and historical states may be documented.

A Canonical Registry Record may preserve former names, prior leadership, earlier domains, historical relationships, previous locations, superseded records, expired credentials, transferred properties, and corrected claims.

The Registry is not limited to a present-day profile. It may serve as a maintained continuity record across the documented lifecycle of the entity.

Relationship to Provenance

Provenance documents where information originated, who supplied or published it, when it entered the record, and how it was changed, transferred, summarized, syndicated, or corrected.

Registry Records may associate claims, evidence, publications, technical artifacts, corrections, recognition observations, and historical states with their relevant provenance.

Provenance explains the source history. The Registry provides the maintained public location where that history may be connected to the correct entity.

Relationship to Recognition

Registry publication and external recognition are separate conditions.

Registry publication confirms that an entity has a maintained public record within the 360WiSE Framework.

Recognition describes a dated and independently observed result in an external AI, search, media, institutional, platform, database, directory, or public-information system.

A Registry Record does not guarantee recognition. An entity may also be externally recognized without having a 360WiSE Registry Record.

Recognition observations may be documented within a Registry Record when the observation is relevant, reproducible, sufficiently supported, and appropriately dated.

Recognition status should never be represented as permanent unless the applicable external condition is continuously verified and the published standard expressly supports that classification.

The Registry publishes. Independent systems recognize independently.

Relationship to AI Systems

The Registry is designed to publish clearer identity, relationship, evidence, provenance, continuity, status, and resolution information in forms intended to be understandable by both people and machines.

Machine-readable Registry publication may include:

• 360WSE Identifiers
• Canonical Resolution Endpoints
• Structured identity fields
• Relationship statements
• Status classifications
• Source and evidence references
• Verification dates
• Provenance records
• Continuity records
• Correction history
• Schema markup
• JSON
• JSON-LD
• APIs
• Technical documentation
• Approved future machine-readable formats

Independent AI systems determine their own retrieval, ingestion, entity matching, reasoning, ranking, citation, summarization, recommendation, and response behavior.

360WiSE does not control those systems and does not guarantee that a Registry Record will be discovered, ingested, cited, ranked, recognized, reproduced, recommended, or interpreted in a particular manner.

The Registry is intended to improve the quality and continuity of the public record available for resolution. It does not override the independent operation of an AI system.

Registry Governance

The Registry is governed through published definitions, eligibility rules, participation pathways, verification criteria, identifier controls, status classifications, correction procedures, privacy protections, continuity requirements, technical standards, and revision controls.

Registry governance may apply to:

• Record eligibility
• Entity classification
• 360WSE Identifier assignment
• Identifier preservation
• Canonical Resolution Endpoint publication
• Verification scope
• Participation status
• Claim and evidence status
• Relationship publication
• Source provenance
• Continuity maintenance
• Corrections and disputes
• Privacy and restricted information
• Machine-readable publication
• Technical implementation
• Suspension, withdrawal, and archival

360WiSE may refuse, limit, suspend, correct, restrict, archive, supersede, or withdraw a Registry Record when necessary to address:

• Materially false or misleading submissions
• Identity misrepresentation
• Unauthorized representation
• Fraud or impersonation
• Unresolved ownership disputes
• Conflicting authority claims
• Violation of applicable law
• Privacy or security concerns
• Intellectual-property infringement
• Expired or revoked authorization
• Failure to maintain materially current information
• Abuse of Registry identifiers or statuses
• Misuse of a Canonical Resolution Endpoint
• Conduct inconsistent with published participation terms
• Technical, operational, reputational, or public-interest risk

Material Registry policy changes should be documented through the Official Canon, Change Log, and Revision History.

Public Boundaries

The 360WiSE Registry does not:

• Replace government identity systems
• Replace corporate registration authorities
• Replace licensing, accreditation, or regulatory bodies
• Constitute governmental approval
• Constitute regulatory approval
• Constitute legal certification
• Create legal identity
• Establish ownership where ownership remains disputed
• Create intellectual-property rights
• Guarantee the truth of every participant-submitted statement
• Guarantee that every Registry field has been verified
• Guarantee that every source remains current
• Guarantee AI recognition
• Guarantee search-engine ranking
• Guarantee citation or recommendation
• Guarantee traffic, revenue, sales, funding, or commercial success
• Control independent platforms, databases, or AI systems
• Require third parties to rely on a Registry Record
• Erase lawful public records
• Replace legal, regulatory, financial, technical, or professional due diligence
• Require publication of private or restricted evidence
• Create external endorsement solely through participation
• Permit transfer or reassignment of a 360WSE Identifier without governance review

Registry publication is limited to the records, claims, relationships, evidence, statuses, dates, identifiers, technical references, and governance maintained within the applicable 360WiSE process.

Related Canon

• Volume I — The Framework
• Volume II — Business Authority Infrastructure™
• Volume III — Identity
• Volume IV — Verification
• Volume V — Resolution
• Volume VI — Continuity
• Volume VII — Provenance
• Recognition Protocol
• Recognition Levels
• Governance
• Developer Standards
• Broadcast Infrastructure
• Change Log
• Revision History

Revision History