.
FRDCSA | internal codebases | SinLess

SinLess Architecture Diagram: GIF

Jump to: Project Description | Capabilities

Project Description

The current plan is to use Weka to do the datamining. Another feature is theorem proving over states. The knowledge base is derived by formalizing sacredtexts.

Capabilities

• Get sinless micro reports to not have to pop up something. Maybe switch to unilang.
• One way to ensure accuracy of repotring ofor sinless is to have many minor sins, and to force the user to record all sins.
• Here are some ideas. all we need now is a simplistic goal system, built from the ground up, _maybe_ with some basic common sense. On the other hand, then, we should get the event logging system working, and write helper functions, EventLog, etc, so that other systems can make use and analyze log data easier. We should generalize the functions found in sinless and manager that make use of the score event system, (moving that of course into the eventlog). problemspace should visualize the eventlog data, using nodebrain type filtering. That stuff has to work inferentially.
• all agents should use sinless!
• Have system for sinless for retroactively asserting sins.
• Have expected progress for sinless, so that the person sees whether they are leraning.
• Change the name of evangelist, sinless, obviously.
• sinless/score is a good system.
• sinless should strongly forbid certain actions, like -10,000 violation or something. Then, gradually increase these, so that the user makes progress towards it.
• sinless is a major development.
• So for instance, we should have processes monitoring the ttyrec file and if they see any bad words, to call up sinless.
• sinless should express things so that it is known whether information is lacking by having plus and minus. Should also use theorem proving everywhere possible.
• Certain programs should be able to ask questions and then automatically report to sinless the violation, like alarm clock could ask about leaving room in normal form. The actual system should work using inferencing.
• That was really cool. The sinless asker just asked me and I caught I sin I otherwise would have forgotten (going outside of my room).
• sinless should sort your sins by recent frequency and ask whether you have committed any of them, every now and then.
• Ultimately maybe other people could file reports against me using sinless.
• sinless should increase the severity of the penalty for habits that are not being broken.
• Could eventually make sinless have inferencing, e.g. if you teased someone, you were talking to someone...
• sinless scores, once computed from our general goodness metric, can be retroactively corrected.
• this is a really good example of how event log should behave: /var/lib/myfrdcsa/codebases/internal/sinless/old-rsr/event-log/days/Thu Feb 17 22:30:46 EST 2005
• sinless should record what type of temptation the user experienced and log that through event stream or unilang.
• sinless should use: Feed images through http://wang.ist.psu.edu/WIPE/ to elimate pornography
• Some things to get done: finish sinless
• sinless should consider r-cran-psy
• sinless ought to have a ranking of who is the most godly.