Letter of Introduction

Hello,

I am an independent systems engineer who builds tools that can be checked. My through-line across every domain is simple: make the work observable, make the claim verifiable, and make the result useful to someone outside the build process. I would rather ship a small thing that anyone can inspect than a large thing that has to be taken on faith.

My current focus is Project Telos, a public ecosystem for AI-era engineering. It is a working flagship line, not a slide deck: a shared perception and state engine (telos), repository and dependency intelligence (index), accountable multi-agent orchestration on a tamper-evident ledger (forum), evidence intake with provenance receipts (gather), a judgment organ that scores claims against measurements (crucible), a byte-level witness that returns MATCH, DRIFT, or UNVERIFIABLE (emet), and a typed-effects compiler with a verified C path (buildlang). Every one of these is a public repository with tests, docs, and a portfolio page, so the claims on my resume are things you can open and run.

I also know how to ship a product that real people use and keep using. Elder ENB, a graphics and lighting preset I built for Skyrim Special Edition, has earned 900,000+ downloads on NexusMods, with more than 150,000 unique downloaders, developed and maintained over roughly two years across about 280 releases and several named editions. It is public and verifiable: nexusmods.com/skyrimspecialedition/mods/117327. That work taught me how to release often, listen to an active user base, fix things under pressure, and sustain a creative product long past the first version.

My background is deliberately broad. Before the engineering arc that became public in 2023, I spent years in technical support, compliance and technical documentation, and hands-on field operations. Those domains now inform how I build: I write so non-engineers can follow, I assess risk quickly, and I design for the version that survives contact with the job rather than only the diagram.

I am open across roles, industries, and work modes: onsite, hybrid, remote, contract, full-time, part-time, and project-based. The strongest fit is any environment that needs someone who can enter ambiguity, map the moving parts, learn the domain fast, build a reliable artifact, and explain it to technical and nontechnical people alike.

If that is useful to you, I would welcome a conversation. The fastest way to judge whether we should work together is to open the work itself, which is exactly how I designed it.

Thank you for your time,
Zain Dana Harper