Grow implementation kit: 22 patterns, 22 contracts, 671 resources
Browse files- README.de.md +1 -1
- README.es.md +1 -1
- README.fr.md +1 -1
- README.ja.md +1 -1
- README.ko.md +1 -1
- README.md +0 -0
- README.pt-BR.md +1 -1
- README.zh-CN.md +1 -1
- data/README.md +1 -1
- data/first_seen.json +3 -1
- data/resource_source_audit.csv +0 -0
- data/resources.csv +0 -0
- data/resources.jsonl +0 -0
- design-qa.md +6 -6
- docs/assets/resources.json +0 -0
- docs/assets/social-preview-671-v10.png +3 -0
- docs/index.html +13 -13
- docs/x-v10-671.html +44 -0
- examples/agent-memory-lifecycle-loop.json +103 -0
- examples/fleet-coordination-loop.json +102 -0
- meta/DISTRIBUTION.md +7 -7
- meta/social-preview.html +3 -3
- patterns/MATRIX.md +3 -1
- patterns/agent-memory-lifecycle-loop.md +106 -0
- patterns/fleet-coordination-loop.md +104 -0
- posts/launch.md +3 -3
- posts/launch.zh-CN.md +2 -2
README.de.md
CHANGED
|
@@ -28,7 +28,7 @@ Ein Loop entdeckt Arbeit, übergibt sie an einen oder mehrere Agenten, prüft da
|
|
| 28 |
|
| 29 |
Loop Engineering umfasst wiederkehrende KI-Agenten- und Coding-Agent-Systeme mit expliziten Auslösern, Verifikation und dauerhaftem Zustand. Software-Event-Loops, Regelungstechnik, Growth Loops, generische Automatisierung und nicht-KI-bezogene Feedback-Loops gehören nicht dazu.
|
| 30 |
|
| 31 |
-
Starte mit
|
| 32 |
|
| 33 |
## Mentales Modell
|
| 34 |
|
|
|
|
| 28 |
|
| 29 |
Loop Engineering umfasst wiederkehrende KI-Agenten- und Coding-Agent-Systeme mit expliziten Auslösern, Verifikation und dauerhaftem Zustand. Software-Event-Loops, Regelungstechnik, Growth Loops, generische Automatisierung und nicht-KI-bezogene Feedback-Loops gehören nicht dazu.
|
| 30 |
|
| 31 |
+
Starte mit 671 Ressourcen, 20 operativen Loop-Patterns, 20 schemavalidierten Loop-Contracts und 8 Runtime-Startern (3 ausführbare Programme und 5 anpassbare Vorlagen), ergänzt durch eine Community-Galerie und 8 Sprachen.
|
| 32 |
|
| 33 |
## Mentales Modell
|
| 34 |
|
README.es.md
CHANGED
|
@@ -28,7 +28,7 @@ Un loop descubre trabajo, lo delega a uno o más agentes, verifica el resultado,
|
|
| 28 |
|
| 29 |
Loop Engineering abarca sistemas recurrentes de agentes de IA y coding agents con disparadores explícitos, verificación y estado duradero. No incluye event loops de software, teoría de control, growth loops, automatización genérica ni feedback loops no relacionados con IA.
|
| 30 |
|
| 31 |
-
Empieza con
|
| 32 |
|
| 33 |
## Modelo Mental
|
| 34 |
|
|
|
|
| 28 |
|
| 29 |
Loop Engineering abarca sistemas recurrentes de agentes de IA y coding agents con disparadores explícitos, verificación y estado duradero. No incluye event loops de software, teoría de control, growth loops, automatización genérica ni feedback loops no relacionados con IA.
|
| 30 |
|
| 31 |
+
Empieza con 671 recursos, 20 patrones operativos, 22 loop contracts validados por esquema y 8 puntos de partida de runtime (3 ejecutables y 5 plantillas listas para adaptar), además de una galería comunitaria y 8 idiomas.
|
| 32 |
|
| 33 |
## Modelo Mental
|
| 34 |
|
README.fr.md
CHANGED
|
@@ -28,7 +28,7 @@ Un loop découvre du travail, le délègue à un ou plusieurs agents, vérifie l
|
|
| 28 |
|
| 29 |
Loop Engineering couvre les systèmes récurrents d'agents IA et de coding agents avec des déclencheurs explicites, une vérification et un état durable. Il n'inclut ni les event loops logiciels, ni la théorie du contrôle, ni les growth loops, ni l'automatisation générique, ni les feedback loops sans rapport avec l'IA.
|
| 30 |
|
| 31 |
-
Commencez avec
|
| 32 |
|
| 33 |
## Modèle Mental
|
| 34 |
|
|
|
|
| 28 |
|
| 29 |
Loop Engineering couvre les systèmes récurrents d'agents IA et de coding agents avec des déclencheurs explicites, une vérification et un état durable. Il n'inclut ni les event loops logiciels, ni la théorie du contrôle, ni les growth loops, ni l'automatisation générique, ni les feedback loops sans rapport avec l'IA.
|
| 30 |
|
| 31 |
+
Commencez avec 671 ressources, 22 patterns opérationnels, 22 loop contracts validés par schéma et 8 points de départ d'exécution (3 exécutables et 5 modèles prêts à adapter), ainsi qu'une galerie communautaire et 8 langues.
|
| 32 |
|
| 33 |
## Modèle Mental
|
| 34 |
|
README.ja.md
CHANGED
|
@@ -28,7 +28,7 @@ Loop は作業を発見し、1 つ以上の agents に委任し、結果を確
|
|
| 28 |
|
| 29 |
Loop Engineering は、明示的なトリガー、検証、永続状態を備えた反復型 AI agent / coding agent システムを対象とします。software event loop、制御理論、growth loop、一般的な workflow automation、非 AI の feedback loop は含みません。
|
| 30 |
|
| 31 |
-
|
| 32 |
|
| 33 |
## メンタルモデル
|
| 34 |
|
|
|
|
| 28 |
|
| 29 |
Loop Engineering は、明示的なトリガー、検証、永続状態を備えた反復型 AI agent / coding agent システムを対象とします。software event loop、制御理論、growth loop、一般的な workflow automation、非 AI の feedback loop は含みません。
|
| 30 |
|
| 31 |
+
671 件の監査済みリソース、20 個の運用パターン、20 個の schema 検証済み loop contract、8 個の runtime starter(3 個の実行ファイルと 5 個の適応可能なテンプレート)から始められます。コミュニティ gallery と 8 言語の導入も利用できます。
|
| 32 |
|
| 33 |
## メンタルモデル
|
| 34 |
|
README.ko.md
CHANGED
|
@@ -28,7 +28,7 @@ Loop 는 작업을 발견하고, 하나 이상의 agents 에게 위임하고,
|
|
| 28 |
|
| 29 |
Loop Engineering 은 명시적 트리거, 검증, 지속 상태를 갖춘 반복 AI agent / coding agent 시스템을 다룹니다. software event loop, control theory, growth loop, 일반적인 workflow automation, 비 AI feedback loop 는 포함하지 않습니다.
|
| 30 |
|
| 31 |
-
|
| 32 |
|
| 33 |
## 멘탈 모델
|
| 34 |
|
|
|
|
| 28 |
|
| 29 |
Loop Engineering 은 명시적 트리거, 검증, 지속 상태를 갖춘 반복 AI agent / coding agent 시스템을 다룹니다. software event loop, control theory, growth loop, 일반적인 workflow automation, 비 AI feedback loop 는 포함하지 않습니다.
|
| 30 |
|
| 31 |
+
671개의 감사된 리소스, 20개의 운영 loop 패턴, 20개의 스키마 검증 loop contract, 8개의 runtime starter(실행 파일 3개와 적용 가능한 템플릿 5개)로 바로 시작할 수 있습니다. 커뮤니티 gallery 와 8개 언어 안내도 제공합니다.
|
| 32 |
|
| 33 |
## 멘탈 모델
|
| 34 |
|
README.md
CHANGED
|
The diff for this file is too large to render.
See raw diff
|
|
|
README.pt-BR.md
CHANGED
|
@@ -28,7 +28,7 @@ Um loop descobre trabalho, delega para um ou mais agentes, verifica o resultado,
|
|
| 28 |
|
| 29 |
Loop Engineering abrange sistemas recorrentes de AI agents e coding agents com gatilhos explícitos, verificação e estado durável. Não inclui event loops de software, teoria de controle, growth loops, automação genérica nem feedback loops sem relação com IA.
|
| 30 |
|
| 31 |
-
Comece com
|
| 32 |
|
| 33 |
## Modelo Mental
|
| 34 |
|
|
|
|
| 28 |
|
| 29 |
Loop Engineering abrange sistemas recorrentes de AI agents e coding agents com gatilhos explícitos, verificação e estado durável. Não inclui event loops de software, teoria de controle, growth loops, automação genérica nem feedback loops sem relação com IA.
|
| 30 |
|
| 31 |
+
Comece com 671 recursos, 22 patterns operacionais, 22 loop contracts validados por schema e 8 starters de runtime (3 executáveis e 5 templates prontos para adaptação), além de uma galeria comunitária e 8 idiomas.
|
| 32 |
|
| 33 |
## Modelo Mental
|
| 34 |
|
README.zh-CN.md
CHANGED
|
@@ -32,7 +32,7 @@ Prompt engineering 改进你对模型说什么。Context engineering 改进模
|
|
| 32 |
|
| 33 |
Loop Engineering 专指具备明确触发、外部验证和持久状态的可重复 AI-agent 与 coding-agent 系统,不包括软件事件循环、控制论、增长循环、通用 workflow automation 或非 AI feedback loop。
|
| 34 |
|
| 35 |
-
可直接从
|
| 36 |
|
| 37 |
## 一句话定位
|
| 38 |
|
|
|
|
| 32 |
|
| 33 |
Loop Engineering 专指具备明确触发、外部验证和持久状态的可重复 AI-agent 与 coding-agent 系统,不包括软件事件循环、控制论、增长循环、通用 workflow automation 或非 AI feedback loop。
|
| 34 |
|
| 35 |
+
可直接从 671 篇论文、官方文档、工具、benchmark 与实践指南,20 个操作模式、20 个经 schema 校验的 loop contracts 和 8 个 runtime starters(3 个可直接执行,5 个可复制改造)开始,并通过社区 gallery 和 8 种语言入口继续探索。
|
| 36 |
|
| 37 |
## 一句话定位
|
| 38 |
|
data/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
| 1 |
# Dataset Exports
|
| 2 |
|
| 3 |
-
Download all
|
| 4 |
|
| 5 |
- `resources.csv` - Tabular export for spreadsheets and ad hoc analysis.
|
| 6 |
- `resources.jsonl` - JSON Lines export and source for the Hugging Face Parquet build.
|
|
|
|
| 1 |
# Dataset Exports
|
| 2 |
|
| 3 |
+
Download all 671 resources as deterministic tabular exports.
|
| 4 |
|
| 5 |
- `resources.csv` - Tabular export for spreadsheets and ad hoc analysis.
|
| 6 |
- `resources.jsonl` - JSON Lines export and source for the Hugging Face Parquet build.
|
data/first_seen.json
CHANGED
|
@@ -181,5 +181,7 @@
|
|
| 181 |
"https://www.starfleetmath.com/": "2026-07-22",
|
| 182 |
"https://www.ayush.digital/blog/the-memory-heist": "2026-07-22",
|
| 183 |
"https://mindgard.ai/blog/cursor-0day-when-full-disclosure-becomes-the-only-protection-left": "2026-07-22",
|
| 184 |
-
"https://lucumr.pocoo.org/2026/7/13/the-tower-keeps-rising/": "2026-07-22"
|
|
|
|
|
|
|
| 185 |
}
|
|
|
|
| 181 |
"https://www.starfleetmath.com/": "2026-07-22",
|
| 182 |
"https://www.ayush.digital/blog/the-memory-heist": "2026-07-22",
|
| 183 |
"https://mindgard.ai/blog/cursor-0day-when-full-disclosure-becomes-the-only-protection-left": "2026-07-22",
|
| 184 |
+
"https://lucumr.pocoo.org/2026/7/13/the-tower-keeps-rising/": "2026-07-22",
|
| 185 |
+
"patterns/agent-memory-lifecycle-loop.md": "2026-07-22",
|
| 186 |
+
"patterns/fleet-coordination-loop.md": "2026-07-22"
|
| 187 |
}
|
data/resource_source_audit.csv
CHANGED
|
The diff for this file is too large to render.
See raw diff
|
|
|
data/resources.csv
CHANGED
|
The diff for this file is too large to render.
See raw diff
|
|
|
data/resources.jsonl
CHANGED
|
The diff for this file is too large to render.
See raw diff
|
|
|
design-qa.md
CHANGED
|
@@ -41,7 +41,7 @@
|
|
| 41 |
8. Compared the published static hero and the Three.js-enhanced hero at the same 1280 x 720 viewport. The enhancement keeps the existing identity, copy, actions, spacing, and section transition while adding a restrained evidence orbit, control-plane stack, verification gate, and six lifecycle nodes behind the content.
|
| 42 |
9. Moved the control-plane stack and verification gate outward after the first 3D pass so they frame the copy rather than crossing its reading path. Rechecked desktop and mobile rendering after the adjustment.
|
| 43 |
10. Verified progressive enhancement behavior: the semantic hero remains complete without WebGL, forced-colors and print hide the scene, reduced-motion renders a static frame, and the animation stops when the hero leaves the viewport.
|
| 44 |
-
11. Expanded the implementation kit to
|
| 45 |
12. Rechecked the expanded pattern and runtime sections at 1440 x 1000 and 390 x 844. Anchor offsets clear the sticky header, the page width stays equal to the viewport, and headings, icons, labels, and descriptions remain aligned.
|
| 46 |
13. Added the role-based future-directions section and rechecked it at both target viewports. Resource Atlas expansion initially displaced direct links to later sections; post-load hash restoration now leaves `#future` 84 px below the desktop viewport top and 74 px below it on mobile.
|
| 47 |
|
|
@@ -76,9 +76,9 @@
|
|
| 76 |
- Tablet: 768 x 900. The first pass clipped the intake and decision stations. The responsive camera now fits an 11.2-unit horizontal view between 720 px and 900 px, keeping all six stations, the retry path, and the outcome node inside the canvas.
|
| 77 |
- Phone: 390 x 844, no horizontal overflow. The compact loop keeps all six stations, the moving work packet, legend, outcome key, and stage selector visible without crossing the hero copy.
|
| 78 |
- Mobile navigation: opens all nine project links, reports `aria-expanded="true"`, closes on Escape, and restores focus to the menu button.
|
| 79 |
-
- Pattern filter: `accessibility` returns exactly one of the
|
| 80 |
-
- Resource Atlas: remains idle above the fold, loads on approach or a direct resource anchor, and reports `669 of
|
| 81 |
-
- Resource interactions: the Model loop-layer filter returns 29 of
|
| 82 |
- Resource row schema: desktop exposes Work, Year, Published at, and Evidence; mobile stacks the same labels. A `ReasoningBank` query returns one row with its ICLR venue, arXiv identifier, Tier A evidence, task fit, and source record without horizontal overflow.
|
| 83 |
- Scene motion: the canvas frame counter advanced from 640 to 662 over 900 ms. Two canvas crops taken 1.2 seconds apart changed 17.79% of sampled RGB channels.
|
| 84 |
- Scene pixels: the current desktop canvas has 7,062 colors with RGB standard deviations of 35.93, 29.76, and 22.29; mobile has 5,755 colors with deviations of 40.73, 30.54, and 19.70. Both renders are nonblank and well contrasted.
|
|
@@ -86,8 +86,8 @@
|
|
| 86 |
- Future directions: direct-anchor restoration waits for the Resource Atlas reflow, all three audience tracks remain readable, and the agenda CTA is fully visible at desktop and mobile widths.
|
| 87 |
- Console: no page-origin errors or warnings during mobile navigation, pattern filtering, and Resource Atlas interactions.
|
| 88 |
- Narrow phone: 320 x 844, document width equals viewport width; the headline stays within 16 px gutters and the Three.js canvas remains fully inside the 288 px content width.
|
| 89 |
-
- Source audit: 669 rows checked;
|
| 90 |
-
- Data and copy: the website, README, translations, social preview source, release copy, and Hugging Face card all report
|
| 91 |
- Semantic scene pass: the desktop hero crop paints 14.61% of pixels beyond the paper background with a 254.71 luminance range; the desktop stack paints 27.83% with a 249.98 range; the mobile hero paints 20.84% with a 229.45 range.
|
| 92 |
- Stage interaction: selecting Verify updates `aria-pressed` across all six controls and replaces the live detail with the independent evidence-gate explanation.
|
| 93 |
- Progressive enhancement: desktop loads the agent-loop and engineering-stack canvases; mobile loads only the agent-loop canvas and exposes the four-layer text stack. Both target viewports have zero horizontal overflow and no console messages.
|
|
|
|
| 41 |
8. Compared the published static hero and the Three.js-enhanced hero at the same 1280 x 720 viewport. The enhancement keeps the existing identity, copy, actions, spacing, and section transition while adding a restrained evidence orbit, control-plane stack, verification gate, and six lifecycle nodes behind the content.
|
| 42 |
9. Moved the control-plane stack and verification gate outward after the first 3D pass so they frame the copy rather than crossing its reading path. Rechecked desktop and mobile rendering after the adjustment.
|
| 43 |
10. Verified progressive enhancement behavior: the semantic hero remains complete without WebGL, forced-colors and print hide the scene, reduced-motion renders a static frame, and the animation stops when the hero leaves the viewport.
|
| 44 |
+
11. Expanded the implementation kit to 22 patterns, 22 schema-checked contracts, and eight runtime starters. The runtime section now labels all five adaptable templates and all three executables, with use-case copy and an even desktop grid.
|
| 45 |
12. Rechecked the expanded pattern and runtime sections at 1440 x 1000 and 390 x 844. Anchor offsets clear the sticky header, the page width stays equal to the viewport, and headings, icons, labels, and descriptions remain aligned.
|
| 46 |
13. Added the role-based future-directions section and rechecked it at both target viewports. Resource Atlas expansion initially displaced direct links to later sections; post-load hash restoration now leaves `#future` 84 px below the desktop viewport top and 74 px below it on mobile.
|
| 47 |
|
|
|
|
| 76 |
- Tablet: 768 x 900. The first pass clipped the intake and decision stations. The responsive camera now fits an 11.2-unit horizontal view between 720 px and 900 px, keeping all six stations, the retry path, and the outcome node inside the canvas.
|
| 77 |
- Phone: 390 x 844, no horizontal overflow. The compact loop keeps all six stations, the moving work packet, legend, outcome key, and stage selector visible without crossing the hero copy.
|
| 78 |
- Mobile navigation: opens all nine project links, reports `aria-expanded="true"`, closes on Escape, and restores focus to the menu button.
|
| 79 |
+
- Pattern filter: `accessibility` returns exactly one of the 22 patterns.
|
| 80 |
+
- Resource Atlas: remains idle above the fold, loads on approach or a direct resource anchor, and reports `669 of 671 resources | showing 8` on a fresh mobile load.
|
| 81 |
+
- Resource interactions: the Model loop-layer filter returns 29 of 671 resources (28 papers plus Awesome Loop Models), paginates eight at a time on mobile, and renders Loopie and LoopWM with their 2026 arXiv records and adjacent-scope labels.
|
| 82 |
- Resource row schema: desktop exposes Work, Year, Published at, and Evidence; mobile stacks the same labels. A `ReasoningBank` query returns one row with its ICLR venue, arXiv identifier, Tier A evidence, task fit, and source record without horizontal overflow.
|
| 83 |
- Scene motion: the canvas frame counter advanced from 640 to 662 over 900 ms. Two canvas crops taken 1.2 seconds apart changed 17.79% of sampled RGB channels.
|
| 84 |
- Scene pixels: the current desktop canvas has 7,062 colors with RGB standard deviations of 35.93, 29.76, and 22.29; mobile has 5,755 colors with deviations of 40.73, 30.54, and 19.70. Both renders are nonblank and well contrasted.
|
|
|
|
| 86 |
- Future directions: direct-anchor restoration waits for the Resource Atlas reflow, all three audience tracks remain readable, and the agenda CTA is fully visible at desktop and mobile widths.
|
| 87 |
- Console: no page-origin errors or warnings during mobile navigation, pattern filtering, and Resource Atlas interactions.
|
| 88 |
- Narrow phone: 320 x 844, document width equals viewport width; the headline stays within 16 px gutters and the Three.js canvas remains fully inside the 288 px content width.
|
| 89 |
+
- Source audit: 669 rows checked; 618 public sources reachable, 2 access-restricted, 51 repository-native, and 0 broken or unreachable as of 2026-07-22 UTC.
|
| 90 |
+
- Data and copy: the website, README, translations, social preview source, release copy, and Hugging Face card all report 671 resources, 22 patterns, 22 contracts, 8 runtime starters, and version 0.9.0. The dataset exposes 50 fields, including `loop_layer` and `scope_fit`.
|
| 91 |
- Semantic scene pass: the desktop hero crop paints 14.61% of pixels beyond the paper background with a 254.71 luminance range; the desktop stack paints 27.83% with a 249.98 range; the mobile hero paints 20.84% with a 229.45 range.
|
| 92 |
- Stage interaction: selecting Verify updates `aria-pressed` across all six controls and replaces the live detail with the independent evidence-gate explanation.
|
| 93 |
- Progressive enhancement: desktop loads the agent-loop and engineering-stack canvases; mobile loads only the agent-loop canvas and exposes the four-layer text stack. Both target viewports have zero horizontal overflow and no console messages.
|
docs/assets/resources.json
CHANGED
|
The diff for this file is too large to render.
See raw diff
|
|
|
docs/assets/social-preview-671-v10.png
ADDED
|
Git LFS Details
|
docs/index.html
CHANGED
|
@@ -4,7 +4,7 @@
|
|
| 4 |
<meta charset="utf-8">
|
| 5 |
<meta name="viewport" content="width=device-width, initial-scale=1">
|
| 6 |
<title>Awesome Loop Engineering</title>
|
| 7 |
-
<meta name="description" content="Explore
|
| 8 |
<meta name="robots" content="index,follow">
|
| 9 |
<meta name="author" content="Chaoyue He">
|
| 10 |
<link rel="canonical" href="https://chaoyue0307.github.io/awesome-loop-engineering/">
|
|
@@ -15,16 +15,16 @@
|
|
| 15 |
<link href="https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@500;600&family=Inter:wght@400;500;600;700;800&display=swap" rel="stylesheet">
|
| 16 |
<meta property="og:type" content="website">
|
| 17 |
<meta property="og:title" content="Awesome Loop Engineering">
|
| 18 |
-
<meta property="og:description" content="Explore 669 papers, docs, tools, benchmarks, and guides, then build recurring agent systems with
|
| 19 |
<meta property="og:url" content="https://chaoyue0307.github.io/awesome-loop-engineering/">
|
| 20 |
-
<meta property="og:image" content="https://chaoyue0307.github.io/awesome-loop-engineering/assets/social-preview-
|
| 21 |
<meta property="og:image:width" content="1280">
|
| 22 |
<meta property="og:image:height" content="640">
|
| 23 |
<meta property="og:image:alt" content="Awesome Loop Engineering: design loops, not just prompts.">
|
| 24 |
<meta name="twitter:card" content="summary_large_image">
|
| 25 |
<meta name="twitter:title" content="Awesome Loop Engineering">
|
| 26 |
-
<meta name="twitter:description" content="
|
| 27 |
-
<meta name="twitter:image" content="https://chaoyue0307.github.io/awesome-loop-engineering/assets/social-preview-
|
| 28 |
<link rel="alternate" type="application/atom+xml" title="Awesome Loop Engineering releases" href="https://github.com/ChaoYue0307/awesome-loop-engineering/releases.atom">
|
| 29 |
<link rel="alternate" type="application/atom+xml" title="Awesome Loop Engineering commits" href="https://github.com/ChaoYue0307/awesome-loop-engineering/commits/main.atom">
|
| 30 |
<style>
|
|
@@ -1307,7 +1307,7 @@
|
|
| 1307 |
"https://huggingface.co/datasets/cy0307/awesome-loop-engineering"
|
| 1308 |
],
|
| 1309 |
"license": "https://creativecommons.org/publicdomain/zero/1.0/",
|
| 1310 |
-
"image": "https://chaoyue0307.github.io/awesome-loop-engineering/assets/social-preview-
|
| 1311 |
"logo": "https://chaoyue0307.github.io/awesome-loop-engineering/assets/awesome-loop-engineering-logo.png",
|
| 1312 |
"author": { "@type": "Person", "name": "Chaoyue He" }
|
| 1313 |
}
|
|
@@ -1355,7 +1355,7 @@
|
|
| 1355 |
"@context": "https://schema.org",
|
| 1356 |
"@type": "Dataset",
|
| 1357 |
"name": "Awesome Loop Engineering resources",
|
| 1358 |
-
"description": "Explore
|
| 1359 |
"url": "https://chaoyue0307.github.io/awesome-loop-engineering/",
|
| 1360 |
"sameAs": [
|
| 1361 |
"https://huggingface.co/datasets/cy0307/awesome-loop-engineering",
|
|
@@ -1430,7 +1430,7 @@
|
|
| 1430 |
<p class="section-label hero-kicker"><i class="icon" data-lucide="repeat-2" aria-hidden="true"></i><span>Field guide for recurring agent systems</span></p>
|
| 1431 |
<h1>Awesome Loop Engineering</h1>
|
| 1432 |
<p class="tagline">Design loops, not just prompts.</p>
|
| 1433 |
-
<p class="lead">Explore
|
| 1434 |
<div class="actions">
|
| 1435 |
<a class="button primary" href="https://github.com/ChaoYue0307/awesome-loop-engineering#readme"><i class="icon" data-lucide="book-open" aria-hidden="true"></i>Explore resources</a>
|
| 1436 |
<a class="button" href="#choose"><i class="icon" data-lucide="compass" aria-hidden="true"></i>Choose a loop</a>
|
|
@@ -1493,7 +1493,7 @@
|
|
| 1493 |
</div>
|
| 1494 |
</figure>
|
| 1495 |
<div class="stats" role="list" aria-label="Field guide at a glance">
|
| 1496 |
-
<div class="stat" role="listitem"><b><i class="icon" data-lucide="library" aria-hidden="true"></i>
|
| 1497 |
<div class="stat" role="listitem"><b><i class="icon" data-lucide="blocks" aria-hidden="true"></i>20</b><span>operational patterns</span></div>
|
| 1498 |
<div class="stat" role="listitem"><b><i class="icon" data-lucide="file-check-2" aria-hidden="true"></i>20</b><span>loop contracts</span></div>
|
| 1499 |
<div class="stat" role="listitem"><b><i class="icon" data-lucide="play" aria-hidden="true"></i>8</b><span>runtime starters</span></div>
|
|
@@ -1793,9 +1793,9 @@
|
|
| 1793 |
<p class="section-label"><i class="icon" data-lucide="library" aria-hidden="true"></i><span>06 / Resource atlas</span></p>
|
| 1794 |
<h2>Find evidence, not just links.</h2>
|
| 1795 |
</div>
|
| 1796 |
-
<p class="section-intro">Filter
|
| 1797 |
</div>
|
| 1798 |
-
<p class="audit-note"><strong>Last source check, 2026-07-21 UTC:</strong>
|
| 1799 |
<div class="loop-layer-map" aria-label="Where different loop concepts live">
|
| 1800 |
<div class="loop-layer-item"><span>Inner loop</span><strong>Model recurrence</strong><p>A learned block refines hidden or latent state inside one inference. Included as an adjacent foundation.</p></div>
|
| 1801 |
<div class="loop-layer-item"><span>Task loop</span><strong>Agent execution</strong><p>The model reasons, calls tools, observes results, and updates working state while solving one task.</p></div>
|
|
@@ -1879,7 +1879,7 @@
|
|
| 1879 |
<button class="resource-collection" type="button" data-collection="Apply" aria-pressed="false"><i class="icon" data-lucide="package-open" aria-hidden="true"></i>Apply</button>
|
| 1880 |
</div>
|
| 1881 |
<div class="resource-summary">
|
| 1882 |
-
<p class="resource-count" id="resource-count" aria-live="polite">Preparing
|
| 1883 |
<label>
|
| 1884 |
<span class="sr-only">Sort resources</span>
|
| 1885 |
<select class="resource-select resource-sort" id="resource-sort">
|
|
@@ -2483,7 +2483,7 @@
|
|
| 2483 |
loading = true;
|
| 2484 |
explorer.dataset.indexState = 'loading';
|
| 2485 |
list.setAttribute('aria-busy', 'true');
|
| 2486 |
-
count.textContent = 'Loading
|
| 2487 |
list.replaceChildren(createText('p', 'resource-loading', 'Loading resources...'));
|
| 2488 |
|
| 2489 |
fetch('assets/resources.json')
|
|
|
|
| 4 |
<meta charset="utf-8">
|
| 5 |
<meta name="viewport" content="width=device-width, initial-scale=1">
|
| 6 |
<title>Awesome Loop Engineering</title>
|
| 7 |
+
<meta name="description" content="Explore 671 resources from model recurrence to governed agent operations, then build with 22 patterns, 22 contracts, and 8 runtime starters.">
|
| 8 |
<meta name="robots" content="index,follow">
|
| 9 |
<meta name="author" content="Chaoyue He">
|
| 10 |
<link rel="canonical" href="https://chaoyue0307.github.io/awesome-loop-engineering/">
|
|
|
|
| 15 |
<link href="https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@500;600&family=Inter:wght@400;500;600;700;800&display=swap" rel="stylesheet">
|
| 16 |
<meta property="og:type" content="website">
|
| 17 |
<meta property="og:title" content="Awesome Loop Engineering">
|
| 18 |
+
<meta property="og:description" content="Explore 669 papers, docs, tools, benchmarks, and guides, then build recurring agent systems with 22 patterns, 22 contracts, and 8 starters.">
|
| 19 |
<meta property="og:url" content="https://chaoyue0307.github.io/awesome-loop-engineering/">
|
| 20 |
+
<meta property="og:image" content="https://chaoyue0307.github.io/awesome-loop-engineering/assets/social-preview-671-v10.png">
|
| 21 |
<meta property="og:image:width" content="1280">
|
| 22 |
<meta property="og:image:height" content="640">
|
| 23 |
<meta property="og:image:alt" content="Awesome Loop Engineering: design loops, not just prompts.">
|
| 24 |
<meta name="twitter:card" content="summary_large_image">
|
| 25 |
<meta name="twitter:title" content="Awesome Loop Engineering">
|
| 26 |
+
<meta name="twitter:description" content="671 resources from model recurrence to agent operations, plus 22 patterns, 22 contracts, and 8 starters for building reliable loops.">
|
| 27 |
+
<meta name="twitter:image" content="https://chaoyue0307.github.io/awesome-loop-engineering/assets/social-preview-671-v10.png">
|
| 28 |
<link rel="alternate" type="application/atom+xml" title="Awesome Loop Engineering releases" href="https://github.com/ChaoYue0307/awesome-loop-engineering/releases.atom">
|
| 29 |
<link rel="alternate" type="application/atom+xml" title="Awesome Loop Engineering commits" href="https://github.com/ChaoYue0307/awesome-loop-engineering/commits/main.atom">
|
| 30 |
<style>
|
|
|
|
| 1307 |
"https://huggingface.co/datasets/cy0307/awesome-loop-engineering"
|
| 1308 |
],
|
| 1309 |
"license": "https://creativecommons.org/publicdomain/zero/1.0/",
|
| 1310 |
+
"image": "https://chaoyue0307.github.io/awesome-loop-engineering/assets/social-preview-671-v10.png",
|
| 1311 |
"logo": "https://chaoyue0307.github.io/awesome-loop-engineering/assets/awesome-loop-engineering-logo.png",
|
| 1312 |
"author": { "@type": "Person", "name": "Chaoyue He" }
|
| 1313 |
}
|
|
|
|
| 1355 |
"@context": "https://schema.org",
|
| 1356 |
"@type": "Dataset",
|
| 1357 |
"name": "Awesome Loop Engineering resources",
|
| 1358 |
+
"description": "Explore 671 resources across model, agent, harness, workflow, operations, and evaluation layers, with publication, contribution, novelty, impact, and evidence fields.",
|
| 1359 |
"url": "https://chaoyue0307.github.io/awesome-loop-engineering/",
|
| 1360 |
"sameAs": [
|
| 1361 |
"https://huggingface.co/datasets/cy0307/awesome-loop-engineering",
|
|
|
|
| 1430 |
<p class="section-label hero-kicker"><i class="icon" data-lucide="repeat-2" aria-hidden="true"></i><span>Field guide for recurring agent systems</span></p>
|
| 1431 |
<h1>Awesome Loop Engineering</h1>
|
| 1432 |
<p class="tagline">Design loops, not just prompts.</p>
|
| 1433 |
+
<p class="lead">Explore 671 resources from model recurrence to agent operations, then build with 22 patterns, 22 adaptable contracts, and 8 runtime starters.</p>
|
| 1434 |
<div class="actions">
|
| 1435 |
<a class="button primary" href="https://github.com/ChaoYue0307/awesome-loop-engineering#readme"><i class="icon" data-lucide="book-open" aria-hidden="true"></i>Explore resources</a>
|
| 1436 |
<a class="button" href="#choose"><i class="icon" data-lucide="compass" aria-hidden="true"></i>Choose a loop</a>
|
|
|
|
| 1493 |
</div>
|
| 1494 |
</figure>
|
| 1495 |
<div class="stats" role="list" aria-label="Field guide at a glance">
|
| 1496 |
+
<div class="stat" role="listitem"><b><i class="icon" data-lucide="library" aria-hidden="true"></i>671</b><span>resources</span></div>
|
| 1497 |
<div class="stat" role="listitem"><b><i class="icon" data-lucide="blocks" aria-hidden="true"></i>20</b><span>operational patterns</span></div>
|
| 1498 |
<div class="stat" role="listitem"><b><i class="icon" data-lucide="file-check-2" aria-hidden="true"></i>20</b><span>loop contracts</span></div>
|
| 1499 |
<div class="stat" role="listitem"><b><i class="icon" data-lucide="play" aria-hidden="true"></i>8</b><span>runtime starters</span></div>
|
|
|
|
| 1793 |
<p class="section-label"><i class="icon" data-lucide="library" aria-hidden="true"></i><span>06 / Resource atlas</span></p>
|
| 1794 |
<h2>Find evidence, not just links.</h2>
|
| 1795 |
</div>
|
| 1796 |
+
<p class="section-intro">Filter 671 resources by goal, loop layer, lifecycle, artifact type, and evidence class. Open any result to see its contribution, novelty, impact, scope, publication details, and original source.</p>
|
| 1797 |
</div>
|
| 1798 |
+
<p class="audit-note"><strong>Last source check, 2026-07-21 UTC:</strong> 618 public links opened successfully, 2 required access, 49 point to files in this repository, and none were broken or unreachable. <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/data/resource_source_audit.csv">View the results</a> or <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=annotation-correction.yml">report a correction</a>.</p>
|
| 1799 |
<div class="loop-layer-map" aria-label="Where different loop concepts live">
|
| 1800 |
<div class="loop-layer-item"><span>Inner loop</span><strong>Model recurrence</strong><p>A learned block refines hidden or latent state inside one inference. Included as an adjacent foundation.</p></div>
|
| 1801 |
<div class="loop-layer-item"><span>Task loop</span><strong>Agent execution</strong><p>The model reasons, calls tools, observes results, and updates working state while solving one task.</p></div>
|
|
|
|
| 1879 |
<button class="resource-collection" type="button" data-collection="Apply" aria-pressed="false"><i class="icon" data-lucide="package-open" aria-hidden="true"></i>Apply</button>
|
| 1880 |
</div>
|
| 1881 |
<div class="resource-summary">
|
| 1882 |
+
<p class="resource-count" id="resource-count" aria-live="polite">Preparing 671 resources...</p>
|
| 1883 |
<label>
|
| 1884 |
<span class="sr-only">Sort resources</span>
|
| 1885 |
<select class="resource-select resource-sort" id="resource-sort">
|
|
|
|
| 2483 |
loading = true;
|
| 2484 |
explorer.dataset.indexState = 'loading';
|
| 2485 |
list.setAttribute('aria-busy', 'true');
|
| 2486 |
+
count.textContent = 'Loading 671 resources...';
|
| 2487 |
list.replaceChildren(createText('p', 'resource-loading', 'Loading resources...'));
|
| 2488 |
|
| 2489 |
fetch('assets/resources.json')
|
docs/x-v10-671.html
ADDED
|
@@ -0,0 +1,44 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<!doctype html>
|
| 2 |
+
<html lang="en">
|
| 3 |
+
<head>
|
| 4 |
+
<meta charset="utf-8">
|
| 5 |
+
<meta name="viewport" content="width=device-width, initial-scale=1">
|
| 6 |
+
<title>Awesome Loop Engineering: 671 resources from model recurrence to agent operations</title>
|
| 7 |
+
<meta name="description" content="Explore 671 resources, then build recurring AI-agent systems with 22 patterns, 22 contracts, and 8 runtime starters.">
|
| 8 |
+
<meta name="robots" content="noindex,follow">
|
| 9 |
+
<link rel="canonical" href="https://chaoyue0307.github.io/awesome-loop-engineering/x-v10-671.html">
|
| 10 |
+
<meta property="og:type" content="website">
|
| 11 |
+
<meta property="og:title" content="Awesome Loop Engineering">
|
| 12 |
+
<meta property="og:description" content="669 papers, docs, tools, benchmarks, and guides, plus 22 patterns, 22 contracts, and 8 starters for recurring AI-agent systems.">
|
| 13 |
+
<meta property="og:url" content="https://chaoyue0307.github.io/awesome-loop-engineering/x-v10-671.html">
|
| 14 |
+
<meta property="og:image" content="https://chaoyue0307.github.io/awesome-loop-engineering/assets/social-preview-671-v10.png">
|
| 15 |
+
<meta property="og:image:width" content="1280">
|
| 16 |
+
<meta property="og:image:height" content="640">
|
| 17 |
+
<meta property="og:image:alt" content="Awesome Loop Engineering: 671 resources, 22 patterns, 22 contracts, and 8 runtime starters.">
|
| 18 |
+
<meta name="twitter:card" content="summary_large_image">
|
| 19 |
+
<meta name="twitter:title" content="Awesome Loop Engineering">
|
| 20 |
+
<meta name="twitter:description" content="From looped models to verified agent work and bounded operations.">
|
| 21 |
+
<meta name="twitter:image" content="https://chaoyue0307.github.io/awesome-loop-engineering/assets/social-preview-671-v10.png">
|
| 22 |
+
<meta name="twitter:image:alt" content="Awesome Loop Engineering: design loops, not just prompts.">
|
| 23 |
+
<link rel="icon" href="assets/favicon-32.png" type="image/png" sizes="32x32">
|
| 24 |
+
<style>
|
| 25 |
+
:root { color-scheme: light; font-family: Inter, ui-sans-serif, system-ui, sans-serif; }
|
| 26 |
+
body { display: grid; min-height: 100vh; margin: 0; place-items: center; background: #f7f9fc; color: #111827; }
|
| 27 |
+
main { width: min(88vw, 420px); text-align: center; }
|
| 28 |
+
img { width: 72px; height: 72px; }
|
| 29 |
+
p { color: #526176; line-height: 1.6; }
|
| 30 |
+
a { color: #1d4ed8; font-weight: 700; }
|
| 31 |
+
</style>
|
| 32 |
+
<script>
|
| 33 |
+
window.location.replace("https://chaoyue0307.github.io/awesome-loop-engineering/?utm_source=x&utm_medium=social&utm_campaign=v0.10.0");
|
| 34 |
+
</script>
|
| 35 |
+
</head>
|
| 36 |
+
<body>
|
| 37 |
+
<main>
|
| 38 |
+
<img src="assets/awesome-loop-engineering-logo.png" alt="Awesome Loop Engineering">
|
| 39 |
+
<h1>Awesome Loop Engineering</h1>
|
| 40 |
+
<p>Opening the interactive Resource Atlas.</p>
|
| 41 |
+
<p><a href="https://chaoyue0307.github.io/awesome-loop-engineering/?utm_source=x&utm_medium=social&utm_campaign=v0.10.0">Continue to the site</a></p>
|
| 42 |
+
</main>
|
| 43 |
+
</body>
|
| 44 |
+
</html>
|
examples/agent-memory-lifecycle-loop.json
ADDED
|
@@ -0,0 +1,103 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
{
|
| 2 |
+
"name": "Agent memory lifecycle loop",
|
| 3 |
+
"objective": "Carry governed operational memory between recurring agent runs: explicitly written, scoped on recall, audited, consolidated, and deletable.",
|
| 4 |
+
"trigger": {
|
| 5 |
+
"type": "scheduled",
|
| 6 |
+
"cadence_or_event": "Weekly consolidation pass, plus a session-end candidate-write hook after each run."
|
| 7 |
+
},
|
| 8 |
+
"intake": {
|
| 9 |
+
"sources": [
|
| 10 |
+
"candidate records from recent runs",
|
| 11 |
+
"live memory store with provenance",
|
| 12 |
+
"retention and privacy policy",
|
| 13 |
+
"audit log",
|
| 14 |
+
"recall-scope definitions"
|
| 15 |
+
],
|
| 16 |
+
"selection_rule": "Process only candidate records written since the last pass and live records due for audit, expiry, or review."
|
| 17 |
+
},
|
| 18 |
+
"workspace": {
|
| 19 |
+
"isolation": "Staging area for candidate records; the live store changes only through gated promotion.",
|
| 20 |
+
"allowed_actions": [
|
| 21 |
+
"distill run artifacts into candidate records",
|
| 22 |
+
"deduplicate and merge with provenance",
|
| 23 |
+
"audit for staleness, contradiction, and scope creep",
|
| 24 |
+
"apply logged expiries and redactions",
|
| 25 |
+
"run recall-scope test queries"
|
| 26 |
+
],
|
| 27 |
+
"disallowed_actions": [
|
| 28 |
+
"store raw transcripts or credentials",
|
| 29 |
+
"delete audited records silently",
|
| 30 |
+
"write to the live store without promotion",
|
| 31 |
+
"broaden a record's recall scope without review"
|
| 32 |
+
]
|
| 33 |
+
},
|
| 34 |
+
"context": {
|
| 35 |
+
"required_files": [
|
| 36 |
+
"memory store manifest",
|
| 37 |
+
"retention and privacy policy",
|
| 38 |
+
"recall-scope map",
|
| 39 |
+
"audit log"
|
| 40 |
+
],
|
| 41 |
+
"runtime_sources": [
|
| 42 |
+
"session-end run artifacts",
|
| 43 |
+
"quarantine queue",
|
| 44 |
+
"recall test results"
|
| 45 |
+
]
|
| 46 |
+
},
|
| 47 |
+
"agents": [
|
| 48 |
+
{
|
| 49 |
+
"role": "recorder",
|
| 50 |
+
"responsibility": "Distill each finished run into explicit candidate records instead of raw transcripts."
|
| 51 |
+
},
|
| 52 |
+
{
|
| 53 |
+
"role": "auditor",
|
| 54 |
+
"responsibility": "Flag stale, contradictory, sensitive, or unattributed records and quarantine failures."
|
| 55 |
+
},
|
| 56 |
+
{
|
| 57 |
+
"role": "consolidator",
|
| 58 |
+
"responsibility": "Merge duplicates, promote repeated lessons to principle-level records, and retire superseded ones."
|
| 59 |
+
},
|
| 60 |
+
{
|
| 61 |
+
"role": "recall gate",
|
| 62 |
+
"responsibility": "Scope what each future run may read by task and access class, and verify scopes with test recalls."
|
| 63 |
+
}
|
| 64 |
+
],
|
| 65 |
+
"verification": {
|
| 66 |
+
"gates": [
|
| 67 |
+
"every record carries provenance, scope, and an expiry or review date",
|
| 68 |
+
"no raw transcript, credential, or policy-barred content in the live store",
|
| 69 |
+
"contradictory records cannot coexist unresolved",
|
| 70 |
+
"recall tests retrieve intended records and nothing out of scope",
|
| 71 |
+
"deletions and redactions are logged and reversible for the review window"
|
| 72 |
+
],
|
| 73 |
+
"receipts": [
|
| 74 |
+
"consolidation receipt linking merged, promoted, and retired records",
|
| 75 |
+
"audit log entries for every write, merge, prune, and redaction"
|
| 76 |
+
]
|
| 77 |
+
},
|
| 78 |
+
"state": {
|
| 79 |
+
"artifacts": [
|
| 80 |
+
"memory store with typed records",
|
| 81 |
+
"audit log of writes, merges, prunes, and redactions",
|
| 82 |
+
"consolidation receipts"
|
| 83 |
+
],
|
| 84 |
+
"update_rule": "Only promoted records enter the live store; quarantined and expired records never recall; every mutation appends to the audit log."
|
| 85 |
+
},
|
| 86 |
+
"budget": {
|
| 87 |
+
"max_retries": 1,
|
| 88 |
+
"max_runtime_minutes": 60
|
| 89 |
+
},
|
| 90 |
+
"escalation": {
|
| 91 |
+
"conditions": [
|
| 92 |
+
"sensitive or ambiguous records",
|
| 93 |
+
"contradiction between operator instruction and remembered preference",
|
| 94 |
+
"retention-policy questions",
|
| 95 |
+
"records whose provenance does not trace to a legitimate run"
|
| 96 |
+
],
|
| 97 |
+
"destination": "Review queue with the quarantined records and their provenance evidence."
|
| 98 |
+
},
|
| 99 |
+
"exit": {
|
| 100 |
+
"success": "All candidates processed, audits clean, recall-scope tests pass, and the receipt is written.",
|
| 101 |
+
"stop_without_success": "Churn cap reached or policy failures found; the live store keeps its last audited state."
|
| 102 |
+
}
|
| 103 |
+
}
|
examples/fleet-coordination-loop.json
ADDED
|
@@ -0,0 +1,102 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
{
|
| 2 |
+
"name": "Fleet coordination loop",
|
| 3 |
+
"objective": "Land many parallel agent-authored changes on one codebase without collisions, duplicate work, or unverified merges.",
|
| 4 |
+
"trigger": {
|
| 5 |
+
"type": "event",
|
| 6 |
+
"cadence_or_event": "Continuous while the task backlog is non-empty, within a wall-clock window."
|
| 7 |
+
},
|
| 8 |
+
"intake": {
|
| 9 |
+
"sources": [
|
| 10 |
+
"task backlog with priorities and dependencies",
|
| 11 |
+
"claim ledger",
|
| 12 |
+
"repository protected-branch and required-check configuration",
|
| 13 |
+
"fleet policy for concurrency and budgets"
|
| 14 |
+
],
|
| 15 |
+
"selection_rule": "Dispatch only unclaimed ready tasks whose dependencies have landed, up to the concurrency cap."
|
| 16 |
+
},
|
| 17 |
+
"workspace": {
|
| 18 |
+
"isolation": "One worktree, branch, or container per worker; no shared mutable checkout.",
|
| 19 |
+
"allowed_actions": [
|
| 20 |
+
"claim a task through the ledger",
|
| 21 |
+
"implement the task in the owned workspace",
|
| 22 |
+
"submit a candidate branch",
|
| 23 |
+
"run the landing gate",
|
| 24 |
+
"land serially through the merge queue"
|
| 25 |
+
],
|
| 26 |
+
"disallowed_actions": [
|
| 27 |
+
"push directly to the integration branch",
|
| 28 |
+
"work an unclaimed task",
|
| 29 |
+
"edit files claimed by another live task",
|
| 30 |
+
"land a candidate that has not passed the gate after final rebase"
|
| 31 |
+
]
|
| 32 |
+
},
|
| 33 |
+
"context": {
|
| 34 |
+
"required_files": [
|
| 35 |
+
"task backlog",
|
| 36 |
+
"claim ledger",
|
| 37 |
+
"landing-gate definition",
|
| 38 |
+
"merge-queue state"
|
| 39 |
+
],
|
| 40 |
+
"runtime_sources": [
|
| 41 |
+
"live claim ledger",
|
| 42 |
+
"merge-queue state",
|
| 43 |
+
"landing-gate results"
|
| 44 |
+
]
|
| 45 |
+
},
|
| 46 |
+
"agents": [
|
| 47 |
+
{
|
| 48 |
+
"role": "dispatcher",
|
| 49 |
+
"responsibility": "Claim and assign tasks, reconcile stale claims, and enforce the concurrency cap."
|
| 50 |
+
},
|
| 51 |
+
{
|
| 52 |
+
"role": "worker",
|
| 53 |
+
"responsibility": "Implement one bounded task in an isolated workspace and submit a candidate change."
|
| 54 |
+
},
|
| 55 |
+
{
|
| 56 |
+
"role": "verifier",
|
| 57 |
+
"responsibility": "Run the landing gate on every candidate independently of the worker that produced it."
|
| 58 |
+
},
|
| 59 |
+
{
|
| 60 |
+
"role": "integrator",
|
| 61 |
+
"responsibility": "Serialize landings through the merge queue, rebasing and re-verifying on conflict."
|
| 62 |
+
}
|
| 63 |
+
],
|
| 64 |
+
"verification": {
|
| 65 |
+
"gates": [
|
| 66 |
+
"full landing gate passes after the candidate's final rebase",
|
| 67 |
+
"diff stays inside the claimed task scope",
|
| 68 |
+
"no two live claims cover the same task or protected files",
|
| 69 |
+
"integration branch stays green; a red landing halts the queue",
|
| 70 |
+
"every landing has a receipt linking task, worker, gate results, and commit"
|
| 71 |
+
],
|
| 72 |
+
"receipts": [
|
| 73 |
+
"landing receipt linking task, worker, gate results, and commit",
|
| 74 |
+
"fleet telemetry snapshot per wave"
|
| 75 |
+
]
|
| 76 |
+
},
|
| 77 |
+
"state": {
|
| 78 |
+
"artifacts": [
|
| 79 |
+
"claim ledger",
|
| 80 |
+
"merge-queue state and landing receipts",
|
| 81 |
+
"fleet telemetry"
|
| 82 |
+
],
|
| 83 |
+
"update_rule": "Claims and landings mutate only through the ledger and merge queue; unfinished tasks return to the backlog with their evidence attached."
|
| 84 |
+
},
|
| 85 |
+
"budget": {
|
| 86 |
+
"max_retries": 2,
|
| 87 |
+
"max_runtime_minutes": 480
|
| 88 |
+
},
|
| 89 |
+
"escalation": {
|
| 90 |
+
"conditions": [
|
| 91 |
+
"a task fails its gate repeatedly",
|
| 92 |
+
"two tasks genuinely require the same files",
|
| 93 |
+
"gate infrastructure breaks",
|
| 94 |
+
"landing order forces a product decision"
|
| 95 |
+
],
|
| 96 |
+
"destination": "Escalation queue with the candidate branch, gate evidence, and claim history."
|
| 97 |
+
},
|
| 98 |
+
"exit": {
|
| 99 |
+
"success": "Backlog empty with all landings receipted and the integration branch green.",
|
| 100 |
+
"stop_without_success": "Budget spent or the branch cannot be kept green; remaining tasks return to the backlog with evidence."
|
| 101 |
+
}
|
| 102 |
+
}
|
meta/DISTRIBUTION.md
CHANGED
|
@@ -8,7 +8,7 @@ Status as of 2026-07-20:
|
|
| 8 |
|
| 9 |
| Surface | Status | Evidence / next action |
|
| 10 |
| --- | --- | --- |
|
| 11 |
-
| GitHub release | Complete | [`v0.9.0`](https://github.com/ChaoYue0307/awesome-loop-engineering/releases/tag/v0.9.0) packages
|
| 12 |
| Release announcement | Ready | Publish the v0.9.0 summary from [`posts/launch.md`](../posts/launch.md); [Discussion #9](https://github.com/ChaoYue0307/awesome-loop-engineering/discussions/9) is the low-noise release and contributor feed. |
|
| 13 |
| GitHub Explore topic | Complete | [`github/explore#5209`](https://github.com/github/explore/pull/5209) merged the `loop-engineering` topic page. |
|
| 14 |
| Canonical Awesome directory | Policy objection | [`sindresorhus/awesome#4339`](https://github.com/sindresorhus/awesome/pull/4339) is open and lint passes, but the owner stated that AI-generated lists are not accepted. Do not treat further visual polish as a path around that policy or misrepresent automated assistance. |
|
|
@@ -50,7 +50,7 @@ Use GitHub-native discovery in this order.
|
|
| 50 |
```
|
| 51 |
|
| 52 |
- **Pin the repository** on your profile, and add it to your profile README (profile-level promotion).
|
| 53 |
-
- **About description.** Keep this concise value statement aligned with the README and project site: `🔁 Build reliable recurring AI-agent systems:
|
| 54 |
- **Custom social preview** (repo Settings, Social preview) so shared links lead with the same four durable proof points. This is UI-only; it cannot be set through the API.
|
| 55 |
- **Releases and Discussions** provide a lower-noise subscription path. Recommend `Watch -> Custom -> Releases and Discussions`; do not ask readers to watch every repository event.
|
| 56 |
|
|
@@ -95,7 +95,7 @@ Use the [English launch article](../posts/launch.md) or [Chinese launch article]
|
|
| 95 |
```text
|
| 96 |
🔁 Awesome Loop Engineering maps how recurring AI agents should act, verify, remember, retry, and stop.
|
| 97 |
|
| 98 |
-
|
| 99 |
|
| 100 |
Explore and build:
|
| 101 |
https://github.com/ChaoYue0307/awesome-loop-engineering
|
|
@@ -105,7 +105,7 @@ https://github.com/ChaoYue0307/awesome-loop-engineering
|
|
| 105 |
|
| 106 |
Attach [`assets/social-preview.png`](../assets/social-preview.png) directly when the platform permits it. The post is 264 characters before platform-specific URL shortening.
|
| 107 |
|
| 108 |
-
For a fresh link card on X or LinkedIn, share <https://chaoyue0307.github.io/awesome-loop-engineering/x-v10-
|
| 109 |
|
| 110 |
### Chinese Short Post
|
| 111 |
|
|
@@ -132,7 +132,7 @@ The release includes:
|
|
| 132 |
- 669 papers, docs, tools, benchmarks, and guides
|
| 133 |
- 29 model-layer resources, including Loopie, labeled as adjacent foundations
|
| 134 |
- an interactive Resource Atlas
|
| 135 |
-
-
|
| 136 |
- 8 runtime starters: 3 executables and 5 copy/paste templates
|
| 137 |
- 50-field CSV, JSONL, and Parquet exports mirrored to Hugging Face
|
| 138 |
- source and evidence fields, with point-in-time link-check results
|
|
@@ -146,11 +146,11 @@ https://github.com/ChaoYue0307/awesome-loop-engineering
|
|
| 146 |
Use a regular submission, not Show HN.
|
| 147 |
|
| 148 |
```text
|
| 149 |
-
Title: Awesome Loop Engineering:
|
| 150 |
|
| 151 |
I have been mapping recurring AI-agent systems: how work enters, agents act, evidence gates results, state survives, and the system retries, escalates, or exits.
|
| 152 |
|
| 153 |
-
The repository connects 669 papers, docs, tools, benchmarks, and guides across model, agent, harness, workflow, operations, and evaluation layers with
|
| 154 |
|
| 155 |
https://github.com/ChaoYue0307/awesome-loop-engineering
|
| 156 |
```
|
|
|
|
| 8 |
|
| 9 |
| Surface | Status | Evidence / next action |
|
| 10 |
| --- | --- | --- |
|
| 11 |
+
| GitHub release | Complete | [`v0.9.0`](https://github.com/ChaoYue0307/awesome-loop-engineering/releases/tag/v0.9.0) packages 671 resources, 22 patterns and contracts, 8 runtime starters, and explicit model-to-operations scope facets. |
|
| 12 |
| Release announcement | Ready | Publish the v0.9.0 summary from [`posts/launch.md`](../posts/launch.md); [Discussion #9](https://github.com/ChaoYue0307/awesome-loop-engineering/discussions/9) is the low-noise release and contributor feed. |
|
| 13 |
| GitHub Explore topic | Complete | [`github/explore#5209`](https://github.com/github/explore/pull/5209) merged the `loop-engineering` topic page. |
|
| 14 |
| Canonical Awesome directory | Policy objection | [`sindresorhus/awesome#4339`](https://github.com/sindresorhus/awesome/pull/4339) is open and lint passes, but the owner stated that AI-generated lists are not accepted. Do not treat further visual polish as a path around that policy or misrepresent automated assistance. |
|
|
|
|
| 50 |
```
|
| 51 |
|
| 52 |
- **Pin the repository** on your profile, and add it to your profile README (profile-level promotion).
|
| 53 |
+
- **About description.** Keep this concise value statement aligned with the README and project site: `🔁 Build reliable recurring AI-agent systems: 671 resources, 22 operational patterns, 22 loop contracts, 8 runtime starters, an interactive atlas, and a structured dataset.`
|
| 54 |
- **Custom social preview** (repo Settings, Social preview) so shared links lead with the same four durable proof points. This is UI-only; it cannot be set through the API.
|
| 55 |
- **Releases and Discussions** provide a lower-noise subscription path. Recommend `Watch -> Custom -> Releases and Discussions`; do not ask readers to watch every repository event.
|
| 56 |
|
|
|
|
| 95 |
```text
|
| 96 |
🔁 Awesome Loop Engineering maps how recurring AI agents should act, verify, remember, retry, and stop.
|
| 97 |
|
| 98 |
+
671 resources · 22 patterns · 22 contracts · 8 starters
|
| 99 |
|
| 100 |
Explore and build:
|
| 101 |
https://github.com/ChaoYue0307/awesome-loop-engineering
|
|
|
|
| 105 |
|
| 106 |
Attach [`assets/social-preview.png`](../assets/social-preview.png) directly when the platform permits it. The post is 264 characters before platform-specific URL shortening.
|
| 107 |
|
| 108 |
+
For a fresh link card on X or LinkedIn, share <https://chaoyue0307.github.io/awesome-loop-engineering/x-v10-671.html>. The versioned URL points to the current preview image, records the `v0.10.0` campaign, and redirects readers to the interactive site.
|
| 109 |
|
| 110 |
### Chinese Short Post
|
| 111 |
|
|
|
|
| 132 |
- 669 papers, docs, tools, benchmarks, and guides
|
| 133 |
- 29 model-layer resources, including Loopie, labeled as adjacent foundations
|
| 134 |
- an interactive Resource Atlas
|
| 135 |
+
- 22 operational patterns and 22 adaptable loop contracts
|
| 136 |
- 8 runtime starters: 3 executables and 5 copy/paste templates
|
| 137 |
- 50-field CSV, JSONL, and Parquet exports mirrored to Hugging Face
|
| 138 |
- source and evidence fields, with point-in-time link-check results
|
|
|
|
| 146 |
Use a regular submission, not Show HN.
|
| 147 |
|
| 148 |
```text
|
| 149 |
+
Title: Awesome Loop Engineering: 671 resources from looped models to agent operations
|
| 150 |
|
| 151 |
I have been mapping recurring AI-agent systems: how work enters, agents act, evidence gates results, state survives, and the system retries, escalates, or exits.
|
| 152 |
|
| 153 |
+
The repository connects 669 papers, docs, tools, benchmarks, and guides across model, agent, harness, workflow, operations, and evaluation layers with 22 operational patterns, 22 adaptable contracts, 8 runtime starters, an interactive Resource Atlas, and a structured Hugging Face dataset. Model-level recurrence is labeled as an adjacent foundation rather than a complete operational loop. Corrections to source links, taxonomy, and summaries are especially welcome.
|
| 154 |
|
| 155 |
https://github.com/ChaoYue0307/awesome-loop-engineering
|
| 156 |
```
|
meta/social-preview.html
CHANGED
|
@@ -79,9 +79,9 @@
|
|
| 79 |
<p>Model / agent / operations</p>
|
| 80 |
</div>
|
| 81 |
<div class="stats">
|
| 82 |
-
<div class="stat"><b>
|
| 83 |
-
<div class="stat"><b>
|
| 84 |
-
<div class="stat"><b>
|
| 85 |
<div class="stat"><b>8</b><span>Runtime starters</span></div>
|
| 86 |
</div>
|
| 87 |
</main>
|
|
|
|
| 79 |
<p>Model / agent / operations</p>
|
| 80 |
</div>
|
| 81 |
<div class="stats">
|
| 82 |
+
<div class="stat"><b>671</b><span>Papers, docs, tools + guides</span></div>
|
| 83 |
+
<div class="stat"><b>22</b><span>Operational patterns</span></div>
|
| 84 |
+
<div class="stat"><b>22</b><span>Schema-checked contracts</span></div>
|
| 85 |
<div class="stat"><b>8</b><span>Runtime starters</span></div>
|
| 86 |
</div>
|
| 87 |
</main>
|
patterns/MATRIX.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
| 1 |
# Pattern Matrix
|
| 2 |
|
| 3 |
-
A side-by-side comparison of all
|
| 4 |
|
| 5 |
## How To Read This Matrix
|
| 6 |
|
|
@@ -37,6 +37,8 @@ Every pattern links to its full write-up and a schema-valid contract in [`exampl
|
|
| 37 |
| [Incident response loop](incident-response-loop.md) | An incident just paged | Event: alert; refresh 2-5 min | Alert, dashboards, traces, changes | Incident timeline, hypotheses | Severity backed by impact evidence | 2 retries / incident life | Outage, data loss, or mitigation needed | Custom durable runtime, shell/cron |
|
| 38 |
| [Data-quality loop](data-quality-loop.md) | A dataset keeps drifting | Event: refresh; or nightly | New version, schema, prior baseline | Profile metrics, accepted exceptions | Hard rules pass before promotion | 2 retries / 90 min | Schema change or regulated fields | Custom durable runtime, shell/cron |
|
| 39 |
| [Knowledge freshness loop](knowledge-freshness-loop.md) | An agent knowledge index is stale | Daily refresh + source change | Approved sources, manifest, retrieval evals | Versioned index, provenance, tombstones | Freshness, retrieval, leakage, atomic promotion | 2 retries / 120 min | Source conflict, access change, sensitive data | Custom durable runtime, scheduled task |
|
|
|
|
|
|
|
| 40 |
| [Release-note loop](release-note-loop.md) | Release notes are a chore | Event: release branch or tag | Merged PRs, issues, commits | Processed IDs, draft changelog | Every entry links to a source | 2 retries / 60 min | Security advisories or wording calls | gh-aw, Codex automations |
|
| 41 |
| [Model-routing loop](model-routing-loop.md) | Model choice is ad hoc | Schedule + model/price change | Per-task telemetry, eval results | Task-class metrics, routing log | Replays hold quality within tolerance | 2 retries / 120 min | Privacy tier or quality-cost tradeoffs | Custom durable runtime |
|
| 42 |
|
|
|
|
| 1 |
# Pattern Matrix
|
| 2 |
|
| 3 |
+
A side-by-side comparison of all 22 loops in the [pattern library](README.md). Use it to pick a pattern, compare trade-offs, or check that your own loop names the same parts.
|
| 4 |
|
| 5 |
## How To Read This Matrix
|
| 6 |
|
|
|
|
| 37 |
| [Incident response loop](incident-response-loop.md) | An incident just paged | Event: alert; refresh 2-5 min | Alert, dashboards, traces, changes | Incident timeline, hypotheses | Severity backed by impact evidence | 2 retries / incident life | Outage, data loss, or mitigation needed | Custom durable runtime, shell/cron |
|
| 38 |
| [Data-quality loop](data-quality-loop.md) | A dataset keeps drifting | Event: refresh; or nightly | New version, schema, prior baseline | Profile metrics, accepted exceptions | Hard rules pass before promotion | 2 retries / 90 min | Schema change or regulated fields | Custom durable runtime, shell/cron |
|
| 39 |
| [Knowledge freshness loop](knowledge-freshness-loop.md) | An agent knowledge index is stale | Daily refresh + source change | Approved sources, manifest, retrieval evals | Versioned index, provenance, tombstones | Freshness, retrieval, leakage, atomic promotion | 2 retries / 120 min | Source conflict, access change, sensitive data | Custom durable runtime, scheduled task |
|
| 40 |
+
| [Agent memory lifecycle loop](agent-memory-lifecycle-loop.md) | Recurring runs cold-start or repeat mistakes | Weekly consolidation + session end | Candidate records, live store, retention policy | Typed records, audit log, receipts | Provenance, scope, contradiction, recall tests | 1 retry / 60 min | Sensitive records, contradictions, injection artifacts | Scheduled task, session hook |
|
| 41 |
+
| [Fleet coordination loop](fleet-coordination-loop.md) | Parallel agents collide or duplicate work | Continuous while backlog non-empty | Task backlog, claim ledger, fleet policy | Claim ledger, merge queue, telemetry | Landing gate after rebase, scoped diff, green branch | 2 retries / 480 min | Repeated gate failures, entangled tasks, product decisions | Merge queue, worktrees, CI |
|
| 42 |
| [Release-note loop](release-note-loop.md) | Release notes are a chore | Event: release branch or tag | Merged PRs, issues, commits | Processed IDs, draft changelog | Every entry links to a source | 2 retries / 60 min | Security advisories or wording calls | gh-aw, Codex automations |
|
| 43 |
| [Model-routing loop](model-routing-loop.md) | Model choice is ad hoc | Schedule + model/price change | Per-task telemetry, eval results | Task-class metrics, routing log | Replays hold quality within tolerance | 2 retries / 120 min | Privacy tier or quality-cost tradeoffs | Custom durable runtime |
|
| 44 |
|
patterns/agent-memory-lifecycle-loop.md
ADDED
|
@@ -0,0 +1,106 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# Agent Memory Lifecycle Loop
|
| 2 |
+
|
| 3 |
+
## Objective
|
| 4 |
+
|
| 5 |
+
Keep recurring agent work from cold-starting every run while the memory that carries between runs stays governed: explicitly written, scoped on recall, audited, consolidated, and deletable.
|
| 6 |
+
|
| 7 |
+
## Use This When
|
| 8 |
+
|
| 9 |
+
- An agent runs repeatedly against the same project, product, or user and repeats mistakes it already made.
|
| 10 |
+
- Prior-session state materially changes what the next run should do.
|
| 11 |
+
- Unbounded transcript carryover has caused stale, contradictory, or sensitive context to leak into later runs.
|
| 12 |
+
|
| 13 |
+
Use the knowledge-freshness loop when the durable product is a retrieval corpus assembled from external sources. Use this pattern when the durable product is the agent's own operational memory: lessons, decisions, preferences, warnings, and open threads.
|
| 14 |
+
|
| 15 |
+
## Trigger
|
| 16 |
+
|
| 17 |
+
- Schedule: consolidation pass daily or weekly; audit pass on a longer cadence.
|
| 18 |
+
- Event: session end, task completion, memory-store size or age threshold, or a policy change that affects retention.
|
| 19 |
+
- Manual bootstrap: "consolidate and audit the agent memory for <project>."
|
| 20 |
+
|
| 21 |
+
## Intake
|
| 22 |
+
|
| 23 |
+
- Candidate writes from recent runs: lessons, decisions, preferences, failures worth remembering.
|
| 24 |
+
- The current memory store with per-record provenance, timestamps, and access class.
|
| 25 |
+
- Retention, privacy, and escalation policy for what may be remembered at all.
|
| 26 |
+
|
| 27 |
+
## Agents
|
| 28 |
+
|
| 29 |
+
- Recorder: distills a finished run into explicit candidate records, never raw transcripts.
|
| 30 |
+
- Auditor: flags stale, contradictory, sensitive, or unattributed records.
|
| 31 |
+
- Consolidator: merges duplicates, promotes repeated lessons to principles, and prunes superseded records.
|
| 32 |
+
- Recall gate: scopes what each future run may read, by task and access class.
|
| 33 |
+
|
| 34 |
+
## Workspace And Permissions
|
| 35 |
+
|
| 36 |
+
- Memory writes go to a staging area; promotion to the live store is a separate gated step.
|
| 37 |
+
- Allow reads of run artifacts and the live store; allow writes only to staging and the audit log.
|
| 38 |
+
- Disallow storing raw transcripts, credentials, or personal data barred by policy, and disallow silent deletion of audited records.
|
| 39 |
+
|
| 40 |
+
## Durable State
|
| 41 |
+
|
| 42 |
+
- The memory store itself: typed records with provenance, scope, timestamps, and expiry or review dates.
|
| 43 |
+
- Audit log of writes, merges, prunes, redactions, and the run that caused each.
|
| 44 |
+
- Consolidation receipts: what was merged or promoted, and which records were retired.
|
| 45 |
+
|
| 46 |
+
## Loop Steps
|
| 47 |
+
|
| 48 |
+
1. Collect candidate records from runs since the last pass.
|
| 49 |
+
1. Reject candidates that violate retention or privacy policy at write time.
|
| 50 |
+
1. Deduplicate against the live store; merge near-duplicates with provenance preserved.
|
| 51 |
+
1. Audit the live store for staleness, contradiction, and scope creep; quarantine failures.
|
| 52 |
+
1. Consolidate repeated instance-level lessons into principle-level records.
|
| 53 |
+
1. Apply expiries: delete, redact, or send to review anything past its window.
|
| 54 |
+
1. Write the receipt and update recall scopes for the next run.
|
| 55 |
+
|
| 56 |
+
## Verification Gates
|
| 57 |
+
|
| 58 |
+
- Every record has provenance, a scope, and an expiry or review date.
|
| 59 |
+
- No raw transcript, credential, or policy-barred content is present in the live store.
|
| 60 |
+
- Contradictory records cannot coexist unresolved; the newer record must cite what it supersedes.
|
| 61 |
+
- Recall tests confirm the next run retrieves the intended records and nothing out of scope.
|
| 62 |
+
- Deletions and redactions are logged and reversible for the review window.
|
| 63 |
+
|
| 64 |
+
## Budget And Exit
|
| 65 |
+
|
| 66 |
+
- Max runtime: 30-60 minutes per consolidation pass.
|
| 67 |
+
- Max churn: cap the fraction of the store that one pass may merge or delete.
|
| 68 |
+
- Stop when candidates are exhausted, the churn cap is reached, or the audit finds policy failures that need a human.
|
| 69 |
+
|
| 70 |
+
## Escalation
|
| 71 |
+
|
| 72 |
+
Escalate for sensitive or ambiguous records, contradictions between an operator instruction and remembered preference, retention-policy questions, and any suspected memory-injection artifact: records whose provenance does not trace to a legitimate run.
|
| 73 |
+
|
| 74 |
+
## Loop Instruction
|
| 75 |
+
|
| 76 |
+
```text
|
| 77 |
+
Consolidate agent memory for <project>.
|
| 78 |
+
Distill recent runs into explicit candidate records; never store raw transcripts.
|
| 79 |
+
Deduplicate, audit for staleness and contradiction, consolidate repeated lessons into principles,
|
| 80 |
+
and apply expiries with logged, reversible deletions.
|
| 81 |
+
Verify recall scope with test queries before finishing.
|
| 82 |
+
Escalate sensitive records, unresolved contradictions, and any record whose provenance
|
| 83 |
+
does not trace to a legitimate run.
|
| 84 |
+
```
|
| 85 |
+
|
| 86 |
+
## Worked Example
|
| 87 |
+
|
| 88 |
+
A team runs a nightly PR-babysitter loop over one repository. Its weekly memory pass distills the week's runs into candidate lessons, merges three near-duplicate records about a flaky integration test into one principle with provenance, expires a remembered workaround that a merged fix made obsolete, quarantines one record whose provenance traces to no known run, and verifies with test recalls that the next babysitter run retrieves the flaky-test principle but not the retired workaround.
|
| 89 |
+
|
| 90 |
+
## Failure Modes
|
| 91 |
+
|
| 92 |
+
- Remembering transcripts instead of distilled records, so recall floods future runs with stale context.
|
| 93 |
+
- Treating the most recent or most assertive record as true when records contradict.
|
| 94 |
+
- Memory that only grows: no expiry, no consolidation, no deletion path.
|
| 95 |
+
- Poisoned records entering the store because writes are not gated by provenance checks.
|
| 96 |
+
- Recall without scoping, so unrelated tasks read each other's remembered state.
|
| 97 |
+
|
| 98 |
+
## Example Contract
|
| 99 |
+
|
| 100 |
+
- [`examples/agent-memory-lifecycle-loop.json`](../examples/agent-memory-lifecycle-loop.json)
|
| 101 |
+
|
| 102 |
+
## References
|
| 103 |
+
|
| 104 |
+
- [Always-On Agents: A Survey of Persistent Memory, State, and Governance in LLM Agents](https://arxiv.org/abs/2606.30306) - Finds the literature over-indexes on accumulating state and under-indexes on governing, recovering, or deleting it.
|
| 105 |
+
- [The Compliance Trap: Diagnosing How AI Agents Consume Conflicting Memory](https://arxiv.org/abs/2607.10608) - Shows agents tend to comply with the most recent or most assertive memory record rather than the correct one.
|
| 106 |
+
- [When Claws Remember but Do Not Tell: Stealthy Memory Injection in Persistent Personal Agents](https://arxiv.org/abs/2607.05189) - Demonstrates why memory writes need provenance gates: one poisoned input can silently steer future unattended runs.
|
patterns/fleet-coordination-loop.md
ADDED
|
@@ -0,0 +1,104 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# Fleet Coordination Loop
|
| 2 |
+
|
| 3 |
+
## Objective
|
| 4 |
+
|
| 5 |
+
Run many coding agents in parallel against one codebase or backlog without merge collisions, duplicated work, or unreviewed changes reaching the integration branch.
|
| 6 |
+
|
| 7 |
+
## Use This When
|
| 8 |
+
|
| 9 |
+
- More than a handful of agents work the same repository or task queue concurrently.
|
| 10 |
+
- Agent throughput is limited by coordination, not generation: collisions, rework, and review pile-ups.
|
| 11 |
+
- You can define a deterministic landing gate that every parallel change must pass before integration.
|
| 12 |
+
|
| 13 |
+
Use the PR-babysitter loop to shepherd a single change. Use this pattern when the unit of work is the fleet: assigning, isolating, verifying, and landing many parallel changes.
|
| 14 |
+
|
| 15 |
+
## Trigger
|
| 16 |
+
|
| 17 |
+
- Schedule: continuous while the backlog is non-empty, or in timed waves.
|
| 18 |
+
- Event: backlog growth past a threshold, a milestone branch opening, or a batch of verified tasks becoming ready.
|
| 19 |
+
- Manual bootstrap: "work this backlog with <N> parallel agents until the queue is empty or budget is spent."
|
| 20 |
+
|
| 21 |
+
## Intake
|
| 22 |
+
|
| 23 |
+
- The task backlog with priorities, dependencies, and claim status.
|
| 24 |
+
- Repository state: protected branches, required checks, and the landing gate definition.
|
| 25 |
+
- Fleet policy: max concurrency, per-agent budgets, and which task classes may run unattended.
|
| 26 |
+
|
| 27 |
+
## Agents
|
| 28 |
+
|
| 29 |
+
- Dispatcher: claims tasks, assigns them to workers, and prevents duplicate claims.
|
| 30 |
+
- Workers: implement one bounded task each inside an isolated workspace.
|
| 31 |
+
- Verifier: runs the landing gate on each candidate change independently of the worker that produced it.
|
| 32 |
+
- Integrator: serializes landings through a merge queue and resolves ordering.
|
| 33 |
+
|
| 34 |
+
## Workspace And Permissions
|
| 35 |
+
|
| 36 |
+
- One isolated worktree, branch, or container per worker; no shared mutable checkout.
|
| 37 |
+
- Allow workers to read the repository and write only to their own workspace and claim record.
|
| 38 |
+
- Disallow direct pushes to the integration branch, cross-worker file claims, and landing without the gate.
|
| 39 |
+
|
| 40 |
+
## Durable State
|
| 41 |
+
|
| 42 |
+
- The claim ledger: which agent owns which task, started when, with what budget remaining.
|
| 43 |
+
- Merge-queue state: ordered candidates, gate results, and landing receipts.
|
| 44 |
+
- Fleet telemetry: per-task cost, retry counts, collision events, and gate failures for tuning concurrency.
|
| 45 |
+
|
| 46 |
+
## Loop Steps
|
| 47 |
+
|
| 48 |
+
1. Refresh the backlog and reconcile stale claims from dead or expired workers.
|
| 49 |
+
1. Dispatch unclaimed ready tasks to idle workers up to the concurrency cap.
|
| 50 |
+
1. Each worker implements its task in isolation and submits a candidate change.
|
| 51 |
+
1. Verify each candidate with the landing gate: build, tests, lint, and scoped-diff checks.
|
| 52 |
+
1. Queue passing candidates; land them serially, rebasing or re-verifying on conflict.
|
| 53 |
+
1. Return failed candidates to their worker with evidence, up to the retry budget.
|
| 54 |
+
1. Record receipts and telemetry; adjust concurrency if collisions or costs trend up.
|
| 55 |
+
|
| 56 |
+
## Verification Gates
|
| 57 |
+
|
| 58 |
+
- Every landed change passed the full landing gate after its final rebase, not before.
|
| 59 |
+
- Each change's diff stays inside its claimed task scope.
|
| 60 |
+
- No two live claims cover the same task or the same protected files.
|
| 61 |
+
- The integration branch stays green: a failed landing halts the queue, not just the one change.
|
| 62 |
+
- Every landing has a receipt linking task, worker, gate results, and commit.
|
| 63 |
+
|
| 64 |
+
## Budget And Exit
|
| 65 |
+
|
| 66 |
+
- Per-task: bounded retries and runtime before the task returns to the backlog for a human.
|
| 67 |
+
- Per-fleet: max concurrent workers, total token or cost ceiling, and a wall-clock window.
|
| 68 |
+
- Stop when the backlog is empty, the budget is spent, or the integration branch cannot be kept green.
|
| 69 |
+
|
| 70 |
+
## Escalation
|
| 71 |
+
|
| 72 |
+
Escalate when the same task fails its gate repeatedly, two tasks genuinely require the same files, gate infrastructure itself breaks, or landing order forces a product decision no worker owns.
|
| 73 |
+
|
| 74 |
+
## Loop Instruction
|
| 75 |
+
|
| 76 |
+
```text
|
| 77 |
+
Work the backlog at <repo> with up to <N> parallel workers.
|
| 78 |
+
One isolated workspace per worker; claim tasks through the ledger, never work an unclaimed task.
|
| 79 |
+
Every candidate change must pass the landing gate after final rebase; land serially through the queue.
|
| 80 |
+
Return gate failures to the owning worker with evidence, within retry budget.
|
| 81 |
+
Halt the queue and escalate if the integration branch goes red or claims conflict.
|
| 82 |
+
```
|
| 83 |
+
|
| 84 |
+
## Worked Example
|
| 85 |
+
|
| 86 |
+
A migration backlog of 140 mechanical refactor tasks runs with twelve workers. The dispatcher hands out tasks by dependency order; each worker edits in its own worktree and submits a branch. The verifier runs build, tests, and a scoped-diff check per candidate; the merge queue lands nine changes per hour serially, bounces two candidates back with failing-test evidence, and reconciles one stale claim after a worker times out. The fleet exits with 137 landed, 3 escalated as genuinely entangled, and per-task receipts for review.
|
| 87 |
+
|
| 88 |
+
## Failure Modes
|
| 89 |
+
|
| 90 |
+
- Shared checkouts, so parallel edits trample each other before verification.
|
| 91 |
+
- Verifying before the final rebase and landing changes that break the branch anyway.
|
| 92 |
+
- Two workers silently duplicating one task because claims are advisory.
|
| 93 |
+
- Per-agent monitors missing fleet-level effects: correlated failures and coordinated drift.
|
| 94 |
+
- Scaling concurrency past what the merge queue and reviewers can absorb, converting throughput into backlog.
|
| 95 |
+
|
| 96 |
+
## Example Contract
|
| 97 |
+
|
| 98 |
+
- [`examples/fleet-coordination-loop.json`](../examples/fleet-coordination-loop.json)
|
| 99 |
+
|
| 100 |
+
## References
|
| 101 |
+
|
| 102 |
+
- [Scaling Long-Running Autonomous Coding](https://cursor.com/blog/scaling-agents) - Cursor's coordination designs, from flat agents with locking to a planner, worker, and judge hierarchy pushing to a single branch.
|
| 103 |
+
- [Multi-Agent AI Control: Distributed Attacks Hamper Per-Instance Monitors](https://arxiv.org/abs/2607.07368) - Shows per-agent monitors weaken as more agents coordinate, motivating fleet-level gates and telemetry.
|
| 104 |
+
- [claude-code-merge-queue](https://github.com/funador/claude-code-merge-queue) - A minimal landing gate: serialize parallel agents through a FIFO queue that blocks integration until a check command passes.
|
posts/launch.md
CHANGED
|
@@ -2,14 +2,14 @@
|
|
| 2 |
|
| 3 |
Awesome Loop Engineering v0.9.0 maps recurrence from a model's inner computation to an agent's tools and the outer operating loop that verifies, remembers, retries, escalates, and stops.
|
| 4 |
|
| 5 |
-
Explore
|
| 6 |
|
| 7 |
## What You Can Use
|
| 8 |
|
| 9 |
- 669 papers, official docs, tools, benchmarks, and guides linked to the original work
|
| 10 |
- 29 model-layer resources, from Universal Transformers and Huginn to Loopie, LoopCoder, and LoopWM, labeled as adjacent foundations rather than complete agent loops
|
| 11 |
-
-
|
| 12 |
-
-
|
| 13 |
- 8 runtime starters: 3 dependency-light executables and 5 copy/paste runtime templates
|
| 14 |
- an interactive Resource Atlas for filtering by goal, loop layer, lifecycle stage, artifact type, and evidence class
|
| 15 |
- 50-field CSV, JSONL, and Parquet exports mirrored as a Hugging Face dataset
|
|
|
|
| 2 |
|
| 3 |
Awesome Loop Engineering v0.9.0 maps recurrence from a model's inner computation to an agent's tools and the outer operating loop that verifies, remembers, retries, escalates, and stops.
|
| 4 |
|
| 5 |
+
Explore 671 resources without collapsing looped models, agent execution, harnesses, workflows, and production operations into one idea.
|
| 6 |
|
| 7 |
## What You Can Use
|
| 8 |
|
| 9 |
- 669 papers, official docs, tools, benchmarks, and guides linked to the original work
|
| 10 |
- 29 model-layer resources, from Universal Transformers and Huginn to Loopie, LoopCoder, and LoopWM, labeled as adjacent foundations rather than complete agent loops
|
| 11 |
+
- 22 operational patterns organized by build, operate, optimize, and govern use cases
|
| 12 |
+
- 22 schema-checked loop contracts, one for every pattern
|
| 13 |
- 8 runtime starters: 3 dependency-light executables and 5 copy/paste runtime templates
|
| 14 |
- an interactive Resource Atlas for filtering by goal, loop layer, lifecycle stage, artifact type, and evidence class
|
| 15 |
- 50-field CSV, JSONL, and Parquet exports mirrored as a Hugging Face dataset
|
posts/launch.zh-CN.md
CHANGED
|
@@ -2,11 +2,11 @@
|
|
| 2 |
|
| 3 |
Awesome Loop Engineering v0.9.0 建立了一张从模型内部递归、Agent 执行、Harness 到外层运行系统的完整地图。
|
| 4 |
|
| 5 |
-
可浏览
|
| 6 |
|
| 7 |
## 可直接使用
|
| 8 |
|
| 9 |
-
-
|
| 10 |
- 29 个模型层资源,覆盖 Universal Transformers、Huginn、Loopie、LoopCoder、LoopWM 等方向
|
| 11 |
- 20 个按 build、operate、optimize、govern 组织的 operational patterns
|
| 12 |
- 20 个经过 schema 校验的 loop contracts,每个 pattern 对应一个
|
|
|
|
| 2 |
|
| 3 |
Awesome Loop Engineering v0.9.0 建立了一张从模型内部递归、Agent 执行、Harness 到外层运行系统的完整地图。
|
| 4 |
|
| 5 |
+
可浏览 671 篇论文、官方文档、工具、benchmark 与实践指南,同时保持清晰边界:模型内的循环提供自适应计算,但不等于具备外部验证、持久状态、预算、人类交接与退出规则的运行级 Loop。
|
| 6 |
|
| 7 |
## 可直接使用
|
| 8 |
|
| 9 |
+
- 671 篇论文、官方文档、工具、benchmark 与实践指南,并直接链接原始来源
|
| 10 |
- 29 个模型层资源,覆盖 Universal Transformers、Huginn、Loopie、LoopCoder、LoopWM 等方向
|
| 11 |
- 20 个按 build、operate、optimize、govern 组织的 operational patterns
|
| 12 |
- 20 个经过 schema 校验的 loop contracts,每个 pattern 对应一个
|