Tenant separation
Every event, report and dashboard must be scoped to the correct client and site.
Internal GCCAP operating surface
GCCAP does not delete operating records, trial packs, hardware activation surfaces or evidence automation layers. They are preserved for authorised client portal, command-centre and internal operating use while the public website stays clean for airline first impressions.
Open portal accessInternal GCCAP surface
This layer defines the multi-client operating model: tenant separation, client/site registers, private dashboards, internal queues, Watchdog gates and production backend migration path.
StatusInternal / restricted surface. Not part of the public client walkthrough.
Operating view
Private cart status, reports and evidence packs
Operational layer
The first pilot should not create chaos when a second or third client asks to participate.
Every event, report and dashboard must be scoped to the correct client and site.
GCCAP needs a single view of pilots, hardware state, evidence packs, client requests and Watchdog gates.
Laptop/local pilot mode must lead into managed backend, database, storage, authentication and monitoring.
Decision clarity
These foundations prevent early demand from exceeding operational control.
Governance
GCCAP should scale quickly, but never by losing trust or client separation.