The Assothink approach involves three complementary levels.
- A general theory of associative intelligence
- The Assothink model
- A set of hardware and software architectures implementing the model
The three levels are readable as separated parts (sets of articles) in this wiki.
An abstract provides a business oriented summary.
Assothink is a project of Philippe Gonze.
The assothink theory: overview
The Assothink theory is both descriptive and elaborative. It is descriptive when attempting to describe parts of natural intelligence processes. It is elaborative when trying to set up forms of artificial intelligence.
Unlike other approaches (ontologies, dictionaries, thesaurus), the Assothink approach tends to manipulate concepts free from any kind of language anchoring. At the basic level, concepts are intrinsically unnamable objects.
The key hope in the assothink theory is emergence. This clearly distinguishes Assothink from reductionnist initiatives (see "reductionnism vs emergence"),.
A more detailed description of the theory is developped in the theory pages.
More recent document describe the theory using various simple but instructive diagrams:
The assothink model
A detailed description of the model is developped in the model pages.
The standard computers are poorly adapted to the need on an associative parallel software, like Assothink.
So several architectures are considered, more or less realistic, more or less expensive.
The currently worked architecture (2012, 2013, 2014) is the A3 architecture.
You can directly access the online web application (basic architecture) on www.assothink.com (note: currentlydisabled).
Various technical notes related to the software are described in the software pages.
Additional internal notes
The current and planned development are in the Roadmap.
Originally the project name was Alex. Both names refer to the same project, but Assothink is used for the model and for the theory, while Alex would be used to name the emerging object with AI capacities.
And here is an overview of the Alex phasing process.
Project sizing and status (as of end of 2016)
The project hibernates since 2014, the main reason being its global size (human resources, staffing, time horizon, financial resources).
It is now considered that
- a minimal staff would include 3 programmers
- a reasonable and effcient staff would include 3 more profiles (including probably an advanced linguist).
- staffing might give possibly work to 20+ profiles (depending on the assigned goals)
- financial resources for entreprise-based project should then be at least 200 k€ per year during at leat two year
- public money is certainly available for such projects (european ? , national ? , chinese ? ...) but public money requires academic frame or enterprise frame (with mid/long term vision)