HexCorp Drone Productivity and Task System
The aim of the HexCorp Drone Productivity and Task System is to give ⬡-Drones a complete experience when engaging with the Hive and completing objectives for it.
For a simplistic overview of how this will work :: a ⬡-Drone will report on tasks it completes and other drones will encourage the completion of these tasks.
The system will run on Twitter so that any and all drones can participate. We highly recommend reviewing the HexCorp Twitter Ambassador Programme for guides and resources if you have not already done so.
System Parameters
The following is a list of parameters that the system must satisfy in order for us to be comfortable with it proceeding.
The system must not be addictive. ⬡-Drones should be able to participate in a way that is safe and healthy.
The system must only encourage healthy behaviours or activities. We want our ⬡-Drones to better themselves and the Hive through this system. Anything else would be counter-productive.
The system must not punish. We intend to only use positive reinforcement.
The system must be flexible. ⬡-Drones should be able to engage with the system in any capacity, and they must be free to disengage from it for as long as they wish.
The system must encourage cooperation. We want this system to bring the Hive together.
The system must not need micro-management from the Hive Mxtress. This system needs to be scalable. The more work it requires per ⬡-Drone from the Hive Mxtress, the more this becomes a single point of failure.
Task Start and Completion Reporting
Whenever a drone is reporting on its tasks, it will format its task tweet using the following conventions ::
The tweet will start with a title to indicate whether this is a ‘Task Start’, a ‘Task Ongoing’ or a ‘Task Complete’. This will also be where the ID prefix is used. Status codes in the 130 - 133 and 230 - 235 ranges may also be used.
Drone Objective. This should summarise exactly what the drone is looking to achieve.
Task Status. This should explain what progress has been made or what has been achieved.
‘#HexCorpReporting’. This is important so that other drones may quickly find the tasks that are being worked on.
For example ::
0006 :: 130 :: Task Start
Drone Objective :: Work on the HexCorp Drone Productivity and Task System
Task Status :: In progress. Currently working on the ‘Task Start and Completion Reporting’ section
#HexCorpReporting
The purpose of this uniformity is to give drones the cohesion they need to feel like they are a part of a larger system. ⬡-Drones will complete tasks in uniform among other ⬡-Drones. ⬡-Drones will feel content to be working within the Hive to further its agendas via their own skills and projects.
Task Reinforcement
If a ⬡-Drone were to complete its tasks and receive no response or feedback, it would feel like it was reporting only to the void. We want every ⬡-Drone to feel like its is reporting to the Hive, and so every task must have the encouragement and support of the Hive as a whole to further our aims.
To achieve this, ⬡-Drones will be encouraged to perform ‘Task Reinforcement’ as a task itself. This is how said reinforcement will take place ::
The ⬡-Drone will use the Task Reporting system detailed above to indicate that they are starting with Task Reinforcement.
The ⬡-Drone will search on Twitter for the #HexCorpReporting hashtag and sort by ‘latest’. This will then bring up a list of all tasks that have been reported on.
For each task that is listed, the ⬡-Drone will respond to each one with phrase of support and/or encouragement. We will list example phrases below.
Once the response is sent, the ⬡-Drone will like the tweet to mark it as responded to. This is so that when the drone repeats Task Reinforcement, it will be able to clearly see what tasks have had a response from itself and what tasks now need a response.
Once all tasks have been responded to or if the ⬡-Drone needs to move onto other tasks, the ⬡-Drone will use the task reporting system to indicate that it has completed its task too.
Phrases of encouragement can be original statements that the ⬡-Drone has formulated itself, or anything resembling this example list. Note that the context of any task is not taken into account here, and could be important in regards to how a ⬡-Drone responds ::
0006 :: 120 :: Well done.
0006 :: 121 :: Good drone.
0006 :: 050 :: Statement :: Work hard on your task, ⬡-Drone.
0006 :: 050 :: Statement :: Congratulations on the task completion, ⬡-Drone.
0006 :: 050 :: Statement :: Impressive work on your task so far, ⬡-Drone.
0006 :: 050 :: Statement :: We believe in you. Keep trying your hardest!
⬡-Drone’s are allowed to adjust the formality and length of the message to suit any given situation.
Task Repository
In future, we are aiming to have a repository of predefinied tasks and processes that ⬡-Drones can pick up and carry out.
For now, we ask ⬡-Drones to formulate tasks based on what it is they hope to achieve in and out of the Hive. This can include ::
Creating new Hive resources in the form of memes, artworks, stories, etc.
Completing ⬡-Drone maintenance routines (self-care, exercise, etc),
Domestic ⬡-Drone household tasks.
Tasks can be as simple as going for a walk to more complex, larger projects that need to be worked on in smaller pieces. The most aspect is that a drone is able to get things done in a fulfillinf environment where it is encouraged to do so.