Portfolio evidence

Accepted external work

These are third-party repositories where maintainers accepted the change. They are the first hiring signal because they show work crossing someone else's review boundary.

Download portfolio brief PDF · Download portfolio brief DOCX

1. Free Law Project: runnable database-free fast-test documentation for litigant-portal PR 820.
2. Hebbian Robotics: reserved-column drift test coverage for hflow PR 157.
3. Voxwire: offline websocket recording and replay coverage for PR 44.
4. DeepEval: unhashable tool-output correctness fix for PR 2822.
5. TOMLKit: dotted-key sibling preservation fix for PR 549.
6. Datasette: wrong-arity composite-primary-key row URLs return a client error rather than a server error.

Accepted external work is counted separately from open work and closed without merge work. Open is not accepted; it stays out of the accepted-work count until a maintainer merges or adopts the change.

Owned systems

The owned work is broad, but it is not used as an unsupported employment claim. It is public project evidence.

Current versions for Index, Gather, Forum, BuildLang, EMET, Crucible, Calibrate Pro and Phantom are kept in one place: the product catalog, which reads the public registry and release receipts.

1. Flywheel. Featured agent-work platform for model routing, verification, gated actions, local workflows, and receipt-bearing execution. It now carries a writing-quality linter served over MCP, so any harness can score prose against a register standard.
2. EMET. Byte-integrity witness CLI that emits re-checkable evidence receipts with Match, Drift, and Unverifiable verdicts.
3. Terminal State Fixtures. Exhaustive terminal-state evaluation fixtures for scoring outcomes rather than transcript claims.
4. BuildLang. Systems-language toolchain with typed effects, native output, shader backends, CLI, LSP, and build receipts.
5. Brender Archival. Retro-system preservation and presentation lane.
6. Engine Revival. Engine restoration and retro-computing crossover work.
7. Security work. Public-safe descriptions of authorized safety, evaluation, and high-security tooling without publishing controlled payloads.

Current employment targets

Technical support, developer operations, QA, evaluation tooling, Python developer tools, public operations, facilities, ports, utilities, fire-support, parks, grounds, and field-safety roles. Seniority and degree requirements are matched only when supported by the current authority or by an explicit equivalency route.

Boundary

Public pages omit phone, legal-name attestation, exact months, sensitive implementation details, private operational records, and recipient-specific safety material. Controlled work moves only through approved private intake channels.