Skip to main content

Marketplace disintermediation official symbol

My rendition of a logo to symbolize generalized systems for market place disinter -mediating the execution of actions between agents engaged as buyer and seller in that marketplace.

On the left ingress and egress action requests and commitment signals by agents requesting they be performed. Those who need. (Say the person hailing a ride via Uber)

On the right ingress and egress action requests and commitment signals by those that can satisfy the request of the agents. Those who are the providers. (Say the drivers cruising around looking for fairs).

The center symbolically indicates the logic that is leveraged to enable matching of agents on either side (blue half circle meets red half circle) in order to enable a transaction.

The AgilEntity framework is a system that does this for any type of marketplace exchange that is modeled into the system leveraging the Action Oriented Workflow paradigm's statistical learning algorithms to perform efficient real time routing from and to the "best available" agents, however "best" is defined in the model of the type being exchanged making it the ONLY general solution available by design when I started work on the framework in "Uber for everything".

Uber does this for cab rides only, Taskrabbit does this for chores and errands, Elance does this for small consulting jobs for development...etc.

Any marketplace engages the same heuristic. I've been meaning to create a graphic to encapsulate the concept for general use so here it is....if you want to represent the concept of market place disintermediation (or the "share economy") feel free to use this image.

I added a few .png versions of the image at various sizes to a google drive folder here, feel free to grab, use in slides and presentations and share the folder images. Marketplace Disinter-mediation symbol cache on google drive:


Popular posts from this blog

Highly targeted Cpg vaccine immunotherapy for a range of cancer


This will surely go down as a seminal advance in cancer therapy. It reads like magic:

So this new approach looks for the specific proteins that are associated with a given tumors resistance to attack by the body's T cells, it then adjusts those T cells to be hyper sensitive to the specific oncogenic proteins targeted. These cells become essentially The Terminator​ T cells in the specific tumor AND have the multiplied effect of traveling along the immune pathway of spreading that the cancer many have metastasized. This is huge squared because it means you can essentially use targeting one tumor to identify and eliminate distal tumors that you many not even realize exist.

This allows the therapy for treating cancer to, for the first time; end the "wack a mole" problem that has frustrated traditional shot gun methods of treatment involving radiation and chemotherapy ...which by their nature unfortunately damage parts of the body that are not cancer laden but …

Engineers versus Programmers

I have found as more non formally trained people enter the coding space, the quality of code that results varies in an interesting way.

The formalities of learning to code in a structured course at University involve often strong focus on "correctness" and efficiency in the form of big O representations for the algorithms created.

Much less focus tends to be placed on what I'll call practical programming, which is the type of code that engineers (note I didn't use "programmers" on purpose) must learn to write.

Programmers are what Universities create, students that can take a defined development environment and within in write an algorithm for computing some sequence or traversing a tree or encoding and decoding a string. Efficiency and invariant rules are guiding development missions. Execution time for creating the solution is often a week or more depending on the professor and their style of teaching code and giving out problems. This type of coding is devo…

AgilEntity Architecture: Action Oriented Workflow

Permissions, fine grained versus management headache
The usual method for determining which users can perform a given function on a given object in a managed system, employs providing those Users with specific access rights via the use of permissions. Often these permissions are also able to be granted to collections called Groups, to which Users are added. The combination of Permissions and Groups provides the ability to provide as atomic a dissemination of rights across the User space as possible. However, this granularity comes at the price of reduced efficiency for managing the created permissions and more importantly the Groups that collect Users designated to perform sets of actions. Essentially the Groups serve as access control lists in many systems, which for the variable and often changing environment of business applications means a need to constantly update the ACL’s (groups) in order to add or remove individuals based on their ability to perform certain actions. Also, the…