Confidence must rise as the target date nears - slide the date early rather than carry a 60 percent to the wire

Situation

Reviewing Justin Haynes automated-repo-testing item on the NGD board, Peter ruled that a low confidence number a few days from a target date is itself the failure. His instruction: this close to the end of the week we need to be communicating to the company, through those two numbers, whether they are getting something - so a few days from the end I do not want to see a 60 percent confidence number, what I want to see a few days ago is that date sliding out now so that we are communicating a higher confidence number when we are this close to a target date. He grounded it in consumer value: the company cannot do anything with 60 percent confidence July 31st, they cannot take attention on that. Immediately afterwards, when Duane Carson acknowledged a cross-team miss on the 10-2 bits, Peter drew the complementary line - I do not mind misses as long as the team recognizes, hey, we have a miss here, and here is how we are going to get better.

Reasoning

Confidence and target date are a single joint signal to go-to-market, not two independent status fields, so a truthful-but-useless pairing still fails the boards only purpose. Peter would rather have an honest later date than a hopeful near one: moving the date early is a cheap, legible act, while holding a low confidence to the wire is precisely what leaves the company unable to plan. He raised it against Justins item specifically because Justin had correctly reported low confidence - so the correction was aimed at the practice, not the honesty. Pairing it with the response to Duane makes the standard clear in both directions: misses are acceptable when named and learned from, unactionable signals are not.

Additional Context

Extends the 5/21 Jira confidence-as-contract doctrine and the 7/28 re-ruling that confidence number plus engineering target delivery date are the only two mandatory NGD fields. The 7/29 TPS report shows the failure mode live - the Nvidia DGX Spark demo slipped 14 days from Jul 24 to Aug 7 with no confidence update, and Justins top three items all sit between 52 and 75 percent. Peter noted separately that the item under discussion probably should not have been on NGD at all, since it was internal quality work rather than go-to-market work.

Observed Evidence

Direct verbatim ruling in the Fathom transcript of the 7/28 Engineering Weekly, delivered against a specific live board item, plus the paired response to Duane Carson establishing that named misses are acceptable.

Confidence Breakdown

Reasoning Depth Analysis