need to make evidence decomposition print the "exact" strings now with
correct namespace.. means getting rid of the EvidenceRole stuff and
working more with the evidence namespace.

--------------

ok.. did the recursive decomposition etc (to print)
will need to have a HandleEvidence class now to have operations on
it (eg.. push it to the knowledge base etc).
** done

do we need a statement for informations?  the evidence hierarchies have
most of that information already.
i am questioning the need for this actually..  unless of course, a
statement is just the concereteness of the evidence hiearchy (sounds good)

need to get rid of the EvidenceRole stuff now (no need. the namespace is
alot better for evidence currently - unless it becomes EvidenceNamespace).

i really need the sql backend rsn.

------------------

Each concrete Evidence, must have a schema associated with it.
this is stored as a config/file (xml?).

then there is a global schema of constraints, correlations.

printing functions/ and recursive decomposition of evidence into atoms
while assocating namespace with each recursion.
******** done

then putting the final atoms into the knowledge base with the correct
namespace.

sql backend for knowledgebase.

------------------------------
time to get some build environment going (make)

-------------------------------

need to get the EvidenceRole stuff done..
need to get a state machine going for the detecives.

multithreading at some point?

need better scheduler also..

-------------------------------
signer_md5

finish up process_maps (god its bad parsing code)

ok.. how to ignore some of the process maps when doing the verification
with the binary on disk..

Have 2 generators.. they get signed, and authenticated

the generators must be able to 

the generator_process must be able to pull in many file generators (for
shared libs etc)

so.. we need a class Machine, that takes say a process or a file.. it
knows what parts are important and what equivalencies exist for
generators.

generators have filters.

a generator has a filter applied to it.

a Machine_Process
	Process_map


Generator_MultipleFile

Each Segment has a label!  this is to identify it to the signer as a seperate
piece of information.

A Judge knows all of the generators.  it gets asked to check something.
The judge knows who is responsible for generating this information.

The judge requests generation.

everyone available generates.
	the generator might request another piece of information also, to make
	sure.  the request is made to the judge.

the signer signs each of them.

the authenticator then compares them, and says which ones do not match.

--------

while not finished
	Detective must ask generators to run
	generators provide detectives with evidence
	detectives may tell the judge the evidence
	the judge may ask detectives to follow leads (based on evidence)

