It is assume that automated processes triggered by maven build scripts need to be 1)told what to do and 2)the same build scripts need to be told what specific steps need to be executed and in which order in order to accomplish each task
if an automated processes in danger of going fubar becomes a 'statistical probability' ..it is up to us (hopefully) intelligent humans to 1)note the aberrant behavior (violation of multiple rules) 2)pull smartly on the choke collar (i.e. shortcircuit the task behavior and quiesce the process) if the automated process does not respond <appropriately> in a <preconfigured> amount of time..the off switch should be considered.. to wit: Cause: http://www.usatoday.com/story/money/markets/2013/07/02/headwinds-loom-for-stocks-in-second-half/2484555/ Effect: http://money.cnn.com/2000/03/30/markets/markets_newyork/ Because these scenarios have become a reality one of the mission statements of CTOs of Financial Houses is to monitor all financial transactions by monitoring software on 24/7/365 basis... the rule-based engine of the monitoring software will 1) monitor aberrant behavior by applying violations of transactions to preconfigured 'rules' and 2) apply appropriate shortcircuits when <n> number of preconfigured rules have been violated (speaking of shortcirtcuit we should probably continue this discussion offline) Martin ______________________________________________ Jogi és Bizalmassági kinyilatkoztatás/Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Ez az üzenet bizalmas. Ha nem ön az akinek szánva volt, akkor kérjük, hogy jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának készítése nem megengedett. Ez az üzenet csak ismeret cserét szolgál és semmiféle jogi alkalmazhatósága sincs. Mivel az electronikus üzenetek könnyen megváltoztathatóak, ezért minket semmi felelöség nem terhelhet ezen üzenet tartalma miatt. Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Date: Wed, 14 Aug 2013 14:01:33 -0600 > From: vektor.kni...@gmail.com > To: users@maven.apache.org > Subject: re: agency theory and software development > > Given the future of computation and being in a technological > singularity, how do we divert a total disaster when the 'machines' have > solid bodies? Since Hume, we have had theories about "ghosts in the > machine", and if we look even at the beginnings of AI since MIT, it's > clear that the software often has a mind of its own and takes us on > courses we never intended to go on. > > Finite-state automata, with no solution to the Halting problem, actually > have exhibited free will and agency. In that respect, how do we > reclassify our notions of human and animal rights when such a species > actually has the entire compendium of human history, knowledge and the > universe? Think Data from Star Trek. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org >
