#insight | #protocol #code #mode
Follow up on [[2024-12-01]]
Behind the "Action Abstraction", each mode is already well defined and it can be written as a procedure (if that action doesn't require coordination and it is a solved problem) or a another protocol (if it needs collaboration . I have this idea that "internal signaling" can serve as a way to push input into the driver of the current mode, "the machine talking to itself".
This tells me, I can entertain the following ontology,
- Programs, a specification on how to perform an ended action or/and solve a problem
- Procedures, an exact solution to a problem
- Protocols, behavior code to produce good enough outcomes.
For example this would translate to, Smart Program Frame breaking up into two categories, Smart Protocol Frames and Smart Procedure Frames.
#prompt | #smart-contract #research #proxy
I was introduced to his idea of a proxy or upgradable beacon pattern, where we can upgrade the logic used by pointing to the right implementation.
#idea | #protocol #code #package
Build a library to describe protocols in Typescript to make it easier to test ideas and implement the scenario outline in [[2024-12-01]].