new-number-type

To scaffold a new Universal number type, generate the complete file skeleton including fwd.hpp and impl.hpp headers, wire CMake, and set up test templates to validate triviality and portability compliance.

Adding a Universal numeric type requires creating fwd.hpp, impl.hpp, exception hierarchy files, numeric_limits specializations, type traits, umbrella headers, and test templates in a specific enforced creation and inclusion order.

Yes, scaffolding supports both static and elastic Universal number type variants, automatically generating the appropriate project structure, CMake wiring, and test directory layout for either configuration.

Yes, adding a Universal number type requires setting up a ready-to-edit exception hierarchy and numeric_limits specialization to enforce compliance with triviality, portability, and exception rules.

The best way to ensure correct file creation order is using an automated scaffold that enforces the required sequence for file generation, umbrella header inclusion, and coding standards compliance.

Portability and triviality checks fail when the new number type scaffold does not adhere to the required file structure, umbrella header inclusion order, or exception rules specified by Universal coding standards.