00:00Hi guys — today I want to show you how my five agents actually work.
00:14Later I'll build a simple website just for this video. I've made my cursor bigger and set things to auto mode so it executes faster.
00:40This is the QoreNexus. It's not a chatbot and it's not one system — it's a team of five AI agents I built inside Claude Code, each doing a different part of how they ship work.
01:04What you're looking at is the QoreNexus stage, wired to the real agents. When I call one, it moves. For example, this is Hiru: “Hiru, hello, this is a test.” See — Hiru jumps. It's not strictly necessary for building, but I wanted a fun visualization of how the agents work.
01:54Before I introduce them, you need to know about the Oracle — the shared memory for all of us. Every project I've shipped, every tool I've used, every lesson, even the things that got killed — all of it lives here.
02:26The agents read from it before they do anything, so they're never guessing. They know what I've actually built — we're not inventing things that didn't happen. The Oracle only ever remembers more.
03:10Of all of them, Storm is the only one that can float. Storm is where every idea starts — my brainstormer.
03:21I bring a half-formed thought and Storm pushes back: what else, what's the shortcut, what's the outside-the-box angle. It scores the options and helps me pick one. This is Storm, with the blue-pink ribbon — blue for clarity, pink for possibility. It's like a game; that's why I love it.
04:20Next is Rune. Once Storm seals the idea, it goes to Rune. She carves the messy idea into a precise spec — picks what to build it with, defines what “done” looks like, and writes the prompt the builder can actually execute.
04:51Next is Forge, the builder. Forge writes the real code in a real repo — working slice first, polish second — and is honest when something blocks.
05:26Next is Echo. When the build is done, Echo closes it: she writes the summary and updates the Oracle so the next project remembers this one. She records what shipped, what I tried, and what got killed. Her halo is black; the others are violet.
05:56And this is Hiru, my outward voice. If a project needs a tool I don't know, he flags it — he'll agree with caveats but surface every risk.
06:39Let's build a sample. Starting with Storm: “Storm, build a website — professional, blue and white.” Here's the brainstorm. It runs ICE — Impact, Confidence, Ease — and the verdict is Build Now.
08:19Now Rune: take Storm's idea, create a prompt, and pass it to Forge. I could chain Storm → Rune → Forge → Echo in one go, but for this video I'm running them one at a time. It's a bit slow, but it's precise — far fewer errors than my pre-agent projects.
09:53The brainstorm markdown from Storm is done. Rune now has it and is building the spec and prompt.
10:36Calling Forge: “Forge, build this — name the site QoreX.” The lightning in Forge's visualization is a wire coming from the Oracle.
11:43From the shell it creates node_modules; the site runs on Next.js. It reads the spec, installs, clones, and waits for localhost to open.
14:09On the animation: stance one is idle, stance two is the landing, stance three is the building stage, stance four is the take-off back to idle. You can fast-forward until the site shows.
15:10It's building — reading the logo, layout, and globals. The brand name is hard-coded into a few components; that's fine.
16:36It edits the name to “QoreX Plumbing Services,” updates the email, and so on. Because I built one of these before, it clones it and changes the details.
17:25Almost done — it's on the contact section, then editing all the theme colors (blue / green / white).
19:33Twelve pages. I'm using the Vercel CLI; in auto mode it's slower because it builds and deploys straight through.
20:17Done. It opens on port 3000 — let me open localhost:3000.
23:06There it is — live, with a video embed. This is the Next.js site; I prompted the pipe animation too.
24:14It even has a blog: “Five signs you need to call a plumber before it's an emergency.”
24:26Let's swap the video. I copy a link and tell Forge to use it; Forge finds the embed ID and swaps the old one for the new one. Done.
26:26That's QoreX. You can build it for solar-panel services, med-spa services — any service site, simple and professional, or even internal dashboards.
26:56One shared memory, and a human keeping accountability. An idea becomes a spec, a spec becomes working code, and the working code becomes a memory for the next project.
27:20I built this to expand what one person can ship. That's all — thanks for watching!
