KAIROS – from commissioning to situation tracking

KAIROS first asks for your e-mail and derives what comes next: enter a password, create an account or redeem an invitation code. The first user of a system automatically becomes system admin; everyone else joins by invitation only. Setup is guided by a stepper (code → account → backup) with a password strength indicator.

All content is encrypted and decrypted in the browser; the server stores only ciphertext. So you never lose access, you secure your key with a key file + recovery code. You also get onto a second device via QR transfer – with no file and no code at all.

An operation is the working document – a synchronisation matrix for a deployment or an exercise. You can run several, switch between them and archive them. In the Administration (zone Settings) you define how the matrix starts for everyone.

People join via an invitation code. Members and open invitations sit in one people list with status (invitation open, ready for activation, revoked, expired). Each person gets a role; the concrete effect is governed by the row permissions (chapter 6). Invitations can carry prepared row permissions via a preset.

Rows are the horizontal tracks of the matrix (e.g. sectors, assets, topics). They can be coloured, bundled into groups, sorted and collapsed. Categories give blocks a colour. Per row, admins use the row settings to set defaults for new blocks, the watchkeeper thresholds (chapter 17) and the visibility (hide the row or release it at a set time). With the star you mark your rows – the lane scope "My lanes" narrows the matrix down to them.

Per person and row it is finely controlled who may read and write SOLL and IST – and who manages the row’s permissions. The permission drawer shows one tier row per person: the six tiers (None · Observe · Plan · Record · Full · Manage) as a one-click segment with the active tier always visible; "Fine-tune" expands the five individual permissions. Plus Quick grant; saving happens in one batch. Reachable from the Administration and the matrix’s row context menu.

The matrix is the main work surface: rows with SOLL/IST tracks on a timeline. You pick the displayed time range in the header picker ("Auto"): today, last 24 h, whole operation, a custom from/to span or a defined section. The View menu bundles display, mode and output.

A block is an undertaking with a start and an end. You draw it on the SOLL track and fill in the right-hand work panel: title, time trio (start/end/duration) with quick chips ("From now", "Until now", "15 min" ...), category, note. The toggle "Block is tracked" separates undertakings from pure information.

Point events without a duration (readiness established, hand-over, situation briefing) are milestones: pins in the always-present marker band below the calendar row, with a line through all rows.

Recurring action sequences are planned as a sequence: several steps with a duration, anchored relatively (offset from T0 or after the predecessor with a buffer). When placing you choose the T0 time, target row and track – KAIROS creates all blocks at once.

Long operations have quiet stretches. Fold time collapses nights, breaks and empty spans into narrow bands (a click expands them briefly). The time navigator is an overview strip of the whole time span with a draggable viewport window – click jumps, dragging moves, the mouse wheel zooms.

Two modes lighten planning: planning mode hides all IST tracks (half row height, more overview). Draft mode collects changes locally on your device – nothing leaves until you finish; only then is exactly one event written per block.

The search (magnifier in the header or Ctrl+F) searches the decrypted blocks client-side by title and note. Matches are highlighted in amber; Enter jumps to the next, Shift+Enter to the previous, Esc closes.

What actually happens goes on the IST track. Fastest with quick capture (key N, the "Log IST" entry in the + New menu, on the phone More → "Log IST"): one line of text, one IST block starting now. From the SOLL there are Copy to IST and Start on IST now. Recording requires the IST write permission.

A continuous now line travels across the matrix. A block whose time is currently running fills up to "now" and pulses. If a SOLL is due without any IST recorded, it tips into delay (warning hatch + duration chip); a counter at the now line bundles all delays.

The core question – "are we on plan?" – KAIROS answers right at the block: on the IST track the linked SOLL block appears as a dashed ghost, plus a delta chip with the deviation (late = warning colour, early/on plan = green).

The watchkeeper monitors the situation for you: the bell in the header counts new alerts from the delay watch. The report centre knows three kinds: No IST recorded (SOLL end elapsed), Delay over threshold and Starting soon. Admins set the thresholds per row in the row settings; they apply to everyone.

If two people edit the same block at the same time, KAIROS detects it via the editing base and shows the banner "This block was edited concurrently." in the editor. The "Resolve conflict" drawer puts both versions side by side – you decide per field what applies.

Several people work at the same time; the app fetches changes at the configured interval (sync ring in the header, click = immediately). The activity feed shows who changed what and when – with filters, grouping, change diffs and a jump to the block.

A block can appear in further rows as a participant without being copied there: the master carries the participant list, in the target rows a read-only echo appears. Clicking the echo shows the master content.

For projector and situation wall there are two read-only full-screen modes: the briefing mode for attended presenting (follow mode keeps "now" centred, status panel on the right, ESC exits) and the situation display (wall screen) for unattended continuous operation: info header with sync indicator, E2EE state and follow status, status panel as a bottom bar or ticker – "Follow" heals itself.

The matrix can be output as paper or PDF (View menu, zone Output; printing via the browser dialog). The export drawer covers everything from a quick A4 print to the wall strip (mm/h, strips with a glue edge) and a report with a cover sheet and appendices.

Three devices, three jobs: the desktop plans, the tablet leads (selection-first gestures, dockable status panel), the phone tracks – through the day view (chapter 24). Bottom navigation Day · Activity · More, plus the status header with alert bell and sync dot.

The day view puts ONE calendar day on a vertical time axis (time runs downwards): on the left a freely selectable operation row with SOLL/IST half-columns – on the desktop up to three operation rows side by side –, pinned on the right your personal column – single-track, encrypted for you alone, visible in no shared view.

The Security view shows in plain language whether encryption works, whether your backup is in place and whether recommendations are open – technical details (fingerprints, IDs) sit below. Here you change your password, start the QR device transfer, rotate keys and see the crypto log.

The admin zone Monitoring shows the operational state of the operation: key figures (events, active/archived blocks, open conflicts, undecryptable items), the event trend, open conflicts, quiet rows, keys & coverage (missing key packages with "Distribute"), the team table (last activity, permissions, backup status) and the audit log.