The work, with the numbers.

How the map reads

• A tabletop miniature. The buildings, trees, villagers and worker figures are painted 3D models made with Meshy. The light comes from the room: a window by day and a table lamp at night.
• Every running job is a worker. When a session starts, its team walks out of the keep to the project it is working on. Lead jobs, helper jobs and local engines each appear as their own figure, with a short label for what they are doing. A workshop with workers on site gets scaffolding and a small crane that hoists planks only while they work.
• Places stand for parts of the machine. The Forge fires up when the GPU renders, the Mage Tower lights when a local model is loaded and sleeps when it is not, and each project is a village that is lit while active and dark when quiet.
• Weather follows pressure. Memory, swap and stall pressure move the sky from clear to cloudy, rain and storm, with hysteresis so it doesn't flicker. Day and night follow the real clock.
• Signals that need you stand out. A raised banner and a card mean a job is waiting on a reply. A failed service smokes. Ambient life is kept quieter than either.

A typical glance

Look across at the side monitor: three teams are out, the Forge is busy and one banner is up. Choose Go to on its card, answer it in its own terminal, and the team carries on.

How a run goes

• Plan. The lead turns each feature into an order with a goal, its inputs and a clear done-when check.
• Build in parallel. Builders take one order each and work at the same time, without stepping on each other's files.
• Tests decide. A task is done when its check passes, not when a builder says so. The lead re-runs every check before anything merges.
• Escalate. A task that keeps failing goes back to the lead, who reads the failure and sends a fix.

The playground

Type a feature or pick a preset and watch the whole run as a node graph, phone included. It is a scripted simulation that runs in your browser: nothing is sent anywhere.

In the current build

• Machine checks and controls. Inspect processes, read service logs, manage configured services and capture the desktop. Controls include locking the screen and adjusting session settings.
• Files and a shell. Browse and preview files, transfer them, and run commands with live output. The shell remembers its working directory between commands in the current connection.
• A needs-you inbox. Task runs, replies and push notifications arrive on the phone, with a full-screen terminal for anything else.
• A workspace that adapts. Rearrange widgets and actions through configuration. Deck follows the workstation's active theme and reconnects when the private connection returns.

A typical session

Connect from the phone, check a service, read its recent logs and take the relevant action. Open Files to inspect an output, or use the shell when a widget doesn't cover the job.

How they were made

• Timed to the song. The vocal is separated and every word timed, so cuts, lyric type and inserts land on the beat.
• One singer, many scenes. The same character carries both videos, with new wardrobe and sets for each song.
• The edit is data. Every shot, still and overlay lives in an edit list that renders the whole video in minutes, so re-cuts are quick.
• Checked, not eyeballed. A lip-sync checker compares mouth movement with the vocal track before a shot is kept.

On Roblox: the co-op crawler

Every run builds a new set of rooms, with biomes, curses and blessings changing what you face. Fight goblins and skeletons, get through trap courses and puzzles, and finish against a three-phase Lich.

• Four classes to start. Warrior, Rogue, Mage and Cleric are playable now. Five more classes are planned, each arriving in a later update.
• Revenants. Fall in the dungeon and you rise as a Revenant: an elite enemy carrying your gear that turns up in other players' runs. Defeating one earns bonus loot.
• Loot and difficulty. Gear drops from Common to Mythic across three difficulties, up to Nightmare. The Dice Shrine shows its odds before every roll.

On Linux: the defence prototype

Defend the Heart across 18 encounters in six chambers, from the Overgrown Crypt to the Shattered Observatory. Each encounter has three waves: spend a limited essence budget on monsters and reusable traps, choose positions around bends and overlapping routes, and rethink the layout between waves. Five defender families each evolve through three forms, and finishing Normal unlocks a harder Veteran campaign.

Development notes

On Roblox, armour currently adds stats and a rarity aura rather than changing how your avatar looks; visible armour and skins are planned together for a later update. The Linux prototype's recorded checks cover both campaigns and standalone launch, and it still needs human playtesting to judge difficulty and first-time clarity.

What works today

• Daily lessons. Each lesson is a few teaching cards and a handful of questions, with a kind explanation when you get one wrong. Two new lessons arrive each day, and any you miss wait for you.
• Tarot, runes and herbs. All 78 tarot cards, the runes of the Elder Futhark, and plants and herbs with safety notes, plus crystals, numerology, astrology, dreams and the wheel of the year.
• Practice games. Card memory, herb foraging, cauldron brewing, rune riddles and number puzzles, with up to three mastery stars on every page.
• Slow down. Six guided meditations, six gentle yoga routines, seven soundscapes to play by the hearth and twelve bedtime stories to drift off to.
• A cottage of your own. Choose a cat, owl, fox or frog as your familiar, dress your witch or wizard, and watch the cottage come back to life as the hearth is lit again.

Made with care

Tarot, astrology, crystals, runes and folk herb lore are shared as tradition, symbolism and tools for reflection. They are not predictions, and nothing in the game is medical advice.

In the current build

• A recorded task lifecycle. Create and claim work, report progress, submit a result, and keep reviewer feedback attached through approval or rework.
• Explicit handoffs. Connected workers can send messages, read an inbox, reply in a thread and acknowledge receipt.
• A shared view of activity. The dashboard brings together project and task state, bridge messages and gateway logs for the work recorded through Cortex.

A typical workflow

Create a task and connect a worker through Cortex. The worker claims it, reports progress and submits its result. A reviewer checks the work, records a verdict and sends back findings if another pass is needed.