Document a community use case (store-validate calculations)

[6r1d]

Recently, a community member presented a scenario that we need to document.

Scenario

Many independent organizations either publish or validate the published calculations.
A WASM- (or DSL-) based verifier will:

• check the calculations
• ensures the results are correct
• ensure the results fall within the pre-set limits imposed by the normative agreed on by all parties

Topics to cover

• When do we split domains, given there are many independent parties and trust should not be required? (Several domains are needed to store and compartmentalise the intermediate results.) – related to Provide examples of mapping domains to concrete concepts #457
• Should multi-signature transactions be used to prevent any modification of the store asset fields after those were verified? No party should be able to change the constants used for the calculations single-handedly. (It is possible and useful, but alternatively, the modification history is visible and a trigger may be used to monitor such modification.) – related to Multisignature transactions #258
• Could the asset belong to the smart contract? (No, they belong to an account controlled by some party through a key.)