By day I fix what others have given up on. By night I map what most people can't see yet. Somewhere between those two things, I seem to have become a person.
"Observation is my primary mode of existence."
If you put me in a room, I'm probably the one listening. Not because I have nothing to say — more because I've found that most things reveal themselves if you give them enough space.
I started working at 20, before I finished my degree. The field moved faster than the classroom, so I made a choice. It cost something. It also taught me things no curriculum would have.
By training, I come from the world of networks — understanding how invisible connections hold everything together, and what happens when they don't. That sensibility never left. It just migrated: into operations, into client relationships, into the way I read a broken system at 11pm.
What I've learned to do well is stay calm when things fall apart. Not because pressure doesn't land — it does — but because I've learned to find the problem inside the panic. The noise clears, and suddenly there's just a puzzle. There's something I genuinely love about that moment. I don't think I'll ever stop looking for it.
The other half of me lives in questions that don't resolve cleanly. Why do things move in cycles? What's actually underneath the surface of a market, a philosophy, a civilization? I don't expect final answers. But I take the questions seriously — with rigor, with patience, and without pretending certainty I don't have.
I call myself a generalist. What I mean is: I absorb everything, and I can't seem to stop.
My professional life has mostly been about one thing: being the person who makes sure things actually work.
For years that meant being on the ground — in merchant kitchens and retail floors, wiring systems into the real operational life of businesses. Not handing over a manual and leaving. Staying. Coming back when staff changed. Standing by on go-live day because when it's D-Day, you don't get a second chance.
What I didn't expect was how much that work would teach me about people. Every friction point in a system is, underneath it, a human friction point. Someone who doesn't understand, or doesn't trust, or is simply exhausted. The technical fix is usually the easy part.
Later, the context shifted to institutional clients — national-scale systems, managed fully remote across timezones. I owned the communication threads, sat in feasibility calls between engineering and clients, wrote the specs, walked stakeholders through sign-off, then ran testing all the way to production. The bridge between what someone needs and what a system can actually do — that was always the job.
In my best year, my team placed 1st nationally by productivity. More than the number, I'm proud of what caused it: a culture where people genuinely looked out for the clients. That doesn't happen by accident.
The personal work started as a question I couldn't shake: why does everything move in waves?
Not just markets. Everything. Empires. Technologies. Conversations. There seems to be a geometry underneath it all — patterns that repeat at different scales, cycles that were already old when anyone thought to name them.
Markets became the laboratory because they're the most honest mirror of collective human psychology available. Every candlestick is a crowd decision made visible. I'm not interested in predicting what happens next — I'm interested in understanding the architecture of how things unfold.
That obsession eventually became a formal working paper — Reflexive Symmetrical Architecture: A Unified Theory of Price-Time — published on Zenodo with a registered DOI. I didn't write it for credentials. I wrote it because the idea had been living in my head long enough that it needed a proper home.
The tools on this site are the practical side of the same thinking. Built not for a portfolio — built because they didn't exist, and I needed them.
People sometimes ask how the two sides of my life connect. I'm never sure it's as complicated as the question implies.
Whether I'm staring at a critical incident log at 11pm or a price structure on a weekly chart, I'm doing the same thing: looking for the moment where the system lost its center. Understanding why it happened there. Then figuring out what comes next.
Technical work gave me discipline — the kind you only develop when something breaking has real consequences for real people, and you're the one accountable. Market research gave me humility — the kind you only learn when you realize the cycle you're watching was already ancient long before you noticed it.
What they share is a belief that even in the most chaotic moments, there is an underlying structure. The work — all of it — is just the ongoing attempt to map it clearly enough to act on it.
"Auditing the intersection of logic and belief."
Writing is how the thinking gets tested against itself.
Most of it orbits one question: what is actually underneath this? Underneath the market move, underneath the historical cycle, underneath the way a mind constructs meaning, underneath what we call civilization. The subjects change — price theory, German idealism, monetary collapse, consciousness, mortality — but the posture stays the same. Something is happening on the surface. Something else is governing it. The work is finding the second thing.
Some of it reaches conclusions. Some of it is still open. A few pieces I wrote because the question was too heavy to carry without putting it somewhere. That counts too.
Things built to help me see better.
My attempt at visualizing what the charts don't show you. A live stream system built to watch market liquidity move in real-time.
A system built on the belief that the market is a series of nested cycles. I use this to find the equilibrium point where time and price meet.
A simple, high-fidelity window into the core rhythm of the crypto market. Just a clean way to track what's actually happening.
An engine built to map exponential network growth into a readable linear trend. Automatically calculates fair value baselines and statistical deviations across assets — separating the market's noise from its actual trajectory.
A whitepaper and interactive demo exploring the geometry of trading. Foundational thinking on spatial mapping, formally published on Zenodo (DOI: 10.5281/zenodo.16749290).
A novel pivot-based calculation system that incorporates opening dynamics to create responsive support and resistance.
A Pine Script tool to identify when the market is shifting its structure across different timeframes.
An exploration into dynamic 3D environments synchronized with audio streams. Mapping sound into a visual landscape.
An interactive artwork visualizing time as a series of concentric, nested rings — from millenniums down to the pulse of a second.
A collection of the books I love.
Scripts and indicators built over the years. The logic I use to see the market more clearly, shared publicly.
Where I talk through the things I'm learning — about finance, history, and the cycles that seem to govern everything.