Summary
Add dedicated serialization layer for Redis backed governed mutation requests so request documents, metadata values, and provider payloads can be written and read consistently.
Goal
Make Redis payload handling explicit, reusable, and compatible with the governance request model instead of scattering JSON serialization details across persistence and query code.
Scope
What should be implemented?
Acceptance Criteria
Notes
Redis backed governance depends on stable document format. Serialization is not just an implementation detail here; it defines how request data survives round trips, how metadata remains usable, and how future package versions can evolve safely.
This should align with the Redis provider architecture and document compatibility ADRs.
Related ADRs:
- ADR-029: Governance Redis Provider Package
- ADR-030: Governance Redis Request Storage and Query Strategy
- ADR-031: Governance Redis Serialization and Document Compatibility
Summary
Add dedicated serialization layer for Redis backed governed mutation requests so request documents, metadata values, and provider payloads can be written and read consistently.
Goal
Make Redis payload handling explicit, reusable, and compatible with the governance request model instead of scattering JSON serialization details across persistence and query code.
Scope
What should be implemented?
ModularityKit.Mutator.Governance.Redis.Serializationarea for Redis payload handlingMutationRequestdocumentsAcceptance Criteria
Notes
Redis backed governance depends on stable document format. Serialization is not just an implementation detail here; it defines how request data survives round trips, how metadata remains usable, and how future package versions can evolve safely.
This should align with the Redis provider architecture and document compatibility ADRs.
Related ADRs: