40 lines
1.0 KiB
Markdown
40 lines
1.0 KiB
Markdown
# Drafting Process
|
|
|
|
## Branches
|
|
|
|
`main` is the protected public branch. Direct mutation of ratified text should be
|
|
exceptional. Ordinary changes should begin as proposals and enter `main` only
|
|
after review.
|
|
|
|
## Proposals
|
|
|
|
Each proposal should identify:
|
|
|
|
- the affected text
|
|
- the reason for change
|
|
- expected benefits
|
|
- rights and minority-protection risks
|
|
- implementation or transition concerns
|
|
- dissenting arguments that remain unresolved
|
|
|
|
Accepted proposals should be linked from the merge commit or preserved directly
|
|
under `proposals/`.
|
|
|
|
## Review
|
|
|
|
Review must consider more than popularity. A proposal should be checked for:
|
|
|
|
- due process risk
|
|
- speech and association risk
|
|
- privacy and surveillance risk
|
|
- local autonomy risk
|
|
- emergency-power abuse
|
|
- concentration of authority
|
|
- impact on politically weak minorities
|
|
|
|
## Ratification
|
|
|
|
Ratified snapshots are signed annotated Git tags named `ratified-YYYY-MM-DD`.
|
|
Each tag message should identify the ratified scope, the public process used,
|
|
and any unresolved minority report.
|