You can write software where for 3d model You can add strategy (code) and state (data, color) to each of pixels. If it's samurai model then edge of katana blade is responsible for something else than eye, etc.
3D model can be made hacking tool or anything else (for example engine model can handle real engine). Advantages are such, that even if plane loses part of wing, it can be not only noticed (we know which of tiny computers on the plane's wing do not respond), but also rest of them still work (for example to handle the evacuation and more).
More advanced implementation hints:
How pixels can be grouped to cooperate, for example in katana's blade? Just like it's done in standard server/clients paradigm. Or servers/workers. We can even mix strategies from many servers in one destination pixel (worker). We can use shared services, for example memory. Or we can use peer-to-peer programming paradigm. P2P is similar to talking objects (sending messages like in classic approach to Object Oriented Paradigm).
Will there be Garbage Collection for Stitie Machine? For now i think no. It has to be handled manually. Argument is such that it's so low level mechanism that it can and should be handled manually, like in the Assembler, to allow for more tricks. Some programmers think that memory deallocation is so important that it has to be done with automated garbage collection. Others think opposite, that it's so important that it has to be done manually. These arguments contradict themselves.
See also: Stitie Machine, and its implementations: Core 1.0 and Sunsail 1.1 .