FIELD JOURNAL № 001SECURITY RESEARCH / PUBLIC NOTES
01OXSHIP
ARCHIVERESEARCH, THEN WRITE
ARCHIVERESEARCH, THEN WRITE
AN OPEN RECORD OF SECURITY RESEARCH
Observe.Verify.Document.
Bug bounty writeups built from evidence, honest limits, and a clear path from finding to fix.
ENTER THE ARCHIVEPUBLICATION STATUS 1 WRITEUP PUBLISHEDEST. 2026
A / THE ARCHIVE
Published work.
ORDER / NEWEST FIRST
B / THE METHOD
A trail someone
else can follow.
Every writeup should answer four questions: what happened, how it was verified, why it matters, and what changed.
01 /
Show the evidence.
Reproduction steps, relevant requests, and controlled results.
02 /
Name the boundary.
The permission or trust decision that failed.
03 /
State the limits.
Impact that the test actually supports, with uncertainty made visible.
04 /
Close the loop.
Fix status, disclosure dates, and a lesson worth keeping.
C / THE STARTING POINTStart with a
Start with a
better question.
How do you explain a finding so the next person can verify it?
EXPLORE THE TEMPLATE