I have some architectural design questions and suggestions for Ory. First and foremost: 1. Is there a way to synchronize Identifiers (and identites) between Ory Keto and an External Database e.g. PostgreSQL 10+ has a separate way of generating unique identities, conforming to SQL standard. It's also important to notice that there are multiple way to encode and pack an UUID/GUID into a Int64 (https://instagram-engineering.com/sharding-ids-at-instagram-1cf5a71e5a5c). So it would've been nice if Ory had support for Numeric Identifiers and a way to synchronize Identities. Ideally, it could be some sort of Postgres FDW and a set of triggers. Ofc I'll need to dig into Ory persistence and research how to supply multiple schemas, so the exact database schema would be compact in terms of data locality and storage. 2. There are multiple ways to do Policy checks, e.g. there's Supabase with their Gotrue (https://github.com/supabase/gotrue) and an AI assisted policy management (https://supabase.com/blog/studio-introducing-assistant). It would be nice to implement an AI assisted policy creation for Ory Keto, as well. And supabase Policy sync would also help with onboarding Supabase adopters to Ory. p.s. I'm a 32 y.o. ukrainian solution architect / cto downshifting to an R&D position, now looking for a short-term contract job and contributing to OSS projects.