N. Package, context, snapshots, case, result, and test
14 pages in this book.
| Page | What it is for |
|---|---|
| Present an event with a time | I want to present an event that actually moves the case into the next stage. |
| Separate an action from a duty | I want to name an action without automatically attributing a permission or a duty to it. |
| Correct an event with a new version | I want to correct an event’s time while keeping the earlier record. |
| Read an external limit from a snapshot | I want to obtain an external indicator from a precisely pinned data set. |
| Inherit an explicit context | I want to lift the common axes of a case into a named profile. |
| Record a case with ready values | I want to present my facts to an existing rule. |
| Compose facts from two cases | I want to join selected facts from two cases while keeping their origin. |
| Choose a mode for assumptions | I want to evaluate an assumption in an explicitly chosen mode. |
| Name a package and parameters for a reader | I want to give the reader names for the package, a relation, and its parameter. |
| Place metadata in the manifest | I want to describe the package and the origin of its review in the artefacts meant for that. |
| Write a scenario with a checkable expectation | I want to keep the input, the question, and the expected answer as an executable scenario. |
| Check a property on a finite domain | I want to check that every element of the presented domain gets the expected conclusion. |
| Check that an example is sensitive to the rule | I want to prove that the promised answer depends on the shown rule. |
| Mark a phase that is not yet executable | I want to mark explicitly the boundary of a future computation round. |
Documentation for Arxo. Writings — blog.arxo.io.
Anonymous visit counts on stats.arxo.io, no cookies.