From 655719fdbdc04475edd3028113b3721d2ace69ba Mon Sep 17 00:00:00 2001
From: Jazz Turner-Baggs <473256+jazzz@users.noreply.github.com>
Date: Wed, 9 Jul 2025 11:43:49 -0700
Subject: [PATCH] remove redundant requirements

---
 specs/conversations.md | 13 +------------
 1 file changed, 1 insertion(+), 12 deletions(-)

diff --git a/specs/conversations.md b/specs/conversations.md
index 8216a3c..bbaf3c1 100644
--- a/specs/conversations.md
+++ b/specs/conversations.md
@@ -37,7 +37,7 @@ A ConversationType MUST define how to generate conversation_ids
 
 A ConversationType SHOULD define membership requirements and limitations.
 A ConversationType SHOULD define privacy and security guarantees.
-
+A ConversationType SHOULD maintain a deterministic decoding tree.
 
 ## ConversationType Identifiers
 ConversationTypes are identified by the title of the specification. This allows developers to lookup the associated specification.
@@ -60,9 +60,7 @@ Care should be taken to ensure that conversation_ids do not conflict.
 To disambiguate between different logical layers, payload types sent by a Conversation are referred to as `Frames`.
 Conversations are free to determine which frames are needed for their specific use cases.
 
-ConversationTypes MUST define a section which defines all possible frames 
 
-ConversationTypes SHOULD maintain a deterministic decoding tree.
 
 
 ## Encryption
@@ -78,15 +76,6 @@ When developing new ConversationTypes contributors should consider:
 - Channel binding and the impacts on message security.
 
 
-
-## Implementation Suggestions (optional)
-An optional *implementation suggestions* section may provide suggestions on how to approach implementation details, and, 
-if available, point to existing implementations for reference.
-
-
-## (Further Optional Sections)
-
-
 ## Security/Privacy Considerations
 
 This approach puts heavy requirements on ConversationTypes to build their own cryptography without providing much guidance. Finding mechanisms that provide safety while maintaining the flexibility should be prioritized in follow up work.