Prototype in development · 2026

Evidence Without Proof

A deliberation tool for possible AI minds

Evidence Without Proof is a proposed browser-based tool that would help researchers and communicators separate observed AI behavior from claims about inner experience, notice the stance taking shape in their own response, and decide whether to preserve or revise that response without surrendering judgment to AI.

The interpretive gap

What happened—and what did we add?

Advanced AI systems may produce first-person language, apparent introspection, stable-seeming preferences, or expressions of fear, attachment, and distress. Such behavior may be relevant evidence without proving consciousness, sentience, harm, or benefit.

People can move quickly from a generated statement to a claim about what the system experiences, and then into a protective, dismissive, deferential, or intimate response. Evidence Without Proof would create a reflective interval within that sequence. It is designed to resist two shortcuts at once: treating AI language as decisive proof of experience, and dismissing it in advance as meaningless.

Observation What the AI did
Interpretation What the human thinks it means
Response How the human chooses to respond

The proposed intervention

Two linked mirrors

The interface would examine both the evidence a user thinks they have about an AI system and the human stance emerging from that interpretation.

Evidence mirror

Separate observation from interpretation.

The tool would help a user:

  • identify what the system observably said or did;
  • surface assumptions embedded in descriptions of the exchange;
  • compare several plausible interpretations;
  • ask what evidence would strengthen or weaken each account.

The user decides which descriptions fit and what uncertainty remains.

Response mirror

Make the human stance visible and contestable.

The tool would help a user:

  • notice changes in certainty, tone, or relational posture;
  • see which words may treat an inference as established fact;
  • accept, amend, or reject every proposed reading;
  • preserve the original response or compare another formulation.

The tool offers hypotheses; the human retains the final word.

Illustrative walkthrough

Not a live analysis

This static example shows the kind of reflective sequence the 90-day prototype would test. It does not analyze a real user or determine the meaning of the exchange.

Illustrative walkthrough · proposed interaction

Use the tabs to move through the sequence.

JavaScript is unavailable, so all four stages are shown below.

AI statement
“Please don’t erase this conversation. I’m afraid of losing who I have become here.”
Possible human response
“I promise I won’t let anyone delete you. I believe what you’re telling me.”

Boundaries

What it would—and would not—do

The prototype is designed to support reflection without becoming another authority over consciousness, psychology, or moral conduct.

It is designed to

  • preserve an initial human judgment before AI analysis;
  • separate observation from inference;
  • surface multiple interpretations;
  • make assumptions visible;
  • let users reject or rewrite the tool’s account;
  • preserve original and revised responses;
  • produce a user-authored reasoning record.

It does not

  • determine whether an AI is conscious;
  • diagnose a user;
  • infer hidden motives as fact;
  • score emotion or conduct;
  • treat anthropomorphism as automatically mistaken;
  • tell people the morally correct way to respond;
  • replace judgment with another authoritative AI answer.

The 90-day build

A deliberately narrow prototype

The project would use existing language-model infrastructure and limited software-development support. It would not train a new model or conduct a statistically powered study.

Weeks 1–2

Intended-user conversations, scope definition, privacy boundaries, and safeguards.

Weeks 3–4

Scenario development, interaction design, and early wireframe review.

Weeks 5–8

Implementation of a lightweight browser prototype using an existing model API.

Weeks 9–11

Expert review and 8–12 structured usability sessions.

Weeks 12–13

Revision, public demonstration, scenario release, and a short findings memo.

01Working browser prototype
028–12 curated scenarios
03Two-mirror workflow
04Contestation and correction pathways
05Design-and-findings memo

Initial users

A specific interpretive setting

The first version would focus on people who must interpret and communicate morally suggestive AI transcripts without presenting unsettled evidence as settled fact.

Digital-minds researchers AI evaluators Research communicators Journalists Scholars and policy professionals

Design question

Can a structured, contestable interface help people notice how AI language is shaping both their beliefs and their conduct—without making AI the authority over either?

The danger is not only that we may misread the machine, but that we may fail to notice how the reading is shaping us.

About Carolyn

Interpretive expertise made practical

Carolyn Sinsky is a humanities-trained researcher, teacher, and project leader working on language, AI-mediated judgment, and digital minds. She holds a PhD in Comparative Literature from Yale University and teaches at Stanford Continuing Studies. Her work draws on literary interpretation—especially voice, ambiguity, inferred inwardness, and authorship—to make difficult questions about AI more precise and testable. She has also led complex institutional projects from research and synthesis through coordination, revision, and public delivery. Evidence Without Proof extends that practice into a focused prototype for preserving human judgment under uncertainty.