May 1, 2026

Origins

slightly modified from the original image source
 Back in August of 2025 I collaborated with Claude to write the science fiction story titled "Battlefield Lipid". For that story, Claude and I pretended that life on Earth began when two different types of ancient space aliens arrived at Earth about 4,000,000,000 years ago and placed "seed microbes" on the planet. One of those two seed microbes evolved into Earth's bacteria while to other became the archaea.  

However, what if we went even further back on the scale of complexity and imagined that space aliens seeded Earth with molecules, not cells? Below is a discussion with Claude in which the article “The selfish ribosome” by Mart Krupovic and Eugene V Koonin is taken as a starting point for planning a new science fiction story. During this chat session with Claude, I tried to explore the idea that the original function of the peptidyltransferase center was the creation of amphiphilic peptides that formed the surface membrane of the first cells in the RNA-protein world. In this theory of the earliest ribosomes, those ribosomes were membrane-attached and they were essential for cellularity. In this theory of the origin of cells, the first cells existed in the RNA-protein world and only later did two distinct lineages of lipid-synthesizing cells arise at the transition to the RNA-protein-lipid world.

I provided Claude with a PDF file that included a copy of the journal article by Koonin (including its two figures) and an introduction to my goals for the chat session. 

 Me: Claude, process the file that I uploaded and then discuss with me the idea that an alien peptidyltransferase ribozyme could have been designed as an obligate membrane-associated molecular device. Claude, explain what is known about how existing ribosomes attache to lipid bilayer membranes and speculate about how an early peptidyltransferase ribozyme could have been anchored to a hypothetical cell surface "peptide bilayer membrane" in the earliest cells of the RNA-protein world.

Claude: {the text below in red was Claude's "thinking" process}

The user wants me to discuss the idea of an alien peptidyltransferase ribozyme designed as an obligate membrane-associated molecular device. They want me to:

  1. Explain what is known about how existing ribosomes attach to lipid bilayer membranes
  2. Speculate about how an early PTC ribozyme could have been anchored to a hypothetical cell surface "peptide bilayer membrane" in the earliest cells of the RNA-protein world

Let me think through what I know about ribosome-membrane interactions and then speculate about the pre-lipid world scenario.

Ribosome-Membrane Interactions in Modern Cells:

 In modern eukaryotic cells, ribosomes attach to the endoplasmic reticulum (ER) membrane to form the "rough ER." This attachment is mediated by:

  1.  Signal Recognition Particle (SRP): When a ribosome is translating a protein that has a signal peptide (hydrophobic N-terminal sequence), the SRP recognizes and binds to the emerging signal peptide. SRP then docks with the SRP receptor on the ER membrane.
  2. Sec61 translocon: The ribosome then docks with the Sec61 complex (translocon) in the ER membrane. The ribosome tunnel exit is positioned directly over the translocon channel, allowing the nascent peptide to be threaded through the membrane.
  3. Ribophorins: In the rough ER, ribophorins I and II are integral membrane proteins that help anchor ribosomes.
  4. Membrane association of large ribosomal subunit: The 60S (large) subunit contacts the ER membrane, specifically through the exit tunnel of the peptide, which aligns with the translocon.

In bacteria, some ribosomes are membrane-associated as well:

  • YidC/Sec translocase: Ribosomes translating membrane proteins can be directly coupled to the SecYEG translocon or YidC insertase
  • Signal peptides work similarly in prokaryotes
  • TF (Trigger Factor) associates with the ribosome exit tunnel

Key structural features enabling ribosome-membrane interaction:

{the text below in blue was Claude's actual response}

This is a rich and genuinely exciting concept to develop. Let me work through the science carefully in two parts before connecting it to your story's speculative framework.


How Modern Ribosomes Associate with Lipid Bilayer Membranes

In all modern cells, ribosomes exist in two populations: free cytoplasmic ribosomes and membrane-associated ribosomes. The membrane-associated population represents one of the most elegant molecular interfaces in cell biology, and its mechanism turns out to be surprisingly relevant to your hypothetical alien design.

In eukaryotes, membrane-bound ribosomes dock with the rough endoplasmic reticulum (rough ER). The attachment is not passive adsorption — it is highly organized and functionally obligate for a specific class of proteins. The mechanism proceeds in stages. As a ribosome begins translating a protein that carries a hydrophobic signal peptide at its amino terminus, a ribonucleoprotein complex called the Signal Recognition Particle (SRP) recognizes and binds the emerging signal sequence the moment it exits the ribosome's peptide tunnel. The SRP then acts as a tethering agent, docking with its cognate receptor protein embedded in the ER membrane. This brings the entire ribosome-nascent chain complex to the membrane surface, where the large ribosomal subunit (LSU) aligns its peptide exit tunnel precisely over a protein channel called the Sec61 translocon. The geometry is critical: the ribosome effectively forms a sealed junction with the translocon, so that newly synthesized peptide is threaded directly through the membrane rather than released into the cytoplasm.

Image generated by Flow.
 Several structural features of the LSU facilitate this membrane docking. Specific loops on the surface of the LSU's rRNA, particularly in expansion segments, contact the cytoplasmic face of the translocon. Ribosome-associated proteins called ribophorins I and II (in eukaryotes) serve as additional membrane anchors. Crucially, the ribosome's exit tunnel is not merely a passive conduit — it is a regulatory and sensing channel approximately 100 angstroms long, lined with rRNA and a small number of ribosomal proteins, that monitors the chemical character of the nascent peptide. The inner wall of the tunnel has a pronounced negative electrostatic character from the rRNA backbone, which tends to repel acidic peptides and retain basic or hydrophobic ones in ways that influence elongation rate and membrane targeting.

In bacteria, the homologous system uses the SecYEG translocon and the insertase YidC for co-translational membrane protein insertion. The bacterial Trigger Factor (TF) chaperone associates directly with the ribosome at the exit tunnel, assisting in the folding or membrane insertion of nascent chains. Importantly, in bacteria there is no compartmentalized ER — membrane-targeted ribosomes dock directly with the plasma membrane. This is architecturally simpler and arguably closer to the ancestral condition.

The universal conservation of the peptide exit tunnel geometry, and the way the tunnel's opening faces toward whatever membrane the ribosome is working with, strongly implies that membrane association was not a late innovation. The tunnel's geometry was apparently set very early in ribosome evolution, before the divergence of the three domains of life.


An Alien-Engineered Obligate Membrane-Associated PTC Ribozyme

Now here is where your story concept becomes genuinely compelling, because you can plausibly reverse-engineer a coherent molecular design.

If the alien engineers wanted to create a PTC ribozyme that was obligately membrane-associated — incapable of functioning unless anchored to a surface — they would have had several design options, and we can think through which ones are most plausible.

Image generated by Flow.
 The peptide bilayer membrane substrate. Before considering the ribozyme's anchoring mechanism, it helps to characterize the hypothetical membrane it was anchoring to. Amphiphilic peptides can self-assemble into bilayer-like structures in aqueous solution, a fact demonstrated experimentally with designed peptides. The key structural requirement is the same as for lipids: a hydrophobic region that prefers to exclude water, flanked by hydrophilic regions that face the aqueous exterior. Alpha-helical amphiphilic peptides accomplish this by placing hydrophobic residues on one face of the helix and hydrophilic residues on the other, allowing two such helices to pair their hydrophobic faces and form a bilayer-like assembly. Beta-hairpin peptides can form analogous sheet-like assemblies. Either architecture could in principle enclose an aqueous compartment. Such a peptide membrane would be more dynamic and more metabolically costly to maintain than a lipid bilayer — it would need continuous replenishment as constituent peptides exchange with the surrounding medium. This fragility is actually a feature from a narrative standpoint, because it creates a strong selective pressure for any compartment-dwelling replicator to produce amphiphilic peptides at high rate.

The ribozyme's membrane anchor domain. An alien-designed PTC ribozyme intended to be membrane-obligate would require a dedicated structural domain that accomplishes two things: it must anchor the ribozyme to the peptide membrane with sufficient affinity to keep it from diffusing away, and it must orient the ribozyme's peptide exit in the correct geometry relative to the membrane surface.

RNA can interact with hydrophobic surfaces and molecules through several mechanisms that are well-documented in modern biochemistry. Specific RNA aptamers bind small hydrophobic ligands with high affinity through the formation of internal binding pockets lined with stacked aromatic bases (the purine rings of adenine and guanine are aromatic and capable of hydrophobic stacking interactions). An alien-designed membrane anchor domain could consist of a dedicated aptamer-like RNA fold that inserts one face of a stacked aromatic platform into the hydrophobic core of the peptide bilayer, much as an intercalating drug molecule inserts between the layers of a lipid membrane. 

Image generated by Flow.
 A G-quadruplex structure — four guanine bases arranged in a planar hydrogen-bonded quartet — would be an especially elegant design choice here, because G-quadruplexes are extremely stable RNA secondary structures, and a stack of two or three G-quartets would present a substantial flat hydrophobic surface capable of intercalation into the peptide membrane's hydrophobic interior.

Alternatively, the anchor domain could exploit electrostatic interactions rather than hydrophobic insertion. If the amphiphilic peptides in the membrane carry positively charged residues (lysine, arginine, or their primitive analogs) in their hydrophilic headgroups, these positive charges would attract the strongly negatively charged phosphate backbone of the RNA ribozyme. This kind of charge-charge anchoring is actually how RNA binds to many modern lipid vesicles carrying cationic lipids. An alien design exploiting this principle would be simpler to engineer than a hydrophobic intercalation domain, but would be less specific and less geometrically precise.

The most sophisticated alien design would combine both: a hydrophobic intercalation domain that inserts into the membrane core and locks the ribozyme's orientation, paired with a fringe of RNA that forms charge contacts with the peptide headgroups, providing both geometric precision and high-affinity binding.

The exit tunnel orientation constraint. Here is the crucial design principle that makes the obligate membrane association functional rather than merely structural. The alien engineers would have configured the ribozyme so that its peptide exit — the equivalent of what became the LSU tunnel in modern ribosomes — faces directly toward the membrane surface when the anchor domain is correctly engaged. This means that every amphiphilic peptide synthesized by the ribozyme would be ejected directly into the peptide bilayer, effectively weaving new structural material into the membrane from the inside surface. The ribozyme would function as both a biosynthetic machine and a membrane maintenance engine simultaneously.

Image generated by Flow.
 This design creates a beautiful molecular mutualism at the smallest possible scale. The ribozyme is dependent on the membrane for its functional orientation — an unanchored ribozyme, tumbling freely in solution, might produce peptides but would do so with reduced efficiency because the correct three-dimensional arrangement of its catalytic components would be subtly disrupted without the mechanical constraint of membrane anchoring. Conversely, the peptide membrane is dependent on the ribozyme for replenishment. The two structures are co-obligate at the molecular level, before there is even a cell in any meaningful sense.

The first-peptide anchoring hypothesis. There is an additional design possibility worth considering for your story. The alien PTC ribozyme might have initially anchored itself through its own reaction products. In modern ribosomes, the nascent peptide exits through the tunnel while still attached to the tRNA at its 3' end via an aminoacyl ester bond. A primitive ribozyme might have been designed so that its first synthesized peptide — perhaps a short amphiphilic sequence of five to ten amino acids — remained transiently tethered to the ribozyme via a structural equivalent of the peptidyl-tRNA linkage. This initial peptide would spontaneously insert into the peptide bilayer, dragging the ribozyme to the membrane surface and orienting it correctly. Subsequent peptides would be cleaved free and incorporated into the membrane independently. This bootstrapping mechanism — where the ribozyme uses its own first product to anchor itself — is elegant precisely because it requires no separate machinery for membrane targeting.


Connecting to the Story's Pre-Lipid World

Image generated by Flow.
 What makes this framework particularly compelling for your narrative is the explanation it provides for the eventual transition from the peptide membrane world to the lipid membrane world. A peptide bilayer is metabolically expensive: every constituent peptide is a complex polymer requiring multiple amino acids, each amino acid requiring its own biosynthetic pathway. Lipids, by contrast, can be synthesized by a relatively simple chain-elongation chemistry from acetyl units. Any protocell that evolved the ability to synthesize even primitive lipid-like molecules would have an enormous energetic advantage, because it could replace costly peptide membrane components with cheap lipids. Under your story's framework, this transition would have occurred independently in two lineages — one giving rise to bacteria with their ester-linked lipids, and one to archaea with their ether-linked isoprenoid lipids — which coincidentally is exactly what the real molecular phylogeny of lipid biosynthesis suggests. The two lineages invented lipid membranes independently, using entirely different chemical pathways, which has always been one of the great puzzles of early cell evolution.

The alien seed molecules — your PTC ribozyme and RdRP ribozyme — could thus have been designed not as the final answer but as a starting system that would, through its own evolutionary logic, eventually transcend the peptide membrane phase and arrive at the lipid bilayer world. Whether that transcendence was intended by the alien engineers, or was an unintended emergent consequence, is exactly the kind of question your story could explore with considerable philosophical depth.

 Me: Claude, assume that the earliest cells had a peptide-based surface membrane that had holes in it. The holes allowed small nutrient molecules (all synthesized by non-biological chemical processes taking place on the early Earth) to enter the cell through the holes. The cell contained two key types of RNA molecules that both functioned as polymerases: one that made polypeptides from amino acids (the proto-ribosome) and another that polymerized RNA chains from nucleotide subunits and had some capacity to function as an RNA replicase. Both of these polymerizing ribozymes might have had multiple RNA subunits. There would have been natural selection for polypeptides and RNA molecules that could bind together with high affinity, aggregate and not escape through the holes in the peptide-based surface membrane.  One of the RNA subunits for either the proto-ribosome or the RNA replicase could have coded for an amphiphilic peptide that would self-assemble into bilayers. The early proto-ribosome may have automatically attached a hydrophobic "leader sequence" to all of the polypeptides that it synthesized in order to prevent production of hydrophilic peptides that that might escape from the cell through its porous surface membrane.

Claude: {the text below in red was Claude's "thinking" process}

The user wants to explore a detailed speculative framework for the earliest cells with peptide-based membranes with holes, and develop the molecular biology of how early ribozymes and their products would have been retained within such cells. This is fascinating science fiction worldbuilding grounded in real biochemistry. Let me think through this carefully and systematically.

Key concepts to address:

  1. The porous peptide membrane as a selective filter
  2. Natural selection for retention of molecules within the cell
  3. The hydrophobic leader sequence hypothesis
  4. RNA-peptide aggregates as retained complexes
  5. The transition to lipid membranes

Let me think about each of these in depth.

{the text below in blue was Claude's actual response}

This is an exceptionally well-constructed theoretical framework, and each element you've introduced connects to real biochemistry in ways that make the whole system surprisingly self-consistent. Let me work through the implications carefully.


The Porous Peptide Membrane as a Selective Pressure Engine

The image of a proto-cell with a leaky peptide surface membrane is actually more biochemically realistic than a fully sealed compartment would be at this stage of evolution. A perfectly sealed membrane from the outset would require a sophisticated and already-evolved lipid biosynthesis apparatus — which is precisely what doesn't yet exist in your RNA-protein world. But a self-assembling peptide bilayer with structural gaps is something that could arise spontaneously from the products of your alien-seeded PTC ribozyme without any additional design.

The hole geometry matters enormously here, and it creates a beautifully clean selective pressure. Small molecules — individual amino acids, mononucleotides, short oligonucleotides, simple metabolic intermediates — pass freely in both directions through gaps between the loosely packed amphiphilic peptides. This free passage is actually essential for the proto-cell's survival, because in your framework the cell has no biosynthetic metabolism of its own yet. It is entirely dependent on the abiotic chemistry of the early Earth environment for its supply of amino acids and nucleotides. The porous membrane must be leaky enough to admit these nutrients, which means it is necessarily also leaky enough to lose small molecules synthesized internally.

This creates an immediate and powerful selection pressure that operates at the molecular level before there is anything resembling a true organism. Any molecule produced inside the proto-cell that is small and hydrophilic enough to pass through the membrane gaps is effectively lost to the environment. Any molecule that is too large to pass through, or that associates strongly with the membrane itself, or that aggregates with other molecules into complexes too large to escape, is retained. The proto-cell accumulates retained molecules at the expense of lost ones. This is natural selection acting on individual molecular species before it acts on anything we would recognize as a genome.

The critical insight is that this is not merely a passive size filter. It is a chemical character filter. Hydrophilic small molecules leave. Hydrophobic molecules associate with the membrane and stay. Large complexes stay. Molecules that bind to other molecules and form assemblies stay. The selective pressure simultaneously favors hydrophobicity, large size, and intermolecular affinity — and each of these properties happens to be useful for building more sophisticated cellular machinery.


The Hydrophobic Leader Sequence Hypothesis

This is the most conceptually elegant element of your framework, and it deserves careful unpacking because it solves several problems at once.

Consider the situation from the proto-ribosome's perspective. It is synthesizing peptides from amino acids that have diffused in through the membrane holes. If those peptides are short and hydrophilic, they will diffuse right back out through the same holes. The proto-cell is essentially running a futile cycle: importing amino acids, polymerizing them into peptides, and then exporting those peptides as the proto-ribosome inadvertently manufactures food for the surrounding environment. Any proto-cell doing this is wasting its imported nutrients and gaining nothing.

Your proposed solution — that the proto-ribosome may have automatically appended a hydrophobic leader sequence to all synthesized polypeptides — is structurally analogous to the signal peptide system in modern cells, but inverted in its logic in a fascinating way. In modern cells, the signal peptide is a targeting device that sends proteins to specific membrane locations. In your primitive system, the leader sequence is a retention device that prevents proteins from escaping the cell at all. The evolutionary pressure runs from retention toward targeting, which gives a plausible pathway for how the modern signal peptide system could have originated.

The mechanics of a universal hydrophobic leader would work as follows. If the proto-ribosome began every synthesis cycle with the same or similar hydrophobic amino acids — either because those amino acids were the most abundant in the early Earth environment, or because the ribozyme's active site had a structural preference for initiating with hydrophobic residues, or because the alien designers built in this preference deliberately — then every peptide product would carry a hydrophobic tail at its amino terminus. This tail would insert into the hydrophobic core of the peptide bilayer membrane the moment the nascent peptide grew long enough to reach the membrane surface. The peptide would be anchored before it was finished being synthesized.

This creates a remarkable functional consequence. The proto-ribosome itself would be dragged toward the membrane as it produced peptides, because each nascent chain would be tugging it toward the bilayer. This is mechanistically very similar to what you described in the first discussion — membrane-associated ribosomes threading their products directly into or through the membrane. The difference is that in your primitive system this association arises not from a dedicated docking mechanism but from the simple chemistry of hydrophobic insertion. The sophistication emerges from the physics rather than from complex molecular recognition.

There is an additional consequence worth developing. A peptide with a hydrophobic leader that inserts into the membrane will be oriented with its hydrophobic terminus anchored in the bilayer and its subsequently synthesized, potentially more hydrophilic residues extending into the aqueous interior of the proto-cell. This is precisely the topology of a modern integral membrane protein. The earliest membrane proteins in your framework would not be sophisticated ion channels or receptors — they would be the clumsy, unoptimized products of a ribozyme that simply attached a hydrophobic hook to everything it made. Some of these randomly structured membrane-anchored peptides would, by chance, adopt conformations that slightly modified the permeability of the membrane. Some would enlarge the holes, which would be disadvantageous. Some would partly occlude the holes, which might be neutral or slightly advantageous if the proto-cell had begun synthesizing valuable small molecules that it didn't want to lose. This is a direct path toward selective membrane permeability without requiring any foresight or complex design.


RNA-Peptide Aggregates as the First Retained Genetic Material

The second major retention mechanism you identified — molecules binding together into assemblies too large to escape through the membrane holes — is where the story becomes particularly rich, because it provides a direct selective pressure for the evolution of ribosomal proteins.

Consider the RNA replicase ribozyme. It is a large molecule, possibly tens of thousands of daltons, certainly too large to escape through the membrane holes on its own. But the RNA it produces — short RNA chains, primers, template fragments — might well be small enough to escape. Any RNA that diffused out would be gone, taking its sequence information with it. There is therefore strong selection pressure for any RNA molecule that can bind tightly to the replicase ribozyme itself, or to other large retained structures, because bound RNA stays inside the cell.

Now consider what kinds of peptides would bind tightly to RNA. RNA is a polyanion — its phosphate backbone carries a dense negative charge at physiological-like pH. Peptides rich in positively charged amino acids (the simplest being any peptide with abundant lysine or arginine equivalents, or even the simplest positively charged amino acid, ornithine, which predates arginine in biosynthetic complexity) would bind electrostatically to RNA. Such peptides, even if they were short and would otherwise escape through the membrane holes, would be retained by association with the large RNA molecules. The RNA molecules and the basic peptides would form non-covalent complexes, and the complex as a whole would be too large and too structured to escape.

This is the origin of ribosomal proteins. Not designed molecules with specific folds and functions, but primitive cationic peptides whose initial selective advantage was simply that they didn't leave the cell, because they were stuck to the RNA that synthesized them or to the RNA replicase that copied them. The function came later. The retention came first.

There is a beautiful autocatalytic logic buried in this. A proto-cell that produces cationic peptides retains those peptides via RNA association. The retained peptides stabilize the RNA molecules they are bound to, protecting them from hydrolysis and helping maintain their three-dimensional folds. Better-folded RNA molecules are more efficient polymerases, producing more peptides per unit time. More peptides means more RNA stabilization. The cycle is self-reinforcing from the very beginning, and it requires no external design beyond the initial seeding of the PTC ribozyme and the RdRP ribozyme.


The RNA Subunit Coding for Amphiphilic Peptides

Your proposal that one of the RNA subunits of either the proto-ribosome or the replicase could have coded for a membrane-forming amphiphilic peptide is where the molecular biology becomes most interesting, because it raises the question of how template-directed peptide synthesis could emerge from a non-templated peptidyltransferase ribozyme.

In the Krupovic-Koonin framework you uploaded, the earliest protoribosome is explicitly non-templated — it produces peptides from abiotic amino acids without reading any sequence information, essentially acting as a random polymerase that strings amino acids together without specifying their order. This is consistent with the experimental evidence from reconstructed protoribosome fragments. But random peptides are mostly useless. The transition to template-directed synthesis — where a specific RNA sequence specifies a specific peptide sequence — is the fundamental revolution that makes life informational rather than merely chemical.

Your proposal creates a selection pressure for exactly this transition. Imagine a proto-cell whose replicase ribozyme has, by chance, acquired a structural domain that happens to present a sequence of three or four nucleotides near the active site of the PTC ribozyme in such a way that specific amino acids are preferentially incorporated. The peptide produced is not completely random — it is biased toward whatever amino acid has chemical affinity for those nucleotides. If that biased peptide is amphiphilic — hydrophobic on one face, hydrophilic on the other — it will spontaneously self-assemble into bilayer patches and reinforce the proto-cell membrane. A proto-cell with a better, denser membrane retains molecules more efficiently, grows larger, divides more frequently, and outcompetes proto-cells with leakier membranes.

This is not yet a genetic code. It is a chemical bias in amino acid incorporation that happens to produce a useful molecule. But it is a direct precursor to a genetic code, and it arises from precisely the selective pressure your framework establishes. The proto-cell does not need to understand what it is doing. The chemistry does the work.

In your alien-seeded scenario, the designers could have pre-loaded this relationship deliberately. The alien PTC ribozyme could have been engineered with a structural motif that presents a short nucleotide sequence to bias its peptide synthesis toward amphiphilic products. The alien RdRP could have been designed so that one of its structural RNA domains — not the catalytic core, but an accessory subunit — contains the template sequence for an amphiphilic peptide when read in the proto-ribosome's active site. The two alien seed molecules would then be mutually dependent from the first moments of their co-existence: the replicase provides the template bias for membrane peptide synthesis, and the proto-ribosome provides the amphiphilic peptides that maintain the compartment in which both of them reside.


The Hole-Sealing Transition and the Path to Lipid Membranes

One final consequence of your porous membrane model deserves attention, because it creates a natural narrative arc from the RNA-protein world to the RNA-protein-lipid world.

As the proto-cell accumulates membrane-anchored peptides through the hydrophobic leader mechanism, the membrane gradually becomes more densely packed. The holes become smaller on average. Small molecules still pass in and out, but the rate decreases. At some point, a proto-cell might evolve peptides that are efficient enough at packing the membrane to significantly slow the influx of nutrients. This would be a crisis — a proto-cell that seals itself too well starves — and it would drive selection for small-molecule transport mechanisms. The earliest membrane transport proteins in your framework would not be sophisticated pumps but simply membrane-anchored peptides that happened to adopt conformations creating a narrow aqueous channel through the hydrophobic bilayer core.

Meanwhile, the problem of membrane maintenance by peptide synthesis is energetically costly. Each membrane peptide requires multiple amino acids, each requiring their own chemical synthesis. A proto-cell that could replace even a portion of its peptide membrane with lipids — which can be synthesized by much simpler chain-elongation chemistry — would have an enormous energetic advantage. The first lipid biosynthesis pathways need not have been efficient or complete. Even a proto-cell that could synthesize a few simple fatty acids and incorporate them into its membrane alongside the peptide components would be better off than one relying entirely on peptides.

In your two-lineage framework, two independent populations of proto-cells solved this problem in two different ways — one evolving ester-linked fatty acid lipids (the bacterial solution) and the other evolving ether-linked isoprenoid lipids (the archaeal solution). The alien seed molecules were agnostic about which lipid chemistry would win. They simply created the selective pressure — maintain your membrane or perish — and two different chemical lineages responded to that pressure with two different innovations. This is both scientifically plausible and narratively satisfying, because it means the aliens did not dictate the outcome of life on Earth. They created the conditions, and Earth's chemistry found its own solutions.

 Me:

Claude

 Me:

Claude

 

 

UNDER CONSTRUCTION

dfs

dsf

Next

Apr 26, 2026

The End of ImageFX

House alien.
by Flow.
 For several weeks I have been seeing a message inside Google's ImageFX saying that Google is terminating ImageFX on April 30th 2026. Today I clicked the button to transfer my old saved images from ImageFX to Google's Flow. It only took Google a few minutes to transfer over to Flow my old ImageFX images going back to January 2025.

Any of the old ImageFX-generated images can now be edited by Flow using Nano Banana 2. I also have access to the original text prompts that ImageFX used to make the images. An example is shown below in Figure 1...

Figure 1. The end of ImageFX.

Inside the ImageFX Creations folder in Google's Flow.

The original text prompt for the image that is shown above was: "science fiction movie still, a futuristic mansion on a distant exoplanet, the mansion is surrounded by palm trees and other desert plants, there are NO suns, stars or planets visible in the movie still 35mm film".

I gave Flow a new prompt that it could use to edit the original image: "Add to this science fiction scene: in the foreground a tall slender young blond woman walking on the stone-paved path towards the front door of the mansion. The woman is seen from behind. The woman is dressed in a tight-fitting futuristic silver metallic jumpsuit that sparkles in the star light of this distant exoplanet. The entire body of the woman can be seen from her black boots to the top of her head." The new image that was generated by Flow is shown below in Figure 2a...

Figure 2a. New image generated by Google's Flow from the image shown in Figure 1.



Planet by Flow.


I made the mistake of mentioning in my text prompt that this scene is on an exoplanet. Google's free image generating software always wants to place big looming planets in the sky for any scene involving an exoplanet (see Figure 2a, above). I wonder if Flow could have found a more ugly way to arrange her hair. I don't know if their "pro" version of the image-generating software is any better than the free version that I have access to.

Humanoid
by Flow.
In my science fiction story "The Nanite Smuggler", Tyhry visits the home of Kasty the Yastyn on the planet Threy. That big empty house (Figure 1) seemed too empty. Here is the new editing prompt that I applied to the image in Figure 2a: "Change the woman's hair so that it falls naturally past her shoulders. Remove the looming ringed planet from the sky. Add a tall slender humanoid female inside the mansion in a room on the first floor. The humanoid female is looking out through the window at the blond woman as she approaches the mansion." The resulting image is shown below in Figure 2b...

Figure 2b. New image generated by Google's Flow from the image shown in Figure 2a.


Figure 3. Altered alien by Flow.

For me, it looks like this alien mansion has three floors. The humanoid alien that was generated by Flow appears to extend from the first floor to the second floor (Figure 2b, above).

I tried to correct the size of the alien and alter its appearance with the following new editing prompt: "Reduce the size of the humanoid female inside the house to half the height. Give the humanoid female long wavy black hair, long pointed ears that protrude through the hair on her head and very large glowing alien eyes." The resulting new image is shown in Figure 3.

For the new image in Figure 3, Flow was able to put hair on the head of the alien and give her long ears and glowing eyes, but she appears to be only slightly shorter than what was originally generated in Figure 2b.

Figure 4. The Astra Lounge by Flow.
I tried once more with a simple editing prompt: "Reduce the height of the humanoid female to half of the current size." The resulting image is shown in Figure 4.

 Welcome to the Astra Lounge. Flow proved that it can shrink a woman, but Flow shrank the wrong woman (compare Figure 3 to Figure 4). Also, Flow spontaneously decided to add a sign that says "Astra Lounge". This kind of inability of Google's free version of the software to follow what seems like simple instructions is a source of frustration. These newly generated images were saved inside Flow's "ImageFX Creations" folder.

Figure 5. A 9/8/2025 Whisk project moved to Flow.
I also transferred my saved files from Whisk to Flow and they were added in to the displayed list of Flow "projects" (going back to December 2025, see Figure 5), with the oldest successfully transferred Whisk-generated files shown as being from May of 2025. It seems as if I did not recover my oldest Whisk files which were created in January of 2025.

The transferred Whisk → Flow files include the Whisk-generated videos (see Figure 6).

Figure 6. A Whisk video now in Flow.

 Extend. For the old Whisk-generated videos, the available options in Flow are shown in Figure 7.

Figure 7. Video options for Flow.
When some of the Whisk-generated images are re-opened in Google's Flow, the images do not always appear to have been correctly re-proportioned (see Figure 8).

I had Flow make an edit to the Whisk-generated image that is shown below in Figure 8. The text prompt for the edit was: "Add some lens flare centered on the white core of the alien creature." The new image generated by Flow is shown below in Figure 9.

Figure 9. Made by Flow from Figure 8.

Figure 8. A Whisk-generated image displayed by Google's Flow in two different ways. Also visible is the prompt ↑.

 No, I don't care if Figure 8 (below ↓) is after Figure 9 (← to the left) on this page. I wanted Figure 8 to be displayed at a large size so that the old Whisk text prompt can be seen in Figure 8.

I tried to get Flow to make a short video clip with the pink alien wrapping its tentacles around the woman....

There are two different short Flow-generated video clips in the video shown above. Those two video clips were combined with the "lens flare" still image from Figure 9 (see above on this page), all packaged with some stock audio by Apple's iMovie into a 25 second video. She says, “Let’s try to establish a synapex connection.”

Left image rejected by Flow.
Sometimes Goggle's Flow fails to generate images. Sometimes Flow claims that a reference image depicts a real world person. Sometimes Flow warns that the topic of the image is too racy for Google. In the image shown to the right, I had an AI-generated image that was made by WOMBO Dream and I tried to use that image as a reference image with Flow, but Flow claimed that the AI-generated woman was someone famous and the image was rejected. I was able to uploaded the Flow-rejected image to Gemini and have Gemini alter the face. Then I was able to upload that new Gemini-generated image to Flow. A "failed to generate" message ↓ is shown in Figure 10, below...

Figure 10. Failed image generation with Google's Flow (third panel on right).


As shown above in Figure 10, Google's Flow is unable to generate a sensible depiction of outer space. Text prompt: "A science fiction scene showing a beautiful humanoid female with long brown hair, large alien eyes and large pointed ears seated inside a futuristic and luxurious cabin of an interstellar spaceship in the far future."

According to Google's blog: "To streamline your workflow, the best capabilities from our image generation experiments — Whisk and ImageFX — are moving directly into Flow, so you can now generate, edit and animate everything in one unified workspace." With ImageFX, I never ran into an upper limit on the length of text prompts. When I asked the Google Search AI if Flow has a limit, it suggested 480 tokens, based on documentation for a different image-generating model than Nano Banana.

Figure 11. A comic book
image by Google's Flow.
Click image to enlarge.
To test Google's Flow, I tried an approximately 400 word-long text prompt (over 2,400 characters): "A page from a 1950s full color comic book introducing readers to several types of artificial life-forms in the comic titled “The Huaoshy Reality”. A billion years or so in the past, in the First Reality, the pek had arrived in Earth's galaxy and discovered that the Phari had the most advanced civilization in the galaxy. The pek tried to work with the Phari, but the Phari could not abide how the pek forced each habitable planet in the galaxy to evolve a humanoid species that was expected to transcend its biological existence and eventually reside inside the Sedron Domain as an artificial life-form. The Phari had their own on-going project of enticing biological intelligences to transcend into the Hierion Domain. Unable to successfully compete with the pek in Hadron Domain, the Phari gave up on the Hadron Domain entirely and retreated into the Hierion Domain of the universe, where they continued to live as artificial life-forms composed of femtobots. The Phari became masters of the Hierion Domain and hierion-based technologies and tried to ignore the pek. Later, when the bumpha came on the scene as the Huaoshy's second type of agent in the Hadron Domain, the Phari extended their deep distrust of the pek to the bumpha as well — viewing both as intruders in the galaxy that the Phari believed was rightfully theirs. Sometimes the Phari altered the course of events on Earth, seemingly just to annoy the pek and the bumpha.
Figure 12. A comic book
image by Google's Flow.
Click image to enlarge.
The pek are one of the two types of artificial life-forms used by the Huaoshy to help develop humanoid species; more conservative than the bumpha.
The Phari are the most ancient humanoid species from Earth’s galaxy. The Phari transcended their biological existence and now reside in the Hierion Domain as artificial life-forms. The Phari are masters of hierion-based technologies. 
The bumpha are one of the two types of artificial life-forms used by the Huaoshy to help develop humanoid species, guiding them towards transcendence into the Sedron Domain. The bumpha specialize in Interventionism, secretly altering the course of development of species like humans.
The Huaoshy are the most technologically advanced form of life in the universe. After the Time Travel War, the Huaoshy altered the Dimensional Structure of the universe so as to prevent further time travel by positronic robots. The Huaoshy never leave the Sedron Domain. The Huaoshy created the pek and the bumpha to function as their agents in the Hadron Domain
." As shown in Figures 11 and 12Flow had no problem incorporating this rather long text prompt into pages of a comic book (click on the two images to enlarge and read the test in the comic panels).

Figure 13. A comic book
image by Google's Flow
  How long is too long? For my next test of Google's Flow with an even longer text prompt I used a 1,400 word long block of text taken from the first scene (on the planet Threy) of the science fiction story "The Nanite Smuggler". This longer text prompt is shown below in blue text...

A page from a 1950s full color comic book introducing readers the characters Tyhry, Marda, Rylla, Eddy, Zeta, Manny and Systolina in the comic titled “The Planet Threy”. Entry into the Asimov Reality by using the Reality Simulation System was like walking through a narrow doorway. Tyhry and Marda, hand in hand, went through first, arriving inside a simulation of the planet Threy. Tyhry and Marda both reacted with delight when they arrived on a small hill over-looking the tourist resort. This part of Threy was located in a region of the planet with lush forests, crystal-clear lakes, and towering mountains in the distance.

Figure 14. Resort on the planet Threy.
Image generated by Google's Flow
 Next, Marda's mother, Rylla Onway, popped through the entry gate of the Simulation System and arrived on Threy. Rylla, a tall and athletic woman who had been a long distance runner for decades, took a deep breath of the Threy air, fragrant with the resins of alien trees that looked like Earthly hemlock. She reached her arms out to bask in the warm rays of Threy's sun.

Lastly, Zeta Gohrlay and her husband Eddy arrived. Eddy, the father of Tyhry, glanced around at the scenery and then told Tyhry, "I can see why you wanted to visit this world and stay at this resort. This region of the planet reminds me of Kings Canyon." It was mid-afternoon and light from the brilliant white star of Threy reflected off the glittering snow-capped peaks that rose high in the distance above a sea of green hills.

Figure 15. A hike on the planet Threy.
Image generated by Google's Flow
 The five vacationers strolled down the hillside, walking on a type of alien plant life that looked like a cross between Earthly grass and moss. The checked into the resort hotel and then they visited the swimming pool, all of them dressed in swimsuits. Rylla immediately dove into the warm water of the pool and began swimming laps. The other visitors from Earth sat at the edge of the pool. They were watching Rylla and the other swimmers while they devoted a small amount of attention to the task of making plans for their first full day on Threy.

There was much discussion of random topics and consumption of many beverages made for them by the robotic staff of the resort and served in the form of colorful frozen concoctions in tall, thin glasses.

Figure 16a. Pool on the planet Threy, version 1.
Image generated by Google's Flow.
Click on the image to enlarge it.
 Tyhry was gazing at her father's face and contemplating the droop on the skin below his jaw line. Both Zeta and Eddy were over eighty, although a combination of good genes and medical nanites made them look far younger. Still, Tyhry worried about their advanced age. Tyhry was barely listening as Eddy told one of his favorite stories about meeting a robot on the planet Triskelion named Dani. Tyhry had heard this story dozens of times and she was feeling a bit bored.

Under Zeta's guidance, the conversation kept returning to the question of what they should do the next day and what popular tourist sites were to be found on Threy. Marda was keeping particularly close eye on her mother and now she said, “Who is that robot with mom?”

Figure 16b. Pool on the planet Threy, version 2.
Image generated by Google's Flow.
Click on the image to enlarge it.
 Tyhry visually searched the rather crowded swimming pool and located Rylla who was standing at the edge of the pool and speaking to a robot. The robots were easy to spot. They were basically human in appearance, but their artificial body surface was composed a silvery metallic substance that glinted in the sunlight. Tyhry watched Rylla climb out of the pool. “She's done swimming.”

Marda noted, “She's bringing the robot over here.”

Figure 17. Systolina the robot serving drinks.
Image generated by Google's Flow.
Click on the image to enlarge it.
 Rylla had finished her laps and now joined the others sitting by the pool. She said, “This is Systolina Kayto.”

Zeta performed introductions and then Systolina asked, “You are all from Earth? We don't get many visitors from the great Home World.”

Eddy said, “We are here for fun... to celebrate the recent college graduations of Marda and Tyhry.”

Figure 18. A resort guest asking a robot
for a drink. Image generated by Google's Flow.
Click on the image to enlarge it.
 Systolina exclaimed, “How nice! I hope you will all enjoy the natural wonders of Threy.”

Rylla explained, “Systolina is a nature guide for the resort.”

Systolina added, “I'd be thrilled to serve as your guide and escort during your mis... vacation on Threy.” The robot was gazing intently at Tyhry and Systolina asked, “Is there some special place you want to visit?”

Figure 19. A resort guest learning from a robot
about a hike. Image generated by Google's Flow
 Now everyone looked at Tyhry who squirmed under their gaze. After a long awkward silence, finally she told Zeta, “I was planned to surprise you with a gift, but I'll say this... it is the next step up from those medical nanites that Manny gave you.”

Rylla told Zeta, “You do look wonderful, mom. Maybe I should ask Manny for some of her magical medical nanites... I'll turn 45 next month and I'm already getting wrinkles on my wrinkles.”

Figure 20a. Version 1: Eddy asking the two robots,
Systolina Kayto and Dyas Totus for information
about a hike. Image generated by Google's Flow
 Zeta giggled. She was quite pleased by the age-reversing effects of the medical nanites that now swarmed through the tissues of her body. Zeta was mid-eighties, but she looked like a vigorous middle-aged woman. Zeta told Rylla, “Your problem is that you just spend too much time in the sun.”

Systolina sat down at the pool-side table with the five visitors from Earth. Responding to questions,  Systolina described some of the nearby tourist hot-spots such as the Anyatal hot springs.

Figure 20b. Version 2: Eddy asking the two robots,
Systolina Kayto and Dyas Totus for information
about a hike. Image generated by Google's Flow

 
In the end, the three older visitors from Earth deferred to Tyhry and Marda since this family vacation was meant to celebrate their recent graduations. Tyhry finally suggested that they all go hiking in the mountains and start before sunup the next day so that they would have time to reach the top of Mt. Glisten. No better idea was offered and Marda gave a secret wink to Tyhry. So far, their plan was unfolding as expected.

As mind clones, Tyhry and Marda shared a telepathic connection. Now, Marda telepathically told Tyhry: No sign of Manny.

Tyhry reflected on the happy fact that someone was distracting Manny. For the past two months, Manny had been busy as a beaver, trying to round up all of those alien nanite samples. Manny took very seriously the task of controlling the availability of nanotechnology on Earth. Tyhry had seen very little of Manny during those past two months. Tyhry telepathically told Marda: All we need is one more day without Manny.

Figure 21. Marda and Tyhry with alien
nanites. Image generated by Google's Flow
 
Systolina was once again looking intently at Tyhry, the robots eyes seemingly searching through Tyhry's tangled mop of long golden hair. “Fair-skinned visitors to Threy must take special care. Our sun emits large amounts of U.V. radiation.” Systolina said to Tyhry, “You are the fairest one of all, so I'm surprised you are not using a sun screen.”

Tyhry said jokingly to Marda, “Just my luck, now I get a robot mother to nag me on my vacation.”

Zeta told her daughter, “I think you should take Systolina's advice.” She moved her arm in a sweeping arc. “This is all a simulation, but you can still get burned.”

Tyhry nodded. “Yes, mother.”

Systolina added, “I can run over to the shop and get you a tube of sun screen.”

Tyhry said, “No, robomother, please don't bother. Nobody believes it, but I can take care of myself. I use nanites to protect myself.”

Systolina seemed surprised. “I always think of Earth a bastion of conservative forces, not a high-tech world like Triskelion. What does a youngster like you, from Earth, know about nanotechnology?”

”I know plenty, granny.” Tyhry immediately regretted her snarky use of the term  'granny' to refer to the robot, but she was defensive about her age and the lack of respect that she got from her elders. “I've had training in nanite programming from Manny the bumpha.”

Figure 22a. Systolina and Tyhry with alien
nanites. Image generated by Google's Flow
 
Systolina asked, “What is a 'bumpha'?” The Reality Simulation System was programmed to automatically translate between languages for anyone using a Simulation of a past Reality. The translation worked both ways. But Systolina had never heard of the alien bumpha.

Systolina said, “Technicians from Triskelion recently obtained some antigravity nanites from the Yastyn. Now those special nanites are used in the transport pods, allowing them to hover above the ground. Tomorrow, we'll use some transport pods to carry supplies to Mt. Glisten.”

Eddy said, “Amazing. Nanite technicians from Triskelion... I had no idea...” Now Eddy was gazing intently at his daughter. Eddy imagined that he could guess why she had selected Threy for a vacation destination. It had nothing to do with the natural beauty of the planet.

Figure 22b. Systolina and Tyhry with alien
nanites. Image generated by Google's Flow

As shown above in Figure 13Flow was able to process my 1,400 word-long text prompt. I had Flow make two versions of the comic book page and the second one took about twice as long to render and had a somewhat different format (see here for a full scale version). I took some of the illustrations from that comic book page and had Flow use them as reference images for the generation of less cartoonish versions. Figure 14 (above) is view of the resort; I cropped out a 1950s era car that was on the road. Flow invented a scene with people in swimsuits walking down the hillside (see Figure 15). 

Figure 23. Reference image used for making
Figure 20. (the names were added later)
Shown above in Figure 16a and Figure 16b are two versions of a pool scene. In Figure 16b Flow gave the robot in the foreground a lot to carry. Since my text prompt included the word "exoplanet", Flow filled the sky with absurd fantasy astronomical clutter. Flow had trouble crafting sensible captions for some of the cartoon panels. The AI-generated caption text (seen here) for the panel shown in Figure 17 was, "Marda was keeping topics and colorful frozen concoctions the resort". For Figure 18, I had to make Flow edit the original image so that the blond woman was shown with a glass in her hand, asking the robot for a refill. 

I was favorable impressed by the image that is shown in Figure 19 because my text prompt included, "The robot is explaining to the woman that she can serve as a guide for a hike in the nearby mountains," and Flow generated what looks like a holographic map of the mountains.

Figure 24. Reference image used to generate Figure 21.
 Two robots are better than oneFlow spontaneously generated an image with two robots seated at the table (see Figure 23, above). Figure 20a and Figure 20b show two versions of the same scene. In Figure 20b Tyhry has seemingly wandered away, maybe to make arrangements to meet Kasty the Yastyn. For the image that is shown in Figure 21, I had Flow modify a rather generic image of two women seated at a table (see the image in Figure 24, to the right). The nanite cloud was added manually by me. As shown in Figure 22aFlow has a thing for ugly hair styles. Figure 22b is better, but it almost looks like Earth's moon there in the sky of Threy. 

Flow confusion.

Hit or Miss. Google's Flow did not reject my 1,400 word-long text prompt (over 8,000 characters), but it displayed obviously poorer performance in using that longer prompt to make a comic. For example, as seen hereFlow sometimes depicted Tyhry as a boy named 'Tuhry'. As shown in the image to the left, one panel in the comic showed Eddy saying, "I knew you'd like it, Dad!" The other comic page that was generated for the 1,400 word-long prompt 1) was rendered in half the time that was taken for the other version, 2) stayed closer to the prompt, 3) included one third as many images and 4) was significantly more coherent. I conclude that very long text prompts are risky, but so far I have not found an actual enforced upper limit for the length of prompts with Flow.

Figure 25a. Image generated by Google's Flow.
 Working with Flow to illustrate science fiction stories. I've had fun with the idea that the Phari are so technologically advanced that they can teleport entire planets over long distances. I asked Google's Flow to generate: "A photo-realistic science fiction movie still showing an exoplanet being teleported. The habitable exoplanet is shown only half re-materialized after being transported to a new star system. Half of the planet is missing and stars from the background star field are visible where the planet has not yet materialized. Some of the planet's molten interior is visible."

Figure 25b. Image generated by Google's Flow.
The Flow-generated image in Figure 25a is not horrible. I suppose Flow felt that there should be a giant space station that is "beaming the planet in" to its new location. The Flow-generated image in Figure 25b doubled down and has two spacecraft. I suppose Flow can't stand the idea of Earth without spaceships hovering nearby. 

I decided to focus my edits on the image in Figure 25b because it did not have the cloudy blue outline of the half of the planet that is still materializing.

Figure 26. Image generated by Google's Flow.
 Editing images with Flow. I suppose Flow did not believe that teleporting a planet is cool enough, so it added other features to the image that I then had to remove by editing. I asked Flow to remove the Sun, the spaceships and the nebulae from the image in Figure 25b. The new edited image is shown in Figure 26.

 Just keep editing. Next, I asked Flow to edit the image that is shown in Figure 26 so as to remove the galaxies and simply use a normal star-field in the background. Also, I asked Flow to NOT use Earth's continents, since this is an exoplanet.

Figure 27. Image generated by Google's Flow.

The next Flow-edited version of this planetary teleportation scene is shown in Figure 27. After some effort, I was fairly satisfied with the version of the scene that is shown in Figure 27. Click on the image to enlarge it.

Lava on surface?

As usual, I reached the point where I did not have the patience to keep working with Flow. In Figure 27 it looks like there are places where molten lava has escaped to the planet's surface after teleportation, but I called it quits. Minor imperfections in AI-generated images can be photoshopped faster than trying to get the AI to fix the image problems. 

I had Gemini generate a song about the demise of ImageFX and Whisk and I built the song into a six minute-long video (see below)...


Whisk early release. Click image to enlarge.

I suspect that the reason why my older Whisk-generated files were not transferred to Flow is that I was initially part of testing an "early release" of Whisk. Possible none of those "early release" images were saved by Google. Some of my older Whisk-generated images that did not get transferred to Flow can be seen on these blog pages: "Back in Time", "Back Track", "Hair Nanites", "What is Library?"

See: Whisk-generated videos on YouTube. Google Flow-generated videos on YouTube. A music video playlist on Youtube. See another music video with images that were generated by Flow.

Next: a re-evaluation of the backstory for "Battlefield Lipid".

Visit the Gallery of Movies, Book and Magazine Covers