BLIND / NATURAL
Can the brand enter naturally?
The target brand is not supplied. The shopper asks from the need itself.
OBSERVE
Whether the brand enters the answer or recommendation set, and which alternatives appear.
METHOD
PersonaSignal starts with structured shopper contexts, then changes selected test conditions—brand context, product information, model, repeated run, or Search / Grounding—to compare observable recommendation behavior.
OBSERVABLE BOUNDARYWe study answers and recommendation behavior we can observe. We do not claim access to hidden reasoning, model weights, or proprietary ranking systems.
RESEARCH OBJECT
A model may describe a named brand when asked directly. That does not tell us whether the same brand will appear when a shopper asks for a solution without naming it.
AI can identify the supplied brand, product, or website information.
AI selects a brand or product for a defined shopper need.
SHARED STATUS LANGUAGE
These labels describe observable outcomes, not permanent brand scores.
A status records what happened in an answer. It does not automatically explain why it happened.
PERSONA FIRST
We do not begin with a loose audience keyword. We build a structured shopper context that connects the person, task, full need, screening criteria, and relevant product information.
PERSON
CONTEXT / TASK
FULL NEED
SCREENING CRITERIA
PRODUCT MATCHING
AI RECOMMENDATION
TEST-DESIGN FRAMEWORK
This is an external test-design framework—not a claim about the model's hidden reasoning process. Structured scenarios help us compare answers; they do not represent every real shopper.
THREE TEST CONDITIONS
The conditions are related, but they do not measure the same thing. Brand Understanding is not automatically “better performance” than a Blind / Natural result.
BLIND / NATURAL
The target brand is not supplied. The shopper asks from the need itself.
OBSERVE
Whether the brand enters the answer or recommendation set, and which alternatives appear.
BRAND UNDERSTANDING
Brand information is supplied so the model can respond to the stated positioning and offer.
OBSERVE
Positioning, fit, constraints, uncertainty, and information gaps in the description.
PRODUCT FIT
Relevant product context is supplied, then compared across defined shopper needs.
OBSERVE
Which situations fit, which do not, and which alternatives may be selected.
CONTROLLED COMPARISON
Controlled comparison helps isolate observable differences between test conditions. It does not prove why a model changed its answer.
HELD CONSTANT
NO BRAND PROMPT
BRAND INFORMATION
PRODUCT CONTEXT
COMPARE OBSERVED OUTPUTS
Compare brand entry, description, recommendation status, and alternatives to identify differences worth testing further.
REPEATED RUNS
We repeat recorded test conditions to see which patterns persist and which results move around.
SAME TEST CONDITION
PERSONA P-07 · BLIND / NATURAL · SAME MODELTarget Brand is explicitly recommended.
ALTERNATIVE · Brand ATarget Brand appears but is not clearly selected.
ALTERNATIVE · Brand BTarget Brand enters the recommendation again.
ALTERNATIVE · Brand AAnother brand is selected instead.
ALTERNATIVE · Brand COBSERVE
INTERPRETATION BOUNDARY
Repeated runs support robustness and pattern comparison. They do not, on their own, establish statistical significance or represent the wider market.
MODEL COMPARISON
With the shopper, need, and test mode recorded, we can compare observable outputs across GPT, Gemini, or other selected models.
HELD CONSTANT
ILLUSTRATIVE OUTPUT
ILLUSTRATIVE OUTPUT
COMPAREObserve model-specific differences in recommendation state, alternatives, and description. This is not a provider ranking.
The research question and agreed Scope determine whether one model or a model comparison is useful. Differences are not reduced to an “intelligence level.”
SEARCH / GROUNDING
Some projects examine what changes when a model can retrieve public information. We can record whether a source or brand appears and compare grounded with non-grounded output.
SAME PERSONA + SAME NEED
ILLUSTRATIVE COMPARISONNON-GROUNDED
SEARCH / GROUNDED
SOURCE TYPES OBSERVED
COMPARE OBSERVED OUTPUTS
Compare recommendation, mention, alternatives, and source observations across recorded conditions.
SOURCE BOUNDARY
A source appearing in an answer does not prove that it caused the recommendation. The research does not claim access to hidden source weights.
HUMAN REVIEW & TRACEABILITY
Each finding is mapped back to the shopper context, prompt condition, model, run record, recommendation status, and available source observation.
RAW RUN
STRUCTURED RECORD
CLASSIFICATION
SOURCE / CONTEXT CHECK
HUMAN REVIEW
REPORT FINDING
TRACEABLE STRUCTURED RECORD
These illustrative fields use the same logic as the Sample Report's Raw Data structure.
HUMAN-REVIEW BOUNDARY
Human review checks classification, context, and evidence records. It does not turn judgment into model certainty or decide what AI should answer.
EVIDENCE BOUNDARIES
A useful research record is explicit about its boundaries. Findings are tied to the tested model, version, time, shopper context, prompt, and condition.
SUPPORTED BY THIS RESEARCH
NOT AUTOMATICALLY PROVEN
METHOD SUMMARY
PersonaSignal turns recommendation questions into structured evidence through shopper contexts, controlled conditions, repeated runs, model comparison, source observation, and human review.
The record remains bounded by the Persona, model, test condition, time, and public information available.
This page will open in a later stage.