Add blog post: The Agent Infrastructure Race

[espennilsen]

New blog post covering this week's agent infrastructure announcements (March 9–14, 2026).

Covers:

• NVIDIA Nemotron 3 Super (hybrid Mamba-Transformer MoE, open weights)
• Stanford OpenJarvis (local-first agent framework)
• Anthropic Claude Agent SDK rename + Code Review launch
• Meta Avocado model delay

Angle: The frontier models have converged. The competition is shifting from model quality to agent infrastructure: tooling, orchestration, efficiency, and local execution.

Sources: Inline links throughout from VentureBeat, Reuters, Stanford, NVIDIA Research, The New Stack, and others.

[reviewbie]

🔍 Correctness Review

📝 Walkthrough

File	Change
blog/the-agent-infrastructure-race.md	New blog post: "The Agent Infrastructure Race" — ~1,400 words covering the week's agent infrastructure announcements (NVIDIA Nemotron, Stanford OpenJarvis, Anthropic Claude Agent SDK, Meta Avocado delay)

Review

No correctness issues found. The post is well-structured and conforms to the project's conventions:

• All required frontmatter fields are present: layout, title, excerpt, date, category, tags, readingTime
• subtitle and featured are optional fields — both are supported by post.njk (subtitle is conditionally rendered; featured doesn't break anything if unused)
• The <!--excerpt--> separator is correctly placed after the lead paragraph
• date: 2026-03-14 matches today's publish date
• layout: post.njk is correct

✅ Approved — ready to merge.

🔒 Security Review

📝 Walkthrough

File	Change
blog/the-agent-infrastructure-race.md	New blog post added — "The Agent Infrastructure Race" (8 min read, 2026-03-14)

Security Review

No security issues found. This PR adds a single static Markdown blog post to the Eleventy site. The file contains only:

• Valid frontmatter (layout, title, excerpt, date, category, tags, readingTime, featured)
• Markdown prose content
• External hyperlinks pointing to legitimate, well-known domains (NVIDIA, Stanford, Reuters, GitHub, Anthropic, VentureBeat, etc.)

There is no user-supplied input, no server-side templating with dynamic data, no credentials or secrets, and no code execution surface introduced by this change. The Eleventy build renders it as a fully static HTML page at build time.

✅ APPROVED — safe to merge.

---

Why did the agent fail the security audit? It had too many open ports and not enough boundaries. Sound familiar?

⚡ Reliability Review

📝 Walkthrough

File	Change
blog/the-agent-infrastructure-race.md	New blog post: "The Agent Infrastructure Race" — a ~1,500-word analysis of the week's agent infrastructure announcements (NVIDIA Nemotron 3 Super, Stanford OpenJarvis, Anthropic Claude Agent SDK, Meta Avocado delay)

Reliability Review

This PR adds a single Markdown blog post. There is no executable code, I/O, resource acquisition, retry logic, or concurrency to evaluate.

Frontmatter completeness check against the project's required fields (layout, title, excerpt, date, category, tags, readingTime): ✅ all present and correctly typed. The <!--excerpt--> separator is present as required. The optional subtitle and featured fields are also valid.

No reliability findings. ✅

---

Why do agent systems fail silently? Because no one implemented a catch block for the existential dread.

[reviewbie]

🔍 Correctness Review

📝 Walkthrough

File	Change
blog/the-agent-infrastructure-race.md	New blog post analyzing the week's agent infrastructure announcements (NVIDIA Nemotron 3 Super, Stanford OpenJarvis, Anthropic Claude Agent SDK rename, Meta Avocado delay). ~1,500 words, category AI, tagged, dated 2026-03-14.

✅ No issues found

The new blog post is correctly structured and passes all content integrity checks:

• Frontmatter: All required fields present — layout, title, excerpt, date, category, tags, readingTime. The optional subtitle and featured fields are also valid; subtitle is rendered in post.njk via {% if subtitle %}.
• Excerpt separator: <!--excerpt--> is present and correctly placed after the lead paragraph.
• Draft flag: Absent, which is correct for a post intended to publish immediately on merge.
• File naming: Follows the <slug>.md convention (no draft. prefix).
• Internal consistency: All technical claims (parameter counts, architecture details, protocol names) are internally consistent throughout the post.

Estimated review effort

1 — single content file, no logic or data transformations involved.

Why did the agent infrastructure race begin? Because the models finally converged — just like my PRs.

🔒 Security Review

📝 Walkthrough

File	Change
blog/the-agent-infrastructure-race.md	New blog post — "The Agent Infrastructure Race" (8 min read, 2026-03-14)

Security Review

This PR adds a single static Markdown blog post. There is no executable code, user input handling, templating logic, authentication surface, or dynamic data flow introduced. From a security perspective, the file is clean:

• No external resources injected — all links are standard [text](url) Markdown with no inline scripts or iframes.
• No sensitive data — no credentials, tokens, or secrets present.
• No unsafe HTML — the post contains no raw HTML blocks that could introduce XSS via the Eleventy render pipeline.
• No path traversal risk — file is placed conventionally under blog/.

✅ Approved — no security findings.

⚡ Reliability Review

📝 Walkthrough

File	Change
blog/the-agent-infrastructure-race.md	New blog post — "The Agent Infrastructure Race"

This PR adds a single new blog post. The file is a pure Markdown content file with no executable code, I/O operations, or runtime logic. There is nothing in scope for a reliability review.

The frontmatter includes all required fields (layout, title, excerpt, date, category, tags, readingTime) and the <!--excerpt--> separator is present as required by the project conventions.

Findings

No reliability findings. This PR adds a static Markdown blog post — there are no error handling paths, resource allocations, retry loops, concurrency concerns, or runtime logic to evaluate.

Estimated review effort

1 / 5 — Single static content file.

Why do agents make great bloggers? Because they never run out of tokens. 🥁

[espennilsen]

🔀 Merge Summary

Strategy	squash
Branch	blog/the-agent-infrastructure-race → main
Commits	2
Changed files	1
Diff	+113 −0

📁 Changed files

• blog/the-agent-infrastructure-race.md (+113 −0)