Summary
Persist version resolution outcomes through a governance runtime path so stale-resolution decisions cannot be dropped accidentally by callers.
Goal
Make governance version resolution auditable by default instead of relying on callers to remember to save the mutated request returned from Resolve(...).
Scope
What should be implemented?
Acceptance Criteria
Notes
Implemented through:
- pure
MutationRequestVersionResolver retained as the evaluator
IMutationRequestVersionResolutionManager
MutationRequestVersionResolutionManager.ResolveAndStore(...)
- optimistic concurrency via
IMutationRequestStore.TryStore(...)
- updated governance
VersionedResolution example
- regression coverage in
MutationRequestVersionResolutionPersistenceTests
The old characterization proving dropped in-memory decisions remains, and is now paired with persisted-path tests that assert the governance runtime stores the resulting resolution state and decision history.
Summary
Persist version resolution outcomes through a governance runtime path so stale-resolution decisions cannot be dropped accidentally by callers.
Goal
Make governance version resolution auditable by default instead of relying on callers to remember to save the mutated request returned from
Resolve(...).Scope
What should be implemented?
ResolveAndStoreor equivalent orchestration for version resolutionAcceptance Criteria
VersionValidated,RejectedAsStale,RevalidationRequired, orRenewedApprovalRequiredthrough a persisted runtime pathModularityKit.Mutator.GovernanceNotes
Implemented through:
MutationRequestVersionResolverretained as the evaluatorIMutationRequestVersionResolutionManagerMutationRequestVersionResolutionManager.ResolveAndStore(...)IMutationRequestStore.TryStore(...)VersionedResolutionexampleMutationRequestVersionResolutionPersistenceTestsThe old characterization proving dropped in-memory decisions remains, and is now paired with persisted-path tests that assert the governance runtime stores the resulting resolution state and decision history.