Parent folderOpen Confluence

RWS Architecture article

Automation First

Make automation the default path for repeatable operational work, minimizing manual drift and ad-hoc changes.

  1. Typeprinciple
  2. Statusactive
  3. Domain60-principles
On this page
  1. Principle – Automation First
  2. Summary
  3. Intent
  4. Scope and Applicability
  5. Principles
  6. Per-Domain Implementation
  7. OpenShift
  8. Networking
  9. Storage
  10. Security
  11. Platform
  12. AI

Principle – Automation First

Summary

Make automation the default path for repeatable operational work, minimizing manual drift and ad-hoc changes.

Intent

Reduce human error, accelerate delivery, and ensure consistent enforcement of architectural intent across domains.

Scope and Applicability

Applies to any workflow that is repeatable, policy-driven, or touches shared infrastructure and platform services.

Principles

  • Prefer declarative configuration and reconciliation over imperative manual change.
  • Treat automation pipelines as production systems with versioning, review, and evidence.
  • Design workflows so outcomes are deterministic and verifiable.

Per-Domain Implementation

OpenShift

  • Use GitOps pipelines for cluster and add-on lifecycle management.

Networking

  • Render and deploy device configurations from approved intent models.

Storage

  • Automate provisioning, policy enforcement, and backup scheduling.

Security

  • Automate policy validation and compliance checks as part of delivery pipelines.

Platform

  • Provide standardized automation primitives that domains can reuse safely.

AI

  • Automate AI workload lifecycle (training/inference pipelines, model artifacts, and policy checks) with versioning, review, and evidence.

Exceptions

Manual intervention is permitted only for emergency remediation with documented evidence and follow-up automation.

Related