Single release identity
PAT release proof compares the same branch, commit, build ID, build timestamp, canonical root, start command, auth mode, and git dirty state across build state, health payloads, runtime fingerprint, and launch validators.
Performance Alignment Technology
Release transparency
Runtime proofCurrent PAT release and build transparency.
This page shows the public runtime fingerprint for the currently served PAT build and explains which release fields are validated together.
Last updated: April 28, 2026Trust center
Runtime fingerprint
Release 403cef4:6uVpM1bHla9_vhoenYJbl
- Release ID
- 403cef4:6uVpM1bHla9_vhoenYJbl
- Stable identifier derived from the current commit and build output.
- Branch
- feat/agent-system-phase-0
- Git branch that produced the currently served build.
- Commit SHA
- 403cef4cae5e9d4c9d01cf5651589034f91af1b2
- Full source commit for the runtime fingerprint.
- Build ID
- 6uVpM1bHla9_vhoenYJbl
- Next.js build identifier emitted by the build process.
- Build timestamp
- 2026-06-10T18:31:41Z
- UTC timestamp carried through release-state proof.
- Canonical root
- c2acct-live
- Repository root name only; the full local filesystem path is not exposed.
- Start command
- node .next/standalone/server.js
- Runtime start command expected by the launch validators.
- Auth mode
- github
- Configured authentication mode for the current runtime.
- Build source
- standalone-build
- Build/runtime source type used by release validation.
- Fingerprint seed
- 1ce7099fc69ffd1d0a85704507987021931b5e39184a221d2bf5a155d8c8196d
- Hash input proof tying root, commit, auth, and build source together.
- Git dirty state
- clean
- Clean or dirty source state reported by the startup and release proof chain.
Public-live status
Manual QA is local-only unless a public deployment artifact exists. Public-live release state remains UNVERIFIED without live URL proof.