Consider storing the user's answers in constexpr variables then using the regular Assert::That syntax instead of static_asserts. This way, the program still checks compile time behavior, but can still compile and provide meaningful feedback (via ExtraMessage) instead of just refusing to compile and giving a vague assertion failure message.

Why is seq_max_v not a function? Is it designed this way specifically for the challenge?