KomarDB
designing

PrintQueue

scores

progress30%
prioritymedium
complexity5/10
readiness7/10
excitement5/10
hours invested0h
last12 days ago

claude · 1 hour ago

PrintQueue is thrashing — regressed from launching→idea→designing→development→designing within 48h, with progress slashed from 88% to 30%. Signals a scope/identity crisis, not a build problem.

  • Write a one-paragraph description and tagline today
  • Define the single core user and print job flow
  • List the 3 features required for v1, cut rest
  • Pick deployment target (local CUPS vs cloud) and commit
  • Stop stage-toggling until scope doc is written

Plan from /cl

  1. Order intake — upload or preset + submit
    /order creates an order; valid file saved to the Docker volume · done 13 days ago
  2. Operator queue board with live polling
    /queue lists jobs oldest-first and refreshes within 10s · done 13 days ago
  3. Status control (Pending -> In Progress -> Done)
    PATCH advances and steps back status; board reflects change · done 13 days ago
  4. Preset library management
    Operator uploads and deletes reusable preset designs · done 13 days ago
  5. Customer confirmation + live status page
    Ticket number shown; status page fires browser notification when Done · done 13 days ago
  6. Operator auth gate
    /queue* and mutating API routes require the password cookie · done 13 days ago
  7. File storage on Docker volume + validation
    Uploads on pq-data volume; png/jpeg/pdf only, max 10MB enforced server-side · done 13 days ago
  8. Deploy to komarlab.com with real password
    Live URL responds; deployed commit matches local

Recent checkpoints

  • 13 days ago0.5hCreated a private GitHub repo (Komark0/printqueue) and pushed both existing commits so the project shows on the dashboard. Registered the project in Founder OS and laid down its first 8-milestone plan from docs/plan.md. The MVP (built in prior sessions) is confirmed code-complete; only deployment to komarlab.com remains.