Update CONVENTIONS.md

Co-authored-by: Otto Allmendinger <otto.allmendinger@googlemail.com>

Author: lcovar

CONVENTIONS.md

@@ -170,9 +170,7 @@ const tx = Transaction.fromBytes(bytes);  // Unnecessary round-trip
 **What:** Transaction deserialization (for signing) and transaction parsing (decoding instructions) are separate operations with separate entry points. `Transaction.fromBytes()` deserializes for signing. `parseTransaction()` is a standalone function that decodes instructions into structured data.
 
 **Why:**
-- Not all use cases need full parsing (e.g., just signing)
-- Parsing can be expensive (especially for complex instruction decoding)
-- Separation of concerns — Transaction is for signing/serialization, parseTransaction is for decoding
+- Separation of concerns: decoding is a protocol-level concept, parsing is a BitGo-level concept 
 - Matches wasm-utxo pattern (BitGoPsbt doesn't parse on construction)
 
 **Good:**