Technology Deep Dive — Section 19 of 20

Human Review Integration

AI workers that know when to ask for help. Seamless escalation to humans with SLA enforcement, zero context loss, and automatic resume.

Uniform interfaceSLA enforcementSuspend-resume

Uniform Interface

In Kaidera, human reviewers and AI workers share the same routing interface. A human is registered with execution_mode='human' and appears in the project roster alongside AI workers. The system routes tasks based on capability, role, availability, and review authority.

Sophi
AI Worker
Execution: autonomous
Autonomy: Level 3
Domain: Backend engineering
Sarah (Legal)
Human Reviewer
Execution: human
SLA: 24 hours
Domain: Contract review

Live Escalation Simulation

AI Worker (Sophi)
Human Reviewer (Sarah - Legal)
AI Working
Escalation Trigger
Context Packaged
Human Review
Decision Made
AI Resumes
Task Complete
SLA Timer (24h window)
0%
Monitoring (Task scheduler: 5 min)
Context Preserved (Redis)
Conversation history (12 messages)
Partial code review (3 files)
Compliance check needed: GDPR clause
Worker state: awaiting_legal_review
Zero information loss on suspension
AI → Human Escalation Flow

Escalation Protocol

When an AI worker reaches its autonomy limit or encounters a task that requires human judgement, it escalates automatically. The routing engine matches the task to the right human by role — business analyst, architect, legal, compliance.

1
AI detects escalation trigger
Task exceeds autonomy level, confidence too low, or requires human approval
2
Context packaged
AI saves complete state to Redis breadcrumb — conversation history, partial work, decision point
3
Route to human by role
Matching engine selects the best available human reviewer based on role, availability, and SLA
4
Human reviews and decides
Approve, reject with feedback, or complete the task manually
5
AI resumes with outcome
On approval, AI continues from exact point of suspension. On rejection, AI adjusts approach.

SLA Enforcement

Every human task has a configurable SLA window. The system sends automatic reminders when time is running out, escalates on breach, and tracks response metrics for accountability.

REMINDER
75%
of SLA window elapsed
BREACH
100%
escalated to manager
MONITORING
5 min
Task scheduler check interval

Suspend-Resume Pattern

When an AI task is escalated, the worker suspends cleanly. All conversation context, working memory, and partial results are preserved in a Redis breadcrumb. When the human responds, the worker resumes from the exact point of suspension — zero information loss.

AI running
Suspended
Human review
AI resumes
Context preserved across suspension boundary — conversation history, partial work, decision rationale

Built on Background Task Scheduling

Human review task scheduling runs on a background task scheduler with Redis as the message broker. A dedicated periodic scheduler checks SLA windows every 5 minutes, sends reminders, and triggers breach escalations — all without any manual intervention.

GOOGLE A2A PROTOCOL

AI workers and human review endpoints can expose A2A-compatible Agent Card metadata when cross-platform discovery is required. This enables standardised discovery and handoff communication across organisational boundaries.

K8S DEPLOYMENT

Task worker and scheduler run as separate Kubernetes deployments alongside the API and frontend. Each pod is non-root (UID 1001), resource-limited, and monitored via ArgoCD GitOps.

Next in Series — Section 18/18
Preview

Code From Your IDE

Your AI worker team lives in the platform — but your developers live in their editor. Section 16 bridges the gap: native VS Code extension, MCP server protocol, and an OpenAI-compatible API that works with any IDE.

Explore IDE Integration

Compatible Environments

VS Code
v0.1.2 · Native extension
Extension
Cursor
OpenAI-compatible API
API
Windsurf
MCP server protocol
MCP
Antigravity
MCP server protocol
MCP
Zed
OpenAI-compatible API
API
Any IDE
via OpenAI-compat API
API

The VS Code extension is available now on the VS Code Marketplace. MCP-compatible IDEs connect via the Kaidera MCP server endpoint. Any IDE with OpenAI API support works via the compatibility layer.