Ground Integrations In Primary Sources
BOUNDARY-GROUND-INTEGRATIONS-IN-PRIMARY-SOURCES
Summary
Base adapter behavior on provider docs, specs, or captured API responses before encoding local assumptions. When primary sources are incomplete, label observations and inferences so guesses do not become fake guarantees.
Rule
Ground integration behavior in primary source documentation.
Why
Provider and platform behavior changes, and memory of an integration is often wrong. Primary docs, specs, or observed API responses should define the boundary contract before local wrappers encode assumptions about names, TTLs, error codes, features, or protocol shapes.
Helps
- Keeps adapters honest and makes integration limits reviewable.
Limits
When primary sources are incomplete, record what is observed and label the inference. Do not present guesses as provider guarantees.
Agent Instruction
Ground integration behavior in primary source documentation because provider and platform behavior
changes.Mechanisms
Supported by source links, captured examples, integration fixtures, adapter docs, and tests that assert documented provider behavior.