Internal · SpaceMusic Factory · Status 22 October 2026
The Factory Ecosystem
One page that shows what the Factory is, what each part does and does not do, and what is still worth building.
What the Factory is
We build fast now. With Claude doing most of the typing, a new part can exist a day after someone thinks of it. The risk is no longer slow work. The risk is two people who mean different things by the same word.
This document fixes the words. It starts with one definition:
The Factory is everything that makes, improves, keeps and shows results. A result is one 3D model, with its pictures, and a record of where it came from.
"Where it came from" means the scene, the values, the machine and the SpaceMusic version. For old work it means the Dropbox file. A part belongs to the Factory when it does one of the four verbs to results.
Some things the Factory uses are not part of it:
The SpaceMusic app itself, and its parameters in DNA. The Factory drives SpaceMusic, but it does not build it.
The core library of scenes, models and textures. The Factory reads it.
The desktop tools on the studio PCs: Rhino, Blender, Maya, OrcaSlicer. The Factory calls them.
Live shows and streaming. They use SpaceMusic, not the Factory.
The map
The Factory has five departments, sorted by purpose. Two layers sit under all of them: the Archive, where every result lives, and the shared ground, which does the work and keeps the rules.
Import, the past. Old studio work comes in from Dropbox.Dropbox import, Convert to 3D
Automation, new work. SpaceMusic makes new results from a plan.Builder, Describe it + Claude, Queue, SpaceMusic runner
Finishing, improve. Results get pictures and better looks.3D views, Studio renders, AI context picture
Fabrication, make it real. A model becomes a printable object.Shrinkwrap, Slice, Print
Showroom, judge and act. People and Claude look, choose, and start actions.Gallery, 3D viewer, Rate and tag, Result actions, Claude looks
Every part has a card with the same five rows. Does is its job in one sentence. In and Out are what it takes and gives. Not is the line it does not cross. To is where its output goes next.
Every card also has a status. Live is built and in use. Partly is built, but a piece is missing, often a button. Planned has a written plan. Idea has no plan yet.
The Not row matters most. It is where two people usually disagree without noticing. For example: Import does not copy old files to the server. The Factory app stores nothing. Claude cannot delete. When a new idea needs one of those lines crossed, that is a decision, not a detail.
One result, many actions
Everything in the Factory turns around one thing: the result. Results come in from three sides. Old work comes through Import, new sweeps through Automation, and single exports from the SpaceMusic app, made by hand.
Once a result is there, a person acts on it. Each action hands the result to the department that does the work. A Worker renders it, or prepares it for print, or SpaceMusic sweeps its scene again. What comes out lands back on the same result, or as a new result linked to it.
This is a shift in weight. Until now the Factory put one action first: New automation from this. The result page is now being redesigned around an actions zone, one place on every result for everything you can do with it. A new automation becomes one action among many, next to Create rendering, Prepare for 3D print, Open its Dropbox folder and Download as zip.
The heavy work happens on the studio PCs, never on the server. A Worker on each PC pulls one job at a time from the queue. That is why a job for an offline machine waits, and why a crashed PC never loses a job.
Gaps and next modules
Most of the map is live. These parts are built in half, planned, or only an idea:
Part
State
What is missing
Result actions
Planned
The actions zone on every result. Being designed now; Create rendering comes first.
Studio renders
Partly
A button. It comes as the Create rendering action.
Shrinkwrap, Slice
Partly
They run, but only through the API. Prepare for 3D print would be their action.
Print
Planned
Sending a sliced file to the Bambu printer.
Render sheet
Planned
Pick results and stages, get one sheet.
Scene knowledge
Planned
Claude knows what parameters mean, then builds scenes. Two decisions are open.
AI context picture
Idea
An image AI puts the model into a place you describe.
Download as zip
Idea
All files of a result in one download. A one-file download exists.
Two things the map makes visible:
Every new tool is two things. It is a card in a department, mostly Finishing or Fabrication, and an action on the result. It needs no new department and no new storage. That keeps the next tools cheap: the AI context picture is one card and one action.
Fabrication has no door yet. Its first two steps work, but only through the API, so no designer can reach them. The actions zone gives it one: Prepare for 3D print.
Some things are decided against, and are on the map so nobody plans them again: screenshots of studio machines, schedules inside the Worker, opening .3dm files in the browser, and copying old originals to the server.
Keeping the map true
A map that is wrong is worse than no map. One rule keeps it true:
No new part without a card. Before we build it, it gets a department and the five rows: Does, In, Out, Not, To. A new tool also gets the name of its action.
If a new idea fits no department, stop and talk first. Either the idea is outside the Factory, or the map needs a new department, and both are decisions for people, not for Claude. If a card cannot fill its Not row, the idea is not clear enough yet.
Claude can redraw this page at any time. The source of truth stays the same: the plans in docs/Plans and the pages on docs.spacemusic.tv.
Glossary
Terms used in this document, in plain language.
Action
One thing you can do with a result, from one place on its page: render it, print it, sweep it, download it.
Archive
The list of all results plus their files. One row per result in the api database; files in MinIO and Dropbox.
Automation
A saved recipe: one scene plus the settings that change. It can run again.
.3dm
A Rhino 3D file. Exact, but big and slow to open.
.glb
A small 3D file for the web. The 3D viewer and Blender read it.
.stl, .gcode
A closed mesh for printing, and the step-by-step code a 3D printer runs.
.smbatch
The list of steps SpaceMusic runs for one automation.
api
api.spacemusic.tv, the single back end. It holds the data, the queue and the rules.
DNA
The database of SpaceMusic's parameters. Outside the Factory.
MCP
Model Context Protocol. The door through which a Claude chat reaches the Factory.
MinIO
File storage on our server for small files: pictures, .glb files, sidecars.
Nano Banana
The nickname of Google's image AI (a Gemini model). It can place an object into a scene you describe.
Plan
A checked, counted sweep that waits for a person's yes. Nothing runs before that.
Result
One 3D model, its pictures, and where it came from.
Run
One launch of an automation. The gallery shows it as a stack of results.
SSO
Single sign-on. One studio account for all our web tools.
Sweep
Many runs of one scene, each with different values.
Worker
A small program on a studio PC. It pulls jobs and starts SpaceMusic, Rhino or Blender for them.
Settled
Five departments, one centre
Import, Automation, Finishing, Fabrication, Showroom. Everything turns around the result, kept in the Archive. Workers do the heavy work.
Next
Actions on every result
Build the actions zone, with Create rendering first. Then give Fabrication its action.
Later
Claude understands scenes
Scene knowledge (plan 088) is the bridge from "plan a sweep" to "make a new scene".