Research.
Formal work moves slowly and becomes visible only at the end. This page keeps score honestly — what's under review, what's done, and the questions that stay open longer than any paper.
Under review
A paper on cloud resource allocation is currently under review. Venue, title, results, and figures stay off this page until the process concludes — double-blind review is part of the work, not an obstacle to it.
context → the Auctus case study
Recent work
Full publication list available on request.
Open questions
who owns a refactor?
Git credits the last hand to touch a line — so a refactorer quietly inherits authorship of code they never designed. Any provenance system that can't tell restructuring from authorship is measuring the wrong thing.
can allocation be fair and efficient under adversarial load?
Markets clear efficiently and starve whoever bids lowest; queues are fair and waste everything. The open question is whether a mechanism can price contention without letting the deepest pockets always win — Auctus is one attempt to find out.
what does provenance mean when the author is a pipeline?
When a model writes the code and a human approves it, neither is cleanly the author. Provenance may have to record a chain of custody — who signed off, under what key — rather than a single name.
how much of infrastructure is secretly a pricing problem?
More than anyone admits. Rate limits, quotas, priority classes, retry budgets — each is a price refusing to call itself one. See contention as a market and half of infrastructure design turns out to be economics in a trench coat.
linger on a question for where the thinking stands — they outlive any answer, though; a good question is a research program wearing modest clothes