sase.tr/docs/TASK_REGISTRY_GUIDELINES.md

Fusion Task Registry Guidelines

Overview

The Fusion platform maintains a task board that records all planning, implementation, and review activities. Occasionally, messages from team members reference task IDs that appear missing from the board. This can happen due to:

1. Accidental deletion – a task was removed without proper archival.
2. Visibility filtering – tasks may be hidden in a different column (e.g., archived) or not indexed in the current worktree.
3. Stale references – the task ID was renamed or superseded by a follow‑up task.

To prevent duplicate work and ensure a single source of truth, follow the guidelines below.

Recommended Process for Verifying a Task ID

1. Search the board using the Fusion API (or the UI) for the exact ID.

   fn_task_show({id: "FN-078"})
   

2. If not found, list all tasks in the archived column to see if it was moved:

   fn_task_list({column: "archived"})
   

3. Search project memory for any mentions of the ID – older logs may indicate why it was removed.

   fn_memory_search({query: "FN-078"})
   

4. Check sibling tasks (e.g., the dependent task FN-085) for notes about the missing task.
5. If the task truly does not exist, create a new task documenting the original intent and link it to the follow‑up task to keep the history.

   fn_task_create({description: "Restore missing FN-078 context – VIN decode board mismatch investigation", dependencies: ["FN-085"]})
   

Documentation Updates

Whenever a missing‑task scenario is resolved, update the following resources:

• docs/TASK_REGISTRY_GUIDELINES.md – Add a brief note about the incident and the steps taken.
• Project memory – Append a durable entry under the task-registry layer summarising the root cause (e.g., accidental deletion, UI filter bug).
• Team wiki or internal Confluence – Reference the Fusion board URL and link the new task.

Preventing Future Duplicates

• Always search before creating a new task that seems related to an existing one.
• Use the fn_task_show command to confirm the existence and status of the referenced ID.
• Link related tasks using the dependencies field so the board shows traceability.
• Archive, never delete, tasks that are obsolete. Archiving keeps the ID searchable.

Quick Reference Commands

Recent Incident (2026-05-11)

• Task ID: FN-078 was referenced but not found on the board.
• Investigation Findings: The board appeared empty; fn_task_list returned no tasks in any column, indicating a possible board initialization issue or data loss.
• Action Taken: Created a follow‑up task FN-086 to document and restore the missing context, and linked it to FN-085.
• Resolution: Updated documentation to record the incident and ensure future verification steps.

Quick Reference Commands

Action	Command
Show task	fn_task_show({id: "FN-078"})
List column	fn_task_list({column: "done"})
Search memory	fn_memory_search({query: "FN-078"})
Create follow‑up	fn_task_create({description: "...", dependencies: ["FN-085"]})

By following these steps, the team can maintain a reliable, auditable task registry and avoid duplicated planning‑failure work.