Clean up section titles and fix transaction tokens draft reference

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

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

@@ -80,7 +80,7 @@ informative:
       - org: Cloud Native Computing Foundation
   I-D.ietf-scitt-architecture:
   I-D.ietf-oauth-transaction-tokens:
-  I-D.ietf-oauth-transaction-tokens-for-agents:
+  I-D.oauth-transaction-tokens-for-agents:
 
 --- abstract
 
@@ -399,7 +399,7 @@ kid:
 The ECT payload contains both WIMSE-compatible standard JWT claims
 and execution context claims defined by this specification.
 
-### WIMSE-Compatible Claims
+### Standard JWT Claims
 
 The following standard JWT claims {{RFC7519}} MUST be present in
 every ECT:
@@ -468,7 +468,7 @@ jti:
   expiration window.  The "jti" value MUST be unique across all
   ECTs issued by the same agent.
 
-### Execution Context Claims {#exec-claims}
+### Execution Context {#exec-claims}
 
 The following claims are defined by this specification:
 
@@ -500,7 +500,7 @@ par:
   a root task with no dependencies.  A workflow MAY contain
   multiple root tasks.
 
-### Policy Claims {#policy-claims}
+### Policy Evaluation {#policy-claims}
 
 The following claims record policy evaluation outcomes:
 
@@ -552,7 +552,7 @@ use any policy engine or framework (e.g., OPA/Rego, Cedar, XACML,
 or custom solutions) provided that the evaluation outcome is
 faithfully recorded in the ECT claims defined above.
 
-### Data Integrity Claims {#data-integrity-claims}
+### Data Integrity {#data-integrity-claims}
 
 The following claims provide integrity verification for task
 inputs and outputs without revealing the data itself:
@@ -577,9 +577,10 @@ inp_classification:
 : OPTIONAL.  String.  The data sensitivity classification of the
   input (e.g., "public", "confidential", "restricted").
 
-### Operational Claims {#operational-claims}
+### Task Metadata {#operational-claims}
 
-The following claims provide additional operational context:
+The following claims provide additional context about task
+execution:
 
 exec_time_ms:
 : OPTIONAL.  Integer.  The execution duration of the task in
@@ -594,8 +595,6 @@ model_version:
 : OPTIONAL.  String.  The version identifier of the AI or ML model
   used to perform the task, if applicable.
 
-### Witness Claims {#witness-claims}
-
 witnessed_by:
 : OPTIONAL.  Array of StringOrURI.  Identifiers of third-party
   entities that the issuing agent claims observed or attested to
@@ -610,7 +609,7 @@ witnessed_by:
   claims.  See also {{self-assertion-limitation}} for the security
   implications of self-asserted witness claims.
 
-### Compensation Claims {#compensation-claims}
+### Compensation and Rollback {#compensation-claims}
 
 compensation_required:
 : OPTIONAL.  Boolean.  Indicates whether this task is a
@@ -632,7 +631,7 @@ Note: compensation ECTs reference historical parent tasks via the
 the ECT itself, not to its validity as a parent reference in the
 ledger.
 
-### Extension Claims {#extension-claims}
+### Extensions {#extension-claims}
 
 ext:
 : OPTIONAL.  Object.  An extension object for domain-specific
@@ -1685,7 +1684,7 @@ the "JSON Web Token Claims" registry maintained by IANA:
 | out_hash | Output Data Hash | IETF | {{data-integrity-claims}} |
 | inp_classification | Input Data Classification | IETF | {{data-integrity-claims}} |
 | exec_time_ms | Execution Time (ms) | IETF | {{operational-claims}} |
-| witnessed_by | Witness Identities | IETF | {{witness-claims}} |
+| witnessed_by | Witness Identities | IETF | {{operational-claims}} |
 | regulated_domain | Regulatory Domain | IETF | {{operational-claims}} |
 | model_version | AI/ML Model Version | IETF | {{operational-claims}} |
 | compensation_required | Compensation Flag | IETF | {{compensation-claims}} |
@@ -1782,7 +1781,7 @@ However, "req_wl" cannot form a DAG because:
   no policy evaluation outcomes, and no execution content.
 
 Extensions for agentic use cases
-({{I-D.ietf-oauth-transaction-tokens-for-agents}}) add agent
+({{I-D.oauth-transaction-tokens-for-agents}}) add agent
 identity and constraints ("agentic_ctx") but no execution
 ordering or DAG structure.