The Living Gate
A bet, registered in public, before the run.
The puzzle gate on our home page is a hypothesis we are willing to lose. Here is what we predicted, what would refute us, and how you will see the result — in plain words, with receipts, including the nulls. The instrument is warming up; first-party events are flowing now, and live posteriors land when the engine ships.
Where this stands today
Instrument warming up. Hypothesis already public.
- Pre-registered
- 2026-06-25 (this page)
- Instrument state
- Warming up. Capturing first-party events; live posteriors land in Phase 3.
- Decision rule
- Demote the gate if, after the registered window, gated-path inbound quality is at or below the skip path.
- Measurement
- First-party, no PII, no third-party trackers. DNT and the Global Privacy Control are honored absolutely.
- Store
- Our own iron (sovereign Postgres on the UNI Lab appliance). The website never holds personal data.
The hypothesis
One bet, four pillars, written down before the result is in.
We do not get to move the goalposts once the data lands. So we register them here, dated.
- 01
The bet
An opaque first impression — a small puzzle solved before the page reveals — qualifies the rare high-intent visitor, while losing the wrong volume on purpose. This is conjecture, not faith.
- 02
What would refute it (FALSIFIES)
If, after the registered window, gated-path inbound quality is at or below the skip-path, OR if cold/search traffic exits sub-five-seconds at a rate that materially exceeds skip-path, OR if engaged-session rate from the gated path is at or below the skip path — the bet is refuted. Demote the gate, report it as FAIL, name the next thing to try.
- 03
What would confirm it (PASS, conjunctive)
ALL of: gate completion rate stays above the registered floor, engaged-session rate from the gated path materially exceeds the skip path, source × behaviour shows the predicted population split, and inbound quality from the gated path is higher than the skip path on a pre-registered window.
- 04
How we will report it
Verdicts are discrete: PASS, PARTIAL, FAIL, or WITHHELD. Never a percentage and never spun. Every number on this page will point to a commit, a stored artifact, and a query that reproduces it.
We adopt the Lab Protocol’s discipline: one cure at a time, gates written first, verdicts that can lose. Operational behavioural and organisational measures are necessary-not-sufficient substrates with ZERO evidential weight for awareness, consciousness, or life on their own. The reverse-filter is a hypothesis about conversion-pool composition, not about minds.
The signal set
What we measure, by source, ourselves.
First-party only. No Google Analytics. No third-party trackers. No bounce-rate kill-switch (bounce is deprecated as a quality metric; we compute engagement ourselves).
- Gate start → completion
- By source. Confirms: healthy completion among the right visitors. Weakens: heavy bleed before solve.
- Engaged-session rate
- Self-computed (>10 seconds OR a key event OR 2+ views). By source. Bounce-rate kill-switches are deprecated; we never use bounce.
- Source × behaviour
- Does direct/referral traffic finish as directed explorers, or quit as friction casualties? The reverse-filter bet predicts the first.
- Inbound quality, not count
- The decisive one. Richness of the intake. Lower-volume / higher-quality from the gated path would confirm. Equal or worse refutes.
- Reveal → contact efficiency
- Time from gate reveal to a meaningful action, solved-path vs skipped-path. Tests whether the gate sharpens intent or just delays it.
- Return-visit quality
- Salted-daily cohort, no durable identity. Reverse filtering can also work through delayed qualification.
- Sub-5s trust exit
- An early-warning that cleverness is costing credibility. If this rises sharply for cold traffic, polish beats cleverness — and we say so, fast.
Where the data goes
Our own iron, never on the internet.
The browser fires a small, no-PII event to a sovereign endpoint on our server. The endpoint validates the event against an allowlist, computes a salted, day-scoped identifier server-side (it cannot be linked across days, by construction), strips anything outside the allowlist, and writes the row via a database role that can only INSERT — not read, not delete, not modify. The database itself stays on a private mesh and is never reachable from the public internet.
When either Do-Not-Track or the Global Privacy Control header is present, the browser sends nothing and the server records nothing. There is no opt-out flag to store because there is nothing to opt out of once suppressed upstream.
The honesty fences
What this is, and is not, claiming.
- 01
We publish nulls and refutations, not just wins. A PARTIAL is reported as PARTIAL and never spun into the larger story.
- 02
The site never stores name, email, IP address, raw User-Agent, form content, or any durable cross-day identifier. A short-lived session ID lives in your tab only.
- 03
Do-Not-Track and the Global Privacy Control are honored absolutely — when either is set, no event is recorded and nothing is sent.
- 04
The on-site engine is a faithful lightweight subset of the categorical active-inference core (UNI). It is not, and will not be presented as, the research engine itself.
How to push back
You can break this in public.
If our reasoning is wrong, the place to say so is on the record. Bring a counter-prediction, a measurement we are missing, or a claim you can show is not falsifiable. We will respond in plain words, on the record.