AI Enablement Engagement

Session 2 — Strategy & Governance Workshop (Detailed Agenda)

Total Duration: 2 hours (120 minutes) Phase / Week: Phase 1, Week 2 Format: Working session with shared document review and live editing Required attendees: Dev team lead(s), architect, security stakeholder, eng management

Pre-session prep (Turner)

  • Read the draft AI Development Strategy Document circulated by Nubitz at least 24 hours in advance
  • Be prepared to confirm decisions during the session (or have decision-makers available)
  • Skim the proposed list of representative projects from Session 1

Agenda

0:00 – 0:10 (10 min) — Re-orient and frame the decisions to be made

  • Lead: Nubitz
  • Format: Briefing
  • Surface the open questions in the draft strategy document. List the decisions we want made by the end of the session.

0:10 – 0:40 (30 min) — Strategy document walkthrough and feedback

  • Lead: Nubitz, with Turner reacting
  • Format: Live document review
  • Walk the document section by section. Capture edits and dissent in real time. Park items that need offline follow-up but flag them.

0:40 – 1:05 (25 min) — Governance framework co-design

  • Lead: Joint
  • Format: Working session
  • Define use-tiers: where is AI use unrestricted, where does it require human review, where is it disallowed? Define minimum standards for AI-touched code (review, attribution, secrets). Capture as a one-page guardrails artifact.

1:05 – 1:15 (10 min) — Break

1:15 – 1:35 (20 min) — Context-management framework for the learning bed

  • Lead: Nubitz, presenting
  • Format: Demo + discussion
  • Walk through the proposed shape of CLAUDE.md, AGENTS.md, and SKILL.md as it will be implemented on the learning bed product, and how the same pattern templates out to Turner's other products. Decide on ownership, versioning, and maintenance.

1:35 – 1:50 (15 min) — Speed-vs-risk and adoption roadmap

  • Lead: Joint
  • Format: Discussion + prioritization
  • Look at the high-velocity practices the team wants to adopt on the learning bed. Stack-rank against the risk view from Session 1. Pin down what gets implemented in Phase 2 versus what Turner extends post-engagement.

1:50 – 2:00 (10 min) — Sign-off and Phase 2 setup

  • Lead: Nubitz
  • Format: Synthesis
  • Confirm sign-off on the strategy document and configuration-asset specifications. Confirm Session 3 logistics: developer access, learning bed repo cloned by every attendee, Claude licensing provisioned.

What Nubitz produces after this session

  • Finalized AI Development Strategy Document
  • Finalized configuration-asset specifications (CLAUDE.md / AGENTS.md / SKILL.md scope)
  • Phase 1 invoice trigger

Risks to manage

  • Endless re-litigation of strategy points: time-box discussions; park anything that doesn't have a decisio