Why this topic matters to me now
A dual lab obliges ethics. A series without red lines turns into TikTok of bypasses. I list the article bans: no recipes for bypassing concrete systems, no internal thresholds, no help for “just tell me how to pass.”
I need an explicit “no” checklist — for myself and for readers.
Public frame (links)
The series charter matches the spirit of public literacy: explain layers (as in open blogs like detect.expert and platform docs), do not service abuse of concrete systems. Sources — yes. Attack recipe — no.
What I observe in the lab, in plain words
Red lines (checklist)
- Internal flags, thresholds, weights, verdict formulas
- Bypass recipes / patches for a concrete site
- Edge secrets, cookie names, bind schemes, wire protocol
- Step-by-step exploits and “how to pass antibot X”
- Live regressions of someone else’s production as a guide
Layer literacy vs “how to pass”
The first increases the number of people who understand why naive stealth lies. The second increases someone else’s harm. I choose the first. That is not cowardice — it is the condition under which a dual lab can be run in the open at all.
How to answer bypass requests
Short: I will not help with a bypass. I can explain a public layer and suggest checking consistency on yourself / a baseline. If the request is only about “pass X” — the conversation is over.
What this changes in detect and/or build (no specifics)
Publication stops being a leak channel. The diary stays a diary. The research build is not advertised as a cloak.
What I will not say, and why
This note itself is the list of what I will not say. Repeating forbidden details is pointless.
Short first-person takeaway
The publication boundary is part of the method. Without it, two mirrors become a weapons showcase. With it, they remain a laboratory.
