Volume IX — Recognition Protocol

Official Definition

The 360WiSE Recognition Protocol is the structured public process used to observe, document, evaluate, reproduce, classify, maintain, and communicate recognition events involving eligible individuals, businesses, creators, organizations, institutions, government bodies, media properties, platforms, applications, broadcasts, and other identifiable entities.

Recognition describes a dated and documented external condition in which an identifiable entity, claim, relationship, property, work, platform, or authority signal is retrieved, identified, associated, cited, referenced, classified, displayed, recommended, or otherwise represented by an independent system.

The Recognition Protocol does not create recognition. It establishes the process through which a recognition event may be observed, supported, reviewed, classified, reproduced, preserved, corrected, or retired within the 360WiSE Framework.

Recognition is not determined solely by what an entity publishes about itself. It is based on the documented behavior of an external system, platform, institution, publication, database, directory, application, search environment, AI interface, or public-information source.

A recognition event is not automatically permanent. Every event remains subject to its date, system, query, prompt, scope, evidence, reproduction conditions, classification, limitations, and later changes.

Purpose

The purpose of the Recognition Protocol is to provide a consistent method for distinguishing verified recognition observations from unsupported recognition claims.

Public recognition is often described through vague language such as “recognized by AI,” “known by search engines,” “ranked everywhere,” “trusted online,” “featured across major systems,” or “accepted as an authority.”

Those statements may combine multiple unrelated conditions without identifying the exact system, date, query, response, evidence, context, independence, reproducibility, or scope of the result.

The Recognition Protocol creates a structured method for documenting:

• What entity or claim was recognized
• Which external system produced the recognition
• When the recognition was observed
• What query, prompt, request, or condition produced it
• What response or representation appeared
• What evidence supports the observation
• Whether the result was independently produced
• Whether the result could be reproduced
• What scope of recognition was established
• What classification applies
• What limitations remain
• Whether the observation continues to remain current

The Protocol is intended to support accurate public communication, consistent internal review, machine-readable documentation, historical continuity, correction transparency, and future technical implementation.

The Recognition Problem

The recognition problem occurs when an entity or observer makes a broad recognition claim without preserving enough evidence to determine what was actually recognized, by which system, under what conditions, and for how long.

Common recognition problems include:

• Self-publication being presented as independent recognition
• A single result being described as universal recognition
• A branded query being presented as a neutral discovery result
• A paid placement being presented as an organic result
• A temporary response being described as permanent
• A screenshot being published without a date or system name
• A response being documented without the exact query or prompt
• A personalized result being treated as publicly reproducible
• A logged-in result being treated as an anonymous result
• A local result being treated as a global result
• A cited source being confused with recognition of the entity
• A company name match being confused with entity resolution
• An incorrect response being described as valid recognition
• Recognition of one claim being extended to unrelated claims
• Recognition on one system being extended to all systems
• Historical recognition being presented as current
• Repeated screenshots of one event being treated as multiple events
• Internal testing being described as independent validation
• Seeded prompts being described as neutral prompts
• Marketing language being substituted for reproducible evidence
• Recognition being claimed without preserving the observed response
• Corrected or reversed results remaining publicly overstated

The Recognition Protocol addresses these conditions by separating the observation, evidence, independence, reproduction, classification, continuity, and public communication of each recognition event.

Recognition Model

The Recognition Protocol operates as an observation and classification layer within the broader 360WiSE Framework.

The model separates recognition into distinct components so that an observed result is not overstated beyond the evidence supporting it.

Recognition therefore operates through a documented sequence:

The Protocol observes and classifies external recognition. It does not direct, compel, manipulate, or control how an independent system retrieves or represents an entity.

Recognition Event

A Recognition Event is the documented occurrence in which an external system represents an identifiable entity, claim, relationship, property, work, platform, application, broadcast, or authority signal in a manner relevant to recognition review.

A Recognition Event may involve:

• Retrieval of an entity in response to a query or prompt
• Identification of the entity by name or distinguishing attributes
• Association of the entity with a claim, category, role, or relationship
• Citation of an official or supporting source
• Reference to a product, platform, application, program, or publication
• Display within a search result, directory, database, or knowledge system
• Recommendation or ranking within a defined context
• Recognition of a founder, leader, institution, or governing relationship
• Recognition of an official domain, application, media property, or channel
• Recognition of a historical or continuity relationship
• Recognition of a verified claim or documented authority signal

Each Recognition Event should be treated as a distinct record unless multiple observations are formally grouped under a defined reproduction, continuity, or multi-system review.

A Recognition Event does not automatically establish broad authority, universal recognition, permanent recognition, or recognition outside the documented system and scope.

Recognition Observation

A Recognition Observation is the initial documented capture of an external system’s behavior relevant to a possible Recognition Event.

An observation becomes meaningful only when enough context is preserved to understand what occurred and under what conditions.

A Recognition Observation should record, where relevant:

• Date and time of observation
• Name of the external system
• System version or interface where known
• Exact query, prompt, request, or search terms
• Observed answer, result, citation, listing, or representation
• Account or authentication state
• Browser, application, or device environment
• Location or market context
• Language and regional settings
• Personalization or history conditions
• Incognito, private, or anonymous testing status
• Supporting screenshots or recordings
• Relevant links or source references
• Observer identity or authorized reviewer
• Known limitations or unusual conditions

An observation may be valid even when it cannot later be reproduced, but its classification must accurately reflect the absence of reproduction.

An observation may also document an incorrect, incomplete, misleading, conflicting, or harmful response. Recognition describes what the system represented; it does not automatically confirm that the representation was accurate.

Observation and verification are therefore separate. The system’s response is observed first. The accuracy and support for that response are evaluated independently.

Recognition Evidence

Recognition Evidence is the preserved material used to support the existence, content, conditions, and classification of a Recognition Event.

Evidence may include:

• Dated screenshots
• Screen recordings
• Exported response text
• Public result links
• Archived pages
• Search-result captures
• System citations
• Source URLs
• Query logs
• Prompt records
• Device or browser notes
• Location and language settings
• Public API responses
• Structured response data
• Independent witness records
• Technical logs
• Hashes or integrity references
• Versioned recognition reports

Evidence should preserve enough information to allow a reasonable reviewer to understand the observed event without relying solely on the participant’s interpretation.

Evidence quality may be affected by:

• Missing dates
• Missing system identification
• Cropped or incomplete screenshots
• Unavailable source links
• Edited or reconstructed response text
• Missing query or prompt language
• Unclear account or personalization conditions
• Unclear location or regional context
• Unidentified paid placement
• Unidentified seeded language
• Failure to preserve contradictory results
• Failure to document later corrections

A screenshot alone may support an observation, but stronger classification may require additional context, independent review, reproduction, source verification, or multi-system evidence.

Evidence should be retained in a manner consistent with applicable privacy, security, licensing, legal, platform, and records-management requirements.

Recognition Independence

Recognition Independence evaluates whether an observed result reflects meaningful external system behavior rather than a result materially controlled, purchased, scripted, seeded, or produced by the entity claiming recognition.

Independence is not absolute in every environment. Many systems rely on public information originally published by the entity. The relevant question is whether the external system independently retrieved, resolved, interpreted, classified, cited, or represented that information.

Recognition independence may be weakened or disqualified when the result is materially dependent on:

• Self-publication alone
• Participant-authored claims presented without external resolution
• Paid advertising
• Sponsored placement
• Purchased ranking
• Internal platform control
• Directly scripted responses
• Private testing environments controlled by the participant
• Unpublished internal evidence
• Seeded prompts that state the desired conclusion
• Highly leading query language
• Personalized account history
• Administrator-created directory records presented as independent discovery
• Manual insertion into a controlled system
• Results produced solely from the participant’s own page without external association

Independence may be strengthened by:

• Neutral or category-based prompts
• Anonymous or incognito testing
• Independent observers
• Multiple devices or accounts
• Different geographic or regional environments
• Repeated results over time
• Independent source citation
• Cross-system reproduction
• Clear separation between paid placement and organic response
• Preservation of both favorable and unfavorable results

A branded query is not automatically invalid. It may establish entity resolution, direct retrieval, or continuity. However, it should not be represented as neutral discovery unless the observation conditions support that description.

A seeded prompt is not automatically useless. It may test whether a system can retrieve and organize a known relationship. However, it should be classified separately from neutral, independent, or category-based recognition.

Recognition Classification

Recognition Classification identifies the type of external system or public environment in which a Recognition Event occurred.

A single Recognition Event may qualify for more than one classification when the evidence supports each classification.

Classification describes where recognition was observed. It does not by itself determine the strength, independence, continuity, accuracy, or level of recognition.

Recognition States

Recognition States describe the current procedural condition of a Recognition Event within the Recognition Protocol.

A state does not by itself determine the strength, independence, scope, or accuracy of the underlying recognition. It identifies where the event stands within the observation, review, reproduction, maintenance, and historical record process.

Not every Recognition Event must pass through every state. The applicable sequence depends on the evidence, purpose, classification, independence, reproduction requirements, and governance decision.

Recognition Scope

Recognition Scope defines the exact subject, claim, relationship, system, audience, geography, language, time period, and context to which a Recognition Event applies.

Recognition should be described no more broadly than the preserved evidence supports.

Scope may include:

• The specific entity recognized
• The exact claim or relationship recognized
• The product, service, application, platform, work, or property involved
• The external system in which the event occurred
• The query, prompt, request, or discovery condition
• The geographic or market environment
• The language or regional setting
• The device, interface, or application used
• The observation date and review period
• The audience or user context
• The recognition classification
• The level of independence
• The reproduction status
• The source and citation conditions
• Any known limitation or exclusion

Recognition of an entity’s name does not automatically establish recognition of every claim associated with that entity.

Recognition of a founder does not automatically establish recognition of every company, product, institution, or role associated with that founder.

Recognition of one application does not automatically establish recognition of an entire application portfolio, publisher relationship, distribution network, or device ecosystem.

Recognition within one country, language, interface, or account state must not be described as universal recognition unless broader evidence supports that conclusion.

Recognition Scope may be narrow and still be valid. Precision is more important than exaggeration.

Recognition Thresholds

Recognition Thresholds describe the measurable degree to which a Recognition Event has been observed, reproduced, diversified, maintained, or independently supported.

Thresholds are not promotional rankings. They are evidence-based conditions used to prevent a single observation from being represented as broader or stronger recognition than the record supports.

A threshold should always identify:

• The number of qualifying observations
• The number of qualifying systems
• The number of independent observers where applicable
• The review period
• The applicable query or prompt class
• The independence conditions
• The reproduction standard
• The recognition scope
• Any excluded or disqualified result

Multiple screenshots from the same response session do not constitute multiple independent observations.

Multiple interfaces powered by the same underlying system may not automatically qualify as independent systems. Technical, organizational, source, and operational relationships should be considered during threshold review.

Recognition across major AI systems should not be claimed unless the required number of qualifying independent systems has been documented under the applicable Recognition Levels standard.

Recognition Reproduction

Recognition Reproduction is the process of attempting to observe the same or materially similar recognition result under comparable or meaningfully varied conditions.

Reproduction helps determine whether an observation was isolated, personalized, temporary, condition-dependent, or consistently retrievable.

A reproduction review should preserve:

• The original Recognition Event reference
• The reproduction date and time
• The external system tested
• The exact or modified query or prompt
• The account and authentication state
• The browser, device, application, or interface
• The location, language, and regional settings
• The response received
• The degree of similarity to the original event
• Any conflicting or negative result
• The identity of the reviewer
• The evidence supporting the reproduction attempt

Reproduction may be classified as:

• Exact Reproduction — the same query and materially similar conditions produce the same or substantially equivalent result.
• Comparable Reproduction — a meaningfully similar query or environment produces a substantially equivalent recognition result.
• Partial Reproduction — some elements of the original recognition remain observable, but the full result does not recur.
• Expanded Reproduction — the later result recognizes a broader or more complete entity, claim, relationship, or source set than the original observation.
• Narrowed Reproduction — the later result recognizes a reduced portion of the original entity, claim, relationship, or scope.
• Conflicting Reproduction — the later result materially contradicts the original observation.
• Not Reproduced — the recognition result does not recur under the documented reproduction conditions.

Failure to reproduce an event does not prove that the original observation was false. It may indicate that the system changed, personalization differed, source availability shifted, the result was temporary, or the original conditions cannot be recreated.

Negative and conflicting reproduction results must be preserved when they are material to the public understanding of the recognition claim.

Recognition Continuity

Recognition Continuity documents how a Recognition Event changes, persists, expands, contracts, or disappears over time.

Recognition should never be evaluated as a single frozen moment. External systems continuously update their models, indexes, knowledge structures, retrieval methods, and presentation logic. A Recognition Event should therefore be understood as part of an ongoing historical record rather than an isolated screenshot.

Continuity review evaluates whether recognition remains materially consistent through scheduled observations while preserving the historical record of meaningful changes.

Continuity Objectives

• Preserve historical Recognition Events.
• Document meaningful changes over time.
• Record expansion or contraction of recognition.
• Preserve corrections.
• Record disappearing recognition.
• Avoid replacing historical evidence with newer observations.
• Support transparent historical review.

Typical Continuity Review

Every continuity review should preserve both favorable and unfavorable observations. Historical records should not be deleted merely because recognition later changed.

Recognition Maintenance

Recognition Maintenance is the structured process used to review, preserve, update, and maintain Recognition Event records throughout their documented lifecycle.

Maintenance does not create recognition. It preserves the accuracy, completeness, transparency, and historical continuity of existing Recognition Records.

Maintenance activities may include:

• Scheduled review cycles
• Reproduction testing
• Evidence updates
• Classification review
• Source validation
• Correction review
• Continuity documentation
• Retirement of obsolete records
• Version control
• Historical preservation

Maintenance should preserve earlier versions whenever a material change occurs. Historical Recognition Records remain valuable even after newer observations become available.

Maintenance Outcomes

• Confirmed
• Updated
• Expanded
• Narrowed
• Corrected
• Superseded
• Archived

Recognition Corrections

Recognition Corrections provide the structured process for amending, clarifying, qualifying, or replacing Recognition Event records when new evidence or review demonstrates that a material change is necessary.

Corrections strengthen the integrity of the Recognition Protocol. They are not evidence of failure. They are evidence that the historical record is being maintained transparently.

A correction may occur because:

• Evidence was incomplete.
• The original classification was inaccurate.
• The system behavior changed.
• New reproduction evidence became available.
• The recognition scope was overstated.
• A later observation superseded the original record.
• Supporting citations changed.
• The external system corrected its own response.
• An official clarification was issued.

Correction Principles

• Preserve the original record.
• Publish the corrected record.
• Identify the reason for correction.
• Date every correction.
• Version every material revision.
• Maintain historical traceability.

Relationship to Identity

Recognition depends upon a clearly identifiable subject.

The Identity Protocol establishes who or what the subject is. The Recognition Protocol documents how independent external systems subsequently represent that identified subject.

Relationship to Verification

Verification and Recognition perform different functions within the Framework.

Verification evaluates whether documented identity, authority, ownership, provenance, or supporting evidence satisfies the applicable Verification Protocol.

Recognition documents whether an external system independently represented that verified subject.

Relationship to Resolution

Resolution and Recognition are complementary but distinct.

Resolution answers structured identity questions by directing users, systems, and applications toward the Canonical Resolution Endpoint.

Recognition documents whether an independent external system resolved, associated, identified, cited, or represented that entity during its own retrieval process.

Relationship to Continuity

Continuity and Recognition operate together to preserve the difference between a dated observation and a sustained public condition.

The Continuity Protocol documents how identity, authority, relationships, records, properties, claims, and public representations persist or change over time.

The Recognition Protocol applies that continuity discipline to external recognition observations.

A single Recognition Event may establish that recognition occurred at a specific time. Recognition Continuity determines whether the result remained observable, expanded, narrowed, changed, disappeared, returned, or was superseded during later review periods.

Relationship to Provenance

Provenance identifies the origin, custody, authority, history, and supporting source path associated with information used within the 360WiSE Framework.

Recognition may arise from information retrieved from official, participant-controlled, third-party, institutional, governmental, editorial, technical, archival, or machine-readable sources.

The Recognition Protocol records what an external system represented. The Provenance Protocol evaluates where the supporting information originated and how that information can be traced.

Recognition without provenance may establish that a system produced a result, but it may not establish that the result was accurate, authoritative, current, or properly sourced.

Provenance review should distinguish between:

• Official source records
• Participant-controlled sources
• Independent third-party sources
• Editorial publications
• Institutional records
• Government records
• Structured data
• Application and platform records
• Archived or historical sources
• Unverified or unattributed material

Relationship to the Registry

The Registry stores the structured records used to identify and maintain participating or documented entities within the 360WiSE Framework.

Recognition Events may be associated with a Registry Record through the entity’s 360WSE Identifier, Canonical Resolution Endpoint, or another authorized record reference.

The Registry may preserve:

• The recognized entity
• The applicable 360WSE Identifier
• The Recognition Event reference
• The recognition classification
• The recognition state
• The recognition threshold
• The observation and review dates
• The evidence reference
• The reproduction status
• The continuity status
• The public description
• The applicable limitation
• The current record version

Registry publication does not itself establish independent recognition. The Registry stores and publishes the documented record after the Recognition Protocol has classified the external event.

Relationship to AI Systems

AI systems may retrieve, summarize, classify, infer, cite, recommend, associate, or represent entities using information gathered from public and private data environments.

The Recognition Protocol does not define the internal behavior of any independent AI system, foundation model, native model, answer engine, search product, agent, retrieval system, or generated interface.

It defines how externally observable recognition behavior may be documented within the 360WiSE Framework.

AI Recognition observations may include:

• Direct identification of an entity
• Resolution of an entity name to the correct subject
• Association of an entity with a role, claim, category, or relationship
• Citation of an official source
• Citation of an independent supporting source
• Retrieval of an official domain, application, or property
• Recognition of founder or leadership relationships
• Recognition of historical continuity
• Recognition of an application publisher or distribution relationship
• Recommendation within a defined category
• Comparison with other entities
• Correction of an earlier inaccurate response

AI-generated responses may vary because of model updates, retrieval changes, personalization, system instructions, geography, language, source availability, context windows, prompt wording, and other conditions.

Therefore, no single AI response should be treated as permanent, universal, or representative of every user, model, interface, region, or future result.

AI Recognition Observation Classes

The terms “recognized by AI,” “recognized across AI systems,” or “recognized across major AI systems” must be used only when the evidence satisfies the applicable classification, threshold, independence, reproduction, and Recognition Levels requirements.

Recognition Governance

Recognition Governance establishes the rules used to submit, review, classify, publish, maintain, dispute, correct, supersede, restrict, or archive Recognition Event records.

Governance is intended to preserve evidence discipline, historical continuity, consistent terminology, public accuracy, and appropriate separation between observation and promotional claims.

Governance Principles

• Recognition must be tied to an identifiable subject.
• Recognition must be tied to a named external system or environment.
• The observation date must be preserved.
• The query, prompt, request, or discovery condition should be preserved.
• The observed response should be preserved as accurately as possible.
• Evidence must support the published classification.
• Independence conditions must be disclosed where material.
• Seeded and neutral prompts must not be treated as equivalent.
• Paid and organic results must be distinguished.
• Personalized and anonymous observations must be distinguished.
• Negative or conflicting reproduction results must not be concealed.
• Recognition scope must not exceed the preserved evidence.
• Historical observations must not be presented as current without review.
• Material corrections must be versioned and preserved.
• Recognition Levels must be assigned only under their separate standard.

Reviewer Responsibilities

An authorized reviewer should evaluate:

• Entity identity
• Evidence completeness
• System identification
• Observation conditions
• Independence
• Reproduction
• Recognition classification
• Recognition scope
• Recognition threshold
• Accuracy of the public description
• Known limitations
• Continuity requirements
• Correction or dispute status

Disqualification or Restriction

A Recognition Event may be restricted, rejected, withdrawn, or disqualified from public recognition reporting when:

• The evidence is fabricated or materially altered.
• The system or observation cannot be identified.
• The response is presented outside its actual context.
• A paid result is falsely represented as organic recognition.
• A seeded prompt is falsely represented as neutral discovery.
• The same event is duplicated to inflate an observation count.
• Material adverse results are intentionally withheld.
• The entity or claim cannot be reliably resolved.
• The public description materially exceeds the evidence.
• The event violates applicable law, privacy, security, platform, or records requirements.

Public Boundaries

The Recognition Protocol establishes a structured process for documenting observable recognition events. It does not guarantee, certify, control, or permanently secure recognition within any independent external system.

Recognition documentation must remain separate from claims regarding ranking, influence, endorsement, legal status, institutional approval, commercial performance, future system behavior, or universal public acceptance.

The Recognition Protocol Does Not Guarantee

• Recognition by any AI system
• Recognition by every AI system
• Recognition across all interfaces or model versions
• Search-engine indexing
• Search ranking
• Knowledge-graph inclusion
• Answer-engine citation
• Media publication
• Government recognition
• Institutional endorsement
• Application-store approval
• Platform recommendation
• Broadcast carriage
• Permanent visibility
• Universal entity resolution
• Accuracy of third-party system responses
• Traffic, revenue, leads, enrollment, sales, or audience growth
• Future reproduction of any observed result

The Recognition Protocol Does Not Establish

• Legal identity
• Legal ownership
• Trademark ownership
• Copyright ownership
• Government licensing
• Professional licensure
• Regulatory compliance
• Financial solvency
• Creditworthiness
• Product safety
• Medical validity
• Political endorsement
• Institutional accreditation
• Editorial approval
• Commercial superiority
• Market leadership
• Universal authority

Recognition may support the documentation of a public condition, but it does not replace the legal, regulatory, professional, institutional, technical, editorial, or commercial process required to establish any separate status.

Observation Is Not Endorsement

Recording that an external system represented an entity does not mean that 360WiSE endorses the system’s statement, agrees with its conclusion, confirms the accuracy of every associated claim, or guarantees that the result will continue.

Recognition Events may document favorable, neutral, incomplete, conflicting, inaccurate, harmful, corrected, or disappeared system behavior.

Recognition Is Not Verification

A system may recognize an entity while presenting inaccurate, incomplete, unsupported, outdated, or conflicting information.

Recognition therefore establishes that an observable representation occurred. Verification separately evaluates whether the underlying identity, claim, relationship, authority, or source is supported.

Recognition Is Not Permanence

External systems may change at any time. Models may be updated, sources may disappear, indexes may be rebuilt, rankings may shift, citations may change, interfaces may vary, and previously observed results may no longer appear.

Every Recognition Event is limited by its documented observation date, review period, system, interface, conditions, evidence, classification, scope, and continuity status.

Recognition Is Not Universal

Recognition observed within one system, model, interface, account, region, language, device, query, or review session must not be represented as universal recognition.

Broader public descriptions require broader qualifying evidence under the Recognition Thresholds and Recognition Levels standards.

Recognition Is Not Control

360WiSE does not control the internal operations of independent AI systems, search engines, media organizations, institutions, governments, platforms, applications, directories, databases, broadcasters, publishers, or public-information environments.

The Framework may publish structured records, maintain provenance, provide resolution endpoints, preserve evidence, and communicate corrections. Independent systems determine whether and how they retrieve, interpret, cite, classify, display, or omit that information.

Related Canon

The Recognition Protocol operates within the complete 360WiSE Framework and should be interpreted together with the related Canon volumes, protocols, standards, records, and technical specifications.

Revision History

Future material revisions should identify the version number, effective date, revision status, affected sections, and summary of substantive changes.

Earlier versions should remain available where appropriate to preserve public continuity, historical traceability, and transparent governance.