From 20316c533f7f7c61c180c7cb3c80ebb76e894963 Mon Sep 17 00:00:00 2001
From: tegwick <bernd.worsch@gmail.com>
Date: Sat, 4 Jul 2026 00:31:34 +0200
Subject: [PATCH] Recorded decision

---
 DECISIONS.md | 54 ++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 54 insertions(+)

diff --git a/DECISIONS.md b/DECISIONS.md
index 1530d63..de76743 100644
--- a/DECISIONS.md
+++ b/DECISIONS.md
@@ -37,3 +37,57 @@ APPROVE: scoped path and confirmed binding are acceptable
 APPROVE: We fixed the path using coulomb as the org/tenant.
 
 ---
+
+## Forgejo hostname and exposure model
+
+**Date:** 2026-07-02  
+**Decided by:** human  
+
+the hostname shall be forgejo.coulomb.social. The exposure model is private repos by default. We will use the transition from gitea to forgejo for closing down public access and establishing credential handling to have convenience when working with the repos. Gitea can and should remain reachable during transition.
+
+---
+
+## Forgejo SMTP and sender identity
+
+**Date:** 2026-07-02  
+**Decided by:** human  
+
+We will use forgejo@coulomb.social
+
+---
+
+## Forgejo package registry scope
+
+**Date:** 2026-07-02  
+**Decided by:** human  
+
+We should support the full range from the start.
+
+---
+
+## Forgejo Actions runner isolation model
+
+**Date:** 2026-07-02  
+**Decided by:** human  
+
+we will try to go with isolated host runners, with least-privilege credential boundaries.
+
+---
+
+## Forgejo backup target and restore cadence
+
+**Date:** 2026-07-02  
+**Decided by:** human  
+
+We will need to figure out the details, but i want to use backup.coulomb.social as the hostname with a backend we need to figure out yet.
+
+---
+
+## Forgejo cutover and rollback strategy
+
+**Date:** 2026-07-02  
+**Decided by:** human  
+
+We will do a staged migration and lock the gitea repos of transitioned repos but keep gitea until everything has been transfered and just then start a 14day trial phase and after that retire gitea to the backup.
+
+---