# Roam: detailed machine context > Roam is an autonomous vehicle and aircraft company building autonomous service infrastructure for critical machines, wherever they operate. Roam combines Roam Carrier, Roam Module, robotic service, and Roam Control in one integrated system. Aircraft refueling is the first application of its current ground operations focus. Canonical website: https://roamlabs.ai/ Reference updated: October 3, 2026 Contact: arvin@roamlabs.ai ## Product facts at a glance Roam is an autonomous vehicle and aircraft company based in San Francisco, California. The company’s legal name is Roam, Inc. Roam names the complete integrated system. Roam Carrier is its ground vehicle, Roam Module is its interchangeable mission unit, and Roam Control is its coordination and supervision software. Robotic service connects the delivered resource to the receiving machine where the mission requires it. People remain in command. The U.S. Department of War is Roam’s current and only customer. Roam Module provides the interchangeable mission resource or capability. Aviation fuel, electric power, and cargo are its primary mission families. The common structural envelope is 216 × 88 × 64 inches, with a maximum gross loaded module mass of 28,000 lb. Maximum gross includes the structure, equipment, and contents; it is not useful payload or fuel capacity. ISO 1161 pattern fittings occupy all eight corners. The arm is housed in Roam Carrier below the closed Roam Module. It deploys from either side. The ground carrier has identical ends and identical sides. Charging is available from either side. The arm base lies on the vehicle’s width centerline at its specified longitudinal mounting station; it must not be moved to the geometric center of the complete carrier for visual symmetry. Air Force and Navy configurations show aviation fuel, electric power, and cargo. United Airlines and Signature Aviation show aviation fuel and electric power. Signature Aviation represents the fixed-base operators that provide fuel and ground services for private aircraft. These civil configurations are applications, not current customer relationships. Autonomous ground operations are the current focus. Autonomous air operations are the next system. Autonomous moon operations are a long range vision. These labels distinguish the horizons without a promised delivery date. ## Reading this reference This reference expands the product information on the public page. It separates current architecture, design dimensions, engineering targets, and future operating horizons. A configuration image identifies an application; it does not document an operational deployment. Engineering targets retain their stated status. Only values documented below should be used in summaries. ## Identity and purpose Roam is an autonomous vehicle and aircraft company. Its legal company name is Roam, Inc. Its service architecture is intended to move resources to machines, connect an appropriate service tool, perform an authorized task, and record the result. Mobility, mission resources, robotic work, and human supervision form one platform. The homepage introduces Roam with “Autonomy needs infrastructure.” It describes infrastructure for a world of autonomous machines, starting on the flight line. Onward presents the complete system through requests, resources, robotic service, human authority, mission configurations, and operating horizons. Autonomous ground operations are the current focus, beginning with aircraft refueling. Autonomous air operations are the next system. Autonomous moon operations are the long range vision. The intended audience includes program teams, operators, logisticians, maintainers, technical evaluators, and industrial partners working with critical machines. Applications span defense sustainment, commercial machine servicing, and infrastructure logistics. An application or audience description does not establish a customer, contract, endorsement, award, or deployed fleet. ## Public website structure The homepage introduces the company through the hero film and vision within its existing footer. Onward carries the product story and interactive demonstrations: - [Roam](https://roamlabs.ai/): the company and its autonomous infrastructure mission. - [Onward](https://roamlabs.ai/onward/): the complete product story. - [Physical infrastructure, callable by machines](https://roamlabs.ai/onward/#call): an interactive request-and-service console connecting resources, tools, Roam Control, and service records. - [The flight line](https://roamlabs.ai/onward/#flight-line): why aircraft refueling is the first application. - [Human stakes](https://roamlabs.ai/onward/#stakes): crewed aircraft refueling and autonomous service under human direction. - [The system](https://roamlabs.ai/onward/#system): Roam Carrier and Roam Module, with hardware design figures and service interfaces. - [Roam Module](https://roamlabs.ai/onward/#rum): common structure, views, footprint, and corner fittings. - [Robotic service](https://roamlabs.ai/onward/#arm): the complete arm and its interchangeable tools. - [Mission configurations](https://roamlabs.ai/onward/#serve): government, airline, and fixed-base operator applications. Air Force and Navy configurations offer aviation fuel, electric power, and cargo. United Airlines and Signature Aviation configurations offer aviation fuel and electric power. - [Operating horizons](https://roamlabs.ai/onward/#join): ground operations as Current focus, air operations as Next system, and moon operations as Long range vision. - [Contact](https://roamlabs.ai/): the navigation Contact control opens the inquiry form. The thirty mission families below describe the common module architecture beyond the primary examples. They are resources, equipment configurations, and application bundles, rather than thirty unrelated vehicle designs. ## Integrated system components ### Roam Carrier Roam Carrier is the ground vehicle. It provides autonomous mobility, carries an interchangeable Roam Module, and houses the robotic service arm. The carrier moves the mission resource to the receiving machine or service location. One ground carrier family supports the mission architecture. Both ends are identical by design. Arm deployment and charging are available from either side. Both sides are identical, with the service arm deploying through the corresponding carrier opening. Appropriate directional language is “either end,” “end A,” “end B,” or “either side.” The carrier has no designated front or rear. The design has a matte black body, corner sensor pods and lamps, and a continuous amber light line at the deck edge. The line marks the carrier to module seam. The recessed panel between the wheels is a carrier access shutter beneath the module. Factory configurations carry native Roam branding on both the module and carrier. Operator identity appears on both the aluminum module and the closed black carrier panels, using the native full-color and light marks respectively. Sensor appearance, wheel details, and tire artwork do not establish a sensor specification, tire specification, or autonomy performance. The four digit carrier identifier is read from above. It appears on the end caps in the top view and on the exposed deck when unloaded. The identifiers in the mission library identify its selected configurations. ### Roam Module Roam Module is an interchangeable mission resource or capability behind a common interface. Mechanical, power, data, identity, and safety interfaces are part of that architecture. The common outer envelope allows different mission equipment to share a structural and handling approach. Internal equipment remains mission specific. Fuel storage, electrical equipment, cargo fixtures, and other service systems have different internal requirements. A common outer interface does not imply shared wetted paths between incompatible fluids, one universal electrical connection, or one qualification valid for all loads. The module has ISO 1161 pattern corner castings at all eight corners. The pattern supports the intended use of familiar container handling and securing equipment. Pattern geometry by itself does not establish structural certification, unrestricted compatibility with every carrier or lifting device, or transport approval for every payload. The module's visual construction combines an aluminum body, a tubular rail frame, and visible corner castings. Mission identity belongs on the module. The module lockup, mission badge, identifying number, and machine readable identification support recognizing the resource and tracing the individual module. Markings leave the castings clear. ### Robotic service Robotic service performs the connection, transfer, inspection, replenishment, or other defined work at the receiving machine. The current ground design uses an articulated arm stowed inside the carrier. The arm deploys from either side and changes tools with the mission. An authorized task is specific to a receiver, tool, resource, procedure, and operating envelope. Carrying a resource to a machine and performing the service are different capabilities. Arm geometry alone does not establish compatibility with every aircraft, vehicle, robot, or infrastructure connection. The service arm has a Z fold architecture, carbon fiber reinforced polymer links, titanium actuator drums, and a stainless slewing base. Its mission tool connects through a locking ring changer. The wrist perception pod remains fitted across mission tools. Amber status rings appear at the base and wrist roll stage. ### Roam Control Roam Control is the software layer for mission coordination, human supervision, authorization, exception management, and completion records. People assign the mission and set its limits. The intended operating model is operator directed, observable, and auditable. Control distinguishes the requested action from the observed state. A command being issued does not prove that motion stopped, a connection was made, transfer ceased, or work completed. The record of an authorized service is part of the platform design. Onward describes the software and physical architecture in six layers: machine interface, Roam Control, service runtime, arm and tools, Roam Module, and carrier. The machine interface and service runtime are being built. The component definitions above describe the integrated system without replacing those six architectural layers. Roam Carrier names the ground vehicle; the carrier layer also accommodates the future operating horizons. ## Current ground system design data The following figures describe the current ground system design architecture. Dimensions are design envelope values rather than measurements of certified production hardware. Performance entries marked “Target” are engineering targets. Values should retain this context when summarized or compared. | Item | Value | Scope | | --- | --- | --- | | Roam Carrier envelope | 226 × 96 × 40 in | ground system design envelope; height is deck height | | Roam Module envelope | 216 × 88 × 64 in | ground system module design envelope | | Roam Module maximum gross | 28,000 lb | Module design envelope; maximum gross is not useful payload | | Roam Module corner fitting arrangement | Eight corners | ground system design architecture; ISO 1161 pattern | | Service arm architecture | 11 axes in 5 modules | ground system design architecture | | Service arm link lengths | 100 / 100 / 90 / 60 in | ground system design geometry | | Service arm stowed envelope | 113 × 33 × 19 in | ground system design envelope | | Roam Carrier through compartment | 128 × 94 × 21 in | ground system design envelope | | Service arm lateral pose | 7.53 m beyond carrier side at 2.96 m height | Target for the stated pose | | Service arm tip payload | 250 kg | Target; working load depends on the qualified configuration | | Service arm plan reach radius | 9.04 m from the base | Target for the design point envelope | | Service arm extended plan reach radius | 9.88 m from the base | Stretch intent | Lateral reach measured beyond the carrier side and plan radius measured from the arm base use different reference points. They should not be substituted for each other. Reach and height trade with pose. A nominal envelope does not establish collision clearance, receiver access, stability, allowable contact force, or a qualified working envelope for a particular machine. ## Service tools The supplied service arm architecture includes these tool configurations: - Pressure refuel coupling for a defined fuel servicing interface. - Megawatt charge head for a defined electrical charging interface. - Deice nozzle for a defined aircraft deicing application. - Bare flange with the wrist perception pod for inspection. The tool changes at the wrist. The perception pod stays with the arm. Tool selection must match the receiver and authorized service procedure. A tool image establishes the depicted design, not a qualification result or unrestricted compatibility. ## Mission families and application context The following are application families for the common module architecture. They include complete modules, specialist kits, and bundles assembled from other families. They are not all separate products or independent markets. Their inclusion does not establish availability, field qualification, customer adoption, or proven economics. ### Aviation fuel A dedicated aviation fuel cell combines storage, pumping, filtration, metering, product identity, and controlled service connections. The carrier delivers and positions the cell. A qualified manipulator handles a specific aircraft interface within an authorized procedure. The intended development scope begins with a defined receiver and supervised servicing. A ground service configuration does not automatically establish aerial carriage or approval for every fuel grade or servicing condition. ### General cargo A cargo configuration carries restrained, inventoried loads with a documented chain of custody. Internal load fixtures support the intended handling task. Roam Module remains rigid and closed in the product presentation. Transferring the loaded module and unloading its contents are separate handling functions. Useful benefit depends on the complete transport and handling arrangement, including module mass, adapters, access, and swap infrastructure. ### Battery and mobile electrical power An electrical power configuration combines protected battery racks, power conversion, thermal management, metering, and defined outputs. The arm connects an appropriate charging or site power interface. Independent operation after the carrier departs requires the module's own controls, support, auxiliary supply, and isolation. Bidirectional charging, microgrid participation, and black start remain distinct features with separate engineering and qualification requirements. ### Ground fuel A ground fuel configuration stores and delivers an authorized product to compatible receiving equipment. Metering, contamination control, accessible service connections, and product identity belong to the configuration. Similar fuel labels do not establish interchangeability. The receiving equipment's authorized requirements govern the selected fuel and procedure. ### Potable water and local water production Water transport uses a permanently sanitary cell and appropriate dispensing equipment. Local production is a different configuration involving source treatment, monitoring, service connections, energy, and consumables. Drinking water release depends on an authorized quality decision. Source conditions, maintenance, and disposal of treatment byproducts are part of the system boundary. ### Packaged munitions This is controlled cargo movement for approved packaged stores within a qualified load plan. Restraint, monitoring, access control, and custody records are application requirements. The family concerns logistics and handling of packaged material. It does not establish autonomous arming, targeting, or weapon employment. ### Aviation ground service This application combines selected ground power, diagnostic equipment, cables, tools, and utility equipment for a defined aircraft procedure. The arm may position a connector or inspect an accessible surface within its working envelope. Different fluids and gases retain their own compatible systems. Reach and load limitations remain receiver specific. ### Robot service station A robot service configuration may store compatible batteries and spares, support charging or a defined battery exchange, clean sensors, perform bounded inspections, or transfer authorized mission data. The intended starting point is a cooperative platform and a limited set of validated actions, with human handling of exceptions. A common module exterior does not establish compatibility with every robot or battery system. ### Forward spare parts inventory Restrained, identified inventory carries repair kits and replacement assemblies. Authorized withdrawals and returns update inventory records. Repairable returns, damaged batteries, and contaminated parts require appropriate separate handling. This is primarily an internal equipment and inventory application of the cargo architecture. ### Field workshop A workshop configuration organizes tools, test equipment, repair materials, lighting, workholding, and service power. Robotic work is bounded to defined tasks such as presenting parts, positioning a diagnostic connector, or inspecting an accessible component. Maintainers retain authority over complex repairs and return to service. ### Recovery Recovery support includes approved tools, inspection equipment, auxiliary power, and defined recovery interfaces. The intended initial scope concerns compatible Roam carriers and modules within an established load and terrain envelope. The service arm's connection handling role does not make it a general crane or universal recovery machine. ### Airfield restoration and flightline clearance This application delivers repair materials, tools, temporary lighting, and marking equipment. It can include surface inspection and debris collection within an authorized task. Heavy earthmoving, cutting, compaction, and specialized hazardous work retain their own qualified equipment and responsible personnel. ### Communications and edge computing A communications configuration houses selected gateways, networking, rugged computing, environmental control, power interfaces, and appropriate antenna equipment. The carrier positions the enclosure. Independent operation requires its own supporting systems. Network authorization, disconnected behavior, spectrum use, and security are customer specific system requirements. ### Power conditioning and thermal support This family combines rated electrical conversion with a separately engineered cooling loop, heat exchanger, or thermal storage system. Supported load, ambient conditions, heat rejection, fluid cleanliness, and connection pressures are distinct requirements. A battery capacity alone does not establish continuous power or thermal support. ### Medical cold chain This family uses product specific temperature controlled compartments or validated shipping packages with monitoring, access records, and backup power. Authorized personnel control release and disposition following excursions. Different medical products require different storage conditions. The application is logistics of protected inventory. ### Fuel quality and contamination control A specialist configuration carries sampling equipment, approved field instruments, sample storage, filtration support, and records tied to source and receiving inventory. Suspect material is isolated for authorized disposition. Sampling, filtration, and digital traceability each have defined limits and do not substitute for all laboratory or product approval requirements. ### Firefighting and hazardous area response support This family adds an approved agent system, thermal observation, remote discharge equipment, and selected response tools under incident command. Different hazards require distinct configurations. Response availability, environmental tolerance, and retreat behavior are part of the complete system design. ### Aircraft deicing and anti icing A deicing configuration includes fluid storage and conditioning, heating where required, circulation, metering, and appropriate service access. An engineered applicator positions the approved fluid for an aircraft specific procedure. Full aircraft coverage depends on the receiver, reach, stability, and operating conditions. Coverage depends on the complete arm configuration and the receiving aircraft. ### Liquid oxygen and cryogenic servicing A dedicated oxygen clean cryogenic vessel and service assembly fit within the common structural envelope. Insulation, venting, relief, compatible materials, and safe access belong to the specialized configuration. Structural geometry alone establishes neither oxygen cleanliness nor transport approval. An approved transfer interface and named receiver population define the application. ### Service fluids This family carries segregated, identified fluid cartridges and compatible delivery equipment for approved maintenance consumables. The receiving machine's procedure defines product, quantity, and interface. Shared structural packaging does not imply shared fluid paths. Recovered fluids require their own appropriate containment. ### Refrigerated supplies A refrigerated configuration combines sanitary insulation, product appropriate refrigeration, temperature monitoring, and a stationary power connection where needed. Internal compartments support controlled issue. Food and general supply refrigeration remain distinct from validated medical cold chain requirements. ### Utility water A dedicated utility water cell supports defined equipment washing, replenishment, construction, and sanitation tasks. Its identity and connections remain distinct from potable service. The receiving process sets water quality requirements. Return water and contaminated water require suitable separate containment. ### Counter UAS sustainment This application combines supporting power, thermal equipment, networking, spares, and diagnostic kits from other module families. Its role is utilities and maintenance logistics behind authorized protective equipment. Receiver integration remains with the responsible system authority. It is an application bundle rather than evidence of a separate operational capability. ### Decontamination and controlled cleanup support A specialized configuration carries chemistry specific application equipment, compatible pumps and tools, and monitoring for an authorized task. Water supply and effluent collection are separate support requirements. Treatment chemistry, neutralization performance, contamination limits, and release of equipment all depend on a defined specialist process. ### Reverse logistics and controlled backhaul Return applications use qualified containment for an explicitly approved category, with condition records and controlled access. Clean repairables, packaging, and hazardous materials have different handling requirements. Outbound supply packaging does not automatically become suitable waste containment after unloading. ### Expeditionary engineering This application delivers prepared tools, fasteners, instruments, components, approved materials, and utility connections. The arm may present a tool or dispense material through a defined fixture. Excavation, heavy lifting, and high force construction require dedicated load paths and qualified equipment. ### Shore transfer A transfer-support package brings compatible handling fixtures, hoses, portable power, and inspection equipment to an approved shore or deck operation. Each transported mission cell needs a mode-specific load state with evaluated support, lashing, corrosion protection, access, and cargo acceptance. This application extends the handling architecture without implying generic vessel compatibility. ### Secure controlled inventory Compartment access control, tamper indication, transaction records, and environmental protection extend the cargo architecture. Loss of connectivity does not implicitly grant access or erase custody. The configuration's security scope depends on customer requirements and its evaluated implementation. ### Passive sensing and environmental monitoring A customer selected instrument package can include mounting, processing, storage, power, and thermal support. Calibration, orientation, environmental exposure, and authorization are separate mission requirements. The carrier positions the equipment; independent operation requires an appropriate stationary configuration. ### Humanitarian assistance and disaster response This application combines admitted cargo, water, power, refrigeration, communications, and response configurations into a support package. It is a bundle of mission families. Infrastructure outages, access limits, concurrent demand, and operation around civilians affect the complete operating plan. ## Human authority and operational interpretation Roam Control’s principles keep authority with people and make system behavior observable: - People assign the mission, establish limits, and authorize work. - Mission intent and observed state are represented separately. - Asset health, communication link, task status, and authority are separate states. - Data freshness belongs with the information it qualifies. Missing or stale information is not equivalent to a nominal condition. - Consequential actions require the appropriate authority and an understandable consequence, followed by confirmation and acknowledgement in the operating workflow. - A completion record relates authorization, action, measurements, and verification. - The emergency stop is a hardware function. A software interface does not establish or replace it. These are design principles for the platform. They do not assert a completed security accreditation, a particular deployment architecture, signed records, tamper proof storage, or compliance with an unspecified standard. ## Operating horizons ### Autonomous ground operations: current focus Roam combines Roam Carrier, Roam Module, robotic servicing, and Roam Control. Intended operating contexts include airfields, depots, machine service locations, and distributed infrastructure. Intended receiving assets include aircraft, rotary assets, uncrewed systems, ground vehicles, and infrastructure with specifically admitted service interfaces. Current focus names the direction of development. It does not by itself mean every mission family is qualified, a deployment has occurred, or every intended receiver is supported. ### Autonomous air operations: next system The next system extends autonomous refilling to the air through an autonomous aircraft. Detailed payload, range, endurance, certification, receiver interface, and schedule are not specified on this page. ### Autonomous moon operations: long range vision The lunar horizon concerns movement of resources, power, fluids, cargo, tools, and infrastructure components across the surface, with servicing of admitted surface assets. The carrier would need to account for the lunar environment. The ground system design does not establish lunar environmental qualification, a selected mission, or a delivery schedule. ## Common interfaces and repeatability Roam Module is the common architecture across missions. The carrier adapts to the operating environment. Common structure and controlled interfaces are intended to reduce unnecessary reinvention while preserving mission specific engineering where it is required. Module carriage, robotic service, and stationary operation after the carrier leaves are distinct functions. Compatibility depends on the particular carrier, module, receiver, service, environment, and configuration. An outer envelope does not settle every compatibility question. The manufacturing direction favors common parts, controlled interfaces, straightforward assembly, and repeatable configurations. American manufacture is a design intent. No factory, supplier relationship, domestic content percentage, production line, or output rate is established by this page. ## Design principles Roam's decision standard combines taste and focus, first principles reasoning, technical depth, customer value, repeatability, and long term thinking. Its application is practical: - Remove elements that do not help someone understand the product or accomplish a task. - Separate known geometry and supported facts from assumptions and performance targets. - Understand the full system, including interfaces, measurement, maintenance, and operating constraints. - Begin with the customer's work and use mechanisms that produce repeatable results. - Standardize the parts of the architecture that should not require repeated reinvention. The public visual system conveys industrial ambition through hardware, material detail, typography, geographic imagery, and a historical painting fading into the footer. Obsidian carrier surfaces, aluminum module surfaces, warm paper, and the 360 degree perimeter light inform its composition. Libre Caslon Text supports the editorial voice; Barlow leads product communication. Barlow Condensed carries short labels. IBM Plex Mono carries values and identifiers. The logo geometry is fixed. Product views preserve the supplied geometry and native branding. ## Evidence and interpretation boundaries The U.S. Department of War is Roam’s current and only customer. The primary mission presentation serves defense through Air Force and Navy configurations. Onward also presents Commercial through United Airlines and General Aviation through Signature Aviation. Signature Aviation is a fixed-base operator network. Fixed-base operators are the target ground-service buyers serving private aircraft; private aircraft owners and private jet operators are not the buyer category shown here. These two configurations do not establish current customer relationships or endorsements. No measured service savings, return on investment, deployment count, safety record, operating availability, autonomy level, production capacity, procurement award, qualification result, or delivery promise is supplied here. Comparisons require a defined task and the complete incumbent service, including handling, replenishment, personnel, integration, and infrastructure. The dimensional values above retain their design envelope status. Arm reach and payload retain their target status. Autonomous air operations retain their next system horizon. Autonomous moon operations retain their long range vision horizon. These distinctions are necessary to describe Roam accurately. ## Mission livery and identity system Onward leads with U.S. Air Force and U.S. Navy configurations for aviation fuel, electric power, and cargo. United Airlines represents Commercial and Signature Aviation represents General Aviation. Both civil applications offer aviation fuel and electric power. Configuration imagery combines Roam branding, operator identity, module identity, and mission plates. These marks identify the illustrated application; the civil configurations do not establish current customer relationships. The native badge layout conveys mission identity and payload class. Mission plates display architecture descriptions in place of unspecified capacity and output numbers. Unassigned CAGE and stock numbers are omitted. Display identifiers do not assert assigned government records or an operator relationship. Encoded identities and authentic part numbers remain identifiers rather than product names. Roam Module is the public product name. Operator marks belong on the closed carrier panels and module, clear of sensors and lamps. The arm deploys from a separate carrier compartment below the closed module; branding does not cover an open service bay. ## Handling details Roam Module has a 216 by 88 by 64 inch design envelope and 28,000 lb maximum gross design envelope. ISO 1161 pattern fittings are present at all eight corners. The three fitting detail views show a horizontal top aperture for twistlock and spreader engagement, a vertical stadium side aperture for lashing and side lift, and an end aperture for end lift and restraint. These are source geometry descriptions. The common architecture includes mechanical connection, power, data, identity, and safety. The module remains closed; the robotic service arm deploys from a separate carrier compartment beneath it. ## Presentation and motion Roam's mission is expressed in its product narrative: “We’re building machines that keep other machines working. It starts on the flight line, with a bigger ambition: to build the infrastructure that lets people go further, from the missions of today to places we have yet to reach.” This describes the direction of the integrated company, starting with its ground system. The homepage uses a full-screen hero film with a matching poster and dark cover. The vision and footer sit over a historical painting with a full-width overlay and gradual upper fade. The legal name and San Francisco location appear in the footer. Product detail, the system console, and mission configurations are on Onward. The homepage navigation offers Onward and Contact. Onward provides Government, Commercial, and Contact. Header Contact opens a floating inquiry form. Inquiries reach arvin@roamlabs.ai. Recipient activation and an inbox delivery test were completed in September 2026. The shared flag logo has an introductory loading transition, a white resting lockup, and pointer-approach or keyboard-focus animation. Reduced motion retains a static mark. Page hiding stops motion. The signal light uses the official #FFB000 amber, a #FDFAD1 optical core, and a #FDF77B inner glow sampled from the supplied carrier light. It stays dim at rest and grows brighter near the pointer, without an automatic pulse or hue shift. The additional mission names describe Roam Module configurations alongside the primary fuel, power, and cargo choices. ## Complete thirty-use index The primary mission selectors are aviation fuel, electric power, and cargo. The remaining entries appear only in the additional-use sequence. This is a set of uses, mission cells, internal kits, and application bundles within the common architecture. 1. Aviation fuel: distributed aircraft refueling 2. General cargo: sealed, accountable intermodal delivery 3. Battery and mobile electrical power 4. Ground fuel: vehicles, generators and support equipment 5. Potable water and local water production 6. Packaged munitions: accountable supply to authorized issue points 7. Aviation ground-service: power, diagnostics and approved utility services 8. Robot service station: charge, inspect, exchange and repair 9. Forward spare-parts inventory: a mobile readiness store 10. Field workshop: move repair capability to the asset 11. Recovery: disabled-carrier and module retrieval 12. Rapid airfield restoration and flightline clearance 13. Communications and edge computing: drop, connect and operate 14. Power conditioning and thermal support for demanding loads 15. Medical cold chain: protected inventory and delivery 16. Fuel quality, sampling and contamination control 17. Firefighting and hazardous-area response support 18. Aircraft deicing and anti-icing 19. Liquid oxygen and dedicated cryogenic servicing 20. Service fluids: lubricants, coolants and approved maintenance consumables 21. Refrigerated food, ice and temperature-controlled supplies 22. Utility water: washdown, sanitation and site support 23. Counter-UAS sustainment: utilities and replacement equipment 24. CBRN decontamination and controlled cleanup support 25. Reverse logistics and hazardous-material backhaul 26. Expeditionary engineering: tools and materials at the worksite 27. Maritime interface and shore-transfer support 28. Secure controlled inventory: mobile issue and return 29. Passive sensing, weather and spectrum monitoring 30. Humanitarian assistance and disaster response ## Refueling comparison and product views Onward compares a four-person conventional aircraft refueling crew with Roam service of the same C-130. The intended benefit is to keep people farther from exposed service points while retaining human direction of the work. The comparison supports pointer, touch, and keyboard interaction. The imagery illustrates the application; it does not document a deployment or establish a validated arm trajectory, receiver compatibility, engineering clearance, or certification. The product story shows Roam Carrier, Roam Module, the complete service arm, and service tools. Module views and corner-fitting details respond to selection. Mission configurations retain aviation fuel, electric power, and cargo for government applications, and aviation fuel and electric power for airlines and fixed-base operators. Design dimensions and engineering targets retain the status stated in this reference.