A group chat organises people. A Mission Room organises a bounded operation with members, roles, files and a shared timeline.
Mission Rooms connect communication to a specific operational context. Decisions, members and material stay with that operation instead of being distributed across permanent general-purpose channels.
Permanent group chats often mix several topics, decisions and time periods. Later it becomes difficult to establish which message belonged to which operation.
A Mission Room begins with a named purpose. Members join for that context, collaborate inside it and can close the room in a controlled way.
Important messages, files and pins remain attached to the same operation. This supports handovers without pretending that every message is automatically a formal audit record.
Roles must be enforced by the server and negative access paths must be tested. Visibility is not authorisation.
VENTEX Connect already models Mission Rooms as a distinct entity with chat and members. Tasks, live sensors, cameras and AI summaries are part of the longer-term product model, not active public capability claims.
A clear target model must never overstate the implementation that can be examined today.
Product state and boundaries are evidenced through the linked VENTEX sources.
A group chat organises people. A Mission Room organises a bounded operation with members, roles, files and a shared timeline.
No. It has a bounded purpose and is modelled as a separate room type for operational context.
No. Module boundaries are prepared, but there is no public capability commitment.
