Generated by Viktor · Monday 23 March 2026 · All elements, schedules, and efficiency review
System Elements — What You're Managing
| Cron | Schedule | What It Does | Data Sources | Frequency |
|---|---|---|---|---|
| Build Window Defender | 08:00 Mon–Fri | Checks if AM meetings block the 09:20–11:30 Build window. Posts only if blocked. | Calendar (VIKTOR-FEED) | Daily |
| Monday Carry-Forward | 08:30 Mon | Surfaces unfinished tasks and deferred items from prior week. Monday clean-slate. | tasks.yaml, waiting-for.yaml | Weekly |
| Meeting Prep Agent | 08:30 Mon–Fri | Scans today's calendar, posts 60-second meeting prep for each meeting with no prep file. | Calendar, agendas/, stakeholders | Daily |
| Direct Reports Pulse | 08:45 Mon–Thu | Quick W/F signal per direct report (Gary, Seamus, Gavin, Conleth, Robert). Flags overdue. | waiting-for.yaml | Daily (Mon–Thu) |
| Morning Briefing | 09:00 Mon–Fri | Full daily HTML brief: tasks, W/F, objectives, meetings, stakeholders, training, signals. | All files + calendar + email + web | Daily |
| Monday W/F Review | 09:30 Mon | Full waiting-for health check. Ageing, owner grouping, risk flagging. | waiting-for.yaml | Weekly |
| Tuesday Objective Alert | 09:00 Tue | Lightweight mid-week signal: any Red objective falling behind or milestone approaching. | active-objectives.yaml | Weekly |
| OKR & Topics Visual Refresh | 10:00 Tue & Thu | Refreshes H1 OKR progress visual + DR/OKR intelligence topics. Added today. | active-objectives.yaml, topics config, OKR data | 2×/week |
| Lunch Training Nudge | 12:15 Mon–Fri | Smart: only fires if training target is behind or a lunch run opportunity exists. | training-log.json, calendar | Daily (smart) |
| Midday Scan | 13:00 Mon–Fri | Read-only urgent scan: priority DMs, @mentions, unread from Elias/Kevin/Lee. No YAML writes. | Slack (live), Outlook unread | Daily |
| Objective Pulse (Mid-Week) | 11:00 Wed | Deeper objective check-in at mid-week. Reviews all Now-horizon objectives. | active-objectives.yaml | Weekly |
| Wednesday W/F Chase | 11:30 Wed | Mid-week W/F review. Surfaces overdue items, suggests chase messages. | waiting-for.yaml | Weekly |
| EOD Summary | 17:00 Mon–Fri | End-of-day full close-out. Reviews tasks, W/F, emails, Zoom AI. Generates EOD briefing HTML. | All files + calendar + email + Slack scan | Daily |
| Thursday Prep Scan | 17:30 Thu | Friday prep: surfaces key tasks, meetings, and prep gaps for the next day. | tasks.yaml, calendar, meetings/prep/ | Weekly |
| Friday W/F Close | 11:30 Fri | End-of-week W/F close sweep. Marks resolved items, updates aging. | waiting-for.yaml | Weekly |
| Friday Weekly Review Pre-Pack | 09:30 Fri | Full weekly review: closed tasks, open objectives, W/F health, next week setup. | All files + weekly review template | Weekly |
| Weekly Intelligence Digest | 20:00 Sun | Strategic intel sweep: iGaming news, GAMB performance, AI finance, sector signals. | Web search, configured topics | Weekly |
| Task Scanner | Every 30min, always | Parses commands from #niall: done, defer, wf done, agenda adds, prep requests. Executes silently. | Slack #niall | Always On |
objective: field in tasks.yamlBuild Window Defender, Lunch Training Nudge, and Midday Scan all have conditional logic — they only post if something genuinely needs attention. This is exactly right. Reduces noise, preserves signal value.
Viktor (automated crons) and Cowork (deep reasoning, YAML writes) have clearly split responsibilities. The VIKTOR-FEED bridge keeps them in sync without coupling. GTD best practice: one trusted system, no duplicate ownership.
87 open W/F items are a real management burden. Dedicated Mon review + Wed chase + Fri close means every item cycles through at least once per week. This matches GTD's "nothing falls through the cracks" principle.
30-minute command parser means Niall can fire "done T045" mid-meeting and the system updates immediately. No backlog of manual YAML edits. This is the key speed advantage of Viktor integration.
You have 4 objective-focused touches per week: Tue Alert (09:00), Wed Objective Pulse (11:00), and OKR Refresh (Tue/Thu 10:00). Tue has two objective signals in one morning. Consider: does the 09:00 Tue Alert add distinct value vs the 10:00 OKR Refresh that runs 30min later?
GTD recommends regular W/F pruning — not just weekly sweeps. Items with no expected_by date (several exist) are invisible to urgency logic. Consider: once/month W/F audit to close or date-stamp stale items. Currently no cron for this.
The pulse skips Friday, but Fri is when the weekly review runs. This is probably intentional (weekly review covers it), but worth confirming the weekly review explicitly surfaces per-direct-report W/F signals vs the daily pulse format.
The Weekly Intelligence Digest runs Sunday 20:00 — which is good timing before Monday. However, it's currently isolated from the OKR/Topics workflow. Confirm: does the Digest explicitly reference the DR/OKR topics visual updated today? If not, there's an opportunity to link them.
09:20–11:30 Build window is sacred. Build Window Defender at 08:00 checks for blockers. Morning Briefing caps Build tasks at 3. No cron fires during the Build window itself. The system actively defends deep work time — this is the most important GTD principle for senior leaders.
With OKR Refresh added today (Tue/Thu 10:00), your H1 priorities get a dedicated checkpoint twice weekly. This bridges the gap between daily task management and quarterly objective tracking — exactly what was missing.
Several W/F items have no expected_by date set. The chase and review crons are date-anchored — undated items are invisible to urgency filtering. Quick fix: monthly "W/F date audit" command or a cron that surfaces undated open items.
T136 was added with type "action" — but the system's task types are Build / Align / Solve. This means it won't appear in Build block logic correctly. Recommend reclassifying: T136 is likely type=align (requires input from Casinos team) or solve. Viktor can update this now.
stakeholder-matrix.yaml was last updated 2026-02-27. Several check-in dates are now past. Elias's check-in was due 2026-03-21. The system can't surface outreach prompts for stale stakeholders if the matrix isn't current. Weekly review is the right moment to update this.