“legacy” cred kind of worked this way; something that had no “incoming” edges from elsewhere in the project would tend not to have any cred, due to the absence of a seed vector. Now, because of the seed vector, everything in the repo “owns” some cred. Doing it this way made it a lot easier to reason about time-weighted cred (things “own” less and less cred when they are old), but I still think of it as a prototype, and expect we will develop a more sophisticated and robust algorithm in the future.