diff --git a/packages/core/src/task-store/async-self-healing.ts b/packages/core/src/task-store/async-self-healing.ts
index ff8408bcf3..baa29a521e 100644
--- a/packages/core/src/task-store/async-self-healing.ts
+++ b/packages/core/src/task-store/async-self-healing.ts
@@ -55,6 +55,17 @@ interface SoftDeletedColumnDriftCandidate {
 export async function listSoftDeletedColumnDriftCandidates(
   db: AsyncDataLayer["db"],
 ): Promise<SoftDeletedColumnDriftCandidate[]> {
+  /*
+  FNXC:WorkflowResolvedColumns 2026-07-31-23:59 DELIBERATE-LITERAL — STATE MARKER, DO NOT RESOLVE:
+  `"archived"` is the marker a soft-deleted row is SUPPOSED to carry, and this query finds rows whose
+  column DRIFTED away from it. Resolving it to the board's archived-lane set would classify a
+  soft-deleted row sitting in a renamed archive lane as drift and "repair" a row that is already
+  correct.
+
+  Marked at the site for the same reason as `task-mutation-ops.ts`'s cleanup sweep: the LANE/STATE
+  classification lived only in `archived-column-gate-parity.test.ts`, and a coordinated conversion
+  edits this file. The shape here is indistinguishable from the six LANE sites without it.
+  */
   const rows = await db
     .select({ id: schema.project.tasks.id, column: schema.project.tasks.column })
     .from(schema.project.tasks)
diff --git a/packages/core/src/task-store/task-mutation-ops.ts b/packages/core/src/task-store/task-mutation-ops.ts
index 48442f93a7..472a4e9f38 100644
--- a/packages/core/src/task-store/task-mutation-ops.ts
+++ b/packages/core/src/task-store/task-mutation-ops.ts
@@ -1066,6 +1066,21 @@ export async function cleanupArchivedTasksImpl(store: TaskStore): Promise<string
     quarantine partition.
     */
     const projectId = layer.projectId?.trim() || "__legacy_unscoped__";
+    /*
+    FNXC:WorkflowResolvedColumns 2026-07-31-23:59 DELIBERATE-LITERAL — STATE MARKER, DO NOT RESOLVE:
+    `"archived"` here is the marker `archiveTask` WROTE, not a board lane. This sweep enumerates rows
+    Fusion itself archived and then REMOVES THEIR DIRECTORIES (`rm` below). Widening it to the
+    resolved archived-lane set would feed cards merely RESTING in a board's archived-trait lane into
+    a filesystem delete — live work, destroyed.
+
+    Marked at the site because the classification previously lived only in
+    `archived-column-gate-parity.test.ts`, and a coordinated three-encoding conversion edits THIS
+    file. A converter working file-by-file would see the same `eq(column, "archived")` shape as the
+    six LANE sites and have nothing here telling them apart.
+
+    The sibling STATE site is `async-self-healing.ts`'s soft-deleted column-drift query; the LANE/
+    STATE split for all eight Drizzle sites is recorded in that parity test.
+    */
     const archivedRows = await layer.db
       .select()
       .from(schema.project.tasks)