pub const CHARGE_SCALE: i64 = 100;Expand description
Fixed-point scale of every bridge charge: charges are stored in HUNDREDTHS of a unit and read back floored to whole units.
Why the accumulator is fractional (post-merge plan §8). Resonance is a small
integer 1..5 — eleven of the twenty-four laws sit at 2 — and the right-column
artifact stones state their effect as a percentage of it (VL-01 +50%,
BL-05 +25%). +25% of 2 is 2.5, so rounding at every fire would decide
the stone instead of the design: rounding down makes it do nothing, rounding
up reaches a capacity-10 bridge in four fires instead of five and turns
+25% into +50%. Keeping the exact value and flooring only at READ time
makes two fires of 2.5 worth 5 and one fire worth 2 — the remainder is not
lost, it just does not count until it completes a unit.
Integer hundredths rather than f64: this state lives between ticks on a
deterministic server, and floating point would accumulate divergence.
A fractional remainder alive at a flip is DELIVERED with the rest of the charge and then floored by the reader, so half a unit simply never counts — the same rule as “charge above capacity burns”.