Alego Archive Agent Notes

Archive Alego 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 Agent Note rules, the archive instructions, and the applicable active lifecycle instructions before classifying. Use current code, configuration, package docs, generated catalogs, newer Agent Notes, and inbound links to establish whether a rationale still owns or constrains anything.

Check supersession when adding a note

Before drafting, apply the creation criteria. Every new Agent Note triggers a scoped audit of active notes covering the same decision, mechanism, or rejected alternative. 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 or independently useful rationale, reject obsolete proposals, and delete rejected notes that no longer prevent a plausible mistake. Apply the Agent Note consolidation rule when the new owner absorbs every unique proposition; do not defer a known match to a later corpus audit.

Classify by future value

Apply these lifecycle-specific outcomes:

• Implemented — delete: delete complete triplets that only describe small UI adjustments or purely mechanical changes, and repair or remove inbound links. Local bug fixes, performance changes, new capabilities, and substantive behavior or ownership decisions do not qualify merely because they are implemented. Apply this criterion before keep/archive classification.
• Implemented — keep active: retain a note when its rationale, alternatives, negative guarantees, durable/wire semantics, ownership boundary, security rule, or reintroduction condition is likely to guide a future change. Classify the decision, not the mechanics of its implementation: a mechanical rename or type extraction can still record lasting naming, compatibility, or ownership rules. Length does not matter.
• Implemented — archive: archive a substantive historical decision when it is complete and unlikely to guide future work, but its historical rationale still warrants preservation. Do not archive records that meet the direct-deletion criterion.
• Proposed — never archive: keep a live proposal active; if it is no longer worth pursuing, reject it with an honest reason and satisfy the rejected lifecycle format.
• Rejected — keep only as a guardrail: retain a rejection only when the losing proposal remains a tempting, meaningful mistake and the note explains why it loses.
• Rejected — delete: delete the whole triplet when the rejected idea is obsolete, superseded, no longer plausible, 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, use best judgment for close cases, and record genuinely borderline decisions for the handoff.

Calibrated examples

These examples set the bar; the word counts demonstrate that size is not the test.

Delete implemented notes such as:

• collapsed sidebar control rail — 533 words: closed, minor UI behavior;
• issue-policy module ownership — completed function relocation and import rewiring with unchanged behavior.

Keep implemented notes such as:

• event-sourced sessions — 248 words: foundational authority and durability boundary;
• single Harness-home resolver — 596 words: cross-product ownership rule;
• project session directories — 628 words: durable storage and identity policy;
• parallel pre-push gates — 400 words: borderline, but still guides gate scheduling and resource tuning;
• dropped image content block — 334 words: keep until multimodal support lands, because it states the coordinated reintroduction condition.

For rejected notes:

• keep folding the compaction package split — 426 words: the temptation to merge the packages remains meaningful;
• delete streaming workflow progress through tool calls — 972 words: its ACP/UI premise is obsolete;
• delete dropping ACP terminal metadata — 362 words: the later automation-only ACP decision resolved the question.