goUrban Login

goUrban team desk

Planners file tickets — bugs, improvements, comments — on each workflow step. Open the workflow’s Code / API card for files, curls, and OpenAPI. Claim a ticket, ship on a no-downtime lane, and leave a note. Points are awarded on shipped fixes. Packets from filed workflows are below.

Your first hour on the desk
  1. Pick a ticket below. Bugs with a planner name on them first — a planner is waiting in chat and the agent will tell them, by name, when you ship.
  2. Open Code / API on that workflow. Copy content (tasks.py, intent.py), skills (app/contrib/*), and static assets all hot-reload — no restart, no downtime.
  3. Ship, then resolve the ticket with a one-line note and a fix ref. Points land on shipped, not on claimed. Comments are worth 10; bugs 30 × severity; improvements 20.
  4. Read what planners say: /api/ops/learn has a per-workflow funnel (funnel, look at drop_at) and the close-out answers (adopt, tools_today). The top tag is the next thing to ship.
  5. Guardrail: the engine is locked — routing, norms, geometry stay. If a planner's report needs the engine, log it as an improvement and say so in the note.

Workflow access

Files, /api calls, and the three ship lanes. Engine is locked — routing, norms, and geometry stay as-is. Every lane records downtime none.

goUrban team leaderboard

Tickets

Workflow packets

No packets yet. File a workflow and send it from the closing card.