October: the application composer, a local tool that tracks and guides each job application, is in build for its first release.

October: I am testing whether a GrapheneOS phone sells better with an educational setup walkthrough, after reading the rules first.

October: every task now has a short launch code, typed as a word and a number, that is dry by default.

October: every utility I build now follows one rule, that the next task and its command fit one screen.

October: every open task of the build now sits on one page of this site, visible to the owner only.

September: the site gained a members' panel and a community page, just after a utilities list, each publishing summaries only.

Most SOCs do not have a detection problem — they have a signal-to-noise problem. Why the tuning loop, not the rule count, decides what gets caught.

A relocked bootloader, a hardware root of trust, and a boot chain you can independently verify — how verified boot actually works and why the discrete secure element matters.

Auditability, failure behaviour, and cryptokey routing: the comparison that matters in practice, grounded in running full-tunnel WireGuard on real infrastructure.

Everyone runs nmap. Fewer people read it properly. A practical tour of scan types, NSE, output, timing, and evasion.