1.7 KiB
Decision Log
Auto-generated by the Custodian State Hub.
Operate at build-stage security posture; defer production policy enforcement
Date: 2026-07-02
Decided by: human
We are in build stage with the infrastructure as a whole. We will tighten security step by step but it is not yet strictly necessary.
SECRETS-WP-0004 — approve warden-sign auth-capability lane prod apply
Date: 2026-07-02
Decided by: human
I want to move to more automation, this is one step needed to go on.
Defer consumer-side contract-parity drift mode (WHYNOT-WP-0003 T09)
Date: 2026-07-02
Decided by: human
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.