Service catalog
Tracks public website, intake, telemetry, journeys, rules, reports, portal and command centre ownership.
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
Know when GCCAP fails before real clients or sensor feeds are exposed.
Internal system phase creates the observability control layer needed before GCCAP can operate live sensor feeds, client portals, reports, alerts and command centre workflows at production scale.
StatusInternal / restricted surface. Not part of the public client walkthrough.
GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
Monitoringhealth + SLOs
Operationsrunbooks + incidents
Boundarypilot now, production gated
Operational layer
What Build 18 controls
Build 18 does not pretend GCCAP already has a managed SRE platform. It creates the readiness layer that decides whether production monitoring is strong enough for clients and global sensors.
Health checks
Defines uptime, freshness, queue, report, portal and backup checks.
SLOs and runbooks
Defines service objectives and operational response paths for failures.
Production blockers
Blocks scale until external monitoring, logs and alert routing are configured.
Decision clarity
Pilot observability vs production observability
GCCAP can test locally now, but production requires always-on monitoring and response.
HealthDefined local checks
LogsLocal files and audit stores
AlertsRegisters and runbooks
SLOsDraft service objectives
IncidentsPlatform incident register