Understand risk before expanding scope.
Useful for threat modeling, attack-surface questions, authorization boundaries, vulnerability validation, or defensive workflow design.
CONTACT / OPEN CHANNEL
DOC DY-CONTACT / OPEN CHANNELLET'S
TALK.
Bring a difficult problem, an ambitious build, or a role where security and engineering need to work as one.
01 / ENGAGEMENT FIT
Useful starting points for a conversation.
A clear first message does not need a finished specification. It should identify the operating problem, the people affected, and the decision or outcome that matters.
Turn an operational need into a testable system.
Useful for secure web applications, internal tools, workflow platforms, dashboards, and carefully bounded prototypes.
Decide where model assistance belongs.
Useful for retrieval, classification, analysis, evaluation design, human-review boundaries, and accountable automation.
Make a difficult failure observable.
Useful for deployment faults, integration boundaries, data-flow problems, release evidence, and structured technical investigation.
Four details are enough to begin.
- 01What is happening now?
- 02Who is affected and what do they need?
- 03What constraints or risks are already known?
- 04What would a useful next outcome look like?
SAFE CHANNEL: Do not submit passwords, API keys, credentials, or production secrets through this form.
01RECEIVERead the problem and context.
02CLARIFYIdentify missing constraints.
03SCOPEDefine a safe next step.
04RESPONDReturn with questions or a direction.
01 / START A CONVERSATION
Tell me what you are building.
I read every message and usually respond within 24 hours. For time-sensitive work, email is the fastest route.
- Bhaktapur, Nepal
- NPT / UTC +05:45
- Available for opportunities