Quickstart
First Project Workflow
End-user onboarding path from organization setup to first controlled release.
Outcome
By the end of this workflow, teams have a governed project with environments, delivery definitions, release controls, and runtime observability.
Preconditions
- Organization and team structure exist.
- At least one platform operator can manage governance and approvals.
- DevOps/developer contributors are assigned with project-level capabilities.
- Runtime ownership model (who runs rollback, who approves production) is agreed.
First 2-Hour Bootstrap Path
Set active organization context and verify role-specific workspace access.
Create project and initialize delivery repository/workspace.
Attach project environments from organization environment catalog.
Define deploy/version policies and approval thresholds per environment.
Add workloads and bindings, then validate generated delivery preview.
Create first release candidate and route through approval policy gates.
Deploy into non-production environment and confirm runtime health.
Promote, rollback, and audit-link a test change to validate full control loop.
Role-Centered Responsibilities
- Defines org environments, tenant governance, and RBAC defaults.
- Configures approval/break-glass policy guardrails.
- Ensures reusable catalog assets and variable standards are in place.
- Owns project setup, workload/binding topology, release operations.
- Executes promotion and rollback runbooks under approval controls.
- Maintains delivery health and drift visibility.
- Prepares workload intent, variable updates, and release-ready changes.
- Uses preview and diff surfaces before requesting execution.
- Collaborates with approvers for production-scoped actions.
- Owns runtime diagnostics, incident triage, and evidence collection.
- Validates rollback safety and closure checklists.
- Feeds preventive guardrail improvements back to platform teams.