https://liquidmind.cloud/landing/blog Build-in-public from the founder of LiquidMind. Trade post-mortems, engineering notes on AI trading systems, and category theses. en Tue, 11 Aug 2026 00:00:00 GMT https://liquidmind.cloud/web-app-manifest-512x512.png https://liquidmind.cloud/landing/blog https://liquidmind.cloud/landing/blog/price-location-dealing-ranges-build-in-public https://liquidmind.cloud/landing/blog/price-location-dealing-ranges-build-in-public Premium and discount sound binary until one price sits above a local 1H range, below a broken 4H leg, and inside 1D discount at the same time. We built a mandatory multi-timeframe price-location tool for our entry and position-management agents — then made sure its output could never become an automatic trade filter. Tue, 11 Aug 2026 00:00:00 GMT engineering agents SMC/ICT premium-discount market-structure position-management build-in-public Python determinism https://liquidmind.cloud/landing/blog/tool-search-vertical-agent https://liquidmind.cloud/landing/blog/tool-search-vertical-agent A well-argued post making the rounds says tool bloat is killing agents: typical multi-MCP setups burn 50-70k tokens on tool definitions before the agent does anything, and models degrade past 30-50 similar tools. The prescription is tool search — index your tools, load them on demand. All of that is correct for horizontal agents. We measured our vertical one and got a different picture: 2,213 tokens of tool definitions, never more than 10 tools in context, and a context budget dominated by market data. Here's the measurement, and the one idea from that post we're stealing outright. Mon, 10 Aug 2026 00:00:00 GMT engineering agents ReAct tool-use context-engineering RAG determinism build-in-public Python https://liquidmind.cloud/landing/blog/partial-fill-risk-build-in-public https://liquidmind.cloud/landing/blog/partial-fill-risk-build-in-public One limit order planned 143,342 units. Only 226 filled. The resulting trade was profitable and its recorded RR was mathematically defensible — but letting the position manager and the learning system treat it like a completed trade exposed a much deeper modeling error. This is how we separated trade intent, live execution state, and statistical evidence. Sun, 09 Aug 2026 00:00:00 GMT engineering partial-fill execution risk-management position-management statistics RAG build-in-public Bybit https://liquidmind.cloud/landing/blog/trading-memory-rag-build-in-public https://liquidmind.cloud/landing/blog/trading-memory-rag-build-in-public An entry agent that evaluates every setup from scratch is doomed to re-learn the same lessons forever. Here's the RAG memory that fixes that: a normalizer that turns raw agent reasoning into price-free narrative documents, an embedding that carries only the story of the setup, deterministic metadata doing the filtering and boosting that vectors are bad at, and trade outcomes kept strictly outside the vector so history informs retrieval without contaminating it. Wed, 22 Jul 2026 00:00:00 GMT engineering RAG embeddings agents trading-memory architecture build-in-public Python PostgreSQL https://liquidmind.cloud/landing/blog/session-liquidity-pois-build-in-public https://liquidmind.cloud/landing/blog/session-liquidity-pois-build-in-public PDH/PDL gave the engine two liquidity magnets a day. But institutional desks don't just hunt yesterday's high — they hunt Asia's low before London commits, and London's high before New York reverses it. Here's how six new POI types, a shared invalidation core, and a full SMC/ICT context block got wired into the pipeline — and the naming mistake I made twice before shipping it. Update: shipping the radar UI surfaced a timezone bug and a default-allow config bug, and finished the move to full DST-aware sessions across the whole feature — level sizing and sweep-timing alike. Wed, 08 Jul 2026 00:00:00 GMT engineering POI SMC/ICT liquidity architecture build-in-public Python Redis agents https://liquidmind.cloud/landing/blog/user-defined-position-triggers-build-in-public https://liquidmind.cloud/landing/blog/user-defined-position-triggers-build-in-public Every trigger the position management engine had so far was something the market did — a POI appeared, a bias flipped, a session opened. None of them fired because a trader looked at their own chart and saw something the engine couldn't. Here's the pair of triggers that closes that gap, and why they share one pipeline down to the cooldown key. Mon, 06 Jul 2026 00:00:00 GMT engineering position-management tradingview webhooks architecture build-in-public risk-management agents https://liquidmind.cloud/landing/blog/session-boundary-triggers-build-in-public https://liquidmind.cloud/landing/blog/session-boundary-triggers-build-in-public The bot was reviewing open positions when candles closed, when structure broke, when news hit, when BTC flipped. But it had no concept of market rhythm — sessions opening, liquidity rotating, institutional desks clocking in and out. Here's how we wired five session boundary events into the Triad pipeline, and why getting the times right turned out to be less obvious than it looks. Sat, 04 Jul 2026 00:00:00 GMT engineering position-management sessions architecture timezone DST build-in-public risk-management scheduler https://liquidmind.cloud/landing/blog/trade-evidence-vault-build-in-public https://liquidmind.cloud/landing/blog/trade-evidence-vault-build-in-public A losing trade with a screenshot showing the drawn zone is a different lesson than a losing trade with none. The screenshot usually existed — it just lived in a phone gallery, disconnected from the decision it was evidence for. Here's the vault we built to fix that, why it isn't a journaling feature, and the security bug our own browser found on day one. Sat, 04 Jul 2026 00:00:00 GMT engineering attachments cloudflare-r2 journaling architecture build-in-public security postgres https://liquidmind.cloud/landing/blog/bias-flip-trigger-build-in-public https://liquidmind.cloud/landing/blog/bias-flip-trigger-build-in-public The daily bias said bearish. Two hours later the engine was short. The next morning the bias flipped bullish — and the short was still open. What should happen? Here's the trigger we built, and why its execution follows the same autonomy rules as every other event. Thu, 02 Jul 2026 00:00:00 GMT engineering bias position-management ReAct agent architecture build-in-public risk-management determinism https://liquidmind.cloud/landing/blog/june-2026-retrospective https://liquidmind.cloud/landing/blog/june-2026-retrospective Every trade LiquidMind's engine has taken since inception — Feb 16 to Jun 30, 2026 — audited in full. +49.8% ROI, a -22% drawdown, a 12-trade losing streak, and what the numbers actually say about the edge. Wed, 01 Jul 2026 00:00:00 GMT transparency retrospective performance drawdown smart-money-concepts algotrading transparency https://liquidmind.cloud/landing/blog/poi-state-machine-build-in-public https://liquidmind.cloud/landing/blog/poi-state-machine-build-in-public The POI tracker started with one boolean: is_active. At 200 zones across multiple timeframes, it imploded. Here's how I replaced it with a 7-state machine where every transition has an explicit trigger — and where BLOCKED is a first-class concept, not a collision bug. Mon, 22 Jun 2026 00:00:00 GMT engineering state machine POI architecture Python build-in-public determinism Redis