How do you manage Nullability Design in enterprise schemas?

In enterprise schemas, almost all fields should be nullable unless it is fundamentally impossible for the entity to exist without them.

GraphQL propagates errors on non-null fields to the parent. If user.age is non-null, and the database fails to fetch the age, the entire user object becomes null. To build resilient distributed systems, fields should default to nullable to allow partial success.