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 access

Internal GCCAP surface

Move GCCAP from file-backed pilot state toward managed persistence, durable evidence storage and scalable queues.

Internal system phase is the storage transition layer. It does not pretend a managed database, object store or queue are already provisioned. It defines the operational schemas, raw packet evidence object stores, queue abstractions, migration exports, backup and restore drills, and production blockers required before real global client scale.

Return to public platform Open portal access

StatusInternal / restricted surface. Not part of the public client walkthrough.

GCCAP

Sensor

Gateway

Evidence

Watchdog

Journey intelligenceRepresentative demo

SchemasTenant + telemetry + evidence data model

Storageraw packets + reports + certificates

Queuesingest + processing + report jobs + AI

Operational layer

What Build 16 controls

The managed persistence foundation is the bridge from local JSON/NDJSON files to production-grade operational database, object evidence storage and queue-backed processing.

Operational database schema register

Tracks the tables and key fields GCCAP needs before migrating tenant, device, cart, telemetry, journey, report and audit data.

Object storage abstraction

Defines the raw packet, report export, certificate and replay archive buckets that protect evidence assets.

Queue abstraction

Defines the managed queue responsibilities for telemetry ingest, processing, report generation and AI agent jobs.

Migration exports and restore drills

Creates local migration snapshot capability and backup/restore drill tracking so file-backed state can be moved cleanly later.

Decision clarity

Pilot state vs production storage

Build 16 keeps the distinction explicit so GCCAP does not mistake local files for global production infrastructure.