Where to go next

• Reference — every option, tag, and lifecycle detail: README
• Working app — all of the above, running: the handler-example app (not yet published as a standalone repo)
• The one idea to keep — authorization is schema-shaping, enforced both inbound (params filtered before call) and outbound (return value projected onto the caller's schema). You shape what each user sees; the gem makes the shape a boundary.

Collected from COOKBOOK.md in the repository. Edit it there, not here.