summaryrefslogtreecommitdiff
path: root/project_marine_cert_prep.md
diff options
context:
space:
mode:
authorClaude Code <claude@terst.org>2026-08-15 17:59:12 +0000
committerClaude Code <claude@terst.org>2026-08-15 17:59:12 +0000
commiteb0932bddad0daa47c36cd20599944c3dc45482a (patch)
tree4b0013e72af9a56ce496d8aeede7068d36fe4389 /project_marine_cert_prep.md
Initial commit: tungsten's memory tree
Diffstat (limited to 'project_marine_cert_prep.md')
-rw-r--r--project_marine_cert_prep.md16
1 files changed, 16 insertions, 0 deletions
diff --git a/project_marine_cert_prep.md b/project_marine_cert_prep.md
new file mode 100644
index 0000000..af3ca16
--- /dev/null
+++ b/project_marine_cert_prep.md
@@ -0,0 +1,16 @@
+---
+name: project-marine-cert-prep
+description: "What the user's \"Marine Cert Prep\" doot chain is for — NMEA MEI certification study plan"
+metadata:
+ node_type: memory
+ type: project
+ originSessionId: 119bd1a5-fb32-4222-9695-fcbe2c8fd63b
+---
+
+The user is working toward NMEA Marine Electrical Installer (MEI) certification. Tracked as a 16-step locked/linear task chain in doot (see [[reference_doot_marine_codemap]] for exact IDs/DB/code locations).
+
+Created 2026-07-17. As of creation, only step 0 ("Pass NMEA DC Electrical Overview online prerequisite") is unlocked/due; the rest unlock one at a time on completion (WIP-1 chain).
+
+Plan covers, in order: the NMEA online prerequisite, ABYC E-11 DC electrical rules (7-40-72 rule, battery switch placement, AIC parameters, temperature/bundling de-rating, voltage-drop budgets), a wire-sizing cheat sheet, AC/DC grounding and ELCI/galvanic-isolation rules, a distance/dimension cheat sheet, the ABYC Marine Electrical practice exams (target >85% before booking the proctored exam), an FCC Amateur Radio General license (via HamStudy.org, focused on G5/G6/G9), and finally a logged hands-on volunteer electrical audit at Honokohau to start the 1-year NMEA experience clock.
+
+**How to apply:** treat this as a personal certification study project, not a software project — "code" work here means reading/updating doot's chain data (via DB or the chain API/UI), not writing new features, unless the user separately asks for a doot code change.