| # Outreach Kit |
|
|
| Use this when inviting authors, practitioners, or tool builders to improve the repository. |
|
|
| ## 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>, this repository is collecting high-signal resources and practical patterns for Loop Engineering: designing recurring AI-agent systems above prompt, context, and harness engineering. |
| |
| If you have a source, correction, real-world loop pattern, or cautionary example that should be included, contributions are welcome: |
| 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? |
| |
| The repo is looking for examples with a clear trigger, work intake, agent roles, verification gates, durable state, retry budget, escalation path, and receipts. An anonymized version is fine if the implementation cannot be public. |
| ``` |
|
|
| ## Accuracy Request |
|
|
| ```text |
| Hi <name>, your work is cited in Awesome Loop Engineering. If the annotation misstates the idea or a better canonical link exists, a correction PR or issue would be very welcome. |
| ``` |
|
|
| ## 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. It is an early curated field guide for an emerging practice. |
|
|
