AI Automation Stack

How it works

1. 1Fetches today's calendar via Microsoft Graph API
2. 2Pulls top unread emails, cross-references with meetings
3. 3Searches the web for AI news from the past 24 hours
4. 4Formats and delivers calendar+email briefing at 6:25 AM
5. 5Formats and delivers AI news briefing at 6:35 AM

How it works

1. 1Fetches recent emails via Microsoft Graph API
2. 2Filters out automated notifications, calendar invites, ServiceNow alerts
3. 3Scores remaining emails by: sender seniority, action language, thread activity
4. 4Delivers a clean 'Needs Your Reply' list to Telegram at 5:30 PM

How it works

1. 1Uses Google OAuth with gmail.readonly scope only
2. 2Searches recent personal Gmail messages for school, district, teacher, attendance, permission, and deadline signals
3. 3Scores messages by action terms, sender patterns, unread status, and low-priority newsletter signals
4. 4Saves a local markdown brief and sends a concise Telegram summary only when something needs attention

How it works

1. 1Scans email for project milestones, wins, and notable outcomes
2. 2Reads Teams channels: AI Use Cases, TritonAI Internal, AI Admin Workgroup
3. 3Checks 1:1 chats with direct reports and key stakeholders
4. 4Drafts two posts: one use case walkthrough, one outcome/numbers post
5. 5Delivers to Telegram for review — reply 'post 1' or 'tweak 1: [notes]'

How it works

1. 1Searches the web for institutional AI deployments at peer universities
2. 2Monitors AI vendor and platform news targeting higher education
3. 3Tracks governance, policy, and compliance developments
4. 4Flags early signals relevant to TritonAI roadmap
5. 5Delivered to Telegram every Sunday at 8:00 AM

How it works

1. 1Loads Brett's knowledge graph (people, projects, relationships)
2. 2Loads UCSD data source catalog (available campus systems)
3. 3Researches recent higher ed AI use cases and campus technology innovations
4. 4Scores ideas against impact, feasibility, Brett relevance, data availability, and competitive urgency
5. 5Surfaces the single highest-scoring idea with required data sources and build complexity
6. 6Delivers to Telegram — reply with a number to act on the finding

How it works

1. 1Reviews the day's activity and conversation context
2. 2Identifies friction points and wins
3. 3Cross-references emails needing reply
4. 4Surfaces tomorrow's calendar highlights
5. 5Delivered to Telegram at 5:30 PM with the email triage

How it works

1. 1Team screen: mission statement, agent org chart, live force-directed system graph (HTML Canvas)
2. 2Tasks: Kanban board (Backlog/In Progress/Blocked/Done) + live activity feed, heartbeat-integrated
3. 3Calendar: all cron jobs visualized with live status from OpenClaw
4. 4Projects: 6 campus initiatives with 'What can we do right now?' reverse-prompting via Claude
5. 5Memory: daily journal browser + long-term memory editor reading from workspace files
6. 6Docs: searchable markdown library scanning the full workspace directory
7. 7Custom tools: TritonAI Adoption Pulse (dept grid) + Executive Decision Queue (pending approvals)

How it works

1. 1Built with Software Blueprint — Next.js App Router, MUI color system, CSS Modules
2. 2Live automation status fetched from OpenClaw cron API at page load
3. 3Hourly GitHub push from Mac mini keeps Vercel deployment current
4. 4Password-protected via NextAuth.js — single owner access
5. 5Each card shows last run, next run, and delivery status in real time

How it works

1. 1Planning Agent uses Claude Opus as primary reasoner to write PLAN.md and lock storage, API surface, and data decisions
2. 2Architect Agent uses Claude Opus to turn PLAN.md into a detailed SPEC.md with design, accessibility, and implementation guidance
3. 3Builder Agent uses Codex / GPT-5.4 as primary code generator, with Claude Sonnet fallback and Nemotron for compliance-sensitive builds
4. 4QA runs deterministic npm/build checks first, with optional Claude Sonnet error analysis only when failures occur
5. 5Deploy uses CLI automation for GitHub and Vercel, with optional Claude Sonnet debugging on deployment failures
6. 6Docs uses local Gemma 4 on the Mac mini for boilerplate and Claude Sonnet for final polish

How it works

1. 1Searches the web for AI news from the past 24 hours
2. 2Filters for higher education, enterprise AI, and governance topics
3. 3Ranks stories by relevance to TritonAI and UC San Diego strategy
4. 4Summarizes top 3-5 items in plain language for fast intake
5. 5Delivered to Telegram each morning

How it works

1. 1Reads email from past 30 days via Microsoft Graph
2. 2Cross-references against known stakeholder list
3. 3Flags contacts with no interaction in 2+ weeks
4. 4Groups by relationship type: direct report, peer, vendor, external
5. 5Delivered to Telegram every Friday at 4:00 PM

How it works

1. 1Searches Reddit (r/UCSD, r/college, higher ed forums)
2. 2Scans for service complaints, workaround threads, tool requests
3. 3Categorizes signals: VPN, Wi-Fi, Canvas, TritonLink, email, printing
4. 4Surfaces top 3-5 pain themes with example quotes
5. 5Delivered to Telegram daily at 7:30 AM

How it works

1. 1Searches UC campus job boards daily at 8:00 AM
2. 2Filters for IT leadership roles above $250K compensation
3. 3Covers southern campuses: UCLA, UC Irvine, UC Riverside, UC Santa Barbara
4. 4Flags new postings and role changes since last run
5. 5Delivers Telegram summary with titles, campuses, and links

How it works

1. 1Runs at 2:00 AM Tuesday and Friday
2. 2Reviews task backlog for quick wins
3. 3Checks henry-dashboard and henry-api for code quality issues
4. 4Scans workspace for stale or orphaned files
5. 5Commits and pushes improvements to GitHub

How it works

1. 1Runs the Granola feeder to sync today's meetings
2. 2For each meeting, fetches the full note with transcript from Granola API
3. 3Extracts key decisions, action items with owners, and Brett's commitments
4. 4Applies context-aware filtering: only creates tasks where Brett is the driver
5. 5Posts filtered action items as backlog tasks in Mission Control
6. 6Saves a clean debrief markdown file to workspace/docs/

How it works

1. 1Checks if tax deadline has passed
2. 2If not past deadline, sends a direct nudge via Telegram
3. 3Increases urgency if it's been more than a week since last reminder
4. 4Automatically disables after April 15

How it works

1. 1Fetches all tasks from the Mission Control API
2. 2Filters for tasks with status 'backlog'
3. 3Formats them as a numbered list with title, date, category, and priority
4. 4Sends the list to Brett via Telegram
5. 5If no backlog tasks, sends: '📋 No backlog tasks currently.'

How it works

1. 1Checks for existence of today's calendar briefing markdown file
2. 2Checks for existence of today's AI news digest markdown file
3. 3Checks for existence of today's opportunity scan markdown file
4. 4If any are missing, alerts Brett with: '☕ Morning briefing gap — [missing items]. Likely cause: Graph token expired or cron timed out. Check `openclaw cron list`.'
5. 5If all present, replies silently with HEARTBEAT_OK

How it works

1. 1Checks the Henry backlog for enhancement tasks (task-henry-enh-001 through task-henry-enh-005 and follow-ons)
2. 2Picks the highest-priority not-done item
3. 3Moves it to in-progress if possible
4. 4Completes one substantial implementation increment
5. 5Updates task notes/status
6. 6Announces a concise progress summary to Brett

How it works

1. 1Checks these repos for uncommitted changes: workspace, mission-control-app, henry-api, henry-dashboard
2. 2For each repo with changes: runs `git status --porcelain`
3. 3If any repo has uncommitted changes: auto-commits with message 'chore: auto-save uncommitted work (weekly watchdog)' and pushes
4. 4Messages Brett with what was committed: '💾 Weekly save — committed uncommitted changes in [repos]. All pushed.'
5. 5If everything is clean: replies HEARTBEAT_OK (no message)

How it works

1. 1Keeps https://brettcpollak.com/ai-digest showing the current Monday-anchored week's digests
2. 2Ensures website version remains PUBLIC-FACING: removes personal/internal framing
3. 3Omits missing digest days rather than inventing content
4. 4If no content changes: exits without committing
5. 5Uses exact paths: workspace digest source → /Users/brettpollak/.openclaw/workspace/docs
6. 6Site repo local clone → /tmp/brettpollak-website
7. 7Site repo remote → https://github.com/bpollak/brettpollak-website.git
8. 8Steps: clone/pull, run update script, preserve public-safe rendering, check for changes, build and push if changed

How it works

1. 1OAuth device flow authentication via Microsoft tenant
2. 2Delegated permissions: Mail.Read, Calendars.Read, Chat.Read, ChannelMessage.Read.All
3. 3Token auto-refreshed hourly to maintain access
4. 4Feeds data to: Morning Briefing, Email Triage, LinkedIn Machine, Evening Reflection

How it works

1. 1Gemma 4 27B running via Ollama on Mac mini
2. 2Apple Metal GPU acceleration
3. 3Registered as a model provider in OpenClaw
4. 4Switch with /model gemma4 — switch back with /model sonnet

How it works

1. 1Extracts entities from email, meetings, and documents
2. 2Maps relationships: reports-to, works-with, vendor, peer, partner
3. 3Rebuilds nightly at 6:20 AM to capture recent additions
4. 4Stored as JSON at data/knowledge-graph.json
5. 5Powering semantic lookups in Meeting Prep, Opportunity Scan, and Briefings

How it works

1. 1Determines the currently installed OpenClaw version
2. 2Checks whether a newer OpenClaw version is available
3. 3If no update: appends brief no-update note to changelog (if none in past 3 days)
4. 4If update available: runs official OpenClaw self-update
5. 5Captures old and new versions
6. 6Summarizes important changes in plain English
7. 7Appends dated entry to OpenClaw changelog
8. 8Also appends short note to today's daily memory file
9. 9On failure: appends failure note and notifies Brett via Telegram

How it works

1. 1Run `openclaw cron list --json` and check all jobs
2. 2List any jobs with errors or that haven't run successfully in the past 7 days
3. 3List any disabled jobs that might have been accidentally turned off
4. 4Check for jobs with repeated timeouts (look at recent run history if available)
5. 5Send Brett a brief Telegram summary ONLY if there are problems. Format: '🔧 Weekly Cron Audit — [N] issues found:' then bullet each problem with job name and what's wrong.
6. 6If everything looks healthy, reply HEARTBEAT_OK (no message to Brett)

How it works

1. 1Read AGENTS.md, knowledge-graph.json, ucsd-data-sources.json, MEMORY.md, PATTERNS.md
2. 2Run `openclaw status` and `openclaw cron list` to get system state
3. 3Analyze and report on 11 areas: cost efficiency, reliability, data freshness, token usage patterns, missing capabilities, security posture, OpenClaw updates, performance, memory consolidation, pattern review, skill audit
4. 4For each area, rate: 🟢 Healthy / 🟡 Needs Attention / 🔴 Action Required
5. 5End with a prioritized list of 3-5 concrete recommendations
6. 6Save to /Users/brettpollak/.openclaw/workspace/docs/architecture-review-$(date +%Y-%m-%d).md

How it works

1. 1Read AGENTS.md to find the Orchestration Assessment and pipeline stages
2. 2For each stage, assess: (1) Is this stage still catching real issues? (2) Has a model upgrade made this stage redundant? (3) Can it be simplified or merged? (4) What's the token/cost overhead?
3. 3Also check: Are context resets still needed? Is the Evaluator actually rejecting bad work? Are Office Hours adding value?
4. 4Produce a brief report with recommendations: KEEP / SIMPLIFY / REMOVE for each stage
5. 5Save to /Users/brettpollak/.openclaw/workspace/docs/harness-review-$(date +%Y-%m-%d).md