How it works
Your fleet's lifecycle is the backbone. At any moment units live in all six phases at once — each phase is a projection over the same inventory.
01·The operational loop
Every unit in your fleet —any framework, any integration level— runs the same loop in Kordana. That's how control holds when the fleet grows and stacks mix.
Visibility
One inventory that absorbs any framework.
Human escalation
Decisions with context and SLA, not noisy alerts.
Operational control
Audited actions that apply regardless of the stack.
Multi-framework in
Pillar · Visibility
One inventory absorbs L0 (manual) through L3 (deep control) units. LangGraph, CrewAI, in-house agents, wrapped RPA — all appear in the same roster with owner, group and status.
Surface
Fleet roster
Flagship view of Phase 4 · Operation
Pillar · Visibility
The Control Room turns heterogeneous signals into a common status light: which units are active, which need attention, how much they spend, which SLAs they meet — today, not last week.
Surface
Control room
Flagship view of Phase 4 · Operation
Pillar · Escalation
When a unit hits a limit —budget, policy, ambiguity— it escalates to a named human with the full trace: input, pending decision, risk and SLA window. The Inbox is a work queue, not a chat.
Surface
Escalation inbox
Flagship view of Phase 4 · Operation
Pillar · Control
Every control action runs against the underlying framework and is recorded as a signed event: who, when, on which unit, with what justification. Same lever regardless of the agent.
Surface
Unit page · Incidents
Flagship view of Phase 4 · Operation
02·State machine
Every transition requires a named human actor or an explicit policy. Every transition is written to the audit. A new version of an active unit enters through "in trial", symmetric with onboarding.
03·The 6 phases
Phase 01
Decide which units should exist, with what business case and under what governance. The structural antidote to agent sprawl.
Entities
Views
Key metric
Projected vs. real coverage and ROI
Phase 02
Turn an approved request into a Role — the contract between business and implementation — and certify that an implementation meets it.
Entities
Views
Key metric
Request → certification time
Phase 03
Move a certified unit to production with the rigor of an operational hire: identity, access, owner, probation and formal handover.
Entities
Views
Key metric
First-period graduation rate
Phase 04
The heart of the product. Keep the fleet working today: health, work, escalations, control, incidents and costs.
Entities
Views
Key metric
Autonomy rate
Phase 05
The fleet's performance review. Close the loop against the Design KPIs and turn findings into versioned improvements.
Entities
Views
Key metric
KPI compliance by domain
Phase 06
Retire units with the same rigor as onboarding. The phase compliance thanks you for: without it, the fleet accumulates zombie agents.
Entities
Views
Key metric
Live credentials post-retirement (target: 0)
04·V1 scope vs. later
Changing the data model later is expensive. Changing the UI is cheap. V1 focuses on Phase 4 plus the minimum inventory that supports it.
| Capability | V1 | Note |
|---|---|---|
| Unit inventory with states, owners and groups | ✓ | The skeleton of everything |
| L0 (manual) and L1 (telemetry) connectors | ✓ | Minimal-friction entry |
| L2 (stop/play, handoff) on priority frameworks | ✓ | |
| Control room + unit page | ✓ | Flagship views |
| Escalation inbox | ✓ | Retention engine |
| Alerts + operational status | ✓ | |
| Fleet payroll (spend and budget) | ✓ | No projections yet |
| Simplified role (mission, limits, KPIs, owner) | ✓ | |
| Immutable audit of control actions | ✓ | Cheap now, impossible to retrofit |
| Formal incidents with postmortem | ◑ | V1.5 |
| Automated probation / graduation | ◑ | V1.5 |
| Scorecards and evaluation cycles | — | V2 — needs history |
| Portfolio: intake and business case | — | V2 |
| Verified retirement and archive | — | V2 |
Owners, non-human identity, immutable audit and verified retirement.
