some other method to instantly sort or display domains differently. Ideally, it would have a thumbnail of the landing page of the site and a thumbnail of the landing page of this sales letter. There should be a function that allows the automatic generation, or, let's put it this way, the checking to ensure that a thumbnail has been created from the most recent version of the site generated. Each thumbnail created from a given version of a site should be incremented in a versioned document with a number and a date, like chain of custody level metadata, like a journal, a file save log journal.

It's okay; it's not going to get that big. I've only got about 250 domains that we're going to be processing initially. We'll gather data from what we've been doing and how well it's worked, and then we will use that to build or modify our approach. For now, we're not worried about the size of the database. Even if we have 10 versions of each site, it's still only 2,500 versions. Even if they were 50 MB apiece, let's say it was 100 MB apiece. 100 times 250 is 25 GB. That's 100 MB times 10 sites, which would be 1 GB times 100 sites, which is 10 GB. It would be 20 GB.

We're still talking about under 25 GB of space, even if we had 100 MB per domain that we're developing, at 250 domains. Is that math correct? If it is, then we really don't care about storage requirements. It's more important that we are making sure we are storing it. Storage is cheap and can refer to it, and once we store it we make sure we don't have to restore it unnecessarily. There are the criteria: when we hear it for the first time or have to process it the first time, we store it, because if it's data related to what we're doing in our platform, based on processes and algorithms that we've written to solve our problems, then it's going to be important and relevant data. Data coming in, we store it, we classify it, we understand it, we contextually understand its relevance in the active project or in the overall scope of things.