diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index 1e6a2f04..fdc472ba 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -26,6 +26,22 @@ FIRST CLIENT SOURCE CODE COMMIT JAN 3rd 2019
 todo: dbutil erase db new tables not added!!
 	should it keep config values so user can erase trial db but keep all their settings and logo and shit?
 		YES DOCUMENT HOW TO **COMPLETELY** ERASE WITH CONFIG SETTING AND WHAT IS KEPT WITH REGULAR LICENSE ERASE
+	holup, from server todo previously:		
+todo: AYANOVA_SERVER_TEST_MODE  Is this a thing anymore?  I think I need to remove it as an environment variable and all the startup code to go with it
+todo: AYANOVA_PERMANENTLY_ERASE_DATABASE does more than that, also resets dbid, should this option name be changed to something more dire
+	it sounds just like the option in ayaNova to erase all data but those are two different things
+	"permanently" is redundant as well.
+todo: permanently erase db startup thing, should it really exist?
+	It will zap the dbid so a user might expect to just use their old license but it wont' fetch again
+	we could issue a new key to replace with the new dbid and also issue a revoke key for the old dbid so that 
+		there can be no fraudulent use this way.
+	I guess it's a rare situation and if the option to delete is there people will surely fuck up and use it unintentionally?
+		or maybe not
+todo: could be a presentation issue but erasing the database and "permanently" erasing the db do two different things completely
+	Maybe change the biz object erase to empty or remove all data or something along those lines
+	If it requires too much explanation then it's probably mis-identified as to what it does
+
+
 
 todo: mirror remove not used settings in regular user notify subscription to avoid duplicate problem there too with invalid or more likely hidden and hard to diagnose settings
 rockfish b4beta cases