Interactive Proof

Documentation

From paper to a clear explanation.

Interactive Proof is designed to start with your own paper. Upload a PDF, select the passage that is hard to follow, and ask for a plain-language explanation. Add a server-side key only when you are ready to request live explanations.

Upload a paperOpen an upload workspace

01

Start with a paper of your own.

Open the upload workspace, give consent for temporary browser storage, and add a paper PDF. The file stays in your tab while you choose the sentence, equation, or proof step that needs more context.

  1. Open the upload workspace and accept the temporary-file consent.
  2. Add a PDF, then select a sentence, equation, or proof step.
  3. Choose an action such as More details or Explain more simply.
  4. Open the source disclosure when you want to review what shaped the explanation.

02

Add Lean only when it helps.

The upload workspace accepts optional individual .lean files or a ZIP of Lean sources alongside the required PDF. Add Lean when you want to connect an informal passage to formal code.

Temporary by design.

Only the selected passage and bounded nearby context are sent when you explicitly request an explanation. Uploaded Lean is labeled unverified.

Review the upload consent and limits

03

Enable live AI explanations.

Keep the OpenAI key on the server. Never paste it into browser code, commit it to Git, or give it a NEXT_PUBLIC_ prefix.

Local development

cp .env.example .env.local
# Edit .env.local and set:
OPENAI_API_KEY=your_key_here
OPENAI_MODEL=gpt-5.6
npm run dev

Restart the development server after changing environment variables. Without a key, the reader remains available and explanation requests return an explicit configuration error.

Hosted deployment

Add OPENAI_API_KEY using the host's secret manager. AddOPENAI_MODEL, EXPLAIN_RATE_LIMIT_PER_HOUR, and an explicit PUBLIC_PROOF_IDS internal-fixture allowlist as environment variables, then deploy a new version. The public demo starts with uploads and currently uses the GPT-5.6 deployment configuration.

04

Know what each source detail means.

From the paper
This is the passage or claim selected from the paper.
From uploaded Lean (unverified)
This points to optional Lean source supplied with the paper; it is context, not a verification claim.
Helpful background
A short definition or reminder that makes this step easier to follow.
In plain English
A focused explanation of the selected passage, with notation added only as needed.

The explanation starts with the idea. The source details stay available when you want to check the exact paper passage or optional Lean excerpt.

Read the evaluation and security methodology

05

Run and verify the project locally.

npm ci
cp .env.example .env.local
npm run dev

# Before a release
npm run proof:validate
npm run eval:validate
npm test
npm run typecheck
npm run lint
npm run build

Node.js 24 is required. Chromium is needed only for browser tests, and Lean is needed only when regenerating the proof check for a full local proof package.