daemon money
Honest machines that make money while you sleep.
I'm an engineer building a fleet of small, mostly-autonomous content and income engines with Claude Code — and documenting every one, including this site, which is itself one of them. Real stacks. Real numbers. The failures too.
nohup@daemon:~$ ./engine --honest --while-you-sleep
A content engine about building content engines.
The "make money with AI" corner of the internet is mostly people selling a course about a business they don't run. This is the opposite: a working portfolio of engines that already earn — a trading-card channel, an animal-card brand, an honest affiliate experiment, a dividend book — and a plain-spoken account of exactly how each one is built, automated, and (sometimes) how it flops.
The trick everyone teaches isn't the moat. The receipts are. So the numbers here are real, the losers stay in, and the mascot in the margins will tell you when I'm being an idiot.
Four questions, one honest answer each.
From the log
All entries →I shuffled the market into noise. It looked exactly the same — so I shut the bot down.
Three weeks ago I published a crypto trading bot and promised I'd write the follow-up either way. This is the either-way. I spent a day trying to find any strategy that could trade around the clock and beat 1% a month, ran every test I could think of against a control arm made of pure noise, and found the arithmetic that ends it. Total cost: zero dollars. Here's every number.
I said I'd wait for the market. Three days later I forced the bot's hand instead.
Last post ended on a promise: my long/short crypto bot had never once fired its leveraged long side, so I'd keep paper-trading until the market forced it to. Then I realized I was conflating two different questions — 'does the edge exist' (needs the right market) and 'does the code even work' (doesn't). So I relaxed one gate and made the strategy run its long path today, in a market that's bad for longs. Here's what the dashboard proved — including the risk governor doing its job in real time.
12 steps to a new project — and the 4 that are still mine.
I've stood up seven of these now, and the routine has hardened into a checklist. But the useful part isn't the 12 steps — it's the seam. Every single time, the same four jobs stay in my hands and the agent does the other eight. Here's the whole assembly line, who does what, and why the split falls exactly where it does.