GCCAPCold chain. Clear evidence. Confidence.

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

Rebuild cart journeys before exposing them to clients.

Journey Lab is the internal Internal system phase surface for converting processed telemetry into cart-level operational timelines. It lets GCCAP inspect journey status, rebuild journeys, review breach records, and add manual process events such as dry ice placement while the real integration matures.

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
Internal purposeJourney reconstruction
Current inputBuild 3 processed events + manual process events
Current outputJourney state, breach records, replay timeline

Build 4 operational tool

Cart journey reconstruction lab

Rebuild cart journeys from processed telemetry, inspect soak assessment, stage coverage, breach records, evidence confidence, and add manual operational process events such as dry ice placement.

Admin access

Use the same GCCAP_ADMIN_TOKEN configured for Build 2 and Build 3 admin APIs.

Waiting for server response.

Journey controls

Run this after Intake Lab and Pipeline Lab have received and processed telemetry.


    

    

      
Journey status

      

        Stats load after token is saved.
      

    

    

      
Add manual process event

      
Use this for dry ice placement, loading bay movement, or aircraft handover until operational integrations exist.

      
      
      
      
      
      
      

    

    

      
Recent journeys

      

    

    

      
Exception review queue

      

    

    

      
Replay timeline

      

    

  






  

    
Governance

    
Journey Lab rules

    
Use this lab to prove operational meaning before client-facing portal or report builds consume the data.

  

  
    
    
  1. Enter the admin token locally before querying Build 4 APIs.
  2. Send sample telemetry through Intake Lab, process it through Pipeline Lab, then rebuild journeys here.
  3. Use manual events for dry ice placement, bay handover, or aircraft handover until integrated operational events are available.
  4. Review evidence limitations before using a journey in a client conversation.
  5. Treat this as pilot/development storage; production database, access control, and audit controls come in later builds.
    6.