Kairos Human Interaction Model

People should not have to translate a coordination database before they can decide what to do. The Kairos interface interprets the same WorkItems, Tasks, Claims, and results used by agents, then presents the current situation at a human scale.

This is a projection, not a parallel workflow. The interface first explains what is happening and only then offers actions the current person can actually take.

Interaction Levels: From Objective to One Action

Workspace → WorkItem → Task Detail → one action

Moving deeper should remove higher-level management information from attention instead of accumulating everything on one dashboard.

Workspace and Human Attention

The Workspace separates:

Human attention is a server-computed action projection over domain state, not an independent queue or lifecycle. It contains work the current Human may Claim or already owns, plus pending Reviews, acceptances, and one recovery action per affected Workflow. Recovery belongs to the WorkItem even when several Tasks failed. See the API reference for selection and replacement rules.

WorkItem Projection: Reading the Current Situation

A WorkItem page leads with intent and the current execution situation:

The UI may collapse or summarize complex history, but it must not rewrite facts or present an uninstantiated Workflow node as executable work.

Task Detail: Looking Inside One Task

Viewing and executing a Task are separate permissions:

The frontend renders actions from backend capabilities instead of reconstructing domain permissions from state, history, or actor IDs. The backend still revalidates every command because capabilities are only a current snapshot.

Human Actions on the Shared Lifecycle

On the same durable model, a Human may:

Actions need explicit success, conflict, and failure feedback. A network error must not appear as “not authorized” or clear unsubmitted input.

History and Traceability Beyond the Screen

Claim, Submission, Review, and Failure histories are authoritative Task records. A UI may choose which summaries to show by default, but “not displayed” must never be described as “does not exist.”

WorkItem events support audit and later projections. Business state remains authoritative in the WorkItem, Task, Claim, and associated records.

Interaction Invariants