SAG / ARCHITECTURE NOTE
Goal Version Snapshots: How to Keep the Basis for Analysis from Shifting
Explains the definition and purpose of Goal snapshots, how they work, how to apply them in SAG architecture, and a practical checklist, drawing on research and official documentation.
Definition in one sentence
A Goal snapshot is a way to save the analysis objective, questions, competitors, language, and scope as an immutable version at a specific point in time.
Key answer: If the criteria change during a run, you cannot explain under what conditions the results were produced. Before-and-after comparisons can also end up comparing different questions.
Why is this technology needed?
If the criteria change during a run, you cannot explain under what conditions the results were produced. Before-and-after comparisons can also end up comparing different questions.
How it works
Separate the latest editable state from the snapshot used for execution. Tasks reference a snapshot ID and input hash, and changes create a new revision.
Accuracy is not the only consideration when designing the system. Latency, cost, data boundaries, refresh cadence, and behavior on failure must also be defined to make results reproducible in production. It is safer to leave values that automation cannot determine with confidence as unmeasured or requiring review, rather than turning them into 0 or marking them as successful.
Connection to SAG technology
SAG links the Goal revision and payload hash to each task. Result reports make it possible to verify the input version used through provenance, improving reproducibility and approval quality.
Practical checklist
- Do not overwrite a snapshot after execution
- Link every task to a Goal revision
- Check whether before-and-after comparisons use the same criteria
- Distinguish the status of failures, empty results, and permission errors from success
- Revalidate before and after changes under the same conditions
Research and official documentation
Reference documents support the principles and recommendations. They do not guarantee search visibility, AI mentions, rankings, or revenue; the actual effects of implementation must be verified through observations using service data under the same conditions.
How to explore this technology further
Explore tenant permissions, task retries, caching, and approval history.
SAG / KNOWLEDGE LINKS
