# Next.js: preserve requirements through advanced agent edits

- [Authorize a Next.js Server Action at the database write](https://frameworkrecipes.dev/nextjs/server-action-ownership/guide.md): A Server Action is a server entry point. Hiding a button or protecting a layout does not authorize the mutation itself. Put identity scope and current state in the conditional write so the action remains protected when called directly.
- [action-write-authorization rule pack](https://reporules.fyi/nextjs/server-action-ownership/rule-pack.zip): YAML requirement and agent task.
- [Prevent private Next.js order responses from entering shared caches](https://frameworkrecipes.dev/nextjs/private-response-cache/guide.md): Authorization can be correct while a shared cache serves the previous customer’s response to the next request. Explicit private, no-store headers express the boundary to browsers and intermediaries; the tenant-scoped query expresses it to the database.
- [private-order-cache rule pack](https://reporules.fyi/nextjs/private-response-cache/rule-pack.zip): YAML requirement and agent task.
- [Framework rule pack](https://reporules.fyi/nextjs/rule-pack.zip): All requirements from this framework site.