archive-agent-notes

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Archiving Agent Notes

归档Agent Notes

Reduce the active decision corpus without erasing history that can still guide work. Judge every note semantically; word count and age are discovery aids, never archive criteria.
在不删除仍可指导工作的历史记录的前提下,精简活跃决策库。需从语义层面评判每一条笔记;字数和时长仅作为发现辅助信息,绝不能作为归档标准。

Read the contracts

阅读相关约定

Read the repository's Agent Note rules, archive instructions, and the applicable lifecycle instructions before classifying. Use current skills, docs, newer notes, and inbound links to establish whether a rationale still owns or constrains anything.
在进行分类前,请先阅读仓库中的Agent Notes规则、归档说明以及适用的生命周期说明。利用当前技能、文档、较新的笔记和入站链接来确定某条理由是否仍对相关内容拥有所有权或施加约束。

Check supersession when adding a note

添加笔记时检查是否被取代

Every new note triggers a scoped audit of active notes covering the same decision or mechanism. Classify each full or partial supersession while writing the new note: archive qualifying implemented triplets in the same PR, retain and cross-link partial supersessions, reject obsolete proposals, and delete rejected notes that no longer prevent a plausible mistake. Apply the consolidation rule when the new owner absorbs every unique proposition, deleting the absorbed triplet whole; do not defer a known match.
每新增一条笔记,都要对涵盖同一决策或机制的活跃笔记进行范围限定的审核。撰写新笔记时,需对每一处完全或部分取代情况进行分类:在同一个PR中归档符合条件的已实施三元组,保留并交叉链接部分被取代的内容,拒绝过时的提案,删除无法再避免合理错误的已拒绝笔记。当新内容涵盖了所有独特主张时,应用合并规则,删除被完全涵盖的三元组;切勿延迟处理已知匹配项。

Classify by future value

按未来价值分类

  • Implemented — keep active: retain a note when its rationale, alternatives, negative guarantee, ownership boundary, or reintroduction condition is likely to guide a future change.
  • Implemented — archive: archive a note when the shipped decision is complete and its body is unlikely to guide future work.
  • Proposed — never archive: keep a live proposal active; if it is no longer worth pursuing, reject it with an honest reason.
  • Rejected — keep only as a guardrail: retain a rejection only when the losing proposal remains a tempting, meaningful mistake.
  • Rejected — delete: delete the whole triplet when the rejected idea is obsolete or unlikely to prevent re-litigation. Repair or delete inbound links.
Do not archive toward a quota. Inspect every note in scope, classify analogous groups under one principle, and record genuinely borderline decisions.
  • 已实施——保留活跃状态: 当笔记的理由、替代方案、负面保证、所有权边界或重新引入条件可能指导未来变更时,保留该笔记。
  • 已实施——归档: 当已发布的决策已完成,且笔记内容不太可能指导未来工作时,对其进行归档。
  • 已提案——绝不归档: 保留活跃的提案;若该提案不再值得推进,请给出真实理由予以拒绝。
  • 已拒绝——仅作为防护保留: 仅当被否决的提案仍是一个诱人且有意义的错误时,才保留该拒绝记录。
  • 已拒绝——删除: 当被否决的想法已过时或不太可能避免重新讨论时,删除整个三元组。修复或删除入站链接。
切勿为了达到配额而进行归档。检查范围内的每一条笔记,将同类群组归为同一原则,并记录真正存在争议的决策。

Archive one implemented triplet

归档单个已实施三元组

  1. Make no body edits. Insert only
    Archived: YYYY-MM-DD
    immediately below
    Status: implemented
    in both language files, using the same date on both sides.
  2. Re-record the consistency record mechanically for the two metadata-only edits, with the repository's pairing recorder in write mode. Do not translate, reformat, update facts, or repair links inside the note.
  3. Move the complete
    foo.md
    ,
    foo.zh.md
    , and
    foo.i18n.yaml
    triplet from
    implemented/{class}/
    to
    archived/{class}/
    ;
    implemented
    is deliberately absent from the archive path.
  4. Search for inbound links from active prose. Redirect them to current authority, retarget them to the archived path only when the historical snapshot is intentionally cited, or delete them. Never verify or repair links out of the archived note.
When inbound-link repair edited an active bilingual doc, hand the counterpart update to
translate-docs
so both sides stay in sync before the pairing gate.
After the triplet is sealed, never edit, move, translate, reformat, or delete it. Archived notes remain valid inbound-link targets but are historical snapshots, not authority for current behavior.
  1. 请勿修改正文内容。仅需在两种语言文件的
    Status: implemented
    下方立即插入
    Archived: YYYY-MM-DD
    ,两边使用相同日期。
  2. 使用仓库的配对记录器以写入模式,为这两次仅修改元数据的操作机械地重新记录一致性记录。请勿翻译、重新格式化、更新事实或修复笔记内部的链接。
  3. 将完整的
    foo.md
    foo.zh.md
    foo.i18n.yaml
    三元组从
    implemented/{class}/
    移至
    archived/{class}/
    ;归档路径中特意不包含
    implemented
  4. 搜索活跃文档中的入站链接。将其重定向至当前权威内容,仅当有意引用历史快照时才将其指向归档路径,否则删除链接。无需验证或修复归档笔记的出站链接。
如果修复入站链接时修改了活跃的双语文档,请将对应的更新交给
translate-docs
,确保两边在配对检查前保持同步。
三元组被封存后,切勿对其进行编辑、移动、翻译、重新格式化或删除操作。归档笔记仍可作为有效的入站链接目标,但它们只是历史快照,并非当前行为的权威依据。

Validate and report

验证与报告

Run the repository's archive seal gate in write mode first: it proves every existing seal still matches, then appends only the newly archived artifacts. Run the gate again normally, then the documentation gates and
git diff --check
. Report active implemented notes kept, implemented notes archived, rejected notes kept/deleted, proposed notes rejected if any, and every genuinely borderline case with its chosen outcome.
首先以写入模式运行仓库的归档封存检查:它会验证所有现有封存是否仍匹配,然后仅追加新归档的工件。正常再次运行该检查,接着运行文档检查和
git diff --check
。报告保留的活跃已实施笔记数量、归档的已实施笔记数量、保留/删除的已拒绝笔记数量(如有)、被拒绝的提案数量(如有),以及每个真正存在争议的案例及其最终结果。