diff --git a/ipa/general/0132.mdx b/ipa/general/0132.mdx
index 20679a9..eaa5bb0 100644
--- a/ipa/general/0132.mdx
+++ b/ipa/general/0132.mdx
@@ -210,7 +210,7 @@ paths:
 
 ```yaml
 paths:
-  /orders/{orderId}:
+  /orders:
     get:
       operationId: listOrders
       responses:
@@ -1032,6 +1032,7 @@ components:
   schemas:
     OperationResponse:
       type: object
+      required: [status]
       properties:
         status:
           type: string
@@ -1039,8 +1040,8 @@ components:
 ```
 
 <Example.Reason>
-  The OperationResponse schema reports its lifecycle through a single status
-  field whose enum is exactly [PENDING, IN_PROGRESS, SUCCEEDED, FAILED,
+  The OperationResponse schema reports its lifecycle through a single required
+  status field whose enum is exactly [PENDING, IN_PROGRESS, SUCCEEDED, FAILED,
   CANCELED, SUPERSEDED], so a generic client can reason about any operation the
   same way and SUCCEEDED is the single success terminal.
 </Example.Reason>
@@ -1418,6 +1419,7 @@ components:
   schemas:
     OperationResponse:
       type: object
+      required: [operationId, operationType, createdAt, updatedAt]
       properties:
         operationId:
           type: string
@@ -1438,7 +1440,8 @@ components:
   The OperationResponse exposes a stable identifier, a standard operation kind,
   and record timestamps, so generic clients and tooling can identify the
   operation, understand what kind of work it represents, and tell when its
-  status last changed.
+  status last changed. The four core fields are declared required, while
+  `customMethod` stays optional because it applies only to `CUSTOM` operations.
 </Example.Reason>
 
 </Example.Correct>