Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implementation of resource management v1 #127

Open
3 tasks
orthecreedence opened this issue Dec 8, 2020 · 0 comments
Open
3 tasks

Implementation of resource management v1 #127

orthecreedence opened this issue Dec 8, 2020 · 0 comments
Labels
layer:core Regarding the core protocol (cost tracking, transactional fabric, etc) project:core tag:governance Having to do with governance in general (global,companies, resources, etc) tag:property Having to do with use/stewardship with property or resources type:discussion Discussion or ideas for future direction, input welcome (don't be shy)

Comments

@orthecreedence
Copy link
Member

orthecreedence commented Dec 8, 2020

This is a branch off of the "Mediation and usage of shared resources" (#86, which can now effectively be closed) issue where we specifically define the systemic controls around shared resources. These are granted to stewards, as opposed to those in-use (although in general, those in-use will likely have input):

  • Defining process(es) for determining use
    • This is where some form of smart contract, scripting layer, or automation system come in (Automating use of resources #126)
    • Could also not be automated, might be a human-defined process and simply recorded
      • Keep in mind, these decisions must be either a) based on a vote or b) made by representatives and ratified by members of the supercompany
    • This process would determine the member(s) and compan(y/ies) given use, the terms of their use (effectively, some form of contract whether automated, legal, or even a gentleman's agreement)
      • Restrictions on use (you can use this house for the length of your life, but please don't burn it down)
      • Time limits/schedules on use (you can use this card for the next 7 days after which it must be returned, or you can use this tractor every tuesday and thursday)
      • Cost transfer (X amount of costs will be transferred to you for each use or each day)
      • Market rate pricing for renting resources to non-members
      • Per-member costing based on membership percentage (member pays at-cost + difference between at-cost and market-rate depending on their status) (see Membership, companies, and labor hour tracking #91)
  • Defining process(es) for sale of resource into market
    • Perhaps here, defining some type of signaling system internally: "Hey, we're going to sell an old tractor, does anybody in-network need one?" This is where a somewhat standard set of tags might come in handy (for matching resource needs).
      • ^ Make this step optional, maybe a supercompany needs the highest price
  • Defining process(es) for purchase from market (via capital pool Capital pools #92)
    • Keep in mind, capital pools are an extension of resource management, and thus subject to the same processes being defined here. It can almost be thought of as a "minable" resource.

Current implementation ideas/thoughts:

  • Resources can be tagged, for instance a supercompany might steward a number of different resources, and want different representatives handling different ones such as housing or farm equipment.
    • Might want to base tags off of some kind of standard lexicon/vocabulary/semantics. Free-form tagging is a shitshow.
@orthecreedence orthecreedence added project:core tag:governance Having to do with governance in general (global,companies, resources, etc) tag:property Having to do with use/stewardship with property or resources type:discussion Discussion or ideas for future direction, input welcome (don't be shy) labels Dec 8, 2020
@orthecreedence orthecreedence added this to the v0.3 - core milestone Dec 8, 2020
@orthecreedence orthecreedence added the layer:core Regarding the core protocol (cost tracking, transactional fabric, etc) label Apr 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
layer:core Regarding the core protocol (cost tracking, transactional fabric, etc) project:core tag:governance Having to do with governance in general (global,companies, resources, etc) tag:property Having to do with use/stewardship with property or resources type:discussion Discussion or ideas for future direction, input welcome (don't be shy)
Projects
None yet
Development

No branches or pull requests

1 participant