My objective is this: overpopulate the world with Rhapsody engines that feed off themselves and replicate into the far corners of the universe. I presume most product companies think like this, and there is no reason to wait for customers when your products can create more of themselves while outlasting their own progenators by generations.
Now it would be a bit irresponsible if these machines were simply clones of each other; an interoperability monoculture could have dystopian consequences. And so it will be prudent to introduce errors and mutations to keep the pool vibrant and vital.
We will build a better box.
What we are actually doing, all hyperbole aside, is making a factory. A Rhapsody engine is delivered as a blank slate, tabula rasa as it were — plenty of gizmos there from which to build, but not much direction, as young Picasso discovered when faced with his first painting commission. What am I to do with all these brushes and colors? he asked himself. Naturally, that one is lost to the ages, but we don't have to face the same fate because we have a pretty good idea what is done with our product.
We can classify the way our Rhapsody Integration Engine is used as any of three or four basic styles. And within any of those styles there are some common best (or at least preferred) practices and patterns.
For style A, then, we can identify say, four, patterns, all following a consistent preferred practice. So let’s create a mold (or assembly) for each of them. When we build that next engine, we can deliver it with just those molds, or we can deliver it pre-built with X of pattern 1 and Y of pattern 2 and customize each one.
Think about how a car dealer fills their lot — not with 200 of the same car, but with 40 each drawn from five different models. No two are exactly the same. That’s what we are doing with the Factory.
Everything we need to create this utopian future is in the Rhapsody product already. We build the molds in Rhapsody and we assemble the orders with Rhapsody. The only thing we don’t do (though we could) is decide which cars to put on the lot. That's up to the customer. After all, they are going to drive it, and we actually need somebody to pay for our science-fiction fantasy.
Here’s a preview:
In this case, it is not a fantasy. It is not fan fiction. Rather, it’s a Stage 3 Prototype from the Co-Creation Lab MakerSpace, coming to an interoperability universe near you.