Proposals

πŸ—³οΈ Proposals: The Heart of the DAO

Proposals are how the community decides what gets built. lore.digital is a DAO-based community, which means everyone has a say in the content we initiate and in what becomes canon. A proposal is the formal way to put an idea in front of the community β€” a new piece of lore, a project, a change in direction β€” and move it through feedback, review, and a binding vote. If competitions are the front door for new writers, proposals are the engine of governance: nothing of consequence happens because one person decided it should. 🎯 What Proposals Are For

A proposal is an open pitch to the DAO. It's the mechanism for: Initiating new content β€” a story, a character, a region of the map, or any addition to the world that should be considered for canon. Funding and resourcing work β€” proposing the costs, timelines, and people involved in getting something made. Setting direction β€” decisions about the world, the organization, and how the community operates.

The point is transparency and shared ownership. Every proposal is visible, every voice can weigh in, and the outcome is decided collectively rather than handed down. πŸ“ How to Initiate a Proposal

Onboarding a new idea begins with the creator initiating a proposal using the proposal module. When you create one, you provide: An overview of what you wish to create or change. A draft of the content, if it exists at this stage. The costs and timelines involved in delivering it.

Once submitted, the proposal enters a phase of feedback and dialog between you and the community. Note: at present, only DAO members can view, create, and provide feedback on proposals. πŸ’¬ Discussion & Feedback

Each proposal has an integrated discussion panel. The Community Feedback pane is open to all DAO members to deliberate on the merits of the proposal and give feedback to the author. A separate Risk Management panel is reserved for the working group that oversees the relevant area β€” for example, members badged as Loremasters are responsible for final diligence on lore proposals that pass the community vote.

This is where a proposal gets sharpened: questions get answered, scope gets refined, and the community builds (or withholds) its support before anything goes to a binding vote. πŸ—³οΈ Voting: Two Types of Vote

The governance system uses two votes β€” a soft, off-chain pre-vote to gauge support, and a binding on-chain vote. Stage One β€” Soft Vote

An upvote / downvote widget sits at the top of the proposal block. When the net upvotes reach the system-wide threshold (for example, +10), the proposal advances to the risk assessment stage. This soft vote is the community's initial signal of whether an idea has the support to proceed. Stage Two β€” Snapshot

After a proposal clears risk assessment, the system generates the required Snapshot vote. Snapshot is integrated directly into the governance UI, so DAO members make their final, binding choice from within the platform. This is the on-chain vote that decides whether a proposal moves forward β€” and, for content, toward canonization. βœ… After a Proposal Passes

A passing proposal isn't the end of the process β€” it's the green light. Approved content moves into creation and, ultimately, canonization, where it's published and woven into the world. The whole flow β€” propose, discuss, vote, build β€” is what keeps the DAO genuinely community-driven, with the pride of ownership that comes from knowing you built that.

Browse all documentation