Build pipeline
Track web, ingestion, worker and live-update container build proof.
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
Track container builds, release evidence, staging deployments and rollback proof.
The P21 lab is the internal surface for managing deployment automation, artifact provenance, zero-secret scans, environment drift checks and release evidence packs before managed service cutover.
StatusInternal / restricted surface. Not part of the public client walkthrough.
GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
APIs/api/deployment-pipeline/*
PurposeRelease automation proof
StatusBlocked until external pipeline evidence exists
Risk reducedManual release failure
Operational layer
Lab controls
Use these APIs to manage release evidence without storing provider credentials.
Artifact provenance
Record digests, source references and approval chain evidence.
Health and drift
Track health verification and environment drift checks.
Release evidence packs
Package deployment proof for staging and production go/no-go review.
Governance
No-secret release rule
P21 stores only artifact metadata and proof records. Real deployment credentials stay external.
- Use secret manager references only.
- Scan ZIPs and container artifacts for literal secrets.
- Keep staging and production differences approved.
- Do not approve production without rollback proof.