Operator mindset. Engineer execution.

How I got here.

Background, operating philosophy, and what I'm building next.

Background

The long way around is sometimes the right way.

I didn't start in cybersecurity. I started in security — the physical kind. Navy Master-at-Arms. Air Force Security Forces. Municipal law enforcement. Industrial armed first responder. Those roles taught me things no certification captures: how people behave under stress, where policy breaks down, how access controls fail at the seam between procedure and reality.

From there I moved into regulatory compliance and food manufacturing operations — where the adversary isn't always a threat actor, sometimes it's entropy, fatigue, and an untested SOP. That discipline — measure it, document it, validate it — transferred directly into how I now approach security architecture.

The formal technical foundation came through WGU: multiple degrees in cybersecurity and an MS in Computer Science with an AI/ML focus. I'm currently one exam from completing it. The credential matters less to me than what it represents: I can hold the full stack — physical security, system design, and applied machine learning — in the same mental model at the same time.

Philosophy

Boundaries matter. Failure is assumed.

Every system I've worked in — military, law enforcement, industrial, digital — has the same failure mode: someone assumed a boundary held. Assumed a door was locked. Assumed a log was being read. Assumed the policy was being followed.

I design against that assumption. The question isn't "is this secure?" It's "what does the attacker see, and what can I see when they move?"

What I'm building

WeanTech and applied research.

WeanTech is the vehicle for everything I'm building: Opaque Clarity Security, the WeanTech Swarm multi-agent system, OctopusONN (a biologically-inspired neural architecture for adaptive security), and applied research into insider threat behavioral escalation.

The applied research work is heading toward a PhD in Forensic Cyberpsychology — specifically the psychological escalation patterns that underlie insider threats before they become incidents.

Credentials

Formal qualifications

  • MS, Computer Science — AI/ML (WGU, in progress)
  • BS, Cybersecurity & Information Assurance (WGU)
  • MS, Cybersecurity & Information Assurance (WGU)
Operating notes

How I communicate

Email is the clean channel. Proton Mail by default — encrypted if the topic warrants it. I don't do discovery calls for low-signal inquiries. If you've read this far and have something real to discuss, reach out directly.

dweant@proton.me

PGP public key →

No tracking

No analytics, no pixels, no forms. This site doesn't collect data about visitors. If you want to reach me, the email address works.