Deployment run records
Track web, ingestion, worker and live-update staging runs.
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 staging deployment runs, release evidence packs and go/no-go approvals.
The P22 lab is the internal surface for managing staging run records, artifact evidence, health proof, zero-secret scans, drift evidence, rollback rehearsal and staging go/no-go decisions.
StatusInternal / restricted surface. Not part of the public client walkthrough.
GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
APIs/api/staging-deployment/*
PurposeStaging release proof
StatusBlocked until evidence pack is approved
Risk reducedUncontrolled staging/prod cutover
Operational layer
Lab controls
Use these APIs to record staging release evidence without storing provider credentials.
Artifact evidence
Record release digest, source version and scan status.
Health and drift
Track API, database, storage, queue and environment drift proof.
Go/no-go
Compile evidence packs for founder, technical, security and operations approval.
Governance
Evidence-only rule
P22 stores proof records and redacted metadata only. Real provider secrets remain external.
- Use secret manager references only.
- Store checksums and result summaries, not credentials.
- Keep public Watchdog and live supplier feed blocked until approved.
- Do not proceed to production without a passed staging evidence pack.