Quickstart
Day 1 Operations
What teams should do on the first real working day with GitOpsHQ.
Day 1 Goal
Run one complete and auditable change cycle in a non-production environment: preview -> release -> approval -> execution -> verification.
Morning Checklist
Open active project and confirm environment states (freeze, policy, approval requirements).
Review pending approvals and identify ownership gaps.
Verify diagnostics and runbook entry points are reachable by on-call roles.
Select one low-risk change for the first controlled execution cycle.
First Controlled Change Cycle
- Prepare a scoped change (workload/binding/variable).
- Run preview and confirm impact scope.
- Create release request with clear summary.
- Route through required approvals.
- Execute and validate runtime outcome.
- Confirm audit trace completeness.
Team Handshake Model
- Confirms RBAC and approval policy guardrails are active.
- Confirms production controls are stricter than non-production.
- Owns execution flow and validates release/promotion statuses.
- Escalates permission/policy blockers with evidence, not assumptions.
- Validates incident path readiness (diagnostics + rollback workflow).
- Checks evidence collection for post-incident closure.
- Submits reviewable, scoped change intent.
- Avoids broad unscoped edits in first-day operations.