Recovered transmissions from the edge of development

Every universe has something holding it together.

The CosmOS is an ambitious project: a universe of massive worlds, each with its own identity, history and possibilities.

Building that universe means working on far more than what appears on the surface.

Behind every environment, every interaction and every meaningful choice lies a foundation that needs to hold. Those foundations are what allow an imaginative world to become somewhere you can actually experience.

This is where Foundations begins.

A look beneath the surface

Foundations is a development series about the work that makes The CosmOS possible.

Each entry will take a closer look at one part of that work. We'll explore the ideas behind it, the problems encountered during development, the solutions being tested and what those decisions mean for the experience we're creating.

Some entries will examine working features. Others will follow experiments or unfinished work.

The distinction matters.

We want to share the process without presenting intentions as achievements, or promising that something is finished simply because we have a compelling vision for it.

Showing the work

The purpose of this series isn't to produce a catalogue of features.

It's to share how The CosmOS is actually being built.

That means showing real development, explaining decisions and being willing to discuss where things don't yet work.

It also means giving each subject the attention it deserves. An important system shouldn't be reduced to a screenshot and a sentence. It deserves an explanation of its purpose, its development and the experience it's intended to create.

Where we begin

There is a great deal to explore, and no need to cover it all at once.

We'll start beneath the surface, work through the foundations one subject at a time, and gradually reveal how those pieces contribute to the larger experience.

The CosmOS is a universe we intend to build, not simply describe.

Welcome to Foundations.

Give a command. Watch it come to life.

A hologram worker is waiting for instructions. You arrange a short program, send it into a warehouse shift and watch what happens. When the worker reaches the wrong place, the next move is yours: rethink the commands, change the loop and try again. Construct Command turns programming into something you can see unfold.

The experience

In most games, you tell a character where to go by moving them yourself. Construct Command changes that relationship. A hologram worker waits while you arrange instructions; then the program runs and the worker follows what you wrote. You can watch your intention become visible, one instruction at a time.

That distance between the decision and its consequence is the point of the experiment. A path that seems obvious in your head is not always the path your commands describe. A loop that looks tidy can repeat the wrong step. When something goes wrong, you are not correcting a mispressed movement key; you are examining a plan.

The playable browser build contains ten warehouse puzzles. They give this idea a specific shape: crates and keycards, pressure plates and patrol timing, plus limits on how many commands you can use. Those constraints turn a blank command list into a puzzle with several things to notice before pressing Run. They also keep the experiment contained enough that its central interaction is easy to find.

Testing for feel

The question behind this experiment is one of feel. Can a sequence of commands make you feel responsible for the result? Does watching a plan go wrong invite another attempt rather than end the fun? The ten levels give us a contained way to explore the rhythm between planning, running, observing and revising. These are design questions, not claims about completed player research.

A programming puzzle needs more than correct answers. We are interested in the feeling that appears between making a prediction and seeing whether it holds. Does the worker's movement make the logic legible? Can you recognize which part of the program deserves another look? Does a failed run suggest a useful next attempt, rather than feeling like arbitrary punishment? These are the questions the prototype gives us room to investigate.

There is a tension here. If every instruction is spelled out so completely that nothing surprises you, running the program risks becoming a formality. If the execution is too hard to understand, a mistake becomes confusing. The interesting space lies between those extremes: enough clarity to understand cause and effect, enough friction to make revision meaningful.

Loops add another version of that tension. Repetition is powerful because a small set of instructions can do more work. It can also repeat an error. Command limits ask you to think about economy, but the game should still make experimentation approachable. You can run a plan, inspect its result and rearrange the commands rather than needing to arrive at a perfect program before trying anything.

Levels unlock as you complete shifts, and you can replay to improve command count and star results. That gives the same puzzle two possible experiences: first, finding a solution at all; then, asking whether the solution can become more elegant. We are exploring whether that progression feels like ownership of a plan, not claiming that formal user testing has already answered the question.

What you can do

• Arrange and drag command blocks into a program, including loop blocks for repeated steps.
• Navigate crates, keycards, pressure plates and patrol timing under each level's command limit.
• Complete levels to unlock the next shift; replay to improve your command count and star result.

What this build does and does not show

What you can play now is a standalone programming puzzle associated with Neo York. It is not a playable release of Neo York itself, nor proof that the wider CosmOS actor systems already use this exact command model. The warehouse setting provides the rules and obstacles needed for a focused experiment; the larger world has a different scope.

Try writing a short route, running it, and changing only the part that did not behave as expected. Then return to a solved level and see whether fewer commands can express the same intention. We want to keep learning from that small cycle: decide, execute, observe, revise. If those four beats feel connected, a little puzzle can reveal a great deal about meaningful interaction.

For now, the experiment is a playable programming puzzle, not the finished Neo York world. If the work makes you curious about what your next set of instructions might do, that is exactly the kind of feeling we want to investigate.

Construct Command is an Arcade experiment, not the completed CosmOS VR world or campaign.

Look closer. There is more to find.

A scene from Cutie World is full of things to notice, but only some belong to your target tray. You look, zoom, peek behind scenery and find what was hiding in plain sight. Cutie World Find It makes a simple act—looking carefully—into the heart of the experience.

The experience

Sometimes the most interesting thing you can do in a world is look closer. A crowded illustration promises that there is more here than the first glance reveals. Cutie World Find It turns that promise into a browser game: you receive a tray of specific targets and search illustrated scenes until you have found them.

The action is simple, but attention is not. Your eye moves across a composition, settles on an interesting shape, decides it is not the one you need and moves on. Something that seemed invisible a moment earlier suddenly becomes obvious. The small moment of recognition is the experience we want to explore, rather than merely asking whether a player can select the correct pixels.

The available build gives you ways to investigate a scene instead of treating the artwork as a fixed poster. You can pan, zoom and use Peek to look behind scenery. A target tray tells you what you are searching for; hints are available when you get stuck. Finishing a scene moves you on to the next one. Those are actual interactions in the browser game, not features being promised for the whole of Kidlandia.

Testing for feel

We are exploring how searching feels, not just whether a player can click the right object. Is it satisfying to notice something overlooked? Does moving around the illustration encourage curiosity? Can a hint help without taking the discovery away? The browser game gives those questions a playable shape; it does not mean we have completed a formal study or built all of Kidlandia.

Testing for feel begins with the relationship between a picture and the person searching it. Does moving around an illustration feel like exploring, or like fighting the interface? Does a target have a readable identity when it appears at a different scale? Can detail reward a second glance without making every scene exhausting? We can ask those questions because the search is playable and the controls are concrete.

There is a balancing act between hiding something and making it unfair. If a target sits in plain view with no competing detail, finding it may feel automatic. If it blends into noise or disappears behind an obscure interaction, finding it may feel accidental. A scene needs somewhere for the eye to travel, landmarks to return to and enough visual distinction that recognition feels earned.

Peek introduces a different kind of discovery. Looking behind scenery suggests that an illustration has layers rather than one flat surface. Zoom and pan change what you notice, too: the same picture can be read as a whole composition or inspected as a collection of little moments. We want to understand when these movements help curiosity and when they interrupt it. The existence of the controls does not, by itself, prove that their feel is right.

Hints sharpen that question. A hint can be a useful invitation back into the search, or it can take away the satisfaction of spotting the target yourself. The aim is not to declare one universal difficulty setting; it is to explore how assistance might preserve the pleasure of discovery. These are design questions, not results from a completed player study.

What you can do

• Click or tap the matching objects shown in the target tray.
• Drag to pan, scroll or pinch to zoom, and use Peek to look behind scenery.
• Use the on-screen hint when stuck, then continue to the next scene after finding every target.

What this build does and does not show

This release is a contained hidden-object game associated with Kidlandia. It does not mean every place shown in its illustrations has become a navigable VR environment, or that an entire Kidlandia campaign is available. The illustrations carry a different sort of interaction: observation, recognition and careful searching.

Try taking in a scene before looking at each target, then use the tray to focus your search. Move closer when a shape catches your eye; use a hint if curiosity turns into a standstill. We are interested in those transitions: from first impression to inspection, from uncertainty to recognition, and finally to the desire to see another scene. A world should reward attention, even when the only movement available is through a picture.

Every found object is a small moment of recognition. This experiment gives us a way to keep exploring how those moments might make an illustrated world feel alive to its visitors.

Cutie World Find It is an Arcade experiment, not the completed CosmOS VR world or campaign.

Place something in the void. See what changes.

Start with an empty field. Choose a material, place it into the space and see how it responds. Change the conditions with a tool, then try something else. Voidway Field is a contained browser experiment where the invitation is simple: touch the rules and discover what they do.

The experience

An empty field does not tell you much about what it can become. Put something into it, though, and the question changes: what happens next? Voidway Field is a standalone browser materials sandbox built around that invitation. Choose matter from a palette, draw into a bounded simulation, apply a tool and watch the response.

There is no need to introduce an entire world before testing this simple exchange. An action creates a visible change; the change invites another action. Perhaps you try a different material, remove something or change the conditions with heat, cold, pressure or wind. The experiment asks whether playing with a set of rules can feel interesting before those rules are surrounded by a campaign, a character or a landscape.

The controls make the question tangible. Select and draw materials, right-click to erase or reverse an applicable tool, middle-drag to pan, and resize the brush or zoom with the scroll wheel and Ctrl modifier. The field offers a space for direct manipulation. Those specific interactions are what the released browser build provides.

Testing for feel

Testing for feel means asking more than whether a simulation runs. Does placing matter produce a response you can understand? Do heat, cold, pressure and wind invite experimentation? Can the results encourage you to wonder what another change might do? These are questions this small playable field helps us explore, not reported results from player testing.

Testing for feel is not the same thing as checking that a simulation runs. A reaction can be mechanically valid and still difficult to read. Can you tell which change came from the material you placed and which came from a tool? Does the result appear connected to what you just did? Is there enough continuity between one experiment and the next for you to form a new question? The field gives us a contained way to examine those relationships.

Readability and surprise are not opposites. Ideally, an unfamiliar result encourages another experiment because you can identify some part of its cause. If everything behaves exactly as you predicted, the space may stop inviting exploration. If nothing has an understandable cause, it may feel like noise. The design problem is to make the rules discoverable without turning play into a rigid tutorial.

The brush matters as much as the material list. Placing a single mark asks a different question from filling an area. Erasing lets you revise the field instead of beginning again whenever an experiment becomes messy. Panning and zooming let you inspect what you have made. These ordinary affordances shape whether the sandbox feels responsive and approachable, even though they are not themselves the simulation's grandest features.

We can describe the purpose of this build and what someone can do in it. We cannot claim that it has already produced proven findings about player enjoyment, or that its materials represent finished world-scale systems. Does placing matter produce a response you can understand? That remains a question to investigate by playing, observing and refining the interaction.

What you can do

• Select materials and tools from the palette, then draw into the field.
• Right-click to erase or reverse applicable tools; middle-drag to pan the view.
• Scroll to resize the brush, or hold Ctrl while scrolling to zoom.

Inside the experiment

Inside Voidway Field: placing and erasing matter in a bounded field lets you investigate the simulation's response to available tools. It is a place to experiment with readable interaction, not a demonstration of an entire world.

Life simulation, weather systems, embodied player survival and their integration into the wider VR worlds remain separate development goals; they are not features demonstrated by this Arcade release.

What this build does and does not show

Inside Voidway Field, the experiment is intentionally limited to a browser field. Life simulation, weather systems, embodied player survival and integration into the wider VR worlds are separate development goals, not features demonstrated here. A materials sandbox can inform how we think about cause and effect, but it should not be mistaken for proof that an entire world has been built.

Try putting down a little matter and making one change at a time. Notice when the field behaves as you expected, when it surprises you, and whether you can think of another experiment from what you saw. That loop—act, observe, wonder, act again—is the feeling this release gives us a place to explore. The larger CosmOS journey continues elsewhere; this is one honest, playable question within it.

This is a standalone materials experiment, not a released VR world or survival mode. The purpose is to explore the immediacy of interaction here while the wider CosmOS systems remain a separate development journey.

Voidway Field is an Arcade experiment, not the completed CosmOS VR world or campaign.

Feel before volume

First-wave testing is intended to gather useful feedback on focused, rough experiences. Readability, movement, interaction, and the desire to keep exploring matter more at this stage than a long list of promised content.

Registration is not immediate build access. It lets interested players be considered when a suitable test opportunity is ready; no specific launch date is announced here.

Useful feedback

• What is understandable without an extended tutorial?
• Which interactions feel clear, confusing, or inconsistent?
• Does a rough experience still invite curiosity?

Future test announcements should identify the actual build and entry conditions separately.

Before the Arcade releases, there were other ways to enter The CosmOS.

An illustration can give a place its first sense of scale. A comic can introduce someone who seems to have lived a whole life before the first panel. A wallpaper can make you linger on a landscape and wonder what lies beyond its edges. None of those experiences requires a finished game. They begin with an invitation: imagine being there.

These were the kinds of invitations that came before our public browser experiments. The Archives bring them together as a collection of things you can actually discover while the larger universe is still being built.

What makes a world worth entering?

One of the challenges of building a universe of massive worlds is that its identity cannot live in a single description. We can tell someone that a place has history, but a scene or story needs to make them curious about that history. We can describe a character, but a glimpse of their choices can say more than a profile ever could.

Art and comics let us explore that difference. The public media records include Signal From The Hidden City and Kidlandia: The Rules, alongside illustrations and wallpapers. They are different kinds of windows into The CosmOS: a moment from a story, an impression of a setting, a view someone might want to return to.

The purpose of collecting them is not to suggest that every depicted place is already playable. It is to give each piece space to establish a feeling of its own, and to let visitors follow whichever thread catches their attention.

Testing for feel, even before play

When we talk about testing for feel, we are not only talking about buttons and movement. Presentation has a feeling, too. What makes an image feel like an invitation rather than an advertisement? How much context does a comic need before its world becomes intriguing? When should an unfamiliar name be explained, and when should it leave a useful mystery?

Those are editorial and design questions we want to explore as the collection grows. An image that looks striking is not automatically a convincing place. A promising title is not the same thing as a finished story. We need to pay attention to what the material genuinely communicates rather than assuming the intention has reached the visitor.

We have not published a formal audience study proving how these pieces make people feel. The Archives simply provide a public place to encounter them, compare their different approaches and give the universe an identity through actual work instead of a catalogue of promises.

What you can find today

The collection includes available comic records, art and wallpapers. Some other formats appear as records of work in progress, and that distinction is deliberate. The First Threshold has a novella cover record; it is not a published manuscript. Audio is marked as incoming, not as something you can download.

A cover can be a compelling first encounter with a story. It should not have to pretend the whole story is ready. We would rather be clear about the current material and let each future release earn its own moment.

That clarity is part of the experience. When you open an item in the Archives, the interesting question should be what it shows you about the world, not whether the site has accidentally promised something that is not there.

Another way into the universe

Playable browser experiments arrived later and added a different sort of invitation. An illustration asks you to look; an Arcade experiment asks you to do something and observe the result. The Arcade now lives alongside the media collection, but its releases have their own dated announcements and their own boundaries. A playable experiment is not a release of the associated VR world or campaign.

That relationship is what makes the Archives useful. Someone can arrive for a picture, stay for a comic and eventually try a small interactive idea. Each encounter is a different way to discover The CosmOS, without requiring us to claim the universe is complete.

We want the collection to grow with the work: more real places to see, more stories to follow, and more experiments that reveal what it might feel like to inhabit them. For now, the pieces already available are enough to begin.

Editorial chronology: May 3 is the timeline position of this retrospective about earlier media. The previous article describing the later Archives reorganization originally appeared August 16, 2026; that reorganization is not being dated to May.