You need to only deposit 12,500 € in the bank account of the GmbH you want to create as capital (Stammkapital). The founder (Gesellschafter) have then an obligation to pay the GmbH the other 12,500 € at a later date. The CEO (Geschäftsführer) can request that the Gesellschafter pay the rest of the capital.
The CEO can use the capital to establish the business. It can be used to pay wages, buy hardware etc.
Of course there are obligations for the CEO to not let the GmbH go bancrupt.
> Maybe you may also want your tool to serve your workflows and not the opposite.
This sounds like you claim that pijul serves all workflows well, which would contradict my own experience. I'm so used to think in branches / PRs (to display a history and showing lineages), that I find the current way of handling channels/patches of pijul alien. Right now I would need to break my workflow in my daily operation to use pijul.
Isn't your comment then very specifiy for that installation of yours? When you use MS Teams in a "normal" O365 environment, then every feature you described for IRC is possible with weebhooks and the cards API. Simple CURL based integration.
Only if you define "undefined behavior" as in a very constraint sense (as in "the language specification doesn't specify the behavior").
But CPU architectures also have undefined behavior. ARM for example calls these "UNPREDICTABLE" and "CONSTRAINED UNPREDICTABLE". Have a at the Armv8 architecture reference and grep for those. Lot's of ways to write programs in pure assembly with undefined behavior too!
x86, 6502 and Z80 etc all have undefined / unpredictable behavior too.
The CEO can use the capital to establish the business. It can be used to pay wages, buy hardware etc.
Of course there are obligations for the CEO to not let the GmbH go bancrupt.