> ## Documentation Index
> Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Implementation Log Archive Convention

> This document defines the convention for implementation logs and their archives so that AI agents and tooling use a single, stable structure.

**Version:** 1.0.0\
**Last Updated:** 2026-02-16\
**Status:** Active

This document defines the convention for implementation logs and their archives so that AI agents and tooling use a single, stable structure.

***

## Overview

* **Main log:** `specs/{core}/IMPLEMENTATION_LOG.md` — source of truth for *current* completion; new entries go here only. Tooling (the `spec-complete` command, the `scripts/audit/audit-spec-completion.js` script, and `scripts/update-feature-metadata.js`) reads and writes only this file.
* **Archive:** `specs/{core}/IMPLEMENTATION_LOG_ARCHIVE.md` — historical entries only; read-only for tooling. Used when the main log exceeds the target size (see below).

***

## Paths and Roles

| File                                         | Role                                   | Written by scripts? |
| -------------------------------------------- | -------------------------------------- | ------------------- |
| `specs/{core}/IMPLEMENTATION_LOG.md`         | Current completion status; new entries | Yes                 |
| `specs/{core}/IMPLEMENTATION_LOG_ARCHIVE.md` | Historical entries (moved from main)   | No                  |

***

## When to Archive

* **Trigger:** When the main log exceeds **500 lines** (per [AGENTS.md File Size Management](https://github.com/Encore-OS/encoreos/blob/development/AGENTS.md#file-size-management)).
* **Action:** Move the **oldest** entries (by spec ID or completion date) from `IMPLEMENTATION_LOG.md` into `IMPLEMENTATION_LOG_ARCHIVE.md`. Keep the most recent 3–5 spec entries (or enough to bring the main log under 500 lines) in the main file.

***

## Main Log Header Format

At the top of every `IMPLEMENTATION_LOG.md` (after the main title), include:

1. **Archive:** Either:
   * **Archive:** `IMPLEMENTATION_LOG_ARCHIVE.md` (e.g. FA-01 through FA-16) when an archive exists, or
   * **Archive:** None (current log under 500 lines) when there is no archive.

2. **Quick Reference (when archive exists):** A table with columns **Spec ID** | **Summary** | **Location**. List each spec that remains in the main log as "This file" and each archived spec as "Archive § SPEC-ID" (e.g. "Archive § FA-10").

***

## Archive File Header Format

At the top of `IMPLEMENTATION_LOG_ARCHIVE.md`:

```markdown theme={null}
# [Core] Implementation Log — Archive

> **Archived:** Historical entries. Current completion: IMPLEMENTATION_LOG.md (same directory).

Entries below: [spec range or date range, e.g. FA-01 through FA-16].
```

***

## Reference Format for Archived Specs

When referring to an archived entry in docs or agent instructions, use:

* **Format:** `IMPLEMENTATION_LOG_ARCHIVE.md § {CORE}-##`
* **Example:** "See IMPLEMENTATION\_LOG\_ARCHIVE.md § FA-10" or "Completion details in IMPLEMENTATION\_LOG\_ARCHIVE.md § HR-02."

***

## Preserved Structure

When moving content to the archive, preserve the existing structure:

* `## SPEC-ID: Title` section headers
* `#### Enhancement N:` subheadings (for audit script detection)
* Schema changes, deliverables, and other subsections as-is

***

## Related

* [SPEC\_COMPLETION\_TRACKING.md](/development/SPEC_COMPLETION_TRACKING) — Commands and workflows
* [AGENTS.md](https://github.com/Encore-OS/encoreos/blob/development/AGENTS.md) — Implementation Logs section and File Size Management
* [specs/\_templates/IMPLEMENTATION\_LOG\_TEMPLATE.md](https://github.com/Encore-OS/encoreos/blob/development/specs/_templates/IMPLEMENTATION_LOG_TEMPLATE.md) — Log entry template