Reservation Request - Accept Request

[jasonmorais]

Background

The ShareThrift platform enables reservers to submit Reservation Requests for items, services, or classes listed by sharers. When a sharer accepts a Reservation Request, this initiates the reservation period and allows both parties to coordinate the sharing transaction. The business rules and workflow are defined in the BRD/SRD under "Reservation Request – Requested" and "Reservation Request – Accepted."

Task Description

• Implement the acceptance workflow for Reservation Requests:
  • Allow sharers to view incoming Reservation Requests and accept them.
  • Update the Reservation Request status from "Requested" to "Accepted" upon sharer action.
  • Trigger the creation of a message thread between the reserver and sharer for coordinating pickup/return arrangements.
  • Emit domain/integration events for status change and messaging initiation (OpenTelemetry/Azure Monitor).
  • Notify both parties via email when a Reservation Request is accepted.
  • Ensure compliance with business rules: only one accepted request per item for overlapping timeframes; prevent double booking.
  • Update system documentation to clarify the acceptance workflow and notification logic.

Acceptance Criteria

• Sharers can accept Reservation Requests for their listings.
• Accepted requests transition the status to "Accepted" and initiate messaging.
• Both parties receive notifications and are able to communicate.
• Double booking is prevented for overlapping timeframes.
• Logs and metrics are emitted for observability and audit.
• Documentation is updated to reflect the workflow.

References

• BRD/SRD: Reservation Request – Requested, Reservation Request – Accepted
• ADR: OpenTelemetry, Observability
• Messaging initiation and notification requirements
• documents/share-thrift-srd-bronze.md
• documents/share-thrift-brd.md