From b81e05387b8f0463249780e1fc42b4b3f62ad02a Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 2 Nov 2026 18:35:17 +0100 Subject: [PATCH] Judge says its rules are its own Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL --- modules/mesh-delivery-indexer/judge/judge.go | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/modules/mesh-delivery-indexer/judge/judge.go b/modules/mesh-delivery-indexer/judge/judge.go index 96cd4a2..3add633 100644 --- a/modules/mesh-delivery-indexer/judge/judge.go +++ b/modules/mesh-delivery-indexer/judge/judge.go @@ -5,9 +5,9 @@ // as the composer is run), use it. Every other part decodes a manifest leniently (catalogue.Decode) and takes the // verdict; it never judges (ADR 0578 §3). // -// Its rules are still mesh-sdk's catalogue functions it calls; they leave mesh-sdk for this package in the group's last -// mesh-sdk commit, once no reader imports them (ADR 0578 §7, issue 1585 S19). Callers depend only on what this package -// answers, so that move changes nothing for them. +// Its rules are this package's own (rules.go; ADR 0578 §7 as carried out by ADR 0593 §1): it reads from mesh-sdk's +// catalogue only the manifest's shapes, the seat table and the readers of a manifest's values every part shares, and +// calls no rule there. A rule is added here, never to mesh-sdk. package judge import (