SAG / ARCHITECTURE NOTE
Unobserved Is Not 0%: Why Preserving Nulls Is a Mark of Professional Reporting
A model that preserves the distinction between no data and a measured zero. If unknowns are filled in as zero, customers may mistake a data-availability problem for a service-performance problem. Automatic chart defaults pose the same risk.
What Is Missingness Semantics?
It is a model that preserves the distinction between no data and a measured zero. This note treats missingness semantics not as a feature name, but as a responsibility spanning input, transformation, and output. To trust an analytical result, it must be possible to trace what data was received, what was verified, and how far the conclusions can go.
Why Is This Technology Needed?
If unknowns are filled in as zero, customers may mistake a data-availability problem for a service-performance problem. Automatic chart defaults pose the same risk.
Design Principles and Data Flow
Distinguish measured values, verified absence of exposure, failures, and disconnected states. Check how nulls are converted to numbers, and provide the reason and the scope for recollection.
Observation state → Validity assessment → Separate measured values from missing data
Each stage must not relabel the success of the preceding stage as the performance of the next. Recording identifiers, time periods, and verification status across stages makes it possible to locate omissions and errors and determine what needs to be checked again.
Connection to the SAG Architecture
SAG does not convert unobserved data into rank 0 or 0%. Example data is also distinguished from a ledger used to fill in months with no measurements.
SAG’s operational value lies in connecting this relationship to pages and questions, comparison results, and improvement tasks. Instead of reading only the numbers, customers can review both what needs to be supplemented and the basis for the assessment. Patterns that require further application should be interpreted within the scope of the relevant paragraph.
Illustrative Example and Assessment Criteria
If all 10 valid responses in an illustrative example contain no citations, then 0/10 = 0%. If no responses were received, do not calculate using a denominator of 0; report that no data is available.
The example above is provided to explain the structure and calculation; it is not measured performance from a specific customer. Actual reports must link the selected period, subjects, observation conditions, and original records so that the same assessment can be checked again.
Practical Verification Checklist
| Flow stage | Item to verify |
|---|---|
| Observation state | Check null conversion |
| Validity assessment | Distinguish measured 0 from unobserved |
| Separate measured values from missing data | Show the number of excluded records |
Check that the same meaning is preserved not only for valid inputs, but also for empty, duplicate, and differently conditioned data. Linking verification items to completion criteria can reduce the gap between feature descriptions and actual operations.
Limitations and Considerations for Use
Comparisons are also unstable when many records are excluded. Do not show only favorable results that omit missing data; disclose the number of excluded records and the conditions.
Research and Official Documentation
- PostgreSQL JSON Types — Official documentation describing the characteristics and limitations of JSON storage types.
External sources provide background on the design topic above; they do not certify every SAG implementation or customer outcome. Interpretations of this note and its illustrative example are organized around SAG’s operational structure. Source checked: 2026-10-06.
Further Reading and Feature Information
- Related architecture note
- Service preview connected to missingness semantics
- Feature-specific FAQ
- Discussing implementation scope
How to Continue Reading About This Technology
Distinguish monthly samples, the denominator for citation rate, competitive benchmarks, and Goal achievement rates.
SAG / KNOWLEDGE LINKS
