Register Organization

⌘K
  2. Home
  4. Docs
  6. Register Organization
  8. Submit Request Form
  10. Registration and Onboarding an Organization

Registration and Onboarding an Organization

Register Organization

Project Overview and Philosophy

Rob’s Rules DAO (RRD) is a Decentralized Governance and Decision Platform (DeGov) that digitizes traditional parliamentary procedures through a blockchain-based framework. By evolving the manual “Robert’s Rules of Order” into an immutable digital environment, RRD enables organizations to move beyond binary “yes/no” votes toward iterative, deliberative consensus-building.
Challenge vs. Solution The Challenge: Organizations traditionally look to leadership to propose solutions, leaving stakeholders with a limited binary choice. This restricts innovation and prevents the development of complex, stakeholder-driven solutions that truly reflect collective intent. The Solution: Rob’s Rules DAO utilizes the fundamentals of parliamentary process to maintain a flow of productive discussions. By leveraging blockchain technology, the platform scales these proven rules, allowing groups of any size to evolve ideas through amendments and distill them into a final, cryptographic solution.
——————————————————————————–

——————————————————————————–

1. Multi-Tenant Onboarding Guide

The system supports unlimited customers on a single Vercel Pro project using dynamic domain-based configuration.

  • Step 1: Collect Information: Obtain the Customer Name, Subdomain prefix, and Chair Wallet Address.
    • Registration form on Website (https://robsrulesdao.com/request-account-on-robs-rules-dao/)
    • The Chair’s wallet address cannot vote. So the Chair’s address must be unique from any voting member within the account’s census)
  • Step 2: Update Configuration: Add the customer profile by shared/src/config/customer-config.ts using the [Customer]-C (Creation) and [Customer]-I (Interaction) naming convention.
  • Step 3: Deploy Code Changes: Push changes to the production-main branch.
  • Step 4: Update Heroku Backend Config Vars: Add new domains to ALLOWED_ORIGINS. Crucial: You must include the full protocol (e.g., https://ABC-C.robsrulesdao.com) and restart the Heroku app for the new origins to be recognized.
  • Step 5: Add Domains in Vercel: Add the specific creation and interaction subdomains to their respective Vercel projects.
  • Step 6: Configure DNS in GoDaddy: Point CNAME records for ABC-C and ABC-I to cname.vercel-dns.com.
  • Step 7: Wait & Monitor: Allow 15–30 minutes for DNS propagation across the global network.
  • Step 8: Fund Chair Account: Ensure the Chair’s wallet contains a small amount of native POL (Polygon) for Aragon execution gas fees.
  • Step 9: Functional Testing: Verify the Chair can create proposals on the -C domain and members can vote on the -I domain.
  • Step 10: Final Verification: Confirm metadata tags appear correctly in the Pinata Dashboard for new elections.
  • Step 11: Customer Handoff: Provide the customer with their dedicated URLs and the Chair wallet requirements.
——————————————————————————–

2. The Rob’s Rules Governance Workflow

The governance process utilizes a “Chained Election” model, allowing a proposal to evolve through five distinct stages:
  1. Initial Proposal: A member submits an issue. It is visible but requires recognition to move forward.
  2. Seconded Proposal: The Chair “seconds” the proposal, officially opening it for deliberation.
  3. Amendments: Members request changes. The Chair approves or declines these based on merit. If the Chair approves an amendment, all voting is reset, forcing members to vote on the new, updated proposal context.
  4. Final Voting: Members cast votes on the final, matured version of the proposal.
  5. Aragon Execution: If the vote passes, the Chair triggers the bridge to the Aragon DAO.
Critical Governance Rules:
  • Smart Comment Limiting: To prevent IPFS bloat, each discussion category (General, Speaking For/Against, etc.) is capped at 20 comments. A UI warning triggers at 15.
  • Census Removal Logic: Once a member casts a vote, they are automatically removed from the census for that specific election. This is a deliberate security feature: it prevents double-voting and ensures that once a member has finalized their choice, they can no longer see or participate in additional discussions or amendments for that proposal.
——————————————————————————–

3. Scalability and Decentralized Indexing

To support 100+ customers without the bottleneck of a central database, RRD uses a decentralized indexing strategy via Pinata Metadata Tags.
The Discovery Workflow:
  1. Tagging: During pinning, the backend attaches key-value tags: organizationName, electionId, and type.
  2. Querying: The frontend calls /api/find-organization-proposals/:organizationName.
  3. Filtering: The backend queries the Pinata API using the metadata[keyvalues] filter, returning all pins associated with that organization.
  4. Resolution: The app extracts the election IDs from the tags and fetches the final “truth” directly from the Vocdoni blockchain.
——————————————————————-

How can we help?