pattern-storage-user-data
Enterprise Part of the commercial Kumiko Enterprise offering — not in the open framework.
GDPR (Art. 20 export / Art. 17 erasure) coverage for pattern-storage’s pattern-file entity. Mounts the EXT_USER_DATA export + delete hooks so a Builder’s authored pattern-files are included in the data export; delete hard-purges them, anonymize severs the author link but keeps the source (it’s the tenant’s live app code). Kept separate from pattern-storage so consumers without the user-data-rights pipeline don’t pull a hard dependency — requires pattern-storage, user-data-rights.
Build it yourself
Section titled “Build it yourself”This Enterprise implementation is optional. If you need a narrower or domain-specific version, you can build an app-owned feature, handler, or job with Kumiko’s public extension points.
Use this package when you want the maintained implementation, its existing contracts, and the surrounding operational behavior. A custom implementation is not drop-in compatible automatically: your app owns its authorization, validation, integrations, tests, security review, and production operations.
Start with Features and composition and Custom write handlers.
How it fits
Section titled “How it fits”What this feature needs to run (Requires).
flowchart TB
n_pattern_storage_user_data["pattern-storage-user-data"]
subgraph how_reqs["Requires"]
n_pattern_storage["pattern-storage"]
n_user_data_rights["user-data-rights"]
end
n_pattern_storage --> n_pattern_storage_user_data
n_user_data_rights --> n_pattern_storage_user_data
Dependencies
Section titled “Dependencies”- Requires:
pattern-storage,user-data-rights - Activation: always on (not toggleable)
Extensions & cross-feature APIs
Section titled “Extensions & cross-feature APIs”- Registers extension:
userData→pattern-file