Adapter Requirements for FACET-compatible Providers
This document defines normative requirements for FACET-compatible provider adapters, which are responsible for translating Canonical JSON into provider-specific payloads.
Why it matters
These adapter requirements are crucial for ensuring interoperability and reproducibility in AI/ML systems that leverage multiple provider APIs.
Key Points
- 1Adapters must be behaviorally passive and not introduce new logic, infer missing data, or apply provider-specific heuristics
- 2Adapters must provide deterministic mapping, preserve provider constraints, and maintain a one-to-one structural mapping
- 3Adapters must be a failure boundary and not compromise reproducibility guarantees
Details
The article outlines the core principles and architectural position of FACET adapters. Adapters are required to be deterministic, not perform semantic repair, treat provider constraints as declarative inputs, maintain one-to-one structural mapping, and contain failures. They are explicitly prohibited from performing validation, type checks, or accessing external resources. Adapters must declare supported Canonical JSON versions and include comprehensive testing. The rationale behind the adapter constraints is to prevent vendor lock-in, localize API churn, and enable provider interoperability.
No comments yet
Be the first to comment