Recent Changes - Search:

Foundations

Members works

Result

Communication

Outside

RSS

Updates

edit SideBar

PriorityByEconomicalSystem

Principle

Associate a costs to actions, thus giving the basis for an economical system, in order to provide the necessary support for incentive on usage and optimization from improvements (cf per page "todo lists").

Solutions

Example

Ordered list of actions for strategy S (at t0) Ordered list of actions for strategy S (at t0+1)
starting point Action C realised
  1. x credits = action A (from project P)
  2. y credits = action B (from project P)
  3. z credits = action C (from project Q)
  4. a credits = estimated cost of action C (from project Q)
  5. b credits = estimated impact of action C (from project Q)

x>y>z>>a>b>0 proportionnal to the ROI of each action

  1. x' credits = action A (from project P)
  2. y' credits = action B (from project P)
  3. z credits = action C (from project Q)
  4. a' credits = estimated cost of action C (from project Q)
  5. b' credits = estimated impact of action C (from project Q)
Account=A Account=A+z

Structure

  • isolate an action A (atomic unit with clearly defined limits)
    • parent
      • default=root
    • expected impact of the realization
      • default=1/number of actions from the parent
      • imposibility to short-circuit the system and consider global impact
      • ultimately should be convertible to unit of energy
    • estimated cost
      • default=2300Kcal
        • shortcuts convertible to unit of energy
          • day of work for me
          • amount of money
          • amount of objects
          • combination of some shortcuts
          • ... (simple to add)
    • return on investment (ROI)
      • expected impact of the realization/estimated cost
  • Hierarchy of actions
    • root=strategy S
      • default=homeostasis
    • actions

Remarks

  • closure must be taken into account in order to
    • make projects "safe" fom side-effects
    • lower the cognitive cost of comparing a long list of actions
      • overall costs is too complex to evaluate and update
      • consequently, consider the cost for each project
  • unit of energy in general as absolute value in one moment in time, as opposed to taking time into account, might be too simplified
    • as the price of a unit of energy is a function of time
    • especially important if strategy takes into account homeostatis for which
      • energy can be stored only to a limited extend
      • energy can not be consumed instantly
  • estimate waste by conversion
    • in both direction
      • in cost, waste of management
      • in estimated impact, energetic waste in order to get the final product
  • EROEI alone can provide a basis for optimization
    • use an estimated base EROEI and tend to perpetually improve it

Credit

  • earned by realizing actions

Debit

  • spended on Energy Slave(s)
    • new tools
      • facilitating productivity of the system
    • delegation

To do

  • add the schemas from the notebook (Canada)
  • for shared/delegated/requests task, use Person/Person social network
  • leverage any existing agenda (for example WikiCalendar)

See also

Edit - History - Print - Recent Changes - Search
Page last modified on November 25, 2009, at 06:56 PM