[axelfontaine]

That may be true for the "what", but certainly not for the "why".

[intelVISA]

Why is best inferred from context imo, otherwise it's a smell for a system with too much scope.

[consteval]

You can't context-out business requirements, IMO. Also code can have bugs. You need more formal requirements definition so you can compare behavior to requirements so you can find out bugs. Otherwise, how do you find the bugs?