Draconai Documentation

dd_id_2f06865258
4. System Technical

Work Queues

Table of Contents

Work Queue System (Codex)

System

  • Instructions are stored as individual numbered files in codex_work_queue/.
  • Each instruction is a single file (e.g., 001_...md) so tasks can be executed one-by-one in order.
  • A 1. new/ subfolder exists under codex_work_queue/ for incoming instructions.
  • A 2. current/ subfolder exists under codex_work_queue/ for the active instruction.
  • A 3. done/ subfolder exists under codex_work_queue/ for completed instructions.
  • A 4. on_hold/ subfolder exists under codex_work_queue/ for instructions that should be ignored until explicitly requested by the user.
  • Workflow:
  • Process the lowest-numbered file first.
  • Execute only that instruction.
  • Before starting, move the instruction file into codex_work_queue/2. current/.
  • When finished, move the file into codex_work_queue/3. done/.
  • Work on one task at a time only; do not start a second instruction until the current one is completed and moved to 3. done/.
  • Execute tasks in strict chronological/consecutive order (lowest numbered first, no skipping).
  • Do not modify or write to the .ssh folder. Stay inside the repo directory and use the sync helper script for server access.
  • Do not reorder files; add new instructions as new numbered files.
  • Planner/Doer roles:
  • Two Codex instances are used: "planner" and "doer".
  • On startup, always ask the user which role you should take; do not assume a default.
  • After the user specifies the role, explicitly state which role you are in to avoid misunderstandings.
  • When a task is completed, move its instruction file into codex_work_queue/3. done/.
  • Auto-start the next task after finishing the current one (lowest-numbered remaining file).
  • When the queue is empty and any DevDocs inputs changed (docs content, theme, or plugins), automatically sync the docs to WordPress.
  • Ignore any tasks in codex_work_queue/4. on_hold/ unless the user explicitly asks to pick a task from on-hold. When explicitly requested, move the chosen task into 1. new/ (or 2. current/ if starting immediately) and treat it as a new task.