semver & git inspired upgrade flow

Rather than having every change to the DAO happen through global "improvement proposals", we could have a more open process where anyone can push modifications to individual branches which ripple up to a `dev` branch that can only be merged to `main` through a proposal.

We could also use semantic versioning to track updates to the DAO as releases (e.g. `dorg-2.1.0`).

Start by examining how global improvement proposals currently govern changes, then map the proposed individual branches into dev and main. Define the semantic-version release process, such as dorg-2.1.0, and document what proposal-gate, branch, and release behavior would count as complete.

Vom Indexierungsmodell aus dem Issue-Text verfasst.