Skip to content

Tags: ModularityKit/ModularityKit.Mutator

Tags

v0.1.6

Toggle v0.1.6's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Feat: Decompose governance query models and align runtime integrations (

#41)

## 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

- Closes #22

## Checklist

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

v0.1.5

Toggle v0.1.5's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Feat: Add Redis governance provider (#39)

## Summary
This PR implements the `ModularityKit.Mutator.Governance.Redis` provider
from scratch, bringing fully functioning, Redis backed governance
storage implementation to ecosystem. It also includes comprehensive
documentation and runnable examples.

## Added
- complete Redis governance provider implementation
- centralized Redis keyspace conventions and serialization strategy
- document and identifier set loading for efficient read side operations
- candidate selection and execution for distributed orchestration
- write side request persistence mechanism
- dedicated package README for `ModularityKit.Mutator.Governance.Redis`
- `RedisQueries` runnable example demonstrating Redis backed governance
queries
- `docker-compose.yml` for local Redis testing in the examples

## Result
The repository now provides fully implemented, Redis backed governance
provider. It correctly documents its capabilities, provides runnable
example for query workflows using Redis, and has accurate package
descriptions in the root overview. The new package is fully implemented,
closing out all underlying provider tasks.

## Testing
- verified local build
- verified `RedisQueries` example runs with local Redis container

## Linked Issues
- Closes #38
- Closes #37
- Closes #36
- Closes #35
- Closes #34
- Closes #33
- Closes #32
- Closes #31
- Closes #20
- Closes #8

## Checklist
- [x] Redis provider features are implemented
- [x] Redis package has dedicated package README
- [x] Redis governance queries example is provided
- [x] Root README correctly describes all packages

v0.1.4

Toggle v0.1.4's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Feat: Refresh docs, package assets, and core runtime concurrency (#30)

v0.1.3

Toggle v0.1.3's commit message
Ci: package publishing to trusted publishing

v0.1.2

Toggle v0.1.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Feat: Implement governance approval workflow (#15)

v0.1.1

Toggle v0.1.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Feat: Introduce governance package and execution model (#5)

## Summary

Introduce `ModularityKit.Mutator.Governance` as a separate package and
define the first governance execution model around mutation requests,
pending lifecycle, and request storage.

## Added

- Separate `ModularityKit.Mutator.Governance` package under `src/`
- Governance abstractions for mutation requests, lifecycle status,
pending reasons, request decisions, and request storage
- `InMemoryMutationRequestStore` as the first governance runtime
implementation
- Governance ADR set for package boundaries, mutation requests, pending
lifecycle, request storage, and versioned request resolution
- `Docs/Roadmap.md` and `Docs/ExecutionModel.md` to document the
governance direction and lifecycle model

## Changed

- Solution layout now includes the governance package alongside the core
runtime
- Core project excludes governance sources to preserve package
boundaries
- ADR index is split between core and governance decisions
- Repository documentation now explains the separation between direct
execution and governed request lifecycle work
- Governance README now follows the same documentation style as the rest
of the repository

## Result

The repository now has a clear architectural seam between direct
mutation execution and governance-specific request lifecycle work, so
future approval, pending execution, versioned resolution, and
persistence features can evolve without bloating the core package.

## Testing

- [x] `dotnet build src/ModularityKit.Mutator.Governance.csproj -c
Release`
- [x] `dotnet build ModularityKit.Mutator.slnx -c Release`

## Linked Issues

- [x] #3

## Checklist

- [x] PR is focused and does not include unrelated cleanup
- [x] New package boundaries are documented in ADRs
- [x] New behavior follows the existing repository structure under
`src/`
- [x] I followed the Code of Conduct