Sdk Assertions

Operator wants to ensure account balances never go negative across all explored histories of a banking SUT.

Encode the safety property with an Always-style assertion placed where the invariant must hold (e.g., after each transfer), so the platform flags any explored history that violates it. Always means 'must hold on every path the explorer reaches'. Keep the predicate cheap and side-effect-free.

Operator wants to confirm a specific recovery code path is exercised, and a specific 'should be impossible' state is never entered.

Use a reachability assertion to require the recovery path IS reached, and an Always/unreachable assertion to require the impossible state is NEVER reached. Distinguish 'we want this to happen at least once' (reachability/Sometimes) from 'this must never happen' (Always/unreachable) — they are diffe…

Several assertions share the generic message 'check failed', so a triage report cannot tell them apart.

Give each assertion a stable, unique identifier and a descriptive message naming the property, so reports aggregate the right failures and operators can find the code site. Distinct, durable ids let the platform track an assertion's pass/fail history across runs. Avoid reusing one generic message a…