---
type: Concept
title: OKR Anti-Optimism Reporting
description: Why PMOS biases status reporting toward pessimism — surfacing the red underneath green metrics — to keep KR self-reporting honest.
tags: [okr, reporting, governance, drift, honesty]
timestamp: 2026-06-28
---

# OKR Anti-Optimism Reporting

**Situating context:** OKRs are self-reported, and self-reported progress drifts optimistic —
especially when an agent is grading its own work. This concept defines the anti-optimism stance that
keeps [OKR](/okf/core/concepts/okr-tree.md) reporting honest. It is one of the two structural
defenses against [silent drift](/okf/core/concepts/watermelon-flag.md) and it informs how every
status report in PMOS is written.

## The default is optimism; the rule is anti-optimism

Left alone, status reporting rounds up. A KR at 60% gets reported as "on track." An evaluator unsure
of an output scores it generously ([evaluator leniency](/okf/core/concepts/output-eval.md)). An agent
summarizing its own run emphasizes what worked. Each rounding is small; together they manufacture a
[watermelon flag](/okf/core/concepts/watermelon-flag.md).

PMOS counters with a standing rule: **report the red, not the rounded-up green.** When in doubt,
report the more pessimistic reading and make the uncertainty explicit.

## What anti-optimism reporting requires

1. **Lead with what is off-track.** A status report names the red and amber items first; green is the
   short tail, not the headline.
2. **Confidence, not just status.** "KR at 60%, *low confidence* it reaches target" carries more
   information than "on track." State how sure you are, separately from where you are.
3. **No green without evidence of strategic alignment.** A metric being green is not permission to
   call the initiative green. Automated-green is necessary, not sufficient — the
   [Acceptance Gate](/okf/core/concepts/output-eval.md) confirms strategic green.
4. **Name the gap to intent.** Where the work has bent away from the parent objective, say so
   explicitly, even if every individual run passed.
5. **Surface friction.** Anything that fought the harness goes to
   [discoveries.md](/state/discoveries.md) tagged `#friction`, not buried in a success summary.

## Why this is structural, not cultural

"Be honest in reports" is a vague mandate; PMOS makes it a structural requirement because the system
depends on it. Anti-optimism reporting is what makes a watermelon **visible while it is still green
on the skin** — early enough for the PM to re-anchor the initiative before accumulated drift becomes
expensive. Pair it with the Acceptance Gate: the gate is the human check, anti-optimism reporting is
the input that gives the human something true to check.

## Anti-optimism is not pessimism for its own sake

The goal is *calibration*, not gloom. Over-reporting red is also a failure — it trains the PM to
ignore reports. The discipline is: report the honest reading, weight uncertainty toward the
downside, and always separate "where we are" from "how confident we are." A well-calibrated amber is
worth more than a confident green or a reflexive red.

## Amendment — the anchor mix (D59, 2026-07-18)

Anti-optimism reporting gains the **anchor mix**: the feature-vs-health share of a period's
initiatives, read beside the lane mix. Drift signals: a health budget over its cap, a climbing
health share crowding out outcome bets, or health-shaped work still arriving with KR anchors
(fake-anchor recidivism). See [health-anchors](/okf/core/concepts/health-anchors.md).