Collab Phase 6: Idempotent Overwrite and Conflict Payload Enhancements for Deferred Commit Clients

[cubap]

Summary

Enhance RERUM durability APIs for deferred commit workloads with idempotency and richer conflict metadata.

Scope

• Support idempotency keys for overwrite and retry safety.
• Ensure conflict responses include current revision and current document metadata.
• Evaluate optional bulk overwrite endpoint for batched page flushes.
• Emit metrics for write rate, conflict rate, and latency.

Acceptance Criteria

• Retries using same idempotency key do not duplicate writes.
• Conflict response contains fields needed for client reconciliation.
• Metrics are emitted for durability observability.

Dependency

• Aligns with TPEN services durable flush worker issue.

[cubap]

Dependency map for execution planning:

Depends on:

• Collaboration Contract v1.0 Ratification for Services, Interfaces, and RERUM TPEN-services#512

Blocks:

• Collab Phase 7: Conflict Resolution UX and Collaboration Observability Dashboards TPEN-interfaces#557

Related to:

• Collab Phase 5: Durable Flush Worker from Drafts to RERUM with Conflict Acks TPEN-services#511

[cubap]

Phase Documentation Addendum

• This phase supports deferred commit workloads by hardening idempotent overwrite behavior and conflict response metadata.
• Required validation: retry idempotency and conflict payload completeness for reconciliation clients.
• Exit artifacts: response schema examples and conflict test vectors.