Folder Implementation

An obvious, but kind of heavy implementation is to gather all documentation into a manifest folder:

• tap.manifest
• .manifest
• .tap

Or something similar. It's a little hard to justify in that it's a total duplication of information already in the files, but it simplifies a variety of tasks such as:

• only updating out-of-date information
• pulling out just the info needed

Harder to handle:

• consistency with files that are changing
• updates when the env configurations change

File Implementation

All the documentation could alternatively be collected into one .yml file using yaml documents. Loading would be a bit slower but management a little cleaner. Collecting the files in one place does not avoid the hard-to-handle issues of a directory.

File as reference

The file could be a reference for data that is slower to lookup... such as which files contain tasks, some reference time, and snippits current to the reference time.