Rename companion spec reference to draft-nennemann-wimse-ect-pol

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

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

@@ -38,9 +38,9 @@ informative:
   RFC8693:
   RFC9421:
   I-D.ni-wimse-ai-agent-identity:
-  I-D.nennemann-wimse-ect-policy-compensation:
+  I-D.nennemann-wimse-ect-pol:
     title: "Policy Evaluation and Compensation Extensions for Execution Context Tokens"
-    target: https://datatracker.ietf.org/doc/draft-nennemann-wimse-ect-policy-compensation/
+    target: https://datatracker.ietf.org/doc/draft-nennemann-wimse-ect-pol/
     date: false
     author:
       - fullname: Christian Nennemann
@@ -103,7 +103,7 @@ ECTs use a directed acyclic graph (DAG) structure to represent task
 dependencies and integrate with WIMSE Workload Identity Tokens (WIT)
 using the same signing model and cryptographic primitives.
 Policy evaluation and compensation extensions are defined in
-{{I-D.nennemann-wimse-ect-policy-compensation}}.  A new
+{{I-D.nennemann-wimse-ect-pol}}.  A new
 HTTP header field,
 Execution-Context, is defined for transporting ECTs alongside
 existing WIMSE headers.  ECTs are a technical building block that
@@ -177,7 +177,7 @@ This document defines:
 - An HTTP header for ECT transport ({{http-header}})
 - Audit ledger interface requirements ({{ledger-interface}})
 - Policy evaluation and compensation extensions are defined
-  separately in {{I-D.nennemann-wimse-ect-policy-compensation}}
+  separately in {{I-D.nennemann-wimse-ect-pol}}
 
 The following are out of scope and are handled by WIMSE:
 
@@ -507,7 +507,7 @@ out_hash:
 ### Compensation and Rollback {#compensation-claims}
 
 Compensation and rollback extensions are defined in
-{{I-D.nennemann-wimse-ect-policy-compensation}}.  The referenced
+{{I-D.nennemann-wimse-ect-pol}}.  The referenced
 parent ECTs may have passed their own "exp" time; ECT expiration
 applies to the verification window of the ECT itself, not to its
 validity as a parent reference in the ECT store.
@@ -545,7 +545,7 @@ they use short names without reverse domain prefixes:
   (e.g., "public", "confidential", "restricted").
 
 Additional extension keys for policy evaluation and compensation
-are defined in {{I-D.nennemann-wimse-ect-policy-compensation}}.
+are defined in {{I-D.nennemann-wimse-ect-pol}}.
 
 ## Complete ECT Example
 
@@ -1013,7 +1013,7 @@ This can contribute to compliance with:
 ## Compensation and Rollback
 
 Compensation and rollback use cases are described in
-{{I-D.nennemann-wimse-ect-policy-compensation}}.  The core
+{{I-D.nennemann-wimse-ect-pol}}.  The core
 ECT mechanism supports compensation through the "par" claim,
 which links a remediation ECT to the original task.
 
@@ -1372,7 +1372,7 @@ the "JSON Web Token Claims" registry maintained by IANA:
 
 Policy evaluation claims and the ECT Policy Decision Values
 registry are defined in
-{{I-D.nennemann-wimse-ect-policy-compensation}}.
+{{I-D.nennemann-wimse-ect-pol}}.
 
 --- back