Pipelines
Registers local validation, staging candidate, production release and hotfix workflows.
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
Control every release before it reaches clients.
The deployment lab keeps GCCAP release candidates, rollback plans, promotion workflows, build provenance and production blockers visible before live deployment is attempted.
StatusInternal / restricted surface. Not part of the public client walkthrough.
GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
AccessAdmin APIs
ControlsGates + rollback
ReadinessBlocked until CI/CD provider
UseRelease management
Operational layer
Deployment lab controls
Use this page as the internal reference for Build 19 release discipline. APIs are admin-gated under /api/deployment.
Release gates
Tracks what must be true before a release can move forward.
Promotion workflow
Separates local, staging and production promotion logic.
Readiness scan
Keeps production release blocked until provider, registry, rollback and staging controls exist.
Decision clarity
Build 19 API surface
The deployment APIs are built for internal control and future CI/CD integration.
StatsGET /api/deployment/stats
PipelinesGET/POST /api/deployment/pipelines
Release gatesGET/POST /api/deployment/release-gates
ReleasesGET/POST /api/deployment/releases
RollbackGET/POST /api/deployment/rollback-plans
ReadinessGET/POST /api/deployment/readiness