Adversarial view
Attack surfaces, trust boundaries, defensive controls, failure paths, and the evidence required to support a finding.
QUESTION: WHAT CAN BE ABUSED?FIELD NOTES / RESEARCH LOG
DOC DY-BLOG / RESEARCH LOGPractical research, engineering breakdowns, and observations from work across security and intelligent systems.
02 / RESEARCH COMPASS
The compass describes the questions behind the writing. It does not imply a published note exists for every topic; the archive below remains the source of truth.
Attack surfaces, trust boundaries, defensive controls, failure paths, and the evidence required to support a finding.
QUESTION: WHAT CAN BE ABUSED?Interfaces, state, dependencies, deployment conditions, and the contracts that keep behavior understandable.
QUESTION: HOW DOES IT HOLD TOGETHER?Grounding, retrieval, data quality, refusal boundaries, human review, and where model assistance is genuinely useful.
QUESTION: WHAT MAKES THE OUTPUT TRUSTWORTHY?Observability, release evidence, incident learning, recovery paths, and the gap between a passing build and a working service.
QUESTION: WHAT HAPPENS AFTER RELEASE?Strong notes often cross more than one track: a security decision changes architecture, an AI evaluation changes product behavior, and an operational failure changes both.
02 / FEATURED
A short selection of foundational notes and current investigations.
A field note on separating public pages, mutable content, contact input, and administration in a Flask portfolio application.
Read note ↗A practical evidence model for describing prototype systems without turning an implementation claim into a production claim.
Read note ↗03 / ARCHIVE
Ordered from the latest dispatch backward.
04 / PUBLISHING STANDARD
Writing is treated as part of the verification process: a way to expose reasoning, supporting material, uncertainty, and the decision that follows.