What does Context-Parametric Rule Distillation and Online Calibration conclude, in numbers, about “Resolving Conflicts Across Volumes: Do More Rules Make a Pack More Accurate?”?
Answer: Chapter 3 scans for conflicts across volumes; just 9 rules put 0.7366 of traffic in conflict, and certainty factors, when five books restate one observation, inflate the posterior to 8.19 times its correct value, so evidence must be deduplicated by observation.
Scope of the numbers: Parameters are illustrative and all calculations are generated by the book's programs. This is general business analysis, not investment, legal or medical advice, and it describes no real customer or sale.
Data table
The numbers below are printed verbatim by the chapter's Python program and can be reproduced by running it. standard-library Python onlyprinted values that match the answer: 0.7366
| rules 9 from 5 books, cells 72 | |
| traffic covered 0.9809 overlapped 0.8425 in conflict 0.7366 | |
| conflicting pairs 20 (traffic share of overlap): | |
| R02 vs R08 | 0.2450 |
| R04 vs R05 | 0.2250 |
| R01 vs R04 | 0.1750 |
| R01 vs R05 | 0.1575 |
| R05 vs R09 | 0.1350 |
| R01 vs R08 | 0.1225 |
| R02 vs R04 | 0.1225 |
| R01 vs R09 | 0.1050 |
| resolution route (traffic share): | |
| specific | 0.5694 |
| weight | 0.3261 |
| tie-red | 0.0853 |
| default | 0.0191 |
| resolved pack agrees with the table on 0.8177 of traffic | |
Show the full program
# Chapter 3. p31: conflict scan over a pack of rules from five books.
# Each rule fixes some attributes of the condition vector (the rest are
# wildcards) and names a parameter bundle; w is its evidence weight.
# We enumerate the 72 cells of p21, measure coverage, overlap and
# conflict (same cell, different conclusions), list conflicting pairs,
# resolve by specificity then weight, and score the result against the
# illustrative table of p21. Rules, books and weights are illustrative.
import itertools
import math
ATTRS = [("tier", ("low", "mid", "high"), (0.50, 0.35, 0.15)),
("src", ("search", "social", "direct"), (0.45, 0.35, 0.20)),
("dev", ("mobile", "desktop"), (0.70, 0.30)),
("visit", ("first", "return"), (0.65, 0.35)),
("slot", ("day", "night"), (0.60, 0.40))]
IDX = {a[0]: i for i, a in enumerate(ATTRS)}
RULES = [("R01", "V1", {"visit": "return"}, "B", 3),
("R02", "V1", {"src": "social", "dev": "mobile"}, "B", 2),
("R03", "V2", {"tier": "high"}, "D", 2),
("R04", "V2", {"tier": "low"}, "S", 1),
("R05", "V3", {"src": "search"}, "D", 2),
("R06", "V3", {"src": "direct", "slot": "night"}, "D", 1),
("R07", "V4", {"tier": "high", "visit": "return"}, "S", 2),
("R08", "V4", {"src": "social"}, "S", 1),
("R09", "V5", {"dev": "desktop"}, "S", 1)]
def label(c):
tier, src, dev, visit, slot = c
if visit == "return":
return "S" if tier == "high" else "B"
if src == "social":
return "B" if dev == "mobile" else "S"
if src == "search":
return "S" if tier == "low" else "D"
return "D" if (slot == "night" and tier != "low") else "S"
def weight(c):
w = 1.0
for (_, vals, ws), v in zip(ATTRS, c):
w *= ws[vals.index(v)]
return w
def fires(rule, c):
return all(c[IDX[k]] == v for k, v in rule[2].items())
def resolve(hits):
if not hits:
return "S", "default"
top = max(len(r[2]) for r in hits)
best = [r for r in hits if len(r[2]) == top]
if len({r[3] for r in best}) == 1:
return best[0][3], "specific"
wt = {}
for r in best:
wt[r[3]] = wt.get(r[3], 0) + r[4]
order = sorted(wt.items(), key=lambda kv: (-kv[1], kv[0]))
if len(order) > 1 and order[0][1] == order[1][1]:
return "S", "tie-red"
return order[0][0], "weight"
def main():
cells = list(itertools.product(*[a[1] for a in ATTRS]))
cov, over, conf, right = [], [], [], []
how = {}
pairs = {}
for c in cells:
w = weight(c)
hits = [r for r in RULES if fires(r, c)]
if hits:
cov.append(w)
if len(hits) > 1:
over.append(w)
if len({r[3] for r in hits}) > 1:
conf.append(w)
for r1, r2 in itertools.combinations(hits, 2):
if r1[3] != r2[3]:
key = (r1[0], r2[0])
pairs.setdefault(key, []).append(w)
out, why = resolve(hits)
how.setdefault(why, []).append(w)
if out == label(c):
right.append(w)
print("rules {} from 5 books, cells 72".format(len(RULES)))
print("traffic covered {:.4f} overlapped {:.4f} in conflict {:.4f}"
.format(math.fsum(cov), math.fsum(over), math.fsum(conf)))
pairs = {k: math.fsum(v) for k, v in pairs.items()}
how = {k: math.fsum(v) for k, v in how.items()}
print("conflicting pairs {} (traffic share of overlap):".format(
len(pairs)))
for k in sorted(pairs, key=lambda k: (-pairs[k], k))[:8]:
print(" {} vs {} {:.4f}".format(k[0], k[1], pairs[k]))
print("resolution route (traffic share):")
for k in ("specific", "weight", "tie-red", "default"):
print(" {:<9} {:.4f}".format(k, how.get(k, 0.0)))
print("resolved pack agrees with the table on {:.4f} of traffic"
.format(math.fsum(right)))
if __name__ == "__main__":
main()Single source and citation
Fan, Y. (2026). Next-Generation Knowledge Distillation, Context-Parametric Compilation and Live-Conversion Feedback Calibration (Version 1.0.0), Chapter 3: Resolving Conflicts Across Volumes: Do More Rules Make a Pack More Accurate?. 5D Library. DOI pending
DOI pending · monograph page goes live after publication · 5DL-B-377 · v1.0.0 · CC-BY-NC-ND-4.0
BibTeX
@book{fan2026377,
author = {Fan, Yafu},
title = {Next-Generation Knowledge Distillation, Context-Parametric Compilation and Live-Conversion Feedback Calibration},
year = {2026},
publisher = {5D Library},
edition = {1.0.0},
note = {DOI pending}
}Other chapter answers in this book
- Chapter 1 · Simpson's Reversal: Why a Rule Without Its Context Can Point the Wrong Way
- Chapter 2 · Context-Parametric Compilation: Squeezing a Decision Table into Decision Lists and Ordered Decision Diagrams
- Chapter 4 · Online Bayesian Calibration: Giving Every Rule a Beta Distribution That Grows
- Chapter 5 · Threshold Drift: Discounted Beta Updates, Sliding Windows and a Cumulative-Sum Alarm
- Chapter 6 · Calibration and the Whole Pipeline: the Brier Partition, Binned Calibration Error and a Net-Benefit Simulation
- Chapter 7 · Classical Sources: Wheelwright Bian and Aristotle on Equity
- Chapter 8 · Closing the Loop: Field Tools and Checker Specifications, the Risk Ledger and a Pre-registered Test