ARGUS
ARGUSNOTE / 004ECOSYSTEMMAP MAINTAINED

Charting where autonomy intersects infrastructure.

Fleets cannot be read in isolation from the systems that hold them up. This note charts the categories that surround autonomy in the field — not the companies that occupy them.

CLASSRELATIONAL MAP
CATEGORIES005
STATUSMAINTAINED
SUBJECTOPERATIONAL ECOSYSTEM
MAP / 004.0

OPERATIONAL RELATIONSHIPS

Five categories. Every pairing carries operational weight. Autonomy emerges from the connections, not the nodes.

FIG. 004.0  ·  ECOSYSTEM TOPOLOGYRELATIONSHIPS · 010
SUPERVISIONRESEARCHOPERATORSFLEETSINFRASTRUCTURE
NODES005
EDGES010
TOPOLOGYFULLY CONNECTED
SCOPECATEGORIES, NOT ENTITIES

THE MAP DESCRIBES CATEGORIES OF SYSTEMS — NOT VENDORS, PRODUCTS, OR ORGANIZATIONS.

INDEX / 004.1

CATEGORY DEFINITIONS

Each category is a layer in the operational stack. Their interior composition is descriptive, not exhaustive.

01

FLEETS

Autonomous assets operating across physical environments.

  • 01MOBILITY
  • 02LOGISTICS
  • 03INDUSTRIAL
  • 04AERIAL
02

INFRASTRUCTURE

The substrate that makes coordinated autonomy observable.

  • 01SENSORS
  • 02COMMUNICATIONS
  • 03COMPUTE
  • 04DATA SYSTEMS
03

OPERATORS

Entities accountable for fleets in motion.

  • 01PUBLIC
  • 02PRIVATE
  • 03INDUSTRIAL
04

RESEARCH

Institutions developing the doctrine beneath autonomy.

  • 01UNIVERSITIES
  • 02LABS
  • 03INITIATIVES

The ecosystem is read as relationships, not entities. Autonomy is a property of the connections between layers — not of any single layer in isolation.

ECOSYSTEM · NOTE 004 · MAINTAINED BY THE ARGUS INITIATIVE

←RETURN TO ARCHIVE