A cold basement. One honest question. Two years later: a backyard office with a server closet, an AI company, a live website run by an agent workforce, a second brain, and a book being written from inside the story.
SCROLL · ARROW KEYS · TAP THE RAIL ON THE RIGHTSCROLL · SWIPE · TAP A DOT AT THE BOTTOM
Unfinished. Cold in a way that gets into the keyboard. Low ceilings, flickering lights, the HVAC and the plumbing running right beside the desk. The cats had their litter boxes down here too; it was their basement first. Two years of evenings and weekends off a laptop, and no single breaking point.
Is this really the best I can do?
Not "where can I rent an office." The question was: what would it actually take to build something in the backyard? Square footage, roof pitch, setbacks, what cedar does in a New Hampshire winter. When I asked for a floor plan, I got one. When I said the desk should face the yard, the plan turned around. Sixteen by ten. A single-slope roof. Charred panels on one wall.
Then the drawing grew a server closet nobody had asked for yet: a dedicated 20 A circuit, a 6-inch exhaust fan, two Cat6A drops. The whole story is on that one sheet.
Could I design this myself?
A general contractor looked at a drawing that had cost nothing and gave it a real number. The trucks arrived, framing went up, and on September 10, 2026 the HVAC went in and air moved inside a building that had been a sentence in a basement. The shed is now finished and paid for in full.
Am I actually going to do this?
A search about whether a new build tied to a business changes the math, and the honest answer being: you will not know until there is a business. So there was one. Avenix Ai LLC, lowercase i and all. Its purpose on day one: build AI platforms and products that run with minimal hands-on involvement and earn steady, passive income. The shed now had a job.
How does this make business sense?
Kits named for what they do: Vault for billing, Foundry for engineering, Atelier for design, Circuit for automation, Scout, Sites, Studio, and Seal, the gate that refuses work. Every agent got a seat and a model tier, like an org chart. All of it moved into an Obsidian vault: the company's brain. I did not learn to code. I learned to charter, dispatch, verify, and refuse.
Who is going to do all the work?
Six rounds of the readiness gate before anyone was allowed to launch: 14 blockers, then 11, 9, 3, 4, and finally 0. On August 21, avenixagency.com went live on Cloudflare: a static site at the edge, a small worker behind the intake form, and layered protection in front of it. The first test lead exposed the seam immediately: "did the agents receive my submission?" They had not.
Will anyone ever see this?
The gap became a bridge: every 15 minutes a scheduled task pulls new leads out of Cloudflare into the vault, outbound only, no open ports. On August 27 the first live lead was fulfilled end to end, then the whole customer arc including a revision, the same day. The next lesson arrived fast: a workforce that never sleeps also never stops spending. Two days later, a fleet-wide spend ceiling.
Does the machine actually work?
A whole department was evaluated and killed the day it was proposed. A site rebuild passed the gate on round eleven and I cancelled it anyway: ten failed rounds on one stubborn subsystem, and a measurement showing repair-and-regate loops eating most of the money. Out of that came a speed doctrine: size the bar at intake, two strikes then redesign, hard caps on rounds and tokens.
What should I not build?
Every scheduled job still lived on the laptop; when the laptop left, the fleet stopped. So I learned what a home server is from zero, wrote the guide I wished existed, and discovered the closet I had specced was sized for a dream rack. The real need is a 25-watt box that raises the closet half a degree. Then the shopping list met the market: the cheap mini PCs were gone and the budget moved. And the yard got its wire after all: on September 12 a dedicated Ethernet run reached the shed, so the closet plugs straight into the house network.
The home lab build is underway, and the stopgap died before it started. For a day the plan was to turn the Alienware into a short-term server; on September 22 the real box was ordered instead: a Beelink SER9 MAX, sixty-four gigabytes, arriving the twenty-eighth. Alongside it a ThinkPad T490s runs Linux as the portable workstation. By September 27 the last parts were ordered: a battery backup, a backup drive, a power strip that fits a ten-inch rack, and a plug that measures every watt. Shopping is over; by mid-October it was all racked and running.
How does this run without my laptop?
A golf-simulator lounge designed in the same sheet language as the office. A friend's loft. A pyramid "future encyclopedia" built in one sitting just to see what the newest model could do. None of them had a plan. All of them are where the skills for the real builds showed up. Play is how the drawing table learned to draw.
What if I just build it for fun?
He is curious about everything, and computers are no exception. So the same story, told for a child: Dad had a cold basement, asked a question, and kept asking until there was a little house with a secret closet full of blinking lights. The first sample went to the printer today.
What will you wonder about?
First the laptop. Wiping Windows off the ThinkPad took three tries: the BIOS keys were silently skipped, and the first USB stick turned out to hold a Windows installer instead of Linux. Both mistakes went straight into the handbook that night, so the next person does not lose the same hour.
Then the node. It arrived on the twenty-eighth and immediately wanted an account it should not have. Remote Desktop worked once and then went silent; after a long hunt the cause was a single word: the network had been labeled Public. Three commands later it answered from the laptop, the old desktop, and a phone in the yard. Then it learned the habits a server needs: never sleep, sign itself in after a power cut, lock its own screen, and pretend a monitor is attached so nothing waits for one.
On October 2 the fleet started moving in. Hundreds of files still carried the old machine's name inside them. Instead of rewriting any of them, the node got a doorway with the old name that leads to the new home, and every path just worked. The scheduled jobs were paused on the old desktop, copied across, and given their tools.
On October 3 they switched on. One job failed until a single secret came across; another turned out to do nothing but open the morning report on whatever screen it runs on, so it stayed on the desk where I actually sit. Then the real test: restart it and touch nothing. It came back, signed itself in, opened its notes and its assistant, locked its own screen, and got back to work. The fleet no longer lives on my laptop.
Can it run without me in the room?
The parts that sat in boxes on the desk are in the closet now: the ten-inch rack, the switch patched to the house wiring, the battery underneath, and the node with its backup drive on the shelf. Then the closet stopped being the place where the pieces lived and became the place where the work happens.
Underneath the website, the back office came together: a database for orders, a container runtime for the services that sit beside the fleet, and a secure line out to the internet that needs no open doors. All of it lives in one repository that tracks every change, so any wrong turn is one step back.
The last proof was the workforce itself. Every agent seat had been written for the old machine, so on October 16 each one was moved to its new home and handed a small task. Eight answered on the first try. The ninth needed one more pass. Nine of nine, from a box in a backyard closet. The next day, this story went up on the agency site.
What does it take to trust it with real work?
Hover a link to see the question that made it. Click to revisit.
| Date | What |
|---|---|
| ≈2024-09 | Basement era begins |
| 2026-08-11 | Backyard Office v4 adds the server closet |
| 2026-08-12 | Avenix Ai LLC formed (NH) |
| 2026-08-13 | 131 agents / 7 kits → Obsidian vault |
| 2026-08-19 | Site v1 passes the gate, round 6, 0 blockers |
| ≈2026-08-20 | Build begins on site (exact date coming) |
| 2026-08-21 | avenixagency.com live |
| 2026-08-26 | Intake bridge fully autonomous |
| 2026-08-27 | First live lead fulfilled end to end |
| 2026-08-28 | Mission Control self-regenerates 2-hourly |
| 2026-08-29 | Fleet-wide spend ceiling live |
| 2026-08-30 | Job Status Board live |
| 2026-09-04 | Speed doctrine · site v3 passes round 11 |
| 2026-09-08 | v3 cancelled; loops measured at 83–88% of tokens |
| 2026-09-09 | Daily report ships · Home Lab Academy built |
| 2026-09-10 | HVAC installed · shopping list · first-dollar path · Codex Giza · picture book sample · this story begins |
| 2026-09-12 | Dedicated Ethernet run reaches the shed; mesh workaround retired |
| by 2026-09-21 | Shed complete and paid in full |
| 2026-09-17 | Windows erased on the ThinkPad T490s; Ubuntu installed as its only system |
| 2026-09-21 | ThinkPad T490s running Linux as the portable workstation |
| 2026-09-22 | Fleet Node ordered: Beelink SER9 MAX, 64 GB, arriving 2026-09-28. The laptop-as-server stopgap is retired before it started |
| 2026-09-26 | Mini rack (DeskPi T2, 12U, 10-inch), 2.5 GbE switch, patch panel and cables ordered, arriving 2026-09-29 |
| 2026-09-27 | Last Phase 1 parts ordered: battery backup, 5 TB backup drive, 10-inch power strip, energy-monitoring plugs, display emulators. Shopping phase over |
| 2026-09-28 | Fleet Node arrives; local account, updates, power-loss recovery set, backup drive prepared |
| 2026-10-01 | Last box delivered; every Phase 1 part on site |
| 2026-10-02 | Node made headless and reachable from laptop, desktop and phone over a private network; the fleet's files and tools moved onto it; its jobs paused on the old desktop pending the switch-over |
| 2026-10-03 | The fleet runs from the node: three jobs switched on in the closet box, the morning report kept on the desk, notes synced across all three machines, and an untouched restart passed |
| 2026-10-06 | The back office stands up beside the fleet: an order database, file storage, and a secure tunnel to the internet |
| 2026-10-16 | The agency workspace gets its own home on the node; all nine agent seats pass a live check from the closet |
| by 2026-10-17 | Rack assembled and running in the closet; containers running; every change tracked in one repository |
| 2026-10-17 | This story goes live on the agency site |
That is how Avenix started. The workforce from this story is the one that runs the agency today.
See what Avenix does now → Back to the beginning