PUBLIC INTEGRATION GUIDE LXKeys integrations should consume canonical records and derive relation context from documented public interfaces rather than maintaining a separate relationship authority. For a record such as CS-1, use the canonical record endpoint for immutable data and the relation or graph endpoint for current context. A derived statement such as `corrected by CS-2` must never be written back into CS-1. The canonical relation remains on the later source record, for example `CS-2 corrects -> CS-1`. Registry Edition consumers should preserve both the canonical registry layer and the edition relational index. The relational index is reproducible from the edition's canonical records and may be regenerated independently. Third-party graph interfaces may visualize or search these relations, but must distinguish canonical record content from derived context and preserve disclosure rules.