| # Outreach Kit |
|
|
| Use these messages to request sources, operating examples, and accuracy corrections without asking for promotion. |
|
|
| ## Who To Invite |
|
|
| - People writing directly about Loop Engineering. |
| - Maintainers of agent runtimes with scheduled, goal-driven, or event-triggered agent work. |
| - Builders running PR babysitting, CI repair, docs drift, deploy verification, feedback clustering, or evaluation loops. |
| - Researchers working on agent feedback, reflection, planning, verification, state, and tool use. |
|
|
| ## Short Message |
|
|
| ```text |
| Hi <name>, Awesome Loop Engineering connects 797 papers, docs, tools, benchmarks, and guides with reusable patterns for recurring AI-agent systems. |
| |
| If you have an original or official source, a correction, a real-world loop, or a cautionary example, you can contribute here: |
| https://github.com/ChaoYue0307/awesome-loop-engineering |
| ``` |
|
|
| ## Pattern Request |
|
|
| ```text |
| Hi <name>, do you have a public example of an agent loop you can share? |
| |
| Useful examples name the trigger, intake, agent roles, verification gates, durable state, retry budget, escalation path, and receipts. An anonymized version is welcome when the implementation cannot be public. |
| ``` |
|
|
| ## Accuracy Request |
|
|
| ```text |
| Hi <name>, I included <work title> in Awesome Loop Engineering and summarized its contribution as: "<current annotation>." |
| |
| Could you check whether that characterization is accurate? If it misses the main contribution, novelty, impact, or source link, please submit a correction: |
| https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=annotation-correction.yml |
| ``` |
|
|
| ## Maintainer Request |
|
|
| ```text |
| Hi <name>, Awesome Loop Engineering helps researchers and builders move from 797 papers, docs, tools, benchmarks, and guides to 22 operational patterns, 22 adaptable contracts, 8 runtime starters, and a structured dataset. |
| |
| Would it fit the related-resources policy for <project or newsletter>? I can provide a shorter description or submit through the normal contribution process: |
| https://github.com/ChaoYue0307/awesome-loop-engineering |
| ``` |
|
|
| ## What Not To Ask For |
|
|
| - Do not ask people to endorse claims they have not made. |
| - Do not ask for private customer data, proprietary prompts, secrets, or internal dashboards. |
| - Do not imply the repository is a standard; describe the concrete resources and tools readers can use. |
| - Do not ask for stars, reposts, or endorsements in an accuracy request. |
|
|
