Web process
Serves public site, portal, command and APIs only
Internal GCCAP operating surface
This page is retained behind the public client website.
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
Separate GCCAP into production web, ingestion, worker and live-update runtime boundaries so telemetry cannot be delayed or broken by the website layer.
P11 responds directly to the architecture risk that a single Node process cannot carry global aviation cold-chain ingestion, processing, reporting, alerts, agents and client traffic. It creates the runtime split control plane for web process, ingestion service, worker service, live socket/update service, simulation isolation, startup manifests, runtime health checks, service dependencies and deployment boundaries.
StatusInternal / restricted surface. Not part of the public client walkthrough.
GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
Runtime modelWeb + ingestion + workers + live updates
SimulationIsolated from production
CutoverBlocked until deployment evidence
Operational layer
P11 runtime split controls
These controls stop GCCAP from becoming a large demo inside one process and move it toward production service boundaries.
Ingestion service
Receives supplier/gateway telemetry without blocking web users
Worker service
Processes telemetry, reports, alerts, AI and evidence jobs asynchronously
Live update service
Publishes client and command updates without owning ingestion
Simulation isolation
Keeps demos and synthetic data out of production runtime
Startup manifests
Defines each service, dependencies, env vars and health checks
Decision clarity
Why this matters
Claude correctly identified that the long-term GCCAP runtime must not be one web server doing everything. P11 makes that architecture explicit.
Sensor failure isolationBad payloads should not crash the website
Scale independenceIngestion and workers must scale separately from UI traffic
Evidence safetyProcessing jobs must be retryable and auditable
Production claritySimulation must never pollute live telemetry
Deployment disciplineEach runtime needs its own health checks and cutover gates