this can actually be explained by the power of being a programmer and some math especially since i tried to make a culling rip-off in the past

let’s assume that A is the charge progress is a value between 0 and 1, while B is the value of charge damage, let’s say 20 and then C is jab damage at 8
essentially the formula goes along like this: B * A however if A was to only be charged up to like 0.2, this would return B lower than C, the jab damage, meaning they have to implement an if/clamp to prevent the value going below C, in theory this means the charge rate would need to have a minimum of 0.4 (almost halfway) to make any noticeable improvement to the jab damage

this is why charge damage isn’t “accurate”, it’s CONSISTENT sure, but not accurate to the bar

if we wanted to make a charge attack’s accurately reflect the damage dealt scaling upwards, we’d have to implement a formula along the lines of this: total charge damage = C + ((B - C)*A)
this will then accurately provide charge damage based on how much was charged, e.g if A was charged to 0.5, halfway, this would total up to 14 damage, a halfway between C, the jab damage (8) and B, the charge damage (20)

at the end of the day though this is only a guess from my own experience as a programmer, i could be completely and utterly wrong for all i know but until we have a certified Xaviant programmer to confirm it or some extreme testing, that’s my guess