Chapter 1 · Frame and baseline

Trees as learned decision rules

Use trees as learned decision rules to move the trees & boosting production brief toward a defensible release.

65–90 min4 key conceptsReviewed 26 Aug 2026
01 · Production proposition

A marketplace must catch rare fraud without blocking trustworthy sellers.

This lesson isolates trees as learned decision rules as one decision inside that system. The people affected are product users and operators; the learning data must carry event time, availability time, ownership, and version; and the operating envelope is reviewer capacity plus false-decline cost.

Decision

Choose whether and how to use impurity gain at a declared prediction cutoff.

Metric

Measure decision utility alongside calibration, slice reliability, and system latency—not model score alone.

Failure consequence

A marketplace must catch rare fraud without blocking trustworthy sellers. An unsafe release must degrade to a named baseline or the last known-good version.

02 · Intuition & prerequisites

Build the mental model before the machinery.

The core move is to treat trees as learned decision rules as a contract between data, a computation, and an action. Version missing-value behavior and model format; monitor calibration, explanations, latency, and reviewer yield. The implementation becomes easier to debug once you can state which inputs exist, which state is learned, what output means, and what must remain invariant after serialization.

01

impurity gain

Define it in a hand-checkable form and name the prediction-time inputs.

02

bagging

Connect it to the production metric and identify what it cannot guarantee.

03

feature subsampling

Stress it with a slice, a temporal boundary, and a failure-safe alternative.

04

pseudo-residuals

Stress it with a slice, a temporal boundary, and a failure-safe alternative.

Bring forward

Classical baselines

03 · Formal treatment

Name every symbol. Check every shape.

Stage-wise boosting update is the central invariant for this lesson. The formula is useful only when its inputs match the production cutoff and its output maps to an action.

Formal treatment
Fm(x)=Fm1(x)+ηhm(x)F_m(x) = F_{m-1}(x) + \eta h_m(x)

Stage-wise boosting update

Symbol, shape or unit contract
SymbolMeaning / shape / unit
F_mensemble after stage m
h_mnew weak learner
ηlearning rate
Open derivation and numerical substitution

Start from the production quantity being optimized, substitute the observed values with their declared units, then isolate the model-controlled term. Preserve shape annotations at each step so broadcasting or aggregation cannot silently change the result.

  1. Write the named inputs: F_m, h_m, η.
  2. Substitute one small, hand-checkable batch before vectorizing.
  3. Calculate an independent reference value and compare within a declared tolerance.
# equation → code contract
inputs = validate_shapes_and_units(batch)
value = compute_c05(inputs)
assert is_finite(value)
04 · Three views of the idea

Calculate it small. Shape it realistically. Break it on purpose.

HAND-CALCULATED TOY

A result you can reproduce on paper

One stump fits the mean; the next stump learns the remaining residual pattern.

  1. Write every input and unit.
  2. Substitute values into the stage-wise boosting update equation above.
  3. Compare the result to one simple baseline and explain the direction of the difference.
PRODUCTION-SHAPED

The same reasoning under real constraints

Detect rare seller fraud with temporal validation, reviewer capacity, calibration, and reason codes.

The production record includes the data snapshot, transformation state, artifact identity, cutoff, score, decision, and the version of the policy that consumed it.

FAILURE / COUNTEREXAMPLE

The attractive result you should reject

High-cardinality IDs and random row splitting produce spectacular leakage that XGBoost exploits.

Diagnostic: replay the smallest failing slice from immutable inputs, then compare each boundary rather than retuning the model.

05 · Deterministic lab

Change one assumption and make the tradeoff visible.

This lab runs predefined TypeScript only. It never executes learner code. Use the slider, numeric input, reset, live text, or table—the computation is the same.

Estimate

Tree capacity lab

Grow depth and compare training fit with estimated temporal generalization.

levels
Primary69.4%
Secondary73.0%
DiagnosisControlled

Assumption: Estimate calibrated to a small, imbalanced synthetic tabular dataset.

Open nonvisual data table
ItemComputed stateInterpretation
fold 170.3%stable
fold 269.6%stable
fold 368.9%stable
fold 468.2%stable
fold 567.5%stable
06 · Production implications

Trace the complete operating path.

  1. 01

    Validate and version impurity gain.

  2. 02

    Compute trees as learned decision rules from prediction-time-safe inputs.

  3. 03

    Persist model, feature, and configuration identities together.

  4. 04

    Serve or materialize behind explicit reviewer capacity plus false-decline cost.

  5. 05

    Join telemetry to mature outcomes and retain a rollback path.

Observability

Join service health, input quality, prediction distributions, slice behavior, and mature outcomes by exact version.

Cost

Measure storage, preprocessing, compute, queueing, and human review under a representative arrival pattern.

Failure modes

High-cardinality IDs and random row splitting produce spectacular leakage that XGBoost exploits. Add a detector, owner, mitigation, and stop condition for this class of failure.

Alternatives

Compare a rule, a simpler statistical baseline, and a different system boundary before adding model complexity.

07 · Check understanding

Explain the contract, not just the vocabulary.

Browser-graded checkpointPass ≥ 80%
01What does bagging mainly reduce?
02What does each boosting learner target?
03Does SHAP prove causality?
08 · Apply in production

Rare-fraud ensemble decision system

Compare a tree, forest, gradient boosting, and XGBoost with temporal validation and operational thresholding.

  • Ensemble ablations
  • Cost and capacity analysis
  • Calibration and explanations
  • Latency/fallback plan
Open assignment and rubric
09 · Sources & next depth

Read primary material with a purpose.

10 · Production resolution

Return to the opening failure.

Version missing-value behavior and model format; monitor calibration, explanations, latency, and reviewer yield.

For this lesson, the release evidence is a hand-checked formal result, deterministic simulation output, a ≥80% checkpoint, the production rubric, and a named fallback. The course resolves when the system can produce calibrated random-forest and xgboost baselines with cost-sensitive thresholds.