Canonical Scenario Form ​

A canonical scenario of Realith tests the architecture against the real form of the problem, rather than replacing it with an industry example or a marketing case.

What a canonical scenario must show ​

Any scenario that claims architectural significance for Realith must make the following elements distinguishable:

1. an object that matters more than an individual message;
2. the line of versions and transitions of that object;
3. several independent subjects working around the same object line;
4. environmental boundaries within which admission, visibility, and right cannot be collapsed;
5. canonical current state, without which the next step cannot count as generally valid;
6. a verifiable outcome that does not require total openness of the entire past.

What a canonical scenario must not do ​

It must not:

• reduce itself to demonstrating an industry;
• prove the project through the token;
• replace the architecture with a private product process;
• portray as settled practice what is still only a pilot or verification form;
• pretend that any coordination process automatically requires Realith.

Minimal form of a canonical scenario ​

In the most compressed form, a canonical scenario of Realith looks like this:

• an object exists;
• the object has an active version;
• several independent parties must relate to one and the same canonical current state;
• local reconstructions begin to diverge;
• a shared infrastructural layer for holding the object is required;
• the outcome must be verifiable, but not necessarily fully public.