The Developers on a home-robot company's firmware team privately track which safety tests they skipped under deadline pressure, without recording it anywhere the Product Owner or stakeholders can see. Which pillar of empiricism does this behavior undermine?

Transparency requires that significant aspects of the process be visible to those responsible for the outcome, and that what is visible be commonly understood and shared with the same standard of definition — often reflected through something like a Definition of Done. Privately tracked skipped safety tests are the definition of a hidden significant aspect: the Product Owner and stakeholders believe the work meets one bar when it actually meets another, which breaks the shared understanding transparency depends on. Inspection is a separate pillar concerned with how frequently and attentively artifacts and progress are examined; the problem here isn't a missed inspection cadence, it's that inspection would find nothing wrong even if performed, because the information is concealed. Adaptation is the pillar about acting on what inspection reveals — it can't even begin until the gap is visible, so naming adaptation as the failure skips over the actual root cause. Forecasting is not one of the three empirical pillars at all; the Scrum Guide names only transparency, inspection, and adaptation, and treats specific forecasting techniques as outside its prescriptions. A concrete check: ask whether the Definition of Done for firmware work explicitly includes the safety tests in question — if it does and the team still isn't reporting against it honestly, that is a transparency failure to surface immediately, not a minor technicality.