Difference between revisions of "Copyfication square"
m (Apm moved page Copification square to Copyfication square: spelling error) |
(added note on analogy breakdown to the fire triangle) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
{{site specific term}} | {{site specific term}} | ||
| − | " | + | "Copyfication" for "immobile replication" or "immobile self-replication". |
| + | |||
| + | == Analogy breakdown to the fire triangle -- runaway accidents no longer possible == | ||
| + | |||
| + | Unlike the [[reproduction hexagon]] and the [[replication pentagon]] this is no longer an analogy to the fire triangle <br> | ||
| + | where when all sides are fulfilled it leads to a runaway chain reaction. <br> | ||
| + | Without mobility copies pile up and congest further copying. See below. <br> | ||
| + | Plus without active plug-in to the required resources by an external actor <br> | ||
| + | not even a second generation of copies can operate by themselves itself. | ||
== The four sides of the immobile self-replication square == | == The four sides of the immobile self-replication square == | ||
| Line 16: | Line 23: | ||
* replicator mobility -- needed for the (outdated) [[molecular assembler]] concept | * replicator mobility -- needed for the (outdated) [[molecular assembler]] concept | ||
* sufficient adaptivity -- needed only by biological life | * sufficient adaptivity -- needed only by biological life | ||
| + | |||
| + | == Intuitive image of pileup and congestion == | ||
| + | |||
| + | Just like on a photocopier on the output side products pile up, and if they are not removed <br> | ||
| + | manually then the clog prevents any further copying process. <br> | ||
| + | Pileups could be quite bad though if congestions are not detected. <br> | ||
| + | <small>Remotely related topic: Breach of a [[global microcomponent redistribution system]].</small> | ||
| + | |||
| + | In contrast replicators ([[replication pentagon]] applies) move actively out of the way (arbitrarily far) <br> | ||
| + | to make space for an arbitrary amount of further replications. | ||
== Blueprint data mobility == | == Blueprint data mobility == | ||
| Line 25: | Line 42: | ||
== Related == | == Related == | ||
| − | * [[reproduction hexagon]] - [[replication pentagon]] - [[ | + | * [[reproduction hexagon]] - [[replication pentagon]] - [[copyfication square]] |
* [[self replication]] | * [[self replication]] | ||
Latest revision as of 11:57, 17 May 2021
"Copyfication" for "immobile replication" or "immobile self-replication".
Contents
Analogy breakdown to the fire triangle -- runaway accidents no longer possible
Unlike the reproduction hexagon and the replication pentagon this is no longer an analogy to the fire triangle
where when all sides are fulfilled it leads to a runaway chain reaction.
Without mobility copies pile up and congest further copying. See below.
Plus without active plug-in to the required resources by an external actor
not even a second generation of copies can operate by themselves itself.
The four sides of the immobile self-replication square
There are four necessary requirements on selfreplicativity for a gemstone metamaterial on-chip factory.
Needed are:
- replication capability
- building block availability
- energy supply
- blueprint data mobility (a mere digital access to a central copy is sufficient, some redundancy is advisable though for resiliency)
Not needed are:
- replicator mobility -- needed for the (outdated) molecular assembler concept
- sufficient adaptivity -- needed only by biological life
Intuitive image of pileup and congestion
Just like on a photocopier on the output side products pile up, and if they are not removed
manually then the clog prevents any further copying process.
Pileups could be quite bad though if congestions are not detected.
Remotely related topic: Breach of a global microcomponent redistribution system.
In contrast replicators (replication pentagon applies) move actively out of the way (arbitrarily far)
to make space for an arbitrary amount of further replications.
Blueprint data mobility
A note on "blueprint data mobility":
The biological example of DNA with a full nanomechanically encoded datastorage copy in
every single cell is ridiculously inefficient and nothing we would want to mimic in artificial systems for manufacturing.
Related
- reproduction hexagon - replication pentagon - copyfication square
- self replication
