90-day lead time
An amendment must be published with reasoning at least 90 days before the first binding vote.
Amendments
Every Tier-4 amendment requires publication, 90-day lead time, SARB and Assembly aggregate thresholds, a 12-month moratorium, debate in every polis, revote, and trustee-veto handling.
An amendment must be published with reasoning at least 90 days before the first binding vote.
The hard bar is 365 days. Current active moratorium counter: 0 / 365 days because no Tier-4 amendment proposal is active.
Public vote evidence shows SARB and per-polis Assembly counts only. It publishes no per-citizen vote data.
Active proposals
The source record is amendments.json. When a proposal enters moratorium, this table must show its day-counter and redline hash.
| Proposal | Invariant | Moratorium counter | Required bar | Redline |
|---|---|---|---|---|
| No active proposal | None | 0 / 365 days | 365 days minimum | No active redline |
Vote tally aggregates
All public tallies are aggregate counts. Private voter identity, private vote rows, and per-citizen records are excluded.
| Gate | Aggregate threshold | Current active tally | Public boundary |
|---|---|---|---|
| SARB initial vote | 60% yes | No active tally | Aggregate count only |
| Per-polis Assembly initial vote | 60% yes in every polis | No active tally | Aggregate count only |
| SARB revote | 60% yes after moratorium | No active tally | Aggregate count only |
| Assembly veto override | 75% yes in every polis | No active tally | Aggregate count only |
The moratorium period requires debate in every polis before a revote can happen.
A trustee veto can only stop ratification unless every polis Assembly reaches the 75% override threshold.
Active redlines also appear on the articles record so legal artifacts and amendment state stay aligned.
Open articles record