Skip to content

About

Engineering modernization notes for the AI era: manifesto, industry data, delivery capabilities, tooling, and agentic platform access.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

Engineering Modernization

AI has lowered the cost of writing code. It has not lowered the cost of operating bad systems.

This repo is one place for the engineering team to understand what that means and what we are going to do about it.


Contents

Path Start here if you want
Manifesto The beliefs and the bar
Strategy Research, capability areas, tooling, and platform governance
Platform How agents access and operate platform infrastructure
Signals Rolling landscape notes filtered for this work

Reading order for the strategy layer: manifesto, then industry data, then processes, then tooling, then platform strategy.

Reading order for the platform layer: overview, then prerequisites through build sequence in the table below.


Strategy

The "why and what" layer. Research, principles, and organizational patterns.

Document What it is
Manifesto The beliefs that guide how we work: what we prioritize, what we refuse to tolerate, and what modernization means for this team. Start here.
Industry Data Curated research from the 2025-2026 landscape, organized by theme. Every stat has a source. Useful when making the case for delivery infrastructure investment.
Processes The six capability areas of a mature AI-era delivery system — safe change, runtime confidence, guardrails, platform leverage, AI discipline, and human sustainability.
Tooling What to build or adopt, organized by capability area and tier. For tech leads and platform thinkers.
Platform Strategy How to govern the tools teams build with AI — the two-speed model, promotion pipeline, lifecycle tiers, and using AI to govern AI-built tools. For engineering leaders and executives.

Platform

How AI agents access and operate platform infrastructure. For platform engineering teams building or operating a cloud-like environment.

Document What it covers
Overview Stack diagram, access model, the API as governance boundary. Start here.
Prerequisites The 10 things that must exist before any agent operates safely.
Agent Archetypes Consumer, Operator, and Support agents — scope, authority, and governance per archetype.
Identity and Authorization Credential model, Least Privilege vs. Least Agency, policy-as-code enforcement.
Threat Model Prompt injection, blast radius tiers, OWASP and CISA guidance.
Telemetry Unified event schema, what each layer emits, agent action log.
Governance Who owns what, the decision model, exception process, and how the model evolves.
Build Sequence What to build first and possible solution shapes.

Signals

Document What it is
Signals Log Rolling signals from the AI engineering landscape, filtered for relevance to our work. Updated each digest run.

Staying current

The signals log is updated by running the digest sync script:

python3 tools/sync-digest.py

This runs the AI digest tool, copies the raw output to signals/, extracts relevant signals with Claude, and commits everything. Run it whenever you want to pull in a fresh read of what is happening in the landscape.


This is a living reference, not a policy document. If something is wrong or outdated, open a PR.

About

Engineering modernization notes for the AI era: manifesto, industry data, delivery capabilities, tooling, and agentic platform access.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages