EVR Documentation, July'23 *draft*
  • 2.0 Preface to a Gitbook
  • World Building
    • 1.9 A Primer
    • 1.9 Specific Benefits
    • 2.0 Introducing EVR
    • 2.0 What's in the foreground
    • 2.0 Skimming the surface
    • 1.9 In-app infrastructure
  • Toolkit
    • 1.9 SRS: Social Recognition Software
    • 0.0 Guild structure
    • 0.9 CGS: Community Governance Structure
    • 1.9 dTVET
  • In the world of EVR
    • 0.0 Emergent Patterns
    • 0.0 Applications & Industry
    • 0.0 Buildouts, Reskins, & Modularity
    • 0.0 Member Profiles
  • White paper
    • ⚖️***Philosophy template***
    • 1.0 Reputations: Public & Administrative
      • 1.9 Engagement
      • 1.0 Public Reputation
        • 0.9 Public Reputations: General- & Specific-
        • 0.9 Awards
        • 0.0 Flags
      • 0.0 Administrative Reputation
        • 0.9 Bayes adjustment
        • 0.9 demurrage
        • 1.9 Billings Score
        • 1.9 Culculus score
    • 1.9 Guild
      • 0.9 Reputation of guilds
      • 1.0 Parent & Daughter guilds
        • 0.0 Seed Guild
        • 0.0 Regional Language Family
        • 1.0 Guild Creation
        • 0.9 Member
      • 0.9 Ordinal Guild
        • 0.9 Acquisition - Integration _ Proliferation
          • 0.9 Skillset Decay
          • 0.9 Relational Dynamic Adjustment
          • 0.9 Advancement
          • 0.9 Level
        • 0.9 Sourcing and Revising Standards
          • 0.9 Safe Work Practices
          • 0.9 Certifying Body
          • 0.0 Practical Factors (rename)
          • 0.9 Fundamental Domain Competencies
          • 0.9 Standard Operating Procedures
          • 0.9 Guild Certification
    • 1.9 Community Governance Structure
      • 0.8 EVR Community
      • 1.5 Content Moderation
      • 0.9 Code of conduct
      • 0.0 Content
      • 1.0 Disputed Content
        • 1.0 Dilemmas Ethical and Procedural
          • 0.9 Unethical
          • 1.0 Unfitting
      • 0.9 Arbitration Process
        • 0.0 Brief
        • 0.0 Proposal
        • 1.0 Arbitration Threshold
        • 0.0 Determination
        • 0.0 Resolution / Dismissal
        • 1.0 Arbitrating Members
        • 0.0 Activity Status
      • 0.0 Reporting Member
      • 1.0 Potenza Threshold
    • 1.0 EVR Team
      • 0.9 Disaster Relief Protocols
      • 1.0 Ikigai Insights
  • Blue Paper
    • ***Form & function Template***
    • 1.0 Reputations: Public & Administrative
      • 1.9 Engagement
      • 0.9 Public Reputation
        • 0.9 Public Reputation: General- & Specific-
        • 0.1 Flags
      • 0.0 Demurrage
      • 1.0 Bays adjustment
      • 0.0 Awards
    • 1.0 Guild
      • 0.0 Reputation of Guilds
      • 0.9 Guild rep
      • 1.0 Guild Creation
      • 0.0 Seed Guild
      • 0.9 Ordinal Guild
      • 0.9 Guild Certification
      • 0.9 Standard Operating Procedures
      • 0.0 Fundamental Domain Competencies
      • 0.9 Certifying Body
      • 0.9 Acquisition - Integration _ Proliferation
      • 0.9 Sourcing and Revising Standards
      • 0.0 Parent & Daughter guilds
      • 1.0 Member
      • 0.0 Advancement
      • 1.0 EVR Community
      • 0.9 Skillset Decay
      • 0.9 Safe Work Practives
      • 0.9 Level
      • 0.9 Practical Factors (rename)
      • 0.9 Relational Dynamic Adjustment
    • 1.9 Community Governance Structure
      • 1.5 Content Moderation
      • 1.0 Potenza Threshold
      • 1.0 Arbitration Threshold
      • 1.0 Arbitration Process
      • 1.8 Billings Score
      • 0.9 Dilemmas: Ethical and Procedural
      • 1.0 Unfitting
      • 1.0 Unethical
      • 0.0 Activity Status
      • 1.0 Resolution / Dismissal
      • 1.0 Arbitrating Members
      • 1.0 Regional Language Family
      • 1.0 Reporting Member
      • 1.0 Disputed content
      • 1.0 Determination
      • 0.0 Content
      • 0.0 Code of Conduct
      • 1.8 Cuculus score
      • 0.0 Proposal
      • 1.0 Brief
    • 0.0 EVR Team
      • 0.9 Ikigai Insights
      • 0.9 EVR Team
      • 0.0 Disaster Relief Protocols
Powered by GitBook
On this page
  1. Blue Paper
  2. 0.0 EVR Team

0.9 EVR Team

Stewards of the platform’s architecture.

Previous0.9 Ikigai InsightsNext0.0 Disaster Relief Protocols

Last updated 1 year ago

Overview

We manage back end, Servers, tech stuff We manage PR stuff, marketing, research, customer service. Research & development teams, impact teams

Where it occurs/ how we initiate it

The team is always working away in the background, hopefully not interfering with anything difectly. Facilitatethe processes of self governance and self direction. We nee ot make sure that theres such a way that the things build cant be taken away from the people who build them. We need to make the system even more robust so as to accomidate the things we wish to accomplish.

You ever team for the time being is run as a benevolent dictatorship. Up until the point that this organization is able to run off, myself a call all the shots when the company has reached the threshold where it is able to sustain itself, at that point in time we won't step away, step down, and we don't need our influence 2 impact every little decision. For the moment though the a team is headed by the people whose brainchild it is. Up until it reaches the level of sophistication that it can be managed on its own, up until left has Matt where there's enough people working on it and enough people contributing to the thing, we're going to have to retain sole control over it. Our team is not simply a group of people do anything, are you requires processes, it requires your check, and requires people to do their different jobs all come together in a way that makes the project as a whole work. Never team exists only to facilitate the app. We try to keep he goes out of the way as much as possible, and we reward finding problems we want to empower our people to come up with Solutions not just appease those in charge. Eventually decisions within the team will more and more be decided by consensus of those working within the teams, better to a point from below that anoint from above, the a teen is there to assimilate the guilds not to direct them, not to tell them what they're Accountabilitysupposed to do or to limit them in any sort of profound ways. We want to encourage them in profound ways, we want to empower them to make their own choices to come up with their own Solutions and to make their own way in the world. The ever team is there tipping maintenance on the tool that is ever. We are not Solutions we are tools to create Solutions. We are stewards of the platform, not saviors not dictators, Don't we maybe the people constructing the platform, it is not ours it is a gift as a public space it is a back to be held in the Commons by the people and we simply maintain the scaffolding the structures that allow people to use this platform. People of the a protein bar all the proteins, and probably not the coronavirus clear up all of the energy forward all of the benefits are all of the money of this thing, it was a group endeavor. I granted it is Guided by myself and Nicole but we need to make sure that the thing is Equitable and fair for everybody involved. We have a order of magnitude. 4 our face pay scale, so that no one person gets more than one order of magnitude pay than anyone else. We want our team on the processes of our team to be as transparent as is possible, we want pay and benefits to be explicit, and to be normal to everybody else within the organization. The organization help is foremost concern. And we're not going to let everything just go completely Milly and we will provide the structure and the ways for people to provide feedback and to give their insights Austin meaning. We maintained accountabilities through having multiple teams work on separate same project and check one mother and one brother, we want our output to be proper and we want to focus on the mission rather than on ego, we want assessments to be made based on Performance Based on contribution rather than on seniority or dictate. We want quote on quote favor to go to those who have earned it from their teammates and from everything nice.

Philosophy