# Archive

> **Do not edit these files.** They're frozen snapshots kept for historical
> context. Internal links inside archived docs still point at the
> pre-reorganization paths (e.g. `ARCHITECTURE.md`) — that's intentional so
> they read as they did at the time.

For the current state of the system, go back to [docs/README.md](../README.md)
or [roadmap.md](../roadmap.md).

## Contents

| File | What it is |
|---|---|
| [HANDOFF-2026-04-18.md](HANDOFF-2026-04-18.md) | The single-page doc index as it stood before the 2026-04-22 reorganization |
| [MIGRATION.md](MIGRATION.md) | Legacy `gestionclient` (MariaDB) → ERPNext migration: table-by-table mapping, completion log |
| [LEGACY-ACCOUNTING-ANALYSIS.md](LEGACY-ACCOUNTING-ANALYSIS.md) | April 2026 audit of the legacy PHP/MariaDB accounting system, informed the migration plan |
| [status-snapshots/](status-snapshots/) | Dated "state of the system" write-ups from individual work sessions |

## Why these still exist

Old snapshots capture context that doesn't belong in the evergreen docs:
what someone was worried about on a specific date, what tradeoffs we
considered and rejected, what shipped in a given sprint. When reading, assume
code examples and doc paths have drifted — verify in the current code before
acting on them.