coulomb/email-connect
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Added decision documentaion
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source
This commit is contained in:
tegwick 2026-07-10 21:42:19 +02:00
parent 72366cde17
commit ae7d0fbf1c
1 changed files with 27 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

27
DECISIONS.md
View file

@ -28,3 +28,30 @@ I want to move to more automation, this is one step needed to go on.
Sufficient for now
---
## DR-3: External identity path for business clients (lightweight vs NK-WP-0011 Keycloak)
**Date:** 2026-07-09
**Decided by:** human
We will go with A for the lightweigt version and just follow up with B if we meet actual demand later.
---
## DR-1: Tenancy model for vergabe-teilnahme commercial offering
**Date:** 2026-07-09
**Decided by:** human
We will do C and allow for early customers to easy starting serving customere but move on to resource cost optimization early.
---
## DR-2: coulomb.social rebuild architecture (Core Hub extension vs standalone app)
**Date:** 2026-07-09
**Decided by:** human
We will go for B as Coulomb Social is it's own Application. Managed by connecting it with our infrastructure but destinct in its purpose and operations model. It is an Application for the Binky Hedgehog GmbH as another App might be provided to other clients. It should not be relevant the the ecosystem as a whole is provided by Binky Hedgehog as the organization creating coulomb and holding the domain and forgejo repos.
---