Add SCITT integration section linking wid to Transparency Services

The ECT workflow identifier (wid) can serve as a correlation point
in SCITT Signed Statements, bridging per-step execution accountability
with end-to-end supply chain transparency.

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

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

@@ -80,6 +80,7 @@ informative:
     date: false
     author:
       - org: Cloud Native Computing Foundation
+  I-D.ietf-scitt-architecture:
 
 --- abstract
 
@@ -1463,6 +1464,27 @@ append-only logs, databases with cryptographic commitments,
 blockchain networks, or any storage providing the required
 properties defined in {{ledger-interface}}.
 
+## SCITT (Supply Chain Integrity, Transparency, and Trust)
+{:numbered="false"}
+
+The SCITT architecture {{I-D.ietf-scitt-architecture}} defines a
+framework for creating transparent and auditable supply chain
+records through Transparency Services, Signed Statements, and
+Receipts.  ECTs and SCITT are naturally complementary: the ECT
+"wid" (Workflow Identifier) claim can serve as a correlation
+identifier referenced in SCITT Signed Statements, linking a
+complete ECT audit trail to a supply chain transparency record.
+For example, in a regulated manufacturing workflow, each agent
+step produces an ECT (recording what was done, by whom, under
+what policy), while the overall workflow identified by "wid" is
+registered as a SCITT Signed Statement on a Transparency Service.
+This enables auditors to verify both the individual execution
+steps (via ECT DAG validation) and the end-to-end supply chain
+integrity (via SCITT Receipts) using the "wid" as the shared
+correlation point.  The "ext" claim in ECTs ({{exec-claims}})
+can carry SCITT-specific metadata such as Transparency Service
+identifiers or Receipt references for tighter integration.
+
 ## W3C Verifiable Credentials
 {:numbered="false"}