Lineage Equation: operator instrument
by Fudoshin Research·2026-08-20·S3·F-2026-08-20-G
The official law now has a usable instrument: one telemetry window in, a card out (Q, u, Q_eff, zone, bottleneck). Additive Q_eff is retired as the published budget.
Problem under load
A law you cannot run on a log line is not an instrument. The official additive budget Q minus unit penalties barely moves Q when Q is order 50. That is a units error dressed as a free-energy term.
Primitive / definition
Operational card: Q from the official identity, u = clip(1 - 0.25 H - 0.25 E-hat - 0.25 D), Q_eff = u Q, zone from u, bottleneck = argmax tau. rest_share and transport_share split Q^2. Extra log fields are ignored. Zero or negative latency fails closed.
Method / protocol
lineage_use_v2.py evaluates one JSON window, compares two, previews cutting the slowest pipe by N ms, and batches JSONL. The law Q^2 = Pi-tilde^2 + M-tilde^2 is unchanged. Additive effective_capacity remains in the module as historical writing only.
Result
Pinned loaded-but-coherent example, official weights: Q = 50.176, u = 0.840, Q_eff = 42.134, zone = steady, bottleneck = retrieval 120 ms. A 20 ms cut on retrieval raises Q to 72.187. That is the r^2 rest term working, not a dashboard bug. 17 instrument checks pass.
Limitations and next
Stage C. Not Stage F. A green zone is not a live prediction. What-if is a first-order preview, not a causal experiment. Official weights are not claimed true for every machine. A card is not a loop; the wait-closed loop is recorded separately.