Save this content to: AGENTS.md

# Module agent guidance

<!-- module-architecture:begin -->
## Feature Flags — Filament package boundary

Read README.md, the [capability plan](https://github.com/liberusoftware/documentation/blob/main/projects/boilerplate/filament/feature-flags.md), [Filament standard](https://github.com/liberusoftware/documentation/blob/main/standards/FILAMENT.md) and [module architecture](https://github.com/liberusoftware/documentation/blob/main/architecture/MODULES.md). Exact source key: `liberusoftware/feature-flags`. Actual Composer identity: `liberusoftware/feature-flags-filament`.

- Preserve public source/package identities and application extension hooks. Do not silently replace canonical domain owners or import host App classes into reusable code.
- Keep policy, tenant context, validation, transactions, owned records and durable events authoritative in their core packages. Register only this capability's reviewed Filament resources/pages/widgets.
- Follow actual manifests and lockfiles. Use declared test/build scripts for implementation changes and meaningful allowed/denied/wrong-tenant checks for protected behavior.
- Keep secrets outside source. Distinguish installed, enabled, entitled and authorized states; do not treat UI visibility as authorization.
- Preserve existing implementation and upstream notices. Skeleton availability is not proof of feature parity or a published release.
<!-- module-architecture:end -->