QBO: A Hotel in a State of Digital Entropy
Based on concepts developed by CW3 Thomas J. Fisher, U.S. Army
Abstract
Modern operational environments are increasingly fragmented across people, process, tools, and organization. Data, compute, and decision-making are separated across systems, resulting in reactive workflows, information bottlenecks, and desynchronized operations.
This paper frames QBO within the model of a “hotel in a state of digital entropy,” describing a unified structure that enables real-time coordination, control, and execution across distributed environments.
The Model
Hotel = QBO Platform
The hotel represents a single system that operates across environments, supports many users and workloads, and remains consistent throughout.
QBO functions as this underlying structure, providing a unified platform that spans edge, on-prem, and cloud environments without requiring centralization.
Rooms = Isolated Environments
Each room represents an isolated environment where a workload or user operates independently while remaining part of the larger system.
Within QBO, this includes:
- MC2 instances
- Plasma workstations
- Per-user Kubernetes clusters
- Individual workloads
- Per-user isolated infrastructure stacks (self-contained within the environment)
This allows independent operation within a shared system, reducing fragmentation across teams and organizational boundaries.
Elevators = Movement of Data and Compute
Elevators represent the movement of data and compute across the system. Information flows between environments, workloads are executed where needed, and compute is applied without being tied to a single location.
Within QBO, this is enabled through:
- Distributed networking
- Scheduling and execution across environments
- Direct execution on underlying hardware (no virtualization overhead)
This removes bottlenecks, increases workload density, and enables real-time, high-performance processing.
Hallways = Communication Paths
Hallways represent the pathways through which systems interact. They enable coordination and communication across environments.
Within QBO, this is reflected in:
- Internal networking
- APIs
- AI interfaces (natural language, voice, MCP)
- Service-to-service communication
This supports continuous interaction rather than delayed, reactive exchange.
Doors = Boundaries and Control
Doors define boundaries between environments. They enforce access control while maintaining isolation within a shared system.
Within QBO, this includes:
- Per-tenant isolation
- Controlled access
- Environment-level security
This supports secure operation in constrained, regulated, and air-gapped environments.
Floors = Operational Domains
Floors represent different domains of operation, where environments are grouped and workloads can move between layers.
Within QBO, this includes:
- Edge, on-prem, and cloud environments
- Multiple security domains
- Distinct operational layers
- ORIGIN and LINK systems forming a continuous environment
State is shared across these domains in real time, allowing each environment to operate with a consistent view of the system. This enables coordination across environments that would otherwise remain disconnected.
Entropy = Constant Change
The system operates under continuous change. Data evolves, workloads shift, connectivity may be partial, and environments are not always synchronized.
Within QBO, this reflects:
- Edge environments
- Air-gapped systems
- Dynamic workloads
- Real-world distributed conditions
QBO is designed to operate under these conditions while maintaining continuity.
Alignment with Operational Gaps (PPTO)
A PPTO-based analysis of current operational environments reveals fragmentation across People, Process, Technology, and Operations. These gaps create separation between data, compute, and decision-making, resulting in delayed responses and reduced operational coherence.
- People: Highly skilled personnel operating in isolated silos of excellence
- Process: Persistently reactive, not proactive, across physical environments
- Technology: Information bottlenecks that limit decision dominance
- Operations / Culture: Disconnected planning leads to increased operational risk, desynchronized execution, and missed opportunities
QBO addresses these conditions by providing a shared operational layer where:
- Teams can operate independently within a unified environment, reducing siloed expertise
- Processes shift from reactive execution to continuous, real-time adaptation
- Data and compute are no longer constrained by centralized bottlenecks
- Coordination across environments can occur without requiring full synchronization
This reduces the distance between signal, interpretation, and action.
Alignment with Desired End State
The desired end state describes a system that can synthesize information, adapt in real time, and support tailored execution across environments.
QBO enables this by:
- Unifying fragmented environments into a single operational layer, allowing information to be interpreted in context
- Supporting real-time movement and processing of data, enabling continuous adjustment
- Enabling workloads to execute at the point of need, improving responsiveness and decision quality
- Providing isolated, customizable environments that adapt to specific operational requirements
This creates a system that is distributed, coordinated, and responsive under changing conditions.
Conclusion
The “hotel in a state of digital entropy” describes a system in which independent actors operate within a shared structure under constant change. It requires coordination without centralization, control without rigidity, and real-time adaptability.
QBO aligns with this model as a distributed execution layer that:
- Bridges data, compute, and decision-making
- Enables real-time operations across environments
- Maintains control within constrained and isolated systems
- Supports decentralized and resilient infrastructure
In this way, the conceptual model becomes operational, capable of functioning across fragmented and dynamic environments.


