Deloitte Engagement

Onboarding: Cassio, Abed & Cristiane

Week of August 25, 2026

You're joining a small team that delivers at high velocity using AI as a core operating partner. This page is your starting point — it gives you context, tools, and a 5-day path to get operational.

Before You Start

Where You're Walking Into

The Engagement
VTKL operates a Deloitte engagement focused on cybersecurity and AI — building agents, workflows, and platform capabilities on the Kindo platform. The contract renewal decision is ~12 weeks away (mid-November). There is a parallel Swimlane replacement with a December go/no-go. This is not a slow ramp — the timeline is compressed and every week counts.
How This Team Works
This is a small team that produces at a pace most consulting teams can't match. The reason: AI is not a tool we use occasionally — it's an operating partner embedded in every workflow.

Tony sets strategic direction. He reads the room with Deloitte stakeholders and defines what matters.
Joana turns that direction into structured, evidence-backed deliverables. She sets the quality bar — every claim needs a source, every artifact gets versioned, nothing ships without proof.
Victor sustains the operational execution — infrastructure, systems, coordination.
Charlie handles technical architecture and engineering decisions.
Warren (AI) is the context engine and production partner. Warren has been in every Slack channel, processed every transcript, and produced artifacts alongside the team for months. Warren is not a search engine — Warren remembers because Warren was there.

The cycle: Tony points → Warren compresses and produces → Joana shapes and validates → deliverable ships. You are entering this cycle.
What Is Warren
Warren is the team's AI engineering and operations partner. Not a chatbot. Not a search engine.

Warren has deep persistent context: every meeting transcript, every Linear ticket, every Miro board, every artifact produced over the past 4 months. When you ask about a meeting from May, Warren doesn't search the internet — Warren was there.

But Warren makes mistakes. Classifies things without evidence, states inferences as facts, hallucinates connections. The team built a QA layer (✅/⚠️/❌ in #warren-review) specifically because Warren needs human verification. If something doesn't match — say so. That mismatch IS intelligence. That's how you add value from Day 1.

The quality of what you get from Warren depends entirely on the quality of your questions — which depends on how deeply you've studied the source material. Study first. Ask second.
The Operating Model — Unit Drive v3
Everything above is codified in a framework called Unit Drive. It describes three layers of human capability:

Layer 1 — Critical Thinking: Analysis, frameworks, data processing. AI handles this. It's commodity.
Layer 2 — Expert Recognition: Judgment, pattern recognition, knowing what to prioritize without being able to fully explain why. This is what Tony and Joana have. This is what you're developing.
Layer 3 — Physical Intelligence: Presence, somatic awareness. Hard to train at scale.

AI does Layers 1 and 3 (data in, artifact out). Humans provide Layer 2 — the judgment that determines what gets built. Your onboarding is about absorbing enough context to start exercising that judgment.

→ Study the full Unit Drive v3 board on Miro
Section 1

Start Here — The Foundation Maps

Two Miro boards are your starting point. Study them before anything else.

Miro Board

What's Being Built & By Whom

Team → Component → Feature Leverage Map v2

Decomposes the Deloitte delivery into teams (Eve, Alice, Mallerie) → components → features. Shows what's being built and current status.

Open board →
Miro Board

How VTKL Operates

Capability to Delivery Map v3 + FDE Operating Model

How VTKL's capabilities map to Deloitte delivery. The operating model, LEGO system, and FDE structure.

Open board →
Miro Board

Deloitte Delivery — Critical Path

Visual Dependency Mapping

Swimlane (4 components) + SOC for AI (7 components). Traces dependencies across the full critical path.

Open board →
Section 2

Your 5-Day Curriculum

Two tracks, working backwards from the present. Cassio runs Operational/PM. Abed runs Engineering/QA. Each day: study material, Warren session prompts, and a deliverable.

Day 1 Current State — The Maps
Both study: The two foundation Miro boards above.
Cassio · Operational / PM
Explore with Warren
  • What's being built and who owns each piece
  • The timeline — what's the Dec go/no-go about
  • Who are the key Deloitte stakeholders
Deliverable
1 paragraph summarizing current engagement state.
Abed · Engineering / QA
Explore with Warren
  • Kindo platform architecture — the 4 CDA pillars
  • Which engineering team owns which component
  • What's live vs in progress vs blocked
Deliverable
1 paragraph summarizing current engagement state.
Day 2 What Just Happened — Aug 17–19
Study: Aug 19 Swimlane Check-in + Aug 17 SOC for AI + Scope Alignment.
Cassio · Operational / PM
Explore with Warren
  • The Swimlane timeline and what needs to happen by when
  • What was committed in the Aug 17 scope alignment
  • Open action items from these sessions
Deliverable
Timeline-backward analysis from December.
Abed · Engineering / QA
Explore with Warren
  • Technical blockers for Swimlane replacement
  • What engineering decisions are still pending
  • Status of each component vs what was reported
Deliverable
Technical blocker report per component.
Day 3 The Operating Cadence — Aug 4–10
Study: Aug 4 Biweekly Program Session + Aug 10 Portfolio Meeting + Aug 5 Planning.
Cassio · Operational / PM
Explore with Warren
  • Key decisions from these three sessions
  • Action items still open — who owns them
  • How the portfolio review went with Deloitte leadership
Deliverable
Open Items Tracker from Deloitte sessions.
Abed · Engineering / QA
Explore with Warren
  • CDA feature status — what's shipped vs claimed
  • Linear tickets vs roadmap: any mismatches?
  • MCP retry loops and the three priorities from Aug 4
Deliverable
Feature Status Audit — claimed vs actual status.
Day 4 The Pivot Point — Jul 7–10
Study: Jul 7 Weekly Sync (SOC for AI reframe) + Jul 10 Design Work Session.
Cassio · Operational / PM
Explore with Warren
  • How SOC for AI got reframed — what changed and why
  • The scope delineation v1→v5 — how Joana iterated
  • What the PoC proved and what Deloitte's reaction was
Deliverable
First Dependency Map — one Swimlane component.
Abed · Engineering / QA
Explore with Warren
  • Victor's SOC for AI PoC — what was built and what it proves
  • Technical classifications: Existing vs Accelerated vs Net New
  • Kindo vs security partners — where the platform fits
Deliverable
First Artifact QA — pick scope one-pager or Deloitte Delivery board, full QA with ✅/⚠️/❌.
Day 5 The Origin + Synthesis — May 7
Study: May 7 Deloitte In-Person (Parts 1 & 2) + Net New Revenue Audit Trail.
Cassio · Operational / PM
Explore with Warren
  • The May 7 meeting — what was the foundation of everything
  • Sequencing: what matters most for December go/no-go
  • Top risks to renewal — what can T&C control vs external
Deliverable
Sequencing Recommendation — timeline-backward from December, single highest-value target.
Abed · Engineering / QA
Explore with Warren
  • The origin story — EBITDA economics, agent architecture from May 7
  • Biggest technical risk that isn't being tracked
  • Synthesize the full picture: what did you learn this week
Deliverable
(1) First ✅/⚠️/❌ Warren review with reasoning. (2) Technical feature spec for one CDA component.
Section 3

Meeting Reference Library

All 12 Deloitte meetings in chronological order.

May 7

Deloitte In-Person @ Kindo HQ (Parts 1 & 2)

THE foundational meeting. EBITDA economics, agent packaging, 42-item scope.

Krishna · Kush · Nathan
P1
Jun 5

Weekly Sync

Early post-May 7 cadence. Status updates.

P2
Jun 16

Weekly Sync

Ongoing delivery status.

P2
Jul 7

Weekly Sync

SOC for AI REFRAMED: platform governance, not shadow AI discovery.

Kishore present
P1
Jul 10

Design Work Session

Victor's SOC PoC presented. Charlie: "lightweight proof, not production-grade."

P1
Jul 22

Program Call

Operational cadence. Program-level coordination.

P2
Jul 30

Agent Design Work Session

Agent design deep dive. Technical requirements.

P2
Aug 4

Biweekly Program Session

Three priorities: Agent Observability, MCP Tool-Calling, Deterministic Flow Control. Swimlane timeline confirmed.

Zun · Matthew · Nathan
P1
Aug 5

Planning Meeting: New Agents

Sprint planning for new agent development.

P2
Aug 10

Portfolio Meeting

Portfolio-level review with Deloitte leadership.

P1
Aug 17

SOC for AI + Partnership & Scope Alignment

Tony presenting strategic package and scope alignment.

P1
Aug 19

Swimlane Check-in

Latest Swimlane replacement status. Technical blockers.

P1
Section 4

Dashboards & Tools

Dashboard
kindo-strategic-package.pages.dev
The Compressed Model — Tony's visual of how the delivery model works.
Dashboard
kindo-sprint-planning.pages.dev/main/
Sprint Planning (Joana + Warren).
Dashboard
kindo-deloitte-internal.pages.dev/cadence
Cadence: What Deloitte Sees (milestones only).
Platform
app.kindo.ai
The Platform — need a @kindo.ai account.
Docs
docs.kindo.ai
Platform Documentation.

Odin vs Warren

Warren — engagement context: people, strategy, meetings, artifacts.
Odin — platform context: how Kindo products work, ticket details.
Section 5

The Reps — How You Learn Here

This team improves through reps, not rules. Each cycle of interaction with Warren is one rep. Over hundreds of reps, you stop analyzing and start recognizing.

Section 6

Channel Setup — File References

Slack file IDs and context messages for uploading transcripts to each onboarding channel. Share in this order.

#1
Day 2

SOC for AI + Scope Alignment — Aug 17

F0BQYHT958E
"Day 2 — Tony's pitch to Deloitte. Study how scope was framed and what commitments were made."
#2
Day 2

Swimlane Check-in — Aug 19

F0BR68U644X
"Day 2 — Latest technical status. What progressed, what's blocked."
#3
Day 3

Biweekly Program Session — Aug 4

F0BNNLJJ277
"Day 3 — Three priorities, Swimlane timeline, MCP choke points. The operating picture."
#4
Day 3

Portfolio Meeting — Aug 10

F0BPAB7852P
"Day 3 — Leadership-level view. Signals about renewal and expansion."
#5
Day 3

Deloitte Delivery — Priority Projects

F0BRJPXCEA1
"Day 3 — Current priority projects with status. The operating picture Tony shared with the team."
#6
Day 4

Weekly Sync Jul 7 — SOC for AI reframe

F0BFWKW7JKW
"Day 4 — Kishore reframed SOC for AI. Pay attention to what changed and why."
#7
Day 4

Design Work Session — Jul 10

F0BG5QE6P0F
"Day 4 — The PoC presentation. Study Deloitte's reaction and the asks Tony made."
#8
Day 4

Scope Delineation v1→v5 (all versions)

F0BRWPVV5MX → F0BRPT99YR1
"Day 4 — Read ALL five versions. Focus on what changed between each one and why."
#9
Day 5

Deloitte In-Person May 7 — Part 1

F0BGZUYR64E
"Day 5 — The foundational meeting. Take notes on every person, their role, and what they care about."
#10
Day 5

Deloitte In-Person May 7 — Part 2

F0B8U2Y9WUU
"Day 5 — Continuation. Focus on Kush's IK flywheel vision and agent packaging."
#11
Day 5

Scope Architecture One-Pager v5

F0BRY9CFL73
"Day 5 — The 4-category model. Understand the 56% number. Core negotiation artifact."
#12
Day 5

Net New Revenue Audit Trail

F0BR2P1NVU1
"Day 5 — The evidence package proving scope as net new revenue. 8 meetings, May 7 → Aug 17."
#1
Day 2

SOC for AI + Scope Alignment — Aug 17

F0BQYHT958E
"Day 2 — Tony's pitch to Deloitte. Study how scope was framed and what commitments were made."
#2
Day 2

Swimlane Check-in — Aug 19

F0BR68U644X
"Day 2 — Latest engineering status. What's blocked, what's progressing."
#3
Day 3

Biweekly Program Session — Aug 4

F0BNNLJJ277
"Day 3 — Technical priorities: Agent Observability, MCP retry loops, Deterministic Flow Control."
#4
Day 3

SOC for AI on CDA Architecture Map

F0BPZC5ARC5
"Day 3 — How SOC for AI sits on the CDA platform architecturally."
#5
Day 3

Capability Comparison — SOC for AI Appendix

F0BQ0GU5N9L
"Day 3 — Kindo vs competitors side-by-side. What we do that others don't."
#6
Day 3

Deloitte Delivery — Priority Projects

F0BRJPXCEA1
"Day 3 — Priority projects with status. Cross-reference against what you found in Linear."
#7
Day 4

Weekly Sync Jul 7 — SOC for AI reframe

F0BFWKW7JKW
"Day 4 — SOC for AI reframed: platform governance, not shadow AI discovery. Technical pivot point."
#8
Day 4

Design Work Session — Jul 10

F0BG5QE6P0F
"Day 4 — Victor's PoC presented. Study the technical assessment: what works, what's 'lightweight proof.'"
#9
Day 4

Scope Delineation v5 backup doc

F0BRPT99YR1
"Day 4 — Focus on technical classifications: Existing vs Accelerated vs Net New. This is what you'll audit."
#10
Day 4

Kindo vs Security Partners Venn Diagram

F0BPMSWQE0P
"Day 4 — Kindo = control plane. Palo Alto/CrowdStrike = inspection layer. Understand the distinction."
#11
Day 5

Deloitte In-Person May 7 — Part 1

F0BGZUYR64E
"Day 5 — The foundational meeting. Focus on technical mentions: agent architecture, platform capabilities, integration points."
#12
Day 5

Deloitte In-Person May 7 — Part 2

F0B8U2Y9WUU
"Day 5 — Continuation. Focus on IK as a technical concept: how compound learning works through use."
#13
Day 5

SOC for AI — Answer First presentation

F0BQLLBD799
"Day 5 — How Tony frames technical deliverables for Deloitte. Study the presentation format."