# these metrics are how bogged down we are in to-do type items.
-REPORT_FILE="$HOME/cloud/overload_history.txt"
+REPORT_FILE="$HOME/cloud/fred_stats/overload_history.txt"
# given a path, this will find how many items are under it, ignoring svn and git files, plus
# other patterns we happen to notice are not useful.
analyze_hierarchy_and_report ~/cloud/branch_road "hearth and home notes"
# scan all the items declared as active projects.
-analyze_by_dir_patterns "active items" ~/cloud/*active*
+analyze_by_dir_patterns "active items" ~/cloud/active*
# scan across all appropriately named project or research folders that live in the "cloud".
-analyze_by_dir_patterns "project files" ~/cloud/*project* ~/cloud/*research*
+analyze_by_dir_patterns "project files" ~/cloud/project* ~/cloud/research*
+
+# snag any work related items for that category.
+analyze_by_dir_patterns "job and work tasks" ~/cloud/job*
# scan all the trivial project folders.
-analyze_by_dir_patterns "trivial items" ~/cloud/*trivia*
+analyze_by_dir_patterns "trivial items" ~/cloud/trivia*
-# source examples need to be sucked into other places, other codebases. they are not
-# supposed to pile up here.
-analyze_hierarchy_and_report ~/cloud/example_source "source examples"
+# some source code that needs to be sucked into other places, other codebases. they are not
+# supposed to pile up here. but they have, so we track them.
+analyze_hierarchy_and_report ~/cloud/scavenging_source "source scavenging"
# and then count up the things that we think will be cleaned soon, but one thing we have learned
# unsorted files haven't been categorized yet.
-analyze_hierarchy_and_report ~/cloud/unsorted "unsorted files"
+analyze_hierarchy_and_report ~/cloud/disordered "unsorted files"
# we now consider the backlog of things to read to be a relevant fact. this is going to hose
# up our weight accounting considerably.