Status values

sbxm status uses stable, untranslated values so they can be recognized across locales. The values below describe an observation result and the action it suggests. sbxm ls uses a smaller user-facing project-state vocabulary; its open-blocked state points to the detailed observations in sbxm status <project-id>.

Value	Meaning	What to do
ready	The observed state is available and matches the project declaration.	Continue with the normal workflow.
missing	The expected item was observed to be absent.	Create or restore the item, then run the command again.
mismatch	The observed state does not match the project declaration.	Inspect the diagnostic and fix the project declaration or the observed artifact.
not-observed	sbxm could not observe the state, so it cannot say whether the item is present or matches.	Read the diagnostic below the table and fix the environment that prevented observation.
not-applicable	There is nothing to look into yet, so the item has no state to report.	Nothing. The item becomes meaningful once the artifact it describes exists.

not-observed is different from missing: absence is an observation, while not-observed means that the check itself could not produce an answer.