Roadmap.md

The equivalent of a constitution has been written, a tech stack has been chosen and high-level technical specifications have been made.

“Constitution” covers bylaws, extra-bylaw rights, policies and protocols, dispute resolution.

• The bylaws are written (not necessarily final draft – pre-lawyer).

  • Questions needing answers:

    • What is the scope of the holding company’s power? What is its relationship to the DCE?

    • What’s the deal with the IPO? Is it going to be a an ICO/securities offering?

    • Are the stakeholders controlling the company by some other means than stock?

  • Tasks:

    • Find way to stay up-to-date with Lynzee, Yue, and Stephanie.

    • Complete more research in risk-assessment, and other committees.

      • consult experts, attend training/conference?

    • Complete working draft

• Extra-bylaw social protocols have been defined

  • Stakeholders are defined

    • Questions to answer:

      • Are our stakeholder groups project or product specific? Is each product a DCE? Is this too granular?

      • Are our stakeholder groups representing pillars of our business?

      • Are they representing certain pre-defined interests we want considered? Ex: ethics, employee rights, consumer protections, local community, web 3 education, investors, etc?

    • Tasks:

      • Work with Lynzee and Stephanie to follow developments on this subject.

      • Analyze hemp collaboration

      • Draft possible project-based SH groups

      • Draft possible pillar-based SH groups

  • Policy domains: who is responsible for what policies, and how can they be amended?

    • Questions:

      • Who decides about employee arbitration agreements?

      • Who decides/dictates data privacy policies?

      • Who decides family leave, salaries, hiring and firing practices? (HR?)

      • Is there a better way to protect worker rights and interests?

    • Tasks:

      • Establish strategy for employees to change policies.

  • Reputation system

    • Questions to answer:

      • Is the reputation system specific only to individuals? To teams? To stakeholder groups as a whole?

      • In what instances should we be considered equals, when should hierarchical roles determine power, and when should reputation play a part?

    • Tasks to be completed:

      • Make some proposals

      • Pilot some systems

      • Lead employee conversations to gather feedback

      • Pitch pilots to higher ups

      • Report results

  • Values, mission, purpose

    • Tasks to be completed:

      • Work with Elaina and Stephanie?

  • Internal governance and management

    • Questions to answer:

      • How do we organize power internally?

      • What is the relationship between internal/employee-level governance and board-level?

    • Tasks to be completed:

      • Research different governance and management styles and technologies

      • Attend some trainings

      • Pilot some systems

      • Lead employee conversations to gather feedback

      • Pitch pilots to higher ups

      • Report results

  • Values, mission, purpose

    • Tasks to be completed:

      • Work with Elaina and Stephanie?

• Processes and Policies Established for Employee Arbitration Agreements, Dispute Resolution and Avoidance

  • Question:

    • What is our employee arbitration agreement?

    • Is it ethical?

    • How are other companies dealing with this in a way that we could benefit from?

    • What should our dispute resolution system be?

  • Tasks:

    • Work with Stephanie and Matt to understand existing structure

    • Research, summarize, and analyze best practices

    • Research Mattereum

    • See about potential Mattereum collaboration (asset-level governance)

    • Research Kleros

    • See about potential Kleros collaboration (decentralized arbitration)

    • More thoroughly research Colony’s dispute resolution

      • Off-chain pilot for IRL conflicts?

    • Draft dispute resolution proposal

Choose Tech stack means that I have identified which stacks we are building on and have designated responsibility for this work

• Colony

  • Questions:

    • Will new developer team have say in this decision?

    • How might we layer Colony’s arbitration system with other systems, like Kleros?

  • Tasks:

    • Meeting May 7

    • Move forward (or not) based on May 7 meeting and Jeff’s input. Actions TBD

• DAOstack Proposal

  • Tasks:

    • Write summary/presentation of how DAOstack could facilitate the DCE contrasting w/ Colony

      • How is Liberland combining Kleros and DAOstack?

    • Coordinate and build relationship with DAOstack

• (potential) Mattereum Proposal

  • Tasks:

    • Research and report (executive summary) of Mattereum

    • If applicable, build relationship

    • If applicable, build presentation/proposal

• (potential) Kleros Proposal

  • Tasks:

    • Research and report (executive summary) of Kleros

    • If applicable, build relationship

    • If applicable, build presentation/proposal

• TBA Dev Team

  • Questions:

    • Might they be interested in starting from 0 and building something with us?

    • Are we even open to starting from 0?

    • Do they have something they already want to use?

    • What will my coordination with this team look like?

  • Tasks

    • Present my progress to them

    • Build relationship, establish coordination

Definition of a high-level technical specification means that I have identified which tech stacks we will use, that I understand from a very high level that what we want is possible with them, and delegated the work to developers to complete:

• Write a full report of the tech stacks we want to use, and a whitepaper-esque non-technical document describing their integration.