What this app does
This is a tool for running multi-day ARV consensus experiments. You pick a YES/NO question about the future (e.g. "Does HBAR reach $0.076 by July 4th?"), build two pools of blind image targets, and run repeated blind viewing sessions against them over several days. At the end, the app tallies how many sessions leaned YES vs NO and shows you the pooled consensus — a rough approximation of the classic "many viewers vote, majority wins" ARV model, but run solo across repeated sessions instead of many people.
Step 1 — Create an experiment
Go to the 🧪 Experiments tab. Type your question exactly as you want it (precise thresholds and dates — "greater than", "by July 4th 2026", etc. — matter, per your own protocol). Set a target date, the date the real answer will be known, and click + Create experiment.
Step 2 — Build Pool A and Pool B
When you create the experiment, choose how many targets each pool holds (default 5 — set it higher, e.g. 20, for a bigger jury). Each pool needs the same number of pairs. For each pair, give a YES label and a NO label (e.g. "Rocket / green candle" vs "Flat line / red candle") — optionally attach an image to each side too, either by pasting a URL or clicking 📎 Upload to pull one straight from your computer.
For bigger pools, add targets in bulk with 📤 Import CSV instead of one at a time. Not sure what the file should look like? The 📋 CSV Template tab generates a blank, correctly-formatted spreadsheet for you — set how many rows you need, download it, fill in your labels in Excel, then import. 📥 Export CSV on a pool card lets you pull an existing pool back out to edit in bulk and re-import.
Made a typo, want to swap a label, or change an image? Click the ✏️ icon on any target row to edit its YES/NO labels and URLs in place — no need to delete and re-add it.
Pool A and Pool B are just two independent sets — use them however fits your design (two time slots, two viewer conditions, two techniques, whatever). Nothing forces a particular meaning onto them.
Step 3 — Run sessions
Once both pools are full, a Session runner appears. Pick a Day number, then click 🎲 Rotate codes for Day N — this reshuffles every code across both pools so you can't consciously recall which code you called YES/NO on a previous day. Then click ▶ Pool A session or ▶ Pool B session to jump into a normal blind viewing session (ideograms, sensory tags, sketches, summary) for a random not-yet-run target from that pool/day. When you reveal and pick YES or NO, it's automatically logged against this experiment, day, and pool.
Why there are three Target #s per pair, not one: each target pair has its own blind Target # (what you see and focus on during the session), plus a separate, independent Target # baked into the YES image and another into the NO image — revealed only after. Earlier versions used one shared number for the whole pair, which meant that single number was linked to both images at once — enough for impressions to blend across both sides instead of describing just the one true outcome. Splitting it into three unrelated Target #s means the number you're viewing has no association with either image until reveal.
Shortcut: the 👁 Session tab also has 🎲 Random Pool A / Random Pool B buttons that jump straight in for whichever experiment you last had open — handy once you're mid-way through a run and don't need to revisit the Experiments tab each time.
Step 4 — Read the results
Scroll down on an open experiment to see the Results card: a day-by-day breakdown (Pool A YES/NO count and Pool B YES/NO count for each day), plus an overall consensus across every session logged so far.
Step 5 — Mark the outcome
Once the real-world answer is known, open the experiment and click Actual answer: YES or Actual answer: NO under Results. This is a one-time click for the whole experiment — not another session pick, and not something you redo per pool. It's just telling the app what actually happened.
The moment you do this, two things happen automatically:
1. The app compares the real answer to your pooled consensus and shows a clear ✓ HIT or ✗ MISS for the experiment as a whole — this is your calibration data for future decoder refinement.
2. Every individual session you logged for this experiment gets auto-scored in your Log: if that session's pick matched the real answer, it's marked Hit; if it didn't, it's marked Miss. You never have to go score ARV sessions manually — this is the only step that scores them.
If it ever looks like a session "shouldn't" have scored as a Hit, remember: for ARV, a Hit just means your pick matched the real outcome — it's not a subjective judgment call the way CRV scoring is.
Step 6 — Save a permanent copy
Nothing here requires a manual "Save" — every experiment, pool, and session is written to your browser's local storage the moment you create or log it, and it'll still be there next time you open the app on this device.
But local storage lives only in this browser. To keep a copy you can archive elsewhere — email to yourself, drop in a folder, back up before clearing browser data — click 📄 Export experiment report (.txt), found just below the Results card. It downloads the full picture: question, day-by-day tallies, overall consensus, outcome, and the complete session log.
Optional — AI collaboration (Claude decode comparison)
Inside a session, there are two buttons — 🔮 AI guess what the target is (before reveal) and 🤖 Get AI match analysis (after reveal) — that send your session data to Claude (Sonnet 4.6) and get back its own independent read, so you can compare your decode to the AI's.
There's also a 🤖 AI decode button on each entry in the 📓 Log tab — for sessions where you saved your impressions without revealing or picking YES/NO yet. It looks up the real pair behind that session (by its stable internal link, not the Target #, so it still works even after codes have rotated), and has Claude make its own independent YES/NO call from your notes alone. If you've already made your own pick, it also shows whether the AI's call matches yours — so you get both readings side by side, per session, without ever having to look at the target yourself.
These need your own Anthropic API key to work — a Claude.ai subscription (Pro, Max, etc.) does not include this; API access is billed separately, per token, through a different account. For light use (a guess + feedback call per session, a few dozen sessions a week) the cost should be small — likely just a few dollars a month — but it's a real, separate charge once you set it up.
To get a key, when you're ready:
1. Go to console.anthropic.com and sign up (or log in).
2. Verify your email and fill in the basic profile questions.
3. Add a payment method under Billing — the API has no ongoing free tier.
4. Go to Settings → API Keys → Create Key, name it something like "ARV app," and click Create.
5. Copy the key immediately — it's a string starting with sk-ant-, and it's only shown once.
Your key is never written into this app's files or pushed to GitHub — it's stored only in this browser's local storage, on this device, and sent directly from your browser to Anthropic when you use the AI buttons. Nobody else can see it. If you ever want to remove it, use the Clear button below.
Where everything else lives
Every session you run — from any experiment — also appears in your 📓 Log tab, in full detail (ideograms, sensory tags, sketches, summary, which target/day/pool it belonged to).
Click any sketch in the Log to open it fullscreen — you can draw directly on top of it to mark it up (arrows, labels, circles), and there's a Note on this sketch text box in the side panel for writing what a shape or mark meant to you. Click 💾 Save annotation to keep both; your original sketch stays untouched underneath.
Reading the 📊 Charts tab
Progress over time shows every scored session as a dot, plus a white trend line running through them.
• Each dot is one individual session, colored by what that session actually scored: red = Miss, amber = Partial, green = Hit, teal = Strong hit.
• The white line is not any single session — it's a rolling average: for each point, "of my last 5 scored sessions, what % were Hit or Strong hit?" It smooths out the noise so you can see whether you're trending better or worse over time, rather than reading too much into one lucky or unlucky session.
• Hover any dot to see that exact session's result alongside the rolling percentage at that point.
Score distribution is the donut chart — a simple breakdown of how many of your total sessions fall into each of the four rating buckets (Miss, Partial, Hit, Strong hit), so you can see your overall mix at a glance.
Both charts pull from every scored session across all your experiments combined — they're not filtered to just one experiment.
A few things worth remembering
• Don't review a prior day's session notes before running a new one for the same experiment — that breaks the blind protocol.
• Rotate codes before each new day, not mid-day, so a day's sessions per pool stay internally consistent.
• You can run multiple experiments at once — just make sure the right one is open before you hit the Session tab's quick-pick buttons.
• Creating an experiment with the exact same question as an existing one will warn you first, so accidental duplicates are easy to catch.
• Each experiment in the list has its own ✕ to delete just that one, or use 🗑 Clear all at the top of the list to wipe every experiment at once.
• Deleting an experiment removes its pools and tallies, but the individual sessions stay in your Log. If a session was still in progress on the Session tab when you deleted its experiment, that in-progress session clears automatically too.
• Local storage is per-browser and per-device — it won't follow you to a different computer or browser unless you export and re-import manually.