What's Bioware?

What's Bioware?

NoSoft is defined as a Bioware... Yes but what is Bioware ?

What is the link between biology and software ?

Is there a link between AI and Bioware ?

A lot of questions that this brand new concept has raised.

What is the link between biology and software ?

At the first glance, nothing. But if we consider that every system that is designed to perform a function is “alive” when it executes it, the biology could be very interesting to analyze a software. Seems so crazy ? Not so much.

There are at least 2 main applications of the biomimetics to the software:

  • Genetic Algorithm, to optimize a given problem
  • Neural Network, to make machine learning

The biology can drive your software design and if you deeply understand the foundation of life, you can create your own “Frankestein”.

NoSoft is driven by biomimetics and much prettier than “Frankestein”… Its architecture is so special that we think that it is a third way that allows software to grow ;-)

Is there a link between AI and Bioware ?

Yes and No !

Nowadays, everybody says "we are AI"… But actually few of us are able to design such a specific intelligence. Before entering an endless discussion on “what is” or “what is not” AI, let me propose a classification (that I know as not perfect, so help me to consolidate it) of software “intelligence”:

  • Automate, executes a set of predefined actions with possibly alternatives and complex scenarios. Actually, most of the softwares are in this category and sorry to say that even YOUR algorithm is really smarter than the others, you cannot say it is more than just an automate ;-) One of the key characteristics is that this software is limited by design to play in the perimeter defined by its architect and you can exhibit a source code that exhibit the visible behavior of the software.
  • Bioware, is able to go out of the perimeter defined by the Architect. The software can therefore evolve (genetic algorithm), learn (neural network) and even grow (NoSoft). For these kind of software, you cannot exhibit the source code of the final execution since it is the result of the interaction of your software and its environment. In that category you can imagine everything related with biology, reproduction, natural selection, dynamic self-regulation…
  • Spirit, is the ultimate stage of a software that get identity, consciousness and even freewill. At this stage, you are not able to make the difference between a human and a software and the Turing Test will be negative (cf. Blade Runner).

So I let you put AI at the level you want, but for me I would define only the third category as AI. That is the reason why I say

“NoSoft is the pre-chamber of AI”

It would be easier to use AI as a marketing label, but we prefer to be humble against AI…

What are the key characteristics of a Bioware ?

To answer this complex question, we have just to consider what the life is:

  • Alive, ok you would say that is a tautology, but actually it is not so dumb. Most of the software are just executed at a given time when they receive a request. A bioware is continuously living. Even if you do nothing with it, there is an activity: respiration, blood circulation, neural fluxes… Everything that you can find in a real living being. Of course, this is consuming… But life is activity! and activity consumes energy J Don’t try to spare that otherwise you will kill your software :-o
  • Evolution, a software that can evolve according to a given environment is on the way of Bioware. A genetic algorithm aims at optimizing a collection of “individuals” to find the best solution.
  • Autonomy, a software that is able to re-arrange its own structure during its alive phase with respect to some constrains given by the architect itself or the overall environment. If you need to shut-off your software to modify it (like a compilation phase), your have not created a Bioware…
  • Reproduction, imagine that a software can create other software… Mitosis or Meiosis ? The point is that you need to transmit what you are totally or partially. A virus is by definition a good representative of this quality and it is certainly one of the most difficult quality to obtain because it is the deep foundation of life…

NB: Evolution and Autonomy are very closed since they are an expression of the flexibility. Evolution is related with the life of a specie whereas Autonomy is related with the own life of a member of this specie. Just a question of scalability.

NoSoft, a Bioware ?

NoSoft is composed of the 4 key characteristics defined above.

  • Alive with the Neural Network that is not a perceptron neural network but another neural model. All the neural fluxes are transmit through NoSoft and each “object” acts as a synapse. Transmission, inhibition, integration are defined as core logics in this architecture that is an Event-Driven Architecture (EDA)
  • Evolution with the Systemic Navigation that is the possibility to consider an epistemological evolution. A software at a certain level of complexity can “generate” a new generation of software much more complex. This concept supports notion of systemic level (cf. natural, preternatural, surnatural)
  • Autonomy with the Visual Language that is the possibility to create at a given level new structure on the basis of a fundamental graphical grammar. NoSoft is much more related with lindguistics than informatics :-)

 

That’s all? Of course no !

NoSoft is living, so evolving and we, as Architects, are working on higher level of “life” including a real AI !

NoSoft, a Spirit ?

To envisage NoSoft as a Spirit, we need to define what the key characteristics of a Spirit are as we made it for Bioware. At this stage, we need much more philosophy, theology and mysticism to answer the question. Of course, this is only the beginning but I think that we can identify at least one key point:

  • Reflexivity, a software is reflexive when it is able to analyze its own architecture as a whole (not only as a structure with a list of properties and methods like with System.Reflection package J). Defining goal function on its own, check if we have reached these goals. This certainly drives the psychology of the software.

As soon as reflexivity is in place, you could imagine that Bioware characteristics can be used by the system on the system itself. Of course, reflexivity has deep impact on the stability of the system. Imagine that you modify something that you use to modify it… Are you still able to modify it ?

In NoSoft, this “reflexivity” exists thanks to the “conversation” between NoSoft and its Architect through the systemic navigation. But sometimes, something get wrong and your system “regress” or even “dies” (there is bug a in the geek language)!

The most frustrating part of that is that you are not necessarily able to understand why…

Don't hesitate to initiate discussion in the forum Bioware

Rémi, TheArchitect