TL;DR — Not "finished." Not "toy project" either. Somewhere in the middle, and here's an honest breakdown of exactly where, feature by feature — including what's genuinely solid and what still needs work.
Most launch posts only show the highlight reel. This one's different — a real self-audit of where ATLOCK v4 stands right now, graded feature by feature.
Low-level WH_KEYBOARD_LL hook, background watchdog killing Task Manager instantly, full input blocking. This has been battle-tested the most (including on myself, more than once). Solid.
NTFS ACL manipulation at the OS permission layer — not a password wrapper. This is the most technically ambitious part of the project. Handle-lifecycle edge cases (already-open handles surviving an ACL change) are handled, but I wouldn't call this "battle-tested at scale" yet — it's been through my own extensive testing, not thousands of real-world environments.
AES (Fernet) + PBKDF2-HMAC-SHA256, 200,000 iterations. This is a real jump from v3's weak encoding scheme. The cryptography itself is standard and correct — I'm not rolling my own crypto, which is the right call at this stage.
