Let an authenticated repeat client request another trip from published facts while human approval remains required.
Track
Continuity & rebooking
Phase
Repeat-client request
Starts with
Eligible prior trip and published package
Ends with
Timed hold and pending CIS awaiting approval
A repeat client starts from prior-trip context, reviews eligible published packages and deterministic availability, then creates a timed hold that remains pending human approval.
An authenticated client with eligible prior-trip history selects Plan another trip.
This is the key moment: the hold reserves capacity but never confirms a sale without human approval.
Owns the human action and verifies the visible result.
Preserves identity, state, and record boundaries.
Only the authorized client context and actions
Why: complete and verify the human part of the journey
Bounded client, trip, and workflow state
Why: enforce trusted boundaries
Rebooking creates a bounded request and pending CIS; it never invents availability or bypasses human confirmation.