From 3ed31f130513a9bf6840b48410d0825ba29c30cd Mon Sep 17 00:00:00 2001
From: seugu <99656002+seugu@users.noreply.github.com>
Date: Thu, 25 Dec 2025 15:52:14 +0300
Subject: [PATCH] threshold_peer_score MUST clarification

---
 vac/raw/eth-mls-offchain.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/vac/raw/eth-mls-offchain.md b/vac/raw/eth-mls-offchain.md
index 9c4af0c..3068dd4 100644
--- a/vac/raw/eth-mls-offchain.md
+++ b/vac/raw/eth-mls-offchain.md
@@ -426,8 +426,8 @@ with new members starting from a configurable default value `default_peer_score`
 Peer scores may decrease due to violations and increase due to honest behavior;
 such score adjustments are derived from observable protocol events, such as
 successful commits or emergency criteria proposals, and each peer updates its local table accordingly.
-Stewards periodically check whether any peer’s score falls below a predefined threshold `threshold_peer_score`;
-only in that case is a removal operation included in the next commit.
+Stewards MUST periodically evaluate peer scores against the predefined threshold `threshold_peer_score`.  
+A removal operation MUST be included in the next commit only if a peer’s score is observed to fall below `threshold_peer_score`.
 This mechanism allows accidental or transient failures to be tolerated while still enabling
 decisive action against repeated or harmful behavior.
 The exact scoring rules, recovery mechanisms, and escalation criteria are left for future discussion.