Skip to content

Activate real trust, safety and administrator operations #127

Description

@zaingulel

Parent

Public-launch activation for #39, #42 and #44, and launch-readiness evidence for #51.

What to build

Operate the real completion, incident, support, administrator and suspension journeys with named authorised staff, approved privacy handling and genuine launch records.

Acceptance criteria

  • Eligible real bookings complete at the correct Iraq-time boundary while cancelled and otherwise ineligible bookings remain excluded.
  • Authorised staff can record real No-Shows and restricted incidents with the approved access, retention, escalation and audit controls.
  • Named administrators can find genuine customer, owner, cottage, booking, refund, review and incident records without crossing tenant or document-privacy boundaries.
  • Every privileged content, exception, suspension and reactivation action requires the correct reason, attribution and immutable audit evidence.
  • Suspension immediately prevents the appropriate new activity, safely resolves pending requests and preserves confirmed commitments and historical evidence.
  • Public support, complaints, incidents, Payment Disputes and reviews remain separate, correctly routed operational records.
  • Representative production-like exercises prove access, escalation, unavailable-channel, safety and privacy failure paths against the exact release candidate.
  • Production fails closed if staffing, access, privacy, retention, breach or support procedures are not approved and exercised.

Blocked by

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified, ready for an AFK agent

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions