// most of my best work never reaches a public repo

I work one layer below the interface — in the protocols, runtimes and bytes most people never look at. Half the craft is reverse engineering: taking systems apart until I understand them completely. The other half is building — Go and Rust backends, LLM pipelines wired with LangChain / LangGraph and PyO3, and scrapers that keep running quietly while I sleep.

What you can see here is a deliberately thin slice. The work I'm proudest of tends to stay private.

type Mignon struct {
    Role    string   // senior engineer · reverse engineer
    Domains []string // LLM · web RE · anti-bot · backend · android
    Stack   []string // C · C++ · Go · Rust · Python · Java · Kotlin · JS/TS · Smali · ARM asm
    Tools   []string // IDA · JADX · JEB · Chrome DevTools
}

// the only invariant that always holds:
//   len(private work)  ≫  len(public work)

A handful of things I've let out into the open:

• mcp-tools-controller · npm — treat every MCP server as a plugin: validate it on connect, manage it from the CLI or from the model itself, and aggregate every tool behind one hot-reloading MCP gateway.
• mignonFramework · PyPI — a batteries-included Python toolkit for serious web scraping: stdout-intercepting logging, DI-based config, a Node.js bridge for executing JS, task queues, DB ops and file utilities.
• mignon-framework · npm — the Node.js half of the toolkit: the JS-execution bridge behind reverse-engineering and anti-bot workflows.