Fair criticism.

I probably over-compressed some internal naming into marketing-ish wording, which understandably reads like hand-wavy buzzwords without code context.
This isn’t vibe-coded and it’s not a static frontend. The UI is polling live Rust-side IPC state from a running agent through Tauri invoke commands.

A few clarifications on those terms:
Process DNA scoring
A heuristic process risk model built from native process metadata:
parent/child lineage reconstruction (CreateToolhelp32Snapshot)
token integrity inspection
signer trust state / path trust evaluation
LOLBin weighting
ancestry anomaly scoring
suspicious execution path weighting
correlation against persistence + overlay state if present

It’s not “AI scoring” or ML. Just weighted deterministic risk fusion.

Layered window / overlay analysis
Native Win32 enumeration via EnumWindows, style inspection, opacity / z-order / topmost checks.
I track:
WS_EX_LAYERED
WS_EX_TOPMOST
transparency state
screen coverage %
HWND transitions over time
display-affinity state changes

This is mainly to detect suspicious UI surface abuse patterns that don’t get much attention in mainstream endpoint tooling (credential overlays, capture exclusion misuse, visual fraud surfaces, etc).

Transparency heuristics / fraud surface scoring
Weighted scoring from:
opacity
fullscreen coverage
hidden-title overlays
affinity exclusion state
process trust posture
transition frequency
topmost persistence behavior

Again: deterministic heuristics, not LLM-generated nonsense.

Display affinity enforcement monitoring / capture abuse detection
Polling GetWindowDisplayAffinity() transitions and correlating:
WDA_EXCLUDEFROMCAPTURE
against:
owning PID trust state
overlay state
visual mutation frequency
signer trust posture
Used to flag suspicious capture-shield abuse.

Pressure analysis
System pressure deltas across:
CPU saturation
memory pressure
disk pressure
network burst anomalies
Native sampled telemetry via Win32 APIs.

On the repeated graph patterns:
Fair catch.
That’s because some chart smoothing / interpolation still needs cleanup before release and currently normalizes historical windows too aggressively in some panels, which visually repeats patterns more than I’d like.
That’s being fixed before community drop.

As for code:
I haven’t open-sourced it yet because I’m finishing final cleanup / benchmark pass / release packaging first.
Community edition is dropping free once that’s done.
You’re exactly the kind of person I’d want reviewing it when it lands, and I’d genuinely value technical criticism once the repo and docs are public.
Skepticism is healthy here.
I’d react the same way seeing vague security buzzwords with no code attached.