Board Movement

Growing
63
Start of Week
68
End of Week
+5
Net Change
12
Moved to Done
17
New Cards Added

Intake outpaced completions this week. 17 new cards entered Triage (meeting follow-ups, AI insights, build proposals) vs. 12 moved to Done. The board is net +5. Triage alone holds 28 cards, 13 of which are more than 5 days old with no resolution. Action needed: a triage pass this weekend to kill, delegate, or schedule the backlog.

Column breakdown (active): Triage 28  |  Up Next 13  |  Priority This Week 9  |  Brian 5  |  Team 9  |  Ready to Review 3  |  Not Now 1

Resolved Autonomously

12 items

Awaiting Your Call

10 items

Ready to Review column (3) + high-activity Triage cards with proposals waiting on your direction (7).

Ready to Review  |  Created 2026-06-05  |  No due date
Ask: Confirm the 3 Salesforce inventory fields (available units, in-transit qty, ETA date) so Pam can start quoting restock dates. Claude built + verified end-to-end. Waiting on your field sign-off only.
Ready to Review  |  14 comments  |  Due 2026-06-07
Ask: Go/no-go on building this now. V1 scope is Google Sheet template + capture phase (Granola + Basecamp Decision Log). 3 open questions: (1) Drive folder? (2) Anthony rates confidence or agent infers? (3) Private to you or shared with Brian?
Ready to Review  |  3 comments  |  No due date
Ask: 3 decisions needed before building: (1) Per brand (iHR vs ITAM) or combined? (2) Judge model: Sonnet 4.6 vs Opus 4.8 (5x cost)? (3) Is "CS Manager Bot" Yuma tuning or a separate supervisor bot? The build differs significantly.
Triage  |  7 comments  |  Created 2026-06-02
Ask: Architecture decision: should bots have separate Basecamp/Slack identities per audience (team vs customer vs CEO), or is prompt-scoping sufficient? Claude has a proposal with pros/cons. Your call on direction.
Triage  |  7 comments  |  Created 2026-06-01
Ask: Evaluation is done. Ready for your verdict: adopt the Agent Cookie pattern, watch for 30 days, or pass entirely?
Triage  |  8 comments  |  Created 2026-05-31
Ask: Claude has assessed build vs. buy. Do you want a vendor shortlist (Okta/JumpCloud/Rippling SSO) or is this deferred until post-EDC?
Triage  |  8 comments  |  Created 2026-05-29
Ask: Research done. Claude identified 2 automation options. Which path: (A) automate filing preparation in-house or (B) engage an outsourced sales tax service?
Triage  |  9 comments  |  Created 2026-05-29
Ask: Design complete. Do you want to wire the GAS feedback endpoint to the daily brief's self-improvement loop now?
Triage  |  11 comments  |  Created 2026-05-29
Ask: 3 enhancements scoped and ready to build. Approve all 3, pick subset, or defer?
Triage  |  9 comments  |  Created 2026-05-29
Ask: Insight + analysis complete. Is there a specific migration at Emazing to apply this pattern to now, or file for reference?

Blocked

3 items

Auto-Trash Next Friday

5 candidates
These cards have had no activity in 30+ days and are not in Done. They will be flagged for trash next Friday unless you rescue them.

Feedback This Week

No thumbs received

Last week's review (2026-05-29) got no 👍/👎 from you. The card was moved to Done on 2026-06-04 but the proposed patterns had no reactions. Claude can't graduate patterns without your signal. If you skipped it intentionally, that's fine — but if you want the auto-approval loop to tighten over time, this is the moment to click the buttons below.

Proposed Auto-Approval Patterns

3 proposals

👍 = Claude can do this without moving to Review. 👎 = Keep requiring your sign-off.

Pattern A: Meeting follow-up cards (granola-generated)

When granola-sync creates a follow-up card from a meeting transcript and Claude processes all action items without requiring a decision from you, Claude closes the card directly to Done. No card lands in Triage or Review.

Examples this week: CST Daily Huddle (2x), Mariana Onboarding (2x), Leadership Daily Huddle, Accounting Sync

Submitted.

Pattern B: Jarvis bug-fix insights (self-contained)

When Claude identifies a Jarvis/cron bug, fixes it in the same session, and verifies the fix, the insight card goes directly to Done. No Triage step. Applies only to fixes where no external service, team member, or spend is affected.

Examples this week: Stop posting usage-limit warnings to Slack; Fix broken Google Python namespace; CCD routines not running

Submitted.

Pattern C: Prep cards — research-only meeting prep

When Claude creates a meeting prep card and the work is purely research + agenda synthesis (no commitments, no external messages), the card closes to Done after the meeting happens. No lingering in Triage.

Examples this week: Prep: Finance AI sync; Prep: CST Monthly Meeting; Prep: AI sharing

Submitted.

Open Questions For You

6 questions
  1. The "Expectations" card has been in Triage since March 31 (66 days). What is it? Kill it, schedule it, or move to Up Next?
  2. coo-executor 16:30 run is failing daily due to session token limit. Should I reduce scope (e.g., skip deep-reading all comments) or should you increase the Claude Team account token allocation first?
  3. Decision Outcome Tracker is due June 7. Do you want me to spin up the Google Sheet template this weekend and start capturing, or is this lower priority than the CST Manager Bot work?
  4. Salesforce connector: which are the authoritative fields — ECS__Available_Units__c for in-stock, serp__Quantity_in_Transit__c per PO for incoming, ETA__c for date? Pam is waiting.
  5. Anne/Joan/Ardie performance cards are 36-49 days stale. Do you want to pause Anne's card given the family emergency, and resume Joan + Ardie reviews now?
  6. Last week's review patterns got no reaction. Should I just auto-approve Pattern A (meeting follow-ups) by default since it's been operating that way in practice for months anyway?
Generated by Claude  |  June 5, 2026  |  Open board