- Data Residency
- Jul 31Enforcement active
- First brownout
- Aug 24Calculating
- Full enforcement
- Sep 25Calculating
Source baseline accepted Aug 8, 2026. Browser dates are planning aids, not a live GitHub status check.
Fleet evidence in. Owner-ready actions out.
Check runner enforcement readiness
Turn redacted runner, ARC, image, bootstrap, label, workflow, and audit evidence into an exact remediation queue.
First result
Runner readiness matrix
Run the checker to classify registration, rolling execution, templates, critical workflows, owners, blockers, and next actions.
- Sources
- 0
- P0
- 0
- P1
- 0
- Version missing
- 0
- Template risks
- 0
- Owner gaps
- 0
| Priority | Runner / source | Version | Registration | Rolling execution | Auto-update / reachability | Image / template | Criticality | Owner / window | Enforcement | Blocker / exact next action |
|---|---|---|---|---|---|---|---|---|---|---|
| No runner readiness result has been generated. | ||||||||||
Version and update check
Registration floor, rolling 30-day exposure, auto-update, reachability, timestamp, and evidence boundaries remain separate.
No version or update evidence classified.
Image, template, and ARC rebuild check
Stale runner bundles can return through images, launch templates, bootstrap code, caches, or autoscaling sources.
No image, template, bootstrap, or ARC source classified.
Critical workflow coverage
Labels and groups are evidence clues only. This page cannot inspect live workflow routing or queued jobs.
Critical dependencies
No critical label or workflow clue classified.
Coverage gaps
Run the checker to identify version, owner, and workflow evidence gaps.
Owner and maintenance queue
Assign a person or team, an approved window, a replacement path, and a fresh verification timestamp.
No owner queue generated.
Brownout readiness checklist
- Freeze a timestamped, redacted fleet and template inventory for the pasted scope.
- Upgrade a canary to the latest supported runner release, not only
2.329.0. - Verify update-service reachability and the chosen automatic or manual update path.
- Recreate the canary from every VM image, container image, ARC, launch template, and bootstrap source.
- Run representative critical-label workflows and record registration, job pickup, completion, and queue behavior.
- Assign owners and approved windows for every blocked source before Aug 24 and again before Sep 25.
Safe command and evidence pack
This page runs nothing. Use approved environment procedures and paste only redacted summaries back into the checker.
Platform-owner ticket
Image / template rebuild checklist
Brownout readiness checklist
Executive / client handoff
Redacted fleet summary
Evidence boundaries that stay visible
Missing evidence remains unknown. A static pasted-text checker cannot prove complete enterprise coverage or live CI execution.
2.329.0supports registration or re-registration, but does not permanently prove execution eligibility.- New runner releases must be installed within 30 days to retain execution eligibility.
- Old runners may fail registration, stop taking jobs, or leave workflows queued or failed.
- GitHub Enterprise Server is not covered by this specific github.com enforcement notice at the accepted source date.