Match the strength of each public claim to its evidence

What This Concept Is

A public claim should identify what was built or observed and the limits under which it holds. Evidence supports a bounded statement; it does not automatically support a broader adjective such as scalable or production-ready.

Why It Matters Here

The original portfolio audit must remove unsupported inference before polished presentation makes it harder to question.

Concrete Example

A local test sustained 100 requests/second for five minutes on one machine. State workload, version, errors, latency distribution and load-generator limits. Do not rewrite it as handles millions of users. An architecture diagram proposing three regions is not evidence that three regions were deployed.

Common Confusion / Misconception

An artifact can be authentic yet irrelevant to the claim. A screenshot without revision and experiment context is hard to reproduce. Author-generated teaching fixtures are not capstone results.

How To Use It

Create a claim ledger: exact statement, evidence path, revision, environment, observer, limits and status. Distinguish measured, implemented, modeled, proposed and pending. Redact private details without hiding material limitations.

Check Yourself

What wider claim is tempting but unsupported? Can a reviewer find the raw observation? Does the evidence belong to this revision?

Mini Drill or Application

Audit ten portfolio sentences. Narrow at least one claim and remove one unsupported assertion, retaining the before/after wording.

Read This Only If Stuck

Building Secure and Reliable Systems provides selective operational reasoning. Use the module sources below for current tool behavior; do not read a whole book before attempting the exercise.

Google code review guidance; Staff Engineer guides. Revisit the degree’s assessment and integrity rules; no new required book.