The short version
Production does not follow the newest branch automatically. Production follows an explicit promotion decision recorded in the corporate release ledger.
Why a Git SHA matters
A Git SHA is an immutable fingerprint for a specific source state. When PayCal approves a release, the approval points at a SHA instead of a vague branch name such as main.
That gives us a precise answer to a practical question: is the running application the same code PayCal Technologies approved?
The four records we compare
| Record | Meaning |
|---|---|
| Release record | The source SHA passed the required local gates. |
| Desired state | The target should run this approved SHA. |
| Deploy receipt | The deploy script checked out and reloaded this SHA. |
| Runtime proof | The running application reports this SHA and health state. |
The release is clean when all four agree.
What public status shows
The public status page shows a redacted summary: product, production status, version, last verified time, and whether runtime matches the approved release. It does not publish raw deployment receipts, server internals, operator identity, or sensitive logs.
Why this helps customers
- Deployments are deterministic: targets deploy exact approved SHAs.
- Rollback points are explicit: last known-good runtime SHA is recorded per target.
- Audit evidence is coherent: approval, deploy, and runtime proof can be compared.
- Operational drift is visible: mismatches are treated as investigation states.