Some of this is possible in the type system like a range: From stackoverflow: https://stackoverflow.com/questions/39494689/is-it-possible-to-restrict-number-to

Some of this is possible in the type system like a range: From stackoverflow: https://stackoverflow.com/questions/39494689/is-it-possible-to-restrict-number-to-a-certain-range/70307091#70307091 https://stackoverflow.com/questions/39494689/is-it-possible-... type Enumerate<N extends number, Acc extends number[] = []> = Acc['length'] extends N ? Acc[number] : Enumerate<N, [...Acc, Acc['length']]> type NumberRange<F extends number, T extends number> = Exclude<Enumerate<T>, Enumerate<F>> type ZeroToOneHundred = NumberRange<0, 100> One limitation is that this has to be bounded on both ends so constructing a type for something like GreaterThanZero is not possible. Similarly for zip codes you could create a union of all possible zip codes like this: type USZipCodes = '90210' | ... Often with the idea you have in mind the solution is to implement an object where the constructor does a run time check of the requirements and if the checks pass instantiate the instance and otherwise throw a run time error. In functional programming this is often handled with the Option which can be thought of as an array with exactly 0 or 1 elements always. 0 elements when a constraint is not met and 1 element when all constraints are met. This [0] is a library I wrote for JS/TS that provides an implementation of Options. Many others exist and other languages like Rust and Scala support the Option data structure natively. [0] https://github.com/sbernheim4/excoptional https://github.com/sbernheim4/excoptional