Operations Center

The seven-stage automation pipeline.

From request to reviewed pull request. Every stage produces artifacts, and any stage can fix, gate or block before the change goes anywhere near production.

Stage by stage, with the evidence each one leaves behind.

1. 0

   Stage 0: Reuse detection

   Existing roles, playbooks and collections are searched and scored before anything is generated. Reuse is preferred over generation.

   • ✓Six-factor similarity scoring across the automation catalog
   • ✓Exact matches returned immediately, near matches extended rather than rebuilt
   • ✓Match confidence reported to the requester

   Evidence

   2 reusable roles found

   similarity scored

2. 1

   Stage 1: Blueprint builder

   A repository and role design is produced before code: structure, variables, tasks, handlers, tests, job template and a documentation plan.

   • ✓Repository structure
   • ✓Role and variable design
   • ✓Handlers and task breakdown
   • ✓Molecule scenarios and documentation plan
   • ✓AWX job template

   Evidence

   Blueprint generated

   repository structure

3. 2

   Stage 2: Quality gate

   Architecture review plus static analysis in one pass: yamllint and ansible-lint, naming, modularity and idempotency expectations.

   • ✓ansible-lint and YAML validation
   • ✓Architecture review against written standards
   • ✓Naming and modularity checks
   • ✓Idempotency expectations

   Evidence

   Lint passed

   2 warnings auto-fixed

4. 3

   Stage 3: Runtime + AWX QA

   Molecule scenarios in disposable containers, then against real managed nodes over SSH and WinRM, then a live AWX job launch. A failure in any phase feeds an automated fix loop.

   • ✓Molecule scenarios in Docker
   • ✓Molecule against real managed nodes (SSH and WinRM)
   • ✓Live AWX job execution, stdout captured
   • ✓Test logs and job artifacts retained

   Evidence

   12 / 12 scenarios passed

   AWX job evidence attached

5. 4

   Stage 4: Hardening

   Security review before a human ever sees the change. This stage can block delivery.

   • ✓Secret detection
   • ✓CVE and dependency review
   • ✓CIS and risky-module checks
   • ✓Secure defaults; secret-manager lookups where configured

   Evidence

   Security clean

   0 critical, 1 medium

6. 5

   Stage 5: Compliance

   Governance gates and evidence retention. Runs in parallel with hardening, and can also block delivery.

   • ✓Data anonymization checks
   • ✓AI governance record and risk classification
   • ✓Privacy and auditability review
   • ✓Evidence retained against the change

   Evidence

   Compliance passed

   evidence retained

7. 6

   Stage 6: Deploy — pull request delivery

   A Git-based pull request carrying the full evidence trail, opened for human review, with the work item updated and artifacts linked. This is the pipeline's result: nothing reaches production without peer review and merge.

   • ✓Pull request opened in your Git platform
   • ✓Full evidence attached to the change
   • ✓Work item transitioned to peer review
   • ✓No automatic production deployment

   Delivery

   PR opened

   awaiting review

Text alternative: seven stages run in order — reuse detection, blueprint builder, quality gate, runtime and AWX QA, hardening, compliance, and deploy. Hardening and compliance run in parallel and either can block. The pipeline's result is stage six: a pull request opened for human review.

Generated evidence

What lands in the pull request.

TODO — confirm final artifact names and retention paths against the product repository before publication.