Skip to content

Feat: Decompose governance query models and align runtime integrations#41

Merged
rian-be merged 16 commits into
mainfrom
develop
Jun 29, 2026
Merged

Feat: Decompose governance query models and align runtime integrations#41
rian-be merged 16 commits into
mainfrom
develop

Conversation

@rian-be

@rian-be rian-be commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Summary

Decompose the governance query model into grouped request filters plus dedicated approval and decision namespaces, then align runtime, Redis, docs, examples, and tests with that split.

Added

  • grouped request query filters for scope, actor, intent, metadata, lifecycle, and time range
  • MutationRequestQueries presets for common governance request query shapes
  • approval and decision query models under dedicated namespaces
  • MutationRequestDecision category-specific helpers for lifecycle, approval, and version-resolution decisions
  • ADR-033 covering governance query model decomposition
  • regression coverage for grouped query filters, metadata scope separation, decision helpers, governed execution metadata propagation, and Redis serialization roundtrips

Changed

  • governance request queries no longer accumulate all filters on one flat MutationRequestQuery surface
  • runtime and in-memory governance query flows now resolve the decomposed request query model and dedicated approval and decision types
  • Redis candidate selection, query reading, materialization, and ordering now use the decomposed query namespaces and grouped filters
  • governed execution now carries request and intent metadata through execution-facing audit surfaces
  • governance and Redis examples now use the updated query namespaces and decision helper factories
  • governance and Redis docs now reflect the decomposed query API and practical usage surface

Result

The governance read model is now organized by concern instead of one expanding flat query namespace. Request filters have clearer ownership, approval and decision projections are separated cleanly, and the runtime plus Redis integrations stay aligned with the same query contracts. The execution path also preserves richer governance metadata for downstream audit and history consumers.

Testing

  • dotnet test Tests/ModularityKit.Mutator.Governance.Tests/ModularityKit.Mutator.Governance.Tests.csproj
  • dotnet test Tests/ModularityKit.Mutator.Governance.Redis.Tests/ModularityKit.Mutator.Governance.Redis.Tests.csproj
  • dotnet build Examples/Governance/Queries/Queries.csproj
  • dotnet build Examples/Governance/RedisQueries/RedisQueries.csproj

Linked Issues

Checklist

  • governance query abstractions are decomposed into request, approval, and decision concerns
  • runtime and Redis query flows are aligned with the new grouped filter model
  • docs, examples, and tests cover the updated governance query surface

@github-actions github-actions Bot added documentation Documentation updates and additions architecture Design, structure, and API-shape changes examples Runnable examples and sample apps tests Test coverage and test changes labels Jun 29, 2026
@rian-be rian-be merged commit 41f747e into main Jun 29, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

architecture Design, structure, and API-shape changes documentation Documentation updates and additions examples Runnable examples and sample apps tests Test coverage and test changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Task]: Persist and expose governance metadata

1 participant