docs(hardware): record DDR4-2666 RAM type for mf01/mf02, fix mf00 status

Add ram_type (DDR4-2666 non-ECC UDIMM) to mf01 and mf02 frontmatter, and
set mf00's placeholder status to staging so the overview index regenerates.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

docs/hardware/mf00.md

@@ -1,7 +1,7 @@
 ---
 hostname: mf00
 kind: server
-status: definitely-not-a-valid-status
+status: staging
 location: The pile
 cpu: "?"
 cpu_cores: "?"

docs/hardware/mf01.md

@@ -7,6 +7,7 @@ cpu: Intel Core i5-8500 @ 3.00GHz
 cpu_cores: 6
 cpu_threads: 6
 ram_gb: 8
+ram_type: DDR4-2666 non-ECC UDIMM
 storage_gb: 40
 storage_type: nvme
 nic_gbps: 1

docs/hardware/mf02.md

@@ -7,6 +7,7 @@ cpu: Intel Core i5-8500 @ 3.00GHz
 cpu_cores: 6
 cpu_threads: 6
 ram_gb: 16
+ram_type: DDR4-2666 non-ECC UDIMM
 storage_gb: 40
 storage_type: nvme
 nic_gbps: 1

docs/services/coursemanagement.md

@@ -0,0 +1,78 @@
+---
+name: event management
+status: proposal
+---
+
+# Problem statement
+
+Not the ad-space - but the event management, sign-up space.
+
+# Operative user requirements
+
+- Overview of events and their repetition
+- ID-management
+  - Only the needed data
+  - ID = email, and so we can let you know if we cancel
+  - Name - To give the instructor a ledger to tick off
+  - Comment field
+  - Profile picture
+  - People who are signed up, can see others who are signed up for the same event
+  - Members are automatically set up
+    - Login via OM-key-chip?
+- Communication system
+  - COM = email
+  - Receipt for sign-up
+  - event materials
+  - Reminders...
+- Open standards
+  - Vcard or similiardstandard
+  - JSON or XML
+  - FLOSS (MIT or lighter)
+- SSO
+  - Authentik
+  - Oauth
+- Security
+  - Own hosting
+  - 3-2-1 backup
+  - Uptime: 99.9 (but we try for more)
+  - HA
+  - Loki+Grafana Alloy+Grafana alerts
+  - Supply-chain / dependencies
+  - GIT
+- Separation of concerns
+  - Sign-up and things directly related to each event
+  - event catalogue/program
+  - Advert
+    - SoMe
+    - Newsletter
+    - MeshCore
+  - Who graduated
+- Admin stuff
+  - Wait lists
+  - Max number of participants
+- SSoT: Where is the event described
+  - Here or on Facebook?
+- Adding new events
+  - Templates
+  - Repeatable
+  - Idea: All can add new events
+  - Depreciated for now: Is English an option?
+- How are people updated on what happens
+  - RSS
+  - Dedicated newsletter
+  - Bot on Matrix
+- Shareable - so no login unless required. Short links/SoMe/e-mail/chat...
+- Application in Danish
+- Responsive
+- GDPR compliant
+- High trust (readable links), HTTPS
+- Do one (a few) things well
+- Modular - so we can drop or add things
+- Very clear for the user to understand if they did the right thing
+- Easy for the user - and for the admin and the AI. Proper headers so that when you post about in on SoMe it picks up the rights graphics
+- REST-API
+
+# PoA
+
+- Marcus - Talk with Kjeld about moving over to GIT
+- PR FTW

notes/relevantLinks.md

@@ -0,0 +1,8 @@
+# Links of general relevance to the project
+
+- https://nordicmedialab.dk/#hvorfor
+- https://zensocial.dk/
+- https://oase.app/oase/46ec46bf-5445-4a32-bb21-ada8a61b4b0a/join/8f84eb1a-1e07-478c-9153-6e21850141fe?spa=1
+- https://meningspunktet.dk
+- https://sustainablemanifesto.org/
+- https://www.demai.tech/