Summary
Benchmark the governance approval workflow so the cost of assigning, approving, rejecting, and expiring approval requirements stays visible over time.
Goal
Measure the overhead of the approval workflow path that turns governance policy requirements into request-level approval actions and terminal approval outcomes.
Problem
Governance already models approval requirements, approval workflow state, and approval actions, but that path is not benchmarked as a dedicated runtime surface.
Without a benchmark for approval workflow behavior, changes in approval assignment, approval completion, rejection handling, or expiration processing can quietly add overhead without being visible in runtime measurements.
Scope
Design Expectations
- The benchmark should measure a real approval workflow rather than a toy loop.
- Approval assignment and terminal approval outcomes should stay visible where possible.
- Helper code should stay local to the benchmark project.
- Scenario names should make the approval path obvious.
Suggested Measurements
- request with pending approvals approved successfully
- request with pending approvals rejected
- request with pending approvals expired
Acceptance Criteria
Non-Goals
- This issue does not change governance runtime behavior
- This issue does not add provider-specific persistence benchmarks
- This issue does not optimize approval workflow prematurely
- This issue does not add full integration or load testing
Notes
This issue is a child of the governance benchmark umbrella #73.
Summary
Benchmark the governance approval workflow so the cost of assigning, approving, rejecting, and expiring approval requirements stays visible over time.
Goal
Measure the overhead of the approval workflow path that turns governance policy requirements into request-level approval actions and terminal approval outcomes.
Problem
Governance already models approval requirements, approval workflow state, and approval actions, but that path is not benchmarked as a dedicated runtime surface.
Without a benchmark for approval workflow behavior, changes in approval assignment, approval completion, rejection handling, or expiration processing can quietly add overhead without being visible in runtime measurements.
Scope
Design Expectations
Suggested Measurements
Acceptance Criteria
Non-Goals
Notes
This issue is a child of the governance benchmark umbrella
#73.