Work items · what this division has been told to do
Open here0
Critical0
No owner0
Frozen backlog (read-only)18
Work items you ownadd, edit and drag to reorder — every write is persisted and audited
#Work itemTypeStatusUrgencyOwnerDueLast written
No work items have been added to this store yet. This is a real empty store, not a failed read — add the first one below.
Type, status and urgency use the same vocabulary as the division’s historical work_items table, so nothing has to be translated later. Due date may be left empty for unscheduled.
Where this division's work is storedNamed before any number is read (§14)
StoreWritableRowsWhat it is
software_work_itemYes0The queue above, inside software-agent-team.db. Every add, edit and reorder writes a row into software_agent_audit carrying the previous value, the next value, who wrote it and when.
work_itemsNo20870The historical pipeline backlog inside software.db, frozen at Sep 22, 2026. It is the source the operating page’s work graph reads, and it is read-only for good: its -wal and -shm siblings are directories, so SQLite cannot open it for writing in any mode.
Two stores, and this page does not pretend they are one. Adding a work item above does not append to the frozen work_items table, and nothing above is a copy of a frozen row. The older /api/work-items endpoint still exists and still targets the frozen database, so its POST and PUT return HTTP 500 and land nothing — no control on this page calls it. The frozen counts shown here come from a real read of that snapshot.