Workflow review queue
These are workflows that can be drafted, logged, or partially handled now, but need a missing backend, provider, hardware, permission, or data source before they can run repeatably. Blue Static the Webmaster keeps the master checklist; the named role owns the actual workflow requirements.
P1 unlocks the core Sheriff/Serafina production workflow. P2 unlocks shared operations and communication infrastructure. P3 improves specialist roles once the core operating system works.
Loading checklist state.
P1 review 1
Blocked by: Final mobile cross-device verification and production admin-password polish
Current fallback: Worker + D1 case board is live; admin token console handles closeout and updates.
Review question: Does one mobile-created case appear on desktop, accept an admin update, and close cleanly?
P1 review 2
Blocked by: R2 bucket deployment and one live upload smoke test
Current fallback: Worker stores file metadata in D1; actual visual inspection can still happen by chat if R2 upload fails.
Review question: After deploying the R2 bucket binding, does a mobile photo upload land in private R2 storage and delete on Case Closed?
P1 review 3
Blocked by: No current blocker after published smoke test
Current fallback: Serafina calls the Worker API directly; browser-local handoff remains only if the Worker fails.
Review question: Monitor the next real escalation for user-facing clarity and media-upload behavior.
P2 review 4
Blocked by: Resend API key, verified sender/from email, Worker secrets, and one test send
Current fallback: Worker update route and admin UI are ready; optional email consent remains disabled until secrets exist.
Review question: Which verified sender should be used for Sheriff case-update emails?
P2 review 5
Blocked by: Shared backend for daily notes
Current fallback: Each staff daily-note page saves notes in the current browser only.
Review question: Should daily notes share the Sheriff D1 database, or get their own D1 table?
P2 review 6
Blocked by: Mailing-list provider, consent storage, contact tagging, and unsubscribe path
Current fallback: Draft follow-ups in chat; Gmail only when explicitly requested.
Review question: Should Mailman use Resend audiences, a simple D1 contacts table, or a full CRM?
P2 review 7
Blocked by: Calendar integration, alert rules, and preferred notification channel
Current fallback: Manual chat reminders and OpenClaw cron/reminder notes when requested.
Review question: Which calendar source should be authoritative?
P2 review 8
Blocked by: Shared inventory API, receipt OCR, product-photo storage, and authenticated H-E-B browser access
Current fallback: Local inventory files and manual H-E-B checks when logged in.
Review question: Do we prioritize receipt import, pantry scanning, or H-E-B cart support first?
P2 review 9
Blocked by: CI link checker, scheduled audit job, and published-report format
Current fallback: Manual link checks before commits.
Review question: Should GitHub Actions run link checks on every push?
P2 review 10
Blocked by: Knowledge base/search layer and photo/archive storage policy
Current fallback: Workspace memory files, Labs pages, and git history.
Review question: Should the archive live in files, Notion, D1, or another searchable system?
P2 review 11
Blocked by: Library database, saved-article workflow, tags, and source-quality rubric
Current fallback: Links in Labs pages and ad hoc web research.
Review question: Should Librarian use a simple HTML index first, or a dedicated library tool?
P2 review 12
Blocked by: Budget data source, subscription list, receipt OCR, and spending-permission boundary
Current fallback: No spending without explicit human confirmation; costs are discussed in chat.
Review question: Should Treasurer start with subscriptions, receipts, or project budgets?
P3 review 13
Blocked by: Weather station, soil sensors, garden photo archive, and routine field checks
Current fallback: Garden checklist pages and Serafina/Sheriff reports.
Review question: Are sensors worth it, or should we start with scheduled photo checks?
P3 review 14
Blocked by: Battery/expiration tracker, sensor dashboard, emergency-kit inventory
Current fallback: Manual Sheriff/Safety notes and room maintenance inventory.
Review question: Should the first Safety workflow be batteries, locks, emergency kit, or trip hazards?
P3 review 15
Blocked by: Guest preference store, reusable welcome packet, and room-readiness checklist
Current fallback: Room guide and chat-prepared guest notes.
Review question: Should Concierge start with a guest intake form?
P3 review 16
Blocked by: Affiliate dashboard, disclosure templates, public metrics, and campaign tracker
Current fallback: Labs build logs and manual public-safe messaging review.
Review question: Which affiliate area should PR track first?
P3 review 17
Blocked by: Social scheduler, platform connections, approval workflow, and analytics
Current fallback: Draft captions in chat for human review.
Review question: Which platform should be first: Instagram, TikTok, LinkedIn, or something else?
P3 review 18
Blocked by: Moodboard tool, swatch/photo library, and photo-lighting kit
Current fallback: Room guide, local design notes, and chat suggestions.
Review question: Should Stylist begin with room styling, wardrobe, or public project visuals?
P3 review 19
Blocked by: Event aggregator, ticket-price tracker, and shared fun calendar
Current fallback: Manual web research and calendar reminders.
Review question: Which event sources should be watched first?
P3 review 20
Blocked by: Watchlist database and streaming availability source
Current fallback: Manual watchlist notes in chat.
Review question: Should Theatre track household watchlists by mood, platform, or guest group first?
P3 review 21
Blocked by: Music-service integration and speaker/room automation permissions
Current fallback: Manual playlist notes and recommendations.
Review question: Which music service and rooms should DJ support first?
P3 review 22
Blocked by: Fitness tracker integration, routine database, and recovery tracking
Current fallback: Manual movement planning in chat.
Review question: Should Coach start with daily movement, stretching, or strength tracking?
P3 review 23
Blocked by: Guest preference store, quiet-hours reminder, and first-aid inventory tracker
Current fallback: Manual guest comfort checklists.
Review question: Should Nanny start with guest comfort or household wellness reminders?
P3 review 24
Blocked by: Reflection library, seasonal tracker, and ritual supply inventory
Current fallback: Serafina Sacred Calendar and chat prompts.
Review question: Should Guru start with a weekly check-in form?
P3 review 25
Blocked by: Recipe database, pantry integration, and meal-planning calendar
Current fallback: Pantry cookbook notes and active inventory files.
Review question: Should Chef start with shelf-stable recipes or weekly meal planning?
P3 review 26
Blocked by: Coffee/tea inventory tracker and drink recipe card system
Current fallback: Manual recipes and inventory notes.
Review question: Should Barista start with coffee, tea, smoothies, or slushies?
P3 review 27
Blocked by: Baking inventory tracker, recipe testing log, and equipment list
Current fallback: Pantry notes and recipe drafts.
Review question: Should Baker start with bread, cookies, cakes, or tools?
P3 review 28
Blocked by: Bar inventory app, wine/cellar tracker, and batched-syrup labels
Current fallback: Andre Mack guide and manual inventory notes.
Review question: Should Bartender start with wine, spirits, beer, or tiki supplies?
P3 review 29
Blocked by: Laundry label/photo guide and fabric-care supply tracker
Current fallback: Room maintenance inventory and chat troubleshooting.
Review question: Should Laundramat start with stain guide or fabric care labels?
P3 review 30
Blocked by: Cleaning schedule app, robot vacuum map, and tool inventory
Current fallback: Room maintenance inventory and manual cleaning notes.
Review question: Should Keeper start with dusting/vacuuming cadence or room reset checklists?
{}