I'm sorry, but to me this really sounds lime you're talking about types of rule defined currency, not instances. This is especially clear because one can't have a set of instances that does not describe specific instances, which this one can't because it's general (you can pay it off with anything meeting the description). We really need to create a clear semantic separation between classes and objects. An instance of an asset could be called an item, but what would we call an instance of a currency (a money sounds wrong). Or should we being going the other way, using the current terms for instances and creating new ones to describe classes?
-Aris On Thu, Apr 26, 2018 at 11:12 AM Kerim Aydin <ke...@u.washington.edu> wrote: > > > (Useful for all kinds of upkeep costs) > > A switch is a Debt switch have possible values consisting of sets > of Rules-defined currencies (the debt load), with a default of > value of empty (0). Any non-empty debt load is "unpaid", a > empty debt is "paid" or "paid off". > > A player CAN flip a specified debt switch by paying Agora a > subset of that switch's debt load for this specified purpose, > thus > removing that subset from that switch's debt load. Attempts > to flip a debt switch by paying a set of currencies that is > not completely in that switch's debt load entirely fail. > > [Elsewhere] > > Upkeep is a debt switch for each facility tracked by the > Cartographer. At the start of each month, that facility's > Upkeep is set to the facility's upkeep cost defined in the > Rules. > > At the end of each month, any facility that is not owned > by Agora and has an unpaid Upkeep is destroyed. > > [optionally: reset the debt: when the facility is created? > when the facility changes hands?] > > > >
