John Mitchell jlmitch5

Infrastructure Request: Observability Framework Runner

Requestor: John Mitchell Project: Observability Framework Tooling (obsfw) Date: 2026-07-22

Summary

Requesting a persistent runner environment to host the obsfw daily report pipeline, which currently runs on a local macOS launchd job. The pipeline generates multi-outcome observability reports for Ansible by pulling data from Jira, GitHub, GitLab, Slack, and Claude (LLM analysis), then publishes HTML reports to GitLab Pages. See https://nexus-observability-report-becce4.pages.redhat.com/multi-outcome/

The Emerging "AI Delivery Engineer" Role: Industry Evidence

Research into how job descriptions and engineering roles are evolving to match the new reality of AI agent-driven software delivery. Compiled to support the Nexus EM alignment discussion around the Feature Architect / lead dev role.

The First Real Job Posting

Fusion Risk Management posted an AI Agentic Delivery Engineer role (also called "Harness Engineer") at $150K-$165K. The role description:

PDT, Feature Teams, EM role, etc. etc. V2--Addressing feedback

Tried to iterate with the conversation in the wg-ansible-nexus-leads thread

The Two Models at a Glance

graph TB

PDT as a Federation of Feature Teams

The Problem

Tension between current collaborative delivery process and the way AO is working: component teams (PDTs) vs. feature teams (pairs/small groups). Some concern if EMs leave the Feature 3-in-the-Box, who provides the "project manager" glue? And what does the PDT even do now?

The Proposal

The PDT becomes a stable home team — a federation of feature pairs that share a component domain (e.g., Controller). The EM leads the PDT but does not own feature delivery. Feature pairs own their own delivery. The EM provides the connective tissue between features and across teams.

Policy-Based Authorization in Ansible Automation Platform's Automation Orchestrator

How the Automation Orchestrator's authorization model helps enterprises manage multi-tenancy across air-gapped environments

The Problem: Governing Automation Across Isolated Environments

Organizations operating multiple air-gapped environments face a compounding governance challenge. Each isolated instance needs consistent access control, but there's no shared identity plane to enforce it. Teams manually replicate RBAC configurations across environments, leading to drift, over-provisioned access, and audit gaps.

	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="UTF-8">
	<meta name="viewport" content="width=device-width, initial-scale=1.0">
	<title>Nexus GA — Road to Release</title>
	<style>
	:root {
	--rh-red: #EE0000;
	--rh-dark: #151515;

	#!/bin/sh

	################################################################################
	# cleanUpSampleDir.sh
	#
	# Description:
	# Cleans up audio sample directories by:
	# 1. Removing macOS metadata files (.DS_Store, ._* resource forks, etc.)
	# 2. Replacing macOS alias files with their original source files
	#

	// pulled from https://llllllll.co/tags/c/library/18/norns, scrolled down all the way
	// [...new Set([...document.getElementsByClassName("title raw-link raw-topic-link")].map(h => h.innerHTML.toString().toLowerCase().replace(/ \|:\|\[\|\]\|\(\|\)\|\-\|\{\|\}\|\~\|\—\|\.\|_\|,\|!\|\\\|\/\|\&\|\;/g, "") + ` -!- [${h.innerText}](${h.href})`).sort())]

	const library = [
	"13angels -!- [13 angels](https://llllllll.co/t/13-angels/41671/4)",
	"3dpurelua3dlibfornorns -!- [3d: pure Lua 3d lib for norns](https://llllllll.co/t/3d-pure-lua-3d-lib-for-norns/39622)",
	"4bigknobs -!- [4 Big Knobs](https://llllllll.co/t/4-big-knobs/42190/2)",
	"abacus -!- [Abacus](https://llllllll.co/t/abacus/37871/2)",
	"amen -!- [Amen](https://llllllll.co/t/amen/43746/2)",
	"animator -!- [Animator](https://llllllll.co/t/animator/28242/18)",

	--- midcentury modular nye livestream
	-- in1: clock
	-- out1: blades 1 v/oct
	-- out2: blades 2 v/oct
	-- out3: ripples v/oct

	function init()
	input[1]{ mode = 'change'
	, direction = 'rising'
	}

	--- coast_is_moving ~ fm cloud inspired by N KRAMER's ENDLESS
	-- in 1: change jf minimum octave (0 - 5v offset knob)
	-- in 2: change jf maximum octave (0 - 5v offset knob)
	-- elements is a rubbery whistle tone
	-- 1st voice is warps, which FM's elements
	-- out 1: cv 1
	-- out 2: gate 1
	-- 2nd voice is elements
	-- out 3: cv 2
	-- out 4: gate 2