Soften regulatory references in introduction, keep mapping in appendix

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

draft-nennemann-wimse-execution-context-00.html

@@ -1635,11 +1635,11 @@ Workload-Proof-Token HTTP headers.<a href="#section-1.1-1" class="pilcrow">¶</a
 accountability.  Knowing who performed an action does not record
 what was done or in what order.<a href="#section-1.1-2" class="pilcrow">¶</a></p>
 <p id="section-1.1-3">Regulated environments increasingly deploy autonomous agents that
-coordinate across organizational boundaries.  Multiple regulatory
-frameworks — including <span>[<a href="#EU-AI-ACT" class="cite xref">EU-AI-ACT</a>]</span>, <span>[<a href="#FDA-21CFR11" class="cite xref">FDA-21CFR11</a>]</span>, <span>[<a href="#MIFID-II" class="cite xref">MIFID-II</a>]</span>,
-and <span>[<a href="#DORA" class="cite xref">DORA</a>]</span> — require structured, auditable records of automated
-decision-making and execution (see <a href="#_table-regulatory" class="auto internal xref">Table 2</a> for a
-detailed mapping).<a href="#section-1.1-3" class="pilcrow">¶</a></p>
+coordinate across organizational boundaries.  Domains such as
+healthcare, finance, and logistics require structured, auditable
+records of automated decision-making and execution.
+<a href="#_table-regulatory" class="auto internal xref">Table 2</a> in the appendix illustrates how ECTs relate
+to specific regulatory frameworks.<a href="#section-1.1-3" class="pilcrow">¶</a></p>
 <p id="section-1.1-4">This document defines an extension to the WIMSE architecture that
 addresses the gap between workload identity and execution
 accountability.  WIMSE authenticates agents; this extension records