Scope
Confirm permission and the exact systems that can be tested.
AMPED RESEARCHPUBLIC ARCHIVE / 2026
>_RESPONSIBLE DISCLOSURE
Findings should read like evidence, not marketing.
This is where I publish technical notes and responsible disclosures. The archive is still young, so the process is visible too: what gets tested, what gets kept, and what is deliberately left out.
CASE / FLOW-001SAFE VALIDATION
01INPUTcontrolled marker
02BEHAVIORreproduced
03IMPACTbounded claim
04REPORTsanitized
hash / screenshot / request / timelineverified manually
PUBLIC DISCLOSURES0
METHOD NOTES1
PUBLICATION MODEMANUAL
DEFAULTPRIVATE FIRST
Method
The boring parts are what make the finding useful.
Signal
Reduce scanner noise until there is a behavior worth reproducing.
Evidence
Keep the minimum requests, hashes, screenshots, and notes needed to prove it.
Disclosure
Report privately, retest the fix, then sanitize before publishing.
ARCHIVEEMPTY BY DESIGN
No padded research feed.
I'm not filling this page with generic security articles just to make it look active. Real disclosures and technical notes will appear here when there is something worth publishing.
$ archive list --public0 disclosures$ statusbuilding research pipeline...