As I’ve covered before, a computational economy uses preemption and priority levels for its allocation schemes. Priority levels are used to determine, when demand exceeds constraints, which demands to fulfill and which to ignore. Previously I mentioned that these would be set arbitrarily at the start until a more rigorous definition is created. Well, I have now created a rough definition, though it will require quite a bit of effort on the survey and data mining side to get it working properly.
I think it will be easier if I show the formula and explain the terms in order. If you don’t recall, I had intended for this to fit within a range of about 120 discrete levels. However, two of the terms here are definitely not integers. I will undoubtedly have to weight some of them or just replace exact values with categories. and the resulting value will simply be rounded down and truncated above 100 (remember, the range is [rt,iso,-19,…,0,…,100] with the leftmost (lowest, after rt and iso) value being the highest priority.
is obviously the priority level.
is the multiplicity of the allocation. Most of these terms will be for an individual product, but products are usually manufactured in bundles, not individually. Lower is better.
is the affectation timescale, the duration of time that the relevant targets are affected. Because time is computationally measured in seconds, this term will not be measured directly, but rather as the (rounded) logarithm of the actual time, with a base of the number of seconds in a year. i.e.,
. The data for this will come from scientific study.
is a binary value, which determines the sign of the affectation values. If the effect is a detriment, dt is one, otherwise it’s zero.
is the people affected. The value can be positive or negative, and the magnitude will be logarithmic with a base of 10. i.e.
Higher is better. This will come from a combination of statistics, scientific study, and survey.
is the ecosystem services affected. I’m not so sure about this term’s viability, since a proper measurement of cost should account for affected ecosystem services. I’ll leave it here in case I think of a good reason to keep it.
is the cost, measured as aggregate relative abundance (ARA). This version of ARA should include the replenishment rate, e.g.,
, where j is the system’s jiffy value. Lower is better. Again, it should be the hiragana こ, but WordPress has its limitations. This value will come from survey and design data.
is the dependency indegree, or the number of things that *depend on the product*. Higher is better. This and the next term will come from the very laborious process of making connections between resource data after survey data is available.
is the *dependency outdegree*, or the number of things that *the product depends on*. Lower is better.
Clearly more work needs to be done, as I’m not even fully certain if I’ve covered everything that should be covered, or if the one term can be dropped. Like, I just realized I should include the time to failure and perhaps the maintenance cost of the product. Other parts of NE will likely be implemented long before there is data comprehensive enough to use this kind of formula, so heuristics will do well enough to start.
The basic idea I’m trying to capture is that tools of creativity, things that have a positive effect on others or the ecosystem, and efficiently-made products should be prioritized above destructive, detrimental, and wasteful products. Guitars over guns, gasifiers over coal furnaces, flowers over tobacco. This is not to say we can’t have the latter in each case at all, but it would be better if we instead had the former, and if it comes down to one or the other, we should certainly choose the healthier alternative.
An aside:
One thing I’ve learned in writing this entry is that though I am trying my best to keep this scientific, there is quite a lot of room for improvement. What ended up here differed significantly from my original notes, as I thought critically about the math here. However, it is important to note that I actually am critical of everything I’ve done, which is why I still feel I am being scientific, and why there is a bit of inconsistency over time.
Though this work (as in all of NE) was originally sparked by The Venus Project and The Zeitgeist Movement, I have grown to feel increasingly uncomfortable being associated with them, as I continually see a lack of self-criticism and quite a bit of groupthink among their members. One of the reasons I avoid explicitly mentioning any group associations here is the ingroup/outgroup biases that any readers would have given that knowledge.
I’d also like to mention that my friend Pieter de Beer, who curates the pages on VIAAC theory, has decided to move back to Durban and attempt to implement, test, and publish research on our ideas. I am very excited about this, as I’m sure he is, and it’s got me wondering what I can do once I graduate. Interestingly, I found out that we independently had the idea of starting with community kitchens, though the reasoning that went in and the idea that resulted differed slightly.