My working notes for Tapster - Maintaining a variant copy of a text file. - Reproducing text changes from a variable file to a variant copy while maintaining a standing difference between the two. - A project including a formal specification and basic toolset. / There is little point in separating the most basic tools (at least) from the formal specification. - Both ends of a tap relation (stock and stand) must have the same form, a simple file. / Simple files only, pending a compelling use case for the inclusion of directories. That would entail the design burden of dealing with standing differences that might include deletion and renaming of paths. + Open a proposed Breccian sub-project that adds (as a valid form) a fractum. / The intercast networking project needs this in order to tap the smaller way parts. - Nested taps may be neatly handled, I believe, by depth-first processing. + Open a proposed Waybreccian sub-project that adds (as a valid form) a thoroughfractal head. / The intercast networking project needs this in order to tap endmost goals. / Not generalizing to allow tapping of other fractal heads, at present.