Summary
Add dedicated query read orchestration layer for Redis backed governance requests so candidate selection, document loading, and query result shaping are coordinated through clear read side pipeline.
Goal
Make Redis backed governance queries easier to evolve and reason about by separating query orchestration from candidate selection, document loading, and result materialization while preserving governance query semantics.
Scope
What should be implemented?
Acceptance Criteria
Notes
Candidate selection alone is not the Redis read side. The provider also needs coherent orchestration layer that turns candidate ids into materialized requests and then into the request, approval, and decision views expected by governance workflows.
This should align with the Redis provider query strategy and governance query API ADRs.
Related ADRs:
- ADR-026: Governance Request Query API
- ADR-029: Governance Redis Provider Package
- ADR-030: Governance Redis Request Storage and Query Strategy
Summary
Add dedicated query read orchestration layer for Redis backed governance requests so candidate selection, document loading, and query result shaping are coordinated through clear read side pipeline.
Goal
Make Redis backed governance queries easier to evolve and reason about by separating query orchestration from candidate selection, document loading, and result materialization while preserving governance query semantics.
Scope
What should be implemented?
ModularityKit.Mutator.Governance.Redis.Storage.Queriesarea for governance query readsAcceptance Criteria
Notes
Candidate selection alone is not the Redis read side. The provider also needs coherent orchestration layer that turns candidate ids into materialized requests and then into the request, approval, and decision views expected by governance workflows.
This should align with the Redis provider query strategy and governance query API ADRs.
Related ADRs: