SAG / ARCHITECTURE NOTE

Content Hashing and Change Detection: First Separate What Has Changed

A pattern for distinguishing unchanged and changed material using content hashes and structural comparisons. The more frequently pages are collected, the more collection runs accumulate. Sending inputs with no actual changes to an expensive model every time increases costs and can weaken consistency in the results.

SAG editorial · 2026-10-08 · Updated 2026-10-08

What Is Change Detection?

It is a pattern for distinguishing unchanged and changed material using content hashes and structural comparisons. This note approaches change detection through the responsibilities of its inputs, transformations, and outputs rather than as a feature name. For analysis results to be trustworthy, there must be a traceable connection between what material was received, what was checked, and how far the conclusions can go.

Why Is This Technology Needed?

The more frequently pages are collected, the more collection runs accumulate. Sending inputs with no actual changes to an expensive model every time increases costs and can weaken consistency in the results.

Design Principles and Data Flow

It is useful to keep the raw-content hash separate from the normalized-body hash. Define change rules so that insignificant whitespace and important specification changes are not treated as the same kind of change.

Page version → Hash and structure comparison → Select scope for reanalysis

Each stage should not describe the success of the previous stage as an achievement of its own. Recording the material’s identifier, time period, and validation status together makes it possible to locate where omissions and errors occurred and determine what to check again.

Connection to the SAG Architecture

This is an analysis-optimization pattern that can be extended based on SAG’s page version records. This article does not claim that a feature that can perfectly determine semantic changes from hashes alone is already guaranteed.

SAG’s operational value lies in connecting this relationship to pages and questions, comparison results and improvement tasks. Rather than looking only at numbers, customers can review both what needs improvement and the grounds for the assessment. Patterns that require additional implementation should be understood within the scope of the relevant paragraph.

Illustrative Example and Criteria for Assessment

As an illustration, consider separately a case where only the whitespace in a menu changes and one where the rated output changes. One possible design is to retain the former as a collection version, while treating the latter as a reason to review related questions and evidence.

The example above is provided to explain structure and calculation; it is not measured performance from a specific customer. In an actual report, the selected period, subject, observation conditions, and original records should be linked so that the same assessment can be checked again.

Practical Validation Checklist

Flow stage	Item to check
Page version	Define the hash input scope
Hash and structure comparison	Record the normalization version
Select scope for reanalysis	Review semantic changes separately

Check that the same meaning is preserved not only for normal inputs, but also for empty, duplicate, and differently conditioned material. Connecting validation items to task completion criteria can reduce the gap between feature descriptions and actual operations.

Limitations and Points to Consider in Application

A hash is a tool for checking identity, not proof of factual accuracy or recency. If the comparison targets, algorithm, or normalization version change, the criteria must also be updated.

Research and Official Documentation

W3C PROV Overview — A provenance framework that describes relationships between material, the activities that generated it, and responsibility.

External materials provide background on the design topic above; they do not certify every SAG implementation or customer outcome. The interpretation of how to apply this note and its illustrative examples are organized according to SAG’s operational structure. Materials checked: 2026-10-06.

How to Continue Reading About This Technology

Follow the sequence: HTML ZIP and sitemap → normalization → page version → evidence recording.