LIST Interesting Applications

LIST and its reference implementation LFW have interesting applications beyond document and knowledge management. We briefly describe one such application which we were able to achieve surprisingly easily – ensuring file provenance in git.

git_lfw: Ensuring File Provenance in Git

A common friction point for developers during large-scale refactoring is the loss of file history. In standard version control systems like Git, renaming or moving a file is often interpreted as a deletion of the old object and the creation of a new one. While Git attempts to detect renames heuristically, these links are frequently broken, severing the chain of provenance.

We addressed this by developing `git_lfw`, a middleware that leverages the LIST specification to make file identity independent of the filesystem path. In this implementation, Git does not track the user’s visible hierarchical structure; instead, it tracks a hidden .lfw directory containing the immutably identified files (UUIDs) and their associated metadata.

The git_lfw middleware acts as a translation layer, projecting this flat, immutable store into the hierarchical view the developer expects. Because Git is tracking the immutable IDs rather than mutable paths, the modification history remains perfectly intact regardless of how the user renames or reorganizes the files in the virtual hierarchy. This effectively transforms file provenance from a heuristic guess into a structural guarantee.

A video demonstration of git_lfw in action is here: