Skip to content
Back/Harness Engineering

AI Engineering Culture Stack

View in Graph
Updated 2026-09-13
3 min read
662 words

AI Engineering Culture Stack

What it is

The AI engineering culture stack is a pace-layer model for agent-assisted software work: standards are the slow foundation, then architecture, specs, plans, and code as the fastest layer. The reusable insight is that code becomes cheap and volatile when agents can generate it quickly, so the durable leverage moves downward into the layers that preserve judgment, system theory, and alignment.

Why it matters

This reframes AI engineering away from the "software factory" metaphor. The hard problem is not eliminating variance like an assembly line; it is keeping humans and agents aligned on what should be built, why, and under which constraints. Without slow layers, AI-generated code becomes "nobody's theory": runnable output without the shared mental model needed to evolve the system.

For Jean's workflow, this argues for strengthening AGENTS.md, CLAUDE.md, architecture notes, skill rules, absorb logs, and MOCs before expecting agents to reliably execute more autonomous work.

Evidence across sources

Source Evidence Implication
Every — The Culture of AI Engineering Noah Brier maps AI engineering to standards, architecture, specs, plans, and code, using Stewart Brand's pace layers and Peter Naur's "programming as theory building". Agent output quality depends on durable cultural and architectural layers, not only model capability.
AI 简报 2026-06-07 Evening Kieran Klaassen reports writing no code this year yet shipping more, because agents moved his bottleneck from implementation to planning, product taste, and feedback. The leverage point in agentic engineering shifts downward from code to judgment and alignment layers.
AI 简报 2026-06-07 Evening Matt Van Horn's plan-first workflow: 80% planning, code last; plan.md as persistent checkpoint; voice input and contextual compounding across documents and decisions. Fast code generation requires even stronger slow-layer discipline to preserve intent and recover context.
AI Briefing 2026-09-03 Afternoon Addy Osmani shares the claim that AI amplifies existing team culture; OpenAI staff describe low ego, mission orientation, ownership, care, pace, and bias for action. AI speed compounds the operating habits already present. Culture is a routing and verification input, not a separate HR topic.

Open questions

  • This is still a single-source candidate; it needs second-source validation from real team practices or Jean's own OpenClaw/wiki workflow.
  • Where should this stack be enforced in practice: repository rules, skills, tests, MOCs, or periodic reviews?
  • How much of spec should remain prose versus becoming executable tests, schemas, or scripts?
  • When a project grows, which local pattern deserves promotion into a reusable skill or global standard?

2026-09-03 addendum: AI amplifies team culture

Addy Osmani's shared article and OpenAI staff comments in the briefing add a current example to this page. The relevant claim is narrow: AI does not fix weak operating habits. It makes them faster. A team with clear ownership, review norms and mission alignment can compound speed. A team with unclear goals can reach the wrong place sooner.

For agent-assisted engineering, culture therefore belongs in the same stack as specs, plans, tests and verification. It decides whether faster generation produces accepted work, rework, or hidden risk.

Pending Jean review

2026-09-13 evening: AI Engineering 让产品判断进入工程职责

来源:AI Briefing 2026-09-13 Evening

Andrew Ng 的 AI Engineering 技能地图把文化栈向执行侧推进了一层:工程师不仅写实现,还要驱动 build loop、做产品决策、协调相关方,并对端到端结果负责。这里的慢层不是额外流程,而是让高速生成仍能围绕用户问题、风险、预算和验收标准运行的共同语言。

这与本页原有的 standards、architecture、spec、plan、code 分层相接。AI 让 code 层更快、更易变,也让产品判断、用户反馈和高 agency ownership 更频繁地进入工程循环。团队文化因此要规定谁能在规格缺失时做决定,谁收集反馈,以及什么证据才算推进而不是单纯完成任务。

Counterpoints & Gaps

  • 技能地图是 Andrew Ng 的框架性文章,不等于所有团队都应由工程师承担完整产品、商业和协调职责。
  • 更广的职责范围可能增加认知负担,仍需用交付结果和返工数据验证。
  • 文化层的作用难以从模型能力、任务难度和组织结构中单独分离。

Sources (addendum)

Pending Jean review

相关主题入口

Sources

Synthesized from 6 sources

Evolution

1 event
  1. absorbed

    Derived from source material

    This page is currently synthesized from 6 sources.

    From Every — The Culture of AI Engineering, AI Briefing 2026-09-03 Afternoon, 2026-09-03-17-44, 2026-09-13-22-58, 2026-06-07-16-04To AI Engineering Culture Stack
    Sources: raw/newsletters/Every/2026-05-08 The Culture of AI Engineering.md · raw/briefing/AI Briefing/2026-09-03-17-44.md · /Users/jean/Documents/Obsidian Vault/raw/briefing/AI Briefing/2026-09-03-17-44.md · /Users/jean/Documents/Obsidian Vault/raw/briefing/AI Briefing/2026-09-13-22-58.md · raw/briefing/AI Briefing/2026-06-07-16-04.md · raw/briefing/AI Briefing/2026-09-13-22-58.md

Linked from