User created templates
Template [noun]: initial storage state for freshly created timestreams. Root templates are lightly modified LXC templates from distributions like Ubuntu. A template may be based upon a parent template (so long as there is eventually a root template). Root templates are provided by the Chronostruct system, but users shall be able to create their own by "quiescing" a moment. Templates may be deprecated by a newer template.
Need to finalize the template namespacing behavior. Current templates are namedspaced under a username, followed by a template name. I think it makes sense to add a third layer underneath: date/revision of template. This would allow a user to have a template that is succeeded with multiple revisions through time, but has the same common name.
Some distributions also impose restrictions on redistribution of derivative works. Ubuntu, in particular, has problematic language in the license agreements. Even root-provided system templates may need to be carefully built as a Chronostruct layer on top of an utterly stock Ubuntu LXC image. These stock/unmodified images could be reified as immediately deprecated templates succeeded by the respective "Ubunthree" Chronostruct augmented templates.
The workflow for quiescing moments also requires some consideration, like common cleanup steps, and validation that the newly generated template actually functions as the genesis for new timestreams (i.e. chronitond based SSH is still operable).