FIELD NOTES / RESEARCH LOG

DOC DY-BLOG / RESEARCH LOG

FIELD
NOTES.

Practical research, engineering breakdowns, and observations from work across security and intelligent systems.

2 PUBLISHED NOTES2 CATEGORIESEVIDENCE STANDARD APPLIED

02 / RESEARCH COMPASS

Four lenses for reading the archive.

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.

N / SECURITY

Adversarial view

Attack surfaces, trust boundaries, defensive controls, failure paths, and the evidence required to support a finding.

QUESTION: WHAT CAN BE ABUSED?
E / SYSTEMS

Structural view

Interfaces, state, dependencies, deployment conditions, and the contracts that keep behavior understandable.

QUESTION: HOW DOES IT HOLD TOGETHER?
S / APPLIED AI

Evaluation view

Grounding, retrieval, data quality, refusal boundaries, human review, and where model assistance is genuinely useful.

QUESTION: WHAT MAKES THE OUTPUT TRUSTWORTHY?
W / OPERATIONS

Field view

Observability, release evidence, incident learning, recovery paths, and the gap between a passing build and a working service.

QUESTION: WHAT HAPPENS AFTER RELEASE?

03 / ARCHIVE

All writing.

Ordered from the latest dispatch backward.

01 / 28.07.2026SYSTEMS · 4 MIN

How a Flask portfolio platform separates public content from administration

02 / 27.07.2026SECURITY · 4 MIN

What makes a prototype project page trustworthy?

04 / PUBLISHING STANDARD

What a useful field note should contain.

Writing is treated as part of the verification process: a way to expose reasoning, supporting material, uncertainty, and the decision that follows.

01QUESTIONDefine the decision or failure being investigated.
02EVIDENCEShow observations, sources, tests, or reproducible behavior.
03LIMITSState what the material cannot establish.
04OPERATIONAL TAKEAWAYTranslate the finding into a decision, control, or next test.