NPSS API Gateway idempotency and distributed write conflict resolution

Direct Answer

The NPSS API gateway's idempotency keys only deduplicate retries that carry the same transaction identifier. When two unique transaction identifiers arrive (i.e., two distinct administrative writes), the gateway does not decide which write wins. Authoritative state is resolved downstream—at the policy enforcement point (PEP) data store or coordination layer. Without the NPSS architecture specification, the exact mechanism cannot be confirmed, but mission‑critical systems typically favor version‑based reconciliation (policy version vectors, change‑set hashes) with audit trails over simple last‑writer‑wins.

Confirmed vs. Likely Behavior

Confirmed (gateway layer)	Likely (data‑store/coordination layer)
Idempotency key guarantees at‑most‑once delivery per key.	Conflict resolution uses version vectors, optimistic concurrency, or a consensus protocol (Raft/Paxos).
Duplicate retries with the same key are dropped before reaching PEPs.	Policy objects may be modeled as CRDTs or use operational transforms for commutative updates.
Gateway does not order or merge concurrent unique writes.	Audit logs and rollback support drive version‑based designs rather than timestamp‑only LWW.

Steps to Verify in Your Environment

1. Obtain the NPSS API Gateway Architecture Guide or Interface Control Document (ICD) for the authoritative conflict‑resolution specification.
2. Check the PEP data‑store documentation (e.g., etcd, Consul, custom DB) for its concurrency control model.
3. Review the idempotency‑key schema: does it embed a policy version, vector clock, or change‑set hash?
4. Run a controlled partition test: have two admin nodes issue concurrent writes with unique transaction IDs and observe the resulting policy state and audit log.

One Diagnostic Detail That Changes the Recommendation

Does the idempotency key schema include a policy version or vector clock field? If yes, the system is designed for version‑based reconciliation; if no, it may rely on last‑writer‑wins or a primary‑node serializer, which risks losing updates during clock drift.

Safe Verification Commands (if you have access)

# Example: fetch the gateway schema documentation (replace with actual path)
cat /opt/npss/docs/api-gateway-idempotency-schema.json | jq '.properties.idempotencyKey.properties'

# Example: check PEP store concurrency settings (etcd example)
etcdctl get /npss/pep/config --prefix | grep -E 'consistency|concurrency|version'

If you cannot access these artifacts, escalate to the NPSS architecture team for the ICD. The gateway alone cannot resolve cross‑node write conflicts; the answer lives in the data‑store layer.