DEV Community

EmoPulse
EmoPulse

Posted on

Building a 5-layer neurosymbolic perception engine alone

Earlier this week, I found myself staring at a wall of code, wondering how I ended up building a 5-layer neurosymbolic perception engine by myself. It was a moment of exhaustion, but also a moment of clarity. I realized that the hardest part of building EmoPulse wasn't the technology itself, but the solitude of making decisions without a team to bounce ideas off of.

As I reflected on the past year, I noticed a pattern. Every time I thought I had made a breakthrough, I would soon realize that it was just a small step in a much larger journey. The stress classification path, for example, implements published peer-reviewed methodology from Giannakakis et al., which reports 93 to 96 percent accuracy on cohorts of N=48 to 58. But what does that really mean? It means that I have to trust the research, trust my implementation, and trust that it will work in the real world. It's a heavy burden to carry alone.

The technical reality of building EmoPulse is daunting. I've had to extract 47 biometric and behavioral signals from any standard RGB camera, all on-device in the browser via WebAssembly. The output is a structured state vector posted to a Flask /state endpoint on the server, with sub-50ms end-to-end latency from frame capture to state vector emission. It's a complex system, and one that requires a deep understanding of the underlying technology. I've had to rely on tools like MediaPipe and custom rPPG implementation to get the job done.

As I look back on the past year, I realize that building EmoPulse has been a journey of continuous learning. Every decision I make has a ripple effect, and every problem I solve reveals a new set of challenges. The liveness scoring system, for example, was a recent addition, shipped on 2026-04-08. It's a server-side anti-spoof scorer that runs on signals already in the /state payload, with a sliding window of last 5 ticks per session. It's a complex system, and one that requires careful consideration of the potential risks and benefits.

The journey of building EmoPulse is far from over. In fact, it's just beginning. As I move forward, I'm forced to confront the reality of my own limitations. I have to be careful not to overpromise and underdeliver, and I have to be willing to adapt to changing circumstances. The pre-seed round of EUR 2 million at EUR 6 million pre-money is just the beginning, and I know that the real challenge lies ahead. What will I learn next, and how will it change the course of EmoPulse?

Top comments (0)