01 Reference
Status vocabulary
Read qualified, blocked, stale, unknown and not-applicable without widening the claim.
Read the state with its scope
A qualification state is useful only when you can identify the boundary, required checks and evidence behind it. “Qualified” is a shortened reading of the technical state qualified-for-scope. It never means every asset, future refresh or business interpretation is correct.
| State | Read it as |
|---|---|
| Qualified | Declared required checks passed on current evidence for this scope. |
| Blocked | A current failure, refusal or failed check prevents qualification. |
| Stale | Evidence no longer matches an observed dependency or binding. |
| Unknown | Qualification has not been established. |
| Not-applicable | An evidence-backed admission enters downstream. This upstream boundary was not proved. |
Always include the scope when sharing a result. For example, describe the declared Sales checks for a selected observation rather than announcing that the entire analytics estate is qualified. Explain exclusions close to the state so a reader does not have to reconstruct them from a separate technical archive.
Read each of the eight boundaries
The local view reports Source, Meaning, Bronze, Silver, Gold, Semantic, Report and Release. They describe different responsibilities. A Gold result does not automatically qualify the semantic query or rendered report. A layout check does not establish a source comparison.
Existing-asset admission can allow entry at a later boundary. Not-applicable makes the unproved upstream portion explicit; it is not a green pass for work the project did not observe. Admission requires current evidence for its declared asset and scope. Newer semantic and report entry routes remain subject to their own preview and proof limits.
Keep missing evidence and local tests visible
Technical views also use not-run when evidence is absent or incomplete. Unknown can describe evidence without a frozen catalogue or another state where qualification has not been established. Neither is a reassuring substitute for a missing check.
Local-pass is reserved for local-only proof. Offline grading, fixture modelling and regression tests can establish that their comparator or refusal behaved correctly. They do not establish a live tenant result. The offline Sales exercise deliberately demonstrates that distinction.
Let retries and changed bindings update the result
Observed changes can make dependent receipts stale. That relationship propagates through the chain, so a downstream pass cannot remain current while its required upstream evidence no longer matches. The local ledger does not continuously poll every remote dependency; changes have to be observed and recorded.
The newest failed retry supersedes an older success. Investigate the current reason rather than selecting the most favourable entry in the timeline. Requalification needs new observations through the owning workflow. Changing an export date or copying an old receipt does not restore freshness.
Do not confuse proof state with product availability
Shipped, preview and planned describe capabilities, not the result of your project. Shipped means an implementation exists in the checked-out sources. Preview identifies material release, composition or live-proof limits. Planned identifies a proposed or owner-gated offering.
A shipped verifier can correctly report blocked. A preview route can have a narrowly observed pass without becoming generally available. Hosted remains a protected preview, and proposed courses or credentials do not become operational services because a software test passed. Read limits and boundaries before carrying any state into a release claim.