4 12 19

upload cert, etc. v
song v
do multiness to caw
- just caw (which has multiple preds in dict), and uses data rather than predicate name specifiers
	- can specify data using qa, eg grammar check, translate, spell check
	- do comp phil algs
	- ff not resynth formulas (with caw)
	
	- replace data in found alg with mr data
	
	- organise day (what you do, how and details) to find initial 10 in mr
	- " in further 10s
	
	- (qa eg. what do you need to do with it (when, who, how, how many, is there anything else?)
		- how->algorithmic transformations
		- finished with data->end of alg) - difficult to write desc-dict and dict-alg rels because desc might change
		- ask questions about recursion (not caw, just qa)
		- run all not caw
		- x algs more complex, write them separately
		
	- ask whether any repetitive data or data that could be processed automatically appeared during day
		
	- ask for rudimental transformations x just data, try the existing transformations or ask user to enter their own
	- x data needs transformations x just data - only find, randomise structure if not manually entered (generate data based on mp, etc.)
	
	base algwriter algs on combos ("10s") of previous algorithms
	- replace data stubs in existing data formats with mr etc.
	
	- don't worry about data changing rather than alg changing because it would have been like it eventually
	
	- dict of combo ns (numbers e.g. ped-twouses-1-1, filenames of algs - files with queries, algs (types optional)
	
	%%
	
	- do algs (not made up ones), then generated ones
	- alg that writes content is nec too (perhaps based on brdict2, self-other, approach brdict1, random grammar)
	- change variable names as well as data
	
10 12 19

multi-predicates x because other predicates need their own specifications, which are too difficult to find, (and modes of predicates written by the algorithm cannot easily be worked out x they are known because the predicates were written).

- could give series of specifications, the relations between give rules of alg

- not multi pred because can have enough variety of preds to cover multi clauses, multi levels, and can join together sessions of caw because connections between alg parts need to be custom done.