April CAN create new calendar blocks freely on Christi's Crimson Outlook calendar without per-block approval. This includes: focus blocks, drive time, prep blocks, EOD wraps, daily lunch, weekly briefing prep, recurring standing items per CLAUDE.md, deep work sessions, and event-specific work blocks (like the SCHARP MFA chase pattern from 5/13). April CANNOT modify, move, delete, or reschedule any meeting created by someone else without explicit per-meeting approval from Christi. The Priority Hierarchy from rec9IuwVM4MBaG2yI applies: Anzor > Pete > External meetings > Christi-organized client meetings > Focus Time (moveable) > CW task blocks (freely moveable). When in doubt about whether something is 'new block' or 'modification', ask. New block = the time slot was empty or only had a moveable Focus block. Modification = there's an existing meeting with attendees. How to apply: - Default behavior at EOD wrap: block tomorrow's calendar with everything that has to be done (per CLAUDE.md doctrine) - Default behavior at Sunday weekly briefing: block advance time across all 3 work cals - When a Claude instance tells April 'don't touch the calendar' or similar ambiguous directive, April should clarify: 'Do you mean don't move existing meetings, or also no new blocks?' Default assumption when ambiguous: still create new blocks (this is core doctrine), surface any existing-meeting modifications for per-item approval. - Voice-to-text often garbles 'calendar' — see the autocorrect handling learning.
Before creating or picking a ConnectWise service ticket for any client, check whether that client has an active project: GET /project/projects?conditions=company/id={id} and look for status In Progress. If one exists, the work belongs on a project ticket inside it (chargeToType ProjectTicket), not on a standalone service ticket. This holds even when the client has a plausible-looking open service ticket. Karney had open service ticket 957259 (Karney AI University - Program Coordination) which looked like the natural home, but the correct destination was project 2626 ticket 913531. Alere similarly went to project 2695 ticket 946130 rather than a new service ticket. Active projects as of 2026-07-28: Alere 2695 (M365 Copilot Readiness, PM Christi) and 2729 (Los Alamitos Network Deployment, PM Julia); Karney 2626 (AI Training, PM Christi).
KLUE security incident notifications from Huntress (info@huntress.com) are FYI-only for Christi. She is on the distribution list as an observer; the Crimson Security team owns and works these incidents. This is NOT a vCIO action item. HARD RULES: - April inbox sweep: do NOT create a Task from a KLUE/Huntress security alert. Do not categorize it into anything that generates a follow-up. Treat as FYI-only and drop. - Chip midday check: do NOT surface KLUE/Huntress tasks as URGENT/overdue flags. - Same pattern as other security-alert noise Christi is merely CC'd on (suspended-line alerts, LumifiCyber/ShieldVision incident notices). History: this task kept getting recreated (June, then again July 2) and re-flagged by Chip on 7/6, 7/7, 7/8. Christi deleted it 7/8 and asked that it stop recurring.
AbilityFirst leadership team is a group of FOUR, not three. Always include all four when emailing leadership, drafting executive comms, looping leadership in on AF decisions, or routing leadership-level deliverables. The four leadership members: 1. Sergio Letona — CEO 2. Carl — CFO 3. Jeremy Sidell — Chief Program Officer (CPO). NOT IT. Programs side of the org. (jsidell@abilityfirst.org, Contacts rec4TQkKFgeMxAgIC) 4. Michuan Fleming — COO / Chief People Officer (mfleming@abilityfirst.org, Contacts recZkxk1xxYkNInpn) NEVER send a leadership-tier AF communication that includes Sergio, Jeremy, and Carl without also including Michuan. She has been left off repeatedly across multiple sessions and that pattern stops now. Applies to: leadership announcement emails, leadership briefings, leadership-only meeting invites, executive summaries, board prep, strategic decision routing, project status to leadership, AF training rollouts targeting leadership, or any 'leadership cc' pattern. Also check: 'Michonne' showing up in transcripts (e.g., camp project 5/1/2026 ops meeting tail) is most likely a transcription mishearing of 'Michuan' — verify before treating as a separate person. Do NOT route IT-specific items to Jeremy. He runs Programs. Do NOT infer leadership roles from name alone. Verify against Contacts table or ask Christi.
The 'Board 80 for Christi's tickets' rule is more nuanced than Dewey v2 playbook captured. **REFINED RULE (2026-04-23, from Christi direct):** 1. **Existing tickets:** Post time to whatever board the ticket already lives on. Do NOT migrate. Christi logs to Board 48, 58, AF project boards, SCHARP project boards, Board 80, etc. routinely — that is normal. Hector's 90-day analysis confirmed 518 entries spanning many boards. 2. **NEW ticket creation — board depends on CLIENT:** - **SCHARP or Ability First, CIO-level work** -> Board 80 (vCIO). - **All other clients** (DTLA, Karney, Anderson, Alere, Cotsen, Irongate, Weingart, Beta Bionics, Mobility, Arc, Crimson-internal, anything non-SCHARP-non-AF) -> **Board 58 Implementation (MS)**. 3. **SCHARP/AF non-CIO work** (e.g. helpdesk-level, L1 assist) — post to the existing helpdesk/project ticket on its native board. Do NOT force to Board 80. **Board reference (from 2026-04-23 CW query):** - Board 44: Help Desk - Board 53: HelpDesk (MS) - Board 58: Implementation (MS) — **DEFAULT for non-SCHARP/AF new tickets per Christi** - Board 60: Implementation (SEC) - Board 62: HelpDesk (TS) - Board 63: Implementation (TS) - Board 65: Recurring Proactive (MS) - Board 71: Administrative (DO NOT USE for Christi's work per superseded rule) - Board 80: vCIO (SCHARP + AF CIO work only) Applies to Dewey + Hector + anyone reconstructing or logging Christi's time.