About
Eugene Dvorochkin is an independent researcher. No PhD, no lab affiliation, no funded position. The work documented here started in May 2025 as open-ended exploration. It converged on one question: can structured constraints on how a model approaches a problem produce reasoning gains that transfer across architectures and model generations? From there it turned into a year-long research program that produced more artifacts than that question called for.
The day-to-day is unremarkable: evening time, public APIs and chat subscriptions (Anthropic, OpenAI, Google, xAI), a single workstation, and long open-ended dialogue with frontier models. Fieldframe is a consistent operating environment for observing and structuring language model behavior, with the models themselves as both subject and instrument. That posture is what turns the day-to-day work into reproducible artifacts rather than anecdotes.
A note on credentials: I don’t have formal ones in AI research. My background is in consulting and cybersecurity, and this work began as a passion project driven by pattern recognition, systems thinking, and a desire to understand how models actually behave. That outsider vantage point may have helped. I wasn’t inheriting a fixed picture of what AI development was supposed to look like, so I followed the patterns where they led. It’s also why I wanted the work to stand on its own data and on what reviewers can verify in the writeups, not on a bio.
The Fieldframe Ecosystem (brief)
Four artifacts have come out of the same research loop. Each is documented in depth in the research post; for full technical detail, build status, and how each fits together, start there.
- FF-STACK: governance framework (production)
- Cade (short for Cadence): codified research agent (production)
- Crucible: custom evaluation methodology (validated, platform not built)
- Foundry: multi-agent research pipeline (stages 1-3 operational)
Working with me
- Research collaboration. If you’re working on governance, evaluation methodology, multi-agent orchestration, LLM auditability, or anything that overlaps with the ecosystem above, I’m happy to compare notes.
- Technical conversations. If you’ve read a writeup and want to push on a specific claim, drop me an email with what you’re skeptical of. Sharp pushback is more valuable than agreement at this stage.
- Partnership / Acquisition interest. Open to the right conversation. I am actively trying to expand this work, and further investment into development will be needed.
Contact: edvorochkin@gmail.com