Executive Overview
59% complete — 59 of 100 items delivered across 6 workstreams. (+6 new issues filed from Mar 23 Office Hours call, +2 done since last update: ThreatConnect integration done, SMK v1.0.3.1 released. Okta write tools moved to Agency team; Okta bug fixed. MITRE ATT&CK canceled.)
Cyber workstream most active with 28 open items; task worker reliability is URGENT. Key integration fixes shipped. SMK v1.0.3.1 released. SMK Installs +6 new items today.
Dashboards
Each dashboard tracks a different class of work across the Deloitte engagement.
What Needs Attention Now
Critical items surfaced from the most recent Deloitte call (Mar 23 Office Hours).
Task Worker Heartbeat Loss — URGENT
Task worker loses Hatchet heartbeat and silently stops processing. Second occurrence. Known bug — Kindo engineering confirmed as highest priority. Patch being coordinated. No application logs available to diagnose root cause. ENG-8920
No Application Logging in Self-Managed Deployment
Deloitte's SMK deployment has zero permanent log storage for container/application logs. When task worker died, nothing to investigate. CloudWatch Logs setup required via K8s add-on — Kindo's turnkey installer includes this, but Deloitte's custom deployment does not. ENG-8924
White-Label Logo Not Rendering
Deloitte's logo hosted in S3 bucket is not displaying in the Kindo portal. Suspected CORS issue. Fix call scheduled: Marcos + Nate at 1:30 PM PST today. ENG-8921
ServiceNow OAuth2 Connection Failure
OAuth2 connection fails while REST API works with same credentials. Now assigned to Yash Kothari. Blocks IAM POC completion. ENG-8794
Engagement Information Flow
Full mind map showing all request sources, classifications, and resolution paths across the Deloitte engagement.
Resource Gap Analysis
Current capacity vs. demand across the Deloitte engagement.
Capacity vs. Demand
👥 Current Capacity (~2 FTE)
- Tony Wong — Chief Delivery Officer, relationship management, scope governance, stakeholder alignment
- Joana Dias — Program coordination, meeting management, dashboard & portfolio tracking
- Kindo Engineering — Shared across all customers; Deloitte-specific allocation is fractional
- Agentic Pipeline — AI-assisted engineering for implementation, monitoring, and triage
- Marcos Pagnucco — Infrastructure (deployment, K8s, ALB) — shared resource
📋 Active Demand (6–7 Groups)
- Cyber / Adelina — 28 open items, most active workstream, RSA prep, Canvas decisions, agent reliability
- IAM / J&J — 2 remaining items, audit logging and multi-agent research
- IAM POC (SailPoint/Entra) — 1 blocker (ServiceNow OAuth2)
- Meta Global Ops — 10 items, entirely unresourced, needs RACI + squad before any work
- SMK Deployments — 7 planned deployments across Deloitte, each with environment-specific issues
- Training Program — LMS build, video production, pilot session, live training coordination
- Ongoing Triage — Every call surfaces new bugs, config questions, and feature requests (6 new items from today alone)
The math doesn't work at current capacity. Every Deloitte meeting — Office Hours, Cyber Weekly, ad hoc calls — generates new bugs, configuration requests, and feature asks. With ~2 FTE against 6–7 active groups of work, the engagement is in sustained triage mode rather than proactive solution development.
Two paths forward: (1) Deloitte assigns a dedicated program manager to centralize request flow and prioritization across their teams, or (2) Kindo's agentic system connects to Deloitte's Microsoft Teams to manage triage, routing, and status tracking programmatically. Either way — someone or something needs to own the coordination layer. The current ad-hoc model cannot scale to 7 SMK deployments.
Kindo can scale the delivery capacity up to 25 people via the agentic development pipeline. But the methodology, system design, and management expertise that make this possible cannot be replicated by adding headcount alone — it took decades of leadership experience to build.