noodle x tar

Thoughts on how noodle relates to tar balls.

I need to understand a number of concepts and how they work together:

The bubble command.
Nested noodle working directories.
tar balls. But I want to emphasize the intersection/interaction/combination of noodle and tar balls here.

So one way of thinking about it might be to just see the tar ball as a regular file. This is the current behaviour. But of course, we want noodle to be a convenient interoperability layer. So, much like how we’re friendly to the filesystem and text files, maybe we can expand that friendliness to tar balls. They’re a natural member of this sort of table of computing elements.

This concept of synthesize and atomize I think should be available in noodle for text files. Sort of translating between text and noodle structure should be natural. I’m still not sure exactly how we should go about this. ffs and semi-structured formats like json and yaml seam to be a good starting point. Of course I want to be able to do “basic” text as well.

Let’s make an example:

The Sci-Fi to Fantasy Gradient
==============================

I'm going to place a bunch of works in media on a gradient from science fiction to fantasy.

Foundation
----------
Books by Asimov about psychohistory.
All-in-all, it's a showcase of a naturalist-physicalist view of reality.

Star Trek
---------
A humanistic vision of the future where humans form the core of a federation of planets.
Very United-Nations-y or something.
Now that I think about, this is more unrealistic than anything on the list.

Star Wars
---------
A long time ago in a galaxy far away...
An american dude finds out he's a wizard and get's a' R2D2.

Harry Potter
------------
A british dude finds out he's a wizard and gets a' owl.

Lord of the Rings
-----------------
A re-integration of folklore mythology into a culture that's losing touch with christianity.
So they get Frodo and Eru Illuvitar instead basically.

Suppose I ran that through an atomize command, or created a self-managed layer. I would want the following structure to be generated:

/path/to/working/directory
origin
  Foundation
    Star_Trek
      Star_Wars
        Harry_Potter
          Lord_of_the_Rings
layermask: >>[The_Sci-Fi_to_Fantasy_Gradient]<<
<noodle>

Each doodle would have the respective blurb as the file content title inclusive. Notice the original file was removed. I’d like to have the option of keeping the original file which would correspond to a self-managed layer, and the option of removing the original file to sort of rip the file structure into noodle.

That kind of dynamic of synthesize/compile and atomize/rip should be present for tar files too. Like maybe I should be able to pull the structure in.