Engineering-Led, Agent-Accelerated
Humans keep intent; agents execute within bounds
Agents default to "no design up front" unless you say otherwise. When "AI-native" means humans only approve chaos, merge authority is already gone - you are rubber-stamping plausible diffs.
Here's what this piece covers: the agent-as-driver risk, what commit 609d567 (2026-06-18) reframed the same day as the framework import, the governance lattice in invariants.md, and three habits I enforce in hiring and reviews.
Part of Field Notes: agentic delivery. Aligns with the engineering manager values treatise §3.
1. The leadership problem
"AI-native team" often means no specs and no accountability. Throughput without contracts produces unreviewable diffs. Seniors burn weekends reconstructing intent from generated code.
Wrong: "Let the AI drive."
Right: "609d567 same day as import: engineering-led, agent-accelerated - defined in invariants, not marketing."
The anti-pattern is agent-driven delivery - humans as approvers of chaos; agents as the source of product intent.
2. What the git history shows
On 2026-06-18, hours after e55425c, commit 609d567 reframed README and methodology.md: engineering-led delivery with agent acceleration. The lattice later crystallized in docs/methodology/invariants.md so other docs reference one governance model instead of restating it.
| Commit | Role |
|---|---|
e55425c |
Import methodology, standards, skills, gates |
| Naming commits | Clarify what the thing is called for adopters |
609d567 |
Operating model: humans lead; agents accelerate |
That reframe was intentional before wide rollout. Shipping skills without naming who owns merge is how orgs confuse "agent default" with "no design up front."
3. What I built: the governance lattice
The table in invariants.md is the anchor artifact - not a slogan:
| Role | Retains / executes |
|---|---|
| Human principals | Product intent, architecture, specification approval, standards ownership and exceptions, ambiguity resolution, merge and release gates |
| Autonomous agents | Bounded implementation, verification, draft PR packaging, evidence assembly, preparatory audit within approved contracts |
Agents are the default execution substrate - not an auxiliary chat. Throughput without specification and standards discipline is out of scope for the framework. Vibe coding is explicitly not the product.
Delivery progression (short form):
project → architecture → proposals → features → specifications
→ gates → agent implementation → draft PR + audit → human mergeNot every change walks the full chain. Scope determines entry point. Authority does not move: agents may draft and prepare; humans must approve intent documents and merge.
const HUMAN_RETAINS = [
'intent', 'architecture', 'spec_approval',
'standards_exceptions', 'ambiguity', 'merge',
];
const AGENT_EXECUTES = [
'bounded_impl', 'verification', 'draft_pr',
'evidence', 'preparatory_audit',
];
function mayMerge(actor, pr) {
return actor === 'human' && pr.contractApproved && pr.auditPassed;
}4. Named pattern: governance lattice
Governance lattice - humans retain intent, architecture, and merge; agents execute within approved contracts - not agent-driven delivery with humans as rubber stamps.
| Phrase in staff meeting | Meaning |
|---|---|
| Engineering-led | Humans own product risk and merge |
| Agent-accelerated | Agents are default executors under contract |
| Out of scope | Throughput without specs/standards |
What "agent-accelerated" means in practice: Spec → agent implementation → deterministic gates → draft PR → human merge. Not: prompt → 100-file PR → hope the reviewer understands.
What broke: teams hear "agent default" and skip design. The lattice exists so leads can say no - and point at a file, not a vibe. Review routing when codegen outpaces reading is article 14.
5. What I'd do as a lead
Three habits - steal one this month:
- Interview for contract thinking, not prompt cleverness. Ask how they would bound an agent before merge.
- Reward small evidenced PRs over large heroic diffs. Size without a contract is not courage.
- Put
invariants.mdin every staff-engineer onboarding packet. One page; no substitutes.
Further reading
- Previous: Shipping the agentic framework
- Next: Human-in-the-loop PR review
- Framework anchor: commit
609d567· 2026-06-18 ·docs/methodology/invariants.md
