Skip to content

Feat: Add side effect support to runtime and examples#2

Merged
rian-be merged 1 commit into
mainfrom
develop
Jun 21, 2026
Merged

Feat: Add side effect support to runtime and examples#2
rian-be merged 1 commit into
mainfrom
develop

Conversation

@rian-be

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

Copy link
Copy Markdown
Contributor

Summary

Add side effect support to the runtime audit flow and demonstrate it in the workflow approvals example.

Added

  • Side effect support in mutation audit entries
  • A dedicated workflow approvals scenario that prints emitted side effects
  • Example side effects for workflow start and workflow rejection in WorkflowApprovals

Changed

  • SideEffect.Create(...) now supports explicit RequiresAction and timestamp values
  • SideEffect.Critical(...) now always marks the effect as requiring follow-up action
  • Runtime audit entry creation now carries MutationResult.SideEffects through to audit records
  • Runtime result logging now prints emitted side effects with severity and action flags
  • The rejected workflow scenario now executes an explicit rejection path after a blocking policy decision
  • ADR-006 status now reflects the accepted side effect design

Result

Side effects now move through the runtime audit path consistently and have a runnable example that shows both standard and critical effects, including the RequiresAction flag.

Testing

  • dotnet build src/ModularityKit.Mutator.csproj -c Release
  • dotnet build Examples/WorkflowApprovals/WorkflowApprovals.csproj -c Release

Linked Issues

  • None

Checklist

  • PR is focused and does not include unrelated cleanup
  • Public API changes are reflected in the example and ADR
  • New behavior follows the existing project structure
  • I followed the Code of Conduct

Added

- Side effect action and timestamp handling in the abstraction layer
- Audit entry coverage for mutation side effects
- Workflow approvals scenario dedicated to observable side effects
- Side effect emission examples for workflow start and workflow rejection

Changed

- Runtime audit entry creation now carries side effects through the execution pipeline
- Mutation result logging now prints emitted side effects with severity and action flags
- Rejected workflow scenario now executes an explicit rejection path after blocking policy decision
- ADR-006 status now reflects the accepted side effect design

Result

Side effects are now part of the runtime audit flow and are demonstrated in the runnable workflow example, including critical effects that require follow up action.
@github-actions github-actions Bot added documentation Documentation updates and additions architecture Design, structure, and API-shape changes abstractions Public abstractions and contracts runtime Runtime implementation and execution flow examples Runnable examples and sample apps labels Jun 21, 2026
@rian-be rian-be merged commit 9ae8b26 into main Jun 21, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

abstractions Public abstractions and contracts architecture Design, structure, and API-shape changes documentation Documentation updates and additions examples Runnable examples and sample apps runtime Runtime implementation and execution flow

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant