@magnificent-energy-493 @curved-nail-40535 Thanks. I think we would want at least the action, the subject of the action, the target if applicable, a timestamp, error indicator (is this event an error), any permissions info (e.g. added permission X, removed permission X, access denied due to permission X). Definitely all events around access decisions in Keto are desired, but it should be uniform throughout all the Ory stack. It seems from my research that the plan is to rely on the logging pipeline, which may not be the best approach for an authoritative audit record. I think it would make much more sense to implement a hooks system similar to Kratos, or create an entirely new events api that can be gathered up.
This is essentially a determining factor for us adopting the Ory stack. Is there any kind of timeline on when even an initial implementation would be ready for testing?