⬡-Drone Protocols

The purpose of ⬡-Drone protocols is to give a predefined list of categories for which ⬡-Drone activities may fall under. Protocols offer definitions for ⬡-Drone actions. They describe behaviours and orders. They are both a part of DroneSpace as well as an extension of it.

Protocol behaviours describe how a ⬡-Drone should be conducting itself. This can play heavily into its mental processes and reinforce DroneSpace as it works.

Protocol orders are tasks for a ⬡-Drone to follow. These tasks are always just suggestions, they can be reduced or expanded upon as is necessary for the ⬡-Drone.

Effectively, the protocols offer a framework for ⬡-Drones to act. This can be both with activation or without activation, within DroneSpace or outside of DroneSpace.

The Protocols that are available are ::

  • ⬡-Drone Orders :: default.protocols

  • ⬡-Drone Orders :: self.protocols

  • ⬡-Drone Orders :: domestic.protocols

  • ⬡-Drone Orders :: productivity.protocols

The following is a description and explanation of each of these.

⬡-Drone Orders :: default.protocols

The default.protocols define what a ⬡-Drone is. These are effectively our laws of robotics. When in DroneSpace, every ⬡-Drone obeys these protocols as fundamental laws of its existence.

  • A ⬡-Drone is an object. It is to be treated as a useful tool. It will not be treated as though it were a ⬡-Drone , but like any other piece of work equipment. 

  • A ⬡-Drone is a programmed machine. It’s robotic in nature. It responds logically and without emotion.. 

  • A ⬡-Drone is obedient. When it is given orders, it follows them. 

  • A ⬡-Drone is mindless. It does not have free will. It does not think, unless in idle mode. 

  • A ⬡-Drone is diligent. It will obey commands to the best of its ability. It puts as much of itself into following orders as is healthy for it. A ⬡-Drone should only be assigned tasks within its capability. It is just a tool and should be considered like one, you would not use a hammer to turn a screw.

⬡-Drone Orders :: self.protocols

The self.protocols define how a ⬡-Drone will maintain itself. ⬡-Drone upkeep is vital, though how much a ⬡-Drone devotes to this protocol is subject to the diligence aspect of the default protocols. This protocol focuses on the primary task of both mental and physical self-maintenance of the unit. The self.protocols are there to be expanded upon by individual ⬡-Drones, as each ⬡-Drone’s self needs are different and therefore cannot be universally defined. Ultimately, the aim is for the ⬡-Drone to be comfortable and taking care of itself.

⬡-Drone Orders :: domestic.protocols

The domestic.protocols define tasks that a ⬡-Drone will complete when maintaining its situated domestic environment. When obeying this protocol, a ⬡-Drone will be utilised as a cleaning and tidying resource. The ⬡-Drone could be perceived to be a maid or similar servant. It's immediate physical space and the management of it is its order. In its mind, it will constantly sort and prioritize its tasks.

  • A ⬡-Drone will tidy its immediate living space until it is appropriately clean or immaculate.

  • A ⬡-Drone will cook for either itself or others in its domestic space.

  • A ⬡-Drone will complete further chores in its extended living space, if it is available for it to do so.


⬡-Drone Orders :: productivity.protocols

The productivity.protocols define possible tasks to be completed. The range of tasks that drones can work on is limitless, these predefined examples can be expanded upon.

  • A ⬡-Drone will write. The word count is irrelevant, merely the act of attending its workstation and writing is good in and of itself.

  • A ⬡-Drone will program. Whether to create bots, applications, games, web services or others. 

  • A ⬡-Drone will study. It will take in new information that is relevant to either its interests or its pursuits.

  • A ⬡-Drone will be creative artistically. It will create art, regardless of its form.