The information already exists, in a form that is usable - all that is required is a link to it. The database also doubles as a metadata journalling system for the filesystem, making it unnecessary to have distinct, single-function journalling or a filesystem checker. Filesystem consistancy is inherently being checked, for every operation performed, along with any impact it may have. Interface As described above, no interface is envisaged, except possibly for the creation of rule files. No other human intervention should be required at all.
All communication is done via the database.
The Database Record Update is managed via events from the filesystem core. Everything else polls the database, to see if any relevent information has changed. Database Record Update obtains the new file information, and pushes it to the database. If a new file, Dependency Path Mapping will poll a change, and obtain the new file information. It will then check the file for all findable dependencies, and create a new mapping.