lesson 3 of 6 · retraining triggers and human reviewlesson 3 of 6 · retraining triggers and human reviewlesson 3 of 6 · retraining triggers and human reviewlesson 3 of 6 · retraining triggers and human reviewlesson 3 of 6 · retraining triggers and human reviewlesson 3 of 6 · retraining triggers and human reviewlesson 3 of 6 · retraining triggers and human reviewlesson 3 of 6 · retraining triggers and human reviewlesson 3 of 6 · retraining triggers and human reviewlesson 3 of 6 · retraining triggers and human reviewlesson 3 of 6 · retraining triggers and human review
Checkpoint
One last thing before we move on. pass this to mark the lesson done, or skip and keep moving. hop to the next when you're ready.
Run the full policy over a month. The POLICY dict carries thresholds WITH owner and date — print its header line first: f"policy: {d}d schedule, {floor} floor (owner {o}, set {date})". Then decide() per week: the upstream-bug veto returns "VETO - fix data, no retrain"; otherwise collect schedule/drift/outcome reasons into "RETRAIN a+b" or "hold". Print f"{name}: {decision}" for W1-W4. Note W2: drifted AND bugged — the veto wins.