OPS-03 / 7 MIN / 02 AUG 2026

Mission Rooms as an operating model

Communication is connected to situation, decisions, roles and evidence.

State: controlled MVP · not externally audited
MaturityCurrent product state
Review basisRepository-aligned
Reviewed2026-08-09
01

More than a group chat

A Mission Room contains one clearly bounded operational situation. Members, roles, messages, files and pins remain in the same context rather than being scattered across tools.

The public simulator also shows tasks and a mission record as a product model. These views are explicitly a target interaction model, not a claim of an already complete control-centre integration.

02

Lifecycle

A room starts with a purpose, an owner and defined membership. During the mission, decisions are pinned with context. At closure, the situation is ended and exportable evidence follows the retention policy.

  • Open a room and set its classification
  • Add members according to role
  • Keep decisions and files in context
  • Re-evaluate access after departure or role change
  • Document closure and retention
03

Roles, not simple membership

Owners govern structure and access. Administrators manage the organisation. Future Operator, Dispatcher and Observer roles separate action, dispatch and read-only oversight.