בס״ד

Action Queue — Operator Views

docs/action-queue/OPERATOR_VIEWS.md · last changed (pre-VM history) · rendered from GitHub master

Action Queue — Operator Views

Generated: Sunday, June 21, 2026 · 3:10 AM ET
Source: Personal Command Inbox sheet (canonical) → normalized projection (action_queue_normalized.json)
Rule applied: raw text stays in the sheet; nothing deleted or closed here. May cards = reverify. Sam Today ≤ 5.

I consolidated the 6 requested view-files into this ONE doc on purpose (your "one place" rule beats 6 fragments on your phone). Say the word and I'll split them.


1. SAM TODAY (max 5 — the only things in your face)

# A-ID Do this Verb
290 A-20260608-005 Call Asher 212.500.1312 — unblocks HOA foreclosure + Eden $20K call
116 A-20260528-011 Darchei registration (late, fees) pay/call
335 A-20260610-019 Darchei aid — Mrs. Kurtz 718-868-2300 x222 call
019 A-20260520-003 Taxes — decide on $9,750 Z&E (gates aid + refunds) decide
284 A-20260607-013 Yaakov Jun 23 plan (Regents + camp drop-off) schedule

Everything else is off your board by design.


2. MILDRED WORK (her lane only — STR + admin)

# A-ID Item Status
333 A-20260610-017 Duke 9332 $243.03 + confirm power before booking OPEN
330 A-20260610-014 HVAC plans 9312/9332 OPEN
032 A-20260520-016 Smart-device list → Nathan WORKING
205 A-20260601-008 AKKO device insurance enrollment OPEN
331 A-20260610-015 June expense review (her list) OPEN
313/342 Her registration-pay + restart date NEED_INFO

Governance: Mildred marks handled; only Sam/Claude sets DONE (proof). Confirm or override.


3. BACKLOG by lane (off the active board, nothing lost)


4. STALE / REVERIFY (P0/P1 with passed dates — do NOT execute blind)

# Item Why reverify
011 HOA $5,609.30 5/22 long passed; now via Asher
116 Darchei registration 5/20 passed
045 LIJ $110.37 ~6/1 passed
278 Camp Agudah $100 6/15 passed
282 Hotel "Thursday" which Thursday?
280 Citi (Zee) card likely = the 6003 missed payment-arrangement (caught 6/17)
328 MIS de-lever engine frozen; advisory only
341 Fund kids Fidelity SpaceX bought 6/12 → likely closeable with proof

5. DUPLICATES / SUPERSEDED


6. SYSTEM FAILURES (not tasks — broken plumbing)

# Looks like a task, is really
042 Memory doesn't sync across devices = architecture gap
202 Session-open stale-sweep doesn't auto-run = the rule exists, automation doesn't
325 "I don't know what's in my drafts/sent" = no visibility layer
LevSMS one-fact-in-6-places (caught 6/19) = same class of drift

These get fixed once structurally, not re-touched as tasks.


7. MISSING INPUTS (need from Sam to finish accepting)

  1. Mildred close rule — confirm: handled-only, Sam closes? (proposed yes)
  2. Source of truth — confirm the Command Inbox sheet stays primary; D1 ledger is later (proposed yes)
  3. #336 personal Gmail — mark DONE? (reconnected this weekend)
  4. #341 kids Fidelity — close with the SpaceX-buy proof?
  5. Hotel #282 / Camp #278 / LIJ #045 — reverify amounts/dates before I touch them

What changed vs the raw queue

Nothing deleted. Nothing closed. This is a read-only projection for acceptance. On your "accepted," I can (a) push these status/owner/reverify flags back into the sheet, and (b) collapse the camera + family-page + Verizon clusters. Until then the sheet is untouched.


EXECUTION LOG — Sam said "accepted," pushed 2026-06-21 ~3:42 AM ET (via the LIVE web app, no code change, no deploy, every write audited to Action_Events)

Pushed (4 writes, all reversible):
- #320CANCELLED. True supersede: #342 explicitly says it supersedes the 2-week framing. Mildred-pause logic now lives on #342 only.
- #045 (LIJ $110.37) → NEED_INFO (reverify balance before paying; due ~Jun 1 passed).
- #278 (Camp Agudah $100) → NEED_INFO (reverify amount owed; Jun 15 passed).
- #282 (hotel Thursday) → NEED_INFO (which Thursday? confirm date before booking).

NOT pushed — projection was WRONG, caught by reading the live cards (evidence rule):
- Camera "cluster" #218/#219/#220/#226 are NOT duplicates — they are four DISTINCT tasks: #218 embed cams in family page, #219 Ring feasibility, #220 physically reconnect dead Camera 4, #226 camera-page polish. Collapsing to 1 would have destroyed real work. LEFT INTACT.
- Family-page "cluster" #222/#223/#229 are NOT duplicates — #222 Chanie shared stylesheet, #223 kiosk two-way, #229 Family-OS board. Related theme, distinct deliverables. LEFT INTACT.
- Verizon #022/#208/#298 — one project but distinct sub-steps (cancel/pay-final, move-all-lines, port-number). LEFT INTACT; #208 is the master that already notes it consolidates the others. Recommend keeping all three until the port completes, then close #022+#298 with proof.

Lesson reaffirmed: "collapse clusters to 1" looked right in the projection; the live card text proved most clusters are themed-but-distinct. Open the card, never act on the projection blind.

Source trail · docs/action-queue/OPERATOR_VIEWS.md @ master · rendered 2026-07-02 7:23 PM EDT by scripts/build-docs.py · the .md in the repo is the truth; this page is the phone-readable view