Skip to content

Weekly refresh 2026-07-03 (cycle #3): loop engineering, formalized - #6

Open
satoshigreek wants to merge 1 commit into
mainfrom
claude/loop-harness-weekly-update-g87kuu
Open

Weekly refresh 2026-07-03 (cycle #3): loop engineering, formalized#6
satoshigreek wants to merge 1 commit into
mainfrom
claude/loop-harness-weekly-update-g87kuu

Conversation

@satoshigreek

Copy link
Copy Markdown
Owner

Third run of the SELF-IMPROVEMENT.md protocol. Scanned Anthropic, OpenAI, Microsoft, and arXiv cs.AI/cs.SE. Three candidates passed all five evals (authority, freshness, non-regression, link integrity, on-purpose); every arXiv title was verified against its abstract before citing.

Ranked change set

1. Loop engineering, formalized — docs/01, index.html, references.md (Priority 1: freshest, and upgrades existing content's authority)
Stop Hand-Holding Your Coding Agent: Engineering the Loops that Replace Step-by-Step Prompting (arXiv:2607.00038, July 2026). This is the arXiv formalization of the outer-loop concept added last cycle from a practitioner newsletter — so it raises that section's authority to a citable source. Folded into docs/01: the loop specification (trigger · goal · verification · stopping rule · memory), the prompt → context → harness → loop progression, the five-level verification ladder, named terminal states, and the 50-loop corpus finding (70% verify autonomously, 74% name terminal states; automated triggering + durable memory are the weak links).

2. Skill harnessing — docs/02, index.html, references.md (Priority 3: reference architecture, on-purpose)
Harnessing Agent Skills: A Reference Architecture for Skill-Mediated LLM Agents (arXiv:2606.20631). The skill-in-use transition governed by four responsibility layers: Supply Chain → Mediation → Execution Control → Evidence & Feedback.

3. First-party corroboration — references.md (no card — not a research paper)
Microsoft Agent Framework at BUILD 2026: Agent Harness — the harness as a first-class SDK layer with built-in mid-loop context compaction and human-in-the-loop gating. Added under §Foundations.

Website

Both papers are research papers → each got a UML card with a real mechanism diagram (Agent loop, Tool design). Hero paper count 32 → 34. Nine categories unchanged.

Website eval gate: PASS — rendered headlessly (Chromium + vendored mermaid, since the CDN is egress-blocked): all 35 .mermaid blocks produced an <svg>, 0 syntax errors.

Bookkeeping

Verified: 0 broken internal links/anchors.

Note: this is a fresh PR on the restarted branch — the previous two PRs (#4, #5) on this branch are already merged, so this begins from current main.

🤖 Generated with Claude Code

https://claude.ai/code/session_01PChasP7sN14akYoz73LXkc


Generated by Claude Code

Ran the SELF-IMPROVEMENT.md protocol. Three candidates passed the full eval
gate (authority, freshness, non-regression, link integrity, on-purpose);
arXiv titles verified against abstracts.

- docs/01: fold in "Stop Hand-Holding Your Coding Agent" (arXiv:2607.00038) --
  the loop specification (trigger, goal, verification, stopping rule, memory),
  the prompt -> context -> harness -> loop progression, the five-level
  verification ladder, named terminal states, and the 50-loop corpus finding.
  Raises last cycle's newsletter-sourced framing to a citable arXiv source.
- docs/02: "Harnessing Agent Skills" (arXiv:2606.20631) -- the skill-in-use
  reference architecture (Supply Chain -> Mediation -> Execution Control ->
  Evidence & Feedback).
- index.html: two new UML cards (Agent loop, Tool design); count 32 -> 34.
- references.md: two papers + a first-party Microsoft Agent Framework
  (Agent Harness, BUILD 2026) entry.
- SELF-IMPROVEMENT.md: last_updated -> 2026-07-03.

Verified: 0 broken links/anchors; 35/35 mermaid diagrams render, 0 errors.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PChasP7sN14akYoz73LXkc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants