App-safe HK / Shenzhen ops
China 2026HK / Shenzhen ops

Admin

Data Review

What public app data is hydrated, what the server health check verifies, what falls back to static data, and what still requires Mohammed action.

Demo fallback
HydrationPublic app data

49

Visit dossiers

14

Itinerary items

10

Enriched events

15

Dossier links

7

Mission phases

4

Team members

Source files

  • itinerary/master_itinerary.md
  • itinerary/hong_kong_week1_plan.md
  • dashboard/program_phases.csv
  • business/dossiers/*.md
  • dashboard/places.csv

Privacy guard

App data carries no contact identifiers, personal IDs, booking references, or QR payloads. Company intel is district-level and public-source-backed; contact routes stay in the private pack.

No PIINo booking refsHK / Shenzhen corridor
Activation readinessAction required

Configured · connection not yet confirmed

  • Environment variables

    Public + service-role keys present

  • Core schema + standard

    Health check queries the business_visit_data_standards row

  • App-intel + auth tables (0003–0004)

    Not verified by the health check — apply 0003–0004 + reseed (27 tables) for mission phases, dossiers, itinerary intel, and the role model

  • Seed freshness

    Regenerate and reapply china_2026_demo.sql so live data matches the domain dataset

  • Auth shell

    NEXT_PUBLIC_PRIVATE_TIER_ENABLED=true — sign-in active, RLS/membership still unverified

  • Private tier

    Enabled · not verified — Sign-in is active. RLS and membership provisioning still require production verification.

  • RLS posture

    Fail-closed role model in 0004 (owner / team / program_viewer); verification in production still required

Private-tier data (contacts, booking refs, IDs) never ships here — it requires authentication first. This page reads live status only via the server-side service-role key and never claims Supabase is active without a confirmed connection.

Supabase config

Verified

green

Environment variables present

Database reachability

Action required

action

Supabase REST health query failed before returning usable data.

Business visit seed

Not verified

amber

china-2026-business-visit-v0.1

RLS policy mode

Not verified

amber

authenticated-read-only-placeholder; no anonymous or mutation policies are created; production RLS behavior requires manual verification

Business target sources

1

Static fallback rows

Sensitive field guardrail

On

Future ingestion rejects blocked fields

Manual review queue

2

Demo targets below verified confidence

Ingestion dry-run

Dry-run corrections needed

contract

No database writes performed

Dry-run accepted

1

Rows ready for human review

Dry-run rejected

3

Rows blocked before staging

Database writes

0

Dry-run only

Import Gates

Review data source:Demo fallbackSupabase business visit review query failed before returning usable data.

Source labels and confidence are required.

Passport, national ID, payment, and credential fields are blocked.

Supabase writes remain deferred until the ingestion source contract is approved.

RLS starts as authenticated read-only; anonymous and mutation policies are not granted.

Dry-run Rejection Reasons

Demo Missing Source URL

row 2

sourceUrl is required

Demo Private Payload

row 3

Blocked sensitive fields: records.2.paymentCard

Demo Shanghai Out-of-Corridor Lead

row 4

city must stay in the Hong Kong/Shenzhen corridor

Targets Awaiting Verification

Demo Shenzhen Advanced Materials Group

Shenzhen · profiled

medium

Demo Hong Kong Packaging Systems Studio

Hong Kong · source needed

unknown