---
title: "External Collection Adapters and Fallbacks: When Does a Substitute Response Count as Success?"
slug: "provider-adapter-fallback-contract"
language: "en"
tags: ["수집 어댑터","아키텍처 노트","sag 기술","플랫폼 운영"]
created: "2026-10-06T08:00:00.000Z"
published: "2026-10-08T10:15:43.354Z"
updated: "2026-10-08T10:15:48.579Z"
sample: false
---

# External Collection Adapters and Fallbacks: When Does a Substitute Response Count as Success?

## What Is a Collection Adapter?

**It is the boundary that converts external service inputs, errors, and source data into common observations.** This note describes collection adapters in terms of their responsibilities for input, transformation, and output rather than by feature name. To trust an analysis result, it must be possible to trace what data came in, what was verified, and how far the conclusions can go.

## Why Is This Technology Needed?

Replacing an API failure with an example and marking it as success can be mistaken for actual collection. Recovering a call and substituting a result are different.

## Design Principles and Data Flow

Return the provider, conditions, source data, and validity status, and distinguish retries, fallback providers, and unobserved results. Keep examples separate from the measured-data storage path.

> **External provider** → **Common observation validation** → **Measured / unobserved**

Each stage must not relabel the success of the previous stage as an achievement of the next. Recording the data identifier, period, and validation status throughout makes it possible to locate where omissions or errors occurred and determine what needs to be checked again.

## Connection to the SAG Architecture

SAG observations record the provider and the conditions of the source data. Actual calls require operational connection settings; examples without a connection are not measured data.

SAG’s operational value lies in connecting these relationships to pages and questions, comparison results, and improvement tasks. Rather than reading only the numbers, customers can review both what needs strengthening and the basis for the judgment. Patterns that require additional application should be interpreted within the scope of the relevant paragraph.

## Illustrative Examples and Evaluation Criteria

An illustrative key that is not configured means insufficient configuration, not rank 0. If a call is made through an approved fallback provider, that provider and its source data must be recorded as a new observation.

The example above is provided to explain the structure and calculation; it is not a measured result from any particular customer. Actual reports must link the selected period, target, observation conditions, and source-data records so the same judgment can be verified again.

## Practical Verification Checklist

| Flow stage | Item to check |
| --- | --- |
| External provider | Distinguish not connected from call failure |
| Common observation validation | Record substitute source data |
| Measured / unobserved | Do not store examples as measured data |

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

## Limitations and Points to Consider When Applying

Changing providers can also change the conditions for comparison. Recovery success and identical conditions must be checked separately.

## Research and Official Documentation

- [IETF HTTP Semantics RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html) — A standard for verifying the meaning of HTTP requests, responses, and statuses.

The external reference provides background on the design topic above; it does not certify every SAG implementation or customer result. The application guidance and illustrative examples in this note are organized according to SAG’s operational structure. Source checked: 2026-10-06.

## Further Reading and Feature Verification

- [Related architecture note](/ko/blog/ai-answer-observation-methodology)
- [Try the service connected to the collection adapter](/ko/preview/geo?scenario=cream)
- [Feature-specific FAQ](/en/faq)
- [Discuss implementation scope](/ko#inquiry)


## How to Continue Reading About This Technology

Review tenant permissions, task retries, caching, and approval history.

- [Designing a stable customer space](/ko/blog?tag=%ED%94%8C%EB%9E%AB%ED%8F%BC%20%EC%9A%B4%EC%98%81)
- [Feature guide FAQ](/en/faq)