0022: Scalar constraints and characteristic states
Borrowed source and Effective data descriptions expose named scalar constraints with exact numeric values, nonnegative mathematical counts and positive steps. Property characteristics separately identify authored values, including inheritance, and specified defaults; existing Boolean access remains compatible. Contributor origins stay separate, following ADR 0020: Owned effective views and nearest origins, and no value is inserted into composed JSON or interaction data.
Named access keeps ordinary callers from selecting raw Quality Names or reconstructing shape checks, following ADR 0010: Domain-oriented library and caller simplicity. Exact numbers and unavailable capability retain ADR 0012: Exact numbers and JSON input policies. Effective inspection’s existing default explanation carries its established Boolean value in human output and an optional JSON default_value field; finite presentation omission preserves the independent typed characteristic. This additive report field follows ADR 0011: Machine-readable report contracts.
FullBaseline also establishes ordinary scalar model meaning in the owning effective description, including final alternatives, without a sample or a general satisfiability proof. Mathematical scalar interpretation and exact const equality remain separate from formal numeric and literal admission. Restricted donor roles, unknown extensions and finite capability retain scoped unfinished observations. The model meaning contract gives the finite completion rules for M042, scalar M043, M045 and M046.
Considered Options
Changing existing Boolean methods to return characteristic states would impose an unnecessary migration. An owned scalar summary would duplicate values and add retained allocation without a demonstrated caller need. A typed numeric-selector argument could enforce the same rules, but named accessors fit the established domain interface and cover text and flags as well. Calling an inherited authored value a specified default would lose the distinction between reuse and absence; treating documentary default data as the source of Property capabilities would conflate two different SDF concepts.