Why we submit our engineering to peer review

Most software is measured against a single question: did the client sign off? It's a comfortable bar. It is also a low one.

At Leaf Monkey Labs we hold our work to a harder test. Where the engineering is genuinely novel, we write it up and send it to venues that don't care whether the client was happy — ISPASS, MDPI, and IEEE. Reviewers who have never met us, and have no reason to be kind, decide whether the reasoning holds.

That process is uncomfortable by design. A reviewer will not accept "it worked in the demo." They want the assumptions stated, the method reproducible, and the numbers defensible. Preparing work to survive that scrutiny forces a level of rigour that day-to-day delivery rarely demands.

The discipline travels back into the product

Here's the part clients don't always expect: the rigour doesn't stay in the paper. Once you've had to defend a design choice to a stranger, you carry that habit into every decision. You document the seams. You name the trade-offs. You stop hand-waving.

The result is software whose logic you can actually reason about later — when regulations change, when the team grows, when someone asks "why is it built this way?" There's an answer, and it's written down.

Research that earns its keep

We're not a research lab that happens to consult. We're a studio that ships — and our applied research feeds directly back into what we build, for clients and for our own products. Publishing is how we keep ourselves honest, not a vanity exercise on the side.

"We can defend our engineering choices to a reviewer, not just a client."

"Labs" in our name is a promise: this is a studio that publishes, not just ships. Peer review is how we keep that promise.