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

Restricted GCCAP operating record retained behind the public website.

Production-readiness phase defines the production database schemas, SQL migrations, tenant isolation constraints, import mappings and verification checks required before GCCAP can run real client telemetry on managed persistence.

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

PhasePost-30 P2

PurposePostgreSQL schema + migration

BoundaryManaged DB still required

Operational layer

What P2 creates

P2 converts the Build 30/P1 control plane into a concrete PostgreSQL migration foundation.

Schema groups

Tenancy, fleet, telemetry, operations, risk, evidence, governance, commercial and ops schema groups.

SQL migrations

Six ordered migration files covering foundations, tenancy, hardware, telemetry, journeys, risk, reporting and governance.

Tenant isolation constraints

Explicit tenant scope, client report visibility and Watchdog publication boundaries.

Verification checks

Row count, packet hash, tenant isolation, report evidence, replay and rollback checks.

Decision clarity

Database cutover gates

GCCAP must clear these before production database migration.

DATABASE_URLConfigured outside the ZIP and pointing to PostgreSQL.

Migration approvalControlled token/approval gate for schema changes.

Object storageEvidence references must resolve to durable object keys.

Tenant isolationClient data isolation tests must pass.

Backup drillRestore path tested before live pilot cutover.

Governance

Commercial position

P2 strengthens GCCAP by moving toward durable evidence infrastructure without pretending local pilot storage is production SaaS.

Build 30 remains the release candidate.
P1 defines production architecture boundaries.
P2 defines PostgreSQL schema and migration controls.
Live client data stays blocked until managed DB, storage, security and supplier feed gates are green.