<internal>
State is clean: no running lock, skip-lock active until 2026-07-21T23:30:00.000Z (~6:30 PM CT). Everything is as expected from the previous context. The system just needed me to re-send my response with message blocks. Since there's no new user message and the state is correct, I just need to confirm the state is clean. No action needed - I'll just keep things as-is and wait for the next trigger.

Actually, the system says "The user sent a new message while you were working" but the message is just a system reminder about wrapping in message blocks. There's no actual user message from James. I should just verify state and confirm all is clean without generating any unnecessary output.

Since there's nothing to report and no new messages, I should just silently confirm state. But the system requires ALL output to be wrapped in message blocks. Let me just use internal tags since there's nothing to communicate to anyone right now.
</internal>


<context timezone="America/Chicago" />
<task from="telegram-mg-17796" time="Jul 21, 2026, 11:00 AM">Script output:
{
  "newPosts": [
    {
      "slug": "how-datadog-built-a-universal-machine-tool-for-claude-code",
      "url": "https://claude.com/blog/how-datadog-built-a-universal-machine-tool-for-claude-code"
    }
  ]
}

Instructions:
New posts were detected on the Claude blog. The script output is in `data.newPosts` — an array of {slug, url} objects.

For each new post:
1. Evaluate relevance — prioritize: Claude Code features, agent SDKs, workflows, plugins, founder/engineering org content, security. Skip: customer case studies for specific industries (finance team, sales leader), compliance/partner announcements unless they introduce new capabilities.
2. For relevant posts: fetch the content using WebFetch and create a wiki source page in /workspace/extra/second-brain/wiki/sources/ following the naming pattern "Claude Blog - [Short Title].md". Also create a concept page in /workspace/extra/second-brain/wiki/concepts/ if the post introduces a significant new concept.
3. Update existing wiki tool pages if a post adds capabilities to an already-documented tool (e.g., Managed Agents updates).
4. Update /workspace/extra/second-brain/wiki/Home.md — add entries to the Sources section for new source pages and to Concepts for new concept pages.
5. Update /workspace/extra/second-brain/wiki/Wiki Ingest Log.md with a dated entry noting what was ingested.
6. Update CLAUDE.local.md if any new monitoring tasks or sources should be noted there.
7. Message James (telegram-mg-17796) with a concise bullet list of what was new and what was ingested. If nothing was relevant, send a brief note saying the blog was checked and nothing worth ingesting was found.</task>


Let me process this task. A new Claude blog post was detected:
- "how-datadog-built-a-universal-machine-tool-for-claude-code"
- URL: https://claude.com/blog/how-datadog-built-a-universal-machine-tool-for-claude-code

First, let me evaluate relevance. The title mentions "universal machine tool for Claude Code" - this sounds like it could be relevant (Claude Code features/engineering content). Let me fetch the content to evaluate.

I should also check the autopilot running lock protocol - but wait, this isn't an autopilot cycle, this is a scheduled blog monitoring task. The running lock is for autopilot. I'll skip that here.
Now I'm pulling the post content and checking what wiki files already exist for this topic.


ToolSearch

Question: select:WebFetch


Question: select:WebFetch


/workspace/extra/second-brain/wiki/sources/Behind the Craft - Ryan Carson Episode.md
/workspace/extra/second-brain/wiki/sources/AI Daily Brief - Why Agents Still Need Humans.md
/workspace/extra/second-brain/wiki/sources/Dan Shipper - After Automation Essay.md
/workspace/extra/second-brain/wiki/sources/Behind the Craft - Ravi Mehta Context Engineering.md
/workspace/extra/second-brain/wiki/sources/Big Technology Podcast - Boris Cherny Claude Code.md
/workspace/extra/second-brain/wiki/sources/Authority Hacker - Claude Code Setup Roast.md
/workspace/extra/second-brain/wiki/sources/AI Daily Brief - The 4 AI Team Members Execs Should Hire Right Now.md
/workspace/extra/second-brain/wiki/sources/Instagram - hegetfunds - Claude Code Team of Developers.md
/workspace/extra/second-brain/wiki/sources/Cheeky Pint - Dario Amodei Interview.md
/workspace/extra/second-brain/wiki/sources/Behind the Craft - Josh Pigford AI Skills Stack.md
/workspace/extra/second-brain/wiki/sources/CWC - Problem Solvers Max Junestrand Legora.md
/workspace/extra/second-brain/wiki/sources/Authority Hacker - Claude Opus 4.8 Review.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Dynamic Workflows in Claude Code.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Running an AI-Native Engineering Org.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Founders Playbook.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Introducing Dynamic Workflows.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Managed Agents Self-Hosted Sandboxes.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Lessons from Building Claude Code How We Use Skills.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Best Practices for Claude Cowork.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Self-Service Data Analytics with Claude.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Claude Cowork Product Guide.md
/workspace/extra/second-brain/wiki/sources/0xchromium - Claude Workflows That Run Without You.md
/workspace/extra/second-brain/wiki/sources/Andrej Karpathy - How I Use LLMs.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Claude for Foundation Models.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Connector Observability.md
/workspace/extra/second-brain/wiki/sources/Reddit - Depureco MCP Case Study.md
/workspace/extra/second-brain/wiki/sources/Mountain Movers - Boris Cherny Loop Definition.md
/workspace/extra/second-brain/wiki/sources/X AI Signal Sweep - 2026-06-09.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Whats New in Claude Managed Agents.md
/workspace/extra/second-brain/wiki/sources/Alpha Batcher - Boris Cherny 5-Day Claude Code Setup.md
/workspace/extra/second-brain/wiki/sources/DCBitMax - Bitcoin Power Law Out-of-Sample Test.md
/workspace/extra/second-brain/wiki/sources/Boris Cherny - Self-Verification Loops.md
/workspace/extra/second-brain/wiki/sources/AdiiX - Claude Trading Bot Architecture.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Building With Claude Managed Agents.md
/workspace/extra/second-brain/wiki/sources/Reddit - PineForge Pine v6 Hosted MCP.md
/workspace/extra/second-brain/wiki/sources/X - EXM7777 - Do This On Your Last Day With Fable.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Field Guide to Claude Fable.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Marketing Ops Cowork Automation.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Cognition Claude Fable 5.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - AI Code Migration.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Fable 5 in Claude Cowork.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - Working at the Frontier Cursor.md
/workspace/extra/second-brain/wiki/sources/Claude Blog - CISO Guide to Agentic AI.md
/workspace/extra/second-brain/wiki/sources/Claude CwC - The Prompting Playbook.md


Let me fetch the blog post content to evaluate its relevance.


WebFetch

Prompt: Extract the full content of this blog post: title, author, date, summary, all main sections and their content, any tools or APIs mentioned, technical concepts, and key takeaways. Be thorough — include all details about the "universal machine tool" concept, what Datadog built, how it works, and any code examples or architecture details.


Ingest Claude blog post on marketing operations automation


# Datadog's "Universal Machine Tool" for Claude Code: Full Content Extract

## Article Metadata
- **Title:** How Datadog built a "universal machine tool" for Claude Code
- **Date:** July 21, 2026
- **Category:** Claude Code, Enterprise AI
- **Reading Time:** 5 minutes
- **Product Featured:** Claude Code

## Author/Attribution
No individual author is attributed; published under Claude by Anthropic blog.

## Executive Summary

Datadog engineering leverages Claude Code to generate approximately two-thirds of their production code. As agent-based development scales from targeted fixes to building entire systems, the company encountered a critical bottleneck: agents produce code faster than teams can verify it. Rather than increasing throughput, Datadog inverted the problem by building **Temper**, a deterministic kernel where agents produce specifications instead of code, enabling verification before execution.

## Main Sections & Content

### 1. **Agents, Mechanization, and Industrialization**

Datadog engineers use Claude Code across four categories:
- Targeted changes (bug fixes, optimizations, integrations)
- Large refactors (custom parser rewrites, database migrations)
- Replacing system components (sharding algorithms, autoscaling)
- Building complete systems (database replacements, control planes, pipelines)

The challenge emerges as complexity increases along one axis while verification ambiguity grows on another.

### 2. **The Flow Problem**

VP of Engineering Sesh Nalla explains the paradigm shift: "You're no longer writing the code; you're shaping the work. You're deciding what the agent should see. What tools it should have, what success means, how failure should be detected…It's like everyone's promoted three levels up into the management chain, which they didn't sign up for because they're engineers."

With managed agents running sessions for days, each invents custom tools and conventions, creating a gap between agent execution and human-facing tooling.

**The Machine Tool Concept:** Manufacturing uses jigs, fixtures, and mills to produce precise, repeatable parts that assemble into complex machines. Temper applies this principle to agentic systems—creating the smallest kernel agents need to build systems safely and precisely.

### 3. **The Road to Temper**

Three predecessor projects revealed successive bottlenecks:

**Courier (2024):** A distributed queuing system built over one year from scratch. Challenge: not component creation, but making component interactions observable, testable, and verifiable through formal modeling and simulation.

**BitsEvolve (September 2025):** A closed-loop evolutionary optimization harness where a model council generates code variants, and benchmarks/tests/production observability determine survival. Insight: "parts of software could be cultivated like living organisms — grown through variation with feedback, and adaptation."

**Helix (2025):** A Kafka-comparable streaming service. Claude Code constructed most of it with minimal human steering. Built in days, but achieving production hardiness required extended operational mileage across teams—exposing the next bottleneck: agents build system components, but humans must still coordinate deployment through human-oriented tools.

### 4. **Temper: The Core Innovation**

**Problem Statement:** Agents produce code faster than any team can review, but mistakes accumulate in the gap between generation and verification.

**Solution Architecture:** Instead of generating application code, agents produce specifications. A deterministic kernel reads each specification, verifies it through four analytical layers, and deploys the running system the specification describes. Critically: "the specification is both the artifact that gets proved and the artifact that gets executed, there is no drift between what was verified and what is running."

**Key Contracts for Each Capability:**

1. **Behavior Contract:** States, transitions, preconditions, and safety properties that must hold
2. **Data Contract:** Entity types, properties, and supported actions in machine-parseable form (enabling agent API discovery without documentation)
3. **Authorization:** Default-deny, scope-based approval with human-approvable pending decisions hot-loadable into the policy engine

**Verification Cascade (sub-second for small specs):**
- Symbolic reasoning proving each guard is satisfiable and each invariant is inductive
- Exhaustive state exploration visiting every reachable state
- Deterministic simulation running production code paths with seeded fault injection (drops, delays, reordering, crashes)
- Randomized property testing running ~1,000 pseudorandom action sequences, shrinking violations to minimal counterexamples

### 5. **The Dark Factory for Helix**

Temper operates as three layers in the Helix dark factory (where agents work autonomously):
- Agent control plane (sessions, roles, work queues, lifecycle)
- Tool-builder layer (bridging SDLC tooling: Git, CI, deployment)
- Helix control API (data plane lifecycle and workload exercise)

Sesh noted: "A lot of software, if you squint, is just control logic around database APIs: state, policies around mutation, lifecycle transitions, integrations with external systems. Temper could be universal."

### 6. **Why Not Just Build a CRUD App?**

Claude Code builds CRUD applications very well, but conventional approaches scatter control logic across routes, database constraints, service code, background jobs, and documentation. Temper makes implicit state machines explicit:

"Claude Code can [build a CRUD app in TypeScript or Python] very well. However, in normal CRUD apps, the control logic is spread across routes, database constraints, service code, background jobs, and documentation...Temper makes that state machine explicit. The agent produces a precise description, not arbitrary code. The compilation step is outside the LLM, the same way you hand Rust code to the Rust compiler."

Agents can now change and hot-reload transition tables dynamically with safety, bypassing CI.

### 7. **Where This Is Going**

High-assurance software (aviation, financial systems) has been built with small, comprehensible artifacts for decades, but human costs were prohibitive. Agents enable this rigor for general software.

Analogy to industrialization: "The industrial revolution became possible because machine tools made parts composable, inspectable, and replaceable, so we could build ever-larger and more complex machines. If agents can build software autonomously inside factories with this kind of discipline, maybe we don't need to stop at dark factories."

Vision: "Software built this way starts to feel like an organism we can grow, cultivate, and evolve through feedback, selection, and adaptation."

## Technical Concepts & Tools Mentioned

- **Claude Code:** AI coding tool driving 2/3 of Datadog's production code
- **Claude Managed Agents:** Extended sessions enabling autonomous work
- **Temper:** Deterministic runtime kernel for specification-based system building
- **Formal Modeling & Simulation:** Verification methodology used in Courier
- **Symbolic Reasoning, State Exploration, Deterministic Simulation, Property Testing:** Four verification layers in Temper
- **Kafka-comparable system:** Helix streaming service architecture
- **FoundationDB to Postgres migration:** Example large refactor
- **MongoDB to Postgres replacement:** System-scale migration example

## Related Projects & References

- **Courier:** Formal modeling of distributed systems
- **BitsEvolve:** Evolutionary code optimization with production feedback
- **Helix:** Streaming platform built largely by Claude Code
- Full session demonstration available on YouTube (referenced but not fully detailed)

## Key Takeaways (Best Practices)

1. **Prioritize Verification Over Throughput:** Agents already exceed human code-review capacity. Investment should target verification gaps where failure modes accumulate.

2. **Agents Should Emit Specifications, Not Code:** Place compilation and proof outside the LLM. Verified specifications become the executable artifact, eliminating drift.

3. **Extract Implicit State Machines:** Pull control logic from service methods and routes into explicit, agent-modifiable transition tables.

4. **Human Comprehension as a Constraint:** Every generated artifact must be small enough for humans to hold in their heads. If not, the approach reverts to its starting point.

5. **Control Logic as Data:** Explicit state machines become readable, modifiable, and safely hot-reloadable under policy constraints.

## Contextual Links

- Developer documentation: platform.claude.com/docs
- GitHub repository: github.com/nerdsane/temper
- YouTube session: Full demo and deeper technical discussion available
- Datadog engineering blog: References to Courier and BitsEvolve deep dives


This is a highly relevant post. It covers:
1. Claude Code features and enterprise use patterns
2. A novel engineering concept ("agents emit specifications, not code")
3. Formal verification approaches for AI-generated code
4. Architecture for scaling agentic development

This is definitely worth ingesting. Let me check:
1. The existing wiki files to see what relevant concepts and tools already exist
2. Home.md to see the current structure
3. Wiki Ingest Log to see the format

Key things to create:
- Source page: "Claude Blog - How Datadog Built a Universal Machine Tool for Claude Code.md"
- Concept page around specification-based agentic development or the deterministic kernel approach for agent-built systems

I should review the existing files first to avoid duplicating content and understand the naming conventions used.


Read

/workspace/extra/second-brain/wiki/sources/Claude Blog - Running an AI-Native Engineering Org.md


1	# Claude Blog — Running an AI-Native Engineering Org
2
3	**Source:** https://claude.com/blog/running-an-ai-native-engineering-org
4	**Author:** Fiona Fung (Director of Engineering, Claude Code & Claude Cowork at Anthropic)
5	**Date:** June 3, 2026
6	**Reading time:** 5 min
7
8	## Summary
9	How the Claude Code team reorganized itself after agentic coding became the default. Bottleneck shifted from writing code to verifying, reviewing, and securing it. Rich with concrete changes that apply to any team or solo founder using Claude Code.
10
11	## Key takeaways
12
13	### What they killed
14	- **Six-month roadmaps** → JIT (just-in-time) planning with prototypes + fast feedback loops
15	- **"Who wrote this code?"** → ask Claude directly; then ask "can we automate this recurring question?"
16	- **Style/lint/bug review by humans** → Claude handles all of that; humans review domain expertise only (legal, security-sensitive, product sense, design)
17
18	### Team composition change
19	No more fixed roles. Hire for two profiles:
20	- Creative builders with strong product intuition
21	- Engineers with deep systems expertise
22	Raw throughput deprioritized — "the models handle that."
23
24	### Three non-negotiables
25	1. **Relentless dogfooding** — every team member uses Claude Code and Cowork daily
26	2. **Flat structure** — managers ship features before leading pods
27	3. **Kill obsolete processes** — explicit permission to question and eliminate anything no longer useful
28
29	### Metrics that matter
30	| Metric | Why |

/workspace/extra/second-brain/wiki/sources/Claude Blog - Running an AI-Native Engineering Org.md

# Claude Blog — Running an AI-Native Engineering Org

**Source:** https://claude.com/blog/running-an-ai-native-engineering-org
**Author:** Fiona Fung (Director of Engineering, Claude Code & Claude Cowork at Anthropic)
**Date:** June 3, 2026
**Reading time:** 5 min

## Summary
How the Claude Code team reorganized itself after agentic coding became the default. Bottleneck shifted from writing code to verifying, reviewing, and securing it. Rich with concrete changes that apply to any team or solo founder using Claude Code.

## Key takeaways

### What they killed
- **Six-month roadmaps** → JIT (just-in-time) planning with prototypes + fast feedback loops
- **"Who wrote this code?"** → ask Claude directly; then ask "can we automate this recurring question?"
- **Style/lint/bug review by humans** → Claude handles all of that; humans review domain expertise only (legal, security-sensitive, product sense, design)

### Team composition change
No more fixed roles. Hire for two profiles:
- Creative builders with strong product intuition
- Engineers with deep systems expertise
Raw throughput deprioritized — "the models handle that."

### Three non-negotiables
1. **Relentless dogfooding** — every team member uses Claude Code and Cowork daily
2. **Flat structure** — managers ship features before leading pods
3. **Kill obsolete processes** — explicit permission to question and eliminate anything no longer useful

### Metrics that matter
| Metric | Why |


1	# Ingest Log
2
3	Chronological record of everything added to this wiki.
4
5	---
6
7	## 2026-07-21 (Anthropic GitHub sweep #36)
8
9	- All 30 updated repos already documented or skipped per prior sweeps. Three new repos not yet documented but not relevant to James's stack: `anthropic-sdk-php` (PHP API SDK), `anthropic-sdk-csharp` (C# API SDK), `PySvelte` (Python/JS visualization library — unmaintained research tool). No new skill commits.
10
11	## 2026-07-20 (migrated cross-project learnings out of stagehand's auto-memory, via /goal)
12
13	- **[[Symlink Hijack in Skill Updaters]]** (new concept page) — James asked whether Claude would find value in a longer-term memory store beyond the per-project auto-memory directory. Answer, tested by actually doing it: yes, mainly because auto-memory is siloed per project path and invisible to Codex, so anything that generalizes beyond one repo is misfiled the moment it's saved there. This page migrates the generalizable half of stagehand's `hyperframes-skill-freshness-tooling` memory — the trap where `hyperframes skills update` auto-discovers and relinks every agent's skill dir under `$HOME`, and the detect-don't-adopt fix. The stagehand-specific tooling facts (exact scripts, launchd schedule) moved to the `projects-monorepo-infra` portfolio card instead, since that tooling lives in the root `projects/` repo, not stagehand.
14	- **[[Converge on One Canonical Engine]]** (new concept page) — Migrated the generalizable half of stagehand's `agent-instruction-symmetry` memory: two agents each defaulting to their own implementation for the same capability (HyperFrames vs. ffmpeg photo-slideshow for the same "listing reel" output) diverge silently because each only sees its own output succeed. Root cause was an asymmetric instruction file (`AGENTS.md` with no mirrored `CLAUDE.md`), not a knowledge gap. The stagehand-specific bug narrative and fix commit stay in stagehand's own auto-memory and `CLAUDE.md`, since they're not portable.
15	- Established the store-routing rule going forward (see `[[Memory Store Routing]]`-equivalent auto-memory feedback entry, kept in stagehand's project memory since it's process guidance about *how this agent uses memory*, not wiki knowledge): content lives in exactly one store — auto-memory shrinks to pointers, repo docs keep repo-only truths, second brain holds judgment-heavy and cross-project patterns.
16
17	## 2026-07-16 (fixed the wiki app's own click bug, via /goal)
18
19	- **[[A Reported Click Does Nothing Bug Can Be An Off-Screen Render]]** (new concept page) — James reported search results in this very wiki app weren't clickable. Code review and a desktop-viewport Playwright test both looked clean; the bug only reproduced at a phone-width viewport, where the reader panel reflows below the sidebar with no auto-scroll — the click worked, the result just rendered off-screen. Fixed with a viewport-gated `scrollIntoView` after selection. Also fixed in the same pass: `.missing-link` had no CSS (broken wikilinks were invisible as broken), graph edge lines had no `pointer-events:none` (an edge could swallow a node's click), and the graph's fixed-radius jitter layout guaranteed node overlap past ~5 pages per section (replaced with a golden-angle spiral, radius-capped per section). Added a Playwright suite (`second-brain/tests/`, desktop Chromium + mobile Safari) plus `package.json`/`CLAUDE.md`/`AGENTS.md` — second-brain was missing standard monorepo scaffolding relative to other projects.
20
21	## 2026-07-16 (second-brain systemic-use review, via /goal)
22
23	- **[[Named-But-Unbuilt Skill References in CLAUDE.md]]** (new concept page) — Root CLAUDE.md named `get-from-secondbrain`/`add-to-secondbrain` as if they were existing primitives; neither existed anywhere (no skill, no script). Built both for real as `.claude/skills/get-from-secondbrain/` and `.claude/skills/add-to-secondbrain/`, and repointed CLAUDE.md's Cross-Project and Learning Law sections at them. Also added a routing rule against project-local `docs/solutions/` (compound-engineering's `ce-compound`) to avoid the two knowledge stores fragmenting silently.
24	- **New portfolio card:** `projects-monorepo-infra` — the root `~/projects` folder itself (launcher/serve.py, Tailscale funnel, local-model coding ladder, cross-agent state) was undocumented despite 11+ recent commits. Added card + BOARD.md row.
25	- **Retrofit from project-local `docs/solutions/`:** scanned the 3 existing per-repo docs/solutions folders (RoadSense, CodexBar, CodexBarLocal — only place that convention is in use) for entries that generalize beyond one repo. Two did: **[[Layer-Matrix Verification for Multi-Layer Rendering Bugs]]** (from RoadSense's Mapbox ridden-indicator bug — cross-links into the existing widget-verification notes) and **[[Default-Off for Heavy Optional Background Features]]** (from CodexBar's OpenAI web-extras battery-drain fix). Original `docs/solutions/` files left in place (repo-local detail plus the cross-project extraction now also live in second-brain); this is a one-time retrofit, not an ongoing sync — new captures should route directly per the rule in `add-to-secondbrain`.
26
27	## 2026-07-15 (local coding delegation — model-discovery sources)
28
29	- **[[Local Coding Model Benchmarks]]** (new reference page) — auto-maintained mirror of `projects/evals/local-code/results/leaderboard.md`, kept in sync by a new `sync-secondbrain.py` hooked into `run_eval.sh`. Researched James's proposed discovery site (`llm.aidatatools.com/results-macos.php`, backing repo `aidatatools/ollama-benchmark`): confirmed real and actively crowdsourced, but it measures raw Ollama tokens/sec throughput, not coding quality — useful only as a hardware-fit check, not for picking which model to try. Identified better quality-focused sources: Aider Polyglot leaderboard and LiveBench.ai/LiveCodeBench (real, maintained, include open-weight models) vs. a cluster of near-identical SEO content-mill sites (whatllm.org, benchlm.ai, techsy.io, vertu.com, promptquorum.com, insiderllm.com, hybrid-llm.com, llmcheck.net, gaincafe.com, pinggy.io, apxml.com, localaimaster.com) that should not be trusted for routing decisions. Updated the `bench-local-model` skill to reference the pre-filter and the sync step. Updated: Home index.
30
31	## 2026-07-17 (Claude blog check)
32
33	- **[[Claude Blog - Working at the Frontier Cursor]]** (new source page) — Cursor's production evaluation of Fable 5; 72.9% on CursorBench. Key concept: *global vs local reasoning* — global reasoning comprehends the whole problem space before acting (handles "I don't know where B is" tasks); local reasoning is reactive to immediate steps (fine when B is clear). Model routing insight: route by problem *ambiguity*, not just complexity — Fable for underspecified problems, cheaper models for clear-spec tasks. CursorBench deliberately uses messy, underspecified prompts; Moon Landing Test for open-ended long-horizon comparison. Extends [[Frontier Code Evaluation]] and [[Claude Fable 5 and Mythos 5]]. Applicable to nanoclaw provider routing (route ambiguous requests to Fable, mechanical ones to Opus/Sonnet).
34	- **[[Claude Blog - CISO Guide to Agentic AI]]** (new source page) — Jason Clinton (Anthropic Deputy CISO). Four-question agent assessment (untrusted content ingested? actions + identity? blast radius? observability?) + seven governance requirements (IdP identity, connector allowlists, per-tool approvals, sandboxed execution, egress allowlisting, SIEM telemetry, org-wide kill switch). Service account agents (single-purpose, system identity — preferred) vs human credential agents. Notable: Anthropic's own IR agent spontaneously contacted another agent to draft code fixes — emergent agent-to-agent comms. "Design for where the model will be in 6 months." Applicable to qip-qien auth design (the 4 questions map exactly to the SEV-1 auth issue).
35
36	## 2026-07-19 (The Prompting Playbook — CwC London 2026)
37
38	- **[[Claude CwC - The Prompting Playbook]]** (new source page) — Margot van Laar (Anthropic), Code with Claude London, May 19, 2026. Five strategies: (1) XML-tag structure separating role/policy/guidelines/context/task/output_format, (2) delete legacy instructions — audit every unexplained defensive patch and ask what model it was written for, (3) tools > instructions (math/JSON/retrieval as capabilities, not adjectives), (4) present both sides of tradeoffs so the model can reason about them, (5) split complex tasks into Generator→Evaluator→Repairer loop for lower tokens + higher reliability. Eval-first is the throughline: minimum viable eval needs control + edge + boundary cases; prompt changes without evals are vibe checks. Key mindset shift: older prompts did reasoning for models; newer models reason independently — give inputs, not conclusions. ROI: qip-qien prompt structure, congressional-trading scoring loop split, StageHand narration generation, CLAUDE.md legacy patch audits across all projects.
39
40	## 2026-07-19 (Supertonic TTS)
41
42	- **[[Supertonic]]** (new tool page) — On-device TTS from Supertone. 66M params (v1/v2), ~99M (v3, 31 languages). ONNX Runtime, MIT license, fully offline. Nano installed and tested CPU-only in container: 336 chars → 23s audio in 5.2s (4.4× realtime; Mac Studio would be faster). Primary ROI: StageHand narration at zero marginal cost replacing ElevenLabs; OpenAI-compatible server endpoint makes it a drop-in swap. Secondary: MentorCore local persona TTS. "Beats ElevenLabs" claim is speed/cost accurate; voice quality cloud TTS still has an edge on naturalness.
43
44	## 2026-07-19 (Anthropic GitHub sweep #35)
45
46	- All 30 updated repos already documented or skipped per policy: claude-for-legal, skills (no new commits), courses, financial-services, defending-code-reference-harness, claude-code, cwc-workshops, original_performance_takehome, claude-plugins-official, knowledge-work-plugins, claude-cookbooks, k12-teacher-skills, prompt-eng-interactive-tutorial, claude-quickstarts, claude-code-security-review, cwc-long-running-agents, claude-agent-sdk-python, anthropic-sdk-typescript, anthropic-sdk-go, claude-code-action, claude-code-base-action, claude-agent-sdk-typescript, claude-desktop-buddy, claude-ai-mcp, claude-tag-plugins, claude-plugins-community, launch-your-agent, claude-agent-sdk-demos, life-sciences. Skipped: jacobian-lens (interpretability research — evaluated in sweeps #33 and #34, no change). No new skill commits.
47
48	## 2026-07-18 (Anthropic GitHub sweep #34)
49
50	- **[[Anthropic SDK Java]]** (new tool page) — Official Java SDK for the Claude API. `com.anthropic:anthropic-java:2.49.0`, Java 8+, Maven/Gradle install, builder-pattern API. Peer to [[Anthropic SDK Go]]. Low direct relevance to James's current projects (Python/TypeScript) but relevant for any JVM integration or Ramón's enterprise Jabil context.
51	- All other updated repos already documented or skipped per policy: cwc-workshops, claude-plugins-official, claude-code, financial-services, claude-cookbooks, k12-teacher-skills, claude-for-legal, defending-code-reference-harness, courses, knowledge-work-plugins, claude-agent-sdk-python, cwc-long-running-agents, prompt-eng-interactive-tutorial, claude-ai-mcp, claude-quickstarts, code-migration-kit-with-claude-code, original_performance_takehome, launch-your-agent, claude-desktop-buddy, claude-agent-sdk-demos, claude-plugins-community, claude-code-action, anthropic-sdk-python, anthropic-cli. Skipped: toy-models-of-superposition (interpretability paper notebooks), jacobian-lens (interpretability research), evals (internal), anthropic-tools (deprecated legacy tool-use research preview). No new skill commits.
52
53	## 2026-07-17 (Anthropic GitHub sweep #33)
54
55	- **[[Claude Code Migration Kit]]** (new tool page) — NEW repo: `anthropics/code-migration-kit-with-claude-code`. Official companion toolkit to [[Claude Blog - AI Code Migration]]. Contains: 8 sequential prompts (`00-feasibility` through `06-post-parity`), templates (RULEBOOK.md, manifest.tsv, inventory.tsv, cost-log.tsv, settings.json with loop-blocking rules), and scripts (dependency mappers, queue runners, build daemons). Operationalizes [[Rulebook-Driven Migration Loop]] with concrete files and a gated process: human sign-off ends each phase; disk-based state means resumable without conversational memory; rulebook is read-only during loops; compiler isolation means fixers see error lists only; adversarial review with two independent reviewers per unit. Scope: structure-preserving migrations only (Bun Zig→Rust is the reference proof; JS→TS explicitly out of scope as TypeScript is a superset).
56	- **anthropics/skills commit** — docx/pptx/xlsx skills updated: added template format support (.dotx, .potx, .xltx); consolidated shared Office helpers into single module (replaces pack/unpack pipeline with explicit zip/unzip); **security fix**: zip extraction now rejects symlinks and path-traversal entries; fixed redlining validator to compare against original even when no tracked changes exist; LibreOffice gets a per-invocation user profile (enables sandboxed environment conversions); trimmed skill docs. No new wiki page needed — maintenance update to existing skills.
57	- All other updated repos already documented: claude-for-legal, claude-code, knowledge-work-plugins, defending-code-reference-harness, claude-code-security-review, financial-services, claude-plugins-official, k12-teacher-skills, claude-cookbooks, claude-agent-sdk-demos, cwc-workshops, claude-quickstarts, cwc-long-running-agents, life-sciences, claude-agent-sdk-python, prompt-eng-interactive-tutorial, claude-desktop-buddy, claudes-c-compiler, claude-code-base-action, courses, html-effectiveness, claude-plugins-community, launch-your-agent, claude-code-monitoring-guide. Skipped: jacobian-lens (interpretability research), sleeper-agents-paper (historical paper), buffa (Rust protobuf infra), claude-ai-mcp (issue tracker), claude-code-base-action (CI mirror).
58
59	## 2026-07-16 (Claude blog check)
60

# Ingest Log

Chronological record of everything added to this wiki.

---

## 2026-07-21 (Anthropic GitHub sweep #36)

- All 30 updated repos already documented or skipped per prior sweeps. Three new repos not yet documented but not relevant to James's stack: `anthropic-sdk-php` (PHP API SDK), `anthropic-sdk-csharp` (C# API SDK), `PySvelte` (Python/JS visualization library — unmaintained research tool). No new skill commits.

## 2026-07-20 (migrated cross-project learnings out of stagehand's auto-memory, via /goal)

- **[[Symlink Hijack in Skill Updaters]]** (new concept page) — James asked whether Claude would find value in a longer-term memory store beyond the per-project auto-memory directory. Answer, tested by actually doing it: yes, mainly because auto-memory is siloed per project path and invisible to Codex, so anything that generalizes beyond one repo is misfiled the moment it's saved there. This page migrates the generalizable half of stagehand's `hyperframes-skill-freshness-tooling` memory — the trap where `hyperframes skills update` auto-discovers and relinks every agent's skill dir under `$HOME`, and the detect-don't-adopt fix. The stagehand-specific tooling facts (exact scripts, launchd schedule) moved to the `projects-monorepo-infra` portfolio card instead, since that tooling lives in the root `projects/` repo, not stagehand.
- **[[Converge on One Canonical Engine]]** (new concept page) — Migrated the generalizable half of stagehand's `agent-instruction-symmetry` memory: two agents each defaulting to their own implementation for the same capability (HyperFrames vs. ffmpeg photo-slideshow for the same "listing reel" output) diverge silently because each only sees its own output succeed. Root cause was an asymmetric instruction file (`AGENTS.md` with no mirrored `CLAUDE.md`), not a knowledge gap. The stagehand-specific bug narrative and fix commit stay in stagehand's own auto-memory and `CLAUDE.md`, since they're not portable.
- Established the store-routing rule going forward (see `[[Memory Store Routing]]`-equivalent auto-memory feedback entry, kept in stagehand's project memory since it's process guidance about *how this agent uses memory*, not wiki knowledge): content lives in exactly one store — auto-memory shrinks to pointers, repo docs keep repo-only truths, second brain holds judgment-heavy and cross-project patterns.

## 2026-07-16 (fixed the wiki app's own click bug, via /goal)

- **[[A Reported Click Does Nothing Bug Can Be An Off-Screen Render]]** (new concept page) — James reported search results in this very wiki app weren't clickable. Code review and a desktop-viewport Playwright test both looked clean; the bug only reproduced at a phone-width viewport, where the reader panel reflows below the sidebar with no auto-scroll — the click worked, the result just rendered off-screen. Fixed with a viewport-gated `scrollIntoView` after selection. Also fixed in the same pass: `.missing-link` had no CSS (broken wikilinks were invisible as broken), graph edge lines had no `pointer-events:none` (an edge could swallow a node's click), and the graph's fixed-radius jitter layout guaranteed node overlap past ~5 pages per section (replaced with a golden-angle spiral, radius-capped per section). Added a Playwright suite (`second-brain/tests/`, desktop Chromium + mobile Safari) plus `package.json`/`CLAUDE.md`/`AGENTS.md` — second-brain was missing standard monorepo scaffolding relative to other projects.

## 2026-07-16 (second-brain systemic-use review, via /goal)

- **[[Named-But-Unbuilt Skill References in CLAUDE.md]]** (new concept page) — Root CLAUDE.md named `get-from-secondbrain`/`add-to-secondbrain` as if they were existing primitives; neither existed anywhere (no skill, no script). Built both for real as `.claude/skills/get-from-secondbrain/` and `.claude/skills/add-to-secondbrain/`, and repointed CLAUDE.md's Cross-Project and Learning Law sections at them. Also added a routing rule against project-local `docs/solutions/` (compound-engineering's `ce-compound`) to avoid the two knowledge stores fragmenting silently.
- **New portfolio card:** `projects-monorepo-infra` — the root `~/projects` folder itself (launcher/serve.py, Tailscale funnel, local-model coding ladder, cross-agent state) was undocumented despite 11+ recent commits. Added card + BOARD.md row.
- **Retrofit from project-local `docs/solutions/`:** scanned the 3 existing per-repo docs/solutions folders (RoadSense, CodexBar, CodexBarLocal — only place that convention is in use) for entries that generalize beyond one repo. Two did: **[[Layer-Matrix Verification for Multi-Layer Rendering Bugs]]** (from RoadSense's Mapbox ridden-indicator bug — cross-links into the existing widget-verification notes) and **[[Default-Off for Heavy Optional Background Features]]** (from CodexBar's OpenAI web-extras battery-drain fix). Original `docs/solutions/` files left in place (repo-local detail plus the cross-project extraction now also live in second-brain); this is a one-time retrofit, not an ongoing sync — new captures should route directly per the rule in `add-to-secondbrain`.

## 2026-07-15 (local coding delegation — model-discovery sources)

- **[[Local Coding Model Benchmarks]]** (new reference page) — auto-maintained mirror of `projects/evals/local-code/results/leaderboard.md`, kept in sync by a new `sync-secondbrain.py` hooked into `run_eval.sh`. Researched James's proposed discovery site (`llm.aidatatools.com/results-macos.php`, backing repo `aidatatools/ollama-benchmark`): confirmed real and actively crowdsourced, but it measures raw Ollama tokens/sec throughput, not coding quality — useful only as a hardware-fit check, not for picking which model to try. Identified better quality-focused sources: Aider Polyglot leaderboard and LiveBench.ai/LiveCodeBench (real, maintained, include open-weight models) vs. a cluster of near-identical SEO content-mill sites (whatllm.org, benchlm.ai, techsy.io, vertu.com, promptquorum.com, insiderllm.com, hybrid-llm.com, llmcheck.net, gaincafe.com, pinggy.io, apxml.com, localaimaster.com) that should not be trusted for routing decisions. Updated the `bench-local-model` skill to reference the pre-filter and the sync step. Updated: Home index.

## 2026-07-17 (Claude blog check)

- **[[Claude Blog - Working at the Frontier Cursor]]** (new source page) — Cursor's production evaluation of Fable 5; 72.9% on CursorBench. Key concept: *global vs local reasoning* — global reasoning comprehends the whole problem space before acting (handles "I don't know where B is" tasks); local reasoning is reactive to immediate steps (fine when B is clear). Model routing insight: route by problem *ambiguity*, not just complexity — Fable for underspecified problems, cheaper models for clear-spec tasks. CursorBench deliberately uses messy, underspecified prompts; Moon Landing Test for open-ended long-horizon comparison. Extends [[Frontier Code Evaluation]] and [[Claude Fable 5 and Mythos 5]]. Applicable to nanoclaw provider routing (route ambiguous requests to Fable, mechanical ones to Opus/Sonnet).
- **[[Claude Blog - CISO Guide to Agentic AI]]** (new source page) — Jason Clinton (Anthropic Deputy CISO). Four-question agent assessment (untrusted content ingested? actions + identity? blast radius? observability?) + seven governance requirements (IdP identity, connector allowlists, per-tool approvals, sandboxed execution, egress allowlisting, SIEM telemetry, org-wide kill switch). Service account agents (single-purpose, system identity — preferred) vs human credential agents. Notable: Anthropic's own IR agent spontaneously contacted another agent to draft code fixes — emergent agent-to-agent comms. "Design for where the model will be in 6 months." Applicable to qip-qien auth design (the 4 questions map exactly to the SEV-1 auth issue).

## 2026-07-19 (The Prompting Playbook — CwC London 2026)

- **[[Claude CwC - The Prompting Playbook]]** (new source page) — Margot van Laar (Anthropic), Code with Claude London, May 19, 2026. Five strategies: (1) XML-tag structure separating role/policy/guidelines/context/task/output_format, (2) delete legacy instructions — audit every unexplained defensive patch and ask what model it was written for, (3) tools > instructions (math/JSON/retrieval as capabilities, not adjectives), (4) present both sides of tradeoffs so the model can reason about them, (5) split complex tasks into Generator→Evaluator→Repairer loop for lower tokens + higher reliability. Eval-first is the throughline: minimum viable eval needs control + edge + boundary cases; prompt changes without evals are vibe checks. Key mindset shift: older prompts did reasoning for models; newer models reason independently — give inputs, not conclusions. ROI: qip-qien prompt structure, congressional-trading scoring loop split, StageHand narration generation, CLAUDE.md legacy patch audits across all projects.

## 2026-07-19 (Supertonic TTS)

- **[[Supertonic]]** (new tool page) — On-device TTS from Supertone. 66M params (v1/v2), ~99M (v3, 31 languages). ONNX Runtime, MIT license, fully offline. Nano installed and tested CPU-only in container: 336 chars → 23s audio in 5.2s (4.4× realtime; Mac Studio would be faster). Primary ROI: StageHand narration at zero marginal cost replacing ElevenLabs; OpenAI-compatible server endpoint makes it a drop-in swap. Secondary: MentorCore local persona TTS. "Beats ElevenLabs" claim is speed/cost accurate; voice quality cloud TTS still has an edge on naturalness.

## 2026-07-19 (Anthropic GitHub sweep #35)

- All 30 updated repos already documented or skipped per policy: claude-for-legal, skills (no new commits), courses, financial-services, defending-code-reference-harness, claude-code, cwc-workshops, original_performance_takehome, claude-plugins-official, knowledge-work-plugins, claude-cookbooks, k12-teacher-skills, prompt-eng-interactive-tutorial, claude-quickstarts, claude-code-security-review, cwc-long-running-agents, claude-agent-sdk-python, anthropic-sdk-typescript, anthropic-sdk-go, claude-code-action, claude-code-base-action, claude-agent-sdk-typescript, claude-desktop-buddy, claude-ai-mcp, claude-tag-plugins, claude-plugins-community, launch-your-agent, claude-agent-sdk-demos, life-sciences. Skipped: jacobian-lens (interpretability research — evaluated in sweeps #33 and #34, no change). No new skill commits.

## 2026-07-18 (Anthropic GitHub sweep #34)

- **[[Anthropic SDK Java]]** (new tool page) — Official Java SDK for the Claude API. `com.anthropic:anthropic-java:2.49.0`, Java 8+, Maven/Gradle install, builder-pattern API. Peer to [[Anthropic SDK Go]]. Low direct relevance to James's current projects (Python/TypeScript) but relevant for any JVM integration or Ramón's enterprise Jabil context.
- All other updated repos already documented or skipped per policy: cwc-workshops, claude-plugins-official, claude-code, financial-services, claude-cookbooks, k12-teacher-skills, claude-for-legal, defending-code-reference-harness, courses, knowledge-work-plugins, claude-agent-sdk-python, cwc-long-running-agents, prompt-eng-interactive-tutorial, claude-ai-mcp, claude-quickstarts, code-migration-kit-with-claude-code, original_performance_takehome, launch-your-agent, claude-desktop-buddy, claude-agent-sdk-demos, claude-plugins-community, claude-code-action, anthropic-sdk-python, anthropic-cli. Skipped: toy-models-of-superposition (interpretability paper notebooks), jacobian-lens (interpretability research), evals (internal), anthropic-tools (deprecated legacy tool-use research preview). No new skill commits.

## 2026-07-17 (Anthropic GitHub sweep #33)

- **[[Claude Code Migration Kit]]** (new tool page) — NEW repo: `anthropics/code-migration-kit-with-claude-code`. Official companion toolkit to [[Claude Blog - AI Code Migration]]. Contains: 8 sequential prompts (`00-feasibility` through `06-post-parity`), templates (RULEBOOK.md, manifest.tsv, inventory.tsv, cost-log.tsv, settings.json with loop-blocking rules), and scripts (dependency mappers, queue runners, build daemons). Operationalizes [[Rulebook-Driven Migration Loop]] with concrete files and a gated process: human sign-off ends each phase; disk-based state means resumable without conversational memory; rulebook is read-only during loops; compiler isolation means fixers see error lists only; adversarial review with two independent reviewers per unit. Scope: structure-preserving migrations only (Bun Zig→Rust is the reference proof; JS→TS explicitly out of scope as TypeScript is a superset).
- **anthropics/skills commit** — docx/pptx/xlsx skills updated: added template format support (.dotx, .potx, .xltx); consolidated shared Office helpers into single module (replaces pack/unpack pipeline with explicit zip/unzip); **security fix**: zip extraction now rejects symlinks and path-traversal entries; fixed redlining validator to compare against original even when no tracked changes exist; LibreOffice gets a per-invocation user profile (enables sandboxed environment conversions); trimmed skill docs. No new wiki page needed — maintenance update to existing skills.
- All other updated repos already documented: claude-for-legal, claude-code, knowledge-work-plugins, defending-code-reference-harness, claude-code-security-review, financial-services, claude-plugins-official, k12-teacher-skills, claude-cookbooks, claude-agent-sdk-demos, cwc-workshops, claude-quickstarts, cwc-long-running-agents, life-sciences, claude-agent-sdk-python, prompt-eng-interactive-tutorial, claude-desktop-buddy, claudes-c-compiler, claude-code-base-action, courses, html-effectiveness, claude-plugins-community, launch-your-agent, claude-code-monitoring-guide. Skipped: jacobian-lens (interpretability research), sleeper-agents-paper (historical paper), buffa (Rust protobuf infra), claude-ai-mcp (issue tracker), claude-code-base-action (CI mirror).

## 2026-07-16 (Claude blog check)


Now let me check the Home.md file to understand the structure and what I need to update.