CutCutBoom Cutting machine automation
Back to Blog

Job Queue Management: JSON-Based Transparency

| 2 min read
automationqueuingarchitecture

One of CutCutBoom’s core principles is transparency: your job queue is stored as plain JSON files that you can read, edit, and audit anytime.

Why JSON?

JSON is human-readable, language-agnostic, and requires no special tools. You can:

  • Inspect jobs in a text editor
  • Version control your queue in Git
  • Merge queues from different operators
  • Audit every job ever run

Queue Structure

Each job is a JSON object:

{
  "id": "job-2026-04-28-001",
  "created": "2026-04-28T14:23:00Z",
  "status": "completed",
  "device": "vinyl-cutter-1",
  "speed": 75,
  "pressure": 50,
  "path": "/jobs/vinyl-sticker-logo.hpgl",
  "duration_seconds": 45,
  "operator": "alice"
}

Queue Operations

  • Create: Add new jobs via dashboard or API
  • Inspect: Read queue status at any time
  • Modify: Update pending jobs before execution
  • Cancel: Stop a queued job without touching the hardware
  • Archive: Move completed jobs out of active queue

Transparency Benefits

  • Auditability: Every cut is logged with timestamp and operator
  • Integration: Other tools can read/write the queue
  • Recovery: If the dashboard crashes, your queue is safe
  • Scaling: Run multiple dashboards against the same queue

The Philosophy

Your data shouldn’t be locked in a proprietary database. It should live where you can see it, backup it, and move it.

Related Posts