Using Cauldron

• Given the limits to repo sizes, \(5\) GB for GitHub and \(10\) GB for GitLab, having Cauldron as a single source for all my notes may not be practically feasible in the long run.

• Cauldron can continue to serve as a point of entry for all notes. - Even if a note fits a very specific project perfectly, let its development happen in Cauldron. The Cauldron is home until a note grows up. Once it is ready to stand on its own, it should find a new home, preferably an existing cluster (refer to the note below).

• When a collection of notes matures and the notes coalesce into a cluster, that is time to give the cluster its separate home.

• Once a note is ready to move out of Cauldron, it should leave its address behind so that there is one big index for all notes that have ever been written. This would also help in easy tracking of notes.

• Only published notes can be duplicated. Duplicating notes that are in draft or review mode will propagate errors in the existing note.

• Published notes can be duplicated and moved to different places. Alternatively, a published note can be repurposed to fit better in a different context.

• The primary audience for the notes is my future self.