Blog
Notes, builds, and research logs.
What we are learning as we build. Mostly honest accounts of what broke, what shipped, and why we made the call we did.
Leverage//6 min read
leverage playbook memory: shadow mode, evidence, and why we are not learning aggressively yet
Most AI trading tools forget everything or learn too fast from noisy outcomes. Playbook Memory records the full episode graph, runs shadow retrieval first, and only promotes lessons that survive evidence review.
Read postEarlier posts
Leverage//5 min read
leverage co-pilot: a trading partner beside the chart
Leverage started as Pulse, an AI scanner that watches charts and surfaces trade ideas. Professional traders need more than signals. Co-Pilot is the second brain we built for that.
Read postResearch//5 min read/Kiing
abstraction all the way up. what two years of building AI systems actually taught me.
Software engineering has always been a story of rising abstraction. AI is the newest layer. Here is what building real systems taught me about where that layer holds and where it breaks.
Read postLeverage//3 min read
leverage, the floor, and why AI tools should feel alive
We built a 3D trading room into a Chrome extension. Here is the thinking behind it, and why making a tool feel alive is not a design indulgence. It is a reliability decision.
Read postLeverage//3 min read
what we cut from leverage in two weeks, and what that taught us about building AI tools for traders
After three weeks of daily use and the first round of beta feedback, we ran a full declutter pass. The lesson was not about design. It was about what happens when you put AI output into a high-pressure environment.
Read postLeverage//2 min read
leverage gets bitcoin. what adding a second market taught us about AI trading context.
Adding BTC support meant confronting something most AI trading tools ignore: different markets need different ground truth, not the same model pointed at a different chart.
Read postLeverage//2 min read
when the model said the stop wasn't hit. it was. what that incident changed about how we build.
The most important architectural decision in Leverage came from one trade going wrong. Here is what we learned about what AI should and should not be deciding in a live trading system.
Read postLeverage//2 min read
leverage: a chrome extension for trading gold off tradingview
What it actually looks like to put AI in the hands of someone who trades gold for a living. Not a demo. A tool we use every session.
Read postApex//2 min read
APEX: open beta ops and how we think about AI at the execution layer
In April we focused on what makes an AI trading system reliable when markets are noisy. The answer is not better AI. It is knowing exactly what the AI should and should not be deciding.
Read postApex//2 min read
APEX: what quality before scale actually means in an AI trading system
March work on APEX was about raising the bar on candidate call quality before thinking about volume. Here is why that ordering matters.
Read postInfrastructure//2 min read
VPS AI engineer: why alert quality matters more than alert volume, and how we are fixing it
February work on the VPS AI engineer was about reducing noise and anchoring AI suggestions to runbook logic. The goal is a system operators can trust, not one they have to second-guess.
Read postInfrastructure//2 min read
VPS AI engineer: what it actually means to put an AI layer on server monitoring
The first phase of the VPS AI engineer was about giving operators faster context when things go wrong. Not automation. Context, at the speed the situation actually needs.
Read postTooling//2 min read
turning GitHub activity into something a team can actually read
In December we built a project management layer that summarises what is happening across repos. The problem it was solving is not a GitHub problem. It is an information density problem.
Read postSlash//2 min read
/Slash goes multi-LLM. why single-provider AI is a fragility you do not notice until you need to.
We moved /Slash from a single-provider architecture to multi-LLM routing with OpenRouter support. The change is mostly invisible to users and matters a lot for reliability.
Read postBlueprint Labs//2 min read/Kiing
introducing blueprint labs
Blueprint Labs is an independent AI research and product lab. This is what we are building, why we build in public, and why this blog exists.
Read post
