The through-line is stateful software interacting with messy worlds.

01 – Real-Time 3D

The Babylon.js work included a substantial horror FPS experiment with:

• UniversalCamera;
• collisions;
• flashlight;
• ghost AI;
• ghost states such as PATROL, CHASE, IDLE and ATTACK;
• multiple ghost types;
• detection and catch radii;
• mansion-grid systems;
• prefabs;
• capped flicker-light pools;
• PBR floors and roofs;
• BFS patrol;
• HUD and inventory;
• ritual mechanics.

This belongs in the Lab because autonomous behaviour, state machines and real-time perception/action loops are not restricted to LLM systems.

02 – Generative Media Pipelines

ComfyUI became an orchestration platform, not just an image-generation interface.

The work covered image generation, video generation, video editing, video stitching, 3D workflows, audio, image analysis, editing, character workflows, LLM orchestration and experimental workflow packs.

Game Character Hub was considered as a target for AI augmentation: ComfyUI could populate assets, an LLM could direct or configure content, and the legacy software could manage sprites and animation.

03 – Embedded Systems

TinyMind Robot aimed at the smallest and cheapest fully local AI-like system possible inside a 3D-printed robot.

The design converged around Seeed XIAO ESP32-S3 Sense, N20 motors, DRV8833 driver, battery, speaker, LEDs and small sensors, with a removable brain-cartridge idea for future upgrades.

The archive is clear about the constraint: an ESP32-class board is not a realistic host for a normal 0.5B-parameter local LLM. The project belongs more to embedded intelligence and behavioural architecture than ordinary LLM deployment.

04 – Web And Business Tooling

WordPress and 3D Printing Ballarat systems also belong in the wider archive:

• instant STL quote/upload;
• photo-to-3D model;
• custom jobs;
• searchable parts library;
• AJAX shortcodes;
• weighted search;
• STL/OBJ preview worker;
• custom post types and taxonomies;
• payment portals and file-upload workflows.

This is the practical software substrate underneath the AI research.

05 – Current Belief

The Lab should not be narrowed until only Omega remains.

Omega is the centre of gravity, but the surrounding work explains the instincts behind it: local-first systems, long-running state, tool use, autonomy, hardware constraints, embodied sensors, real-time interaction and an unwillingness to treat failures as embarrassing.

Source note: assembled from v2 sections on Babylon.js, ComfyUI/generative media, Game Character Hub, TinyMind Robot, Espruino, WordPress tooling and 3D Printing Ballarat systems.

This entry is a map, not a victory lap.

01 – The Lineage

The pattern begins in ordinary software work: WordPress, PHP, JavaScript, Node, React, C#/.NET, integrations, APIs, automation and UX. That work matters because it created the reflex that later shaped the AI systems: build tools that survive contact with users, file systems, queues, APIs, permissions and ugly operational state.

From there the archive moves through several layers:

• LLM integration inside existing software.
• WordPress and command-line agents with memory, task queues and history.
• Autonomous experiments in persistent worlds such as Screeps.
• AntBrain-style cognition experiments using perception, memory and LLM decision loops.
• Local assistants and plugin runtimes.
• Genesis as a more general agentic substrate.
• Omega as a shift away from assistant orchestration and toward artificial cognitive architecture.

The important point is continuity. Omega did not appear as a clean abstract idea. It emerged after enough agent systems behaved too much like tools waiting for instructions.

02 – What Changed

Earlier systems could be useful without being alive in the architectural sense. They could receive a task, call a model, use tools, write state, and return a result. But their default condition was still sleep.

The Omega question is different:

What would a system be doing when nobody is asking it anything?

That one question changes the architecture. Memory stops being a transcript dump. Attention becomes a real resource. Goals need to persist. Idle time becomes cognitive time. A model becomes a processor inside a larger system rather than the seat of the system itself.

03 – Why The Old Work Belongs Here

Screeps matters because persistent game worlds expose planning, resource constraints and long-running autonomous loops.

AntBrain matters because cognition framing existed before the Omega name.

The WordPress CLI LLM agent matters because it joins ordinary web tooling to memory, history and task queues.

Genesis matters because it tried to make agent systems modular: profiles, plugins, local-friendly execution and interoperability with other frameworks.

The hardware work matters because the later specialist-cluster idea depends on accepting heterogeneous compute as a design material rather than treating it as an inconvenience.

04 – Current Belief

The Lab should not be organised as a portfolio of isolated projects. It should be organised as an intellectual trail: predecessor, failure, correction, successor.

That means some entries are not "successful projects" in the normal sense. They are preserved because they explain why the later architecture exists.

05 – What Still Needs Verification

This entry is reconstructed from the knowledge base rather than independently verified against every repository or live URL. Existing public pages and repos should be checked for:

• AntBrain.
• Screeps agent work.
• Genesis Runtime.
• Local AI Home Assistant.
• WordPress-CLI-Agent-LLM-Model.
• Omega ACA.

The safe public claim is not that each project reached a particular outcome. The safe claim is that each belongs to the chain of experiments that led toward persistent artificial cognition.

Source note: assembled from Derek_Robertson_Lab_Knowledge_Base_v2.md, especially the project-lineage and archaeological-pass sections. Dates and implementation states remain conservative unless separately verified.