Amibroker: Github

So far, no one has found the branch named h0und .

The backtest finished in eleven seconds. The Sharpe ratio was 3.1. The max drawdown: 4%. It was impossible.

// The market is not random. The market is a delayed reaction. This finds the delay.

The issue had no replies. The user’s account was deleted. amibroker github

But the commit count keeps changing.

“It’s not the logic,” he whispered, wiping condensation from his coffee mug. “It’s the backtest speed. I can’t optimize 50,000 permutations overnight.”

"Standard multi-threading helpers for AmiBroker. No memory bridges. No coherence functions. Trade what you see." So far, no one has found the branch named h0und

The code was elegant—violent, even. It didn’t just optimize parameters; it rewired AmiBroker’s internal pricing engine to inject synthetic latency. The comment in the main function made his skin prickle:

The last commit was two years old. No stars. One fork.

Most results were dead ends—archived scripts for moving average crossovers from 2015, a half-finished Python wrapper, forum scraps. Then, on page four, a repository with a strange name: h0und/AB_Matrix . The max drawdown: 4%

Leo was a coder, not a mystic. But he was also down 40% on his yen account. He cloned the repo.

He compiled the bridge, linked it to AmiBroker, and ran his system against five years of Nikkei 225 futures.

That night, he dreamed of candles. Not green or red—but white. They formed a single, silent word: Coherence .

The hum of the server was the only sound in Leo’s cramped Tokyo apartment. On his screen, a waterfall of red numbers cascaded down his AmiBroker charting platform. Another trading day, another brutal drawdown. His system, the one he’d spent three years perfecting, was failing.

The code was discarding trades that violated the expected emotional response of the market . The bridge wasn’t predicting price. It was predicting when the crowd would panic—and only trading the gaps between those panics.