Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 40 additions & 0 deletions processes/Weight-check-automation-resolution-process.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
## Weight Check Automation & Resolution Process

### Purpose

Ensure that automated checks validate Super Validator weight configurations against on-chain votes and provide a clear resolution workflow for any discrepancies.

### Process

#### 1. Re-enable automated weight checks
- GSF DevOps toggles the CI pipeline to run weight-consistency checks on every PR against `approved-sv-id-values.yaml`
- Checks fetch live on-chain weights and compare them to the YAML configuration

#### 2. Flag and notify
- On mismatch, CI creates an issue labeled `weight-check-failure` in the SV config repo

#### 3. Assign responsibility
- The originator of the weight-change proposal must resolve any flagged errors
- If no PR corresponds to a recent vote, that vote should be voted down by default

#### 4. PR creation and correction
- As per Itai’s guidance, the proposal originator opens the PR and references it in the vote request
- The originator must update the PR to clear all CI flags before merging

#### 5. Merge permissions
- By default, PRs can't be reviewed by employees of the same organisation that submitted a vote.
- IEU staff may merge weight-change PRs internally provided that:
- One individual submits the PR and a different individual merges it
- All CI checks pass

#### 6. Visibility and reporting
- CI results and open failure issues remain publicly visible in the SV config repository

#### 7. Escalation
- Unresolved errors older than 48 hours trigger notification of the GSF governance team

---

### Background & Related Automations

- GSF now handles many parallel weight changes; automated checks prevent configuration drift