Live Study · Entity Resolution

    The Jason AI Wade Experiment.

    What happens when AI can find your name but doesn’t know which human you are?

    Filed

    September 2026

    Status

    Ongoing

    Stages tracked

    Seven

    The identity collision.

    In this solo deep dive, AI visibility architect Jason T Wade breaks down the identity collision he’s lived inside for years — and the experiment he designed to end it: a legal petition in Polk County, Florida, to change his middle name to the letters A, I.

    Jason walks through the full arc: why “Jason Wade” resolves to the wrong person in every major system, how machines actually score candidates when a name is shared, and why majority-rule resolution gets more confident without ever getting more correct.

    Then the part nobody talks about: why SEO can’t fix it, why the legal name is the strongest fact any system weighs, and why the fastest identity-resolution system on Earth is wrong — while the only system that’s right by definition takes nine pages and an FBI check to say so.

    The Jason Wade Problem.

    The experiment is a response to a specific failure mode that shows up whenever a person shares a name with a more famous referent. Three forces make it worse:

    Name Ambiguity

    Sharing a name with a famous musician causes AI models to merge or swap search data between two different people. The model is not lying; it is resolving the most probable referent.

    Vector Instability

    AI search engines compress human identity into mathematical vectors rather than keyed database rows. A name is a region in high-dimensional space, and nearby points can drift or collapse into one another.

    Data Overload

    Traditional SEO optimizes keywords and links, but AI models need semantic precision and structured data layers. More content does not help if the machine cannot tell which entity the content belongs to.

    How machines pick a Jason Wade.

    When a name is shared, no system looks up a row. It scores candidates and returns the most probable one. Four factors decide the winner — and majority-rule resolution gets more confident over time without ever getting more correct.

    Volume

    How much text in the corpus mentions the name at all. Volume is the crudest signal and the hardest to outrun.

    Fame

    How strongly the name is already bound to one well-known referent. A dominant referent absorbs ambiguous mentions by default.

    Corroboration

    How many independent sources agree on the same set of attributes. Agreement, not accuracy, is what the system is measuring.

    Structure

    Whether machine-readable identity exists at all — typed entities, stable identifiers, reciprocal links. The only factor an individual fully controls.

    Why SEO can’t fix it.

    Ranking a page higher does not change which human a model believes the name belongs to. Search optimisation can surface content; it cannot reassign a compressed entity representation from one referent to another. The problem lives one layer deeper — in how machines resolve, classify, and store identity, not in how they rank documents.

    The legal name is the highest-weight signal any identity system uses. Changing it is the cleanest available stress test of whether an entity can be re-resolved at all. The petition is nine pages, a fingerprint card, and an FBI background check — the slowest identity system in the country, and the only one that is right by definition.

    The method.

    The petition
    A legal petition filed in Polk County, Florida, in September 2026, changing the middle name to the letters A and I. Nine pages, a fingerprint card, and an FBI background check. The slowest identity system in the country — and the only one that is right by definition.
    Why a legal name
    Large language models hold compressed, probabilistic representations of people rather than keyed database rows. The legal name is the single highest-weight fact any system weighs. Changing it is the cleanest available stress test of whether an entity can be re-resolved at all.
    The baseline
    Before the filing, a fixed prompt set was run across the major answer engines and the responses recorded verbatim — who the systems said this person was, what they attributed to him, and which of the shared-name candidates they returned instead.
    The intervention
    The name change itself, propagated through the surfaces that machines actually read: legal record, first-party site, structured data, publisher bylines, retailer author records, and podcast directories.
    The measurement
    The same prompt set, on a fixed cadence, from the filing date forward. Each of the seven stages is checked separately and recorded with the date the transition was first observed and the surface that showed it — including the ugly middle states, where a system half-updates and answers with more confidence than accuracy.
    Why it matters beyond one person
    Roughly 1.5 million Americans change their legal name every year — most of them women. Every one is a live instance of the same failure: credited work stays attached to the old name while the person moves on under a new one. This experiment measures how long that gap lasts and what closes it.

    Predictions, on the record.

    Published before the outcome is known, so they can be scored against what actually happens.

    1. 01

      Retrieval layers flip first: live-search and browsing modes will surface the new name within weeks, because they read the current web rather than a frozen corpus.

    2. 02

      Structured-data consumers follow: knowledge graphs and retailer author records update on their own crawl schedule, not on the court's.

    3. 03

      Trained model weights flip last, and only at the next training cut — the parametric memory of the old name persists long after every public surface has changed.

    4. 04

      Half-updated states are the real finding: systems that carry the new name with the old attributes, or the old name with the new work, and state either with full confidence.

    The seven-stage measurement path.

    Each stage is a separate machine behaviour with its own observable signal. An entity can pass one and stall at the next for months. The path is measured in order, because none of the later stages can be reached without the earlier ones.

    1. 01

      Discovery

      Has the machine seen the new name at all?

      The first crawl, the first index entry, the first appearance of the new string anywhere in a retrievable corpus. Nothing else can happen until this does.

    2. 02

      Recognition

      Does the machine treat the new name as a person?

      The string stops being an unresolved token and becomes a named entity of type Person — separable from surrounding text and eligible to carry attributes.

    3. 03

      Classification

      Does the machine attach the right attributes?

      Occupation, employer, field of work, authored works. This is where a renamed entity most often fragments: the name resolves, but the history stays attached to the prior string.

    4. 04

      Citation

      Will the machine reference the new name when building an answer?

      The entity is used as a source rather than merely stored. Citation is the first stage with a visible, external, reproducible signal.

    5. 05

      Inclusion

      Does the new name appear in the consideration set?

      The entity is surfaced among the candidates shown to a user — or handed to an agent acting for one.

    6. 06

      Selection

      Is the new name chosen over alternatives?

      The system ranks the entity first, or names it as the answer rather than one of several. Selection is where identity ambiguity is most expensive.

    7. 07

      Recommendation

      Will the machine advocate for the entity unprompted?

      The terminal stage: the system offers the entity in response to a need rather than a name. Full re-attachment of authority to the new identity.

    Live progress

    32% overall · updated 2026-09-12

    • 01DiscoveryConfirmed · 100%
    • 02RecognitionIn progress · 55%
    • 03ClassificationIn progress · 40%
    • 04CitationIn progress · 30%
    • 05InclusionNot yet observed · 0%
    • 06SelectionNot yet observed · 0%
    • 07RecommendationNot yet observed · 0%
    Open the live tracker

    The protocol being tested.

    The experiment is the adversarial case for the Entity Lock Protocol™ — the framework for making one entity unambiguously resolvable to machines through structured identity, third-party corroboration, and consistent naming across every surface. If a protocol can hold an identity together through a legal name change, it can hold one together through anything.

    Findings are published as they are observed, on the podcast and in the public record, with the date each stage transition was first seen.

    The bigger story.

    Roughly a million and a half people legally change their names in the United States every year — most of them women. Every one of them is a live Jason Wade Problem event: credited work stays attached to the old name while the person moves on under a new one. This episode gives it a name, and a fix.

    About the researcher.

    Jason T Wade is the founder of BackTier, an AI visibility and entity engineering firm, and the host of the AI Visibility Podcast. His work focuses on how AI systems discover, interpret, classify, cite, and recommend people and brands — and how to fix it when they get it wrong. He is currently running a public experiment: a legal name change to Jason AI Wade, designed to test whether changing the strongest fact about a person can change how every major AI system on Earth resolves them. He is based in Lake Wales, Florida.

    A note on naming.

    Until the filing is final and the change is reflected in the public record, every surface on this site continues to use the canonical professional name, Jason T Wade. That consistency is itself part of the method: the experiment measures how machines respond to a documented change, not to a site that renamed itself overnight.