Sync v0.6.0 source-audited release

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @ChaoYue0307

.github/ISSUE_TEMPLATE/annotation-correction.yml

@@ -0,0 +1,52 @@
+name: Annotation or metadata correction
+description: Correct a summary, contribution, novelty, impact, author, date, venue, identifier, or canonical link.
+title: "[Correction]: "
+labels:
+  - documentation
+body:
+  - type: input
+    id: entry
+    attributes:
+      label: Current entry
+      description: Link to the resource or the README section containing it.
+      placeholder: https://github.com/ChaoYue0307/awesome-loop-engineering#section
+    validations:
+      required: true
+  - type: textarea
+    id: current
+    attributes:
+      label: What is inaccurate or incomplete?
+      description: Quote only the short phrase or field that needs correction.
+      placeholder: The current annotation says...
+    validations:
+      required: true
+  - type: textarea
+    id: proposed
+    attributes:
+      label: Proposed correction
+      description: State the corrected contribution, novelty, impact, metadata, or canonical URL concisely.
+      placeholder: It should say...
+    validations:
+      required: true
+  - type: input
+    id: evidence
+    attributes:
+      label: Primary-source evidence
+      description: Link to the official page, paper record, documentation, or repository that supports the correction.
+      placeholder: https://example.com/canonical-source
+    validations:
+      required: true
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Add any material caveat, conflict, or source-access limitation.
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Checklist
+      options:
+        - label: I am asking for an accuracy correction, not promotional placement.
+          required: true
+        - label: I have linked the strongest canonical evidence available.
+          required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -1,7 +1,7 @@
 blank_issues_enabled: false
 contact_links:
   - name: Community pattern discussion
-    url: https://github.com/ChaoYue0307/awesome-loop-engineering/issues/1
+    url: https://github.com/ChaoYue0307/awesome-loop-engineering/discussions/2
     about: Share real-world Loop Engineering patterns, examples, and lessons learned.
   - name: Open a pull request
     url: https://github.com/ChaoYue0307/awesome-loop-engineering/compare

.github/pull_request_template.md

@@ -12,7 +12,7 @@ Select all that apply.
 
 ## Resource Summary
 
-List the resources, patterns, or translation files changed.
+List the resources, patterns, or translation files changed. For each resource, include the canonical URL and original publishing venue or platform.
 
 - Title and URL:
 
@@ -76,6 +76,14 @@ Which README section did you update?
 - [ ] Tier C: curated survey or high-quality explainer
 - [ ] Tier D: commentary or news coverage
 
+## Accuracy And Provenance
+
+- Canonical 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.
@@ -83,10 +91,14 @@ Which README section did you update?
 - [ ] 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 format: `- 📄 **Paper** [Title](https://example.com) - One sentence annotation.`
+- [ ] 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 canonical 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.

.github/workflows/quality.yml

@@ -54,6 +54,12 @@ jobs:
       - name: Check resource dataset export
         run: python scripts/export_resource_dataset.py --check
 
+      - name: Check project count and release consistency
+        run: python scripts/check_project_consistency.py
+
+      - name: Check Hugging Face dataset card
+        run: python scripts/build_hf_card.py --check
+
       - name: Check publication metadata
         run: python scripts/check_publication_metadata.py
 

CITATION.bib

@@ -3,5 +3,5 @@
   title        = {Awesome Loop Engineering},
   year         = {2026},
   howpublished = {\url{https://github.com/ChaoYue0307/awesome-loop-engineering}},
-  note         = {Curated resources for Loop Engineering}
+  note         = {Curated resources for Loop Engineering, version 0.6.0}
 }

CITATION.cff

@@ -2,6 +2,8 @@ cff-version: 1.2.0
 message: "If this repository is useful in your work, please cite it as below."
 title: "Awesome Loop Engineering"
 type: software
+version: 0.6.0
+date-released: 2026-07-17
 authors:
   - family-names: "He"
     given-names: "Chaoyue"

CONTRIBUTING.md

@@ -18,6 +18,8 @@ If you are suggesting one resource and do not want to prepare a fork, use the [r
 
 Maintainers will still apply the same scope, duplication, source-quality, and annotation checks used for pull requests. Corrections to an existing annotation are equally useful; link the current entry and state exactly what should change.
 
+For an inaccurate summary, contribution, novelty, impact, author, date, venue, identifier, or canonical link, use the dedicated [annotation-correction form](https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=annotation-correction.yml). Include primary-source evidence and omit unavailable metadata rather than guessing.
+
 ## Quick PR Flow
 
 1. Search `README.md` for the resource title, author, project, and URL.
@@ -38,6 +40,8 @@ When a source exposes no reliable publication date, omit the year and keep only
    - the evidence quality tier and resource type label;
    - any caveat such as vendor bias, paywall, early-stage status, or weak evidence.
 
+If automated tools assisted discovery, extraction, or drafting, say so in the PR. Check every resulting claim against the canonical source; generated text is not evidence.
+
 ## License For Contributions
 
 By contributing to this repository, you agree that your contribution to this repository's curation text, annotations, templates, patterns, metadata, and documentation is released under [CC0-1.0](LICENSE).

README.de.md

@@ -28,7 +28,7 @@ Ein Loop entdeckt Arbeit, übergibt sie an einen oder mehrere Agenten, prüft da
 
 Dieses Repository behandelt die neue Bedeutung von Loop Engineering im Kontext von KI-Agenten und Coding Agents. Es geht nicht um Software-Event-Loops, Regelungstechnik, Growth Loops, generische Automatisierung oder nicht-KI-bezogene Feedback-Loops.
 
-Neben der Liste mit über 430 kuratierten Ressourcen bietet dieses Repository 15 Loop-Patterns, einen schemavalidierten Loop-Contract pro Pattern, 6 ausführbare Loop-Vorlagen, eine Community-Galerie und 8 Sprachen.
+Neben 540 kuratierten Ressourcen bietet dieses Repository 15 Loop-Patterns, einen schemavalidierten Loop-Contract pro Pattern, 6 ausführbare Loop-Vorlagen, eine Community-Galerie und 8 Sprachen.
 
 ## Mentales Modell
 

README.es.md

@@ -28,7 +28,7 @@ Un loop descubre trabajo, lo delega a uno o más agentes, verifica el resultado,
 
 Este repositorio se centra en el significado nuevo de Loop Engineering para agentes de IA y coding agents. No trata sobre event loops de software, teoría de control, growth loops, automatización genérica o feedback loops no relacionados con IA.
 
-Además de la lista con más de 430 recursos curados, este repositorio incluye 15 patrones de loop, un loop contract validado por esquema para cada patrón, 6 plantillas de loop ejecutables, una galería comunitaria y 8 idiomas.
+Además de 540 recursos curados, este repositorio incluye 15 patrones de loop, un loop contract validado por esquema para cada patrón, 6 plantillas de loop ejecutables, una galería comunitaria y 8 idiomas.
 
 ## Modelo Mental
 

README.fr.md

@@ -28,7 +28,7 @@ Un loop découvre du travail, le délègue à un ou plusieurs agents, vérifie l
 
 Ce dépôt concerne le nouveau sens de Loop Engineering dans le contexte des agents IA et coding agents. Il ne concerne pas les event loops logiciels, la théorie du contrôle, les growth loops, l'automatisation générique ou les feedback loops non liés à l'IA.
 
-Au-delà de la liste de plus de 430 ressources sélectionnées, ce dépôt fournit 15 patterns de loop, un loop contract validé par schéma pour chaque pattern, 6 modèles de loop exécutables, une galerie communautaire et 8 langues.
+Au-delà de 540 ressources sélectionnées, ce dépôt fournit 15 patterns de loop, un loop contract validé par schéma pour chaque pattern, 6 modèles de loop exécutables, une galerie communautaire et 8 langues.
 
 ## Modèle Mental
 

README.ja.md

@@ -28,7 +28,7 @@ Loop は作業を発見し、1 つ以上の agents に委任し、結果を確
 
 このリポジトリは AI agents / coding agents における新しい意味の Loop Engineering に限定しています。software event loop、制御理論、growth loop、一般的な workflow automation、非 AI の feedback loop は対象外です。
 
-430 件超の精選リソースのリストに加えて、本リポジトリは 15 個の loop パターン、各パターンに対応する schema 検証済み loop contract、6 個の実行可能な loop テンプレート、コミュニティ gallery、8 言語を提供します。
+540 件の精選リソースに加えて、本リポジトリは 15 個の loop パターン、各パターンに対応する schema 検証済み loop contract、6 個の実行可能な loop テンプレート、コミュニティ gallery、8 言語を提供します。
 
 ## メンタルモデル
 

README.ko.md

@@ -28,7 +28,7 @@ Loop 는 작업을 발견하고, 하나 이상의 agents 에게 위임하고,
 
 이 저장소는 AI agents / coding agents 맥락의 새로운 Loop Engineering 의미에만 집중합니다. software event loop, control theory, growth loop, 일반적인 workflow automation, 비 AI feedback loop 는 범위에 포함하지 않습니다.
 
-430개 이상의 엄선된 리소스 목록 외에도 이 저장소는 15개의 loop 패턴, 각 패턴에 대한 스키마 검증 loop contract, 6개의 실행 가능한 loop 템플릿, 커뮤니티 gallery, 8개 언어를 제공합니다.
+540개의 엄선된 리소스 외에도 이 저장소는 15개의 loop 패턴, 각 패턴에 대한 스키마 검증 loop contract, 6개의 실행 가능한 loop 템플릿, 커뮤니티 gallery, 8개 언어를 제공합니다.
 
 ## 멘탈 모델
 

README.pt-BR.md

@@ -28,7 +28,7 @@ Um loop descobre trabalho, delega para um ou mais agentes, verifica o resultado,
 
 Este repositório trata do novo significado de Loop Engineering no contexto de AI agents e coding agents. Ele não trata de event loops de software, teoria de controle, growth loops, automação genérica ou feedback loops não relacionados a IA.
 
-Além da lista com mais de 430 recursos curados, este repositório inclui 15 patterns de loop, um loop contract validado por schema para cada pattern, 6 templates de loop executáveis, uma galeria comunitária e 8 idiomas.
+Além de 540 recursos curados, este repositório inclui 15 patterns de loop, um loop contract validado por schema para cada pattern, 6 templates de loop executáveis, uma galeria comunitária e 8 idiomas.
 
 ## Modelo Mental
 

SUPPORT.md

@@ -4,11 +4,11 @@ This repository is maintained as a public field guide and curated resource list
 
 ## Best Channels
 
-- **Resource suggestions**: use the resource suggestion issue template.
-- **Loop patterns**: use the loop pattern suggestion issue template or the pinned community pattern issue.
-- **Corrections**: open a pull request when the fix is clear, or open an issue if it needs discussion.
-- **Translations**: use the translation proposal issue template and follow `TRANSLATIONS.md`.
-- **Security concerns**: follow `SECURITY.md`.
+- **Resource suggestions**: use the [resource suggestion form](https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=resource-suggestion.yml).
+- **Loop patterns**: use the [loop pattern form](https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=pattern-suggestion.yml) or the [community pattern discussion](https://github.com/ChaoYue0307/awesome-loop-engineering/discussions/2).
+- **Corrections**: use the [annotation-correction form](https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=annotation-correction.yml) when a summary or source record is inaccurate, or open a pull request when the fix is clear.
+- **Translations**: use the [translation proposal form](https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=translation.yml) and follow `TRANSLATIONS.md`.
+- **Security concerns**: follow [`SECURITY.md`](SECURITY.md).
 
 ## What Maintainers Can Help With
 

data/README.md

@@ -16,11 +16,43 @@ The main exports preserve the original section and annotation while adding three
 
 `key_contribution`, `novelty`, and `impact` are resource-specific. `signal` states the evidence basis and its limits; GitHub stars and forks are reported as current context, never as proof of reliability. Signal strength is calibrated as `high` for primary official documentation and benchmarks, `medium` for inspectable implementations, papers, patterns, and repository-native artifacts, `contextual` for practitioner analysis and curated lists, and `unverified` only when the latest source audit cannot validate availability.
 
+## Load And Query
+
+```python
+from datasets import load_dataset
+
+resources = load_dataset(
+    "cy0307/awesome-loop-engineering",
+    "resources",
+    split="train",
+)
+
+verification_papers = resources.filter(
+    lambda row: row["resource_type"] == "Paper"
+    and "verification" in row["lifecycle_stages"].split(";")
+)
+```
+
+For pandas:
+
+```python
+import pandas as pd
+
+resources = pd.read_csv("data/resources.csv")
+current_sources = resources[resources["source_status"].isin(["ok", "local_ok"])]
+```
+
+Use `url` as the durable join key. `row_id` and `source_line` are positional and may change when the README is reordered.
+
+## Reproducibility
+
 Render the README rows first, then regenerate all three discovery files after changing resource entries or refreshing the source audit:
 
 ```sh
 python3 scripts/render_readme_tables.py
 python3 scripts/export_resource_dataset.py
+python3 scripts/check_project_consistency.py
+python3 scripts/build_hf_card.py --check
 ```
 
 The export is deterministic and includes one row for every README resource-table row that follows the repository's curated entry format: marker, resource type, title, link, original publishing platform or venue, annotation, section, and source line.
@@ -32,3 +64,11 @@ python3 scripts/audit_resource_sources.py --timeout 20 --workers 16 --attempts 2
 ```
 
 The audit file is a snapshot. HTTP status, redirects, page titles, publication metadata, and GitHub statistics can change over time. arXiv bibliographic fields come from the primary arXiv API; GitHub dates come from the repository API; other web metadata comes from citation or Open Graph tags when available. A blank publication date means the primary source did not expose one. Rows marked `restricted` returned an access-control or rate-limit status during retrieval; they are tracked separately from broken or unreachable links.
+
+Build the focused Hugging Face dataset card for a staging mirror with:
+
+```sh
+python3 scripts/build_hf_card.py --output /tmp/awesome-loop-engineering-hf/README.md
+```
+
+The card is generated from `meta/hf_card_header.yaml`, `meta/hf_card_body.md`, the current dataset, and `CITATION.cff`. The YAML front matter is intentionally Hugging Face-only and must not be added to the GitHub README.

design-qa.md

@@ -61,4 +61,27 @@
 - Three.js pointer-motion frame: `/private/tmp/awesome-loop-hero-three-motion-final.png`
 - Social preview: `/Users/chaoyue/Library/CloudStorage/Dropbox/Loop Engineering/awesome-loop-engineering/assets/social-preview.png`
 
+## 2026-07-17 Repository Audit
+
+- Desktop: 1440 x 1000, no horizontal overflow, no hero text/scene overlap, and all eight section headings render without requiring scroll-triggered opacity changes.
+- 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.
+- 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.
+- Mobile navigation: opens all eight project links, reports `aria-expanded="true"`, closes on Escape, and restores focus to the menu button.
+- Resource Atlas: remains idle above the fold, loads on approach or a direct resource anchor, and reports `540 of 540 resources | showing 8` on mobile.
+- Resource interactions: `SWE-bench` returns 9 matches, the paper filter narrows those to 6, Reset restores all 540, and Show more expands the rendered set from 8 to 16.
+- 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.
+- Scene pixels: 79,858 of 362,880 canvas pixels differ from the paper background (22.01%), confirming a nonblank render with useful contrast.
+- Console: no page-origin errors or warnings. The only warnings came from the browser-control extension and are unrelated to the site.
+- Data and copy: the website, README, translations, social preview source, release copy, and Hugging Face card all report 540 resources, 15 patterns, 15 contracts, and version 0.6.0.
+
+### Current Evidence
+
+- Desktop before/after: `/tmp/loop-desktop-before-after.png`
+- Tablet framing before/after: `/tmp/loop-tablet-before-after.png`
+- Phone hero: `/tmp/loop-qa-mobile-after-fit.png`
+- Phone Resource Atlas: `/tmp/loop-qa-mobile-resource-cards.png`
+- Canvas frame 1: `/tmp/loop-motion-canvas-1.png`
+- Canvas frame 2: `/tmp/loop-motion-canvas-2.png`
+- Canvas pixel difference: `/tmp/loop-motion-diff.png`
+
 final result: passed

docs/assets/loop-hero-scene.js

@@ -877,14 +877,19 @@ if (container && hero) {
     function resize() {
       const width = Math.max(container.clientWidth, 1);
       const height = Math.max(container.clientHeight, 1);
-      const compact = width < 620;
+      const compact = width < 720;
       const tablet = !compact && width < 900;
       applyLayout(compact);
       renderer.setPixelRatio(Math.min(window.devicePixelRatio || 1, compact || lowPower ? 1.3 : 1.65));
       renderer.setSize(width, height, false);
 
-      const viewHeight = compact ? 3.9 : tablet ? 3.45 : 3.15;
-      const viewWidth = viewHeight * (width / height);
+      const aspect = width / height;
+      const viewHeight = compact
+        ? Math.max(3.45, 5.8 / aspect)
+        : tablet
+          ? 11.2 / aspect
+          : 3.15;
+      const viewWidth = viewHeight * aspect;
       camera.left = -viewWidth / 2;
       camera.right = viewWidth / 2;
       camera.top = viewHeight / 2;

docs/index.html

@@ -336,6 +336,8 @@
 
       .section-head { display: grid; grid-template-columns: minmax(250px, 0.78fr) minmax(360px, 1.22fr); gap: 64px; align-items: end; margin-bottom: 36px; }
       .section-intro { max-width: 720px; margin: 0; color: var(--muted); }
+      .audit-note { margin: -17px 0 28px; border-top: 1px solid var(--line); padding-top: 13px; color: var(--muted); font-size: 0.8rem; }
+      .audit-note strong { color: var(--ink); }
       .diagram { width: 100%; }
       .caption { margin: 13px 0 0; color: var(--quiet); font-size: 0.78rem; text-align: right; }
       .supporting-visual { margin: 0 0 34px; }
@@ -417,6 +419,7 @@
       .mobile-lifecycle-outcomes span { display: block; margin-top: 2px; color: var(--muted); font-size: 0.66rem; line-height: 1.35; }
 
       .principles, .link-grid, .pattern-grid { display: grid; grid-template-columns: repeat(3, minmax(0, 1fr)); }
+      .contribute-grid { grid-template-columns: repeat(4, minmax(0, 1fr)); }
       .principle, .card, .pattern {
         min-width: 0;
         border-top: 1px solid var(--line-strong);
@@ -580,13 +583,6 @@
       .copy { position: absolute; top: 8px; right: 8px; border: 1px solid var(--line-strong); border-radius: 4px; padding: 4px 9px; background: var(--surface); color: var(--ink); font-size: 0.72rem; font-weight: 700; cursor: pointer; }
       .legal { margin: 30px 0 0; color: var(--quiet); font-size: 0.8rem; }
 
-      .motion-ready .motion-item {
-        opacity: 0;
-        transform: translateY(14px);
-        transition: opacity 420ms ease, transform 420ms ease;
-      }
-      .motion-ready .motion-item.is-visible { opacity: 1; transform: translateY(0); }
-
       @media (max-width: 1040px) {
         .links { display: none; }
         .menu-btn { display: inline-flex; }
@@ -763,7 +759,7 @@
       }
       @media (prefers-reduced-motion: reduce) {
         html { scroll-behavior: auto; }
-        .pattern, .motion-ready .motion-item { opacity: 1; transform: none; transition: none; }
+        .pattern { transition: none; }
       }
       @media (forced-colors: active) {
         .hero-scene { display: none; }
@@ -839,11 +835,18 @@
           "https://github.com/ChaoYue0307/awesome-loop-engineering"
         ],
         "identifier": "https://huggingface.co/datasets/cy0307/awesome-loop-engineering",
+        "version": "0.6.0",
         "license": "https://creativecommons.org/publicdomain/zero/1.0/",
         "isAccessibleForFree": true,
         "creator": { "@type": "Person", "name": "Chaoyue He" },
         "datePublished": "2026-06-10",
-        "dateModified": "2026-07-16",
+        "dateModified": "2026-07-17",
+        "keywords": ["Loop Engineering", "AI agents", "Coding agents", "Agent reliability", "Agent evaluation"],
+        "includedInDataCatalog": {
+          "@type": "DataCatalog",
+          "name": "Hugging Face Hub",
+          "url": "https://huggingface.co/datasets"
+        },
         "distribution": [
           {
             "@type": "DataDownload",
@@ -1130,6 +1133,7 @@
             </div>
             <p class="section-intro">Search 540 audited works by goal, lifecycle stage, artifact type, and evidence class. Each row combines the curated assessment with verified authorship, year, venue or source platform, and identifiers when the primary source exposes them.</p>
           </div>
+          <p class="audit-note"><strong>Audit snapshot, 2026-07-17:</strong> all 540 rows checked; 493 public sources reachable, 4 access-restricted, 43 repository-native, and 0 broken or unreachable. <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/data/resource_source_audit.csv">Inspect the audit</a> or <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=annotation-correction.yml">report a correction</a>.</p>
           <div class="resource-explorer" id="resource-explorer">
             <div class="resource-toolbar" role="search" aria-label="Search curated resources">
               <label>
@@ -1194,7 +1198,7 @@
               <button class="resource-collection" type="button" data-collection="Apply" aria-pressed="false"><span class="emoji" aria-hidden="true">📦</span>Apply</button>
             </div>
             <div class="resource-summary">
-              <p class="resource-count" id="resource-count" aria-live="polite">Loading resource index...</p>
+              <p class="resource-count" id="resource-count" aria-live="polite">Resource index loads as you approach this section.</p>
               <label>
                 <span class="sr-only">Sort resources</span>
                 <select class="resource-select resource-sort" id="resource-sort">
@@ -1211,8 +1215,8 @@
               <span>Published at</span>
               <span>Evidence</span>
             </div>
-            <div class="resource-list" id="resource-list" aria-busy="true">
-              <p class="resource-loading">Loading audited resources...</p>
+            <div class="resource-list" id="resource-list" aria-busy="false">
+              <p class="resource-loading">Preparing the audited resource index...</p>
             </div>
             <p class="resource-empty" id="resource-empty" hidden>No resources match the current filters.</p>
             <div class="resource-actions">
@@ -1234,8 +1238,9 @@
             </div>
             <p class="section-intro">Add a vetted source with a specific annotation, or document a loop you actually run. Both paths have a checklist.</p>
           </div>
-          <div class="link-grid">
+          <div class="link-grid contribute-grid">
             <a class="card" href="https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=resource-suggestion.yml"><h3><span class="emoji" aria-hidden="true">➕</span>Suggest a resource</h3><p>Submit one canonical source and a precise annotation in under five minutes.</p></a>
+            <a class="card" href="https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=annotation-correction.yml"><h3><span class="emoji" aria-hidden="true">✅</span>Correct the map</h3><p>Fix a summary, contribution, date, venue, identifier, or canonical link with primary evidence.</p></a>
             <a class="card" href="https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/gallery/README.md"><h3><span class="emoji" aria-hidden="true">🔁</span>Share a loop</h3><p>Publish a real or anonymized case study using the gallery checklist.</p></a>
             <a class="card" href="https://github.com/ChaoYue0307/awesome-loop-engineering/discussions/2"><h3><span class="emoji" aria-hidden="true">💬</span>Join the discussion</h3><p>Compare operating patterns with other loop builders.</p></a>
           </div>
@@ -1286,7 +1291,8 @@
   author       = {He, Chaoyue},
   title        = {Awesome Loop Engineering},
   year         = {2026},
-  howpublished = {\url{https://github.com/ChaoYue0307/awesome-loop-engineering}}
+  howpublished = {\url{https://github.com/ChaoYue0307/awesome-loop-engineering}},
+  note         = {Version 0.6.0}
 }</pre>
             </div>
           </div>
@@ -1296,6 +1302,8 @@
             <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/MANIFESTO.md">Manifesto</a>
             <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/TAXONOMY.md">Taxonomy</a>
             <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/ANTI-PATTERNS.md">Anti-patterns</a>
+            <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/meta/CURATION.md">Curation + provenance</a>
+            <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/data/resource_source_audit.csv">Source audit</a>
           </div>
           <div>
             <h4><span class="emoji" aria-hidden="true">🛠️</span>Project</h4>
@@ -1372,20 +1380,6 @@
         }, { rootMargin: '-24% 0px -66% 0px', threshold: 0 });
         sections.forEach(function (section) { observer.observe(section); });
       })();
-      (function () {
-        if (!('IntersectionObserver' in window) || window.matchMedia('(prefers-reduced-motion: reduce)').matches) return;
-        var items = Array.prototype.slice.call(document.querySelectorAll('.section-head, .diagram, .principles, .link-grid, .levels'));
-        document.documentElement.classList.add('motion-ready');
-        items.forEach(function (item) { item.classList.add('motion-item'); });
-        var observer = new IntersectionObserver(function (entries) {
-          entries.forEach(function (entry) {
-            if (!entry.isIntersecting) return;
-            entry.target.classList.add('is-visible');
-            observer.unobserve(entry.target);
-          });
-        }, { rootMargin: '0px 0px -8% 0px', threshold: 0.08 });
-        items.forEach(function (item) { observer.observe(item); });
-      })();
       (function () {
         var input = document.getElementById('pattern-filter');
         var grid = document.getElementById('pattern-grid');
@@ -1432,6 +1426,7 @@
         var pageSize = compactResources.matches ? 8 : 24;
         var state = { collection: '', limit: pageSize };
         var resources = [];
+        var loading = false;
 
         function words(value) {
           return String(value || '').replace(/-/g, ' ');
@@ -1639,6 +1634,10 @@
 
         function resetLimitAndRender() {
           state.limit = pageSize;
+          if (!resources.length) {
+            loadResources();
+            return;
+          }
           render();
         }
 
@@ -1681,23 +1680,54 @@
           search.focus();
         });
 
-        fetch('assets/resources.json')
-          .then(function (response) {
-            if (!response.ok) throw new Error('Resource index request failed');
-            return response.json();
-          })
-          .then(function (payload) {
-            resources = (payload.resources || []).map(function (resource, index) {
-              resource._index = index;
-              return resource;
+        function loadResources() {
+          if (loading || resources.length) return;
+          loading = true;
+          explorer.dataset.indexState = 'loading';
+          list.setAttribute('aria-busy', 'true');
+          count.textContent = 'Loading 540 audited resources...';
+          list.replaceChildren(createText('p', 'resource-loading', 'Loading audited resources...'));
+
+          fetch('assets/resources.json')
+            .then(function (response) {
+              if (!response.ok) throw new Error('Resource index request failed');
+              return response.json();
+            })
+            .then(function (payload) {
+              resources = (payload.resources || []).map(function (resource, index) {
+                resource._index = index;
+                return resource;
+              });
+              explorer.dataset.indexState = 'ready';
+              render();
+            })
+            .catch(function () {
+              loading = false;
+              explorer.dataset.indexState = 'error';
+              list.replaceChildren(createText('p', 'resource-loading', 'The resource index could not be loaded. Browse the complete library on GitHub or Hugging Face.'));
+              list.setAttribute('aria-busy', 'false');
+              count.textContent = 'Resource index unavailable';
             });
-            render();
-          })
-          .catch(function () {
-            list.replaceChildren(createText('p', 'resource-loading', 'The resource index could not be loaded. Browse the complete library on GitHub or Hugging Face.'));
-            list.setAttribute('aria-busy', 'false');
-            count.textContent = 'Resource index unavailable';
-          });
+        }
+
+        var resourceSection = document.getElementById('resources');
+        if (window.location.hash === '#resources') {
+          loadResources();
+        } else if ('IntersectionObserver' in window && resourceSection) {
+          var resourceObserver = new IntersectionObserver(function (entries) {
+            if (!entries.some(function (entry) { return entry.isIntersecting; })) return;
+            resourceObserver.disconnect();
+            loadResources();
+          }, { rootMargin: '700px 0px', threshold: 0 });
+          resourceObserver.observe(resourceSection);
+        } else {
+          loadResources();
+        }
+
+        explorer.addEventListener('focusin', loadResources, { once: true });
+        window.addEventListener('hashchange', function () {
+          if (window.location.hash === '#resources') loadResources();
+        });
       })();
       Array.prototype.forEach.call(document.querySelectorAll('.copy'), function (button) {
         var label = button.querySelector('span') || button;
@@ -1723,6 +1753,6 @@
         });
       });
     </script>
-    <script type="module" src="assets/loop-hero-scene.js?v=19"></script>
+    <script type="module" src="assets/loop-hero-scene.js?v=20"></script>
   </body>
 </html>

meta/AWESOME_SUBMISSION.md

@@ -11,7 +11,9 @@ Use this before submitting `awesome-loop-engineering` to [`sindresorhus/awesome`
 - Cover image: present in `assets/awesome-loop-engineering-cover.png`.
 - Contribution guidelines: `CONTRIBUTING.md`.
 - Code of conduct: `CODE_OF_CONDUCT.md`.
-- Quality workflow: enabled, but the README does not show a CI badge.
+- Quality workflow: enabled and visible from the README.
+
+The upstream PR is open at [`sindresorhus/awesome#4339`](https://github.com/sindresorhus/awesome/pull/4339). Its lint check passes, but the repository owner has stated that AI-generated lists are not accepted. Treat that as a policy objection, not a formatting issue. Do not imply acceptance is pending or obscure how automation assisted the curation workflow.
 
 ## Submission Timing
 
@@ -33,6 +35,8 @@ python3 scripts/check_license.py
 python3 scripts/check_resource_labels.py README.md
 python3 scripts/render_readme_tables.py --check
 python3 scripts/export_resource_dataset.py --check
+python3 scripts/check_project_consistency.py
+python3 scripts/build_hf_card.py --check
 python3 scripts/check_publication_metadata.py
 python3 scripts/check_loop_contract_examples.py
 python3 scripts/check_pages_metadata.py

meta/CURATION.md

@@ -43,6 +43,35 @@ Usually reject resources that are mostly:
 
 Prefer the highest-tier source that explains the same idea clearly.
 
+## Editorial Responsibility And Assistance
+
+The maintainer is accountable for every released inclusion decision, category, annotation, and project-level claim. Repository automation may assist with discovery, URL resolution, duplicate detection, bibliographic extraction, repository statistics, and draft normalization. Automated output is never treated as evidence on its own: the canonical source record, primary metadata, and stated limitations control the final entry.
+
+The public dataset keeps those layers separate:
+
+- `annotation`, `key_contribution`, `novelty`, and `impact` are original repository syntheses;
+- `source_title`, `source_description`, authorship, date, venue, DOI, and repository statistics come from the source audit and record their metadata provenance;
+- `signal_strength` describes the kind of evidence available, not whether the maintainer agrees with the work;
+- `source_status` records reachability at one point in time and is not a guarantee of future availability.
+
+No author, company, venue, star count, or citation count can buy or guarantee placement. Vendor inclusion does not imply endorsement, and inclusion of a critique does not imply that every claim in it is accepted.
+
+## Corrections And Disputes
+
+Accuracy corrections take priority over expansion. Authors and readers can submit the [annotation-correction form](https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=annotation-correction.yml) or a pull request with the current entry, the disputed text, the proposed correction, and primary-source evidence.
+
+When evidence conflicts:
+
+1. prefer the original publishing venue, official documentation, paper record, or repository over secondary coverage;
+1. distinguish a verified fact from the repository's interpretation;
+1. preserve material caveats, negative results, and stated evaluation limits;
+1. omit a date, venue, author, or metric rather than infer it from an unreliable source;
+1. record the correction in the next release notes when it changes the meaning of an entry.
+
+## Audit And Versioning
+
+`data/resource_source_audit.csv` is the inspectable point-in-time audit log. `data/resources.csv` and `data/resources.jsonl` are deterministic exports of the canonical English README enriched with that audit. GitHub Releases identify versioned snapshots; downstream users should cite a release or commit when reproducibility matters.
+
 ## Annotation Rules
 
 Each annotation should answer: **why does this matter for Loop Engineering?**

meta/DISTRIBUTION.md

@@ -8,10 +8,10 @@ Status as of 2026-07-17:
 
 | Surface | Status | Evidence / next action |
 | --- | --- | --- |
-| GitHub release | Complete | [`v0.5.0`](https://github.com/ChaoYue0307/awesome-loop-engineering/releases/tag/v0.5.0) describes 509 resources and links the atlas, dataset, templates, and contribution guide. |
-| Release announcement | Complete | [Discussion #9](https://github.com/ChaoYue0307/awesome-loop-engineering/discussions/9) gives readers a low-noise way to follow releases, monthly digests, and contributor tasks. |
+| GitHub release | Complete | [`v0.6.0`](https://github.com/ChaoYue0307/awesome-loop-engineering/releases/tag/v0.6.0) describes 540 resources, the public provenance standard, the focused dataset card, and the cross-surface consistency gates. |
+| Release announcement | Ready | Publish the v0.6.0 summary from [`posts/launch.md`](../posts/launch.md); [Discussion #9](https://github.com/ChaoYue0307/awesome-loop-engineering/discussions/9) remains the low-noise release and contributor feed. |
 | GitHub Explore topic | Complete | [`github/explore#5209`](https://github.com/github/explore/pull/5209) merged the `loop-engineering` topic page. |
-| Canonical Awesome directory | In review | [`sindresorhus/awesome#4339`](https://github.com/sindresorhus/awesome/pull/4339) is open with a passing lint check. Respond to maintainer feedback; do not open a duplicate. |
+| 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. |
 | Adjacent harness directory | In review | [`ai-boost/awesome-harness-engineering#131`](https://github.com/ai-boost/awesome-harness-engineering/pull/131) transparently proposes the project for the list's Related Awesome Lists section. |
 | Hugging Face dataset | Complete | [`datasets/cy0307/awesome-loop-engineering`](https://huggingface.co/datasets/cy0307/awesome-loop-engineering) carries the structured resource sheet and full project mirror. |
 | English and Chinese launch articles | Ready | Publish [`posts/launch.md`](../posts/launch.md) and [`posts/launch.zh-CN.md`](../posts/launch.zh-CN.md) natively on suitable channels. |
@@ -33,15 +33,16 @@ The repository is mirrored to the Hugging Face Hub dataset repo [`datasets/cy030
 
 - The mirror tracks the full GitHub tree (docs, patterns, examples, schema, scripts).
 - The dataset mirror includes generated resource sheets at `data/resources.csv` and `data/resources.jsonl`, refreshed from the canonical English `README.md` by `scripts/export_resource_dataset.py`.
-- The HF copy of `README.md` carries a dataset-card YAML header (`license`, `language`, `size_categories`, `task_categories`, `tags`, `pretty_name`, and `configs`); the canonical header lives in meta/hf_card_header.yaml. This header is **HF-only**: it must never be added to the GitHub `README.md`, because the YAML list items break `awesome-lint`.
-- Sync uses the `hf upload --type dataset` CLI against a staging copy with the header prepended, so the GitHub working tree stays header-free. The token lives in the local Hugging Face cache; no token is committed.
+- The HF copy of `README.md` is a focused dataset card generated from `meta/hf_card_header.yaml` and `meta/hf_card_body.md` by `scripts/build_hf_card.py`. It documents intended uses, provenance, limitations, loading examples, and the current audit snapshot without duplicating the 540-row GitHub README.
+- The YAML header is **HF-only**: it must never be added to the GitHub `README.md`, because the metadata list items break `awesome-lint`.
+- Sync uses `python3 scripts/build_hf_card.py --output <staging>/README.md` followed by `hf upload --type dataset` against a staging copy. The token lives in the local Hugging Face cache; no token is committed.
 
 ## GitHub-Native Promotion
 
 Discoverability levers that live on GitHub itself, in priority order.
 
 - **Topic page (`github/explore`).** The [`loop-engineering` topic](https://github.com/topics/loop-engineering) now has a curated page through merged PR [`github/explore#5209`](https://github.com/github/explore/pull/5209). Keep the topic description ecosystem-wide rather than repository-specific.
-- **sindresorhus/awesome submission.** Track the open canonical directory PR at [`sindresorhus/awesome#4339`](https://github.com/sindresorhus/awesome/pull/4339) and respond to maintainer feedback quickly. Use [`AWESOME_SUBMISSION.md`](AWESOME_SUBMISSION.md) for the acceptance criteria.
+- **sindresorhus/awesome submission.** The open PR at [`sindresorhus/awesome#4339`](https://github.com/sindresorhus/awesome/pull/4339) has a passing lint check and an explicit owner policy objection to AI-generated lists. Keep the curation process transparent and wait for maintainer clarification; do not present the PR as ordinary pending review. See [`AWESOME_SUBMISSION.md`](AWESOME_SUBMISSION.md).
 - **Editorial submissions to adjacent lists** this repo already cites (harness, context, and agent-paper lists). Submit only where the maintainers explicitly accept related resources. Ready-to-paste entry:
 
   ```md
@@ -66,8 +67,8 @@ Baseline captured on 2026-07-17 for the API window ending 2026-07-15:
 | Unique visitors | 142 |
 | Clones | 204 |
 | Unique cloners | 81 |
-| Stars | 24 |
-| Forks | 3 |
+| Stars | 26 |
+| Forks | 4 |
 | Watchers | 1 |
 
 The repository overview reached 119 unique visitors. The Chinese README was the second-most visited content path with 19 unique visitors. The largest identifiable referrers were Google (17 unique visitors), GitHub (14), Bing (14), and the project site (6); launch and community channels had not yet become material sources.
@@ -89,28 +90,29 @@ Use the canonical [English launch article](../posts/launch.md) or [Chinese launc
 ### Short Post
 
 ```text
-Awesome Loop Engineering v0.5.0 is live.
+🔁 Awesome Loop Engineering v0.6.0 is live: 540 source-audited resources, 15 operational patterns, validated loop contracts, runnable templates, an interactive Resource Atlas, and a structured Hugging Face dataset.
 
-509 audited resources for designing recurring AI-agent systems above prompt, context, and harness engineering, plus an interactive Resource Atlas, 15 patterns, 15 validated loop contracts, runnable templates, and a structured Hugging Face dataset.
-
-Explore the atlas:
+🧭 Explore:
 https://chaoyue0307.github.io/awesome-loop-engineering/
+
+#AIAgents #AgentEngineering #LoopEngineering
 ```
 
 ### Longer Post
 
 ```text
-Awesome Loop Engineering v0.5.0 is live.
+Awesome Loop Engineering v0.6.0 is live.
 
 Loop Engineering is the operating layer above prompt, context, and harness engineering: the recurring system that discovers work, delegates it, verifies results, persists state, and decides what happens next.
 
 The release includes:
 
-- 509 audited resources
+- 540 audited resources
 - an interactive Resource Atlas
 - 15 operational patterns and 15 validated loop contracts
 - 6 runnable templates
 - CSV and JSONL exports mirrored to Hugging Face
+- a public provenance standard and point-in-time source audit
 
 Explore, reuse, or correct the map:
 https://github.com/ChaoYue0307/awesome-loop-engineering
@@ -121,11 +123,11 @@ https://github.com/ChaoYue0307/awesome-loop-engineering
 Use a regular submission, not Show HN.
 
 ```text
-Title: Awesome Loop Engineering: 509 resources for recurring AI-agent systems
+Title: Awesome Loop Engineering: 540 resources for recurring AI-agent systems
 
 I have been mapping the layer above prompt, context, and harness engineering: recurring systems that discover work, delegate it, verify results, persist state, and decide whether to retry, escalate, or exit.
 
-The repository now includes 509 audited sources, 15 operational patterns, validated loop contracts, runnable templates, an interactive Resource Atlas, and a structured Hugging Face dataset. Corrections to the taxonomy and source annotations are especially welcome.
+The repository now includes 540 audited sources, 15 operational patterns, validated loop contracts, runnable templates, an interactive Resource Atlas, and a structured Hugging Face dataset. The curation and source-audit method is public, and corrections to the taxonomy and source annotations are especially welcome.
 
 https://github.com/ChaoYue0307/awesome-loop-engineering
 ```

meta/MAINTENANCE.md

@@ -71,6 +71,8 @@ python3 scripts/check_license.py
 python3 scripts/check_resource_labels.py README.md
 python3 scripts/render_readme_tables.py --check
 python3 scripts/export_resource_dataset.py --check
+python3 scripts/check_project_consistency.py
+python3 scripts/build_hf_card.py --check
 python3 scripts/check_publication_metadata.py
 python3 scripts/check_loop_contract_examples.py
 python3 scripts/check_pages_metadata.py

meta/MAINTENANCE_CALENDAR.md

@@ -34,10 +34,11 @@ Run the local checks in [MAINTENANCE.md](MAINTENANCE.md#local-verification) befo
 
 ## Canonical Awesome Submission Status
 
-The 30-day age requirement has passed. [`sindresorhus/awesome#4339`](https://github.com/sindresorhus/awesome/pull/4339) is open and its lint check is passing as of 2026-07-17.
+The 30-day age requirement has passed. [`sindresorhus/awesome#4339`](https://github.com/sindresorhus/awesome/pull/4339) is open and its lint check is passing as of 2026-07-17, but the repository owner has stated that AI-generated lists are not accepted.
 
 - Do not open a duplicate submission.
-- Respond to maintainer feedback quickly and keep changes scoped and owner-authored.
+- Treat the owner's statement as a policy objection, not a design or lint problem. Respond only with an accurate account of the editorial process if clarification is requested.
+- Keep changes scoped and owner-authored; do not misrepresent automated assistance.
 - Re-run the full preflight in [AWESOME_SUBMISSION.md](AWESOME_SUBMISSION.md#required-preflight) after any structural README change.
 - If accepted, submit to adjacent directories only where the normal editorial policy permits related lists.
 - Keep public claims conservative: this is an early curated field guide, not a finished standard.

meta/OUTREACH.md

@@ -32,7 +32,7 @@ The repo is looking for examples with a clear trigger, work intake, agent roles,
 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 best canonical link, a correction is very welcome:
-https://github.com/ChaoYue0307/awesome-loop-engineering
+https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=annotation-correction.yml
 ```
 
 ## Maintainer Request

meta/hf_card_body.md

@@ -1,69 +1,112 @@
+<p align="center">
+  <a href="https://chaoyue0307.github.io/awesome-loop-engineering/"><img src="assets/awesome-loop-engineering-logo.svg" alt="Visit the Awesome Loop Engineering website" width="128"></a>
+</p>
+
+<h1 align="center">Awesome Loop Engineering Dataset</h1>
+
+<p align="center">
+  A source-audited sheet of {{RESOURCE_COUNT}} papers, official docs, tools, benchmarks, patterns, critiques, and implementation guides for recurring AI-agent systems.
+</p>
+
+<p align="center">
+  <a href="https://chaoyue0307.github.io/awesome-loop-engineering/">Resource Atlas</a> ·
+  <a href="https://github.com/ChaoYue0307/awesome-loop-engineering">GitHub field guide</a> ·
+  <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/meta/CURATION.md">Curation standard</a> ·
+  <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=annotation-correction.yml">Report a correction</a>
+</p>
+
+## Dataset Summary
+
+Each row represents one resource from the canonical English field guide. The export combines the maintainer's short assessment with source-level bibliographic metadata, lifecycle and audience facets, evidence classification, audit status, and current repository statistics when applicable.
+
+Current release: **v{{VERSION}}**
+
+| Surface | Count |
+| --- | ---: |
+| Curated resources | {{RESOURCE_COUNT}} |
+| Operational patterns | {{PATTERN_COUNT}} |
+| Validated loop contracts | {{CONTRACT_COUNT}} |
+| Runnable templates | {{RUNNABLE_COUNT}} |
+
+The source audit dated **{{AUDIT_DATE}}** found {{REACHABLE_COUNT}} reachable public sources, {{RESTRICTED_COUNT}} access-restricted sources, {{LOCAL_COUNT}} repository-native artifacts, and {{BROKEN_COUNT}} broken or unreachable sources.
+
+## Load The Data
+
+```python
+from datasets import load_dataset
+
+resources = load_dataset(
+    "cy0307/awesome-loop-engineering",
+    "resources",
+    split="train",
+)
+
+papers = resources.filter(lambda row: row["resource_type"] == "Paper")
+verification = resources.filter(
+    lambda row: "verification" in row["lifecycle_stages"].split(";")
+)
+```
+
+For pandas:
+
+```python
+import pandas as pd
+
+resources = pd.read_csv(
+    "https://huggingface.co/datasets/cy0307/awesome-loop-engineering/resolve/main/data/resources.csv"
+)
+```
+
+Use `url` as the durable join key. `row_id` and `source_line` are positional and can change when the README is reordered.
+
+## Intended Uses
+
+- discover primary sources and implementation references for recurring agent systems;
+- compare resources by lifecycle stage, audience, evidence class, source type, and publication metadata;
+- build literature maps, reading lists, dashboards, or retrieval indexes;
+- audit how a public field guide characterizes contribution, novelty, impact, and evidence;
+- find reusable patterns, contracts, schemas, and runnable examples.
+
+Do not use `signal_strength`, GitHub stars, forks, or inclusion in this collection as a quality label, endorsement, or automated ranking of scientific validity.
 
 ## Dataset Structure
 
-Each row in `data/resources.jsonl` (and the equivalent `data/resources.csv`) is one curated resource, exported from the English `README.md`.
-
-| Field | Description |
-| --- | --- |
-| `row_id` | Positional identifier (`ale-NNNN`); not stable across README reorders. |
-| `section` | The `##` section the entry lives under. |
-| `section_slug` | Anchor-style slug of the section. |
-| `resource_type` | Paper, Blog, Docs, Tool, Benchmark, Pattern, Template, List, or Critique. |
-| `marker` | Emoji shown before the entry in the README. |
-| `title` | Linked entry title. |
-| `url` | Resource URL. |
-| `url_kind` | `external` or `local_path` (a file inside the repository). |
-| `domain` | Host of an external URL (empty for local paths). |
-| `annotation` | The one-line description as written in the README. |
-| `description` | Copy of the annotation for tooling that expects a `description` field. |
-| `key_contribution` | Short statement of what the resource adds. |
-| `novelty` | Why the entry is distinct within its section. |
-| `impact` | Who benefits and how. |
-| `signal` | Why the entry is trustworthy (adoption, venue, authorship). |
-| `signal_strength` | Calibrated confidence label (`high`, `medium`, `contextual`, or `unverified`). |
-| `source_readme` | README file the row came from. |
-| `source_line` | 1-based line number in that README. |
-| `source_url` | Permalink to the source line on GitHub. |
-| `date_added` | First-seen date when tracked; blank for resources added before tracking began. |
-| `collection` | Task-oriented atlas group: Learn, Design, Build, Persist, Verify, Govern, or Apply. |
-| `collection_slug` | Stable lowercase slug for the task-oriented collection. |
-| `user_goal` | Reader outcome served by the collection. |
-| `lifecycle_stages` | Semicolon-delimited Loop Contract stages addressed by the resource. |
-| `audience` | Semicolon-delimited intended audiences, such as newcomer, builder, operator, evaluator, or security. |
-| `evidence_class` | Source-provenance category, independent of popularity or editorial judgment. |
-| `source_status` | Latest audit result: `ok`, `restricted`, `local_ok`, or an explicit failure state. |
-| `canonical_url` | Redirect-resolved or repository-canonical URL used for source verification. |
-| `source_title` | Title metadata retrieved during the latest source audit. |
-| `source_description` | Description or abstract metadata retrieved from the primary source. |
-| `authors` | Semicolon-delimited authors from primary bibliographic metadata when available. |
-| `publication_date` | Primary-source publication or repository creation date in ISO format when available. |
-| `publication_year` | Four-digit year derived from the verified publication date or identifier. |
-| `publication_venue` | Journal, conference, repository, or named venue reported by the source. |
-| `publisher` | Publishing organization or source platform; falls back to the canonical domain. |
-| `doi` | Normalized DOI without a URL prefix when available. |
-| `publication_note` | Primary-source journal reference, acceptance note, or publication comment when available. |
-| `primary_category` | Primary arXiv category when applicable. |
-| `metadata_source` | Provenance for bibliographic fields, such as `arxiv-api`, `github-api`, `html-meta`, or `domain-fallback`. |
-| `github_repo` | Normalized GitHub `owner/repository` identifier where applicable. |
-| `github_stars` | GitHub star count captured at audit time; context, not a reliability score. |
-| `github_forks` | GitHub fork count captured at audit time. |
-| `github_license` | Repository license identifier reported by GitHub where available. |
-| `github_created_at` | Repository creation timestamp reported by GitHub. |
-| `github_updated_at` | Latest repository update timestamp reported by GitHub. |
-| `arxiv_id` | arXiv identifier extracted from a primary paper URL where applicable. |
-| `audited_at` | UTC timestamp for the source metadata and availability snapshot. |
-
-## Considerations and Limitations
-
-- Annotations are written and curated by a single maintainer; they summarize each resource and are not the authors' own abstracts.
-- URLs are third-party and can rot; `data/resource_source_audit.csv` carries a retrieval-time reachability snapshot, but it is a point-in-time check, not a live guarantee.
-- `row_id` and `source_line` are positional and change when the README is reordered; join on `url` for anything durable.
-- `signal_strength` is calibrated as `high`, `medium`, `contextual`, or `unverified`; GitHub stars and forks are reported only as adoption context.
-- Coverage skews toward English-language, publicly available resources.
-
-## Changelog
-
-Versioned changes are published as [GitHub Releases](https://github.com/ChaoYue0307/awesome-loop-engineering/releases).
+The primary configuration is `resources`, with one `train` split backed by `data/resources.jsonl`. `data/resources.csv` contains the same rows for spreadsheet and dataframe workflows.
+
+| Field group | Fields | What it describes |
+| --- | --- | --- |
+| Identity | `row_id`, `title`, `url`, `canonical_url`, `resource_type`, `domain` | What the resource is and where it lives. |
+| Editorial assessment | `annotation`, `key_contribution`, `novelty`, `impact` | Why the resource matters in this collection. |
+| Navigation | `section`, `collection`, `user_goal`, `lifecycle_stages`, `audience` | Where the resource fits and who it serves. |
+| Evidence | `evidence_class`, `signal`, `signal_strength`, `source_status`, `audited_at` | What kind of evidence or provenance is available. |
+| Publication | `authors`, `publication_date`, `publication_year`, `publication_venue`, `publisher`, `doi`, `arxiv_id`, `primary_category` | Bibliographic data exposed by the canonical source. |
+| Source provenance | `source_title`, `source_description`, `metadata_source`, `publication_note` | Where metadata came from and what caveats accompany it. |
+| Repository context | `github_repo`, `github_stars`, `github_forks`, `github_license`, `github_created_at`, `github_updated_at` | Point-in-time adoption and maintenance context for GitHub projects. |
+| Export trace | `source_readme`, `source_line`, `source_url`, `date_added` | How the row maps back to the canonical field guide. |
+
+The complete field-by-field schema is documented in [`data/README.md`](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/data/README.md).
+
+## Curation And Provenance
+
+The collection prioritizes primary papers, official documentation, project repositories, and implementation-heavy practitioner sources. Every released row must pass the public [curation standard](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/meta/CURATION.md).
+
+Annotations are original repository syntheses, not copied abstracts and not claims of author endorsement. Automation may assist discovery, URL resolution, duplicate detection, bibliographic extraction, repository statistics, and draft normalization. The canonical source remains the evidence, and the maintainer is accountable for the released inclusion decision and text.
+
+The full point-in-time audit is available as [`data/resource_source_audit.csv`](https://huggingface.co/datasets/cy0307/awesome-loop-engineering/blob/main/data/resource_source_audit.csv).
+
+## Limitations
+
+- The collection is maintained by one person and reflects editorial judgment despite a public acceptance standard.
+- Coverage is skewed toward English-language, publicly available material.
+- A successful URL check proves reachability at audit time, not correctness, permanence, or independent validation.
+- Access-restricted rows could not be fully retrieved during the latest audit and should be checked manually.
+- Publication dates and authors remain blank when the primary source does not expose reliable metadata.
+- Resource statistics are snapshots and will drift after the recorded `audited_at` timestamp.
+- Linked third-party works retain their own licenses and terms; CC0-1.0 covers only original repository curation, metadata, templates, and documentation.
+
+## Versioning And Corrections
+
+GitHub Releases define versioned snapshots. Cite a release or commit when reproducibility matters. Accuracy corrections to summaries, contribution, novelty, impact, author, date, venue, identifier, or canonical URL are accepted through the [correction form](https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=annotation-correction.yml).
 
 ## Citation
 
@@ -72,6 +115,7 @@ Versioned changes are published as [GitHub Releases](https://github.com/ChaoYue0
   author       = {He, Chaoyue},
   title        = {Awesome Loop Engineering},
   year         = {2026},
-  howpublished = {\url{https://github.com/ChaoYue0307/awesome-loop-engineering}}
+  howpublished = {\url{https://github.com/ChaoYue0307/awesome-loop-engineering}},
+  note         = {Version {{VERSION}}}
 }
 ```

meta/hf_card_header.yaml

@@ -2,6 +2,14 @@
 license: cc0-1.0
 language:
   - en
+language_creators:
+  - found
+annotations_creators:
+  - other
+multilinguality:
+  - monolingual
+source_datasets:
+  - original
 pretty_name: Awesome Loop Engineering
 size_categories:
   - n<1K
@@ -9,6 +17,8 @@ task_categories:
   - text-classification
   - text-retrieval
 tags:
+  - tabular
+  - datasets
   - loop-engineering
   - ai-agents
   - coding-agents

posts/launch.md

@@ -1,27 +1,29 @@
-# Awesome Loop Engineering v0.5.0
+# Awesome Loop Engineering v0.6.0
 
-Awesome Loop Engineering v0.5.0 maps the operating layer above prompt, context, and harness engineering: the recurring system that discovers work, delegates it, verifies results, persists state, and decides what happens next.
+Awesome Loop Engineering v0.6.0 strengthens the project as both a field guide and a verifiable data product for recurring AI-agent systems.
 
-This release turns the repository from a long resource list into a browsable field guide and structured dataset.
+The collection now maps 540 sources across the operating layer above prompt, context, and harness engineering: the system that discovers work, delegates it, verifies results, persists state, and decides what happens next.
 
 ## What Is Included
 
-- 509 audited resources linked to canonical sources
-- 15 operational patterns and a comparison matrix
+- 540 audited resources linked to canonical sources
+- 15 operational patterns and a symptom-first comparison matrix
 - 15 schema-validated loop contracts
 - 6 runnable templates for local, scheduled, CI, and hosted execution
 - an interactive Resource Atlas for filtering by goal, lifecycle stage, artifact type, and evidence class
 - CSV and JSONL exports mirrored as a Hugging Face dataset
 - 8 language entry points
 
-## What Changed Since v0.4.0
+## What Changed Since v0.5.0
 
-- Expanded the audited library from 483 to 509 resources.
-- Added richer contribution, novelty, impact, evidence, lifecycle, source-status, and adoption metadata to the dataset.
-- Added an interactive, keyboard-accessible 3D lifecycle showing evidence moving through Intake, Delegate, Act, Verify, Persist, and Decide.
-- Redesigned the stack, lifecycle, contract, runtime, and maturity visuals around one consistent visual system.
-- Improved website resource discovery, sorting, mobile navigation, reduced-motion behavior, and canvas diagnostics.
-- Documented the enriched dataset fields and corrected source-line handling in the export.
+- Expanded the source-audited library from 509 to 540 resources.
+- Rechecked every row against its canonical source: 493 public sources were reachable, 4 were access-restricted, 43 are repository-native, and none were broken or unreachable in the 2026-07-17 audit.
+- Added an explicit trust and provenance layer covering editorial responsibility, automated assistance, source metadata, corrections, licensing, and versioning.
+- Replaced the full 540-row Hugging Face README mirror with a focused dataset card containing load examples, intended uses, provenance, and limitations while retaining the full repository and data files.
+- Added consistency gates so README, website, translations, launch copy, social-preview source, release metadata, and generated datasets cannot silently drift to different counts.
+- Deferred the 1 MB Resource Atlas index until readers approach it and removed scroll-hidden content so deep links, printing, screenshots, and accessibility tooling see a stable document.
+- Corrected the pull-request template to require the original publishing venue and primary-source metadata rather than this repository's name.
+- Added a dedicated annotation-correction flow and explicit ownership routing for reviews.
 
 ## Why This Matters
 
@@ -37,9 +39,10 @@ The goal is not unlimited autonomy. The goal is bounded, reviewable, evidence-dr
 - [Use the Hugging Face dataset](https://huggingface.co/datasets/cy0307/awesome-loop-engineering)
 - [Browse patterns and contracts](https://github.com/ChaoYue0307/awesome-loop-engineering#pattern-library)
 - [Run a template](https://github.com/ChaoYue0307/awesome-loop-engineering/tree/main/examples/runnable)
-- [Contribute a source or real loop](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/CONTRIBUTING.md)
+- [Review the curation standard](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/meta/CURATION.md)
+- [Contribute a source or correction](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/CONTRIBUTING.md)
 
-Corrections are especially valuable. If a cited work is summarized inaccurately, or a stronger canonical source exists, please open an issue or pull request.
+Corrections are especially valuable. If a cited work is summarized inaccurately, or a stronger canonical source exists, use the annotation-correction form or open a pull request.
 
 ## Repository
 

posts/launch.zh-CN.md

@@ -1,27 +1,29 @@
-# Awesome Loop Engineering v0.5.0
+# Awesome Loop Engineering v0.6.0
 
-Awesome Loop Engineering v0.5.0 聚焦于 prompt、context 与 harness engineering 之上的运行层：一个能够发现工作、分派任务、验证结果、持久化状态并决定下一步的循环系统。
+Awesome Loop Engineering v0.6.0 进一步把项目升级为面向循环式 AI-agent 系统的领域指南和可验证数据产品。
 
-这次更新将仓库从一份较长的资源列表升级为可浏览的领域指南和结构化数据集。
+当前集合包含 540 条资源，覆盖 prompt、context 与 harness engineering 之上的运行层：负责发现工作、分派任务、验证结果、持久化状态并决定下一步的系统。
 
 ## 本次版本包含
 
-- 509 条链接到 canonical source 的审阅资源
-- 15 个可操作的 loop patterns 与对比矩阵
+- 540 条链接到 canonical source 的审阅资源
+- 15 个可操作的 loop patterns 与按问题选择的对比矩阵
 - 15 个经过 schema 校验的 loop contracts
 - 6 个适用于本地、定时、CI 与托管环境的可运行模板
 - 可按目标、生命周期阶段、资源类型和证据类别筛选的交互式 Resource Atlas
 - CSV 与 JSONL 数据导出，并同步到 Hugging Face Dataset
 - 8 个语言入口
 
-## 相比 v0.4.0 的变化
+## 相比 v0.5.0 的变化
 
-- 审阅资源数量从 483 条增加到 509 条。
-- 为数据集补充 contribution、novelty、impact、evidence、lifecycle、source status 与 adoption 等元数据。
-- 新增支持键盘操作的 3D 生命周期，让 evidence 在 Intake、Delegate、Act、Verify、Persist 与 Decide 之间流动。
-- 统一重设计 stack、lifecycle、contract、runtime 与 maturity visuals。
-- 改进网站资源筛选、排序、移动端导航、reduced-motion 行为与 canvas diagnostics。
-- 完善数据字段文档，并修正导出过程中的 source-line 处理。
+- 审阅资源数量从 509 条增加到 540 条。
+- 逐条重新核对 canonical source：在 2026-07-17 的审计中，493 个公开来源可访问，4 个来源受访问限制，43 个为仓库原生材料，没有 broken 或 unreachable 来源。
+- 新增明确的 trust 与 provenance 说明，覆盖编辑责任、自动化辅助、来源元数据、纠错、许可证和版本管理。
+- 将 Hugging Face 上完整复制的 540 行超长 README 改为专门的数据集卡片，补充加载示例、适用场景、来源说明和局限，同时保留完整仓库与数据文件。
+- 新增一致性检查，避免 README、网站、翻译、发布文案、social preview 源文件、release metadata 与生成数据集之间的数量漂移。
+- Resource Atlas 的约 1 MB 索引改为接近该区域时再加载，并移除依赖滚动才显示的隐藏内容，让 deep link、打印、截图和辅助工具获得稳定页面。
+- 修正 pull request 模板，要求填写作品原始发布平台和 primary-source metadata，而不是本仓库名称。
+- 新增专门的 annotation correction 流程与明确的 review ownership。
 
 ## 为什么值得关注
 
@@ -37,9 +39,10 @@ Loop Engineering 继续追问：什么系统应该定期或按事件启动，发
 - [使用 Hugging Face 数据集](https://huggingface.co/datasets/cy0307/awesome-loop-engineering)
 - [查看 patterns 与 contracts](https://github.com/ChaoYue0307/awesome-loop-engineering#pattern-library)
 - [运行模板](https://github.com/ChaoYue0307/awesome-loop-engineering/tree/main/examples/runnable)
-- [贡献资源或真实 loop](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/CONTRIBUTING.md)
+- [查看 curation standard](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/meta/CURATION.md)
+- [贡献资源或提交纠错](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/CONTRIBUTING.md)
 
-如果仓库对某篇引用工作的概括不够准确，或存在更可靠的 canonical source，欢迎提交 issue 或 pull request。
+如果仓库对某篇引用工作的概括不够准确，或存在更可靠的 canonical source，请使用 annotation-correction form 或提交 pull request。
 
 ## 仓库
 

scripts/build_hf_card.py

@@ -0,0 +1,109 @@
+#!/usr/bin/env python3
+"""Build the Hugging Face dataset card from repository metadata."""
+
+from __future__ import annotations
+
+import argparse
+import json
+import re
+import sys
+from collections import Counter
+from pathlib import Path
+
+
+ROOT = Path(__file__).resolve().parents[1]
+HEADER = ROOT / "meta" / "hf_card_header.yaml"
+BODY = ROOT / "meta" / "hf_card_body.md"
+RESOURCES = ROOT / "data" / "resources.jsonl"
+CITATION = ROOT / "CITATION.cff"
+REQUIRED_METADATA = (
+    "license",
+    "language",
+    "pretty_name",
+    "size_categories",
+    "task_categories",
+    "tags",
+    "configs",
+)
+TOKEN_RE = re.compile(r"\{\{([A-Z0-9_]+)\}\}")
+
+
+def load_rows() -> list[dict[str, str]]:
+    return [json.loads(line) for line in RESOURCES.read_text(encoding="utf-8").splitlines() if line.strip()]
+
+
+def project_context() -> dict[str, str]:
+    rows = load_rows()
+    statuses = Counter(row.get("source_status", "") for row in rows)
+    audit_dates = sorted({row.get("audited_at", "")[:10] for row in rows if row.get("audited_at")})
+    version_match = re.search(r"^version:\s*([^\s]+)\s*$", CITATION.read_text(encoding="utf-8"), re.MULTILINE)
+
+    patterns = [path for path in (ROOT / "patterns").glob("*.md") if path.name not in {"README.md", "MATRIX.md"}]
+    contracts = list((ROOT / "examples").glob("*-loop.json"))
+    runnable = [path for path in (ROOT / "examples" / "runnable").iterdir() if path.is_file() and path.name != "README.md"]
+
+    return {
+        "RESOURCE_COUNT": str(len(rows)),
+        "REACHABLE_COUNT": str(statuses["ok"]),
+        "RESTRICTED_COUNT": str(statuses["restricted"]),
+        "LOCAL_COUNT": str(statuses["local_ok"]),
+        "BROKEN_COUNT": str(sum(statuses[key] for key in ("broken", "unreachable", "local_missing"))),
+        "AUDIT_DATE": audit_dates[-1] if audit_dates else "not recorded",
+        "PATTERN_COUNT": str(len(patterns)),
+        "CONTRACT_COUNT": str(len(contracts)),
+        "RUNNABLE_COUNT": str(len(runnable)),
+        "VERSION": version_match.group(1) if version_match else "unversioned",
+    }
+
+
+def validate_header(header: str) -> list[str]:
+    failures: list[str] = []
+    lines = header.strip().splitlines()
+    if len(lines) < 3 or lines[0] != "---" or lines[-1] != "---":
+        failures.append("meta/hf_card_header.yaml must be wrapped in YAML front matter delimiters")
+    for key in REQUIRED_METADATA:
+        if not re.search(rf"^{re.escape(key)}:\s*", header, re.MULTILINE):
+            failures.append(f"meta/hf_card_header.yaml is missing {key}")
+    return failures
+
+
+def render_card() -> tuple[str, list[str]]:
+    header = HEADER.read_text(encoding="utf-8").strip()
+    body = BODY.read_text(encoding="utf-8")
+    context = project_context()
+    failures = validate_header(header)
+
+    rendered = TOKEN_RE.sub(lambda match: context.get(match.group(1), match.group(0)), body)
+    unresolved = sorted(set(TOKEN_RE.findall(rendered)))
+    if unresolved:
+        failures.append("unresolved dataset-card tokens: " + ", ".join(unresolved))
+
+    return f"{header}\n\n{rendered.lstrip()}", failures
+
+
+def main() -> int:
+    parser = argparse.ArgumentParser(description=__doc__)
+    parser.add_argument("--check", action="store_true", help="validate the card template without writing it")
+    parser.add_argument("--output", type=Path, help="write the rendered card to this path")
+    args = parser.parse_args()
+
+    card, failures = render_card()
+    if failures:
+        print("Hugging Face dataset card check failed:", file=sys.stderr)
+        for failure in failures:
+            print(f"- {failure}", file=sys.stderr)
+        return 1
+
+    if args.check:
+        return 0
+    if args.output:
+        args.output.parent.mkdir(parents=True, exist_ok=True)
+        args.output.write_text(card, encoding="utf-8")
+        print(f"Wrote {args.output}")
+    else:
+        sys.stdout.write(card)
+    return 0
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())

scripts/check_project_consistency.py

@@ -0,0 +1,84 @@
+#!/usr/bin/env python3
+"""Check cross-surface counts, release metadata, and generated discovery files."""
+
+from __future__ import annotations
+
+import csv
+import json
+import sys
+from pathlib import Path
+
+from build_hf_card import project_context, render_card
+
+
+ROOT = Path(__file__).resolve().parents[1]
+
+
+def require(path: Path, snippets: list[str], failures: list[str]) -> None:
+    text = path.read_text(encoding="utf-8")
+    for snippet in snippets:
+        if snippet not in text:
+            failures.append(f"{path.relative_to(ROOT)}: missing {snippet!r}")
+
+
+def main() -> int:
+    context = project_context()
+    count = context["RESOURCE_COUNT"]
+    version = context["VERSION"]
+    failures: list[str] = []
+
+    require(
+        ROOT / "README.md",
+        [
+            f"resources-{count}-",
+            f"**{count} curated resources**",
+            f"covers all {count} rows",
+        ],
+        failures,
+    )
+    require(
+        ROOT / "docs" / "index.html",
+        [
+            f'content="{count} audited resources',
+            f">{count}</b><span>curated entries</span>",
+            f"Search {count} audited works",
+            f"Search {count} audited resources",
+            f'"version": "{version}"',
+        ],
+        failures,
+    )
+    require(ROOT / "meta" / "social-preview.html", [f">{count}</b>"], failures)
+    require(ROOT / "posts" / "launch.md", [f"# Awesome Loop Engineering v{version}", f"{count} audited resources"], failures)
+    require(ROOT / "posts" / "launch.zh-CN.md", [f"# Awesome Loop Engineering v{version}", f"{count} 条"], failures)
+    require(ROOT / "meta" / "DISTRIBUTION.md", [f"v{version}", f"{count} audited resources"], failures)
+
+    for translation in sorted(ROOT.glob("README.*.md")):
+        require(translation, [count], failures)
+
+    with (ROOT / "data" / "resources.csv").open(encoding="utf-8", newline="") as handle:
+        csv_count = sum(1 for _ in csv.DictReader(handle))
+    if csv_count != int(count):
+        failures.append(f"data/resources.csv: expected {count} rows, found {csv_count}")
+
+    site_payload = json.loads((ROOT / "docs" / "assets" / "resources.json").read_text(encoding="utf-8"))
+    if site_payload.get("count") != int(count) or len(site_payload.get("resources", [])) != int(count):
+        failures.append("docs/assets/resources.json: count or resources array is stale")
+
+    _, card_failures = render_card()
+    failures.extend(card_failures)
+
+    if failures:
+        print("Project consistency check failed:", file=sys.stderr)
+        for failure in failures:
+            print(f"- {failure}", file=sys.stderr)
+        return 1
+
+    print(
+        f"Validated {count} resources, {context['PATTERN_COUNT']} patterns, "
+        f"{context['CONTRACT_COUNT']} contracts, and release v{version}."
+    )
+    return 0
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())