Docs · Glidepath
Glidepath: admin guide
Documentation for people running this platform - installing it, operating it, and understanding why it’s built the way it is. If you’re an application developer using an already-running platform, see ../user/ instead.
Start here
| Doc | Read this when… |
|---|---|
| architecture.md | You want the current-state system overview. |
| security.md | You want the security model end to end - threat model, RBAC, supply chain, known gaps. |
| installation.md | You’re installing this platform on a cluster. |
| onboarding-mechanics.md | You’re registering a new app onto an already-running platform. |
| adr/ | You want to know why a specific decision was made this way. |
Reference
Grouped by concern - each is a standalone deep-dive, cross-linked from architecture.md wherever relevant.
Chaining & multi-cluster
- chaining.md - the CDEvents broker and TokenReview auth mechanism
- multi-cluster.md - staging/prod topology, ArgoCD-per-cluster
- concepts.md - terminology (Application, flow, stage)
Governance & supply chain
- api.md -
glidepath-api: runs, logs, release records, image evidence and test runs for people, Tower and agents, PipelineRun re-run and cancel, and Flight promote and rollback - contract.md - the generated contract,
glidepath validate, what an agent may change incicd.yaml, and thecicd-validatecheck that holds every app-repo PR to it - governance-stubs.md - the stub→real gate mechanism
- image-signing.md - Fulcio/cosign keyless signing
- signing-pki-cutover.md - the Hangar signing PKI (C-2a): managed Fulcio/Rekor keys, the trusted root, the cutover and its rollback
- provenance-policy.md - SLSA attestation policy
- commit-signing.md - gitsign commit verification
- rootless-builds.md - rootless BuildKit image builds and the Pod Security level they meet
Release & operations
- release.md - the GitOps promotion flow, step by step
- release-state.md - the release record and state machine: how a prod-side fact becomes a release event (ADR-0021)
- release-guardrails.md - adding/removing a release-PR gate; required vs advisory
- github-app.md - the PaC GitHub App: the check-run name (
pipelinesAsCode.applicationName) and the App slug Tower trusts (gateCommentApps) - registries.md - Ground and Flight registries: promotion by digest before the merge, upper-cluster admission, retention (ADR-0029)
- agent-gates.md - agent-identity and agent-scope: every PR checked against Clearance’s record of agent PRs
- agent-definitions.md - the agent-definitions PR check and the agent release: Clearance reviews each definition, the broker opens its pin PR, the deployment gate tiers it
- clearance-gate.md - the deployment gate: every release PR to a protected environment classified 0-3 by Clearance from its rendered diff and cleared by policy or by the app’s owners
- change-management.md - the
itsmgate as a wrapper over the company’s change tool (ServiceNow, or any tool behind a webhook) - catalog-versioning.md - promoting shared catalog changes
- pipelinerun-pruner.md - PipelineRun history cleanup
- stalled-pipeline-detector.md - stuck-flow alerting
- pipeline-performance.md - what a stage costs, the 2026-10 performance review, open levers
Observability
- tracing.md - OpenTelemetry span/trace stitching across stages
- dora-metrics.md - deployment frequency/lead time/CFR/MTTR
- tekton-results.md - long-term PipelineRun/TaskRun archival (logs
- full run history)
- OTEL_AND_CDEVENTS_FLOW.md, OTEL_CDEVENTS_COMPLETE_EXAMPLE.md, OTEL_CDEVENTS_DEBUGGING_GUIDE.md - deep debugging reference for the tracing/CDEvents plumbing
Notifications & secrets
- notifications.md, design-language.md - Slack/GitHub notification content and shared visual language
- secrets-management.md, app-secrets.md - the ClusterSecretStore/ExternalSecrets model
- ephemeral-environments.md - per-branch/PR preview envs
- naming-conventions.md - namespace/resource naming rules
See ../archive/ for the original, unabridged design history these docs and the ADRs were distilled from.