Add 'Agentic Coding Is an Organisational Design Problem' blog post

[dave1010]

Motivation

• Add a new blog post that reframes “agentic coding” as an organisational design problem and provides practical, actionable guidance rather than model-level advice.
• Align with prior governance and executable-doctrine posts by emphasising verification, policy, and delivery practices that let agents move safely at machine speed.

Description

• Create blog/2026-02-06-agentic-coding-throughput.md containing frontmatter and a structured essay introducing the throughput model and eight constraint areas (task readiness, verification, observability, delivery architecture, communication, governance/InfoSec, human capability, and CI speed).
• The post includes concrete requirements, common constraints, practical enablers, a prioritized list of first actions, and a quick self-audit checklist for teams.

Testing

• No automated tests were run because this is a content-only change.

---

Codex Task

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
wardley-leadership-strategies	Ready	Preview, Comment	Feb 2, 2026 11:18pm

[github-actions]

• Ensure all links in the post are functional and direct to the correct resources.
• Verify consistency in terminology (e.g., "PRD" and "Acceptance Criteria" should have an explanation if used).
• Consider breaking down longer sentences for better readability.
• Check for any potential grammatical errors or awkward phrasing in the text.
• Ensure the quick self-audit section is visually distinct to enhance readability.
• Confirm adherence to the existing blog formatting guidelines (e.g., headings, lists styles).

[github-actions]

• Consider adding a brief summary or conclusion section to reinforce key takeaways from the blog post.
• Ensure all links to previous posts are correctly formatted and functioning in the markdown.
• Review content for consistent use of terminology, especially "agentic coding" and "organisational design."
• Ensure all claims about practices (e.g., "Feature flags with ownership and expiry dates...") are well-supported, possibly with references to relevant studies or examples.
• Check for typos or grammatical errors throughout the document for clarity and professionalism.
• If possible, incorporate visuals or diagrams that could enhance understanding of complex concepts presented.
• Verify that the blog post adheres to any established style guide (if applicable).

LGTM