Private pilot readiness

Staging deployment, test users, operations, and QA

Prepare ClaimRight GCC for invite-only pilot testing without enabling public launch behavior, payments, government integrations, automatic decisions, or outcome guarantees.

Admin safeguards

ClaimRight GCC provides document-readiness, workflow support, administrative assistance, and submission guidance only. Final decisions belong to the relevant official authority, bank, ministry, or finance institution.

Human-assisted support does not guarantee approval, refund, financing, subsidy, timeline, or outcome.
Government or bank submission is not enabled in this phase and requires explicit customer authorization and legal approval in a later phase.
AI outputs remain advisory, explainable, editable, auditable, and human-reviewable.

Privacy and document handling

  • Upload only relevant documents: Customers should not upload unrelated documents and should remove unnecessary sensitive information where possible.
  • Private document access: Documents must use private storage, authenticated access, short-lived signed access where needed, and no public buckets.
  • File restrictions: Future uploads are limited to PDF, JPG, JPEG, and PNG files with a 10 MB per-file limit until a separate security review changes that policy.
  • Data use boundary: Case answers, document metadata, and notes are for readiness review only and must not be used for unrelated services.
  • Audit/access logs: Access, reviewer actions, quote changes, readiness pack events, and future document handling must be auditable.

Operational safeguards

  • All customer case reads and writes require authenticated ownership or authorized reviewer/admin checks.
  • Reviewer overrides require a reason, previous/new value where applicable, actor, timestamp, and audit log entry.
  • Customer-facing notes and internal reviewer notes must remain separate.
  • Quotes are quotation-only, expire or require re-review in a future workflow, and are not tax invoices or payment requests.
  • Readiness packs must list missing items, risks, customer next steps, and the submission boundary.
  • Rate limiting is a required production control before enabling state-changing endpoints.

Staging readiness checks

Private pilot staging is an invite-only rehearsal. These checks do not enable persistence, payments, government integrations, AI calls, uploads, or public registration.

staging

Environment separation

Ready

Staging environment label is configured.

Supabase connection health

Manual review required

Configuration is present, but live connectivity and the private-pilot safety contract still require verification.

Invite-only pilot access

Ready

Private pilot should be invite-only. Public registration must stay disabled.

Login abuse protection

Ready

The distributed login rate limit and Supabase Auth controls are attested as verified.

Feature flag status

Ready

The approved private-pilot feature matrix is enforced and satisfied.

Upload feature status

Disabled safely

Uploads are disabled, which is safe for the default private pilot rehearsal.

AI classification feature status

Disabled safely

AI classification is disabled, which is safe for the default private pilot rehearsal.

Payment status

Disabled safely

No payment collection, payment gateway, tax invoice, or success-fee collection is enabled.

Government/bank integration status

Disabled safely

No government, authority, bank, finance institution, or automatic submission integration is enabled.

Analytics/event placeholders

Disabled safely

Pilot event names are documented only. No external analytics connection is active.

Environment separation

Local

Developer-only checks, static UI, safe API behavior, and no real data.

Data boundary: Demo data and local test payloads only.

Staging private pilot

Invite-only pilot rehearsal with a separate Supabase project and test users.

Data boundary: Synthetic/demo data first; any real pilot data requires consent, RLS, retention, and deletion readiness.

Future production

Public launch only after compliance, security, source, support, and operational sign-off.

Data boundary: Not enabled by this PR.

Required staging environment groups

Environment identity

NEXT_PUBLIC_CLAIMRIGHT_APP_ENV

Use `staging` only for the private pilot deployment.

Supabase public server client

NEXT_PUBLIC_SUPABASE_URLNEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY

Use a staging Supabase project. Do not reuse production credentials.

Private pilot access

CLAIMRIGHT_ENABLE_PRIVATE_PILOT_ACCESSCLAIMRIGHT_ENABLE_INVITE_ONLY_ACCESSCLAIMRIGHT_ENABLE_PUBLIC_REGISTRATION

Private pilot access should be enabled, invite-only should be enabled, and public registration should remain disabled.

Verified external controls

CLAIMRIGHT_LOGIN_ABUSE_PROTECTION_VERIFIED

Set to true only after the Vercel Firewall rule and Supabase Auth limits pass the controlled verification.

Uploads if explicitly enabled

NEXT_PUBLIC_ENABLE_DOCUMENT_UPLOADSCLAIMRIGHT_DOCUMENT_BUCKETCLAIMRIGHT_ENABLE_STORAGE_SIGNED_UPLOADSCLAIMRIGHT_ENABLE_UPLOAD_METADATA_PERSISTENCE

Uploads may stay disabled. If enabled for staging, use a private bucket and test-only files.

AI classification if explicitly enabled

NEXT_PUBLIC_ENABLE_AI_DOCUMENT_CLASSIFICATIONCLAIMRIGHT_ENABLE_AI_CLASSIFICATION_ADAPTERCLAIMRIGHT_ENABLE_AI_CLASSIFICATION_AUTHZ_CHECKS

AI remains advisory and disabled unless a separate staging review approves it.

Private pilot access controls

  • Private pilot access is invite-only in staging; no public registration is enabled.
  • Pilot users must be tagged as customer, reviewer, or admin before any live role-based access test.
  • Reviewer and admin access must be separated before customer data appears in queues.
  • Customers can only view their own cases after Supabase Auth and RLS verification.
  • No public document access or unauthenticated customer case access is allowed.

Operational documents

These documents define pilot onboarding, reviewer handling, customer support, escalation, deletion requests, and incident reporting. They are required before inviting real pilot users.

Pilot onboarding checklistReviewer SOPCustomer support SOPEscalation SOPData deletion request process placeholderIncident reporting placeholder

Pilot case workflow

1

Customer creates a case

Customer

Customer selects country/service and starts a draft readiness case.

2

Support preference selected

Customer

Customer chooses AI-guided, human-assisted, hybrid, call-back, or future channel preference.

3

Quote estimate viewed

Customer

Customer sees quotation-only package estimate with no payment collection.

4

Documents uploaded if enabled

Customer

Uploads remain disabled unless staging storage, consent, RLS, and scanning gates are approved.

5

Reviewer reviews case

Reviewer

Reviewer records internal notes, customer-facing notes, document status, and escalation reason.

6

Readiness pack placeholder

Reviewer/Admin

Pack remains placeholder or internal summary until audited generation is approved.

7

Customer receives next-step guidance

Customer support

Guidance explains customer-controlled next steps and no outcome guarantee.

Pilot test scenarios

Demo data must remain synthetic and clearly marked. Do not use real customer identifiers, real documents, or real portal references.

UAE National Home VAT Refund

Demo UAE national home builder; no Emirates ID, TRN, invoice, bank, or portal identifiers.

Expected path: Eligibility started, quote estimate viewed, checklist reviewed, missing/unclear invoice items routed to human review.

deadline riskmissing completion certificateinvoice missing supplier TRNcustomer requests human-assisted support

Kuwait Housing / Building Loan Readiness

Demo Kuwaiti applicant with broad property/allocation status; no Civil ID, salary amount, or loan identifiers.

Expected path: Service selected, support preference captured, quote estimate viewed, building permit and salary evidence checklist reviewed.

missing building permitunclear property ownership/allocationguarantor issuespecial applicant status

Bahrain Mazaya / Tas'heel Housing Readiness

Demo Bahraini applicant with broad income band and family status; no CPR, salary amount, bank, or portal identifiers.

Expected path: Program selected, financing readiness reviewed, quote estimate viewed, family/salary/finance documents checked.

unclear income eligibilityprior housing benefit conflictbank financing issuemissing CPR/salary/family documents

QA checklist groups

Customer flow QA

  • Country and service selection is clear.
  • Support preference is captured as a placeholder only.
  • Eligibility text warns against sensitive identifiers.
  • Quote estimate is quotation-only with no payment path.

Reviewer flow QA

  • Queues are placeholder-only unless reviewer auth is enabled.
  • Internal and customer-facing notes remain separate.
  • Override/rejection reasons are required before future persistence.
  • Escalation states are visible for ambiguous or high-risk cases.

Admin flow QA

  • Admin configuration is static unless auth/RLS/audit controls are ready.
  • Reviewer assignment remains placeholder-only.
  • Pricing controls show no payment or invoice issuance.
  • Feature flag status is visible for staging sign-off.

Upload flow QA

  • Uploads are disabled unless explicitly enabled.
  • PDF/JPG/JPEG/PNG and 10 MB guidance is visible.
  • Private access and malware scanning requirements are visible.
  • No public URL, storage path, or signed URL is shown.

RLS/access-boundary QA

  • Anonymous users cannot read customer cases.
  • Customer test user cannot read another customer case.
  • Reviewer test user cannot access admin configuration.
  • Admin test user access is audited before configuration changes.

Mobile QA

  • Pilot, service, dashboard, review, and admin pages have no horizontal overflow.
  • Status badges and disabled buttons wrap cleanly.
  • Long checklist rows remain readable.
  • No compliance text is hidden behind controls.

Analytics placeholders

Event names are internal placeholders only. No external analytics, tracking pixel, or data export is connected.

case_startedeligibility_completedquote_viewedquote_accepteddocuments_uploadedreview_completedreadiness_pack_generated

Remaining public-launch blockers

  • Supabase connection health