Keto example permission model doesn't traverse graph

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Ory Network Project

https://gracious-hypatia-b9te8t22yp.projects.oryapis.com

Describe the bug

Following steps in this guide: https://www.ory.sh/docs/keto/modeling/create-permission-model

Created a bug here as the documentation should make clearer how to the setup relationships to make the permission model work.

Please let me know if I understand something fundamentally wrong about the way the permission model is supposed to work :)

Reproducing the bug

1. Go the permission model page
2. Copy code of permissions-v5.ts
3. Go to https://console.ory.sh/projects/-/permissions/configuration
4. Paste the code under "Permission Rules"
5. Click save
6. Go to relationships: https://console.ory.sh/projects/-/permissions/relationships
7. Create the following two relationships:
8. userA is owners of Folder:folderA
9. folderA is parents of Document:docA
10. Make the following request: https://-.projects.oryapis.com/relation-tuples/check?namespace=Document&object=docA&relation=share&subject_id=userA&max-depth=100

Expected: /relation-tuples/check returns {"allowed": true}
Actual: /relation-tuples/check returns {"allowed": false}

Relevant log output

No response

Relevant configuration

No response

Version

v0.13.0-alpha.0

On which operating system are you observing this issue?

Ory Network

In which environment are you deploying?

Ory Network

Additional Context

Permission v3 and v4 don't work. Permission v5 works again (which is marked as optional) :D

Start with docs/keto/modeling/create-permission-model.mdx, especially the permissions-v5.ts example referenced in lines 315-361, and reproduce the listed relationships and relation-tuples/check request. Compare the documented permission model versions and relationship setup. Done means the guide clearly explains the required relationships and the documented example produces the expected allowed result.