You are looking at historical revision 5951 of this page. It may differ significantly from its current revision.
Iron Chicken is Chicken Scheme, but on a wiki. Specifically, it's Chicken Scheme running on an external server, but analysing wiki content, processing it, and writing the results to the wiki.
But it doesn't stop there. The software itself, the scheme programs, also reside on pages on the wiki, and can be edited and recompiled using the normal wiki editing process. And of course that means that your code is instantly public and your code development environment is instantly collaborative.
Because the chosen wiki environment is the English Wikipedia, by far the largest and busiest wiki in the world, this means that any one of the thousands of regular Wikipedia users, or indeed any one of the millions of daily visitors to Wikipedia, can edit your code, and you are free to accept or reject the changes.
Iron Chicken is also user-enabling. Once a script has been written, it can be published in a form that anybody can use by typing a few brief phrases into a wiki page. They won't even know they're running a Scheme program. Unless you tell them.
Iron Chicken enhances the wiki environment by providing it with external processing power without requiring the core wiki engine to be changed. The software is 100% Chicken Scheme and runs on computers external to the Wikipedia server itself. Anybody who can install Chicken Scheme (and, for the time being, runs a UNIX-like system) can run the software.
Iron Chicken is part of a project to create a new concept: a public wiki bot, an intelligent software tool that can be used by anyone.
Iron Chicken is (September, 2007) in advanced alpha state. The account TonyBot on English Wikipedia has made over 500 automated edits since it was authorized as a bot a few months ago. Running on Tony Sidaway's home computer, it is now capable of automatically recognising, dispatching and executing user-level queries based on scripts written in Scheme on the wiki.
If anyone is interested in any aspect of this project, please contact the principal developer, Tony Sidaway, <firstname.lastname@example.org>