No, I get that. I was just asking because looking at Taku Temple for example. You reduced it from 5 laps to 3 laps when you added the track, but it was before you had tested it yet, it was still marked as "income". I have tested the track and each lap took about 15 seconds for me on 150cc, which is a total of 45 seconds. Having it at 5 laps would make it a total of 75, still fitting within the 100 second rule.
Even beyond that, personally I'm against changing the lap count and not leaving a reference of what it used to be. As time passes and tracks get their original download links removed, people (including myself) often come to your archive to replace the download links. By changing the lap count and not including the original anywhere, you can create an issue where the replaced download doesn't match what the original file contained and what the author intended the lap count to be.
Personally, I would include the original lap count first and then if a change is required to fit the 100 second rule, I'd include that as a separate entry, marked as "norm" like what was originally done when the archive was created.
Especially considering you said that exceptions are alternate lap counts used in distributions, and if an originally 5 lap track is reduced to 3 lap, and the 5 lap version is a SHA1 alias, in the distribution tab it'll still show up as 3 laps because that's what the entry shows, which creates an inconsistency.
Even beyond that, personally I'm against changing the lap count and not leaving a reference of what it used to be. As time passes and tracks get their original download links removed, people (including myself) often come to your archive to replace the download links. By changing the lap count and not including the original anywhere, you can create an issue where the replaced download doesn't match what the original file contained and what the author intended the lap count to be.
Personally, I would include the original lap count first and then if a change is required to fit the 100 second rule, I'd include that as a separate entry, marked as "norm" like what was originally done when the archive was created.
Especially considering you said that exceptions are alternate lap counts used in distributions, and if an originally 5 lap track is reduced to 3 lap, and the 5 lap version is a SHA1 alias, in the distribution tab it'll still show up as 3 laps because that's what the entry shows, which creates an inconsistency.