Integrations
Integrations cross different authority boundaries. Before changing one, identify which layer owns the fact you need.
| Concern | Authority |
|---|---|
| Contract behavior | Contract source and tests |
| Recorded deployment | Chain deployment artifact |
| Schema identity | Schema configuration and deployment artifact |
| Indexed events | packages/indexer/config.yaml and handlers |
| Application access | Shared modules, hooks, and package exports |
| Semantic mapping | Ontology and generated entity matrix |
The generated integration pages own recorded status for Cookie Jar, ENS, Gardens, Hats, Hypercerts, Karma, and Octant. EAS, Authentication, and Tokenbound Accounts retain conceptual guidance because their cross-layer boundaries require explanation.
Do not infer live health from an address or code path. Activation, indexing, and external-service availability need separate operational evidence.