Technical writing · systems analysis · software testing
I investigate how software behaves, test the boundaries of what can actually be claimed, and turn that understanding into documentation people can use.
I came to software from manufacturing and machine operation, where unclear instructions and misunderstood system behavior have immediate consequences. My current work focuses on software testing, technical documentation, evidence, provenance, and making complex systems easier to inspect and explain.
A local-first mapper for PowerShell codebases. Its documentation covers installation, first use, function review, export behavior, testing, and explicit limits on what its classifications and risk indicators prove.
An experimental Python utility for finding the smallest policy-compatible reusable part of an open-source tool that the current implementation can prove. The project emphasizes dependency closure, verification boundaries, licensing evidence, and conservative failure states.
An auditable large language model and model-behavior evaluation harness for deterministic testing, regression analysis, preserved evidence, and reproducible judgments.
A small technical-writing portfolio is being assembled here on GitHub, including explanatory articles and practical software documentation.