readme: ambient-drift baseline result — zero registrations on 100 v2 candidates over ~1.4h

1006f9101531eb5f4ec5ce4659a922a525b2ae71 · 2026-05-12 19:13:57 -0700 · steve

Re-checked both v2 cohort batches at ~1.4h post-generate (no lure ever
fired). Results: pronounceable 29/50 -> 29/50 (zero change per-bucket
across A/B/C/D/E), brand-adjacent 38/50 -> 38/50 (same). 100 candidate
names exhibited zero ambient registration in a ~1h window.

This is a hard experimental baseline. If a future v2 lure produces
snipes > 0, those snipes are attributable to the lure itself, not
random ambient demand on lookalike names. Critical control for the
desirability-hypothesis experiment.

Spot-check curve update: 0/280 across 24 datapoints (5.60h slice 8-9
just landed via the extracted spotcheck.js).

Files touched

M README.md

Diff

commit 1006f9101531eb5f4ec5ce4659a922a525b2ae71
Author: steve <steve@designerwallcoverings.com>
Date:   Tue May 12 19:13:57 2026 -0700

    readme: ambient-drift baseline result — zero registrations on 100 v2 candidates over ~1.4h
    
    Re-checked both v2 cohort batches at ~1.4h post-generate (no lure ever
    fired). Results: pronounceable 29/50 -> 29/50 (zero change per-bucket
    across A/B/C/D/E), brand-adjacent 38/50 -> 38/50 (same). 100 candidate
    names exhibited zero ambient registration in a ~1h window.
    
    This is a hard experimental baseline. If a future v2 lure produces
    snipes > 0, those snipes are attributable to the lure itself, not
    random ambient demand on lookalike names. Critical control for the
    desirability-hypothesis experiment.
    
    Spot-check curve update: 0/280 across 24 datapoints (5.60h slice 8-9
    just landed via the extracted spotcheck.js).
---
 README.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/README.md b/README.md
index d26f04e..04abbce 100644
--- a/README.md
+++ b/README.md
@@ -88,6 +88,8 @@ The v1 0-result over 120 DoH checks across 13 datapoints is the headline finding
 
 **Safety gates** — `generate` and `check` always allowed (no leaks). `lure` is **refused** unless `LURE_CONFIRM_LEAK_2026=yes` env is set as a one-shot Steve gesture; YOLO autonomous loops cannot trigger it. The lure body itself is currently a stub — wire-up before re-firing.
 
+**Ambient-drift baseline (2026-05-13)** — both v2 cohorts re-checked ~1.4h after generation, *no lure ever fired*: pronounceable 29/50 → 29/50 (zero change per-bucket too), brand-adjacent 38/50 → 38/50 (zero change). So **the natural registration rate on these specific candidate names is zero over a ~1h window**. Any future v2 lure result with snipes > 0 is directly attributable to the lure rather than ambient demand.
+
 ## Known issues — public CT-log infrastructure is fragile
 
 State of the world for **free** real-time CT-log access, as of 2026-05-12 ~23:05 UTC:

← e3b60de inspect: --summary flag for one-line YOLO status · back to Domain Sniper · spotcheck: harden newestHoneypot() regex to exclude -results fb0cf73 →