Seedea, scalable creativity
Xye, consultancy for serious creators
Seedea : leveraging EE on your cognitive swarm
Associate APIs to a specific usage within Seedea, the focus is to foster those new automated tool in order to favorably allow innovation and creativity (NOT to use yet another new trendy API).
Using a personal notation like "nodea" (proposed during the early research period) or "microservices" could give more uniqueness but could also be confusing at the same time ("yet another term").
|cf dedicated section in the creativity article
|Specialized engines should be based on the category detected (cf following service)
|Very basic but still useful especially for professional presentation.
|Facilitate micro-blogging/SMS conversion
|Does not seem to provide an API so far!
|Suggest one or many categories amongst : technology, science, philosophy, art, ...
|Having a quick view of the content of the page.
|Being able to share interesting ideas with others quickly.
|Check the length of the sentences and infer on the expected public.
|Non-Seedea microservices tracking
|Being able to track tools but based on local running softwares, not internal or external services.
|Presence of keywords and length of their associated sections.
|Check if the user added key structuring elements (title, keyword, visual, references, etc).
|Long-term statistics of usage and suggestion based on patterns of successes and failures.
|Used to keep the user focused on his task.
|Opportunity time slice detector
|Probability of lowest edit moment based on activity statistics.
|Used to make suggestions without disturbing the user.
|(CAEE based) Exploiting bibliographic data to track back the origin of the key component of the idea
|Providing a visual but also suggestions (see how other fields previously helped the discipline progress, Suggest similar paper, ...)
|(CAEE based) See what user with similar method or interested liked recently (Ev. Epistemic Actions?).
|Evolve the network of services based on personal usage.
|check periodically the status of each service (and compare it to the overall situation
|Freq X or with event Y : try <test-value,expected-result> then do A or B. Also store the response time, compute its average and its evolution over time (to predict degrading performances and provide a potential alternative solution).
|Combining the previous services to maximize efficiency.
|Our core real core added value : methodology (EE) supported by tools (AI netMAS)
In general see WikiBot regarding internal mechanisms.
Introduce microservices (bots/nodeas/affordances/epistemic actions) gradually to users based on results from CAEE.
Simulating the Ontogenic View (OV) based on Phylogenic View (PV) studied. Eventually Mixed View (MV) can be used to initialize a user account (using another user as a model).
This chronological approach should facilitate adoptions of microservices more efficiently.