# Future Enhancements

## Dynamic Key Names

LocalData currently enforces exact, statically-registered key names for auditability.
If we decide to allow dynamic names later (e.g., per-account keys), the suggested design is:

- Add a name rule type (e.g., `StorageKeyNameRule`) that supports `exact` and `prefix` matching.
- Extend `StorageKeyEntry` to carry a name rule.
- Update catalog registration to validate overlapping rules and duplicates.
- Update `StorageRouter` validation to accept keys that match the registered rules.
- Require a catalog entry that documents the dynamic name pattern and rationale.

This keeps audit behavior explicit while allowing a controlled, documented escape hatch.