Blog Post Week 6

I’ve been thinking a lot about the current state of LLM orchestration, specifically how to move beyond basic prompting and into using local tools for orchestration my own tasks. I already have openclaw on my machine to do work, but the tools are still pretty terrible. My goal is to work on a project where we’re expanding the frontier of tools into things I find useful.

I’ve been diving into frameworks like LangChain, LlamaIndex, and Haystack, as they’re essential for managing the complexity of tool-calling, memory, and retrieval pipelines. In terms of a longer project, I would love to think about a way to compress existing abstractions for things like web pages and human UI so we use less tokens and can improve net performance through small but slightly creative techniques.

Because this space is so new, we’re constantly dealing with model drift, breaking API changes, and the inherent unpredictability of orchestration. I’m comfortable navigating that instability through my work in Kalshi/Polymarket. I’ve found that small changes in these systems can cascade quickly, so I focus heavily on technical execution and reading deep into codebases to understand architectural tradeoffs.

One of the most impactful experiences I’ve had recently was evaluating Hummingbot for crypto market making. It gave me a real appreciation for modular system design, specifically how strategies plug into exchange connectors. It got me thinking about how that kind of extensibility could be generalized beyond crypto to broader CLOB-style (Central Limit Order Book) markets. Applying that level of architectural insight—moving from a specific crypto implementation to a generalized abstraction—is where I think I contribute the most value.