Do not index
Do not index
Fingering Our Way Through Life
To create mechanizations in the least amount of time, with the least amount of cognitive overhead, and with the highest levels of performance and reliability, basic elements need to be designed and “plugged into”.
In some cases humans will be creating a mechanization, in some cases machines, and in some cases it will be a subroutine of some automated system.
For the typical human case, we would manually go to the UI of some automation tool or service, then manually enter our sign up details, and gain access to a dashboard.
From here we would typically use our fingers to slowly enter the details needed to create the outcomes that the tools or service provides to us.
An obvious example would be services which automate social media posting - however, the requirement from these services is different for mechanizations.
This is a slow process we need to move away from. In this modern age there is no need to have to do this, and in the context of mechosophy this is a total non-starter.
We Need Speed
Let’s consider social media posting not as some automation services we can use independently of other parts of our life or business, but an “element”, capable of being “plugged into” a larger system of similar elements.
This concept is not novel by the way - look to IFFFT for the best case of technologies which spin up interconnected networks of different tools and services to achieve more complex outcomes.
The difference in our case is that our desire is to create fully self-contained, self-sufficient, and resilient task modules which lead to high level outcomes.
IFFFT and similar is tool-centric. Mechosophy is outcome-centric.
Circling back to the social posting scenario - we don’t want situations where humans use their fingers to create mechanizations.
Natural language processing allows for mechanizations to be generated by speaking them into existence.
Under the hood, an AI is selecting the right elements and piping them in the right way to get a recognised outcome, reliably, and with low time and cognitive cost.
That means these elements need some specific characteristics to allow for this.
Characteristics of Elements
- instantly accessible (we need to request to create an element using a service via an API and have it done right away)
- self-contained (each element should be a discrete unit within a mechanization)
- customizable (the way the element is used needs to be programmable with a defined set of inputs to get the flavour of element we want as the output)
- resilient (an element failing could mean the entire mechanization fails, therefore the robustness of each element is paramount)
- replicable (we should be able to spin up hundreds of thousands of such elements)
- modularly-interoperable (we should have the ability to instantaneously plug one element into any configuration of other elements and have it function)
