HodosRef

import tropos.actor.UntypedActor;
import tropos.actor.UntypedActorFactory;
import tropos.actor.ActorSystem;
import tropos.actor.Props;

Mandated Utility

The mandate has no value in and of itself. It only has context. The utility is proven and due to the runtime.

There are nine (9) classes to define tokenship and set the value proposition as a mixed sort of fungibility. Utility is, of course, a class distinction and, as such, should neither be employed, made dependent nor summarised within the running proof system. It can change, however. And, as we tend to number things alongside other contexts, we include the and instantiate the mandate as the original, default tranche -- the nominal, latent value of the antiquated or dissolute user state.

Tokenship

1. Expressivity
2. Actionability
3. Integrity
4. Material Tractability (Run-Length Encoded)
5. Compactness
6. Votive Luxury
7. Novelty
8. Zero Fungibility
9. Emergency

Each class is used to track related events (attestations) garnered from the economic environment. Consequently, the history of these aspects of fungibility can be seen to run multi-part, with each class in their own respective "lanes". As a whole, with the right transaction logic within the multi-class accounting, the system of variable fungibility become meta-stable in its own right. Also, each class can have its own set of objective views of the value proposition as it gets braided into the token's elastic sense of overall worth. In the end, the assessments between multi-class tokens and "flat" fungible (e.g. ERC-20) will enable security and financial provisions not available at present: rates in context, reflexivity that imparts meaning back into the economy.

1. Expressivity

Expressivity is the user's oracular right to emit interpellative safety/stability measures through continuous and spontaneous knowledge representation.

2. Actionability

Veritable, in placement, on foundational grounds, e.g. landmarked, established.

3. Integrity

Actionability in historical matters; performative mark or signal.

4. Material Tractability (Run-Length Encoded)

The matter of complex refined actionability and, thus, adaptability in situ. Performance means and measures are represented here through historical documentation. As we dealing with unique identifiers for comprehensive user reference, any number of differentiation standards may be assigned (an ERC-721 transaction, for example).

5. Compactness

In the archival of the above, we must account for space.

6. Votive Luxury

Easily measureable.

7. Novelty

Implicitly connected; explicitly derived, validate.

8. Zero Fungibility

The case of stacking up last-resort measures, to maintain security: calculation is orthogonal to the problem space and we include the exclusionary view. N.B. this is not necessarily equivalent to non-fungibility. For the case of non-fungibility, see the case of materiality, which is being stacked up in lanes 4-7 (above).

9. Emergency

As the most literal of the contexts, we look to the condition of various deployed solvers which are left to run for many years beyond the scope, even, of the mandated utility (e.g. the calculations are reactive, not of any concurrency). There are many issues of reachability one must survey in this case. What's radically time-consuming, for example, cannot be considered in any way part of the emergency sense of fungibility. Other abstract notions can easily co-exist, numerically, within the exchange.

Mandate can incorporate many different functions of language, for example, a vertex (or Αρχική, 'Origin') -- a point of reference for the attestations of utility that are generally established in the running of the solver (e.g. by the contracts, on-chain).