Jeremy Knox · The Code Whisperer
I’m an engineer and AI operator. I build systems for work I actually need to do, then share the methods that make them useful.
Engineering is my foundation. Markets sharpen my analysis. Strategy shapes how I decide. Today, those disciplines come together in the agent fleets I build and operate.
View full portrait ↗ChannelAdvisor Genesys Pendo SAS
The connection is practical: understand the system, evaluate the evidence, choose a direction, and take responsibility for what happens next.
Build something that holds up.
Distributed systems, enterprise SaaS, blockchain architecture, and production AI/ML. Different domains; the same responsibility to understand the system, make the tradeoffs, and deliver working software.
Explore the systems →
Decide what matters before moving.
25+ years studying military strategic doctrine: Sun Tzu, Clausewitz, Boyd, and Liddell Hart. That study informs how I think about constraints, feedback, priorities, and the decisions an operator must keep.
Read my operating principles →
Make the reasoning explicit.
7+ years in markets. As Chief Blockchain Analyst at Hive Mind Crypto, I educated 300+ investors on blockchain and market structure. That analytical work became InDecision, a six-factor framework for evaluating market signals.
Inspect the analytical framework →
Coordinate the work. Own the result.
I started building agent fleets in 2025. Today, engineering, analysis, and strategy meet in an agent organization with shared context, specialized roles, and a human approver. The work is delegated. The judgment stays with me.
See the agent organization →These are the questions I bring to an AI workflow. Open each one to see how it shapes the work.
Define the outcome, the constraints, and what a useful result looks like. Give an agent a bounded task and the context it needs. Architecture and scope come before volume.
Inspect the output, exercise the behavior, and check the assumptions. A generated answer is a starting point. A working system needs evidence that survives review.
Automate repeatable work while keeping judgment explicit. Decide what an agent can do, where it must stop, and who approves the next step. More autonomy requires clearer boundaries.
The products put the approach to work. Teaching makes that practice useful to someone else.
Competitive intelligence brings my engineering, market analysis, and strategic thinking together. It is the primary mission behind the systems I build.
Read the Intel Dispatch ↗The methods behind the systems are worth sharing. Clear context, bounded tasks, and deliberate review are habits you can practice, starting with one useful agent.
Explore the operating basics ↗Turn a task you understand into a workflow you can inspect.
Bring a system you’re working onWork with meExplore production builds, architecture, code review, and operator mentorship.
Keep exploring: Ask Knox ↗Connect on LinkedIn ↗