start filling in

diff --git a/isa_conflict_resolution.mdwn b/isa_conflict_resolution.mdwn
index 3c0d2ab43c645ce334a261ba097d6de4bd31778d..b7d187add35c5ececa614919fa8b5a0ba5e7305a 100644 (file)
--- a/isa_conflict_resolution.mdwn
+++ b/isa_conflict_resolution.mdwn
@@ -380,6 +380,12 @@ So to summarise:
 * The implementation details are clear (and problem-free except for
   vendors who insist on deploying dozens of conflicting Custom Extensions:
   an extreme unlikely outlier).
+* Compliance Testing is straightforward and allows vendors to seek and
+  obtain *multiple* Compliance Certificates with past, present and future
+  variants of the RISC-V Standard (in the exact same processor), in order
+  support legacy customers and provide same customers with a way to avoid
+  "impossible-to-make" decisions that throw out ultra-expensive multi-decade
+  proprietary legacy software at the same as the hardware.
 
 # Conversation Exerpts