01
Explain what silence means in the chosen system
An empty record can mean that no observation arrived, that a check was not scheduled or that a system recorded no event. Those meanings are not interchangeable. A Sivigil example should choose one and make it explicit in the legend. In a scheduled-reading exercise, mark a missing reading as missing rather than assigning it a numerical zero. This preserves the distinction between data availability and the value of the observed quantity. Readers can then understand why a rule changes state without inferring that the underlying condition improved during the gap.
02
Separate rule outcomes from broader assurances
A rule can qualify a sequence for attention under a supplied policy. That outcome does not establish the cause of the readings or prescribe a response in a real environment. A project page can describe the calculation directly and identify the policy as illustrative. Likewise, the absence of a qualifying sequence is not evidence that nothing relevant occurred between samples. Keep these boundaries close to the example so a compact summary does not imply more coverage than the observation process provides. The name should support careful attention to evidence, not replace that evidence.
03
Keep the record readable across handoffs
Use Sivigil consistently in page titles and exported worksheets, while assigning each scheduled observation a stable position or timestamp. Put the rule version beside the trace so another person can reproduce the result later. A useful display includes the raw reading, whether it is available, whether it meets the threshold and the resulting consecutive count. Text labels should carry these distinctions even when colour is unavailable. This helps a handoff preserve the reasoning behind the status instead of passing along a badge whose meaning depends on an unseen calculation.