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

Membership, companies, and labor hour tracking #91

Open
orthecreedence opened this issue Aug 6, 2020 · 2 comments
Open

Membership, companies, and labor hour tracking #91

orthecreedence opened this issue Aug 6, 2020 · 2 comments
Labels
layer:core Regarding the core protocol (cost tracking, transactional fabric, etc) project:paper tag:economics Regarding economics: dynamics, costs, incentives, etc tag:governance Having to do with governance in general (global,companies, resources, etc) type:discussion Discussion or ideas for future direction, input welcome (don't be shy)
Milestone

Comments

@orthecreedence
Copy link
Member

orthecreedence commented Aug 6, 2020

A member is someone who works at a member company (worker co-op, uses Basis). This gives them entry into the system. However membership is sliding scale that depends on contribution, and contribution is defined as amount of labor hours.

Ideas/benefits:

  • Define a systemic clamp (based on governance) on labor hours: the minimum required to be considered a member at all, and the maximum after which no further benefits are derived.
    • Would likely need to be some form of moving average
    • Would form the basis for setting an explicit and systemic "work week"
  • More systemic voting rights for people who track more hours
    • Why should someone who works 3 hours a week have the same input into the system as someone who works 50 hours a week?
    • Would not apply to companies because they are free to manage their own voting rights as they see fit
  • Sliding-scale use of shared property (housing, mop) based on hourly work
    • Effectively, determine the market rate (for non-membership) and determine the at-cost rate, and depending on membership ratio based on contribution, charge some amount of rent between market rate and at-cost.
    • Incentivizes full membership, and also derives network profit for those not contributing fully
  • UBI pays out by hours worked.

Thoughts/rebuttals:

  • What incentive is there for me to not just fill in 40 hours a week no matter what? With wages, it's because the cost needs to be paid by consumers, so I'm incentivized not to inflate my wages. With hours though, if tracking them gives me more systemic privs, what's to stop me from over-reporting?
    • What about some kind of per-company budgeting?
      • Nice idea, but not sure how this would do anything useful
    • Is there a social enforcement aspect here? Ie "you recorded 40 hours but you've only worked 10 hours, how dare you..."
  • Hours might need to be clamped: ie, you're only a member if you work more than 8 hours a week, and after working 40 hours a week you get the max privileges. This incentivizes a minimum and maximum work week length to some extent.
@orthecreedence orthecreedence added project:paper tag:economics Regarding economics: dynamics, costs, incentives, etc tag:governance Having to do with governance in general (global,companies, resources, etc) type:discussion Discussion or ideas for future direction, input welcome (don't be shy) labels Aug 6, 2020
@orthecreedence orthecreedence added this to the v0.3 - Core milestone Aug 6, 2020
This was referenced Aug 6, 2020
@orthecreedence
Copy link
Member Author

There really needs to be a systemic/economic incentive balance for tracking hours. It absolutely does make sense that we do this, because we cannot treat membership as binary, at least not in the beginning, but we need to make sure everyone doesn't just report their time as 40 hours each week. Paying people hourly is a good incentive to this end: you attach the hours worked to the cost of those hours. However, this doesn't work for salary or project-based payment. Needs more thought.

@orthecreedence
Copy link
Member Author

Given the epiphany in raw material tagging (#17) it seems to me the answer is to have some credit cost per hour tracked. Only thing is, I think the cost might have to be a universal agreed-on amount. Otherwise, how does costing work? It could be decided by the company the work happens on, but then we'd have to track occupation-hour-cost instead of just occupation-hour (much huger collection, not doing it, nope). Or we could just move the costing of labor hours to various companies where the consumption takes place, but why wouldn't they just set it to zero? I think until we have some alternative-pricing framework (currently prices are incentivized to revolve around costs), it makes sense to have a fixed costs for labor hours across the board. 1 hour = 1₡. Deal with it.

@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:paper tag:economics Regarding economics: dynamics, costs, incentives, etc tag:governance Having to do with governance in general (global,companies, resources, etc) 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