diff --git a/.obsidian/plugins/obsidian-toggle-list/data.json b/.obsidian/plugins/obsidian-toggle-list/data.json
index 7ee7a44..1c40d4a 100644
--- a/.obsidian/plugins/obsidian-toggle-list/data.json
+++ b/.obsidian/plugins/obsidian-toggle-list/data.json
@@ -9,7 +9,7 @@
     {
       "index": 0,
       "name": "Progress Checklist",
-      "tmp_name": "Command 0",
+      "tmp_name": "Progress Checklist",
       "bindings": [
         0
       ],
@@ -32,9 +32,5 @@
       ],
       "states_dict": {}
     }
-  ],
-  "registedCmdName": [
-    "Progress Checklist-Next",
-    "Progress Checklist-Prev"
   ]
 }
\ No newline at end of file
diff --git a/benjamin-obrien.md b/benjamin-obrien.md
new file mode 100644
index 0000000..81e6dfb
--- /dev/null
+++ b/benjamin-obrien.md
@@ -0,0 +1,7 @@
+---
+aliases:
+  - Ben
+title: Benjamin "Ben" O'Brien
+tags: []
+---
+# Benjamin "Ben" O'Brien
diff --git a/cincinnati-convention-center-hotel.md b/cincinnati-convention-center-hotel.md
new file mode 100644
index 0000000..5a215e7
--- /dev/null
+++ b/cincinnati-convention-center-hotel.md
@@ -0,0 +1,12 @@
+---
+title: Cincinnati Convention Center Hotel
+tags: []
+up: "[[conest-projects]]"
+---
+# Cincinnati Convention Center Hotel
+
+## TODO
+
+* [ ] Feeders
+    * [ ] 3NT3, 3NL3 (split from 3NTL3 in previous revision) moved over 100ft
+        Feeds to company switches (and possibly others) will need to be remeasured.
diff --git a/heuristics.md b/heuristics.md
index b0eb3a7..1e7dab0 100644
--- a/heuristics.md
+++ b/heuristics.md
@@ -1,9 +1,9 @@
 ---
 aliases:
   - rule-of-thumb
+title: Heuristics
 tags:
   - type/encyclopedia
-title: Heuristics
 ---
 # Heuristics
 
@@ -56,3 +56,8 @@ is to _forecast as accurately as possible_.
 
 Realism is noble, granted,
 but instrumentalism is far more practical.
+
+## See Also
+
+* [Map--territory relation - Wikipedia](https://en.wikipedia.org/wiki/Map%E2%80%93territory_relation)
+    * "Mistaking the map for the territory" (logical fallacy)
diff --git a/timestamped/2026-05-06_14-00-10.md b/timestamped/2026-05-06_14-00-10.md
new file mode 100644
index 0000000..c00b423
--- /dev/null
+++ b/timestamped/2026-05-06_14-00-10.md
@@ -0,0 +1,23 @@
+---
+id: 2026-05-06T14:00:10-0400
+title: 2026-05-06 14:00:10
+tags: []
+daily: "[[2026-05-06]]"
+---
+# 2026-05-06 14:00:10
+
+Relevant to [[feeders-takeoff]]
+for [[cincinnati-convention-center-hotel]].
+
+> [!quote] [[zane-meyers|Me]] 2026-05-06 13:36 via Microsoft Teams
+> Hey Joel, \[previous estimator\]'s feeder takeoff used aluminum grounds
+> instead of copper like the schedule wanted in the GMP set
+> and still does in this one.
+> Are we assuming that's fine from the proposal
+> "Aluminum 100A and above | Per Schedule & Spec"?
+
+> [[joel-jansen|Joel]] 2026-05-06 13:41 via Microsoft Teams
+> Yea, if we are allowed to use Aluminum,
+> we should be good to use aluminum grounds as well
+
+[[benjamin-obrien|Ben]] confirmed.
diff --git a/wiring-method-selection.md b/wiring-method-selection.md
index 06ed263..dfa3e92 100644
--- a/wiring-method-selection.md
+++ b/wiring-method-selection.md
@@ -19,9 +19,18 @@ It's my intent that if a rule holds in _all_ cases,
 even the super special one you're thinking I didn't consider,
 that I specifically say so.
 If I didn't say so, and your edge case is not covered,
-you should seek clarification.
+**you should seek clarification.**
 %%
 
+## Wire Material Selection
+
+[[pdi-estimating]] preference is to use aluminum conductors
+
+If [[pdi-bid-estimating|Bid]]'s proposal sells aluminum 100A and larger
+use aluminum for grounds, even if the feeder schedule uses copper.[^1]
+
+[^1]: [[2026-05-06_14-00-10]]
+
 ## Example Wiring Method Selection
 
 Below is an example Wiring Method Selection