See the model events behind a rule
When a rule fires where it should not, or fails to fire where it should, the trace shows what the model reported and the verdict each rule reached. The trace is Anvil's; Anvil: trace model events says how to raise it, what each channel shows, what it costs and how to read a block. This page holds only what is specific to Touchstone.
The category
Every line this resource writes carries the category Touchstone. Raise it in
<installation>/data/log4j2.xml:
<Logger name="Touchstone" level="debug"/>and read it back with:
grep ' Touchstone - ' csm.logThe three verdicts
The rule= fragment at the end of an event names one of the three rules and marks each half of its
condition ✓ or ✗, followed by what was found there: the element as Metaclass "name" «stereotypes»,
or unset.
| Rule | Halves |
|---|---|
Attribute | owner, type |
Relation | owner, type |
StepAction | owner, behavior |
The two property rules share their triggers and their sweep, so one Property produces a verdict from each, and the pair is the expected shape:
rule=Attribute no-match ✓owner:Class "Function" «Concept» ✗type:Class "System Component" «Concept»
rule=Relation MATCH(apply) ✓owner:Class "Function" «Concept» ✓type:Class "System Component" «Concept»A PrimitiveType-typed property shows the reverse. A property whose type half fails on both rules
with a Class carrying no «Concept» is typed by a plain Class and belongs to neither. ✗type:unset on
both means the property was created and owned in one transaction and typed in the next; the second
transaction carries the match.
Which event to read
Applying «Concept» to a Class reports two events on the Class and none on its properties, and the rules sweep from the Class to the properties it owns and types. The verdict on a swept property therefore appears in the transaction that stereotyped the Class, not in one that touched the property. The same holds for «Step» and the actions that call it.