Make dataset copy reader focused

Mirror GitHub commit 6947e8c. Replace process-first copy with concrete descriptions across the dataset card, field guide, site, and generated resource sheets.

.github/pull_request_template.md

@@ -78,7 +78,7 @@ Which README section did you update?
 
 ## Accuracy And Provenance
 
-- Canonical source checked:
+- Original or official source checked:
 - Original publishing venue or platform:
 - Publication date, authors, and identifier verified from:
 - Material caveats or source-access limits:
@@ -97,7 +97,7 @@ Which README section did you update?
 - [ ] 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.
+- [ ] Any automated assistance was checked against the original or official source; generated text was not treated as evidence.
 - [ ] I ran `python3 scripts/render_readme_tables.py` and `python3 scripts/export_resource_dataset.py` after changing resource rows.
 - [ ] I agree that my contribution to this repository is released under `CC0-1.0`.
 - [ ] I did not copy third-party content into this repository without the right to do so.

.github/workflows/quality.yml

@@ -56,6 +56,9 @@ jobs:
       - name: Check resource type labels
         run: python scripts/check_resource_labels.py README.md
 
+      - name: Check reader-facing copy
+        run: python scripts/check_reader_facing_copy.py
+
       - name: Check README resource tables
         run: python scripts/render_readme_tables.py --check
 

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, version 0.8.0}
+  note         = {Field guide and implementation kit for Loop Engineering, version 0.8.0}
 }

CITATION.cff

@@ -9,7 +9,7 @@ authors:
     given-names: "Chaoyue"
 repository-code: "https://github.com/ChaoYue0307/awesome-loop-engineering"
 url: "https://chaoyue0307.github.io/awesome-loop-engineering/"
-abstract: "Source-audited resources and reusable patterns for recurring, stateful, verified AI-agent systems."
+abstract: "Practical resources and reusable patterns for recurring, stateful, verified AI-agent systems."
 keywords:
   - loop-engineering
   - ai-agents

CONTRIBUTING.md

@@ -1,24 +1,24 @@
 # Contributing
 
-Contribute a canonical source, an evidence-backed correction, or a loop you have run.
+Contribute an original or official source, an evidence-backed correction, or a loop you have run.
 
 Contributions must address recurring AI-agent or coding-agent systems with explicit triggers, work intake, verification, durable state, budgets, escalation, and exit.
 
-Before submitting, read the [curation standard](meta/CURATION.md). It defines scope, evidence tiers, annotation rules, and correction handling.
+Before submitting, read the [resource selection guide](meta/CURATION.md). It explains the scope, evidence labels, summary style, and correction process.
 
 ## Fastest Contribution (Under Five Minutes)
 
 Use the [resource suggestion form](https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=resource-suggestion.yml) to propose one source without preparing a fork. Include:
 
-- the canonical public URL;
+- the original or official public URL;
 - the most specific README category;
 - one sentence on the contribution, novelty, or practical value for recurring agent systems;
 - the source type and evidence tier;
 - any caveat, such as vendor bias, a paywall, early-stage status, or weak evidence.
 
-Maintainers apply the same scope, duplication, source-quality, and annotation checks used for pull requests. Corrections are equally valuable: link the current entry and state the exact change.
+Each suggestion is checked for scope, duplication, source quality, and a useful summary. Corrections are equally valuable: link the current entry and state the exact change.
 
-For an inaccurate summary, contribution, novelty, impact, authorship, date, venue, identifier, or canonical link, use the [annotation-correction form](https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=annotation-correction.yml). Include primary-source evidence; omit unavailable metadata rather than guessing.
+For an inaccurate summary, contribution, novelty, impact, authorship, date, venue, identifier, or source link, use the [annotation-correction form](https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=annotation-correction.yml). Include primary-source evidence; omit unavailable metadata rather than guessing.
 
 ## Quick PR Flow
 
@@ -28,10 +28,10 @@ For an inaccurate summary, contribution, novelty, impact, authorship, date, venu
 1. Add one metadata-rich row with a resource type label, verified year/source context, and one specific key feature:
 
 ```md
-| 📄 **[Title](https://example.com)**<br><sub>Paper</sub> | **2026** · arXiv<br><sub>First Author et al.</sub> | One sentence explaining the resource's contribution to Loop Engineering. | **Tier A** · Research preprint<br><sub>Preprint; inspect methods and evaluation</sub> |
+| 📄 **[Title](https://example.com)**<br><sub>Paper</sub> | **2026** · arXiv<br><sub>First Author et al.</sub> | One sentence explaining the resource's contribution to Loop Engineering. | **Research preprint**<br><sub>Preprint; inspect methods and evaluation</sub> |
 ```
 
-When a source exposes no reliable publication date, omit the year and keep only the original venue or publishing platform. Do not infer a date from a search-result snippet. Maintainers derive the evidence tier from the audited source class and regenerate the table layout and structured exports after review.
+When a source exposes no reliable publication date, omit the year and keep only the original venue or publishing platform. Do not infer a date from a search-result snippet. The evidence label is derived from the source type, and the table layout and structured exports are regenerated after review.
 
 1. Open a PR using the template and explain:
    - why the resource belongs;
@@ -40,11 +40,11 @@ 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.
+If automated tools assisted discovery, extraction, or drafting, say so in the PR. Check every resulting claim against the original or official 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).
+By contributing to this repository, you agree that your original summaries, templates, patterns, metadata, and documentation are released under [CC0-1.0](LICENSE).
 
 Do not copy third-party articles, papers, images, documentation, code, or other content into this repository unless you have the right to do so. Prefer stable links and short original annotations. External resources keep their own licenses and terms.
 
@@ -82,7 +82,7 @@ Prefer higher tiers when two resources cover the same idea.
 | --- | --- | --- |
 | A | Primary source or official docs | Tool docs, paper, project README, author write-up |
 | B | Practitioner write-up with implementation detail | Field notes, playbooks, postmortems |
-| C | Curated survey or high-quality explainer | Taxonomy, comparison, tutorial |
+| C | Synthesis or high-quality explainer | Taxonomy, comparison, tutorial |
 | D | Commentary or news coverage | Useful only when it documents origin, adoption, or debate |
 
 If two links cover the same idea, prefer the more primary, stable, and implementation-specific source.
@@ -171,7 +171,7 @@ See [TRANSLATIONS.md](TRANSLATIONS.md).
 
 Translation PRs should:
 
-- link back to the canonical English README;
+- link back to the full English guide;
 - preserve the narrow AI/coding-agent scope;
 - keep resource URLs unchanged;
 - update language navigation if a new language file is added;
@@ -190,4 +190,4 @@ If you do not want to open a PR, use the resource suggestion issue template. Ple
 
 ## Review Standard
 
-Maintainers may ask for stronger relevance, a more precise category, a better annotation, or removal of promotional language. The goal is to keep the list useful for people designing real agent loops, not to collect every AI-agent link on the internet.
+A review may ask for stronger relevance, a more precise category, a better summary, or removal of promotional language. The goal is to keep the list useful for people designing real agent loops, not to collect every AI-agent link on the internet.

DEFINITION.md

@@ -1,4 +1,4 @@
-# Canonical Definition
+# Working Definition
 
 Use this definition to scope a system, review a design, or cite the concept consistently.
 

FUTURE-DIRECTIONS.md

@@ -152,7 +152,7 @@ The tiers describe dependency order, not prestige. Establish trustworthy state t
 - **Decision unlocked:** whether an operator can reconstruct why the loop acted, retried, escalated, or exited.
 - **Build:** a receipt envelope for trigger, objective version, input identity, action, tool result, verifier result, state transition, budget delta, next action, and redaction policy, mapped where practical to [OpenTelemetry GenAI semantic conventions](https://github.com/open-telemetry/semantic-conventions-genai).
 - **Measure:** receipt coverage, missing causal links, replay agreement, trace overhead, redaction failures, and time to diagnose seeded incidents.
-- **Starter slice:** instrument one validated contract end to end and build a replay view that derives the decision timeline from receipts rather than model narration.
+- **Starter slice:** instrument one schema-checked contract end to end and build a replay view that derives the decision timeline from receipts rather than model narration.
 - **Completion gate:** an independent reviewer can identify the cause of a seeded failure and reproduce the control decision without access to the original chat session.
 
 ### 9. Security, Permissions, And Containment

README.de.md

@@ -28,7 +28,7 @@ Ein Loop entdeckt Arbeit, übergibt sie an einen oder mehrere Agenten, prüft da
 
 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.
 
-Starte mit 579 geprüften 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.
+Starte mit 579 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.
 
 ## Mentales Modell
 
@@ -71,7 +71,7 @@ Ein nützlicher Loop macht normalerweise diese Bestandteile sichtbar:
 
 ## Erste Lektüre
 
-Die vollständige Ressourcenliste bleibt im kanonischen englischen README: [README.md](README.md).
+Alle Ressourcen findest du im vollständigen englischen Leitfaden: [README.md](README.md).
 
 Empfohlene Einstiege:
 

README.es.md

@@ -28,7 +28,7 @@ Un loop descubre trabajo, lo delega a uno o más agentes, verifica el resultado,
 
 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.
 
-Empieza con 579 recursos auditados, 20 patrones operativos, 20 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.
+Empieza con 579 recursos, 20 patrones operativos, 20 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.
 
 ## Modelo Mental
 
@@ -71,7 +71,7 @@ Un loop útil normalmente necesita estas partes:
 
 ## Por Dónde Empezar
 
-La lista completa de recursos vive en el README canónico en inglés: [README.md](README.md).
+Explora todos los recursos en la guía completa en inglés: [README.md](README.md).
 
 Recursos iniciales recomendados:
 

README.fr.md

@@ -28,7 +28,7 @@ Un loop découvre du travail, le délègue à un ou plusieurs agents, vérifie l
 
 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.
 
-Commencez avec 579 ressources auditées, 20 patterns opérationnels, 20 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.
+Commencez avec 579 ressources, 20 patterns opérationnels, 20 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.
 
 ## Modèle Mental
 
@@ -71,7 +71,7 @@ Un loop utile rend généralement visibles ces éléments :
 
 ## Premières Lectures
 
-La liste complète des ressources reste dans le README canonique en anglais : [README.md](README.md).
+Explorez toutes les ressources dans le guide complet en anglais : [README.md](README.md).
 
 Ressources recommandées pour commencer :
 

README.ja.md

@@ -71,7 +71,7 @@ Prompt、context、harness engineering は 1 回の実行を良くします。Lo
 
 ## はじめに読むもの
 
-完全なリソース一覧は英語の canonical README にあります: [README.md](README.md)。
+すべてのリソースは英語の完全版ガイドで確認できます: [README.md](README.md)。
 
 おすすめの入口:
 

README.ko.md

@@ -71,7 +71,7 @@ Prompt, context, harness engineering 은 한 번의 실행을 더 좋게 만듭
 
 ## 시작하기
 
-전체 리소스 목록은 영어 canonical README 에 있습니다: [README.md](README.md).
+전체 리소스는 영어 전체 가이드에서 볼 수 있습니다: [README.md](README.md).
 
 추천 시작 자료:
 

README.md

@@ -38,36 +38,36 @@ configs:
 <h1 align="center">Awesome Loop Engineering Dataset</h1>
 
 <p align="center">
-  A source-audited dataset of 579 papers, official docs, tools, benchmarks, patterns, critiques, and implementation guides for recurring AI-agent systems.
+  A structured dataset of 579 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/blob/main/meta/CURATION.md">Resource selection</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 pairs one source with a concise editorial assessment, bibliographic metadata, lifecycle and audience facets, evidence classification, audit status, and point-in-time repository statistics when applicable.
+Each row connects an original source to its contribution, novelty, impact, publication details, lifecycle stages, audience, evidence type, link status, and repository context when applicable.
 
 Current release: **v0.8.0**
 
 | Surface | Count |
 | --- | ---: |
-| Source-audited resources | 579 |
+| Resources | 579 |
 | Operational patterns | 20 |
-| Validated loop contracts | 20 |
+| Adaptable loop contracts | 20 |
 | Runtime starters | 8 |
 
-The source audit dated **2026-07-18** reports these row statuses: **528 reachable public**, **3 access restricted**, **48 repository-native**, and **0 broken or unreachable**.
+At the **2026-07-18** source check, **528 public links opened successfully**, **3 required access**, **48 pointed to repository files**, and **0 were broken or unreachable**.
 
 ## What A Loop Contract Is
 
 A **Loop Contract** is a reviewable operating specification for one recurring agent job. It fixes what authorizes a run, which work and actions are allowed, what context and roles the run uses, which external evidence proves progress, what state survives, how much the loop may spend, and when a human takes over or the loop exits.
 
-Recurring agents need this policy because schedules, events, queues, and goals remove live supervision. Without explicit boundaries, missing decisions become hidden defaults: the loop can select the wrong work, widen its own scope, approve itself, forget failed attempts, or retry without a stopping rule. Start with the [JSON schema](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/schemas/loop-contract.schema.json) and adapt one of the [20 validated examples](https://github.com/ChaoYue0307/awesome-loop-engineering/tree/main/examples).
+Recurring agents need this policy because schedules, events, queues, and goals remove live supervision. Without explicit boundaries, missing decisions become hidden defaults: the loop can select the wrong work, widen its own scope, approve itself, forget failed attempts, or retry without a stopping rule. Start with the [JSON schema](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/schemas/loop-contract.schema.json) and adapt one of the [20 schema-checked examples](https://github.com/ChaoYue0307/awesome-loop-engineering/tree/main/examples).
 
 ## Loop Maturity Model
 
@@ -124,7 +124,7 @@ Use `url` as the durable join key. `row_id` and `source_line` are positional and
 - Compare works by lifecycle, audience, evidence class, source type, and publication metadata.
 - Separate model, agent, harness, workflow, operations, evaluation, and cross-layer resources without treating adjacent model recurrence as a complete operational loop.
 - Build literature maps, reading lists, dashboards, or retrieval indexes.
-- Audit contribution, novelty, impact, provenance, and evidence claims.
+- Inspect contribution, novelty, impact, source, and evidence fields before following a claim.
 - Find reusable patterns, contracts, schemas, executable examples, and copy/paste runtime templates.
 
 Do not use `signal_strength`, GitHub stars, forks, or inclusion in this collection as a quality label, endorsement, or automated ranking of scientific validity.
@@ -148,38 +148,38 @@ The primary configuration is `resources`, with one `train` split backed by the n
 | 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` | What the resource contributes to recurring agent systems. |
+| Resource analysis | `annotation`, `key_contribution`, `novelty`, `impact` | What the resource contributes to recurring agent systems. |
 | Scope | `loop_layer`, `scope_fit` | Where recurrence lives and whether the source is direct, enabling, or adjacent to operational Loop Engineering. |
 | Navigation | `section`, `collection`, `user_goal`, `lifecycle_stages`, `audience` | Where the resource fits and who it serves. |
 | Evidence | `evidence_class`, `evidence_tier`, `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. |
+| Publication | `authors`, `publication_date`, `publication_year`, `publication_venue`, `publisher`, `doi`, `arxiv_id`, `primary_category` | Bibliographic data exposed by the original or official source. |
+| Source details | `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. |
+| Export trace | `source_readme`, `source_line`, `source_url`, `date_added` | How the row maps back to the full 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
+## How To Read The Evidence
 
-Start with 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).
+Open the linked work before relying on a summary. Evidence labels distinguish published research, official documentation, inspectable implementations, practitioner analysis, risk analysis, and discovery indexes; they describe the kind of source, not its scientific quality.
 
-Annotations are original syntheses, not copied abstracts or 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; the maintainer owns each released inclusion decision and annotation.
+Summaries explain each work's contribution in original language rather than copying abstracts. They do not imply author endorsement. Follow the source link to inspect methods, results, limitations, licenses, and current documentation.
 
-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).
+The latest link-check results are 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 selective rather than exhaustive, and one person currently reviews changes.
 - 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.
+- A successful URL check proves that a link opened at check time, not that its claims are correct, permanent, or independently validated.
+- Access-restricted rows could not be fully retrieved during the latest check and should be opened 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.
+- Linked third-party works retain their own licenses and terms; CC0-1.0 covers only original repository descriptions, metadata, templates, and documentation.
 
 ## Versioning And Corrections
 
-GitHub Releases define versioned snapshots; cite a release or commit for reproducibility. Submit corrections to summaries, contribution, novelty, impact, authorship, dates, venues, identifiers, or canonical URLs through the [correction form](https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=annotation-correction.yml).
+GitHub Releases define versioned snapshots; cite a release or commit for reproducibility. Submit corrections to summaries, contribution, novelty, impact, authorship, dates, venues, identifiers, or source URLs through the [correction form](https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=annotation-correction.yml).
 
 ## Citation
 

README.pt-BR.md

@@ -28,7 +28,7 @@ Um loop descobre trabalho, delega para um ou mais agentes, verifica o resultado,
 
 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.
 
-Comece com 579 recursos auditados, 20 patterns operacionais, 20 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.
+Comece com 579 recursos, 20 patterns operacionais, 20 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.
 
 ## Modelo Mental
 
@@ -71,7 +71,7 @@ Um loop útil normalmente precisa deixar estes elementos visíveis:
 
 ## Primeiras Leituras
 
-A lista completa de recursos fica no README canônico em inglês: [README.md](README.md).
+Explore todos os recursos no guia completo em inglês: [README.md](README.md).
 
 Leituras recomendadas:
 

README.zh-CN.md

@@ -32,7 +32,7 @@ Prompt engineering 改进你对模型说什么。Context engineering 改进模
 
 Loop Engineering 专指具备明确触发、外部验证和持久状态的可重复 AI-agent 与 coding-agent 系统，不包括软件事件循环、控制论、增长循环、通用 workflow automation 或非 AI feedback loop。
 
-可直接从 579 条经审核资源、20 个操作模式、20 个经 schema 校验的 loop contracts 和 8 个 runtime starters（3 个可直接执行，5 个可复制改造）开始，并通过社区 gallery 和 8 种语言入口继续探索。
+可直接从 579 篇论文、官方文档、工具、benchmark 与实践指南，20 个操作模式、20 个经 schema 校验的 loop contracts 和 8 个 runtime starters（3 个可直接执行，5 个可复制改造）开始，并通过社区 gallery 和 8 种语言入口继续探索。
 
 ## 一句话定位
 

ROADMAP.md

@@ -8,7 +8,7 @@ Use the role-based [Future Directions agenda](FUTURE-DIRECTIONS.md) to choose re
 
 - Collect more direct Loop Engineering sources as the term stabilizes.
 - Add real or anonymized gallery entries from practitioners running recurring agent loops.
-- Turn more validated contracts into runtime-specific executables with crash recovery, timeouts, replayable receipts, and failure-injection tests.
+- Turn more schema-checked contracts into runtime-specific executables with crash recovery, timeouts, replayable receipts, and failure-injection tests.
 - Add more translations for the introduction, mental model, Loop Contract, and contribution guide.
 - Audit contextual sources in small batches; replace weak summaries and secondary links with canonical evidence.
 - Replace unstable links with primary sources, official docs, papers, or implementation-heavy write-ups.

TRANSLATIONS.md

@@ -1,6 +1,6 @@
 # Translations
 
-Translate the core Loop Engineering concepts for new audiences while preserving the boundaries and facts in the canonical [English README](README.md).
+Translate the core Loop Engineering concepts for new audiences while preserving the boundaries and facts in the full [English guide](README.md).
 
 ## Available
 
@@ -44,7 +44,7 @@ Maintainers and contributors are welcome for:
 
 ## Translation PR Checklist
 
-- [ ] The translation links back to the canonical English README.
+- [ ] The translation links back to the full English guide.
 - [ ] The language switcher has been updated in `README.md`.
 - [ ] The `<!-- last-synced: YYYY-MM-DD -->` marker is present and current.
 - [ ] The translation preserves the scope boundary.

data/README.md

@@ -1,13 +1,13 @@
 # Dataset Exports
 
-Download deterministic tabular exports of all 579 source-audited resources.
+Download all 579 resources as deterministic tabular exports.
 
 - `resources.csv` - Tabular export for spreadsheets and ad hoc analysis.
 - `resources.jsonl` - JSON Lines export and source for the Hugging Face Parquet build.
 - `resources.parquet` - Native Parquet shard generated in the Hugging Face release snapshot; it powers the Dataset Viewer without relying on server-side conversion.
 - `../docs/assets/resources.json` - Slim generated payload used by the website's searchable Resource Atlas.
 - `first_seen.json` - Forward-only sidecar mapping resource URL to the date it was first added; the export left-joins it into the `date_added` column. Empty `date_added` means the entry predates per-entry tracking (started 2026-07-15).
-- `resource_source_audit.csv` - Retrieval-time audit of every row, including URL status, source title metadata, arXiv IDs, and GitHub repository stats where available.
+- `resource_source_audit.csv` - Point-in-time source check for every row, including URL status, source title metadata, arXiv IDs, and GitHub repository stats where available.
 - `arxiv_publication_overrides.csv` - Human-verified conference, journal, and workshop records backed by official proceedings, DOI registries, OpenReview, or current author-supplied acceptance notes.
 - `arxiv_publication_audit.csv` - Complete decision table for every arXiv-linked resource: published, accepted, or preprint-only.
 
@@ -15,10 +15,10 @@ The exports preserve each section and annotation while adding four discovery lay
 
 - **Scope facets**: `loop_layer` identifies where recurrence lives (`model`, `agent`, `harness`, `workflow`, `operations`, `evaluation`, or `cross-layer`); `scope_fit` distinguishes resources that are `direct`, `enabling`, or `adjacent` to operational Loop Engineering.
 - **Task facets**: `collection`, `user_goal`, `lifecycle_stages`, and `audience` answer why a reader needs the source and where it fits in the Loop Contract.
-- **Evidence facets**: `evidence_class`, `evidence_tier`, `signal_strength`, `source_status`, canonical URL, source metadata, GitHub statistics, arXiv ID, and audit timestamp separate source provenance from popularity or editorial judgment.
+- **Evidence facets**: `evidence_class`, `evidence_tier`, `signal_strength`, `source_status`, original URL, source metadata, GitHub statistics, arXiv ID, and check timestamp separate source type from popularity or a recommendation.
 - **Publication facets**: `authors`, `publication_date`, `publication_year`, `publication_venue`, `publisher`, `doi`, `publication_note`, `primary_category`, and `metadata_source` provide a paper-like bibliographic row without inventing missing facts.
 
-`key_contribution`, `novelty`, and `impact` are resource-specific. Model-level recurrence is retained as an adjacent foundation because it repeats learned blocks or latent-state updates inside one inference; it does not by itself supply work intake, external verification, durable state, budgets, or human handoff. `evidence_tier` follows the public A-C source hierarchy: A for primary or official artifacts, B for implementation-grounded practice and risk analysis, and C for curated synthesis. `signal` states the evidence basis and limits; GitHub stars and forks provide point-in-time context, never proof of reliability. `signal_strength` is `high` for primary official documentation and benchmarks, `medium` for inspectable implementations, papers, patterns, and locally maintained artifacts, `contextual` for practitioner analysis and curated lists, and `unverified` only when the latest audit cannot validate availability.
+`key_contribution`, `novelty`, and `impact` are resource-specific. Model-level recurrence is retained as an adjacent foundation because it repeats learned blocks or latent-state updates inside one inference; it does not by itself supply work intake, external verification, durable state, budgets, or human handoff. `evidence_tier` follows the public A-C source hierarchy: A for primary or official artifacts, B for implementation-grounded practice and risk analysis, and C for synthesis and discovery indexes. `signal` states the evidence basis and limits; GitHub stars and forks provide point-in-time context, never proof of reliability. `signal_strength` is `high` for primary official documentation and benchmarks, `medium` for inspectable implementations, papers, patterns, and locally maintained artifacts, `contextual` for practitioner analysis and discovery indexes, and `unverified` only when the latest source check cannot validate availability.
 
 ## Load And Query
 
@@ -54,7 +54,7 @@ Use `url` as the durable join key. `row_id` and `source_line` are positional and
 
 ## Reproducibility
 
-Render the README rows first, then regenerate all three discovery files after changing resource entries or refreshing the source audit:
+Render the README rows first, then regenerate all three discovery files after changing resource entries or refreshing the source check:
 
 ```sh
 python3 scripts/render_readme_tables.py
@@ -66,15 +66,15 @@ python3 scripts/build_hf_card.py --check
 
 Every README resource-table row becomes one deterministic export row with its marker, resource type, title, link, original publishing platform or venue, annotation, section, and source line.
 
-Run a network-backed source audit when refreshing the Hugging Face dataset:
+Run a network-backed source check when refreshing the Hugging Face dataset:
 
 ```sh
 python3 scripts/audit_resource_sources.py --timeout 20 --workers 16 --attempts 2 --github-cli
 ```
 
-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, while verified conference or journal records take precedence for venue, publisher, DOI, and canonical URL. The arXiv ID and original preprint link remain available for provenance and access. 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.
+The source-check 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, while verified conference or journal records take precedence for venue, publisher, DOI, and original URL. The arXiv ID and original preprint link remain available for access and traceability. 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.
 
-Refresh publication decisions before applying them to a current source audit:
+Refresh publication decisions before applying them to the current source check:
 
 ```sh
 python3 scripts/resolve_arxiv_publications.py --refresh --cache-dir /tmp/ale-publication-cache

data/resource_source_audit.csv

@@ -568,13 +568,13 @@ ale-0566,Awesome AI Agent Papers,https://github.com/VoltAgent/awesome-ai-agent-p
 ale-0567,awesome-ralph,https://github.com/snwfdhmp/awesome-ralph,external,github.com,ok,200,https://github.com/snwfdhmp/awesome-ralph,https://github.com/snwfdhmp/awesome-ralph,text/html; charset=utf-8,"GitHub - snwfdhmp/awesome-ralph: A curated list of resources about Ralph, the AI coding technique that runs AI coding agents in automated loops until specifications are fulfilled. · GitHub","A curated list of resources about Ralph, the AI coding technique that runs AI coding agents in automated loops until specifications are fulfilled. - snwfdhmp/awesome-ralph",,2026-01-19,2026,snwfdhmp/awesome-ralph,GitHub,,,,github-api,snwfdhmp/awesome-ralph,913,72,12,"A curated list of resources about Ralph, the AI coding technique that runs AI coding agents in automated loops until specifications are fulfilled.",,2026-01-19T08:42:54Z,2026-07-13T12:09:52Z,,,2026-07-18T08:16:45+00:00
 ale-0568,Awesome Agent Loops,https://github.com/serenakeyitan/awesome-agent-loops,external,github.com,ok,200,https://github.com/serenakeyitan/awesome-agent-loops,https://github.com/serenakeyitan/awesome-agent-loops,text/html; charset=utf-8,"GitHub - serenakeyitan/awesome-agent-loops: A curated collection of the best /loop, /goal, and /schedule uses for Claude Code & Codex — real commands sourced from Twitter/X. The awesome-list of agent loops. · GitHub","A curated collection of the best /loop, /goal, and /schedule uses for Claude Code & Codex — real commands sourced from Twitter/X. The awesome-list of agent loops. - serenakeyitan/awesome-agent-loops",,2026-06-09,2026,serenakeyitan/awesome-agent-loops,GitHub,,,,github-api,serenakeyitan/awesome-agent-loops,194,16,2,"A curated collection of the best /loop, /goal, and /schedule uses for Claude Code & Codex — real commands sourced from Twitter/X. The awesome-list of agent loops.",CC-BY-4.0,2026-06-09T01:26:51Z,2026-07-15T11:44:20Z,,,2026-07-18T08:16:45+00:00
 ale-0569,Awesome Loop Models,https://github.com/huskydoge/Awesome-Loop-Models,external,github.com,ok,200,https://github.com/huskydoge/Awesome-Loop-Models,https://github.com/huskydoge/Awesome-Loop-Models,text/html; charset=utf-8,GitHub - huskydoge/Awesome-Loop-Models: A curated list of papers and selected technical blogs on Loop Models. · GitHub,A curated list of papers and selected technical blogs on Loop Models. - huskydoge/Awesome-Loop-Models,,2026-04-24,2026,huskydoge/Awesome-Loop-Models,GitHub,,,,github-api,huskydoge/Awesome-Loop-Models,215,8,3,A curated list of papers and selected technical blogs on Loop Models.,MIT,2026-04-24T12:16:55Z,2026-07-18T06:50:42Z,,,2026-07-18T08:16:45+00:00
-ale-0570,Resource Atlas,https://chaoyue0307.github.io/awesome-loop-engineering/,external,chaoyue0307.github.io,ok,200,https://chaoyue0307.github.io/awesome-loop-engineering/,https://chaoyue0307.github.io/awesome-loop-engineering/,text/html; charset=utf-8,Awesome Loop Engineering,"555 source-audited resources, 20 patterns, 20 validated contracts, and 8 runtime starters for recurring, stateful, verified AI-agent systems.",Chaoyue He,,,,chaoyue0307.github.io,,,,html-meta,,,,,,,,,,,2026-07-18T08:16:45+00:00
+ale-0570,Resource Atlas,https://chaoyue0307.github.io/awesome-loop-engineering/,external,chaoyue0307.github.io,ok,200,https://chaoyue0307.github.io/awesome-loop-engineering/,https://chaoyue0307.github.io/awesome-loop-engineering/,text/html; charset=utf-8,Awesome Loop Engineering,"Explore 579 resources from model recurrence to governed agent operations, then build with 20 patterns, 20 contracts, and 8 runtime starters.",Chaoyue He,,,,chaoyue0307.github.io,,,,html-meta,,,,,,,,,,,2026-07-18T08:16:45+00:00
 ale-0571,Hugging Face dataset,https://huggingface.co/datasets/cy0307/awesome-loop-engineering,external,huggingface.co,ok,200,https://huggingface.co/datasets/cy0307/awesome-loop-engineering,https://huggingface.co/datasets/cy0307/awesome-loop-engineering,text/html; charset=utf-8,cy0307/awesome-loop-engineering · Datasets at Hugging Face,We’re on a journey to advance and democratize artificial intelligence through open source and open science.,,,,,Hugging Face,,,,domain-fallback,,,,,,,,,,,2026-07-18T08:16:45+00:00
 ale-0572,Dataset export guide,data/README.md,local_path,,local_ok,,https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/data/README.md,https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/data/README.md,,Dataset export guide,,,,2026,GitHub,GitHub,,,,repository,,,,,,,,,,,2026-07-18T08:16:45+00:00
 ale-0573,Runtime selection guide,meta/RUNTIME_SELECTION.md,local_path,,local_ok,,https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/meta/RUNTIME_SELECTION.md,https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/meta/RUNTIME_SELECTION.md,,Runtime selection guide,,,,2026,GitHub,GitHub,,,,repository,,,,,,,,,,,2026-07-18T08:16:45+00:00
 ale-0574,Future Directions agenda,FUTURE-DIRECTIONS.md,local_path,,local_ok,,https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/FUTURE-DIRECTIONS.md,https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/FUTURE-DIRECTIONS.md,,Future Directions agenda,,,,2026,GitHub,GitHub,,,,repository,,,,,,,,,,,2026-07-18T08:16:45+00:00
-ale-0575,Release notes,https://github.com/ChaoYue0307/awesome-loop-engineering/releases,external,github.com,ok,200,https://github.com/ChaoYue0307/awesome-loop-engineering/releases,https://github.com/ChaoYue0307/awesome-loop-engineering/releases,text/html; charset=utf-8,Releases · ChaoYue0307/awesome-loop-engineering · GitHub,"🔁 555 source-audited resources · 20 operational patterns · 20 validated contracts · 8 runtime starters · interactive atlas + dataset for recurring, stateful, verified AI-agent systems. - Releases · ChaoYue0307/awesome-loop-engineering",,2026-06-09,2026,GitHub Releases,GitHub,,,,github-api,ChaoYue0307/awesome-loop-engineering,31,6,9,"🔁 555 source-audited resources · 20 operational patterns · 20 validated contracts · 8 runtime starters · interactive atlas + dataset for recurring, stateful, verified AI-agent systems.",CC0-1.0,2026-06-09T16:17:27Z,2026-07-18T07:38:30Z,,,2026-07-18T08:16:45+00:00
+ale-0575,Release notes,https://github.com/ChaoYue0307/awesome-loop-engineering/releases,external,github.com,ok,200,https://github.com/ChaoYue0307/awesome-loop-engineering/releases,https://github.com/ChaoYue0307/awesome-loop-engineering/releases,text/html; charset=utf-8,Releases · ChaoYue0307/awesome-loop-engineering · GitHub,"🔁 Explore 579 resources from model recurrence to governed agent operations · Build with 20 patterns, 20 contracts, and 8 runtime starters · Atlas + dataset. - Releases · ChaoYue0307/awesome-loop-engineering",,2026-06-09,2026,GitHub Releases,GitHub,,,,github-api,ChaoYue0307/awesome-loop-engineering,31,6,9,"🔁 Explore 579 resources from model recurrence to governed agent operations · Build with 20 patterns, 20 contracts, and 8 runtime starters · Atlas + dataset.",CC0-1.0,2026-06-09T16:17:27Z,2026-07-18T07:38:30Z,,,2026-07-18T08:16:45+00:00
 ale-0576,Roadmap,ROADMAP.md,local_path,,local_ok,,https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/ROADMAP.md,https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/ROADMAP.md,,Roadmap,,,,2026,GitHub,GitHub,,,,repository,,,,,,,,,,,2026-07-18T08:16:45+00:00
 ale-0577,Launch article,posts/launch.md,local_path,,local_ok,,https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/posts/launch.md,https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/posts/launch.md,,Launch article,,,,2026,GitHub,GitHub,,,,repository,,,,,,,,,,,2026-07-18T08:16:45+00:00
 ale-0578,Discussion guide,meta/DISCUSSIONS.md,local_path,,local_ok,,https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/meta/DISCUSSIONS.md,https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/meta/DISCUSSIONS.md,,Discussion guide,,,,2026,GitHub,GitHub,,,,repository,,,,,,,,,,,2026-07-18T08:16:45+00:00
-ale-0579,Show your Loop Engineering patterns,https://github.com/ChaoYue0307/awesome-loop-engineering/discussions/2,external,github.com,ok,200,https://github.com/ChaoYue0307/awesome-loop-engineering/discussions/2,https://github.com/ChaoYue0307/awesome-loop-engineering/discussions/2,text/html; charset=utf-8,Show your Loop Engineering patterns · ChaoYue0307/awesome-loop-engineering · Discussion #2 · GitHub,Show your Loop Engineering patterns,,2026-06-09,2026,GitHub Discussions,GitHub,,,,github-api,ChaoYue0307/awesome-loop-engineering,31,6,9,"🔁 555 source-audited resources · 20 operational patterns · 20 validated contracts · 8 runtime starters · interactive atlas + dataset for recurring, stateful, verified AI-agent systems.",CC0-1.0,2026-06-09T16:17:27Z,2026-07-18T07:38:30Z,,,2026-07-18T08:16:45+00:00
+ale-0579,Show your Loop Engineering patterns,https://github.com/ChaoYue0307/awesome-loop-engineering/discussions/2,external,github.com,ok,200,https://github.com/ChaoYue0307/awesome-loop-engineering/discussions/2,https://github.com/ChaoYue0307/awesome-loop-engineering/discussions/2,text/html; charset=utf-8,Show your Loop Engineering patterns · ChaoYue0307/awesome-loop-engineering · Discussion #2 · GitHub,Show your Loop Engineering patterns,,2026-06-09,2026,GitHub Discussions,GitHub,,,,github-api,ChaoYue0307/awesome-loop-engineering,31,6,9,"🔁 Explore 579 resources from model recurrence to governed agent operations · Build with 20 patterns, 20 contracts, and 8 runtime starters · Atlas + dataset.",CC0-1.0,2026-06-09T16:17:27Z,2026-07-18T07:38:30Z,,,2026-07-18T08:16:45+00:00

data/resources.parquet

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:d54b0458ecbf0a9c8ddc1c56d731c4111a04e8633a1c9e8f9b7ea1e70fce97ca
-size 466752
+oid sha256:001e145eeaa0637b293573dcf1be692cbc8d8ef672796177ecb7f08e0735e4ab
+size 466679

design-qa.md

@@ -38,7 +38,7 @@
 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.
 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.
 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.
-11. Expanded the implementation kit to 20 patterns, 20 validated 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.
+11. Expanded the implementation kit to 20 patterns, 20 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.
 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.
 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.
 

docs/index.html

@@ -4,7 +4,7 @@
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1">
     <title>Awesome Loop Engineering</title>
-    <meta name="description" content="579 source-audited resources across model, agent, harness, workflow, and operations layers, plus 20 patterns, 20 contracts, and 8 runtime starters.">
+    <meta name="description" content="Explore 579 resources from model recurrence to governed agent operations, then build with 20 patterns, 20 contracts, and 8 runtime starters.">
     <meta name="robots" content="index,follow">
     <meta name="author" content="Chaoyue He">
     <link rel="canonical" href="https://chaoyue0307.github.io/awesome-loop-engineering/">
@@ -15,7 +15,7 @@
     <link href="https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@500;600&amp;family=Inter:wght@400;500;600;700;800&amp;display=swap" rel="stylesheet">
     <meta property="og:type" content="website">
     <meta property="og:title" content="Awesome Loop Engineering">
-    <meta property="og:description" content="579 source-audited resources across the model-to-operations stack, plus 20 patterns, 20 validated contracts, and 8 runtime starters.">
+    <meta property="og:description" content="Explore 579 papers, docs, tools, benchmarks, and guides, then build recurring agent systems with 20 patterns, 20 contracts, and 8 starters.">
     <meta property="og:url" content="https://chaoyue0307.github.io/awesome-loop-engineering/">
     <meta property="og:image" content="https://chaoyue0307.github.io/awesome-loop-engineering/assets/social-preview-579-v08.png">
     <meta property="og:image:width" content="1280">
@@ -23,7 +23,7 @@
     <meta property="og:image:alt" content="Awesome Loop Engineering: design loops, not just prompts.">
     <meta name="twitter:card" content="summary_large_image">
     <meta name="twitter:title" content="Awesome Loop Engineering">
-    <meta name="twitter:description" content="579 source-audited resources across the model-to-operations stack, plus a practical kit for recurring AI-agent systems.">
+    <meta name="twitter:description" content="579 resources from model recurrence to agent operations, plus 20 patterns, 20 contracts, and 8 starters for building reliable loops.">
     <meta name="twitter:image" content="https://chaoyue0307.github.io/awesome-loop-engineering/assets/social-preview-579-v08.png">
     <link rel="alternate" type="application/atom+xml" title="Awesome Loop Engineering releases" href="https://github.com/ChaoYue0307/awesome-loop-engineering/releases.atom">
     <link rel="alternate" type="application/atom+xml" title="Awesome Loop Engineering commits" href="https://github.com/ChaoYue0307/awesome-loop-engineering/commits/main.atom">
@@ -158,12 +158,12 @@
 
       main { overflow: hidden; }
       section { padding: 86px 0; border-top: 1px solid var(--line); }
-      .hero { position: relative; isolation: isolate; min-height: 0; overflow: hidden; padding: 64px 0 20px; border-top: 0; text-align: center; }
+      .hero { position: relative; isolation: isolate; min-height: 0; overflow: hidden; padding: 52px 0 16px; border-top: 0; text-align: center; }
       .hero .wrap { position: relative; z-index: 1; }
       .hero-copy { position: relative; z-index: 2; }
       .hero-system {
         width: min(100%, 1120px);
-        margin: 34px auto 0;
+        margin: 28px auto 0;
         border-top: 1px solid var(--line-strong);
         border-bottom: 1px solid var(--line-strong);
         background: var(--surface);
@@ -190,7 +190,7 @@
         z-index: 0;
         min-width: 0;
         width: 100%;
-        height: 324px;
+        height: 300px;
         overflow: hidden;
         background: #f4f7fc;
         pointer-events: none;
@@ -204,7 +204,7 @@
         align-items: center;
         justify-content: center;
         gap: 26px;
-        min-height: 38px;
+        min-height: 34px;
         border-top: 1px solid var(--line);
         color: var(--muted);
         font-size: 0.68rem;
@@ -226,7 +226,7 @@
         align-items: center;
         justify-content: center;
         gap: 26px;
-        min-height: 38px;
+        min-height: 34px;
         border-top: 1px solid var(--line);
         color: var(--muted);
         font-size: 0.7rem;
@@ -243,7 +243,7 @@
         align-items: center;
         min-width: 0;
         border-top: 1px solid var(--line);
-        padding: 14px 0;
+        padding: 12px 0;
       }
       .mental-model { padding: 18px 0 52px; }
       .section-label {
@@ -980,34 +980,34 @@
         .contract-example-head { padding: 18px 0; }
         .contract-example-row { grid-template-columns: 1fr; gap: 5px; padding: 13px 0; }
         .contract-example-result { align-items: flex-start; flex-direction: column; gap: 9px; padding: 15px 0; }
-        .hero { min-height: 0; padding: 32px 0 18px; }
+        .hero { min-height: 0; padding: 20px 0 6px; }
         .hero-kicker { max-width: 100%; align-items: center; margin: 0 auto 10px; line-height: 1.35; text-align: left; }
         .tagline { margin-top: 11px; font-size: 1.18rem; }
-        .lead { margin-top: 8px; font-size: 0.95rem; line-height: 1.48; }
-        .actions { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); width: 100%; max-width: 420px; gap: 8px; margin: 16px auto 0; }
+        .lead { margin-top: 6px; font-size: 0.95rem; line-height: 1.48; }
+        .actions { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); width: 100%; max-width: 420px; gap: 8px; margin: 12px auto 0; }
         .actions .button { min-width: 0; min-height: 44px; padding-inline: 8px; font-size: 0.82rem; }
         .actions .button .icon { width: 16px; height: 16px; }
-        .hero-system { display: flex; flex-direction: column; margin-top: 20px; }
-        .scene-head { order: 1; justify-content: center; min-height: 34px; padding: 6px 0; }
+        .hero-system { display: flex; flex-direction: column; margin-top: 8px; }
+        .scene-head { order: 1; justify-content: center; min-height: 24px; padding: 2px 0; }
         .scene-flow { display: none; }
-        .hero-scene { order: 2; width: 100%; height: 258px; }
+        .hero-scene { order: 2; width: 100%; height: 208px; }
         .hero-scene canvas { opacity: 1; }
-        .scene-key { order: 4; display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); gap: 0; min-height: 68px; padding: 0; font-size: 0.67rem; }
+        .scene-key { display: none; }
         .scene-key-item { justify-content: flex-start; min-width: 0; min-height: 34px; padding: 7px 8px; }
         .scene-key-item:nth-child(even) { border-left: 1px solid var(--line); }
         .scene-key-item:nth-child(n+3) { border-top: 1px solid var(--line); }
         .scene-key-item::before { width: 13px; flex: 0 0 auto; }
-        .scene-outcomes { order: 5; display: grid; grid-template-columns: repeat(3, minmax(0, 1fr)); gap: 0; min-height: 46px; padding: 0; font-size: 0.64rem; line-height: 1.3; }
+        .scene-outcomes { order: 5; display: grid; grid-template-columns: repeat(3, minmax(0, 1fr)); gap: 0; min-height: 34px; padding: 0; font-size: 0.62rem; line-height: 1.3; }
         .scene-outcome { justify-content: flex-start; gap: 5px; min-width: 0; padding: 8px 6px; }
         .scene-outcome + .scene-outcome { border-left: 1px solid var(--line); }
         .scene-outcome::before { width: 6px; height: 6px; flex: 0 0 auto; }
-        .hero-inspector { order: 3; gap: 8px; padding: 0 0 10px; }
+        .hero-inspector { order: 3; gap: 8px; padding: 0 0 6px; }
         .loop-stage-rail { margin-top: 20px; }
         .hero-system .loop-stage-rail { margin: 0; }
         .loop-stage { min-height: 44px; padding-inline: 6px; font-size: 0.71rem; }
         .loop-stage-number { font-size: 0.61rem; }
         .loop-stage-detail { min-height: 40px; margin-top: 8px; font-size: 0.75rem; line-height: 1.45; }
-        .hero-inspector .loop-stage-detail { min-height: 48px; margin: 0; padding: 8px 8px 0 12px; line-height: 1.42; }
+        .hero-inspector .loop-stage-detail { min-height: 36px; margin: 0; padding: 4px 8px 0 12px; line-height: 1.42; }
         .mental-model { padding: 30px 0 46px; }
         .definition { margin-bottom: 18px; font-size: 0.88rem; line-height: 1.55; text-align: left; }
         .definition-full { display: none; }
@@ -1236,7 +1236,7 @@
         "@type": "CollectionPage",
         "name": "Awesome Loop Engineering",
         "url": "https://chaoyue0307.github.io/awesome-loop-engineering/",
-        "description": "A source-audited field guide and implementation kit for recurring, stateful, verified AI-agent systems.",
+        "description": "A practical field guide and implementation kit for recurring, stateful, verified AI-agent systems.",
         "keywords": ["Loop Engineering", "AI agents", "Coding agents", "Agent workflows", "Agentic loops"],
         "datePublished": "2026-06-10",
         "dateModified": "2026-07-18",
@@ -1293,7 +1293,7 @@
         "@context": "https://schema.org",
         "@type": "Dataset",
         "name": "Awesome Loop Engineering resources",
-        "description": "579 source-audited resources across model, agent, harness, workflow, operations, and evaluation layers, with explicit scope, contribution, novelty, impact, and evidence fields.",
+        "description": "Explore 579 resources across model, agent, harness, workflow, operations, and evaluation layers, with publication, contribution, novelty, impact, and evidence fields.",
         "url": "https://chaoyue0307.github.io/awesome-loop-engineering/",
         "sameAs": [
           "https://huggingface.co/datasets/cy0307/awesome-loop-engineering",
@@ -1368,7 +1368,7 @@
             <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>
             <h1>Awesome Loop Engineering</h1>
             <p class="tagline">Design loops, not just prompts.</p>
-            <p class="lead">579 source-audited resources from model recurrence to production operations, plus 20 patterns, 20 validated contracts, and 8 runtime starters for agent systems that must keep working.</p>
+            <p class="lead">Explore 579 resources from model recurrence to agent operations, then build with 20 patterns, 20 adaptable contracts, and 8 runtime starters.</p>
             <div class="actions">
               <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>
               <a class="button" href="#choose"><i class="icon" data-lucide="compass" aria-hidden="true"></i>Choose a loop</a>
@@ -1425,7 +1425,7 @@
             </div>
           </figure>
           <div class="stats" role="list" aria-label="Field guide at a glance">
-            <div class="stat" role="listitem"><b><i class="icon" data-lucide="library" aria-hidden="true"></i>579</b><span>audited resources</span></div>
+            <div class="stat" role="listitem"><b><i class="icon" data-lucide="library" aria-hidden="true"></i>579</b><span>resources</span></div>
             <div class="stat" role="listitem"><b><i class="icon" data-lucide="blocks" aria-hidden="true"></i>20</b><span>operational patterns</span></div>
             <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>
             <div class="stat" role="listitem"><b><i class="icon" data-lucide="play" aria-hidden="true"></i>8</b><span>runtime starters</span></div>
@@ -1601,7 +1601,7 @@
             <div class="choice-step"><span class="number">03</span><strong>Bound action</strong><p>Set readable and writable scope, non-goals, retries, time, and cost.</p></div>
             <div class="choice-step"><span class="number">04</span><strong>Plan the next pass</strong><p>Decide what persists, retries, escalates, or exits after each result.</p></div>
           </div>
-          <p class="choice-sequence"><strong>Pattern → contract → runtime.</strong> Select the operating model below, adapt its validated contract to your environment, then choose where it runs based on persistence, isolation, and permissions.</p>
+          <p class="choice-sequence"><strong>Pattern → contract → runtime.</strong> Select the operating model below, adapt its schema-checked contract to your environment, then choose where it runs based on persistence, isolation, and permissions.</p>
           <div class="filter-row">
             <input type="search" id="pattern-filter" class="pattern-filter" placeholder="Filter patterns by keyword..." aria-label="Filter patterns by keyword" autocomplete="off">
             <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/patterns/MATRIX.md">Compare every contract field →</a>
@@ -1725,9 +1725,9 @@
               <p class="section-label"><i class="icon" data-lucide="library" aria-hidden="true"></i><span>06 / Resource atlas</span></p>
               <h2>Find evidence, not just links.</h2>
             </div>
-            <p class="section-intro">Filter 579 source-audited works by goal, loop layer, lifecycle, artifact type, and evidence class. Open any result for contribution, novelty, impact, scope, provenance, and source metadata.</p>
+            <p class="section-intro">Filter 579 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>
           </div>
-          <p class="audit-note"><strong>Audit snapshot, 2026-07-18 UTC:</strong> all 579 rows checked; 528 public sources reachable, 3 access-restricted, 48 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>
+          <p class="audit-note"><strong>Last source check, 2026-07-18 UTC:</strong> 528 public links opened successfully, 3 required access, 48 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>
           <div class="loop-layer-map" aria-label="Where different loop concepts live">
             <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>
             <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>
@@ -1751,7 +1751,7 @@
                   <option value="Template">Templates</option>
                   <option value="Blog">Practitioner writing</option>
                   <option value="Critique">Critiques</option>
-                  <option value="List">Curated lists</option>
+                  <option value="List">Related lists</option>
                 </select>
               </label>
               <label>
@@ -1815,7 +1815,7 @@
               <label>
                 <span class="sr-only">Sort resources</span>
                 <select class="resource-select resource-sort" id="resource-sort">
-                  <option value="curated">Curated order</option>
+                  <option value="curated">Guide order</option>
                   <option value="publication">Publication year</option>
                   <option value="stars">GitHub stars</option>
                   <option value="recent">Recently added</option>
@@ -1829,7 +1829,7 @@
               <span>Evidence</span>
             </div>
             <div class="resource-list" id="resource-list" aria-busy="false">
-              <p class="resource-loading">Preparing the audited resource index...</p>
+              <p class="resource-loading">Preparing the resource index...</p>
             </div>
             <p class="resource-empty" id="resource-empty" hidden>No resources match the current filters.</p>
             <div class="resource-actions">
@@ -1901,11 +1901,11 @@
               <p class="section-label"><i class="icon" data-lucide="handshake" aria-hidden="true"></i><span>08 / Contribute</span></p>
               <h2>Improve the evidence or share a loop.</h2>
             </div>
-            <p class="section-intro">Submit one canonical source, correct an existing record with primary evidence, or document a loop you have run.</p>
+            <p class="section-intro">Share an original or official source, correct an entry with primary evidence, or document a loop you have run.</p>
           </div>
           <div class="link-grid contribute-grid">
-            <a class="card" href="https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=resource-suggestion.yml"><h3><i class="icon" data-lucide="plus" aria-hidden="true"></i>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><i class="icon" data-lucide="badge-check" aria-hidden="true"></i>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/issues/new?template=resource-suggestion.yml"><h3><i class="icon" data-lucide="plus" aria-hidden="true"></i>Suggest a resource</h3><p>Share one original or official source and a precise summary in under five minutes.</p></a>
+            <a class="card" href="https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=annotation-correction.yml"><h3><i class="icon" data-lucide="badge-check" aria-hidden="true"></i>Correct an entry</h3><p>Fix a summary, contribution, date, venue, identifier, or source link with primary evidence.</p></a>
             <a class="card" href="https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/gallery/README.md"><h3><i class="icon" data-lucide="repeat-2" aria-hidden="true"></i>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><i class="icon" data-lucide="messages-square" aria-hidden="true"></i>Join the discussion</h3><p>Compare operating patterns with other loop builders.</p></a>
           </div>
@@ -1967,13 +1967,13 @@
           </div>
           <div>
             <h4><i class="icon" data-lucide="compass" aria-hidden="true"></i>Explore</h4>
-            <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/DEFINITION.md">Canonical definition</a>
+            <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/DEFINITION.md">Working definition</a>
             <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/FUTURE-DIRECTIONS.md">Future directions</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>
+            <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/meta/CURATION.md">How resources are chosen</a>
+            <a href="https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/data/resource_source_audit.csv">Source check</a>
           </div>
           <div>
             <h4><i class="icon" data-lucide="wrench" aria-hidden="true"></i>Project</h4>
@@ -2117,12 +2117,12 @@
             'source-implementation': 'Source implementation',
             'implementation': 'Implementation',
             'benchmark': 'Benchmark or evaluation',
-            'repository-native': 'Validated project artifact',
+            'repository-native': 'Project artifact',
             'reusable-artifact': 'Reusable artifact',
             'operational-pattern': 'Operational pattern',
             'practitioner-analysis': 'Practitioner analysis',
             'risk-analysis': 'Risk analysis',
-            'curated-index': 'Curated index'
+            'curated-index': 'Discovery index'
           };
           return labels[value] || words(value);
         }
@@ -2168,9 +2168,9 @@
 
         function sourceStatus(resource) {
           if (resource.source_status === 'restricted') return 'Access restricted';
-          if (['broken', 'unreachable', 'local_missing'].indexOf(resource.source_status) !== -1) return 'Audit issue';
-          if (String(resource.source_status || '').indexOf('local') === 0) return 'Repository source';
-          return 'Source checked';
+          if (['broken', 'unreachable', 'local_missing'].indexOf(resource.source_status) !== -1) return 'Source unavailable';
+          if (String(resource.source_status || '').indexOf('local') === 0) return 'Repository file';
+          return 'Link checked';
         }
 
         function detailSection(title, values) {
@@ -2394,8 +2394,8 @@
           loading = true;
           explorer.dataset.indexState = 'loading';
           list.setAttribute('aria-busy', 'true');
-          count.textContent = 'Loading 579 audited resources...';
-          list.replaceChildren(createText('p', 'resource-loading', 'Loading audited resources...'));
+          count.textContent = 'Loading 579 resources...';
+          list.replaceChildren(createText('p', 'resource-loading', 'Loading resources...'));
 
           fetch('assets/resources.json')
             .then(function (response) {

docs/llms.txt

@@ -1,11 +1,11 @@
 # Awesome Loop Engineering
 
-> Curated resources and practical patterns for Loop Engineering: the practice of designing recurring AI-agent and coding-agent systems that discover work, delegate to agents, verify results, persist state, and run again on a cadence or until a verifiable goal is reached.
+> Practical resources and reusable patterns for Loop Engineering: the practice of designing recurring AI-agent and coding-agent systems that discover work, delegate to agents, verify results, persist state, and run again on a cadence or until a verifiable goal is reached.
 
 ## Core
 
-- [README](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md): the curated list with the Loop Contract, design checklist, and maturity model
-- [Canonical definition](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/DEFINITION.md): short definition, positioning, and minimal loop test
+- [README](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md): the full resource guide with the Loop Contract, design checklist, and maturity model
+- [Working definition](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/DEFINITION.md): short definition, positioning, and minimal loop test
 - [Taxonomy](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/TAXONOMY.md): classification by trigger, intake, verification, state model, and topology
 - [Anti-patterns](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/ANTI-PATTERNS.md): common loop failure modes
 
@@ -13,15 +13,15 @@
 
 - [Pattern library](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/patterns/README.md): operational loop patterns with triggers, gates, budgets, and escalation
 - [Pattern matrix](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/patterns/MATRIX.md): every pattern compared by trigger, gate, state, and budget, indexed by symptom
-- [Loop contracts](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/examples/README.md): schema-validated contract JSON for every pattern, plus runnable reference loops
+- [Loop contracts](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/examples/README.md): schema-checked contract JSON for every pattern, plus runnable reference loops
 - [Runtime selection guide](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/meta/RUNTIME_SELECTION.md): choosing where a loop runs by persistence, file access, isolation, and permissions
 
 ## Data
 
-- [Resource sheet (CSV)](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/data/resources.csv): all curated entries with section, type, and annotation columns
+- [Resource sheet (CSV)](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/data/resources.csv): all entries with section, type, and summary columns
 - [Resource sheet (JSONL)](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/data/resources.jsonl): the same rows as line-delimited JSON
-- [Hugging Face dataset](https://huggingface.co/datasets/cy0307/awesome-loop-engineering): mirrored dataset with a data viewer over all curated entries
-- [Source audit](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/data/resource_source_audit.csv): per-entry reachability, HTTP status, and repository metadata
+- [Hugging Face dataset](https://huggingface.co/datasets/cy0307/awesome-loop-engineering): mirrored dataset with a data viewer over all entries
+- [Source check](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/data/resource_source_audit.csv): per-entry link status, HTTP response, and repository metadata
 
 ## Optional
 

docs/x-v07-545.html

@@ -3,23 +3,23 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1">
-    <title>Awesome Loop Engineering: 545 source-audited resources</title>
-    <meta name="description" content="A source-audited field guide with 545 resources, 20 operational patterns, 20 validated contracts, and 8 runtime starters for recurring AI-agent systems.">
+    <title>Awesome Loop Engineering: 545 resources and a practical implementation kit</title>
+    <meta name="description" content="Explore 545 resources, then build recurring AI-agent systems with 20 operational patterns, 20 contracts, and 8 runtime starters.">
     <meta name="robots" content="noindex,follow">
     <link rel="canonical" href="https://chaoyue0307.github.io/awesome-loop-engineering/x-v07-545.html">
     <meta property="og:type" content="website">
     <meta property="og:title" content="Awesome Loop Engineering">
-    <meta property="og:description" content="545 source-audited resources, 20 operational patterns, 20 validated contracts, and 8 runtime starters for recurring AI-agent systems.">
+    <meta property="og:description" content="545 resources, 20 operational patterns, 20 contracts, and 8 runtime starters for recurring AI-agent systems.">
     <meta property="og:url" content="https://chaoyue0307.github.io/awesome-loop-engineering/x-v07-545.html">
     <meta property="og:image" content="https://chaoyue0307.github.io/awesome-loop-engineering/assets/social-preview-545-v07.png">
     <meta property="og:image:width" content="1280">
     <meta property="og:image:height" content="640">
-    <meta property="og:image:alt" content="Awesome Loop Engineering: design loops, not just prompts. 545 source-audited resources, 20 patterns, 20 contracts, and 8 runtime starters.">
+    <meta property="og:image:alt" content="Awesome Loop Engineering: design loops, not just prompts. 545 resources, 20 patterns, 20 contracts, and 8 runtime starters.">
     <meta name="twitter:card" content="summary_large_image">
     <meta name="twitter:title" content="Awesome Loop Engineering">
-    <meta name="twitter:description" content="545 source-audited resources and a 20-pattern implementation kit for recurring, stateful, verified AI-agent systems.">
+    <meta name="twitter:description" content="545 resources and a 20-pattern implementation kit for recurring, stateful, verified AI-agent systems.">
     <meta name="twitter:image" content="https://chaoyue0307.github.io/awesome-loop-engineering/assets/social-preview-545-v07.png">
-    <meta name="twitter:image:alt" content="Awesome Loop Engineering: 545 source-audited resources, 20 patterns, 20 contracts, and 8 runtime starters.">
+    <meta name="twitter:image:alt" content="Awesome Loop Engineering: 545 resources, 20 patterns, 20 contracts, and 8 runtime starters.">
     <link rel="icon" href="assets/favicon-32.png" type="image/png" sizes="32x32">
     <style>
       :root { color-scheme: light; font-family: Inter, ui-sans-serif, system-ui, sans-serif; }

docs/x-v07-555.html

@@ -3,23 +3,23 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1">
-    <title>Awesome Loop Engineering: 555 source-audited resources</title>
-    <meta name="description" content="A source-audited field guide with 555 resources, 20 operational patterns, 20 validated contracts, and 8 runtime starters for recurring AI-agent systems.">
+    <title>Awesome Loop Engineering: 555 resources and a practical implementation kit</title>
+    <meta name="description" content="Explore 555 resources, then build recurring AI-agent systems with 20 operational patterns, 20 contracts, and 8 runtime starters.">
     <meta name="robots" content="noindex,follow">
     <link rel="canonical" href="https://chaoyue0307.github.io/awesome-loop-engineering/x-v07-555.html">
     <meta property="og:type" content="website">
     <meta property="og:title" content="Awesome Loop Engineering">
-    <meta property="og:description" content="555 source-audited resources, 20 operational patterns, 20 validated contracts, and 8 runtime starters for recurring AI-agent systems.">
+    <meta property="og:description" content="555 resources, 20 operational patterns, 20 contracts, and 8 runtime starters for recurring AI-agent systems.">
     <meta property="og:url" content="https://chaoyue0307.github.io/awesome-loop-engineering/x-v07-555.html">
     <meta property="og:image" content="https://chaoyue0307.github.io/awesome-loop-engineering/assets/social-preview-555-v07.png">
     <meta property="og:image:width" content="1280">
     <meta property="og:image:height" content="640">
-    <meta property="og:image:alt" content="Awesome Loop Engineering: design loops, not just prompts. 555 source-audited resources, 20 patterns, 20 contracts, and 8 runtime starters.">
+    <meta property="og:image:alt" content="Awesome Loop Engineering: design loops, not just prompts. 555 resources, 20 patterns, 20 contracts, and 8 runtime starters.">
     <meta name="twitter:card" content="summary_large_image">
     <meta name="twitter:title" content="Awesome Loop Engineering">
-    <meta name="twitter:description" content="555 source-audited resources and a 20-pattern implementation kit for recurring, stateful, verified AI-agent systems.">
+    <meta name="twitter:description" content="555 resources and a 20-pattern implementation kit for recurring, stateful, verified AI-agent systems.">
     <meta name="twitter:image" content="https://chaoyue0307.github.io/awesome-loop-engineering/assets/social-preview-555-v07.png">
-    <meta name="twitter:image:alt" content="Awesome Loop Engineering: 555 source-audited resources, 20 patterns, 20 contracts, and 8 runtime starters.">
+    <meta name="twitter:image:alt" content="Awesome Loop Engineering: 555 resources, 20 patterns, 20 contracts, and 8 runtime starters.">
     <link rel="icon" href="assets/favicon-32.png" type="image/png" sizes="32x32">
     <style>
       :root { color-scheme: light; font-family: Inter, ui-sans-serif, system-ui, sans-serif; }

docs/x-v08-579.html

@@ -3,23 +3,23 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1">
-    <title>Awesome Loop Engineering: 579 source-audited resources</title>
-    <meta name="description" content="A source-audited field guide spanning model recurrence, agent execution, and operations, with 20 patterns, 20 contracts, and 8 runtime starters.">
+    <title>Awesome Loop Engineering: 579 resources and a practical implementation kit</title>
+    <meta name="description" content="Explore model recurrence, agent execution, and operations, then build with 20 patterns, 20 contracts, and 8 runtime starters.">
     <meta name="robots" content="noindex,follow">
     <link rel="canonical" href="https://chaoyue0307.github.io/awesome-loop-engineering/x-v08-579.html">
     <meta property="og:type" content="website">
     <meta property="og:title" content="Awesome Loop Engineering">
-    <meta property="og:description" content="579 source-audited resources across the model-to-operations stack, plus a practical implementation kit for recurring AI-agent systems.">
+    <meta property="og:description" content="Explore 579 papers, docs, tools, benchmarks, and guides, then build recurring AI-agent systems with 20 patterns, 20 contracts, and 8 starters.">
     <meta property="og:url" content="https://chaoyue0307.github.io/awesome-loop-engineering/x-v08-579.html">
     <meta property="og:image" content="https://chaoyue0307.github.io/awesome-loop-engineering/assets/social-preview-579-v08.png">
     <meta property="og:image:width" content="1280">
     <meta property="og:image:height" content="640">
-    <meta property="og:image:alt" content="Awesome Loop Engineering: design loops, not just prompts. 579 source-audited resources, 20 patterns, 20 contracts, and 8 runtime starters.">
+    <meta property="og:image:alt" content="Awesome Loop Engineering: design loops, not just prompts. 579 resources, 20 patterns, 20 contracts, and 8 runtime starters.">
     <meta name="twitter:card" content="summary_large_image">
     <meta name="twitter:title" content="Awesome Loop Engineering">
-    <meta name="twitter:description" content="579 source-audited resources across model, agent, harness, workflow, operations, and evaluation layers.">
+    <meta name="twitter:description" content="579 resources across model, agent, harness, workflow, operations, and evaluation layers.">
     <meta name="twitter:image" content="https://chaoyue0307.github.io/awesome-loop-engineering/assets/social-preview-579-v08.png">
-    <meta name="twitter:image:alt" content="Awesome Loop Engineering: 579 source-audited resources, 20 patterns, 20 contracts, and 8 runtime starters.">
+    <meta name="twitter:image:alt" content="Awesome Loop Engineering: 579 resources, 20 patterns, 20 contracts, and 8 runtime starters.">
     <link rel="icon" href="assets/favicon-32.png" type="image/png" sizes="32x32">
     <style>
       :root { color-scheme: light; font-family: Inter, ui-sans-serif, system-ui, sans-serif; }

examples/README.md

@@ -1,4 +1,4 @@
-# Validated Loop Contracts
+# Schema-Checked Loop Contracts
 
 Twenty JSON examples turn the operational patterns into reviewable machine-readable contracts. Every file validates against [`schemas/loop-contract.schema.json`](../schemas/loop-contract.schema.json) in CI.
 

meta/CURATION.md

@@ -1,4 +1,4 @@
-# Curation Standard
+# Resource Selection Guide
 
 Include only recurring AI-agent and coding-agent systems with explicit triggers, verification, durable state, budgets, escalation, and exit. General agent links belong elsewhere.
 
@@ -38,23 +38,23 @@ Usually reject resources that are mostly:
 | --- | --- | --- |
 | A | Primary or official source | Paper, official docs, project README, author write-up |
 | B | Practitioner source with implementation detail | Field note, runbook, postmortem, architecture note |
-| C | Curated survey or high-quality explainer | Taxonomy, comparison, tutorial |
+| C | Synthesis or high-quality explainer | Taxonomy, comparison, tutorial |
 | D | Commentary or news coverage | Useful only for origin, adoption, quotes, or debate |
 
 Prefer the highest-tier source that explains the same idea clearly.
 
-## Editorial Responsibility And Assistance
+## How Summaries And Metadata Are Built
 
-The maintainer owns every released inclusion decision, category, annotation, and project-level claim. Automation may assist discovery, URL resolution, duplicate detection, bibliographic extraction, repository statistics, and draft normalization. Automated output is not evidence; canonical sources, primary metadata, and stated limitations control the final entry.
+Every released entry links to evidence that readers can inspect and exposes its category, summary, and source details for correction. Automation may assist discovery, URL resolution, duplicate detection, bibliographic extraction, repository statistics, and draft normalization. Automated output is not evidence; original or official sources, primary metadata, and stated limitations control the final entry.
 
 The public dataset keeps those layers separate:
 
-- `annotation`, `key_contribution`, `novelty`, and `impact` are original editorial syntheses;
-- `source_title`, `source_description`, authorship, date, venue, DOI, and repository statistics come from the source audit and record their metadata provenance;
-- `evidence_tier` records whether the row is a primary source, implementation-grounded practitioner source, or curated synthesis;
+- `annotation`, `key_contribution`, `novelty`, and `impact` are original summaries;
+- `source_title`, `source_description`, authorship, date, venue, DOI, and repository statistics come from the source check and record where the metadata came from;
+- `evidence_tier` records whether the row is a primary source, implementation-grounded practitioner source, or synthesis and discovery index;
 - `loop_layer` records whether recurrence lives inside the model, agent, harness, workflow, operations, evaluation, or spans layers;
 - `scope_fit` records whether a resource directly describes operational Loop Engineering, enables it, or is an explicitly adjacent foundation;
-- `signal_strength` describes the kind of evidence available, not whether the maintainer agrees with the work;
+- `signal_strength` describes the kind of evidence available, not whether the work is recommended or scientifically valid;
 - `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.
@@ -71,9 +71,9 @@ When evidence conflicts:
 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
+## Source Checks 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.
+`data/resource_source_audit.csv` records a point-in-time source check. `data/resources.csv` and `data/resources.jsonl` are deterministic exports of the full English guide enriched with those results. GitHub Releases identify versioned snapshots; downstream users should cite a release or commit when reproducibility matters.
 
 ## Annotation Rules
 
@@ -124,4 +124,4 @@ Pattern entries should be concrete enough to adapt to a real agent runtime. A go
 
 ## License Scope
 
-Only original repository curation text, annotations, templates, pattern documents, and metadata are released under `CC0-1.0`. Linked third-party resources keep their own licenses and terms.
+Only original repository summaries, templates, pattern documents, and metadata are released under `CC0-1.0`. Linked third-party resources keep their own licenses and terms.

meta/DISTRIBUTION.md

@@ -32,8 +32,8 @@ Search engines may still take days or longer to index a new repository. Backlink
 The Hugging Face dataset [`datasets/cy0307/awesome-loop-engineering`](https://huggingface.co/datasets/cy0307/awesome-loop-engineering) exposes the collection to AI/ML users and tabular workflows. Sync it after each GitHub release or data change.
 
 - 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` 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 579-row GitHub README.
+- The dataset mirror includes generated resource sheets at `data/resources.csv` and `data/resources.jsonl`, refreshed from the full English `README.md` by `scripts/export_resource_dataset.py`.
+- 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, evidence fields, limitations, loading examples, and the latest link status without duplicating the 579-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.
 
@@ -46,11 +46,11 @@ Use GitHub-native discovery in this order.
 - **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
-  - [Awesome Loop Engineering](https://github.com/ChaoYue0307/awesome-loop-engineering#readme) - Source-audited resources, reusable patterns, validated contracts, and runtime starters for recurring AI-agent systems.
+  - [Awesome Loop Engineering](https://github.com/ChaoYue0307/awesome-loop-engineering#readme) - Practical resources, reusable patterns, adaptable contracts, and runtime starters for recurring AI-agent systems.
   ```
 
 - **Pin the repository** on your profile, and add it to your profile README (profile-level promotion).
-- **About description.** Keep this concise proof-point copy aligned with the README and project site: `🔁 579 source-audited resources across model, agent, harness, workflow, operations, and evaluation layers · 20 patterns · 20 contracts · 8 runtime starters.`
+- **About description.** Keep this concise value statement aligned with the README and project site: `🔁 Explore 579 resources from model recurrence to governed agent operations · Build with 20 patterns, 20 contracts, and 8 runtime starters · Atlas + dataset.`
 - **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.
 - **Releases and Discussions** provide a lower-noise subscription path. Recommend `Watch -> Custom -> Releases and Discussions`; do not ask readers to watch every repository event.
 
@@ -86,12 +86,12 @@ Treat these as measurement targets, not promises. Log the publication date and c
 
 ## Launch Copy
 
-Use the canonical [English launch article](../posts/launch.md) or [Chinese launch article](../posts/launch.zh-CN.md) for long-form distribution.
+Use the [English launch article](../posts/launch.md) or [Chinese launch article](../posts/launch.zh-CN.md) for long-form distribution.
 
 ### Short Post
 
 ```text
-🔁 Awesome Loop Engineering v0.8.0 is live: 579 source-audited resources across the model-to-operations stack, plus 20 patterns, 20 contracts, and 8 runtime starters.
+🔁 Awesome Loop Engineering v0.8.0 is live: explore 579 resources from model recurrence to agent operations, then build with 20 patterns, 20 contracts, and 8 runtime starters.
 
 🧭 Explore the layers:
 https://chaoyue0307.github.io/awesome-loop-engineering/x-v08-579.html
@@ -108,13 +108,13 @@ Awesome Loop Engineering v0.8.0 is live.
 
 The release includes:
 
-- 579 source-audited resources
+- 579 papers, docs, tools, benchmarks, and guides
 - 23 selected model-recurrence papers labeled as adjacent foundations
 - an interactive Resource Atlas
-- 20 operational patterns and 20 validated loop contracts
+- 20 operational patterns and 20 adaptable loop contracts
 - 8 runtime starters: 3 executables and 5 copy/paste templates
 - 50-field CSV, JSONL, and Parquet exports mirrored to Hugging Face
-- a public provenance standard and point-in-time source audit
+- source and evidence fields, with point-in-time link-check results
 
 Explore, reuse, or correct the map:
 https://github.com/ChaoYue0307/awesome-loop-engineering
@@ -129,7 +129,7 @@ Title: Awesome Loop Engineering: 579 resources from looped models to agent opera
 
 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.
 
-The repository includes 579 source-audited works across model, agent, harness, workflow, operations, and evaluation layers; 20 operational patterns; 20 validated contracts; 8 runtime starters; an interactive Resource Atlas; and a structured Hugging Face dataset. Model-level recurrence is explicitly labeled as an adjacent foundation rather than a complete operational loop. The curation and audit methods are public; corrections to the taxonomy and annotations are especially welcome.
+The repository connects 579 papers, docs, tools, benchmarks, and guides across model, agent, harness, workflow, operations, and evaluation layers with 20 operational patterns, 20 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.
 
 https://github.com/ChaoYue0307/awesome-loop-engineering
 ```
@@ -147,11 +147,11 @@ Do not ask anyone to upvote the submission.
 
 ## Where To Share
 
-- X/Twitter thread with the cover image and canonical definition.
+- X/Twitter thread with the cover image and working definition.
 - LinkedIn post focused on the prompt/context/harness/loop stack.
 - Hacker News or Reddit only if framed as a useful field guide, not a launch announcement.
 - Relevant GitHub issues or discussions where Loop Engineering, coding agents, or agent workflows are already being discussed.
-- Authors and maintainers cited in the repo, asking for corrections or stronger canonical links.
+- Authors and maintainers cited in the repo, asking for corrections or better original source links.
 - The repository's own Discussions, using [`DISCUSSIONS.md`](DISCUSSIONS.md) for starter prompts and scope guidance.
 
 ## Outreach Targets
@@ -184,5 +184,5 @@ Candidate places:
 
 - Do not claim that Loop Engineering is a finished standard.
 - Do not imply cited authors endorse this repository unless they explicitly do.
-- Prefer "early field guide" or "curated map" over "definitive source".
+- Describe what readers can explore, compare, or build instead of claiming authority or completeness.
 - Keep all claims linked to public, inspectable sources.

meta/MAINTENANCE.md

@@ -7,7 +7,7 @@ Keep Awesome Loop Engineering accurate, stable, and trustworthy with the checks
 - Review the latest Quality workflow result.
 - Run the link checker if the scheduled workflow reports failures.
 - Triage new issues and PRs.
-- Reject resources that do not pass the curation standard.
+- Reject resources that do not pass the resource selection guide.
 - Prefer replacing unstable links with primary or official sources.
 
 ## Monthly Checks
@@ -23,7 +23,7 @@ Keep Awesome Loop Engineering accurate, stable, and trustworthy with the checks
 When a link fails:
 
 1. Check whether the original source moved.
-1. Prefer an official canonical URL over mirrors.
+1. Prefer an original or official URL over mirrors.
 1. If the source is gone, replace it with a stronger equivalent resource.
 1. If no equivalent exists, remove the entry rather than linking to an unreliable archive.
 1. Keep the annotation focused on what the replacement contributes to Loop Engineering.
@@ -69,6 +69,7 @@ npx --yes markdownlint-cli2 "**/*.md"
 python3 -m py_compile scripts/*.py
 python3 scripts/check_license.py
 python3 scripts/check_resource_labels.py README.md
+python3 scripts/check_reader_facing_copy.py
 python3 scripts/render_readme_tables.py --check
 python3 scripts/export_resource_dataset.py --check
 python3 scripts/check_project_consistency.py

meta/MAINTENANCE_CALENDAR.md

@@ -30,7 +30,7 @@ Run the local checks in [MAINTENANCE.md](MAINTENANCE.md#local-verification) befo
 
 - Taxonomy review: confirm [TAXONOMY.md](../TAXONOMY.md) still covers how loops are being built in practice.
 - Roadmap review: update [ROADMAP.md](../ROADMAP.md) with shipped work and the next pattern, gallery, and runtime priorities.
-- Translation drift review: confirm each translated README still matches the canonical English overview and bump the `last-synced` markers; see [TRANSLATIONS.md](../TRANSLATIONS.md).
+- Translation drift review: confirm each translated README still matches the full English overview and bump the `last-synced` markers; see [TRANSLATIONS.md](../TRANSLATIONS.md).
 
 ## Canonical Awesome Submission Status
 
@@ -41,7 +41,7 @@ The 30-day age requirement has passed. [`sindresorhus/awesome#4339`](https://git
 - 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.
+- Keep public claims concrete: describe what readers can explore, compare, or build without presenting the project as a finished standard.
 
 ## See Also
 

meta/OUTREACH.md

@@ -12,9 +12,9 @@ Use these messages to request sources, operating examples, and accuracy correcti
 ## Short Message
 
 ```text
-Hi <name>, Awesome Loop Engineering collects source-audited resources and reusable patterns for recurring AI-agent systems.
+Hi <name>, Awesome Loop Engineering connects 579 papers, docs, tools, benchmarks, and guides with reusable patterns for recurring AI-agent systems.
 
-If you have a canonical source, correction, real-world loop, or cautionary example, you can contribute here:
+If you have an original or official source, a correction, a real-world loop, or a cautionary example, you can contribute here:
 https://github.com/ChaoYue0307/awesome-loop-engineering
 ```
 
@@ -31,14 +31,14 @@ Useful examples name the trigger, intake, agent roles, verification gates, durab
 ```text
 Hi <name>, I included <work title> in Awesome Loop Engineering and summarized its contribution as: "<current annotation>."
 
-Could you check whether that characterization is accurate? If it misses the main contribution, novelty, impact, or canonical link, please submit a correction:
+Could you check whether that characterization is accurate? If it misses the main contribution, novelty, impact, or source link, please submit a correction:
 https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=annotation-correction.yml
 ```
 
 ## Maintainer Request
 
 ```text
-Hi <name>, Awesome Loop Engineering is a source-audited field guide and implementation kit for recurring AI-agent systems. It includes 579 resources across model-to-operations layers, 20 operational patterns, 20 validated contracts, 8 runtime starters, and a structured dataset.
+Hi <name>, Awesome Loop Engineering helps researchers and builders move from 579 papers, docs, tools, benchmarks, and guides to 20 operational patterns, 20 adaptable contracts, 8 runtime starters, and a structured dataset.
 
 Would it fit the related-resources policy for <project or newsletter>? I can provide a shorter description or submit through the normal contribution process:
 https://github.com/ChaoYue0307/awesome-loop-engineering
@@ -48,5 +48,5 @@ https://github.com/ChaoYue0307/awesome-loop-engineering
 
 - Do not ask people to endorse claims they have not made.
 - Do not ask for private customer data, proprietary prompts, secrets, or internal dashboards.
-- Do not imply the repository is a standard. It is an early curated field guide for an emerging practice.
+- Do not imply the repository is a standard; describe the concrete resources and tools readers can use.
 - Do not ask for stars, reposts, or endorsements in an accuracy request.

meta/hf_card_body.md

@@ -5,36 +5,36 @@
 <h1 align="center">Awesome Loop Engineering Dataset</h1>
 
 <p align="center">
-  A source-audited dataset of {{RESOURCE_COUNT}} papers, official docs, tools, benchmarks, patterns, critiques, and implementation guides for recurring AI-agent systems.
+  A structured dataset 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/blob/main/meta/CURATION.md">Resource selection</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 pairs one source with a concise editorial assessment, bibliographic metadata, lifecycle and audience facets, evidence classification, audit status, and point-in-time repository statistics when applicable.
+Each row connects an original source to its contribution, novelty, impact, publication details, lifecycle stages, audience, evidence type, link status, and repository context when applicable.
 
 Current release: **v{{VERSION}}**
 
 | Surface | Count |
 | --- | ---: |
-| Source-audited resources | {{RESOURCE_COUNT}} |
+| Resources | {{RESOURCE_COUNT}} |
 | Operational patterns | {{PATTERN_COUNT}} |
-| Validated loop contracts | {{CONTRACT_COUNT}} |
+| Adaptable loop contracts | {{CONTRACT_COUNT}} |
 | Runtime starters | {{RUNNABLE_COUNT}} |
 
-The source audit dated **{{AUDIT_DATE}}** reports these row statuses: **{{REACHABLE_COUNT}} reachable public**, **{{RESTRICTED_COUNT}} access restricted**, **{{LOCAL_COUNT}} repository-native**, and **{{BROKEN_COUNT}} broken or unreachable**.
+At the **{{AUDIT_DATE}}** source check, **{{REACHABLE_COUNT}} public links opened successfully**, **{{RESTRICTED_COUNT}} required access**, **{{LOCAL_COUNT}} pointed to repository files**, and **{{BROKEN_COUNT}} were broken or unreachable**.
 
 ## What A Loop Contract Is
 
 A **Loop Contract** is a reviewable operating specification for one recurring agent job. It fixes what authorizes a run, which work and actions are allowed, what context and roles the run uses, which external evidence proves progress, what state survives, how much the loop may spend, and when a human takes over or the loop exits.
 
-Recurring agents need this policy because schedules, events, queues, and goals remove live supervision. Without explicit boundaries, missing decisions become hidden defaults: the loop can select the wrong work, widen its own scope, approve itself, forget failed attempts, or retry without a stopping rule. Start with the [JSON schema](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/schemas/loop-contract.schema.json) and adapt one of the [{{CONTRACT_COUNT}} validated examples](https://github.com/ChaoYue0307/awesome-loop-engineering/tree/main/examples).
+Recurring agents need this policy because schedules, events, queues, and goals remove live supervision. Without explicit boundaries, missing decisions become hidden defaults: the loop can select the wrong work, widen its own scope, approve itself, forget failed attempts, or retry without a stopping rule. Start with the [JSON schema](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/schemas/loop-contract.schema.json) and adapt one of the [{{CONTRACT_COUNT}} schema-checked examples](https://github.com/ChaoYue0307/awesome-loop-engineering/tree/main/examples).
 
 ## Loop Maturity Model
 
@@ -91,7 +91,7 @@ Use `url` as the durable join key. `row_id` and `source_line` are positional and
 - Compare works by lifecycle, audience, evidence class, source type, and publication metadata.
 - Separate model, agent, harness, workflow, operations, evaluation, and cross-layer resources without treating adjacent model recurrence as a complete operational loop.
 - Build literature maps, reading lists, dashboards, or retrieval indexes.
-- Audit contribution, novelty, impact, provenance, and evidence claims.
+- Inspect contribution, novelty, impact, source, and evidence fields before following a claim.
 - Find reusable patterns, contracts, schemas, executable examples, and copy/paste runtime templates.
 
 Do not use `signal_strength`, GitHub stars, forks, or inclusion in this collection as a quality label, endorsement, or automated ranking of scientific validity.
@@ -115,38 +115,38 @@ The primary configuration is `resources`, with one `train` split backed by the n
 | 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` | What the resource contributes to recurring agent systems. |
+| Resource analysis | `annotation`, `key_contribution`, `novelty`, `impact` | What the resource contributes to recurring agent systems. |
 | Scope | `loop_layer`, `scope_fit` | Where recurrence lives and whether the source is direct, enabling, or adjacent to operational Loop Engineering. |
 | Navigation | `section`, `collection`, `user_goal`, `lifecycle_stages`, `audience` | Where the resource fits and who it serves. |
 | Evidence | `evidence_class`, `evidence_tier`, `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. |
+| Publication | `authors`, `publication_date`, `publication_year`, `publication_venue`, `publisher`, `doi`, `arxiv_id`, `primary_category` | Bibliographic data exposed by the original or official source. |
+| Source details | `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. |
+| Export trace | `source_readme`, `source_line`, `source_url`, `date_added` | How the row maps back to the full 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
+## How To Read The Evidence
 
-Start with 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).
+Open the linked work before relying on a summary. Evidence labels distinguish published research, official documentation, inspectable implementations, practitioner analysis, risk analysis, and discovery indexes; they describe the kind of source, not its scientific quality.
 
-Annotations are original syntheses, not copied abstracts or 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; the maintainer owns each released inclusion decision and annotation.
+Summaries explain each work's contribution in original language rather than copying abstracts. They do not imply author endorsement. Follow the source link to inspect methods, results, limitations, licenses, and current documentation.
 
-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).
+The latest link-check results are 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 selective rather than exhaustive, and one person currently reviews changes.
 - 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.
+- A successful URL check proves that a link opened at check time, not that its claims are correct, permanent, or independently validated.
+- Access-restricted rows could not be fully retrieved during the latest check and should be opened 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.
+- Linked third-party works retain their own licenses and terms; CC0-1.0 covers only original repository descriptions, metadata, templates, and documentation.
 
 ## Versioning And Corrections
 
-GitHub Releases define versioned snapshots; cite a release or commit for reproducibility. Submit corrections to summaries, contribution, novelty, impact, authorship, dates, venues, identifiers, or canonical URLs through the [correction form](https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=annotation-correction.yml).
+GitHub Releases define versioned snapshots; cite a release or commit for reproducibility. Submit corrections to summaries, contribution, novelty, impact, authorship, dates, venues, identifiers, or source URLs through the [correction form](https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=annotation-correction.yml).
 
 ## Citation
 

meta/social-preview.html

@@ -69,7 +69,7 @@
   <body>
     <main class="preview">
       <div class="identity">
-        <p class="kicker">Source-audited field guide + implementation kit</p>
+        <p class="kicker">Field guide + implementation kit</p>
         <h1>Awesome Loop Engineering</h1>
         <p class="tagline">Design loops, not just prompts.</p>
         <p class="support">From model recurrence to verified agent work and bounded operations.</p>
@@ -79,9 +79,9 @@
         <p>Model / agent / operations</p>
       </div>
       <div class="stats">
-        <div class="stat"><b>579</b><span>Source-audited resources</span></div>
+        <div class="stat"><b>579</b><span>Papers, docs, tools + guides</span></div>
         <div class="stat"><b>20</b><span>Operational patterns</span></div>
-        <div class="stat"><b>20</b><span>Validated contracts</span></div>
+        <div class="stat"><b>20</b><span>Schema-checked contracts</span></div>
         <div class="stat"><b>8</b><span>Runtime starters</span></div>
       </div>
     </main>

posts/launch.md

@@ -2,14 +2,14 @@
 
 Awesome Loop Engineering v0.8.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.
 
-Navigate 579 source-audited works without collapsing looped models, agent execution, harnesses, workflows, and production operations into one idea.
+Explore 579 resources without collapsing looped models, agent execution, harnesses, workflows, and production operations into one idea.
 
 ## What You Can Use
 
-- 579 source-audited resources linked to canonical works
+- 579 papers, official docs, tools, benchmarks, and guides linked to the original work
 - 23 selected model-recurrence papers, from Universal Transformers and Huginn to LoopCoder and LoopWM, labeled as adjacent foundations rather than complete agent loops
 - 20 operational patterns organized by build, operate, optimize, and govern use cases
-- 20 schema-validated loop contracts, one for every pattern
+- 20 schema-checked loop contracts, one for every pattern
 - 8 runtime starters: 3 dependency-light executables and 5 copy/paste runtime templates
 - an interactive Resource Atlas for filtering by goal, loop layer, lifecycle stage, artifact type, and evidence class
 - 50-field CSV, JSONL, and Parquet exports mirrored as a Hugging Face dataset
@@ -21,7 +21,7 @@ Navigate 579 source-audited works without collapsing looped models, agent execut
 - Added `loop_layer` and `scope_fit` to every dataset row so model recurrence remains discoverable without being misclassified as operational Loop Engineering.
 - Added a model-to-operations map and loop-layer filter to the Resource Atlas.
 - Added a cross-layer research protocol for comparing internal recurrent depth with external evidence-aware retries under matched compute and cost.
-- Rechecked all 579 canonical sources and refreshed every arXiv publication decision so official conference or journal records take precedence when verified.
+- Checked all 579 source links and refreshed every arXiv publication record so verified conference or journal publications take precedence over preprints.
 - Updated the website, social preview, translations, release metadata, and Hugging Face dataset to the same counts and terminology.
 
 ## Why This Matters
@@ -41,12 +41,12 @@ The goal remains bounded, reviewable, evidence-driven repetition, not unlimited
 
 - [Explore the Resource Atlas](https://chaoyue0307.github.io/awesome-loop-engineering/#resources)
 - [Choose an operational pattern](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/patterns/README.md)
-- [Adapt a validated contract](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/examples/README.md)
+- [Adapt a schema-checked contract](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/examples/README.md)
 - [Run a starter](https://github.com/ChaoYue0307/awesome-loop-engineering/tree/main/examples/runnable)
 - [Use the Hugging Face dataset](https://huggingface.co/datasets/cy0307/awesome-loop-engineering)
 - [Contribute a source or correction](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/CONTRIBUTING.md)
 
-Corrections are especially valuable. If a summary is inaccurate or a stronger canonical source exists, use the annotation-correction form or open a pull request.
+Corrections are especially valuable. If a summary is inaccurate or a better original or official source exists, use the annotation-correction form or open a pull request.
 
 ## Open The Field Guide
 

posts/launch.zh-CN.md

@@ -2,11 +2,11 @@
 
 Awesome Loop Engineering v0.8.0 建立了一张从模型内部递归、Agent 执行、Harness 到外层运行系统的完整地图。
 
-可浏览 579 条经审核资源，同时保持清晰边界：模型内的循环提供自适应计算，但不等于具备外部验证、持久状态、预算、人类交接与退出规则的运行级 Loop。
+可浏览 579 篇论文、官方文档、工具、benchmark 与实践指南，同时保持清晰边界：模型内的循环提供自适应计算，但不等于具备外部验证、持久状态、预算、人类交接与退出规则的运行级 Loop。
 
 ## 可直接使用
 
-- 579 条链接到 canonical source 的审阅资源
+- 579 篇论文、官方文档、工具、benchmark 与实践指南，并直接链接原始来源
 - 23 篇精选模型递归论文，覆盖 Universal Transformers、Huginn、LoopCoder、LoopWM 等方向
 - 20 个按 build、operate、optimize、govern 组织的 operational patterns
 - 20 个经过 schema 校验的 loop contracts，每个 pattern 对应一个
@@ -21,7 +21,7 @@ Awesome Loop Engineering v0.8.0 建立了一张从模型内部递归、Agent 执
 - 为每条数据新增 `loop_layer` 与 `scope_fit`，避免将模型递归误标为完整的运行级 Loop Engineering。
 - 在 Resource Atlas 中新增模型到运维的层级图与 Loop 层级筛选器。
 - 新增跨层评测方案，用匹配算力和成本的实验比较模型内部递归与外部证据驱动重试。
-- 重新检查全部 579 个 canonical sources，并刷新所有 arXiv 的发表状态。
+- 检查全部 579 个来源链接，并刷新所有 arXiv 论文的会议或期刊发表状态。
 - 同步更新网站、social preview、翻译、release metadata 与 Hugging Face Dataset。
 
 ## 为什么值得关注
@@ -43,12 +43,12 @@ v0.8.0 将这些层级连接起来：
 
 - [浏览 Resource Atlas](https://chaoyue0307.github.io/awesome-loop-engineering/#resources)
 - [选择 operational pattern](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/patterns/README.md)
-- [改造 validated contract](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/examples/README.md)
+- [改造经 schema 校验的 contract](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/examples/README.md)
 - [运行 starter](https://github.com/ChaoYue0307/awesome-loop-engineering/tree/main/examples/runnable)
 - [使用 Hugging Face 数据集](https://huggingface.co/datasets/cy0307/awesome-loop-engineering)
 - [贡献资源或提交纠错](https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/CONTRIBUTING.md)
 
-如果某条概括不够准确，或存在更可靠的 canonical source，请使用 annotation-correction form 或提交 pull request。
+如果某条概括不够准确，或存在更可靠的原始或官方来源，请使用 annotation-correction form 或提交 pull request。
 
 ## 打开 Field Guide
 

scripts/check_project_consistency.py

@@ -113,25 +113,25 @@ def main() -> int:
         ROOT / "README.md",
         [
             f"resources-{count}-",
-            f"**{count} source-audited resources**",
-            f"covers all {count} rows",
+            f"**{count} resources**",
+            f"At the latest <a href=\"data/resource_source_audit.csv\">source check</a>",
         ],
         failures,
     )
     require(
         ROOT / "docs" / "index.html",
         [
-            f'content="{count} source-audited resources',
-            f">{count}</b><span>audited resources</span>",
-            f"Filter {count} source-audited works",
+            f'content="Explore {count} resources',
+            f">{count}</b><span>resources</span>",
+            f"Filter {count} 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} source-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} source-audited resources"], failures)
+    require(ROOT / "posts" / "launch.md", [f"# Awesome Loop Engineering v{version}", f"{count} 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} resources"], failures)
 
     for translation in sorted(ROOT.glob("README.*.md")):
         require(translation, [count], failures)

scripts/check_reader_facing_copy.py

@@ -0,0 +1,72 @@
+#!/usr/bin/env python3
+"""Reject self-evaluative marketing phrases on reader-facing surfaces."""
+
+from __future__ import annotations
+
+import re
+import sys
+from pathlib import Path
+
+
+ROOT = Path(__file__).resolve().parents[1]
+PUBLIC_FILES = {
+    ROOT / "README.md",
+    ROOT / "CONTRIBUTING.md",
+    ROOT / "DEFINITION.md",
+    ROOT / "CITATION.cff",
+    ROOT / "CITATION.bib",
+    ROOT / "TRANSLATIONS.md",
+    ROOT / "data" / "README.md",
+    ROOT / "docs" / "index.html",
+    ROOT / "docs" / "llms.txt",
+    ROOT / "meta" / "DISTRIBUTION.md",
+    ROOT / "meta" / "CURATION.md",
+    ROOT / "meta" / "OUTREACH.md",
+    ROOT / "meta" / "hf_card_body.md",
+    ROOT / "meta" / "social-preview.html",
+    ROOT / "posts" / "launch.md",
+    ROOT / "posts" / "launch.zh-CN.md",
+    ROOT / ".github" / "pull_request_template.md",
+}
+PUBLIC_FILES.update(ROOT.glob("README.*.md"))
+PUBLIC_FILES.update((ROOT / "docs").glob("x-v*.html"))
+
+BANNED_PHRASES = {
+    "source-audited": re.compile(r"source[ -]audited", re.IGNORECASE),
+    "audited resources": re.compile(r"audited (?:resources|works)", re.IGNORECASE),
+    "canonical source": re.compile(r"canonical source", re.IGNORECASE),
+    "canonical README": re.compile(r"canonical README", re.IGNORECASE),
+    "curated marketing claim": re.compile(
+        r"curated (?:field guide|map|resources|order|lists)", re.IGNORECASE
+    ),
+    "process-first heading": re.compile(
+        r"(?:maintainer picks|trust and provenance|audit snapshot)", re.IGNORECASE
+    ),
+}
+
+
+def main() -> int:
+    failures: list[str] = []
+    for path in sorted(PUBLIC_FILES):
+        if not path.exists():
+            failures.append(f"missing public surface: {path.relative_to(ROOT)}")
+            continue
+        for line_number, line in enumerate(path.read_text(encoding="utf-8").splitlines(), 1):
+            for label, pattern in BANNED_PHRASES.items():
+                if pattern.search(line):
+                    failures.append(
+                        f"{path.relative_to(ROOT)}:{line_number}: {label}: {line.strip()}"
+                    )
+
+    if failures:
+        print("Reader-facing copy uses process-first language:", file=sys.stderr)
+        for failure in failures:
+            print(f"- {failure}", file=sys.stderr)
+        return 1
+
+    print(f"Reader-facing copy check passed across {len(PUBLIC_FILES)} files.")
+    return 0
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())

scripts/check_resource_labels.py

@@ -11,9 +11,9 @@ from export_resource_dataset import TYPE_MARKERS, parse_entry_line
 
 
 RESOURCE_SECTIONS = {
-    "Canonical Definition",
+    "Working Definition",
     "Concept Guides",
-    "Maintainer Picks",
+    "Recommended Path",
     "Start Here",
     "Core Loop Primitives",
     "Official Runtime Guides",

scripts/export_resource_dataset.py

@@ -352,7 +352,7 @@ TYPE_SIGNAL = {
     "Template": ("Reusable template, schema, checklist, or guide; signal comes from concrete adaptation and validation.", "medium"),
     "Blog": ("Practitioner essay or field note; signal comes from concrete experience, framing, examples, or adoption discussion.", "contextual"),
     "Critique": ("Risk or limitation analysis; signal comes from boundary conditions, failure modes, and adoption cautions.", "contextual"),
-    "List": ("Adjacent curated collection; signal comes from ecosystem coverage rather than a single technical claim.", "contextual"),
+    "List": ("Adjacent directory or reading list; signal comes from ecosystem coverage rather than a single technical claim.", "contextual"),
 }
 
 EVIDENCE_TIERS = {
@@ -596,9 +596,9 @@ def signal(
 ) -> tuple[str, str]:
     status = audit.get("audit_status", "")
     if status in {"broken", "unreachable", "local_missing"}:
-        return "The latest source audit could not verify this resource; treat its claims and availability as unverified.", "unverified"
+        return "The linked source was unavailable at the latest check; treat its claims and availability as unverified.", "unverified"
     if url_kind != "external":
-        return "Local artifact maintained with automated validation checks.", "medium"
+        return "Repository file; inspect the linked schema, example, guide, or implementation.", "medium"
     if evidence == "official-documentation":
         return f"Primary official documentation from {domain}; use it for current product or standard behavior.", "high"
     if evidence in {"research-preprint", "research-paper"}:
@@ -625,7 +625,7 @@ def signal(
         return f"Inspectable GitHub source{detail}; popularity is context, not proof of reliability.", "medium"
     if evidence in {"practitioner-analysis", "risk-analysis", "curated-index"}:
         return f"Contextual source from {domain}; useful for practice signals or boundary conditions, not independent validation.", "contextual"
-    return TYPE_SIGNAL.get(resource_type, (f"Curated source from {domain}; verify fit against the linked artifact.", "contextual"))
+    return TYPE_SIGNAL.get(resource_type, (f"Background source from {domain}; verify fit against the linked artifact.", "contextual"))
 
 
 def iter_rows(readme_path: Path = README) -> list[dict[str, str]]:

scripts/render_readme_tables.py

@@ -30,7 +30,7 @@ TYPE_DESCRIPTIONS = {
     "Benchmark": "Benchmark, eval suite, leaderboard, or evaluation dataset",
     "Pattern": "Operational playbook or reusable workflow",
     "Template": "Template, checklist, schema, guide, or contribution artifact",
-    "List": "Adjacent awesome list, ecosystem map, or curated collection",
+    "List": "Adjacent directory, ecosystem map, or reading list",
     "Critique": "Risk analysis, limitation, caveat, or skeptical take",
 }
 
@@ -47,13 +47,13 @@ EVIDENCE_LABELS = {
     "source-implementation": "Source implementation",
     "implementation": "Implementation",
     "benchmark": "Benchmark or evaluation",
-    "repository-native": "Validated project artifact",
+    "repository-native": "Project artifact",
     "reusable-artifact": "Reusable artifact",
     "operational-pattern": "Operational pattern",
     "practitioner-analysis": "Practitioner analysis",
     "risk-analysis": "Risk analysis",
-    "curated-index": "Curated index",
-    "curated-source": "Curated source",
+    "curated-index": "Discovery index",
+    "curated-source": "Background source",
 }
 
 EVIDENCE_NOTES = {
@@ -64,13 +64,13 @@ EVIDENCE_NOTES = {
     "source-implementation": "Inspectable source and runtime behavior",
     "implementation": "Working implementation or runtime",
     "benchmark": "Repeatable tasks, scores, or evaluation data",
-    "repository-native": "Maintained with project validation checks",
+    "repository-native": "Schema, example, guide, or repository documentation",
     "reusable-artifact": "Adaptable template, schema, or guide",
     "operational-pattern": "Transferable operating practice",
     "practitioner-analysis": "Experience-backed implementation context",
     "risk-analysis": "Failure modes, limits, or adoption cautions",
-    "curated-index": "Ecosystem coverage and discovery",
-    "curated-source": "Curated context for comparison",
+    "curated-index": "Broader ecosystem coverage for finding related work",
+    "curated-source": "Background context for comparison",
 }
 
 
@@ -156,14 +156,13 @@ def publication_cell(row: dict[str, str]) -> str:
 
 def evidence_cell(row: dict[str, str]) -> str:
     evidence = row["evidence_class"]
-    tier = row["evidence_tier"]
     label = EVIDENCE_LABELS.get(evidence, evidence.replace("-", " ").title())
     note = EVIDENCE_NOTES.get(evidence, "Inspect the linked source")
     if row["source_status"] == "restricted":
-        note = "Access restricted during the latest source audit"
+        note = "The linked source required access at the latest check"
     elif row["source_status"] not in {"ok", "local_ok"}:
-        note = "Availability was not verified in the latest audit"
-    return f"**Tier {escape_cell(tier)}** · {escape_cell(label)}<br><sub>{escape_cell(note)}</sub>"
+        note = "The linked source was unavailable at the latest check"
+    return f"**{escape_cell(label)}**<br><sub>{escape_cell(note)}</sub>"
 
 
 def resource_cells(row: dict[str, str]) -> tuple[str, str, str, str]: