Read this first. A flag on the Work Queue is not the system being wrong — it means
nobody wrote the answer down. If a flag is wrong, close it with the correction:
a wrong flag closed with a correction is worth more than a right flag closed quietly.
Flags are closed in the job's own Claude Project with
close F-…, using the id
printed on the row.
Where things stand
- 1,257Open flags
- 87Blocking a gate
- 481Over 7 days
- 44Jobs w/ flags
- 7Closed to date
Work from these every day
Start here
Project Tracker & Work Queue
The company board. Overview, tracker, my projects, subcontractors,
commands — and the Work Queue, every open flag ranked by blocked gate then age.
Group By job to attack one file at a time.
Process
Order of Events
Prospect to warranty, current state only — no superseded text. Each stage
carries what happens, its commands, its advancing gate and its hard rules.
Reference
Sub Bid Filing Card
The filename pattern, the
a_/x_ prefixes, the
_mat/_inst markers and the sanctioned scope vocabulary.
The filename is what sets the price.Planning — internal
Superseded view
Open Flags Roll-up
The standalone flags list, kept for now. The Work Queue tab on the board
replaces it and is the one that can be closed against.
Staffing
Superintendent & Supervisor Assignments
Capacity against the caps, cluster tightness per superintendent, the geocoded
job map, and the records with nobody named. Any supervisor can be assigned to any
superintendent — there are no standing pairings.
Program
Master To-Do
Open items across the Claude process program, by priority and owner,
with a closed-today view that keeps what moved and why.