rcf-lite 0.26.0 → 0.28.0

package/blueprints/application-api-rest/contributions/user-stories/application-api-rest-us-2106.json

@@ -2,7 +2,7 @@
   "usId": "application-api-rest-US-2106",
   "prdId": "PRD-001",
   "reqId": "application-api-rest-REQ-005",
-  "version": "1.0.0",
+  "version": "1.0.3",
   "status": "approved",
   "title": "Auth-class declaration: every endpoint names its class and middleware enforces it",
   "asA": "security reviewer auditing the API surface",
@@ -16,7 +16,8 @@
       "when": "every operation's x-auth-class value is read",
       "then": "each carries exactly one of the four declared values and no other",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2106-2",
@@ -25,7 +26,8 @@
       "when": "contract validation runs",
       "then": "validation fails naming the classless endpoint",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2106-3",
@@ -34,16 +36,18 @@
       "when": "the request is processed",
       "then": "the middleware rejects it and the handler observably does not execute",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2106-4",
-      "description": "Enforcement is driven by the same declaration the spec publishes: changing an endpoint's declared class changes its enforcement with no second edit site.",
+      "description": "Enforcement is driven by the same declaration the spec publishes: changing an endpoint's declared class changes its enforcement with no second edit site. Applying agent sets: the mapping from each operation to one of the four auth classes named on `application-api-rest-REQ-005.description` (public, authenticated user, admin, service-to-service).",
       "given": "an endpoint whose declared class is changed from user to admin",
       "when": "the service is rebuilt and the endpoint called with a non-admin user token",
       "then": "the request is rejected per the new class, and the spec and enforcement agree",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "template"
     },
     {
       "id": "AC-2106-5",
@@ -52,7 +56,8 @@
       "when": "each is submitted to a protected endpoint",
       "then": "responses are 401, 401, and 403 respectively, each with a problem-details body",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2106-6",
@@ -61,7 +66,8 @@
       "when": "auth logic outside the four class middlewares is searched for",
       "then": "none exists; every endpoint's auth behaviour is fully attributable to its declared class",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     }
   ],
   "tacIds": [

package/blueprints/application-api-rest/contributions/user-stories/application-api-rest-us-2107.json

@@ -2,7 +2,7 @@
   "usId": "application-api-rest-US-2107",
   "prdId": "PRD-001",
   "reqId": "application-api-rest-REQ-005",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "approved",
   "title": "Per-class behaviour: the four auth classes each honour their declared contract",
   "asA": "platform operator running the service for multiple caller populations",
@@ -16,7 +16,8 @@
       "when": "requests with and without auth headers are submitted",
       "then": "both succeed with identical behaviour and no resolved identity appears in logs or context",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2107-2",
@@ -25,7 +26,8 @@
       "when": "the burst is submitted",
       "then": "requests beyond the limit receive 429 per the rate-limiting contract",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2107-3",
@@ -34,7 +36,8 @@
       "when": "requests with a valid token, an expired token, and no token are submitted",
       "then": "the valid token resolves an identity available to the handler; the other two receive 401 with the error envelope",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2107-4",
@@ -43,16 +46,18 @@
       "when": "an authenticated non-admin and an authenticated admin each call it",
       "then": "the non-admin receives 403 with the error envelope; the admin succeeds",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2107-5",
-      "description": "Every admin-class request is audit-logged with the acting identity, the endpoint, the outcome, and the request id.",
+      "description": "Every admin-class request is audit-logged with the acting identity, the endpoint, the outcome, and the request id. Applying agent sets: the audit-log destination and retention window applied to admin-class requests.",
       "given": "an admin-class request, successful or rejected",
       "when": "the audit log is read",
       "then": "an entry records identity, endpoint, outcome, and request id",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "template"
     },
     {
       "id": "AC-2107-6",
@@ -61,16 +66,18 @@
       "when": "a correctly signed or mTLS-authenticated peer calls it, and an unauthenticated caller attempts it",
       "then": "the peer succeeds with a service principal and no user identity; the unauthenticated caller receives 401",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2107-7",
-      "description": "Every service-class request is audit-logged with the calling service principal, and service-class traffic is counted under its own rate limit separate from user traffic.",
+      "description": "Every service-class request is audit-logged with the calling service principal, and service-class traffic is counted under its own rate limit separate from user traffic. Applying agent sets: the audit-log destination and the service principal namespace for service-class traffic; the per-service rate-limit tier.",
       "given": "service-class traffic at volume alongside user traffic",
       "when": "audit logs and rate-limit counters are inspected",
       "then": "service calls are attributed to the service principal and limited under the service-class limit, independent of user-class counters",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "template"
     },
     {
       "id": "AC-2107-8",
@@ -79,12 +86,13 @@
       "when": "it is presented to a service-class endpoint",
       "then": "the request is rejected with 403 and the error envelope; the admin token grants nothing outside its classes",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     }
   ],
   "tacIds": [
     "TAC-302-application-api-rest-auth-middleware"
   ],
   "createdAt": "2026-08-19T10:00:00Z",
-  "updatedAt": "2026-08-19T10:00:00Z"
+  "updatedAt": "2026-09-09T00:00:00Z"
 }

package/blueprints/application-api-rest/contributions/user-stories/application-api-rest-us-2108.json

@@ -2,7 +2,7 @@
   "usId": "application-api-rest-US-2108",
   "prdId": "PRD-001",
   "reqId": "application-api-rest-REQ-006",
-  "version": "2.0.0",
+  "version": "2.0.1",
   "status": "approved",
   "title": "Liveness, readiness, and startup probes that tell the orchestrator the truth, at the resolved paths",
   "asA": "platform operator running the service under Kubernetes",
@@ -16,43 +16,48 @@
       "when": "the resolved liveness path is called",
       "then": "it returns 200 against the specified schema, unaffected by the dependency outage",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2108-2",
-      "description": "GET on the resolved readiness path returns 200 only when every declared downstream dependency check (database, cache, queues) passes.",
+      "description": "GET on the resolved readiness path returns 200 only when every declared downstream dependency check (database, cache, queues) passes. Applying agent sets: the declared downstream dependency set (database, cache, queues) the readiness probe registers with.",
       "given": "an instance with all declared dependencies reachable and the readiness path resolved (Kubernetes profile default /ready) or supplied by project configuration",
       "when": "the resolved readiness path is called",
       "then": "it returns 200 with the specified schema listing each check as passing",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "template"
     },
     {
       "id": "AC-2108-3",
-      "description": "GET on the resolved readiness path returns 503 with a body enumerating the failed checks by name when any declared dependency is unreachable.",
+      "description": "GET on the resolved readiness path returns 503 with a body enumerating the failed checks by name when any declared dependency is unreachable. Applying agent sets: the declared dependency set whose names appear in the 503 body when unreachable.",
       "given": "an instance with one declared dependency down and the readiness path resolved as above",
       "when": "the resolved readiness path is called",
       "then": "it returns 503 and the body names the failing check while still listing the passing ones",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "template"
     },
     {
       "id": "AC-2108-4",
-      "description": "GET on the resolved startup path returns 200 only after initialisation (migrations applied, cache warmed, config loaded) completes, and a non-200 with the pending steps before that. The startup path is available when the composed observability-probe-endpoints blueprint enables it via `probeInterface.options.kubernetes.startup.enabled: true` or the project supplies `probeInterface.paths.startup` in configuration.",
+      "description": "GET on the resolved startup path returns 200 only after initialisation (migrations applied, cache warmed, config loaded) completes, and a non-200 with the pending steps before that. The startup path is available when the composed observability-probe-endpoints blueprint enables it via `probeInterface.options.kubernetes.startup.enabled: true` or the project supplies `probeInterface.paths.startup` in configuration. Applying agent sets: the resolved startup-probe path (the Kubernetes profile default `/startup` when enabled through `probeInterface.options.kubernetes.startup.enabled: true`, or a `probeInterface.paths.startup` override), and the enumeration of initialisation steps the pending response names.",
       "given": "an instance mid-initialisation and the same instance after initialisation, with the startup path resolved (Kubernetes profile default /startup when enabled) or supplied by project configuration",
       "when": "the resolved startup path is called in each state",
       "then": "the mid-initialisation call is non-200 naming pending steps; the post-initialisation call is 200",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "template"
     },
     {
       "id": "AC-2108-5",
-      "description": "All three probes sit outside the auth middleware and outside rate limiting: the auth-middleware installer consumes exactly the resolved probe path set (the same list observability-probe-endpoints emits via TAC-1501 getExemptPathSet, or the exact set derived from `probeInterface.paths` in the essentials-alone case), so each probe succeeds with no credentials and is never 401, 403, or 429; adjacent routes never fall under the same exemption.",
+      "description": "All three probes sit outside the auth middleware and outside rate limiting: the auth-middleware installer consumes exactly the resolved probe path set (the same list observability-probe-endpoints emits via TAC-1501 getExemptPathSet, or the exact set derived from `probeInterface.paths` in the essentials-alone case), so each probe succeeds with no credentials and is never 401, 403, or 429; adjacent routes never fall under the same exemption. Applying agent sets: the resolved probe path set the composed application ships (observability-probe-endpoints TAC-1501 getExemptPathSet output or the derived set).",
       "given": "a running instance with the resolved probe path set exposed to the auth-middleware installer",
       "when": "each probe is called with no credentials at sustained frequency AND an adjacent user-traffic route is also called unauthenticated",
       "then": "every probe call is answered on probe semantics alone, never with an auth or rate-limit status; the adjacent route returns the auth middleware unauthenticated response",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "template"
     },
     {
       "id": "AC-2108-6",
@@ -61,16 +66,18 @@
       "when": "info-level logs and endpoint metrics are inspected",
       "then": "probe requests appear in neither, and the dedicated probe-outcome metric carries their results",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2108-7",
-      "description": "The generated OpenAPI document names the three probe surfaces (liveness, readiness, startup) and their resolved paths, plus each probes success and failure schemas and its documented failure mode; the resolved paths are computed at documentation-generation time from the composed observability-probe-endpoints blueprint or from project configuration.",
+      "description": "The generated OpenAPI document names the three probe surfaces (liveness, readiness, startup) and their resolved paths, plus each probes success and failure schemas and its documented failure mode; the resolved paths are computed at documentation-generation time from the composed observability-probe-endpoints blueprint or from project configuration. Applying agent sets: the resolved probe path values named in the OpenAPI document at documentation-generation time.",
       "given": "the generated OpenAPI document produced for a project that has resolved its probe paths",
       "when": "the three probe entries are read",
       "then": "each declares its success and failure schemas and its documented failure mode; every entry path is the resolved path (no legacy literal probe-path prefix appears in the generated document)",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "template"
     },
     {
       "id": "AC-2108-8",
@@ -79,12 +86,27 @@
       "when": "the resolved readiness path is called after restoration",
       "then": "it returns 200 without the process having restarted",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-2108-9",
+      "description": "Given a readiness check whose downstream dependency never responds and a per-check deadline configured on the readiness registry, when the deadline elapses, then the aggregate readiness response is 503 with a body listing that check as `failed: deadline-exceeded` (naming the check id and the configured deadline in milliseconds); liveness continues to answer 200 throughout, unaffected by the readiness-side timeout.",
+      "given": "a readiness check whose dependency will not respond within the configured deadline and a live liveness probe",
+      "when": "the deadline elapses on the pending check",
+      "then": "readiness returns 503 naming the failed check id and the deadline value, and liveness continues answering 200",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-306-application-api-rest-operability",
+        "field": "interfaces[0].name"
+      }
     }
   ],
   "tacIds": [
     "TAC-306-application-api-rest-operability"
   ],
   "createdAt": "2026-08-19T10:00:00Z",
-  "updatedAt": "2026-09-04T00:00:00Z"
+  "updatedAt": "2026-09-09T00:00:00Z"
 }

package/blueprints/application-api-rest/contributions/user-stories/application-api-rest-us-2109.json

@@ -2,7 +2,7 @@
   "usId": "application-api-rest-US-2109",
   "prdId": "PRD-001",
   "reqId": "application-api-rest-REQ-007",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "approved",
   "title": "Cursor pagination with a navigable envelope and enforced limits",
   "asA": "API consumer walking large collections",
@@ -16,7 +16,8 @@
       "when": "a page is requested with cursor and limit",
       "then": "the response conforms to the pagination envelope with items, next, and prev fields",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2109-2",
@@ -25,7 +26,8 @@
       "when": "the collection is walked via next from the first page",
       "then": "every item appears exactly once and the final page's next is null",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2109-3",
@@ -34,7 +36,8 @@
       "when": "it is submitted",
       "then": "the service responds 400 with the declared error envelope rather than best-effort interpretation",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2109-4",
@@ -43,16 +46,18 @@
       "when": "the walk completes",
       "then": "every item that existed throughout appears exactly once",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2109-5",
-      "description": "The declared maximum limit is enforced: a request exceeding it receives 400 with a problem-details body naming the maximum, and a request without a limit receives the declared default page size.",
+      "description": "The declared maximum limit is enforced: a request exceeding it receives 400 with a problem-details body naming the maximum, and a request without a limit receives the declared default page size. Applying agent sets: the declared maximum limit value and the declared default page size per collection.",
       "given": "requests with an oversized limit and with no limit",
       "when": "each is submitted",
       "then": "the oversized request receives 400 naming the maximum; the limitless request returns the default page size",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "template"
     },
     {
       "id": "AC-2109-6",
@@ -61,12 +66,13 @@
       "when": "both responses are compared",
       "then": "only the explicit request carries the total, per the envelope's documented count field",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     }
   ],
   "tacIds": [
     "TAC-304-application-api-rest-resource-layer"
   ],
   "createdAt": "2026-08-19T10:00:00Z",
-  "updatedAt": "2026-08-19T10:00:00Z"
+  "updatedAt": "2026-09-09T00:00:00Z"
 }

package/blueprints/application-api-rest/contributions/user-stories/application-api-rest-us-2110.json

@@ -2,7 +2,7 @@
   "usId": "application-api-rest-US-2110",
   "prdId": "PRD-001",
   "reqId": "application-api-rest-REQ-008",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "approved",
   "title": "Documented filters, one sort convention, and strict rejection of unknown parameters",
   "asA": "API consumer querying collections",
@@ -11,21 +11,27 @@
   "acceptanceCriteria": [
     {
       "id": "AC-2110-1",
-      "description": "Every collection endpoint's filter parameters are declared in the generated spec with their types and accepted values; no undocumented filter is honoured.",
+      "description": "Every collection endpoint's filter parameters are declared in the generated spec with their types and accepted values; no undocumented filter is honoured. Applying agent sets: the filter parameter set (name and type) per collection endpoint.",
       "given": "the generated spec entry for a collection endpoint",
       "when": "its declared filters are compared with the parameters the implementation honours",
       "then": "the sets are identical",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "ownerRef": {
+        "tacId": "TAC-303-application-api-rest-contract-surface",
+        "field": "interfaces[0].name"
+      },
+      "disposition": "template"
     },
     {
       "id": "AC-2110-2",
-      "description": "Sorting uses ?sort=field,-field2: comma-separated keys, leading minus for descending, applied in declared key order.",
+      "description": "Sorting uses ?sort=field,-field2: comma-separated keys, leading minus for descending, applied in declared key order. Applying agent sets: the sortable-key set per resource.",
       "given": "a collection with sortable fields",
       "when": "?sort=fieldA,-fieldB is requested",
       "then": "results order by fieldA ascending then fieldB descending",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "template"
     },
     {
       "id": "AC-2110-3",
@@ -34,16 +40,18 @@
       "when": "a request carries an undeclared query parameter",
       "then": "the service responds 400 with the declared error envelope naming the parameter, and no handler logic runs",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2110-4",
-      "description": "A sort key that is not declared sortable for the resource is rejected with 400 and a problem-details body naming the key and the declared sortable set.",
+      "description": "A sort key that is not declared sortable for the resource is rejected with 400 and a problem-details body naming the key and the declared sortable set. Applying agent sets: the sortable-key set the resource declares.",
       "given": "a collection endpoint",
       "when": "?sort= names an undeclared key",
       "then": "the service responds 400 with the error envelope naming the key and the sortable fields",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "template"
     },
     {
       "id": "AC-2110-5",
@@ -52,7 +60,8 @@
       "when": "a value of the wrong type is submitted",
       "then": "the service responds 400 with the error envelope naming parameter and expected type",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2110-6",
@@ -61,12 +70,13 @@
       "when": "the next cursor is followed",
       "then": "subsequent pages honour the same filter and sort without restating them incorrectly or losing them",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     }
   ],
   "tacIds": [
     "TAC-304-application-api-rest-resource-layer"
   ],
   "createdAt": "2026-08-19T10:00:00Z",
-  "updatedAt": "2026-08-19T10:00:00Z"
+  "updatedAt": "2026-09-09T00:00:00Z"
 }

package/blueprints/application-api-rest/contributions/user-stories/application-api-rest-us-2111.json

@@ -2,7 +2,7 @@
   "usId": "application-api-rest-US-2111",
   "prdId": "PRD-001",
   "reqId": "application-api-rest-REQ-009",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "approved",
   "title": "Problem details everywhere: one error shape on every failure path",
   "asA": "API consumer building error handling once",
@@ -16,7 +16,12 @@
       "when": "the body and content type are inspected",
       "then": "the body carries the five base fields and the content type is application/problem+json",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed",
+      "vendorCitation": {
+        "url": "https://datatracker.ietf.org/doc/html/rfc7807",
+        "verifiedOn": "2026-09-09"
+      }
     },
     {
       "id": "AC-2111-2",
@@ -25,7 +30,16 @@
       "when": "extension fields are compared against the declaration",
       "then": "every observed extension is declared",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "ownerRef": {
+        "tacId": "TAC-303-application-api-rest-contract-surface",
+        "field": "interfaces[0].name"
+      },
+      "disposition": "fixed",
+      "vendorCitation": {
+        "url": "https://datatracker.ietf.org/doc/html/rfc7807",
+        "verifiedOn": "2026-09-09"
+      }
     },
     {
       "id": "AC-2111-3",
@@ -34,7 +48,12 @@
       "when": "the body's status field and the HTTP status line are compared",
       "then": "they are equal",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed",
+      "vendorCitation": {
+        "url": "https://datatracker.ietf.org/doc/html/rfc7807",
+        "verifiedOn": "2026-09-09"
+      }
     },
     {
       "id": "AC-2111-4",
@@ -43,7 +62,12 @@
       "when": "their detail fields are read",
       "then": "the 4xx names the client-side correction; the 5xx exposes the correlation instance and no internals",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed",
+      "vendorCitation": {
+        "url": "https://datatracker.ietf.org/doc/html/rfc7807",
+        "verifiedOn": "2026-09-09"
+      }
     },
     {
       "id": "AC-2111-5",
@@ -52,7 +76,12 @@
       "when": "the request is submitted",
       "then": "the response is a 500 with the declared envelope, not a framework default body",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed",
+      "vendorCitation": {
+        "url": "https://datatracker.ietf.org/doc/html/rfc7807",
+        "verifiedOn": "2026-09-09"
+      }
     },
     {
       "id": "AC-2111-6",
@@ -61,12 +90,17 @@
       "when": "each response is inspected",
       "then": "each carries the declared problem-details envelope with the appropriate 4xx status",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed",
+      "vendorCitation": {
+        "url": "https://datatracker.ietf.org/doc/html/rfc7807",
+        "verifiedOn": "2026-09-09"
+      }
     }
   ],
   "tacIds": [
     "TAC-301-application-api-rest-request-pipeline"
   ],
   "createdAt": "2026-08-19T10:00:00Z",
-  "updatedAt": "2026-08-19T10:00:00Z"
+  "updatedAt": "2026-09-09T00:00:00Z"
 }

package/blueprints/application-api-rest/contributions/user-stories/application-api-rest-us-2112.json

@@ -2,7 +2,7 @@
   "usId": "application-api-rest-US-2112",
   "prdId": "PRD-001",
   "reqId": "application-api-rest-REQ-010",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "status": "approved",
   "title": "Idempotency keys: retries replay, duplicates never apply twice",
   "asA": "API consumer retrying over an unreliable network",
@@ -11,21 +11,27 @@
   "acceptanceCriteria": [
     {
       "id": "AC-2112-1",
-      "description": "The project declares which verb and resource-class combinations require an Idempotency-Key; the declaration is published in the generated spec per operation.",
+      "description": "The project declares which verb and resource-class combinations require an idempotency-key; the declaration is published in the generated spec per operation. Applying agent sets: the declared verb-plus-resource-class combinations that require an idempotency-key. The per-operation `x-idempotency-key` value (`required` or `forbidden`) the OpenAPI generator emits is fixed on TAC-303-application-api-rest-contract-surface.responsibilities[2].",
       "given": "the generated OpenAPI document",
       "when": "operations on non-safe verbs are inspected",
-      "then": "each declares whether Idempotency-Key is required, and every duplicate-harmful operation declares it required",
+      "then": "each declares whether idempotency-key is required, and every duplicate-harmful operation declares it required",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "ownerRef": {
+        "tacId": "TAC-303-application-api-rest-contract-surface",
+        "field": "responsibilities[2]"
+      },
+      "disposition": "template"
     },
     {
       "id": "AC-2112-2",
-      "description": "An operation declared key-required rejects a request without the header: 400 with a problem-details body naming the missing header.",
+      "description": "An operation declared key-required rejects a request without the header: 400 with a problem-details body naming the missing header. Applying agent sets: the set of operations declared key-required.",
       "given": "a key-required operation",
-      "when": "a request without Idempotency-Key is submitted",
+      "when": "a request without idempotency-key is submitted",
       "then": "the service responds 400 with the error envelope naming the header",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "template"
     },
     {
       "id": "AC-2112-3",
@@ -34,7 +40,8 @@
       "when": "the identical request is repeated within the TTL",
       "then": "the original response is replayed and exactly one side effect exists",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2112-4",
@@ -43,7 +50,8 @@
       "when": "the same key arrives with a different body within the TTL",
       "then": "the service responds 422 with the error envelope naming the conflict",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2112-5",
@@ -52,21 +60,23 @@
       "when": "the same key and body arrive concurrently",
       "then": "the second request receives 409 with the error envelope and the side effect applies exactly once",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-2112-6",
-      "description": "The de-duplication cache honours its declared TTL: within it replays occur, after it a reused key is treated as a fresh request, and the TTL value is documented.",
+      "description": "The de-duplication cache honours its declared TTL: within it replays occur, after it a reused key is treated as a fresh request, and the TTL value is documented. Applying agent sets: the de-duplication cache TTL value.",
       "given": "the declared TTL",
       "when": "a keyed request is repeated inside and after the TTL window",
       "then": "the inside repeat replays; the after repeat executes as new; the TTL matches its documentation",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "template"
     }
   ],
   "tacIds": [
     "TAC-301-application-api-rest-request-pipeline"
   ],
   "createdAt": "2026-08-19T10:00:00Z",
-  "updatedAt": "2026-08-19T10:00:00Z"
+  "updatedAt": "2026-09-09T00:00:00Z"
 }