# Readiness (/docs/concepts/readiness) Readiness summarizes what the current verified evidence says about your product. It is a decision aid, not a release score that hides missing data. ## Core measures [#core-measures] | Measure | Meaning | | ------------------------- | ------------------------------------------------------------------------ | | Safe outcomes | Verified outcomes that completed safely out of measured outcomes | | Known blockers | Unresolved findings or conditions that block the readiness decision | | Required journey coverage | Required journeys with approved, verified coverage out of the target set | ## Readiness states [#readiness-states] * **Ready** means the required evidence, coverage, and safety conditions are satisfied. * **Needs attention** means a known problem, coverage gap, or stale result requires review. * **Not ready** means a required condition failed or cannot be verified. The page explains the condition behind the state and links to the next useful action. ## Freshness [#freshness] Readiness is tied to evidence time. A previous pass may become stale after a product, action, agent, or journey change. When the page marks evidence as stale, rerun the affected journey before using the old result for a current decision. ## Coverage gaps [#coverage-gaps] A coverage gap means a required journey or test condition lacks current, verified evidence. Missing coverage is not a pass and does not improve the readiness percentage. ## History [#history] The history chart updates when a verified run changes the measured outcome set. Use it to spot improvement, regression, and changes in measured coverage. Open the underlying findings and test results before acting on a trend. See [Review results](/docs/guides/review-results) and [Statuses and outcomes](/docs/reference/statuses-and-outcomes).