01
Distinguish the rule from the world it describes
A rule can be an exercise assumption, an organisation’s convention or a claim about observed behaviour. Those roles need different kinds of support. In a Sinfero teaching example, label rules as fictional assumptions so readers know the conclusions depend on them. Correctly applying an assumed rule does not prove that the rule holds outside the exercise. A practical project should keep the rule’s source and scope beside its wording. That allows another reader to challenge the premise without confusing that challenge with an arithmetic or logical error in the derivation.
02
Use uncertainty labels that mean what they say
Unknown should indicate that the available facts and permitted rules do not settle an attribute. It should not be used as a synonym for unlikely, false or incomplete processing. A rule prototype can display which facts it examined and whether any new conclusion was added. A learning worksheet can explain why an apparently plausible statement is not supported by the supplied rules. Consistent labels help visitors understand the boundary of the demonstration. They also prevent a visually confident result card from communicating more certainty than its underlying reasoning permits.
03
Keep the identity and proof notation separate
Use Sinfero consistently in headings and exports, while giving each fact and rule its own short identifier. A rule named R1 is easier to cite repeatedly than a decorative slogan. Let the visual system distinguish input, rule and conclusion with labels as well as colour. Avoid making an arrow ambiguous: it should have a clear direction and a legend explaining its meaning. The brand can remain concise while the proof notation carries the detail. This makes the presentation usable when a worksheet is printed, cropped or shared without the surrounding site.