# Pull Request

## What Changed

Select all that apply.

- [ ] Added or updated resource entries
- [ ] Added or updated a loop pattern
- [ ] Added or updated a translation
- [ ] Improved docs, templates, or repository presentation
- [ ] Fixed links, typos, or formatting

## Resource Summary

List the resources, patterns, or translation files changed. For each resource, include the canonical URL and original publishing venue or platform.

- Title and URL:

## Relevance To Loop Engineering

Explain how this PR relates to the new AI/coding-agent meaning of Loop Engineering: the layer above prompt, context, and harness engineering where recurring systems trigger agents, provide context, bound actions, verify results, persist state, retry, and escalate.

## Category

Which README section did you update?

- [ ] Start Here
- [ ] Core Loop Primitives
- [ ] Official Runtime Guides
- [ ] Research Foundations
- [ ] Agent Workflow Patterns
- [ ] Coding-Agent Loop Systems
- [ ] Verification And Feedback Gates
- [ ] State, Memory, And Context Persistence
- [ ] Orchestration And Multi-Agent Delegation
- [ ] Benchmarks And Evaluation
- [ ] Operations Playbooks
- [ ] Templates And Patterns
- [ ] Critiques, Risks, And Limitations
- [ ] Adjacent Awesome Lists
- [ ] Translation or repository docs

## Source Type

- [ ] 📄 Paper
- [ ] 📝 Blog
- [ ] 📚 Docs
- [ ] 🧰 Tool
- [ ] 🧪 Benchmark
- [ ] 🔁 Pattern
- [ ] 🧾 Template
- [ ] 🧭 List
- [ ] ⚠️ Critique

## Quality Labels

- [ ] Direct Loop Engineering source
- [ ] Paper or technical report
- [ ] Official documentation
- [ ] Engineering blog or field note
- [ ] Tool, framework, or repository
- [ ] Benchmark or evaluation resource
- [ ] Critique or limitation analysis
- [ ] Adjacent awesome list
- [ ] Primary source
- [ ] Implementation-heavy
- [ ] Foundational
- [ ] Cautionary
- [ ] Translation
- [ ] Repository maintenance

## Evidence Quality

- [ ] Tier A: primary source or official docs
- [ ] Tier B: practitioner write-up with implementation detail
- [ ] Tier C: curated survey or high-quality explainer
- [ ] Tier D: commentary or news coverage

## Accuracy And Provenance

- Original or official source checked:
- Original publishing venue or platform:
- Publication date, authors, and identifier verified from:
- Material caveats or source-access limits:
- Automated assistance used for discovery, extraction, or drafting (if any):

## Checklist

- [ ] I searched the README for duplicates.
- [ ] The resource is public and has a stable URL.
- [ ] The entry is in the most specific category.
- [ ] The entry includes the correct resource type label, such as `📄 **Paper**` or `📚 **Docs**`.
- [ ] The annotation explains why the resource matters for loop design.
- [ ] The `Published at` cell names the work's original venue or publishing platform, not this repository.
- [ ] I omitted unavailable publication metadata instead of inferring it from search snippets or secondary coverage.
- [ ] Adjacent prompt, context, or harness resources explicitly connect to repeated agent runs, state, verification, or escalation.
- [ ] The entry follows the table format: `| 📄 **[Title](https://example.com)**<br><sub>Paper</sub> | **2026** · Venue<br><sub>Author</sub> | Specific contribution. |`.
- [ ] The resource is not about unrelated event loops, growth loops, control theory, or generic automation.
- [ ] New loop patterns include trigger, discover/intake, delegation, state, verification gates, retry budget, escalation path, and loop instruction or automation artifact.
- [ ] Any automated assistance was checked against the original or official source; generated text was not treated as evidence.
- [ ] I ran `python3 scripts/render_readme_tables.py` and `python3 scripts/export_resource_dataset.py` after changing resource rows.
- [ ] I agree that my contribution to this repository is released under `CC0-1.0`.
- [ ] I did not copy third-party content into this repository without the right to do so.
- [ ] Any translation links back to the canonical English README.